Closed GoogleCodeExporter closed 9 years ago
Could you describe how you attached the link to the message? Assuming that you
copied
& pasted the shortened link manually, you might have accidentally selected the
wrong
text (including the ending parentheses when pasting the original URL to
bit.ly). If
that is the case, you might consider selecting the "Include URL" and
"...shortened"
checkboxes while viewing the page you want to post, and the link will be
included and
shortened automatically for you.
Original comment by past...@gmail.com
on 14 May 2009 at 7:27
Hmm I didn't specify to use bit.ly. I have the "Include URL" checked and the
"...shortened" checked. Then I pasted to the entry field "testing firestatus
(https://addons.mozilla.org/en-US/firefox/addon/8973)" and press Send.
The twitter update turns out shortened to use bit.ly, while the facebook update
use
the original url.
I have twitterfox extension if it can give you any clue.
Original comment by hha...@gmail.com
on 14 May 2009 at 7:36
Firestatus uses only tinyURL and urlb.org for link shortening and shortens only
the
url of the page you are currently viewing (not urls pasted in the status text
field).
So the incorrect shortening by bit.ly of the link you pasted in the box was not
done
by firestatus. We will further investigate and let you know.
Original comment by chstath
on 14 May 2009 at 9:17
Hmm that's weird then. Not sure what causes the url in twitter update to be
shortened
to bit.ly (instead of tinyURL). I checked twitterfox extension and my twitter
settings, and there's no such url-shortening setting. I'll let you know if I
find
anything. Thanks :)
Original comment by hha...@gmail.com
on 14 May 2009 at 11:13
Apparently Twitter now shortens automatically URLs using bit.ly (previously
they used tinyurl):
http://www.techcrunch.com/2009/05/06/url-shortening-wars-twitter-ditches-tinyurl
-for-bitly/
Since the reported issue was not caused by FireStatus, I'm marking the bug as
invalid.
Original comment by past...@gmail.com
on 5 Jun 2009 at 5:22
Original issue reported on code.google.com by
hha...@gmail.com
on 14 May 2009 at 3:37