I finally had a chance to battle the scrapers and bots and crawlers enough that I can open the instance to the public again. Thanks for the patience.

Many thanks to the very responsive mbin team.

Ok, there are three problems going on. First, the site has been intermittently super slow. This is happening because of some database locking conflicts and long running queries. I don't have this fully mitigated yet, but I know what I need to do and just need to get it scripted so it can recover automatically and gracefully.

My attempts to solve the prior problem broke federation by causing the messenger services to think they didn't have a connection to the database. This should be fixed now, and now that I know it happens, I can mitigate it in the future.

The other problem is with only being able to go back one to three pages (some times the first page is all you get). This is a known issue in the new version of mbin and the devs are going to revert the pagination scheme to the prior version until the bugs get worked out. In the mean time, if you click on "combined", you will be able to go back for miles (or kilometers).

test

this is only a test

Anubis works well for a few hours, the slows the site to a crawl. I will be removing it first thing in the morning. My apologies.

Hi all. I've implemented anubis in front of fedia.io in an attempt to mitigate the absolutely insane amount of crawlers hammering the site. I have also reenabled anonymous access, hoping that anubis will be effective at keeping the bots out and letting legit people in.

For reference, I run 17 different instances*. All are using a common postgres database server, running on a latest gen AMD Epyc server with 48 physical/96 logical cores. When I enabled anonymous access previously, fedia.io would consume 6 times the amount of database resources as all the other 16 instances using the database server combined. It's off the hook absurd.

So far, it's going ok with anubis in place and anonymous access. I'll see how it performs over the next day or so.

• list is here: https://infosec.exchange/@jerry/110781964594201103

My apologies for how long the site was down. Just about everything that could go wrong did, but I think we are working now...

In an effort to reduce costs due to the exchange rate and declining donations, I’m going to be consolidating Fedia.io onto another existing server so I can decommission and return the server that it is running on. I’ll be turning off unauthenticated access to content again because that drastically reduces the bandwidth/compute load that Fedia uses. I am not sure on timing yet - likely around 2PM ET/6PM UTC. I’ll plan for an hour downtime but I’m hoping it should only be a few minutes if I do things correctly.