You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you expect to happen? What happened instead?
The tv2.dk front page was crawled with brave archiveWeb chromium extension at Thursday 11:16 where the building still was burning - and replay there is ok - even though it did'not get the video:
But when I upload the wacz file to browsertrix is shows a newer video AFTER the fire was extinguished:
Here you can download the wacz crawled with brave archiveWebpage extension v0.12.2: https://drive.google.com/file/d/1yHXfm_Z_xwIpN8wNn9t1UHoAI8Y-yDKV/view?usp=sharing
When i try to go through all the .ts video segments in the resourcelist - are they all newer than the burning image. It seems not to have crawled the video at that time, but uses a newer harvested instead. Perhaps it has something todo with the way tv2 has coded the replay of the video urls?
I'm not sure if it is a brave archiveWebpage or a browsertrix replay problem.
Reproduction instructions
se above
Screenshots / Video
No response
Environment
No response
Additional details
No response
The text was updated successfully, but these errors were encountered:
Browsertrix Version
v1.10.2-dc9069d
What did you expect to happen? What happened instead?
The tv2.dk front page was crawled with brave archiveWeb chromium extension at Thursday 11:16 where the building still was burning - and replay there is ok - even though it did'not get the video:
But when I upload the wacz file to browsertrix is shows a newer video AFTER the fire was extinguished:
Here you can download the wacz crawled with brave archiveWebpage extension v0.12.2: https://drive.google.com/file/d/1yHXfm_Z_xwIpN8wNn9t1UHoAI8Y-yDKV/view?usp=sharing
When i try to go through all the .ts video segments in the resourcelist - are they all newer than the burning image. It seems not to have crawled the video at that time, but uses a newer harvested instead. Perhaps it has something todo with the way tv2 has coded the replay of the video urls?
I'm not sure if it is a brave archiveWebpage or a browsertrix replay problem.
Reproduction instructions
se above
Screenshots / Video
No response
Environment
No response
Additional details
No response
The text was updated successfully, but these errors were encountered: