_serverless_ file sharing says title, yet the technology "requires a HTTP server". "Its completely anonymous as no data is ever stored on the server". Incorrect, only mild protection against sniffing and spoofing is provided.
The underlying code documentations speaks of "This makes it perfect for anonymity": https://github.com/ShirsenduK/WhatAreYouDownloading/tree/mas...
No PKI is linked or included. Proxy service or Sender/receiver unlinkability is not provided. The used WebRTC technology limits UDP/TCP listen sockets. Browser constraints mean WebRTC offers a severely limited experience. For instance, the state of the art in UDP NAT traversal using the neighbor-invite method (beyond STUN/TURN) is not possible.
Rant Disclaimer: As an academic working on a real deployed zero-server P2P technology for 7 years, this sort of claims are a bit upsetting. Zero-server file sharing systems, with a proven effective spam/pollution prevention mechanism have been proven to be extremely difficult to build. (e.g. no-spam version of Kazaa,Gnutella) See,
https://torrentfreak.com/tribler-makes-bittorrent-impossible...
Tribler research group created an upcoming IETF Internet Standard on sharing/streaming which features integrated NAT/firewall puncturing (IETF PPSP work). Compliant IETF PPSP implementations are capable of doing HD-quality streaming, both on-demand and live streaming: https://datatracker.ietf.org/doc/draft-ietf-ppsp-peer-protoc...
Sorry for the misleading title. By serverless I meant direct browser to browser file transfer with no server in between. Files are transferred directly. We need the HTTP Server to host the static webpage which facilitates the bridge. After all, its a browser based solution you need a page to visit. :). Services file dropbox can be used to host the static files and everyone can setup their own file transfer service. With services like WebDHT coming up each of these shares can communicate.
Just read about Tribler, it sounds really interesting. All the best with it.
This, Tribler and countless other solutions will make the internet what it was meant to be, a decentralized, fault-tolorent network for information exchange. Thanks!
Strictly speaking, PPSP is a swarm transport protocol ("give me that data over IP, UDP or what have you, use any source available"). I mean, "sharing" is a concept unrelated to the TCP/IP stack thus PPSP is not a sharing standard.
For example, it is easy to imagine HTTP over PPSP (instead of TCP) -- which is essentially a serverless Web.
This currently works only on the latest browsers; like Chrome 24 on the desktop. Its still not 100% stable. Stability and support for other platforms will soon arrive through browsers updates and polyfills.
Why is everyone thinking about torrenting in browsers? I want a service where I can select a sensitive file, give my associate a link, and have that file transferred between our two computers without ever reaching an intermediate server.
Does anyone know of a service like that, easy enough for my father to use?
[+] [-] synctext|13 years ago|reply
_serverless_ file sharing says title, yet the technology "requires a HTTP server". "Its completely anonymous as no data is ever stored on the server". Incorrect, only mild protection against sniffing and spoofing is provided.
The underlying code documentations speaks of "This makes it perfect for anonymity": https://github.com/ShirsenduK/WhatAreYouDownloading/tree/mas... No PKI is linked or included. Proxy service or Sender/receiver unlinkability is not provided. The used WebRTC technology limits UDP/TCP listen sockets. Browser constraints mean WebRTC offers a severely limited experience. For instance, the state of the art in UDP NAT traversal using the neighbor-invite method (beyond STUN/TURN) is not possible.
Rant Disclaimer: As an academic working on a real deployed zero-server P2P technology for 7 years, this sort of claims are a bit upsetting. Zero-server file sharing systems, with a proven effective spam/pollution prevention mechanism have been proven to be extremely difficult to build. (e.g. no-spam version of Kazaa,Gnutella) See, https://torrentfreak.com/tribler-makes-bittorrent-impossible... Tribler research group created an upcoming IETF Internet Standard on sharing/streaming which features integrated NAT/firewall puncturing (IETF PPSP work). Compliant IETF PPSP implementations are capable of doing HD-quality streaming, both on-demand and live streaming: https://datatracker.ietf.org/doc/draft-ietf-ppsp-peer-protoc...
[+] [-] ShirsenduK|13 years ago|reply
Just read about Tribler, it sounds really interesting. All the best with it.
This, Tribler and countless other solutions will make the internet what it was meant to be, a decentralized, fault-tolorent network for information exchange. Thanks!
[+] [-] gritzko|13 years ago|reply
For example, it is easy to imagine HTTP over PPSP (instead of TCP) -- which is essentially a serverless Web.
[+] [-] dgit|13 years ago|reply
[+] [-] janerik|13 years ago|reply
http://tmp.fnordig.de/scr/aacc737f52.png
[+] [-] ShirsenduK|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] piranna|13 years ago|reply
[+] [-] nextparadigms|13 years ago|reply
[+] [-] ShirsenduK|13 years ago|reply
[+] [-] pre|13 years ago|reply
Has that requirement been dropped? Or does this do something strange to get around it?
[+] [-] iSnow|13 years ago|reply
[+] [-] ShirsenduK|13 years ago|reply
[+] [-] StavrosK|13 years ago|reply
Does anyone know of a service like that, easy enough for my father to use?
[+] [-] ShirsenduK|13 years ago|reply
[+] [-] jaip|13 years ago|reply
[+] [-] plusfour|13 years ago|reply
It works on most browsers
[+] [-] pranny|13 years ago|reply
[+] [-] joelthelion|13 years ago|reply
That would have a far greater impact than yet another file-sharing system.
The architecture would basically be a flooding P2P network with measures against spamming (machine learning?).
[+] [-] icebraining|13 years ago|reply
[+] [-] ShirsenduK|13 years ago|reply
[+] [-] loceng|13 years ago|reply
[+] [-] kybernetikos|13 years ago|reply
[+] [-] ShirsenduK|13 years ago|reply
[+] [-] davedx|13 years ago|reply
[+] [-] StavrosK|13 years ago|reply
> by @prianna
yet the link goes (correctly) to @piranna. It irks me to see people's names misspelled in attributions.
[+] [-] ShirsenduK|13 years ago|reply
[+] [-] plusfour|13 years ago|reply
[+] [-] bartl|13 years ago|reply
[+] [-] ShirsenduK|13 years ago|reply
[+] [-] jaip|13 years ago|reply
[+] [-] roothacker|13 years ago|reply
[+] [-] aoprisan|13 years ago|reply
[+] [-] wildmXranat|13 years ago|reply