BitTornado Bans All BitComet Users
BitTornado developer John Hoffman, better known as Shad0w, decided to ban BitComet users from accessing his client. Shad0w says that BitComet is gaming the system and stealing precious bandwidth, which results in slower speeds for all non-Bitcomet users.
Context & Ripple Effects
With no tracker operator or court involved, this is a unilateral move by a single client developer: John Hoffman (Shad0w) has confirmed that his BitTornado client now refuses connections from BitComet entirely, on the grounds that BitComet gamed the torrent system and was 'stealing' bandwidth at the expense of every non-BitComet user in the swarm.
First-order effects
- Every BitComet user attempting to download a torrent through a BitTornado-seeded swarm is cut off immediately, shrinking BitComet's effective peer pool on any swarm where BitTornado clients participate.
Second-order effects
- Other mainstream client developers now face the same choice Hoffman made — tolerate what he characterizes as protocol abuse or lose users who blame their client for slow speeds — making client-to-client banning a live template rather than an experiment.
Third-order effects
- If client-level bans spread, swarm access becomes contingent on behaving like an approved client, moving enforcement of sharing norms out of tracker administration and into the code of the clients themselves — with each developer acting as gatekeeper under standards nobody formally agreed.
The trend: BitTorrent governance is drifting from shared-protocol neutrality toward client-side enforcement, where individual developers decide which peers deserve bandwidth.