Those have been active for a few months now and usually get banned from most (non-ask) communities quite quickly.

What concerns me more is despite how obvious it is that they are bots, the posts often seem to get a lot of engagement from other accounts that are both human and some less obvious bots (or maybe lurkers).

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.

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.

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.

The specific chip is only 4 years or so old. The 10 years refers to the Ryzen series first release.

Why this specific chip? It is the fastest available for the older AM4 socket + DDR4 combination, so it is highly sought after by people upgrading their older rig without having to buy new expensive DDR5 RAM or a new mainboard.

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 👍

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

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.

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.

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.

Well other than sending money and free laptops to a racist multi-millionaire and excusing it with a “big tent” approach when asked why the fuck they do that…