hey glenn.
i think something went wrong in the copy and paste -- there should have been
a space between the URL and the hashtag.
On Thu, May 13, 2010 at 11:02 PM, glenn gillen <gl...@rubypond.com> wrote:
> Raffi,
>
> This follows on nicely from the presentation at Warblecamp last week
> discussing how difficult it is to do this right, and I think a
> consistent approach across all clients (including twitter.com,
> mobile.twitter, and 3rd party apps) should be priority number 1.
> However looking at your example:
>
> On May 13, 10:25 pm, Raffi Krikorian <ra...@twitter.com> wrote:
> > {
> > "text" : "hey @raffi tell @noradio to check out
> http://dev.twitter.com#hot";,
> > <snip>
> > {
> > "url" : "http://dev.twitter.com";,
> > "indices" : [38, 64]
> > },
> > ],
> > "hashtags" : [
> > {
> > "text" : "#hot",
> > "indices" : [66, 69]
> > "url" : "http://search.twitter.com/search?q=%23hot";
> > }
> > ]
> > }
>
> Without looking at how twitter.com would currently handle that
> example, I would have expected the url to be "http://dev.twitter.com/
> #hot" and for the tweet to contain no hashtag. If the hashtag always
> takes precedence I'd have no way to link to the following without
> using a URL shortener: http://oauth.net/core/1.0a/#anchor41
> --
> Glenn Gillen
> http://glenngillen.com/
>
--
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi
