Of course, if you're going to offload hosting, GDPR concerns, or just your own backup peace of mind to the Internet Wayback Machine, don't forget to say thank you - <a href="https://archive.org/donate/" rel="nofollow">https://archive.org/donate/</a>
A few years back I have removed all like buttons, Disqus comments and analytics from my blog. Even though I have hosted the images myself and generated links. It took me maybe an hour and that is because I was browsing reddit or something at the same time. Now I do not need to do anything about GDPR.
<i>"So I searched trough my websites: Remove Facebook Like Button, Remove analytics, Add privacy statement, Add cookie opt-in/out …. the list goes on."</i><p>This is exactly why GDPR is so essential.<p>Not a single thought about why allowing tracking or the trade offs for others gain had occurred before GDPR.<p>For a blog GDPR is a non-issue.<p>Though I'm deeply disappointed in how many large sites have interpreted "opt in" as spending 5 minutes vigorously unchecking boxes with ambiguous meaning, hopefully that will bite them hard.<p>This isn't rocket science. Yes, if you go out of your way trying to game your users privacy as much as possible then things will get hairy. That's a feature and the whole point.
There is already quite a good plugin available by Berkman, Harvard University related to what author's idea seem to be. It works with Drupal as well as Wordpress upon which I worked as my GSoC project (nginx/httpd modules as well). <a href="http://amberlink.org" rel="nofollow">http://amberlink.org</a><p>It use Archive and local copies as backend, while had ideas to support IPFS among others.<p>What Amber does?<p>Amber is an open source tool for websites to provide their visitors persistent routes to information. It automatically preserves a snapshot of every page linked to on a website, giving visitors a fallback option if links become inaccessible.<p>If one of the pages linked to on this website were to ever go down, Amber can provide visitors with access to an alternate version. This safeguards the promise of the URL: that information placed online can remain there, even amidst network or endpoint disruptions.
I'd argue that running a webserver on a VPS/Raspberry/etc, with no logs, serving a static site or a wget mirrored version of that site is better - you still own the site, but if you don't store any information of your visitors at all, in any form, there's no way GDPR will bite you.
The tooling is ridiculous, while we can do this with some barebone bookmarklets.<p>Save url to archive:<p>javascript:void(window.open('<a href="https://web.archive.org/save/'+location.href));" rel="nofollow">https://web.archive.org/save/'+location.href));</a><p>Search the archive for url:<p>javascript:void(window.open('<a href="https://web.archive.org/web/*/'+location.href));" rel="nofollow">https://web.archive.org/web/*/'+location.href));</a><p>xD
I've just about had it with these GDPR shitposts on HN.<p>The website the author talks about (datenschutzhelden.de meaning "data protection heroes") was apparently a platform to share tools and best practices for online privacy. Now it turns out the same guy running that website thinks it's too much hassle to remove Facebook integration and offer a cookie opt-out.<p>That's truly next level hypocrisy.