|
Top-level
 Every time you use the word "hacker" when you mean "cybercriminal", "attacker", "malicious actor", you *personally* support this kind of bullshit. Every time you use the word "hack" to mean "compromise", "break-in", "leak", you *personally* make it harder for a small community of creative people to focus on their projects, because now they have to go prove to Google they are not, in fact, attacking anyone. 9 comments
And why is that? Because over-blocking a website of small hackerspace is *cheap*. "No downside". Because "hacker" and "hack" have been appropriated by those too lazy to be specific in their use of language when talking about "computer stuff." Also, it drives clicks! Result? Some algorithm somewhere sees "hacker" and goes bananas: "danger, Will Robinson!" So forgive me when in the future I react *badly* to some random toot mislabeling cybercriminals as "hackers". And if you happen to ever be in Reykjavík on a Thursday evening, come have a beverage with us. Hopefully the site gets unblocked soon, we try to keep it up to date with the details of where we meet each week. Oh by the way, this is what the site looks like (and yes, we will soon move away from the gmail address, because — you guessed it — #FuckGoogle). @rysiek Wrt email, I use protonmail with my own domain, I say #FuckGoogle at least once a day, life outside the #Matrix is so much better 😎 |
Gregory's Server
And guess what, when Google Sites are used in phishing attacks — and anyone who does any #InfoSec work knows they do, a lot! — somehow the whole sites.google.com domain does not get flagged like that.
When Google Amp is used in phishing attacks — again, not a rare occurrence! — somehow Google Amp domains do not get flagged this way. :thaenkin:
Flagging our site stopped exactly zero attacks. But now we have to send in reports and beg Google to maybe please unblock us.
#FuckGoogle #Hackers