I was listening to music (on Grooveshark touch) while driving down the highway. The page refreshed and this came up, it was a very weird feeling.
This was the best music product I've ever used, and it was buggy as fuck sometimes. I used it so much I learned weird ways to get around the menu rendering issues on the html5/touch version of grooveshark. Even with its bugs it was my main music platform.
Thank you for your hard work. It was one of my favorite webapps.
Obvious beginner question here, what use cases would this work well for? I ran the the code you linked, and understand vaguely whats happening. Could this say, be used to distribute database requests to another server?
Excuse my slight condescending tone, but I don't think he really understands what twitter is for, and who benefits from its service. The model explained, which was tried by app.net, doesn't coincide with the real idea behind twitter in the first place.
A neighbor once said to me, we should pay to use the sidewalks in our city; I don't think she understood the ramifications of such a move, but it made sense in her mind because she /could/ pay for the sidewalk and the model worked for her. -yet she didn't understand that the sidewalk wasn't even necessarily meant for her. The same sides she paces, kids use to travel to school everyday, homeless persons use to panhandle, families use to travel to work everyday, and every once in a while some lune is up there with a sign expressing their view.
Twitter is no different. Sure we use twitter to post about our latest projects and greatest food pictures, however somewhere someone is using twitter to alert his friends that government and police are encroaching the neighborhood, quick alerting those near about a wildfire, or trying to start
Just because you could pay for want, doesn't mean someone else has the means to pay for necessity. I don't mind sharing a common good/service even though I know someone else might not be paying the same amount as I.
I think I just found my project. Stay tuned!