Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Using Google fonts is a violation now. It's a nightmare for web developers.


How could that possibly be a nightmare? Download the fonts and host them yourself.


Maybe web devs should more carefully consider how much crap third party scripts and resources inject into their sites, rather than caring about a tiny bit of convenience.


Maybe users should be responsible for what they intentionally run on their machines.


That’s absurd. That’s like saying car owners should be held responsible for how safe their car is to drive. It makes unrealistic assumptions about the competency of the end user to judge such things.


No it’s not. Rather it’s more like drivers should be held responsible for how they drive their car.

I’m not even saying responsible— just they cant reasonably complain when they drive somewhere new and they don’t like the road conditions.

Your original analogy is more like this: If a person's computer got hacked unintentionally, they shouldn’t be responsible for the damage it caused to others.


Nobody in their right mind is going to carefully peruse the cookies and injected JS scripts of every page they visit.

No, the onus is clearly on the developers, who are the ones with the professional responsibility to make software that abides by the laws.


I’m talking at the meta level. The laws can start nationalizing every company. But I think it shouldn’t. The law can put the burden on developers — but shouldn’t.

I shouldn’t have to abide by some stupid rules to plug my server onto the Internet and listen on port 80.


When the law is not enforced, there is no hope.


Clearly the GDPR is being enforced


Your right. The best way is to filter at the firewall level everything Google, Microsoft, Cloudfare, Facebook, Twitter etc. The world would be a better place. Now try to do this on Windows 10 :)


I use NoScript on Google. Works fine. Most things work okay without scripts if you are just there to read.


Note that fonts from Google Fonts can be self-hosted which resolves that problem. It's a little bit more work to set up, but it does resolve this issue well, while also being slightly more efficient for the end-user (assuming that you've got a decent CDN setup).


no less efficient hosting yourself.

cross-site resource caching has been unavailable in major browsers for a while - safari since 2013, chrome since 2020, firefox since 2021.


That's what I was trying to say, I think I got excited and used too many double negatives...

Theoretically, it should be more efficient hosting these things yourself - there are fewer origins to request, which means fewer lookups, fewer connections, etc.


You can put this in your build steps that it downloads everything; I have that and prefer it anyway; companies ‘tend’ to suddenly remove, change or switch things off or get hacked.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: