• 6 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: September 29th, 2025

help-circle



  • Normally I would say the best link for sharing is that of the host for the community, not the host of your account. But in this case you posted in Lemmy.world, which is jailed in the exclusive walled-garden of Cloudflare™. I highly suggest not posting in Cloudflare. It’s a centralized walled garden by an oppressive US-based tech giant. Might as well use Facebook at that point.

    There is one open free-world “Mildlyinfuriating” community: [email protected]. I suggest posting there first, and then share that link. If you cannot stomach the idea of less reach/engagement or cannot resist the urge to use LW, at least make your first post in the free world and crosspost into the walled gardens so the ignorant walled-gardeners at least learn about the existence of free world communities.

    Now to answer your question, the infosec.pub admin is also the fedia.io admin. This post could¹ give some insight:

    https://fedia.io/m/fedia/t/2188602/Fedia-io-performance-issues-and-blocking-anonymous-access

    That is, anonymous access to infosec.pub could have been blocked for the same sort of reason.

    ¹ But you may need to create an account on fedia.io to read that… LOL.

    copy of linked post

    Hi all. Fedia.io has for a long time been subject to ddos attacks, including many that are “accidental”, caused by myriad scrapers constantly hammering the site. I gave up on trying to play whack-a-mole with blocking them based on IP address (they do not honor robots.txt and do not use a conspicuous user agent string) since I was inadvertently blocking some legitimate users. So, I’ve restricted access to the content of fedia.io to only those that are logged in. That will mean we don’t show up in search engines and whatnot, which for some will considered a good thing and will likely cause others to leave.

    There is a remaining problem related to the login form. Calls to the login page are breathtakingly expensive, computationally speaking, and so I also have a script that monitors unusual numbers of calls to that form and blocks at the firewall any offenders. I strongly suspect I’m catching some legitimate users with this too, and so I continue to try to tune it, but it’s maddening, y’all.

    These issues have been causing performance problems for everyone (despite the fedia.io app running on a dedicated 96 core, 256GB server with nvme disks), and became unavailable for certain people that accidentally tripped various thresholds. I’m hoping most of this is resolved now.

    Thanks for the patience.

    update

    Found this: https://infosec.pub/post/45546187

    I erroneously assumed you would have already looked in [email protected] so I did not initially look myself.





  • AT&T is the worst of the worst. And I boycott them for countless reasons like snooping on their own customers voluntarily without a warrant. It’s really a hard-right corp. In any case, never tried them so I didn’t know they blocked egress 25.

    One trick that works if truth-in-advertising laws are in force: ask the sales people before subscribing if the block port 25. They always say “no, we block nothing” (in my experience). So you subscribe and sign the contract. Then when you see they actually block 25, you have a false advertising situation and also a contract violation (if either verbal contracts are enforcable or if you can get it in writing that nothing is blocked). So you complain. In my experience, they give a gratis upgrade to an enterprise level of service that generally has a static IP and no blocks – for the price of the residential plan you signed up for.