Skip to content
This repository has been archived by the owner on May 17, 2024. It is now read-only.

Google Fonts is blocked #136

Closed
hectorm opened this issue Feb 29, 2020 · 4 comments
Closed

Google Fonts is blocked #136

hectorm opened this issue Feb 29, 2020 · 4 comments
Labels
broken-site Valid block breaks a legit site

Comments

@hectorm
Copy link

hectorm commented Feb 29, 2020

Similar to #132, fonts.gstatic.com domain has a CNAME record pointing to gstaticadssl.l.google.com and the blocking of the latter prevents Google Fonts from working.

I see that this was mentioned in #104, but I open a new issue to follow up on this problem in particular.

@lightswitch05
Copy link
Owner

See also how google fonts tracks: google/fonts#2345

I have no interest in blocking google fonts, but I’m also not inclined to unblock gstaticadssl.l.google.com over it, especially considering the tracking they are doing.

@lightswitch05 lightswitch05 added the broken-site Valid block breaks a legit site label Feb 29, 2020
@hectorm
Copy link
Author

hectorm commented Mar 1, 2020

Yes, I'm aware of Google using their font service to collect statistics, in fact it is not something they hide, they have a section on their website that shows some data: https://fonts.google.com/analytics

However, since Google Fonts does not require JS, the data they can collect with it is more limited.

It is a difficult decision between more privacy and breaking some websites.

Do you know if the domain gstaticadssl.l.google.com is used in other Google services that have more privacy implications?

@hectorm
Copy link
Author

hectorm commented Mar 1, 2020

Although it cannot be guaranteed that the domain gstaticadssl.l.google.com is being used for other purposes, I checked the CNAME records of this list and the only one I found was fonts.gstatic.com.

@lightswitch05
Copy link
Owner

lightswitch05 commented Mar 2, 2020

I understand that people would not want fonts blocked. This is why I do not block fonts.gstatic.com. However, I do block gstaticadssl.l.google.com, which is an ad host (gstatic ad ssl). It’s really unfortunate that they use that as a CNAME for fonts. Let’s leave this ticket open, but as more and more CNAME issues pop up- I have less and less interest in whitelisting based on them. I’m not blocking `fonts.gstatic.com and if it ends up being blocked for you because of a CNAME reference, then it’s on you to figure out how to whitelist it. At least that’s my viewpoint on this matter at the moment.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
broken-site Valid block breaks a legit site
Projects
None yet
Development

No branches or pull requests

2 participants