Conversation

Notices

1. Embed this notice
   Rich Felker (dalias@hachyderm.io)'s status on Sunday, 13-Jul-2025 12:26:47 JST Rich Felker

   • Jenniferplusplus

   @jenniferplusplus @hipsterelectron Mechanically, "rejecting a reply" is just refusal to include it when a request for the replies/thread is made, pretending it's not there.

   If you do that, only users whose home instance is the same instance as the unwanted reply-guy is replying from might be able to see the reply.

   Adding something to the protocol to ask that instance not to allow it is the main addition that would be nice.

   • Embed this notice
     Jenniferplusplus (jenniferplusplus@hachyderm.io)'s status on Sunday, 13-Jul-2025 12:42:19 JST Jenniferplusplus

     in reply to

     @dalias @hipsterelectron the de facto definition of a reply is any post that sets a value for the inReplyTo field, and the set of instances that can see it is any instance that received it, plus the few that might later request it.

     Whether it gets added to a replies collection is basically never a factor.

     It's also relevant that there is no way to query a collection. All you can do is iterate it. So the only way to confirm an objects presence or absence in a collection is to iterate the whole thing. Which contributes to the wild west authorization.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Sunday, 13-Jul-2025 12:48:02 JST Rich Felker

     in reply to

     • Jenniferplusplus

     @jenniferplusplus @hipsterelectron I don't know the exact protocol mechanism, but there's some iterator by which you obtain all replies to a post, or similar, from the instance the post is from.

     All that instance has to do is omit the offending post from the iteration, and nobody will see it as part of the thread except possibly on the instance it originated from.

   • Embed this notice
     Jenniferplusplus (jenniferplusplus@hachyderm.io)'s status on Sunday, 13-Jul-2025 12:51:57 JST Jenniferplusplus

     in reply to

     @dalias @hipsterelectron right. What I'm telling you is nobody does it that way, because it's a performance nightmare.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Sunday, 13-Jul-2025 13:23:27 JST Rich Felker

     in reply to

     • Jenniferplusplus

     @jenniferplusplus @hipsterelectron Don't they omit blocked accounts from the iteration though? If so, how is this harder?

   • Embed this notice
     Jenniferplusplus (jenniferplusplus@hachyderm.io)'s status on Sunday, 13-Jul-2025 14:11:42 JST Jenniferplusplus

     in reply to

     @dalias @hipsterelectron 3rd party servers don't constantly re-iterate reply collections every time they encounter a post that claims to be a part of one. Because it would take forever, and it would produce an enormous traffic amplification attack on every participant in the network.