31–40 of 72 posts
I'd like to see this technology used to build a decentralized, uncensorable alternative to twitter or reddit. 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?).
I'd like to see this technology used to build a decentralized, uncensorable alternative to twitter or reddit. 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?).
Earlier quoted context omitted.
this is exciting. Only Chrome24 supports it, but sooner all browsers will.
I'm running Chrome 24.0.1312.56, on Mac OS X 10.8.2, yet I still get the alert about unsupported browsers...
I'd like to see this technology used to build a decentralized, uncensorable alternative to twitter or reddit. 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?).
Wouldn't this require each computer on any receiving end to process all of the incoming data in order to determine if it's spam or not?
Also, you could also select peers for the quality of the content they forward to you.
_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...
Earlier quoted context omitted.
WebRTC is for Real-time communication between browsers. Same-origin policy applies to communication between browser and the server. http://www.w3.org/TR/webrtc/ . There are ways to turn it off on your browser, but why would you? :). The tech is yours to be used.
> The tech is yours to be used. Well, the tech is for every website to be used, as a visitor to the site that may or may not benefit me. I think that was the reason for the same-origin policy and is, probably the source of concern of the OP. Personally, I use NoScript and RequestPolicy to deal with it. After all, just because JavaScript exists does not mean I want any random website to execute arbitrary code on my ma…
Isn't the browser supposed to stop pages from making connections to machines other than the server they were downloaded from? Has that requirement been dropped? Or does this do something strange to get around it?