News for hackers. Stuff that matters.
Re:Faster CRDTs (2021) by Vinnl on Wednesday August 28, 2024 @08:45AM (#41378854)
I don't think the concern was necessarily about overhead, but about sensitive data. This is a problem in Git too: people make the mistake of reverting a commit with sensitive values and think it's gone, but the history is still out there.

Edit: or maybe that was the concern, but this other concern exists too :)

Re:Faster CRDTs (2021) by josephg on Wednesday August 28, 2024 @07:41PM (#41385611)
If thats what you're worried about, use Yjs. Yjs doesn't store deleted characters in documents. Unless you actively make yjs snapshots, once a character in a yjs document is deleted, its gone.
Re:Faster CRDTs (2021) by Vinnl on Thursday August 29, 2024 @08:24AM (#41390066)
Huh! I wonder how that works if the deletion isn't synced with other clients yet.
Re:Faster CRDTs (2021) by toomim on Wednesday September 11, 2024 @02:56PM (#41514257)
It stores the deleted ranges, but not the chars of text that compose those ranges.

So from a privacy perspective, you see the metadata of edit history (the DAG of character positions edited), but are blind to the text.

Re:Faster CRDTs (2021) by Vinnl on Thursday September 12, 2024 @05:19AM (#41519007)
Ah! That makes sense, thanks - today I learned!