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.
-
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.
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
-
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
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
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login