I did a search this morning to see if there was anything related to the cookie issue with Openwave software. Instead I found a post from Dennis saying that it appears that Sprint has now followed Vodafone in disrupting the mobile web. Ouch. And their partner in crime? Openwave. I was hoping to find some positive reaction, instead I find a new mention of negative behavior. Damn.
Mike Rowehl
I've been working in mobile for a long time, and on internet service scalability even longer. I'm founder and CTO at Metaresolver, Inc, a tech platform for performance media buying in mobile. I have a personal blog at rowehl.com.
Miker on Twitter- del.icio.us feed
- Leveling Up on Chef Best Practices
- How to pass system properties to "maven test" task?
- OneTab extension for Google Chrome - save 95% memory and reduce tab clutter
- Solve for X
- Orwell: Politics and the English Language
- Form Factor
- opencog/opencog
- http://www.mattsilverman.com/2013/02/tools-to-generate-beautiful-api-documentation.html
- plenty-web
- Filipe Kiss : A better git log
We found that sites beginning with “mobile.” are still sent the UA properly. So, one quick hack is to detect the Sprint UA and redirect those clients to an appropriately named host in your domain. Another idea that we’re still testing is to detect the Sprint UA, redirect to a “mobile.” site that does not nothing but redirect back with the real UA encoded as a query parameter in the URL.
Pingback: Sprint OpenWeb Update at Wap Review
Pingback: Wap Review
Pingback: Taptology - Taptu Mobile Search Engine » Blog Archive » Sprint & OpenWave are breaking the mobile web: Why transcoders suck
Pingback: [IMPORTANTE] Sobre Free GPRS/Navegación WAP en Nextel - Página 3 - psicofxp.com