On 10/24/07, <b class="gmail_sendername">Joshua Layne</b> <<a href="mailto:joshua@willowisp.net">joshua@willowisp.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Sorry if I participated in the thread-jacking mentioned above, but I<br>fundamentally disagree with your premise above. I should not have to<br>know what protocol I am using to contact my friends - I should be able<br>
to configure it and it should just work, negotitating protocols as<br>necessary.<br>text-based messaging = texting + IMing + emailing<br>emailing is asynchronous<br>IMing is synchronous (usually)<br>texting is somewhere in between.
<br><br>it's fine to target an SMS-only app, but I personally think it would be<br>better if it evolved to unified messaging.<br><br>Regards,<br>Josh<br><br></blockquote></div><br><br>We all love thread jacking! <br>
<br>Here are a few quick points in considering "unified" messaging system.<br>1- SMS is one paid add-on. Data service (for IM) is a separate paid add-on. Many people have one, or the other - not nearly as many have both.
<br>2- SMS has no online status. IM is all about status.<br>3- SMS is not necessarily real time. IM is generally real time.<br>4- SMS is length limited. IM is not.<br>5- I need the ability to customize on a per contact basis, and switch services quickly. (EX: Which service is default, how it "fails over" to the next service in line, what the order of services are. Also - If I IM someone and get back an auto reply saying they are out, I need to be able to SMS them in as few steps as possible.)
<br><br>Thats a few key items I thought of off hand. I think they are important to discuss how to "resolve" these issues. While Yahoo and AIM work in much the same fashion as one another, IM and SMS are completely different designs. That all being said - I'd love to see Pidgin w/ SMS powers on the OpenMoko (or similar style software)
<br><br>-Jon<br>