PEOPLE LISTS
`
`CROSS REFERENCE TO RELATED APPLICATIONS
`
`[0001]
`
`This application is a continuation of US. Application Serial No. 15/608,891, filed
`
`on May 30, 2017, which is a continuation ofU.S. Application Serial No. 13/616,750, filed on
`
`September 14, 2012 and now issued as US Patent No. 9,667,585, which is a continuation of
`
`US. Application Serial No. 13/507,429 filed on June 28, 2012 and now issued as US. Patent
`
`No. 9,774,560, which is a continuation of US. Application Serial No. 13/048,312 filed on
`
`March 15, 2011 and now issued as US. Patent No. 8,224,916, which is a continuation of US.
`
`Application Serial No. 10/715,215 filed on November 18, 2003 and now issued as US. Patent
`
`No. 7,908,327, which claims the benefit of priority to US. Provisional Application Serial Nos.
`
`60/477,333 filed on June 11, 2003, 60/426,812 filed on November 18, 2002, and 60/426,806
`
`filed on November 18, 2002. Each of the aforementioned applications and patents are hereby
`
`incorporated by reference in their entirety.
`
`TECHNICAL FIELD
`
`[0002]
`
`This document relates to the identification and creation of lists of contacts to which
`
`electronic messages may be sent from one or more communications applications.
`
`BACKGROUND
`
`[0003]
`
`Many activities that leverage the Internet involve communicating and sharing
`
`messages (aka, sending messages). Multiple communications programs may be used to send
`
`messages over the Internet. For example, separate applications exist for sending e-mail
`
`messages,
`
`instant messages, digital pictures, and electronic calendar information. These
`
`different applications may be used to send messages to common people or common groups of
`
`people. However, conventionally, each application typically stores a separate list of people or
`
`groups of people with whom communication using that application regularly occurs. For
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`1
`
`Patent Application
`
`

`

`example, an e-mail application has an address book, and an instant messaging application has
`
`a buddy list.
`
`BRIEF SUMMARY
`
`[0004]
`
`In one general aspect, enabling management of contacts includes passively
`
`recognizing a set of contacts that are, as a group, repeatedly sent communications by a member,
`
`bringing the member's attention to the recognized set of contacts, enabling the member to name
`
`the set of contacts, and enabling the member to address future communications to the set of
`
`contacts through use of the name associated by the member with the set of contacts.
`
`[0005]
`
`Implementation may include one or more of the following features. For example,
`
`in one implementation, passively recognizing the set of contacts may include storing
`
`communications sent by the member during a period of time, examining the communications
`
`sent by the member during the period of time, and identifying a set of contacts that was sent at
`
`least a minimum number of communications by the member during the period of time.
`
`[0006]
`
`In another implementation, passively recognizing the set of contacts may include
`
`storing a predetermined number of communications sent by the member, examining the
`
`predetermined number of communications sent by the member, and identifying a set of contacts
`
`that was sent at least a minimum number of communications out of the predetermined number
`
`of communications by the member.
`
`[0007]
`
`The member may be enabled to accept or to reject the recognized set of contacts
`
`brought to the member's attention. The member may be enabled to delay a rejected set of
`
`contacts from being brought to the member's attention. The member may be enabled to assign
`
`a unique identifier to the set of contacts.
`
`[0008]
`
`In one implementation, the communications sent to the set of contacts and the future
`
`communications may be sent from multiple applications.
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`2
`
`Patent Application
`
`

`

`[0009]
`
`The multiple applications may include communications applications. The
`
`communications applications may include an e-mail application and at least one application
`
`other than an e-mail application. The communications applications may include an instant
`
`messaging application and at least one application other than an instant messaging application.
`
`The communications applications may include a digital image sharing application and at least
`
`one application other
`
`than a digital
`
`image sharing application. The communications
`
`applications may include an alerting application that sends alerts and reminders to users and at
`
`least one application other than an alerting application that sends alerts and reminders to users.
`
`The communications applications may include an application for sharing and exchanging
`
`contact information and at least one application other than an application for sharing and
`
`exchanging contact information.
`
`[0010]
`
`The multiple applications may include other sharing applications. The other sharing
`
`applications may include an electronic journal application and at least one application other
`
`than an electronic journal application. The other sharing applications may include an e-mail
`
`filtering application and at least one application other than an e—mail filtering application. The
`
`other sharing applications may include an application that enables the specification of parental
`
`controls over a child account and at least one application other than an application that enables
`
`the specification of parental controls over a child account.
`
`[0011]
`
`These general and specific aspects may be implemented using a system, a method,
`
`or a computer program, or any combination of systems, methods, and computer programs.
`
`[0012]
`
`Other features will be apparent from the description and drawings, and from the
`
`claims
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0013]
`
`FIG. 1 is a block diagram of a communications system.
`
`[0014]
`
`FIGS. 2 and 3 are expansions of the block diagram of FIG. 1.
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`3
`
`Patent Application
`
`

`

`[0015]
`
`FIGS. 4 and 7 are flow charts of processes for automatically creating and storing a
`
`people list.
`
`[0016]
`
`FIG. 5 is an illustration of an interface for selecting people or groups of people to
`
`whom a message is sent.
`
`[0017]
`
`FIG. 6 is a flow chart of specifying, sharing, and using people lists.
`
`[0018]
`
`Like reference symbols in the various drawings may indicate like elements.
`
`DETAILED DESCRIPTION
`
`[0019]
`
`People lists are lists of contacts, for example, with each contact stored in a people
`
`list as a single identifier. The single identifier may be an e-mail address, a screen name, a cell
`
`phone number, or any other identifier capable of uniquely identifying the corresponding
`
`contact. A people list may be accessed from a central people list repository by multiple
`
`applications to address messages. For example, an e-mail application may use a people list to
`
`specify the recipients of an e-mail message and a digital image sharing application may use the
`
`same people list to specify the recipients of a shared digital image.
`
`[0020]
`
`People lists may be actively created through the specification of a single identifier
`
`for each of the contacts to be included in the people list. People lists also may be created
`
`passively through automatic detection of a set of contacts that are repeatedly specified as the
`
`recipients of messages, where the set of contacts repeatedly receiving messages include the
`
`members of a passively created people list. People lists also may be created through the
`
`integration of existing lists from within the multiple applications into the set of people lists.
`
`For example, distinct people lists may be created based on each of the named groups within a
`
`buddy list of an instant messaging application.
`
`[0021]
`
`Once created, people lists may be shared to prevent the need for duplicate creation
`
`of a people list for use by multiple people. The person who originally creates the people list
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`4
`
`Patent Application
`
`

`

`shares the people list by sending copies to each of the people with whom the list is to be shared.
`
`If any of the people holding a copy of the people list makes any changes to the people list, the
`
`changes may be automatically propagated to the other copies of the people list.
`
`[0022]
`
`For illustrative purposes, FIGS. 1—3 show an example of a communications system
`
`for implementing techniques for transferring electronic data. People lists may be used to
`
`address communications sent using the communications system illustrated in FIGS. 1-3. For
`
`brevity, several elements in the figures described below are represented as monolithic entities.
`
`However, as would be understood by one skilled in the art, these elements each may include
`
`numerous interconnected computers and components designed to perform a set of specified
`
`operations and/or may be dedicated to a particular geographical region.
`
`[0023]
`
`Referring to FIG. 1, a communications system 100 is capable of delivering and
`
`exchanging data between a requestor system 105 and a provider system 110 through a
`
`communications link 115. The requestor system 105 may include a client system and the
`
`provider system 110 may include a host system. The requestor system 105 typically includes
`
`one or more requestor devices 120 and/or requestor controllers 125, and the provider system
`
`110 typically includes one or more provider devices 135 and/or provider controllers 140. For
`
`example, the requestor system 105 or the provider system 110 may include one or more
`
`general-purpose computers (e.g,, personal computers), one or more special-purpose computers
`
`(e.g., devices specifically programmed to communicate with each other and/or the requestor
`
`system 105 or the provider system 110), or a combination of one or more general—purpose
`
`computers and one or more special-purpose computers. The requestor system 105 and the
`
`provider system 110 may be arranged to operate within or in concert with one or more other
`
`systems, such as, for example, one or more Local Area Networks (“LANs”) and/or one or more
`
`Wide Area Networks (“WANs”).
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`5
`
`Patent Application
`
`

`

`[0024]
`
`The provider system 110 may include a communication interface such as an
`
`electronic mail gateway. For instance, the provider system 110 may include a dedicated mailing
`
`system that is implemented by specialized hardware or executed by a general purpose processor
`
`capable of running various applications, such as electronic mailer programs, and capable of
`
`employing various file transfer protocols, such as the Simple Mail Transfer Protocol
`
`(“SMTP”). The communications interface of provider system 110 enables communications
`
`between the provider system 1 10 and other systems through, for example, communications link
`
`1 15.
`
`[0025]
`
`The requestor device 120 (or the provider device 135) is generally capable of
`
`executing instructions under the command of a requestor controller 125 (or a provider
`
`controller 140). The requestor device 120 (or the provider device 135) is connected to the
`
`requestor controller 125 (or the provider controller 140) by a wired or wireless data pathway
`
`130 or 145 capable of delivering data.
`
`[0026]
`
`The requestor device 120, the requestor controller 125, the provider device 135, and
`
`the provider controller 140 each typically include one or more hardware components and/or
`
`software components. An example of a requestor device 120 or a provider device 135 is a
`
`general-purpose computer (e.g., a personal computer) capable of responding to and executing
`
`instructions in a defined manner. Other examples include a special-purpose computer, a
`
`workstation, a server, a device, a component, other physical or virtual equipment or some
`
`combination thereof capable of responding to and executing instructions. The requestor device
`
`120 and the provider device 135 may include devices that are capable of peer-to-peer
`
`communications.
`
`[0027]
`
`An example of a requestor controller 125 or a provider controller 140 is a software
`
`application loaded on the requestor device 120 or the provider device 135 for commanding and
`
`directing communications enabled by the requestor device 120 or the provider device 135.
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`6
`
`Patent Application
`
`

`

`Other examples include a program, a piece of code, an instruction, a device, a computer, a
`
`computer system, or a combination thereof, for independently or collectively instructing the
`
`requestor device 120 or the provider device 135 to interact and operate as described. The
`
`requestor controller 125 and the provider controller 140 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 requestor device 120 or
`
`the provider device 135.
`
`[0028]
`
`The communications link 115 typically includes a delivery network 160 making a
`
`direct or indirect communication between the requestor system 105 and the provider system
`
`110, irrespective of physical separation. Examples of a delivery network 160 include the
`
`Internet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone
`
`networks (e.g., PSTN, ISDN, and xDSL), radio, television, cable, satellite, and/or any other
`
`delivery mechanism for carrying data. The communications
`
`link 115 may include
`
`communication pathways 150 and 155 that enable communications through the one or more
`
`delivery networks 160 described above. Each of the communication pathways 150 and 155
`
`may include, for example, a wired, wireless, cable or satellite communication pathway.
`
`[0029]
`
`An electronic information store 180 may be connected to the provider system 110,
`
`included as a component of the provider system l 10, and/or connected to the delivery network
`
`160. The electronic information store 180 may be a repository for electronic information that
`
`may be in an indexed and/or searchable format.
`
`[0030]
`
`FIG. 2 illustrates a communications system 200 including a requestor system 205
`
`communicating with a provider system 210 through a communications link 215. Requestor
`
`system 205 typically includes one or more requestor devices 220 and one or more requestor
`
`controllers 225 for controlling the requestor devices 220. Provider system 210 typically
`
`includes one or more provider devices 235 and one or more provider controllers 240 for
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`7
`
`Patent Application
`
`

`

`controlling the provider devices 235. The communications
`
`link 215 may include
`
`communication pathways 250 and 255 that enable communications through the one or more
`
`delivery networks 260.
`
`[0031]
`
`Examples of each element within the communications system of FIG. 2 are broadly
`
`described above with respect
`
`to FIG.
`
`1.
`
`In particular,
`
`the provider system 210 and
`
`communications link 215 typically have attributes comparable to those described with respect
`
`to the provider system 1 10 and the communications link 1 15 ofFIG. 1. Likewise, the requestor
`
`system 205 of FIG. 2 typically has attributes comparable to and illustrates one possible
`
`implementation of the requestor system 105 of FIG. 1.
`
`[0032]
`
`The requestor device 220 typically includes a general-purpose computer 270 having
`
`an internal or external storage 272 for storing data and programs such as an operating system
`
`274 (e.g., DOS, WindowsTM, Windows 95““, Windows 98““, Windows 2000““, Windows
`
`MeTM, Windows XPTM, Windows NTTM, 08/2, or Linux) and one or more application
`
`programs. Examples of application programs include authoring applications 276 (e.g., word
`
`processing programs, database programs, spreadsheet programs, calendar programs, or
`
`graphics programs) capable of generating documents or other electronic content; client
`
`applications 278 (6g, stand alone e-mail client or AOL client, CompuServe client, AIM client,
`
`AOL TV client, or ISP client, all of which may include a built-in or embedded e-mail and/or
`
`instant messaging client) capable of communicating with other computer users, accessing
`
`various computer resources, and viewing, creating, or otherwise manipulating electronic
`
`content; browser applications 280 (e. g, Netscape's Navigator or Microsoft's Internet Explorer)
`
`capable of rendering standard Internet content and also capable of supporting a web-based e-
`
`mail and/or instant messaging client; and other applications such as a digital image sharing
`
`application.
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`8
`
`Patent Application
`
`

`

`[0033]
`
`The general-purpose computer 270 also includes a central processing unit 282
`
`(CPU) for executing instructions in response to commands from the requestor controller 225.
`
`In one implementation, the requestor controller 225 includes one or more of the application
`
`programs installed on the internal or external storage 272 of the general—purpose computer 270.
`
`In another implementation, the requestor controller 225 includes application programs stored
`
`in and performed by one or more device(s) external to the general-purpose computer 270.
`
`[0034]
`
`The general-purpose computer also includes a communication device 284 for
`
`sending and receiving data. One example of the communication device 284 is a modem. Other
`
`examples include a transceiver, a set—top box, a communication card, a satellite dish, an
`
`antenna, or another network adapter capable of transmitting and receiving data over the
`
`communications link 215 through a wired or wireless data pathway 250. The general-purpose
`
`computer 270 also may include a TV tuner 286 for receiving television programming in the
`
`form ofbroadcast, satellite, and/or cable TV signals. As a result, the requestor device 220 can
`
`selectively and/or simultaneously display network content received by communications device
`
`284 and television programming content received by the TV tuner 286.
`
`[0035]
`
`The general-purpose computer 270 typically includes an input/output interface 288
`
`for wired or wireless connection to various peripheral devices 290. Examples of peripheral
`
`devices 290 include, but are not limited to, a mouse 29] , a mobile phone 292, a personal digital
`
`assistant 293 (PDA), a l\/[P3 player (not shown), a keyboard 294, a display monitor 295 with
`
`or without a touch screen input, a TV remote control 296 for receiving information from and
`
`rendering information to subscribers, and an audiovisual input device 298.
`
`[0036]
`
`Although FIG. 2 illustrates devices such as a mobile telephone 292, a PDA 293, and
`
`a TV remote control 296 as being peripheral with respect to the general-purpose computer 270,
`
`in another implementation, such devices may themselves include the functionality of the
`
`general-purpose computer 270 and operate as the requestor device 220. For example, the
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`9
`
`Patent Application
`
`

`

`mobile phone 292 or the PDA 293 may include computing and networking capabilities and
`
`function as a requestor device 220 by accessing the delivery network 260 and communicating
`
`with the provider system 210. Furthermore, the requestor system 205 may include one, some
`
`or all of the components and devices described above.
`
`[0037]
`
`FIG. 3 illustrates a communications system 300 including a requestor system 305
`
`communicating with a provider system 310 through a communications link 315. The requestor
`
`system 305 typically includes one or more requestor devices 320 and one or more requestor
`
`controllers 325 for controlling the requestor devices 320. Provider system 310 typically
`
`includes one or more provider devices 335 and one or more provider controllers 340 for
`
`controlling the provider devices 335. The communications
`
`link 315 may include
`
`communication pathways 350 and 355 that enable communications through the one or more
`
`delivery networks 360.
`
`[0038]
`
`Examples ofeach element within the communications system ofFIG. 3 are broadly
`
`described above with respect
`
`to FIG.
`
`1.
`
`In particular,
`
`the requestor system 305 and
`
`communications link 315 typically have attributes comparable to those described with respect
`
`to the requestor system 110 and the communications link 115 of FIG. 1. Likewise, the provider
`
`system 310 of FIG. 3 typically has attributes comparable to and illustrates one possible
`
`implementation of the provider system 1 10 of FIG. 1.
`
`[0039]
`
`The provider device 335 typically includes or enables access to one or more
`
`applications. The applications may be used to deliver or control messages sent and received by
`
`users of the requestor devices 320. The applications may be categorized into two groups:
`
`communications applications used to send and receive messages and other sharing applications.
`
`Examples of communications applications include an e-mail application, an instant messaging
`
`application, a digital image sharing application, an application for sharing contact information,
`
`and an application for sending alerts and reminders. Examples of other sharing applications
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`10
`
`Patent Application
`
`

`

`include an e-mail filtering application, an application for specifying parental controls over a
`
`parental account, and an electronic journal application. Other applications capable of
`
`controlling communications also may be included in the provider device 335. The users of the
`
`requestor system 305 use the requestor devices 320 to create messages, and the created
`
`messages are given to the applications included in the provider device 335 for delivery.
`
`[0040]
`
`The applications included in the provider device 335 are capable of executing
`
`instructions in response to commands from the provider controller 340. In one implementation,
`
`the provider controller 340 includes one or more of the application programs installed on the
`
`provider device 335.
`
`In another implementation,
`
`the provider controller 340 includes
`
`application programs stored in and performed by one or more device(s) external to the provider
`
`device 335.
`
`[0041]
`
`An address book server and database 380 may be connected to the provider system
`
`310, included as a component of the provider system 310, and/or connected to the delivery
`
`network 360. The address book server and database 380 is broadly described above with respect
`
`to FIG. 1. The address book server and database 380 typically has attributes comparable to and
`
`illustrates one possible implementation of the electronic information store 180 of FIG. 1. The
`
`address book server and database 380 may be a repository for contact information that may be
`
`in an indexed and/or searchable format. The address book server and database 380 may store
`
`pairs of names and identifiers for individual contacts as well as for people lists. The identifiers
`
`stored by the address book server and database 380 may be used to address messages delivered
`
`by the applications included in the provider device 385, where the identifiers to be used may
`
`be selected through selection of the corresponding names stored in the address book server and
`
`database 3 80.
`
`[0042]
`
`In one exemplary implementation, a selection interface 385 is included in the
`
`provider system 310 to facilitate the selection of names and, consequently, identifiers from the
`
`Attorney Docket No. 19487. 33. 1. 1. 1. 1
`
`1 1
`
`Patent Application
`
`

`

`address book server and database 380. The selection interface 385 enables the selection of
`
`names from the address book. The message to be delivered is thereby addressed to the
`
`identifiers corresponding to the names selected in the selection interface 3 85. After the message
`
`is addressed, it is delivered to the specified recipients by the appropriate application from the
`
`provider device 335.
`
`[0043]
`
`Alternatively or additionally, the selection interface 385 and the applications may
`
`be included in the requestor system 305 so that the recipients of the message to be sent may be
`
`specified before the message is given to the applications included in the provider device 335
`
`for delivery. When the selection interface 385 is included in the requestor system 305, the
`
`contents of the address book server 380 may be accessed and/or transferred over the
`
`communications link 315 to the requestor system 305, Where the contents are displayed by the
`
`selection interface 385. The applications included in the provider device 335 may immediately
`
`deliver a message to the recipients that have been specified through the selection interface 385
`
`included in the requestor system 305. In addition or alternatively, the address book server and
`
`database 380 and the selection interface 385 may be included in the requestor system 305.
`
`[0044]
`
`The majority of the activity of the communications system illustrated in FIGS. 1-3
`
`involves the communication and sharing of messages and information. The users of the
`
`communications system 100, 200, or 300 may send various kinds ofinformation to one another,
`
`including e-mail messages, instant messages, digital images, address information, and alerts or
`
`reminders. Typically, a different application exists for using the communications system 100,
`
`200, or 300 to send each type of message. Within each application, a user may actively specify
`
`a list of people with which communications regularly occur using that application.
`
`[0045]
`
`People lists are lists ofidentifiers of people to Whom messages may be sent. People
`
`lists represent filtered versions ofa single list of contacts with whom a user communicates. The
`
`identifiers included in a people list are used to address messages to the people corresponding
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`12
`
`Patent Application
`
`

`

`to the identifiers when the people list that includes the identifiers is chosen. People lists may
`
`be stored in an address book or in some other central repository that may be accessed by
`
`multiple applications.
`
`[0046]
`
`Each of the applications may access the central repository of people lists when
`
`addressing a message. One or more people lists may be chosen as a recipient of the message,
`
`and the message is sent to the people corresponding to the identifiers in the people list. In this
`
`way, people lists function in the same way as e-mail addresses or screen names in that people
`
`lists are used to specify the recipients of a message. Several applications access the same central
`
`repository of people lists, so specification of people lists only needs to occur in one place at
`
`one time. Additionally or alternatively, all or a portion of the central repository of people lists
`
`may be communicated to a local device (e.g., requestor device 120, 220, or 320) for access and
`
`use by the applications on the local device. In one exemplary implementation, the people lists
`
`may be transferred to the local device for a temporary duration. Any changes to the people lists
`
`while on the local device including any additions, deletions, and edits, may be communicated
`
`to the central repository of people lists such that the central repository of people lists is updated.
`
`[0047]
`
`In some applications, people lists may be used to specify the recipients of a message
`
`or some other form of shared information. For example, a people list may be used in an e-mail
`
`application to specify the direct recipients, the carbon copied recipients, or the blind carbon
`
`copied recipients of an e-mail message. A people list may be used by an instant messaging
`
`application to address an instant message that is broadcast simultaneously to multiple people.
`
`A people list may specify the recipients of images shared through use of a digital image sharing
`
`application. A people list may specify the contacts that receive address information and updates
`
`to the address information that are sent by an address sharing application. Finally, people lists
`
`may indicate the contacts that are sent alerts and reminders from an alerting application.
`
`Attorney Docket No. 1948 7. 33. 1. 1. 1. 1
`
`13
`
`Patent Application
`
`

`

`[0048]
`
`In addition, people lists may be used as access control lists. For example, a people
`
`list may be used by an e-mail filtering application to specify the contacts from which e-mail
`
`messages are accepted. Messages from contacts included in the people list may be accepted,
`
`while messages from people not included in the people list may be blocked. On the other hand,
`
`a people list may be used by the e-mail filtering application to specify the contacts from which
`
`e-mail messages are blocked. In this case, messages from contacts included in the people list
`
`may be blocked while messages from contacts not included in the people list may be accepted.
`
`A similar behavior may be implemented by an application through which parental controls over
`
`a child account are specified. People lists may be used to specify contacts from which
`
`communications are accepted or rejected by the child account, as the case may be. Similarly,
`
`people lists may be used by an electronic journal application to specify the contacts that are
`
`allowed or disallowed access to the electronic journal.
`
`[0049]
`
`A single people list may be used by multiple applications to address multiple kinds
`
`of messages. For example, a single people list may be used to address an instant message sent
`
`by an instant messaging application, as well as specify the recipients of a set of shared images
`
`from a digital image sharing application. In addition, a single people list may be used to address
`
`an e-mail as well as an instant message that is sent to the people contained in the single people
`
`list. Moreover, a single people list may be used by a mail filtering application to specify
`
`contacts from which e-mails accepted or blocked and also by an application enabling the
`
`specification of parental controls over a child account to specify the contacts from which
`
`communications are accepted or blocked by the child account. A single people list may be used
`
`by any number of communications applications after only a single specification. For example,
`
`a single people list may be populated with contacts from whom spam e-mail messages were
`
`received in an e-mail application. The list may be used by an e-mail filtering application as
`
`Attorney Docket No. 19487. 33. 1. 1. 1. 1
`
`14
`
`Patent Application
`
`

`

`well as an application for specifying parental controls to block communications from contacts
`
`included in the list.
`
`[0050]
`
`If an identifier contained in a people list may not be used by a particular application,
`
`then the user that chose the people list may be prompted to enter an identifier that may be used
`
`by the application. For example, the user may be prompted for an e-mail address of a contact
`
`whose cellular phone number is stored in the people list when the people list is being used by
`
`an e-mail application. When the user is not prompted for a usable identifier, then the unusable
`
`identifier is omitted, and the corresponding contact is not included in the action taken on the
`
`people list. Continuing the above example, if the user is not prompted for an e—mail address,
`
`then the message being created by the e-mail application is not sent to the contact whose
`
`cellular phone number is stored in the people list.
`
`[0051]
`
`A people list is identified and selected by a name that is unique among the names
`
`of the other people lists stored in the central repository. In the event that multiple non-identical
`
`people lists are stored within the central repository with the same name, then the names of the
`
`conflicting people lists are automatically modified.
`
`[0052]
`
`People lists may be created manually or automatically. When creating a list
`
`manually, a user must specify a name for the people list as well as the identifiers of the people
`
`to be included in the people lists. When created automatically, a system may automatically
`
`detect a set of people that could include a people list. The system may prompt the user for a
`
`name of the automatically detected set of people.
`
`[0053]
`
`Referring to FIG. 4, a process 400 for automatically recognizing a set of recipients
`
`that have been repeatedly specified as recipients of messages enables the automatic
`
`specification of a people list. After a set of contacts are identified as repeated recipients of
`
`messages, the set is given a name, and that set becomes a people list that can be used to quickly
`
`specify the set of contacts as the recipients of a message in the future. The process 400 monitors
`
`Attorney Docket No. 19487. 33. 1. 1. 1. 1
`
`15
`
`Patent Application
`
`

`

`the communications sent from at least one application before suggesting that a set of contacts
`
`should be formalized into a people list.
`
`[0054]
`
`The process 400 begins with the monitoring of the messages sent by the various
`
`applications. It is i