So how would defederation work in this case?

Reply to So how would defederation work in this case? on Wed, 01 Apr 2026 16:05:51 GMT

silverpill@mitra.social — Wed, 01 Apr 2026 16:05:51 GMT

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

Reply to So how would defederation work in this case? on Wed, 01 Apr 2026 11:56:04 GMT

ineedmana@piefed.zip — Wed, 01 Apr 2026 11:56:04 GMT

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

Reply to So how would defederation work in this case? on Wed, 01 Apr 2026 11:48:49 GMT

ineedmana@piefed.zip — Wed, 01 Apr 2026 11:48:49 GMT

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 entirely

Or, 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