Thanks for getting this going and sharing your experience. It's really fun when it's interactive. I'd like to hope having 1000's in the same map with fast upda

Thanks for getting this going and sharing your experience. It's really fun when it's interactive. I'd like to hope having 1000's in the same map with fast updates, without being a huge burden to any one person is possible. Perhaps run a master instance at 1110.n01se.net Invite others to run a slave instance that is configured to connect to your master, report health, and serve areas as directed. The master serves the client and assigns a spawn point to the client to other interesting locations when load is high. It also manages the list of slaves and the areas covered and updates it with clients as it changes. (But there's a potential bottleneck here. Not sure how to do this yet... Also how do you subdivide the map so high traffic areas are smaller? I'm guessing Quadtrees so the subdivide data can be very small. How well can clients be connected to multiple servers? And is a master/slave relationship needed?) Well I'll leave it there. It's an interesting problem and I think it's part of what node.js is trying to become.