@povoq@slrpnk.net mentioned the possibility of a solarpunk piefed instance in the past, but it’s yet to become something concrete.

We don’t plan to setup a separate Piefed instance, but we want to migrate our main Lemmy instance to Piefed sometimes early next year, but there are still some unknowns if the migration will be feasible or not.

https://join.piefed.social/try/ has a list. There just arn’t that many yet but https://anarchist.nexus/ is a solid choice.

Sounds more like countries where the advertisement revenue share model of Shitter made this a lucrative income opportunity.

Never missed it 🤷

Peertube already supports livestreams. And there is also Owncast, which is a bit easier to selfhost and also federates via ActivityPub.

It is already supported in Peertube and works fine.

It looks fine as in the default Piefed theme, yes. But they used to have a very nice custom theme.

Their theme broke with the update?

Probably? I have not tried it myself to be honest.

I am not sure how intercompatible the modules are. It might be that you have to chose between them.

It is a modular system that includes a module for microblogging. But it can also be turned into something else.

It also further links to another issue about individually blocking users and communities. Apparently that is quite inefficient in the current version, so maybe that adds to your problem?

What you can try is to clear your browser cache for the main domain. In the past there was a bug in Lemmy that caused Firefox based browsers to accumulate many gigabytes of cache data and that slowed down the loading of the page significantly. In the latest version there are some fixes for this and it shouldn’t effect app usage, but I suspect this problem still persists to some extend.

Aside from general issues others have mentioned, our instance (slrpnk.net) is seeing some especially high database load in the last couple of days and I also noticed the subscribed page to be even slower than usual. I tried to figure out what it causing it, but so far there is no clear smoking gun, but I suspect some AI scrapers found a way to target the Lemmy API directly so our current scraper protections for the webinterface are inadequate.

Indeed, Postgres 18 introduced some breaking changes and AFAIK Lemmy isn’t compatible with them yet. This will probably be fixed in the next release.

Afaik it is a specific implementation issue in Lemmy that causes this. Instances in Australia had problems catching up with lemmy.world because of that.

It probably has less to do with Qatar and more with US arms producers wanting to sell fighter jets and drones to Qatar.

1 . As you could have guessed from the community this was posted in, a software that is part of the fediverse. It has various modules for different functionality. 2. Because they made a long blogpost that explains the new features that you hopefully read before commenting?

MAU is a very incomplete measure of active users as by far the most users lurk and post very little.

In total numbers Mastodon has about 10m users and only 30% of those are on mastodon.social, the rest is distributed on the 9k other instances. That’s pretty close to the scenario you stated.

So lets say there are 100 instances. My instance needs to issue api requests to each instance to sync with the network. They in turn need to issues 100 requests to me to sync (and eachother). What about when there are 100k instances? Its exponential.

This falsely assumes that everything gets federated to everyone, which isn’t the case for ActivityPub. You only get what you actually subscribe to with it.

Mastodon already has those numbers you mention and there are no performance issues in the overall network.