Perfect, now you just have to wrap your program inside a debugger in production!
Perfect, now you just have to wrap your program inside a debugger in production!
Yep, that’s the gist of it. In order to change the license from the GPL, they’d need the permission of all of the copyright holders who’ve contributed code under the GPL to the project. After a few months have passed, this basically makes it impossible (or at least extremely difficult) since at least one person (and likely many people) will say no.
They have also funded a lot of improvements to XMPP clients and servers.
I’d like to second Snikket - it’s designed for this use case and is very simple to set up.
If you’d rather not use Snikket, check out these recommendations for clients and servers.
Hope it works for you! Feel free to reach out if you have any questions.
Different strokes for different folks! I’ve been fortunate enough that many of my family and friends have been happy enough to follow me.
But I don’t disagree with you, Signal has a much more recognisable brand and better user experience. These are things that we need to improve if we’re going to get anywhere near the level of adoption Signal has.
How I Got a Truly Anonymous XMPP Account:
Sorry, it’s a cheap joke, but it still baffles me that Signal requires a phone number, so I felt I had to post it :)
Of course, this is not XMPP-specific either, just my protocol of choice, there are many other open alternatives that also offer such functionality.
I’ve had good fortune converting some family and friends to use XMPP.
People always mention fragmentation, and while there is some truth to it, it can be massively minimised by choosing blessed clients and servers for them to use.
In my case, I run my own server, and thoroughly test the clients (especially the onboarding flow) that I expect them to use, so that any question they have, I can help them out with quickly. Since we’re all on identically configured servers, it minimises one whole class of incompatibilities.
There is still unfortunately a bit of a usability gap compared to Signal - particularly on the iOS clients. But they have come a long way and are consistently improving.
It’s not perfect yet, but it’s much, much better than the old days.
OMEMO is supported by every major client, and they interoperate successfully. Unfortunately, most clients are stuck with an older version of the OMEMO spec. It’s not ideal, but it doesn’t cause any practical issue, unless you use Kaidan or UWPX, which only support the latest version.
All popular clients and servers support retrieving chat history now too.
In practice, I’ve been using it for several months to chat with friends and family, and haven’t had any issues.