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
{{ message }}
This repository has been archived by the owner on Sep 17, 2020. It is now read-only.
I'm having trouble opening twitter archives in webrecorderplayer. These archives are created with Webrecorder. Twitter isn't the only problem I've had but it's my most used site for archiving. Twitter appears to try loading the page but then says "Something went wrong. Try again" like Twitter is actually trying to load instead of browsing the file. Even though it's no longer maintained Webarchiveplayer is able to open the file within seconds and browse successfully. I usually use that for my warc playback but I keep giving Webrecorderplayer a try on every version.
I can't view the archive with webrecorderplayer until I copy the page URL in the app's lower left corner, click help, expand the debug section, open up the app host URL, and finally append the collection link to http://localhost:XXXXX/local/collection. After that it takes around 10-20 minutes to load depending on the size of the warc file.
What's causing the difference between webarchiveplayer and webrecorderplayer? Is there something I'm doing wrong with these archives or any other settings I have to tweak for webrecorderplayer to work?
The text was updated successfully, but these errors were encountered:
Bumping this to say:
I have the same problem - Webrecorder Player won't display Twitter content and tells me that "Something went wrong" while pywb inside the brozzler installation I am running is displaying the Twitter pages without issue.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm having trouble opening twitter archives in webrecorderplayer. These archives are created with Webrecorder. Twitter isn't the only problem I've had but it's my most used site for archiving. Twitter appears to try loading the page but then says "Something went wrong. Try again" like Twitter is actually trying to load instead of browsing the file. Even though it's no longer maintained Webarchiveplayer is able to open the file within seconds and browse successfully. I usually use that for my warc playback but I keep giving Webrecorderplayer a try on every version.
I can't view the archive with webrecorderplayer until I copy the page URL in the app's lower left corner, click help, expand the debug section, open up the app host URL, and finally append the collection link to
http://localhost:XXXXX/local/collection
. After that it takes around 10-20 minutes to load depending on the size of the warc file.What's causing the difference between webarchiveplayer and webrecorderplayer? Is there something I'm doing wrong with these archives or any other settings I have to tweak for webrecorderplayer to work?
The text was updated successfully, but these errors were encountered: