From what I see, this isn't about creating a mesh network for many users, its about enabling communication with your friends or co-workers in places where there isn't network access. So in that sense, there is no chicken-egg problem. I was just wishing for something like this when skiing in Whistler last weekend so I could communicate with my friends without using int'l data/roaming.
I was born and raised in the Traverse City area. The Great Lakes have become remarkably clearer throughout the years. I was told that it was due to the invasive species of Zebra Mussels[1] which have no natural predators in the Great Lakes. As their population exploded, they have significantly increased the clarity of the water.
I didn't live there, but my grandparents did and my family summered there (on Long Lake) every year from the early 80's thru the last few years. I snorkels and later dove in Lake Michigan and surrounding connected and non-connected lakes. The water definitely got more clear in the 90's and 2000's to my unscientific eye.
It's beautiful country up there. Nothing much compares, to me, to northern lower-peninsula Michigan summers.
This has always been my concern (perhaps naive) with any (not just this) javascript SDK. It seems that it would be very easy, and almost inviting, for a malicious user to script a spam attack using the javascript console in their browser, and perform a large number of inserts to the database before you can detect this and disable their account.
Are there common javascript development practices or conventions to prevent malicious users from writing an infinite loop (as pseudo-coded in the post above) and spamming your data set?
