FANDOM


TorrentFreak.com (commonly referred to as TorrentFreak) is a weblog dedicated to reporting the latest news on the BitTorrent protocol and anything closely related to it. TorrentFreak was started in November of 2005 by a Dutchman named Ernesto.[1] He added Smaran to his staff in September of 2006, and he added Enigmax to his staff in February of 2007.[2]

TorrentFreak is listed in Technorati's top 100 blogs[3] and among the 50 most popular domains featured on the frontpage of Digg.[4]

Comcast BitTorrent ThrottlingEdit

On August 17th, 2007 TorrentFreak reported that Comcast had begun throttling its upload bandwidth, specifically against BitTorrent users. This made seeding, which is an essential part of the BitTorrent protocol, effectively impossible.[5] It was later determined that Comcast was using Sandvine products which implement network traffic shaping and policing, and include support for both blocking new and forcefully terminating established network connections. Comcast has denied these claims whenever they have been asked to comment. A guide, for customer service representatives when asked about Comcast's BitTorrent throttling, was leaked to the Consumerist on October 26th, 2007.[6]

ControversyEdit

In October of 2007, TorrentFreak was criticized for attributing the temporary shutdown of the Demonoid.com BitTorrent Tracker to the CRIA, when nobody had knowledge of the true reason for the downtime. It was later revealed that TorrentFreak was, in fact, correct in its assertion that Demonoid was shutdown by the CRIA.[7]

External linksEdit

ReferencesEdit

Template:Reflist

This page uses Creative Commons Licensed content from Wikipedia (view authors). Smallwikipedialogo.png


From BitTorrent Wiki, a Wikia wiki.

Cite error: <ref> tags exist, but no <references/> tag was found

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.