Package Details: boostnote 0.12.1-1

Git Clone URL: (read-only)
Package Base: boostnote
Description: Open source note-taking app for programmers
Upstream URL:
Keywords: electron productivity
Licenses: GPL3
Submitter: rokt33r
Maintainer: clone1612
Last Packager: clone1612
Votes: 55
Popularity: 1.198241
First Submitted: 2016-04-11 13:01
Last Updated: 2019-07-27 09:50

Pinned Comments

clone1612 commented on 2018-06-13 06:04

Just an FYI on certain warnings appearing during the installation:

  • Warning about optional dependencies -> Bug in npm ignoring the --no-optional flag (

  • Reference to $srcdir ... -> Again unwanted behaviour in npm which saves absolute paths in the package.json file ( These warnings can safely be ignored since package.json is not used after installation.

  • Security alerts -> Upstream issue, I'll try looking into it and fix things where possible

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

jcstryker commented on 2017-10-09 16:06


I am still getting a connection to on starting the app. Is this analytics related?

clone1612 commented on 2017-10-09 12:53

Fully removed analytics again. People keep having problems with it (e.g. and it's more privacy friendly this way. Much smaller package size is also a bonus.

clone1612 commented on 2017-08-10 15:45

If you have any problems with preferences being reset, please follow the instructions in This release contains a bug that will be fixed when they release a new version (in the coming days) but that post contains a work-around.

EDIT: Problems should be fixed with v0.8.14

clone1612 commented on 2017-07-29 07:12

Updated to v0.8.12, thanks for the advice @NicoHood. For now I've just set tracking to false by default, like you mentioned, while I look at a clean way of removing all analytics (since they changed a bit since my previous removal patch). Should be possible but do not worry even without the removal tracking is disabled by default :)

EDIT: Removed amazon analytics once again, turned out to be easier then first expected :)
If any issues arise feel free to say so and I will look into them.

NicoHood commented on 2017-07-22 06:57

Thanks for the patch!
For the next version:

in the next version you could patch browser/main/lib/ConfigManager.js to set the tracking to false by default. I think in long term it would be complicated to fully remove it. But if you can fully remove it, that'd be better :)

clone1612 commented on 2017-07-20 06:58

@NicoHood More details in this pull request:

Pushed a new package release. Found a way around the npm issue so moved back to good old npm. Also removed all of their amazon analytics, thereby also fixing the problem mentioned by @vczm. So no more analytics present which also had a great effect on the package size.

NicoHood commented on 2017-07-20 05:38

They added spy functions to boostnote? Is there any details about that? It seems I will not use Boostnote anymore with those functions.

@clone1612: We can change the source code, its GPL3. No need to ask any maker.

clone1612 commented on 2017-07-19 20:50

@vczm That's not an error I can fix. They have added amazon analytics (which are those requests) but they only add the correct key when they package for distribution (so not provided in the source code used to build the package). Unless they provide their analytics id the requests (send by the program, not something I added) will fail.

In theory the analytics could be removed but that would be really changing the source code and I have no idea if the makers would agree to that.

EDIT: Trying to get in touch with them, will see how it goes. Even if its fixed though the requests will still be send (it's their analytics) however they will no longer fail. But working on a solution.

vczm commented on 2017-07-19 20:32

Still not fixed:
Why do you need to send these requests?

clone1612 commented on 2017-07-19 19:04

@NicoHood I received a bug report that installations were failing due to an npm error. Failures could be reproduced on my two systems, both with a normal attempt to install and a clean chroot. Sadly I had a bit less time in the past days so this is a (dirty) temporary fix while I look for a definitive solution to the issue, which seems to have appeared with a recent npm update. Will look into that and move back to npm if a fix is found, but for now the focus was on making it possible to install once again. Sorry for the inconvenience.