https://wab.ac/ loads WARC and HAR files directly in the browser, to be rendered for replay using service workers.
WARC support made possible using the excellent https://github.com/N0taN3rd/node-warc … by @johnaberlin
-
-
Show this thread
-
An example to load and index a WARC from github pages: https://wab.ac/?coll_example=examples/netpreserve-twitter.warc … Load and redirect to a replayed page, all running from github pages: https://wab.ac/?coll_example=examples/netpreserve-twitter.warc&url=example/https://twitter.com/netpreserve … (Examples might require 2nd try to load, this is a prototype!)
Show this thread -
If web archive replay can happen entirely in the browser, the 'web archive' can be a simple file and index store, simplifying web archive integration with data repositories and reducing complexity of web archive servers
Show this thread -
More deep integration of web archives with p2p and dweb systems like
@dat_project and@IPFSbot seems within reach. Running https://wab.ac on dat:// in@BeakerBrowser is unfortunately currently blocked byhttps://github.com/beakerbrowser/beaker/issues/46 …Show this thread -
This all works thanks to service workers, now supported in all major browsers, including mobile:https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API …
Show this thread -
http://wab.ac uses components from pywb for replay, but is an early proof-of-concept prototype and intended for testing. much more work is needed to match fidelity of our existing systems such as pywb and
@webrecorder_io -- please use carefullyShow this thread -
Finally, I also want to acknowledge
@ibnesayeed and@machawk1 for their work on https://github.com/oduwsdl/ipwb and https://github.com/oduwsdl/Reconstructive … in first exploring web archive replay with service workers, and@anjacks0n for first suggesting a web archiving use case for SWsShow this thread
End of conversation
New conversation -
-
-
I’m super excited to learn more!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.