Shared content feed access in chat

Abstract

Systems and methods herein describe generating a federated content feed accessible from within a dialog thread. The system and method access a chat session between users on a messaging platform, receive input from a selected user from within the chat session, the input corresponding to a joint content feed, the joint content feed including shared content related to all users of the chat session and personalized content only related to the selected user, in response to receiving the input, the user interface associated with the chat session is replaced with the user interface associated with the federated content feed, and the user interface associated with the federated content feed is displayed on the computer device associated with the selected user.

Description

[0001] Priority Statement

[0002] This application claims priority to U.S. Provisional Application No. 63 / 496,241, filed April 14, 2023, and U.S. Patent Application No. 18 / 464,701, filed September 11, 2023, each of which is incorporated herein by reference in its entirety. Technical Field

[0003] The implementations described herein generally relate to public media content. More specifically, but not as a limitation, the implementations described herein describe the generation of federated content with public media content for members of a conversation thread. Background Technology

[0004] Messaging apps allow users to share media content, such as images and videos, between different friend groups. Each friend group can be customized based on specific interests, hobbies, and conversation topics. Attached Figure Description

[0005] In the accompanying drawings (which are not necessarily drawn to scale), similar reference numerals may describe similar parts in different views. To facilitate identification of any particular element or action being discussed, one or more of the highest-order digits in the reference numerals indicate the drawing number in which the element was first introduced. Some non-limiting examples are shown in the accompanying drawings:

[0006] Figure 1 It is a graphical representation of a networked environment in which the present disclosure can be deployed, based on some examples.

[0007] Figure 2 It is a graphical representation of a messaging system with both client-side and server-side functionality, based on some examples.

[0008] Figure 3 It is a graphical representation based on examples such as data structures maintained in a database.

[0009] Figure 4 It is a graphical representation based on some example messages.

[0010] Figure 5 The process for displaying a joint content feed accessed within a communication thread between at least two users on a social media platform is illustrated according to an example.

[0011] Figure 6 This is a diagram of the user interface based on an example chat session.

[0012] Figure 7The interface shown is an example of a navigation bar for accessing federated content.

[0013] Figure 8 A silent notification within an interface according to one implementation is shown.

[0014] Figure 9 The illustration shows the process for generating shared content that can be accessed within a communication thread between at least two users on a social media platform, based on an example.

[0015] Figure 10 A system with a head-mounted wearable device is shown, based on some examples.

[0016] Figure 11 It is a graphical representation of a machine in the form of a computer system, based on some examples, within which a set of instructions can be executed to cause the machine to perform any or more of the methods discussed herein.

[0017] Figure 12 It is a block diagram illustrating an example of a software architecture that can be implemented therein. Detailed Implementation

[0018] The following paragraphs describe systems and methods for generating shared content feeds for users within a conversation thread. A conversation thread can be initiated from the interface of a messaging system. Conversation threads exist between users “connected” to each other within a social media application. Each member in a group conversation thread can access the content feed from within the conversation thread. For example, an icon or button is visible within the conversation thread, and when the icon or button is selected, the content feed is initiated within the social media application. In some examples, the content feed can be accessed by performing an up swipe action within the conversation thread's user interface. Content feeds include public media content (e.g., videos and images). Content feeds include shared content with public media content relevant to all members of the group conversation thread, as well as personalized content tailored to each member in the group. Shared content is only visible when accessed from within the conversation thread. Content feeds can also be accessed from outside the conversation thread and from other entry points within the social media application. When accessing a content feed from outside the conversation thread, the content feed only includes personalized content feeds for a specific user of the social media application.

[0019] Users of conversational threads can simultaneously view public media content and receive notifications from conversational threads (or other aspects of the messaging system) without interrupting their viewing experience. Users can also seamlessly share public media content to conversational threads with a single action, without navigating multiple interface screens.

[0020] Content to be shared can be determined by analyzing the overlap of profile data and interests of group members. For example, shared content can be selected based on the overlap of demographic data, location data, or friendship or connection data within social media applications. It can also be selected based on the overlap of public media content category interests, subscriptions to public media content creators, and other activity data that can be retrieved from a given user's interactions with their personalized content feeds.

[0021] When content feeds are accessed from within a chat thread, shared content ranks higher than personalized content. A higher ranking for shared content can result in it being displayed before personalized content, more prominently displayed within the user interface, or any reasonable combination thereof. Members interacting with content in a shared content feed within a group chat thread can cause that specific content to rank higher among other members of the group chat thread within the shared content feed.

[0022] Further details regarding the generation of shared content feeds are described in the following paragraphs.

[0023] Networked computing environment

[0024] Figure 1 This is a block diagram illustrating an example interactive system 100 for facilitating interactions on a network, such as exchanging text messages, making text audio and video calls, or playing games. Interactive system 100 includes multiple user systems 102, each of which hosts multiple applications including an interactive client 104 and other applications 106. Each interactive client 104 is communicatively coupled to other instances of the interactive client 104 (e.g., hosted on corresponding other user systems 102), an interactive server system 110, and a third-party server 112 via one or more communication networks including a network 108 (e.g., the Internet). The interactive client 104 may also communicate with the locally hosted applications 106 using an application programming interface (API).

[0025] Each user system 102 may include multiple user devices, such as mobile devices 114, head-mounted wearable devices 116, and computer client devices 118, that are communicatively connected to exchange data and messages.

[0026] Interactive client 104 interacts with other interactive clients 104 and with interactive server system 110 via network 108. The data exchanged between interactive clients 104 (e.g., interaction 120) and between interactive client 104 and interactive server system 110 includes functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0027] Interactive server system 110 provides server-side functionality to interactive client 104 via network 108. While some functions of interactive system 100 are described herein as being performed by interactive client 104 or interactive server system 110, the location of certain functions within interactive client 104 or interactive server system 110 may be a design choice. For example, it may be technically preferred that specific technologies and functions are initially deployed within interactive server system 110, but later migrated to interactive client 104 of user system 102 with sufficient processing power.

[0028] The interactive server system 110 supports various services and operations provided to the interactive client 104. Such operations include sending data to and receiving data from the interactive client 104, and processing data generated by the interactive client 104. This data may include message content, client device information, geolocation information, media enhancements and overlays, message content persistence conditions, entity relationship information, and live event information. Data exchange within the interactive system 100 is activated and controlled via functions available through the user interface (UI) of the interactive client 104.

[0029] Specifically, the focus now shifts to interactive server system 110. Application Programming Interface (API) server 122 is coupled to interactive server 124 and provides it with a programming interface, making the functionality of interactive server 124 accessible to interactive client 104, other applications 106, and third-party server 112. Interactive server 124 is communicatively coupled to database server 126, thereby facilitating access to database 128, which stores data associated with the interactions processed by interactive server 124. Similarly, web server 130 is coupled to interactive server 124 and provides a web-based interface to interactive server 124. For this purpose, web server 130 handles incoming network requests via Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0030] Application Programming Interface (API) server 122 receives and sends interactive data (e.g., command and message payloads) between interactive server 124 and user system 102 (as well as interactive client 104 and other applications 106) and third-party server 112. Specifically, API server 122 provides a set of interfaces (e.g., routines and protocols) that can be invoked or queried by interactive client 104 and other applications 106 to activate the functionality of interactive server 124. Application Programming Interface (API) server 122 exposes various functions supported by interaction server 124, including account registration; login functionality; sending interactive data from one interaction client 104 to another interaction client 104 via interaction server 124; transferring media files (e.g., images or videos) from interaction client 104 to interaction server 124; setting up collections of media data (e.g., stories); retrieving the friend list of users in user system 102; retrieving messages and content; adding and deleting entities (e.g., friends) against an entity relationship graph (e.g., entity graph 310); locating friends in the entity relationship graph; and opening (e.g., application events associated with interaction client 104).

[0031] Interactive server 124 hosts multiple systems and subsystems, as shown below. Figure 2 Describe it.

[0032] System Architecture

[0033] Figure 2 This is a block diagram illustrating further details of an interactive system 100 according to some examples. Specifically, the interactive system 100 is shown as including an interactive client 104 and an interactive server 124. The interactive system 100 includes multiple subsystems supported on the client side by the interactive client 104 and on the server side by the interactive server 124. In some examples, these subsystems are implemented as microservices. A microservice subsystem (e.g., a microservice application) may have components that enable the microservice subsystem to operate independently and communicate with other services. Example components of a microservice subsystem may include:

[0034] • Functional logic: Functional logic implements the functions of the microservice subsystem and represents the specific capabilities or functions provided by the microservice.

[0035] • API Interface: Microservices can use lightweight protocols such as REST or messaging to communicate with each other through well-defined APIs or interfaces. The API interface defines the inputs and outputs of a microservice subsystem and how it interacts with other microservice subsystems of the interactive system 100.

[0036] • Data storage: The microservice subsystem can be responsible for its own data storage, which can be in the form of a database, cache, or other storage mechanism (e.g., using database server 126 and database 128). This allows the microservice subsystem to operate independently of other microservices in the interactive system 100.

[0037] • Service discovery: Microservice subsystems can find and communicate with other microservice subsystems in the interacting system 100. The service discovery mechanism enables microservice subsystems to locate and communicate with other microservice subsystems in a scalable and efficient manner.

[0038] • Monitoring and logging: Microservice subsystems may need to be monitored and logged to ensure availability and performance. Monitoring and logging mechanisms enable the tracking of the health and performance of microservice subsystems.

[0039] In some examples, the interactive system 100 may employ a monolithic architecture, a service-oriented architecture (SOA), a function-as-a-service (FaaS) architecture, or a modular architecture:

[0040] The example subsystem is discussed below.

[0041] The image processing system 202 provides various functions that enable users to capture and enhance (e.g., annotate or otherwise modify or edit) media content associated with a message.

[0042] The camera device system 204 includes (e.g., in a camera device application) control software that (e.g., directly or via an operating system) interacts with and controls the hardware camera device hardware of the user system 102 to modify and enhance real-time images captured and displayed via the interactive client 104.

[0043] Communication system 206 is responsible for enabling and processing various forms of communication and interaction within interactive system 100, and includes messaging system 208, audio communication system 212, and video communication system 210. Messaging system 208 is responsible for enabling temporary or time-limited access to content by interactive client 104. Messaging system 208 includes (e.g., in a short-lived timer system) multiple timers that selectively enable access (e.g., for presentation and display) of messages and associated content via interactive client 104 based on duration and display parameters associated with a message or set of messages (e.g., a story). Audio communication system 212 enables and supports audio communication (e.g., real-time audio chat) between multiple interactive clients 104. Similarly, video communication system 210 enables and supports video communication (e.g., real-time video chat) between multiple interactive clients 104.

[0044] User management system 214 is operationally responsible for managing user data and profiles, and maintaining entity information about users of interactive system 100 and the relationships between users (e.g., stored in entity table 308, entity diagram 310, and profile data 302).

[0045] The collection management system 216 is operationally responsible for managing collections or sets of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) can be organized into “event galleries” or “event stories.” Such collections can be made available for a specified time period (e.g., the duration of the event to which the content relates). For example, content related to a concert can be available as a “story” for the duration of the concert. The collection management system 216 can also be responsible for publishing icons that notify the user interface of the interactive client 104 of the availability of specific collections. The collection management system 216 includes curation functions that enable collection managers to manage and curate specific content collections. For example, a curation interface enables event organizers to curate collections of content related to a specific event (e.g., removing inappropriate content or redundant messages). Additionally, the collection management system 216 employs machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, users may be compensated for including user-generated content in a collection. In such cases, the collection management system 216 operates to automatically pay such users for using their content.

[0046] Map system 218 provides various geographic location (e.g., geolocation) functions and supports the presentation of map-based media content and messages by interactive client 104. For example, map system 218 enables the display (e.g., stored in profile data 302) of user icons or avatars on the map to indicate the current or past location of the user's "friends" within the context of the map, as well as media content generated by such friends (e.g., a collection of messages including photos and videos). For example, on the map interface of interactive client 104, messages posted by a user from a specific geographic location to interactive system 100 can be displayed to the specific user's "friends" within the context of that specific location on the map. Users can also share their location and status information with other users of interactive system 100 via interactive client 104 (e.g., using an appropriate status avatar), where such location and status information is similarly displayed to selected users within the context of the map interface of interactive client 104.

[0047] External resource system 220 provides interactive client 104 with an interface to communicate with remote servers (e.g., third-party server 112) to launch or access external resources (i.e., applications or applets). Each third-party server 112 hosts applications or smaller versions of applications (e.g., game applications, utility applications, payment applications, or ride-sharing applications) based on markup languages ​​(e.g., HTML5). Interactive client 104 can launch web-based resources (e.g., applications) by accessing HTML5 files from the third-party server 112 associated with the web-based resource. The application hosted by third-party server 112 is programmed in JavaScript using a software development kit (SDK) provided by interactive server 124. The SDK includes application programming interfaces (APIs) with functionality that can be called or activated by the web-based application. Interactive server 124 hosts a JavaScript library that provides access to a given external resource for specific user data of interactive client 104. HTML5 is an example of a technology for programming games, but applications and resources programmed using other technologies can be used.

[0048] To integrate the SDK's functionality into the web-based resource, the third-party server 112 downloads the SDK from the interactive server 124, or the third-party server 112 otherwise receives the SDK. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the interactive client 104 into the web-based resource.

[0049] The SDK stored on the interactive server system 110 effectively bridges the gap between external resources (e.g., application 106 or applet) and the interactive client 104. This provides users with a seamless experience communicating with other users on the interactive client 104 while preserving the look and feel of the interactive client 104. To bridge communication between the external resources and the interactive client 104, the SDK facilitates communication between the third-party server 112 and the interactive client 104. A bridging script running on the user system 102 establishes two unidirectional communication channels between the external resources and the interactive client 104. Messages are sent asynchronously between the external resources and the interactive client 104 via these communication channels. Each SDK function activation is sent as a message and callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with that callback identifier.

[0050] By using the SDK, not all information from the interactive client 104 is shared with the third-party server 112. The SDK limits which information is shared based on the needs of the external resources. Each third-party server 112 provides the interactive server 124 with an HTML5 file corresponding to the web-based external resource. The interactive server 124 can add a visual representation (e.g., box design or other graphics) of the web-based external resource to the interactive client 104. Once the user selects the visual representation or instructs the interactive client 104 to access the features of the web-based external resource through the interactive client 104's GUI, the interactive client 104 obtains the HTML5 file and instantiates the resource for accessing the features of the web-based external resource.

[0051] Interactive client 104 presents a graphical user interface (GUI) for an external resource (e.g., a login page or title screen). During, before, or after presenting the login page or title screen, interactive client 104 determines whether the initiated external resource has previously been authorized to access the user data of interactive client 104. In response to determining that the initiated external resource has previously been authorized to access the user data of interactive client 104, interactive client 104 presents another GUI for the external resource, including its functionality and characteristics. In response to determining that the initiated external resource has not previously been authorized to access the user data of interactive client 104, after displaying the login page or title screen of the external resource for a threshold time period (e.g., 3 seconds), interactive client 104 slides up a menu for authorizing the external resource to access user data (e.g., animating the menu to appear from the bottom of the screen to the middle or other part of the screen). This menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user selection of the accept option, interactive client 104 adds the external resource to the list of authorized external resources and allows the external resource to access user data from interactive client 104. External resources are authorized by the interactive client 104 to access user data under the OAuth 2 framework.

[0052] Interactive client 104 controls the type of user data shared with external resources based on the type of authorized external resource. For example, it provides access to a first type of user data (e.g., a two-dimensional avatar of a user with or without different avatar characteristics) to external resources including full-scale applications (e.g., application 106). As another example, it provides access to a second type of user data (e.g., payment information, a user's two-dimensional avatar, a user's three-dimensional avatar, and avatars with various avatar characteristics) to external resources including smaller versions of the application (e.g., a web-based version of the application). Avatar characteristics include different ways of customizing the appearance and feel of an avatar (e.g., different poses, facial features, clothing, etc.).

[0053] The advertising system 222 is operationally designed to enable third parties to purchase advertisements to be presented to end users via the interactive client 104, and also handles the delivery and presentation of these advertisements.

[0054] Artificial intelligence and machine learning system 224 provides various services to different subsystems within interaction system 100. Communication system 206 and messaging system 208 can use artificial intelligence and machine learning system 224 to analyze communication patterns and provide insights into how users interact with each other, as well as provide intelligent message classification and tagging, such as classifying messages based on sentiment or topic. Artificial intelligence and machine learning system 224 can also provide chatbot functionality to message interactions 120 between user systems 102 and between user systems 102 and interaction server system 110. Artificial intelligence and machine learning system 224 can also cooperate with audio communication system 212 to provide speech recognition and natural language processing capabilities, enabling users to interact with interaction system 100 using voice commands.

[0055] The federated content feed system 226 generates federated content feeds for display within a conversation thread between two or more users in a social media application. The federated content feed includes public media content with shared content relevant to all members of the conversation thread, as well as personalized content unique to each member of the conversation thread. (The following is a continuation of the previous paragraph.) Figure 9 Further details regarding the joint content feed system 226 are described.

[0056] Data Architecture

[0057] Figure 3 This is a schematic diagram illustrating a data structure 300 that can be stored in a database 304 of an interactive server system 110, according to certain examples. Although the contents of the database 304 are shown as including multiple tables, it should be understood that data can be stored in other types of data structures, such as object-oriented databases.

[0058] Database 304 includes message data stored in message table 306. For any given message, this message data includes at least message sender data, message receiver (or recipient) data, and payload. See below for reference. Figure 3 Further details describe information that can be included in the message and is contained within the message data stored in message table 306.

[0059] Entity table 308 stores entity data and (e.g., by reference) links to entity diagram 310 and profile data 302. Entities for which records are maintained in entity table 308 can include individuals, company entities, organizations, objects, locations, events, etc. Regardless of entity type, any entity whose data is stored in the interactive server system 110 can be an identified entity. Each entity is assigned a unique identifier and an entity type identifier (not shown).

[0060] Entity Graph 310 stores information about the relationships and associations between entities. As an example only, such relationships can be social, professional (e.g., working in a common company or organization), interest-based, or activity-based. Some relationships between entities can be one-way, such as an individual user subscribing to digital content from a business or publishing user (e.g., a newspaper or other digital media channel, or a brand). Other relationships can be two-way, such as the "friendship" between individual users of Interactive System 100.

[0061] Certain licenses and relationships can be attached to each relationship, and also to each direction of the relationship. For example, a two-way relationship (e.g., a friendship between individual users) can include authorization for the posting of digital content items between the individual users, but certain restrictions or filters can be imposed on the posting of such digital content items (e.g., based on content characteristics, location data, or time of day data). Similarly, a subscription relationship between an individual user and a business user can impose varying degrees of restrictions on the posting of digital content from the business user to the individual user, and can significantly restrict or prevent the posting of digital content from the individual user to the business user. A specific user, as an example of an entity, can (e.g., through privacy settings) record certain restrictions in the record for that entity within entity table 308. Such privacy settings can be applied to all types of relationships in the context of interaction system 100, or selectively applied to certain types of relationships.

[0062] Profile data 302 stores various types of profile data about a specific entity. Based on privacy settings specified by the specific entity, profile data 302 can be selectively used and presented to other users of the interaction system 100. In the case of an individual, profile data 302 includes, for example, a username, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a set of such avatar representations) selected by the user. A specific user can then selectively include one or more of these avatar representations within the content of messages transmitted via the interaction system 100 and on a map interface displayed to other users by the interaction client 104. The set of avatar representations may include "status avatars," which present a graphical representation of a status or activity that the user can choose to transmit at a specific time.

[0063] In the case that the entity is a group, in addition to the group name, members and various settings for the relevant group (e.g., notifications), the profile data 302 for the group may similarly include one or more avatars associated with the group.

[0064] Database 304 also stores enhancement data, such as overlays or filters, in enhancement table 312. Enhancement data is associated with and applied to videos (video data is stored in video table 314) and images (image data is stored in image table 316).

[0065] In some examples, filters are displayed as overlays on images or videos during presentation to the receiving user. Filters can be of various types, including user-selected filters from a set of filters presented to the sending user by the interactive client 104 while the sending user is composing a message. Other types of filters include geolocation filters (also known as geographic filters), which can be presented to the sending user based on geographic location. For example, geolocation filters specific to nearby or particular locations can be presented by the interactive client 104 within the user interface based on geolocation information determined by the Global Positioning System (GPS) unit of the user system 102.

[0066] Another type of filter is a data filter, which can be selectively presented to the sending user by the interactive client 104 based on other inputs or information collected by the user system 102 during the message creation process. Examples of data filters include the current temperature at a specific location, the sending user's current speed, the battery life of the user system 102, or the current time.

[0067] Other augmented data that can be stored in image table 316 includes augmented reality content items (e.g., corresponding to an application "lens" or augmented reality experience). Augmented reality content items can be real-time special effects and sounds that can be added to images or videos.

[0068] Collection table 318 stores data about collections of messages and associated image, video, or audio data, compiled into collections (e.g., stories or galleries). The creation of a specific collection can be initiated by a specific user (e.g., each user for whom records are maintained in entity table 308). A user can create "personal stories" in the form of collections of content created and sent / broadcast by that user. For this purpose, the user interface of interactive client 104 may include user-selectable icons that allow the sending user to add specific content to his or her personal story.

[0069] The collection can also constitute a "live story," which is a collection of content from multiple users created manually, automatically, or using a combination of manual and automatic technologies. For example, a "live story" can constitute a curated stream of user-submitted content from various locations and events. Users whose client devices have location services enabled and who are at a co-located event at a specific time can be presented with the option to contribute content to a specific live story, for example, via the user interface of interactive client 104. Live stories can be identified to a user by interactive client 104 based on their location. The end result is a "live story" told from a collective perspective.

[0070] Another type of content collection is called a "location story," which allows users of user system 102 located in a specific geographic location (e.g., on a college or university campus) to contribute to a specific collection. In some examples, contributions to a location story may employ secondary authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on a university campus).

[0071] As mentioned above, video table 314 stores video data, which in some examples is associated with messages for which records are maintained within message table 306. Similarly, image table 316 stores image data associated with messages whose message data is stored in entity table 308. Entity table 308 can associate various enhancements from enhancement table 312 with various images and videos stored in image table 316 and video table 314.

[0072] Database 304 also includes an activity table 320, which includes interaction information between the first user and the second user and their corresponding personalized feeds. The interaction information also includes previously shared public media content between the first user and the second user within their dialogue thread. A shared aspect table 322 includes common aspects between the first user's data, the first user's activity data, the second user's data, and the activity data of the second user.

[0073] Data communication architecture

[0074] Figure 4 This is a schematic diagram illustrating the structure of message 400 according to some examples, generated by interactive client 104 for transmission to another interactive client 104 via interactive server 124. The content of a particular message 400 is used to populate message table 306 within database 304 accessible by interactive server 124. Similarly, the content of message 400 is stored in memory as "in-transit" or "in-flight" data for user system 102 or interactive server 124. Message 400 is shown to include the following example components:

[0075] • Message Identifier 402: A unique identifier that identifies message 400.

[0076] • Message text payload 404: The text to be generated by the user via the user interface of user system 102 and included in message 400.

[0077] • Message image payload 406: Image data captured by the camera device component of the user system 102 or retrieved from the memory component of the user system 102 and included in the message 400. The image data for the sent or received message 400 can be stored in the image table 316.

[0078] • Message video payload 408: Video data captured by the camera device component or retrieved from the memory component of the user system 102 and included in the message 400. The video data for the sent or received message 400 can be stored in the image table 316.

[0079] • Message audio payload 410: Audio data captured by the microphone or retrieved from the memory component of the user system 102 and included in message 400.

[0080] • Message enhancement data 412: Enhancement data (e.g., filters, labels, or other annotations or enhancements) representing enhancements to be applied to the message image payload 406, message video payload 408, or message audio payload 410 of message 400. Enhancement data for the sent or received message 400 can be stored in enhancement table 312.

[0081] • Message duration parameter 414: A parameter value, in seconds, indicating the amount of time that the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) should be presented to the user via the interactive client 104 or made accessible to the user.

[0082] • Message geolocation parameter 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the message's content payload. Multiple message geolocation parameter 416 values ​​may be included in the payload, each of which is associated with a content item included in the content (e.g., a specific image within the message image payload 406 or a specific video within the message video payload 408).

[0083] • Message Story Identifier 418: An identifier value that identifies one or more sets of content (e.g., “story” identified in set table 318) associated with a specific content item in the message image payload 406 of message 400. For example, the identifier value can be used to associate multiple images within the message image payload 406 with multiple sets of content, respectively.

[0084] • Message Tag 420: Each message 400 can be labeled with multiple tags, each of which indicates the subject of the content included in the message payload. For example, in the case where a specific image depicts an animal (e.g., a lion) is included in the message image payload 406, the tag value can be included within the message tag 420 indicating the relevant animal. The tag value can be manually generated based on user input, or it can be automatically generated using, for example, image recognition.

[0085] • Message sender identifier 422: An identifier (e.g., message sending system identifier, email address, or device identifier) ​​indicating the user of the user system 102 on which message 400 is generated and from which message 400 is sent.

[0086] • Message receiver identifier 424: An identifier (e.g., message sending and receiving system identifier, email address, or device identifier) ​​indicating the user of the user system 102 to which message 400 is addressed.

[0087] The content (e.g., values) of each component of message 400 can be pointers to locations in tables where content data values ​​are stored. For example, image values ​​in message image payload 406 can be pointers to locations (or their addresses) within image table 316. Similarly, values ​​in message video payload 408 can point to data stored in image table 316, values ​​in message enhancement data 412 can point to data stored in enhancement table 312, values ​​in message story identifier 418 can point to data stored in set table 318, and values ​​in message sender identifier 422 and message receiver identifier 424 can point to user records stored in entity table 308.

[0088] Figure 5 The illustration shows a process 500 for displaying federated content accessed within a communication thread between at least two users on a social media platform, according to one example. In one example, a processor in federated content feeding system 226, a processor in communication system 206, a processor in messaging system 208, a processor in client system 102, a processor in interactive server system 110, or any combination thereof, may perform the operations in process 500.

[0089] In Operation 502, the processor accesses a chat session between at least two users on a messaging platform.

[0090] In operation 504, the processor receives input from a selected user among at least two users within the user interface associated with the chat session. The input corresponds to a federated content feed, which includes shared content related to at least two users associated with the chat session and personalized content related only to the selected user.

[0091] In some examples, the input may involve selecting a button that appears within the chat session. Figure 6 The chat session interface 604 is shown. Users can select optional icon 602 to access syndicated content feeds.

[0092] In some examples, the input may involve touchscreen gestures (e.g., a swipe in a given direction). Figure 7 An interface 702 with a navigation bar 706 is shown. Interface 704 is displayed when the navigation bar 706 is swiped. The user can swipe further upwards to access the federated content feed. It should be understood that any reasonable optional user interface element or gesture (based on touchscreen or computer vision) can be used to access the federated content feed.

[0093] In operation 506, in response to receiving input, the processor replaces the user interface associated with the chat session with a user interface associated with the federated content feed. The user interface associated with the federated content feed includes a set of public media content items (e.g., images and videos). Each of the shared content and personalized content includes images, videos, and other public multimedia content.

[0094] In operation 508, the processor causes a user interface associated with the federated content to be displayed on a computer device associated with the selected user.

[0095] In some examples, the processor determines that the selected user is viewing public media content in the federated content feed from within a user interface associated with the federated content feed. The processor receives a notification from a second user among at least two users associated with the chat session. The notification may include any user activity occurring within the chat session (e.g., new messages, new reactions to previous messages, phone calls, video calls, etc.). In response to this determination and the received notification, the processor generates a silent notification that does not interrupt the selected user's viewing experience of the public media content and causes the silent notification to be displayed in a separate section of the user interface associated with the federated content feed. Figure 8 An example of a silent notification is shown in the figure. Figure 8An interface 806 with a silent notification 802 is shown. As shown in interface 806, the silent notification 802 does not visually interrupt public media content 810. Similarly, interface 808 includes a silent notification 804. The silent notification 804 does not visually interrupt public media content 812.

[0096] In some examples, the processor receives a selection of public media content in a federated content feed from a selected user. This selection can be a selectable user interface element (e.g., a button or icon) placed near or overlapping the public media content. In response to receiving a selection, the processor causes a transparent overlay window to be displayed. The transparent overlay window allows the selected user to continue viewing the public media content and includes a dialog box from which the processor can receive input from the selected user. For example, a user might want to share the selected public media content with other members of a group during a chat session. The user can select an icon that allows them to enter text, graphics, voice annotations, or other user input while simultaneously viewing the selected public media content. Once the user is ready to share their input and the selected public media content, they can easily do so with a single action. The processor receives a second selection of an icon within the user interface associated with the federated content feed, and in response to receiving the second selection, the processor automatically shares the input from the transparent overlay window and the selected public media content to the chat session while maintaining the user interface of the federated content feed displayed on the computer device associated with the selected user.

[0097] Figure 9 The illustration shows a process 900 for generating shared content for access within a communication thread between at least two users on a social media platform, according to one example. In one example, a processor in a federated content feeding system 226, a processor in a communication system 206, a processor in a messaging system 208, a processor in a client system 102, a processor in an interactive server system 110, or any combination thereof, can perform the operations in process 900.

[0098] Although the following operations are described using the first user and the second user, it should be understood that processing 900 can be implemented in any group conversation thread, where there are at least two users, each on their own separate computing device.

[0099] In operation 902, the processor accesses a chat session (e.g., a conversation thread) between a first user on a first computer device and a second user on a second computer device.

[0100] In operation 904, the processor accesses first user data, first activity data, and first personalized media content associated with a first user. The first personalized media content includes public media content associated with the first user data and the first activity data. The first user data can be accessed from a social media profile associated with the first user (e.g., profile data 302). Profile data 302 may also include a list of content creators subscribed to by the user and category interests associated with the public media content (e.g., sports, fashion, food bloggers, etc.). The first user data may also include information such as demographic data. The first activity data includes interaction information associated with the first personalized media content. Interaction information includes the amount of time spent viewing public media content items that are part of the first personalized media content, and the user's reactions to public media content items that are part of the first personalized media content (e.g., sharing content items, "liking" or "disliking" content items, "commenting" on content items, "following" the creator of content items).

[0101] In operation 906, the processor accesses second user data, second activity data, and second personalized media content associated with the second user. The second personalized media content includes public media content related to the second user data and the second activity data. An example of user data and activity data was described above in conjunction with operation 904.

[0102] In operation 908, the processor generates a shared dataset based on identifying common aspects among the first user data, the first activity data, the second user data, and the second activity data. Common aspects can be determined by identifying overlaps in the profile data 302, other user data, and activity data. For example, if the first user is interested in recipe content and the second user is interested in restaurant reviews, the processor determines that "food" is a common aspect and presents food-related content in the shared content.

[0103] In some examples, the processor receives an instruction from a first computing device regarding recommended public media content from the first personalized content provider. This instruction could be an action such as a user's reaction to a video (e.g., liking or disliking the video, or commenting on it). In response to receiving this instruction, the processor adds recommended public media content for display as part of the shared content. If a content item is added to the shared content as a result of receiving this instruction, that content item can be ranked higher than other content within the shared content. Therefore, the shared content displayed on both the first and second computing devices can be continuously updated even when the user accesses their personalized content feed outside of a chat conversation.

[0104] In operation 910, the processor generates shared content based on the shared dataset, including public media content associated with the shared dataset. In some examples, the processor accesses previously shared public media content from within a conversation thread or chat session and generates shared content based on the shared dataset and the previously shared public media content. In some examples, the processor identifies and includes trending public media content in the shared content even if it does not include common aspects identified between each user.

[0105] In operation 912, the processor causes a combined content feed, comprising shared content and first personalized content, to be displayed to a first computer device, and causes a combined content feed, comprising shared content and second personalized content, to be displayed to a second computer device. Each of the shared content and personalized content includes images, videos, and other public multimedia content. Only the combined content feed is displayed when accessed from within a chat session. For example, a first user selects a user interface element (e.g., a button) from within the chat session user interface. When a user interface element is selected, the processor causes the combined content feed to be displayed on the first computer device.

[0106] In some examples, shared content ranks higher than personalized content within a federated content feed. For instance, shared content may appear first within a federated content feed or before personalized content. In some examples, shared content is displayed in a prominent position within a federated content feed (e.g., centered or with a border or other marker to attract attention to the shared content).

[0107] Systems with head-worn devices

[0108] Figure 10 A system 1000 including a head-worn wearable device 116 with a selector input device is shown according to some examples. Figure 10 This is a high-level functional block diagram of an example head-mounted wearable device 116 that is communicatively coupled to mobile devices 114 and various server systems 1004 (e.g., interactive server system 110) via various networks 108.

[0109] The head-mounted wearable device 116 includes one or more camera devices, each of which may be, for example, a visible light camera 1006, an infrared emitter 1008, and an infrared camera 1010.

[0110] Mobile device 114 connects to head-mounted wearable device 116 using both low-power wireless connection 1012 and high-speed wireless connection 1014. Mobile device 114 is also connected to server system 1004 and network 1016.

[0111] The head-mounted wearable device 116 also includes two image displays in the image display 1018 of the optical components. These two image displays 1018 of the optical components include an image display associated with the left lateral side of the head-mounted wearable device 116 and an image display associated with the right lateral side of the head-mounted wearable device 116. The head-mounted wearable device 116 also includes an image display driver 1020, an image processor 1022, low-power circuitry 1024, and high-speed circuitry 1026. The image displays 1018 of the optical components are used to present images and videos to the user of the head-mounted wearable device 116, including images that may include a graphical user interface.

[0112] The image display driver 1020 commands and controls the image display 1018 of the optical components. The image display driver 1020 can directly deliver image data to the image display 1018 of the optical components for presentation, or it can convert the image data into a signal or data format suitable for delivery to the image display device. For example, the image data can be video data formatted according to compression formats such as H.264 (MPEG-4 Part 10), HEVC, Theora, Dirac, RealVideo RV40, VP8, VP9, ​​etc., while still image data can be formatted according to compression formats such as Portable Network Group (PNG), Joint Photo Experts Group (JPEG), Tagged Image File Format (TIFF), or Exchangeable Image File Format (EXIF), etc.

[0113] The head-worn device 116 includes a frame and a handle (or leg) extending laterally from the frame. The head-worn device 116 also includes a user input device 1028 (e.g., a touch sensor or a press button), comprising an input surface on the head-worn device 116. The user input device 1028 (e.g., a touch sensor or a press button) is used to receive input selections from a user for manipulating a graphical user interface of a presented image.

[0114] Figure 10 The components shown for the head-worn wearable device 116 are located on one or more circuit boards (e.g., PCBs or flexible PCBs) in the frame or legs. Alternatively or additionally, the depicted components may be located in the modules, frame, hinge, or nose bridge of the head-worn wearable device 116. The left and right visible light camera devices 1006 may include digital camera elements, such as complementary metal-oxide-semiconductor (CMOS) image sensors, charge-coupled devices, camera lenses, or any other corresponding visible light or light-capturing elements that can be used to capture data, including images of scenes with unknown objects.

[0115] The head-mounted wearable device 116 includes a memory 1002 that stores instructions for performing a subset or all of the functions described herein. The memory 1002 may also include a storage device.

[0116] like Figure 10 As shown, the high-speed circuit 1026 includes a high-speed processor 1030, a memory 1002, and a high-speed wireless circuit 1032. In some examples, an image display driver 1020 is coupled to the high-speed circuit 1026 and operated by the high-speed processor 1030 to drive the left and right image displays in the image display 1018 of the optical components. The high-speed processor 1030 can be any processor capable of managing the high-speed communication and operation of any general-purpose computing system required by the head-worn device 116. The high-speed processor 1030 includes the processing resources required to manage high-speed data transmission over a high-speed wireless connection 1014 to a wireless local area network (WLAN) using the high-speed wireless circuit 1032. In some examples, the high-speed processor 1030 executes the operating system of the head-worn device 116, such as a LINUX operating system or another such operating system, and this operating system is stored in the memory 1002 for execution. Among other duties, the high-speed processor 1030, which executes the software architecture of the head-worn device 116, manages the data transmission using the high-speed wireless circuit 1032. In some examples, the high-speed wireless circuit 1032 is configured to implement the Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard, also referred to herein as Wi-Fi®. In some examples, the high-speed wireless circuit 1032 can implement other high-speed communication standards.

[0117] The low-power wireless circuitry 1034 and high-speed wireless circuitry 1032 of the head-mounted wearable device 116 may include a short-range transceiver (Bluetooth™) and a wireless wide-area network transceiver, a wireless local area network transceiver, or a wide-area network transceiver (e.g., cellular or Wi-Fi®). The mobile device 114, including transceivers communicating via low-power wireless connection 1012 and high-speed wireless connection 1014, can be implemented using the architectural details of the head-mounted wearable device 116, as can other components of the network 1016.

[0118] Memory 1002 includes any storage device capable of storing various data and applications, including camera data generated by the left and right visible light imaging devices 1006, infrared imaging device 1010, and image processor 1022, as well as images generated for display on an image display in an optical component image display 1018 via image display driver 1020. While memory 1002 is shown as integrated with high-speed circuitry 1026, in some examples, memory 1002 may be a separate, independent component of the head-mounted wearable device 116. In some such examples, electrical wiring may provide a connection from image processor 1022 or low-power processor 1036 to memory 1002 via a chip including high-speed processor 1030. In some examples, high-speed processor 1030 may manage addressing of memory 1002 such that low-power processor 1036 will activate high-speed processor 1030 whenever a read or write operation involving memory 1002 is required.

[0119] like Figure 10 As shown, the low-power processor 1036 or high-speed processor 1030 of the head-mounted wearable device 116 may be coupled to a camera device (visible light camera 1006, infrared emitter 1008 or infrared camera 1010), an image display driver 1020, a user input device 1028 (e.g., a touch sensor or a press button), and a memory 1002.

[0120] The head-mounted wearable device 116 is connected to a host computer. For example, the head-mounted wearable device 116 is paired with the mobile device 114 via a high-speed wireless connection 1014 or connected to the server system 1004 via a network 1016. The server system 1004 may be one or more computing devices as part of a service or network computing system, for example, it includes a processor, memory, and network communication interfaces to communicate with the mobile device 114 and the head-mounted wearable device 116 via the network 1016.

[0121] Mobile device 114 includes a processor and a network communication interface coupled to the processor. The network communication interface allows communication via network 1016, low-power wireless connection 1012, or high-speed wireless connection 1014. Mobile device 114 may also store at least a portion of the instructions for generating binaural audio content in the memory of mobile device 114 to implement the functions described herein.

[0122] The output components of the head-worn wearable device 116 include visual components, such as displays (e.g., liquid crystal displays (LCDs), plasma display panels (PDPs), light-emitting diode (LED) displays, projectors, or waveguides). The image display of the optical components is driven by an image display driver 1020. The output components of the head-worn wearable device 116 also include acoustic components (e.g., speakers), haptic components (e.g., vibration motors), other signal generators, etc. The input components (e.g., user input devices 1028) of the head-worn wearable device 116, mobile device 114, and server system 1004 may include alphanumeric input components (e.g., keyboards, touchscreens configured to receive alphanumeric input, photoelectric keyboards, or other alphanumeric input components), pointing-based input components (e.g., mice, touchpads, trackballs, joysticks, motion sensors, or other pointing instruments), haptic input components (e.g., physical buttons, touchscreens that provide position and force for touch or touch gestures, or other haptic input components), audio input components (e.g., microphones), etc.

[0123] The head-mounted wearable device 116 may also include additional peripheral device elements. Such peripheral device elements may include biometric sensors, additional sensors, or display elements integrated with the head-mounted wearable device 116. For example, peripheral device elements may include any I / O components, including output components, motion components, positioning components, or any other such elements described herein.

[0124] For example, biometric components include those for detecting expressions (e.g., hand gestures, facial expressions, vocal expressions, body posture, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), and identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition). Biometric components may include brain-computer interface (BMI) systems that allow communication between the brain and external devices or machines. This can be achieved by recording brain activity data, converting that data into a format that can be understood by a computer, and then using the resulting signals to control the device or machine.

[0125] Examples of BMI technology types include:

[0126] • Brain-based brain-computer interfaces (BMIs) use electrodes placed on the scalp to record electrical activity in the brain.

[0127] • Invasive BMI, which uses electrodes surgically implanted in the brain.

[0128] • Optogenetics BMI uses light to control the activity of specific nerve cells in the brain.

[0129] Any biometric data collected by the biometric component is captured and stored only with user approval and is deleted upon user request. Furthermore, such biometric data may be used for very limited purposes (e.g., authentication). To ensure restricted and authorized use of biometric information and other personally identifiable information (PII), access to this data is limited to authorized personnel (if applicable). Any use of biometric data may be strictly limited to authentication purposes, and such biometric data may not be shared or sold to any third party without the user's explicit consent. In addition, appropriate technical and organizational measures are implemented to ensure the security and confidentiality of this sensitive information.

[0130] Moving components include accelerometer components (e.g., accelerometers), gravity sensor components, rotation sensor components (e.g., gyroscopes), etc. Positioning components include position sensor components (e.g., GPS receiver components) for generating position coordinates, Wi-Fi or Bluetooth™ transceivers for generating positioning system coordinates, altitude sensor components (e.g., altimeters or barometers that detect air pressure, from which altitude can be obtained), orientation sensor components (e.g., magnetometers), etc. Such positioning system coordinates can also be received from mobile device 114 via low-power wireless circuit 1034 or high-speed wireless circuit 1032, through low-power wireless connection 1012 and high-speed wireless connection 1014.

[0131] Machine architecture

[0132] Figure 11This is a schematic representation of machine 1100, within which instructions 1102 (e.g., software, program, application, app, or other executable code) can be executed to cause machine 1100 to perform any or more of the methods discussed herein. For example, instructions 1102 can cause machine 1100 to perform any or more of the methods described herein. Instructions 1102 transform the general, unprogrammed machine 1100 into a specific machine 1100 programmed to perform the described and illustrated functions in the described manner. Machine 1100 can operate as a standalone device or can be coupled (e.g., networked) to other machines. In a networked deployment, machine 1100 can operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. Machine 1100 may include, but is not limited to, server computers, client computers, personal computers (PCs), tablet computers, laptop computers, netbooks, set-top boxes (STBs), personal digital assistants (PDAs), entertainment media systems, cellular phones, smartphones, mobile devices, wearable devices (e.g., smartwatches), smart home devices (e.g., smart appliances), other smart devices, web devices, network routers, network switches, network bridges, or any machine capable of sequentially or otherwise executing instructions 1102 specifying actions to be taken by machine 1100. Furthermore, although only a single machine 1100 is shown, the term "machine" should also be considered as a collection of machines that individually or jointly execute instructions 1102 to perform any one or more of the methods discussed herein. For example, machine 1100 may include user system 102 or any of a plurality of server devices forming part of interactive server system 110. In some examples, machine 1100 may also include both client and server systems, wherein certain operations of a particular method or algorithm are performed on the server side and certain operations of that particular method or algorithm are performed on the client side.

[0133] Machine 1100 may include a processor 1104, a memory 1106, and an input / output (I / O) unit 1108 that can be configured to communicate with each other via a bus 1110. In the example, processor 1104 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processors 1112 and 1114 that execute instruction 1102. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") capable of executing instructions simultaneously. Although Figure 11 Multiple processors 1104 are shown, but machine 1100 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0134] Memory 1106 includes main memory 1116, static memory 1118, and memory cell 1120, all of which are accessible by processor 1104 via bus 1110. Main memory 1106, static memory 1118, and memory cell 1120 store instructions 1102 embodying any one or more of the methods or functions described herein. Instructions 1102 may also reside wholly or partially within main memory 1116, static memory 1118, machine-readable medium 1122 within memory cell 1120, at least one processor of processor 1104 (e.g., within the processor's cache memory), or any suitable combination thereof during execution by machine 1100.

[0135] I / O component 1108 may include various components for receiving input, providing output, generating output, transmitting information, exchanging information, capturing measurement results, etc. The specific I / O component 1108 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine may not include such a touch input device. It should be understood that I / O component 1108 may include... Figure 11Many other components are not shown. In various examples, I / O component 1108 may include user output component 1024 and user input component 1126. User output component 1024 may include visual components (e.g., displays such as plasma display panels (PDP), light-emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tubes (CRTs)), acoustic components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. User input component 1126 may include alphanumeric input components (e.g., keyboards, touchscreens configured to receive alphanumeric input, photoelectric keyboards, or other alphanumeric input components), pointing-based input components (e.g., mice, touchpads, trackballs, joysticks, motion sensors, or other pointing instruments), haptic input components (e.g., physical buttons, touchscreens that provide position and force for touch or touch gestures, or other haptic input components), audio input components (e.g., microphones), etc.

[0136] In other examples, I / O component 1108 may include biometric component 1128, motion component 1130, environmental component 1132, or position component 1134, as well as a wide range of other components. For example, biometric component 1128 includes components for detecting expressions (e.g., hand expressions, facial expressions, vocal expressions, body posture, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), and recognizing people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition). Biometric component may include a brain-computer interface (BMI) system that allows communication between the brain and external devices or machines. This can be achieved by recording brain activity data, converting that data into a format that can be understood by a computer, and then using the resulting signals to control devices or machines.

[0137] Examples of BMI technology types include:

[0138] • Brain-based brain-computer interfaces (BMIs) use electrodes placed on the scalp to record electrical activity in the brain.

[0139] • Invasive BMI, which uses electrodes surgically implanted in the brain.

[0140] • Optogenetics BMI uses light to control the activity of specific nerve cells in the brain.

[0141] Any biometric data collected by the biometric component is captured and stored only with user approval and is deleted upon user request. Furthermore, such biometric data may be used for very limited purposes (e.g., authentication). To ensure restricted and authorized use of biometric information and other personally identifiable information (PII), access to this data is limited to authorized personnel (if applicable). Any use of biometric data may be strictly limited to authentication purposes, and the data may not be shared or sold to any third party without the user's explicit consent. In addition, appropriate technical and organizational measures are implemented to ensure the security and confidentiality of this sensitive information.

[0142] The moving part 1130 includes an acceleration sensor part (e.g., an accelerometer), a gravity sensor part, and a rotation sensor part (e.g., a gyroscope).

[0143] The environmental component 1132 includes, for example, one or more camera devices (with still image / photograph and video capabilities), lighting sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers for detecting ambient temperature), humidity sensor components, pressure sensor components (e.g., barometers), acoustic sensor components (e.g., one or more microphones for detecting background noise), proximity sensor components (e.g., infrared sensors for detecting nearby objects), gas sensors (e.g., gas detection sensors for detecting the concentration of hazardous gases for safety purposes or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0144] Regarding the camera device, user system 102 may have a camera device system including, for example, a front-facing camera on the front surface of user system 102 and a rear-facing camera on the rear surface of user system 102. The front-facing camera may be used, for example, to capture still images and videos (e.g., “selfies”) of the user of user system 102, which can then be enhanced with the enhancement data (e.g., filters) described above. The rear-facing camera may be used, for example, to capture still images and videos in a more conventional camera device mode, wherein these images are similarly enhanced with the enhancement data. In addition to the front-facing and rear-facing cameras, user system 102 may also include a 360° camera for capturing 360° photos and videos.

[0145] Furthermore, the camera system of user system 102 may include dual rear cameras (e.g., a main camera and a depth-sensing camera), or even triple, quadruple, or quintuple rear camera configurations on the front and rear sides of user system 102. For example, these multi-camera systems may include wide-angle cameras, ultra-wide-angle cameras, telephoto cameras, macro cameras, and depth sensors.

[0146] The position component 1134 includes a positioning sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure and can determine altitude based on air pressure), an orientation sensor component (e.g., a magnetometer), etc.

[0147] Various technologies can be used to achieve communication. I / O component 1108 also includes a communication component 1136 operable to couple machine 1100 to network 1138 or device 1140 via a suitable coupling or connection. For example, communication component 1136 may include a network interface component or other suitable device that interfaces with network 1138. In other examples, communication component 1136 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, or Bluetooth. ® Components (e.g., Bluetooth) ® Low energy consumption), Wi-Fi ® Components and other communication components for providing communication via other means. Device 1140 can be any peripheral device from other machines or various peripheral devices (e.g., a peripheral device coupled via USB).

[0148] Furthermore, communication component 1136 can detect identifiers, or includes components operable to detect identifiers. For example, communication component 1136 may include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, QR codes such as Quick Response (QR) codes, Aztec codes, data matrices, and data symbols). TM The device can be equipped with optical sensors for multidimensional barcodes and other optical codes, such as MaxiCode, PDF417, UltraCode, and UCC RSS-2D barcodes, or acoustic detection components (e.g., microphones for identifying audio signals of the tags). Additionally, various information can be obtained via communication component 1136, such as location obtained via Internet Protocol (IP) geolocation, location obtained via Wi-Fi® signal triangulation, or location obtained by detecting NFC beacon signals that indicate a specific location.

[0149] Various memories (e.g., main memory 1116, static memory 1118, and the memory of processor 1104) and storage unit 1120 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. These instructions (e.g., instruction 1102) cause various operations to implement the disclosed examples when executed by processor 1104.

[0150] Instructions 1102 can be sent or received over network 1138 via a network interface device (e.g., a network interface component included in communication component 1136) using a transmission medium and employing any of the known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, instructions 1102 can be sent or received via a transmission medium through coupling with device 1140 (e.g., peer-to-peer coupling).

[0151] Software Architecture

[0152] Figure 12 This is a block diagram 1200 illustrating a software architecture 1202 that can be installed on any one or more of the devices described herein. The software architecture 1202 is supported by hardware such as a machine 1204 including a processor 1206, memory 1208, and I / O components 1210. In this example, the software architecture 1202 can be conceptualized as a stack of layers, where each layer provides a specific function. The software architecture 1202 includes layers such as an operating system 1212, libraries 1214, frameworks 1216, and applications 1218. Operationally, application 1218 activates API calls 1220 via the software stack and receives messages 1222 in response to API calls 1220.

[0153] Operating system 1212 manages hardware resources and provides public services. Operating system 1212 includes, for example, a kernel 1224, services 1226, and drivers 1228. Kernel 1224 acts as an abstraction layer between the hardware layer and other software layers. For example, kernel 1224 provides memory management, processor management (e.g., scheduling), component management, networking and security settings, and other functions. Services 1226 can provide other public services to other software layers. Drivers 1228 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 1228 may include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® low-power drivers, flash memory drivers, serial communication drivers (e.g., USB drivers), Wi-Fi® drivers, audio drivers, power management drivers, etc.

[0154] Library 1214 provides common low-level infrastructure used by application 1218. Library 1214 may include system library 1230 (e.g., the C standard library), which provides functions such as memory allocation, string manipulation, and mathematical functions. Additionally, library 1214 may include API library 1232, such as media libraries (e.g., libraries for supporting the rendering and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Picture Experts Group (JPEG or JPG), or Portable Web Graphics (PNG)), graphics libraries (e.g., the OpenGL framework for rendering graphic content on a display in two-dimensional (2D) and three-dimensional (3D) formats), database libraries (e.g., SQLite, which provides various relational database functions), web libraries (e.g., WebKit, which provides web browsing functionality), and so on. Library 1214 may also include various other libraries 1234 to provide many other APIs to application 1218.

[0155] Framework 1216 provides common high-level infrastructure for use by application 1218. For example, framework 1216 provides various graphical user interface (GUI) functions, advanced resource management, and advanced location services. Framework 1216 can provide a wide range of other APIs that can be used by application 1218, some of which may be specific to a particular operating system or platform.

[0156] In the example, application 1218 may include home application 1236, contact application 1238, browser application 1240, book reader application 1242, location application 1244, media application 1246, messaging application 1248, game application 1250, and a wide variety of other applications such as third-party application 1252. Application 1218 is a program that performs the functions defined in the program. One or more applications of application 1218 can be created using various programming languages, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or assembly language). In a particular example, third-party application 1252 (e.g., an application developed by an entity other than a platform vendor using the Android™ or iOS™ Software Development Kit (SDK)) may be mobile software that runs on a mobile operating system such as iOS™, Android™, Windows® phones, or other mobile operating systems. In this example, a third-party application 1252 can activate API call 1220 provided by the operating system 1212 to facilitate the functionality described herein.

[0157] Example

[0158] Example 1 is a method comprising: accessing a chat session between at least two users on a messaging platform; receiving input from a selected user of the at least two users from within a user interface associated with the chat session, the input corresponding to a federated content feed comprising shared content associated with the at least two users associated with the chat session and personalized content associated only with the selected user; in response to receiving the input, replacing the user interface associated with the chat session with a user interface associated with the federated content feed; and causing the user interface associated with the federated content feed to be displayed on a computer device associated with the selected user.

[0159] In Example 2, the subject of Example 1 includes an input where the input is a selection of optional user interface elements.

[0160] In Example 3, the subject of any of Examples 1 to 2 includes touchscreen gestures on a user's computer device where the input is a selection.

[0161] In Example 4, the subject of any one of Examples 1 to 3 includes determining that a selected user is viewing public media content in a federated content feed from within a user interface associated with the federated content feed; receiving a notification from a second user among at least two users associated with a chat session; generating a silent notification in response to the determination and the received notification that does not interrupt the selected user's viewing of the public media content; and causing the silent notification to be displayed in a separate section of the user interface associated with the federated content feed.

[0162] In Example 5, the subject of any of Examples 1 through 4 includes that notifications are associated with new messages received within a chat session.

[0163] In Example 6, the subject of any one of Examples 1 to 5 includes receiving a selection of public media content in a federated content feed from a selected user; in response to receiving the selection, causing a transparent overlay window to be displayed, the transparent overlay window allowing the selected user to continue viewing the public media content; receiving input from the selected user from the transparent overlay window; receiving a second selection of an icon within a user interface associated with the federated content feed; and in response to receiving the second selection, automatically sharing the input from the transparent overlay window and the selected public media content to a chat session while maintaining the display of the user interface of the federated content feed on the computer device associated with the selected user.

[0164] In Example 7, the subject of any of Examples 1 through 6 includes generating shared content further including: accessing previously shared public media content within a chat session; and generating shared content based on previously shared public media content.

[0165] In Example 8, the subject of any of Examples 1 to 7 includes receiving instructions from a selected user for recommended public media content from personalized content; and in response to receiving such instructions, adding recommended public media content for display as part of shared content.

[0166] In Example 9, the subject of any of Examples 1 through 8 includes, in response to receiving the instruction, displaying recommended public media content in a high ranking within the shared content.

[0167] Example 10 is a computing system including means for implementing any one of Examples 1 through 9.

[0168] In Example 11, the subject of Example 10 includes a system that is a head-mounted wearable device or a client device.

[0169] In Example 12, the subject of any of Examples 10 to 11 includes a head-worn device that is eyeglasses having a frame that carries a pair of lenses and is coupled to a camera device.

[0170] Example 13 is a non-transitory computer-readable storage medium that stores instructions that, when executed by at least one processor, cause at least one processor to perform any one of the methods in Examples 1 to 9.

[0171] Glossary

[0172] "Carrier signal" refers to any intangible medium capable of storing, encoding, or carrying instructions to be executed by a machine, and includes digital or analog communication signals or other intangible media that facilitate the communication of such instructions. Instructions can be sent or received over a network using a transmission medium via a network interface device.

[0173] "Client device" means any machine, for example, connected to a communication network to obtain resources from one or more server systems or other client devices. Client devices can be, but are not limited to, mobile phones, desktop computers, laptop computers, portable digital assistants (PDAs), smartphones, tablet computers, ultrabooks, netbooks, laptops, multiprocessor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user can use to access the network.

[0174] "Communications network" means, for example, one or more parts of a network, which can be an ad hoc network, intranet, extranet, virtual private network (VPN), local area network (LAN), wireless local area network (WLAN), wide area network (WAN), wireless wide area network (WWAN), metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a common old-style telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, other types of networks, or a combination of two or more such networks. For example, a network or a part of a network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a Global System for Mobile Communications (GSM) connection, or other types of cellular or wireless coupling. In this example, coupling can implement any data transmission technology of various types, such as single-carrier radio transmission technology (1xRTT), evolved data optimization (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate GSM evolution (EDGE) technology, the 3rd Generation Partnership Project (3GPP) including 3G, fourth-generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA), Global Microwave Access Interoperability (WiMAX), Long Term Evolution (LTE) standard, other data transmission technologies defined by various standards-setting organizations, other long-distance protocols, or other data transmission technologies.

[0175] A “component” refers to a logical or physical entity having boundaries defined by functional or subroutine calls, branch points, APIs, or other technologies that partition or modularize a particular processing or control function. A component can be combined with other components via its interface to perform machine processing. A component can be an encapsulated functional hardware unit designed for use with other components, and part of a program that typically performs a related function. A component can constitute a software component (e.g., code implemented on a machine-readable medium) or a hardware component. A “hardware component” is a tangible unit capable of performing certain operations and can be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., standalone computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., an application or application portion) to operate to perform certain operations as described herein. Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component can include dedicated circuitry or logic permanently configured to perform certain operations. Hardware components can be dedicated processors, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs). Hardware components can also include programmable logic or circuitry temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a particular machine (or a specific part of a machine), which is uniquely tailored to perform the configured function and is no longer a general-purpose processor. It will be appreciated that a decision can be made, for cost and time considerations, whether to implement a hardware component mechanically in a dedicated and permanently configured circuit or in a temporarily configured (e.g., software-configured) circuit. Therefore, the phrase “hardware component” (or “hardware-implemented component”) should be understood to include tangible entities, i.e., entities physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain way or perform certain operations described herein. Consider the example of a hardware component being temporarily configured (e.g., programmed), without needing to configure or instantiate each hardware component at any given time. For example, in cases where the hardware components include a general-purpose processor that is configured as a dedicated processor via software, this general-purpose processor can be configured as its own distinct dedicated processor (e.g., including different hardware components) at different times. The software accordingly configures one or more specific processors to constitute a particular hardware component at one moment and different hardware components at different times. Hardware components can provide information to and receive information from other hardware components. Therefore, the described hardware components can be considered communicatively coupled.In the presence of multiple hardware components, communication can be achieved through signal transmission between or among two or more hardware components (e.g., via appropriate circuitry and buses). In examples where multiple hardware components are configured or instantiated at different times, such communication between hardware components can be achieved, for example, by storing information in a memory structure accessible to the multiple hardware components and retrieving information from the memory structure. For example, a hardware component can perform an operation and store the output of that operation in a memory device communicatively coupled to it. Another hardware component can then access the memory device at a subsequent time to retrieve and process the stored output. Hardware components can also initiate communication with input or output devices and can operate on resources (e.g., collections of information). The various operations of the example methods described herein can be performed, at least in part, by one or more processors configured, either temporarily (e.g., by software) or permanently, to perform the relevant operations. Whether temporarily or permanently configured, such processors can constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the methods described herein can be implemented at least in part by processors, where one or more specific processors are examples of hardware. For example, at least some operations of the methods can be performed by one or more processors or processor-implemented components. Furthermore, one or more processors can also operate to support the execution of related operations in a “cloud computing” environment or as “Software as a Service” (SaaS) operations. For example, at least some operations can be performed by a group of computers (as an example of machines including processors), where these operations are accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs). The execution of some operations can be distributed among processors, not residing within a single machine, but deployed across multiple machines. In some examples, the processors or processor-implemented components can reside in a single geographic location (e.g., within a home environment, office environment, or server cluster). In other examples, the processors or processor-implemented components can be distributed across multiple geographic locations.

[0176] "Computer-readable storage medium" refers to both, for example, machine storage media and transmission media. Therefore, these terms include both storage devices / media and carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" refer to the same thing and can be used interchangeably in this disclosure.

[0177] A "brief message" is a message that is accessible for a limited time, such as a short period of time. Brief messages can be text, images, videos, etc. The access time for a brief message can be set by the message sender. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting method, the message is temporary.

[0178] "Machine storage medium" refers to one or more storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Therefore, this term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGAs, and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage medium," "device storage medium," and "computer storage medium" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage medium," "computer storage medium," and "device storage medium" expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are covered by the term "signal medium."

[0179] "Non-transitory computer-readable storage medium" means, for example, a tangible medium capable of storing, encoding, or carrying instructions that can be executed by a machine.

[0180] "Signal medium" means any intangible medium capable of storing, encoding, or carrying instructions that can be executed by a machine, and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be considered to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means a signal whose characteristics are set or altered in a manner that encodes information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

[0181] "User equipment" means, for example, a device that is accessed, controlled, or owned by a user, and that the user interacts with to perform actions or interactions on the user equipment, including interactions with other users or computer systems.

[0182] Glossary

[0183] "Carrier signal" refers to any intangible medium capable of storing, encoding, or carrying instructions to be executed by a machine, and includes digital or analog communication signals or other intangible media that facilitate the communication of such instructions. Instructions can be sent or received over a network using a transmission medium via a network interface device.

[0184] "Client device" means any machine, for example, connected to a communication network to obtain resources from one or more server systems or other client devices. Client devices can be, but are not limited to, mobile phones, desktop computers, laptop computers, portable digital assistants (PDAs), smartphones, tablet computers, ultrabooks, netbooks, laptops, multiprocessor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user can use to access the network.

[0185] "Communications network" means, for example, one or more parts of a network, which can be an ad hoc network, intranet, extranet, virtual private network (VPN), local area network (LAN), wireless local area network (WLAN), wide area network (WAN), wireless wide area network (WWAN), metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a common old-style telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, other types of networks, or a combination of two or more such networks. For example, a network or a part of a network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a Global System for Mobile Communications (GSM) connection, or other types of cellular or wireless coupling. In this example, coupling can implement any data transmission technology of various types, such as single-carrier radio transmission technology (1xRTT), evolved data optimization (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate GSM evolution (EDGE) technology, the 3rd Generation Partnership Project (3GPP) including 3G, fourth-generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA), Global Microwave Access Interoperability (WiMAX), Long Term Evolution (LTE) standard, other data transmission technologies defined by various standards-setting organizations, other long-distance protocols, or other data transmission technologies.

[0186] A “component” refers to a logical or physical entity having boundaries defined by functional or subroutine calls, branch points, APIs, or other technologies that partition or modularize a particular processing or control function. A component can be combined with other components via its interface to perform machine processing. A component can be an encapsulated functional hardware unit designed for use with other components, and part of a program that typically performs a related function. A component can constitute a software component (e.g., code implemented on a machine-readable medium) or a hardware component. A “hardware component” is a tangible unit capable of performing certain operations and can be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., standalone computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., an application or application portion) to operate to perform certain operations as described herein. Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component can include dedicated circuitry or logic permanently configured to perform certain operations. Hardware components can be dedicated processors, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs). Hardware components can also include programmable logic or circuitry temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a particular machine (or a specific part of a machine), which is uniquely tailored to perform the configured function and is no longer a general-purpose processor. It will be appreciated that a decision can be made, for cost and time considerations, whether to implement a hardware component mechanically in a dedicated and permanently configured circuit or in a temporarily configured (e.g., software-configured) circuit. Therefore, the phrase “hardware component” (or “hardware-implemented component”) should be understood to include tangible entities, i.e., entities physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain way or perform certain operations described herein. Consider the example of a hardware component being temporarily configured (e.g., programmed), without needing to configure or instantiate each hardware component at any given time. For example, in cases where the hardware components include a general-purpose processor that is configured as a dedicated processor via software, this general-purpose processor can be configured as its own distinct dedicated processor (e.g., including different hardware components) at different times. The software accordingly configures one or more specific processors to constitute a particular hardware component at one moment and different hardware components at different times. Hardware components can provide information to and receive information from other hardware components. Therefore, the described hardware components can be considered communicatively coupled.In the presence of multiple hardware components, communication can be achieved through signal transmission between or among two or more hardware components (e.g., via appropriate circuitry and buses). In examples where multiple hardware components are configured or instantiated at different times, such communication between hardware components can be achieved, for example, by storing information in a memory structure accessible to the multiple hardware components and retrieving information from the memory structure. For example, a hardware component can perform an operation and store the output of that operation in a memory device communicatively coupled to it. Another hardware component can then access the memory device at a subsequent time to retrieve and process the stored output. Hardware components can also initiate communication with input or output devices and can operate on resources (e.g., collections of information). The various operations of the example methods described herein can be performed, at least in part, by one or more processors configured, either temporarily (e.g., by software) or permanently, to perform the relevant operations. Whether temporarily or permanently configured, such processors can constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the methods described herein can be implemented at least in part by processors, where one or more specific processors are examples of hardware. For example, at least some operations of the methods can be performed by one or more processors or processor-implemented components. Furthermore, one or more processors can also operate to support the execution of related operations in a “cloud computing” environment or as “Software as a Service” (SaaS) operations. For example, at least some operations can be performed by a group of computers (as an example of machines including processors), where these operations are accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs). The execution of some operations can be distributed among processors, not residing within a single machine, but deployed across multiple machines. In some examples, the processors or processor-implemented components can reside in a single geographic location (e.g., within a home environment, office environment, or server cluster). In other examples, the processors or processor-implemented components can be distributed across multiple geographic locations.

[0187] "Computer-readable storage medium" refers to both, for example, machine storage media and transmission media. Therefore, these terms include both storage devices / media and carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" refer to the same thing and can be used interchangeably in this disclosure.

[0188] A "brief message" is a message that is accessible for a limited time, such as a short period of time. Brief messages can be text, images, videos, etc. The access time for a brief message can be set by the message sender. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting method, the message is temporary.

[0189] "Machine storage medium" refers to one or more storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Therefore, this term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGAs, and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage medium," "device storage medium," and "computer storage medium" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage medium," "computer storage medium," and "device storage medium" expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are covered by the term "signal medium."

[0190] "Non-transitory computer-readable storage medium" means, for example, a tangible medium capable of storing, encoding, or carrying instructions that can be executed by a machine.

[0191] "Signal medium" means any intangible medium capable of storing, encoding, or carrying instructions that can be executed by a machine, and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be considered to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means a signal whose characteristics are set or altered in a manner that encodes information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

[0192] "User equipment" means, for example, a device that is accessed, controlled, or owned by a user, and that the user interacts with to perform actions or interactions on the user equipment, including interactions with other users or computer systems.

Claims

1. A system comprising: At least one processor; At least one memory component stores instructions that, when executed by the at least one processor, cause the at least one processor to perform operations, the operations including: Access a chat session between at least two users on a messaging platform; Receive input from a selected user among the at least two users within the user interface associated with the chat session, the input corresponding to a federated content feed that includes shared content related to the at least two users associated with the chat session and personalized content related only to the selected user; In response to receiving the input, the user interface associated with the chat session is replaced with the user interface associated with the federated content; and This causes a user interface associated with the federated content to be displayed on the computer device associated with the selected user.

2. The system according to claim 1, wherein, The input is a selection of selectable user interface elements.

3. The system according to claim 1, wherein, The input is a touchscreen gesture on the selected user's computer device.

4. The system according to claim 1, further comprising: It is determined that the selected user is viewing public media content in the syndicated content feed from within a user interface associated with the syndicated content feed; Receive notification from the second user of the at least two users associated with the chat session; In response to the determination and the received notification, a silent notification is generated that does not interrupt the selected user's viewing of the public media content; as well as This causes the silent notification to be displayed in a separate section of the user interface associated with the joint content feed.

5. The system according to claim 4, wherein, The notification is associated with a new message received within the chat session.

6. The system according to claim 1, further comprising: The selected user receives a selection of public media content from the joint content feed; In response to receiving the selection, a transparent overlay window is displayed, which allows the user who made the selection to continue viewing the public media content; Receive input from the selected user from the transparent overlay window; Receive a second selection of an icon within the user interface associated with the federated content; as well as In response to receiving the second selection, the input from the transparent overlay window and the selected public media content are automatically shared to the chat session, while the user interface displaying the federated content is maintained on the computer device associated with the selected user.

7. The system according to claim 1, wherein, Generating the shared content also includes: Access to previously shared public media content within the chat session; and The shared content is generated based on the previously shared public media content.

8. The system according to claim 1, further comprising: The selected user receives instructions on recommended public media content from the personalized content. as well as In response to receiving the instruction, the recommended public media content is added for display as part of the shared content.

9. The system of claim 8, in response to receiving the instruction, displays the recommended public media content with a high ranking within the shared content.

10. A method comprising: Access a chat session between at least two users on a messaging platform; Receive input from a selected user among the at least two users within the user interface associated with the chat session, the input corresponding to a federated content feed that includes shared content related to the at least two users associated with the chat session and personalized content related only to the selected user; In response to receiving the input, the user interface associated with the chat session is replaced with the user interface associated with the federated content; and This causes a user interface associated with the federated content to be displayed on the computer device associated with the selected user.

11. The method according to claim 10, wherein, The input is a selection of selectable user interface elements.

12. The method according to claim 10, wherein, The input is a touchscreen gesture on the selected user's computer device.

13. The method of claim 10, further comprising: It is determined that the selected user is viewing public media content in the syndicated content feed from within a user interface associated with the syndicated content feed; Receive notification from the second user of the at least two users associated with the chat session; In response to the determination and the received notification, a silent notification is generated that does not interrupt the selected user's viewing of the public media content; as well as This causes the silent notification to be displayed in a separate section of the user interface associated with the joint content feed.

14. The method according to claim 13, wherein, The notification is associated with a new message received within the chat session.

15. The method of claim 10, further comprising: The selected user receives a selection of public media content from the joint content feed; In response to receiving the selection, a transparent overlay window is displayed, which allows the user who made the selection to continue viewing the public media content; Receive input from the selected user from the transparent overlay window; Receive a second selection of an icon within the user interface associated with the federated content; as well as In response to receiving the second selection, the input from the transparent overlay window and the selected public media content are automatically shared to the chat session, while the user interface displaying the federated content is maintained on the computer device associated with the selected user.

16. The method of claim 10, wherein, Generating the shared content also includes: Access to previously shared public media content within the chat session; and The shared content is generated based on the previously shared public media content.

17. The method of claim 10, further comprising: The selected user receives instructions on recommended public media content from the personalized content. as well as In response to receiving the instruction, the recommended public media content is added for display as part of the shared content.

18. The method of claim 17, wherein, in response to receiving the instruction, the recommended public media content is displayed with a high ranking within the shared content.

19. A non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform operations, the operations comprising: Access a chat session between at least two users on a messaging platform; Receive input from a selected user among the at least two users within the user interface associated with the chat session, the input corresponding to a federated content feed that includes shared content related to the at least two users associated with the chat session and personalized content related only to the selected user; In response to receiving the input, the user interface associated with the chat session is replaced with the user interface associated with the federated content; and This causes a user interface associated with the federated content to be displayed on the computer device associated with the selected user.

20. The non-transitory computer-readable storage medium according to claim 19, wherein, The input is a touchscreen gesture on the selected user's computer device.

Images