Update on BitTorrent Chat

BitTorrent was founded on a few simple core principles. Uphold user privacy, and user control. Keep the web free, open, and accessible to all.

This is what keeps us up at night. And this is what keeps us coding. Every two months, we dedicate two days to all-company hackathons (Paloozas, we call them). It’s free time to build and vet distributed concepts. And it’s often where awesome ideas come from. Winners of these events graduate to BitTorrent Labs. BitTorrent Sync came from Palooza. So did Bundle.

Over the past 6 months, it’s become increasingly clear that we need to devote hackathons, hours and resources to developing a messaging app that protects user privacy. We’ve seen this basic right of communication compromised, over and over again, in 2013. User control has become a casualty of centralization. The thing is, Internet doesn’t need to work this way.

Current chat apps rely on centralized, cloud-based servers that store user messages. This is true even of “private” messaging services, like Snapchat.

And that means they’re vulnerable: to hackers, to NSA dragnet surveillance sweeps. While we’re hearing legislative calls to curb domestic spying, and corporate assurances regarding user privacy, we can’t rely on these systems. Statements like “just because we can, doesn’t mean we should” don’t guarantee user privacy. They do guarantee provider access: we can.

As Joshua Kopstein pointed out last week in The New Yorker’s Elements Blog, decentralized systems can solve for surveillance, privacy, and more. Distributed products create infrastructure efficiencies. They prevent single points of failure. And they put end users in control of data. Not the cloud. Technology can solve what legislation cannot.

And that’s where BitTorrent Chat comes in. We’re building a product that allows you to talk to your friends using peer-to-peer. No central authority required.

121713-bt-chat-blog-2

We put out a call for testers in September, and have received an enthusiastic response. Today, BitTorrent software engineer Abe Goldoor explains our unique technical approach to creating a serverless chat product. In our solution, the Distributed Hash Table (DHT) replaces the need for a server when two people are trying to connect. You can read about that here.

In a related post, BitTorrent’s Chief Architect Arvid Norberg shares an update to the DHT bootstrap server. This update makes it open source and also refines the security, a step toward building BitTorrent Chat.

Sign up for the BitTorrent Chat Alpha.

Sign Up
christian
Written by: christian

Christian Averill is the Vice President of Marketing for BitTorrent, Inc.

 Related Posts:

8 Responses to “Update on BitTorrent Chat”

  1. Joe

    The question on everyone’s mind since day one is if the application and/or the protocol will be open source. BitTorrent really needs to make a statement about this so people will know whether or not to look forward to BT Chat, since it will be quite pointless if not OSS.

    Reply
    • Ast

      I second that. At least the protocol should be open source, so it can be checked and — maybe even more importantly — implemented in other chat software.

      Reply
  2. Evan Peters

    It might take off, but I and so many others will not use it. Open-source is the best, even Microsoft starts to understand that.

    Reply

Leave a Reply

  • (will not be published)

Trackbacks and Pingbacks:

  1. BitTorrent Chat Alpha: Private instant messaging via secure, distributed technology | Privately Investigating

    […] sweeps,” Christian Averill, BitTorrent’s director of communications said in a blog post. “While we’re hearing legislative calls to curb domestic spying, and corporate […]

  2. Bittorrent Develops Secure, Decentralized Chat Program Using Public-key Crypto

    […] sweeps,” Christian Averill, BitTorrent’s director of communications said in a blog post. “While we’re hearing legislative calls to curb domestic spying, and corporate […]

  3. BitTorrent Chat to fix the privacy message issues

    […] Source: BitTorrentBlog […]