

If you want notes “sometimes on the web, sometimes local first”, and possibly more than just notes (with the tools to extend into an actual knowledge base), you might be better served by https://triliumnotes.org/


If you want notes “sometimes on the web, sometimes local first”, and possibly more than just notes (with the tools to extend into an actual knowledge base), you might be better served by https://triliumnotes.org/


I’m holding off on Fluxer until they decide how they’re going to implement federation
Seems wise. They seem competent in the front-end/client space and complete amateurs in the (difficult) protocol space. There is no example of successful tech (that I know of) that successfully added federation/P2P after the fact. It’s not an afterthought, it probably won’t ever happen.


Don’t do Element, Matrix is a nightmare (and a significant commitment) to self host. Other servers (recently, continuwuity) are a bit better on that front, but then you run into compatibility issues and edge cases as a forever second-tier citizen.
My advice is to just go with XMPP and ejabberd, and you will find clients for all kinds of usages and people (a free-er WhatsApp takes you to Conversations/Quicksy/Cheogram/Monocles/Monal, a better banquet/IRC-style rooms takes you to gajim/fluux, social networking and group calling takes you to Movim, etc).
Personally my needs are covered by Monocles on Android, Gajim on the PC, and Movim on occasions. Using multiple clients around the same protocol and account is a strength, not a weakness.


To add to the collection of chat apps enabling that, there is XMPP, too: https://f-droid.org/en/packages/de.monocles.chat/
It’s not as dramatic as GP makes it, but Matrix had been at the prototyping stage and at figuring out its core protocol and state resolution algorithm for more than a decade now, it’s pretty ridiculous in itself.


Isn’t that the premise of the “$4 ubuntu over droplet deployment” option?
Instead of having Secluso-Deploy ssh into some cloud box and prep it up with the server-side software, why not have a container deployment option as well? I get that you want to ensure that the server is publicly reachable for the mobile clients to work on the go, but ultimately (and in all honesty) at this point, that should be a user concern/choice (those more advanced users may be peculiar about running behind tailscale, a home-VPN, a port-routing config, …).
Needless to say, most people here might find it easier to work with containers and build trust in the project by having it run in an isolated environment with limited permissions than blindly trusting that the code is what it says it is and not quietly running a botnet at digitalocean with their PII attached.
How does that compare to wallabag? (Does it?)