view the rest of the comments
Mildly Infuriating
Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-The Community !actuallyinfuriating has been born so that's where you should post the big stuff.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
Looks pretty obvious to me.
I'm more infuriated by the "abnormal activity from your IP". It seems pretty much everything is abnormal to these CDNs, including using Firefox on Linux. On the stack/exchange/ask networks I get that shit every fucking time. And no, I'm not using a VPN/Tor.
Especially when it’s a website that requires an account but they want to use SMS-based or Google Authenticator style 2FA in 2025. “Magic links” are stupid as hell too if you’re not a moron and use a decent password manager — I have no clue what random email address I generated for you since I can’t trust any company not to sell off my PII.
How hard is it to implement FIDO2 then let valid users make requests from whatever IP address they want? IP-based blocking is pretty fucking stupid if you’re already doing secure account-based authorization.
Saying all this as a heavily privacy-conscious web developer. All my traffic looks “suspicious” because how dare I not want your shit hole website to put its grubby little hands all over my IP address.
OK, that last sentence made me laugh!
Considering the amount of traffic from LLM bots nowadays, everything human/"natural" traffic seems to be abnormal as it doesn't behave like the majority of requests
With browser extensions and other programs becoming tunnels for AI scrapers, consumer IPs are becoming less and less trustworthy. I receive bots from just about every Brazilian consumer ISP. All it takes is one person on your network with a shitty app/extension installed and your home becomes indistinguishable from a bot farm. It's extra bad if you're behind CGNAT so you can't even influence your IP's reputation.
Nobody wants these CAPTCHAs, but they're still pretty effective, even with AI image interpretation. Plus, it still beats remote attestation in terms of Linux friendliness, and that's the inevitable next step in the war against scrapers.
the problem isn't captcha as a concept, it's how it's executed
there are good captchas that aren't obviously making you train an AI model and which seem like they'd actually be effective at identifying humans, like dragging a circle over a specific feature of an image.
@[email protected] @[email protected]
Greetings. Brazilian here.
I can confirm that a lot of websites unexpectedly block my access with a pretty opaque "403 Forbidden". No Captchas, no Anubis-like man-in-the-middle, just an invisible and ruthless Gandalf digitally yelling "you shall not pass".
I have read similar stories about how Brazilian IP addresses seem to be infested with bots. It's often Brazil: it's odd how people rarely complain about other countries on this matter... Not pointing fingers towards you, specifically, but I wonder how much of geofencing against Brazilian IP addresses stems from prejudice and xenophobia of foreign webmasters.
It's worth mentioning that bots have no borders and aren't restricted to a specific country, but the vast majority of Brazilians (myself included) are restricted to an entire biological existence within Brazilian territory, with hundreds of millions of people never having set foot on an airplane or cruise ship.
Webmasters of the world should think about this before geofencing entire countries. Not just Brazil, but any country out there. Because living beings can't choose where they're born and humans often can't even afford to travel and/or reside elsewhere.
(My sincere apologies for my outburst, but it resonates with the community's name: being blocked from websites just because of nationality is not just Mildly Infuriating: it can be totally infuriating sometimes, and this exact phenomenon happened earlier today while I tried to access a psychology website)
It's not just Brazil. China and Huawei's Singapore datacenter are common bots for me too, but I have less of a problem blocking those off for most services, as I only have a few applications running where server-to-server traffic makes sense. There are a few Indian CGNAT exit points that sometimes show up as well, but their traffic is low enough that it doesn't stand out. When spam traffic is coming from local (European) sources, it's almost always from server IP blocks. Not a lot of domestic ISPs in my spam logs from most countries.
For some reason, Brazillian consumer ISPs just seems infested with certain strains of malware. It's probably a brand of cheap IP cameras or routers that keeps getting infected, I remember Mirai hitting Brazil pretty badly. But I also get the feeling that Brazilian ISPs care even less about their networks' security than the ones I'm used to with how much infected customers find their way to my servers. I would've expected similarly populous countries like the USA and India to hit my servers at a similar rate, but Brazil seems to stand out for some reason.
I don't tend to block countries directly (they have too many IP ranges for me to bother, to be honest), not that I have anything that they'd be interested in anyway. I do get waves of Brazilian IP addresses trying to submitp spam to my mail server, though. I haven't seen those coming from other countries yet. I know it's not Brazilians themselves sending those, but that doesn't make the spam any less annoying. For larger websites, I can see why they block IP ranges so aggressively.
I don't think of ISPs in terms of nationality per se. I block per ISP, not per country, with the exception of China whose great firewall should probably "protect" their citizens from my websites anyway, and there I'm probably missing a whole bunch of ASNs anyway. It's up to ISPs to maintain the reputation of their networks and to stop their infected customers from bothering everyone else, and if they don't do it, I block their networks. In fact most filters that throw up blockades and CAPTCHAs and fail2ban blocks are doing this entirely automatically, if countries get blocked out it's usually for legal reasons rather than anti bot protection.
If you get a lot of these blocks, it's possible you're in the same subnet as someone with a hacked device or shitty VPN app and got hit as collateral damage. I got that for a while after switching to an ISP that had just bought a block of IP addresses from a Ukrainian ISP. It's just an unfortunate side effect of the modern Internet that you must either figure out how to get a new IP or hope the malware on your IP neighbours gets cleaned up. I don't have enough time and energy to protect the innocent from the guilty when it comes to my small, insignificant websites, and I shouldn't be needing to take such aggressive action against these IP ranges in the first place.
In a similar vein, I get a lot of 403 errors when browsing websites like Reddit because news websites still block off GDPR countries. I know how annoying it can be.
I deal with this a lot since I do most of my browsing through a VPN.
As great as VPNs are, there probably are a lot of bad actors using them and sometimes I'm the next person using that IP.