Ask HN: What does the GDPR penalty for loading fonts mean for website owners?

Story of GDPR penalty for loading external fonts from Google - https://news.ycombinator.com/item?id=30135264

I was thinking of starting my own blog recently. I like the idea of having comments section in blog powered by Disqus or another service that can be embedded in website with javascript. But this will be violating GDPR? Is it risky move?

From now on we should load all page resources from the same domain? No more using of external javascript to power syntax highlighting for code blocks, commenting section? What do website owners think about this penalty decision? What changes will you do to your websites to protect yourself?

IANAL, but it could mean that we're going to see an Abmahnwelle in Germany, ie. where law firms systematically scan websites hosted in DE for violations and demand cash at the threat of sueing. The habit of Abmahnen is a staple in German civil law and is seen as part of Rechtspflege (upholding the law by putting economical interest behind), but its application has been limited in recent years by a high court AFAIK, and I don't know how it could work in this particular case where visitors have individual claims. Which I think is the dangerous thing ie. continuing using Google Fonts and other CDNs without consent could set you up for quite a lot of claims.

FWIW, yesterday I rushed to change my sites to serve all assets locally.

If you have your blog self-hosted in your garage !IN EUROPE!, and your apache use custom log format that do not log IP addresses, and I add an to some image on your site (example - some cool car), I should be OK?

Now imagine this: Then one day you change the image with something else (example - birds picture). Can I sue you that without my permission you changed MY website?

My logic is that if in court I am responsible for something that is outside my webserver (it is on your webserver), then you should be responsible too? (it is still your webserver)

What if one day you decide to start logging IP addresses, and move your blog from your garage server to AWS in USA without notifying me?

Your logic makes no sense whatsoever.

You own a website, then you're responsible for the content on said website. You choose to embed content from 3rd parties? Then you take on a risk. If you have a business relationship with this 3rd party, then you can maybe take them to court.

No contact, no company, njala domain, cloudflare proxy. Problem solved for small sites/blogs