Google Safe Browsing incident
statichost.eu
Google Safe Browsing incident
1–10 of 183 posts
Re: Google Safe Browsing incident
#2It feels like unless you're one of the big social media companies, accepting user content is slowly becoming a larger and larger risk.
Re: Google Safe Browsing incident
#3Still not sure why it's legal for Google to slander companies like this. They often have no proof or it's a false positive, meanwhile they're screaming about how malicious you are.
Re: Google Safe Browsing incident
#4It feels like unless you're one of the big social media companies, accepting user content is slowly becoming a larger and larger risk.
It always was. You're one upload and a complaint to your ISP/Google/AWS/MS away from having your account terminated.
Re: Google Safe Browsing incident
#5Still not sure why it's legal for Google to slander companies like this. They often have no proof or it's a false positive, meanwhile they're screaming about how malicious you are.
Because Google has absolutely nothing to lose and you do, besides that they can outlast anybody except for nation states in court.
Re: Google Safe Browsing incident
#6Still not sure why it's legal for Google to slander companies like this. They often have no proof or it's a false positive, meanwhile they're screaming about how malicious you are.
Good question, it probably shouldn't be legal. Enforcing the law on these behemoths is another problem, though... :)
Re: Google Safe Browsing incident
#7Hosts phishing sites, gets blocked by anti phishing mechanism. Works as expected from my point of view.
Get yourself on public suffix list or get better moderation. But of course just moaning about bad google is easier.
Re: Google Safe Browsing incident
#8The PSA is good, the article is meh. There is too much misdirected anger towards google here, IMO. I agree it sucks to be the false positive, but it'd also suck more to unknowingly be part of phishing campaigns and not know.
On top of that, it is also recommended to serve user content from another domain for security reasons. It's much easier to avoid entire classes of exploits this way. For the site admins: treat it as a learning experience instead of lashing out on goog. In the long run you'll be better off, having learned a good lesson.
Re: Google Safe Browsing incident
#9Still not sure why it's legal for Google to slander companies like this. They often have no proof or it's a false positive, meanwhile they're screaming about how malicious you are.
Notably this post did not examine whether any of the sites it was hosting on this domain was malicious/misleading.
Re: Google Safe Browsing incident
#10Github discovered the same thing a long long time ago which is why you now have the github.io domain.