URL encoding of status= parameter in #newtwitter

[Jonathan Strauss]

The following link works fine for users with access to #vintagetwitter
but breaks on the first URL encoded & (%26) or # (%23) for users with
#newtwitter:
http://twitter.com/home?status=Trying+out+URL+encoding+%26+stuff+on+%23newtwitter+vs+%23vintagetwitter

Is this intentional?

Thanks,
-jonathan

--
Jonathan Strauss, Co-Founder
http://awe.sm

Blog: http://jonathanhstrauss.com
Twitter: http://twitter.com/jhstrauss

[Matt Harris]

Hi Jonathan,

I'll look into this but have you consider using the Tweet Button
instead. Using the Tweet Button gives a better experience and means
users don't need to leave your website to tweet your message.

You can get the Tweet Button on our Goodies page:
http://twitter.com/goodies/tweetbutton

or create your own using the developer resources:
http://dev.twitter.com/pages/tweet_button

Best,
@themattharris

> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: http://groups.google.com/group/twitter-development-talk
>

--

Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[Jonathan Strauss]

Hey Matt,

I know the tweet button very well, and I agree that it's better for
most use-cases (we're actually driving our customers towards using /
share instead of /home?status= for their custom share to Twitter
interfaces). However, all legacy 'Share on Twitter' or 'Tweet This'
implementations (that don't go through OAuth) use /home?status= and if
the things that worked before stop working as #newtwitter rolls out to
the full userbase, it's going to break a lot of stuff for people who
haven't yet had a chance to switch to the tweet button or a custom
integration with /share.

Thanks,
-jonathan

On Sep 24, 5:47 pm, Matt Harris <thematthar...@twitter.com> wrote:
> Hi Jonathan,
>
> I'll look into this but have you consider using the Tweet Button
> instead. Using the Tweet Button gives a better experience and means
> users don't need to leave your website to tweet your message.
>
> You can get the Tweet Button on our Goodies page:
>    http://twitter.com/goodies/tweetbutton
>
> or create your own using the developer resources:
>    http://dev.twitter.com/pages/tweet_button
>
> Best,
> @themattharris
>
>
>
>
>
> On Fri, Sep 24, 2010 at 12:36 PM, Jonathan Strauss <jonat...@awe.sm> wrote:
> > The following link works fine for users with access to #vintagetwitter
> > but breaks on the first URL encoded & (%26) or # (%23) for users with
> > #newtwitter:

> >http://twitter.com/home?status=Trying+out+URL+encoding+%26+stuff+on+%...

[Matt Harris]

Hey Jonathan,

Absolutely! Just wanted to put the Tweet Button out there as an option.

So we can track this can you file an issue on:
http://code.google.com/p/twitter-api/issues/list

I'll keep that updated with progress.

Thanks,
@themattharris

[Pat Diven II]

Hey Jonathan, how's the Mission? Figures that I'd find a thread
started by you for the same issue we're also having. :)

So yes, we're also getting bit by the same issue. One thing I noticed
on #newtwitter is that the encoding is mangled during a redirect
(from /home?status= to /?status=):

Redirect FAILS on #newtwitter:
http://twitter.com/home?status=Trying%20out%20URL%20encoding%20%26%20stuff%20on%20%23newtwitter%20vs%20%23vintagetwitter

Direct URL WORKS on #newtwitter:
http://twitter.com/?status=Trying%20out%20URL%20encoding%20%26%20stuff%20on%20%23newtwitter%20vs%20%23vintagetwitter

Unfortunately we're all not supposed to use the latter method. It
works on #vintagetwitter but it doesn't preserve the status message
after the user logs in to either version anyway.

I just submitted the issue because it looks like @jhstrauss didn't get
around to it yet:
http://code.google.com/p/twitter-api/issues/detail?id=1904

Cheers,
Pat - @micropat

On Sep 24, 8:51 pm, Matt Harris <mhar...@twitter.com> wrote:
> Hey Jonathan,
>
> Absolutely! Just wanted to put the Tweet Button out there as an option.
>
> So we can track this can you file an issue on:
>    http://code.google.com/p/twitter-api/issues/list
>
> I'll keep that updated with progress.
>
> Thanks,
> @themattharris
>

[Jonathan Strauss]

Heh, thanks Pat! That was on my To Do list for tonight, I swear :-)

On Sep 28, 9:04 pm, Pat Diven II <p...@addtoany.com> wrote:
> Hey Jonathan, how's the Mission? Figures that I'd find a thread
> started by you for the same issue we're also having. :)
>
> So yes, we're also getting bit by the same issue.  One thing I noticed
> on #newtwitter is that the encoding is mangled during a redirect
> (from /home?status= to /?status=):
>

> Redirect FAILS on #newtwitter:http://twitter.com/home?status=Trying%20out%20URL%20encoding%20%26%20...
>
> Direct URL WORKS on #newtwitter:http://twitter.com/?status=Trying%20out%20URL%20encoding%20%26%20stuf...

[Jonathan Strauss]

@themattharris, Pat's ticket just got rejected for not being an API
issue :-/. See http://code.google.com/p/twitter-api/issues/detail?id=1904

I have just filed it (again) via http://twitter.com/help/escalate.

-jonathan

On Sep 28, 9:24 pm, Jonathan Strauss <jonat...@awe.sm> wrote:
> Heh, thanks Pat! That was on my To Do list for tonight, I swear :-)
>
> On Sep 28, 9:04 pm, Pat Diven II <p...@addtoany.com> wrote:
>
>
>
> > Hey Jonathan, how's the Mission? Figures that I'd find a thread
> > started by you for the same issue we're also having. :)
>
> > So yes, we're also getting bit by the same issue.  One thing I noticed

> > on #newtwitter is that theencodingis mangled during a redirect

[Tom van der Woerdt]

Well, it's not an API issue. ;-)

Tom