BitTorrent Blog

I love that Thom and Nigel continue to experiment in this space, and having been previously unfamiliar with Bundle I was pleasantly surprised to see that several of my favorite artists/labels have released material via this channel in recent months. But I'm not sure if I really see the benefit of this (for artists or listeners) over e.g. Bandcamp, and the more I dig into BT's messaging about Bundle[0] the less I feel I understand about the overall strategy. [0]http://blog.bittorrent.com/2014/06/16/bittorrent-bundle-hits-100-milli…

OwnCloud is quite nice, but its Dropbox-like feature isn't his best asset. We have big shared folders and the client app does weird stuff sometimes (and given the way things are architected, I'm not confident it will change). On the other hand, it gives you a nice web-based file browser, CardDav, CalDav, and a RSS webapp. And there's a basic iPhone app. The approach posted somewhere else in the comments[0] seems interesting. Use BTSync for the synchronization, and put ownCloud over that for the web interface and other goodies. I'm tempted to experiment with that. [0] http://blog.bittorrent.com/2013/05/23/how-i-created-my-own-personal-cl…

I really liked the implementation listed out on this site. I went through it and it was a great learning experience. You also get a sweet web interface with owncloud. http://blog.bittorrent.com/2013/05/23/how-i-created-my-own-personal-cl…

I plan on setting up a cloud system using BitTorrent Sync, Owncloud, and a Raspberry Pi. There's a great article on it, if you're interested. [1] [1] http://blog.bittorrent.com/2013/05/23/how-i-created-my-own-personal-cl…

https://blog.bittorrent.com/2018/07/23/its-official-bittorrent-is-now-… The announcement is dated 23rd July 2018. https://www.airoav.com/wp-content/uploads/2019/07/image14.png The certificate for the malware is stamped 4th September 2018.

> Apps have been free to abuse UDP all this time, but it's not been a real issue. Even data-hungry applications like video-streaming have gone with TCP almost every time. In the past Bittorrent and the creation of the µTP prooved ( http://blog.bittorrent.com/2009/11/13/testing-%C2%B5tp-is-%C2%B5tp-act… ) that unmanaged protocol abuse in userspace can lead to big degradation in QOS yes. Mainly due to "unfair" congestion policy between protocols.

Nice, not even 4 months after releasing this. http://blog.bittorrent.com/2018/06/19/user-message/

Announcement on Bittorrent Blog: http://blog.bittorrent.com/2016/06/16/bittorrent-inc-separates-out-syn…

> "Powered by our proprietary and patented peer-to-peer live streaming protocol," And now I care about this much less... source: http://blog.bittorrent.com/2016/05/17/bittorrent-live-multichannel-app…

All limits were removed in 2.2 http://blog.bittorrent.com/2015/09/09/sync-2-2-now-available/

In principle this is not a problem in a peer to peer network as long as there are peers. You simply store the message encrypted on enough peers that are in the swarm. It seems though that they store the message on the sender's device until the peer becomes available: http://blog.bittorrent.com/2014/11/21/offline-messages-come-to-bleep/ Edit: it is fully asynchronous now: http://blog.bittorrent.com/2014/12/22/bleep-now-supports-asynchronous-…

Moreso than decentralized web I think he means decentralized site. Most sites are served by just a few servers. I think bittorrent is working on this with a project called Maelstrom: http://blog.bittorrent.com/2014/12/10/project-maelstrom-the-internet-w…

It doesn't look like ipfs has human friendly named pointers yet either? At least that's what I gather from their documentation: http://ipfs.io/docs/commands/#ipfs-name In answer to your question: bookmarks have been a long standing solution to remembering names. I absolutely understand that it's not the most ideal solution - but hopefully acceptable for a beta. Unfortunately, the linked to TechCrunch article doesn't do much to explain how the browser works. One of the original-source blog posts does a (slightly) better job of explaining how things work - or at least points you in the direction: http://blog.bittorrent.com/2015/04/10/project-maelstrom-developer-tool… The hashes directly represent the infohash for the created torrent website.

Hmmm... http://blog.bittorrent.com/2014/12/10/project-maelstrom-the-internet-w… See also: https://www.tahoe-lafs.org/trac/tahoe-lafs

Is this like Popcorn Time for Wikipedia? I think Bittorrent is also working on a similar project for the whole web, called Maelstrom: http://blog.bittorrent.com/2014/12/10/project-maelstrom-the-internet-w…

I don't know yet if BitTorrent has pulled this off in a way that is reliable, secure, truly decentralized and easy-to-use, but this at least points to future we want. They claim[1], "Bleep offers the freedom to communicate without the risk of metadata being exposed.", and that it is good for "Journalists communicating with sources without exposing their identity or their content." This line worries me: "In typical Silicon Valley fashion, we’ll evaluate monetization models down the line." I'm sure idlewords (Maciej Ceglowski) would agree. [1] http://blog.bittorrent.com/2014/07/30/bittorrents-chat-client-unveiled…

It wouldn't be the craziest thing people do with docker: http://blog.bittorrent.com/2013/10/22/sync-hacks-deploy-bittorrent-syn… http://blog.docker.io/2013/07/docker-desktop-your-desktop-over-ssh-run… There has been discussion of taking the git analogy further. We actually experimented with a lot of that early on (https://github.com/dotcloud/cloudlets) and I can tell you it's definitely possible to take the scm analogy too far :) I do think we can still borrow a few interesting things from git. Including, potentially, their packfile format and cryptographic signatures of each diff. We'll see! Here's a relevant discussion thread: https://groups.google.com/forum/#!msg/docker-user/CWc5HB6kANA/oHyw-rgj…

I completely agree. Any potential benefits are far outweighed by the project not being open sourced. "Our goal is to build a sharing tool that lets you move big files, and big ideas, freely. Without surveillance." [1] Unfortunately without proof this sort of marketing sounds like "give us all of your data, we won't look, we promise." ... I may be a little cynical because I like the idea of decentralized sync. [1] http://blog.bittorrent.com/2013/11/05/introducing-bittorrent-sync-1-2/

They released support for file recovery a few days ago, along with their android app (http://blog.bittorrent.com/2013/07/17/now-in-beta-bittorrent-sync/). Instructions to recover files and set the recovery history time here: http://forum.bittorrent.com/topic/16410-bittorrent-sync-faq/.

I agree, Owncloud is getting quite mature. Combined with a Raspberry Pi and BitTorrent Sync (http://blog.bittorrent.com/2013/05/23/how-i-created-my-own-personal-cl… you got yourself well started...

And where are the files stored? If I create a 'Sync'ed file, switch off the computer and start the laptop, the file needs to be stored somewhere. And if this somewhere is the torrent swarm, then I would expect an interesting discussion on cryptography and (perhaps) fountain codes etc. ( Unfortunately the blog post [1] is even less detailed than OP's submission.) [1] http://blog.bittorrent.com/2013/01/24/test-bittorrent-sync-pre-alpha/

The original article: http://blog.bittorrent.com/2010/05/21/%C2%B5tp-open-source-implementat… Though I think ars explains it better.

(Full disclosure: movies.io admin here) Right now, it's hard to tell. I like that their current protocol is published as an IETF draft [1], but it doesn't include anything about their 'proxy layer' which is touted in the TF article. From the details in this article, it seems to work a bit like Tor, which raises a few questions: who is going to run the ProxyNodes: is that their business model: making people pay a subscription to access their vast network of ProxyNodes? (Will they claim innocence because "they don't inspect the content passing through", even though it'll be mostly pirate content). PPSP (the IETF version) looks like a more modern and lightweight BitTorrent that runs on UDP. I like that, but as every network, we'll have to see the adoption rate. People stay on BitTorrent the same reason they stay on Facebook: everybody's there. The Tribler guys are not the only one to want to do P2P on top of UDP though: uTorrent came out much sooner (and with reasonably good adoption) with μTP [2]. [1] https://datatracker.ietf.org/doc/draft-ietf-ppsp-peer-protocol/?includ… [2] http://blog.bittorrent.com/2009/10/05/changing-the-game-with-%CE%BCtp/