Skip to content

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

Comments

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 <img> 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.

That’s a helluva straw man you got there!

Look, there’s two options:

1) Only serve things your control.

2) If pulling in stuff from a third party (ie instructing the users browser to pull in stuff from a third party), have an agreement with the third party.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.