Trying to sum up the current proposal (keeping hashes):

1. Extend the hash length to avoid collisions.
   
2. Introduce the concept of, what shall we call it, “update twts”.
   
   • A twt starting with (edit:#3f36byq) tells clients to update the twt #3f36byq with the content of this particular twt.
     
   • A twt starting with (delete:#3f36byq) advises clients to delete #3f36byq from their storage.
     

Right?

@movq@www.uninformativ.de Pretry much 👌

The important bits missing from this summary (devil is in the details) are two requirements:

• Clients should order Twts by their timestamp.
  
• Clients must validate all edit and delete requests that the hash being indicated belongs to and came from that feed.
  
• Client should honour delete requests and delete Twts from their cache/archive.

@movq@www.uninformativ.de I think not.

What about edits of edits? Do we want to “chain” edits or does the latest edit simply win?

This gets too complicated if we start to support this kind of nonsense 🤣