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”?

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 😅

The noqanon list and the OP warning sign are two different things.

The first is a default url blocklist that gets pulled on first start of a Piefed instance and which contains extreme right-wing and mis-information outlets.

The domain warning sign mentioned in OP is a separate list only manually added to the piefed.social flagship instance.

I was referring to a different but similar case where someone intentionally spread mis-information about supposedly hardcoded things that turned out to be a complete nothingburger as all of it was behind an admin toggle. The same seems to be now true for this old issue you specifically pointed out here.

It is true that there is some experimental stuff in Piefed, which is part of the relatively rapid iteration of features, but looking at the code and also the explanations given by the Piefed development team I can really not see any malice in those settings. It is perfectly normal that things get overlooked or implemented partially and when someone reports a bug (like a missing admin configuration setting) it usually gets fixed quite quickly, and at least in my experience without much discussions.

You are jumping to conclusions. I think it is generally worthwhile to discuss the use of LLMs for making moderation decisions and also using them to produce ideological profiles of users.

A while back, someone realized that piefed was hard coded to give negative reputation to certain people, regardless of what settings the admins had made.

Please don’t spread old mis-info or at least back this up with actual links to the source-code (and if we are talking about the same thing, this was clearly debunked).

As for the OP post, this is factually correct and I have seen the evidence. Although maybe Rimu should have been more clear in pointing out that this seems to be not an official instance tool, but rather something some moderators have cobbled together themselves.

Previously had some good experience with this store selling refurbished hardware: https://www.computerstoreberlin.de/

Old DDR3 ECC is actually cheaper than regular DDR3 RAM, and it generally works with AMD CPUs (who unlike Intel don’t artificially restrict ECC support to their enterprise offerings).

But tbh, ECC is generally not needed and I wouldn’t bother designing a system around it. Use a file system with checksums and regularly scrub the drives and you should not have any major issues with random bit flips that ECC protects against.

No, typically you use the DNS server of the domain provider.

Hosting your own DNS server is possible, but if you don’t have a static IP address the other DNS servers will have no idea which server to ask when your IP changes, so in this specific scenario it wouldn’t work. And in general it isn’t really worth it as you get a DNS server with your domain included.

DynDNS short for dynamic DNS is what you want. But IPv6 only websites are unfortunately even in 2026 still not accessible by many people due to their ISP only supporting IPv4.

ionos.de has VPS for 1€/month, which are not that bad. Server locations are Spain or Germany afaik.

What does this have to do with solarpunk technology though 🤔

Have fun with the next round of enshittification then 🤷

XMPP and the Fediverse works just fine as far as I am concerned.

Is Matrix technically part of the fediverse? I noticed it does not appear on fedidb.com.

Depends on your definition of Fediverse, but I think most people would say no, even though it is a federated protocol.

On a related note, what is the active userbase size?

The company behind Matrix it is known to vastly inflate user-numbers for scamming investors, but a somewhat realistic estimate for the openly federated Matrix network is 200-300k MAU (as shared by the Element CEO when pressed on a realistic number).

Who is the developer/team and do they have an active presence on the fediverse?

It is mostly developed by Element / New Vector Inc., but they have a non-profit front with the Matrix Foundation.

You didn’t ask, but conceptually Matrix is closer to Bluesky than to the Fediverse. If you want a Fediverse equivalent for chat, look into XMPP/Jabber, which is based on an truly open standard and is democratically governed by an independent community organization.

Because you usually don’t want to do automatic upgrades across major versions. There is a “latest” equivalent for each major version release though.

Install a newer Linux distro on it and run a Luanti server for the kids to play on.