Ok, I've done my homework, really. I get that you can't let m.twitter.com do pre-populated status updates. Clickjacking, you say. Mobile browsers won't process your special javascript-busting, you say. I've read all of these threads that say so.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/6a5f2194b03778b5/4917d80e49787def?lnk=gst&q=mobile#4917d80e49787def http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7865e894d94161e7/ae9f1cb1fbf272f9?lnk=gst&q=mobile#ae9f1cb1fbf272f9 http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c1bd0818e0e8f7b0/e11ea235e961c75e?lnk=gst&q=mobile#e11ea235e961c75e http://groups.google.com/group/twitter-development-talk/browse_thread/thread/ea702e91df11dfd/fe71e005e7427039?lnk=gst&q=mobile#fe71e005e7427039 What about just letting us specify that we want to load the standard page? Is that possible? Or could you make it so? It's possible to send an iPhone user to twitter, which loads the mobile site, and then if that user clicks for the standard view, the pre-populated status is present. Is that really any different, security-wise, than visiting the standard page (with pre-populated text) in the first place? Thanks, Brian Williammee
