New blog post: "Products vs Protocols: What Signal got right"
https://snikket.org/blog/products-vs-protocols/
This extended version of @mattj's recent #FOSDEM talk explores the thinking behind Snikket, and what #XMPP and #decentralized protocols can learn from #Signal's success.
@snikket_im @mattj
Is Snikket an alternative to Signal? I tested it a few days ago, and it seems to target team chats and other closed groups by requiring invites on the one hand and putting all people into the same room on the other hand.
Isn't @blabber the Signal alternative that uses XMPP as it provides a product with security by default, nice UI/UX and a free of cost server with easy signup.
I would like to see Snikket as a one-to-one messenger, but currently, this seems to be a non-goal.
@allo
Alternative? Yes. Clone? No.
We believe in a network of small, independent servers (federated, of course!). We believe people should use servers run by people they know and trust. Invites make signing up a group of trusted people to your service (e.g. family/friends/other group) quick and easy.
Team chat is not a goal right now. It requires different UI/UX and social considerations.
@mattj @blabber
@snikket_im
Your goals always sound like you want to provide an messenger, which is THE client for xmpp or at least one App that one can recommend to avoid talking about protocols instead of Apps (so it can be installed without first understanding the need to find an app for a protocol).
But your solution does provide something else (what you just described). I like your project, but I am confused by the difference between the goal stated in blog posts and so on and the actual project goal.