git-sync VS notes

For those that want to crosslink anything and everything I suggest Logseq[1]. Its journal and graph view are fantastic. And it has many iseful plugins. I use it along with git-sync [2] and syncthing [3] now I can sync the notes across my work, personal desktops and my mobile.

[1] http://logseq.com/

[2] https://github.com/simonthum/git-sync

[3] https://syncthing.net/

I’m using almost the same approach to automatically sync my vault between my devices (Git, Termux, Tasker). The main difference is, that I'm using the great git-sync script by Simon Thum for syncing. In the past I had some problems with a simple script that included only git pull, commit and push. With the git-sync script I now have less problems. Nevertheless you can't avoid to have conflicts if you or plugins edit the same files at the same time. I have documented my setup in this GitHub repository.

Before I came to macos I was using stow to keep all my dotfiles in one place. Then they were being copied nightly to a private github repo with git-sync which, as you know, is nice for versioning. I also had the central dotfile folder in a syncthing folder, so all my configs were always the same on any machine I used. If I update anything on one computer, it's changed on the other automatically. I also have a VPS that's participating, and somewhat acting as an always-on central sync server to keep everything recent.

I use vim and git with git-sync addon (I think it's this one: https://github.com/simonthum/git-sync). I don't care too much about mobile, but I also have configured vim via Termux on my Android phone.

I use git bare, it works great: syncs only the files I explicitly add, allows to place git repos as children of $HOME, and I get to sync changes with a single command: you can use an alias to rebase, commit and push or something like git-sync.

This is not enough if you want to update from multiple machines. Again u/blevlabs I really suggest you use something like https://github.com/simonthum/git-sync to do this, as it gracefully handles a lot of the corner cases that you might want to implement with something like this.

Thanks! I'm not 100% sure about this, still hearing feedback from people on both ends. Some reasons for the switch would be:

1. File versioning

2. Easier self-hosted syncing

3. Better data portability (although we already support exporting to .txt)

I would love to hear counterpoints. Currently, SQLite works pretty well, and our custom database is pretty simple (plus, our database code is also open source[1]).

[1] https://github.com/nuttyartist/notes/blob/master/src/dbmanag....

Plume is actually based on my open source note-taking app Notes[1]. You can already get it on Flathub, Snap Store etc. Notes uses just a simple plain text editor while Plume has a completely revamped block editor that I built from scratch. That parts of Notes used in Plume will remain open source (per the MPL license) but the rest of the code will be closed source. At least for the time being.

[1] https://github.com/nuttyartist/notes

Plume is built on top of my open source note-taking app Notes[1]. Since Plume is based on Notes, I'll of course comply with the MPL license and release all existing files that were changed (and must stay MPL licensed).

But I recently discussed my reasoning to go close-source with Plume[2]. I've been working night and day (every day) converting 4 cups of coffee into code for the last 4.5 months to create Plume. I don't want to risk not being rewarded sufficiently for it. But, I'm 99% sure that I'll either open source the core block editor or the entire app in the future.

[1] https://github.com/nuttyartist/notes

[2] https://news.ycombinator.com/item?id=38584960

2. Each note is just a simple plaintext in the underlying data (although currently stored in a database, but in a future update we'll convert the database to an arbitrary folder).

So you can create beautiful and advanced notes, easy. In a non-proprietary format (when that future update arrives). All while using a resource efficient and fast software that is cross-platform.

[1] https://www.get-plume.com/

[2] https://www.get-notes.com/

My Noets app[1] editor is built on top of the Markdown syntax of QOwnNotes.

My new app Plume[2] is built on top of Notes but features an advanced block editor and a new design.

[1] https://www.get-notes.com/

[2] https://www.get-plume.com/

Indeed, I want this feature badly myself to create wikis and such. There's an open issue[1]. We'll definitely implement that some day.

[1] https://github.com/nuttyartist/notes/issues/431

I mostly disagree. Like you said, Qt is the best native GUI toolkit available today. And that is a hard achievement. There are many tradeoffs (some you pointed out) but the open source community seems to find a way around those limitations. There are thousands of open source libraries you can plug-in into your Qt app to overcome many of its limitations (although some remain, like how can't we still not easily change caret/cursor color of QTextEdit??).

Unlike you, I like the direction where Qt is taking. I think QML and Qt Quick are great. I just implemented a feature in my note-taking app that turns Markdown text into Kanban board using QML and the experience has been great (https://github.com/nuttyartist/notes/pull/574). I'm planning to continue transition from QWidgets to QML/Qt Quick.

I do worry of the continuous friction with open source development and hate the online installers as well. I can recommend this useful tool https://github.com/miurahr/aqtinstall that allows you to easily download prebuilt Qt binaries. I hope they can revert their approach on that.

I beg to differ, QML is great. I'm implementing a feature that converts all tasks in Markdown editor to a Kanban view (written in QML) and it's been so easy to do. Work in progress GIF here: https://imgur.com/a/sZNHnp6

And it's even crazier that most of it compiles to C++. It's so fast to develop with it, and runs so fast.

BTW, source code here: https://github.com/nuttyartist/notes/pull/574