I would love if we could maintain a revision history for notes - right now, I have to dual-wield subscriptions (Bear + Drafts) in order to maintain proper revision history for my notes (at risk of switching out of a window in bear and losing some edit history before realising). I’d love to have piece of mind of maintaining version history in here too 
1 Like
Right now the focus is on Bear Web and Panda. After that, revision history is high on the list of things we would like to do.
6 Likes
Glad to hear, thank you!
Does “revision history of notes” means an automatic back up of the whole database OR saving manually different versions of a note?
1 Like
The latter I would guess. What would you find useful?
I personally would like to see a version saved every time I make a change to any note, for the last 30 days.
3 Likes
I agree. You usually want note versions when something went wrong, and that means not having to manually establish them.
Yeah that’s sort of what I’m envisioning. For example, in drafts (where I have it currently) I can see and restore versions over time:
This is one of the few remaining reasons I keep drafts around
1 Like
Actually i would consider both functions useful. But if i have to decide i would choose the latter one. The first one is more like a general backup. The second one - the version control - serves a different purpose but also can be considered as a kind of backup. Maybe both functions can be combined: The notes are all backuped by a special time rhythm (like in ulysses) and additionally to that i can store single notes manually. It would be then important for me to be able to find easily those manualy stored versions. A deluxe feature would be to be able to work with all those manually stored versions: I am thinking of having different drafts of the same note. I hope you understand what i mean with “other purpose than backup”
1 Like
In this thread automatic backups were discussed. Note version control by manually saving versions is indeed a different task. I took a look into drafts and it works different than what I have in my mind. I would be interested to hear how and for what purpose you use a version history like in drafts.
In drafts you can restore once saved versions but with two main differences to what I imagined as version control: 1. After restoring a version it remains with its old content as preset for a future restoration. I rather thought that by continuing working on that version the content of that version changes automatically by adaption to what you have added to the note. And 2. after restoring a version you loose the content of the note before restoration.
When we talk about version control we seam to mean two different tasks:
-
Actually there is just one note that keeps different versions as a backup for replacing the current note (like in draft)
-
You have real versions and each version changes with the process of working with that version
Would be interested to hear what would be more preferable 
I think revision history should be a higher priority, considering how Bear actually has data loss problems. Just last week, I found a note with a missing image:
I reported this particular bug in April 2023: [BUG] Missing images upon sync?
See also this thread: Images missing in imported notes