<div><div><br>Hi, i'll add my 2 cents :)<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Then again, while XMPP is quite nice for normal usage on the net, maybe we
<br>need a different protocol, namely one that is VERY bandwidth efficient (XML<br>is not really famous for that, a binary protocol could potentially do much<br>better) to keep GPRS costs low?</blockquote><div><br>The best would be:
<br>- using a plain text protocol : irc would be great, but prevents further extension (webcam over ip or voip), so SIP might be better<br>- using a compressive transport layer (tunneling into ssh, with compression ?).<br>
<br>My opinion is, if we really want to turn the OpenMoko platform to it's maximum extend, we'll have to associate it with a server-side component (running all the time, such as a WRT or NSLU2 device), a multiprotocol IM gateway, a remote storage feature (sshfs?), an imap webserver, a web gateway... Everything tunneled into a secure-as-possible connection.
<br></div></div><br>Example:<br><a href="http://www.bitlbee.org/main.php/news.html">http://www.bitlbee.org/main.php/news.html</a> for IRC (server side)<br>