Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message Rewrite Facility (MRF) #29252

Open
JainWasUsed opened this issue Feb 16, 2024 · 4 comments
Open

Message Rewrite Facility (MRF) #29252

JainWasUsed opened this issue Feb 16, 2024 · 4 comments
Labels
suggestion Feature suggestion

Comments

@JainWasUsed
Copy link

JainWasUsed commented Feb 16, 2024

Pitch

Implement a similiar Version of a Message Rewrite Facility (MRF) (https://docs.akkoma.dev/stable/configuration/mrf/)
Give the Admins a "Framework" or an "Environment" which is able to rewrite or discard incoming or outgoing stuff.
Recent Spam Waves showed that for example Akkoma can handle such stuff way better than any other existing Platform.
Let me give you some examples:

RejectNewlyCreatedAccountNotesPolicy: Rejects posts from accounts when they are freshly created
https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/lib/pleroma/web/activity_pub/mrf/reject_newly_created_account_note_policy.ex
KeywordPolicy: Rejects posts based on keywords
https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/lib/pleroma/web/activity_pub/mrf/keyword_policy.ex
HellthreadPolicy: Rejects posts based on the amount of mentions
https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/lib/pleroma/web/activity_pub/mrf/hellthread_policy.ex

The point is, let Admins implement their own rules...

Motivation

Fight against Spam, fight against all sort of attacks, allows more fine grained configuration which anyone would benefit from.

@JainWasUsed JainWasUsed added the suggestion Feature suggestion label Feb 16, 2024
@KisaragiEffective
Copy link

See also: misskey-dev/misskey#13207 (in Japanese)

@KuJoe
Copy link

KuJoe commented Feb 17, 2024

These would all be amazing to have included natively in Mastodon. Thank you for sharing the examples!

@samwightt
Copy link

This really needs to be prioritized. The spam situation has really shown the absolutely abysmal state of mod tooling for Mastodon currently. It just does not scale. I'm having to suspend servers left and right, reporting accounts to their admins, following up with admins of suspended servers to see if they're abandoned or not... all because I cannot filter out posts programmatically. This is a basic feature that lots of other pieces of Fediverse software have. In a language like Ruby where you can literally interpret a string of code as Ruby dynamically, this should be incredibly easy to implement so that at least admins have something than the whack-a-mole bullshit we have right now.

@hellquist
Copy link

Posting just to confirm that the MRF (in Akkoma) has meant I have seen zero (0) spam in this latest wave. Implementing this, should be a priority in all the Fediverse services in general, and in Mastodon in particular. Seeing as Akkoma (and Pleroma) use Mastodons API (+ extensions) it should be backward compatible to use for Mastodon itself as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion Feature suggestion
Projects
None yet
Development

No branches or pull requests

5 participants