Please no crossposting! Re: Information regarding theMessaging Support in OpenMoko

Paul Jimenez pj at
Thu Feb 1 16:22:56 CET 2007

I think a good Jabber client could totally supplant MMS - it support
file transfers, which is all MMS really does (I think), as well as
things MMS never dreamed of like encryption and presence and etc.
Putting a good mobile-UI on, say, Psi or one of the other open source
Jabber clients shouldn't be too difficult. Unless there's already one
that I don't know about?

Another feature could actually be an SMS-to-Jabber gateway that runs
on your phone, so as long as your phone has power (and permission to
get on the net, etc) your SMSs will get gatewayed to Jabber so you don't
miss them if you happen to leave your phone at home.


On Thursday, Feb 1, 2007, Sean Moss-Pultz writes:
>On 2/1/07 4:30 AM, "David Schlesinger" <David.Schlesinger at>
>>> Also, who uses MMS?
>> Only pretty much the majority of actual cellphone users in Europe, based on
>> the market research and carrier requirements I've read...
>IMHO, only because nobody has given us anything better. We're trying to do
>that. So I asked the guys to ignore MMS for the now. If this is an issue
>I'll put resources on this in the future. Right now, I'd much prefer to see
>solutions that use GPRS such an IM / Email / ...
>>> Seems like the typical user would just email
>>> and attach media and/or just s/ftp
>> Typical _Linux_ user, maybe. This is the sort of thing which (in my view)
>> represents something of a disconnect between the goals of "having as open a
>> phone as possible" and "selling a lot of phones"...
>You might be right. But I personally feel that MMS is fundamentally flawed.
>Costs aside, it's just not the way I think media should be transferred. The
>benefits are just too low for the end user. We're trying to fix this.
>Really guys, we're trying to rethink lots of things with OpenMoko. I don't
>want to do the same things just running under FOSS. We'd be missing out on a
>huge invitation to innovate both as a company and a community. Why not use
>the flexibility and rethink how we want these devices to work -- as end
>users -- not just for geeks but for everyone? I'm not saying we'll get
>things right the first time. Just that we're going to try our best ;-)
>_This_ opportunity is what makes me excited about OpenMoko. Not (simply) the
>fact that it's FOSS based.

More information about the community mailing list