[Yetanfou]

Telegram is not connected to Facebook while Whatsapp is. This makes Whatsapp a no-go for many people, me being one of them. While Telegram's "Russian roots" seem to cause others to doubt about its trustworthiness I don't see this as a problem. From what I gather, Pavel Durov (the man behind Telegram, former founder of VKontakte) is not on friendly terms with the current Russian regime so it would take a rather elaborate conspiracy theory to have him collude with the Kremlin.

Apart from that Telegram is fast, reliable and flexible and it treats Linux as a first-class citizen - maybe partly due to its Russian roots?

So, Telegram. Before it came around I used my own XMPP-server with diverse clients but Telegram has the advantage of being much more accessible to those less computer-savvy. I still have this server and can switch back to it any time I want but for now I'm happy with Telegram.

[majewsky]

> So, Telegram. Before it came around I used my own XMPP-server with diverse clients but Telegram has the advantage of being much more accessible to those less computer-savvy.

Is this still true now that we have <https://conversations.im/>? Most people use messengers only on their phones, anyway.

[Yetanfou]

It is. My father loathes mobile devices (or rather the stranglehold they seem to have on some people) but he has no qualms against using a PC. I converse with him daily through Telegram. My mother uses Telegram as well, on both her mobile as well as a tablet and her PC.

[deno]

There’s plenty of nice XMPP clients for desktop, though. I do agree, however, that there is a void to be filled by an XMPP client with good discovery.

The latency and battery problems everyone was blaming are solved now. The missing piece is this:

A way to provide XMPP service for any address, in particular gmail addresses, without both touching any DNS config and without any support from whoever controls the domain (RIP Google Talk).

Basically from UX perspective:

1) User downloads an app (mobile or desktop).

2) User confirms email address via either email confirmation (it’s good enough for SSL, so…) or OAuth flow

3) That’s it.

4) Bonus: For OAuth flow user has prepopulated address book.

Behind the scenes at step 2 a unique ID is associated with the email address. Then other clients resolve this via something, DHT, blockchain, whatever.

This introduces some trusted oracle that assists in discovery, but keeps everything else decentralized.

Build this and it can certainly compete with Telegrams of this world.

Unfortunately, I don’t think Keybase can be compatible by itself with email or phone № proofs. Perhaps if they explicitly add support for oracles, that would be cool.

[skinnymuch]

What's the URL meant for. It 404s

[aw3c2]

https://conversations.im/ obviously

[majewsky]

Gah. I enclosed it in <> explicitly to avoid the dot becoming part of the URL. Guess that HN doesn't know about the convention of using <> as URL delimiters.