Displaying content feeds within messaging system
Through automatic display and interactive switching of different content feeds, the problem of users in the prior art requiring multiple inputs to view content is solved, and the user experience and efficiency of the messaging system is improved.
Patent Information
- Application Number
- CN202280067488.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2021-08-30
- Filing Date
- 2022-08-30
- Publication Date
- 2025-01-14
AI Technical Summary
In the existing messaging system, users need to touch input multiple times to view different content feeds, resulting in increased time waste and computing resource consumption, and insufficient automatic presentation of content feeds, affecting the user experience.
The messaging system reduces user input needs by automatically displaying friend content feeds, subscribed content feeds and non-subscribed content feeds, and uses interactive methods such as sliding gestures and taps to realize automatic switching and browsing of content feeds, combining the collection management system and the profile system. , realize automatic sorting and presentation of content.
Improve user experience, reduce the demand for user input, save computing resources, increase the automatic presentation appeal of content feeds, and simplify the content browsing process.
Smart Images

Figure CN119318138A_ABST
Abstract
Description
[0001] Priority claim
[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 238,636, filed on August 30, 2021, the entire contents of which are incorporated herein by reference. Technical Field
[0003] The present disclosure relates generally to messaging systems, including displaying content feeds within a messaging system. Background Art
[0004] The messaging system enables the exchange of message contents between users. For example, the messaging system allows a user to exchange message contents (e.g., text, images) with one or more other users. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] In the drawings, which are not necessarily drawn to scale, similar reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the highest digit or digits in the reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the accompanying drawings, in which:
[0006] Figure 1 is a diagrammatic representation of a networking environment in which the present disclosure may be deployed, according to some examples.
[0007] Figure 2 is a diagrammatic representation of a messaging system having both client-side and server-side functionality according to some examples.
[0008] Figure 3 is a diagrammatic representation of data structures as maintained in a database according to some examples.
[0009] Figure 4 is a graphical representation of messages according to some examples.
[0010] Figure 5 is an interaction diagram illustrating a process for displaying a content feed within a messaging system, according to some example implementations.
[0011] Figure 6 An example user interface corresponding to a content feed is shown according to some example embodiments.
[0012] Figure 7 is a flow diagram illustrating a process for displaying a content feed within a messaging system, according to some example implementations.
[0013] Figure 8is a flow diagram for an access restriction process according to some examples.
[0014] Fig. 9 is a diagrammatic representation of a machine in the form of a computer system according to some examples within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein.
[0015] Fig.10 is a block diagram illustrating a software architecture in which examples may be implemented. DETAILED DESCRIPTION
[0016] Messaging systems typically allow users to exchange content items (e.g., messages, images, and / or videos) with each other in message threads. As described herein, messaging systems may include user-selectable content feeds for presenting media content items or media content item collections.
[0017] The disclosed embodiments cause a messaging system to automatically display a second content feed after display of a first content feed has completed. For example, the messaging system causes a friend content feed (e.g., a collection of content from friends) to be displayed to a user in response to a user input for displaying a friend content feed. Upon determining that display of the friend content feed has completed, the messaging system automatically displays a subscription content feed (e.g., a collection of content from publishers to which the user subscribes). In one or more embodiments, upon determining that display of the subscription content feed has completed, the messaging system may automatically display a non-subscription content feed (e.g., a collection of content from publishers to which the user does not subscribe).
[0018] By automatically displaying different content feeds in this manner, the need for separate user input for displaying content feeds can be reduced. Without providing display of content feeds in this manner, the end user may need to perform other touch inputs (e.g., press a few buttons and / or gestures) to view different content feeds. Thus, the messaging system saves time for the user and reduces the computing resources / processing power associated with having to perform other touch inputs. In addition, the automatic surfacing of content feeds may be more attractive to users of the messaging system.
[0019] Figure 11 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each instance hosting a number of applications, including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on respective other client devices 102), a messaging server system 108, and a third-party server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with the local host application 106 using an application program interface (API).
[0020] The messaging clients 104 are able to communicate and exchange data with other messaging clients 104 and messaging server systems 108 via the network 112. The data exchanged between the messaging clients 104 and between the messaging clients 104 and messaging server systems 108 include functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).
[0021] The messaging server system 108 provides server-side functionality to certain messaging clients 104 via the network 112. Although certain functions of the messaging system 100 are described herein as being performed by the messaging client 104 or by the messaging server system 108, it may be a design choice whether certain functions are located within the messaging client 104 or within the messaging server system 108. For example, it may be technically preferable to initially deploy certain technologies and functions within the messaging server system 108, but later migrate the technologies and functions to the messaging client 104 where the client device 102 has sufficient processing power.
[0022] The messaging server system 108 supports various services and operations provided to the messaging clients 104. Such operations include sending data to the messaging clients 104, receiving data from the messaging clients 104, and processing data generated by the messaging clients 104. As examples, the data may include message content, client device information, geolocation information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The data exchange within the messaging system 100 is stimulated and controlled by functions available via the user interface (UI) of the messaging client 104.
[0023] Turning now specifically to the messaging server system 108, an application program interface (API) server 116 is coupled to the application server 114 and provides a programming interface to the application server 114. The application server 114 is communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application server 114. Similarly, a web server 128 is coupled to the application server 114 and provides a web-based interface to the application server 114. To this end, the web server 128 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.
[0024] The application program interface (API) server 116 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the application program interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 to activate the functions of the application server 114. An application program interface (API) server 116 exposes various functions supported by the application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via the application server 114; sending media files (e.g., images or videos) from a messaging client 104 to a messaging server 118 and for possible access by another messaging client 104; setting up of a collection of media data (e.g., a story); retrieving a friend list of a user of a client device 102; retrieving such a collection; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends in a social graph; and opening application events (e.g., related to a messaging client 104).
[0025] The application server 114 hosts several server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and a social networking server 124. The messaging server 118 implements several message processing techniques and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in more detail, text and media content from multiple sources can be aggregated into collections of content (e.g., referred to as stories or galleries). These collections are then made available to the messaging client 104. Given the hardware requirements for other processor and memory intensive data processing, other processor and memory intensive data processing may also be performed on the server side by the messaging server 118.
[0026] The application server 114 also includes an image processing server 122 that is dedicated to performing various image processing operations, typically with respect to images or videos within the payload of messages sent from the messaging server 114 or received at the messaging server 118 .
[0027] The social network server 124 supports various social networking functions and services and makes them available to the message server 118. To this end, the social network server 124 maintains and accesses the entity graph 304 (e.g., Figure 3 ). Examples of functions and services supported by the social network server 124 include identifying other users in the messaging system 100 that have a relationship with a particular user or that the particular user is "following," and also identifying interests and other entities of a particular user.
[0028] Returning to the messaging client 104, the features and functions of the external resource (e.g., application 106 or applet) are available to the user via the interface of the messaging client 104. In this context, "external" refers to the fact that the application 106 or applet is outside the messaging client 104. External resources are usually provided by a third party, but can also be provided by the creator or provider of the messaging client 104. The messaging client 104 receives a user selection of an option to launch or access the features of such an external resource. The external resource can be an application 106 (e.g., a "local app") installed on the client device 102, or a small-scale version of the application (e.g., a "applet") hosted on the client device 102 or away from the client device 102 (e.g., on a third-party server 110). The small-scale version of the application includes a subset of the features and functions of the application (e.g., a full-scale, local version of the application) and is implemented using a markup language document. In one example, the small-scale version of the application (e.g., a "applet") is a web-based markup language version of the application and is embedded in the messaging client 104. In addition to using markup language documents (eg, *ml files), applets may include scripting languages (eg, .*js files or .json files) and style sheets (eg, *ss files).
[0029] In response to receiving a user selection of an option to launch or access a feature of an external resource, the messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed application 106. In some cases, the application 106 locally installed on the client device 102 can be independent of the messaging client 104 and launched separately from the messaging client 104, such as by selecting an icon corresponding to the application 106 on a home screen of the client device 102. A small-scale version of such an application can be launched or accessed via the messaging client 104, and in some examples, none of the portions of the small-scale application can be accessed outside of the messaging client 104 or limited portions of the small-scale application can be accessed outside of the messaging client 104. The small-scale application can be launched by the messaging client 104 receiving, for example, a markup language document associated with the small-scale application from a third-party server 110 and processing such a document.
[0030] In response to determining that the external resource is a locally installed application 106, the messaging client 104 instructs the client device 102 to launch the external resource by executing the locally stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the third-party server 110 (for example) to obtain a markup language document corresponding to the selected external resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.
[0031] The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of activities occurring in one or more external resources. For example, the messaging client 104 may provide a notification to a participant in a conversation (e.g., a chat session) in the messaging client 104 about the current or recent use of an external resource by one or more members of a user group. One or more users may be invited to join a valid external resource or to start an external resource that was recently used but is currently inactive (in the friend group). The external resource may provide the participants in the conversation who each use the corresponding messaging client 104 with the ability to share items, conditions, states, or locations in the external resource with one or more members of the user group entering the chat session. The shared item may be an interactive chat card that members of the chat may interact with, for example, to start a corresponding external resource, view specific information within an external resource, or bring members of the chat to a specific location or state within an external resource. Within a given external resource, a response message may be sent to a user on the messaging client 104. The external resource may selectively include different media items in the response based on the current context of the external resource.
[0032] The messaging client 104 may present a list of available external resources (e.g., applications 106 or applets) to the user to launch or access a given external resource. The list may be presented in the form of a context-sensitive menu. For example, icons representing different applications (or applets) of the application 106 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).
[0033] Figure 2 1 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 contains several subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, an external resource system 212, and a profile system 214.
[0034] The transient timer system 202 is responsible for implementing temporary or time-limited access to content by the messaging client 104 and the messaging server 118. The transient timer system 202 includes several timers that selectively enable access (e.g., for presentation and display) of messages and associated content via the messaging client 104 based on duration and display parameters associated with a message or a collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 202 are provided below.
[0035] The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) may be organized into "event galleries" or "event stories." Such collections may be made available for a specified period of time (e.g., the duration of the event to which the content relates). For example, content related to a concert may be made available as a "story" for the duration of the concert. The collection management system 204 may also be responsible for publishing an icon to the user interface of the messaging client 104 that provides notification of the existence of a particular collection.
[0036] In addition, the collection management system 204 also includes a curation interface 206, which enables collection managers to manage and curate specific content collections. For example, the curation interface 206 enables event organizers to curate collections of content related to specific events (e.g., deleting inappropriate content or redundant messages). In addition, the collection management system 204 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation can be paid to users for including user-generated content in a collection. In such a case, the collection management system 204 operates to automatically pay such users for using their content.
[0037] The enhancement system 208 provides various functions that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to generating and publishing media overlays (media overlays) for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geographic location of the client device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information such as social network information of the user of the client device 102. The media overlay can include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos) at the client device 102. For example, the media overlay can include text or images that can be superimposed on the top of a photo taken by the client device 102. In another example, the media overlay includes a location identifier (e.g., Venice Beach) overlay, the name of a live event, or a business name (e.g., Beach Cafe) overlay. In another example, the augmentation system 208 uses the geolocation of the client device 102 to identify a media overlay that includes the business name at the geolocation of the client device 102. The media overlay may include other logos associated with the business. The media overlay may be stored in the database 120 and accessed by the database server 120.
[0038] In some examples, the enhancement system 208 provides a user-based publishing platform that enables a user to select a geolocation on a map and upload content associated with the selected geolocation. The user may also specify under what circumstances a particular media overlay should be provided to other users. The enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.
[0039] In other examples, the enhancement system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with a geographic location via a bidding process. For example, the enhancement system 208 associates the highest bidding merchant's media overlay with the corresponding geographic location for a predefined amount of time.
[0040] In other examples, such as the following Figure 3 As discussed, the augmentation system 208 enables presentation of augmented reality content in association with an image or video captured by a camera of the client device 102. The augmentation system 208 may implement or otherwise access augmented reality content items (e.g., corresponding to an application lens or augmented reality experience) to provide real-time special effects and / or sounds that may be added to the image or video.
[0041] The mapping system 210 provides various geolocation functions and supports the presentation of map-based media content and messages by the messaging client 104. For example, the mapping system 210 enables the display of user icons or avatars (e.g., stored in the profile data 302) on a map to indicate the current or past locations of the user's "friends" and media content (e.g., a collection of messages including photos and videos) generated by such friends in the context of the map. For example, on the map interface of the messaging client 104, messages posted by the user to the messaging system 100 from a particular geolocation can be displayed to the "friends" of the particular user within the context of that particular location on the map. The user can also share his or her location and status information with other users of the messaging system 100 (e.g., using appropriate status avatars) via the messaging client 104, where the location and status information is similarly displayed to selected users within the context of the mapping interface of the messaging client 104.
[0042] The external resource system 212 provides an interface for the messaging client 104 to communicate with a remote server (e.g., a third-party server 110) to launch or access external resources (i.e., applications or applets). Each third-party server 110 hosts, for example, an application or a small-scale version of an application based on a markup language (e.g., HTML5) (e.g., a game application, a utility application, a payment application, or a ride-sharing application). The messaging client 104 can launch a web-based resource (e.g., an application) by accessing an HTML5 file from a third-party server 110 associated with a web-based resource. In some examples, the application hosted by the third-party server 110 is programmed in JavaScript using a software development kit (SDK) provided by the messaging server 118. The SDK includes an application programming interface (API) having functions that can be called or activated by a web-based application. In some examples, the messaging server 118 includes a JavaScript library that provides a given external resource access to certain user data of the messaging client 104. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.
[0043] To integrate the functionality of the SDK into a web-based resource, the SDK is downloaded by the third-party server 110 from the messaging server 118, or received by the third-party server 110 in other ways. Once downloaded or received, the SDK will be 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 messaging client 104 into the web-based resource.
[0044] The SDK stored on the messaging server 118 effectively provides a bridge between external resources (e.g., an application 106 or applet) and the messaging client 104. This provides users with a seamless experience of communicating with other users on the messaging client 104 while also preserving the look and feel of the messaging client 104. In order to bridge the communication between the external resources and the messaging client 104, in some examples, the SDK facilitates communication between the third-party server 110 and the messaging client 104. In some examples, the web view JavaScript bridge running on the client device 102 establishes two one-way communication channels between the external resources and the messaging client 104. Messages are sent asynchronously between the external resources and the messaging client 104 via these communication channels. Each SDK function activation is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.
[0045] By using the SDK, not all information from the messaging client 104 is shared with the third-party server 110. The SDK limits which information is shared based on the needs of the external resource. In some examples, each third-party server 110 provides an HTML5 file corresponding to a web-based external resource to the messaging server 118. The messaging server 118 can add a visual representation (e.g., box art or other graphics) of the web-based external resource in the messaging client 104. Once the user selects the visual representation or instructs the messaging client 104 to access a feature of a web-based external resource through the GUI of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources required to access the features of the web-based external resource.
[0046] The messaging client 104 presents a graphical user interface (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the launched external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the launched external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents another graphical user interface of the external resource including the functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access the user data of the messaging client 104, after displaying the login page or title screen of the external resource for a threshold period of time (e.g., 3 seconds), the messaging client 104 slides a menu for authorizing the external resource to access the user data (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving the user selection of the accept option, the messaging client 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the messaging client 104. In some examples, the messaging client 104 authorizes the external resource to access the user data according to the OAuth 2 framework.
[0047] The messaging client 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, an external resource comprising a full-scale application (e.g., application 106) is provided with access to a first type of user data (e.g., only a two-dimensional avatar of a user with or without different avatar characteristics). As another example, an external resource comprising a small-scale version of an application (e.g., a web-based version of the application) is provided access to a second type of user data (e.g., payment information, a two-dimensional visualization of a user, a three-dimensional visualization of a user, and a visualization with various visualization characteristics). Avatar characteristics include different ways to customize the look and feel of an avatar representation (e.g., different poses, facial features, clothing, etc.).
[0048] The profiling system 214 implements various functions for maintaining profiles about the messaging system 100. Profile data maintained by the profiling system may be selectively used and presented to other users of the messaging system 100 based on the privacy settings specified by the particular entity.
[0049] From the perspective of an individual user, the profile system 214 enables maintenance and presentation of one or more of a self-profile (e.g., "my profile"), a friendship profile, a group profile, and a public profile. In one or more embodiments, the self-profile corresponds to the individual user's own information in the messaging system, such as a user name, phone number, address, settings (e.g., notification and privacy settings), and / or an avatar representation (or a collection of such avatar representations) selected by the user.
[0050] In one or more embodiments, a friendship profile includes information common to two users. Such information may include message content about two users (e.g., friends) exchanged within one or more message threads, such as, but not limited to, images, videos, audio files, attachments, and messages (e.g., text-based messages), with any corresponding annotation data. A group profile includes information similar to that of a friend profile and applies to a group of users (e.g., 2 or more users).
[0051] In one or more embodiments, a public profile enables maintenance and presentation of information associated with an entity. For example, an entity associated with a public profile may be a publisher, such as a merchant, an enterprise, a social media influencer, and / or an advertiser. The entity may create a public profile to present its content to other users (e.g., all users) of the messaging system 100, rather than being limited to friends (e.g., associated with a friend profile). In addition, a public profile enables other users to choose to subscribe to content provided by the entity (e.g., via a subscription button). For example, such content may be presented in a content feed provided by the messaging system 100 together with other content from other entities.
[0052] Figure 3 is a diagram illustrating a data structure 300 that may be stored in a database 126 of a messaging server system 108 according to some examples. Although the contents of the database 126 are illustrated as including several tables, it should be understood that data may be stored in other types of data structures (e.g., object-oriented databases).
[0053] Database 126 includes message data stored in message table 306. For any particular message, the message data includes at least message sender data, message recipient (or receiver) data, and payload. Figure 4 Additional details regarding information that may be included in a message and included in the message data stored in message table 306 are described.
[0054] The entity table 308 stores entity data and is linked (e.g., referenced) to the entity graph 304 and the profile data 302. The entities for which records are maintained within the entity table 308 may include individuals, corporate entities, organizations, objects, places, events, etc. Regardless of the entity type, any entity about which the messaging server system 108 stores data may be an identified entity. Each entity is provided with a unique identifier as well as an entity type identifier (not shown).
[0055] The entity graph 304 stores information about relationships and associations between entities. By way of example only, such relationships may be social, professional (e.g., working in a common company or organization), interest-based, or activity-based.
[0056] Profile data 302 (e.g., in conjunction with profile system 214) stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 302 can be selectively used and presented to other users of messaging system 100. In the case where the entity is a person, profile data 302 includes, for example, user name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a collection of such avatar representations) selected by the user. The particular user can then selectively include one or more of these avatar representations in the content of messages transmitted via messaging system 100 and in a map interface displayed to other users by messaging client 104. The collection of avatar representations can include a "status avatar" that presents a graphical representation of a state or activity that a user can select to communicate at a particular time.
[0057] Where the entity is a group, the profile data 302 for the group may similarly include one or more visual representations associated with the group, in addition to the group name, members, and various settings related to the group (eg, notifications).
[0058] Database 126 also stores enhancement data, such as overlays or filters, in enhancement table 310. Enhancement data is associated with and applied to videos (whose data is stored in video table 314) and images (whose data is stored in image table 316).
[0059] In one example, a filter is an overlay displayed as an overlay on an image or video during presentation to a recipient user. The filter can be of various types, including filters selected by a user from a set of filters presented to a sending user by the messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geofilters), which can be presented to a sending user based on geolocation. For example, a geolocation filter specific to a nearby or special location can be presented by the messaging client 104 within a user interface based on geolocation information determined by a global positioning system (GPS) unit of the client device 102.
[0060] Another type of filter is a data filter, which can be selectively presented to the sending user by the messaging client 104 based on other input or information collected by the client device 102 during the message creation process. Examples of data filters include the current temperature at a particular location, the current speed at which the sending user is traveling, the battery life of the client device 102, or the current time.
[0061] Other augmented data that may be stored in the image table 316 include augmented reality content items (eg, corresponding to an application lens or augmented reality experience). The augmented reality content items may provide real-time special effects and / or sounds that may be added to an image or video.
[0062] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, and similar terms referring to modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify images when they are captured using a device sensor (e.g., one or more cameras) of the client device 102 and then display the modified images on the screen of the client device 102. This also includes modifications to stored content such as video clips that can be modified in a gallery. For example, in a client device 102 that can access multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to watch how different augmented reality content items will modify the stored clips. For example, by selecting different augmented reality content items for content, multiple augmented reality content items that apply different pseudo-random movement models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently captured by the sensor of the client device 102 will modify the captured data. Such data may simply be displayed on the screen without being stored in memory, or content captured by the device sensors may be recorded and stored in memory with or without modification (or both). In some systems, a preview function may display different augmented reality content items as they would appear in different windows of a display simultaneously. This may, for example, enable viewing of multiple windows with different pseudo-random animations on a display simultaneously.
[0063] Thus, data and various systems using augmented reality content items or other such transformation systems that modify content using such data may involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames; tracking of such objects as they leave, enter, and move around the field of view; and modification or transformation of such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve: generating a three-dimensional mesh model of one or more objects; and using transformations of the model and animated textures within a video to implement the transformations. In other examples, tracking of points on an object may be used to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In further examples, neural network analysis of a video frame may be used to place an image, model, or texture in content (e.g., an image or video frame). Thus, augmented reality content items refer both to images, models, and textures used to create transformations in content, and to additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.
[0064] Real-time video processing can be performed using any kind of video data (e.g., video streams, video files, etc.) stored in the memory of any kind of computerized system. For example, a user can load video files and store them in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, any object, such as a human face and parts of a human body, an animal, or a non-living thing (e.g., a chair, a car, or other objects) can be processed using computer animation models.
[0065] In some examples, in the case where a specific modification is selected together with the content to be transformed, the element to be transformed is identified by the computing device, and then if the element to be transformed is present in the video frame, the element to be transformed is detected and tracked. The elements of the object are modified according to the request for modification, thereby transforming the frame of the video stream. The transformation of the frame of the video stream can be performed by different methods for different types of transformations. For example, for the transformation of the frame that mainly involves changing the form of the elements of the object, the feature points of each element of the object are calculated (for example, using an active shape model (ASM) or other known methods). Then, for each element of at least one element of the object, a grid based on the feature points is generated. The grid is used for the subsequent stage of tracking the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the position of each element. Then, additional points are generated on the grid. A first set of first points is generated for each element based on the request for modification, and a set of second points is generated for each element based on the set of first points and the request for modification. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the set of first points and the set of second points and the grid. In such a method, the background of the modified object may also be changed or deformed by tracking and modifying the background of the modified object.
[0066] In some examples, the transformation of some areas of the object using the elements of the object can be performed by calculating the feature points of each element of the object and generating a grid based on the calculated feature points. Points are generated on the grid, and then various areas are generated based on the points. Then, the elements of the object are tracked by aligning the area of each element with the position of each element in at least one element, and the properties of the area can be modified based on the modification request, thereby transforming the frame of the video stream. Depending on the specific modification request, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects in the area based on the modification request; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some feature points may be selected as control points for determining the entire state space of options for model animation.
[0067] In some examples of computer animation models that use face detection to transform image data, faces are detected on an image using a specific face detection algorithm (e.g., Viola-Jones). An active shape model (ASM) algorithm is then applied to the face region of the image to detect facial feature reference points.
[0068] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points that exist in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not recognizable (for example, if the person wears an eye patch), secondary landmarks can be used. Such landmark identification procedures can be used for any such objects. In some examples, a set of landmarks forms a shape. The coordinates of the points in the shape can be used to represent the shape as a vector. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points. The mean shape (meanshape) is the average value of the aligned training shapes.
[0069] In some examples, the landmark search begins with a mean shape aligned with the position and size of the face determined by a global face detector. Such a search then repeats the steps of proposing tentative shapes by adjusting the positions of shape points via template matching of the image texture around each point, and then conforming the tentative shapes to a global shape model until convergence occurs. In some systems, individual template matches are unreliable, and the shape model pools the results of weak template matches to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid from coarse to fine resolution.
[0070] The transformation system can capture an image or video stream on a client device (e.g., client device 102) and perform complex image manipulations locally on the client device 102 while maintaining an appropriate user experience, computational time, and power consumption. Complex image manipulations can include size and shape changes, mood transformations (e.g., changing a face from a frown to a smile), state transformations (e.g., aging a subject, reducing apparent age, changing gender), style transformations, application of graphical elements, and any other suitable image or video manipulations that can be implemented by a convolutional neural network that has been configured to execute efficiently on the client device 102.
[0071] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network that operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the data image, or the computer animation model can be presented as associated with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the image of the user to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream, and once a modification icon has been selected, the modified result can be presented in real time or near real time. In addition, when the video stream is being captured, the modification can be persistent and the selected modification icon remains toggled. Machine learning neural networks can be used to implement such modifications.
[0072] The graphical user interface presenting the modifications performed by the transformation system can supply additional interactive options for the user. Such options can be based on the interface for initiating content capture and selecting a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, after the modification icon is initially selected, the modification can be persistent. The user can switch to turn the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing other areas of the imaging application. In the case of multiple faces modified by the transformation system, the user can globally turn on or off the modification by tapping or selecting a single face modified and displayed in the graphical user interface. In some examples, each face in a plurality of face groups can be modified individually, or such modifications can be switched individually by tapping or selecting a single face or a series of faces displayed in the graphical user interface.
[0073] The story table 312 stores data about a collection of messages and associated image, video or audio data that are compiled into a collection (e.g., a story or gallery). The creation of a particular collection can be initiated by a particular user (e.g., each user whose record is maintained in the entity table 306). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by the user. To this end, the user interface of the messaging client 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.
[0074] A collection may also constitute a "live story" that is a collection of content from multiple users, created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" may constitute a curated stream of content submitted by users from different locations and events. Users whose client devices have location services enabled and who are at a co-located event at a particular time may be presented with an option, for example, via a user interface of the messaging client 104, to contribute content to a particular live story. Live stories may be identified to a user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.
[0075] Another type of content collection is called a "location story," which enables users whose client devices 102 are located within a particular geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some implementations, contributions to location stories may require secondary authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student on a university campus).
[0076] As mentioned above, the video table 314 stores video data, which in one example is associated with a message whose record is saved within the message table 306. Similarly, the image table 316 stores image data associated with a message whose message data is stored in the entity table 308. The entity table 308 can associate various enhancements from the enhancement table 310 with the various images and videos stored in the image table 316 and the video table 314.
[0077] Figure 4 is a schematic diagram illustrating the structure of a message 400 generated by a messaging client 104 for transmission to another messaging client 104 or a messaging server 118 according to some examples. The content of a particular message 400 is used to populate a message table 306 stored in a database 126 accessible by a messaging server 118. Similarly, the content of the message 400 is stored in memory as "in-flight" or "in-flight" data of a client device 102 or application server 114. The message 400 is shown as including the following example components:
[0078] Message identifier 402 : a unique identifier that identifies the message 400 .
[0079] Message text payload 404 : Text to be generated by a user via the user interface of the client device 102 and included in the message 400 .
[0080] Message image payload 406 : Image data captured by a camera component of the client device 102 or retrieved from a memory component of the client device 102 and included in the message 400 . Image data for a sent or received message 400 may be stored in the image table 316 .
[0081] Message video payload 408 : Video data captured by the camera component or retrieved from the memory component of the client device 102 and included in the message 400 . The video data for a message 400 sent or received may be stored in the video table 314 .
[0082] Message audio payload 410 : audio data captured by a microphone or retrieved from a memory component of the client device 102 and included in the message 400 .
[0083] Message enhancement data 412 : Enhancement data (eg, filters, stickers, 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 the message 400 . The enhancement data for a sent or received message 400 may be stored in the enhancement table 310 .
[0084] ·Message duration parameter 414: In response to receiving a second user input, switching from the explorer user interface to the capture user interface based on the selected augmented reality content item, and updating the first set of augmented reality content items to include the selected augmented reality content item, so that the carousel interface continuously presents the selected augmented reality content item as part of the first set of augmented reality content items. A parameter value indicating the amount of time in seconds that the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) will be presented to the user via the messaging client 104 or made accessible to the user.
[0085] Message geolocation parameters 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. 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 a message image payload 406 or a specific video in a message video payload 408).
[0086] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., a "story" identified in story table 312) associated with a particular content item in message image payload 406 of message 400. For example, multiple images within message image payload 406 may each be associated with multiple content collections using an identifier value.
[0087] Message tags 420: Each message 400 may be tagged with a plurality of tags, each of which indicates the subject of the content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value may be included within the message tags 420 indicating the relevant animal. The tag values may be manually generated based on user input, or may be automatically generated using, for example, image recognition.
[0088] • Message sender identifier 422: An identifier (eg, a messaging system identifier, an email address, or a device identifier) that indicates the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.
[0089] • Message recipient identifier 424: Indicates an identifier (eg, a messaging system identifier, an email address, or a device identifier) of the user of the client device 102 to which the message 400 is addressed.
[0090] The content (e.g., value) of the various components of message 400 may be pointers to locations in a table where content data values are stored. For example, the image value in message image payload 406 may be a pointer (or address) to a location within image table 316. Similarly, the value within message video payload 408 may point to data stored within video table 314, the value stored within message enhancement data 412 may point to data stored in enhancement table 310, the value stored within message story identifier 418 may point to data stored in story table 312, and the values stored within message sender identifier 422 and message recipient identifier 424 may point to user records stored within entity table 308.
[0091] Figure 5 is an interaction diagram illustrating a process 500 for displaying a content feed within a messaging system according to some example implementations. Figure 1 The messaging client 104 and Figure 2The process 500 is described with reference to the collection management system 204 of the embodiment of the present invention. However, one or more frames (or operations) of the process 500 can be performed by one or more other components and / or other suitable devices. Further for the purpose of illustration, the frames (or operations) of the process 500 are described herein as occurring in series or linearly. However, multiple frames (or operations) of the process 500 can occur in parallel or simultaneously. In addition, the frames (or operations) of the process 500 do not need to be performed in the order shown, and / or one or more frames (or operations) of the process 500 do not need to be performed and / or can be replaced by other operations. When its operation is completed, the process 500 can terminate. In addition, the process 500 can correspond to a method, a program, an algorithm, etc.
[0092] The messaging client 104 may be associated with a corresponding user of the messaging server system 108, and the user may be associated with a user account of the messaging server system 108. As described above, a user may be identified by the messaging server system 108 based on a unique identifier (e.g., a messaging system identifier, an email address, and / or a device identifier) associated with the user account of the user. In addition, the messaging server system 108 may implement and / or work in conjunction with a social network server 124 that is configured to identify other users (e.g., friends) with whom a particular user has relationships.
[0093] As described herein, the messaging client 104 (e.g., in conjunction with the messaging server system 108) causes a friend content feed to be displayed to a user in response to a user input for displaying the friend content feed. After determining that display of the friend content feed has been completed, the messaging client 104 (e.g., in conjunction with the collection management system 204) automatically displays a subscription content feed to the user. In one or more implementations, after determining that display of the subscription content feed has been completed, the messaging client 104 (e.g., in conjunction with the collection management system 204) automatically displays a non-subscription content feed to the user.
[0094] As described above, the collection management system 204 may correspond to a subsystem of the messaging system 100 and may be supported on the client side by the messaging client 104 and / or on the server side by the application server 114. Thus, the operations described herein with respect to the collection management system 204 may be implemented on the client side, the server side, and / or a combination of the client side and the server side.
[0095] At block 502, the messaging client 104 receives user input requesting to view a friend content feed. For example, the messaging client 104, in conjunction with the messaging server system 108, enables the user to switch between different interfaces (e.g., switch between a first tab and a second tab via a corresponding sliding gesture) to present the content feed.
[0096] The first tab may correspond to viewing a collection of content (e.g., a story), each of which includes one or more media content items. A content feed may correspond to a set of content collections for a particular type of entity. In one or more embodiments, a first content feed is associated with a user's friends, a second content feed is associated with content provided by a publisher to which the end user subscribes, and a third content feed is associated with content provided by a publisher to which the end user does not subscribe. As described above, the profile system 214 may implement various functions for maintaining profiles of friends and publishers (e.g., which may be subscription-based or non-subscription-based for the end user).
[0097] Each of the content feeds may be presented within a separate section in the first tab. For example, a first content feed includes a collection of content categorized under a "Friends" section (e.g., Title), a second content feed includes a collection of content categorized under a "Subscription" section, and a third content feed includes a collection of content categorized under a non-subscription (e.g., "For You") section.
[0098] In this regard, the messaging client 104 presents each content collection (e.g., story) as a separate icon (e.g., tile) within the first tab. For example, each of the "Friends" section, the "Subscriptions" section, and the "For You" section may include a set of corresponding tiles, each of which may be selected by the terminal user. Each tile may include one or more of the following: a thumbnail having a representative image corresponding to the content collection (e.g., for a particular friend or publisher); a title for the content collection; and / or an entity associated with the content collection (e.g., the identity of a friend or publisher). User selection of a tile causes the messaging client 104 to display the content collection corresponding to the selected tile.
[0099] In one or more embodiments, the tiles of a particular content feed are displayed in a ranked order. The ordering of the tiles (e.g., content collections) can be based on metadata stored in association with each content collection by the collection management system 204. Such metadata can indicate whether a given content collection has been viewed by an end user, when the content collection was generated (e.g., based on a timestamp), the popularity of the content collection, etc.
[0100] The second tab may correspond to viewing individual media content items submitted by different entities (e.g., creators, publishers, etc.). In one or more embodiments, the messaging system 100 may automatically select media content items to include in the second interface based on overall user popularity. The user popularity of a media content item may be based on one or more of system-wide views, user-submitted reviews, user-submitted endorsements, etc.
[0101] Thus, the messaging system 100 enables different entities to provide content feeds that can be selected for viewing by the end user. Content feeds (e.g., grouped content collections) associated with the user's friends, publishers to which the end user subscribes, and publishers to which the end user does not subscribe can be accessible within the various sections of the first tab discussed above. A separate content feed is included in the second tab, and the content feed can include popular media content items associated with a publisher, creator, etc. In addition, as described above, the profile system 214 enables access to friend profiles and / or public profiles in conjunction with the profile data 302.
[0102] exist Figure 5 In the example of , at block 502, the messaging client 104 receives user input within a first tab to view a friend content feed. For example, the end user may select a tile corresponding to one of the content collections that appear within the "Friends" section.
[0103] At operation 504, the messaging client 104 sends a request for a friend content feed to the collection management system 204. As described above, the collection management system 204 is configured to manage media content items, content collections, and / or grouped content collections. In one or more embodiments, such media content items, content collections, and / or grouped content collections may be accessed via corresponding identifiers. Thus, the request at operation 504 may include an identifier of a content collection (e.g., a story) associated with the selected tile.
[0104] In response to the request, the collection management system 204 accesses the friend content feed and provides it to the messaging client 104 (operation 506). As described above, the friend content feed can include a set of content collections (e.g., stories) in a first tab. Therefore, at operation 506, the collection management system 204 can provide the content collections (e.g., via corresponding identifiers) to the messaging client 104 in a specific order starting with the content collection corresponding to the tile selected by the user at box 502. The order of the remaining content collections after the first content collection (e.g., corresponding to the selected tile) can be based on the ranking order of the above-mentioned tiles (e.g., viewing status, when the content collection was generated, popularity of the content collection, etc.). For example, the collection management system 204 can provide each content collection to the messaging client 104 based on the ranking order, for example, which is intended to present each content collection within the friend content feed to the user.
[0105] At block 508, the messaging client 104 displays the friend content feed provided by the collection management system 204. For example, the messaging client 104 displays each content collection as it is received from the collection management system 204.
[0106] At operation 510, it is determined that display of the friend content feed is complete. Such a determination may be made by the collection management system 204, by the messaging client 104, or by a combination of the collection management system 204 and the messaging client 104. In one or more embodiments, such a determination is based on detecting that each content collection in the friend content feed has been viewed in its entirety by the user. For example, the messaging client 104 detects that each content collection received from the collection management system 204 has been viewed by the user without user input for skipping any content collection. Alternatively, the messaging client 104 may detect that the user did skip one or more of the content collections.
[0107] With respect to skipping content collections, the messaging client 104 enables navigation of content collections via corresponding predefined gestures. For example, in response to an upward swipe gesture, the messaging client 104 in conjunction with the collection management system 204 enables access and display of the next content collection within the friend content feed.
[0108] In response to the swipe down gesture, the messaging client 104 is configured to re-present a previous content collection within the friend content feed. In the event that the messaging client 104 displays a first content collection of the friend content feed (e.g., a first tile in a first tab), the messaging client 104 is configured to cancel display of the content feed (e.g., and revert to the first tab) in response to the swipe down gesture. In addition, in the event that a particular content collection has not been loaded (e.g., from the collection management system 204) in response to the swipe up or swipe down gesture, the messaging client 104 may display a loading screen. For example, the loading screen may be a black screen with an indication that the content is loading.
[0109] In addition, the messaging client 104 enables traversal of individual media content items of a content set in response to a predefined gesture. In response to a tap right gesture (e.g., a tap on the right two-thirds of the screen or more), the messaging client 104 enables advancement to the next media content item. The next media content item may be the next media content item in the current content set, or if the last media content item is reached in the current content set, the next media content item is the first media content item in the next content set.
[0110] In addition, in response to a left tap gesture (e.g., a tap on the left two-thirds or more of the screen), the messaging client 104 causes the previous media content item to be re-presented. The previous media content item can be a media content item in the current content set, or if the first media content item is reached within the current content set, the previous media content item is the last media content item in the previous content set. In the case where the messaging client 104 displays the first content set of the friend content feed (e.g., the first tile in the first tab), the messaging client 104 is configured to cancel the display of the friend content feed (e.g., and restore to the first tab) in response to the left tap gesture.
[0111] As described above with respect to operation 510, determining that display of the friend content feed is complete can be based on detecting a user input for skipping display of the entirety of at least one content collection in the friend content feed. Such input can correspond to a swipe up gesture to skip a content collection. Alternatively or additionally, such input can correspond to a tap right gesture performed with respect to a media content item within a content collection included in the friend content feed.
[0112] Thus, at operation 510, determining that display of the friend content feed is complete may be based on the user viewing all content collections within the friend content feed, or may be based on the user skipping (e.g., via a swipe up gesture and / or a tap right gesture) one or more content collections. In one or more implementations, content collections may be viewed and / or skipped based on the order of content collections provided by the collection management system 204. Alternatively or additionally, content collections may be viewed and / or skipped based on the user having individually selected tiles for playback within the first tab.
[0113] In response to the determination at operation 510, the collection management system 204 is configured to provide a subscription content feed to the messaging client 104 (operation 512). As described above, the subscription content feed is separate from the friend content feed and can be presented within the "Subscriptions" section. The subscription content feed includes a collection of content provided by publishers to which the user has subscribed with respect to the messaging system 100.
[0114] As described above, the subscription content feed may include a set of content collections (e.g., tiles) in the first tab. Therefore, at operation 512, the collection management system 204 may provide the content collections (e.g., via corresponding identifiers) to the messaging client 104 in the above-mentioned ranking order of the tiles. As described above, the ranking may be based on the browsed state, when the content collection was generated, the popularity of the content collection, etc. The collection management system 204 may provide each content collection to the messaging client 104 based on the above-mentioned order, which is intended to present each content collection within the subscription content feed to the user.
[0115] At block 514, the messaging client 104 displays the subscribed content feed provided by the collection management system 204. The messaging client 104 may display each content collection as it is received from the collection management system 204.
[0116] At operation 516, it is determined that the display of the subscription content feed is complete. Such a determination can be made by the collection management system 204, by the messaging client 104, or by a combination of the collection management system 204 and the messaging client 104. In one or more embodiments, such a determination is based on detecting that each content set in the subscription content feed has been viewed in its entirety by the user. For example, the messaging client 104 detects that each content set received from the collection management system 204 has been viewed by the user without a user input for skipping any content set. Alternatively, the messaging client 104 detects a user input (e.g., an upward sliding gesture for skipping a set and / or a tapping right gesture for skipping a media content item) for skipping the display of the entirety of at least one content set in the subscription content feed. Content sets may have been viewed and / or skipped based on the order of content sets provided by the collection management system 204. Alternatively or additionally, content sets may be viewed and / or skipped based on the user selecting tiles individually within the first tab.
[0117] Based on the design and / or administrator settings, the messaging client 104 in conjunction with the collection management system 204 may behave differently in response to operation 516. Figure 5 In the example embodiment (not shown in FIG), the messaging client 104 is configured to cancel display of the subscribed content feed (eg, and revert to the first tab) in response to determining that display of the subscribed content feed has completed.
[0118] In another example (shown in dashed lines with respect to operation 518 and block 520), the messaging client 104 displays a collection of content from a non-subscription content feed. As described above, the non-subscription content feed is separate from the subscription content feed and can be presented within a "For You" section. The non-subscription content feed includes a collection of content provided by publishers to which the user is not subscribed with respect to the messaging system 100.
[0119] The non-subscription content feed may include a set of content collections (e.g., tiles) in the first tab. Thus, at operation 518, the collection management system 204 may provide the content collections (e.g., via corresponding identifiers) to the messaging client 104 in the above-described ranking order of the tiles. As described above, the ranking may be based on browsing status, when the content collection was generated, popularity of the content collection, etc.
[0120] At block 520, the messaging client 104 displays the non-subscription content feed provided by the collection management system 204. For example, the collection management system 204 may provide each content collection to the messaging client 104 based on the order described above, and the messaging client 104 may display each content collection as it is received from the collection management system 204. In one or more implementations, the messaging client 104 is configured to cancel display of the non-subscription content feed (e.g., and revert to the first tab) in response to determining that display of the non-subscription content feed is complete (e.g., based on viewing the content feed in its entirety or the user skipping the content collection as discussed above).
[0121] Therefore, the messaging system 100 enables the display of the friend content feed to the user in response to the user input for displaying the friend content feed. When it is determined that the display of the friend content feed has been completed, the messaging system 100 automatically displays the subscription content feed to the user. In one or more embodiments, after determining that the display of the subscription content feed has been completed, the messaging system 100 can automatically display the non-subscription content feed to the user. By automatically displaying the content feed in this way, the need for a separate user input for displaying the content feed can be reduced. In the case where the display of the content feed is not provided in this way, the terminal user may need to perform other touch inputs (e.g., press a button several times and / or a number of gestures) to view different content feeds. Therefore, the messaging system 100 saves time for the user and reduces the computing resources / processing power associated with having to perform other touch inputs. In addition, the automatic presentation of the content feed may be more attractive to the user of the messaging system 100.
[0122] Figure 6 Example user interfaces 602-604 corresponding to content feeds are shown according to some example implementations. Figure 6 In the example of FIG. 6 , user interface 602 corresponds to display of a friend content feed, and user interface 604 corresponds to display of a subscription content feed.
[0123] exist Figure 6 In the example of FIG. 6 , user interface 602 displays media content item 606 that is included in a friend content feed. Figure 5As described, the "Friends" portion of the first tab may include user-selectable tiles, each of which corresponds to a collection of content (e.g., stories) from the user's friends. The user interface 602 may include a subscription button 608 for subscribing to content from friends associated with the content feed. The user interface 602 may also include a menu button 610 for presenting menu options such as subscriptions, switching subtitles, and / or adding to a story (e.g., by capturing an image and creating a new media content item). The user interface 602 may also include a capture button 612 for adding to a story. In addition, the user interface 602 may include a reply button 614 for replying to a friend who provides a media content item 606.
[0124] As mentioned above about Figure 5 As described above, the messaging client 104 in conjunction with the collection management system 204 may determine that display of the friend content feed has completed and, in response, cause display of the subscription content feed. Figure 6 In the example of , a user performs an upward swipe gesture for a last displayed content collection (e.g., a story) in a friend content feed (e.g., as depicted by “Last Friends Stories”) to skip display of the last content collection. In response, messaging client 104 provides display of the subscription content feed starting with the first collection ranked by collection management system 204. Media content item 616 may correspond to a first media content item of the first collection.
[0125] Thus, user interface 604 includes media content items 616 that are included in the subscribed content feed. Figure 5 As described, the "Subscription" portion of the first tab may include user-selectable tiles, each of which corresponds to a collection of content (e.g., stories) from a publisher to which the user has subscribed. The user interface 604 may include a subscription button 618 for switching a subscription status performed by the user. The user interface 604 may also include a menu button 620 for displaying menu options for subscribing, reporting a media content item to an administrator, switching subtitles, or sharing a media content item (e.g., sharing with friends, as a broadcast, and / or sharing outside the platform). In addition, the user interface 604 may include a send button 622 for sharing a media content item.
[0126] Figure 7 700 is a flowchart illustrating a process 700 for displaying a content feed within a messaging system according to some example implementations. Figure 1The messaging client 104 of the embodiment of the present invention is used to describe the process 700. However, one or more frames (or operations) of the process 700 can be performed by one or more other components and / or other suitable devices. Further for the purpose of illustration, the frames (or operations) of the process 700 are described in this article as occurring in series or linearly. However, multiple frames (or operations) of the process 700 can occur in parallel or simultaneously. In addition, the frames (or operations) of the process 700 do not need to be performed in the order shown, and / or one or more frames (or operations) of the process 700 do not need to be performed and / or can be replaced by other operations. When its operation is completed, the process 700 can terminate. In addition, the process 700 can correspond to a method, a program, an algorithm, etc.
[0127] The messaging client 104 receives user input corresponding to a request for a first content feed, the first content feed including a first plurality of media content items provided by one or more friends of the user (block 702). The messaging client 104 provides display of the first content feed in response to receiving the user input (block 704).
[0128] The messaging client 104 determines that display of the first content feed is complete (block 706). Determining that display of the first content feed is complete may include detecting whether each of the plurality of content sets of the first content feed has been displayed. For example, the detection may be based on the entirety of each of the plurality of content sets of the first content feed having been displayed. In another example, the detection may be based at least in part on a second user input for skipping display of the entirety of at least one of the plurality of content sets of the first content feed.
[0129] In response to determining that display of the first content feed is complete, the messaging client 104 provides display of a second content feed (block 708). The second content feed includes a second plurality of media content items provided by one or more content providers to which the user subscribes with respect to the messaging application. Each of the first content feed and the second content feed may include a respective plurality of content collections, each of which includes at least one media content item in the respective plurality of media content items.
[0130] The messaging client 104 may determine that display of the second content feed has completed, and in response to determining that display of the second content feed has completed, may provide for display of a third content feed, the third content feed comprising a third plurality of media content items provided by one or more content providers to which the user is not subscribed with respect to the messaging application. Determining that display of the second content feed has completed may include detecting that each of a plurality of content collections of the second content feed has been displayed.
[0131] Figure 8is a schematic diagram illustrating an access restriction process 800 according to which access to content (e.g., ephemeral message 802 and associated multimedia data payload) or a collection of content (e.g., ephemeral message group 804) can be time-restricted (e.g., made ephemeral).
[0132] The ephemeral message 802 is shown to be associated with a message duration parameter 806, the value of which determines the amount of time that the messaging client 104 will display the ephemeral message 802 to the receiving user of the ephemeral message 802. In one example, depending on the amount of time specified by the sending user using the message duration parameter 806, the receiving user can view the ephemeral message 802 for up to 10 seconds.
[0133] The message duration parameter 806 and the message recipient identifier 424 are shown as inputs to a message timer 810, which is responsible for determining the amount of time that the transient message 802 is shown to a particular receiving user identified by the message recipient identifier 424. In particular, the transient message 802 is shown to the associated receiving user only for a period of time determined by the value of the message duration parameter 806. The message timer 810 is shown as providing an output to a more general transient timer system 202, which is responsible for the overall timing of displaying content (e.g., the transient message 802) to the receiving user.
[0134] Short message 802 Figure 8 804 (e.g., a collection of messages in a personal story or an event story). The ephemeral message group 804 has an associated group duration parameter 808, the value of which determines the duration for which the ephemeral message group 804 is presented and accessible to users of the messaging system 100. For example, the group duration parameter 808 may be the duration of a concert, where the ephemeral message group 804 is a collection of content about the concert. Alternatively, a user (an owning user or a curator user) may specify a value for the group duration parameter 808 when performing setup and creation of the ephemeral message group 804.
[0135] In addition, each ephemeral message 802 within the ephemeral message group 804 has an associated group participation parameter 812, the value of which determines the duration for which the ephemeral message 802 is accessible within the context of the ephemeral message group 804. Thus, a particular ephemeral message group 804 may "expire" and become inaccessible within the context of the ephemeral message group 804 before the ephemeral message group 804 itself expires according to the group duration parameter 808. The group duration parameter 808, the group participation parameter 812, and the message recipient identifier 424 each provide inputs to a group timer 814, which is operable to first determine whether a particular ephemeral message 802 in the ephemeral message group 804 is to be displayed to a particular receiving user, and if so, how long to display it. Note that the identity of the particular receiving user is also known to the ephemeral message group 804 due to the message recipient identifier 424.
[0136] Thus, the group timer 814 is operable to control the total lifespan of the associated ephemeral message group 804 and the individual ephemeral messages 802 included in the ephemeral message group 804. In one example, each ephemeral message 802 within the ephemeral message group 804 remains viewable and accessible for a period of time specified by the group duration parameter 808. In another example, within the context of the ephemeral message group 804, a particular ephemeral message 802 may expire based on the group participation parameter 812. Note that even within the context of the ephemeral message group 804, the message duration parameter 806 may still determine the duration for which a particular ephemeral message 802 is displayed to a receiving user. Thus, the message duration parameter 806 determines the duration for which a particular ephemeral message 802 is displayed to a receiving user, regardless of whether the receiving user is viewing the ephemeral message 802 within or outside the context of the ephemeral message group 804.
[0137] The transient timer system 202 may also be operable to remove a particular transient message 802 from the transient message group 804 based on a determination that an associated group participation parameter 812 has been exceeded. For example, where the sending user has established a group participation parameter 812 of 24 hours from posting, the transient timer system 202 will remove the associated transient message 802 from the transient message group 804 after the specified 24 hours. The transient timer system 202 also operates to remove a transient message group 804 when the group participation parameter 812 for each transient message 802 within the transient message group 804 has expired, or when the transient message group 804 itself has expired according to the group duration parameter 808.
[0138] In some use cases, the creator of a particular ephemeral message group 804 may specify an indefinite group duration parameter 808. In this case, the expiration of the group participation parameter 812 for the last remaining ephemeral message 802 within the ephemeral message group 804 will determine when the ephemeral message group 804 itself expires. In this case, a new ephemeral message 802 with a new group participation parameter 812 added to the ephemeral message group 804 effectively extends the life of the ephemeral message group 804 to a value equal to the group participation parameter 812.
[0139] In response to the transient timer system 202 determining that the transient message group 804 has expired (e.g., is no longer accessible), the transient timer system 202 communicates with the messaging system 100 (and, for example, in particular, the messaging client 104) to cause the indicia (e.g., icon) associated with the relevant transient message group 804 to no longer be displayed within the user interface of the messaging client 104. Similarly, when the transient timer system 202 determines that the message duration parameter 806 for a particular transient message 802 has expired, the transient timer system 202 causes the messaging client 104 to no longer display the indicia (e.g., icon or text identification) associated with the transient message 802.
[0140] Fig. 9The illustrative embodiment of the present invention is a diagrammatic representation of a machine 900 in which instructions 910 (e.g., software, programs, applications, applet, app, or other executable code) may be executed to cause the machine 900 to perform any one or more of the methods discussed herein. For example, the instructions 910 may cause the machine 900 to perform any one or more of the methods described herein. The instructions 910 convert a general purpose, unprogrammed machine 900 into a specific machine 900 that is programmed to perform the functions described and illustrated in the manner described. The machine 900 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a network deployment, the machine 900 may 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. The machine 900 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 910 specifying actions to be taken by the machine 900. In addition, although only a single machine 900 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 910 to perform any one or more of the methods discussed herein. For example, the machine 900 may include any of the client device 102 or a number of server devices that form part of the messaging server system 108. In some examples, the machine 900 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side, and certain operations of the particular method or algorithm are performed on the client side.
[0141] The machine 900 may include a processor 904, a memory 906, and an input / output I / O component 902, which may be configured to communicate with each other via a bus 940. In an example, the processor 904 (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, a processor 908 and a processor 912 that execute instructions 910. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that can execute instructions simultaneously. Although Fig. 9 Multiple processors 904 are shown, but the machine 900 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.
[0142] The memory 906 includes a main memory 914, a static memory 916, and a storage unit 918, which are all accessible by the processor 904 via the bus 940. The main memory 906, the static memory 916, and the storage unit 918 store instructions 910 that implement any one or more of the methods or functions described herein. The instructions 910 may also reside, completely or partially, within the main memory 914, within the static memory 916, within the machine-readable medium 920 within the storage unit 918, within at least one of the processors 904 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 900.
[0143] I / O components 902 may include various components that receive input, provide output, generate output, send information, exchange information, capture measurements, etc. The specific I / O components 902 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 will be less likely to include such a touch input device. It should be understood that I / O components 902 may include Fig. 9928. In various examples, the I / O components 902 may include a user output component 926 and a user input component 928. The user output component 926 may include a visual component (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 928 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.
[0144] In other examples, the I / O component 902 may include a biometric component 930, a motion component 932, an environmental component 934, or a position component 936, as well as a wide range of other components. For example, the biometric component 930 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 932 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).
[0145] Environmental components 934 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., a photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., a barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., an infrared sensor that detects nearby objects), gas sensors (e.g., a gas detection sensor for detecting concentrations 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.
[0146] With respect to cameras, client device 102 may have a camera system including, for example, a front-facing camera on a front surface of client device 102 and a rear-facing camera on a rear surface of client device 102. The front-facing camera may, for example, be used to capture still images and videos (e.g., “selfies”) of a user of client device 102, which may then be enhanced with the enhancement data (e.g., filters) described above. The rear-facing camera may, for example, be used to capture still images and videos in a more traditional camera mode, where the images are similarly enhanced using the enhancement data. In addition to the front-facing camera and the rear-facing camera, client device 102 may also include a 360° camera for capturing 360° photos and videos.
[0147] Additionally, the camera system of the client device 102 may include dual rear cameras (e.g., a main camera and a depth sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of the client device 102. For example, these multi-camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.
[0148] The location component 936 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, from which the altitude can be obtained), an orientation sensor component (e.g., a magnetometer), and the like.
[0149] A variety of technologies may be used to achieve communication. The I / O component 902 also includes a communication component 938, which is operable to couple the machine 900 to a network 922 or a device 924 via a corresponding coupling or connection. For example, the communication component 938 may include a network interface component or another suitable device that interfaces with the network 922. In other examples, the communication component 938 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, a Bluetooth component (e.g., Bluetooth low energy), a Wi-Fi component, and other communication components that provide communication via other modalities. The device 924 may be any peripheral device from another machine or a variety of peripheral devices (e.g., a peripheral device coupled via USB).
[0150] In addition, the communication component 938 can detect an identifier or include a component operable to detect an identifier. For example, the communication component 938 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting a one-dimensional barcode such as a universal product code (UPC) barcode, a multi-dimensional barcode such as a Quick Response (QR) code, an Aztec code, a data matrix, a data symbol (Dataglyph), a maximum code (MaxiCode), PDF417, UltraCode, UCC RSS-2D barcode, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be derived via the communication component 1616, such as a location derived via Internet Protocol (IP) geolocation, a location derived via Wi-Fi signal triangulation, a location derived via detection of an NFC beacon signal that can indicate a specific location, etc.
[0151] Various memories (e.g., main memory 914, static memory 916, and memory of processor 904) and storage unit 918 may store one or more sets of instructions and data structures (e.g., software) used by or implementing any one or more of the methods or functions described herein. When executed by processor 904, these instructions (e.g., instructions 910) cause various operations to implement the disclosed examples.
[0152] The instructions 910 may be sent or received via a network interface device (e.g., a network interface component included in the communication component 938) using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over the network 922. Similarly, the instructions 910 may be sent or received via a coupling (e.g., a peer-to-peer coupling) to the device 924 using a transmission medium.
[0153] Fig.10 1000 is a block diagram illustrating a software architecture 1004 that may be installed on any one or more of the devices described herein. The software architecture 1004 is supported by hardware such as a machine 1002 including a processor 1020, a memory 1026, and an I / O component 1038. In this example, the software architecture 1004 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1004 includes layers such as an operating system 1012, a library 1010, a framework 1008, and an application 1006. In operation, the application 1006 invokes an API call 1050 through the software stack and receives a message 1052 in response to the API call 1050.
[0154] The operating system 1012 manages hardware resources and provides public services. The operating system 1012 includes, for example, a core 1014, a service 1016, and a driver 1022. The core 1014 serves as an abstraction layer between the hardware and other software layers. For example, the core 1014 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. The service 1016 can provide other public services for other software layers. The driver 1022 is responsible for controlling the underlying hardware or interfacing with the underlying hardware. For example, the driver 1022 may include a display driver, a camera driver, a Bluetooth or Bluetooth low energy driver, a flash drive, a serial communication driver (e.g., a USB driver), a WI-FI driver, an audio driver, a power management driver, etc.
[0155] The library 1010 provides a common low-level infrastructure used by the application 1006. The library 1010 may include a system library 1018 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the library 1010 may include an API library 1024, such as a media library (e.g., a library for supporting the presentation 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 Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for presenting in two dimensions (2D) and three dimensions (3D) in graphical content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 1010 may also include various other libraries 1028 to provide many other APIs to the application 1006 .
[0156] The framework 1008 provides a common high-level infrastructure used by the applications 1006. For example, the framework 1008 provides various graphical user interface (GUI) functions, high-level resource management, and high-level positioning services. The framework 1008 can provide a wide range of other APIs that can be used by the applications 1006, some of which can be specific to a particular operating system or platform.
[0157] In the example, the application 1006 may include a home application 1036, a contact application 1030, a browser application 1032, a book reader application 1034, a positioning application 1042, a media application 1044, a messaging application 1046, a game application 1048, and a variety of other applications such as third-party applications 1040. Application 1006 is a program that executes the functions defined in the program. Various programming languages can be used to create one or more of the applications 1006 constructed in various ways, such as object-oriented programming languages (e.g., Objective-C, Java, or C++) or process programming languages (e.g., C or assembly language). In a specific example, a third-party application 1040 (e.g., an application developed using an ANDROID or IOS software development kit (SDK) by an entity other than a supplier of a specific platform) can be a mobile operating system, such as IOS, ANDROID, WINDOWS Phone, or a mobile software running on other mobile operating systems. In this example, the third-party application 1040 can activate an API call 1050 provided by the operating system 1012 to facilitate the functions described herein.
[0158] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by a machine and includes digital or analog communications signals or other intangible media that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.
[0159] "Client Device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.
[0160] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the 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 type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.
[0161] "Component" refers to a device, a physical entity, or logic with boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be packaged functional hardware units designed for use with other components and can be part of a program that generally performs specific functions in related functions. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent 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., applications or application parts) to perform hardware components that operate to perform certain operations described herein. Hardware components can also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include a dedicated circuit or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the 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 specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It should be understood that it can be decided whether to mechanically implement the hardware component in a dedicated and permanently configured circuit or in a circuit temporarily configured (for example, configured by software) for cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (for example, hardwired) or temporarily configured (for example, programmed) to operate in some way or perform certain operations described herein. Considering an example in which a hardware component is temporarily configured (for example, programmed), it is not necessary to configure or instantiate each of the hardware components at any time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be respectively configured as different special-purpose processors (e.g., including different hardware components) at different times. Software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time, and to constitute different hardware components at different times. Hardware components can provide information to other hardware components and receive information from other hardware components. Accordingly, the described hardware components can be considered to be coupled in communication.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled to it in communication. Then, another hardware component can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (e.g., a collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether it is temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described in this article can be implemented at least in part by a processor, wherein one or more specific processors are examples of hardware. For example, at least some of the operation of the method can be performed by one or more processors or the components implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some of the operations in the operation can be performed by a group of computers (as an example of a machine including a processor), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of some operations in the operation can be distributed between processors, can not only reside in a single machine, but also can be deployed across several machines. In some examples, a processor or a component implemented by a processor can be located in a single geographic location (e.g., in a home environment, an office environment, or a server cluster). In other examples, a processor or a component implemented by a processor can be distributed across several geographic locations.
[0162] "Computer-readable storage media" refers to both machine storage media and transmission media. Therefore, these terms include storage devices / media and carrier / modulated data signals. The terms "machine-readable medium", "computer-readable medium" and "device-readable medium" mean the same thing and can be used interchangeably in this disclosure.
[0163] "Transient messages" are messages that are accessible for a limited duration. Transient messages can be text, images, videos, etc. The access time for transient messages can be set by the sender of the message. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.
[0164] "Machine storage media" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the 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), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage media", "device storage media", and "computer storage media" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage media", "computer storage media", and "device storage media" expressly exclude carrier waves, modulated data signals, and other such media (at least some of which are encompassed by the term "signal media").
[0165] “Non-transitory computer-readable storage medium” refers to tangible media capable of storing, encoding, or carrying instructions to be executed by a machine.
[0166] "Signal medium" refers to any intangible medium that is capable of storing, encoding or carrying instructions 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 deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" refers to a signal that has one or more of its various characteristics set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.
Claims
1. A method comprising: receiving, by a messaging application associated with a user, a user input corresponding to a request for a first content feed including a first plurality of media content items provided by one or more friends of the user; in response to receiving the user input, providing display of the first content feed; determining, by the messaging application, that display of the first content feed has completed; as well as In response to determining that display of the first content feed is complete, providing for display of a second content feed including a second plurality of media content items provided by one or more content providers to which the user has subscribed with respect to the messaging application.
2. The method according to claim 1, wherein: Each of the first content feed and the second content feed includes a respective plurality of content collections, each content collection including at least one media content item of a respective plurality of media content items.
3. The method according to claim 2, wherein: Determining that display of the first content feed is complete includes: It is detected that each content set of the plurality of content sets of the first content feed has been displayed.
4. The method according to claim 3, wherein: The detecting is based on the entirety of each content collection of the plurality of content collections of the first content feed having been displayed.
5. The method according to claim 3, wherein: The detecting is based at least in part on a second user input for skipping display of an entirety of at least one content set of the plurality of content sets of the first content feed.
6. The method according to claim 2, further comprising: determining, by the messaging application, that display of the second content feed has completed; as well as In response to determining that display of the second content feed is complete, providing for display of a third content feed including a third plurality of media content items provided by one or more content providers to which the user is not subscribed with respect to the messaging application.
7. The method according to claim 6, wherein: Determining that display of the second content feed is complete includes: It is detected that each content set of the plurality of content sets of the second content feed has been displayed.
8. A system comprising: processor, and a memory storing instructions that, when executed by the processor, configure the processor to perform operations comprising: receiving, by a messaging application associated with a user, a user input corresponding to a request for a first content feed including a first plurality of media content items provided by one or more friends of the user; in response to receiving the user input, providing display of the first content feed; determining, by the messaging application, that display of the first content feed is complete; and In response to determining that display of the first content feed is complete, providing for display of a second content feed including a second plurality of media content items provided by one or more content providers to which the user has subscribed with respect to the messaging application.
9. The system according to claim 8, wherein: Each of the first content feed and the second content feed includes a respective plurality of content collections, each content collection including at least one media content item of a respective plurality of media content items.
10. The system according to claim 9, wherein: Determining that display of the first content feed is complete includes: It is detected that each content set of the plurality of content sets of the first content feed has been displayed.
11. The system according to claim 10, wherein: The detecting is based on the entirety of each content collection of the plurality of content collections of the first content feed having been displayed.
12. The system according to claim 10, wherein: The detecting is based at least in part on a second user input for skipping display of an entirety of at least one content set of the plurality of content sets of the first content feed.
13. The system of claim 9, the operations further comprising: determining, by the messaging application, that display of the second content feed has completed; as well as In response to determining that display of the second content feed is complete, providing for display of a third content feed including a third plurality of media content items provided by one or more content providers to which the user is not subscribed with respect to the messaging application.
14. The system according to claim 13, wherein: Determining that display of the second content feed is complete includes: It is detected that each content set of the plurality of content sets of the second content feed has been displayed.
15. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform operations comprising: receiving, by a messaging application associated with a user, a user input corresponding to a request for a first content feed including a first plurality of media content items provided by one or more friends of the user; in response to receiving the user input, providing display of the first content feed; determining, by the messaging application, that display of the first content feed has completed; as well as In response to determining that display of the first content feed is complete, providing for display of a second content feed including a second plurality of media content items provided by one or more content providers to which the user has subscribed with respect to the messaging application.
16. The computer-readable medium of claim 15, wherein: Each of the first content feed and the second content feed includes a respective plurality of content collections, each content collection including at least one media content item of a respective plurality of media content items.
17. The computer-readable medium of claim 16, wherein: Determining that display of the first content feed is complete includes: It is detected that each content set of the plurality of content sets of the first content feed has been displayed.
18. The computer-readable medium of claim 17, wherein: The detecting is based on the entirety of each content collection of the plurality of content collections of the first content feed having been displayed.
19. The computer-readable medium of claim 17, wherein: The detecting is based at least in part on a second user input for skipping display of an entirety of at least one content set of the plurality of content sets of the first content feed.
20. The computer readable medium of claim 16, the operations further comprising: determining, by the messaging application, that display of the second content feed has completed; as well as In response to determining that display of the second content feed is complete, providing for display of a third content feed including a third plurality of media content items provided by one or more content providers to which the user is not subscribed with respect to the messaging application.