messaging_candidates:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| messaging_candidates:start [2015/07/16 01:32] – [Recommendation] mithat | messaging_candidates:start [2017/06/30 18:14] (current) – [Telegram Messenger] mithat | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Messaging Candidates ====== | ====== Messaging Candidates ====== | ||
| - | This is a summary of candidates for a cross-platform, | + | This is a summary of candidates for a cross-platform, |
| ===== Requirements ===== | ===== Requirements ===== | ||
| - | The starting point is the [[https:// | + | The starting point in candidate selection |
| In addition, the ideal candidate will: | In addition, the ideal candidate will: | ||
| Line 16: | Line 16: | ||
| * Offer privacy and security protections by default. | * Offer privacy and security protections by default. | ||
| * Feel like it's not going to abandoned. | * Feel like it's not going to abandoned. | ||
| + | * Not require a phone number create an account. | ||
| * Not require your phone number to be divulged to everyone with whom you communicate. | * Not require your phone number to be divulged to everyone with whom you communicate. | ||
| Line 58: | Line 59: | ||
| In-browser tool. Not really what we are after. | In-browser tool. Not really what we are after. | ||
| - | ==== Telegram ==== | + | ==== Telegram |
| + | [[https:// | ||
| * //Be federated with an open source server.// The server is currently closed source. Federated open source services appear to be planned. From the [[https:// | * //Be federated with an open source server.// The server is currently closed source. Federated open source services appear to be planned. From the [[https:// | ||
| Line 65: | Line 67: | ||
| > All code will be released eventually. We started with the most useful parts -- a well-documented API that allows developers to build new Telegram apps, and open source clients that can be verified by security specialists. | > All code will be released eventually. We started with the most useful parts -- a well-documented API that allows developers to build new Telegram apps, and open source clients that can be verified by security specialists. | ||
| - | * //Offer privacy and security protections by default.// For the highest security (i.e., full marks from EFF), secret chats can be used. See the [[https:// | + | * //Offer privacy and security protections by default.// For the highest security (i.e., full marks from EFF), secret chats can be used. See the [[https:// |
| - | * //Not require your phone number to be divulged to everyone with whom you communicate.// | + | * //Not require a phone number to create an account.// The only way to open a Telegram account is by using an SMS-enabled phone number. |
| + | * //Not require your phone number to be divulged to everyone with whom you communicate.// | ||
| Additional vetting of the founders' | Additional vetting of the founders' | ||
| Line 73: | Line 76: | ||
| Open Whisper Systems' | Open Whisper Systems' | ||
| - | ===== Recommendation ===== | + | ==== Tox ==== |
| + | Relative newcomer [[https:// | ||
| - | Right now, I can't honestly recommend any of the preceding for general use. Telegram comes close, but its use of your phone number as effectively the only source for identification while fine for an SMS replacement is not acceptable for a general text messaging platform. | + | ===== Recommendation ===== |
| + | Tox needs a more complete evaluation, but on the surface it is encouraging. Telegram comes close to a recommendation, | ||
messaging_candidates/start.1437010376.txt.gz · Last modified: 2015/07/16 01:32 by mithat