View Single Post
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#2
Thanks for another great issue. However I do have a couple of objections to editorial comments:

Given that Google provides the most used Jabber servers on the planet, this is likely to be of technical interest only
(Disclosure: I was the link submitter[1], but not affiliated with the project in any other way)

First of all, citation needed. I don't believe Google is anywhere near being the most used provider, nor do they claim so. I don't have any "official" stats, but it looks like ejabberd may still be the most widely deployed platform, even after jabber.org's migration to M-Link.

It may be true that google don't support pubsub (most of their re-implementations of IETF protocols tend to be incomplete anyway, just ask gmail IMAP users) but most other implementations do and no one has to use gtalk either as there are loads of free services out there.

Also, there has been enough interest here in getting proper user location support instead of the append-random-text-to-status kludge Maemo5 chose to implement.


Further threads have highlighted a few problems with the release (which is why it's not been released to the world!) including breaking the cellular modem on downgrading - resulting in an inability to make calls.
This has been a known issue with all previous upgrades that touch the modem firmware, and most likely will be with the official PR1.2 release as well.

Someone should also mention that flashing an unverified firmware image downloaded from some random location on the net can be risky. Who's to say that it doesn't contain "additions" that send your account passwords to the publisher or make premium rate calls in the middle of the night?

[1] incidentally, sent with XMPP via tweet.im, which is very handy if like me you use too many computers and don't feel like setting up extra accounts/apps on each one for this :-)
 

The Following 3 Users Say Thank You to lma For This Useful Post: