There's no point in offering users self hosting if you are going to throw them into a fire by doing so. Notesnook is rapidly evolving and changing, and hoping for self hosted users to keep up is impractical. Instead, we want to first stabilize the backend, and then think about self hosting.
After v3, our primary focus will be on self hosting and getting an audit done.
> Notesnook is rapidly evolving and changing, and hoping for self hosted users to keep up is impractical
I don't know...does self-host equal slow changes? For me that's part of being a self-hoster, I have to keep the softwares up-to-date, and I actually appreciate if updates are frequent.
> After v3, our primary focus will be on self hosting
Sounds good, good luck on further development, if I ever see a self-hosting guide I'll check y'all out ;)
Not slow changes. Offering self hosted officially means that we have to be aware of users who are self hosting before we make any drastic changes, writing migrating guides, and giving some sort of support. All that has an impact on productivity.
build an export and import and offer it with docker and I'm on board. I dont care much If I have to take a few extra steps... but I'm done hosting my private stuff in the cloud. Self host is the future.
yes, it's a pwa so offline first. it uses yjs with webrtc for p2p generically and the "last mile" will be a "light" electron app that you can use via webrtc to store files .
no technical server, so really the only infrastructure is the signalling, and it's straight forward to scale that.
might still be a niche but it serves my day job needs. field work and reporting asynchronous is a pain.
