zlacker

I've had similar thoughts. I've been sketching out a design where you can tag data with a location (a restaurant menu, say, which is only needed near the restaurant). Suppose the data is being gossiped between mobile devices. Some process which understands the user's past (and estimated future) movements can decide when the data can be forgotten.

Plus--as I imagine it--users would be able to trust each other in certain domains, so which fragments your device hangs on to is going to depend on who you trust and what you're interested in.

Hopefully, these combined would mean that whatever part of the web is relevant to your location is also the part of it that's already cached on your device or on a nearby one.