One of the apps which I like to use under Android, is the Evernote Web-clipper. But because I am not using Windows anymore, I no longer have the official Windows client application for this service. Yet, I have a paid-for Premium subscription to Evernote. Therefore, I am interested in synchronizing my clippings with my desktop computer, even though I’m using Linux.
One solution which exists for people like me, is the NixNote2 (Linux) application, which is essentially a clone of the Evernote client application. But before Linux users go ahead to install and use this program, there is a recent fact which they need to be aware of. Under Debian / Stretch, aka Debian 9, the version which we may install from the package manager, is currently only version 2.0~beta11-1. This version is badly broken, and trying to use it could lead to some confusion, about why it malfunctions.
The behaviour might already be familiar to some other, unfortunate Linux users: When we first authorize it to sync with our account, it stores its token but only syncs once. After that, attempts to sync fail, and, the (Qt5) System Tray Icon misbehaves badly.
From what I heard this version is broken because the package maintainer for it has failed to maintain the code properly. Maybe he has moved on to different projects? But if he has, the defective version should not really be in the repositories anymore. And so a different developer has come forward, who will allow people to download his up-to-date version, that seems to work fine. This up-to-date version is available as an Appimage.
I suppose that a type of question may arise, as to why software like this needs to be maintained, or, why it stops working. And in this case, the best answer I can decipher is that Evernote allows third-party client programs to connect, but tightens the protocol with which any client – mainly their own – needs to communicate with their server, either to improve security, to add features, or both.
Situations like this can even lead to some feelings of persecution, which may be stronger in the manufacturers of third-party devices or the programmers of third-party client apps, than they need to be for users. But what might just be happening is the provider trying to improve their infrastructure, and perhaps also, being a bit sluggish in communicating changes they make to the protocol to independent developers and users.
What users need to know, is to start with a healthy client app, before searching for other answers as to why, perhaps, the sync is malfunctioning.