Gregory's Server@renchap it’s not more wasteful than posting. Which works fine. I don’t see the problem.
|
6 comments
@renchap Yes but account deletions are incredibly rare. The alternative would be to check every time you search an account on your instance to check if the account still exists.  @pkreissel they may be rare most of the time, but when you mass-delete accounts after some bad actors actions, spam attempts or other events, you call generate a lot of them in a short time. For a real example, we had to delete about 3000 accounts, which created 3000*17000 outbound notifications. And this gets worse with more users/instances.  @renchap @pkreissel Perhaps there should be a "BulkDelete" notification: signed by the instances public key listing all the accounts to be deleted in that batch. Then a single notification only needs to go out to each known server which can do a quick "do I hold any records at all from (origin server)" before processing further. To make things more efficient, servers could batch delay sending deletes for 10mins.  @renchap I think sending Deletes just to followers is a decent solution, if combined with servers refreshing an actor every time it appears in an Activity or Object. Ie, if some server wants to send a Note to a bunch of recipients the server should refresh the actors, and then notify the user that they're trying to send the Activity to invalid actors for every received Tombstone (or even removing them all together from the recipients list). |
@pkreissel you only broadcast posts to your followers. Account deletions are broadcasted to every known instance.