URL Encoding of Twitter updates
Lee
When I am posting to Twitter via my plugin I always include a URL
along with some other text in the status parmeter. The URL more often
than not includes multiple URL parameters so I obviously url_encode
the whole parameter (text and URL). All this works fine and the
update is posted to my Twitter account. When I view my Twitter page I
see the post from my plugin and the URL that I posted has been
converted into a TinyURL which is what I would expect. The problem I
have is that the TinyURL seems to have been created using the encoded
version of the URL. For example:
I include this URL in my Twitter update:
http://leeturner.org/index.php?title=twitterlution_v0_2_released&more=1&c=1&tb=1&pb=1
When I click on the TinyURL on the Twitter web page I am taken to this
URL:
http://leeturner.org/index.php?title=twitterlution_v0_2_released&more=1&c=1&tb=1&pb=1
Is this something I am doing wrong or is this a problem on the Twitter
side of things?
Any help great appreciated.
Kind regards
Lee
Alex Payne
Our automatic TinyURL conversion relies on a regular expression to
find URLs within status text. Sometimes that regular expression
doesn't match correctly. We've been trying to fix it on a
case-by-case basis, but it's not a top-priority bug. Until then,
consider shortening URLs on your end if you want to ensure that
they're converted correctly. Thanks!
--
Alex Payne
http://twitter.com/al3x
Lee
Thank you for the reply. From what I can tell the URL is being
matched correctly. There doesn't seem to be any of it missing. The
only problem I have is that the '&' symbols have been converted to
'&' during the url encoding and not converted back. I am not sure
if this is related to the regular expressions that you use to find the
urls but I will work around it for the time being.
Many thanks
Lee
On Sep 17, 7:22 pm, "Alex Payne" <a...@al3x.net> wrote:
> Lee,
>
> Our automatic TinyURL conversion relies on a regular expression to
> find URLs within status text. Sometimes that regular expression
> doesn't match correctly. We've been trying to fix it on a
> case-by-case basis, but it's not a top-priority bug. Until then,
> consider shortening URLs on your end if you want to ensure that
> they're converted correctly. Thanks!
>
> On 9/17/07, Lee <l...@leeturner.org> wrote:
>
>
>
>
>
> > Hi
>
> > When I am posting to Twitter via my plugin I always include a URL
> > along with some other text in the status parmeter. The URL more often
> > than not includes multiple URL parameters so I obviously url_encode
> > the whole parameter (text and URL). All this works fine and the
> > update is posted to my Twitter account. When I view my Twitter page I
> > see the post from my plugin and the URL that I posted has been
> > converted into a TinyURL which is what I would expect. The problem I
> > have is that the TinyURL seems to have been created using the encoded
> > version of the URL. For example:
>
> > I include this URL in my Twitter update:
> >http://leeturner.org/index.php?title=twitterlution_v0_2_released&more...
>
> > When I click on the TinyURL on the Twitter web page I am taken to this
> > URL:
> >http://leeturner.org/index.php?title=twitterlution_v0_2_released&...