this post was submitted on 10 Nov 2026
29 points (91.4% liked)

Fediverse

44900 readers
998 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)

founded 3 years ago
MODERATORS
 

As the Fediverse grows, the amount and frequency of harmful spam also increases. The feudalistic structure of the network creates notable moderation overhead as every instance admin has to ban offending remote accounts and remove their content themselves, if the originating instance does not act quick enough or such delete actions are not federated properly.
An example (and my motivation for this post) are reports from the last days about accounts which post CSAM content. This is especially problematic, as media content gets duplicated to every receiving instance.

The following idea came to my mind: A software which sits on top of Activity Pub and creates a kind of court. Instances of this software are independent courts. All users can elect admins / mods of their home instance as judge. Everyone can post a case via normal Fedi posts to the court and the elected judges give a verdict via majority vote (votes are also normal Fedi comments with special formatted content). Once a case has a verdict, all instances should immediately apply the decided action against the offending content / account. This can be done via a bot which is set as an instance moderator and follows the published verdicts of a court instance the local admin trusts.

This way swift action can be applied through all instances which follow the court at once. By having periodic elections it is kept democratic.

And the task of the court is to defend universal rules all following instances agree on. Not to handle politics between instances.


What are you thoughts on this matter? Or do other approaches to solve this issue already exist?


Update:
From this came the idea that instances can follow mod actions of other instances and apply them if x% of other instances did the same.

I think this is an interesting approach which might be better than my proposal. So I would like to hear your thoughts about this too.

top 50 comments
sorted by: hot top controversial new old
[–] Quokka@quokk.au 3 points 12 hours ago* (last edited 12 hours ago) (1 children)

I'm not a huge fan of a software solution to this, we already have a large group chat open for instance operators to share and discuss details of user bans, spam, etc. This respects each instances 'culture' while also facilitating communication and dialogue around potential issues.

[–] blued_gear@fedia.io 1 points 4 hours ago

Ohh, I didn't know about that. Would you share the address?

Also, is there some general onboarding material for new instance admins which is software-unspecific?

[–] HubertManne@piefed.social 4 points 1 day ago (1 children)

I think this is an instance owner thing. They run the instances and ultimately who owns and thus mods the communities on their instance. I doubt anyone running an instance would want anything foisted on them. I honestly am more concerned with development that allows users to control their feed as much as possible. Like being able to subscribe to a mod or someones block list. Or even better filter options that allow for complex blocking.

[–] Quokka@quokk.au 1 points 12 hours ago

I honestly am more concerned with development that allows users to control their feed as much as possible. Like being able to subscribe to a mod or someones block list. Or even better filter options that allow for complex blocking.

PyLova offers those features.

[–] goferking0@lemmy.sdf.org 3 points 1 day ago* (last edited 1 day ago)

As with anything it depends on who is in control of the moderation or the ones doing the moderation.

And part of it sounds like a centralized layer on top of federation that would just be the antithesis of what the purpose of federation is.

I know you are thinking of csam specifically but as described could end up giving certain mods and instances an essential veto.

Based on certain instances cough lemmy.world and piefed.social I see that going extremely poorly

[–] Kichae@lemmy.ca 13 points 2 days ago (1 children)

I'm not sure how a process modelled off of a tribunal is supposed to act as a fix to mods or admins not acting quickly enough. Trials and tribunals are notoriously slow, because they are called when correctness is more important than speed.

By design, these are not vehicles for "swift actions".

If a certain website is known to have a problem with their moderation, then that's what server block lists are for. Communal server block lists already exist. Having a standardized format and the ability to subscribe to one would be nice, but as of right now the amount of effort to update a server's block list with a new version is relatively simple.

The thing is, as the fediverse grows, and especially as the group-based part of the fediverse grows, we have to accept network splits as a natural part of that process. It is going to get patchy here. It's a natural part of social network development. What we need to get ahead of is showing people that that is OK, and that frictionless access to the whole of the social web isn't necessarily a good thing.

[–] blued_gear@fedia.io 2 points 1 day ago

A tribunal is not the fastest solution; true and that is a problem. But on the other hand following the verdicts of just one entity (a list, an instance, a person) brings the risk of abuse of power by that entity where a jury is democratic.
I don't want to defend my idea as the right approach, as it has pros and cons and I don't know what the optimal solution should be myself.

[–] Vicinus@piefed.zip 10 points 2 days ago (2 children)

I think Pylova (a soft-fork of Piefed) is at the forefront of moderation tools in the threadiverse.

I think their recent addition of shareable user-subscribable block-lists is a good direction to go. I think this can be expanded to instance-level subscribable block-lists. There could be a variety of lists (CSAM, scrappers, scammers, agentics, etc.) and each instance chooses what list(s) to subscribe to or build their own for others to subscribe and contribute to. The lists would be easily fork-able so that any instance can take control of their own moderation, if they disagreed with an addition/subtraction to a list.

For some lists (like scrappers), I think automatic addition could be set up to quickly "inoculate" the rest of the threadiverse against them. Perhaps one approach could be any IP that clicks on a non-user clickable link or gets stuck(?) in Anubis could be added.

I think subscribable block-lists for instance admins could be a great way to protect the threadiverse (perhaps expanded to the fediverse as a whole or just any website in general) against any problematic actors quickly and at the first encounter (alternatively: after (x) # or % of instance admins add them to a list).

Apparently some of these lists may already exist in some form (@Christopher@lemmy.grey.fail: "I was able to implement community maintained blocklists."). So, my thought would be to make sure these lists are a standard format (if they aren't already) that instances can auto retrieve and contribute to.

Anyone: let me know if you have any thoughts or see any issues with the idea (constructive criticism only, please).

[–] vk6flab@lemmy.radio 3 points 1 day ago (1 children)

Posts hitting the fediverse over the past 24 hours or so are essentially creating a new account for each post. The accounts are across many instances and posts across many communities.

I'm not sure how this proposal would work in the current environment.

[–] Vicinus@piefed.zip 2 points 1 day ago

The accounts are across many instances ...

Good point. If they have a shared identifier (IP or something) than I could see the block list working. If not, and it's probably not, then yeah, I don't think the block list would be able to handle that spam.

I wonder if there is any approach that could. Different origins, different entrances, and different targets, that's a difficult one. It's not my knowledge base, so maybe something exists that could handle it? I'd be curious to hear about it, probably pretty cool.

Maybe machine learning on interaction rates (sign in to post timeline)? I'm assuming it's automated though...

[–] blued_gear@fedia.io 2 points 1 day ago (3 children)

The difference between blocking and purging is that a blocked account is still residing on the instance (even more so for user blocks instead of admin blocks). As the data is still there, it opens possibility for legal trouble. Full purges by instance moderation action is different.

The scope of my proposal is not to help curate and filtering content for instances, but to enable widespread coordinated action against content which was already created and is harmful without any room for interpretation.

approach could be any IP

That is a whole other issue. Scrapers and request spammers, not content spamming accounts, can be combated with already existing technology at the reverse proxy server. There are big crowdsourced IP banlists which are continuously updated.

I think subscribable block-lists for instance admins

This would be the easiest solution. But I think it will lead away from individualism of instances, as all decisions are automatically applied, instead of only a manually reviewed subset.
Your idea with applying the mod action after a threshold of other instances did it too is something to consider. It will keep individualism but also creates "avalanches" once enough instances in the network agreed on a decision, which might be even better for propagating swift action against general harmful content.

[–] Quokka@quokk.au 2 points 13 hours ago

Full purges on PF/Pylova are a click of a checkbox when we ban an account.

[–] OpenStars@discuss.online 2 points 1 day ago (1 children)

They each serve a different purpose - instance bans are "hard" (firm), and appropriate for e.g. CSAM & trolling, whereas shareable blocklists are for more "soft" (personal choice) matters, like whether someone prefers to not see posts from bot accounts that rarely if ever respond to comments within those posts (although arguably a bot account that is not properly registered as such could be grounds for banning, depending on instance rules).

[–] goferking0@lemmy.sdf.org 1 points 1 day ago

It's odd equating csam (absolutely terrible) and trolling (something that the definition of is extremely flexible). Hell even establishing bot behavior is difficult if not using the bot tag or account.

All in all apart from the csam everything you described is dependent on the instance so would not work with a top level

[–] Vicinus@piefed.zip 2 points 1 day ago

Appreciate the feedback :)

The difference between blocking and purging is that a blocked account is still residing on the instance (even more so for user blocks instead of admin blocks). As the data is still there, it opens possibility for legal trouble. Full purges by instance moderation action is different.

The scope of my proposal is not to help curate and filtering content for instances, but to enable widespread coordinated action against content which was already created and is harmful without any room for interpretation.

Makes sense. I suppose my described lists could also be made into purge lists.

That is a whole other issue. Scrapers and request spammers, not content spamming accounts, can be combated with already existing technology at the reverse proxy server. There are big crowdsourced IP banlists which are continuously updated.

Not my knowledge base, so good to know that already exists.

This would be the easiest solution. But I think it will lead away from individualism of instances, as all decisions are automatically applied, instead of only a manually reviewed subset.

Your idea with applying the mod action after a threshold of other instances did it too is something to consider. It will keep individualism but also creates “avalanches” once enough instances in the network agreed on a decision, which might be even better for propagating swift action against general harmful content.

Definitely a balance needs to be struck, between quick action and preventing abuse.

[–] chris@lemmy.grey.fail 11 points 2 days ago (3 children)

I administer my own instance of Lemmy and Mastodon. The CSAM issue was something I learned about real quick, unfortunately. I was able to implement community maintained blocklists. It's not perfect, by any means, but I've not seen any more harmful content.

The idea of a centralized judicial system does not seem compatible with the spirit of federation. The safety we expect from centralized platforms is something we gave up for our freedom. With that, we do have to be diligent and deal with the bad actors. It's the worst trade off in the whole deal.

It's also impossible to enforce, I think. The Rage Against the Machine "f you, I won't do what you tell me" spirit lives in all small server admins (by virtue of rebelling in the first place).

[–] WhyJiffie@sh.itjust.works 2 points 1 day ago

The idea of a centralized judicial system does not seem compatible with the spirit of federation. The safety we expect from centralized platforms is something we gave up for our freedom.

that's right but I think smaller groups of server admins could still team up and curate shared blocklists. in a small group trust is easier to manage.

load more comments (2 replies)
[–] docus@lemmy.dbzer0.com 7 points 2 days ago (7 children)

Interesting idea. Not an instance owner, and not familiar with the finer details of federation, so no idea if it could be done. My initial concerns is that a majority vote won’t work, if you have to wait for the majority of instance mods to vote it’s going to be too slow. Maybe some degree of instance level config helps. For example, if i had my own instance, i would follow ban/delete recommendations from the likes of .world, .dbzer0, but maybe not from .ml without a human reviewing it first. Also need to ensure the ‘court’ does not get flooded.

[–] anarcockworkorange@anarchist.nexus 1 points 1 day ago (1 children)

.world has its issues, mostly because of its behemoth size. Not all bans there would necessarily be a great idea to apply on instances that are an order or two of magnitude smaller. Their needs and approaches to moderation differ in enough ways that an auto-copy would probably not be advisable, unless we can reliably categorize them. If we can tell a ban comes because of CSAM, or something like that, that would make sense to immediately copy. But a behavioral / rule break sanction is much more closely tied to the specific instance rules and moderation standard.

[–] docus@lemmy.dbzer0.com 1 points 1 day ago (1 children)

Every instance will have its own approach to moderation. Almost by definition, since disagreement with an instance’s policies is a good reason to spin up your own one. .world was my home instance for a while, I would not say they have more issues than other instances. I left them because their policies on piracy related stuff. I understand their reasons, so it’s my issue, not theirs. Anyway, yes CSAM (and spamming?) should be a prompt fediverse wide ban and delete, as long as we can trust the decision makers

Well, I think the size of their userbase naturally poses a higher workload for admins and mods. So they naturally will have a lower tolerance for any risqué behavior, by sheer need of expediency dealing with the issues there. So even if a smaller instance shares the rules with them, the way they'd apply the rules are likely to be quite different.

load more comments (6 replies)
[–] hendrik@palaver.p3x.de 7 points 2 days ago* (last edited 2 days ago) (1 children)

I like the idea. Better yet: Don't put it on top, but make it part of the platform itself. I think moderation is an integral part of a platform and should be baked in.

And another idea: Some other platforms have moderation be some kind of feed. We could expose moderation decisions as some kind of feed people can subscribe to. That way I could say: I trust team XY to do the moderation for me. And someone else could subscribe to a different "court" or team of moderators who are more or less strict. I kinda like that idea as well. But it's also guaranteed to be (ab)used for the usual political, online ideology/identity war. Not sure if that's a bad thing or a good thing.

If you combine both concepts, you'd get a solution which isn't "central". And it offers customizability to the users, and/or individual instance admins.

[–] blued_gear@fedia.io 4 points 2 days ago (1 children)

Don't put it on top, but make it part of the platform itself.

Then we would need to convince every platform dev to implement it with a predefined standard and wait for the release. With the independent server + bot approach it gives more flexibility and every server admin can add the service without the platform to support it.

We could expose moderation decisions as some kind of feed people can subscribe to.

But then it would depend too much on the views of one instance. Every instance has their own set of rules, which is their right and is fine. But not all instances would like to apply the mod decisions based on rules they might not even have. With a common 3th-party jury mod actions are limited on only a set of rules all instances agree on, while they can apply more fine-grained rules themselves and not interfering with other servers.

But it's also guaranteed to be (ab)used for the usual political, online ideology/identity war.

This is also a big problem with following mod actions of a server which also publishes posts. There will be a bias and if that server has beef with someone else, it will lead to injustice.

Also another thing about "feed people can subscribe to": this proposed system is not for curated blocklists between users or such. It is for actions which have to apply to whole instances like account purges to ensure illegal media is not distributed.

[–] hendrik@palaver.p3x.de 6 points 2 days ago* (last edited 2 days ago) (1 children)

I think 1) and 2) are kind of what makes the Fediverse fun. We're not just an accumulation of sometimes compatible servers. We do make an effort to span one big, interoperable network and put in the effort to standardise and find common solutions. And we also try to offer means to individualise the experience on different instances.

It is for actions which have to apply to whole instances like account purges to ensure illegal media is not distributed.

I'm afraid we also have additional issues with different jurisdictions. I mean I'm a server operator based in Germany. I have different rules for hate speech than for example someone based in the USA. How I can and can't phrase certain things. The UK has some different/strict internet laws. And someone from Japan for example has a whole different set of rules for some kinds of posts... It'd be difficult to come up with a central solution which isn't some lowest common denominator. Which probably will be overblocking in this case?

[–] blued_gear@fedia.io 4 points 2 days ago (1 children)

It'd be difficult to come up with a central solution which isn't some lowest common denominator. Which probably will be overblocking in this case?

It should be lowest common denominator with underblocking; so the intersection of rules, not the union. If one needs more strict blocking, nobody stops them. The court is not supposed to replace instance local moderation, just to augment it to allow more swift central decisions on certain topics.

Also the implementation can allow following more than one court. So for example once for international internet law (really lowest common denominator) and one for German internet law.

[–] hendrik@palaver.p3x.de 5 points 2 days ago* (last edited 2 days ago)

Guess we're going for different goals, then.

For me in the role of an instance admin, I'd like some solution which properly cuts down on work that ends up on my plate. I'd rather have something so I can pool resources with other admins. I feel technically, it's not all that different from your suggestion, so I'd just go the extra mile and maybe that'd be something to properly rely on. I mean ultimately one of my main responsibilities is to enforce law and the rest of moderation comes second to that. But I'd also use whatever people have to offer to at least make it a bit easier.

And nobody wants to see all the spam, nor do I want to get nasty pictures in a DM. All that stuff should disappear more swiftly.

[–] jeena@piefed.jeena.net 5 points 2 days ago (3 children)

I'm not sure about centralization but delegation would probably make more sense. So I could delegate my own instances moderation to a instance I trust. This way we still can have seperate ways of moderating so the Tankies can moderate their stuff, the Nazis their stuff, Liberals theirs, etc. pp.

load more comments (3 replies)
[–] Pamasich@kbin.earth 4 points 2 days ago (1 children)

Everyone can post a case via normal Fedi posts to the court and the elected judges give a verdict via majority vote. Once a case has a verdict, all instances should immediately apply the decided action against the offending content / account.

My immediate thought reading this was, how does that work across jurisdictions? Is the idea that every jurisdiction runs its own instance of this software? Something illegal in one jurisdiction might not be in another.

There's also the question of representation. Does every (lemmy/mbin/piefed) instance get the same representation? If there's proportional representation, that just promotes centralization of the fediverse. If there's not, you can just set up new instances to manipulate the vote.

And the task of the court is to defend universal rules all following instances agree on.

Sure, but are there checks and balances which ensure that?

load more comments (1 replies)
[–] vk6flab@lemmy.radio 3 points 2 days ago (1 children)

The more steps, the less effective any moderation is going to be.

I literally just reported about 50 or so spam posts, manually, for a message that was being posted by new accounts with only one or two posts, each to a different communities and instances, seconds apart, each username related words with a number that changed, account age less than a day.

In other words, an automated spamming engine creating accounts across multiple instances and posting at scale.

Think USENET Green Card from the early 90's, a pivotal moment in spam history. This is the tip of the iceberg.

You cannot fight this with judges and voting, you need a better approach.

[–] nocturne@piefed.social 3 points 1 day ago (2 children)

Lemmy & piefed need a multi post report mechanism, or at least the ability to report an account and not just their posts.

[–] WhyJiffie@sh.itjust.works 2 points 1 day ago

the reporting system could also keep track of a reporter score, measuring how useful a user's reports are. the only effect it would have is for ordering of incoming reports in the list moderators see, reports from users with a good track record show earlier in the list

[–] vk6flab@lemmy.radio 2 points 1 day ago

While true, reporting the spam run I saw would not have benefitted from such a system, since there were nearly as many accounts as there were posts and they were across many different instances.

[–] slazer2au@lemmy.world 4 points 2 days ago (1 children)

It does sound like a decent idea, just not sure how it will work with the different ideologies of the Lemmy instances.
Things that are banworthy on one instance are not banworthy on another.

[–] Auster@thebrainbin.org 4 points 2 days ago (3 children)

I think it sounds good only until put in practice.

If 99% is useful but 1% goes against the instance's philosophy, they have to accept this 1%. But if someone involved in picking what is put in this overarching moderation starts pushing this 1% to 2%, 4%, ever more through the Overton Window, it would deteriorate more and more the instances that had to accept the original 1%.

And even without the possibility of intentional sabotage, one rule being applied for every individual instance would still mean instances would need to adapt for the lowest common denominator, meaning a slow end of individuality. And if a small instance is no different than a big one, those bigger ones start canibalizing the userbase of the smaller ones.


What I expect to happen, and that already does to some extent, is to clusters of instances with similar interests to form, and by extension being prone to accept aligning moderation and philosophies with their direct allies.

But that's still mostly a bilateral move, not an one rule to govern them all, so dependence or independence is still tied to individual interests.

load more comments (3 replies)
[–] lambalicious@lemmy.sdf.org 2 points 1 day ago (1 children)

CSAM

Wouldn't disabling media federation get rid of that part of the problem real fast, to then leave people open to work on the moderation issues such as "federated judging" etc?

[–] goferking0@lemmy.sdf.org 1 points 1 day ago

Not if just using a link to said material. Media blocks would only cover uploads.

Not to mitigate the issue of csam but also completey separate issue from moderation or federation judgment

[–] INeedMana@piefed.zip 3 points 2 days ago (1 children)

Just as food for thought, there has also been an idea in the opposite direction - decentralize voting even more

I was going to mention the FAF.

[–] mschae@discuss.mschae23.de 3 points 2 days ago (2 children)

This is especially problematic as media [...] gets duplicated to every receiving instance.

I'm not sure this is actually the case. The posts certainly do get duplicated to every instance, of course, but the media contained in them are always hosted by the originating instance, as far as I can tell. So once it is deleted from there, no one can access it anymore.

I think it's an interesting idea though. Since you mentioned votes by members of the individual instances, I wonder how you would handle the different sizes of instances. I'm the only user of my instance, for example. I probably wouldn't be able to be judge then, right?

[–] Auster@thebrainbin.org 5 points 2 days ago

From what I'd seen in the announcements of lemm.ee when it was alive (RIP), one concern by the administrator was if the instance should keep local copies of files for as long as possible, as a timed cache, or link to the original instance. So taking it as an example, the technology for local copies does seem to exist on Lemmy at least.

[–] blued_gear@fedia.io 4 points 2 days ago

The posts certainly do get duplicated to every instance, of course, but the media contained in them are always hosted by the originating instance, as far as I can tell.

Some software creates thumbnails on the server storage.

I wonder how you would handle the different sizes of instances.

That is a problem to discuss after it is decided if the Fediverse even wants such a service ;)
But I'm aware and one possibility would be to limit the number of electable judges from one instance. The upper limit must be in proportion to their user-count to be somewhat representing. But I think instances with only a handful of users won't ever get seats without the jury being way too big. Or they are so popular that they get enough votes from other instance users.

[–] slimes@lemmy.world 3 points 2 days ago

This is a way for white people to abuse power dynamics and harm marginalized people.

Moderation is a skill and requires experience, more than most moderators have. It's ideally a paid role that people have to compensate them for the difficult work they do.

The mentality that its free or non-skilled work is due to tech companies being terrible role models for morality, worker equity, and justice. You cannot imitate these systems to succeed, they are based in bottomless pits of money that they use to squash human rights violations.

Judges in court systems are ideally well trained and experienced in the law. Its a paid gig and prone to being terribly abused.

When some instance that wants mutual aid posts to disappear gets a "judge" to do this would you tell the disabled person on your instance that they cannot ask their community for help? Where would you tell them to go when the people who make the most impact are cut off? Would they be banned for that? What choices to people harmed by "judges" have when they are targeted unfairly?

The amount of overhead managing moderation on one instance can be difficult, but sifting through decisions made by a bunch of anonymous "judges" sounds like an utterly depraved torture chamber. In the end the choice would be whether the instance agrees with the (unqualified, unvetted, unpaid) "judge's decision" which ultimately brings this back to where we are now.

load more comments
view more: next ›