# Patent

## Title
Community-modified profile with connection-based authorization

## Abstract

In some embodiments, disclosed techniques may include providing a profile of a first user to a second user, wherein the profile of the first user includes a first profile data; determining that the second user is permitted to modify the profile of the first user, wherein said determination includes determining that a social connection exists between the second user and the first user; receiving a second profile data from the second user, wherein the second profile data is a proposed modification to the first profile data; providing the second profile data to the first user; receiving from the first user an approval of a change to the profile of the first user, wherein the change to the profile of the first user includes the second profile data; and associating the second profile data with the profile of the first user.

## Background
CROSS REFERENCE TO RELATED APPLICATIONS
This application is a continuation of U.S. patent application Ser. No. 12/833,982, entitled COMMUNITY-MODIFIED USER DATA WITH ACCOUNTABILITY, filed Jul. 11, 2010, now U.S. Pat. No. 8,065,312, which is incorporated herein by reference for all purposes, which is a continuation of U.S. patent application Ser. No. 11/895,129, entitled COMMUNITY-MODIFIED USER DATA, filed Aug. 22, 2007, now U.S. Pat. No. 7,756,895, which is incorporated herein by reference for all purposes, which claims priority to U.S. Provisional Patent Application No. 60/839,216, entitled INFORMATION PROCESSING, filed Aug. 22, 2006, which is incorporated herein by reference for all purposes.


FIELD OF THE INVENTION
The present invention relates generally to the area of online services. More specifically, techniques for community-contributed modification of user-related data associated with an online service are disclosed.
BACKGROUND OF THE INVENTION
Online services with a strong social component have grown exponentially in the last several years. Sites such as MySpace and Facebook have garnered tens of millions of users. Many online services include user profiles, in which various information relating to a user can be displayed, such as friends, music, videos, comments, etc.
Many sites allow a user a degree of control over such data, such as selecting how to order friends, or what music or video is played when a profile page is viewed. Some sites also provide for community modifications to a particular constrained portion of a page, such as an area to leave comments about or endorsements of the user. However, current online services do not allow for community editing of profile data relating to the user associated with the profile, such as the ordering of friends, “what I like,” favorite bands, interests, physical appearance, characteristic music, videos, etc.
Community-edited content sites such as Wikipedia and other wikis offer members of a community the ability to alter content relating to a wide variety of topics. However, such community editing is generally applied toward knowledge management and does not apply to user-related data such as profile data.
Unfettered modifications by a community of user-related data could lead to problems such as digital vandalism or inappropriate content. Community-edited sites have suffered widely from such problems and have instituted various reputation systems, with mixed results. In the case of user-related data, there is an opportunity to avoid such problems by allowing modification of such data only by those users who have demonstrated themselves to be positive participants in the community based on their previous activities, by allowing a user control over the availability and extent of such editing, and by using friend relationships and other data to ascertain permission. However, current online services do not provide this control for user-related data.
Accordingly, it would be useful to enable community-based editing of user-related data, and it would be further useful to predicate the availability and/or extent of such editing on the prior actions of would-be editors.



BRIEF DESCRIPTION OF THE DRAWINGS
Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.
FIG. 1 is a diagram of a system for social profile modification, according to some embodiments.
FIG. 2 is a flow diagram of a method for modifying a profile, according to some embodiments.
FIG. 3 is a flow diagram of a method for processing profile modification permissions, according to some embodiments.
FIG. 4 is a flow diagram of a method for displaying a modification to a profile, according to some embodiments.
FIG. 5 is a flow diagram of a method for reviewing modifications to a profile, according to some embodiments.



DETAILED DESCRIPTION
The invention can be implemented in numerous ways, including as a process, an apparatus, a system, a composition of matter, a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or electronic communication links. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention.
A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
FIG. 1 is a diagram of a system for social profile modification, according to some embodiments. In this example, a profile page generator 101 may generate a profile page based on data associated with a profile data store 102. A profile page refers herein to a page (such as a page on a web site, which may for example be provided at HTML or XHTML, or syndicated via RSS or Atom) the primary function of which is to describe a user of a service such as an online social networking service, and which is under the primary control of the user so described. In some embodiments, a profile page may be topically structured, including topics such as a user's interests, likes and dislikes, physical appearance, home town, current mood, current location, current activity, biography, photos, blog, top friends, favorite places, etc. In some embodiments, a profile page may have a distinctive color scheme and/or theme music, and/or places for unstructured content such as one or more widgets or videos. A user may enter some or all profile information relating to himself or herself.
A profile page generator 101 may retrieve various data from profile data store 102, assemble it into a renderable page, and provide it, for example in response to an HTTP request. In some embodiments, a rendered page may be retrieved. In some embodiments, elements of data may be retrieved and integrated together, for example using a template which in some embodiments may include stylistic information such as a color scheme and/or layout. The use of such templates is well known to those skilled in the art.
A profile page generator 101 may retrieve data from a social relationship data store 103, which may for example provide data about one or more connections such as friend connections relating to a user whose profile page has been requested. Such data may be included in a renderable profile page. Information relating to modification permissions of one or more customizable data elements may be received from modification permission determiner 105, and modifiable data element(s) may be indicated in the assembly of the page.
A profile data store 102 may store data relating to profiles, such as text, references to objects that may appear in a profile, and metadata. Examples of a profile data store 102 include one or more files on a filesystem, one or more databases such as relational databases, one or more tables associated with which may in some embodiments use a user identifier as a key, and a combination of filesystem(s) and database(s), for example in which data in a database maps user identifiers to user-specific data stored in a filesystem. In some embodiments, a profile data store 102 may be or include an in-memory data structure such as an array, list, binary tree, or hash table. In some embodiments, such an in-memory data structure may be read from and written to persistent storage such as one or more databases and/or files.
A social relationship data store 103 may store data relating to social connections between and among users. Examples of a social relationship data store 103 include one or more files on a filesystem, one or more databases such as relational databases, one or more tables associated with which may in some embodiments use a user identifier as a key and provide one or more contacts (for example one per row) and optionally associated connection type(s) in response to a query, and a combination of filesystem(s) and database(s), for example in which data in a database maps user identifiers to user-specific connection data stored in a filesystem. In some embodiments, a social relationship data store 103 may be or include an in-memory data structure such as an array, list, binary tree, or hash table. In some embodiments, such an in-memory data structure may be read from and written to persistent storage such as one or more databases and/or files.
Modification permission determiner 105 may provide information relating to modification permissions of one or more customizable data elements to profile page generator 101 and/or modification processor 109. Modification permission determiner 105 may determine permissions for user A to modify profile data belonging to user B, for example by retrieving and processing one or more permissions relating to user B's profile or element(s) thereof from permission data store 108. In some embodiments, modification permission determiner 105 may retrieve social relationships from social relationship data store 103, for example if a modification is permitted by user B conditionally based on the existence of a connection status between user A and user B, such as a friend relationship.
Modification processor 109 may receive a request to perform a modification to a user's profile data, for example via an HTTP request. Modification processor 109 may check permissions for a requesting user to modify the requested data element(s) via modification permission determiner 105. Based on permissions, one or more requested modifications may be made to profile data store 102 and/or modification quarantine 107.
Modification quarantine 107 may contain modifications that have been made to profiles which require approval from a profile owner or other authorized party to take effect. Examples of a modification quarantine 107 include one or more files on a filesystem, one or more databases such as relational databases, one or more tables associated with which may in some embodiments use a user identifier as a key and provide one or more quarantined profile modifications (for example one per row), and a combination of filesystem(s) and database(s), for example in which data in a database maps user identifiers to user-specific connection data stored in a filesystem. In some embodiments, a modification quarantine 107 may be or include an in-memory data structure such as an array, list, binary tree, or hash table. In some embodiments, such an in-memory data structure may be read from and written to persistent storage such as one or more databases and/or files.
Modification accepter/rejecter 104 may provide a user interface (for example via HTTP in response to an HTTP request, and/or using Javascript) that enables a profile owner, or in some embodiments another authorized modifier, to review quarantined modifications in modification quarantine 107. If a user elects to accept a quarantined modification, then in this example it is applied to data in profile data store 102 and removed from modification quarantine 107. If a user elects to reject a quarantined modification, then in this example it is removed from modification quarantine 107.
Permission data store 108 may contain permission data relating to who is authorized to modify profile data and/or specific element(s) of profile data. Examples of parties and/or classes thereof for whom permissions may be stored in permission data store, indicating permission to modify (or not modify) part or all of a profile, include a friend of a profile owner, a user explicitly authorized by a profile owner, a user who has had his modification permissions elevated by accumulation of karma, for example by a high or meritorious level of usage of the social network service, and a user who has purchased the permission to modify a profile. In some embodiments, a combination of criteria may be required for a user to be permitted to modify profile data, for example explicit identification by the profile owner combined with payment or an accumulation of karma.
Examples of a permission data store 108 include one or more files on a filesystem, one or more databases such as relational databases, one or more tables associated with which may in some embodiments use a user identifier corresponding to a profile owner and/or a profile element as a key and provide one or more permission-related data, and a combination of filesystem(s) and database(s), for example in which data in a database maps user identifiers to user-specific permission-related data stored in a filesystem. In some embodiments, a permission data store 108 may be or include an in-memory data structure such as an array, list, binary tree, or hash table. In some embodiments, such an in-memory data structure may be read from and written to persistent storage such as one or more databases and/or files.
A modification authorizer 106 may provide a user interface to a profile owner, allowing review and/or modification of permissions such as those discussed in conjunction with permission data store 108. In some embodiments, a modification authorizer 106 may include the capability to view and edit permissions filtered by element, by permission level (for example by defining roles and allowing mapping of users to roles with respect to the profile owner's profile data), and/or by user.
Further details of the operation of the system of this FIG. 1 are discussed in conjunction with the remaining Figures.
FIG. 2 is a flow diagram of a method for modifying a profile, according to some embodiments. In this example, user A creates a profile (201). An example of creating a profile is to register with a social networking service and enter data. In some embodiments, such data may subsequently be edited. “User A” refers herein to any user differentiated from “user B,” and vice-versa.
User A may set modification permissions (202). In some embodiments, modification permissions may be coarse-grained, such as allowing modifications by everyone or by friends, or disallowing any modifications. In some embodiments, modification permissions may be fine-grained, such as permission regarding a particular element of profile data such as the ability to edit “top N friends” or a video or audio element. In some embodiments, a permission may apply to a user that is a friend (e.g. is connected via a friendship relationship on a social network) of the profile owner. An example of a friend is a person identified as a friend by the profile owner, for example by proactively or reactively asserting a friend relationship. In some embodiments, a permission may apply to a user explicitly authorized to make a profile modification, for example any profile modification or a profile modification of a particular element. In some embodiments, a permission may apply to a user who has had his modification privileges elevated by accumulation of karma, for example by a high or meritorious level of usage of the social network service. In some embodiments, a permission may apply to a user who has purchased the right to modify a profile. In some embodiments, a permission may apply to a role to which users may be assigned. In some embodiments, a permission may apply to user(s) based on a combination of criteria, for example explicit identification by the profile owner combined with payment or an accumulation of karma.
In some embodiments, a specification of acceptable modification(s) may be received as part of permissions setting. For example, modification options may be restricted to explicitly specified content, or restricted by an aspect of the content such as a performer (e.g. a band), a genre, and/or content certified or classified in some manner (for example excluding undesired or inappropriate content such as pornographic content).
User B may view a profile page owned by (e.g. associated with the identity of) user A (203). Such a view may result in a page request such as an HTTP request being received at a social networking service.
It may be determined whether user B has permission to modify user A's profile (204). Such determination may be made by looking up user B's permissions and/or permissions associated with user A's profile data, for example as discussed in conjunction with modification permission determiner 105 of FIG. 1.
If it is determined that user B does not have permission to modify user A's profile (204), then in this example the profile page is provided without user interface element(s) enabling modification of the profile (205). An example of providing a profile page is to provide it in response to an HTTP request, for example as HTML data.
If it is determined that user B has permission to modify user A's profile (204), then in this example the profile page is provided with one or more user interface elements enabling modification of the profile (206). In some embodiments, such a user interface element may permit dynamic editing, for example via Javascript and XmlHttpRequest. In some embodiments, such a user interface element may link to another page where a modification may be made.
An election to modify an element of the profile page may be received (207), for example a selection of a link indicating that user B wishes to perform a modification.
A modification user interface may be presented for one or more elements that user B has permission to modify (208). In some embodiments, such a user interface may be presented by providing a web page. In some embodiments, such a user interface may be presented by manipulating a document object model, for example via Javascript. In some embodiments, such a user interface may be present unconditionally for an element that user B has permission to modify. In some embodiments, a modification user interface may be specific to a selected element of page data. In some embodiments, a modification user interface may be provided for all relevant elements of page data that user B has permission to modify.
A modification may be received (209), for example via HTTP. An example of receiving a modification is to receive data containing the modification, for example as a form submission. Another example of receiving a modification is to receive data from a script such as a Javascript script, for example via an XmlHttpRequest. Another example of receiving a modification is to receive it via an API; in such embodiments, 203, 204, 205 and 206 may be omitted.
Examples of a modification include text describing the subject of a profile, one or more images, music that is to be played when a profile is loaded, one or more videos that can be played when a profile is loaded, and list of top friends such as a “top N” friends list.
It may be determined whether the modification is acceptable (210). Settings for acceptable modifications may be global and/or or specific to a profile page. For example, a modification may be restricted to explicitly specified content, or restricted by an aspect of the content such as a performer (e.g. a band), a genre, and/or content certified or classified in some manner (for example excluding inappropriate content such as pornographic content).
In some embodiments, determining whether a modification is acceptable may include confirming that user B has permission to modify relevant element(s) of user A's profile, for example as discussed in conjunction with FIG. 3.
If it is determined that the modification is not acceptable (212), then in this example the modification is rejected, and an opportunity to alter the proposed modification, or provide an alternate modification, may be provided (209). In some embodiments, an option to cancel modification may be provided.
If it is determined that the modification is acceptable (212), then in this example user B may be charged, in some embodiments (213). An example of charging user B is to debit an account associated with user B. Another example of charging user B is to deduct from a non-monetary balance, such as a karma level or a points-based scoring sustem.
The modification may be applied to user A's profile (211). An example of applying a modification to a profile is to alter profile data associated with the profile owner. In some embodiments, such a modification may include a record of the change made and/or the user making the change (e.g. in this example, user B). In some embodiments, for example in situations in which user B does not have an unrestricted right to modify user A's profile, or when user A (or a global setting) has required review of modifications, the modification to profile data may be quarantined. Quarantining a modification refers herein to storing the modification in a manner in which it is reviewable and subject to approval or rejection by an authorized party such as the owner of a profile to which the modification applies, but may not have an effect on viewing a page to which it applies for a general viewer. As an example of such storage, the modification may be stored in a modification quarantine 107 of FIG. 1.
In some embodiments, a modification may be applied to persist indefinitely. In some embodiments, a modification may be applied to persist for a limited period of time, for example a predetermined period of time or a period of time associated with a user making the modification (e.g. user B), such as a period of time associated with karma the user has accumulated or a payment the user has made.
FIG. 3 is a flow diagram of a method for processing profile modification permissions, according to some embodiments. The technique of this FIG. 3 may be used to determine how to display a profile to a visiting user, for example as discussed in conjunction with 204, 205 and 206 of FIG. 2.
In the example of this FIG. 3, user B may view a profile page owned by (e.g. associated with the identity of) user A, or an element thereof (301). Such a view may result in a page request such as an HTTP request being received at a social networking service.
Permission data associated with user A's profile may be retrieved, and it may be determined whether modification is disallowed (302). If it is determined that modification is disallowed (302), then in this example profile modification is not permitted (308). An example of not permitting profile modification is to not display a modification user interface element. Another example of not permitting profile modification is to reject a requested modification.
If it is not determined that modification is disallowed (302), then in this example it is determined whether a friend connection exists that specifies that user B is a friend of user A (303). If it is determined that such a friend relationship exists, and that user A's profile is modifiable by his or her friends, then in this example profile modification is permitted (307). An example of permitting profile modification is to display a modification user interface element. Another example of permitting profile modification is to apply a requested modification.
If it is not determined that user B is a friend of user A (303), or if permissions associated with user A's profile do not necessarily permit modification by a friend, then in this example it is determined whether user B is specifically permitted to modify user A's profile (304). If it is determined that user B is specifically permitted to modify user A's profile (304), then in this example modification is permitted (307).
If it is not determined that user B is specifically permitted to modify user A's profile (304), then in this example it is determined whether user B has sufficient karma to modify user A's profile (305). An example of determining whether a karma level associated with a user is sufficient to permit a modification is to compare a numeric karma level with a threshold, which in various embodiments may be a global threshold or a threshold specified by an owner of data to which a modification is being considered (e.g. user A).
If it is determined that user B has sufficient karma to permit modification (305), then in this example profile modification is permitted (307). In some embodiments, a deduction may be made from user B's karma level.
If it is not determined that user B has sufficient karma to permit modification (305), then in this example it is determined whether user B is associated with a paying account (306). If it is determined that user B is associated with a paying account, and that the account is in good standing for the modification (e.g. by having a balance over a threshold, or by being fully paid up), then in this example profile modification is permitted (307).
If it is determined that user B is not associated with a paying account, or that user B's account is not in good standing for the modification (306), then in this example profile modification is not permitted (308).
FIG. 4 is a flow diagram of a method for displaying a modification to a profile, according to some embodiments. In this example, user C may view a profile page owned by (e.g. associated with the identity of) user A (401). Such a view may result in a page request such as an HTTP request being received at a social networking service. “User C” refers herein to any user.
It may be determined whether user C has a privilege to see one or more authors of user-contributed modifications to the profile (402). One example of a privileged user is a user associated with the modified profile page (e.g. user A). Another example of a privileged user is a user who is a friend of the user who is associated with the modified profile page (e.g. a friend of user A). Another example of a privileged user is the user who performed the modification (e.g. user B of FIG. 2). Another example of a privileged user is a user who is a friend of the user who has performed the modification (e.g. a friend of user B of FIG. 2). Another example of a privileged user is a user with elevated privileges, for example an administrative user or a user who has been granted such permissions, for example by a high or meritorious level of usage of the social network service.
If it determined that user C does not have the privilege to see modification(s) (403), then in this example the profile page is provided without an indication of modification(s) and/or their associated author(s) (404). For example, the profile page may be provided with modifications invisible, or with an indication that a modification was made but without an indication of the author of the modification. In some embodiments, for example in embodiments in which friends of a modifier may see modifications made by the modifier, a profile page may be provided with some modifications visible and/or authorially indicated, and others may not, on the basis of a per-modification determination of privilege.
If it is determined that user C has the privilege to see modification(s) (403), then in this example the profile page is provided with an indication of modification(s) and/or their associated author(s) (405). For example, the profile page may be provided with an indication of where modification(s) were made, and in some embodiments an indication of the author(s) of such modification(s). In some embodiments, for example in embodiments in which friends of a modifier may see modifications made by the modifier, a profile page may be provided with some modifications visible and/or authorially indicated, and others may not, on the basis of a per-modification determination of privilege.
FIG. 5 is a flow diagram of a method for reviewing modifications to a profile, according to some embodiments. In this example, a user views his or her own profile (e.g. a request is received from a user to view that user's profile), or elects to review one or more modifications associated with his or her profile (501).
Information relating to one or more modifications may be provided, in some embodiments with associated modification author(s) (502). One example of providing a modification is to provide it in context in a profile page data such as HTML or XHTML data, for example visually indicated as a modification, for example by color coding or by specifying a visual boundary such as a box around a modified element, and/or with an icon or textual link indicating a modification has occurred; in some embodiments, additional details such as a time and/or author of a modification, either initially or in response to a user action such as a mouseover. Another example of providing a modification is to provide a summary of the modification in a list of modifications. Such a list may be ordered or grouped in various ways, such as by date, by modifier, or by modified element. In some embodiments, a query may be received and modifications conforming to the query (which may for example specify a modifier, a modifier role, a textual element, a time range, and/or an element) may be provided. In some embodiments, a summary may contain details of a modification such as a time, modifier, and optionally a representation of a change, such as an output of “diff.” In some embodiments, providing modification(s) may include transmitting HTML or XHTML data.
An election of an action may be received, for example by receiving an indication of a user selection of a user interface element such as a button associated with election of an action. It may be determined whether the action is to accept one or more quarantined modifications (503). If is determined that the election is to accept quarantined modification(s), then in this example one or more relevant modifications (such as specifically selected modification(s), or all modifications) are incorporated into the profile (504). An example of incorporating a modification into a profile is to alter profile data associated with the profile in accordance with the modification, and remove the modification from the quarantine, for example as discussed in conjunction with 506. Remaining modifications, if any, may be provided (502).
If it is not determined that the election is to accept a quarantined modification (503), then in this example it is determined whether the election is to reject a quarantined modification (505). If it is determined that the election is to reject a quarantined modification (505), then in this example one or more relevant modifications (such as specifically selected modification(s), or all modifications) are removed from quarantine (506). An example of removing a modification from quarantine is to remove information relating to the modification from a modification quarantine 107 of FIG. 1. Remaining modifications, if any, may be provided (502).
If it is not determined that the election is to reject a quarantined modification (505), then in this example it may be determined whether the election is to reject an unquarantined modification, e.g. a modification that has already been applied to the profile (507). If it is determined that the election is to reject an unquarantined modification (507), then in this example the modification is rolled back from the profile (508). An example of rolling back a modification from the profile is to retrieve a record relating to the modification, which includes a version of the data prior to the modification or a way to derive such data, and substituting the data. In some embodiments, a rollback may include successive rollbacks in reverse chronological order of any relevant modifications (for example, all modifications affecting a data element) through the modification being rolled back, followed (optionally) by reapplication in chronological order of modifications that are not being rolled back. These examples are illustrative and other applicable techniques for rolling back changes are known to those skilled in the art. Remaining modifications, if any, may be provided (502).
If it is not determined that the election is to reject an unquarantined modification (507), then in this example it may be determined whether the election is to finish reviewing modifications (510).
If it is determined that the election is not to finish reviewing modifications (510), then in this example remaining modifications, if any, may be provided (502). If it is determined that the election is to finish reviewing modifications (510), then in this example processing is complete (509).
Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.

## Claims

1. A method, comprising:
receiving a first profile data from a first user, wherein the first profile data is associated with the first user;
associating the first profile data with a profile of the first user;
providing the profile of the first user to a second user, wherein the second user is different from the first user, and wherein the profile includes the first profile data;
determining that the second user is permitted to modify the profile of the first user, wherein determining that the second user is permitted to modify the profile of the first user includes determining that a social connection exists between the second user and the first user;
responsive to determining that the second user is permitted to modify the profile of the first user, providing a user interface to the second user, wherein the user interface enables modification of the first profile data;
receiving a second profile data from the second user, wherein the second profile data is a proposed modification to the first profile data;
providing the second profile data to the first user;
receiving from the first user an approval of a change to the profile of the first user, wherein the change to the profile of the first user includes the second profile data;
associating the second profile data with the profile of the first user;
receiving a request for the profile of the first user from a third user; and
providing the profile of the first user to the third user, wherein the profile of the first user includes the second profile data.

2. The method of claim 1, performed at a social networking service.

3. The method of claim 1, wherein the second profile data is associated with audio.

4. The method of claim 1, wherein the second profile data is associated with video.

5. The method of claim 1, wherein the second profile data is associated with text.

6. The method of claim 1, wherein the second profile data is associated with a physical description.

7. The method of claim 1, wherein the second profile data is associated with an interest.

8. The method of claim 1, wherein the second profile data is associated with an image.

9. The method of claim 1, wherein the user interface is part of a web page on which the first profile is provided.

10. The method of claim 1, wherein the user interface links to a web page on which a second user interface enables modification of the first profile data.

11. The method of claim 1, wherein the user interface permits a proposed modification to the first profile data using Javascript and XmlHttpRequest.

12. The method of claim 1, further comprising providing the second profile data to the first user, and receiving from the first user an approval of the second profile data.

13. The method of claim 1, further comprising providing a second user interface to the first user, wherein the second user interface permits reviewing of the second profile data, and accepting or rejecting a change to the profile of the first user that includes the second profile data.

14. The method of claim 1, wherein providing the second profile data to the first user includes providing an indication that the second profile data was provided by the second user.

15. The method of claim 1, wherein providing the second profile data to the first user includes indicating a difference between the first profile data and the second profile data.

16. The method of claim 15, wherein the difference between the first profile data and the second profile data is indicated by color coding.

17. The method of claim 1, further comprising determining whether the second profile data includes inappropriate content, and rejecting the second profile data when it is determined that the second profile data includes inappropriate content.

18. A system for modifying a profile, comprising:
a processor configured to:
receive a first profile data from a first user, wherein the first profile data is associated with the first user;
associate the first profile data with a profile of the first user;
provide the profile of the first user to a second user, wherein the second user is different from the first user, and wherein the profile includes the first profile data;
determine that the second user is permitted to modify the profile of the first user, wherein determining that the second user is permitted to modify the profile of the first user includes determining that a social connection exists between the second user and the first user;
responsive to determining that the second user is permitted to modify the profile of the first user, provide a user interface to the second user, wherein the user interface enables modification of the first profile data;
receive a second profile data from the second user, wherein the second profile data is a proposed modification to the first profile data;
provide the second profile data to the first user;
receive from the first user an approval of a change to the profile of the first user, wherein the change to the profile of the first user includes the second profile data;
associate the second profile data with the profile of the first user;
receive a request for the profile of the first user from a third user; and
provide the profile of the first user to the third user, wherein the profile of the first user includes the second profile data; and

a memory coupled with the processor, wherein the memory provides instructions to the processor.

19. The system of claim 18, wherein the user interface is part of a web page on which the first profile is provided.

20. The system of claim 18, wherein the user interface links to a web page on which a second user interface enables modification of the first profile data.

21. The system of claim 18, wherein the user interface permits a proposed modification to the first profile data using Javascript and XmlHttpRequest.

22. The system of claim 18, wherein the processor is further configured to provide the second profile data to the first user, and receive from the first user an approval of the second profile data.

23. The system of claim 18, wherein the processor is further configured to provide a second user interface to the first user, wherein the second user interface permits reviewing of the second profile data, and accept or reject a change to the profile of the first user that includes the second profile data.

24. A computer program product for modifying a profile, the computer program product being embodied in a non-transitory computer readable medium and comprising computer instructions for:
receiving a first profile data from a first user, wherein the first profile data is associated with the first user;
associating the first profile data with a profile of the first user;
providing the profile of the first user to a second user, wherein the second user is different from the first user, and wherein the profile includes the first profile data;
determining that the second user is permitted to modify the profile of the first user, wherein determining that the second user is permitted to modify the profile of the first user includes determining that a social connection exists between the second user and the first user;
responsive to determining that the second user is permitted to modify the profile of the first user, providing a user interface to the second user, wherein the user interface enables modification of the first profile data;
receiving a second profile data from the second user, wherein the second profile data is a proposed modification to the first profile data;
providing the second profile data to the first user;
receiving from the first user an approval of a change to the profile of the first user, wherein the change to the profile of the first user includes the second profile data;
associating the second profile data with the profile of the first user;
receiving a request for the profile of the first user from a third user; and
providing the profile of the first user to the third user, wherein the profile of the first user includes the second profile data.

25. The computer program product of claim 24, wherein the user interface is part of a web page on which the first profile is provided.

26. The computer program product of claim 24, wherein the user interface links to a web page on which a second user interface enables modification of the first profile data.

27. The computer program product of claim 24, wherein the user interface permits a proposed modification to the first profile data using Javascript and XmlHttpRequest.

28. The computer program product of claim 24, further comprising computer instructions for providing the second profile data to the first user, and receiving from the first user an approval of the second profile data.

29. The computer program product of claim 24, further comprising computer instructions for providing a second user interface to the first user, wherein the second user interface permits reviewing of the second profile data, and accepting or rejecting a change to the profile of the first user that includes the second profile data.