(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2007/0214141 A1
`Sittig et al.
`(43) Pub. Date:
`Sep. 13, 2007
`
`US 20070214141A1
`
`(54)
`
`(76)
`
`(21)
`(22)
`
`(60)
`
`SYSTEMIS AND METHODS FOR
`GENERATING A SOCIAL TIMELINE
`
`Inventors: Aaron Sittig, Palo Alto, CA (US);
`Mark Zuckerberg, Palo Alto, CA (US)
`Correspondence Address:
`CARR & FERRELL LLP
`2200 GENG ROAD
`PALO ALTO, CA 94.303 (US)
`Appl. No.:
`11/646,206
`
`Filed:
`
`Dec. 26, 2006
`
`Related U.S. Application Data
`Provisional application No. 60/753,810, filed on Dec.
`23, 2005.
`
`Publication Classification
`
`(51) Int. Cl.
`G06F 7/30
`
`(2006.01)
`
`(52) U.S. Cl. ................................................. 707/7, 702/189
`
`(57)
`
`ABSTRACT
`
`A system, method, and computer program for generating a
`Social timeline is provided. A plurality of data items asso
`ciated with at least one relationship between users associated
`with a social network is received, each data item having an
`associated time. The data items are ordered according to the
`at least one relationship. A social timeline is generated
`according to the ordered data items.
`
`RECEIVE A PLURALITY OF DATA ITEMS ASSOCIATED WITHAT LEAST ONE
`RELATIONSHIP BETWEEN USERS ASSOCIATED WITH A SOCIAL NETWORK,
`EACH DATA ITEM HAVING AN ASSOCIATED TIME;
`
`702
`
`ORDER THE DATA ITEMS ACCORDING TO THE ASSOCIATED TIME
`
`704
`
`
`
`GENERATE A SOCIAL TIMELINE ACCORDING TO THE ORDERED DATA ITEMS
`
`1
`
`TIKTOK 2004
`Triller v. TikTok
`IPR2022-00180
`
`

`

`Patent Application Publication Sep. 13, 2007 Sheet 1 of 7
`
`US 2007/021.4141 A1
`
`
`
`:
`
`
`
`: s
`
`S
`
`2
`
`

`

`Patent Application Publication Sep. 13, 2007 Sheet 2 of 7
`
`US 2007/021.4141 A1
`
`
`
`?InpOWN
`
`LZ-OZ
`
`3
`
`

`

`Patent Application Publication Sep. 13, 2007 Sheet 3 of 7
`
`US 2007/021.4141 A1
`
`
`
`009
`
`peuôJepun
`
`800Z
`
`09
`
`90
`
`4
`
`

`

`Patent Application Publication Sep. 13, 2007 Sheet 4 of 7
`
`US 2007/021.4141 A1
`
`
`
`
`
`
`
`& 0C] uuor Moux noÁ op woH
`
`5
`
`

`

`Patent Application Publication Sep. 13, 2007 Sheet 5 of 7
`
`US 2007/021.4141 A1
`
`
`
`009
`
`6
`
`

`

`Patent Application Publication Sep. 13, 2007 Sheet 6 of 7
`
`US 2007/021.4141 A1
`
`RECEIVE DATA ITEMS AND CALENDARDATES ASSOCIATED WITH THE DATA 592
`ITEMS FOR ONE ORMORE RELATIONSHIPS BETWEEN TWO USERS
`
`GENERATE CHRONOLOGICAL LIST OF CALENDARDATES IN DESCENDING -504
`ORDER
`
`GENERATE CATEGORIES CORRESPONDING TO THE CHRONOLOGICAL
`LISTING
`
`e
`
`IDENTIFY NAMES OF INDIVIDUALS CORRESPONDING TO CATEGORIES
`
`OBTAIN PHOTOS CORRESPONDING TO THE IDENTIFIED NAMES
`
`DISPLAY SOCIAL TIMELINE
`
`FIG. 6
`
`608
`YN/
`
`610
`
`2
`
`7
`
`

`

`Patent Application Publication Sep. 13, 2007 Sheet 7 of 7
`
`US 2007/021.4141 A1
`
`RECEIVE A PLURALITY OF DATA ITEMS ASSOCIATED WITHAT LEAST ONE
`RELATIONSHIPBETWEENUSERS ASSOCIATED WITH A SOCIAL NETWORK,
`EACH DATA ITEM HAVING AN ASSOCIATED TIME;
`
`702
`
`ORDER THE DATA ITEMS ACCORDING TO THE ASSOCIATED TIME
`
`704
`
`
`
`
`
`GENERATE A SOCIAL TIMELINE ACCORDING TO THE ORDERED DATA ITEMS
`
`7O6
`
`FIG. 7
`
`8
`
`

`

`US 2007/021.4141 A1
`
`Sep. 13, 2007
`
`SYSTEMS AND METHODS FOR GENERATING A
`SOCIAL TIMELINE
`
`0015 FIG. 7 is a flow diagram of an exemplary process
`for generating a social timeline.
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`0001. The present application claims the benefit and
`priority of U.S. provisional patent application Ser. No.
`60/753,810 filed on Dec. 23, 2005 and entitled “Systems and
`Methods for Social Timeline,” which is herein incorporated
`by reference.
`
`BACKGROUND OF THE INVENTION
`
`0002)
`1. Field of the Invention
`0003. The present invention relates generally to social
`networking, and more particularly to systems and methods
`for generating a social timeline.
`0004 2. Description of Related Art
`0005 Conventionally, people have networked with one
`another by joining Social clubs, attending Social events,
`meeting friends through other friends, and so forth. The
`Internet has made keeping in touch with friends and
`acquaintances more convenient for many people. For other
`people, the Internet provides a social forum for networking
`and meeting new people.
`0006 For many people, the Internet more recently rep
`resents the principal way in which the people meet new
`friends and remain in touch with existing friends. Thus, the
`Internet provides a medium for a complex array of interac
`tions between vast numbers of individuals.
`0007. In order to facilitate communications between the
`vast numbers of individuals, various Social networking
`websites have developed in recent years. Social networking
`websites can provide organizational tools and forums for
`allowing these individuals to interact with one anther via the
`Social networking website. Many users prefer to limit com
`munications to specific groups of other users.
`
`SUMMARY OF THE INVENTION
`0008. The present invention provides a system and
`method for generating a social timeline. A plurality of data
`items associated with at least one relationship between users
`associated with a social network is received, each data item
`having an associated time. The data items are ordered
`according to the at least one relationship. A social timeline
`is generated according to the ordered data items.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0009 FIG. 1 is a block diagram of an exemplary envi
`ronment for Social mapping;
`0010 FIG. 2 illustrates an exemplary social network
`engine;
`FIG. 3 illustrates an exemplary friends list;
`0011
`0012 FIG. 4 illustrates an exemplary relationship editor
`page.
`0013 FIG. 5 illustrates an exemplary social timeline;
`0014 FIG. 6 is a flow diagram of an exemplary process
`for ordering data for a social timeline; and
`
`DETAILED DESCRIPTION
`0016 FIG. 1 is a block diagram of an exemplary envi
`ronment for generating a social timeline. One or more users
`102, such as a user 102A, a user 102B, and a user 102N, are
`in communication with a Social network engine 106 via a
`network 104. The social network engine 106 may comprise
`a social networking website, one or more servers operating
`the Social networking website, or any other device or appli
`cation capable of providing Social networking services via
`the network 104. The users 102 can access the services
`provided by the social network engine 106 via the network
`104. Optionally, one or more of the users 102 may be able
`to access the social network engine 106 directly.
`0017. The users 102 may use a computing device, such as
`a laptop or desktop computer, a cellular telephone, a per
`Sonal digital assistant (PDA), a set top box, and so forth to
`access the social network engine 106. The users 102 can
`view data about social network members, view a Social
`timeline, enter data about themselves and possibly others,
`join Social network groups, and so forth. The users 102 are
`typically members of a social networking website associated
`with the social network engine 106, for example, and thus
`comprise the Social network members.
`0018. According to exemplary embodiments, a user 102,
`such as the user 102A, identifies one or more other members
`associated with the social network engine 106, such as the
`user 102B and the user 102N, with which the user 102A
`wants to build a relationship or establish or alter the details
`of an existing relationship. Using the Social network engine
`106, the user 102A enters the details about the relationship.
`The Social network engine 106 then sends data comprising
`the details from the user 102A to the other users (i.e., user
`102B and user 102N). The user 102B and the user 102N may
`then provide input in response to the data. The response may,
`for example, modify the data.
`0019. The relationship with the user 102B and the user
`102N may confirmed, based on the input, by the social
`network engine 106. Alternatively, the existence of the
`relationship may be denied, according to Some embodi
`ments. Any type of confirmation and/or input may be
`utilized to alter, deny, and/or establish the relationship
`between the user 102A and the user 102B and the user 102N.
`0020. The relationship may comprise any type of rela
`tionship that exists between two of the users 102. For
`example, the user 102A and the user 102B may have worked
`together, been classmates, be related, have dated, and so
`forth. More than one relationship may exist between the two
`users. For example, the user 102A and the user 102B may
`have both worked together and dated.
`0021. The data may then be ordered. For example, the
`user 102A may specify that the relationship with the user
`102B is older than the relationship with the user 102N. In
`other words, the user 102A may enter detailed data that
`indicates calendar dates, years, and other timing information
`about the relationship. The social network engine 106 can
`then order the data by the indicated times and generate a
`social timeline based on the ordered data. The social time
`line may indicate when certain events related to the rela
`
`9
`
`

`

`US 2007/021.4141 A1
`
`Sep. 13, 2007
`
`tionships occurred, for example, Such as in the year 2004,
`the user 102A met the user 102B and traveled with the user
`102B to Argentina. Any type of events, details, and other
`data related to the relationship may be provided by the users
`102 and utilized to generate the social timeline.
`0022 Referring now to FIG. 2, an exemplary social
`network engine is illustrated. Such as the Social network
`engine 106 discussed in FIG.1. A communications interface
`202 is provided in association with the social network
`engine 106 for receiving data from and sending data to the
`users 102. The users 102 can send any type of data to the
`social network engine 106 via the network 104 and vice
`versa. For example, a user 102 can provide details about
`relationships with other users 102 that the social network
`engine 106 can utilize to generate the social timeline for the
`user 102, such as the user 102A, based on the details.
`0023 Typically, the users 102 access a website associated
`with the social network engine 106. For example, the social
`network engine 106 may host a social networking website
`where the users 102 can visit to interact with one another.
`The website can display various types of data about the users
`102 to one another, such as the social timeline, profile
`information, or relationships a particular user, such as the
`user 102A, has with other users, such as the user 102B and
`the user 102N. The users 102 may belong to particular
`communities within the Social networking website. Such as
`communities categorized according to School attended,
`workplace, geographical location, and so forth.
`0024. A social relationship editor module 204 is provided
`for editing and/or entering the Social relationships that the
`users 102 have with one another. For example, the user 102A
`can specify a particular relationship with the user 102B and
`the user 102N. The user 102B and/or the user 102N may
`then be asked to confirm the particular relationship specified
`by the user 102A. Accordingly, each relationship established
`via the social networking website is verified by two or more
`of the users 102 in the relationship. A social relationship
`editor display page associated with the Social relationship
`editor module 204 is discussed further in association with
`FIG. 4.
`0.025 The social relationship editor module 204 can track
`the one or more relationships between the users 102. The
`Social relationship editor module 204 can also generate and
`send communications to the users 102 to confirm the rela
`tionships identified. As discussed herein, the users 102 are
`typically members of the social networking website.
`Accordingly, the users 102 interact with one another via the
`social network website associated with the social network
`engine 106 and can identify relationships with one another
`in order to facilitate the interactions, or for any other reason.
`0026. The social relationship editor module 204 may also
`be utilized by the users 102 to enter data about the relation
`ships with other users 102, as discussed herein. The data
`may then be utilized to generate the social timeline for the
`users 102. Such as what events happened each day, month,
`or year to the user 102A.
`0027. A relationship storage module 206 is provided for
`storing one or more databases including the relationships
`between the users 102. The relationship storage module 206
`can utilize any type of storage device or medium to store the
`database. For example, the relationship storage module 206
`
`can store the databases in hard drives, on CD ROMS, in
`DRAM, and so forth. Any type of storage device or storage
`medium for storing information about the relationships,
`profile data associated with the users 102, or any other
`information associated with the users 102, is within the
`Scope of various embodiments. According to some embodi
`ments, the relationship storage module 206 can store the
`social timeline generated for each of the users 102.
`0028. A social timeline module 208 is also provided in
`association with the social network engine 106. The social
`timeline module 208 utilizes the relationship data provided
`by the users 102. The data provided by the users 102 about
`various relationships is then ordered by the times the rela
`tionships occurred, or events associated with the relation
`ships occurred, as indicated by the users 102. For example,
`the user 102A may indicate that the user 102A took a class
`with user 102B in the Fall of 2003. The data about the class
`is then ordered in relation to other data provided by the user
`102A and the social timeline for the user 102A is generated.
`0029. The user 102A may be able to request, via a button,
`portal, link, and so forth, a display page showing the Social
`timeline associated with the user 102A. Other users 102 may
`also be able to request the social timeline for the user 102A.
`A different social timeline may be generated for different
`communities associated with the user 102A, such as one
`Social timeline for the workplace community, another Social
`timeline for a college community, etc.
`0030) A display module 210 may be associated with the
`social network engine 106. The display module 210 may
`generate a display for displaying the Social timeline to the
`users 102. The social timeline may be displayed to the user
`102 that provides the social timeline data items, such as
`events and timeframes associated with the events, or the
`social timeline may be displayed to other users 102 that want
`to see one another's social timelines. The user 102A may
`adjust privacy settings to identify other users 102 or groups
`of users 102 that can access the social timeline for the user
`102A
`0031. Although FIG. 2 shows various modules associated
`with the Social network engine 106 (e.g., the communica
`tions interface 202, the social relationship editor module
`204, the relationship storage module 206, and the social
`timeline module 208), fewer or more modules may be
`associated with the social network engine 106 and still fall
`within the scope of various embodiments.
`0032 FIG.3 illustrates an exemplary friends list 300. The
`friends list 300 may be displayed on a page associated with
`the social network engine 106. The friends list 300 may be
`selected by the users 102 via a friends list tab 302. A social
`timeline tab 304 may also be selected. The social timeline
`tab 304 may display events associated with the relationships
`with friends on the friends list 300 according to a timeline.
`0033) A pictorial or graphical representation 306 for each
`of the users 102 may be included as part of the friends list
`300. For example, the user 102A may utilize a photo of the
`user A 102, while the user 102B may utilize a cartoon
`character to represent the user 102B. Any type of picture,
`photo, graphic, icon, symbol, and so forth may be utilized to
`represent the users 102 via the pictorial or graphical repre
`sentation 306.
`0034 Biographical data 308 is displayed about each of
`the users 102 that are listed. For example, the name, status,
`
`10
`
`

`

`US 2007/021.4141 A1
`
`Sep. 13, 2007
`
`year of graduation, field of study, and so forth may be
`displayed as the biographical data 308 for each of the users
`102. Any type of data about the listed users 102 may
`comprise the biographical data 308.
`0035 A user action area 310 may be associated with the
`friends lists 300 and may be displayed in association with
`each of the users 102. In FIG. 3, the user action area 310 is
`displayed to the right of the biographical data 308 for each
`of the users 102. However, the user action area 310, the
`biographical data 308, and/or the pictorial/graphical repre
`sentation 306 may be displayed anywhere. For example, the
`pictorial/graphical representation 306 may be accessed,
`check-marked, highlighted, and so forth in order to display
`the user action area 310.
`0036) The user action area 310 allows the users 102 to
`select one or more actions to perform in association with a
`particular user, such as the user 102A, about which the
`biographical data 306 is being viewed. For example, the
`users 102 can choose to send the users 102 an email or other
`message via the 'send message' function, to utilize a "poke
`her function to be directed to a pop-up or similar screen,
`confirming that the user 102 wishes to “poke a displayed
`user. An announcement may be sent to the displayed user
`informing the displayed user that the displayed user has been
`“poked' by another user 102.
`0037. The user action area 306 may also allow the users
`102 to utilize a “view friends’ function in order to view the
`data about friends of the users 102, to utilize a “view photos”
`function to view photos associated with the user, and/or an
`“add to friends’ function to request addition to a friends
`group of the user 102. Various other options may be accessed
`via the user action area 306. For example, the users 102 may
`be able to access stories about a particular user, Such as the
`user B 102B, via the user action area 306.
`0038 For example, the users 102 can choose to send the
`users 102 an email or other message via the 'send message'
`function, to utilize a “poke her function to be directed to
`a pop-up or similar screen, confirming that the user 102
`wishes to "poke a displayed user. An announcement may be
`sent to the displayed user informing the displayed user that
`the displayed user has been “poked by another user 102.
`0.039 The user action area 306 may also allow the users
`102 to utilize a “view friends’ function in order to view the
`data about friends of the users 102, to utilize a “view photos'
`function to view photos associated with the user, and/or an
`“add to friends’ function to request addition to a friends
`group of the user 102. Various other options may be accessed
`via the user action area 306. For example, the users 102 may
`be able to access stories about a particular user, Such as the
`user B 102B, via the user action area 306.
`0040. The friends list 300 may be utilized for displaying
`any type of data about the users 102. The friends list 300
`shown in FIG. 3 is an exemplary display page for displaying
`data about various users belonging to a community. Profile
`data about individual users or groups of users is shown via
`the friends list 300. Data about the users 102 belonging to
`various communities, stories about the users 102, and so
`forth, may also be displayed via the friends list 300, or any
`other display page.
`0041) The friends list 300 in FIG.3 may also be utilized,
`according to exemplary embodiments, to display a social
`
`timeline associated with the friends on the friends list 300.
`The friends list 300 may be generated by the social rela
`tionship editor module 304 and be displayed in response to
`a search or filter function initiated by the user 102A. As
`discussed herein, the data about the users 102 for the friends
`list 300 may be stored in a database by the relationship
`storage module 206 or another storage module (not shown)
`for storing data about the users 102.
`0042. The friends list 300 may be utilized to display a
`directory of the users 102, a collection of the users 102, a
`directory of established relationships associated with the
`user 102A, or any other information about the users 102. As
`discussed herein, any of the data associated with the users
`102 may be displayed utilizing the friends list 300 or any
`other display mechanism associated with the Social network
`engine 106.
`0043. The friends list 300 can also display the users 102
`in an ascending or descending order according to a chro
`nology associated with the relationships the users 102 have
`with other users, such as by generating the Social timeline
`discussed herein. For example, the user 102N may be
`displayed before the user 102B in a listing requested by the
`user 102A because the user 102A has known the user 102N
`for a longer period of time than the user 102B. The users 102
`can be displayed according to common groups, association
`with common events, situations, or occurrences, and so
`forth.
`0044 FIG. 4 illustrates an exemplary relationship editor
`page 400. The relationship editor page 400 illustrated in
`FIG. 4 can be utilized to question the users 102 about the
`relationships with other users 102. The relationship editor
`page 400 may be utilized to learn details about the relation
`ships, such as timing information for generating the Social
`timeline. The relationship editor page 400 may be sent in
`response to a request from a particular user, Such as the user
`102A, to form or otherwise establish a relationship with
`another user, such as the user 102B, and/or to edit details
`about the relationship, such as providing details about spe
`cific events and/or timeframes associated with the specific
`eVentS.
`0045. A relationship inquiry 402 may be utilized to
`establish the subject matter for the relationship editor page
`400. For example, FIG. 4 illustrates the relationship editor
`page 400 for the relationship inquiry 402"How do you know
`John Do? However, the relationship inquiry 402 may
`comprise any inquiry, such as "Is the information provided
`by John Do about your relationship accurate'? Any type of
`relationship inquiry 402 may be provided in association with
`the relationship editor page 400.
`0046. A relationship type identifier 404 may be displayed
`for allowing a user 102 to select and/or identify the rela
`tionship the user 102 has with other users 102. For example,
`the user 102A may select that the user 102A lived with the
`user 102B, worked with the user 102B, and/or knows the
`user 102B through a friend. One or more of the relationship
`identifiers 404 may be selected. As discussed herein, the
`users 102 may have more than one relationship.
`0047 A relationship details identifier 406 allows the
`users 102 to further specify the nature of the relationship.
`For example, the relationship details identifier 406 may
`establish where the users 102 lived together, where the users
`
`11
`
`

`

`US 2007/021.4141 A1
`
`Sep. 13, 2007
`
`102 worked together, which friends the users 102 have in
`common, and so forth. Although only one relationship
`details identifier 406 is illustrated for each relationship type
`identifier 404, more than one relationship details identifier
`406 associated with each of the relationship type identifiers
`404 may be provided.
`0.048. A timeframe identifier 408 may also be provided in
`association with the relationship editor page 400. The time
`frame identifier 408 may be utilized to establish a time or
`timeframe associated with the relationship type identifier
`404. For example, the timeframe identifier 408 can specify
`when the users 102 lived together, worked together, dated,
`and so forth. The timeframe identifier 408 data may then be
`ordered and utilized to generate the Social timeline, dis
`cussed herein.
`0049. The relationship inquiry 402, the relationship type
`identifier 404, the relationship details identifier 406, and/or
`the timeframe identifier 408 may be selectable via a drop
`down menu, a text entry box, a check box, and/or via any
`other selection method or combination of selection methods.
`According to some embodiments, the relationship inquiry
`402 is pre-populated with selections when sent to the users
`102 with whom confirmation of the relationship is sought.
`Further, the relationship editor page 400 can be automati
`cally populated, partially or wholly, utilizing data already
`stored about the users 102 and/or the relationships the users
`102 have established with one another on previous occa
`sions. For example, the relationship editor page 400 can be
`sent to the user 102A to confirm that the timeframe data
`about the relationship specified by the relationship editor
`page 400 is correct.
`0050. The arrangement, presentation, display, and/or sub
`ject matter described in connection with FIGS. 3 and 4 may
`vary and still remain within the scope of various embodi
`ments. Additional timeframe questions may be utilized in
`association with the social relationship page 400 or addi
`tional types of the biographical data 304 may be displayed
`via the friends list 300.
`0051. For example, the user 102A may complete the
`relationship editor page 400 by selecting from the relation
`ship inquiry 402, the relationship type identifier 404, the
`relationship details identifier 406, the timeframe identifier
`408, and/or any other identifiers that may be provided via the
`relationship editor page 400, in order to provide details
`about the relationship the user 102A has with the user 102B.
`The user 102B may then be sent the pre-populated relation
`ship editor page 400 and asked to confirm the data provided
`by the user 102A. The user 102B can confirm the accuracy
`of the data on the relationship editor page 400, modify the
`data on the relationship editor page 400, add to the data on
`the relationship editor page 400, and/or deny the accuracy of
`the data on the relationship editor page 400.
`0.052 The details about the relationship established via
`the relationship editor page 400 can be stored by the
`relationship storage module 206 and a relationship database
`utilized to access timeframe information provided by the
`user 102 about each data item to organize the data items
`provided by the users 102 associated with the relationships
`between the users 102 and to generate the social timeline.
`Alternatively, the social timelines or timeline data from the
`user 102B may be utilized to populate times for the data
`
`items associated with the user 102A, such as when the user
`102A fails to provide the times associated with the data
`items.
`0053. The subject matter of the inquiries and the data
`associated with the relationship editor page 400 may include
`any topics, such as membership in a club, a team, a church,
`etc.; common courses, classes, institutions, programs of
`study, etc.; common travels, journeys, adventures, parties,
`conferences, etc., common familial relationships, friends,
`acquaintances, romantic partners or interests, musical inter
`ests, restaurants, bars, pubs, etc., whether two or more of the
`users 102 met randomly, accidentally, purposefully, via
`online activities, etc.; and/or whether two or more of the
`users 102 have never met, etc.. Any type of data can be
`established via the relationship editor page 400, as discussed
`herein.
`0054 As discussed herein, a confirmation request may be
`sent to the users 102 in response to completion of the
`relationship editor page 400. The social relationship editor
`module 204 can send a communication, for example, to the
`user 102B that the user 102A Selected the user 102B as a
`person the user 102A may know or with whom the user
`102A wishes to establish a relationship. The user 102B may
`elect to confirm the data provided by the user 102A, adjust
`or edit the data, send a message to the user 102A regarding
`the relationship, deny the existence of the relationship, add
`data about the relationship, and so forth. If the user 102B
`edits or adds to the data, the user 102A may be asked to
`confirm the added or edited data, according to exemplary
`embodiments.
`0055 According to some embodiments, the user 102A
`may complete portions of the relationship editor page 400,
`while leaving other portions for the user 102B to complete.
`For example, the user 102A may want the user 102B to
`complete portions of the relationship editor page 400
`describing timeframes for the relationship between the user
`102A and the user 102B.
`0056 Referring to FIG. 5, an exemplary social timeline
`page 500 is illustrated. The social timeline page 500 may be
`accessed via the social timeline tab 304 discussed in FIG. 3
`or in any other manner. Such as via a link, a button, a search
`request, and so forth.
`0057. A time identifier 502 is displayed on the social
`timeline page 500. The time identifier 502 indicates the time
`in which events or other data items associated with the user
`102A may be displayed. The social timeline page 500 for the
`user 102A may include events associated with each rela
`tionship the user 102A has with other users 102. The data
`about the relationships, such as classes taken with other
`users 102, timeframe the user 102A dated another user 102,
`etc. may be ordered according to dates within the time
`identifier 502, the dates or times for each of the data items
`provided by the user 102A. The data may then be displayed
`within the time identifier 502 according to an ascending or
`descending order, for example.
`0058. A member list 504 may be displayed according to
`the time identifier 502, according to some embodiments. As
`shown in FIG. 5, the member list 504 includes names of
`members grouped under various categories, such as cowork
`ers, classmates, travel companions, hookups, coursemates,
`Summer/abroad friends, relationships, teammates, and so
`
`12
`
`

`

`US 2007/021.4141 A1
`
`Sep. 13, 2007
`
`forth. The member list 504 may include the names of the
`members that the user 102A met in the year specified, for
`example. Any of the users 102 can click on, or otherwise
`access, the name of a particular member (i.e., users 102) to
`access further data about timeframes associated with the
`user 102A's relationship with the particular member,
`depending upon the privacy settings selected by the user
`102A
`0059) Photos 506 may be displayed in association with
`each of the time identifiers 502 listed as part of the social
`timeline page 500. According to some embodiments, a user
`102 may click on the photos 506 to access specific time
`frame data about the user 102A's relationship with the users
`102 in the photos 506. Other users 102 can also submit
`photos that correlate with the time identifier 502 specified on
`the social timeline page 500. Any type of data can be utilized
`to generate the Social timeline and to be displayed via the
`social timeline page 500. Further, some of the time identi
`fiers 502 may not have any names or events listed.
`0060. The photos 506 may be selected automatically,
`based on profiles associated with the users 102 or any other
`data. The photos 506 may be automatically updated when a
`user 102 uploads or otherwise provides updated photos 506
`that the social network engine 106 determines to be relevant
`to the Social timeline. According to Some embodiments, the
`user 102 can approve or reject added or edited photos, such
`as the photos 506 shown in FIG. 5, before the photos 506 are
`uploaded or otherwise provided for display with the social
`timeline.
`0061 According to exemplary embodiments, a social
`timeline for each of the users 102 may be displayed. The
`social timeline for each of the users 102 may list all of the
`events or other data pertaining to the relationship a particular
`user 102, such as the user 102A, has in common with one or
`more of the other users 102. For example, a social timeline
`for user A's 102A relationship with the user 102B may be
`generated. The Social timeline in this example may list the
`events the user 102A and the user 102B had in common for
`each year, such as the user 102A and the user 102B traveled
`to Mexico together in March of 2003, attended a New Year's
`party together in January of 2004, threw a summer barbeque
`together in June of 2004, and so forth. The time identifier
`502 may utilize any increment of time. Such as day, month,
`every two years, etc. to display a list of names, events, and
`so forth associated with the users 102.
`0062) The social timeline module 208 may generate
`and/or display the Social timeline page 500, according to
`Some embodiments. However, any module, application,
`device, or componen