BCWNS Community Hotspot Portal System (BCWNS CHPS)
Contents
Intro-ducktion
The BCWNS CHPS is a project to deploy localized wireless networks that provide a gateway into the local physical community. Local events, businesses and residents should be able to interact with themselves electronically, and BCWNS CHPS will help accomplish this goal.
A hotspot is a localized network with a limited range (within an establishment or a local neighborhood, servicing the immediate vicinity). It is not an infrastrucural network.
Network owners operate a wireless access point such as a Linksys WRT54G. The access point may be range extended to cover more area of a building or even the neighborhood.
Visitors to the access point are greeted with a welcome page showing information about the access point's host and are asked to identify themselves using a username and password.
Some people have asked why we demand a username and password, rather than providing an anonymous gateway or "splash" page. Here's a few of our reasons:
- It's hard to interact with people when you don't know their name.
Requiring a username and password allows us to construct interactive tools such as instant messaging, BCWJxta peer to peer content and other directed content.
- Node owners should be able to see who is using their resource.
- Node owners should be protected from malicious users.
That being said, there's no reason why a person can't deploy a wide open network running NoCatSplash.
As of Februrary 7 2005, a basic service offering is available to hosts in the general population. The Society operates a simple hotspot server based on the WiFi Guard Dog (WifiDog) software written by Ile Sans Fil.
Once appropriate hardware and software has been obtained a BC Wireless user can register their hotspot through the Hotspot Manager in the WaveCaster system. Descriptive information about the hotspot can be entered and is used on the primitive portal page (such as directions on how to reach the CHPS site, maps, and a description). Additional links and basic content can be added by way of "RSS" feeds.
The costs for a CHPS site to deploy a public hotspot consist of a one time hardware charge (and any hardware upgrade costs) ($70-$200 depending on accessorization) along with their regular Internet service. Internet access from the hotspot is necessary to allow users to login and (possibly) view content, however a CHPS owner can elect to NOT allow visitors to use their Internet for general web surfing. We feel this is inline with the Society's goals of creating local digital communities, rather than propogating Internet access, but we feel the decision of whether to allow visitors general internet access can only be made by a network owner.
Long term goals and issues
Long term we seek to implement the following:
- A concept of user classes.
- A template driven portal content system
- Acceptable Use policies
Concept of user classes
At our January meeting we discussed the concept of user classes to help CHPS owners decide what level of security and trust they can use to determine how visitors can use their hotspot. At the very least all known users should be able to login to the local community network and interact with it.
The specific scenario we discussed was that of offering general internet access. BCWNS does not exist to propogate Internet access, our goals are to build up digital communities at a localized level. Some node owners may wish to offer Internet access and it was felt that the Society should not impose restrictions on node owners who wish to offer such a value added service. The other consideration was that of security, if a node owner does wish to offer Internet access what can we do to help prevent abuse of their broadband connection?
We came up with this plan:
- Keys:
Class Name
Description
Welcome page
Interact with the local community
Access the Internet
Anonymous
Anyone without a valid BCW account
General user
Anyone with a valid BCW account
BCW Participant
Anyone who participates in the BC Wireless project (a node owner, someone who has donated rights of way or other tangible resources, etc.)
Node Owner
The person who runs the specific node
- - yes
- - no
- - discretionary
These user classes should provide metrics of trust based on a persons involvement with the BC Wireless Community at large. An anonymous user is limited to local content, while a general user is allowed to roam freely. A BC Wireless participant (that is, someone who provides tangible, inkind contributions to the BC Wireless project) should be more trusted than a registered user, and a node owner may choose to allow those participants a greater level of access (perhaps as a Thank you).
It should be mentioned that the idea of denying Internet access to general users and not participants is based around the assumption that people who contribute tangible resources into the rest of the project's efforts would be more trusted than anyone who simply created a user account and validated their Email address.
Of course a node owner themselves should be able to access any resource they choose, including unlimited Internet access.
Portal system
This topic has been briefly discussed amongst volunteers but still needs a fair bit of discussion. For now we will begin developing a system and talk with test sites to find out their needs.
The portal is the page displayed after a succesful login, this portal page should display information about the CHPS host as well as information about the local community.
The present portal system is a single page "template" that fills in content from pre-defined fields within the hotspot's database entry. It is able to display dynamic content through the use of RSS/XML feeds in a consistent-stylized manner. Hotspots owners are not forced to use the portal system, they can direct a logged in user to their own home page as well.
We could develop a number of modules to enhance the functionality of a portal page, some ideas are:
stylized rss boxen
local events db-backend
guestbook module
shoutbox module
maps ui
community directory
news paper
swap/shop
forums
Communifying distributed content
(a brain fart in progress)
Assuming that network owners will want to host their own local content, or may even have an existing website they'd prefer to use, we should look at ways to make a website "community aware".
An API could be developed that allows a website hosted "elsewhere" (not on the portal server or the user's hotspot device) to become aware of community wireless users. At a very minimum, the API could determine a person's screen name or userID to allow the website to provide interactive content such as discussion forums, instant messaging and other similar services. The ability to distinguish a local wireless user from a remote visitor would enable the website to provide custom content relevent to current happenings.
This type of functionality also has the added benefit of keeping the network decentralized, with the exception of the central authentication service.
... insert ideas here ...
MichaelLenczner has some good ideas.
Usage Policies
As a Society we will need to formulate some policies to outline expectations and responsibilities to ensure everyone knows where they stand. For now the general policy is place nice but long term we will need to talk about this.
BCWNS maintains the node list and the user database, node owners do not have access to confidential user information and users do not have access to confidential node information. In compromising situations BCWNS can serve as a neutral party in conflict resolution between a node owner and user.
Node owners
Some thoughts:
- Node owners can't charge for access to their networks
- Node owners must respect the privacy of their users
- Node owners have a right to privacy from their users
User policies
Some thoughts:
- Users can not abuse a node for criminal or illicit gain.
- Users have an expectation to privacy
