hi ed, as i already stated 2 times i used urlencoding. i wanted to prevent my tweets looking like this "http%3A%2F%2Fwww%2Fmydomain%2F.xyz %2Findex.php%3Fkey1%3Dvalue1%26key2%3Dvalue2%26%3Dvalue3" . this looks pretty ugly. i am basically wondering why there isn't a solution to wrap these ugly urls like hrefs in html using a title for the link name and <a></a> tags to wrap!?
regards, tino On 17 Jan., 04:19, Ed Costello <epcoste...@gmail.com> wrote: > Are you absolutely certain that the entireURLis being posted to twitter? Is > it possible that some filter is interpreting the “&” character and stripping > off the remainingURLbefore you post it to twitter? > > Do you have a log of what is being transmitted to twitter? > > Are you transmitting through any proxies which could potentially be stripping > the data off? Is twitter the only site with which this problem is occuring? > > I can’t reproduce the problem, including posting theURLyou listed, but I > amURLencoding “&” to “%26”. > > By definition > (seehttp://apiwiki.twitter.com/Things-Every-Developer-Should-Know#5Parame...) > tweets are supposed to beURLencoded before transmitting to twitter, so I > don’t understand what you mean byURLencoding. If you want the “&” to have > meaning within your tweet (regardless of whether it’s in aURLor just text), > you MUST convert it to %26 otherwise it will appear to twitter as a variable > on par with source, geo, status and in_reply_to_status_id. If you are > notURLencoding the tweet then start doing so. > -- > -ed costello