{"id":867,"date":"2023-03-28T21:32:22","date_gmt":"2023-03-28T21:32:22","guid":{"rendered":"http:\/\/blogs.harvard.edu\/perma\/?p=867"},"modified":"2023-03-28T21:33:22","modified_gmt":"2023-03-28T21:33:22","slug":"867","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/perma\/2023\/03\/28\/867\/","title":{"rendered":"New Release: High Fidelity Capture Engine for Witnessing the Web 🍨"},"content":{"rendered":"

This week the Perma team is releasing new software that is a building block for any individual or organization creating a web archive. Scoop is a <\/span>highly-tunable single page capture library that prioritizes fidelity and provenance, drawing on our decade of experience archiving citations for law journals and courts. \u00a0 \u00a0 \u00a0<\/span><\/p>\n

\n

When designing Scoop, we focused on making high-quality, signed web captures that you can take with you and host anywhere you want, while still being able to verify where they came from.<\/span><\/p>\n

Why does that matter? Because we want to update how people talk to each other \u2014 and convince each other \u2014\u00a0about what content has been on the web.<\/span><\/p>\n

We\u2019ve all seen them: the contextless, but authentic-looking screenshot tweeted out to thousands of followers and proliferated throughout different networks, often jumping platforms.\u00a0<\/span><\/p>\n

Media literacy and years of experience seeing photoshopped or faked content could help you parse what is real and what is fake, but the more time we spend on the internet and seek our news there, the more we will fall victim to inauthentic web content. Given the state of information on the web, this is likely to <\/span>only get worse<\/span><\/a>, not better.\u00a0<\/span><\/p>\n

Our IT departments and savvy-minded friends will give us tips on how to avoid phishing scams: call the friend directly, log into your bank account via the online portal instead of clicking that link, or otherwise meet the information at its source to guarantee you\u2019re not being duped. How do we validate authenticity, though, when the thing we\u2019re seeking is fragile: a dynamic web page, <\/span>vulnerable<\/span><\/a> to<\/span> link rot<\/span><\/a>?\u00a0<\/span><\/p>\n

We trust things that we know represent reality as much as possible, and we trust things that we know the origin of. Basically, we trust witnesses.\u00a0<\/span><\/p>\n

Here\u2019s the thing: running a web archive up to this point has been so complex that it is necessarily centralized. Witnessing what is on the web has come down to just a few centralized archives who are trusted to maintain their collections, whether it is the indispensable Internet Archive or our own Perma.cc.<\/span><\/p>\n

Even the most established archives have potential to <\/span>be manipulated<\/span><\/a>, and no one archive can serve all the needs our users have for web witnessing. With tools like Scoop, and others pioneered by our friends at the Webrecorder project, we don\u2019t have to. Advances in web technology are making it more plausible to decentralize the means of web archiving throughout the entire pipeline, from creation to storage and playback. But what about that trust factor?\u00a0<\/span><\/p>\n

Scoop is a highly-tunable single-page capture engine that has compatibility with<\/span> recently crafted .wacz signing standards<\/span><\/a>. As a default, extensive provenance information is included for traceability and transparency. Additionally, as a guiding light in our design we captured the web under a no alterations principle, prioritizing an \u201cas is\u201d state over potentially smoother playbacks to strengthen the value of the record\u2019s testimony.<\/span><\/p>\n

Scoop is a library that can be used as a witness. Learn more about the specs on <\/span>Github<\/span><\/a>, and keep an eye out for stories about how this technology can be used and deep dives about its capabilities.\u00a0<\/span><\/p>\n

 <\/p>\n

\n

Perma Links for sources in this blog post:\u00a0<\/span><\/i><\/p>\n