By adding a shit-ton of tracking and analytic code from 3rd parties that provide some convenience. Blog owners are worried because it's not always clear what happens through the imported 3rd-party code, and now they have to start caring about that.
They should've been caring about that from the start. If GDPR is what it takes to get bloggers to think twice about embedding Like buttons and analytics/trackers up the wazoo, then I for one welcome our new European overlords.
Facebook like-buttons. Google Analytics. Comments function that stores user data. Server logs.
Can all be documented appropriately or adjusted to not collect unneccessary data, but it is some amount of work. It's kind of embarrassing that the author ran a platform for privacy-friendly stuff though and didn't have some of that down before, especially since in Germany a lot of this is not new ideas with GDPR.
A static archive would also have been very easy to self-host in a privacy-friendly way, but using archive.org is interesting (not sure if a good idea, but interesting)
Facebook have changed their privacy policy and ask for consent to track via external sites through things like the 'like' button.
Google Analytics is largely anonymised and deletes data after a set time now, including any custom user data that you may set up yourself. You have a legitimate reason to track people interacting with your web property.
Also, if a site is a personal project, not a business, it doesn't even come under GDPR as there's a household use exemption. (Not sure how a household use interacts with things like FB but let's assume non-third-party processing of data is exempt - e.g. comments with named user labels on a personal blog)
This feels like a whole lot of fuss over a very shallow reading of one of the most carefully thought-out pieces of privacy legislation the world has seen. It's got flaws but these aren't them.
