Twitter | Pretraživanje | |
Ilya Kreymer 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 CNI keynote:
Reply Retweet Označi sa "sviđa mi se"
Ilya Kreymer 27. lip
Odgovor korisniku/ci @IlyaKreymer
As DSHR suggests, alternate replay systems like could more easily display the temporal range of a given page instead of a single date. Here's another quick example from
Reply Retweet Označi sa "sviđa mi se"
Ilya Kreymer 27. lip
Odgovor korisniku/ci @IlyaKreymer
But what if the 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:
Reply Retweet Označi sa "sviđa mi se"
Ilya Kreymer 27. lip
Odgovor korisniku/ci @IlyaKreymer
By archiving a client-side replay system like , 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:
Reply Retweet Označi sa "sviđa mi se"
Ilya Kreymer
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!
Reply Retweet Označi sa "sviđa mi se" More
Sawood Alam 27. lip
Odgovor korisniku/ci @IlyaKreymer
This replay embedding is both cool and clever!
Reply Retweet Označi sa "sviđa mi se"