Slashdot Mirror


BitTorrent Sees Sync Users Share Over 1PB of Data

An anonymous reader writes with an update on the rapid adoption of BitTorrent Lab's Sync tool. From the article: "BitTorrent on Monday announced an impressive milestone for its file synchronization tool Sync: users have synced over 1PB of data. The company says over 70 terabytes are synced via the tool every day. BitTorrent first announced its Sync software back in January and released a private alpha. Between then and April 23, when the company release a public alpha, users synced over 200TB worth of data. In other words, over the past 13 days users have synced over 800TB of data. At this rate, the service will pass 10PB before even hitting a stable release."

14 of 56 comments (clear)

  1. How can they possibly know that number? by goruka · · Score: 5, Insightful

    I guess that's why it was closed-source only?

    1. Re:How can they possibly know that number? by UnsignedInt32 · · Score: 5, Informative

      As they are using BitTorrent technology, perhaps the metadata would contain size of data (number of blocks) to be transferred. Considering you can choose to NOT use a tracker, and go DHT (or pre-defined host) only, so probably there are some data transfer that are not accounted in this figure.

    2. Re:How can they possibly know that number? by masternerdguy · · Score: 5, Funny

      You can hide rootkits in your source code by setting their text color to white.

      --
      To offset political mods, replace Flamebait with Insightful.
    3. Re:How can they possibly know that number? by ChristianAverill · · Score: 5, Informative

      Hi, Christian here from BitTorrent. We updated our post to qualify this. Here is the update: "Sync was built for secure sharing. While we have general statistics about the app, we don’t have any access to private information. The client reports back anonymous usage statistics in the same way our other clients do. Sync uses this call to check if there’s a new build available. This call also contains some anonymous statistics that allow us to understand how Sync performs, and how it’s being used; data transferred directly, through relay, size of folders, and number of files synced. This is the only information we collect, and we left it open intentionally – so that people could see the data we’re collecting. That way, it can be easily verified that we don’t have access to any private information. Read more here: http://forum.bittorrent.com/topic/17002-btsync-calling-home/ "

    4. Re:How can they possibly know that number? by gshegosh · · Score: 2

      It's said in the linked forum thread that collected statistics are anonimized, but there's clearly an ID (id=htRWdGwwER-daEraerE) in the URL called. How is that anonimized, is beyond me.

    5. Re:How can they possibly know that number? by gshegosh · · Score: 2

      Sooo, what's the great fuss about cookies then? All they contain is some kind of ID, too -- right?

  2. Re:Am I misunderstanding this? by Ignacio · · Score: 2

    The fact that you in turn save encrypted copies of their data.

  3. Re:Am I misunderstanding this? by UnsignedInt32 · · Score: 4, Informative

    You only share among people with same shared key. So, no, you are not spreading your encrypted file to other people. At 1:1 it's pretty much direct peer-to-peer transfer. If more nodes are participating, then it can leverage distributed transfers from other nodes that may have part of the whole part of a file.

  4. Re:Am I misunderstanding this? by monkeyhybrid · · Score: 3, Informative

    I might be wrong but I was under the understanding that it is primarily aimed at syncing your own data between your own devices (think Dropbox but without a centralised file server). You could choose to sync it with other users but they would then have access to your unencrypted data.

  5. Re:Am I misunderstanding this? by Anonymous Coward · · Score: 3, Informative

    My understanding is that your data is only sync'd among your own computers. Specifically, when you create a shared folder, it has an associated secret (random string used as an encryption key), and only computers that have that secret have a copy of the data.

  6. Re:Am I misunderstanding this? by Fluffeh · · Score: 2

    Indeed, I thought this was going to be the perfect thing for say two friends to use as a backup method between each other - not so much a randon anyone on the internets has the backup... If it does pick users off the internet, I am less interested in it - I thought the concept of peer to peer based backup (but selecting your peers) was brilliant.

    --
    Moved to http://soylentnews.org/. You are invited to join us too!
  7. Re:Am I misunderstanding this? by complete+loony · · Score: 2

    FYI, they're transferring file blocks based on their hash. They aren't doing delta comparisons as this would require you to cache the previous version of the file. So if you insert a byte at the start of your file, expect the whole thing to be re-transferred.

    --
    09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
  8. Re:Am I misunderstanding this? by Burz · · Score: 2

    You only share among people with same shared key. So, no, you are not spreading your encrypted file to other people.
    At 1:1 it's pretty much direct peer-to-peer transfer. If more nodes are participating, then it can leverage distributed transfers from other nodes that may have part of the whole part of a file.

    I haven't tried it yet, but it sounds like Sync may accomplish the very significant task of getting users to easily share and manage (and use) keys like it was just something you do while working with your files.

    That would be far more significant than merely attaching a distributed filesystem to a P2P protocol.

  9. Re:Am I misunderstanding this? by Xylantiel · · Score: 2

    From reading the descriptions on the sync site... no. Anyone with the key can access the files. This provides some security, but it is pretty brittle. As long as everyone using it understands the level of security that should be applied to that key. i.e. anyone who steals the key can access the files. So, for example, never send the key over email.

    This seems like a reasonable solution for either just syncing personal files, where one individual has control of the key(s). Or syncing among a small technical group where everyone understands the relevance of the security of the key(s). Or syncing low-risk files among a less formal group. So it provides "some security" but you shouldn't really call it "secure", where "secure" would be per-user authenticated based on unique, private credentials for each user that they will not, in practice, give to others.