@mkljczk This is one of the reasons I decided against implementing an MRF. A declarative filtering system with rules stored in database is more user friendly and enables severed relationship checks
@silverpill I'm considering proposing some sort of configurable, maybe programmable like MRF-s, *composed moderation actions*, that would consist of steps like, append example.tld to `[:pleroma, :mrf_simple, :reject]`, then severe relationships with example.tld users and send severed relationships notifications, and then remove content from the suspended instance. The default actions could be modeled after Mastodon. But you could also write an action that, say, adds the instance to `:media_nsfw` and creates a job to remove it after a week. I think this aligns with Pleroma philosophy
@silverpill I'm considering proposing some sort of configurable, maybe programmable like MRF-s, *composed moderation actions*, that would consist of steps like, append example.tld to `[:pleroma, :mrf_simple, :reject]`, then severe relationships with example.tld users and send severed relationships notifications, and then remove content from the suspended instance. The default actions could be modeled after Mastodon. But you could also write an action that, say, adds the instance to `:media_nsfw`...
Gregory's Server
@mkljczk This is one of the reasons I decided against implementing an MRF. A declarative filtering system with rules stored in database is more user friendly and enables severed relationship checks