So my thinking so far is:

• We build a /api/v1/admin/delete API endpoint which takes {"hash": <hash>} as JSON input.
  
• We build a yarnc admin delete <hash> sub-command (start a new sub-command group)
  

Which would delete a Twt by hash from the Pod’s archive and blacklist it (as it could come back from other pods via the Converge logic).

This would require manual operations to be performed by one or more cooperating / participating Pod operators in the network. And I think this would have to end up being a “culture” we build upon where we agree when incidents that require this happen, that we get together in some way to cooperatively agree on a Twt deletion.

A similar set of tools would have to be built for the Twtxt Search engine too, although I would probably do this by hand for now as it does not peer with pods and therefore has no way to bring back Twts from the dead from a convergence logic that yarnd has.

As discussed on IRC just now (g’night @lyse@lyse.isobeef.org 😴) couple of things we agree on:

• The API was always written like this, so changing it now is “too much work” 😅 so we’ll leave it the way it is.
  
• We don’t complete agree on the “automatic deletion” just yet, and there are clear problems with this when pods exchange twts with each other (Convergence)
  
• We should document a design proposal and discuss