She configured her server to block requests from certain nations. One could suppose that's just due to some misconfiguration or something, but in fact it became a quite popular trend nowadays.
We routinely block nations where we have no customers from some assets, because why would they be there other than doorknob rattling hoping for some security issue. "No customers" is now racism? If we block people from the UK because of their burdensome Online Safety Act, we're racist? If we blocked Russian or Chinese IP addresses because their government doesn't want their citizens data stored on our infrastructure, it's because we're racists?
Apparently the definition of 'racism' has grown wildly in certain quarters.
One could suppose that's just due to some misconfiguration
Sure...but so much easier to assume they're a racist I guess.
I don't know you, so I don't care about your services, block whomever you want.
Rachel has a weblog, she writes articles, I used to come to her blog to read them, I am not a customer of any of her services.
Now that she blocks users by their origin - I see she has no problems with being discriminatory. That's a shame, I thought of her a bit higher than that.
I read her blog as well. Please point exactly to where she says "I block this user/IP address/netblock/AS #/etc. because of the ethnicity of the user".
That would expose her to the others, so obviously she doesn't manifest her blocks to everyone, she just configures her servers to drop packets received from specific origins.
It used to work directly and now it doesn't.
It works via foreign proxy/VPN, but I'll just stop visiting her site from now until she stops with her racism.
> She configured her server to block requests from certain nations.
That's not racist. It's pragmatic, reasonable, and a good idea. I haven't looked at the figures recently, but some years back over 90% of all automated exploits were coming from just 3 countries. If you don't do business in those 3 countries, blocking them wholesale massively decreases the risk of succumbing to an automated exploit and reduces the sheer noise in your operational workflows so you can focus on things that matter, not script kiddies with fat pipes.
It can also reduce your hosting costs significantly. I do this on every service I personally operate, and I've never once though about the race of the person I'm blocking. In fact, I don't even believe that the IP space being blocked necessarily represents attacks coming from inside that IP space, it could just be exploited systems being used as jump boxes by attackers elsewhere. From my perspective, it doesn't matter, I just don't see any reason to allow attackers to access my sites and services from regions I don't have any reason to serve.
Maybe come up with a better analysis than jumping to "she's racist"? It just makes you sound dumb.
That's a very stupid generalization on your side. And again: you talk about some customers as if I came to her site to buy some service.
No.
I just used to read her blog.
Now she can go to hell with her racist discrimination.
Easy for you to speak like you do until you personally get in a situation where you get discriminated for something like your origin.
That's even worse than being discriminated for skin color.
And again, that's very stupid of you to think that people from "good" country won't exploit your site or that all people from "bad" country only come to your site to exploit it.
