Open mayel opened 9 months ago
Have you considered knicking/replicating the MRF functionality of *oma services? It is extremely effective in stopping spam. There is a proposal to implement that for Mastodon, but I am thinking that the underlying thinking could be applied to any/all Fediverse services, and as I say, it has proven itself to really be working nicely (I run Akkoma and have had zero spam during this latest wave).
Thanks for the suggestion! Luckily we do have MRF built-in: https://doc.bonfirenetworks.org/mrf.html (as our federation library started as fork of Pleroma). I will look into added the policies mentioned in that thread.
I can think of three possible approaches to begin with:
[ ] custom solution? (described below)
Custom solution could look like a simple scoring system, which adds/remove points based on things like:
and if the score passes a configurable limit, do not actively notify the user (i.e. with push or email notification) and filter them out in separate tabs in notifications/messages views
could try making the algorithm using a configurable formula, so admins but even users can go in settings to improve the formula or simply tweak the sensitivity of different criteria in real time to better react to a spam influx, and share their algos or copy paste them from others... potential lib: https://hexdocs.pm/ex_pression/full_description.html
For inspiration see: pixelfed/pixelfed@dev/app/Util/Sentiment/Bouncer.php#L57-L100