Releases: konabe-studio/konode
Release list
v1.3.0
Konode speaks your language on every screen it has. Settings was the last one still in English whatever the rest of Konode was reading in, and Spanish and Chinese (Simplified) are now complete, which brings the finished languages to five: English, Hungarian, German, Spanish and Chinese. Konode follows the language your browser is already set to, so there is nothing to switch on. Alongside that, a device you forgot no longer haunts your other machines, and three fixes for browsers built on WebKit. Full list in CHANGELOG.md.
Who translated it
Spanish is the work of Pablo Trabucco, and Chinese (Simplified) is the work of keane. Both are complete, all 308 strings, and both were volunteered through Hosted Weblate, where anyone can translate Konode without touching code or opening a pull request. Thank you both.
More languages are being worked on there now. A language ships once it is complete, because a screen that is half translated reads worse than an English one.
One honest note on the WebKit fixes
They come from a field session on Orion, they are written and tested against the suite, and none of them has been run on the device yet. If you sync with Orion, they should fix bookmarks arriving split across two folders, a session restoring as a single tab, and a first install with no way into setup. Reports welcome.
Which download
Both zips here are source builds. They do not carry Konode's own Google OAuth client, so in these builds Google Drive sign-in needs an OAuth client of your own. GitHub and WebDAV are unaffected and need nothing extra. For Drive working out of the box, install from the store instead.
- Chrome, Brave, Helium and other Chromium browsers — Chrome Web Store. 1.3.0 is submitted and waiting on review, so the store serves 1.2.1 until it clears, and Chrome updates itself once it does. To use the zip instead: unzip
konode-chrome-1.3.0.zip, thenchrome://extensions→ Developer mode → Load unpacked. - Firefox and Waterfox — Firefox Add-ons, already serving 1.3.0. Firefox and Waterfox update themselves, so there is nothing to do. Installing from the listing is the right way in;
konode-firefox-1.3.0.ziphere loads only as a temporary add-on (about:debugging#/runtime/this-firefox), which Firefox drops on restart, so it is for trying it rather than for living on.
Upgrading
Nothing to do. The sync file format is unchanged, so your devices keep talking to each other across the update with no migration and no re-setup.
Two things you may notice once every device has updated. Konode's interface will be in your browser's language if that is one of the five it now ships, which is a change you did not ask for and can't switch off, but nothing about your data moves with it. And a device you forgot a while ago will finally stop being offered for session restore on your other machines: each one drops it on its next sync, not the instant you click Forget.
Full Changelog: v1.2.1...v1.3.0
v1.2.1
A patch release, and four field reports over two days that turned out to be one mistake:
Konode treated a permission its manifest asks for as proof that the browser implements the
feature behind it. That is not true on Firefox for Android, not true on Chrome for an
optional permission you never granted, and not reliable on WebKit browsers either. Konode
now checks what your browser can actually do, and says so plainly where it can't. Full list
in CHANGELOG.md.
The headline fixes:
- Settings could open to a blank page. On a fresh 1.2.0 install with extension sync left
off, which is the default, opening Settings showed nothing at all. It opens normally now,
whether or not extension sync is on. - Firefox for Android works properly. Setup no longer blames your WebDAV server for a
permission it was never asked about, the History toggle explains itself instead of
springing back, and Bookmarks and History are shown as unavailable there with the reason
rather than failing every sync. Open tabs sync as before. - One unsupported browser feature no longer takes the rest of Konode with it. A browser
missing a single API used to stop Konode setting itself up past that point. Now it loses
only what depends on that feature. - A data type that lost its permission says so. Browsers let you take a permission back
from their own settings without telling the extension. Konode now names the missing
permission and how to restore it, and keeps syncing everything else meanwhile. - If a screen ever fails to draw, you get an explanation, the error text to quote in a
report, and a reload button, instead of an empty window. Your synced data is never
involved in those failures, and the screen says so.
Which download
Most people need neither zip. Firefox Add-ons is already serving 1.2.1, so Firefox and
Waterfox update on their own, and the Chrome Web Store is reviewing 1.2.1 right now and
will update Chromium browsers once it clears.
Both zips here are source builds. They do not carry Konode's own Google OAuth client,
so in these builds Google Drive sign-in needs an OAuth client of your own. GitHub and
WebDAV are unaffected and need nothing extra. For Drive working out of the box, install
from the store.
- Chrome, Brave, Helium and other Chromium browsers:
Chrome Web Store.
1.2.1 is uploaded and waiting on review, so the store serves 1.2.0 until it clears. If you
would rather not wait: unzipkonode-chrome-1.2.1.zip, thenchrome://extensions→
Developer mode → Load unpacked. - Firefox and Waterfox:
Firefox Add-ons, which is live at
1.2.1.konode-firefox-1.2.1.zipis here for building and review, not for daily use: a
temporary add-on loaded throughabout:debuggingis removed when Firefox restarts.
Upgrading
Nothing to do. The sync file format is unchanged from 1.2.0, so there is no re-upload this
time and no action on any of your devices. If a data type had been quietly syncing nothing
because its permission was revoked, Konode will now tell you which one and why.
Full Changelog: v1.2.0...v1.2.1
v1.2.0
A code-review pass over the sync engine, the storage backends and the interface, plus the
first release carrying a Firefox build. Most of it is correctness: several ways your data
could quietly fail to reach your other devices, and several places Konode reported success
it had never actually checked. Full list in
CHANGELOG.md.
Verified on Brave, Helium and Firefox on desktop — three devices sharing one Google Drive
folder, with device naming, bookmark sync, renames and history all crossing between them.
Which download
Both zips here are source builds. They do not carry Konode's own Google OAuth client,
so in these builds Google Drive sign-in needs an OAuth client of your own. GitHub and
WebDAV are unaffected and need nothing extra. For Drive working out of the box, install
from the store instead.
- Chrome, Brave, Helium and other Chromium browsers —
Chrome Web Store.
1.2.0 is submitted and waiting on review, so the store serves 1.1.0 until it clears.
To use the zip instead: unzipkonode-chrome-1.2.0.zip, thenchrome://extensions→
Developer mode → Load unpacked. - Firefox —
konode-firefox-1.2.0.zip. Submitted to Firefox Add-ons and waiting on
review; this is the first Konode release with a Firefox build. Until the listing is live:
about:debugging#/runtime/this-firefox→ Load Temporary Add-on → pick the zip. A
temporary add-on is removed when Firefox restarts, so this is for trying it, not for
living on.
Upgrading
Nothing to do. Every device re-uploads each of its files once on the first sync after
updating, then settles down; if a sync had previously got stuck, updating clears that too.
Your other devices may report "an unusual deletion was blocked" if bookmarks you deleted a
while ago never managed to propagate — that is the safety net working, a restore point is
saved and nothing is lost.
Full Changelog: v1.1.0...v1.2.0
v1.1.0
v1.0.2
v1.0.1
v1.0.0
Full Changelog: https://github.com/konabe-studio/konode/commits/v1.0.0