Yes! Right now we have @machawk1's WARCreate for Chrome (https://warcreate.com ), but having fully archive/Memento-aware browsers would enable many new use cases and applications.https://www.slideshare.net/mweigle/enabling-personal-use-of-web-archives/73 …
-
-
Yes, it would be awesome if WARCreate could bundle the created WARC file with a little HTML and JavaScript viewer along the lines of wabac.
1 reply 0 retweets 4 likes -
We discussed the idea of a landing page annotation in a WARC file (a while ago in
@NetPreserve's Slack and internally at@WebSciDL). The intent was to be able to open a WARC file in a browser, have it be indexed and served using#Reconstructive as a supercharged MHTML.1 reply 0 retweets 7 likes -
Replying to @ibnesayeed @weiglemc and
Yes, clearly wabac.js is based on
@WebSciDL's work here, as Ilya said in that thread. I definitely can see the place for saving collection metadata in the WARC file. But I was wondering if there could be a simple convention for bundling up the WARC data w/ a wabac player.pic.twitter.com/H7zMcui3Bx
3 replies 0 retweets 3 likes -
The
#ServiceWorker requires that it is associated with an origin and server over HTTPS (except localhost). It does not work with file:/ URI. So, this type of duplicate inclusion of a replay system is not that useful really.2 replies 0 retweets 0 likes -
Replying to @ibnesayeed @weiglemc and
Yes, I know about sw and https. A large portion of the web is https now so it's not a bit issue. But I'm not following what you mean about duplicate inclusion of a replay system...
1 reply 0 retweets 1 like -
To answer that, I need to understand the purpose of that directory organization you proposed. I thought you were asking for tools like
#WARCreate to bundle a replay system with each WARC file which a user can open in a browser locally, but the replay won't work on file:/ URIs.1 reply 0 retweets 0 likes -
Replying to @ibnesayeed @weiglemc and
Local browsing would definitely be great. But I was thinking the bundle would be useful for mounting on the web somewhere. We already have WebrecorderPlayer for reading locally/offline.
1 reply 0 retweets 0 likes -
For that we need only one instance of the replay (which can be downloaded independently or loaded from
@github pages once, which can work offline). I personally think it would be an overkill to add more structure around WARC files and ship a non-upgradable replay with each WARC.1 reply 0 retweets 1 like -
Replying to @ibnesayeed @weiglemc and
Hmmm, you might be right. It might help if I put the idea into code instead of just into tweets...
1 reply 0 retweets 3 likes
Dir structure is certainly useful for many reasons, as WARC alone are not enough to represent a 'web archive collection' with all additional metadata, indexes. Bundling replay engine is a separate interesting q, becomes much easier if it itself is just a couple of JS files
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.