rich1.0Akamaister (npub19w…dguvd)https://nostr.ae/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvdnjumphttps://nostr.ae**Local Version History Comes to Continuum** Andrew G. Stanton – July 7, 2026 One of the more interesting things about Nostr is that not all events behave the same way. - Profiles (kind:0) are replaceable by design. - Articles (kind:30023) are parameterized replaceable events identified by a d tag. Traditional notes (kind:1) are different. They aren't replaceable at all. Every edit is simply another event. Continuum has started taking advantage of those differences. Today I added local version history for: Profiles Articles Continuum-authored notes For profiles and articles, the relationship already exists within the protocol itself. For notes, Continuum uses a local convention: edited notes preserve a shared d tag so they can be grouped together as revisions of the same piece of writing. Other Nostr clients simply see independent kind:1 notes. Continuum understands the relationship between them. Every authored revision is preserved locally before the current state moves forward. For notes and articles, previous revisions are available directly from the viewer through a collapsible Versions section. For profiles, previous revisions can now be loaded directly into the dashboard itself, allowing older profile states to be viewed without leaving the page. Nothing is overwritten. Nothing is lost. Under the hood, Continuum now maintains three distinct layers of memory: nostr_events — current local state nostr_events_history — local revision history Git archives — long-term preservation and recovery Most Nostr clients focus on the latest event. Continuum is beginning to preserve the path that led there. #Continuum #Nostr #LocalFirst #DigitalPreservation #RelationalMemory