GURFL file is a list of operators and their associated IP address ranges. This is a good way to find out from which carrier (ie. which country) does a request come from.

You can find it here

This file is currently “under construction”

I knew this day would come, did not expect it that fast and certainly not because of a flaw.
Browsers on mobile are becoming more and more powerful and a direct consequence is that making a difference between them and a desktop browser seems to be less and less useful (even though it will “always” make sense). I am surprised it comes that early, and even more it comes because of a flaw from Nokia engineers: I realised recently that mobile browsers embedded in some recent Nokia’s phone identified themself in the user-agent string as
“Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)”
ie. as a desktop browser. This is actually how the Open Source browser from Nokia identified itself and this browser is currently shipped on some Series 60 3rd edition and Series 90 phones.

That means you can not detect the request comes from a mobile device, you can not find out device properties with tool like WURFL,… Other mechanism have to be implemented to give access to a mobile version of a website (like the “social” mechanism, ie go on xxx/mobile)

More on that later…

Follow the thread of discussion on Yahoo! Group.

mobile.nytimes.com

Download the KAYWA reader

diggriver.com (QR Code for Digg River)

See also Digg on your mobile using Mobits.com service www.mobits.com/digg

Unfortunately the problem arise when you click on a link… the target website is not adapted to mobile device and you end up downloading a very heavy page that does not display well (if at all).
Useless on my phone.

Dave Winer seems also to be intersted by the mobile world since he bought a blackberry. He has put together YoMoBlog.com (QR Code)a service that lets you publish on your blog via a web interface using the MetaWeblog API.
He tries also to “mobilize” a few blogs: GigaOM, MicroPersuasion, Scripting (his own blog). In my opinion taking out css and removing some elements is not enough to claim those compatible for mobile. At the very best they are “Blackberry” friendly. What about the pictures ? what about the size/weight of the pages ?
Dave Winer identified the issue:

What’s coming next must be a web that works for mobile users, where we never click a link to a page designed to be rendered on a big-screen.

If the end result is not as good as expected and/or not so useful, those two examples put a little bit more the mobile web on stage…

TechCrunch: Dave Winer Ponders Mobile
TechCrunch: Digg Mobile, Inspired by Dave Winer

Download the KAYWA QR Code reader

Welcome to Kaywa too :-)

Remember MySpace sending alerts via SMS (via dailyphreak.com) ? well we also have implemented some SMS services on our blog plateform. Some of them are currently available on BleuBlog. They can still be improved and we are working on more features…

SMS Publishing:
Publish directly on your blog via SMS. Send the post content after the keyword “pub” to publish a SMS on your blog.

SMS Alert:
Get notified by SMS whenever a new post is published on your favorite blog. With the mobile link in the SMS you are one click away to read the full post on your mobile.
Send Alert {blogid} where {blogid} identified the blog on the plateform.

and here is how the SMS alert you get looks like (note the link with the “mobile” permalink to the post)

SMS Chat:
Allow all your readers to chat together in a SMS chat room.
Send Bchat {blogid} and your content to chat via SMS with all
readers in the chatroom associated to the blog {blogid} (where {blogid} identified the blog)

Cute is not it ? and more are coming…

More on KAYWA wiki (in french): SMS

works in Lausanne. welcome

From Austria. Welcome Stefan!!

This is neat… a FireFox plugin that lets you generate the QR Code for the page you are on. No need to type in long URL on the mobile phone… it generates them on the fly.

Of course this has a big drawback,… the webpage you are looking at is more likely not adapted for browsing on the mobile phone*, unless there are some content negotiation implemented (that serves you the tight content depending on the device) or some mobile link discovery mechanism.

This is the case for this blog located at https://www.smoothplanet.com while the mobile version much better to look at from a mobile device is located on https://www.smoothplanet.com/mobile. The right QR Code becomes then:

Generate your own QR Code
Download the KAYWA Reader

Thanks Marco for the pointer

It’s on .mobi website… it emulates behavior of a N70. Well not much to say except that emulator remains an emulator. The thoughest task on mobile world is to deal with a lot of various devices which is exactly what an emulator does NOT do!
Need to test ? get yourself the User Agent switcher add on for Firefox. It will do the job!

On the same topic read:
What’s .mobi Playing At Now?
On .mobi

Via dotMobi blog