On Jul 15, 5:04 pm, Nick Arnett <nick.arn...@gmail.com> wrote:
> There's a horrible solution to
> that, too... tweet the original URL and then read back the status to get the
> Twitter-specific bit.ly URL.  Ugh.

Actually that is a pretty good idea, thanks!!! It is horrible, but I
can't think of a better way atm. I think twiturly have mentioned that
they can resolve URLs to tweets, but their API is very limited. My
current application is not cool enough to ask them for a higher rate
limit ;-)

Björn

Reply via email to