Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

I'd like share a view on where the project should be headed. In short, it should be simpler and owned by contributors.

  • No more Dnote Pro. The freemium model distracts from the core mission of creating open source knowledge base software. To get started, I've removed the mention of Dnote Pro and open-sourced the end-to-end test (Add sync test #678).
  • No more CLA. The contributors should own the code.
  • More permissive license. GPL is too restrictive.
  • Replace Postgres with SQLite. We should be able to download and run a binary to run the server.
  • Simplify.

Please share your feedback.

You must be logged in to vote

Replies: 3 comments · 4 replies

Comment options

Hi @sungwoncho !
I'm glad to see dnote is still alive ;)
Dnote can become a great tool I guess. Thank you for releasing dnote (cli and back) under a free license 🙏

I hope you're not too disappointed with the paid version; in fact, I think it's a good idea to keep a paid version like https://miniflux.app/ => https://miniflux.app/hosting.html

You must be logged in to vote
0 replies
Comment options

Thanks @fredix. By the way, any preferences for the license that's more permissive?

You must be logged in to vote
4 replies
@fredix
Comment options

I think that AGPLv3 is a good license.
BTW, I have a suggest about a feature. Indeed I'm a bit afraid to store all my knowledge in a database. What about a possibly corruption of the sqlite file ?
So, it should be great to keep all markdown files and use sqlite to find an item. dnote could sync the sqlite file and markdown files from a directory ?
sqlite would not store the file, but just the name/shasum/whatever usefull from the markdown.
what do you think about ?

@sungwoncho
Comment options

sungwoncho Oct 20, 2025
Maintainer Author

You mean storing data as files, but maintaining indices in SQLite for searching, etc? Sounds like we can get best of both worlds--files and SQLite. A trade-off is keeping them in sync would add complexity. Maybe we can have a tool that translates SQLite notes into files. What is your thought?

AGPL is definitely solid but I wonder if a more permissive license might help adoption and long-term success. Apache or MIT, probably.

@fredix
Comment options

A trade-off is keeping them in sync would add complexity. Maybe we can have a tool that translates SQLite notes into files. What is your thought?

Sure, but if the database file is corrupted I suppose the user would not be able to export his datas to files ?
I suggest you this process:
when the user write a markdown file with any editor, the tmp file is stored in sqlite and in a data directory. Same process when he update any note.
On dnote sync, the server update his database and export all notes in files.
So in case of a corrupted database, the server or the client can rebuilt it with an import from the data directory.

AGPL is definitely solid but I wonder if a more permissive license might help adoption and long-term success. Apache or MIT, probably.

Depend what you want. With MIT I can use your code in a propritary software.

@sungwoncho
Comment options

sungwoncho Nov 1, 2025
Maintainer Author

Thanks for the interesting idea. Let's use it as data point for the future direction.

Comment options

sungwoncho
Nov 1, 2025
Maintainer Author

Dnote server v3.0.0 is released with SQLite as database. Dnote is now released under Apache 2.0 (previously AGPLv3 + GPLv3). Contributor license agreement is removed. Contributors should own the code.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.