WO2004061612A2

WO2004061612A2 - Notification of contact list memberships and statistics

Info

Publication number: WO2004061612A2
Application number: PCT/US2003/041500
Authority: WO
Inventors: Justin Uberti
Original assignee: America Online Inc
Current assignee: Historic AOL LLC
Priority date: 2002-12-31
Filing date: 2003-12-30
Publication date: 2004-07-22
Anticipated expiration: 2005-06-30
Also published as: AU2003300417A8; AU2003300417A1; WO2004061612A3

Abstract

Determining the popularity of a user may include determining a number of contacts in a user contact list (420), determining a number of contact lists that include the user (430), comparing the number of contacts to the number of lists (440), and determining the popularity of the user based on the comparison. Popularity also may be determined based on comparing the number of users monitoring a user to the number of users monitored by the user.

Description

NOTIFICATION OF CONTACT LIST MEMBERSHIPS AND STATISTICS

TECHNICAL FIELD

The following description relates generally to communications networks and messaging systems with user contact lists.

BACKGROUND

With the rapid proliferation and affordability of computers, the Internet has become the communications medium of choice for many users. Many types of communications techniques are available to transmit and receive data. For example, two commonly used communications techniques are instant messaging and e-mail.

Instant messaging allows rapid communication of messages between users who are connected to a computer network. Generally, instant messaging software runs on a client device and provides one or more graphical user interfaces. The graphical user interfaces may be used to send and receive instant messages. For example, a graphical user interface may display a contact list. The contact list may include a list of identifiers (e.g., names or screen names) associated with users with whom a user communicates. The graphical user interfaces also provide an indication of the presence of a user on a host network (i.e., whether the client device of the user associated with an identifier is connected to the host network and able to receive a one-to-one and/or peer-to-peer communication).

E-mail provides somewhat slower communications than instant messaging.

However, unlike instant messaging, the presence or connection of a message recipient to the host network is not required to deliver a message. Generally, e-mail software runs on a client device and provides one or more graphical user interfaces to compose, send, sort, archive, and read messages.

An e-mail graphical user interface allows the user to select a contact from an address book or enter the e-mail address manually. The address book may include e-mail addresses or identifiers associated with e-mail addresses to which messages may be sent and delivered.

SUMMARY

In one general aspect, statistics about user communications and messaging systems are determined and used to determine various attributes of the users (e.g., the popularity of a user).

In one implementation, the number of user lists (e.g., a contact list or an address book) that include a particular user (e.g., to monitor the user's presence on a network) may be determined and compared to a threshold. If the number of lists is greater than the threshold, a determination is made that the user is popular. If the number of lists is less than or equal to the threshold, a determination is made that the user is less popular.

The number of lists also may be compared to several different thresholds to determine a graduated level of popularity. For example, each threshold may be associated with a different level of popularity. If the number of lists surpasses a threshold, a determination is made that the user has obtained the level of popularity associated with the threshold. A message may be sent to the user indicating the determined level of popularity.

In another general aspect, the number of users in a user list (e.g., a contact list or address book) of a particular user is determined. The number of contacts is compared to the number of lists that include the user. A popularity ratio of the user then is determined based on the comparison. For example, a determination is made that the user is relatively more popular if the number of lists that include the user is greater than the number of contacts on the user's list. A determination is made that the user is relatively less popular if the number of contacts is less than or equal to the number of lists. A message may be sent to the user indicating the determined popularity. In another general aspect, the interest level of a user in other uses may be determined.

In one implementation, the number of user contacts (e.g., in a contact list or an address book) of a particular user may be determined and compared to a threshold. If the number of contacts is greater than the threshold, a determination is made that the user is interested or inquisitive. If the number of lists is less than or equal to the threshold, a determination is made that the user is less inquisitive.

The number of contacts also may be compared to several different thresholds to determine a graduated level of interest. For example, each threshold may be associated with a different level of interest. If the number of lists surpasses a threshold, a determination is made that the user has obtained the level of interest associated with the threshold. A message may be sent to the user indicating the determined level of interest.

DESCRIPTION OF DRAWINGS

Fig. 1 is a block diagram of an exemplary communications system.

Figs. 2, 3, and 4 are flow charts of exemplary processes that may be used in the system of Fig. 1 to determine the popularity of a user.

Figs. 5 and 6 are exemplary graphical user interfaces of the communications system of Fig. 1 for displaying a contact list.

Fig. 7 is an exemplary graphical user interface of the communications system of Fig.

1 for making data regarding relative popularity of a user perceivable. Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

As shown in Fig. 1, a communications system 100 may include a number of networks (e.g., a host network 110, an intranet 130, and the Internet 135) to facilitate communications between one or more client devices 120. The client devices 120 may connect directly to the host network 110 using communications paths 140, or they may connect indirectly through the intranet 130 or the Internet 135. Once connected, a client device 120 may send messages to and receive messages from other client devices 120 connected to the host network 110. The host network 110 may be implemented using any number of components and/or network devices (e.g., hubs, routers, switches, servers, repeaters, storage devices, communications interfaces, processors, and various communications media) to establish a local area network (LAN), a wide area network (WAN), a switched network, a radio network, a cable network, a satellite network, or a combination of two or more of these networks. In particular, the host network 110 may include one or more host devices to provide access to the network and/or to provide online services. The host devices may include one or more login servers 145, an instant message (IM) host 160, an e-mail host 162, a host complex 164, a profile server 170, and a database 175. The host devices may exchange or access data using a host network communications structure 180 that may include communications media, servers, routers, switches, processors, storage, interfaces, and gateways (e.g., for conversion of protocols between host devices, if necessary). The host devices may provide one or more online services, such as accessing web content, searches, personalizing web content, e- mailing, instant messaging, chatting, and shopping. The client devices 120 may be operated by one or more users to send and receive messages using the communications system 100. An example of a client device 120 is a general-purpose computer capable of responding to and executing instructions in a defined manner. Client devices 120 also may include a special-purpose computer, a personal computer ("PC"), a workstation, a server, a laptop, a Web-enabled phone, a Web-enabled personal digital assistant ("PDA"), an interactive television set, a set top box, an on-board (i.e., vehicle-mounted) computer, or a combination of one or more these devices capable of responding to, generating, and/or executing instructions. The client device 120 may include any number of other devices, components, and/or peripherals, such as memory/storage devices, input devices, output devices, user interfaces, and/or communications interfaces. The client device 120 also may include one or more software applications (e.g., an operating system, a browser application, a microbrowser application,, a server application, a proxy application, a gateway application, a tunneling application, an e-mail application, an IM client application, an online service provider client application, and/or an interactive television client application) loaded on the client device 120 to command and direct communications enabled by the client device 120. Applications may include a computer program, a piece of code, an instruction, or some combination thereof, for independently or collectively instructing the client device 120 to interact and operate as desired.

The applications may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal capable of providing instructions to the client device 120. In particular, the applications may be stored on a storage medium or device (e.g., read only memory (ROM), a random access memory (RAM), a volatile/non- volatile memory, a magnetic disk, or a propagated signal) readable by the client device 120, such that if the storage medium or device is read by the client device 120, the step or instructions specified are performed.

The client device 120 also may include one or more communications interfaces that allow the client device to send and receive information using a communications path 140. The communications paths 140 may be configured to send and receive signals (e.g., electrical, electromagnetic, or optical) that convey or carry data streams representing various types of analog and/or digital content. For example, the communications paths 140 maybe implemented using various communications media and one or more networks comprising one or more network devices (e.g., servers, routers, switches, hubs, repeaters, and storage devices). The one or more networks may include a WAN, a LAN, a plain old telephone service (POTS) line network, a digital subscriber line (DSL) network, an integrated services digital network (ISDN), a synchronous optical network (SONNET), or a combination of two or more of these networks. In addition, the communications paths 140 may include one or more wireless links that transmit and receive electromagnetic signals, such as, for example, radio, infrared, and microwave signals to convey information.

The client device 120 may establish a connection (through a communications path 140) to a login server 145, to access the host network 110 using ah ISP client and/or a . browser application. The login server 145 determines whether a particular user of a client device 120 is authorized to access the host network 110 (e.g., by verifying a user identification and a password). If the user is authorized to access the host network 110, the login server 145 facilitates the establishing of communications between the client device 120 and the hosts corresponding to any services desired by the user.

Once communications with the host network 110 have been established* the client device 120 may directly or indirectly transmit data to and access services from the network hosts. For example, a client device 120 may establish a connection with the host complex 164 to browse the Internet, access web pages, shop online, get customized news, weather, and stock quotes, and search the World Wide Web.

The host network 110 also includes one or more user profile servers 170 connected to a database 175 to store user profile data. The user profile server 170 may be used to enter, retrieve, edit, manipulate, or otherwise process user profile data. In one implementation, user profile data includes a user contact list, an address book, identified interests, a geographic, location, a type of account, and demographic information. If authorized, the user may use the EVI client application or an ISP client application of the client device 120 to interact with the user profile server 170 and perform various functions (e.g., enter, edit and/or delete user profile data).

The user profile and/or user profile data also may be stored at the client device 120. For example, a storage medium of the client device 120 may store user account information, contact lists, and/or address books. In one implementation, the client device 120 provides the . user profile data to the host network 110 at specified times or when requested. In another implementation, the user profile data is stored locally at the client device 120 and at the host network 110. In this instance, the user host profile data and user client device profile data are periodically synchronized (e.g., at logon, logoff, or when appropriate).

If the user profile data is stored or mirrored by the host network 110, the user does not have to reenter or update such information in the event that the user accesses the host network 110 using a new or a different client device 120. Accordingly, when a user accesses the host network 110, the login server 145 can instruct the user profile server 170 to retrieve the user profile data from the database 175 and to provide, for example, user profile data to . any host device that requires the information. As previously described, the client device 120 may include one or more

communications applications (e.g., e-mail and IM). Each of the communications applications typically has an associated number of contacts and/or contact data that may be stored in a database, a file, a list, or two or more of these in combination. For example,, the contacts may be identifiers associated with a user including names, screen names, and/or e- mail addresses. The contact data may include additional information (e.g., name, address, . phone number, and other demographic information). The contacts may be arranged and presented as a contact list or an address book using a graphical user interface. As previously described, the contacts may be stored locally at the client device 120, at the host network 110, or both.

Statistics related to the contacts may be used to determine one or more attributes of a user. In one instance, an attribute of user popularity may be determined. A user's popularity may be determined using contact information as described below. A user's popularity ratio and/or interest level also may be determined, as described below. The communications application (e.g., an ISP application, a browser application, an

IM application, and/or an e-mail application) may include one or more features to determine attributes associated with a user. These features may be implemented as part of a communications application or as a service provided by the host network 110 (e.g., in association with a communications application). . If the features are implemented as part of a communications application, the communications application accesses contact data stored at the client device 120 or at the host network 110 to determine the user attributes. If the features are provided as a service of the host network 110, the communications application sends a request to the host network .

110 to determine the user's attributes. Ahost device (e.g., the IM host 160, the e-mail host 162* or the host complex 164) of the host network 110 may determine the attributes and respond to the client device 120.

In one implementation, the popularity of a user may be determined using the number of users who monitor the user's presence on the network or the number of contact lists that identify the user as a contact. For example, the number of contact lists that include the user's identifier may be compared to a threshold. If the number of contact lists is greater than the threshold, a determination is made that the user is popular. If the number of contacts is equal to or below the threshold, a determination is made that the user is less popular.

The number of contacts also may be compared to several thresholds to determine a graduated level of popularity. For example, a first threshold of 50 contacts maybe equated with a popularity rating of "popular," a second threshold of 100 contacts may be equated with a popularity rating of "very popular" or "famous," and a third threshold of 400 contacts may be equated with a popularity rating of "celebrity."

The user's popularity is determined to be equal to highest threshold that is surpassed. For example, if a user has 105 contacts in her contact list, a determination is^" made that she is famous. If a user has fewer contacts than the lowest threshold, a determination is made that the user is less popular. For example, if a user has 10 contacts in his contact list, a determination is made that he is unpopular. The communications application may display an indication of the user's popularity to the user based on the determined popularity (e.g., in a message provided by a graphical user interface).

In another implementation, the curiosity and/or interest level in other users is determined by comparing the number of contacts stored in a user profile, a contact list, an address book, or a database to a threshold. The threshold is a number that corresponds to a level of interest, curiosity, or inquisitiveness of the user. If the number of contacts is greater than the threshold, a determination is made that the user is inquisitive. If the number of contacts is below or equal to the threshold, a determination is made that the user is less inquisitive or indifferent.

A graduated level of interest corresponding to more than one threshold also may be used (as described above, e.g., apathetic, indifferent, inquisitive, curious, and nosy). The communications application may display an indication of the user's inquisitiveness based on the determined interest (e.g., in a message provided by a graphical user interface).

In another implementation, the relative popularity or popularity ratio of a user may be determined by comparing the number of contacts appearing in the user's contact list to the number of contact lists that include the user. For example, a user who has twelve contacts in his contact list may be perceived as being relatively popular if in comparison the user is listed in fifteen other contact lists. The user may be perceived as relatively more popular because more users are interested in monitoring the user than the user is interested in monitoring. However, if the same user were listed in only ten contact lists, the user may be perceived as being relatively less popular because the user is interested in monitoring more users than are interested in monitoring the user.

Fig. 2 shows an exemplary process 200 that may be used in the system of Fig. 1 to determine the interest level of a user. Initially, a request is received to determine a user's interest (210). The number of contacts in the contact list of the user (e.g., an IM contact list or an e-mail address book) is then determined (220). The number of contacts is compared to one or more thresholds (230). A determination is then made as to whether the number of contacts is greater than the threshold (240).

If the number of contacts is greater than the threshold, a determination is made that the user is inquisitive (242). If the number of contacts is less than or equal to the threshold, a determination is made that the user is less inquisitive (245). After the interest level of the

user is determined, an indication of the user's determined interest is provided to the user

(250).

Fig. 3 shows an exemplary process 300 that may be used in the system of Fig. 1. to

determine the popularity of a user. Initially, a request is received to determine a user's popularity (310). The number of contact lists (e.g., an IM contact list or an e-mail address book) that list the user is then determined (320). The number of contact lists is compared to one or more thresholds (330). A determination is then made as to whether the number of contact lists is greater than or equal to a threshold (340). If the number of contacts is greater than the threshold, a determination is made that the user is popular (342). If the number of contacts is less than or equal to the threshold, a determination is made that the user is relatively less (345). After the popularity of the user is determined, a message indicating the user's determined .popularity is provided to the user (350). Fig. 4 shows a process 400 to determine the relative popularity or popularity ratio of a user. Initially, a request is received to determine a user's relative popularity (410). The number of contacts in the contact list of the user is determined (420). The number of contact lists listing the user is determined (430). The number of lists is compared to the number of contacts to determine whether the number of contacts is greater than the number of lists (440).

If the number of contacts is greater than the number of lists, a determination is made that the user has a low popularity ratio and/or is relatively less popular (442). If the number of contacts is less than the number of lists, a determination is made that the user has a high popularity ratio and/or is relatively more popular (445). A message indicating the determined relative popularity is provided to the user (450).

The processes 200, 300 and 400 may be implemented by an application running on the client device 120 or at the host network 110 (e.g., an application of the IM host 160, the e-mail host 162, and the host complex 164). Each process 200 and 300 also may include a graduated level of thresholds as described above.

Figs. 5 and 6 show a graphical user interface that may be used with the communications system of Fig. 1 to display a user contact list. As shown in Fig. 5, the graphical user interface 500 may be implemented using a communications client application (e.g., an BVI application) running on the client device 120. Although the following examples of a user interface are described with reference to an IM interface, other user interfaces for communications applications, such as an e-mail application, also may be used in a similar manner.

The graphical user interface 500 may be used to invoke various IM client application functions. The IM interface 500 includes a menu bar 510 to select menus and features associated with the communications application. The TM interface 500 also includes a contact list online tab 520 and a list setup tab 530. The list setup tab 530 includes a list of one or more contacts of a user. The contacts on the contact list may be stored locally on the client device 120 and/or at the host network 110 (e.g., in database 175) as described above. The contacts may be organized into one or more user groups. For example, the contact list shown includes a buddies group 535, a co-workers group 536, and a family group 537. Each group includes one or more contact group members. Each group member may have an associated identifier (e.g., a screen name or user ID). The list setup tab 530 also includes list setup icons 540 to perform functions (e.g., adding a screen name or a group, deleting a screen name or a group, and finding a screen name of a user).

The interface 500 also includes an TM toolbar 542 including one or more icons to perform functions (e.g., linking to an IM-related web page, entering an away message, and setting IM-related user preferences). The toolbar 542 also includes a popularity icon 550. The popularity icon is used to invoke the determination of user popularity (e.g., using the process 300). Icons for interest level and popularity ratio also may be included (and determined using processes 200 or 400, respectively).^' These features also may be provided using another input (e.g., a dropdown menu). As shown in Fig. 6, the online tab 520 displays a contact list including the online status or presence (e.g., the ability for the client device 120 of the user to establish a peer-to- peer connection with the client device 120 associated with the contact identifier displayed on online tab) of the contact and capabilities of the contact identified by the user (e.g., using the list setup tab 530). The online tab 520 groups the contacts according to the user groups. For example, the online tab 520 may include a Buddies list 536, a Co-Workers list 537, and a Family list 538. Each online list includes one or more screen names corresponding to IM group members that currently are online. The online tab 520 also includes an offline list 539 identifying offline members from one or more of the IM groups according to each group or collectively (without reference to groups). The online tab 520 also includes online icons 545 for performing Hvl functions (i.e., displaying an IM window, sending an invitation to enter a chat room, and finding profile information associated with a screen name).

A user may determine the popularity by selecting an input (e.g., the popularity icon

550) of the graphical user interface 500. Selecting the popularity icon 550 causes the communications application (e.g., an IM application) to generate a request, which is sent from the client device 120 through an associated communications path 140 to a host device (e.g., the IM host 160) of the host network 110. An IM server of the IM host 160 receives the request and contacts the profile server 170 to determine the contact information needed to determine the user's popularity.

In another implementation, selecting the popularity icon 550 causes the IM application to determine the user's popularity. If the contact data that is needed to perform the determination is not stored by the client device 120, the TM application contacts the host network 110 to obtain the contact information as described above. After the popularity is determined, the communications application provides a. message using a graphical interface to present the determined popularity. As shown in Fig. 7, an exemplary message interface 700 to display a relative popularity message includes a toolbar 701 for accessing and performing various functions of the message interface 700. The message interface 700 also includes a message window 710 to display the relative popularity message 715. The message 715 indicates the number of lists 725 in which the user appears (e.g., "You are listed in 15 buddy lists"). The message 715 alsoindicates the popularity 730 of the user (e.g., "You are very popular!")

A user also may request information (e.g., identity information) about others who monitor the user. For example, a communications application of the client device 120 may send a request to the host network 110 for the identifications of any users who monitor the user's presence on the host network 110. A user's presence may be monitored by including an identifier associated with a user in a contact list of a communications program/service that monitors the online presence of users. The host network 110 also may provide the identifiers (e.g., the screen names) of others who monitor the presence of the user on the host network 110 in response to a request from the user. Similarly, the host network 110 may provide information indicating that others monitoring the user have included the user in a contact list stored in a personal profile. A message including the information may be generated and sent to the user and displayed using a communications application of the client device 120.

In another implementation, a user may determine the relative popularity of others, such as the popularity of a contact on the user's contact list. The host network 110 maybe configured to return information about the relative popularity of a specified user based on information stored in a corresponding profile of the specified user. A user may send a request to the host network 110 including user identity information (e.g., a screen name) of the specified user for which a relative popularity is desired. The host network 110 may perform one process (e.g., any of the processes 200, 300, 400) to determine the relative popularity of the identified user. The determined popularity may then be sent to the user. A user may opt out of any monitoring or popularity determination, by selecting an opt-out feature from the graphical interface of the communications application. If the user opts out, an indication to this effect may be stored in the user's profile at the host network 110.

In another implementation, usage data or other sociological data obtained by the host network 110 may be tracked over time to determine usage trends for the host network 110. An administrator of the host network 110 may use information derived from these usage trends to configure the host network 110. In particular, usage trends of closed and open groups may be monitored. A closed group of users monitors the presence of other members of the group, whereas an open group of users monitors the presence of users inside and outside the group.

The administrator of the host network 110 may adjust the network configuration based upon the usage trends determined for such groups. For example, the administrator may configure user connection procedures so that members of a closed group connect to the same server (e.g., a server in the IM host 160). Similarly, a user of the host network 110 may monitor usage trends of other users and groups. For example, the user may determine the times at which a contact in his contact list is most likely to be connected to the host network 110.

In one implementation, the measure of a person's popularity by examining the number of contact lists that list the person may be applied in a degrees of separation context. Degrees of separation is highly analogous to contact lists (e.g., an IM contact list or an e-mail address book), because it is merely an extension of those contact lists that includes additional contact lists on which the user is not directly listed, but with whom there is a traceable link of contacts, within the network of people related to the user. The degrees of separation context may be used to identify other users that are related to a user within a specific number of degrees of separation. Thus, a person's popularity may be measured by determining the number contact lists that include the person, as described above, and a person's popularity may be measured by determining the number of people that list the person within one degree of separation, within two degrees of separation, and within n degrees of separation. In another exemplary implementation, the measure of a person's popularity may be used to gauge a level of trust and/or a level of competence in a particular area. For example, an inference may be drawn that the popularity of a person or entity is related to their trustworthiness and/or competence. This may be applied in a professional setting where a person's business contact information is used to determine how popular the person is. For instance, if the person is a plumber and the person is deemed to be very popular through their inclusion within contact lists of n degrees of separation or otherwise, then one can infer that they are a competent or at least well-liked plumber.

A number of exemplary implementations have been described. Nevertheless, it is understood that various modifications may be made. For example, suitable results may be achieved if the steps of described techniques are performed in a different order and/or if components in a described system, architecture, device, or circuit are combined in a different manner and/or replaced or supplemented by other components. Accordingly, other implementations are within the scope of the following claims.

Claims

WHAT IS CLAIMED IS:

1. A method for determining an attribute of a user, the method comprising: determining a number of contacts in a contact list of the user; comparing the number of contacts to one or more thresholds; and determining the user attribute based on the comparison.

2. The method of claim 1 wherein determining the user an attribute includes determining user interest in other users.

3. The method of claim 2 wherein comparing further comprises determining whether the number of contacts is greater than the one or more thresholds.

4. The method of claim 3. wherein determining the user interest further comprises determining that the user is inquisitive if the number of contacts is greater than the one or more thresholds.

5. The method of claim 3 wherein determining the user interest further comprises determining that the user is relatively less popular if the number of contacts is less than or equal to the one or more thresholds.

6. The method of claim 1 further comprising providing an indication of the user's determined attribute.

7. The method of claim 1 wherein the contact list is an instant messaging contact list.

8. The method of claim 1 wherein the contact list is an e-mail address book.

9. The method of claim 1 wherein comparing the number of contacts to one or more thresholds comprises comparing the number of contacts to multiple thresholds.

10. A method of determining popularity of a user, the method comprising: determining a number of contact lists that include the user, comparing the number of lists to one or more thresholds; and determining a popularity of the user based on the comparison.

11. The method of claim 10 wherein determining the popularity includes determining that the user is relatively more popular if the number of contact lists is greater than the one or more thresholds.

12. The method of claim 10 wherein determining the popularity includes determining that the user is relatively less popular if the number of contacts is less than or equal to the one or more thresholds.

13. A method of determining the popularity ratio of a system user, the method comprising: determining a number of users monitoring the presence of a user on a network; determining a number of users whose presence is monitored by the user; comparing the number of users monitored to the number of monitoring users; and determining a relative popularity of the user based on the comparison.

14. The method of claim 13 wherein determining the popularity includes determining that the user is relatively more popular if the number of monitoring users is greater than the number of monitored users.

15. The method of claim 13 wherein determining the popularity includes determining that the user is relatively less popular if the number of monitored users is greater than or equal to the number of monitoring users.

16. The method of claim 13 further comprising sending a message to the user indicating the determined popularity.

17. The.method of claim 13 wherein determining a number of users monitoring a user includes determining a number of contact lists that include the user.

18. The method of claim 13 wherein determining the number of users monitored by the user includes determining a number of entries in a contact lists .of the user. _2Q _

19. The method of claim 13 wherein the network is an instant message .

network.

20. A computer readable medium including instructions for determining the popularity of a system user, the instructions being executable to cause a processor to: determine a number of contacts lists that include the user; compare the number of contacts to one or more thresholds; and determine the popularity of the user based on the comparison.

21. The computer readable medium of claim 20 including instructions being executable to cause a processor to determine whether the number of lists is greater than the one or more thresholds.

22. The computer readable medium of claim 20 including instructions being executable to cause a processor to determine that the user is popular if the number of lists is greater than the one or more thresholds.

23. The computer readable medium of claim 20 including instructions being executable to cause a processor to determine that the user is less popular if the number of list is less than or equal to the one or more thresholds.

24. The computer readable medium of claim 20 including instructions being executable to cause a processor to provide an indication of the user's determined popularity.

25. The computer readable medium of claim 20 including instructions being executable to cause a processor to compare the number of list to multiple thresholds.

26. A computer readable medium including instructions for determining the popularity ratio of a system user, the instructions being executable to cause a processor to: determine a number of users monitoring a user; determine a number of users monitored by the user; compare the number of users monitored to the number of momtoring users; and determine a popularity ratio of the user based on the comparison.

27. The computer readable medium of claim 26 further comprising instructions to cause a processor to determine that the user is relatively more popular if the number of monitoring users is greater than the number of monitored users.

28. The computer readable medium of claim 26 further comprising instructions to cause a processor to determine that the user is relatively less popular if the number of monitored users is greater than or equal to the number of monitoring users.

29. The computer readable medium of claim 26 further comprising instructions to cause a processor to send a message to the user indicating a determined

popularity ratio.

30. The computer readable medium of claim 26 further comprising instructions to cause a processor to determine a number of contact lists that include the user.

31. The computer readable medium of claim 26 further comprising instructions to cause a processor to determine a number of contact lists that include the user.

32. A system comprising a host including: an input to receive a popularity request from a user; and a processor to determine a number of contacts lists that include the user, to compare the number of lists to one or more thresholds; and to determine the popularity of the user based on the comparison.

33. The system of claim 32 wherein the processor is configured to determine whether the number of lists is greater than the one or more thresholds.

34. The system of claim 32 wherein the processor is configured to determine

that the user is popular if the number of lists is greater than the one or more

thresholds.

35. The system of claim 32 wherein the processor is configured to determine that the user is less popular if the number of lists is less than or equal to the one or

more thresholds.

36. The system of claim 32 wherein the.processor is configured to provide an indication of the user's determined popularity.

37. The system of claim 32 wherein the processor is configured to compare the number of lists to multiple thresholds.

38. The system of claim 32 wherein the.processor is configured to generate an indication of the determined popularity that is perceivable by the user.

39. The system of claim 32 further comprising: a host including the input, the processor, and a user profile database that includes contact lists for network users, wherein the processor is configured to access the database to determine the number of lists.

40. The system of claim 39 wherein the host further comprises a user profile

server to receive a request from the processor, to determine the number of lists, and to

provide the number of lists to the processor.

41. The system of claim 39 further comprising a client device configured to generate the popularity request.

42. The system of claim 39 further comprising a client device configured to receive and present the message to the user.

43. A host network for determining the popularity of a host network user, the host network comprising a host including: an input to receive a popularity check request from a user; and a processor to determine a number of users monitoring a user to compare the number of monitoring user to one or more thresholds, and to determine a popularity of the user based on the comparison in response to the popularity check request.

44. The host network of claim 43 wherein the processor is configured to determine that the user is more popular if the number of monitoring users is greater than a threshold.

45. The host network of claim 43 wherein the processor is configured to determine that the user is less popular if the number monitoring users is less than or equal to a threshold.

46. The host network of claim 43 wherein the host includes an output to send a message to the user indicating the determined popularity.

47. The host network of claim 43 wherein the processor is configured to determine a number of contact lists that include the user.

48. A graphical user interface for enabling a determination of the popularity of a user, the graphical interface comprising a mechanism to enabling the determination of a user's popularity and an interface to display the user's popularity in response to activation of the mechanism.

49. The graphical user interface of claim 48 wherein the mechanism is a virtual button.

50. The graphical user interface of claim 48 wherein the mechanism is configured to cause a processor to determine a number of contact lists that include the user, to compare the number of lists to one or more thresholds; and to determine the popularity of the user based on the comparison.

51. The graphical user interface of claim 50 wherein the processor is configured to determining whether the number of lists is greater than the one or more thresholds and that the user is popular if the number of lists is greater than the one or more thresholds.

52. The graphical user interface of claim 51 wherein determining the popularity further comprises determimng that the user is less popular if the number of lists is less than or equal to the one or more thresholds.

53. The graphical user interface of claim 48 further comprising providing an indication of the user's determined popularity.

54. The graphical user interface of claim 48 wherein the contact list is an instant messaging contact list.

55. The graphical user interface of claim 48 wherein the contact list is an e- mail address book.

56. The method of claim 10 wherein determining the number of contact lists that include the user includes determimng the number of contact lists that include the user within n degrees of separation.

57. The computer readable medium of claim 20 wherein the instructions being executable that cause the processor to determine the number of contact lists that include the user includes instructions being executable that cause the processor to determine the number of contact lists that include the user within n degrees of separation.

58. The system of claim 32 wherein the processor is configured to determine the number of contact lists that include the user within n degrees of separation.

59. The host network of claim 43 wherein the processor is configured to determine a number of users monitoring the user within n degrees of separation.