Deleted Status Updates (toots) that were indexed as vacancy should be removed from the index eventually.
Problem
When a user deletes a toot (update), or delete and redrafts it, we are showing results that are no longer available in the fediverse.
We need to remove these from our index too.
Discussion
When deleting a toot, a server may send out a delete event over the fediverse. The mastodon streaming API then emits this as a delete event. We may capture this event, but could miss it.
Structure
Options:
Rely only on the the delete event of the streaming api. This requires us to have solid uptime and ensure we don't miss any delete events otherwise.
A cron or timed run that re-checks a list of updates to see if it still available. Could be done over the web relying on HTTP status codes. Delete when no longer fetchable/timeout etc.
Combination of both.
The timed-recheck is more solid and will capture servers going down or toots otherwise dissapearing without sending delete events. It is heavier on server and client.
Intent
Problem
When a user deletes a toot (update), or delete and redrafts it, we are showing results that are no longer available in the fediverse.
We need to remove these from our index too.
Discussion
When deleting a toot, a server may send out a delete event over the fediverse. The mastodon streaming API then emits this as a
deleteevent. We may capture this event, but could miss it.Structure
Options:
deleteevent of the streaming api. This requires us to have solid uptime and ensure we don't miss any delete events otherwise.The timed-recheck is more solid and will capture servers going down or toots otherwise dissapearing without sending delete events. It is heavier on server and client.
Example
Toot re-drafted several times:
Check list