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: https://blog.dshr.org/2019/06/michael-nelsons-cni-keynote-part-3.html …https://twitter.com/IlyaKreymer/status/1144052239033499650 …
-
Prikaži ovu nit
-
As DSHR suggests, alternate replay systems like http://oldweb.today could more easily display the temporal range of a given page instead of a single date. Here's another quick example from https://wab.ac pic.twitter.com/iI4lyIP5ZN
1 reply 0 proslijeđenih tweetova 1 korisnik označava da mu se sviđaPrikaži ovu nit -
But what if the http://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: https://web.archive.org/web/https://wab.ac/ …
1 reply 0 proslijeđenih tweetova 1 korisnik označava da mu se sviđaPrikaži ovu nit -
By archiving a client-side replay system like http://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: https://web.archive.org/web/https://wab.ac/#/20180131235341|https://www.cnn.com/ …
1 reply 0 proslijeđenih tweetova 2 korisnika označavaju da im se sviđaPrikaži ovu nit -
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!
1 reply 0 proslijeđenih tweetova 2 korisnika označavaju da im se sviđaPrikaži ovu nit
This #WebArchiving replay embedding is both cool and clever!
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.