481 karma · joined October 28, 2013
This is good thing. Once everyone will be embarased by his history,
> We probably will stop caring about online privacy.
This would be bad, I would rather this to happen: "We probably will stop pretending of being perfect and become more honest."
I am actually glad they did it. This should make it harder for ponzi-like schemes to get traction, so hopefully, it will make price less volatile.
I was talking about implementation of Facebook messenger, or Google hangout (which does not use XMPP), not what is used internally for communication.
Also, at Facebook, messenger is most used product internally. IRC is still used, but not that much (depends on org, infra devs use IRC more than product devs). But IRC is still essential, in case of emergencies (where you don't want to use your own product, as it may be down).
Why? Facebook, google, slack are not using XMPP internally for chat products, because of technical reasons. They dropped XMPP gateway for mix of technical and strategic reasons. Instead of trying to be a warrior for technical correctness, XMPP foundation should rather seek feedback and try to make sure that developers integrating with XMPP will do everything correctly as easy as possible. Otherwise, more and more projects would be dropping XMPP support.
People wear rings all the time, application is painless, easy to change once compromised or if there is a new model, and provides same features. Chips would have advantage if they would provide better IO, but currently they don't.
But with servers in more locations, and possibly accounting for network topology (could be mined with traceroute?), accuracy could go quite up.
Let user to check which languages he is using (somewhere in settings) and then allow him to use them as he wish. Mix all selected languages into one, previous (or two previous word) should be enough to predict correct next word.