Problem
I have been using Wayscriber for note-taking and explanations, and I really like its smooth workflow. However, I have faced a serious persistence problem: sometimes my whole session disappears permanently.
In normal usage, Wayscriber sessions are usually persistent. But I noticed that data loss can happen when switching between --active mode and --daemon mode, or possibly due to other unexpected situations that I have not fully identified yet.
I am not sure whether this is caused by a persistence bug, a mode-switching issue, or a session overwrite problem. But the result is very serious: all written notes, explanations, and board content can be lost forever.
Suggested feature
If fixing all persistence edge cases is complicated, I suggest adding a manual board export/import feature.
For example, Wayscriber could support saving boards to an external local file, such as: .board, .wayboard, .wayscriber, or any other suitable extension.
Expected behavior
The user should be able to:
- Save the current board/session to an external local file before closing Wayscriber.
- Continue using the existing automatic session persistence normally.
- Open/import a saved file later.
- When importing a saved file, Wayscriber should add it as an extra board to the current Wayscriber environment, instead of replacing the existing session.
Why this matters
This would provide a manual recovery mechanism if the automatic persistent session is lost or overwritten.
Even if Wayscriber already has session persistence, an explicit “Save board as file” feature would give users much more confidence while working, especially when using Wayscriber for important explanations, study notes, teaching, or long sessions.
Losing all work unexpectedly is extremely frustrating. It is serious enough that a user may consider leaving Wayscriber, despite how smooth and useful the app is, and look for another note-taking or annotation tool.
Possible UI/actions
A simple first version could include:
Save board as...Import board from file...- Optional keyboard shortcuts
- Optional command-line support, for example:
wayscriber --export-board my-notes.wayboard
wayscriber --import-board my-notes.wayboard
Additional note
This feature does not need to replace the current session persistence system. It would simply act as a safety backup layer, so users can manually protect important work from unexpected session loss.
Problem
I have been using Wayscriber for note-taking and explanations, and I really like its smooth workflow. However, I have faced a serious persistence problem: sometimes my whole session disappears permanently.
In normal usage, Wayscriber sessions are usually persistent. But I noticed that data loss can happen when switching between
--activemode and--daemonmode, or possibly due to other unexpected situations that I have not fully identified yet.I am not sure whether this is caused by a persistence bug, a mode-switching issue, or a session overwrite problem. But the result is very serious: all written notes, explanations, and board content can be lost forever.
Suggested feature
If fixing all persistence edge cases is complicated, I suggest adding a manual board export/import feature.
For example, Wayscriber could support saving boards to an external local file, such as:
.board,.wayboard,.wayscriber, or any other suitable extension.Expected behavior
The user should be able to:
Why this matters
This would provide a manual recovery mechanism if the automatic persistent session is lost or overwritten.
Even if Wayscriber already has session persistence, an explicit “Save board as file” feature would give users much more confidence while working, especially when using Wayscriber for important explanations, study notes, teaching, or long sessions.
Losing all work unexpectedly is extremely frustrating. It is serious enough that a user may consider leaving Wayscriber, despite how smooth and useful the app is, and look for another note-taking or annotation tool.
Possible UI/actions
A simple first version could include:
Save board as...Import board from file...Additional note
This feature does not need to replace the current session persistence system. It would simply act as a safety backup layer, so users can manually protect important work from unexpected session loss.