Hey, Thanks for the email. The URL pattern you are using is incorrect which is why you are seeing the status get dropped. For the ?status= URLs to work you should make sure your links follow this pattern: http://twitter.com/home?status=url%20encoded%20message
Missing the /home will mean the status isn't maintained on redirects or logins so you'll want to make sure you use that pattern instead. I'll let the team know about the double encoding issue on redirect from www.twitter.com to twitter.com but to be safe you should use the URL pattern above and not rely on the redirect. Thanks, Matt On Fri, Jul 30, 2010 at 6:59 AM, warpdesign <nicolas.r...@gmail.com> wrote: > I think I found a problem with the status update using GET. > > http://twitter.com/?status=foo%20bar will work, correctly unescaping > characters in the status textarea: > > "foo bar" > > However when trying to change the update using this url: > > http://www.twitter.com/?status=foo%20bar, the user gets redirected to > twitter.com/?status=foo%2520bar (notice the %25) which results into > the escaped status in the textarea: > > "foo%20bar" > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
