<![CDATA[Idea for a more capable relay server]]>Very often I hear from users and ex-users of the Fediverse, that they they complain about posts that never reached their accounts. For example they subscribed to a hashtag on two accounts on separate servers. Now they see that both servers deliver different posts.

A solution for that are relay servers. But not every admin wants to receive thousands of unwanted posts just receive the few ones with content that a user wanted.

A solution for that would be a relay server that would be able to deliver content based on some rules that the admin defined. This should be much more than just a list of hashtags. It should be possible to filter on content in any field of a message.

What do you think about this idea? I’m currently in the process of thinking about a way to communicate these filter conditions.

]]>https://fedi.wiki/topic/b5659013-d13a-4210-87fe-00bb70a7c878/idea-for-a-more-capable-relay-serverRSS for NodeWed, 24 Jun 2026 14:33:05 GMTThu, 15 Jan 2026 10:25:54 GMT60<![CDATA[Reply to Idea for a more capable relay server on Thu, 04 Jun 2026 08:51:55 GMT]]>Here's another interesting FEP from @steve where JSONPath-based syntax was proposed: https://codeberg.org/fediverse/fep/src/branch/main/fep/c195/fep-c195.md

]]>https://fedi.wiki/post/https://mitra.social/objects/019e91d4-fcc7-7d80-9bd7-697712e4b2d0https://fedi.wiki/post/https://mitra.social/objects/019e91d4-fcc7-7d80-9bd7-697712e4b2d0Thu, 04 Jun 2026 08:51:55 GMT<![CDATA[Reply to Idea for a more capable relay server on Wed, 03 Jun 2026 09:46:13 GMT]]>An activitypub relay based on rules makes sense. Filtering by hashtags, actors or message fields can reduce unnecessary traffic and improve consistency of delivery. Maybe FEP-6606 is a good basis for that approach: https://codeberg.org/fediverse/fep/src/branch/main/fep/6606/fep-6606.md

]]>https://fedi.wiki/post/https://socialhub.activitypub.rocks/ap/object/13a247d78d9e72ab0d234e674a84e592https://fedi.wiki/post/https://socialhub.activitypub.rocks/ap/object/13a247d78d9e72ab0d234e674a84e592Wed, 03 Jun 2026 09:46:13 GMT