4 ms·
There are some technical differences like AT storing all content in a Merkle tree so it's easier to replicate, check integrity, etc. It's not clear to me how va
by wmf 4y ago
There are some technical differences like AT storing all content in a Merkle tree so it's easier to replicate, check integrity, etc. It's not clear to me how valuable these features will be. Perhaps the biggest difference is that they've introduced a username->server indirection layer.
- nightpool 4y agoHow would you ever handle deleting posts or removing content if there's a Merkle tree that gets invalidated for every deleted post you send?
- pfraze 4y agoThe 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.
- gargron 4y agoRewriting 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.
- topranks 4y agoIt’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.