I had to block some external instances on Masto.host shared hosting.

Here is why and how that can be reverted: masto.host/i-had-to-block-some

This was a tricky decision but couldn't think of a better solution.

If you have any suggestions, please do let me know.


@mastohost Is the bug tracked somewhere on the Mastodon project? If the maintainer(s) know about it, maybe they could help with a fix for 2.4.x boxes.

Even if the fix is to auto-reject requests from old instances that could cause this bug, at least then you wouldn't have to manually keep checking if they've upgraded yet.

@glcls I don't know if I should open an issue on GitHub for an issue that I don't know what causes it and how to reproduce it, I just know that it has something to do with accounts with pinned toots being followed from instances running older versions of Mastodon.

What do you think? Should there be an issue opened for this?

@glcls OK, it looks like this has already been reported and Nolan has even made a hotfix for it: toot.cafe/@nolan/1006345209326

Sign in to participate in the conversation
Boop Town

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!