3 ms·
It's probably a replay of what you did. I'm trying to think how the internals would be made using Javascript, but probably it's a case of recording changes to t
by netsharc 7y ago
It's probably a replay of what you did. I'm trying to think how the internals would be made using Javascript, but probably it's a case of recording changes to the DOM structure ("After 3 seconds, the password input field had the value 'hunter2'. After 5 seconds, a DIV appears with the the text 'Incorrect password'", etc).
- amelius 7y agoMakes sense, but I wouldn't call it an "interactive copy".
- jrochkind1 7y agoI am also just interpreting the copy on the OP, but I don't think it's just a replay -- I imagine they record all HTTP requests and responses, so can echo back the recorded response for any given JS query to server, when it's triggered. 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.
- drewmol 7y ago>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.)
- amelius 7y agoThis wouldn't work for websites using more advanced techniques where ordering of requests matters.
- jrochkind1 7y agoRight, it would not and presumably does not work universally. Hopefully it works on a great enough majority to be useful.
- amelius 7y agoThe problem is that at save-time you want to know if it works. It would be very annoying if you thought you saved something but it turns out to be not the case.
- yrio 7y agoNo this doesn't record DOM structure changes. 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 https://github.com/webrecorder/webrecorder-player/releases