It seems similar to what Peersm project (http://www.peersm.com) intends to do via node-Tor (https://github.com/Ayms/node-Tor)
In its current form browsers are connected to Tor nodes, as well as Peersm clients (https://github.com/Ayms/node-Tor/tree/master/install) who are bridging to the bittorrent network. Despite of the several encryption/hash computation for each Tor packet we get a rate of 2 Mbps which is normally enough to stream (but we limit this rate to 1 Mbps currently), the limitation comes more from the transcoding of the files to adapt them so they can be played by browsers (https://github.com/Ayms/torrent-live#transcoding-and-file-conversion). Currently you get data anonymously from one peer, not several ones, it's obvious that the Tor network is too small to implement a P2P network on top of it. So the final phase (https://github.com/Ayms/node-Tor#anonymous-serverless-p2p-inside-browsers---peersm-specs) is designed to be a P2P network with browsers as peers communicating via WebRTC using the Tor protocol but not the Tor network. Another (complementary or different) idea could be that browsers are connected to Tor nodes using Websockets (like Peersm phase 1) and implement a complete Tor relay (not only the Onion proxy function as Peersm is doing), then relaying data with other browsers and exiting whether in the clear (like uProxy) or to the Tor network via Websockets again. One of the issues of this model is the limitation induced by the upload bandwidth of the peers, so a traditional Tor connection should use different circuits and peers to exchange data, and not only one circuit, which implies some modifications of the Tor protocol. Le 17/01/2016 13:08, Fabio Pietrosanti (naif) - lists a écrit : > Within the Italian Nexa Center for internet and Society mailing list, > there was recently a discussion on the IP-level blocking forced by the > government's judges to ISPs against "informal/unofficial" football video > streaming services. > > I learned that those kind of services, usually provide browsers plug-in > to distribute the streaming in a semi-p2p-bittorrent-way. > > Btw, the IP-blocking regardless of the reasons, is basically censorship. > > I was wondering if Tor network couldn't be a network/platform for that > kind of video-streaming-services. > > Obviously the problem is that video-streaming require a lot of bandwidth > and massive-services attract a lot of users, so even brainstorming > something about it, would imply thinking a network/application design > that does not increase linearly the bandwidth resources required for > each new user. > > So, it come up to my mind that in MAN (metropolitan area network) that > share a common network topology and software, multicast is used for that > kind of purposes. > > On my italian fiber service provider Fastweb, when i use their own TV > with their own set-top-box and click "Channel X", there's basically a > "join" to a multicast group, that will then deliver me the streaming and > in their network topology there are "edges" that does cache and > redistribute the content. > > So, i was wondering if the multicast streaming concept for content > distribution with edges-caching, couldn't fit somehow in a future Tor > network use-cases or design. > > -- Get the torrent dynamic blocklist: http://peersm.com/getblocklist Check the 10 M passwords list: http://peersm.com/findmyass Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org Peersm : http://www.peersm.com torrent-live: https://github.com/Ayms/torrent-live node-Tor : https://www.github.com/Ayms/node-Tor GitHub : https://www.github.com/Ayms -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
