Conversation
Notices
-
Embed this notice
Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 25-Oct-2023 06:16:23 JST Haelwenn /элвэн/ :triskell:
@winter Mastodons will use anything but MRFs :D -
Embed this notice
Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 25-Oct-2023 07:21:18 JST Haelwenn /элвэн/ :triskell:
@lispi314 @winter Message Rewrite Facility, it allows to write a bunch of modules to arbitrarily filter/rewrite messages.
https://docs-develop.pleroma.social/backend/configuration/cheatsheet/#mrf-policies
A concept that IRC/Email/… servers pretty much all have and need in practice. -
Embed this notice
LisPi (lispi314@mastodon.top)'s status on Wednesday, 25-Oct-2023 07:21:19 JST LisPi
In conversation permalink -
Embed this notice
Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 25-Oct-2023 07:32:01 JST Haelwenn /элвэн/ :triskell:
@lispi314 @winter They're sadly quite specific to Pleroma (and derived) but at the same time writing modules is pretty easy, in fact quite a lot of MRFs shipped in Pleroma were contributed by admins and several maintain their own for some server-specific behavior.
And I'm not aware of another fedi implementation having similar capabilities so the need to get something fairly agnostic like you have with email (but not on IRC) hasn't really appeared.In conversation permalink -
Embed this notice
LisPi (lispi314@mastodon.top)'s status on Wednesday, 25-Oct-2023 07:32:02 JST LisPi
@lanodan @winter Yeah, filtering module chains are nicely flexible.
How separated from the implementation are they in practice? Email seems to mostly use pipes/subprocesses for such things.
In conversation permalink
-
Embed this notice