|
@IlyaKreymer | |||||
|
But what if the wab.ac could be used to improve fidelity and trust of existing web archives, and address limitations of existing replay systems, all w/o costing any more $ to operate ?
This is now possible, as a proof-of-concept, at:
web.archive.org/web/https://wa…
|
||||||
|
||||||
|
Ilya Kreymer
@IlyaKreymer
|
27. lip |
|
Thread #2: What if wabac.js / client-side replay could be used to improve trust in web archives through better transparency, as DSHR calls for in part 3 of his critique of @phonedude_mln CNI keynote: blog.dshr.org/2019/06/michae… twitter.com/IlyaKreymer/st…
|
||
|
|
||
|
Ilya Kreymer
@IlyaKreymer
|
27. lip |
|
As DSHR suggests, alternate replay systems like oldweb.today could more easily display the temporal range of a given page instead of a single date. Here's another quick example from wab.ac pic.twitter.com/iI4lyIP5ZN
|
||
|
|
||
|
Ilya Kreymer
@IlyaKreymer
|
27. lip |
|
By archiving a client-side replay system like wab.ac, it may be possible to create an alternate replay system from within an existing one
For example, it should be possible to load an alternative replay of IA's wayback by loading:
web.archive.org/web/https://wa…
|
||
|
|
||
|
Ilya Kreymer
@IlyaKreymer
|
27. lip |
|
Client-side web archive replay can blur the line between an archived page and an archive, but perhaps also provide additional transparency and insight into how the web archive replay process works by moving most of the hard work to the browser itself!
|
||
|
|
||