Patent Application
20230252085
A social media messaging platform may facilitate the exchange of millions or hundreds of millions of social media messages among its users. The messages posted to the platform often can provide users of the platform the latest update or reporting on current events. The exchange of messages on the messaging platform may be part of a conversation between users. Some conventional messaging systems may store the reply structure of messages so that a user can view parts of the conversation when viewing a particular message. However, the list of messages that form the conversation view may be relatively large, which may lead to slower load times and/or higher request failures.
A messaging platform facilitates the exchange of messages between users of the messaging platform. The messages may be part of a conversation occurring on the messaging platform. For example, a user may post a message on the platform, and other users may post a number of replies to that message, and then replies to the replies, and so forth. The reply structure may be stored as a conversation graph, and the messaging platform may store any number of conversation graphs that relate to conversations taking place on the messaging platform. In some examples, the conversation graph may be relatively large (e.g., a number of nodes in the conversation graph exceeding a threshold number). The generating and maintaining of the conversation graphs may enable faster retrieval of information when responding to requests to view messages in a reply relationship with a particular message.
When viewing content on the messaging platform, a user may select a message to view other messages of the conversation graph. In response to the user’s selection, the client application may generate and send a conversation view request to the messaging platform to retrieve messages from the conversation graph. Rather than displaying all of the messages related to the conversation graph (which may be relatively large), the messaging platform may perform a ranking mechanism to rank and select a subset of messages that are provided to the user.
In some examples, the ranking mechanism includes a two-level ranking mechanism in which i) messages of the conversation graph are ranked and the conversation graph is pruned to obtain a candidate subset with higher quality messages and ii) messages of the candidate subset are ranked (e.g., re-ranked) to form a ranked list. In some examples, at least a portion of the ranked list is transmitted to a client application for display. The candidate subset is obtained from the conversation graph by pruning the conversation graph, where the ranking of the candidate subset involves more computer-resource intensive ranking operations using one or more predictive models (e.g., machine-learning models). In other words, the candidate subset includes the remaining messages after the pruning step, and the messaging platform uses one or more predictive models to rank the messages of the candidate subset.
In some examples, the amount of pruning (e.g., how many messages the candidate subset contains) is dependent on a system load factor. For example, if the system load factor is relatively high (e.g., above a threshold level), the messaging platform may prune a higher number of messages (which may result in a lower number of messages within the candidate subset). In some examples, the messaging platform determines the system load factor based on a system load metric (e.g., a latency). The system load metric may be a time interval or duration (e.g., averaged time interval) for processing conversation view requests over a period of time (e.g., the average latency over a 2 or 3 minute window). If the system load metric is relatively high, the messaging platform may increase the number of messages that are pruned from the conversation graph. In some examples, the amount of pruning is dependent on the size of the conversation graph (e.g., the number of messages included within the conversation graph). For example, if the size of the conversation graph is relatively large (e.g., above a threshold level), the messaging platform may increase the number of messages that are pruned from the conversation graph. In some examples, the amount of pruning is dependent on a combination of the system load factor and the size of the conversation graph.
The ranking mechanism implemented by the messaging platform to filter and retrieve messages of a conversation graph may increase the speed of information retrieval, reduce computer resources during high system loads, and/or increase the quality of messages delivered to the client application. For example, the pruning stage may use a ranking algorithm that can remove less-desirable messages (e.g., unwanted messages) earlier in the process, thereby increasing the quality of messages that are selected for the more resource-intensive ranking mechanism. Also, by adjusting the number of messages that are pruned using the system load metric, the speed of information retrieval may be increased during high system loads and the system’s overall reliability may be increased. For example, the messaging platform may be able to handle a higher number of conversation view requests, thereby reducing the number of conversation view requests that may fail.
The first level ranking (e.g., the pruning stage) may include ranking the messages of the conversation graph using a plurality of first signals and selecting, based on the rank, a portion of the messages of the conversation graph as a candidate subset. The first signals may include engagement-based signals, health-based signals, and metadata-based signals to capture higher quality messages from the conversation graph. In some examples, the first signals may include whether or not a message is a deleted message (e.g., a message not marked for deletion may be ranked higher than a message marked for deletion), whether or not an author of a message is a focal author (e.g., a message by the focal author may be ranked higher than other messages), whether or not an author of a message is a root author (e.g., a message by the root author may be ranked higher than other messages), and/or whether or not a message is a message of the viewer (e.g., the one that requested the conversation view request) (e.g., a message by the viewer may be ranked higher than other messages).
In some examples, the first signals include the number of engagement counts with a respective message (e.g., a message with a higher engagement count is ranked higher than a message with a lower engagement count). In some examples, the engagement count includes the number of times that the message has been favoritized, the number of times that the message has been re-shared, and/or the number of times that a reply was received to a respective message.
In some examples, the first signals include health-based signals about the quality of a message of a conversation graph. In some examples, the health-based signals include a toxicity signal that represents a predicted level of toxicity or abusive content. In some examples, the health-based signals include a reporting signal that represents a predicted level of another user (e.g., a target or mentioned user) blocking, muting, or reporting the message. In some examples, the health-based signals include a spam signal that represents a predicted level of another user reporting the message as spam (when the message is created). In some examples, the health-based signals include a reporting signal that represents a predicted level of any user reporting the message. In some examples, the health-based signals are predicted by one or more prediction models and are retrieved during the pruning stage.
The messaging platform may determine the quantity of messages selected for the candidate subset based on a system load factor. In other words, the messaging platform may determine the amount (e.g., percentage) of pruning based on the system load factor. In some examples, the system load factor is computed based on the latency of executing conversation view requests over a period of time. In some examples, the messaging platform may determine the amount (e.g., percentage) of pruning based on a conversation size factor. In some examples, the messaging platform may determine the amount (e.g., percentage) of pruning based on a combination of the system load factor and the conversation size factor.
The messaging platform may define a lower threshold and an upper threshold for the system load factor. If the latency is equal to or less than the lower threshold, the messaging platform may determine a first value (e.g., zero) for the system load factor, which may cause a first percentage (e.g., 32%) of the conversation graph to be pruned. In some examples, if the latency is equal to or less than the lower threshold, the messaging system is operating in a normal mode. If the latency is equal to or higher than the upper threshold, the messaging platform may determine a second value (e.g., one) for the system load factor, which may cause a second percentage (e.g., 55%) of the conversation graph to be pruned. In some examples, if the latency is higher than the upper threshold, the messaging system is operating in a peak system load mode. In some examples, if the latency is a value between the lower threshold and the upper threshold, the messaging platform may compute a value for the system load factor, where the value is between the first value and the second value, which causes a certain percentage of the conversation graph to be pruned (e.g., between the first percentage and the second percentage). For example, the percentage of pruning may increase (e.g., linearly increase) from the lower threshold to the upper threshold. In some examples, if the latency is between the lower threshold and the higher threshold, the system is operating in a high system load mode.
The amount of pruning may be adjusted based on the conversation size factor. For example, the messaging platform may determine the conversation size factor based on the size of the conversation graph. The messaging platform may define a lower threshold and an upper threshold for the conversation size factor. In some examples, if the size of the conversation graph is lower than the lower threshold, the messaging platform may determine the conversation size factor as a first value (e.g., zero). In some examples, if the size of the conversation graph is higher than the upper threshold, the messaging platform may determine the conversation size factor as a second value (e.g., one). In some examples, if the size of the conversation graph is between the lower threshold and the upper threshold, the messaging platform may compute the value of the conversation factor as being between the first value and the second value. In some examples, the messaging platform may determine the amount of pruning based on the conversation size factor and the system load factor.
The messaging platform may select or prune the messages for the candidate subset using the scores from the first level ranking. In some examples, the messaging platform may select a message having the highest score (e.g., highest rank) from a candidate list. The candidate list first includes the direct replies to the focal message (e.g., all the direct replies to the focal message) along with their scores assigned from the first level ranking. The messaging platform may select the highest scoring message to be included in the candidate subset and may add any replies to the selected message in the candidate list. This process continues until the candidate subset has a number of messages that satisfy the pruning factor. For example, if the conversation graph has 100 messages and the pruning rate is 30%, the process continues until the candidate subset has 70 messages. This methodology may ensure that the conversation graph is connected after the pruning step and no message is served without their parent message.
The second level ranking may include ranking the messages of the candidate subset (e.g., the output of the first level ranking) according to a plurality of second signals. The second signals may include one or more signals that are different from one or more of the first signals. In some examples, the number of second signals may be greater than the number of first signals. The second signals may include a wide variety of signals such as data structure-related signals, health-related signals, engagement signals, social graph signals, historical aggregate signals, and/or content-related signals. The number of second signals and the number of different categories of the second signals used in the prediction may improve the accuracy of the model predictions.
In some examples, the messaging platform may use the plurality of second signals to determine predictive outcomes for each message of the candidate subset. The predictive outcomes are user engagement outcomes that are predicted for each message of the candidate subset. The messaging platform may combine the predictive outcomes to form an engagement score for a particular message and the engagement scores are used to rank the messages of the candidate subset.
The predictive outcomes may include a negative engagement probability, a positive engagement probability, and a reciprocal engagement probability. The negative engagement probability indicates a probability value that the user is predicted to negatively view or engage with the message (e.g., the user may find a message abusive). The positive engagement probability indicates a probability value that the user is predicted to positively engage with the message (e.g., like or favoritize a message). The reciprocal engagement probability indicates a probability value that the user is predicted to further develop the conversation graph (e.g., predicted to reply to the message). The incorporation of the reciprocal engagement probability into the predictive outcomes may incentivize more conversations on the platform.
The second level ranking may use predictive models (e.g., neural networks) to predict the engagement outcomes, which may be more computer-resource intensive in terms of memory and computer processing unit (CPU) power than the first level ranking. In some examples, the second level ranking uses more signals (e.g.., substantially more) signals than the first level ranking. In some examples, the messaging platform may select the top ranked messages from the candidate subset, which forms the ranked list. At least a portion of the messages from the ranked list may be delivered to the client application to be displayed.
Providing a ranked list allows the messaging platform to increase the value provided to users while serving fewer responses. For example, the messaging platform may provide a subset of the responses (e.g., top 10, 15, 20, etc. responses) for each request, which may lead to faster computation on the server, faster load times for the user, and substantially without loss (e.g., any loss) of engagement. Further, the messages ranked according to the engagement values may be specific to each user. For example, some messages of the conversation graph may be more relevant to a first user while other messages of the conversation graph may be relevant to a second user. However, the predictive outcomes determined by the messaging platform are tailored to the specific user. In contrast, some conventional approaches use a voting-based mechanism that may provide the same view for each. In addition, because the messaging platform incorporates the reciprocal engagement probability within its scoring algorithm, the messaging platform may incentivize more conversations on the messaging platform.
According to an aspect, a method for ranking messages of a conversation graph in a messaging platform includes receiving, over a network, a conversation view request to retrieve messages from a conversation graph stored on the messaging platform, obtaining a system load metric associated with the messaging platform, computing a pruning factor based on the system load metric, pruning the conversation graph according to the pruning factor to obtain a candidate subset of messages, ranking the candidate subset of messages to form a ranked list of messages, and transmitting, over the network, information to render at least a portion of the ranked list on a client application.
According to some aspects, the system load metric includes a latency of executing conversation view requests by the messaging platform. The method may include obtaining a size of the conversation graph, wherein computing the pruning factor includes computing the pruning factor based on the size of the conversation graph and the system load metric. The method may include ranking messages of the conversation graph using a plurality of first signals to form an intermediate ranked list, wherein the intermediate ranked list is pruned according to the pruning factor such that lower ranked messages are not included in the candidate subset of messages. The plurality of first signals may include at least one of a toxicity signal, a reporting signal, or a spam signal. The candidate subset of messages are ranked using a plurality of second signals, the plurality of second signals including one or more signals that are different from the plurality of first signals. The method may include computing a first value for a system load factor in response to the system load metric being equal to or less than a lower threshold, computing a second value for the system load factor in response to the system load metric being equal to or greater than an upper threshold, and computing a third value for the system load factor in response to the system load metric being between the lower threshold and the upper threshold, the third value being a value between the first value and the second value, wherein the pruning factor is computed based on the first value, the second value, or the third value for the system load factor. In some examples, ranking the candidate subset includes computing a plurality of predictive outcomes for each message of the candidate subset, computing an engagement value for a respective message based on the plurality of predictive outcomes, and ranking the candidate subset using the engagement values.
According to an aspect, a messaging system includes at least one processor and a non-transitory computer-readable medium storing executable instructions that when executed by the at least one processor cause the at least one processor to obtain a system load metric associated with a messaging platform, compute a pruning factor based on the system load metric, rank messages of a conversation graph using a plurality of first signals to form an intermediate ranked list, prune the intermediate rank list according to the pruning factor to obtain a candidate subset of messages, rank the candidate subset of messages using a plurality of second signals to form a ranked list of messages, and transmit, over a network, information to render at least a portion of the ranked list on a client application.
In some aspects, the system load metric includes a latency of executing conversation view requests by the messaging platform. The executable instructions include instructions that when executed by the at least one processor cause the at least one processor to compute a system load factor based on the system load metric, obtain a size of the conversation graph, compute a conversation size factor based on the size of the conversation graph, compute the pruning factor based on the system load factor and the conversation size factor. The plurality of first signals include at least one of metadata-based signals, health-related signals, or engagement-based signals. The plurality of second signals include machine-learning (ML) signals configured to be inputted to a predictive model. The executable instructions include instructions that when executed by the at least one processor cause the at least one processor to compute a plurality of predictive outcomes for each message of the candidate subset, compute an engagement value for a respective message based on the plurality of predictive outcomes, and rank the candidate subset using the engagement values.
According to an aspect, a non-transitory computer-readable medium storing executable instructions that when executed by at least one processor causes the at least one processor to execute operations. The operations include obtaining a system load metric associated with a messaging platform and a size of a conversation graph stored on the messaging platform, computing a pruning factor based on the system load metric and the size of the conversation graph, ranking messages of a conversation graph using a plurality of first signals to form an intermediate ranked list, pruning the intermediate rank list according to the pruning factor to obtain a candidate subset of messages, ranking the candidate subset of messages using a plurality of second signals to form a ranked list of messages, and transmitting, over a network, information to render at least a portion of the ranked list on a client application.
In some examples, the system load metric includes a latency of executing conversation view requests by the messaging platform. The operations may further include computing a system load factor based on the system load metric, computing a conversation size factor based on the size of the conversation graph, and computing the pruning factor based on the system load factor and the conversation size factor. The plurality of first signals includes at least one of metadata-based signals, health-related signals, or engagement-based signals. The plurality of second signals has a number of signals greater than the plurality of first signals. The operations further include computing a plurality of predictive outcomes for each message of the candidate subset, computing an engagement value for a respective message based on the plurality of predictive outcomes, and ranking the candidate subset using the engagement values.
For retrieving messages of a conversation graph, the messaging platform may determine how many messages are to be pruned from the conversation graph during a pruning stage based on a system load factor and/or a conversation size factor. The system load factor is computed based on a system load metric (e.g., a latency of executing conversation view requests over a period of time). The conversation size factor is computed based on the size of the conversation graph. In some examples, the messaging platform may determine a certain percentage of the conversation graph to be pruned using the system load factor and/or the conversation size factor. The messaging platform may rank the messages of the conversation graph using first signals, which may include engagement-based signals, health-based signals, and/or metadata-based signals.
The messaging platform may prune the bottom ranked messages to obtain a candidate subset having higher quality messages. The messaging platform may determine an engagement score for each message of the candidate subset based on predictive outcomes for a respective message. For example, the messaging platform may combine a negative engagement probability, a positive engagement probability, and a reciprocal engagement probability to form an engagement value for a respective message. Then, the messaging platform may select and rank the messages of the candidate subset using the engagement values, which forms a ranked list. In response to the conversation view request, the messaging platform may send information to render at least a portion of the messages from the ranked list on a user interface of a client application.
The ranking mechanism implemented by the messaging platform to filter and retrieve messages of a conversation graph may increase the speed of information retrieval, reduce computer resources during high system loads, and/or increase the quality of messages delivered to the client application. For example, the pruning stage may use a ranking algorithm that can remove less-desirable messages (e.g., unwanted messages) earlier in the process, thereby increasing the quality of messages that are selected for the more resource-intensive ranking mechanism. Also, by adjusting the number of messages that are pruned based on a system load metric and/or a size of the conversation graph, the speed of information retrieval may be increased during high system loads and the system’s overall reliability may be increased. The messaging platform may be able to handle a higher number of conversation view requests, thereby reducing the number of conversation view requests that may fail due to long processing delays.
The client application 154 may be a social media messaging application in which users post and interact with messages exchanged on the messaging platform 104. In some examples, the client application 154 is a native application executing on an operating system of the computing device 152 or may be a web-based application executing on the server computer 102 (or other server) in conjunction with a browser-based application of the computing device 152. The computing device 152 may access the messaging platform 104 via the network 150 using any type of network connections and/or application programming interfaces (APIs) in a manner that permits the client application 154 and the messaging platform 104 to communicate with each other.
The computing device 152 may be a mobile computing device (e.g., a smart phone, a PDA, a tablet, or a laptop computer) or a non-mobile computing device (e.g., a desktop computing device). The computing device 152 also includes various network interface circuitry, such as for example, a mobile network interface through which the computing device 152 can communicate with a cellular network, a Wi-Fi network interface with which the computing device 152 can communicate with a Wi-Fi base station, a Bluetooth network interface with which the computing device 152 can communicate with other Bluetooth devices, and/or an Ethernet connection or other wired connection that enables the computing device 152 to access the network 150.
The server computer(s) 102 may be a single computing device or may be a representation of two or more distributed computing devices communicatively connected to share workload and resources. The server computer(s) 102 may include at least one processor and a non-transitory computer-readable medium that stores executable instructions that when executed by the at least one processor cause the at least one processor to perform the operations discussed herein.
The messaging platform 104 is a computing platform for facilitating communication (e.g., real-time communication) between user devices (one of which is shown as computing device 152). The messaging platform 104 may store millions of accounts 141 of individuals, businesses, and/or entities (e.g., pseudonym accounts, novelty accounts, etc.). One or more users of each account 141 may use the messaging platform 104 to send messages to other accounts 141 inside and/or outside of the messaging platform 104. In some examples, the messaging platform 104 may enable users to communicate in “real-time”, e.g., to converse with other users with minimal delay and to conduct a conversation with one or more other users during simultaneous sessions. In other words, the messaging platform 104 may allow a user to broadcast messages and may display the messages to one or more other users within a reasonable time frame (e.g., less than two seconds) to facilitate a live conversation between users. In some examples, recipients of a message may have a predefined graph relationship in a connection graph 134 with an account 141 of the user broadcasting the message.
The connection graph 134 includes a data structure that indicates which accounts 141 in the messaging platform 104 are associated with (e.g., following, friends with, subscribed to, etc.) a particular account 141 and are, therefore, subscribed to receive messages from the particular account 141. For example, the connection graph 134 may link a first account with a second account, which indicates that the first account is in a relationship with the second account. The user of the second account may view messages posted on the messaging platform 104 by the user of the first account (and/or vice versa). The relationships may include unidirectional (e.g., follower/followee) and/or bidirectional (e.g., friendship). The messages can be any of a variety of lengths which may be limited by a specific messaging system or protocol.
Users interested in viewing messages authored by a particular user can choose to follow the particular user. A first user can follow a second user by identifying the second user as a user the first user would like to follow. After the first user has indicated that they would like to follow the second user, the connection graph 134 is updated to reflect the relationship, and the first user will be provided with messages authored by the second user. Users can choose to follow multiple users. Users can also respond to messages and thereby have conversations with one another. In addition, users may engage with messages such as sharing a message with their followers or favoritizing (or “liking”) a message in which the engagement is shared with their followers.
Messages exchanged on the messaging platform 104 are stored in a message repository 138. The message repository 138 may include one or more tables storing records. In some examples, each record corresponds to a separately stored message. For example, a record may identify a message identifier for the message posted to the messaging platform 104, an author identifier (e.g., @tristan) that identifies the author of the message, message content (e.g., text, image, video, and/or URL of web content), one or more participant account identifiers that have been identified in the body of the message, and/or reply information that identifies the parent message to which the message replies (if the message is a reply to a message).
The messaging platform 104 includes a conversation graph manager 136 that generates the conversation graphs 126 and a timeline manager 142 that injects a timeline 156 of messages into the client application 154. The conversation graph manager 136 generates (and updates) one or more conversation graphs 126 as messages are exchanged on the messaging platform 104. In some examples, the conversation graphs 126 are stored in a data storage device associated with the messaging platform 104. In some examples, the conversation graphs 126 are stored at the timeline manager 142. The messaging platform 104 may store multiple conversation graphs 126 (e.g., hundreds, thousands, or millions of conversation graphs 126).
Each conversation graph 126 may represent a structure of replies to an original, non-reply message (e.g., a root message). For example, whenever a user creates and posts an original, non-reply message on the messaging platform 104, a potential new conversation may be started. Others can then reply to that original or “root” message and create their own reply branches. Over time, if the number of replies to the original, non-reply message (and/or replies to the replies to the original, non-reply message) is greater than a threshold level, the conversation graph manager 136 may assign a conversation identifier to the conversation graph 126, and the conversation identifier may uniquely identify the conversation graph 126. In some examples, the conversation graph manager 136 may assign a conversation identifier to each message with a reply. For example, if the messaging platform has message A, and then someone responds to it with a message B, then message A is assigned a conversation identifier that can be used to identify a conversation, which leads to the conversation graph 126 as discussed in detail below. In some examples, if there is a reply to a message, then there is a conversation.
The conversation graph 126 may be a hierarchical data structure representing the messages in a conversation. In some examples, the conversation graph 126 includes a nonlinear or linear data structure. In some examples, the conversation graph 126 includes a tree data structure. The conversation graph 126 may include nodes 128 (or vertices) representing messages and edges 130 (or arcs) representing links between nodes 128. The conversation graph 126 may store the message identifier of the respective message at each node 128. In some examples, the conversation graph 126 stores a user identifier of the author of a respective message at each node 128. The conversation graph 126 may define one or more branches 132 of nodes 128. In some examples, a branch 132 is a portion (e.g., a sub-tree) of the conversation graph 126 that includes one or more nodes 128. In some examples, a branch 132 may be at least two nodes 128 connected by an edge 130, where one of the nodes 128 is a leaf node. In some examples, a branch 132 may be defined as the messages that are connected in a single line (e.g., a leaf message, a first parent message connected to the leaf message, a second parent message connected to the first parent message and so forth until a parent message does not have another parent message).
It is noted that the term “node” may be referred to as a message within the conversation graph 126, or the term “message” may be referred to as a node 128 if that message is included as part of the conversation graph 126. A particular node 128 may be linked to another node 128 via an edge 130, and the direction of the edge 130 identifies the parent message. The nodes 128 may represent a root message, messages in reply to the root message, messages in reply to the messages in reply to the root message, etc.
The conversation graph manager 136 may generate the conversation graph 126 based on a reply structure of the messages. The reply structure may be identified based on metadata associated with each message and/or reply information identified from within the message content. In some examples, the reply structure is identified based on metadata associated with each message which is received from the client application 154 to compose the message. For example, a user may click on a reply link displayed below a message displayed on the user interface of the client application 154. The client application 154 may then display a message composition box for drafting a reply message. The client application 154 may submit metadata including the reply relationship (e.g., a message identifier of the parent message) with the reply message. In some examples, the reply relationship may be explicitly defined by the user within the message content (e.g., identifying a user account 141 (e.g., @tristan) within the body of the message). In this example, the reply structure may be identified by identifying one or more account identifiers and/or message identifiers mentioned within the body of the message.
The timeline manager 142 may send digital information, over the network 150, to enable the client application 154 to render and display a timeline 156 of social content on the user interface of the client application 154. The timeline 156 includes a stream of messages (e.g., message A, message B, message C). In some examples, the stream of messages are arranged in reverse chronological order. In some examples, the stream of messages are arranged in chronological order. In some examples, the timeline 156 is a timeline of social content specific to a particular user. In some examples, the timeline 156 includes a stream of messages curated (e.g., generated and assembled) by the messaging platform 104. In some examples, the timeline 156 includes a list of messages that resulted from a search on the messaging platform 104. In some examples, the timeline 156 includes a stream of messages posted by users from accounts 141 that are in relationships with the account 141 of the user of the client application 154 (e.g., a stream of messages from accounts 141 that the user has chosen to follow on the messaging platform 104). In some examples, the stream of messages includes promoted messages or messages that have been re-shared.
When viewing the messages on the timeline 156, the user may select one of the messages (e.g., message B) from the timeline 156, which may cause the client application 154 to generate and send a conversation view request 121, over the network 150, to the messaging platform 104. In some examples, the selected message (e.g., message B) may be referred to as a context message or focal message that may serve as an entry point or point of reference within the conversation graph 126. A focal author may be an author of the focal message. The conversation view request 121 may be a request to retrieve messages from the conversation graph 126. In some examples, the conversation view request 121 includes the message identifier of the selected messages and the user identifier of the user of the client application 154. In some examples, the conversation view request 121 also includes the time of the request, which device the user is on, the operating system (OS) version, and/or other metadata associated with the request.
In response to the conversation view request 121, the timeline manager 142 may control the ranking engine 108 to execute the operations discussed herein to retrieve and identify a portion of the messages of the conversation graph 126 to be provided to the user. The ranking engine 108 includes a light ranking manager 110 configured to identify a candidate subset 112 from the messages of the conversation graph 126 based on a plurality of signals 106. For example, the light ranking manager 110 may rank the messages of the conversation graph 126 using the signals 106. The light ranking manager 110 may prune the conversation graph 126 to identify the candidate subset 112, where the candidate subset 112 may include higher quality messages from the conversation graph 126.
The light ranking manager 110 may determine how many messages are pruned based on a system load metric 167 (e.g., a latency 168 of executing conversation view requests 121) and/or a size 170 of the conversation graph 126. In some examples, the light ranking manager 110 may determine a pruning factor 178 based on the system load metric 167 and/or the size 170 and prune the conversation graph 126 according to the pruning factor 178. In some examples, the pruning factor 178 includes a pruning percentage such as “prune X%” of the conversation graph 126. The light ranking manager 110 may remove the bottom X% of ranked messages, where the remaining messages are identified as the candidate subset 112.
The ranking engine 108 includes a prediction manager 114 configured to obtain a ranked list 116 of messages of the candidate subset 112 based on a plurality of signals 118. For example, the prediction manager 114 may rank the messages from the candidate subset 112 using the signals 118. The signals 118 may include one or more signals that are different from the signals 118. In some examples, the number of signals 118 used by the prediction manager 114 is greater than the number of signals 118 used by the light ranking manager 110. In some examples, the prediction manager 114 uses one or more neural networks to rank the messages of the candidate subset 112. The timeline manager 142 may transmit information to the client application 154 to render the ranked list 116 (or a portion thereof). In some examples, if the ranked list 116 includes a number of messages exceeding a threshold level, the timeline manager 142 may select a portion of the ranked list 116. For example, if the ranked list 116 includes 150 messages, the timeline manager 142 may return the top X number (e.g., top 50 messages) from the ranked list 116.
Referring to
The data service(s) 166 may be components on the messaging platform 104 that compute or otherwise derive data obtained by the messaging platform 104 and/or the client application 154. In some examples, the light ranking manager 110 may communicate with the data services 166 over a server communication interface. In some examples, the light ranking manager 110 may obtain at least some of the signals 106 from the data service(s) 166 via one or more APIs. In some examples, in response to the conversation view request 121, the light ranking manager 110 may transmit a thrift call or a remote procedure call (RPC) to data service(s) 166 and then receive at least some of the signals 106 from the relevant data service(s) 166. In some examples, the light ranking manager 110 may transmit a representational state transfer (REST) request to the data service(s) 166 and then receive at least some of the signals 106 from the relevant data service(s) 166. In some examples, the light ranking manager 110 communicates with the data service(s) 166 via a GraphQL request. In some examples, the light ranking manager 110 obtains some of the signals 106 from other components of the messaging platform 104 including the conversation graph manager 136 and/or the timeline manager 142.
The signals 106 may include one or more signals relating to the quality of the messages of the conversation graph 126. The signals 106 may include metadata-based signals 160, health-based signals 162, and/or engagement-based signals 164.
In some examples, the metadata-based signals 160 may include whether or not a message is a deleted message, whether or not an author of a message is a focal author, whether or not an author of a message is a root author, and/or whether or not a message is a message of the viewer. In some examples, the engagement-based signals 164 include the number of engagement counts with a respective message. The number of engagement counts may represent the number of times users have engaged with the message of the conversation graph 126. In some examples, the engagement count includes the number of times that the message has been favoritized (e.g., liked) by users of the messaging platform 104. In some examples, the engagement count includes the number of times that the message has been reshared by users of the messaging platform 104. In some examples, the engagement counts include the number of times that the message has received a reply posted by users of the messaging platform 104. In some examples, the engagement count includes a combination of the number of times that the message has been favoritized, reshared, and replied.
The health-based signals 162 may include signals relating to the health of the messages on the messaging platform 104 (e.g., how abusive, offensive, and/or toxic the messages are). In some examples, the light ranking manager 110 may obtain the health-based signals 162 from one or more data services 166. The data service(s) 166 may use one or more machine-learning models (e.g., neural network(s)) to generate the health-based signals 162. In some examples, the light ranking manager 110 may transmit the message identifiers of the messages of the conversation graph 126 to the data service(s) 166 and receive the health-based signals 162 from the data service(s) 166.
In some examples, referring to
The health-based signals 162 may include a reporting signal 163 that represents a predicted level of a target (mentioned) user blocking, muting, or reporting the message. In some examples, the reporting signal 163 is considered a blocking signal. In some examples, the reporting signal 163 includes a value between a first value (e.g., zero) and a second value (e.g., one). In some examples, the reporting signal 163 may include a value that represents a likelihood that a respective message will be blocked, muted, and/or reported. In some examples, a predictive model (e.g., a neural network) may predict a likelihood that the message will be blocked, muted, or reported based on a plurality of features. The plurality of features may include features relating to the content of the message (e.g., text length, punctuations, hashtags, emojis, mentions, and/or if the text is abusive, etc.). The plurality of features may include features about the source user and the target user (e.g., the number of times the source and/or target user was blocked/reported/muted, the follower count, whether the source and/or target user has a profile or a profile that is available to view, the number of messages posted by the source and/or target user, the account age, profile name, description, screen name, and/or URL, etc.). In some examples, the reporting signal 163 may represent a predicted level that a respective message will receive any report.
In some examples, the health-based signals 162 may include a spam signal 165 that represents a predicted level of another user reporting the message as spam (when the message is created). In some examples, the spam signal 165 includes a value between a first value (e.g., zero) and a second value (e.g., one). In some examples, a predictive model (e.g., a neural network) may predict a likelihood that the message will be reported as spam based on a plurality of features. The plurality of features may include features relating to the content of the message (e.g., text length, punctuations, hashtags, emojis, mentions, and/or if the text is abusive, etc.). The plurality of features may include features about the source user (e.g., the number of times the source user was blocked/reported/muted, the follower count, whether the source target user has a profile or a profile that is available to view, the number of messages posted by the source user, the account age, profile name, description, screen name, and/or URL, etc.).
The light ranking manager 110 includes a ranking unit 159 configured to rank the messages of the conversation graph 126 using the signals 106. In some examples, the ranking unit 169 may generate scores for the messages of the conversation graph 126 using the signals 106. In some examples, the ranking unit 159 includes a heuristic-based algorithm that uses the signals 106 to generate a ranked list 182 (e.g., an intermediate ranked list) and/or generate a score for each message of the conversation graph 126. In some examples, the ranked list 182 includes a score associated with a respective message of the conversation graph 126. In some examples, the ranking unit 159 includes one or more predictive models. In some examples, the ranking unit 159 includes one or more neural networks.
In some examples, the ranking unit 159 may apply a series of rules to determine the ranked list 182, where a message not marked for deletion is ranked higher than a message marked for deletion, a message by the focal author is ranked higher than other messages, a message by the root author is ranked higher than other messages, a message by the viewer is ranked higher than other messages, and a message with a higher engagement count is ranked higher than a message with a lower engagement count. In some examples, the ranking unit 159 may combine the health-based signals 162 (e.g., the toxicity signal 161, the reporting signal 163, and the spam signal 165) to produce a composite health signal, where a message having a higher composite health signal is ranked lower than a message having a lower composite health signal.
The light ranking manager 110 includes a system load unit 172 configured to determine the quantity of messages selected for the candidate subset 112 based on a system load metric 167 (e.g., a latency 168) and/or a size 170 of the conversation graph 126. The candidate subset 112 may include a portion of the messages in the conversation graph 126. The light ranking manager 110 may determine which and how many messages are included within the candidate subset 112. The system load unit 172 may determine the amount (e.g., percentage of) of pruning based on the system load metric 167 and/or the size 170 of the conversation graph 126. For example, if the system load metric 167 is relatively high (e.g., greater than a threshold), the system load unit 172 may increase the number of messages that are pruned (e.g., not included within the candidate subset 112). If the system load metric 167 is relatively low (e.g., less than a threshold), the system load unit 172 may decrease the number of messages that are pruned. In some examples, if the size 170 of the conversation graph 126 is relatively high (e.g., greater than a threshold), the system load unit 172 may increase the number of messages that are pruned. If the size 170 of the conversation graph 126 is relatively low (e.g., less than a threshold), the system load unit 172 may decrease the number of messages that are pruned.
When a conversation view request 121 is received, the system load unit 172 may obtain the system load metric 167. The system load metric 167 may be a parameter that represents a level of system load caused by servicing conversation view requests 121. In some examples, during periods of time when there are many conversation view requests 121 and/or when large conversation graphs 126 are requested for viewing, the system may be under heavier loads, which can cause delays/failures in rendering messages from a conversation graph 126. In some examples, the system load metric 167 may be a level of CPU usage provided by the ranking engine 108. In some examples, the system load metric 167 may be a level of memory allocation used by the ranking engine 108.
In some examples, the system load metric 167 includes a latency 168. In some examples, the latency 168 is the time delay (e.g., time window, time interval) from receiving a conversation view request 121 to rendering messages from the conversation graph 126 on the user interface of the client application 154. In some examples, the latency 168 may be the latency of executing a conversation view request 121. In some examples, the latency 168 is the period of time from receipt of a conversation view request 121 to rendering the ranked list 116 (or a portion thereof) on the client application 154. In some examples, the latency 168 is the average latency of executing conversation view requests 121 over a period of time (e.g., three minutes).
The system load unit 172 may compute a system load factor 174 based on the system load metric 167. Although some of the description uses latency 168 as an example of the system load metric 167, it is understood that the system load metric 167 may encompass any type of metric for measuring the system’s load. The system load factor 174 may be a value within a range of values. In some examples, the system load factor 174 may be a first value (e.g., zero), a second value (e.g., one), or one of a series of values between the first value and the second value. In some examples, the system load unit 172 may compare the system load metric 167 (e.g., latency 168) to an upper threshold 171 and/or a lower threshold 173 to compute the system load factor 174.
If the system load metric 167 is equal to or less than the lower threshold 173, the system load unit 172 may determine the first value (e.g., zero) for the system load factor 174. In some examples, if the system load metric 167 is less than the lower threshold 173, the messaging platform 104 may be operating in a normal mode. If the system load metric 167 is equal to or higher than the upper threshold 171, the system load unit 172 may determine a second value (e.g., one) for the system load factor 174. In some examples, if the system load metric 167 is higher than the upper threshold 171, the messaging platform 104 may be operating in a high system load mode. In some examples, if the latency 168 is a value between the lower threshold 173 and the upper threshold 171, the system load unit 172 may compute a value for the system load factor 174, where the value is between the first value and the second value. In some examples, the value for the system load factor 174 may linearly increase from the lower threshold 173 to the upper threshold 171.
In some examples, the system load unit 172 may compute a conversation size factor 176 based on the size 170 of the conversation graph 126. The size 170 is determined based on how many messages the conversation graph 126 includes. The conversation size factor 176 may be a value within a range of values. In some examples, the conversation size factor 176 may be a first value (e.g., zero), a second value (e.g., one), or one of a series of values between the first value and the second value. In some examples, the system load unit 172 may compare the size 170 to an upper threshold 175 and/or a lower threshold 177 to compute the conversation size factor 176.
In some examples, if the size 170 is less than or equal to the lower threshold 177, the system load unit 172 may determine the conversation size factor 176 as the first value (e.g., zero). In some examples, if the size 170 is equal to or greater than the upper threshold 175, the system load unit 172 may determine the conversation size factor 176 as the second value (e.g., one). In some examples, if the size 170 is between the lower threshold 177 and the upper threshold 175, the system load unit 172 may compute the value of the conversation size factor 176 as being a value between the first value and the second value. In some examples, the value of the conversation size factor 176 may increase (e.g., linearly increase) from the lower threshold 177 to the upper threshold 175. In some examples, when the size 170 is between the lower threshold 177 and the upper threshold 175, the system load unit 172 may calculate the conversation size factor 176 as (conversation size - lower threshold) / (lower threshold - upper threshold).
The system load unit 172 may compute a pruning factor 178 based on the system load factor 174 and the conversation size factor 176. In some examples, the pruning factor 178 may be computed by using the system load factor 174 and the conversation size factor 176 in a ratio, a scoring algorithm (e.g., weighted scoring algorithm), or other function that computes a value using the system load factor 174 and the conversation size factor 176. The pruning factor 178 may determine the level (or amount) of pruning applied to the conversation graph 126 or the number of messages included within the candidate subset 112. In some examples, the pruning factor 178 includes a percentage of the conversation graph 126. In some examples, the pruning factor 178 includes a percentage of messages to be pruned from the conversation graph 126, where the remaining messages are the messages included in the candidate subset 112. In some examples, the pruning factor 178 includes a percentage of messages to be included within the conversation graph 126. In some examples, the pruning factor 178 includes a value within a range of ranges (e.g., from a lower bound to an upper bound), where each value is associated with a percentage of messages to be pruned or included in the candidate subset 112. If the pruning factor 178 is closer to the lower bound, a lower percentage of messages are pruned. If the pruning factor 178 is closer to the upper bound, a higher percentage of messages are pruned.
In some examples, the system load unit 172 may compute the pruning factor 178 based on the system load factor 174, the conversation size factor 176, and an adjusted intercept value. The adjusted intercept value may be computed based on the lower bound, the upper bound, and the system load factor 174 (e.g., adjusted intercept value = lower bound + system load factor 174 * (upper bound - lower bound)). In some examples, the pruning factor 178 = adjusted intercept + (1 - adjusted intercept) * conversation size factor 176.
The light ranking manager 110 may obtain the pruning factor 178 and select messages from the ranked list 182 according to the pruning factor 178. For example, if the pruning factor 178 indicates that 37% of messages are to be pruned, the message selector 180 may remove the bottom 37% of messages from the ranked list and identify the top 63% of messages from the ranked list 182 as the candidate subset 112. In this manner, messages having a higher quality are selected for heavier ranking while balancing the load on the system.
In some examples, the message selector 180 selects the messages for the candidate subset 112 using the scores from the first level ranking. In some examples, the message selector 180 may select a message having the highest score (e.g., highest rank) from a candidate list. The candidate list first includes the direct replies to the focal message (e.g., all the direct replies to the focal message) along with their scores assigned from the first level ranking. The message selector 180 may select the highest scoring message to be included in the candidate subset 112 and may add any replies to the selected message in the candidate list. This process continues until the candidate subset 112 has a number of messages that satisfy the pruning factor 178. For example, if the conversation graph 126 has one hundred messages and the pruning rate is 30%, the process continues until the candidate subset has seventy messages. This methodology may ensure that the conversation graph 126 is connected after the pruning step and no message is served without their parent message.
Referring to
In response to the prediction manager 114 receiving the candidate subset 112, the prediction manager 114 may obtain the signals 118 relating to the messages of the candidate subset 112 from one or more data services 166. The signals 118 may include signals generated by the messaging platform 104 and/or generated by the client application 154 that relate to predicting user outcomes for displaying messages on the client application 154. For example, the signals 118 may include signals generated by the client application 154 based on the user’s interaction with the client application 154. The signals generated by the client application 154 may be transmitted to the messaging platform 104 for storage thereon.
The signals generated by the client application 154 may include signals representing engagement information such as positive user engagements with messages (e.g., favoritizing, likes, re-sharing), and/or negative user engagements with the messages (e.g., the reporting of abusive content). In some examples, the signals 118 may include signals generated by the messaging platform 104. In some examples, the signals generated by the messaging platform 104 may include signals representing data generated from the user’s connection graph 134, data generated from the conversation graph 126, data generated from user behavior on the platform (e.g., the number of times a user has engagement with messages, etc.), and/or data generated from the content of the messages such as the result of a semantic analysis that predicts user sentiment or the result of a topical analysis that determines a topic of one or more messages.
As shown in
The data structure-related signals 101 may include signals related to data from the conversation graph 126. In some examples, the data structure-related signals 101 may include signals representing the number of nodes 128, the number of edges 130, the number of branches 132, the length or size of each branch 132, the number of parent nodes, the number of children nodes, the number of leaf nodes, the height of the conversation graph 126 (e.g., the length of the longest path to a leaf node), and/or the depth of a node (e.g., the depth of a node is the length of the path to the root node). In some examples, the data structure-related signals 101 include one or more signals representing the number of unique authors in the conversation graph 126 or a subset of the conversation graph 126 such as a branch 132. In some examples, the data structure-related signals 101 include signals representing a location of a message having a certain type of data (e.g., an image, video, a link to video, etc.) within the conversation graph 126. In some examples, with respect to a particular message within the conversation graph 126, the data structure-related signals 101 may include signals representing whether the message is a child node, whether the message is a parent node, whether the message is a leaf node, the location of the message within the conversation graph 126, the location of a branch 132 that includes the message, the size of the branch 132 that includes the message, the depth of the message within the conversation graph 126.
The data structure-related signals 101 may include branch contextual features. In some examples, the data structure-related signals 101 include signals representing the number of replies within a branch 132, the number of conversations within a branch 132, the number of conversations within a branch 132 between the user of the client application 154 and an author of the root message, the number of conversation within a branch 132 between the user of the application 154 and a user mentioned in a new message, and/or the number of conversations between a specific node (e.g., a focal message) and a leaf node. In some examples, with respect to branch contextual features, a conversation may be defined as a back and forth between at least two users. In some examples, a conversation may be defined as a message posted by user A, a reply posted by user B, and then a reply posted by user A.
In some examples, the conversation graph manager 136 may receive the conversation identifier from the prediction manager 114, and then derive or determine the data structure-related signals 101 from the conversation graph 126 according to the conversation identifier and may store the data structure-related signals 101 in a data storage on the messaging platform 104. In some examples, in response to the conversation view request 121, the prediction manager 114 may control the conversation graph manager 136 to derive or determine the data structure-related signals 101 and then receive the data structure-related signals 101 from the conversation graph manager 136 to be used with the predictive models 117 to determine the predictive outcomes 125. In some examples, the prediction manager 114 may derive or determine the data structure-related signals 101 from the conversation graph 126. In some examples, in response to the conversation view request 121, the prediction manager 114 may transmit the conversation identifier to the conversation graph manager 136, and then receive the conversation graph 126 to derive or determine the data structure-related signals 101 from the conversation graph 126.
The health-related signals 103 may include signals that represent the health of presenting a message of the conversation graph 126 to the user of the client application 154. In some examples, the health-related signals 103 may include signals representing whether the user of the client application 154 has restricted (e.g., blocked, muted, etc.) an author of a message in the conversation graph 126 in the past. The health-related signals 103 may be stored in a data storage on the messaging platform 104. In some examples, the prediction manager 114 may transmit a request to a data service 166 (e.g., a health data service) to obtain the health-related signals 103, where the request may include the message identifiers of the messages of the conversation graph 126 and/or the user identifier of the user of the client application 154.
The engagement signals 105 may represent user engagement data associated with the messages of the conversation graph 126. In some examples, the engagement signals 105 include signals representing the number of engagements (e.g., number of times the messages has been favoritized or liked, the number or replies to the message, the number of times the message has been re-shared) with respect to a message of the conversation graph 126. In some examples, the engagement signals 105 include one or more signals representing the engagements of users that follow the user of the client application 154 in the user’s connection graph 134 (e.g., whether the message has one or more engagements provided by users that follow the user of the client application 154 in the user’s connection graph 134). In some examples, the prediction manager 114 obtains the engagement signals 105 from a data service 166 that stores the engagement data. In some examples, the prediction manager 114 may transmit a request that may include the message identifiers of the conversation graph 126, and the prediction manager 114 may receive the engagement signals 105 from the data service 166.
The social graph signals 107 may include signals representing information from the connection graph 134. In some examples, the social graph signals 107 includes signals representing the number of times that the user of the client application 154 has favoritized or liked messages of an author of a message over a period of time, whether the user is linked to the author of a message in the connection graph 134, and/or the number of times that the user has re-shared or replied messages of an author of a message over a period of time. In some examples, the prediction manager 114 obtains the social graph signals 107 from a data service 166 that stores the social graph signals. In some examples, the prediction manager 114 may transmit a request that may include a user identifier of the user of the client application 154, and the prediction manager 114 may receive the social graph signals 107 from the data service 166.
The historical aggregate signals 109 may include signals representing a user behavior on the messaging platform 104. In some examples, the historical aggregate signals 109 may include signals representing the number of times the user of the client application 154 has favoritized messages on the messaging platform 104 during a period of time, the number of times the user of the client application 154 has re-shared messages on the messaging platform 104 during a period of time, and/or the number of times the user of the client application 154 has replied to messages on the messaging platform 104 during a period of time. The period of time may be within the last day, last month, or last year, etc. In some examples, the historical aggregate signals 109 may include signals representing the number of times the user of the client application 154 has favoritized, liked, re-shared, and/or replied to messages that include an image or video.
In some examples, the historical aggregate signals 109 may include signals representing the number of times that the user of the client application 154 has favoritized, liked, re-shared, and/or replied to messages that are from accounts 141 linked to the user in the connection graph 134, and/or the number of times that the user has favoritized, liked, re-shared, and/or replied to messages that are from accounts 141 not linked to the user in the connection graph 134. In some examples, the prediction manager 114 obtains the historical aggregate signals 109 from data storage on the messaging platform 104. In some examples, the prediction manager 114 transmits a request to a data service 166 to obtain the historical aggregate signals 109. In some examples, the request includes a user identifier of the user of the client application 154. In some examples, the historical aggregate signals 109 includes batch aggregate information and real-time aggregate information. The batch aggregate information may include a relatively long history (e.g., greater than 50 days). In some examples, the batch aggregate information may not include interaction from the last day (or last few days). The real-time aggregate information may include relatively recent interaction history (e.g., within the last 30 minutes or so).
The content-related signals 111 may include signals representing one or more aspects of the contents of a message of the conversation graph 126. In some examples, the content-related signals 111 may include signals representing the length of the message, and/or whether the content includes text, video, or image. In some examples, the prediction manager 114 obtains the content-related signals 111 from data storage on the messaging platform 104. In some examples, the prediction manager 114 transmits a request to a data service 166 to obtain the content-related signals 111. In some examples, the request includes message identifiers of the messages of the conversation graph 126.
The similarity signals 113 may include one or more signals representing how similar a message is to other messages that the user has favoritized or liked. For example, the similarity signals 113 may represent a level of similarity between a particular message and one or more other messages that the user has favoritized or liked, and if the level of similarity is relatively high, it may provide an indication of a potential positive engagement. In some examples, the similarity signals 113 may include one or more signals representing how similar the user is to other users that have engaged with the message. For example, if a user profile of the user is determined as relatively similar to user profiles that have engaged with the message, it may provide an indication of a potential positive engagement. In some examples, the prediction manager 114 may obtain the similarity signals 113 from data storage on the messaging platform 104. In some examples, the prediction manager 114 may transmit a request to a data service 166 to obtain the similarity signals 113. In some examples, the request may include message identifiers and/or the user identifier of the user.
In some examples, technical difficulties or hurdles exist in order to obtain at least some of the signals 118 used for the prediction (e.g., especially for signals related to viewer-author relationships whenever a message goes viral). Popular messages may have a relatively large number of responses (e.g., in some cases, more than 80K). This also means that many users may try and view the popular message at the same time. For each viewer, the messaging platform 104 may obtain their relationship with all the authors that have replied to the popular message. Using the techniques described above, the messaging platform 104 may be able to filter the total number of messages from 80K to 4K, which may still mean that there can be 4K viewer author pairs for which to obtain relationship signals.
Also, in some examples, the viewer-author relationship may not even exist because the viewer would not be following the author. To handle these types of situations, instead of querying by viewer-author as a key to a data service 166, the messaging platform 104 can query by the viewer identifier and get their relationships with all other authors at once. Then, the messaging platform 104 can determine if any authors overlap with the authors of the replies and keep the signals where relevant. This reduces over the network calls by a relatively large magnitude as instead of making 4K calls per viewer, the prediction manager 114 may generate and send one call.
Another technical difficulty may exist for message-level signals. For example, for large conversations, the messaging platform 104 may query other data services 166 with 4K queries for each viewer. This could lead to “hot-key” problems where the data service 166 receives too many queries for the same message identifier. To overcome the above-identified difficulty, the messaging platform 104 may use in-memory caching. The service would cache the features in memory if the underlying data service 166 indicates a hot-key. For example, a message T goes viral and has responses R1,R2...R4000, and the message feature is the number of characters in the message. Then, 1000 users send requests for the same message simultaneously (or around the same time). If the data service 166 indicates a hot-key, the messaging platform 104 can store the character value for R1,R2..R4000 each in memory for a very short duration and just use them instead of calling the data service 166 for each user.
The prediction manager 114 includes an engagement predictor 115 configured to determine one or more predictive outcomes 125 of each message of the candidate subset 112 using the signals 118. In some examples, the engagement predictor 115 inputs the signals 118 to one or more predictive models 117 to compute the predictive outcomes 125.
The predictive models 117 are predictive models trained by one or more machine learning algorithms inputted with training data. The machine learning algorithms may include one or more of Markov models, logistic regression, decision tree analysis, random forest analysis, neural nets, and combinations thereof. Generally, machine learning is the field where a computer learns to perform classes of tasks using the feedback generated from experience or data that the machine learning process acquires during computer performance of those tasks. In supervised machine learning, the computer can learn one or more rules or functions to map between example inputs and desired outputs as predetermined by an operator or programmer. Labeled data points can then be used in training the computer. Unsupervised machine learning can involve using unlabeled data, and the computer can then identify implicit relationships in the data, for example by reducing the dimensionality of the data set.
The predictive models 117 may one predictive model 117 or multiple predictive modes 117 such as a positive engagement model, a negative engagement model, and a reciprocal engagement model. The predictive model(s) 117 may compute the positive engagement probability 127, the negative engagement probability 129, and the reciprocal engagement probability 131. For example, in response to the conversation view request 121 (e.g., the user selecting message B), the engagement predictor 115 may obtain the signals 118 relating to the messages of the candidate subset 112 and apply the signals 118 (which also includes the user identifier and the message identifier) to the predictive models 117 to determine the positive engagement probability 127, the negative engagement probability 129, and/or the reciprocal engagement probability 131, respectively.
The positive engagement probability 127 indicates a probability value that the user is predicted to positively view or engage with the message. In some examples, the probability value for the positive engagement probability 127 is a number (x) between a first value and a second value, where the first value represents a zero chance that the user is predicted to positively view or engage with the message, and the second value represents a 100% chance that the user is predicted to positively view or engage with the message. In some examples, the probability value for the positive engagement probability 127 is a positive number. In some examples, the first value is zero and the second value is one. However, the values for the first value and the second value may define any type of range (e.g., 0 to 1, 0 to 50, 0 to 100, etc.). In other words, the positive engagement probability 127 indicates a level of likeliness that the user is predicted to favoritize, like, or share the message.
The negative engagement probability 129 indicates a probability value that the user is predicted to negatively view or engage with the message. In some examples, the probability value for the negative engagement probability 129 is a number (y) between a first value and a second value, where the first value represents a zero chance that the user is predicted to negatively view or engage with the message, and the second value represents a 100% chance that the user is predicted to negatively view or engage with the message. In some examples, the probability value for the negative engagement probability 129 is a negative number. In some examples, the first value is zero and the second value is negative one. However, the values for the first value and the second value may define any type of range (e.g., 0 to -1, 0 to -50, 0 to -100, etc.). In some examples, the negative engagement probability 129 indicates a level of likeliness that the user is predicted to block the author of the message, unfollow the author of the message, and/or report the message as abusive.
The reciprocal engagement probability 131 indicates a probability value that the user is predicted to continue to develop the conversation graph 126. In some examples, the probability value for the reciprocal engagement probability 131 is a number (z) between a first value and a second value, where the first value represents a zero chance that the user is predicted to continue to develop the conversation graph 126, and the second value represents a 100% chance that the user is predicted to continue to develop the conversation graph 126. In some examples, the probability value for the reciprocal engagement probability 131 is a positive number. In some examples, the first value is zero and the second value is one. However, the values for the first value and the second value may define any type of range (e.g., 0 to 1, 0 to 50, 0 to 100, etc.). In some examples, the reciprocal engagement probability 131 indicates a level of likeliness that the user is predicted to reply to the message, thereby further developing the conversation graph 126.
The prediction manager 114 includes an engagement scorer 119 computes the engagement values 123 for the messages in the candidate subset 112 using the predictive outcomes 125. The engagement value 123 may provide an overall engagement value for a respective message, which incentivizes more healthy conversations on the messaging platform 104. For example, with respect to a particular message of the candidate subset 112, the engagement scorer 119 may combine the positive engagement probability 127, the negative engagement probability 129, and the reciprocal engagement probability 131 to generate an engagement value 123, which can be used to select the most relevant nodes 128 for the user. For example, the engagement scorer 119 may combine the values of the predictive outcomes 125 to determine the engagement value 123 for a particular message. If the probability value of the negative engagement probability 129 is relatively high (e.g., having a greater negative value), this value may offset the positive values of the positive engagement probability 127 and the reciprocal engagement probability 131. In a simple example, if the positive engagement probability 127 is +10, the negative engagement probability 129 is -10, and the reciprocal engagement probability 131 is +10, the engagement value 123 for the message is +10.
In some examples, the engagement scorer 119 may apply weights with the predictive outcomes 125, and then compute the engagement value 123 based on the weighted positive engagement probability 127 the negative engagement probability 129, and the reciprocal engagement probability 131. In some examples, the weight applied to the reciprocal engagement probability 131 is greater than the weight applied to the negative engagement probability 129.
The engagement values 123 are used to select relevant messages or branches of messages within the conversation graph 126 to be rendered to the user. For example, the timeline manager 142 receives the engagement values 123 from the prediction manager 114 and uses the engagement values 123 to rank the messages in the conversation graph 126 (e.g., from highest to lowest). The timeline manager 142 may provide, over the network 150, at least a subset of the messages of the ranked list 116 to be rendered on the timeline 156 according to the rank. In some examples, the timeline manager 142 provides only a subset of the ranked list 116 to be rendered on the timeline 156, where the subset includes the higher ranked messages of the conversation graph 126. Then, the timeline manager 142 may receive a request for additional messages of the conversation graph 126 from the client application 154 (e.g., selects a user affordance to view more messages of the conversation graph 126), and the timeline manager 142 may select the next group of messages from the candidate subset 112 to be transmitted to the client application 154. In this manner, the messaging system 100 may collapse parts of the conversation graph 126 that are less likely to provide a positive engagement, but then surface those messages when requested by the user.
In some examples, the timeline manager 142 selects one or more branches 132 (or a subset of a branch 132) of the conversation graph 126 to be rendered on the timeline 156 using the engagement values 123. For example, if a branch 132 includes one or more nodes 128 having high engagement values 123 (or engagement values 123 over a threshold level), the timeline manager 142 may select the entire branch 132 to be rendered as part of the messages delivered to the client application 154 despite the fact that the branch 132 may include one or more nodes 128 having low engagement values 123 (or engagement values 123 below a threshold level) in order to provide the user more context about the conversation. In some examples, a particular branch 132 is associated with an overall engagement value which may be the average of the engagement values 123 for the nodes 128 within the particular branch 132. Then, the timeline manager 142 may rank the branches 132 according to their overall engagement values.
In some examples, the timeline manager 142 selects messages from the candidate subset 112 having high engagement values (or engagement values 123 over a threshold level) for inclusion in the set of messages provided to the client application 154. In some examples, the timeline manager 142 ranks the selected branches 132 and/or the messages of the candidate subset 112 according to highest to lowest engagement values 123 (e.g., where the branches 132 or the messages having the highest engagement values 123 are presented to the user first).
In some examples, the ranked list 116 represents a subset of the messages of the conversation graph 126 that are determined as relevant to the user. For example, some messages of the conversation graph 126 may be relevant to a first user while other messages of the conversation graph 126 may be relevant to a second user. In contrast, some conventional approaches use a voting-based mechanism that may provide the same view for each. In further detail, the engagement predictor 115 may obtain the signals 118 (e.g., engagement history, connection graph data, etc.) that are related to the first user and obtain the predictive outcomes 125 for each message in the candidate subset 112, which are then used to compute the engagement values 123. The timeline manager 142 may receive the engagement values 123 from the prediction manager 114, and then rank the messages of the candidate subset 112 using the engagement values 123.
However, with respect to the second user, the engagement predictor 115 may obtain the signals 118 related to the second user, obtain the predictive outcomes 125 that are tailored to the second user, which are then used to compute the engagement values 123. Then, the timeline manager 142 may rank the messages in the candidate subset 112 using the engagement values 123. As such, the messages of the ranked list 116 that are displayed on the client application 154 for the second user may be different from the messages of the ranked list 116 that are displayed on the client application 154 for the first user.
Using the neural network 219 to obtain the predictive outcome(s) 225 may involve applying weighted and biased numeric input to interconnected nodes 260 in the neural network 219 and computing their output. The weights and bias applied to each node 260 in the neural network 219 may be obtained by training the neural network 219 using, for example, machine learning algorithms. The nodes 260 in the neural network 219 may be organized in two or more layers including at least the input layer 262 and the output layer 266. For a multi-layered neural network 219, the output from one layer may serve as input to the next layer. The layers with no external output connections may be referred to as the hidden layers 264. The output of each node 260 is a function of the weighted sum of its inputs plus a bias.
To obtain the predictive outcome(s) 225, a vector of feature values (X1...XN) is applied as the input to each node 260 in the input layer 262. In some examples, the vector of feature values (X1...XN) includes the values of the signals 118 explained above. The input layer 262 distributes the values to each of the nodes 260 in the hidden layer 264. Arriving at a node 260 in the hidden layer 264, the value from each input node is multiplied by a weight, and the resulting weighted values are summed together and added to a weighted bias value producing a combined value. The combined value is passed through a transfer or activation function, which outputs a value. Next, the outputs from the hidden layer 264 are distributed to the node 260 in the output layer 266 of the neural network 219. Arriving at a node 260 in the output layer 266, the value from each hidden layer node is multiplied by a weight, and the resulting weighted values are summed together and added to a weighted bias value to produce a combined value. The combined value is passed through the transfer or activation function, which outputs Y1 (e.g., the predictive outcome(s) 225).
Operation 302 includes receiving, over a network 150, a conversation view request 121 to retrieve messages from a conversation graph 126 stored on the messaging platform 104. Operation 304 includes obtaining a system load metric 167 associated with the messaging platform 104. Operation 306 includes computing a pruning factor 178 based on the system load metric 167. Operation 308 includes pruning the conversation graph 126 according to the pruning factor 178 to obtain a candidate subset 112 of messages. Operation 310 includes ranking the candidate subset 112 of messages to form a ranked list 116 of messages. Operation 312 includes transmitting, over the network 150, information to render at least a portion of the ranked list 116 on a client application 154.
In the above description, numerous details are set forth. It will be apparent, however, to one of ordinary skill in the art having the benefit of this disclosure, that implementations of the disclosure may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the description.
Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as “identifying,” “determining,” “calculating,” “updating,” “transmitting,” “receiving,” “generating,” “changing,” or the like, refer to the actions and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (e.g., electronic) quantities within the computer system’s registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
Implementations of the disclosure also relate to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may include a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a non-transitory computer readable storage medium, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, flash memory, or any type of media suitable for storing electronic instructions.
The words “example” or “exemplary” are used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the words “example” or “exemplary” is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X includes A or B” is intended to mean any of the natural inclusive permutations. That is, if X includes A; X includes B; or X includes both A and B, then “X includes A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Moreover, use of the term “an implementation” or “one embodiment” or “an implementation” or “one implementation” throughout is not intended to mean the same embodiment or implementation unless described as such. Furthermore, the terms “first,” “second,” “third,” “fourth,” etc. as used herein are meant as labels to distinguish among different elements and may not necessarily have an ordinal meaning according to their numerical designation.
The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present disclosure is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the disclosure as described herein.
The above description sets forth numerous specific details such as examples of specific systems, components, methods and so forth, in order to provide a good understanding of several implementations of the present disclosure. It will be apparent to one skilled in the art, however, that at least some implementations of the present disclosure may be practiced without these specific details. In other instances, well-known components or methods are not described in detail or are presented in simple block diagram format in order to avoid unnecessarily obscuring the present disclosure. Thus, the specific details set forth above are merely examples. Particular implementations may vary from these example details and still be contemplated to be within the scope of the present disclosure.
This application claims priority to U.S. Provisional Application No. 63/267,780, filed on Feb. 9, 2022, and to U.S. Provisional Application No. 63/362,556, filed on Apr. 6, 2022, the disclosures of which are incorporated by reference herein in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63267780 | Feb 2022 | US | |
| 63362556 | Apr 2022 | US |
