right now i'm trying out Outline [1] which has an option for self hosting.
Outline also has an RPC-style API for the entire project btw, the documentation needs a little work but it's there: https://getoutline.com/developers
We're considering the self-hosted option too - that's the big draw.
* unlike Notion, it's one workspace per instance. makes sense, but worth noting as using workspaces as for organisational purposes won't work so well here.
* for personal instances, Slack doesn't make all that much sense. i see a PR for LDAP support on GitHub, so i will play around with that
* supports embeds just like Notion - paste the link and it just works. supports codepen, figma, gsuite, youtube and others. this was the feature that made me take notice of notion, so it's good to see it here.
* even better, the embed API seems pretty easily extensible, so the sky's the limit here. i can't wait to make some sweet dashboards based on entirely self-hosted data!
* no mobile app is a bit of a bummer, but the PWA experience works pretty well. considering i'll be authoring predominantly on desktop and only reading on iPhone, this isn't so much of a big deal for my use case
* no auto-save :(
* you can share a read-only, fully public link of any page you want. pretty damn cool.
all in all i'm pretty impressed. it seems pretty robust! i mean, it's definitely not as full-fat as Notion, but perhaps that's a good thing - and OSS means it's easily extensible for whatever you need to use it for. who knows which way my opinion will change after some more extensive use, but this definitely shows promise.
I certainly agree that that's the point, but such a system needs some potential usability affordances. For instance, a key stored in the browser rather than a password the user has to remember, and ideally a key synced between multiple devices controlled by the user so that the loss or failure of one device does not mean loss of the account.
For example, imagine having the browser generate an asymmetric key for the user, and making sure browsers store such keys (encrypted) in Firefox Sync or equivalent, so that the keys are safe even if the user moves to a new device or an existing device fails or gets lost.
https://francoisbest.com/posts/2020/password-reset-for-e2ee-...
https://1password.com/files/1Password-White-Paper.pdf
Don't work for Agile Bits, but have used 1P for a long time and couldn't live without it.
Currently everything happens client side, however we believe homomorphic encryption is at a level of sophistication that should support most users and their needs.
My guess is that all these apps are salivating over the data to be able to train their NLP models which they can sell to an acquirer. I can't wait for Obsidian or some other app to reach feature parity (including wide, stable platform support). Would happily pay $$$ per year for it.
That being said, having clear-text data would allow features like an API on publicly shared pages/blocks, to use Notion as a CMS. I have seen some attempts [1] at reverse-engineering their internal API, but an official one on a paid plan could be a nice addition.
[1] https://github.com/splitbee/notion-api-worker