What I immediately noticed looking at the README, is that the communication is centered around you and your values, rather than on the end-user:
You mention why you created it, not what it enables the user to do. You use Linux-lingo, like “free (speech and beer)” which many users are unfamiliar with and don’t know why they should care. Your installation instructions make it hard for users to pick which one they should choose. There are no Mac binaries, but Macs are wide-spread among developers. Windows binaries mention “x64”, which is very technical and might scare users away.
The Ubuntu screenshots make it look like “Linux only”. You could replace it with a Windows or Mac screenshot, to get people to understand it works on their platform.
You could still keep this technical (and potentially alienating) language in your documentation, but simplifying the README to make it easier for the 90% of your potential audience could make it more popular.
You mentioned in this thread that some people don’t want Electron. That’s true, and it’s a great USP for those that require it, but personally I would avoid assuming that it’s the USP that convinces the masses.
(Regarding Mac, I unfortunately don't have a Mac and neither does anyone who I know well enough to ask to borrow theirs, though someone did in fact contribute homebrew-based build scripts that supposedly work at some point. I just have no idea how to package the result to make it easy to install.)
- You don't want to give more priority to non-Linux users
- GTK feels terrible on those other platforms
- You don't believe those who care about licensing issues would use it
- You cannot build releases or installers for Mac
The first thing that comes to mind on reading your response is that the non-Linux users are a market you are not really interested in - and even if they were they are not a market you can effectively serve (installers, updates, issues).
You should consider formally abandoning official support for non-Linux, as in reality you don't currently have actual support for them anyway. Be honest, cut your losses, and choose your customers. Cross-platform is not a benefit if it is unsustainable.
To nitpick a little, I also didn't say I don't think that those who care about licensing issues would use [the Windows build]; rather, I think that those who don't care about licensing issues and are on Windows would not use it, because there is a Windows-only product that is closed-source which I am unlikely to be able to compete with on that ground.
I'm not really advertising Mac support beyond having some files merged from people who did get it to work (https://github.com/blackhole89/notekit/blob/master/screensho...).
Replace? I'm not Linux user but this sounds strange to me. He did native GTK app and he should not be considering Linux users?
In regard to getting the word out, it depends on the kind of person you want to reach. If you really want to reach a "general" public, the sibling's comments sound useful, in particular binary availability.
In particular for Windows. I've clicked on the link, ended up on the GH workflows page, looked around quickly, didn't see where to grab the binary and went on my way being happy that I'm on Arch Linux and there's a package in the AUR.
I don't know if I want to reach what you would call the "general public" (at least not until the program is quite a bit more polished than it is now), but I'd certainly want to reach typical Linux-using HN posters who are interested in Markdown notetaking, and the circumstance that this subthread played out as it did implies I haven't yet done so.
Hope your approach gets more widespread !
Who's good to only write stuff on a computer and on that alone?
Best solution to me so far is to just use Wiki.js.