7 ms·
Bit.ly is Harmful to Your Reputation
- Osmose 17y agoI'm having a really hard time believing the scenario where a user follows a shortened link in a re-tweet, sees the bit.ly warming page, assumes that the original author is trying to spread malicious stuff (and that the re-tweeter, whom this user is following and supposedly trusts, is supporting this malicious stuff), and starts telling other people about how untrustworthy the original poster is. In reality, they'd probably close the page, maybe make a reply tweet confused about the warning, and go on with their life.
- DenisM 17y agoWhat do you think happens when you click it and report a mistake? Do they check the link and remove the flag if the site is ok? No, they don't. They told me to make a new bit.ly link and give it out to people, as if that would undo the damage that was done Uhm. Reminds me of Yelp.
- jrockway 17y agoWhat Twitter needs is to remove the 140 character limitation. Nobody uses SMS anymore, especially when the content contains URLs to non-mobile-friendly sites.
- markbao 17y agoI think that would completely go against the concept of Twitter: short-form communication.
- jbellis 17y agoAllowing your users to determine how short is short enough would be a good thing.
- patio11 17y agoIs "the concept of Twitter" what people are getting value from? If not, forget "the concept". (In my circles, people seem to be getting value from "an opt-in audience of likeminded people who you may extract business value from someday which does not include your girlfriend, high school buddy, mother, or Farmville." People definitely are not using Twitter primarily for short-form communication: if they were, two tweets out of every three wouldn't include a link to long-form communication.)
- derefr 17y ago> People definitely are not using Twitter primarily for short-form communication: if they were, two tweets out of every three wouldn't include a link to long-form communication.) That's not quite true; people read the short text to figure out whether they want to click the link. Even if long-form communications were allowed, there would still need to be a "title" field, for people to determine if they want to read the whole thing—which would basically be what is currently the tweet itself.
- alextgordon 17y agoThey could detect URLs and not count them towards the total message length.
- tkaemming 17y agoWhat would happen when those messages are delivered to a user's phone via SMS? There's still a nontrival amount of users having status updates/direct messages delivered to their mobile phones that probably wouldn't appreciate a message with a 50+ character URL (or the URL being stripped, effecting message integrity).
- alextgordon 17y agoThey could apply URL shortening to a tweet when delivering over SMS, if necessary.
- deleted 17y ago[deleted]
- derefr 17y agoOr they could apply URL canonicalization to tweets delivered any other way: follow all the 302s until they get the actual page, then replace with those URLs instead. (Actually, the best approach would be to canonicalize the URL on its way in, and then shorten with a single, known URL shortener on the way out, if sending via SMS. This would stop the "shortener wars" in its tracks, which is probably a good thing, because each shortener that dies leaves dangling links in its wake.)
- dmoney 17y agoand then shorten with a single, known URL shortener on the way out Which should be Twitter's own built-in shortener.
- jrockway 17y agoWhat happens when something in the middle redirects infinitely, is slow, or is down? Does the tweet have to wait until canonicalization to show up? How long are people willing to wait? Is it acceptable to not be able to link to a site unless it's up? As OpenID implementors have noticed, these issues cannot simply be ignored. Making an untrusted HTTP request is tricky business.
- deleted 17y ago[deleted]
- ja2ke 17y agoI think Twitter officially supporting and converting URLs into a token at the time a tweet was written would do the trick fine. The 140 limit is what made them, but URLs are obviously a point of failure and frustration, hence the near constant hulabaloo over shorteners and redirects etc. It'd surprising to me that Twitter hasn't offered an official solution for URLs yet, to be honest. They saw people were using @ to reply, and supported it. They saw hash tags and retweets show up and supported them, too. But most users go to a third party to handle links.
- jlees 17y agoyeah, I'm very surprised there isn't a twt.tr or something. Maybe they're holding out for .co...
- alexro 17y agoTwitter in fact sort of remove that limit. There is a change called annotations around the corner
- philwelch 17y agoActually I remember a huge discussion a few days ago about how Twitter has a very large base of urban African-American users who do, in fact, use SMS to access it.
- justinph 17y agoTons and tons of people still use twitter via SMS. @EV talked about this during his (otherwise boring) SXSW talk. I don't see them ditching that anytime soon.
- edanm 17y agoI think Twitter should just not count URL's towards the 140 characters. All URL's should count as one character.
- ericz 17y agoThat seems rather stupid. How is url-shortening a already url-shortened url a security threat?
- whughes 17y agoExtra cloaking for malicious links? Bit.ly can't exactly check the original site to see if it's OK if it's hidden behind a funky redirection layer. I think that bit.ly was reasonable to have an interstitial, although maybe they should be more open about why and how to remove it.
- tkaemming 17y agoThey could check the endpoint URL by following the HTTP headers on 301/302 redirects.
- sjs 17y agoIt's a standard http 301 redirect, not a "funky redirection layer". /Users/sjs % curl -i http://xrl.in/33qj HTTP/1.1 301 Permanent Redirect Date: Sun, 09 May 2010 00:38:19 GMT Server: Apache Location: http://www.donationcoder.com/CodingSnacks/index.php Content-Length: 0 Content-Type: text/html
- thenduks 17y agoRight, but the problem is this scenario: Bit.ly see's your xrl.in and does a request. They find 301 and the location at donationcoder.com. They conclude "this site is ok". Later, the xrl.in url is changed to <malware link>. They aren't going to do a request to every url they're linking to on every click, obviously. So they'd only get the one chance. Now, I'm not actually sure that xrl.in lets you change links after shortening. The point is that bit.ly doesn't know either.
- jbm 17y agoBit.ly could check a link to no_malware_here.com, which thereafter adds a 301 that redirects to your_computer_now_has_aids.com. I think it is misleading to display that message based on the possibility of a redirection. Any page can do that, not just xrl.in.
- tkaemming 17y agoWhile the author has a right to be upset, her attitude toward the support staff — who likely have no control over the situation — is disgusting. ("Your apology is worthless", "Your refusal to check the link", etc. from the email conversation, and the ensuing comments on the blog post.)
- markbao 17y agoSeriously. I've found it's easier to make someone do something when you don't have your teeth clenched at first, looking to attack. If she approached that with a "Could you help me figure out..." or "I think you should probably fix..." attitude, instead of a "screw you" one, she probably would have received a similarly gracious response.
- csallen 17y agoI see your point. I don't think she's railing against the support staffers personally, but against the company itself. "Your apology is worthless", as in "Bit.ly, your apology is worthless". Still, she could've been a bit more tactful. Anyway, this is quite an eye-opening article. What bit.ly is doing is a great example of how not to run a business. We should be educating people about the internet, not taking advantage of their ignorance so we can lie about our competitors.
- jlees 17y agoShe only started to get uppity after the extremely terse and unforgiving reply from bit.ly ("We don't allow that"), obviously we should all wait a while before writing emails or blog posts while angry, but we're also all human.
- wyclif 17y agoShe forgot #3: Just use one of the whitelisted shorteners she mentioned further up in the article, e.g. goo.gl.
- jlees 17y agoNot quite as simple as that, none of the three are readily available to use by just, say, visiting the site and typing in an URL. You need toolbars/extensions/clients etc. If she usually uses a client that's set to xrl.in changing to another shortening service might be a massive pain.
- vaporstun 17y agohttp://goo.gl/ http://goo.gl/ "Google URL Shortener is currently available for Google products and not for broader consumer use."
- DanielRibeiro 17y agoIt is interesting to note that common users can easily use goo.gl by using google toolbar's share function.
- MWinther 17y agoHow about putting some of the blame on Tweetdeck? Shouldn't "short enough" links be allowed to stay intact?
- jackowayed 17y agoYes, they should. But what's worse? Software that people don't even pay for being stupid in a fairly minor way, or bit.ly being anticompetitive and severely hurting its users in the process? He was focusing on the major issue.
- MWinther 17y agoI agree that bit.ly aren't being cool about this, clearly they should fix it. On the other hand, you could say that Tweetdeck is actually being stupid in a pretty major way. I have a hard time imagining this scenario occuring without the help of Tweetdeck, or other lazily written convenience shortener functions.
- bobbyi 17y agoIn Tweetdeck, when you paste in the URL, you can see it turn into a bitly URL. It's not as if you don't know that's what's going to be posted. There is a checkbox next to where you compose your tweet for "Auto Shorten URLs" that you can uncheck to disable this behavior. It's right there in plain sight, not buried inside preference dialogs.
- moultano 17y agoSo their spam detection system isn't as good as at should be. Give them a break. People spreading malware use url shorteners all the time, and I'd bet some automated system just got tripped up here. (malice -> incompetence etc.) I'm happy bitly is at least working on spam.
- tdavis 17y agoFirstly, the hypocrisy of a URL shortener blocking another URL shortener's links because they can't be verified is hilarious. Secondly, if a person goes as far as to shorten every link they copy from their browser and use a Twitter client that shortens all links regardless of length, I hardly think they have much room to complain about the system they're fully backing. What did she expect to happen? That Bitly would concern themselves with her reputation? If you want a URL shortener who cares, your only option is to run your own. Bitly's only concern is for their business, nothing more.
- toni 17y agoIn this case, even running your own URL shortener will not help in any way. Bit.ly blocks any already-shortened URL. Whether it's xrl.in, tinyurl or your own. You can only control your own shortened URL but you have no control when people re-tweet it and pass it through Bit.ly. Which then flags it as harmful.
- trezor 17y agoYou can only control your own shortened URL but you have no control when people re-tweet it and pass it through Bit.ly. Which then flags it as harmful. So bitly, a URL-shortening service, is blocking other shortened URLs because they deem shortened URLs harmful? And here I thought the stupidity of twitter and it's ecosystem of useless URL-shorteners had an actual limit.
- mst 17y agoOnly in the sense of the number of characters provided to perpetrate said stupidity. tweet.im keeps tinyurl-ing my xrl.us URLs. The result is actually longer. I suspect the closest to a solution here is a "don't shorten this unless it'd be X% shorter as a result" type flag for shortening APIs and then beat client authors over the head until they all pass the flag. And then beat client users over the head until they all upgrade. And then ... er ... never mind. I think I'll go stick my head in an oven now.
- Confusion 17y ago
- ck2 17y agoSo? Run your own blog with your own rss feeds and stop using twitter.
- malnourish 17y agoNot very feasible for the most part. I don't use twitter, but it does have a large following. This is somewhat along the lines of saying "So? Stop using facebook", although I understand where you're coming from.
- nhebb 17y agoDoes SMS have to display the href? Could Twitter just replace all URL's with the word 'link' and show the real URL on hover, thereby doing away with URL shorteners altogether?
- MWinther 17y agoHover doesn't work well with touch based interaction, which is all the rave these days, I hear. I like the idea of showing them separately somehow, though.
- pyre 17y agoIt only has to display 'link' in SMS. I don't necessarily think that it has to still say 'link' outside of SMS. It makes more sense to just strip the links when going through the SMS gateway, and count all URLs as 4 characters in the '140 characters' limit.
- steveklabnik 17y agoI've typed many a bit.ly link into a web browser directly from my phone. It's easy to do because they're so short.
- jrockway 17y agoBut not as easy as finding the tweet in your twitter client and just clicking.
- nostrademons 17y agoI solve this problem by not clicking on shortened URLs. At all. If you want me to click on something, send me the full link. If it's too long for Twitter, find me on GChat or send me an email.
- toddml 17y agoTodd from bit.ly here. From day one, we've prized security, transparency, reliability, and openness at bit.ly. Along the way, we've made a number of product decisions based on those tenets. Among those are link permanence (link destinations don't change once created), the avoidance of anything that interferes with user experience (we've never framed, nor will we), and a dedicated focus on spam and malware detection, so that our users can click on bit.ly links with a high degree of confidence. We take our responsibility as internet citizens seriously, and you'll see this exhibited even in the small details of the ways in which we manage flagged links (you'll notice we never actually disable a redirect, and at most simply insert an interstitial which retains the end destination link). In the course of analyzing content for spam, malware, and phishing attacks, we rely on a number of systems, both internal and external. Over the course of the past year, a number of spammers have attempted to use various levels of indirection through redirectors (some of which are reconfigurable), in order to obfuscate and cloak their efforts. In fact, the bulk of shortens to bit.ly coming through other URL shorteners have tended to be attempts to spam the system. While our crawlers do of course follow links through redirections, the inclusion of modifiable redirects in the stream, and our analysis of the preponderance of spam attempts via these vectors have made it necessary and appropriate in some cases to block the URL shorteners. Just to reiterate, the only goal is and always has been to protect the end user clicking on bit.ly links, regardless of the link source. Given that multiple layer wrapping of URL redirectors tends to be an edge case based on inappropriate API usage, confused users, or in the preponderance of cases, attempts to spam, we think this has been a fair approach. As such, you'll note that we did in fact update our interstitial warning pages with language better reflecting the reasoning behind the status. We're happy to see a healthy, vibrant, shortening ecosystem, and have no intention whatsoever to put a damper on other sites in the space. Some have suggested we simply not shorten URLs already pointing to 3rd party short URLs. While this is a potential possibility, our API responses and the innumerable clients and scripts that use these methods aren't currently designed with this state in mind. Consequently, any changes would have to be carefully considered. As with any product, bit.ly is a work in progress, and we're always interested in finding ways to best serve our users, while maintaining the integrity and openness of the product.
- tyler 17y ago
- qeorge 17y agoI have to agree with the author, this is ridiculous. They even do this to tinyurl: http://bit.ly/cGLU0o http://bit.ly/cGLU0o Tinyurl was without a doubt bit.ly's #1 competitor, especially when their service launched, and they know you can't edit a tinyurl. Seems like a pretty convenient time for an URL shortener to suddenly get preachy about the dangers of URL shorteners.
- caffo 17y agoI've contacted bit.ly about this issue 4 months ago. Got the same answer - "Page is under review". Maybe its an indirect attack to the competitors?
- malnourish 17y agoUnfortunately, offering itself as the best alternative to protecting links when setting a warning page for already shortened links doesn't seem very "indirect".
- bcl 17y agoGee, how about we stop acting like we need to limit things to 140 characters? This isn't SMS you know. We do have the bandwidth to actually exchange useful information and real URLs. Twitter, bit.ly, et. al. are all pretty damn silly. Even back in the days of 300bd modems and BBS's we weren't this dumb.
- nollidge 17y agoThe brevity is what makes Twitter distinct from everything else.
- carussell 17y agoFunny, I thought the reason people should use a service is its worth, not auxiliary novelties. If I make a pitch to somebody, do you think I should rest assured that they'll go for it if I word it in the following way, "Now I know that by almost all metrics this kind of behavior is bad, but we did some looking into what other people are doing, and it's unique."?
- nollidge 17y agoYou seem quite confident that the 140-character limit is an auxiliary novelty, whereas I think it's rather central to Twitter's success. There are any number of other similar services (LiveJournal, Wordpress, Blogger, Posterous, Tumblr) that do not enforce any such limit, yet everybody's all over Twitter. And which metrics show that limiting updates to 140 characters is bad behavior? URL shortening sucks, for sure, but that doesn't mean the limit on prose isn't useful or attractive to users.
- carussell 17y agoI know that the gimmick is the cause of Twitter's success as well; I wasn't saying otherwise. But that doesn't make it a gimmick. URL shortening is bad for humans and bad for machines. Ergo, that behavior is bad.
- vsync 17y ago
- Hume62 17y agoIsn't the problem bigger than a small number of people not paying attention to their Twitter client re-shortening links when it's not necessary? Aren't people intentionally re-shortening links they get from others, so that they can track their own reach/influence? If I have a big following and I re-shorten your link, I can then go to Bit.ly or (anywhere else I have an account) and exactly measure how that link was spread across the net, regardless of whether any RTs mention me. "I'll take your short link and raise you my own..."
- gsiener 17y agoMy takeaway is to make sure I'm using the most popular shortener (aka bit.ly)