2025-08-03 GoToSocial and the Butlerian Jihad

I run a single user instance for the fediverse using GoToSocial and since I'm blocking thousands of IP address ranges -- mostly from companies renting out bandwidth and computing power to web scrapers -- I'm also blocking my instance from seeing a lot of the fediverse. That's not good.

thousands of IP address ranges

The solution is to continue blocking the big cloud providers like Microsoft, Google, Amazon, Hentzner, OVH, Alibaba and whatever else they are called. But if I'm following somebody from a fedi instance hosted by these big cloud providers, I should put the IP numbers associated with just those domain names onto a separate allow list.

Instead of using the Mastodon client protocol to get the list of people I'm following, I can just access the database directly.

Here's the script that adds IP addresses:

This prints lines such as the following to STDERR:

And it prints lines such as the following to STDOUT:

I redirect STDOUT to a file called `gotosocial.sh` and then I run this script, which creates to IP sets called `gotosocial` and `gotosocial6`:

If you run it, you'll get warnings about duplicate entries, I'm sure:

In my case, for example, I have both of these entries and I didn't bother to fix this:

There are plenty more, of course.

In any case, you should now have an allow list that prevents these IP addresses from getting blocked by `fail2ban` because the `gotosocial` rule comes first:

To delete and recreate the lists, I use the following:

​#GoToSocial ​#Butlerian Jihad

**2025-12-24**. And of course now I had to replace it all with `nft` stuff. 😭