Abstract: A system and method for a user to send presence information to authorized contacts in her device's address book and to receive the presence information of those contacts in her device's address book that have authorized her. A user can authorize any contact in her address book. Optionally, a user can only authorize a contact and be authorized by a contact if she is in that contact's address book. A local application on the device interacts with and displays the device's address book, manages the authorization of contacts, updates the user's presence, and receives and displays the presence of contacts. The local application updates the user's presence manually, semi-automatically, or automatically. Semi-automatic updates involve synchronizing with the device's calendar. Automatic updates may involve the use of location data, the device's built-in sensors, and augmented reality.

Abstract: A method and system for collecting the contents of a computer network. There is a single Data Store, one or more Address Dispatchers, and Data Fetchers. A Fetcher requests a network site address from a Dispatcher, collects information from that site, and sends it to the Data Store. A Central Dispatcher retrieves usable addresses from the information stored in the Data Store. Deployed Dispatchers receive addresses from the internal database of a Network Hosting Service Provider (NHSP). A Global Fetcher resides anywhere on the network. A Deployed Fetcher resides on a dedicated resource within an NHSP. A Community Fetcher resides on a private personal computer that has relatively continuous access to the network, collecting only textual information, thereby producing relatively little network traffic. As a consequence, the Community Fetcher can run in the background, leading to the use of multitudes of volunteers, each running a Community Fetcher.