107 karma · joined July 7, 2016
You are describing what should be the goals in your opinion, not the one of Signal's developers.
Having something that works to show (Signal), was a big point to sell to those, closed and already used by many people, systems; so having a non federated Signal means they can iterate more often and change things how they more or less want.
In the long run federated protocols and servers demonstrated their resilience regarding third parties and time, see irc for example.
Probably Signal is just a reference implementation, the big deal is implementing Signal protocol in different systems (whatsapp, allo, fb messenger..).
Having said that, I would be happier to not give my phone number for registration, and contact discovery but this is today a user interface well understood and accepted outside geek communities that's hard to eradicate.
it's 20 years that people suggest a cool new way to deal with email addresses, I don't even mind listening anymore! :)
I feel this article is advertising their book, maybe the only point to consider is the somewhat broken status of pip that have to deals with system libraries dependencies, but whatever, I still use pip every day and with multiple production deploys.
Is there some good comment about python docs, packaging management, that isn't so much a rant?