I find the notification showing up each time I restart Zettlr a bit annoying: "You got the newest version of Zettlr".
I'd be fine with this message showing up, but only if there are actual updates. Even then, only one message would do. I understand that you might be concerned that users actually update the software, but making it possible to opt out of these notification would make the experience less intrusive, in my opinion.
If keeping users in the loop on new versions is important, you shouldn't remove the message completely, but as suggested, only show it when new versions exist. I'd argue that it's easier to miss _actual_ update notifications, if there's "you're up-to-date" prompts each time you start the app.

You are right that I want to "force" people to update, because I cannot maintain more than one single version of the app at one time, a lot of users (who are seldomly on GitHub) are pretty lazy when it comes to updating anything, and as Zettlr is Open Source either way there's only little cost in updating (apart from edge cases in big companies, etc).
As many people wanted to get rid of this, I have given it thought myself, and here's my proposal:
I want to make it less obtrusive, but still in a way that tells the user "Hey folk, you _do_ have internet, and hence you could now download the application, so DO IT!"
Thanks Nathan. Great to hear that you're considering some options for this. There's also the option to implement periodic checks and a dialog that comes up every X days/weeks. That could be a good middle-ground where everyone wins: you get people to update and people get to not see this message at all, until next check according to set time period occur.
There's also the option to implement periodic checks and a dialog that comes up every X days/weeks. That could be a good middle-ground where everyone wins:
I think I'd rather have users see that there's an update available immediately. What if it's a critical security issue and malicious http content could (hypothetically) be run in Zettlr and do things on the local machine?
I do see a use case for being able to disable the notification altogether for two purposes, though:
In saying that, I'd rather that the option to disable this notification altogether be hidden, if implemented at all, rather than easily changed through the UI, saving users from themselves.
I like your suggestion, Nathan - It's definitely an improvement on the current behaviour, and a notification that only appears when there's a new version is less likely to be ignored than one that's there at every startup!
I do see a use case for being able to disable the notification altogether for two purposes, though:
Yeah, I was planning to implement something where users could create a certain file (or something like this) in the Zettlr settings directory, which, if present, disables the update check.
Sooo, everyone: It has been done! Two full work-days and about 1.000 lines of code as well as approximately two heart attacks later, the update check has been changed:
It will never get easier than this, at least if I want to retain my sanity.
P.S.: Anybody interested in looking at the strings and implement the translations? I'm through with this sh** for now and will now have a beer.
P.P.S.: Yes, I tend to overstretch the issues at hand, but prove me that it's not good once I publish the second alpha 😎
Most helpful comment
Sooo, everyone: It has been done! Two full work-days and about 1.000 lines of code as well as approximately two heart attacks later, the update check has been changed:
It will never get easier than this, at least if I want to retain my sanity.
P.S.: Anybody interested in looking at the strings and implement the translations? I'm through with this sh** for now and will now have a beer.
P.P.S.: Yes, I tend to overstretch the issues at hand, but prove me that it's not good once I publish the second alpha 😎