Yes, you need to ask twitter to fix that. They are using our api, but
obviously, they are encoding the ) after the .jpg. Thanks for
letting us know, but yes, this is a twitter issue.
Good luck with that. Since it is acceptable to have the unencoded )
character in a URL, I don't know how they
Yet another reason Twitter should NOT be bit.ly encoding URLs that do not
cause tweets to go 140 chars. (or at all for that matter, leave that up to
the users)
On Thu, Sep 10, 2009 at 13:42, Matthew Terenzio mteren...@gmail.com wrote:
Yes, you need to ask twitter to fix that. They are using
@googlegroups.com
Subject: [twitter-dev] Re: Errornous link - Bracket problem with bit.ly
Yet another reason Twitter should NOT be bit.ly encoding URLs that do
not cause tweets to go 140 chars. (or at all for that matter, leave
that up to the users)
On Thu, Sep 10, 2009 at 13:42, Matthew Terenzio mteren
On Thu, Sep 10, 2009 at 2:45 PM, Jim Renkel james.ren...@gmail.com
wrote:
Does the URL shortening happen only for tweets entered at twitter.com?
Or does it also happen for tweets created via the API? The former is a
twitter UI issue, and if they want to shorten tweets, well, that’s their
If in fact URL shortening is possible via the API, then there should at
least be an option to suppress it.
I have seen the API shorten URLs that I have already shortened which has
caused problems but I never got an answer on what the rules were because I
have also noticede some longer URLs
