Patent Application
20200287860
This specification relates to social messaging platforms, and in particular, to providing event-specific media content to one or more users of the social messaging platform.
Conventional social messaging platforms allow users to maintain social networking profiles and build connections with other users. Social messaging platforms include common features that allow users to post messages, view messages, or comment on messages.
This specification describes technologies for composing messages associated with media content and providing those messages to one or more users of a social messaging platform. When a user of a social messaging platform composes a message to be sent to the platform using a mobile device, the social messaging platform can determine a location of the mobile device. Using the location of the mobile device, the social messaging platform can determine one or more topics corresponding to events that are occurring in the proximity of the location. If the user's message relates to a nearby event, e.g., includes text or media that describes the event, then the system can suggest one or more topics that correspond to the event for inclusion. Other users of the social messaging platform can search for content related to corresponding events by topic. In some implementations, the message can further include information that identifies a third-party to which the authoring account of the message is affiliated. This information allows a user of the platform to verify the authenticity of the authoring account, and therefore the authenticity of the corresponding message.
In general, one innovative aspect of the subject matter described in this specification can be embodied in methods that include the actions of receiving, by a social messaging platform, an indication of a message by a user of client software on a first user device; receiving, from the first user device, a first location of the first user device; providing, to the first user device, one or more topics that are specific to an event temporally associated with the first location; receiving, the message for posting on the social messaging platform, the message including (i) a topic selected from the one or more topics, and (ii) user selected media content; and adding the message to one or more streams of the social messaging platform.
Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods. For a system of one or more computers to be configured to perform particular operations or actions means that the system has installed on it software, firmware, hardware, or a combination of them that in operation cause the system to perform the operations or actions. For one or more computer programs to be configured to perform particular operations or actions means that the one or more programs include instructions that, when executed by data processing apparatus, cause the apparatus to perform the operations or actions.
The foregoing and other embodiments can each optionally include one or more of the following features, alone or in combination. In particular, one embodiment includes all the following features in combination. Providing, to the first user device, one or more topics based, on the first location includes: receiving, from a second user device, a second topic associated with a second location; determining that the first location is within a threshold distance from the second location; and providing, to the first user device, the second topic associated with the second location. Providing, to the first user device, a topic of the one or more topics based on the first location includes: receiving, from the first user device, text related to the event as part of the message composition; generating a topic using the text and the first location; and providing, to the first user device, the generated topic.
The method further includes determining a location confidence score for the received location, wherein determining the first location confidence score includes determining whether the location was identified by user input or obtained directly from the user device, and wherein locations obtained directly from the user device have a greater confidence than locations identified by the user input; and determining whether to add the message to one or more streams based on the first location confidence score. The method further includes determining a content confidence score for the media content, wherein determining the content confidence score includes determining whether the media content is captured using an application associated with the social messaging platform; and determining whether to add the message to one or more streams based on the content confidence score.
The method further includes generating map data that identifies locations associated with one or more topics; and providing the map data for display on a user device. The method further includes in response to a request from a receiving user, retrieving stream content that includes the message; and providing the stream content for presentation, wherein the presentation includes the media content and a first overlay to the media content that provides one or more of a profile picture of the user, a name of the user, or a username of the user. The message presentation further includes a second overlay to the media content that presents one or more of text describing the media content, text identifying the first location, or text identifying a time that the message was posted by the user. The method further includes determining that the user is affiliated with a particular third-party organization; adding an overlay to the media content that identifies the third-party organization; in response to a request from a particular user device associated with a receiving user, retrieving stream content that includes the message and the overlay; and providing the stream content to the particular user device for presentation.
The subject matter described in this specification can be implemented in particular embodiments so as to realize one or more of the following advantages. The social messaging platform facilitates the dissemination of events as they occur. A user can construct, on the social messaging platform, a message that includes media content specific to a certain event. The user can post the media content as an event is occurring to allow other users to experience primary source information related to the event. The social messaging platform can also verify the location of the user, to provide confidence that the location in which the user captured the media content corresponds to the actual location in which the event is occurring. The social messaging platform can associate the media content with affiliated parties to provide further confidence in the source of the media content.
Like reference numbers and designations in the various drawings indicate like elements.
An online social messaging platform (“platform”) and user devices can interact over one or more data communication networks. The social messaging platform is implemented on one or more computers in one or more locations that operate as one or more servers that support connections over wired or wireless networks from many different kinds of user devices. The platform may have many millions of accounts, and anywhere from hundreds of thousands to millions of connections may be established or be in use between clients and the platform at any given moment.
The platform facilitates real-time communication. The platform and client software are configured to enable users to use the platform to post messages to the platform and to use the platform to receive messages posted by other users. In some implementations, the platform provides facilities for users to send messages directly to one or more other users of the platform, allowing the sender and recipients to maintain a private exchange of messages.
The platform is configured to provide content, generally messages, to a user in a message stream. The messages will generally be messages from accounts the user is following, meaning that the recipient has registered to receive messages posted by the followed account, and optionally content that such accounts have engaged with, e.g., endorsed. In some implementations, the platform is configured to include in a recipient user's message stream other messages that the platform determines are likely to be of interest to the recipient, e.g., messages on topics of particular current interest, as represented by the number of messages posted on the topics by users of the platform, or messages posted on the topics of apparent interest to the recipient, as represented by messages the recipient has posted or engaged with, as well as selected advertisements, public service announcements, promoted content, or the like.
The platform is configured to enable users to exchange messages in real-time, i.e., with a minimal delay. The platform is also configured to enable users to respond to messages posted earlier, on the order of hours or days or even longer. The platform is configured to display posted messages to one or more other users within a short time frame so as to facilitate what can essentially be a live conversation between the users.
Thus, the basic messaging functionality of the platform includes at least posting new messages, providing message streams for accounts in response to requests from corresponding users, managing accounts, managing connections between accounts, messages, and streams, and receiving engagement data from user accounts engaging with messages.
In some implementations of the platform, a message contains data representing content provided by the author of the message. The message may be a container data type storing the content data. The types of data that may be stored in a message include text, graphics, images, video, and computer code, e.g., uniform resource locators (URLs), for example. Messages can also include key phrases, e.g., hashtags that can aid in categorizing or relating messages to topics. Messages can also include metadata that may or may not be editable by the composing account holder, depending on the implementation. Examples of message metadata include a time and date of authorship and a geographical location of the user device when it submitted the message. In some implementations, what metadata is provided to the platform by a user device is determined by privacy settings controlled by the user or the account holder.
Messages composed by one account holder may reference other accounts, other messages, or both. For example, a message may be composed in reply to another message composed by another account holder. A message may also be composed by a user in reply to a message originally posted by the user. Messages may also be reposts of a message composed by and received from another account holder.
In some implementations, messages are microblog posts, which differ from e-mail messages, for example, in that an author of a microblog post does not necessarily need to specify, or even know, who the recipients of the message will be.
A stream is a stream of messages on the platform that meet one or more stream criteria. A stream can be defined by the stream criteria to include messages posted by one or more accounts. For example, the contents of a stream for a requesting account holder may include one or more of (i) messages composed by that account holder, (ii) messages composed by the other account holders that the requested account holder follows, (iii) messages authored by other account holders that reference the requested account holder, or (iv) messages sponsored by third-parties for inclusion in the account holder's message stream. The messages of a stream may be ordered chronologically by time and date of authorship, or reverse chronologically. Streams may also be ordered in other ways, e.g., according to a computationally predicted relevance to the account holder, or according to some combination of time and relevance score.
A stream may potentially include a large number of messages. For both processing efficiency and the requesting account holder's viewing convenience, the platform generally identifies a subset of messages meeting the stream criteria to send to a requesting client once the stream is generated. The remainder of the messages in the stream are maintained in a stream repository and can be accessed upon client request.
In general, account holders have relationships with other account holders on the platform. Relationships between account holders of the platform are represented by connection data maintained by the platform, e.g., in the form of data representing one or more connection graphs. The connection data may be maintained in a connection repository. A connection graph includes nodes representing accounts of the platform and edges connecting the nodes according to the respective relationships between the entities represented by the nodes. A relationship may be any kind of association between account holders, e.g., a following, friending, subscribing, tracking, liking, tagging, or other relationship. The edges of the connection graph may be directed or undirected based on the type of relationship.
In some implementations, the platform tracks engagement with messages. In some implementations, the platform maintains, in a message repository, data that describes each message as well as the engagement data with each message.
Engagement data can include any type of information describing user activity related to a message by an engaging account of the platform. Examples of engagement by a user include, for example, reposting the message, marking the message to indicate it is a favorite of, liked by, or endorsed by the user, responding to the message, and mentioning or referencing the message. Engagement data may also include how many followers, connections, and/or friends of the context account have connections with the engaging account, e.g., are in a connection graph of the engaging account, or an indication that the context account is a favorite account of the engaging account.
A user may be an account holder of an account, or an authorized user of an account on the platform. The platform may have millions of accounts of individuals, businesses, or other entities, e.g., pseudonym accounts, novelty accounts, and so on.
Users can interact with the social messaging platform through their respective user devices. A user device can be any suitable Internet-connected device, e.g., a laptop or desktop computer, a smartphone, or an electronic tablet. The user device can be connected to the Internet through a mobile network, through an Internet service provider (ISP), or otherwise.
Each user device is configured with software, which will be referred to as a client or as client software, that in operation can access the platform so that a user can post and receive messages, view and curate the user's streams, and view and interact with lists of content items. On any particular user device, the client may be a web browser or an HTML (hypertext markup language) document rendered by a web browser. Or the client may be or include JavaScript code or Java code. Or the client may also be dedicated software, e.g., an installed app or installed application, designed to work specifically with the platform. Or the client may be or include a Short Messaging Service (SMS) interface, an instant messaging interface, an e-mail-based interface, or an API function-based interface, for example. Data, e.g., messages, sent to the social messaging platform by a user device is sent to the platform by the client software on the user device. Similarly, data, e.g., one or more messages from a stream associated with the user, received by the user device from the social messaging platform, is received by the client software on the user device.
The social messaging platform can allow users to post text to a large number of other users to disseminate current events. Because many individuals are used to viewing media content on social messaging platforms, allowing a user to broadcast media content related to current events can be more engaging for both the broadcasting user and the users that view the broadcasted media content. In addition, the social messaging platform that can verify that a user is indeed at a location where breaking news is occurring can facilitate the dissemination of news-related media content that other users can trust to be authentic primary-source content. This specification describes techniques for associating media content related to a current event with one or more topics that describe the event, to provide users with trustworthy event coverage.
In this specification the term “engine” is used broadly to refer to a software based system or subsystem that can perform one or more specific functions. Generally, an engine will be implemented as one or more software modules or components, installed on one or more computers in one or more locations. In some cases, one or more computers will be dedicated to a particular engine; in other cases, multiple engines can be installed and running on the same computer or computers.
Various components of the topic processing system 130 can be located on the same device, e.g., a server, mainframe, or other suitable computing device, or can be located on separate devices connected by a network, e.g., a local area network (LAN), or the Internet.
A user device, for example the first device 110 or second device 120, can capture media content related to an event while at a particular location. Captured media content can include, for example, a photo, a video, an audio recording, or a GIF (Graphics Interchange Format). An event can be any particular activity or occasion occurring at a given location and time locally or globally. For example an event can be a holiday or other special occasion, a sporting event, a concert, a festival, a conference, a march, a rally, or a protest. As another example, an event can be a local or global news event such as a traffic jam, a power outage, or a wildfire.
The topic database 132 can maintain a mapping of event location to topics. A topic can be a word or phrase that describes an event. The topic processing system 130 can populate the topic database 132 based on upcoming events. For example, the topic processing system 130 can access a website that lists the dates, times, and locations of upcoming events, and generate one or more topics based on the upcoming events. As another example, the topic processing system 130 can access one or more news outlets, determine current or upcoming events, e.g., by parsing online news content sources, and generate one or more topics based on the current or upcoming events. The topic processing system 130 can also populate the topic database 132 based on topics provided to the social messaging platform 100 by one or more users.
Apart from populating the topic database 132 by collecting topic information from various sources as described above, topics can be identified from content posted by users to the social messaging platform. For example, if several users include similar content in posts associated with a given location, it may indicate a trending topic associated with that location. In particular, users may tag particular text, for example, with a hashtag that indicates its importance. When a threshold number of users post the same or similar text, it can indicate an event occurring at that location. The topic processing system 130 can store these topics derived from user message posts in the topic database 132.
For example, if a user encounters a wildfire, the user can document the wildfire by taking a video. The user can associate the video with a topic such as the text “#SonomaWildfire”. In addition to associating the media content with a topic, the user can also send text that elaborates on the event to the topic processing system 130. For example, the text can be, “Beware: wildfire sighting near Highway 12 and Calistoga Road.”
A user device can send a device location, e.g., as identified by the user device from a global positioning system (GPS) or other location system, the media content, the topic, and the text to the social messaging platform 100. In some implementations, the social messaging platform 100 can use the topic processing system 130 to perform one or more actions to determine whether the topic provided by the device is accurate.
If the text provided by the user includes a location, the topic processing system 130 can verify that the location specified by the topic corresponds to the device location. The topic processing system 100 can verify the location to ensure that topics are accurate, making the system less susceptible to malicious users that may attempt to broadcast an event that they are not actually in proximity to.
The topic processing system 130 can also send the topic to the text analysis engine 136. The text analysis engine 136 can analyze the text and verify that the topic does not contain any misspelled words and, if the topic does contain one or more misspelled words, then the text analysis engine 136 can suggest possible correct spellings of the one or more misspelled words. After determining that the topic is accurate, the topic processing system 130 can store the topic in the topic database 132.
The text analysis engine 136 can also determine whether the text that elaborates on the event includes a location. If the text includes a location, the text analysis can verify that the location corresponds to the first location. For example, if the text reads, “Very windy here at Point Reyes!” the text analysis engine can detect that the text includes a user-specified location, i.e., Point Reyes, and determine whether the location associated with the user device is within a threshold proximity of the user-specified location.
The account database 142 can maintain various relationships between accounts of the messaging platform or between accounts of the social messaging platform and other third parties. For example, some accounts may be identified as affiliated with a particular entity account. Some message posts, as described in greater detail below, can include an indication of the affiliated entity based on the relationships identified in the account database 142.
The social messaging platform receives a message composition request (205). The message composition request can be an indication that the user wants to post a message. When a user launches a messaging function on a user interface of the social messaging platform, the user's device can also send an indication of a message composition to the social messaging platform.
The social messaging platform determines a first location associated with a first user device (210). After determining the first location, the first user device can communicate the first location to a topic processing system of the social messaging platform. The first user device can use a number of ways to determine a location. For example, the first user device can use GPS location information to determine the first location. The social messaging platform can obtain the GPS information from the first user device. For example, the user can compose a message using a mobile application for the social messaging platform installed on the first user device. This application can request access to the GPS information of the first user device, for example, using an appropriate application programming interface. Similarly, when composing a message using a web browser on the first user device, the social messaging platform may be able to request access, through the browser, to the GPS information.
In some implementations, when the social messaging platform determines a location using one or more methods, the platform calculates a confidence score to the location. The confidence score can reflect the degree to which the social messaging platform trusts the authenticity of the location. For example, if the social messaging platform determines a location using the GPS location information obtained directly from the user device, the confidence score that the social messaging platform assigns to the GPS location information can be higher than the confidence score assigned to a location identified from the user's composed message text.
The social messaging platform can use the calculated confidence scores to select which messages are most relevant to certain topics or events. For example, the social messaging platform can collect and provide a collection of messages about a particular topic or event to a broader audience of users of the social messaging platform, e.g., in response to a user search query. In another example, the social messaging platform can provide media content related to a topic or event to users of the social messaging platform, e.g., including users of the social messaging platform that do not have a relationship with one or more of the authors of the collection of messages, for example by adding the content to a stream associated with respective user account. The message can be retrieved and presented when one of the user accounts requests content from their message stream.
The selection of messages of the collection of messages about the topic to provide to a given user account can be based on filter criteria such as whether the messages have a confidence score that satisfies a threshold value. Thus, a particular message can be included if the confidence score for that message satisfies the threshold. As another example, the social messaging platform can display messages associated with the topic in order of the confidence scores. Following this example, if the social messaging platform displays media content in a list, the platform can display the media content associated with high confidence scores towards the beginning of the list and media content with low confidence scores towards the end of the list. In some implementations, the confidence scores can be one or multiple ranking criteria that are combined to determine a final selection and ordering of messages.
Returning to the message composition of
The platform can first determine whether there is a temporal association between the event and the location before determining topics based on the location to provide to the user device. A temporal association to an event indicates a time constraint between a location and an event occurring at the location. For example, an event is temporally associated with a location when the event is ongoing at the location, recently completed at the location, or occurring soon at the location.
For example, a concert that is occurring at a stadium represents an event, i.e., the concert, that is temporally associated with a location, i.e., the stadium. Accordingly, a user may want to view topics corresponding to the event that is occurring at the location. Likewise, a user at the location may post messages that include topics corresponding to the event.
By contrast, a concert that will occur at a stadium in the future or one that occurred at the stadium in the past may not be temporally associated with the stadium if the concert will not or has not occurred within a certain time range. This prevents an event from being incorrectly associated with a location with regard to determining one or more topics to provide to a user device.
For example, a stadium may host two separate concerts on two consecutive days, day 1 and day 2. Because the concerts are separate from each other, the social messaging platform recognizes each one as a separate event. Event 1 may be the concert occurring on day 1, while event 2 may be the concert occurring on day 2. Event 1 is temporally associated with the stadium during day 1. Event 2 is temporally associated with the stadium on day 2. Consequently, the temporal association is used to determine whether to suggest a topic for event 1 or event 2.
The components of the social messaging platform can use a number of methods to determine the one or more topics to provide.
In some implementations, the topic processing system determines the one or more topics based on a second location associated with a topic sent to the social messaging platform. Prior to determining the first location, the social messaging platform can receive, from a second user device, a topic associated with a second location. The social messaging platform can store the topic associated with the second location in a topic database. The topic processing system can then determine a threshold distance from the first location. The topic processing system can identify one or more topics associated with a location that satisfies the threshold distance from the first location. For example, the topic processing system can query the topic database to retrieve one or more topics that are within a threshold distance from the first location. As a result of querying the topic database, the topic processing system can retrieve a topic associated with a second location, which the topic processing system has determined is within the threshold distance from the first location. The topic processing system can then provide, to the first user device, the topic associated with the second location.
The threshold distance can be any distance that indicates two events are likely related by proximity. For example, the threshold distance can be an eighth of a mile, a quarter of a mile, a half a mile, or one mile. The threshold distance can be based on a coordinate distance or based on a relationship to a particular entity, e.g., within the same neighborhood, city, or region.
In the implementation described above, the topic processing system determines that media content captured at locations that satisfy the threshold distance relative to each other are likely to describe the same event; therefore, the topic processing system associates the media content with the same topic. For example, a first user can be at a first location, e.g., the first hole of a golf course for the Bay Area Golf Tour. Prior to receiving the first location, the topic processing system can also have received, from a second user at a second location, e.g., the parking lot of the Bay Area Golf Tour, media content that the second user associated with the topic “#BayAreaGolfTour”. The topic processing system can determine that the first location is within the threshold distance from the second location and that media content captured at the first location is likely to be associated with the topic “#BayAreaGolfTour” as well. In this way, the topic database can maintain a single topic for an event, regardless of whether the event is associated with multiple locations.
In some implementations, the topic processing system provides the one or more topics based on text related to a message. The text analysis engine 136 can process text related to a message and generate a topic based on the text. For example, in response to receiving the text “Hour long delay on the 101!” from a first user, the text analysis engine can generate a topic relevant to the text, e.g., “#TrafficJamOn101”, and add the generated topic to a topic database. The topic processing system can provide the generated topic to the first user device, so that the first user can associate the text with the generated topic. The topic processing system can also provide the generated topic to a second user based on text received from the second user, or the second user's proximity to the first user.
The social messaging platform receives, from the first user device, a topic selected from the one or more topics (220). The user selects a topic and sends the selection to the social messaging platform. Alternatively, the selected topic is sent to the social messaging platform with the completed message composition.
The social messaging platform receives, from the first user device, media content related to the first location (225). After capturing media content related to the first location, e.g., using the camera of the first user device, the user can also send the media content to the social messaging platform.
The media content related to the first location can be captured using a media application and hardware of the first user device, e.g., camera hardware and associated application software. For example, a mobile device can include an integrated camera that is configured to capture images or video content in response to user commands input to a user interface of the camera application. In some implementations, the camera hardware can be accessed by other applications of the user device, for example, an application associated with the social messaging platform. For example, as part of a message composition, a user may be able to select a command to capture media content to include in the message.
The social messaging platform can assign a confidence score to the media content based, for example, on the source of the media content. The confidence score can reflect the degree to which the social messaging platform trusts the authenticity of the media content. The social messaging platform can assign a high confidence score to media content captured using the user interface of the social messaging platform, and media content captured at the time and place of an event. A higher confidence score can indicate that the media content is more trustworthy than, for example, media content captured using the media application of the first user device independently from composition using the social messaging platform.
The social messaging platform posts the message including, at least, the topic and the media content (230). The social messaging platform can send the message to one or more other users depending on the message sharing settings of the first user.
The social messaging platform receives a selection of a first topic associated with a first location, wherein the first topic is specific to a first event that is associated with a first message (305). The selection can be received, for example, in response to a message composition, submitted by a user account, as described above with respect to
The social messaging platform receives a selection of a second topic associated with a second location, wherein the second topic is specific to a second event that is associated with a second message (310). The selection can be received, for example, in response to a message composition, submitted by a different user account, as described above with respect to
The social messaging platform determines that the first event is related to the second event (315). A topic processing engine of the social messaging platform can determine that the first event and the second event are related in a number of different ways, as described in the following example implementations.
In some implementations, the social messaging platform determines that the first event is related to the second event by first determining that the first location is within a threshold distance from the second location. That is, the social messaging platform can determine the first and second events are related by virtue of their proximity.
In some other implementations, the social messaging platform determines that the first and second events are related by analyzing text received from respective message compositions. The social messaging platform can receive text associated with the second message. For example, the text can be sent to the social messaging platform by a user. The social messaging platform can then determine that the text is related to the first topic. In this implementation, a text analysis engine can process the text to determine that the text is related to the first topic. For example, the first and second topics can be “#MusicFestDay1” and “#MusicFestDay2”, respectively, while the text associated with the second broadcast can be “So excited for day 2 of Music Fest!” Although the two topics are not identical, the text analysis engine can process the text associated with the second broadcast to determine that the text is related to the first topic, e.g., that the text is related to a continuation of Music Fest Day 1, and that both topics describe the same, or similar, event, namely Music Fest.
In another implementation, the social messaging platform determines that the first event is related to the second event by receiving, from a user device, an indication that the first topic is related to the second topic. If the user interacts with a topic, e.g., by tapping or clicking on the topic, the interface of the social messaging platform can present a dialog box that allows the user to provide related topics. For example, a user could construct a message that includes the topic “#MusicFestDay1”. The user can then provide the topic “#MusicFestDay2” as a related topic.
The social messaging platform provides for display on a user device content including one or more message posts that include the first topic, the second topic, or both topics (320). For example, the social messaging platform can provide the messages in response to a user search for content associated with the first or second topic. Because the first and second events are related, a user may want messages associated with the events to be displayed contiguously, regardless of whether the messages share the same topic. For example, a user may want to view messages related to Music Fest, regardless of whether those messages include the same topic.
A first user can choose an event and view messages related to the chosen event, including multiple topics related to the event. In some implementations, the set of messages related to the chosen event can include messages created by users that the first user does not have a relationship with.
In some implementations, the social messaging platform generates a user interface that presents a map that shows locations associated with one or more topics. The topic processing system can include a topic mapping engine that is configured to access the topic database to retrieve the locations that are present in the database. The topic mapping engine 134 can generate a map that includes the locations retrieved from the database along with one or more topics associated with each location. The social messaging platform can send the map to a user device, which can display the map on a user interface. In some implementations, a user can specify an event to the social messaging platform, which can then display the location of the event and topics associated with the event using the map. A user can interact with the map to view content specific to an event, e.g., messages or media content about the event.
In some implementations, additional information can be added to a message being composed. For example, a composing user can provide additional details about the video or image content that has been captured for inclusion in the message. Rather than appending this content as a separate text portion of the message, the system can overlay this information in a region of the media content similar to a television chyron. In some other implementations, other information identifying the source of the post is laid over the content, for example, an identifier of the composing user or an identifier of an entity or organization associated with the composing user.
Another user, referred to as a composing user, composed a message based on capturing a photo 402 or video to post to the social messaging platform, using techniques similar to those described above. Interface 400 shows a view that the viewing user of the user device sees when viewing the photo 402, which in this example shows the launch of a rocket.
Interface 400 includes additional overlay information. For example, the interface 400 includes a first overlay 404 that provides information about the composing user. The first overlay 404 includes a profile picture 404a, a name 404b, and a username 404c. The information about the composing user can be retrieved from a user profile of the composing user.
In addition to sending the photo 402 to the social messaging platform 100, the system can add text describing the photo and a location at which the photo was taken for presentation in a second overlay. In
In addition to displaying text 406a, location 406b, and timestamp 406c, the second overlay 406 also includes graphical control buttons that the viewing user can use to interact with the social messaging platform. The second overlay 406 includes a reply button 408, a rebroadcast button 410, a like button 412, and a direct message button 414.
Using the reply button 408, the viewing user can view replies related to the message. For example, the replies can include text and media uploaded by other users of the social messaging platform. In addition, the reply button 408 can also allow the viewing user to post their own reply to the message.
The repost button 410 allows the viewing user to repost the message including the photo 402, the text 406a, and the location 406b. That is, the viewing user can repost the complete message so that the message is provided to the message feed of other users of the social messaging platform that follow the viewing user.
The like button 412 allows the viewing user to like the message. In some implementations, liking the message increments a counter that tracks the total number of likes the message has received. A count 412a shows the viewing user the total number of likes the message has.
The direct message button 414 allows the viewing user to respond directly to the broadcaster of a message, e.g., the composing user.
Alternatively, or additionally, an interface can include other graphical control buttons for performing different operations, e.g., sharing a message or saving it as a bookmark for later viewing. As another example, an interface can include a button that allows a viewing user to email or text a message to members of the user's contacts.
Interface 400 can show one or more replies made to the composing user by a user of the social messaging platform. In the example of
In the example of
A third-party organization can have an account on the social messaging platform 100. When a composing user is affiliated with a third-party organization, the social messaging platform can determine the composing user's affiliation and display a graphic that indicates the determined affiliation. For example, the social messaging platform can access a third-party account database, e.g., the third-party account database 142 of
The third-party broadcaster sends a photo 502 to the social messaging platform. As illustrated by interface 500, the photo 502 relates to a weather report and shows an image of Hurricane Irma.
Similar to interface 400, interface 500 displays the photo 502 along with first overlay 504, which displays identification information of the third-party composing user, e.g., a profile picture 504a, a name 504b, and a username 504c. Interface 500 includes a second overlay 506, which displays text 506a, sent to the social messaging platform 100 by the third-party composing user. The text 506a describes the photo 502 and includes the topic “#Irma”. Second overlay 506 also includes a location 506b and a timestamp 506c. Also like interface 400, interface 500 includes the reply button 408, the rebroadcast button 410, the like button 412, and the message button 414.
Although interface 400 shows the reply box 418, interface 500 does not show a reply box, indicating that the neither the viewing user, nor any other user of the social messaging platform, has sent a reply to the third-party composing user. Because no user has a reply, interface 500 shows a reply bubble 518. Using the reply bubble 518, the viewing user can reply directly to the third-party composing user. The reply bubble 518 also includes media button 518a, which allows the viewing user to attach media, e.g., pictures or videos, to the reply.
As mentioned above, the composing user described with regard to interface 500 is affiliated with a third-party organization. In the example of
In some implementations, the overlay can show additional information based on a particular event. For example, when an interface is displaying text and media related to a sporting event, a chyron can show a score of the sporting event.
Therefore, the social messaging platform verifies the identity of the third-party composing user and provides the overlay 520 as an indication of the composing user's verified identity. This is advantageous for a user of the social messaging platform because the user is able to verify the authenticity of the message based on the verified identity of the third-party composing user.
Embodiments of the subject matter and the actions and operations described in this specification can be implemented in digital electronic circuitry, in tangibly-embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible non-transitory storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively, or in addition, the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer storage medium can be or be part of a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them. A computer storage medium is not a propagated signal.
The term “data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. Data processing apparatus can include special-purpose logic circuitry, e.g., an FPGA (field programmable gate array), an ASIC (application-specific integrated circuit), or a GPU (graphics processing unit). The apparatus can also include, in addition to hardware, code that creates an execution environment for computer programs, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
A computer program, which may also be referred to or described as a program, software, a software application, an app, a module, a software module, an engine, a script, or code, can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages; and it can be deployed in any form, including as a stand-alone program or as a module, component, engine, subroutine, or other unit suitable for executing in a computing environment, which environment may include one or more computers interconnected by a data communication network in one or more locations.
A computer program may, but need not, correspond to a file in a file system. A computer program can be stored in a portion of a file that holds other programs or data, e.g., one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files, e.g., files that store one or more modules, sub-programs, or portions of code.
The processes and logic flows described in this specification can be performed by one or more computers executing one or more computer programs to perform operations by operating on input data and generating output. The processes and logic flows can also be performed by special-purpose logic circuitry, e.g., an FPGA, an ASIC, or a GPU, or by a combination of special-purpose logic circuitry and one or more programmed computers.
Computers suitable for the execution of a computer program can be based on general or special-purpose microprocessors or both, or any other kind of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a central processing unit for executing instructions and one or more memory devices for storing instructions and data. The central processing unit and the memory can be supplemented by, or incorporated in, special-purpose logic circuitry.
Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to one or more mass storage devices. The mass storage devices can be, for example, magnetic, magneto-optical, or optical disks, or solid state drives. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device, e.g., a universal serial bus (USB) flash drive, to name just a few.
To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on, or configured to communicate with, a computer having a display device, e.g., a LCD (liquid crystal display) monitor, for displaying information to the user, and an input device by which the user can provide input to the computer, e.g., a keyboard and a pointing device, e.g., a mouse, a trackball or touchpad. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's device in response to requests received from the web browser, or by interacting with an app running on a user device, e.g., a smartphone or electronic tablet. Also, a computer can interact with a user by sending text messages or other forms of message to a personal device, e.g., a smartphone that is running a messaging application, and receiving responsive messages from the user in return.
Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface, a web browser, or an app through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server transmits data, e.g., an HTML page, to a user device, e.g., for purposes of displaying data to and receiving user input from a user interacting with the device, which acts as a client. Data generated at the user device, e.g., a result of the user interaction, can be received at the server from the device.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of what is disclosed or on the scope of what is being or may be claimed, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially be claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claim may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings and recited in the claims in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous.
