Conversation

Notices

1. Embed this notice
   Toast :chaos: (toast@mk.toast.cafe)'s status on Sunday, 16-Oct-2022 23:49:29 JST Toast :chaos:

   #FoundKey release v13.0.0-preview2 is OUT
   
   It's highly recommended you update to it ASAP because of two highly important features:
   * outgoing deletes now work properly (they're sent out to ALL KNOWN instances)
   * instances are flagged as dead automatically (no more manually selecting "stop sending activities to this instance") for the benefit of your job queue
   
   This makes #fkey the first (to my knowledge) fedi software with optimal and correct handling of both incoming and outgoing deletes (e.g threads)!
   
   There are many other new and useful features as well.
   You can look at the full changelog here for the rest of them.

   • Embed this notice
     Toast :chaos: (toast@mk.toast.cafe)'s status on Tuesday, 08-Nov-2022 21:21:56 JST Toast :chaos:

     in reply to

     • clacke

     @clacke@libranet.de the correct behavior is to send the delete to basically everyone, since you never know where it might have been federated to (via fetches or relaying)
     other msky variants only send it to your followers
     
     as for other software, all msky variants cascade deletes
     so let's say you have a thread of notes A -> B -> C -> D
     on a deletion of B, all msky variants will trigger a deletion of C and D as well

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Tuesday, 08-Nov-2022 21:21:58 JST clacke

     in reply to
     @toast How are other implementations handling deletes incorrectly?
     
     EDIT: Oh, I see "they're sent out to ALL KNOWN instances", not just instances that would have received the original activity. So it would cover some of the instances that received the original post indirectly.