<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mobile Web that needs usernames and passwords. Just an arse.</title>
	<atom:link href="http://www.mobileindustryreview.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mobileindustryreview.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html</link>
	<description>Daily news and opinion for 250,000 industry executives and mobile fanatics</description>
	<lastBuildDate>Tue, 14 Feb 2012 22:14:00 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John</title>
		<link>http://www.mobileindustryreview.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html/comment-page-1#comment-42612</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 12 Apr 2007 09:35:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html#comment-42612</guid>
		<description>My thoughts on the N95, posted elsewhere first:

I&#039;ve had one for 2 weeks now. Its terrible. Actually let me qualify that - the individual elements of it are great - the screen is lovely, media playback is nice. However put them all together and you have a phone that is a real mess, and unfortunately another example of Nokia&#039;s race to have lots of features that look great on paper, and forgetting the basics.

For example, the phone doesn&#039;t have any central awareness of its state of connectedness - if you download and use the podcasting application it doesn&#039;t care if you are already connected to the internet via wireless lan, it makes you disconnect first, and then choose a new access point. No doubt that&#039;s down to how the series 60 operating system works but its stupid. You cannot choose a default wireless lan point and match it with a default WAP access point - you can make one the default for each application, or you can be asked every single time.

The screen causes a high pitch whistle during phone calls (although you have to be young/have decent hearing to hear that - I can only hear it with one ear).

I also found that if you set the phone to use a default wireless lan access point, and it can&#039;t find it, the phone will crash.

Camera - 5 megapixel but HUGE delay between pressing the button and the picture being taken, even more so if the flash is involved.

Sat Nav is nice, but will drain the battery in 15 minutes so buy a car charger. It also seems to use a data connection throughout the journeys. Had a couple of glitches where it stopped tracking where we were, and &quot;at the next roundabout......&quot; nothing.  Incidentally, a 1.5 hour sat nav assisted trip from Berkshire to Warminster with a couple of suggested course corrections caused the phone to use 3 meg of data.

You will NEED an unlimited data bundle - just opening the (other web site) homepage causes 300 KB of data according to the phone, so any browsing and you&#039;ll run up a very large data bill.

RSS feeds are accessed via the web browser, rather than being their own stand alone applicaion as found in SonyEricsson phones. I prefer the way SE do it - for me RSS feeds are all about reading stuff in a dedicated application, rather than reading it as another web page.

Oh, and Nokia have seen fit not to put a hard cover over the screen, so you can squash the LCD crystals with your finger - god knows what the long term effect of having it in your pocket with your keys is going to be like.</description>
		<content:encoded><![CDATA[<p>My thoughts on the N95, posted elsewhere first:</p>
<p>I&#8217;ve had one for 2 weeks now. Its terrible. Actually let me qualify that &#8211; the individual elements of it are great &#8211; the screen is lovely, media playback is nice. However put them all together and you have a phone that is a real mess, and unfortunately another example of Nokia&#8217;s race to have lots of features that look great on paper, and forgetting the basics.</p>
<p>For example, the phone doesn&#8217;t have any central awareness of its state of connectedness &#8211; if you download and use the podcasting application it doesn&#8217;t care if you are already connected to the internet via wireless lan, it makes you disconnect first, and then choose a new access point. No doubt that&#8217;s down to how the series 60 operating system works but its stupid. You cannot choose a default wireless lan point and match it with a default WAP access point &#8211; you can make one the default for each application, or you can be asked every single time.</p>
<p>The screen causes a high pitch whistle during phone calls (although you have to be young/have decent hearing to hear that &#8211; I can only hear it with one ear).</p>
<p>I also found that if you set the phone to use a default wireless lan access point, and it can&#8217;t find it, the phone will crash.</p>
<p>Camera &#8211; 5 megapixel but HUGE delay between pressing the button and the picture being taken, even more so if the flash is involved.</p>
<p>Sat Nav is nice, but will drain the battery in 15 minutes so buy a car charger. It also seems to use a data connection throughout the journeys. Had a couple of glitches where it stopped tracking where we were, and &#8220;at the next roundabout&#8230;&#8230;&#8221; nothing.  Incidentally, a 1.5 hour sat nav assisted trip from Berkshire to Warminster with a couple of suggested course corrections caused the phone to use 3 meg of data.</p>
<p>You will NEED an unlimited data bundle &#8211; just opening the (other web site) homepage causes 300 KB of data according to the phone, so any browsing and you&#8217;ll run up a very large data bill.</p>
<p>RSS feeds are accessed via the web browser, rather than being their own stand alone applicaion as found in SonyEricsson phones. I prefer the way SE do it &#8211; for me RSS feeds are all about reading stuff in a dedicated application, rather than reading it as another web page.</p>
<p>Oh, and Nokia have seen fit not to put a hard cover over the screen, so you can squash the LCD crystals with your finger &#8211; god knows what the long term effect of having it in your pocket with your keys is going to be like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HeavyLight</title>
		<link>http://www.mobileindustryreview.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html/comment-page-1#comment-42456</link>
		<dc:creator>HeavyLight</dc:creator>
		<pubDate>Wed, 11 Apr 2007 23:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html#comment-42456</guid>
		<description>Tom - I was thinking more about reclaiming the website and applications&#039; account-names and passwords that would be compromised by losing the phone. Eg. my gmail account details are stored on my phone and I wouldn&#039;t want that hijacked! What about the folk who access their bank accounts?

openID *from* your mobile?  That sounds interesting.
I&#039;ve wondered about using my mobile number as an identity.
Keep us (or nominally, Ewan!) informed?</description>
		<content:encoded><![CDATA[<p>Tom &#8211; I was thinking more about reclaiming the website and applications&#8217; account-names and passwords that would be compromised by losing the phone. Eg. my gmail account details are stored on my phone and I wouldn&#8217;t want that hijacked! What about the folk who access their bank accounts?</p>
<p>openID *from* your mobile?  That sounds interesting.<br />
I&#8217;ve wondered about using my mobile number as an identity.<br />
Keep us (or nominally, Ewan!) informed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://www.mobileindustryreview.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html/comment-page-1#comment-42398</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Wed, 11 Apr 2007 19:19:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html#comment-42398</guid>
		<description>HeavyLight said:&quot;My concern is how easy itâ€™ll be to â€˜re-claimâ€™ your application/website accounts (new and tough passwords all round?) when you lose your phone?&quot; There are many ways to reclaim accounts if you lose your phone/have it stolen/run out of credit - and that&#039;s covered by customer support processes.

As for openID, the more interesting bit (for me at least!) is making your mobile your openID, something I&#039;m working on at the moment...</description>
		<content:encoded><![CDATA[<p>HeavyLight said:&#8221;My concern is how easy itâ€™ll be to â€˜re-claimâ€™ your application/website accounts (new and tough passwords all round?) when you lose your phone?&#8221; There are many ways to reclaim accounts if you lose your phone/have it stolen/run out of credit &#8211; and that&#8217;s covered by customer support processes.</p>
<p>As for openID, the more interesting bit (for me at least!) is making your mobile your openID, something I&#8217;m working on at the moment&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HeavyLight</title>
		<link>http://www.mobileindustryreview.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html/comment-page-1#comment-42263</link>
		<dc:creator>HeavyLight</dc:creator>
		<pubDate>Wed, 11 Apr 2007 11:44:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html#comment-42263</guid>
		<description>tom says: &quot;you never need to log in from your phone because we know who you are.&quot;

My concern is how easy it&#039;ll be to &#039;re-claim&#039; your application/website accounts (new and tough passwords all round?) when you lose your phone?

I&#039;m all for automatic authentication but ideally shouldn&#039;t it be the internet connection itself that&#039;s passworded?

How about OpenID for mobiles?</description>
		<content:encoded><![CDATA[<p>tom says: &#8220;you never need to log in from your phone because we know who you are.&#8221;</p>
<p>My concern is how easy it&#8217;ll be to &#8216;re-claim&#8217; your application/website accounts (new and tough passwords all round?) when you lose your phone?</p>
<p>I&#8217;m all for automatic authentication but ideally shouldn&#8217;t it be the internet connection itself that&#8217;s passworded?</p>
<p>How about OpenID for mobiles?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://www.mobileindustryreview.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html/comment-page-1#comment-42216</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Wed, 11 Apr 2007 09:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html#comment-42216</guid>
		<description>it&#039;s possible to automate the login process on any wapsite by tying the access to the physical device, which is easy enough to do with services like IPX so you can identify the MSISDN, and is something we do on Pitch - you never need to log in from your phone because we know who you are.

We also have ways of getting around issues where MSISDN identification fails. That said, we enforce passwords on the WEB version of the service.

A good example of a bad implementation of this in a mobiel application is ShoZu, which forces you to re-enter your username and password if it ever fails activation, which gets old really quickly. 

So it;s not just mobile sites that fall down on this - mobile applications can do so as well.</description>
		<content:encoded><![CDATA[<p>it&#8217;s possible to automate the login process on any wapsite by tying the access to the physical device, which is easy enough to do with services like IPX so you can identify the MSISDN, and is something we do on Pitch &#8211; you never need to log in from your phone because we know who you are.</p>
<p>We also have ways of getting around issues where MSISDN identification fails. That said, we enforce passwords on the WEB version of the service.</p>
<p>A good example of a bad implementation of this in a mobiel application is ShoZu, which forces you to re-enter your username and password if it ever fails activation, which gets old really quickly. </p>
<p>So it;s not just mobile sites that fall down on this &#8211; mobile applications can do so as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricky Cadden</title>
		<link>http://www.mobileindustryreview.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html/comment-page-1#comment-42037</link>
		<dc:creator>Ricky Cadden</dc:creator>
		<pubDate>Tue, 10 Apr 2007 17:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/04/mobile_web_that_needs_usernames_and_passwords_just_an_arse.html#comment-42037</guid>
		<description>Ewan, 

I agree 100%. This is also why I use Opera Mobile on my N73. Usernames and passwords are saved and automatically entered. I don&#039;t use this on my home computer, as I like to have to type out my passwords so that I remember them, but the mobile web is supposed to be centered around convenience. That&#039;s truly the only reason it&#039;s in existence. To make part of it inconvenient is obtuse.</description>
		<content:encoded><![CDATA[<p>Ewan, </p>
<p>I agree 100%. This is also why I use Opera Mobile on my N73. Usernames and passwords are saved and automatically entered. I don&#8217;t use this on my home computer, as I like to have to type out my passwords so that I remember them, but the mobile web is supposed to be centered around convenience. That&#8217;s truly the only reason it&#8217;s in existence. To make part of it inconvenient is obtuse.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

