Roadmap

This page tracks status honestly rather than optimistically. Anything listed as planned has no date attached, because Konode is a small independent project and a date would be a guess.

Working today

Four data types, across Chromium and Firefox, onto storage you already own, with optional end-to-end encryption on every backend. Entry by entry:

• Shipped

  Live on both stores

  • Firefox Add-ons1.3.2
  • Chrome Web Store1.3.2
• Shipped1.3.2

  A blocked deletion that would not stop

  Konode refuses any one sync that would remove more than 60 percent of your bookmarks, and saves a restore point when it does. What it used to do next was keep that request and publish it again under its own name, so within a few cycles every device was asking every other one to delete bookmarks all of them still had. The warning returned every minute, named a different device each time, and nothing you did on any single device ended it.

  Nothing was ever lost. The guard refused the deletion every time; what it could not do was stop being asked. A device now only ever asks for the deletions it made itself, and ignores that request when a peer makes it, so the warning stops on the first sync after one device updates, even while your others are still on the older build.

• Shipped1.3.1

  See what a held back deletion holds, and allow it

  Settings → Activity shows a card for a deletion Konode stopped: how many bookmarks of how many, which device asked for it, and how much of your tree that is, with a button that applies it. Before this the only route was a slider that stops at 95 percent, so a device asking to clear nearly all of its bookmarks stayed blocked wherever you put it.

  Saying yes covers the sync that follows and nothing after it, so a deletion that turns up later is stopped and shown to you like any other. The restore point is already saved before you are asked.

• Shipped1.3.0

  Interface translation

  English, Hungarian, German, Spanish and Chinese (Simplified), all five complete, on every screen Konode has. It reads through the browser's own chrome.i18n, so there is no library and no bundle cost, and it follows the language your browser is already set to rather than asking you to pick one.

  Spanish and Chinese came from volunteers on Hosted Weblate, where translating needs no git, no pull request and nothing installed. A language reaches a release once it is complete, because a screen that is half translated reads worse than an English one.

• Shipped1.2.0

  Chromium browsers and Firefox

  Chrome, Brave, Helium and ungoogled-chromium, plus Firefox and Waterfox. Verified across Firefox, Brave and Helium sharing one sync folder. History arrives on its original visit dates on Firefox, the only engine that permits it. Firefox for Android runs it too, with open tabs only: that browser has no bookmarks API and will not grant the history permission on request, so Konode marks both unavailable there and skips them rather than failing the sync.

• Shipped1.1.0

  Three backends, seven ways in

  Google Drive with the narrow drive.file scope, GitHub with a fine-grained token on a single private repository, and WebDAV against any compliant server. Nextcloud, ownCloud, pCloud, Koofr and Fastmail each get a card of their own. Synology, kDrive and everything else go through the generic WebDAV card.

• Shipped1.1.0

  Bookmark restore points

  Timestamped copies of the bookmark tree on your own storage, the newest ten kept. Saved by hand, or automatically when Konode refuses an unusual mass deletion. A restore only ever adds bookmarks back, never removes any.

• Shipped1.1.0

  Activity, statistics and devices

  One tab in Settings covering what synced and when, alongside the device list and the option to forget a device you no longer use. Since 1.3.0 forgetting reaches your other machines too: each one drops the forgotten device on its next sync, so its tabs stop being offered and its extensions stop counting as missing here.

• Shipped

  Four data types, merged across every device

  Bookmarks with two-way sync, tombstoned deletions, and renames, moves and folder reorders propagating. Open tabs and sessions, de-duplicated history, and the installed-extension list. Every type folds in each peer's file on every sync, so three or more devices converge rather than overwriting one another.

• Shipped

  Optional end-to-end encryption

  Turn it on and your storage provider holds ciphertext it cannot read. The key is derived on your device from a passphrase that never leaves it: AES-256-GCM, with PBKDF2-SHA256 over 600,000 iterations. Every download is checked against a SHA-256 sum before it is applied, on every backend.

• Shipped

  Conflict resolution you choose

  Newest change wins, always prefer this device, always prefer the other, or resolve each conflict yourself. The first three decide without asking and are what most people want. Resolving by hand is the weakest of the four today, and the Planned section says what it is missing.

• Works

  Orion, on the WebKit engine

  Not a supported target, and the reason is no longer that it fails. A field session in August 2026 had Orion and Brave sharing one WebDAV folder with encryption on, and all four data types synced.

  What it also showed is that WebKit breaks assumptions the Chromium code rests on, invisibly to the test suite. Three of those are fixed in 1.3.0:

  • arriving bookmarks split across Orion's two bookmark roots, so a tree landed partly in each
  • a saved session restored as one tab, because WebKit grants a click a single programmatic open and Konode spent it checking whether it was allowed more
  • a first install showed no setup wizard, because the engine never fires the event that opens it. The popup now offers a way in until a provider is chosen

  All three are written and released, and none has been run on an Orion device yet, which is why this card still says Works rather than Shipped. Reports are welcome.

  Google Drive sign-in is the one thing that stays broken: the browser's own OAuth bridge throws instead of opening Google's consent screen, so Drive is switched off there with a plain message. WebDAV is the verified way in, GitHub is reported working there by someone running Orion RC, and Safari itself would need a native app wrapper that Konode does not ship.

Planned

Nothing here has a date. Konode is a small independent project and a date would be a guess.

• Planned

  Traditional Chinese

  Konode had no Traditional Chinese at all, and the language it falls back to is English, so a browser set to 正體中文 was not quietly getting the Simplified version. It was getting English. A reader in Taiwan told us, and they were right. The language is open on Hosted Weblate now and ships once it is complete.

  It will not be a conversion of the Simplified files. 擴充功能 and 扩展 are different words, not one word in two sets of characters, and a converted file would read as mainland Chinese wearing Traditional characters. If you read it, this is the one where help would land soonest.

• Planned

  Nutstore, in the next release

  A card for Nutstore (坚果云), so setting it up is picking it from the list and pasting an app password rather than typing a server address. It is written and due in 1.3.3. If you are in mainland China this is the one that matters, because Google Drive is not reachable from there and the storage option the setup leads with is not an option for you. GitHub and WebDAV both work in the meantime.

• Planned

  More languages

  Italian, Estonian and Japanese are being translated by volunteers on Hosted Weblate, and none of them has a date. Each ships in the first release after it is finished. Anyone who reads a language Konode does not speak yet can start it there.

• Planned

  More backends, cheapest sign-in first

  Token and basic-auth backends come first, because they are the same class of work as WebDAV and GitHub: a Dropbox token, S3-compatible storage, Backblaze B2. OAuth backends follow, Dropbox and OneDrive among them, each needing its own app registration, redirect and refresh handling per browser.

• Planned

  MEGA

  The heaviest of the backends, and the reason it is not simply another WebDAV card: MEGA's own API is the only real way in, it is only practical to drive through a client library, and that library has to carry MEGA's client-side encryption. Not started in any usable form, and still the further along of the two storage backends here: it is the one with the design work written down.

• Planned

  Filen, behind MEGA

  Asked for on Reddit, and deliberately not scheduled. MEGA comes first because it is the one we have thought through, and Filen follows only if what MEGA costs turns out to carry over. We would rather leave it out than force it in, so treat this as a condition rather than a plan.

  What is settled so far: Filen encrypts everything on your device before it leaves, and it offers no hosted WebDAV address, so it cannot become one more preset on the WebDAV card. It does publish an official SDK that runs in a browser, so the question is not whether a route exists. It is whether carrying another provider's encryption is worth what it costs an extension this size, and that question is open, which is the honest reason there is no date here.

  There is something to try today if you already run Filen's command line tool. It can serve your drive over WebDAV or S3 from your own machine, and the generic WebDAV card takes a local address. Nobody has reported trying that with Konode, and a server you run yourself is not a backend we support, so treat it as an experiment. Reports are welcome.

• Planned

  Conflict resolution that shows you the difference

  Set conflict resolution to Manual and Konode asks which version of your bookmarks to keep, without showing you either one. Both answers act on the whole tree, so the choice is a guess. The plan is a resolve screen in Settings with room to list what actually differs, title and address for bookmarks and history, reached by a button on the popup rather than squeezed into a popup 360 pixels wide.

  Underneath it is a second problem worth fixing first. Manual asks whenever two devices' files are not identical byte for byte, and they never are: each browser gives a bookmark its own internal identifier and its own date added, neither of which can survive the trip. So it asks on the first sync between any two devices even when the bookmarks on both are the same. Both are open in the tracker.

• Planned

  Diffs between restore points

  See what actually changed between two restore points, rather than only that a sync ran. A restore point already holds a full bookmark tree, and the extension already reads one back and decrypts it in order to restore it, so this is a comparison view over data that exists. Bookmarks only, and only across the ten most recent restore points.

• Planned

  Faster history sync

  The full-history dedup scan that runs on every import. Since 1.3.1 it is built once per sync rather than once per device, which was the larger half of the cost as soon as you had more than one other device. What is left is that a sync importing any history at all still reads your whole local history once, to answer whether it already holds a newer visit for a page. An incremental diff for very large bookmark trees, past ten thousand or so, sits in the same bucket.

Not planned

Some things get asked for regularly and are not coming, for reasons worth stating plainly:

• No

  iCloud Drive

  Apple publishes no third-party API for iCloud Drive and no WebDAV, so there is no supported way for an extension to put a file there. What circulates as iCloud over WebDAV is a relay service that copies your files through its own servers, which is the arrangement Konode exists to avoid.

  The sanctioned route, CloudKit, writes into a container the developer registers rather than into your iCloud Drive. You could not open those files in Finder, copy them out, or hand them to another tool. Being able to do exactly that is what "storage you own" means here, so an iCloud card would be the one backend that makes the promise untrue. On Apple hardware, any WebDAV provider works today, and so does a private GitHub repository.

• No

  Password sync

  Browser extensions cannot read the browser's native password store. That is a security boundary the browser enforces, so this is not something Konode can choose to add. Use a dedicated password manager.

• No

  A hosted Konode backend

  Running a server would undo the entire point. Your data goes to storage you already control, which is only true as long as there is nothing in the middle.

• No

  Analytics or telemetry

  Not now and not later, including the anonymous, aggregated kind. Bug reports through GitHub issues are how Konode finds out what is broken.