4 ms·
Both things can be problems. 1. You should host dev stuff and separate domains. 2. Google shouldn't be blocking your preview environments.
by kevincox 1y ago
Both things can be problems.
1. You should host dev stuff and separate domains.
2. Google shouldn't be blocking your preview environments.
- lucideer 1y agoA safe browsing service is not a terrible idea (which is why both Safari & Firefox use Google for this) & while I hate that Google has a monopoly here, I do think a safe browsing service should absolutely block your preview environments if those environments have potential dangers for visitors to them & are accessible to the public.
- sureglymop 1y agoHowever, why does it work in such a way that it blocks the whole domain and not just the subdomains? Is it far fetched that the people controlling a subdomain may not be the same that control the domain?
- lucideer 1y agoWhich subdomains? To be clear, the issue here is that some subdomains pose a risk to the overall domain - visiting any increases your risk from others. It's also related to a GitHub workflow that auto-generates new subdomains on demand, so there's no possibility to have a fixed list of known subdomains since new ones are constantly being created.
- justusthane 1y agoThat’s what the Public Suffix List is for
- account42 1y agoIt is a terrible idea when what is "safe" is determined arbitrarily by a private corporation that is perhaps the biggest source of malicious behavior on the web.