Haven’t read an article so full of BS in a while… thanks for sharing 😅

Nice that you are so self aware 😅

I have not looked at the CVEs in Rsync specifically, but given the deludge of “critical” security issue found by AI lately that have been mostly nothing burgers, I am near certain the same applies to those included in that Rsync patchset.

The ones in Nginx and the Linux kernel.

The “critical” bugs that I have recently seen being found by AI were all extremely unlikely to be exploitable under realistic assumptions 🤷

They could have just refused merging slop. Rsync didn’t need these “contributions”.

Taking a project that works fine and making it actively worse by introducing AI made bugs is imho a valid reason to hard fork. The maintainer might not owe you anything, but it shows very poor judgement to slopify a good project like rsync this way.

The main dev can be easily reached through the official Peertube Github repo.

https://mindustrygame.github.io/

Gotosocial with Phanpy or a mobile app works great when you mainly use it as a personal server to interact with other servers. The limits are mostly intentional privacy features that make it less suitable as a public publishing platform.

Otherwise Akkoma works well and doesn’t need much resources either, but the setup is a bit involved.

I also don’t get what the issue is.

It’s not a big deal, but a single user instance has some issues with discoverability as it will only show communities you personally have subscribed to.

A fediverse instance obviously.

You can use the same containers with Podman, but docker-compose is not recommended with Podman and you rather use Quadlets which integrate nicely with Systemd.

Because it is missing an “and”?

Heh, that reminds me of trying to miniaturize origami folds when I was a kid. Yeah, don’t ask 😸

I think Vernissage even added a migration option from Pixelfed lately.

I am also interested in some feedback on hosting it. I tried hosting Pixelfed a while ago, and while I got it to run, it was honestly quite annoying with lots of papercuts, so I retired it again shortly after.

But that has nothing to do with the size of an instance of community. Rather the opposite is the case: an instance admin might decide to silence an community or instance because it is too big/busy and drowns out all the posts from smaller instances.

Or a very practical example: those Reddit and RSS repost instances. We had to defederate them because they were drowning out all organic posts and discussions. I would have rather liked to silence them though as people might want to stay subscribed to them without bothering other people on the same instance by having them pollute the federated feed.

On Mastodon it is also commonly used to temporarily silence an instance that is being abused for spam. This is much better than to defederate, as it still allows people to continue communicating with legitimate users on that instance.

which cannibalizes smaller instances as their posters are incentivized to post in the communities of the bigger instance and not their home instance since less people will see it.

Why would that be the case? Either you or me totally misunderstand that feature 😅

There is also white wood-filler. For small scratches it might be good enough to hide the damage.