We used Firepad[1] (which is based on Firebase) to sync data.
What was the reasoning behind this decision? On one hand, it sort of acts like a phonetic alphabet if you want to read out the URL over skype. But on the other hand - is OberonNostalgicCeciliaVoltage really that easy to spell if you aren't a native English speaker?
http://web.archive.org/web/20090918202746/http://tothink.com...
a 4 character alpha-numeric code is 36^4 (1.6M) which is fine for new websites.
If you run out, add a 5th character which gets you to 60M, and a 6th character gets you 2T.
I think it's basically just as you say, for English speakers anyway, a bit of an easier way to read out URLs when talking in person or voice chatting. With non-English speakers it doesn't do much, and you're forced to say letter for letter as you would with a lot of other URLs.
But for a protocol, I think what EtherPad (and google wave) had done with cell by cell action is what's needed. If google wave had taken off (and actually implemented their federation concept), I could definitely see people creating plugins to send and receive character operations via a google wave server.
One question: before beginning the session I got a "popup" claiming that the session is encrypted, does it just mean it's https or are you doing any other encryption?
Getting these errors in dev console. Could not open document: [object Object]
webrtc works fine, but I'm unable to type anything...
