<oembed><type>rich</type><version>1.0</version><title>Gigi wrote</title><author_name>Gigi (npub1de…9xzpc)</author_name><author_url>https://yabu.me/npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Here&#39;s a left-side-of-the-bell-curve way to do the Internet Archive &#34;right&#34;: &#xA;- Create browser extension&#xA;- User loads page&#xA;- User clicks &#34;archive&#34; button&#xA;- Whatever is in user&#39;s browser gets signed &amp; published to relays&#xA;- Archival event contains URL, timestamp, etc.&#xA;- Do OpenTimestamps attestation via NIP-03&#xA;- ???&#xA;- Profit&#xA;&#xA;I&#39;m sure there&#39;s a 100 details I&#39;m glossing over but because this is user-driven and does all the archiving &#34;on the edge&#34; it would just work, not only in theory but very much so in practice.&#xA;&#xA;The reason why the Internet Archive can be blocked is because it is a central thing, and if users do an archival request they don&#39;t do the archiving themselves, they send the request to a central server that does the archiving. And that central server can be blocked.</html></oembed>