yes, twitter is after all a text based service.
anyway, adding html to a tweet opens up a can of worms.
it wont happen. it shouldnt happen.
yes, twtr could provide, via the web UI at least, a way to add
metadata to a tweet that is extra (not the text message itself, but
associated data that can be exposed on certain UIs. but thats a
different topic and i'd like to improve the current issue of short
also of interest - http://twitterdata.org
On Jul 8, 4:42 pm, Joel Strellner <j...@twitturly.com> wrote:
> It goes back to the root of twitter originally being a SMS
> application. I recall hearing or reading someone on the Twitter team
> saying that.
> On Jul 8, 2009, at 1:31 PM, whoiskb <whoi...@gmail.com> wrote:
> > I am curious if there has ever been an official response from twitter
> > on why some simple HTML has not been allowed in a tweet? If we were
> > able to use an anchor tag, and the HTML did not count against the 140
> > character limit, then the need for a URL shortener service would not
> > be needed.
> > On Jul 8, 10:27 am, sull <sullele...@gmail.com> wrote:
> >> ironically, my example urls are shortened here ;)
> >> On Jul 8, 12:20 pm, sull <sullele...@gmail.com> wrote:
> >>> this is a topic of interest to me for a long while.
> >>> been meaning to start a thread.
> >>> i'm often bothered by the automatic shortening of urls when in fact
> >>> the url does not need to be shortened. in these cases, i of
> >>> course do
> >>> not want to hide the real url by using a forced 3rd party service
> >>> like
> >>> bit.ly.
> >>> i have use cases where all that is posted is a url. and the url
> >>> includes a long detailed description of the link. this, in my
> >>> opinion, is smart as the only object to maintain is the url itself
> >>> which provides a hyperlink and a short message combined. sometimes,
> >>> these use cases are using natural language vanity urls to form short
> >>> sentences.
> >>> ie.http://john.tot.al.ly/wiped-out-on-this-huge-wave-in-hawaii-at-
> >>> the-Su...
> >>> the other annoying thing that is related to the twitter UI is how
> >>> long
> >>> urls are cut-off//trimmed even if they dont need to be. the above
> >>> example would be destroyed because it would result in something
> >>> like:
> >>> actually, i'm not certain if that is still the case as it seems to
> >>> me
> >>> that every url is shortened with bit.ly now. i grok the value in
> >>> tracking urls and bit.ly may be bought by twitter at some point and
> >>> this notion of url tracking will be fully integrated.... but the
> >>> debate about url shortners in general.... how they can break the
> >>> natural web, are vulnerable to massive broken links and simply thr
> >>> cryptic format itself that hides the true location.... are all to be
> >>> considered and continued to be debated.
> >>> at the very least, 3rd party developers should get an override
> >>> toggle.
> >>> that is something i think we all need to start demanding.
> >>> and yes, an official doc explaining the current and future
> >>> impementations of url shortening on twitter is definitely needed
> >>> now.
> >>> ...
> >>> @sull
> >>> On Jul 8, 4:50 am, Swaroop <rh.swar...@gmail.com> wrote:
> >>>> "However, if you paste in a link that is less than 30 characters,
> >>>> we'll post it in its entirety. If it's longer than 30 characters,
> >>>> we'll convert it to a shorter URL."
> >>>> Source:http://help.twitter.com/portal