EtherPK 0.22.0 adds version history to synced notes
Understand this story
EtherPK 0.22.0 adds version history to every Markdown page and journal entry in synced graphs, and retains deleted content for recovery. This feature requires version 0.22.0 or higher and the use of synced graphs; local graphs are just file folders on the device and have no version history in EtherPK. Versions are generated automatically after an editing pause, at most once every 10 minutes per document per device, and are additionally saved before operations such as deletion, renaming, merging, and replace-all; the retention period defaults to 30 days and is billed against the storage quota. AI agents connected to synced graphs can use the list_versions and read_version tools to list and read the retained versions of a document, but cannot restore versions.
AI overview based on source reports · Updated 3 days ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Hacker News AIShow HN: Version History for Your Synced Notes (AI Agent Safety)
EtherPK 0.22.0 adds automatic version history for every page and journal entry in a synced graph, creating versions as you write and before actions like delete, rename, merge, Replace all, or removing protection. Versions and deleted items are kept for a set period (30 days in the examples), thinned as they age, encrypted with the graph's key before upload, and restorable from a Version history tab or the Deleted documents and files section. AI agents connected to a synced graph can list and read versions via the list_versions and read_version tools but cannot restore them, which a person does in EtherPK.
Activity for this story
- Current comparable activity
- 3
- Peak comparable activity
- 10Nov 12 06:00
- Change in the past 24 hours
- -50%
Trends compare the same fully observed participants, which may cover fewer participants than current activity. Move the pointer or tap the chart to inspect hourly activity; use the left and right arrow keys with a keyboard.