In the future, if you plan to add sync, consider reimplementing Joplin sync algorithm
That would give you tens of thousands of passionate users, dedicated FOSS server as well as webdav/s3/dropbox/onedrive client sync ability, webclipper and a lot of support to navigate future issues/roadmap
If you ever decide to do that, there’s even a plan to repackage the algorithm as a standalone library
I’ll just leave here the response from obsidian. If you can extract truthful reason from this corp double speak, please share
deleted by creator
Would be interested in more detailed followup about the search. Anything in particular stands out?
Project: Joplin joplinapp.org !joplinapp@sopuli.xyz
What it does right: Focus on user experience by aligning aims of product with aim of users.
Everything it does is foss, however its main revenue achieving product (cloud sync target) is focused on convenience rather than vendor lock-in. So it incentivizes the project to cater to its users.
What’s so unique about it: due to lack of monetary incentive a lot of oss projects simply forget about the user and serve mostly to themselves. They fail to listen to feedback because listening to feedback means loss of resources rather than gaining them. As a result many critical bugs are unfixed for decades and UI is so dated no new users want to use the product.
TLDR: don’t forget to create revenue generating module along with the main foss product
Classy!
Bloody banking apps. I’m sick of them not exposing any API to make third party apps.
To quote Linus Torvalds “**** ***, Nvidia”
TiddlyWiki was infact an inspiration for Obsidian when it just started