So how would defederation work in this case?
-
So how would defederation work in this case?
-
So how would defederation work in this case?
I'm just a tourist here, but here's my take:
If C can recognize that the post it just got from D is the same as the one from B, then there should be a way for it to recognize it comes from A and ignore entirelyOr, even better, follow the federation model: subscribe to D's and B's pass-through from E and F, leaving out A. So D and B won't send out unwanted posts at all
-
There should be some routing in the protocol. So A sending out to whole alphabet won't take down C by multiplied burst from all the other letters
-
each NNTP post would be a thin wrapper around a data structure containing the HTTP headers (with signature and digest) and JSON that a normal HTTP POSTed Activity would have
Signature can also be embedded within an activity: https://codeberg.org/fediverse/fep/src/branch/main/fep/8b32/fep-8b32.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