5 ms·

Peerbind: convert a webpage into a massively interconnected website

37 points by bpierre 15y ago

rmc 15y ago
Right now it looks like a website that's down.
- mamacker 15y ago
  Sorry it fell over - its back up.
  - buss 15y ago
    If this is matt@, I really enjoyed the internal tech talk at the SLU campus a few months ago. During Q&A, I asked if any of this was going to be open sourced, has that changed? Also, did you fix that javascript code execution vulnerability I found during the demo? :P
    - mamacker 15y ago
      Still not open-sourced. Amazon-licensed. Yup. ;)
chetan51 15y ago
What does it do?
- jchrisa 15y ago
  Looks like some form of cross domain message bridge, along with some DOM code to transparently turn the messages into events. Odd that something so simple would have a proprietary server.
azharb 15y ago
Cache - http://webcache.googleusercontent.com/search?q=cache:http://peerbind.com/ http://webcache.googleusercontent.com/search?q=cache:http://...
buss 15y ago
This was demoed to Amazon developers internally, and is immensely cool. The main demo involved having all of the developers pull up the slideshow on their laptops, and everyone's instance of the slideshow followed along with matt's instance (when he advanced a slide, we all did automatically). The latencies were fantastic, too. If you're looking to do real-time many-user interactions on a website with minimal effort, try this!
- Palahala 15y ago
  Nice! Any chance you know if (and where) we can report issues? One possible issue: It seems that binding to the same peer-event multiple times, also SENDS all outgoing events multiple times. For example, open the example website peerbind.com and then run: $('#chatinput').peerbind("change", { peer: function(e) { console.log("Incoming", e.peerSrc, e.peerData); } }); Now, by simply binding to incoming events twice, everything one sends in the chat, is sent twice too. I guess that's not the expected behavior? Still, nice! And for those who agree that the chat example is not very secure: peek into the HTML source for the actual implementation! ;-)
  - mamacker 15y ago
    Good find! Thanks, I'll take a look. If you see anything else wrong - feel free to send me a note: matt@a9.com
______ 15y ago
It's interesting how anonymous users just now were engaging in fun ways just by dragging -- moving the squares on top of each other, or in a line, or back in order -- without being explicitly told what to do. Of note, node.js and Socket.IO make this kind of demo quite easy to do, if you want to do it with open technologies

37 points by bpierre 15y ago

rmc 15y ago

Right now it looks like a website that's down.

mamacker 15y ago
Sorry it fell over - its back up.
- buss 15y ago
  If this is matt@, I really enjoyed the internal tech talk at the SLU campus a few months ago. During Q&A, I asked if any of this was going to be open sourced, has that changed? Also, did you fix that javascript code execution vulnerability I found during the demo? :P
  - mamacker 15y ago
    Still not open-sourced. Amazon-licensed. Yup. ;)

chetan51 15y ago

What does it do?

jchrisa 15y ago
Looks like some form of cross domain message bridge, along with some DOM code to transparently turn the messages into events. Odd that something so simple would have a proprietary server.

azharb 15y ago

Cache - http://webcache.googleusercontent.com/search?q=cache:http://peerbind.com/ http://webcache.googleusercontent.com/search?q=cache:http://...

buss 15y ago

This was demoed to Amazon developers internally, and is immensely cool. The main demo involved having all of the developers pull up the slideshow on their laptops, and everyone's instance of the slideshow followed along with matt's instance (when he advanced a slide, we all did automatically). The latencies were fantastic, too. If you're looking to do real-time many-user interactions on a website with minimal effort, try this!

Palahala 15y ago
Nice! Any chance you know if (and where) we can report issues? One possible issue: It seems that binding to the same peer-event multiple times, also SENDS all outgoing events multiple times. For example, open the example website peerbind.com and then run: $('#chatinput').peerbind("change", { peer: function(e) { console.log("Incoming", e.peerSrc, e.peerData); } }); Now, by simply binding to incoming events twice, everything one sends in the chat, is sent twice too. I guess that's not the expected behavior? Still, nice! And for those who agree that the chat example is not very secure: peek into the HTML source for the actual implementation! ;-)
- mamacker 15y ago
  Good find! Thanks, I'll take a look. If you see anything else wrong - feel free to send me a note: matt@a9.com

______ 15y ago

It's interesting how anonymous users just now were engaging in fun ways just by dragging -- moving the squares on top of each other, or in a line, or back in order -- without being explicitly told what to do. Of note, node.js and Socket.IO make this kind of demo quite easy to do, if you want to do it with open technologies