The following is a fictional scenario. It’s an example of what could happen with the local web.
The “enforcers” at PAX have a hard and rewarding job. Being the spine and lifeblood of the show, they are tasked with making sure everything goes according to plan and attendees have a great time.
To pull this off they use the local web to setup quick and temporary local “channels” to communicate on. There is /u/enforcer.comms for general communications, and /u/enforcer.zoneleaders for the zone leaders to communicate on, and /u/enforcer.questions for the new enforcers to get their questions answered. The /u/ in each of these URLs means that it’s unlisted from the local web front page. The only way you can access these “slashes” is if you know the URLs, and only the enforcers know them.
They work a bit better than a group communication app because it’s not an app that everyone has to download. It’s a simple URL that anyone can access, as long as they know the URL. If the URL leaks online, it’s really not a huge deal because content on the local web is location based so anyone outside of Boston won’t see anything posted to /enforcer.comms.
PAX is a big deal and there is a lot going on that only lasts a few days. Permanent repositories of information like forums have their place, but they are often not real-time or perform poorly on mobile. The organized chaos of PAX lends itself to a decentralized and mobile based communication system, which is exactly what the local web provides.
Note: PAX is not officially affiliated with the local web. The above is just an example of what could happen when the local web launches at PAX East in April.
We are building the local web and sharing a new way to use it each day.
Signup at localweb.is