The root gets updated with each update, and the diff gets exchanged as part of the sync protocol. Deleting and purging is no different than other federated protocols in that regard.
Rewriting the user's entire database on each delete sounds like it might become a problem. Especially as some users like to automatically delete old posts on a regular basis.
Comments
How would you ever handle deleting posts or removing content if there's a Merkle tree that gets invalidated for every deleted post you send?
The root gets updated with each update, and the diff gets exchanged as part of the sync protocol. Deleting and purging is no different than other federated protocols in that regard.
Rewriting the user's entire database on each delete sounds like it might become a problem. Especially as some users like to automatically delete old posts on a regular basis.
It’s literally the dumbest idea ever.
Why use a merkle tree if you need to give users the ability to remove stuff?
Just store it in some other struct and have each message signed by the user. Let them add and remove messages at will.