Closed PedroHome18207 closed 3 months ago
So far, I have not noticed any restrictions due to the blocking of id.google.*
@Retold3202 Do you have any further information on this?
Whatever the answer, here are some missing TLDs:
||id.google.com.bo^
||id.google.com.py^
||id.google.com.uy^
Thanks @PedroHome18207, will be added on next release.
@Retold3202 Do you have any further information on this?
@hagezi I actually ran into these id
domains myself as well, and yeah, they're difficult to find information on. My understanding based off what I was able to find is that they're responsible for those annoying "Sign-in with Google" prompts/trackers on websites. (Ex: here, here, here, & here). If no one's ran into any issues, then I think they're probably safe to leave blocked, I'm not able to find any other legitimate functionality tied to them.
Thank you @Retold3202. Does that answer your question @PedroHome18207?
Yes, thank you very much @hagezi and @Retold3202 for answering my question.
Is it safe to block
id.google.*
?In EasyPrivacy the filter is different:
||id.google.*/verify/
instead of||id.google.*^
reference:https://github.com/easylist/easylist/blob/9fa53c0cd737341a9835b420801d98d7842f2e7e/easyprivacy/easyprivacy_thirdparty.txt#L1098C1-L1098C22
Your response would be very helpful.