Facebook Lets You j.mp Again, After Massive Spam And Malware Concerns

Robin Wauters

Robin Wauters is the European Editor of tech blog The Next Web and lead editor of Virtualization.com. He was a senior staff writer at TechCrunch until his departure in February 2012. Aside from his professional blogging activities, he’s an entrepreneur, event organizer, occasional board adviser and angel investor but most importantly an all-round startup champion. Wauters lives and works in... → Learn More

Friday, December 24th, 2010

As we reported yesterday, Facebook for a while blocked all j.mp short URLs provided by parent company bit.ly in status and page updates.

Asked for more information, Facebook said it was working with bit.ly to resolve the issue, and that more than 70% of j.mp links pointed to spam or “other security issues” at the time the block was imposed.

Thanks to our original tipster on the story, William Albano, we’ve now learned that j.mp links can now again be posted to Facebook walls worldwide.

For what it’s worth, bit.ly hasn’t said much about the blocking on its blog or Twitter account, but since they’re not disputing the 70% spam and malware claim from Facebook, we’re assuming that this was actually the case.

Shows you still need to be careful of which short URL you click – consider the source, primarily, and look for a browser extension that automatically shows destinations for short URLs, or take other precautions.

Company: bitly
Website: bit.ly
Launch Date: 2008
Funding: $30M

bit.ly allows users to shorten, share, and track links (URLs). Reducing the URL length makes sharing easier. bit.ly can be accessed through our website, bookmarklets and a robust and open API. bit.ly is also integrated into several popular third-party tools such as Tweetdeck. A more full list of third party tools can be found on the bit.ly blog. Unique user-level and aggregate links are created, allowing users to view complete, real-time traffic and referrer data, as well as location...

→ Learn more

blog comments powered by Disqus