@matigo I probably should have said something about being part of a shared experience with other people, but, I should be in bed. :P
@hybotics of course, but they want to leverage the existing Signal userbase.
// @matigo @thrrgilag
@thrrgilag the main reason for that: email cannot easily evolve. It's basically stuck in the 1970s.
Note the same thing can be said for SMS and the PSTN. They are as ubiquitous, decentralized, and unable to evolve at anything faster than a glacial pace.
// @matigo @larand
@thrrgilag it's a problem we've tried to solve for decades. The only thing that's come close to achieving mass federation is email.
// @matigo
@thrrgilag Remember that sharing the code under an open source license doesn't mean someone doesn't own the code and can't make decisions about what gets committed to the official code branch.
The real issue (as I see it) has nothing to do with Open Source, but rather allowing those who use forks of the official Signal clients to connect to Signal-maintained servers. As that's a service Open Whisper Systems maintains irrespective of the code that runs it, they are well within their rights to restrict who can connect to it with what clients.
// @matigo
@thrrgilag I find myself agree with Moxie on this. Federation hasn't worked all that well for these sorts of clients and adds significant UX barriers.
// @matigo
@kdfrawg we all have a role to play in how things got to where they are now.
// @skematica @larand