v1.7.0
FUTO Notes 1.7.0
Batched blob transfers, prefix and fuzzy search, per-note undo history, and a much faster desktop start-up.
Sync and the note you’re editing
- Better handling of changes that come in from the server while you’re editing a note
- Faster transfers — blobs upload and download in batches, with timeouts scaled to size
- A filename your platform can’t represent is now skipped instead of breaking sync for every device
Search
- Support for prefixes
- Multi-word searches now require every word, falling back to any-word only when nothing contains them all
- Fuzzy finding
- Titles and recently edited notes rank higher
Editor
- Every note keeps its own undo history — leave a note and come back and undo still works, and it can never pull in text from a different note
- Caret placement fixes
- Title renames commit reliably when you move to the body, when the field loses focus, and across a whole drag
- A duplicate title now warns you instead of quietly failing to save
- Renumbering an ordered list undoes in one step, together with the edit that caused it
Speed
- Desktop opens much faster
- The note list appears at startup instead of waiting for everything to load
- The folder tree is virtualized — scrolling and flinging no longer blank out or drop labels
- Large pastes, typing wikilinks in a big vault, note previews, and tag scanning no longer get slower as your vault grows
- Collapsing the sidebar and typing in long notes hold their frame rate
Android
- Text fields in dialogs keep focus when the keyboard opens
- The launcher icon renders at full size again
- The editor is gated on what the WebView engine can actually do rather than its version number, so third-party WebViews work
- Choosing a folder that already holds notes opens it instead of refusing
- A note that fails to be created now reports the failure instead of disappearing
iOS
- A pending sync decision for the open note is kept while that note loads
Safety and diagnostics
- An incoming sync path that would escape the vault is rejected
- Vault reads-then-writes are serialized across writers, including tombstone and folder operations
- Installing falls back to a copy when the filesystem rejects atomic rename flags