PeerServer: A Server in a Browser with WebRTC(peer-server.com)
peer-server.com
PeerServer: A Server in a Browser with WebRTC
http://www.peer-server.com/
26 comments
Won't connect for me (Fx 25, Linux). Blank white screen and this in the console:
TypeError: Not enough arguments to mozRTCPeerConnection.createOffer. @ http://www.peer-server.com/shared/lib/peer.min.js:1
TypeError: Not enough arguments to mozRTCPeerConnection.createOffer. @ http://www.peer-server.com/shared/lib/peer.min.js:1
Quite interesting idea.
On this we could have a distributed web server that scales as new ppl load the (site??). I can see this hurting akamai. People now have 10Mbps-20Mpbs up on DSL and cable; even before widespread FTOH this could become potent. It would also simplify a Tor alternative implementation, would'nt it?
On this we could have a distributed web server that scales as new ppl load the (site??). I can see this hurting akamai. People now have 10Mbps-20Mpbs up on DSL and cable; even before widespread FTOH this could become potent. It would also simplify a Tor alternative implementation, would'nt it?
> People now have 10Mbps-20Mpbs up on DSL and cable;
Are you talking about the bay area? I have never seen such an connection in a private home. (central and southern europe)
We have it here in Mtl Canada. It's fiber to the neighbourhood and a new hi-speed DSL link for the last 200-300M.
Here in Ukraine that's pretty common. I have 60 mbps for 9$/m, and that is quite normal in Kyiv.
guess what, in the bay area, connectivity up is generally even worse than that. For all the amazing internet companies here, the infrastructure for the public is pretty bad.
southern europe here (portugal) and in the cities it's pretty common
Congrats, I have been waiting to see someone build something like this for a while. This is truly a glimpse into the future :)
Edit: I should have vetted this a little harder before commenting. I recognized the idea immediately, but the implementation here is rather lacking. Still, props for pushing the envelop.
Edit: I should have vetted this a little harder before commenting. I recognized the idea immediately, but the implementation here is rather lacking. Still, props for pushing the envelop.
Erm, you guys did disable TURN right? (because otherwise the security value here is fairly decreased)
Firefox 25 (Linux):
"[22:21:01.082] TypeError: Not enough arguments to mozRTCPeerConnection.createOffer. @ http://www.peer-server.com/shared/lib/peer.min.js:1"
"[22:21:01.082] TypeError: Not enough arguments to mozRTCPeerConnection.createOffer. @ http://www.peer-server.com/shared/lib/peer.min.js:1"
Reminds me about Opera Unite.
Using profanity for needless shock value is not an effective way to get people to click your link.
(original title was along the lines of "Here's WebRTC, because F--K Servers.")
Capitalizing the 'K' was, though. Set off my OCD:)
What's wrong with fsck'ing servers?
Nice! Why not chrome, exactly?
Last I checked Chrome's DataChannels implementation was flakey and missing support for several attributes
This should no longer be true. Chrome v31 (http://googlechromereleases.blogspot.com/2013/11/stable-chan...) added SCTP support for reliable DataChannels and allowing compatibility with Firefox.
Chrome and Firefox DataChannels cannot connect with each other. Chrome and Firefox media connections can interop though
there are a few workarounds you have to use. there is a compatibility shim floating around somewhere (i think from mozilla).
[deleted]
We are planning to open-source the code and create a brief video showing off its abilities this weekend, as well as fix some of the issues you may be having in more recent versions of Firefox. The WebRTC DataChannel spec has been changing, so it works in FF 22 (beta at the time we developed it) but breaks for some later versions where the API changed. It'll be fixed over the weekend for FF and the latest Chrome -- sorry for the issues some are having now.
Thanks for the great comments and enthusiasm!