@hongminhee@hollo.social · Reply to Steve Bate

@steve @mariusor @nick Most deletes happen soon after posting, before many non-followers have fetched the object. Most posts are never boosted anyway. So maybe: if a post has never received an Announce, send the Delete only to followers; once it has, fall back to the current wider delivery.

The obvious race is a boost arriving just before the delete, but I think that still mostly works. The server receiving the Announce has to fetch the original, and by then it should get a 404 Not Found.

That would avoid a lot of unnecessary Delete fanout.

2 replies

@mariusor@metalhead.club · Reply to 洪 民憙 (Hong Minhee) :nonbinary:

@hongminhee to me that's too much logic to stuff in an already complicated machine.

Just send the Delete to the smallest set of parties you absolutely **know** as being directly interested: the people that would send something your way: your following list. As a courtesy you can do it to the people that follow you, so they know to purge you from their list.

Everyone else will suffer a 404 and deal with it to the best of their abilities, which should be way less complicated than the rube goldberg'esque setups you guys seem to favour.

@steve @nick