git-sync looks like it does at you’re looking for.

Oh, nice. Saving the link’s content is exactly the feature I’ve been looking for.

As someone who was also recently looking for a multi device alternative for mihon/tachiyomi, I highly recommend Suwayomi. It’s even somewhat compatible with Mihon. It can use the same extension repos and you can restore Mihon backups in Suwayomi, which makes the migration pretty smooth.

Username on github seems to be the same as on Docker Hub: https://github.com/sciactive/nephele

“Poor planning on your part does not constitute an emergency on my part.”

Codeberg isn’t an entirely new forge. It’s just a well-known gitea/forgejo instance. Sourcehut would probably be a better example.

From what I’ve read you need it for Bittorrent or at least the chance of failed downloads is higher without it.

Definitely worth it IMO. There’s a lot of parts involved in a Matrix setup and this playbook handles them all for you. Just make sure to have a look at the changelog whenever you update your installation. If there are any changes that require manual steps, it usually explains those steps quite well.

I think Stash should cover most of your points, except for the page-less scroll: https://github.com/stashapp/stash The only other software I know for this is Porn Vault: https://gitlab.com/porn-vault/porn-vault

That’s a cool idea. Thanks for your work!

One question: Let’s say the script defederates an instance and then the admin of that instance cleans up their database and makes sure no new bots can register. Would your script remove them from the blacklist or would I have to manually check if all instances on my blacklist are still “infested” to give them a second chance?

I run a Jellyfin server, complete with Jellyseerr, Sonarr, Radarr, the works.

They’re already using Jellyseer.

Wouldn’t it still be a bit less taxing even with only one user? If I’m not mistaken then your instance only initially requests a community/post/comment from another instance when you specifically search for it. After that your server gets updates through activities pushed by the other instance. So if you refresh a post multiple times those requests only go to your instance. It somewhat acts like a cache, while the other instance can push activities at it’s own pace instead of being hammered with requests. Of course multiple users per instance would still be better.