Hi Matt, We´re with the same problem. Look: http://twitter.com/home?status=Brasil%20avan%C3%A7a%20em%20primeiro%2C%20mas%20joga%20mal%20e%20irrita%20Dunga%20http%3A%2F%2Fbit.ly%2F9U4ax6%20%23terra
There´s a problem only when the user was not logged in. Tks a lot. On Jun 22, 3:56 pm, Matt Harris <thematthar...@twitter.com> wrote: > You want to make sure you URL encode the entire status you are sending, > including the spaces. That being said the hashtag is dropped so that's a bug > at our end. Can you file it > onhttp://code.google.com/p/twitter-api/issuesandi'll pass it onto the > team. > > Thanks, > Matt > > On Tue, Jun 22, 2010 at 10:27 AM, maestrojed > <maestro...@highfivefriday.com>wrote: > > > > > > > You can pre-populate a tweet by doing something like: <a > > href="http://twitter.com/home?status=Iam asking a question on > > stackoverflow">http://twitter.com/home?status=Iam asking a question > > on stackoverflow</a> > > > If you want to use a hashtag you have to urlencode it <a href="http:// > > twitter.com/home?status=I am asking a question on > > %23stackoverflow">http://twitter.com/home?status=Iam asking a > > question on %23stackoverflow</a> > > > If the user is not already logged into twitter, once they do log in, > > they are redirected to a 404 because of these hashtags. I am sure its > > because twitter has to save/pass through this status query string > > while you log in. > > > Any one have suggestions? A hashtag is important to me in this > > situation. > > -- > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris
