[PATCH] tinyurlification of URLs in notices
[PATCH] tinyurlification of URLs in notices
| Issue ID: | 31 |
| Issue Category: | feature |
| Component: | ui |
| Priority: | minor |
| Status: | fixed |
| Assigned: | Unassigned |
| Version: | 0.5 |
| Milestone: | 0.9 |
| Keywords: | short urls |
We should automatically tiny-urlify URLs in notices.
We should find an [http://opendefinition.org/osd OSD]-compatible smallifier to use by default. Or install one if none exists.
We need a configuration option for using another tinyurlifier.
Comment: please don't shorten URLs unless they bump the notice length over 140 characters. I rarely click on URLs in tweets, because they're all shortened and hence opaque - unless the user has bothered to explicitly describe them. -- Earle Martin
Comment: TwitterFox shortens URLs and puts the original URL in the title attribute of the HTML link, making it visible on hover. This is an elegant and convenient solution to the above issue. -- Micah Sittig
That would certainly be useful for when URLs are shortened, but having to mouseover every single shortened URL on the screen is still a bit wearying. -- Earle Martin
Comment: As long you are putting in titles and whatnot, why not just embrace HTML and leave the full link in and truncate the displayed link text? E.g., {{{youtube.com/b...}}} -- Ian Bicking
http://bit.ly/ is promising. should the service used be a user-pref? -- danbri
Comment: I agree with Earle Martin. auto tinyurls save no characters in your message & reduce trust in the proffered URL. at most Ian Bicking's suggestion to use a character (like # for hashtags) to automatically linkify thus leaving out "http://" would be beneficial. -- exador23
| Attachment | Size |
|---|---|
| 31_url_auto_shortening.2.patch | 12.29 KB |
| 31_url_auto_shortening.patch | 12.22 KB |

Updates
#1
I am with Earle and others who don't like clicking suspicious-looking links. If this is implemented, please at least allow a user to disable it for their own posts. Preferably for inbound messages as well, although I can see that would be harder.
#2
My take:
* definitely user (poster) configurable (use/don't use)
* use only when message length is too long when URL is not shortened
* do not shorten an already-shortened URL - even if that would bring message length within the 140char limit (that would break usage of utilities like longURL which expand short URLs for the reader)
#3
This ticket is not closed, but the feature is already implemented on 0.61b
I found a bug and reported it at bug #779.
You can also subscribe to the
RSS feed for updates to this issue.