Despite what some other people falsely claim here in the comments, scraping is actually not the same at all as federation. Besides not being reciprocal, scraping puts considerably higher load on the server to the point where it brings down entire servers or at least severely degrades the performance for legitimate users.

Opensense is based on BSD, which has a single threaded network stack. This means that low end CPUs can struggle to do >1gbit throughputs. Depending on your WAN this could be an issue.

Why would I follow a feed of what appears to be made of pictures that are mostly AI slop?

There is apparently an incredible amount of manipulation and legal fights happening around these reviews on Google maps, so that is probably a minefield any independent open-source developer should avoid.

Sure, but the point of getting a mini-pc is usually not that you have an open case with a second ATX PSU sitting on top to power some extra hardrives.

How will you power the drives?

And from what I have heard, these m2 to SATA adapters have over-heating issues.

You mean “mid” as in midi-tower? Because that sounds like the large version. Well maybe there is an even larger workstation version or so, but the normal medium sized Optiplex comes with one 3.5" SATA bay and one DVD drive.

Optiplex etc. with an Intel 8th gen “T” chips seem to offer the best bang for the buck + energy efficiency on the second hand market right now.

The main issue with these thin clients is the lack of SATA ports and power connections for them if you want to add some larger 2.5” SSD/HDD storage. Usually it is only one, but you can also use the DVD drive slot with an adapter in the mid sized versions.

That’s for instances, not accounts, no?

What is probably needed is a 3rd party vouching account system. A bit like how email accounts are used today, but with a back-channel that allow you to get reputation from the places you join with that account and that in turn makes it easier to join other places.

The 80% LLM applications doesn’t seem to have reached Lemmy yet. For us it is more like 10% or so. But yeah, it is getting harder to distinguish these.

There used to be a women’s space on slrpnk.net (although a bit unfortunately named after a controversial Reddit community), but we could never really find women willing to moderate it longer term and the amount of dudes showing up with trollish comments became a bit too much for us admins to handle.

Thanks for sharing the details 👍

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 😅

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.