Really a disgusting company.
Thanks HN: Lessons learned after Google nearly killed my site
51–60 of 296 posts
Re: Thanks HN: Lessons learned after Google nearly killed my site
#52Re: Thanks HN: Lessons learned after Google nearly killed my site
#53Re: Thanks HN: Lessons learned after Google nearly killed my site
#54Earlier quoted context omitted.
I think it's fairly easy to acknowledge the the following are all true: 1. The poster was hosting malicious content from their domain (user uploaded no doubt, but still on the domain they control). 2. On one hand, it is desirable that people who are not malicious be given enough information as fast as possible to rectify their sites. 3. On the other hand, this same sort of information can make it easier for malicious…
If you're hosting lots of malware on different subdomains, there is harm in Google telling you which ones it detected. You could use that information to keep hosting the undetected malware, perhaps out of laziness.
Re: Thanks HN: Lessons learned after Google nearly killed my site
#55Earlier quoted context omitted.
Something tells me that Google doesn't ban G Drive, Dropbox or MS's what ever it is named when those host malware. I rather not have only the giants host user generated content ...
Google does the silly separate domain dance GP recommended. I couldn't figure out what is it for, until I read this advice in the previous discussion. Disclaimer: I'm a Google SRE. But never supported anything reachable from the outside.
Re: Thanks HN: Lessons learned after Google nearly killed my site
#56> But there are plenty of Google engineers and good helpful people on Hacker news. > (from a screenshot) I work at Google [...] so I escalated your issue [...] > I believe the HN thread getting on the homepage tremendously helped me and somebody from Google saw it and expedited the review after all So, once more an issue with FAANG could only be fixed because somebody knew somebody else and went out of his way to get…
Even with HN it's a complete lottery what contents reaches the front page, so getting issues like these resolved is a matter of extreme luck for a common person.
Re: Thanks HN: Lessons learned after Google nearly killed my site
#57Earlier quoted context omitted.
This is really feudalism replayed. If you know important people at the emperor's court, you have a chance to get yor problem solved.
It's not "feudalism", it's human social relations and power dynamics.
Re: Thanks HN: Lessons learned after Google nearly killed my site
#58Re: Thanks HN: Lessons learned after Google nearly killed my site
#59Earlier quoted context omitted.
Google does the silly separate domain dance GP recommended. I couldn't figure out what is it for, until I read this advice in the previous discussion. Disclaimer: I'm a Google SRE. But never supported anything reachable from the outside.
That's not what it's for. It's to prevent user content from being served from the same origin as Google services. If the content were to be served from the same origin, scripts loaded from that origin would be able to access your google cookies and therefore would be able to access your account data.
Thanks, this makes more sense.
Re: Thanks HN: Lessons learned after Google nearly killed my site
#60Earlier quoted context omitted.
It's not "feudalism", it's human social relations and power dynamics.
Democratic societies try to limit this problem by establishing some semireliable channels to remedy injustice, though.