Monitoring user activity on messaging platform

Abstract

Methods and systems are disclosed for performing operations for monitoring user activity on a messaging platform. Operations include receiving, from a first client device, a request to access a group portal associated with a user group; in response to receiving the request, generating a first identifier of a first user in the user group for display in a first portion of the group portal; accessing activity information associated with the first user, the activity information describing one or more messages sent by a second client device of the first user to a group of recipients; and generating activity information associated with the first user, but excluding content of one or more messages sent by the second client device for display in a second portion of the group portal.

Description

[0001] Priority claim

[0002] This application claims the benefit of priority to U.S. patent application serial number 17 / 661,682, filed on May 2, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to messaging applications. Background Art

[0004] Messaging applications allow users to exchange messages with different friends. Messages can include text, audio, video, and augmented reality (AR) experiences. Users most often use this forum or medium to communicate due to the ease of use and the speed at which messages can be exchanged. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the accompanying drawings (which are not necessarily drawn to scale), similar reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the most significant digit or digits in a reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the accompanying drawings, in which:

[0006] Figure 1 is a pictorial representation of a networked environment in which the present disclosure may be deployed, according to some examples.

[0007] Figure 2 is a graphical representation of a messaging client application according to some examples.

[0008] Figure 3 is a graphical representation of data structures maintained in a database according to some examples.

[0009] Figure 4 is a graphical representation of the message according to some examples.

[0010] Figure 5 is a block diagram illustrating an example user activity monitoring system according to some examples.

[0011] Figures 6 to 8 is a graphical representation of output of a user activity monitoring system according to some examples.

[0012] Fig. 9 is a flow diagram illustrating example operation of a user activity monitoring system according to some examples.

[0013] Fig.10 is a diagrammatic representation of a machine in the form of a computer system according to some examples within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein.

[0014] Fig.11 is a block diagram illustrating a software architecture in which examples may be implemented. DETAILED DESCRIPTION

[0015] The following description includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative examples of the present disclosure. In the following description, for the purpose of illustration, many specific details are set forth to provide an understanding of various examples. However, it will be apparent to those skilled in the art that examples may be practiced without these specific details. Typically, it is not necessary to show in detail known instruction instances, protocols, structures, and techniques.

[0016] Users often communicate with each other through messaging applications. As messaging applications become more common or become the medium of choice for communication, the demographics of users will also change. That is, younger user groups are beginning to communicate with each other through messaging applications. Although such communications are generally considered safe, there are environments where younger user groups may not be aware of the dangers involved. Parents of such younger users are increasingly concerned about how their children communicate. However, there is currently no technology that balances the need to protect the privacy of the user or child while allowing parents to monitor their children's activities. Specifically, modern systems provide parents with the ability to obtain a complete view of their child's device to read the child's messages. Such an approach fails to protect the child's privacy and can be very invasive.

[0017] The disclosed technology aims to solve technical challenges and improve the efficiency of using electronic devices by providing a seamless and non-intrusive mechanism for monitoring the messaging activities of a group of users to a primary user (e.g., a parent viewing the messaging activities of their child). The disclosed technology limits the type of activity information presented to the primary user and avoids showing the actual content of the message. This keeps the privacy level of the user being monitored at a relatively safe and high level while providing the primary user with access to basic user activity information. In this way, the disclosed method allows the user being monitored to feel safer and more comfortable when sharing their messaging activities with their primary user (e.g., a parent). Specifically, the disclosed technology can provide an identifier to a primary user in only a subset of the recipients to whom the user being monitored has sent a message, but the content of such a message will not be displayed or presented to the primary user. The identifier of the set of recipients can include the recipient's avatar and / or name and the last time each of the messages was sent. This information may be valuable and critical for the primary user to keep the user being monitored safe. The messaging activity may also include a list of friends added by the first user within a threshold time period (e.g., recently added friends).

[0018] In particular, the disclosed technology receives a request from a first client device (e.g., of a primary user or parent) to access a group portal associated with a user group (e.g., a child or user being monitored). The disclosed technology generates a first identifier of a first user in the user group for display in a first portion of the group portal in response to receiving the request. The disclosed technology accesses activity information associated with the first user, the activity information representing one or more messages sent by a second client device of the first user to a set of recipients. The disclosed technology generates the activity information associated with the first user, but does not disclose the content of the one or more messages sent by the second client device, for display in a second portion of the group portal.

[0019] Therefore, a safer and more private messaging environment and platform can be provided to users of all ages, which improves the overall experience of users when using electronic devices.

[0020] Networked computing environment

[0021] Figure 1 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each of the multiple instances hosting a number of applications including a messaging client 104 and other external applications 109 (e.g., third-party applications). Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on corresponding other client devices 102), a messaging server system 108, and an external application server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with locally hosted third-party applications such as the external application 109 using an application programming interface (API).

[0022] The client device 102 can operate as a stand-alone device, or can be coupled (e.g., networked) to other machines. In a networked deployment, the client device 102 can operate as a server machine or a client machine in a server-client network environment, or operate as a peer machine in a peer-to-peer (or distributed) network environment. The client device 102 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web device, a network router, a network switch, a network bridge, or any machine capable of performing the disclosed operations. In addition, although only a single client device 102 is shown, the term "client device" should also be considered to include a collection of machines that perform the disclosed operations individually or jointly.

[0023] In some examples, client device 102 may include AR glasses or AR headsets, wherein virtual content is displayed within the lenses of the glasses while the user views the real world environment through the lenses. For example, an image may be presented on a transparent display, which allows the user to view content presented on the display and real-world objects simultaneously.

[0024] The messaging clients 104 are able to communicate and exchange data with other messaging clients 104 and messaging server systems 108 via the network 112. The data exchanged between the messaging clients 104 and between the messaging clients 104 and messaging server systems 108 include functions (e.g., commands to invoke functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0025] The messaging server system 108 provides server-side functionality to certain messaging clients 104 via the network 112. Although certain functions of the messaging system 100 are described herein as being performed by the messaging client 104 or by the messaging server system 108, the location of certain functions within the messaging client 104 or within the messaging server system 108 may be a design choice. For example, it may be technically preferred to initially deploy certain technologies and functions within the messaging server system 108, but later migrate the technologies and functions to the messaging client 104 where the client device 102 has sufficient processing power.

[0026] The messaging server system 108 supports various services and operations provided to the messaging clients 104. Such operations include sending data to the messaging clients 104, receiving data from the messaging clients 104, and processing data generated by the messaging clients 104. As examples, the data may include message content, client device information, geographic location information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The data exchange within the messaging system 100 is invoked and controlled by functions available via the user interface of the messaging client 104.

[0027] Turning now specifically to the messaging server system 108, an API server 116 is coupled to and provides a programming interface to the application server 114. The application server 114 is communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application server 114. Similarly, a web server 128 is coupled to and provides a web-based interface to the application server 114. To this end, the web server 128 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0028] The API server 116 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the API server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 to invoke the functions of the application server 114. The API server 116 exposes various functions supported by the application server 114, including: account registration, login functionality, sending messages from a particular messaging client 104 to another messaging client 104 via the application server 114, sending media files (e.g., images or videos) from a messaging client 104 to the messaging server 118 and for possible access by another messaging client 104, setting up a collection of media data (e.g., a story), retrieving a friend list of a user of a client device 102, retrieving such a collection, retrieving messages and content, adding entities (e.g., friends) to an entity graph (e.g., a social graph) and removing entities (e.g., friends) from an entity graph (e.g., a social graph), locating friends in a social graph, and opening application events (e.g., related to a messaging client 104).

[0029] The application server 114 hosts many server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and a social network server 124. The messaging server 118 implements many message processing techniques and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, text and media content from multiple sources can be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available to the messaging client 104. In view of the hardware requirements for other processor and memory intensive processing of data, such processing can also be performed on the server side by the messaging server 118.

[0030] The application server 114 also includes an image processing server 122 that is dedicated to performing various image processing operations, typically on images or videos within the payload of messages sent from or received at the messaging server 118 .

[0031] The image processing server 122 is used to implement ( Figure 2 ) enhanced system 208. The scanning function includes: when an image is captured by the client device 102, activating and providing one or more AR experiences on the client device 102. Specifically, the messaging client 104 on the client device 102 can be used to activate the camera. The camera displays one or more real-time images or videos and one or more icons or identifiers of one or more AR experiences to the user. The user can select a given identifier in the identifier to start the corresponding AR experience or perform the desired image modification (for example, replace the clothing worn by the user in the video or recolor the clothing worn by the user in the video or modify the clothing based on the gesture performed by the user).

[0032] The social network server 124 supports various social networking functions and services and makes them available to the messaging server 118. To this end, the social network server 124 maintains and accesses an entity graph 308 (e.g., Figure 3 Examples of functions and services supported by the social networking server 124 include identifying other users of the messaging system 100 that have a relationship with a particular user or that the particular user is "following," and also identifying interests and other entities of a particular user.

[0033] Returning to the messaging client 104, the features and functions of the external resource (e.g., a third-party application 109 or an applet) are available to the user via the interface of the messaging client 104. The messaging client 104 receives a user selection of an option for launching or accessing features of an external resource (e.g., a third-party resource) such as an external application 109. The external resource can be a third-party application (external application 109) installed on the client device 102 (e.g., a "local application"), or a small-scale version of a third-party application (e.g., a "applet") hosted on the client device 102 or remote from the client device 102 (e.g., on a third-party server 110). The small-scale version of the third-party application includes a subset of the features and functions of the third-party application (e.g., a full-scale, local version of a third-party standalone application), and a markup language document is used to implement the small-scale version of the third-party application. In one example, the small-scale version of the third-party application (e.g., a "applet") is a web-based markup language version of the third-party application and is embedded in the messaging client 104. In addition to using markup language documents (eg, .*ml files), applets may include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, .*ss files).

[0034] In response to receiving a user selection of an option for launching or accessing a feature of an external resource (external application 109), the messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed external application. In some cases, an external application 109 installed locally on the client device 102 can be launched independently of the messaging client 104 and separately from the messaging client 104, for example, by selecting an icon corresponding to the external application 109 on the home screen of the client device 102. A small-scale version of such an external application can be launched or accessed via the messaging client 104, and in some examples, any portion or limited portion of the small-scale external application cannot be accessed outside the messaging client 104. The small-scale external application can be launched by the messaging client 104 receiving a markup language document associated with the small-scale external application from the external application server 110 and processing such a document.

[0035] In response to determining that the external resource is a locally installed external application 109, the messaging client 104 instructs the client device 102 to launch the external application 109 by executing the locally stored code corresponding to the external application 109. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the external application server 110 to obtain a markup language document corresponding to the selected resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.

[0036] The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of activities occurring in one or more external resources. For example, the messaging client 104 may provide a notification related to the current or recent use of an external resource by one or more members of a user group to a participant in a conversation (e.g., a chat session) in the messaging client 104. One or more users may be invited to join an active external resource or to start an external resource that has been recently used but is currently inactive (in the friend group). The external resource may provide the ability to share items, conditions, states, or locations in the external resource with one or more members of the user group entering the chat session to participants in the conversation who each use the corresponding messaging client 104. The shared item may be an interactive chat card that members of the chat may interact with, such as to start a corresponding external resource, view specific information in an external resource, or bring members of the chat to a specific location or state in an external resource. Within a given external resource, a response message may be sent to the user on the messaging client 104. The external resource may selectively include different media items in the response based on the current context of the external resource.

[0037] The messaging client 104 may present a list of available external resources (e.g., third-party or external applications 109 or applets) to the user to launch or access a given external resource. The list may be presented in a context-sensitive menu. For example, icons representing different external applications in the external applications 109 (or applets) may vary based on how the user launches the menu (e.g., from a conversation interface or from a non-conversation interface).

[0038] The messaging client 104 can allow the user to safely monitor the messaging activities of the user group while maintaining the privacy of the user group. Specifically, the messaging client 104 can allow the primary user to establish a group portal (also referred to as a family portal) through the first client device 102. The group portal can allow the primary user to view the messaging activities of each user in the user group. As mentioned herein, the "group portal" is a special feature of the messaging client 104, and the messaging client 104 provides a graphical user interface to the primary user to monitor the messaging activities of a group of users (e.g., secondary users). The group portal can also allow each user in the user group to view their own messaging activities without seeing the messaging activities of other users in the group. In this way, the messaging activity information is only shared with the primary user, and not shared between other users in the group, which improves the privacy level of the user group. In some cases, the messaging activity information identifies a list of friends of a particular user to which the particular user has previously (e.g., within the past 24 hours or within the past 7 days) sent messages without providing the primary user with access to view the content of the sent messages (e.g., by excluding the content of the sent messages).

[0039] For example, the activity information may include a list of all messages sent by the user to a list of friends and a timestamp when each message was sent, and all messages received by the user from a list of friends and the timestamps of such messages. In such a case, the server may retrieve the list of friends and the timestamp only from the activity information associated with the received messages, not from the activity information associated with the sent messages, and exclude the actual messages or message content. In some cases, the entire contents of the activity information are provided to the client device of the primary user, and the client device retrieves the list of friends and the timestamp only from the activity information associated with the received messages, not from the activity information associated with the sent messages, and excludes the actual messages or message content. In some cases, the messaging activity information does not include or indicate any friends from whom a particular user receives messages. That is, the messaging client 104 may present only the identifier of the recipient of an outgoing message sent from a particular user's client device 102, and not the identifier of an incoming message received by the particular user from other senders.

[0040] System Architecture

[0041] Figure 21 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 contains a number of subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, a game system 212, and an external resource system 220.

[0042] The transient timer system 202 is responsible for implementing temporary or time-limited access to content by the messaging client 104 and the messaging server 118. The transient timer system 202 includes a number of timers that selectively enable access to messages and associated content (e.g., for presentation and display) via the messaging client 104 based on duration and display parameters associated with a message or collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 202 are provided below.

[0043] The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, image video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) can be organized into "event galleries" or "event stories." Such collections can be available for a specified time period (e.g., the duration of an event related to the content). For example, content related to a concert can be made available as a "story" for the duration of the concert. The collection management system 204 can also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client 104.

[0044] In addition, the collection management system 204 also includes a curation interface 206, which allows the collection manager to manage and curate specific content collections. For example, the curation interface 206 enables an event organizer to curate a collection of content related to a specific event (e.g., to delete inappropriate content or redundant messages). In addition, the collection management system 204 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation can be paid to users for including user-generated content in a collection. In such a case, the collection management system 204 operates to automatically pay such users for using their content.

[0045] The enhancement system 208 provides various functions that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to generating and publishing media overlays for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geographic location of the client device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information such as social network information of the user of the client device 102. The media overlay can include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos) at the client device 102. For example, the media overlay can include text, graphic elements, or images that can be overlaid on photos taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., Venice Beach), the name of a live event, or a business name overlay (e.g., Beach Cafe). In another example, the enhancement system 208 uses the geographic location of the client device 102 to identify a media overlay that includes the name of the business at the geographic location of the client device 102. The media overlay may include other tags associated with the business. The media overlay may be stored in the database 126 and accessed through the database server 120.

[0046] In some examples, the enhancement system 208 provides a user-based publishing platform that enables a user to select a geographic location on a map and upload content associated with the selected geographic location. The user can also specify an environment in which a particular media overlay should be provided to other users. The enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

[0047] In other examples, the augmentation system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with a geographic location via a bidding process. For example, the augmentation system 208 associates the media overlay of the highest bidding merchant with the corresponding geographic location for a predefined amount of time. The augmentation system 208 communicates with the image processing server 122 to obtain an AR experience and presents an identifier of such an experience in one or more user interfaces (e.g., as an icon on a real-time image or video, or as a thumbnail or icon in an interface dedicated to the identifier of the presented AR experience). Once the AR experience is selected, one or more images, videos, or AR graphical elements are retrieved and presented as an overlay on top of the image or video captured by the client device 102. In some cases, the camera is switched to a front view (e.g., the front camera of the client device 102 is activated in response to activation of a particular AR experience), and an image from the front camera of the client device 102, rather than the rear camera of the client device 102, begins to be displayed on the client device 102. One or more images, videos, or AR graphical elements are retrieved and rendered as an overlay on top of the image captured and displayed by the front-facing camera of the client device 102 .

[0048] In other examples, the augmentation system 208 can communicate and exchange data with another augmentation system 208 on another client device 102 and a server via the network 112. For example, during a video call between multiple users or participants, the exchanged data may include: a session identifier identifying a shared AR session; a transformation between a first client device 102 and a second client device 102 (e.g., the multiple client devices 102 include a first device and a second device), the transformation being used to align the shared AR session to a common origin; a common coordinate system; functions (e.g., commands for invoking functions), and other payload data (e.g., text, audio, video, or other multimedia data).

[0049] The augmentation system 208 sends the transformation to the second client device 102 so that the second client device 102 can adjust the AR coordinate system based on the transformation. In this way, the first client device 102 and the second client device 102 synchronize their coordinate systems and frames to display the content in the AR session. Specifically, the augmentation system 208 calculates the origin of the second client device 102 in the coordinate system of the first client device 102. The augmentation system 208 can then determine an offset in the coordinate system of the second client device 102 based on the location of the origin in the coordinate system of the second client device 102 from the perspective of the second client device 102. The offset is used to generate a transformation so that the second client device 102 generates AR content according to a common coordinate system or frame with the first client device 102.

[0050] The augmentation system 208 can communicate with the client device 102 to establish a separate or shared AR session. The augmentation system 208 can also be coupled to the messaging server 118 to establish an electronic group communication session (e.g., group chat, instant messaging, video call, group video call, etc.) for the client device 102 in the shared AR session. The electronic group communication session can be associated with a session identifier provided by the client device 102 to obtain access to the electronic group communication session and the shared AR session. In one example, the client device 102 first obtains access to the electronic group communication session and then obtains a session identifier in the electronic group communication session that allows the client device 102 to access the shared AR session. In some examples, the client device 102 is able to access the shared AR session without the assistance of the augmentation system 208 in the application server 114 or without communicating with the augmentation system 208 in the application server 114.

[0051] The mapping system 210 provides various geo-location functions and supports presentation of map-based media content and messages by the messaging client 104. For example, the mapping system 210 enables display of (e.g., stored in Figure 3) in the profile data 316 shown in the figure to indicate the current or past locations of the user's "friends" and media content (e.g., a collection of messages including photos and videos) generated by such friends within the context of the map. For example, messages posted by a user to the messaging system 100 from a particular geographic location can be displayed to the "friends" of the particular user on the map interface of the messaging client 104 within the context of the particular location on the map. The user can also share his or her location and status information with other users of the messaging system 100 via the messaging client 104 (e.g., using an appropriate status avatar), where the location and status information is similarly displayed to the selected user within the context of the map interface of the messaging client 104.

[0052] The gaming system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a gaming interface that provides a list of available games (e.g., web-based games or web-based applications) that can be launched by a user within the context of the messaging client 104 and played with other users of the messaging system 100. The messaging system 100 also enables a particular user to invite other users to participate in playing a particular game by sending an invitation to such other users from the messaging client 104. The messaging client 104 also supports both voice messaging and text messaging (e.g., chatting) within the context of game play, provides leaderboards for games, and supports providing in-game rewards (e.g., coins and items).

[0053] The external resource system 220 provides an interface for communicating with an external application server 110 to start or access external resources to the messaging client 104. Each external resource (application) server 110 hosts, for example, an application based on a markup language (e.g., HTML5) or a small-scale version of an external application (e.g., a game, utility, payment, or ride-sharing application external to the messaging client 104). The messaging client 104 can start the web-based resource (e.g., application) by accessing an HTML5 file from an external resource (application) server 110 associated with a web-based resource. In some examples, the application hosted by the external resource server 110 is programmed in JavaScript using a software development kit (SDK) provided by the messaging server 118. The SDK includes an API with functions that can be called or activated by a web-based application. In some examples, the messaging server 118 includes a JavaScript library that provides access to certain user data of the messaging client 104 to a given third-party resource. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.

[0054] In order to integrate the functionality of the SDK into a web-based resource, the SDK is downloaded from the messaging server 118 by the external resource (application) server 110 or received in other ways by the external resource (application) server 110. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the messaging client 104 into the web-based resource.

[0055] The SDK stored on the messaging server 118 effectively provides a bridge between external resources (e.g., third-party or external applications 109 or applets) and the messaging client 104. This provides users with a seamless experience of communicating with other users on the messaging client 104 while retaining the look and feel of the messaging client 104. In order to bridge the communication between the external resources and the messaging client 104, in some examples, the SDK facilitates the communication between the external resource server 110 and the messaging client 104. In some examples, the WebViewJavaScriptBridge running on the client device 102 establishes two one-way communication channels between the external resources and the messaging client 104. Messages are sent asynchronously between the external resources and the messaging client 104 via these communication channels. Each SDK function call is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

[0056] By using the SDK, not all information from the messaging client 104 is shared with the external resource server 110. The SDK limits which information is shared based on the needs of the external resource. In some examples, each external resource server 110 provides an HTML5 file corresponding to a web-based external resource to the messaging server 118. The messaging server 118 can add a visual representation (e.g., a block diagram or other graphic) of the web-based external resource in the messaging client 104. Once the user selects the visual representation or instructs the messaging client 104 to access the features of the web-based external resource through the graphical user interface of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources required to access the features of the web-based external resource.

[0057] The messaging client 104 presents a graphical user interface (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the launched external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the launched external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents another graphical user interface of the external resource, which includes the functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access the user data of the messaging client 104, after a threshold time period (e.g., 3 seconds) of displaying the login page or title screen of the external resource, the messaging client 104 slides a menu for authorizing the external resource to access the user data (e.g., animating the menu to emerge from the bottom of the screen to the middle or other part of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user selection of the accept option, the messaging client 104 adds the external resource to the list of authorized external resources and allows the external resource to access the user data from the messaging client 104. In some examples, external resources are authorized to access user data by messaging client 104 according to the OAuth 2 framework.

[0058] The messaging client 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, access to a first type of user data (e.g., only a two-dimensional avatar of a user with or without different avatar characteristics) is provided to an external resource including a full-scale external application (e.g., a third party or external application 109). As another example, access to a second type of user data (e.g., payment information, a two-dimensional avatar of a user, a three-dimensional avatar of a user, and an avatar with various avatar characteristics) is provided to an external resource including a small-scale version of an external application (e.g., a web-based version of a third-party application). Avatar characteristics include different ways to customize the look and feel of an avatar (e.g., different poses, facial features, clothing, etc.).

[0059] The user activity monitoring system 224 allows a user to safely monitor the messaging activity of a user group (e.g., a parent can monitor the messaging activity of their child) while maintaining the privacy of the user group. Specifically, the user activity monitoring system 224 can allow a primary user to establish a group portal through the first client device 102. The group portal can allow the primary user to view the messaging activity of each user in the user group.

[0060] In some examples, the user activity monitoring system 224 can automatically remove users from the user group in response to determining that certain conditions are met. For example, the user activity monitoring system 224 can continue to allow parents to monitor the messaging activities of their children until the child becomes an adult or reaches a certain age. Specifically, the user activity monitoring system 224 can continuously monitor the age of a specific user in the user group. The user activity monitoring system 224 can compare the age with a standard (e.g., an age threshold or age range, such as between 13 and 18 years old or not more than 18 years old). In response to determining that the age of a specific user exceeds or exceeds the age threshold or age range, the user activity monitoring system 224 automatically removes the specific user from the user group. Therefore, the user activity monitoring system 224 prevents the main user from accessing the messaging activity information of the specific user after the specific user reaches the threshold age or age range.

[0061] In some examples, the user activity monitoring system 224 can also prevent certain users from being added to the user group based on certain conditions. For example, the user activity monitoring system 224 can receive a request from the primary user to add a given user to the user group. The user activity monitoring system 224 can transmit a notification or invitation of the request to the given user. The user activity monitoring system 224 can determine that the age of the given user does not meet the age standard (for example, the given user is less than 13 years old or greater than 17 years old). In such a case, the user activity monitoring system 224 can present a notification or invitation to the given user on the client device 102 of the given user.

[0062] In some examples, in response to determining that the age of a given user does not meet the age criteria, the invitation excludes the option of accepting to join the user group. That is, an invitation or notification can be presented to a given user, but the invitation to join the user group cannot be accepted. This prevents the given user from being included in the user group and also prevents the primary user from being notified that the given user has not yet accepted the invitation to join. This further maintains the privacy of the given user by preventing the primary user from being informed of the reason why the given user has not joined the group (e.g., because the age of the given user does not meet the age criteria). Specifically, the primary user may or may not be notified that the given user has not yet joined the user group, but the indication of the age of the given user that has not exceeded or met the age criteria remains private or hidden from the primary user. In this way, the primary user cannot send multiple messages to multiple target users in an attempt to discover which target users have a specific age that meets the age criteria, which improves the overall level of security, privacy, and confidentiality of operating the user activity monitoring system 224.

[0063] Data Architecture

[0064] Figure 3is a schematic diagram illustrating a data structure 300 that may be stored in a database 126 of a messaging server system 108 according to some examples. Although the contents of the database 126 are illustrated as including a number of tables, it should be appreciated that data may be stored in other types of data structures (e.g., as an object-oriented database).

[0065] The database 126 includes message data stored in the message table 302. For any particular message, the message data includes at least message sender data, message recipient (or receiver) data, and payload. Figure 4 Additional details regarding information that may be included in a message and included within the message data stored in message table 302 are described.

[0066] The entity table 306 stores entity data and is linked (e.g., by reference) to the entity graph 308 and profile data 316. The entities whose records are maintained within the entity table 306 may include individuals, corporate entities, organizations, objects, places, events, etc. Regardless of the entity type, any entity about which the messaging server system 108 stores data may be an identified entity. Each entity is provided with a unique identifier as well as an entity type identifier (not shown).

[0067] The entity graph 308 stores information about relationships and associations between entities. By way of example only, such relationships may be social, professional (e.g., working in a common company or organization), interest-based, or activity-based.

[0068] Profile data 316 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 316 can be selectively used and presented to other users of the messaging system 100. In the case where the entity is a person, profile data 316 includes, for example, a user name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a collection of such avatar representations) selected by the user. A particular user can then selectively include one or more of these avatar representations within the content of messages transmitted via the messaging system 100 and on a map interface displayed to other users by the messaging client 104. The collection of avatar representations can include a "status avatar" that presents a graphical representation of a status or activity that a user may choose to convey at a particular time.

[0069] Where the entity is a group, profile data 316 for the group may similarly include one or more avatar representations associated with the group, in addition to the group name, members, and various settings for the relevant group (eg, notifications).

[0070] The database 126 also stores enhancement data, such as overlays or filters, in an enhancement table 310. The enhancement data is associated with and applied to videos (data for videos is stored in the video table 304) and images (data for images is stored in the image table 312).

[0071] The database 126 may also store data related to individual and shared AR sessions. The data may include data transmitted between an AR session client controller of a first client device 102 and another AR session client controller of a second client device 102, and data transmitted between an AR session client controller and an augmented system 208. The data may include data for establishing a common coordinate system for a shared AR scene, transformations between devices, session identifiers, images depicting the body, skeletal joint positioning, wrist joint positioning, and feet, and the like.

[0072] In one example, a filter is displayed as an overlay over an image or video during presentation to a recipient user. The filter can be of various types, including a user-selected filter from a set of filters presented to a sending user by the messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geofilters), which can be presented to a sending user based on geographic location. For example, the messaging client 104 can present a geolocation filter specific to a nearby or specific location within a user interface based on geographic location information determined by a global positioning system (GPS) unit of the client device 102.

[0073] Another type of filter is a data filter that can be selectively presented to the sending user by the messaging client 104 based on other input or information collected during the message creation process by the client device 102. Examples of data filters include the current temperature at a particular location, the current speed the sending user is traveling, the battery life of the client device 102, or the current time.

[0074] Other augmented data that may be stored in the image table 312 include AR content items (eg, corresponding to an applied AR experience). AR content items or AR items may be real-time special effects and sounds that may be added to an image or video.

[0075] As described above, augmented data includes AR content items, overlays, image transformations, AR images, AR logos or badges, and similar items involving modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify the image when it is captured using the device sensor (e.g., one or more cameras) of the client device 102 and then displaying the image with the modifications on the screen of the client device 102. This also includes modifications to stored content (e.g., video clips in a gallery that can be modified). For example, in a client device 102 that has access to multiple AR content items, a user can use a single video clip with multiple AR content items to see how different AR content items will modify the stored clips. For example, by selecting different AR content items for the content, multiple AR content items that apply different pseudo-random movement models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently captured by the sensor of the client device 102 will modify the captured data. Such data may be displayed only on the screen and not stored in memory, or content captured by the device sensors may be recorded and stored in memory with or without modification (or both). In some systems, a preview feature may simultaneously show how different AR content items will look in different windows in the display. This may, for example, enable viewing of multiple windows with different pseudo-random animations on the display at the same time.

[0076] Thus, data and various systems using AR content items or other such transformation systems using the data to modify content may involve: detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames; tracking such objects as they leave, enter, and move around the field of view; and modifying or transforming such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve: generating a three-dimensional mesh model of one or more objects, and using transformations and animated textures of the models within a video to implement the transformations. In other examples, tracking of points on an object may be used to place an image or texture (which may be two-dimensional or three-dimensional) at a tracked location. In yet another example, a neural network analysis of a video frame may be used to place an image, model, or texture in content (e.g., a frame of an image or video). Thus, an augmented reality content item refers to both images, models, and textures used to create transformations in content, as well as additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0077] Real-time video processing can be performed using any type of video data (e.g., video streams, video files, etc.) stored in the memory of any type of computerized system. For example, a user can load a video file and save it in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, computer animation models can be used to process any object, such as human faces and body parts, animals, or inanimate objects (e.g., chairs, cars, or other objects).

[0078] In some examples, when a specific modification is selected together with the content to be transformed, the elements to be transformed are identified by a computing device, and then if the elements are present in the frame of the video, they are detected and tracked. The elements of the object are modified according to the modification request, thereby transforming the frame of the video stream. For different types of transformations, the transformation of the frame of the video stream can be performed by different methods. For example, for the transformation of the frame that mainly involves changing the form of the elements of the object, the characteristic points of each element of the object are calculated (for example, using an active shape model (ASM) or other known methods). Then, a grid based on the characteristic points is generated for each element of at least one element of the object. The grid is used for the subsequent stage of tracking the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the positioning of each element. Then, additional points are generated on the grid. A first group of first points is generated for each element based on the modification request, and a group of second points is generated for each element based on the group of first points and the modification request. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the group of first points, the group of second points and the grid. In such an approach, the background of the modified object may also be changed or distorted by tracking and modifying the background.

[0079] In some examples, a transformation that changes some areas of an object using elements of an object can be performed by calculating characteristic points of each element of the object and generating a grid based on the calculated characteristic points. Points are generated on the grid, and then various areas are generated based on the points. The elements of the object are then tracked by aligning the area for each element with the positioning for each element of at least one element, and the properties of the area can be modified based on the modification request, thereby transforming the frame of the video stream. Depending on the specific modification request, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects into the area based on the modification request; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some characteristic points may be selected as control points for the entire state space to be used to determine options for model animation.

[0080] In some examples of computer animation models for transforming image data using face detection, faces are detected on images using a specific face detection algorithm (e.g., Viola-Jones). The ASM algorithm is then applied to the face region of the image to detect facial feature reference points.

[0081] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, and the landmarks represent distinguishable points that are present in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not identifiable (for example, when a person wears an eye patch), secondary landmarks can be used. Such a landmark identification process can be used for any such object. In some examples, a set of landmarks forms a shape. The coordinates of the points in the shape can be used to represent the shape as a vector. A similarity transformation (which allows translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points is used to align one shape with another shape. The mean shape is the average value of the aligned training shapes.

[0082] In some examples, the landmark search begins with an average shape that aligns with the location and size of the face as determined by a global face detector. Such a search then repeats the steps of proposing tentative shapes by template matching the image texture around each point to adjust the position of the shape points, and then conforming the tentative shapes to the global shape model until convergence occurs. In some systems, template matching alone is unreliable, and the shape model pools the results of weak template matches to form a stronger overall classifier. The entire search is repeated at each level in the image pyramid, from coarse to fine resolution.

[0083] The transformation system can capture an image or video stream on a client device (e.g., client device 102) and perform complex image manipulations locally on the client device 102 while maintaining an appropriate user experience, computation time, and power consumption. Complex image manipulations can include size and shape changes, emotion transitions (e.g., changing a face from a frown to a smile), state transitions (e.g., aging a subject, reducing apparent age, changing gender), style transitions, application of graphical elements, and any other suitable image or video manipulations enabled by a convolutional neural network that has been configured to execute efficiently on the client device 102.

[0084] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network, where the neural network operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model for transforming the image data, or the computer animation model can exist in association with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the user's face within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the user's image to reflect the selected modification icon (e.g., generating a smiling face for the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream, and once a modification icon is selected, the modified result can be presented to the user in real time or near real time. In addition, the modification can be persistent while the video stream is being captured and the selected modification icon remains toggled. A machine-learned neural network can be used to implement such modification.

[0085] The graphical user interface presenting the modifications performed by the transformation system can provide additional interactive options to the user. Such options can be based on the interface for initiating the selection of a particular computer animation model and content capture (e.g., initiated from a content creator user interface). In various examples, the modification can be persistent after the modification icon is initially selected. The user can switch the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing to other areas of the imaging application. In the case where multiple faces are modified by the transformation system, the user can globally switch the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some examples, each face in a group of multiple faces can be modified individually, or such modifications can be switched individually by tapping or selecting a single face or a series of single faces displayed within the graphical user interface.

[0086] The story table 314 stores data related to a collection of messages and associated images, videos, or audio data that are compiled into a collection (e.g., a story or gallery). The creation of a particular collection can be initiated by a particular user (e.g., each user whose record is maintained in the entity table 306). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by the user. To this end, the user interface of the messaging client 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.

[0087] A collection may also constitute a "live story," which is a collection of content from multiple users created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" may constitute a curated stream of user-submitted content from various locations and events. Users whose client devices have location services enabled and who are at a common location event at a particular time may be presented with the option of contributing content to a particular live story, for example, via the user interface of the messaging client 104. Live stories may be identified to the user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

[0088] Another type of content collection is called a "location story," which enables users whose client devices 102 are located in a particular geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some examples, contributions to location stories may require secondary authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student on a university campus).

[0089] As mentioned above, the video table 304 stores video data, which in one example is associated with a message whose record is maintained within the message table 302. Similarly, the image table 312 stores image data associated with a message whose message data is stored in the entity table 306. The entity table 306 can associate various enhancements from the enhancement table 310 with the various images and videos stored in the image table 312 and the video table 304.

[0090] Data communication architecture

[0091] Figure 4is a schematic diagram illustrating the structure of a message 400 according to some examples, the message 400 being generated by a messaging client 104 for transmission to another messaging client 104 or a messaging server 118. The content of a particular message 400 is used to populate a message table 302 stored in a database 126 accessible by a messaging server 118. Similarly, the content of the message 400 is stored in memory as "in-transit" or "in-flight" data of a client device 102 or application server 114. The message 400 is shown to include the following example components:

[0092] Message identifier 402 : a unique identifier that identifies the message 400 .

[0093] Message text payload 404 : Text to be generated by a user via the user interface of the client device 102 and included in the message 400 .

[0094] Message image payload 406 : Image data captured by a camera component of the client device 102 or retrieved from a memory component of the client device 102 and included in the message 400 . The image data for a sent or received message 400 may be stored in the image table 312 .

[0095] Message video payload 408 : Video data captured by the camera component or retrieved from the memory component of the client device 102 and included in the message 400 . The video data for a message 400 that has been sent or received may be stored in the video table 304 .

[0096] Message audio payload 410 : audio data captured by a microphone or retrieved from a memory component of the client device 102 and included in the message 400 .

[0097] Message enhancement data 412: Enhancement data (e.g., filters, stickers, or other annotations or enhancements) representing enhancements to be applied to the message image payload 406, message video payload 408, or message audio payload 410 of the message 400. The enhancement data for a sent or received message 400 may be stored in the enhancement table 310.

[0098] Message duration parameter 414: A parameter value indicating the amount of time in seconds that the content of a message (eg, message image payload 406, message video payload 408, message audio payload 410) will be presented to or made accessible to a user via messaging client 104.

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

[0100] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., a "story" identified in stories table 314) associated with a particular content item in message image payload 406 of message 400. For example, an identifier value may be used to associate multiple images within message image payload 406 with each of multiple content collections.

[0101] Message tags 420: Each message 400 may be tagged with a plurality of tags, each of which indicates the subject of the content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value indicating the relevant animal may be included within the message tags 420. The tag values ​​may be manually generated based on user input, or may be automatically generated using, for example, image recognition.

[0102] • Message sender identifier 422: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.

[0103] • Message recipient identifier 424: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 to which the message 400 is addressed.

[0104] The content (e.g., value) of each component of message 400 may be a pointer to a location in a table in which the content data value is stored. For example, the image value in message image payload 406 may be a pointer to a location in image table 312 (or the address of a location in image table 312). Similarly, the value in message video payload 408 may point to data stored in video table 304, the value stored in message enhancement data 412 may point to data stored in enhancement table 310, the value stored in message story identifier 418 may point to data stored in story table 314, and the values ​​stored in message sender identifier 422 and message recipient identifier 424 may point to user records stored in entity table 306.

[0105] User activity monitoring system

[0106] Figure 5 is a block diagram illustrating an example user activity monitoring system 224 according to some examples. The user activity monitoring system 224 includes a group portal setup module 510, an age monitoring module 520, and a user activity module 560. The user activity monitoring system 224 implements or accesses an API that enables various components of the user activity monitoring system 224 to communicate with the messaging server 118 or the social network server 124 to retrieve and present messaging activity information for various users in the group.

[0107] The group portal setup module 510 can initially be launched by a primary user (e.g., a parent). For example, a parent's first client device 102 can launch a messaging client 104. The messaging client 104 can present a search interface or option on a login page associated with the group portal. Specifically, the first client device 102 can receive input from the primary user including a search string associated with the group portal. The search string can include the words "family portal" or "group portal" or any other suitable word or words. In response to receiving the search string, an identifier of the group portal can be displayed on the first client device 102. The first client device 102 can receive input from the primary user selecting an identifier of the group portal. In response, the first client device 102 can instruct the group portal setup module 510 to display a group portal page.

[0108] As an example, the group portal setup module 510 may present Figure 6 600 shown in . Screen 600 includes instructions for the operation of the group portal. Specifically, screen 600 includes the following message, which welcomes the primary user and indicates that the group portal allows the primary user (e.g., a parent or guardian) to view their child's (e.g., a teenager's) friends and to view who the child has messaged within a specific time period (e.g., 7 days or 24 hours). The group portal setup module 510 displays a search interface 610 in a portion of screen 600. The search interface 610 allows the first client device 102 to receive a search string. The search string is used to identify various family members (e.g., children).

[0109] In some implementations, the group portal setup module 510 may call an API function of the messaging server 118. The API function may be called by passing a parameter of a search string and an identifier of a primary user. The messaging server 118 may then return a list of users to the group portal setup module 510 that are associated with the primary user on the messaging server 118 and include or are associated with an identifier that matches the search string. The group portal setup module 510 may present a list of users including a first user 612 on the screen 600.

[0110] The group portal setup module 510 may receive input from the primary user to select one or more of the list of users displayed on the screen 600. For example, the group portal setup module 510 may receive input to select the first user 612. In response, the group portal setup module 510 may mark the selected first user 612, for example by presenting a check mark, or visually distinguish the selected first user 612 from other users in the list. The group portal setup module 510 may present a send invite option 620.

[0111] In response to receiving a selection of the send invitation option 620, the group portal setup module 510 communicates with the age monitoring module 520 to verify that the primary user meets the age criteria. Specifically, the group portal setup module 510 can call an API function with the identity of the primary user and the age of the primary user. The API function can instruct the age monitoring module 520 to verify that the primary user is a parent and has an age greater than an age threshold (greater than 25 years old). In response to confirming that the primary user is a parent and has an age greater than the age threshold, the age monitoring module 520 transmits a message to the group portal setup module 510 confirming that the invitation can be sent to the client device 102 of the first user 612.

[0112] In some examples, the group portal setup module 510 can send a direct message to the client device 102 of the first user 612. Specifically, Figure 7 As shown in , a user interface 700 is presented on the client device 102 of the first user 612. The user interface 700 includes a chat screen and identifies the first user 710. The chat screen includes a message 720 indicating that the primary user has sent an invitation to add the first user 710 to the user group of the group portal. A similar user interface (not shown) with a chat screen can be presented with the same message or a similar message on the messaging client 104 of the primary user. Then, the two users can also chat with each other by sending messages to each other via the chat screen. Message 720 may include a subtext (not shown) indicating the status of accepting the invitation to join the user group in the group portal. The subtext may specify that the first user 710 has not yet accepted or has accepted the joining option.

[0113] Message 720 includes view invitation option 722. In response to the client device 102 of the first user 612 receiving the selection of view invitation option 722, the client device 102 of the first user 612 presents prompt 701 (e.g., as an overlay on top of the user interface 700). Prompt 701 includes message 711 identifying the primary user who invites the first user 612 to join the group portal (e.g., become a user in the user group associated with the group portal). Message 711 in prompt 701 can notify the first user 612 that by joining (e.g., selecting an option to join or accept an invitation to join the user group), the first user 612 is authorizing or making available to the primary user a list of the first user 612's friends and a list of recipients to whom the first user 612 (the client device 102 of the first user 612) sent messages within the past interval (e.g., 7 days or 1 day). Message 711 in prompt 701 also specifies that even if the first user 612 joins the user group, the content of the sent messages cannot be read and will not be presented to the primary user. This preserves a degree of privacy for the first user 612 .

[0114] In some examples, the group portal setup module 510 can communicate with the age monitoring module 520 to selectively and conditionally present the acceptance option 721 in the message 711. Specifically, the group portal setup module 510 communicates with the age monitoring module 520 to verify that the first user 612 is a child and meets the age criteria. Specifically, the group portal setup module 510 can call an API function with the identity of the first user 612 and the age of the first user 612. The API function can instruct the age monitoring module 520 to verify that the first user 612 is a child and has an age that meets the age criteria (e.g., less than an age threshold or within an age range, or less than 18 years old, or between 13 and 18 years old). In response to confirming that the first user 612 is a child and has an age that meets the age criteria, the age monitoring module 520 transmits a message to the group portal setup module 510 confirming that the acceptance option 721 can be presented as part of the message 711.

[0115] In some examples, the group portal setup module 510 detects or receives input from the client device 102 of the first user 612 indicating a selection of the acceptance option 721. Specifically, if the acceptance option 721 is presented in the message 711, the client device 102 of the first user 612 can determine that the first user 612 has selected the acceptance option 721. In response, the group portal setup module 510 forms a link between the first user 612 and the primary user, and adds the first user 612 to the user group associated with the group portal. The group portal setup module 510 also updates the status subtext in the message 720, which indicates that the first user 612 has accepted the invitation to join the group.

[0116] The group portal setup module 510 may present Figure 8 800. The user interface 800 includes a first area that identifies users in a user group. That is, the group portal setup module 510 can present a first identifier 810 of a first user 612 who has selected the accept option 721 and a second identifier 820 of a second user who has selected the accept option on their respective devices. The group portal setup module 510 can organize the identifiers presented in the first area alphabetically or by any other criteria or attributes. The identifiers can include the names and / or avatars of the associated users.

[0117] In some examples, the user interface 800 is presented in response to the group portal setup module 510 receiving input from the primary user selecting an option to launch the group portal. In response to receiving the input, the group portal setup module 510 calls an API function with the identity of the user of the client device 102. The API function can return an indication of whether the user is a parent or a child. In response to determining that the user is a parent (e.g., the primary user), the group portal setup module 510 can call a getchildren API function with the identity of the primary user. The API function can return a list of all child links (e.g., a list of all users who are part of a user group that have accepted an invitation to join a user group associated with the group portal). The API function can also identify the first user in the list (e.g., the user associated with the first identifier 810), and can return the user activity associated with the first identifier 810 to the group portal setup module 510 to generate a list of recent messaging activities associated with the first identifier 810.

[0118] The user activity module 560 can access the messaging client 104 of the user associated with the first identifier 810. The user activity module 560 can request a list of recipient identifiers to which the messaging client 104 transmits messages from the messaging client 104 of the user associated with the first identifier 810. That is, the messaging client 104 can access a messaging feed that shows or includes all messages in messages transmitted by the client device 102 in the past specified time period (e.g., 7 days or 1 day) and / or a list of friends added by the client device 102 within a threshold time period (e.g., within the past 7 days). The messaging client 104 can exclude from the list any messages that have not been received within the specified time period. The messaging client 104 can extract a recipient identifier (e.g., name and / or avatar) of each recipient in the list of messages. The messaging client 104 can then provide the user activity module 560 with a list of recipients to whom the messaging client 104 sent messages in the past specified time period and / or a list of friends added by the messaging client 104 within the threshold time period. The messaging client 104 may also provide the last time a message was sent to each recipient and / or how much time has elapsed since a message was last sent to each recipient, respectively.

[0119] The user activity module 560 can provide a list of recipients to the group portal setup module 510. The group portal setup module 510 can present a second area 830 that includes a list of recent conversations involving the user associated with the first identifier 810. The second area 830 can include a list of recipients received from the user activity module 560. In some examples, the list of recipients includes a first recipient identifier 832. The first recipient identifier 832 includes the name and / or avatar of the recipient to whom the user associated with the first identifier 810 sent the message. The first recipient identifier 832 can also include a timestamp or other indication of the last time a message was sent to the recipient and / or how much time has passed since the message was last sent to the recipient.

[0120] In some examples, the second area 830 may include a reporting option 834 for each recipient identifier presented in the second area 830. In response to receiving input from the primary user selecting the reporting option 834 for a given recipient, the group portal settings module 510 transmits a message to a third party (e.g., an entity operating a messaging application platform) indicating that the recipient associated with the recipient identifier is associated with or has performed an inappropriate activity.

[0121] In some examples, the group portal setup module 510 may present a view friends option 812. In response to receiving input from the primary user selecting the view friends option 812, the group portal setup module 510 calls an API function with the first identifier 810. The group portal setup module 510 receives from the API function a list of all friends (e.g., including names and / or avatars) of the user associated with the first identifier 810. The group portal setup module 510 may present an overlay including a list of all friends of the user associated with the first identifier 810 in response to receiving input from the primary user selecting the view friends option 812.

[0122] The group portal setup module 510 may receive input from the primary user selecting the second identifier 820. In response, the group portal setup module 510 may again communicate with the user activity module 560 to obtain a list of recipients to which the client device 102 of the user associated with the second identifier 820 has recently sent messages. The group portal setup module 510 may update the display of information in the area 830 with the new information about the user associated with the second identifier 820 obtained from the user activity module 560.

[0123] In some examples, the user interface 800 is presented in response to the group portal settings module 510 receiving input from a user (non-primary user, such as a child user) selecting an option to launch a group portal. In response to receiving the input, the group portal settings module 510 calls an API function with the identity of the user of the client device 102. The API function can return an indication of whether the user is a parent or a child. In response to determining that the user is a child (e.g., a non-primary user), the group portal settings module 510 can communicate with the user activity module 560 to obtain a list of recent messaging activities associated with the user and / or a list of friends added by the first user within a threshold time period. In such a case, the user interface 800 includes a similar layout and display of information provided to the primary user. In response to determining that the user is a child user, the group portal settings module 510 limits the information displayed to information associated with a specific user, and prevents the user from viewing or accessing information associated with other children or other users in the same group or other users also associated with the group portal. In this way, parents can monitor the activities of all their children, but children can only monitor their own activities.

[0124] In some examples, the age monitoring module 520 can automatically remove a user from the user group in response to determining that certain conditions are met. For example, the age monitoring module 520 can continue to allow the primary user to view the messaging activity of the user group until a given user in the user group reaches a certain age. Specifically, the age monitoring module 520 can continuously monitor the age of the user associated with the first identifier 810 and the second identifier 820. The age monitoring module 520 can compare the age with a standard (e.g., an age threshold or age range, such as between 13 and 18 years old or not more than 18 years old). In response to determining that the age of a given user associated with the second identifier 820 exceeds or crosses the age threshold or age range, the age monitoring module 520 automatically removes the second identifier 820 from the user group and the user interface 800 presented to the primary user.

[0125] The group portal setting module 510 may receive a request or input from a primary user and / or a given user of a user group to remove a given user from a user group. In response to receiving the request, the group portal setting module 510 removes an identifier associated with the given user requested to be removed from the user interface 800 presented to the primary user.

[0126] Fig. 9 900 is a flow chart of a process 900 performed by the user activity monitoring system 224 according to some examples. Although the flow chart may describe the operations as a sequential process, many of the operations may be performed in parallel or simultaneously. In addition, the order of the operations may be rearranged. When the operations of the process are completed, the process is terminated. A process may correspond to a method, a process, etc. The operations of a method may be performed in whole or in part, may be performed in combination with some or all of the operations in other methods, and may be performed by any number of different systems or any portion thereof (such as a processor included in any of the systems).

[0127] At operation 901 , the user activity monitoring system 224 (eg, the client device 102 or a server) receives a request from a first client device to access a group portal associated with a user group, as discussed above.

[0128] At operation 902 , the user activity monitoring system 224 generates a first identifier of a first user in the user group in response to receiving the request for display in a first portion of the group portal, as discussed above.

[0129] At operation 903 , the user activity monitoring system 224 accesses activity information associated with the first user, the activity information describing one or more messages sent by the second client device of the first user to a group of recipients, as discussed above.

[0130] At operation 904 , the user activity monitoring system 224 generates activity information associated with the first user, but does not expose the content of one or more messages sent by the second client device, for display in the second portion of the group portal, as discussed above.

[0131] Machine Architecture

[0132] Fig.10 1000 within which instructions 1008 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 1000 to perform any one or more of the methods discussed herein. For example, the instructions 1008 may cause the machine 1000 to perform any one or more of the methods described herein. The instructions 1008 transform a general purpose, unprogrammed machine 1000 into a specific machine 1000 that is programmed to perform the functions described and illustrated in the manner described. The machine 1000 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1000 may operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1000 may include, but is not limited to, a server computer, a client computer, a PC, a tablet computer, a laptop computer, a netbook, an STB, a PDA, an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 1008 specifying actions to be taken by the machine 1000. In addition, although only a single machine 1000 is shown, the term "machine" should also be considered to include a collection of machines that individually or jointly execute instructions 1008 to perform any one or more of the methods discussed herein. For example, the machine 1000 may include a client device 102 or any of a number of server devices that form part of a messaging server system 108. In some examples, the machine 1000 may also include both a client system and a server system, where certain operations of a particular method or algorithm are performed on the server side and certain operations of the particular method or algorithm are performed on the client side.

[0133] The machine 1000 may include a processor 1002, a memory 1004, and an input / output (I / O) component 1038 that may be configured to communicate with each other via a bus 1040. In an example, the processor 1002 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1006 that executes instructions 1008 and a processor 1010. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.10 Multiple processors 1002 are shown, but the machine 1000 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0134] The memory 1004 includes a main memory 1012, a static memory 1014, and a storage unit 1016, which are all accessible by the processor 1002 via the bus 1040. The main memory 1012, the static memory 1014, and the storage unit 1016 store instructions 1008 that embody any one or more of the methodologies or functions described herein. The instructions 1008 may also reside, completely or partially, within the main memory 1012, within the static memory 1014, within a machine-readable medium within the storage unit 1016, within at least one of the processors 1002 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1000.

[0135] I / O components 1038 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 1038 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will most likely not include such a touch input device. It should be appreciated that I / O components 1038 may include Fig.101024 and 1026. In various examples, the I / O components 1038 may include a user output component 1024 and a user input component 1026. The user output component 1024 may include a visual component (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 1026 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0136] In other examples, the I / O component 1038 may include a biometric component 1028, a motion component 1030, an environmental component 1032, or a positioning component 1034, as well as various other components. For example, the biometric component 1028 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1030 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0137] Environmental components 1032 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometers), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors that detect concentrations of hazardous gases for safety or measure pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0138] With respect to cameras, client device 102 may have a camera system including, for example, a front-facing camera on a front surface of client device 102 and a rear-facing camera on a rear surface of client device 102. The front-facing camera may, for example, be used to capture still images and videos of a user of client device 102 (e.g., a "selfie"), which may then be enhanced with the enhancement data (e.g., filters) described above. For example, the rear-facing camera may be used to capture still images and videos in a more conventional camera mode, where the images are similarly enhanced with the enhancement data. In addition to the front-facing camera and the rear-facing camera, client device 102 may also include a 360° camera for capturing 360° photos and videos.

[0139] Additionally, the camera system of the client device 102 may include dual rear cameras (e.g., a main camera and a depth sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of the client device 102. For example, these multiple camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

[0140] The positioning component 1034 includes a position sensor component (for example, a GPS receiver component), an altitude sensor component (for example, an altimeter or a barometer that detects air pressure, and the altitude can be obtained based on the air pressure), an orientation sensor component (for example, a magnetometer), etc.

[0141] A variety of technologies may be used to achieve communication. The I / O components 1038 also include a communication component 1036 that is operable to couple the machine 1000 to the network 1020 or device 1022 via a corresponding coupling or connection. For example, the communication component 1036 may include a network interface component or other suitable device that interfaces with the network 1020. In other examples, the communication component 1036 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Parts (e.g. Low energy consumption), Device 1022 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via USB).

[0142] In addition, the communication component 1036 can detect the identifier or include a component that is operable to detect the identifier. For example, the communication component 1036 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as universal product code (UPC) bar codes, multi-dimensional bar codes such as quick response (QR) codes, Aztec codes, data matrix, data symbol (Dataglyph), MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar codes and other optical codes) or an acoustic detection component (e.g., a microphone for identifying a tagged audio signal). In addition, various information can be obtained via the communication component 1036, such as location via Internet Protocol (IP) geolocation, ... Signal triangulation to derive location, location via detection of NFC beacon signals that can indicate a specific location, etc.

[0143] Various memories (e.g., main memory 1012, static memory 1014, and memory of processor 1002) and storage unit 1016 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. When executed by processor 1002, these instructions (e.g., instructions 1008) cause various operations to implement the disclosed examples.

[0144] The instructions 1008 may be sent or received over the network 1020 using a transmission medium via a network interface device (e.g., a network interface component included in the communication component 1036) and using any of several well-known transmission protocols (e.g., HTTP). Similarly, the instructions 1008 may be sent or received via a coupling (e.g., a peer-to-peer coupling) with the device 1022 using a transmission medium.

[0145] Software Architecture

[0146] Fig.11 1100 is a block diagram illustrating a software architecture 1104 that may be installed on any one or more of the devices described herein. The software architecture 1104 is supported by hardware, such as a machine 1102 including a processor 1120, a memory 1126, and I / O components 1138. In this example, the software architecture 1104 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1104 includes layers such as an operating system 1112, a library 1110, a framework 1108, and an application 1106. In operation, the application 1106 invokes an API call 1150 through the software stack and receives a message 1152 in response to the API call 1150.

[0147] The operating system 1112 manages hardware resources and provides public services. The operating system 1112 includes, for example, a kernel 1114, a service 1116, and a driver 1122. The kernel 1114 serves as an abstraction layer between the hardware layer and other software layers. For example, the kernel 1114 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. The service 1116 can provide other public services for other software layers. The driver 1122 is responsible for controlling the underlying hardware or interfacing with the underlying hardware. For example, the driver 1122 may include a display driver, a camera driver, or Low-power drivers, Flash drivers, Serial communication drivers (e.g., USB drivers), Drivers, audio drivers, power management drivers, etc.

[0148] The libraries 1110 provide a common low-level infrastructure used by the applications 1106. The libraries 1110 may include a system library 1118 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1110 may include an API library 1124, such as a media library (e.g., a library for supporting the presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for rendering in two and three dimensions in graphical content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 1110 may also include various other libraries 1128 to provide many other APIs to the application 1106 .

[0149] The framework 1108 provides a common high-level infrastructure used by the applications 1106. For example, the framework 1108 provides various graphical user interface functions, advanced resource management, and advanced location services. The framework 1108 can provide a wide range of other APIs that can be used by the applications 1106, some of which can be specific to a particular operating system or platform.

[0150] In an example, applications 1106 may include a home application 1136, a contacts application 1130, a browser application 1132, a book reader application 1134, a location application 1142, a media application 1144, a messaging application 1146, a game application 1148, and a variety of other applications such as external applications 1140. Applications 1106 are programs that execute functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 1106 constructed in various ways, such as an object-oriented programming language (e.g., Objective-C, Java, or C++) or a procedural programming language (e.g., C or assembly language). In a specific example, external applications 1140 (e.g., applications created by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM SDK developed applications) can be mobile operating systems such as IOS TM ANDROID TM , Phone, or another mobile operating system running on the mobile software. In this example, the external application 1140 can call the API call 1150 provided by the operating system 1112 to facilitate the functions described herein.

[0151] Glossary

[0152] "Client Device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop computer, PDA, smart phone, tablet computer, ultrabook, netbook, laptop computer, multiprocessor system, microprocessor-based or programmable consumer electronics, game console, set-top box, or any other communications device that a user may use to access a network.

[0153] "Communications Network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the Public Switched Telephone Network (PSTN), a Plain Old Telephone Service (POTS) network, a cellular telephone network, a wireless network, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0154] "Component" means a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization of specific processing or control functions. Components can be combined with other components via their interfaces to perform a machine process. A component can be a packaged functional hardware unit designed for use with other components and is part of a program that typically performs a specific one of the related functions.

[0155] Components may constitute software components (e.g., code implemented on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit that is capable of performing certain operations and that can be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., a processor or group of processors) may be configured by software (e.g., an application or application portion) to be hardware components that operate to perform certain operations described herein.

[0156] Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include a dedicated circuit system or logic that is permanently configured to perform certain operations. A hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It will be recognized that it can be determined for cost and time considerations whether to implement the hardware component mechanically in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein.

[0157] Consider an example where hardware components are temporarily configured (e.g., programmed), without configuring or instantiating each of the hardware components at any one time. For example, where the hardware components include a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured into different special-purpose processors (e.g., including different hardware components) at different times. The software configures one or more specific processors accordingly, for example, to constitute a specific hardware component at one time and to constitute different hardware components at different times.

[0158] Hardware components can provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components can be considered to be coupled in communication. In the case of multiple hardware components simultaneously, communication can be realized by signal transmission (for example, by appropriate circuits and buses) between or among two or more hardware components in the hardware components. In the example that multiple hardware components are configured or instantiated at different times, the communication between such hardware components can be realized, for example, by storing information in a memory structure to which multiple hardware components have access rights and retrieving information in the memory structure. For example, a hardware component can perform an operation and store the output of the operation in a memory device coupled in communication with it. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (for example, a collection of information).

[0159] The various operations of the example methods described herein may be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described herein may be implemented at least in part by a processor, wherein a specific one or more processors are examples of hardware. For example, at least some operations of the method may be performed by one or more processors 1002 or processor-implemented components. In addition, one or more processors may also be operated to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some of the operations may be performed by a group of computers (as an example of a machine including a processor), wherein these operations may be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of certain operations may be distributed between processors, not just residing in a single machine, but deployed across many machines. In some examples, the processor or processor-implemented components may be located in a single geographic location (e.g., in a home environment, an office environment, or a server farm). In other examples, the processor or processor-implemented components may be distributed across multiple geographic locations.

[0160] "Computer-readable storage media" refers to both machine storage media and transmission media. Thus, the term includes both storage devices / media and carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

[0161] "Transient message" refers to a message that is accessible for a limited duration. Transient messages can be text, images, videos, etc. The access time of a transient message can be set by the sender of the message. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.

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

[0163] “Non-transitory computer-readable storage medium” refers to tangible media capable of storing, encoding, or carrying instructions to be executed by a machine.

[0164] "Signal medium" refers to any intangible medium that is capable of storing, encoding or carrying instructions to be executed by a machine, and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" refer to the same thing and may be used interchangeably in this disclosure.

[0165] Changes and modifications may be made to the disclosed examples without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure as expressed in the appended claims.

Claims

1. A method comprising: receiving a request from a first client device to access a group portal associated with a user group; In response to receiving the request, generating a first identifier of a first user in the user group for display in a first portion of the group portal; accessing activity information associated with the first user, the activity information describing one or more messages sent by a second client device of the first user to a group of recipients; as well as Activity information associated with the first user, but excluding content of one or more messages sent by the second client device, is generated for display in a second portion of the group portal.

2. The method according to claim 1, further comprising: receiving, by the first client device via the group portal, a selection of the first user; in response to receiving the selection of the first user, transmitting from the first client device to a second client device of the first user an invitation to join the group portal; as well as In response to determining that a second client device of the first user receives a confirmation from the first user to join the group portal, the first user is added to the user group.

3. The method according to any one of claims 1 to 2, further comprising: In response to the second client device receiving the invitation from the first client device, causing the second client device to generate a display of a message representative of the invitation.

4. The method according to claim 3, wherein: The message includes a plurality of options and an identification of a primary user of the first client device, the plurality of options including an acceptance option confirming that the first user joins the group portal.

5. The method according to any one of claims 1 to 4, wherein: The message includes a prompt identifying various activities that will be available to the primary user in response to receiving a selection of the accept option.

6. The method according to claim 5, wherein: The various activities include a list of the first user's friends, a list of friends added by the first user within a threshold time period, and a list of a plurality of messages sent by a second client device of the first user within a specified interval.

7. The method according to any one of claims 1 to 6, wherein: The specified interval includes seven days or one day.

8. The method according to any one of claims 1 to 7, wherein: The first portion includes a second identifier of a second user in the group of users.

9. The method according to claim 8, further comprising: receiving a selection of the second identifier by the first client device; as well as In response to receiving a selection of the second identifier: accessing activity information associated with the second user, the activity information representing one or more messages sent by a third client device of the second user to a second set of recipients; as well as The second portion is updated to generate activity information associated with the second user but without presenting content of one or more messages sent by the third client device for display.

10. The method according to any one of claims 1 to 9, wherein: The first portion includes a view friends option, wherein in response to receiving a selection of the view friends option, a list of friends of the first user is presented on a first client device associated with a primary user.

11. The method according to any one of claims 1 to 10, further comprising: displaying, on the first client device, a list of users to whom the second client device has sent messages within a specified time period; as well as A report icon is displayed for each user in the list of users, the report icon causing a message to be transmitted to a third party indicating the inappropriate activity.

12. The method according to any one of claims 1 to 11, further comprising: A private message including an invitation to join the group portal is transmitted from the first client device to the second client device.

13. The method according to claim 12, further comprising: A state in which the first user joins the group portal is presented as a subtext of the private message.

14. The method according to any one of claims 1 to 13, further comprising: determining an age of a first user associated with the second client device; as well as determining whether the age of the first user meets a criterion; as well as An accept invitation option is conditionally presented in the private message based on determining whether the age of the first user meets the criteria.

15. The method according to any one of claims 1 to 14, further comprising: determining an age of a first user associated with the second client device; as well as determining whether the age of the first user meets a criterion; as well as In response to determining that the age of the first user no longer meets the criteria, the first user is automatically removed from the group of users.

16. The method according to any one of claims 1 to 15, further comprising: receiving a request from the second client device to access the group portal; In response to receiving the request from the second client device, activity information associated with the first user is generated without presenting content of one or more messages sent by the second client device for display to the second client device.

17. The method according to any one of claims 1 to 16, wherein: The user group includes a parent and one or more children of the parent.

18. The method according to any one of claims 1 to 17, wherein: A plurality of identifiers of the user groups are displayed in alphabetical order in the first portion.

19. A system comprising: processor; as well as a memory component having stored thereon instructions which, when executed by the processor, cause the processor to perform operations comprising: receiving a request from a first client device to access a group portal associated with a user group; In response to receiving the request, generating a first identifier of a first user in the user group for display in a first portion of the group portal; accessing activity information associated with the first user, the activity information describing one or more messages sent by a second client device of the first user to a group of recipients; and Activity information associated with the first user, but excluding content of one or more messages sent by the second client device, is generated for display in a second portion of the group portal.

20. A non-transitory computer-readable storage medium having stored thereon instructions, the instructions, when executed by a processor, causing the processor to perform operations comprising: receiving a request from a first client device to access a group portal associated with a user group; In response to receiving the request, generating a first identifier of a first user in the user group for display in a first portion of the group portal; accessing activity information associated with the first user, the activity information describing one or more messages sent by a second client device of the first user to a group of recipients; as well as Activity information associated with the first user, but excluding content of one or more messages sent by the second client device, is generated for display in a second portion of the group portal.

Images