Skip to content

v1.2.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Aug 21:12
· 101 commits to main since this release
v1.2.1
ffa75b8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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: unzip konode-chrome-1.2.1.zip, then chrome://extensions →
    Developer mode → Load unpacked.
  • Firefox and Waterfox:
    Firefox Add-ons, which is live at
    1.2.1. konode-firefox-1.2.1.zip is here for building and review, not for daily use: a
    temporary add-on loaded through about:debugging is 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

Assets 4
Loading