If I understand this correctly, the pushed information by the master isn't stored on the server (hosting the application) and then retrieved by the slave device?

But can the pushed information be intercepted by the server?

Does anyone know if there are more applications/experiments like this? I really like this idea (if I've understood the concept correctly).

As of server-less concepts, I only know http://peerjs.com/ which is based on WebRTC IIRC. The only server involved is typically a signaling server that does the pairing and is out of the game thereafter.

All other conecpts I know (http://sharejs.org/ , http://www.mobwrite.net/ and the likes) require a server.

Great Demo.

Yes, we tried server-less system on WebRTC. The problem is an actual support for WebRTC in mobile browsers. It is even less than HTML5. So, just wait for a moment.

Wait, so isn't it server-less? What HTML5 features are in use here?

Do you just send the message to the server and back to the other client?

How is this different than chat rooms we had 10 years ago?

It is server-based. Server-less version will be later as I wrote. Yes, it is like chat rooms, it is like client-server and it is like web. There is a web session actually :). We've tested a way for linking (pairing) two devices. From HTML5 there is File Reading API

We have been using a variant of this using websockets at work for about a year.