> now i think about it, i think i need to extend that feature to tombstone the replaced ones as well, so they don't get resurreted after deleting the newest version IMO, it may be correct to resurrect. If a user makes note A, then replaces it with note B, then deletes note B, they may expect that note A is what gets served. Suppose user makes A -> B -> C, then deletes B. Presumably that should not impact serving C.