Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Well imessage does the exact same thing. It doesn't seem to confuse the users. More basic protocols as a fallback mechanism can be a good idea, if you understand the risks (and of course, if you allow the recipient to use the better protocol!)

Signal always warned me very clearly if it was forced to send a message via SMS, and even pushed me to invite the recipient to Signal. It made sense to support it still, because it's the second most basic service in the Android world (after calls), and now that Signal doesn't offer it, it can't be the default service any longer.

Signal's task as I see it isn't just to protect your communication, but encourage widespread use of strong encryption so that you don't stand out for using it. For that, there are tradeoffs. I think being able to handle the forced insecure communication for the user, clearly marked as such, was a great tradeoff for the sake of wider adoption.



>Well imessage does the exact same thing. It doesn't seem to confuse the users.

What % of iPhone users do you think understand the difference between SMS, MMS and iMessage protocols? I bet most don't. But if iMessage had its own separate app, they would know it's an Apple-only protocol. And that would make them less likely to exclude non-iPhone users and more likely to use cross-platform alternatives. It's not like all iPhone are jerks, they're being mislead on how "texting" in the default iPhone app really works. That's what I meant by confusion.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: