> Webrecorder creates an interactive copy of any web page that you browse, including content revealed by your interactions such as (...) clicking buttons, and so forth.
How can they guarantee this if the code may run on the server?
How can they guarantee this if the code may run on the server?
The page linked says:
> Webrecorder takes a new approach to web archiving by capturing ("recording") network traffic and processes within the browser while you interact with a web page. Unlike conventional crawler-based web archiving methods, this allows even intricate websites, such as those with embedded media, complex Javascript, user-specific content and interactions, and other dynamic elements, to be captured and faithfully restaged.
and:
> Webrecorder creates an interactive copy of any web page that you browse, including content revealed by your interactions such as playing video and audio, scrolling, clicking buttons, and so forth.
I think they record whatever HTTP transactions you trigger, so they can be played back when triggered in the replay.
That could be a useful history for circumventing forced usability reductions when a site 'upgrades' but doesn't change the request structure and/or doesn't deny access/EOL a previous API version but just hides the old interface after a makeover.
For example: I would love to have a recording of sessions from the previous version of ESPN's html fantasy football interface with a record of request to see if I could roll my own so to speak.
(ESPN ruined the usability of the site by rewriting it in some Javascript framework hoping to annoy users into app conversions last year.)
It would be very annoying if you thought you saved something but it turns out to be not the case.
Instead this captures network traffic (bytes) into a .warc file. Then you can replay it later (from the website) or you can download the .warc file to your computer & play it offline using the desktop app (Webrecorder player app) see the bottom of the page or [1]
The downside is that the desktop app is slow (5 seconds to loads a page on my laptop). I've created a fast player app that loads pages instantly, but I haven't open sourced it yet ;)
[1] https://github.com/webrecorder/webrecorder-player/releases