[go: up one dir, main page]

WO2024249978A2 - Plateforme de style de vie en ligne de confidentialité contextuelle, systèmes et procédés associés - Google Patents

Plateforme de style de vie en ligne de confidentialité contextuelle, systèmes et procédés associés Download PDF

Info

Publication number
WO2024249978A2
WO2024249978A2 PCT/US2024/032202 US2024032202W WO2024249978A2 WO 2024249978 A2 WO2024249978 A2 WO 2024249978A2 US 2024032202 W US2024032202 W US 2024032202W WO 2024249978 A2 WO2024249978 A2 WO 2024249978A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
profile
settings
message
readable storage
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/032202
Other languages
English (en)
Other versions
WO2024249978A3 (fr
Inventor
Monica C. ZLOTOGORSKI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
VaporStream Inc
Original Assignee
VaporStream Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by VaporStream Inc filed Critical VaporStream Inc
Publication of WO2024249978A2 publication Critical patent/WO2024249978A2/fr
Publication of WO2024249978A3 publication Critical patent/WO2024249978A3/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/52—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H04L51/046—Interoperability with other network applications or services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles

Definitions

  • CPOL platform contextualized privacy online lifestyle platform
  • concepts and associated implementations are described in the context of one or more embodiments of a CPOL platform, it is contemplated that any such concept or associated implementation may also be utilized with a different embodiment of a CPOL platform or other type of online platform, system, or environment as applicable.
  • Existing digital communications and interaction platforms lack the ability and functionalities to allow users to maximize the efficiency of their use of these tools. Users often are forced to utilize multiple platforms, depending on the contextual or situational need, to interact with different individuals or groups of people and/or for different topics of interaction. For example, a person’s contacts can be friends, co-workers, businesses, organizations, celebrities, influencers, and others with which the person interacts or follows. Such contacts may each exist in different environments and/or require different interaction treatment. Such different interaction treatments include, but are not limited to, different social, security, privacy, compliance, disappearing messaging, and/or record retention requirements.
  • a person may have distinctly different environments in which they interact with other entities, such as a business context and a social context, each having its own needs for interaction treatment.
  • the person may wish to project out different impressions, images, personas, emotions, etc. to their contacts in those different contextual environments.
  • a person may have a context in which their interactions are governed by another entity, which imposes certain interaction treatments onto them in that context. Examples of such other entities that may impose an interaction treatment upon a person include, but are not limited to, an employer, an educational organization, a social organization, a career organization, a medical organization, a government body, a standards organization, a sports organization, and any combinations thereof.
  • a third-party standard unique identifier is an identifier that can be used to uniquely identify and communicate with a person due to it being standardized for use by multiple entities for communicating with a single end point, such as is the case with standardized emails and phone numbers that can be used across multiple platforms to uniquely identify a person.
  • an existing system can require a user to have multiple different phone numbers in order to set up different accounts for the purpose of projecting out to contacts different contextual impressions of the user with different profile images and information.
  • a CPOL platform (or any similar digital platform, such as a social media platform, a messaging platform, a business management platform, a workflow platform, etc. and platforms that have combinations of such features) may include an architecture that is configured to allow a user to have a single account with multiple profiles, each having a different outwardly projected persona, without the need for multiple third-party standard unique identifiers.
  • Other CPOL platform concepts that can be combined with the foregoing and/or exist by themselves or in combination with each other are also disclosed herein.
  • Examples of a third-party standard unique identifier include, but are not limited to, a standard email address, a universal resource locator (URL), a phone number (e.g., a mobile phone number), a government issued identifier (e.g., social security number, driver’s license number), and any combinations thereof.
  • a third-party standard unique identifier may be assigned to a user of a digital platform by an entity other than that platform that uses it as an account identifier.
  • a CPOL platform of the current disclosure may be configured to utilize a third-party standard unique identifier that is a standard email address of a platform different from the CPOL platform.
  • a third-party standard unique identifier is a phone number provided to a user of a CPOL platform by a phone service provider other than the CPOL platform.
  • digital communications and interaction platforms utilize a third-party standard unique identifier to uniquely identify that person on the platform.
  • the platform can use the third-party standard unique identifier to communicate with the user, and/or identify a user’s device (e.g., a mobile phone).
  • a user is assigned a user account having an account identifier that uniquely identifies the user on the CPOL platform.
  • a third-party standard unique identifier may be used as an account identifier.
  • the user account includes the ability for the user to have different user profiles, such that multiple user profiles can exist for a single user account (e.g., using a single third-party standard unique identifier).
  • a user account can have multiple user profiles without the need for more than one third- party standard unique identifier.
  • a profile identifier within the CPOL platform can be some other identifier that is not a third-party standard unique identifier (e g., a username).
  • one or more profiles under a single account may have profile identifiers (such as a profile discoverability identifier described below) that are third-party standard unique identifiers, but not require that each have one (e.g., one profile using the same third-party standard unique identifier as the account identifier and other profiles using a different identifier, such as a username).
  • profile identifiers such as a profile discoverability identifier described below
  • Each profile includes one or more profile discoverability identifiers.
  • a profile discoverability identifier is an identifier that can be used by other users of a platform to search for and find the user profile associated with the particular profile discoverability identifier.
  • a profile discoverability identifier can be used to uniquely identify a user profile within a CPOL platform. Examples of a profile discoverability identifier include, but are not limited to, a third-party standard unique identifier, a platform specific identifier, and any combinations thereof.
  • a CPOL platform includes a profile that includes a profile discoverability identifier that is a standard email address.
  • a CPOL platform includes a profile that includes a profile discoverability identifier that is a phone number.
  • a profile can have multiple profile discoverability identifiers (e.g., multiple of the same type, such as multiple email addresses, and/or multiple of different types, such as one or more email addresses and one or more phone numbers). It is contemplated that an account with multiple profiles may have a phone number utilized for a profile discoverability identifier in one profile and each other profile has one or more profile discoverability identifiers that are a platform specific identifier and/or a non-phone number third-party standard unique identifier (e.g., an email address).
  • a CPOL platform may also be configured to allow a first profile to use an email address as a profile discoverability identifier and other profiles have one or more discoverability identifiers that are a platform specific identifier and/or a non-email address third-party standard unique identifier.
  • a platform specific identifier is an identifier within a CPOL platform that can be used by the platform to distinguish different profiles and/or allow for discoverability of a user.
  • a platform specific identifier is unique to the CPOL platform.
  • a platform specific identifier may be an identifier that is not part of a standardized system recognized by multiple platforms operated by different entities for identifying an individual (e.g., a phone number usable across a telephone network that includes multiple phone entity companies, an email address utilizing a standardized email protocol, a social security number, a government issued identification number coupled with the identification type, etc.).
  • platform specific identifiers include, but are not limited to, a username, an alphanumeric string, a platform specific QR code, and any combinations thereof. It is contemplated that a user may utilize the same identifier (e.g., same username) on multiple platforms (e.g., on a platform according to the current disclosure and one or more other platforms), but that the username itself is not part of a standardized identification system. In one example, one of a user’s profiles in a CPOL platform utilizes the same third-party standard unique identifier associated with that user’s user account as a profile discoverability identifier for that profile.
  • an implementation of such a CPOL platform may allow for each additional user profile under the same user account to not have any third-party standard unique identifiers associated with the profile as a profile discoverability identifier.
  • an implementation of a CPOL platform may require that each additional user profile under the same user account have a profile discoverability identifier that is not a third-party standard unique identifier.
  • a profile may have any number of profile discoverability identifiers.
  • a profile may be configured to allow a user to enter any one or more of a plurality of different profile discoverability identifiers for each profile.
  • each profile is restricted to have a different value for each type of profile discoverability identifier across a user account (e.g., no two profiles of a user account are allowed to have the same phone number or the same username).
  • two different profiles may have the same profile discoverability identifier (e.g., allowing another user to “discover” more than one profile for a user).
  • a profile may be configured to allow a user to associate two different profile discoverability identifiers of the same type (e.g., two mobile phone numbers) with the same profile.
  • a CPOL platform may be configured such that each profile can have a phone number, an email address, and a username as profile discoverability identifiers such that a user can input a phone number for one profile and a username for another profile (e.g., not requiring more than one phone number).
  • a profile may include a variety of discoverability settings configured to customize the use of a profile discoverability identifier and/or other aspects of how a user is identifiable on a CPOL platform.
  • Examples of a discoverability setting include, but are not limited to, a setting indicating which profile discoverability identifier for a profile can be actively utilized to discover the user profile, a setting indicating a degree of separation from a user and/or contact required to be able to discover a profile, and any combinations thereof.
  • certain discoverability settings may be potentially applicable across multiple profiles (e.g., findable only to a certain degree of separation to existing contacts, findable only by a certain type of profile discoverability identifier, etc.) and could be set by a user using a user interface that spans applicability to multiple profiles (e.g., setting such a setting at the level of a user account, setting such a setting for a group of profiles, etc.).
  • any such other user may be added to a contacts list for the user account in a manner that allows for fluid utilization of the associated user by the first user across profiles.
  • a contact object for the added user is associated with an object representing one of the user profiles of the first user (e.g., the user profile with which the added user discovered the first user, the user profile selected by the first user to initially associate the added user, etc.).
  • a CPOL platform may be configured to allow the first user to later reassociate the added user to a different one of the first user’s user profiles.
  • the term “associate” is not meant to require that the user belongs only to that profile or that the user cannot be used in connection with interactions in a digital platform that relate to another user profile of that user (e.g., a contact list of a CPOL platform can be configured to allow contacts to be used across profiles, such as via a centralized contacts list, even if they are “associated” with a profile).
  • An association of a contact with a profile relates to the outward facing projection of information about the profile owner, such as the profile image, etc.
  • a CPOL platform may be configured to allow a first user to have one contact user associated with a first profile and a second contact user associated with a second profile such that the first user can communicate with both contact users and each of the contact users will be presented information about the first user based on the profile to which the contact user is associated.
  • a first user can have a group conversation (e.g., via a group message room interaction object as described further below) with both the first and second contact users and the first contact user will be presented information about the first user based on the first profile and the second contact user will be presented information about the first user based on the second profile, even though the three users are all communicating in the same group conversation.
  • each of the two contact users in this example will have associated the first user with profiles from their corresponding accounts such that the first user will see them in the group conversation based on their selected profile personas.
  • a profile may include any number of outward facing profile settings.
  • An outward facing profile setting (also referred to herein as a profile object setting) is a setting that allows a user to provide information, an image, or other content that is used in association with a profile to communicate such information, image, or other content to other users of the platform that are associated with the corresponding profile.
  • An outward facing profile setting may also govern one or more interaction preferences for how the user will interact with other users of the platform that are associated with the corresponding profile.
  • a user may project out a particular persona that corresponds to each profile (e.g., different profile information, different profile image, different mood, etc.).
  • An account of a user may include a single profile having one or more outward facing profile settings that can be utilized by a user to establish a particular persona or an account may include multiple profiles each having one or more outward facing profile settings that can be utilized by a user to establish different particular personas.
  • a digital platform such as a CPOL platform of the current disclosure, can utilize the outward facing profile settings of a particular profile for a user to present that user to other users of the platform based on such setting in a way to project the corresponding persona of the user (e g., by governing the way the user is presented to contacts in one or more user interfaces of the platform, by governing the way that contacts of a user are presented the persona of the user via an interaction object, and combinations thereof).
  • Examples of an outward facing profile setting include, but are not limited to, a profile username, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • a visibility setting is a setting that governs an aspect of interacting with a profile related to whether or not a user or certain activity about a user will be viewable and/or findable by other users.
  • Examples of a visibility setting include, but are not limited to, a setting related to a user’s online status, a setting related to a user’s last activity status, a setting related to the availability of typing indicators (e.g., an indicator that a user is typing in a user interface of a CPOL platform), a setting related to the availability of an interaction object read indicator, and any combinations thereof.
  • a mood setting is a setting that allows a user to preselect one or more environment settings for one or more of the user interfaces of a CPOL platform.
  • a mood setting may allow a user to easily project a particular mood that they are experiencing. Having a mood setting at the level of a user profde may allow the projection of different moods depending on the profile (e g., different mood settings in each profile). It is contemplated that a mood setting may alternatively be included at the account level and/or at a level of a privacy governance object (discussed further below).
  • a mood setting impacts an environmental parameter of one or more display interfaces of a CPOL platform that are presented to the user who sets the mood setting (i.e., the user of the user account in which the mood setting is located).
  • a mood setting impacts an environmental parameter of one or more display interfaces of a CPOL platform that are presented to a user with whom the user who sets the mood setting interacts (e.g., via an interaction object, via a profile display). It is contemplated that a mood setting may impact both a display to the user setting the mood setting and a user in which the user setting the mood setting interacts.
  • Examples of a mood setting include, but are not limited to, a shared mood statement setting, a shared mood graphic setting, a display setting, and any combinations thereof.
  • Examples of a display setting include, but are not limited to, a background color, a text color, a font, and any combinations thereof.
  • Examples of a shared mood graphic setting include, but are not limited to, a still image setting, a video image setting, an audio/video setting, a graphic setting, a mood object setting, and any combinations thereof.
  • a mood object is an object that can be presented in association with the display of an interaction object and/or a profile display for a user, the mood object expressing a mood of a user.
  • Examples of a mood object include, but are not limited to, an image, a video object, an audio object, a graphical object, an animation object, a moving image GIF object, and any combinations thereof.
  • a user added as a contact for a first user that is associated with a given profile will interact with the first user governed by the corresponding outward facing profile settings (e.g., will see the corresponding profile image).
  • a contact may also have one or more specific contact settings that govern interaction between the first user and the specific contact. Examples of a contact setting include, but are not limited to, a translation setting, a favorited status, a notification setting, and any combinations thereof.
  • interactions between a first user and a user having contact settings are governed by both the profile settings for the associated profile and the individual contact’s contact settings.
  • the contact setting is applied.
  • the profile setting is applied.
  • a user interface may be provided that allows a user to set priority settings that indicate how a CPOL platform will handle conflicts between different levels of settings.
  • a profile may also include one or more notification settings.
  • a notification setting is a setting that governs one or more aspects of notifications generated by a CPOL platform for presentation to a user (e.g., a user creating the setting, a user interacting with a user creating the setting). Examples of a notification setting include, but are not limited to, an activity occurring on the platform notification setting, a sound notification setting, a new interaction object available setting, a new message segment available indicator, a changed setting indicator, a group member change setting, a group expiration setting, and any combinations thereof. It is contemplated that one or more notification settings may be part of a set of profile object settings in a platform (e.g., such that contacts associated with a particular profile will be governed by such notification settings). It is also contemplated that one or more notification settings may be part of a settings of a privacy governance object (discussed below).
  • such a platform may be configured to allow a user to open as many profiles as they wish with the user being able to define (e.g., by selection of profile discoverability identifiers and/or discoverability settings) how other uses will find them on the platform.
  • Such a platform may also be configured to allow a searched user (one found by a searching user via one of the profile discoverability identifiers) to associate (e g., via an appropriate contact acceptance user interface) the searching user to the profile corresponding to the profile discoverability identifier used by the searching user or to a different profile of the same account that doesn’t have the profile discoverability identifier used by the searching user.
  • a searched user one found by a searching user via one of the profile discoverability identifiers
  • associate e g., via an appropriate contact acceptance user interface
  • a golf buddy finds a user via a profile discoverability identifier that is part of a profile that projects out a more strict business persona of the user (e.g., via profile image, username, other information about the user) and the platform can be configured to allow the user to associate the golf buddy as a contact associated with a different profile that the user has for more casual, personal contexts (e.g., having a more casual profile image, etc.). Additionally, in such a platform, even after a contact is associated with one profile, the platform may be configured to allow a user to change a profile association of a contact.
  • the golf buddy from the example above may become over time a business prospect or client and the user may wish to change the contextual outward facing persona that they project to the golf buddy by changing the association of the golf buddy to their more business oriented contextual profile.
  • a platform can be configured to allow such a change (e.g., via a user interface configured to allow the user to change a profile association of a contact).
  • a user account of a CPOL platform may include one or more privacy governance objects (PGO).
  • PGO privacy governance objects
  • a PGO also referred to herein as a persona governance object
  • a PGO is an object of a CPOL platform that includes one or more configured settings for governing the interaction of users via an interaction object (e.g., a message thread or message room).
  • an interaction object e.g., a message thread or message room.
  • a PGO includes security and privacy settings (e.g., initiator privacy settings) that can easily be used to apply a security/privacy protocol to an interaction object (e.g., with a user initiating an interaction object having control of the security/privacy of the interaction object for all users of the interaction object).
  • Examples of an interaction object for a CPOL platform include, but are not limited to, a message thread, a message room, a calendar item, a document, and any combinations thereof.
  • An interaction object may include subcomponents within the interaction object. Examples of subcomponents include, but are not limited to, a text component, an audio component, a video component, a still image component, a graphical component, a message segment, and any combinations thereof.
  • certain actions that are discussed as being taken with respect to an interaction object may also be taken with respect to a subcomponent thereof (e.g., discussion with respect to restrictions on forwarding an interaction object or with respect to translating an interaction object may also apply to a subcomponent thereof, such as a message segment).
  • an account having more than one PGO may allow a user to establish multiple personas having different preset settings for privacy, security, object retention, personality, and/or other aspects of their lives.
  • different PGO’s can be configured to allow a user to easily start and maintain interactions with different contacts from different aspects of their professional and personal experiences.
  • having different profiles with different outward facing profile object settings allows a user to have different outwardly facing characteristics of their persona portrayed to other users and having multiple PGO’s can allow a user to easily have different privacy and security aspects of their persona utilized with interaction objects.
  • a CPOL platform may be configured to have a single account with multiple profiles (as discussed above) and also have multiple PGO’s within the account such that regardless of profile association of contacts participating in an interaction object (such contacts seeing a user based on profile association), a user of an account can assign a PGO to a given interaction object to govern its privacy and security behavior. It is also contemplated that one or more of the concepts disclosed herein with respect to PGO’s may be part of a CPOL platform that does not include one or more of the disclosures herein related to profiles (e.g., specific discoverability aspects, etc.).
  • a PGO may originate from one of the profiles of a user’s account. Origination of a PGO from a profile means that a user selects a profile from which to originate the PGO and the CPOL platform retains a record of the origination. Origination is not a hierarchical relationship between a PGO and the profile from which it originates. A record of the origination may be done in any form that the CPOL platform can recognize. Examples of a form for recording the origination of a PGO include, but are not limited to, a data element in an object representing the PGO identifying the origination profile, a data table, a data element in an object representing the origination profile identifying the PGO, and any combinations thereof. It is noted that a CPOL platform having PGO’s may be configured such that origination of a PGO from a profile is not required and/or not an option.
  • a user may select a profile from which to originate a PGO using any variety of user interfaces and processes.
  • Examples of a way to select a profile from which to originate a PGO include, but are not limited to, a profile is set in the platform (e.g., automatically, by user selection, and/or by default upon login to the platform) as active and the active profile is the profile from which a PGO originates, a user is presented with a user interface mechanism to select a profile from which to originate a PGO, and any combinations thereof.
  • a user interface of a CPOL platform includes an active profile selector configured to allow a user to select a profile from the one or more profiles of that user’s user account.
  • Any digital platform according to the current disclosure may be configured such that one profile (e.g., of multiple profiles) in a user account is set to active, such as, for example, by an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • An active profile being set in an account may have a variety of functions, including, but not limited to, filtering a contact list to the contacts associated with that profile, filtering a list of interaction objects to those including a user that is associated with that profile, having one or more profile object settings (e.g., a notification setting) be active, allowing a user to be within a given context in one or more user interfaces of their account (e.g., to bw within a business oriented context associated with a centrally managed/administered profile), one or more other functions, and any combinations thereof.
  • profile object settings e.g., a notification setting
  • a PGO not being tethered to a profile allows a PGO to be used by a user for interactions stemming from a profile different from the originating profile, for interactions with other users associated with a profile different from the originating profile, and/or for interactions that initiate while a profile other than the originating profile is set in a user interface of a CPOL platform as an active profile.
  • a user account includes two or more PGO’s (each of which may or may not originate from a particular profile of that user account), each of the two or more PGO’s being useable across multiple profiles of the user account.
  • a user account of a CPOL platform may include two or more PGO’s (each of which may or may not originate from a particular profile of that user account), wherein one or more PGO’s are useable across multiple profiles of the user account and one or more other PGO’s are restricted to be useable only with a specific profile (e g., a centrally managed profile of an employer of a user).
  • a PGO may include a set of initiator privacy settings.
  • An initiator privacy setting is a setting that governs the privacy and/or security behavior and environment of an interaction object initiated by a user.
  • An initiating user is the user that starts an interaction object (e.g., who starts a message thread or group message room). Other users of an interaction object are referred to as recipient users (even if they later add message segments to the same interaction object).
  • recipient users even if they later add message segments to the same interaction object.
  • it is the initiating user (and corresponding association of an initiating user’s PGO to an interaction object) that governs the security and privacy settings for an interaction object initiated by that initiating user.
  • a CPOL platform may be configured to allow an initiating user of a given interaction object to change a PGO association with that interaction object after it is created such that a new set of initiator privacy settings will apply (as described further below).
  • a CPOL platform may be configured to create a notification to recipient users when a PGO association is changed (e.g., with a notification of new privacy and/or security rules that may apply).
  • an initiating user can initiate an interaction object, such as a message thread with a recipient contact user.
  • a PGO of the initiating user can be associated with the interaction object.
  • a PGO of each recipient user may also be associated with the interaction object.
  • a digital platform may retain a record of an association of a PGO with an interaction object (e.g., to allow for application of a PGO’s settings to the interaction object as described herein).
  • the PGO of the initiating user governs which initiator privacy settings apply to the interaction object.
  • the initiator privacy settings of the associated PGO of the recipient users do not govern the interaction object.
  • the initiating user can change the PGO assignment of the interaction object, at which point the initiator privacy settings of the newly assigned PGO will govern the interaction object.
  • any subcomponents of the interaction object e.g., message segments within a message thread/room
  • any subcomponents of the interaction object e.g., message segments within a message thread/room
  • a PGO may be pre-configured by a CPOL platform to have one or more default values for an initiator privacy setting and/or a PGO recipient setting (described further below.
  • a user may be presented with a user interface for creating a new PGO in which one or more of the initiator privacy settings and/or PGO recipient settings is preset with a value. The user may then be presented with a user interface for selecting and/or providing a changed value for a preset/ default value.
  • a user account may include one or more preset PGO’s for a user in which one or more of the initiator privacy settings and/or PGO recipient settings is preset with a value.
  • a CPOL platform may be configured to have one or more default values for one or more profile object settings of a profile.
  • a user may be presented with a user interface for creating a new profile in which one or more of the profile object settings is preset with a value.
  • the user may then be presented with a user interface for selecting and/or providing a changed value for a preset/default value.
  • a user account may include one or more preset profiles for a user in which one or more of the profile object settings is preset with a value. The user may then be presented with a user interface for selecting and/or providing a changed value for a preset/default value.
  • Examples of an initiator privacy setting include, but are not limited to, an interaction object expiration, a forwarding setting, a side chat setting, an encryption setting, a screen capture setting, a forwarding request setting, a calendar event sharing limitation, a storage limitation or setting, an archive setting, a retention setting, and any combinations thereof.
  • An interaction object expiration setting is a setting governing a time period for automatic deletion of an interaction object (e.g., within a certain time period from creation, within a certain time period from being read by a recipient, and any combinations thereof).
  • a forwarding setting is a setting restricting and/or allowing a certain level of forwarding of an interaction object (e.g., allowing no forwarding, allowing all forwarding, allowing only forwarding to a set of users, and any combinations thereof).
  • a side chat setting is a setting governing the behavior and/or allowability of a side chat associated with an interaction object, such as a group messaging room/thread (e.g., a setting related to how long a side chat exists before deletion, etc.). Side chat concepts are discussed further below.
  • An encryption setting is a setting governing a level of encryption applied to an interaction object. An encryption setting may also be at an account level (an account wide setting).
  • a screen capture setting is a setting governing the allowability or restriction of the ability to screen shot/screen capture while an interaction object is displayed via a user interface of a CPOL platform.
  • a forwarding request setting is a setting related to a functionality of requesting an ability to forward an otherwise forward restricted interaction object. Forwarding request concepts are discussed further below.
  • a calendar event sharing limitation is a setting that governs an aspect of sharing of a calendar-related interaction object (e.g., which users can interact with a calendar related interaction object, which portions of an interaction object are shared, and any combinations thereof).
  • a storage limitation or setting is a setting related to the storage of an interaction object or other information (e.g., mandatory storage of an interaction object, method of storage, location of storage (e.g., on a local device, on a cloud resource or other centralized storage facility, etc.), backup storage requirements, and any combinations thereof).
  • a retention setting is a setting related to the retention period for an interaction object or other information (e.g., minimum retention time, maximum retention time, whether or not an interaction object is kept and/or stored and/or archived, and any combinations thereof).
  • a storage setting, a retention setting, and/or one or more other settings may be managed by an administrator of a profile from which a PGO originates (e.g., a PGO originating from a business owned profile).
  • a business entity may be allowed to administer a profile that is accessed and used by an employee or other user who also has personal profiles associated with their CPOL platform account.
  • a user account may include one or more profiles that a user fully manages (e.g., personal, individual business context, social, etc.) and also one or more centrally managed profiles that are controlled at least in part by a third-party (e.g., a business with which a user is employed or otherwise associated may allow a user to add a centrally managed profile to their account, such as one related to their job, in which the business administers certain PGO’s, settings, and/or other aspects of the profile and interaction objects that are associated with the profile (e.g., via starting from the profile, via being associated with a PGO originating from the profile, via being with contacts associated with the profile, and combinations thereof). Additional aspects of centralized administration are discussed further below.
  • a storage setting may exist in a CPOL platform in whole or in part at a profile level (e.g., such that a storage aspect of an interaction object is governed in a consistent manner for all interaction objects associated with a profile, such as by being with a contact of that profile and/or being started when such profile is set to active in the platform for a user).
  • a profile may have a storage setting indicating that interaction objects are to be stored on a cloud resource (e.g., instead of or in addition to on a user computing device) such that any interaction object with a contact associated with a given profile and/or any interaction object started by a user while a given profile is active in their account will be stored according to the storage setting of that given profile.
  • a CPOL platform may be configured such that any setting in a CPOL platform can be configured to allow a user to set one or more exceptions (i.e., a situation in which the setting will not apply as set and/or has a different value such as having exclusions and/or additions) to the setting.
  • a setting may be set to do a particular action and an exception can be set to have that action not take place for a particular situation, such as for a specific interaction object.
  • a setting may be set to not do a particular action and an exception can be set to have that action take place for a particular situation.
  • a profile may have a storage setting set to have all interaction objects associated with the profile be stored in a cloud resource and also have one or more exceptions set by a user, such as to store one or more specific group interaction objects locally on a user device (i.e., not stored in the same cloud resource).
  • a PGO may include a set of PGO recipient settings.
  • a recipient setting is a setting that governs the display and general behavior of an interaction object as that interaction object is presented to a user whose user account includes the PGO having the PGO recipient setting.
  • Examples of a PGO recipient setting include, but are not limited to, a translation setting, a notification setting, a group notification setting, a display setting, a language setting, and any combinations thereof.
  • a translation setting is a setting related to a translation functionality for a display of an interface of a CPOL platform and/or for content of an interaction object.
  • Examples of a translation setting include, but are not limited to, an on/off setting for a translation functionality, an automatic translation setting (e.g., on/off, language of translation), a request for translation setting, a language of translation setting, an interface language setting, a spoken language setting, a language of incoming message segments or other interaction object types that are to be translated setting, a language to which a translation is to occur setting, and any combinations thereof.
  • One or more translation settings may also be located at a profile or account level.
  • FIG. 30 illustrates one example of a display screen functionality of a CPOL platform for allowing a user to enter values for settings of various types.
  • a settings display screen 3005 includes user actuatable controls (each shown a user actuatable button with a textual description (and optionally a graphical icon) and a right facing arrow graphic) configured to allow a user to select to navigate to an additional screen where one or more relevant settings (e.g., those discussed herein) can be set, viewed, edited, etc. by a user.
  • the user actuatable controls include those for account settings 3010; profile settings for each profile in the account (in this example two profiles: John Smith (business) 3015 and John Smith (Personal) 3020); a create a new profile button 3025 (for creating a new profile and setting appropriate settings); PGO settings (in this example platform PGO’s are referred to as “zones” and the account includes settings buttons for three preset zones: The Keeper Zone 3030, The Middle Zone 3035, and the Brief Zone 3040); a create a new “Zone” (PGO) button 3045 (for creating a new PGO and setting relevant settings); side chat settings 3050 (for settings specific to the operation of side chats that are not already included in a PGO setting or elsewhere in a system); parallel chat settings 3055 (for settings specific to the operation of parallel chats that are not already included in a PGO setting or elsewhere in a system); and moods (backgrounds) settings 3060.
  • account settings 3010 for each profile in the account (in this example two profiles: John Smith
  • PGO three “Zones”
  • one such preset zone can include the most strict and protective initiator privacy settings
  • another preset zone can include more lax and less protective initiator privacy settings
  • a third middle zone can include a balance set of initiator privacy settings.
  • such preset PGO’s may assist a new user in easily utilizing flexibility and security of messaging, interacting, and managing lifestyle activities to which they associate PGO’s to relevant interaction objects.
  • a CPOL platform may be configured to allow a user to add additional PGO’s for specific needs and requirements and/or to replace the settings of a preset PGO.
  • an initiating user has a user account with multiple profiles and multiple PGO’s.
  • the initiating user initiates an interaction object with a contact user associated with a first profile of their user account.
  • This contact user sees the initiating user in the user interfaces of the exemplary CPOL platform (e.g., when discovering the initiating user, when viewing profile information, when interacting via an interaction object, etc.) based on the profile object setting for the first profile.
  • the first profile for the initiating user may be focused on a business aspect of the initiating user’s life and projects a professional image to contacts (e g., via a professional looking profile picture).
  • a first PGO of the initiating user is associated with the interaction object.
  • the first PGO may be one with stricter privacy and security settings relevant to the specific business relationship with the contact user.
  • the contact user may be involved with a recreational activity with the initiating user and even though the initiating user wishes to continue to project out the professional appearances of the first profile, the recreational activity allows for lesser security and privacy settings of a different PGO.
  • a user can have multiple profiles in the same account (e.g., one professional and another casual) and use different profiles to project out different outward persona characteristics and also have one or more PGO’s (e.g., that can be used across profiles and/or are tied to a particular profile) that allow the user to easily set security and privacy settings that are particular to a given interaction object.
  • the contact user also has a user account with multiple profiles and multiple PGO’s.
  • the contact user has associated the initiating user with a profile from their account that projects a more casual image of the contact user to the initiating user via the corresponding profile object settings.
  • a PGO from the contact user’s account is associated with the interaction object in this example.
  • the interaction object is governed by the initiator privacy settings from the initiator’s PGO for both users.
  • the PGO recipient settings from the initiating user’s associated PGO apply.
  • the PGO recipient settings from the contact user’s associated PGO apply.
  • a user of that platform may need to (and/or be required to) enter a selection and/or information to be used by the platform. This entry can be done by any known or later developed mechanism for making a selection or entering information into a digital platform. Examples and further discussion of user interfaces are discussed further below
  • one or more embodiments of a contextualized privacy online lifestyle platform and related methods according to the current disclosure may be implemented across a plurality of computing devices, for example over one or more networks.
  • components of a platform are located on one or more centralized computer devices (e.g., a cloud resource) and users of the platform access the one or more centralized computer devices via one or more networks.
  • Such access may be by any well-known mechanism or mechanisms.
  • Examples of such mechanisms include, but are not limited to, Internet connectivity using a web-based application user interface (e.g., using an Internet browsing application on a user device), application software running on a user device that connects to the platform over a network, private network connection, peer-to-peer connectivity, other known distributed and centralized systems, and any combinations thereof.
  • machine-executable instructions exist on one or more centralized computer devices and each user of the platform utilizes a local application program and/or a web-based interface to connect to the one or more centralized computer devices.
  • a user can download a user application program that is a part of the platform from a mobile operating system application store (e.g., an Apple iOS store, an Android application store, etc.), from one of one or more centralized computer devices of the platform, from a desktop application repository (e.g., a Microsoft app store, a website of a platform operator, etc.), or from another downloadable resource center.
  • a mobile operating system application store e.g., an Apple iOS store, an Android application store, etc.
  • desktop application repository e.g., a Microsoft app store, a website of a platform operator, etc.
  • a user application program may be acquired in a form that requires installation on a computing device (e.g., an executable installation file).
  • a user may acquire a local application program for a CPOL platform via other channels, such as acquiring the local application program on a physical machine readable medium (e g., via ecommerce purchase and physical deliver, via purchase at a brick-and-mortar retail outlet, etc.).
  • a user application program may include machine executable instructions stored in the user computing device that interacts with operating system components and hardware components of the user computing device to communicate over a network to the centralized portions of a CPOL platform of the current disclosure and to execute such instructions to provide one or more user interfaces of the CPOL platform to the user and execute portions of one or more of the aspects of a CPOL platform and related methods as disclosed herein.
  • FIG. 1 illustrates one example of a diagrammatic illustration of an exemplary network disbursed implementation 100 that can be utilized for a contextualized privacy online lifestyle platform and related methods.
  • Implementation 100 has its components disbursed across physical components (e.g., memory elements, processors, etc.) of one or more platform computing devices 105 and user computer devices 110 and 115.
  • Computer devices 105, 110, and 115 are connected via networks 120, 125.
  • a portion of the contextualized privacy online lifestyle platform (“CPOL platform”) is stored in a memory of computing device 105 for execution by a processor of device 105 and communication with one or more of user computers (such as computers 110, 115) on which a portion (e.g., a client portion) of the CPOL platform is stored (e.g., via a memory) and executed (e.g., via a processor).
  • CPOL platform the contextualized privacy online lifestyle platform
  • programmatic elements (as described herein) of a CPOL platform are downloaded to a client portion on computer 110, 115 from computer 105 (or other source) with executable programming running on a processor of computer 110, 115 and a displayable and interactive portion being run at the client portion on computer 110, 115.
  • CPOL platform 100 is shown with optional user application portion 130 (on user computing device 110) and user application portion 135 (on user computing device 115).
  • a majority of a CPOL platform is stored and processed on computer 105 with displayable interactions being communicated to one or more of client computers 110, 115. Examples of computing devices, networks, and other related components are discussed below.
  • Interaction objects may be communicated between user computer devices in a CPOL platform or other digital platform (e.g., via one or more server computers.
  • an interaction object may be transmitted from user computer 110 via network 120 to platform computer 105, then transmitted from computer 105 via network 125 to user computer 115 where one or more aspects of the interaction object may be displayed to a user of computer 115.
  • the interaction object is not stored at platform computer v05 for more than a time period needed to transmit it to one or more user computers (such as computers 110, 115).
  • FIG. 2 illustrates an exemplary implementation of a user account 205 of a CPOL platform according to the current disclosure.
  • User account 205 includes an associated third-party standard unique identified 10, account level settings 215, and multiple user profiles 220, 225, and 230. While this example includes three user profiles, it is contemplated that a user account may have any number of one or more user profiles.
  • FIG. 3 illustrates an exemplary implementation of user profiles 305 and 310 of a user account (such as user account 205 of FIG. 2) of a CPOL platform.
  • the user profiles shown in FIG. 3 include one or more profile discoverability identifiers 315 for profile 305 and one or more profile discoverability identifiers 320 for profile 310.
  • profile discoverability identifiers 315 include an email address and a phone number and profile discoverability identifiers 320 include a username that is not a third-party standard unique identifier.
  • Profile 305 includes discoverability settings 325 and profile 310 includes discoverability settings 330.
  • Profile 305 includes profile object settings 335 and profile 310 includes profile object settings 340.
  • FIG. 4 illustrates another exemplary implementation of a user account 405 of a CPOL platform according to the current disclosure.
  • User account 405 includes an associated third-party standard unique identifier410, account level settings 415, and multiple user profiles 420, 425, and 430.
  • User account 405 also includes multiple PGO’s 435 and 440.
  • PGO 435 originates from user profile 420 and PGO 440 originates from user profile 430.
  • PGO’s 435 and 440 do not originate from a specific user profile.
  • PGO 435 originates from user profile 420 and PGO 440 does not originate from a specific user profile.
  • PGO’s 435 and 440 may be utilized for interaction objects across user profiles (e.g., utilized with interaction objects with contact users that are associated with different user profiles). It is also contemplated that a PGO (e.g., PGO 435 in the example where it originates from profile 430) may be restricted to only being used with contacts associated with an originating profile.
  • User account 405 also includes a set of contacts 445. In one example, each contact user is associated with one of user profiles 420, 425, and 430.
  • the contact association may be configured such that a contact associated with one profile may be utilized with interaction objects that are associated with a PGO that originates from a different profile and/or that are associated with initiation while another profile is set to active in one or more user interfaces of the corresponding CPOL platform.
  • the fluidity of contacts and PGO’s across profiles allows for flexible usage of the different security and privacy settings of different PGO’s while still projecting out the associated image of a different profile that is associated with a given contact.
  • FIG. 5 illustrates an exemplary implementation of a set of PGO’s 505 and 510 of a user account of a CPOL platform according to the current disclosure.
  • PGO 505 includes a set of initiator privacy settings 515 and PGO 510 includes a set of initiator privacy settings 520.
  • PGO 505 includes a set of PGO recipient settings 525 and PGO 510 includes a set of PGO recipient settings 530.
  • FIG. 6 illustrates an exemplary implementation of an interaction object 605 that is initiated by initiating user 610 (“initiating user A”) with contact user 615 (“contact user 1”).
  • an interaction object may include multiple recipient contact users (e.g., a group message thread/room).
  • Interaction object 605 is associated with one of initiating user A’s (610) PGO’s 620 from initiating user A’s user account.
  • PGO 620 includes initiator privacy settings 625 and PGO recipient settings 630.
  • Initiator privacy settings 625 govern the privacy and security of interaction object 605 throughout the corresponding CPOL platform.
  • PGO recipient settings 630 govern the display and interaction with initiating user 610 of interaction object 605.
  • FIG. 7 illustrates another exemplary implementation of an interaction object 705 that is initiated by initiating user 710 (“initiating user A”) with contact user 715 (“contact user 1”).
  • an interaction object may include multiple recipient contact users (e.g., a group message thread/room).
  • Interaction object 705 is associated with one of initiating user A’s (710) PGO’s 720 from initiating user A’s user account.
  • PGO 720 includes initiator privacy settings 725 and PGO recipient settings 730.
  • Initiator privacy settings 725 govern the privacy and security of interaction object 705 throughout the corresponding CPOL platform.
  • PGO recipient settings 730 govern the display and interaction with initiating user 710 of interaction object 705.
  • Interaction object 705 is associated with PGO 735 from the user account of recipient contact user 715.
  • PGO 735 has its own initiator privacy settings, those settings are not applied to interaction object 705, which is governed by the initiator privacy settings 725 of PGO 720 of initiating user 710.
  • PGO 735 includes PGO recipient settings 740, which are associated with interaction object 705 for governing the display and interaction with recipient contact user 715 with interaction object 705.
  • FIG. 8 illustrates yet another exemplary implementation of an interaction object 805 that is initiated by initiating user 810 (“initiating user A”) with contact user 815 (“contact user 1”).
  • Interaction object 805 is a message thread/room between initiating user 810 and contact user 815.
  • the message room includes the subcomponents of multiple message segments 820, 825, .. . , 830.
  • message segments 820, 825, 830 alternate as being initiated by user 810 and contact user 815.
  • message segments 820, 825, ..., 830 are initiated in any combination of orders by initiating user 810 and contact user 815.
  • Message room 805 is associated with a set of initiator privacy settings 835 from a PGO from initiating user 810’s user account.
  • the set of initiator privacy settings 835 govern each of message segments 820, 825, .. ., 830.
  • each of message segments 820, 825, . . ., 830 are tagged with one or more of the settings of the set of initiator privacy settings 835.
  • FIG. 9 illustrates yet another exemplary implementation of an interaction object 905 that is initiated by initiating user 910 (“initiating user A”) with contact user 915 (“contact user 1”).
  • Interaction object 905 is a message thread/room between initiating user 910 and contact user 915.
  • the message room includes the subcomponents of multiple message segments 920, 925, .. ., 930.
  • message segments 920, 925, . . ., 930 alternate as being initiated by user 910 and contact user 915.
  • message segments 920, 925, 930 are initiated in any combination of orders by initiating user 910 and contact user 915.
  • Message room 905 is associated with a set of initiator privacy settings 935 from a PGO from initiating user 910’s user account at the time of initiating message room 905.
  • the set of initiator privacy settings 935 govern message segment 920, which is created by initiating user 910.
  • initiating user 910 changes the association of message room 905 from one PGO to another PGO from initiating user 910’s user account.
  • Message segments 925, . . ., 930 which are created after the changed PGO association, are associated with a different set of initiator privacy settings 940 from the new PGO associated with message room 905 from initiating user’s user account.
  • FIG. 10 illustrates another exemplary implementation of a user account 1005 according to the current disclosure.
  • User account 1005 includes an associated third-party standard unique identifierlOlO for identifying an account user of user account 1005 (e.g., a user of a CPOL platform as discussed herein).
  • User account 1005 also includes account level settings 1015 for allowing a user to input one or more settings configurations governing aspects of their use of a CPOL platform that impact usage across multiple profiles.
  • User account 1005 is configured to have multiple user profiles. As shown in figure 10, user account 1005 includes three user profiles 1020, 1022, and 1024.
  • Different users of a digital platform may setup different numbers of profiles when the platform is configured to allow for multiple profiles.
  • the account user of user account 1005 has setup three user profiles (e.g., via inputs and/or selections using one or more user interfaces of the corresponding platform).
  • One possible use of multiple profiles is to allow the account user to project out to other users of the platform different impressions and characteristics of the account user.
  • an account user may choose to set up profile 1020 as a personal profile to project a casual image and profiles 1022 and 1024 as different professional profiles to project out different variations of career related images.
  • user profile 1024 may be a centrally administered profile (e.g., a profile managed by an employer of the account user).
  • a centrally administered profile may include one or more restrictions on settings (such as having a privacy and security setting controlled by the central administrator) such that the account user has limited flexibility with respect to such settings.
  • Each of user profiles 1020, 1022, and 1024 are configured to allow the account user to associate with each profile one or more profile discoverability identifiers 1030, 1032, and 1024, respectively.
  • a profile e.g., profile 1024
  • the administrator may have one or more rules governing the type of profile discoverability identifier to be utilized. For example, an administrator that is an employer of the account user may require the account user to use an employer related third-party standard unique identifier (e.g., an employer provided email address, an employer provided phone number, etc.) and/or an employer related platform specific identifier.
  • Each of user profiles 1020, 1022, and 1024 are configured to allow the account user to associate with each profile one or more discoverability settings 1040, 1042, and 1044 and one or more profile object settings 1050, 1052, 1054, each respectively.
  • Other users of the digital platform of user account 1005 may find the account user for account 1005 if they know and use one of the profile discoverability identifiers the account user associates with one of profiles 1020, 1022, and 1024 (i.e., the other user utilizes a search interface of the digital platform to input an identifier that matches one of the discoverability identifiers 1030, 1032, and/or 1024).
  • the discoverability of an account user by other users is further governed by the one or more discoverability settings 1040, 1042, and 1044 associated with the particular profile.
  • a digital platform’s user accounts may be alternatively configured to have discoverability settings be set as part of account level settings (e.g., account level settings 1015) and apply to the discoverability of more than one profile or all profiles.
  • Such users that connect with the account user are added to the contacts 1060 of account 1005.
  • Each contact user associated with a user account, such as account 1005 may be associated with the profile with which the contact user discovered the account user.
  • each contact user of contacts 1060 is associated with the profile with which the contact user discovered the account user of user account 1005.
  • a digital platform may be configured with one or more user interfaces that allow an account user to change a profile to which a contact user is associated after an original association.
  • a user associated with a particular profile will view and be presented information about an account user based on the profile object settings of the corresponding profile.
  • user account 1005 contact users Cl and C2 are shown as being associated with user profile 1020, contact user C3 is shown being associated with user profile 1022, and contact user C4 is shown being associated with user profile 1024. It is contemplated that a user account may have any number of contact users that are appropriate for a particular digital platform associated with a user profile.
  • a contact user can be utilized with interaction objects across user profiles (e.g., be used with an interaction object initiated while another profile is active in a user interface of a digital platform, be used with an interaction object that is associated with a PGO that originates from another profile, etc.).
  • one or more of profiles 1020, 1022, and 1024 may be limited (e.g., be a centrally administered profile) such that a contact user that is associated with that profile may only be utilized with that profile (e.g., be used with an interaction object initiated while that profile is active in a user interface of a digital platform, be used with an interaction object that is associated with a PGO that originates from that profile, etc.).
  • User account 1005 includes four PGO’ s 1070, 1072, 1074, and 1076.
  • a PGO may originate from a user profile.
  • each of PGO’ s 1070, 1072, 1074, and 1076 originate from one of user profiles 1020, 1022, and 1024.
  • one or more of PGO’ s 1070, 1072, 1074, and 1076 originate from one of user profiles 1020, 1022, and 1024.
  • none of PGO’s 1070, 1072, 1074, or 1076 originate from one of user profiles 1020, 1022, and 1024.
  • a digital platform may be configured to allow a PGO to be utilized across profiles (e.g., be associated with an interaction object that is initiated when a profile other than the profile from which the PGO originates is set to an active status for a user account, be associated with an interaction object that includes a contact that is associated with a profile other than the profile from which the PGO originates, etc.).
  • one or more PGO of a user account may be configured in a digital platform (e.g., a PGO that originates from a centrally administered profile) to be limited to use in one or more aspects with the profile from which it originates.
  • user account 1005 and the corresponding digital platform may be configured such that PGO1076 originates from user profile 1024 (in an example where user profile 1024 is a centrally administered profile wherein PGO 1076 may only be utilized with user profile 1024, but such that PGO’s 1070, 1072, and 1074 can be utilized across user profiles 1020 and 1022.
  • Each of PGO’s 1070, 1072, 1074, and 1076 include a set of initiator privacy settings 1080, 1082, 1084, and 1086 and a set of PGO recipient settings 1090, 1092, 1094, and 1096, each respectively.
  • the corresponding initiator privacy settings 1080, 1082, 1084, or 1086 govern the privacy and security of that interaction object across the digital platform (e.g., regardless of which of a recipient user’s PGO’s are associated with the interaction object).
  • the account user for user account 1005 interacts with an interaction object with the corresponding PGO recipient settings 1090, 1092, 1094, or 1096 of the PGO 1070, 1072, 1074, or 1076 that is associated with the interaction object applying to such interaction with the interaction object.
  • user account 1005 One example configuration for a user account of an exemplary CPOL platform, such as user account 1005, is now described using user account 1005.
  • This example configuration is only demonstrative of one way to configure user account 1005 with other configurations being possible. It is also contemplated that variations and additions to the particular choices for this example configuration will be understood as possible at one or more of the settings locations (e.g., additional settings, having a particular setting associated with a different object, omission of a setting, etc.).
  • user account 1005 is configured to accept a telephone number (e.g., a mobile telephone number as third-party standard unique identifierlOlO.
  • the account user provides a mobile telephone number to a CPOL platform during setup of user account 1005 via a user interface provided to the account user by the CPOL platform.
  • a third-party standard unique identifier e.g., a mobile phone number, an email address, etc.
  • account level settings 1015 include a set of language and translation settings (e g., a language for display interfaces, one or more languages spoken by the account user, a preferred language for an automated translation functionality (such as for use with interaction objects)), general settings, permissions settings, security settings, and other settings pertinent to an account level.
  • each of profiles 1020, 1022, and 1024 are configured to allow an account user to enter one or more of an email address, a mobile phone number, and a username for each of profile discoverability identifiers 1030, 1032, and 1034.
  • an account user may utilize the same email address or phone number in more than one profile while the platform requires that the username for each profile be unique to the platform.
  • a digital platform requires that an account user use different email addresses, different phone numbers, and different usernames in each of the user profiles in a user account.
  • Discoverability settings 1040, 1042, and 1044 in this example configuration include a degree of separation setting.
  • Profile object settings 1050, 1052, and 1054 in this example configuration include multiple privacy and visibility settings (including a setting related to a user’s online status, a setting related to a user’s last activity status, a setting related to the availability of typing indicators, a setting related to the availability of an interaction object read indicator), a translation setting, a profile image, a notification setting, and a display setting.
  • privacy and visibility settings including a setting related to a user’s online status, a setting related to a user’s last activity status, a setting related to the availability of typing indicators, a setting related to the availability of an interaction object read indicator), a translation setting, a profile image, a notification setting, and a display setting.
  • each of PGO’s 1070, 1072, 1074, 1076 originates from one of user profiles 1020, 1022, and 1024.
  • Initiator settings 1080, 1082, 1084, 1086 in the example configuration include a side chat setting, an interaction object expiration setting, and an interaction object forwarding setting.
  • PGO recipient settings 1090, 1092, 1094, 1096 in the example configuration include an automatic translation setting (e.g., an on/off setting), a notification setting (e.g., a new interaction object available setting, a new message segment available indicator, a changed setting indicator), and a group notification setting (e.g., a new interaction object available setting, a new message segment available indicator, a changed setting indicator, a group expiration notification, and a new group member notification).
  • an automatic translation setting e.g., an on/off setting
  • a notification setting e.g., a new interaction object available setting, a new message segment available indicator, a changed setting indicator
  • a group notification setting e.g., a new interaction object available setting, a new message segment available indicator, a changed setting indicator, a group expiration notification, and a new group member notification.
  • a user account may include multiple profiles, each of which having one or more profile discoverability identifiers.
  • another user of the platform can utilize an interface of the platform to request a search of the platform using a search identifier (e.g., provided by the searching user via the interface). If that search identifier matches a profile discoverability identifier of one or more profiles of another user, the platform may provide one or more interfaces to the searching user to allow the searching user to associate a matching profile of the searched user with their user account (e.g., associating the searched user with a profile of the searching user’s account).
  • the searched user may have settings in the matching profile’s discoverability settings (or elsewhere in their account in alternate implementations) that limit which searching users are allowed by the platform to discover the searched user, notwithstanding the matching of the search identifier with one of the profile discoverability identifiers of the searched user.
  • settings include, for example, limitations on being discovered only by searching users that are also contacts of an existing contact of the searched user (or other degrees of separation, such as contacts of contacts of an existing contact, etc.), and limitations on which type (and/or particular one) of the searched user’s profile discoverability identifiers can be used to discover that profile.
  • a digital platform may be configured to take a no search match response.
  • Examples of a no search match response include, but are not limited to, presenting an indication to the searching user that the searched user is not a member of the platform, presenting an indication to the searching user that the searched user was not discovered, presenting an indication to the searching user that the searched identifier was not found, presenting a null indicator (e.g., a searching user does not get a specific indication (e.g., gets a generic not discovered response) that a user was not findable based on a profile discoverability identifier or that the searched user declined a connection with the searching user), and any combinations thereof.
  • a null indicator e.g., a searching user does not get a specific indication (e.g., gets a generic not discovered response) that a user was not findable based on a profile discoverability identifier or that the searched user declined a connection with the searching user
  • a searching user may not meet a degree of separation requirement in a profile discoverability setting of a searched user (e g., the searching user is not a contact of a contact of the searched user) and the searching user is presented by a user interface of a digital platform a similar response to if the searched user didn’t exist (e.g., no indicator that the searched user is actually a user of the platform).
  • a searched user may decline to be a contact of a searching user and the searching user is presented by a user interface of a digital platform a similar response to if the searched user didn’t exist (e.g., no indicator that the searched user is actually a user of the platform).
  • a digital platform may be configured to present a connect request to a searched user when a match of a search identifier with a profile discoverability identifier is otherwise disallowed by one or more of the searched user’s profile discoverability settings.
  • a digital platform may check a particular search identifier, other aspects of a search request, and/or the searching user against one or more discoverability settings during a matching process.
  • Example times for such a check include, but are not limited to, before checking if a search identifier matches a profile discoverability identifier (e.g., where a profile discoverability setting relates to an aspect of a search request that is independent of whether a search identifier matches a profile discoverability identifier, such as a degree of separation setting or other setting related to the searching user), after checking if a search identifier matches a profile discoverability identifier, and any combination thereof.
  • a connect request would include a presentation to the searched user (e.g., via one or more user interfaces) that the searching user had searched the searched user and a match was disallowed by one or more settings.
  • Such a connect request would include an option for the searched user to select to connect with the searching user via associating the searching user with one of the searched user’s profiles (i.e., having the searching user become a contact associated with that profile) or reject the connection. If the searched user rejects the connection, the digital platform takes a no search match response.
  • the option to select is limited to the user profile that included the profile discoverability identifier that matches the search identifier.
  • the option to select includes the user profile that included the profile discoverability identifier that matches the search identifier and at least one additional profile of the searched user’s account (e.g., an option to select to associate the searching user to one from two or more profiles that are a subset of all the profiles of the user account or an option to select to associate the searching user to one from all the profiles of the user account).
  • a digital platform includes a user setting for governing which user profiles can be utilized in a connect request (e.g., a setting at an account level, a setting at a profile level, a setting at some other location in a digital platform).
  • Such a user setting may include a default value and/or be settable by a user (e.g., a searched user) at a time prior to being searched by other users.
  • a digital platform may be configured to present a connect request to the searched user as part of the matching process.
  • a connect request would include a presentation to the searched user (e.g., via one or more user interfaces) that the searching user had searched the searched user and (optionally, that a match was found to a profile and/or a profile discoverability identifier).
  • Such a connect request would include an option for the searched user to select to connect with the searching user via associating the searching user with one of the searched user’s profiles (i.e., having the searching user become a contact associated with that profile) or reject the connection.
  • the digital platform takes a no search match response.
  • the option to select is limited to the user profile that included the profile discoverability identifier that matches the search identifier.
  • the option to select includes the user profile that included the profile discoverability identifier that matches the search identifier and at least one additional profile of the searched user’s account (e.g., an option to select to associate the searching user to one from two or more profiles that are a subset of all the profiles of the user account or an option to select to associate the searching user to one from all the profiles of the user account).
  • a digital platform includes a user setting for governing which user profiles can be utilized in a connect request (e.g., a setting at an account level, a setting at a profile level, a setting at some other location in a digital platform).
  • a user setting may include a default value and/or be settable by a user (e.g., a searched user) at a time prior to being searched by other users.
  • Additional settings may exist that govern how a digital platform determines to present a connect request to a searched user (e.g., in a digital platform configured to present a connect request after a setting disallows a match, in a digital platform configured to present a connect request after matching a search identifier to a profile discoverability identifier, in a digital platform configured for both approaches).
  • Such additional settings include, but are not limited to, a setting turning on/off a feature to present a connect request upon matching, a setting turning on/off a feature to present a connect request upon disallowed matching due to a user setting, a setting indicating which profile discoverability setting will result in a connect request if the profile discoverability setting disallows a match, and any combinations thereof.
  • a setting may be included at an account level, a profile level, or some other location within a digital platform.
  • a searched user that is allowed to interact with a searching user may also be associated with a profile of the searching user’s account. Associating a searched user with a searching user’s profile may occur by one or more of a variety of mechanisms and approaches.
  • Examples of ways for a searched user to be associated with a searching user’s profile include, but are not limited to, associating a searched user with the searching user’s profile that is active in the searching user’s account at the time of the searching user initiating a search request, presenting via a user interface to the searching user with an option to select one of the searching user’s profiles to which to associate a searched user (e.g., at the time of the initiation of the search request, after the searched user allows a request to connect, after a platform finds a match to a search request by the searching user, etc.), associating the searched user with a default profile of the searching user (e g., a default set by the searching user, a default of a corresponding digital platform), and any combinations thereof.
  • a default profile of the searching user e.g., a default set by the searching user, a default of a corresponding digital platform
  • a searched user will interact with a searching user based on the profile to which the searching user associates the searched user (e.g., in interactions on the corresponding digital platform that involve the searched user and the searching user, information about the searched user will be presented to the searched user based on one or more of the profile object settings corresponding to the associated profile).
  • FIG. 1 1 illustrates one exemplary implementation of a method for discovering a user on a digital platform 1100.
  • method 1100 includes associating one or more profile discoverability identifiers with each user profile of a user account (e.g., user account 205 of FIG. 2, user account 405 of FIG. 4, user account 1005 of FIG. 10, etc.).
  • the corresponding platform is configured to require at least one profile discoverability identifier for each profile.
  • a digital platform may be configured such that the multiple profile discoverability identifiers may be different types of identifiers (e.g., phone number, email address, username, etc.), to allow a profile to be created without use of a third-party standard unique identifier as a profile discoverability identifier (e.g., by use of only a platform specific identifier even in examples where other types of identifiers are optional), and/or to require that a profile discoverability identifier of one type in a first profile be different from that same type in other profiles (e.g., not allowing the same email address in two different profiles).
  • identifiers e.g., phone number, email address, username, etc.
  • a digital platform may or may not be configured to allow for the same third-party standard unique identifier utilized for a user account level identifier for a profile discoverability identifier for one or more of the user profiles of that account.
  • the same third-party standard unique identifier used for a user account identifier is allowed to be used as a profile discoverability identifier of a user profile for that account.
  • a default configuration for a platform’s user account is such that a first user profile created for a user account is set by default with the same third-party standard unique identifier used as an account identifier as one of that first user profile’s user discoverability identifiers.
  • a search request is received by the platform via a user interface presented to a searching user.
  • the search request includes a search identifier.
  • step 1115 the digital platform compares the search identifier from step 1110 to profile discoverability identifiers across the platform. If the platform does not find a match, the method proceeds to step 1120 where the platform takes a no search match response.
  • the platform finds a match of the search identifier to a profile discoverability identifier in one or more profiles, at step 1125, the platform allows the searching user to interact with the user to whom the matching profile(s) belong via the corresponding profile of the searched user.
  • the platform may present a request to connect to the searched user as discussed above. In one such example, a positive response by the searched user to connect would result in allowing interaction at step 1125, whereas a negative response by the searched user to connect would result in a no match response being taken at step 1120.
  • the platform may disallow a certain matching at step 1115 based on one or more profile discoverability settings of the searched user.
  • a request to connect may be presented to the searched user as discussed above. In such a case, a positive response by the searched user to connect would result in allowing interaction at step 1125, whereas a negative response by the searched user to connect would result in a no match response being taken at step 1120.
  • a user of a digital platform is allowed to interact with another user of the digital platform (e.g., as in method 1100 at 1125 or in other methods disclosed herein), such interaction may be by any of the well-known interactions known or yet to be developed for interactions on digital platforms.
  • Examples of such interactions include, but are not limited to, allowing a user to view another user’s profile information (e.g., a user’s information set in that user’s profile object settings, other profile information, etc.) of the corresponding profile, adding a searched user to a searching user’s contacts (e.g., adding to a list of one or more contacts associated with a searching user’s account, adding to a list of one or more contacts associated with a searching user’s user profile), adding a searching user to a searched user’s contacts (e.g., adding to a list of one or more contacts associated with a searched user’s account, adding to a list of one or more contacts associated with a searched user’s user profile), providing the searching user with an option to request a connection with the searched user, providing the searched user with an option to accept or deny the connection to the searching user, allowing a searching user to initiate an interaction object with the searched user, allowing the searched user to initiate an interaction object with the searching user, and any combinations thereof.
  • the digital platform can be configured such that the first user may not see other profiles of the second user even if the first user conducts a search request with a search identifier that matches a profile discoverability identifier of the second user’s other profiles (e.g., until the second user reassociates the first user to a different profile).
  • a platform is configured such that a searching user is associated with the user profile of the searched user that includes the matching profile discoverability identifier searched by the searching user and the searched user is associated with a user profile of the searching user’s account (e.g., as selected by the searching user).
  • a platform is configured such that a searching user is associated with a user profile of the searched user based on a selection received from the searching user (e.g., in response to request to connect).
  • the searching user will be presented to the searched user in one or more user interfaces of the corresponding platform based on the profile object settings of the user profile of the searching user to which the searched user is associated and the searched user will be presented to the searching user in one or more user interfaces of the platform based on the profile object settings of the user profile of the searched user to which the searched user is associated.
  • a digital platform may be configured such that each user continues to be presented information about the other user based on the profile object setting of the user profile each is associated with in the other user’s account, notwithstanding which of that user’s profiles are active, which PGO’s are associated with an interaction object, or what other contacts of either of the users (which may be associated with different profiles) are interacting in a given interaction object (e.g., a group message room/thread).
  • FIG. 12 illustrates another exemplary implementation of a method for discovering a user on a digital platform 1200.
  • FIG. 12 illustrates another exemplary implementation of a method for discovering a user on a digital platform 1200.
  • some of the details, concepts, aspects, features, characteristics, examples, and/or alternatives discussed with respect to the discussion of method 1100 in FIG. 11 and other implementations in this disclosure are not repeated in the discussion of FIG. 12. Any one or more of the like details, concepts, aspects, features, characteristics, examples, and alternatives may apply similarly here, except where noted.
  • method 1200 includes associating one or more profile discoverability identifiers with each user profile of a user account (e.g., user account 205 of FIG. 2, user account 405 of FIG. 4, user account 1005 of FIG. 10, etc.).
  • a user account e.g., user account 205 of FIG. 2, user account 405 of FIG. 4, user account 1005 of FIG. 10, etc.
  • a search request is received by the platform via a user interface presented to a searching user.
  • the search request includes a search identifier.
  • the digital platform compares the search identifier from step 1210 to profile discoverability identifiers across the platform. If the platform does not find a match, the method proceeds to step 1220 where the platform takes a no search match response.
  • the matching process may include, upon a matching of a search identifier with a profile discoverability identifier of the searched user’s account, presenting a request to connect to the searched user as discussed above. In one such example, a positive response by the searched user to connect would result in proceeding to step 1225, whereas a negative response by the searched user to connect would result in a no match response being taken at step 1220.
  • step 1225 the platform checks the discoverability settings of the searched user’s matching profile (and, in alternative implementations, in other locations of the user account) to check if the current searching user is allowed to discover the searched user (e.g., proper degrees of separation to the searching user, the type of profile discoverability identifier, etc.). If the discoverability settings do not allow the particular match, the process continues to step 1220 where the platform takes a no search match response. If the discoverability setting do allow the particular match, the process continues to step 1230.
  • a request to connect may be presented to the searched user as discussed above.
  • a positive response by the searched user to connect would result in the process proceeding to 1230, whereas a negative response by the searched user to connect would result in a no match response being taken at step 1220.
  • step 1225 may occur prior to step 1215 (e.g., where a profile discoverability setting relates to an aspect of a search request that is independent of whether a search identifier matches a profile discoverability identifier, such as a degree of separation setting or other setting related to the searching user).
  • the platform allows the searching user to interact with the user to whom the matching profile(s) belong via the corresponding profile of the searched user.
  • FIG. 13 illustrates yet another exemplary implementation of a method for discovering a user on a digital platform 1300.
  • some of the details, concepts, aspects, features, characteristics, examples, and/or alternatives discussed with respect to the discussion of method 1100 in FIG. 11, method 1200 in FIG 12, and other implementations in this disclosure are not repeated in the discussion of FIG. 13. Any one or more of the like details, concepts, aspects, features, characteristics, examples, and alternatives may apply similarly here, except where noted.
  • method 1300 includes receiving a third-party standard unique identifier from each user of a digital platform.
  • the third-party standard unique identifier is associated with the user account level for each user.
  • a digital platform may be configured such that only a single third-party standard unique identifier is required to establish an account having multiple user profiles having one or more of the features or aspects described herein (e g., even if a second third-party standard unique identifier is optionally acceptable in one or more profiles as a profile discoverability identifier).
  • step 1305 may be omitted.
  • the process of method 1300 includes associating one or more profile discoverability identifiers with each user profile of a user account (e.g., user account 205 of FIG. 2, user account 405 of FIG. 4, user account 1005 of FIG. 10, etc.).
  • a user account e.g., user account 205 of FIG. 2, user account 405 of FIG. 4, user account 1005 of FIG. 10, etc.
  • a search request is received by the platform via a user interface presented to a searching user.
  • the search request includes a search identifier.
  • the digital platform compares the search identifier from step 1320 to profile discoverability identifiers across the platform. If the platform does not find a match, the method proceeds to step 1330 where the platform takes a no search match response.
  • the platform checks the discoverability settings of the searched user’s matching profile (and, in alternative implementations, in other locations of the user account) to check if the current searching user is allowed to discover the searched user (e.g., proper degrees of separation to the searching user, the type of profile discoverability identifier, etc.). If the discoverability settings do not allow the particular match, the process continues to step 1330 where the platform takes a no search match response. If the discoverability settings do allow the particular match, the process continues to step 1335.
  • the platform allows the searching user to interact with the user to whom the matching profile(s) belong via the corresponding profile of the searched user.
  • FIG. 14 illustrates another exemplary implementation of a method for discovering a user on a digital platform 1400.
  • some of the details, concepts, aspects, features, characteristics, examples, and/or alternatives discussed with respect to the discussion of method 1100 in FIG. 11, method 1200 in FIG. 12, method 1300 in FIG. 13, and other implementations in this disclosure are not repeated in the discussion of FIG. 14. Any one or more of the like details, concepts, aspects, features, characteristics, examples, and alternatives may apply similarly here, except where noted.
  • method 1400 includes associating one or more profde discoverability identifiers with each user profile of a user account (e.g., user account 205 of FIG. 2, user account 405 of FIG. 4, user account 1005 of FIG. 10, etc.).
  • a user account e.g., user account 205 of FIG. 2, user account 405 of FIG. 4, user account 1005 of FIG. 10, etc.
  • a search request is received by the platform from a searching user via a user interface presented to a searching user.
  • the search request includes a search identifier.
  • step 1415 the digital platform compares the search identifier from step 1410 to profile discoverability identifiers across the platform. If the platform does not find a match, the method proceeds to step 1420 where a no search match response is taken.
  • the matching process of step 1415 may optionally include determining if one or more profile discoverability settings of the searched user’s account (e.g., a profile discoverability setting of a set of profile discoverability settings in a profile of the searched user that includes a profile discoverability identifier matching the search identifier from 1410) disallows a matching (e.g., as discussed above). In one such example, if a match is disallowed the process proceeds to step 1420 where a no search match response is taken.
  • the searched user may optionally be presented with a request connect (as discussed above with respect to connect requests following a disallowed match) at step 1425.
  • the platform finds a match of the search identifier to a profile discoverability identifier in one or more profiles (and optionally if the matching at step 1415 is not disallowed or is allowed to proceed to a request to connect after disallowing the match), the method proceeds to step 1425.
  • a request to connect the searching user to the searched user is presented to the searched user (e.g., via one or more user interfaces of the corresponding digital platform).
  • the request to connect includes a presentation to the searched user of an option to allow or not allow the connection.
  • the searched user is also presented with an option for the searched user to select a profile from one or more of the presenting to the searched user one or more profiles of the searched user’s account to which to associate the searching user.
  • the option presented includes an option to select from at least two of the user profiles of the searched user’s account (e.g., the profile corresponding to the profile discoverability identifier matched at step 1415 and at least one additional profile of the searched user’s account).
  • the at least two of the user profiles is a subset of all of the profiles of the searched user’s account.
  • the option presented includes an option to select from all of the profiles of the searched user’s account.
  • One or more settings of the searched user’s account may apply to the process of presenting a request to connect to the searched user, examples of which are discussed above. If the searched user responds to the request to connect with a do not allow response, the process would proceed to a similar no match response similar to that of step 1420.
  • an affirmative response to the request to connect is received from the searched user along with a selection of a select profile to which to associate the searching user (i.e., making the searching user a contact of the searched user and making the searched user a contact of the searching user).
  • the select profile is the same profile as the profile matched to the search identifier at step 1415.
  • the select profile is not the same profile as the profile matched to the search identifier at step 1415.
  • a corresponding digital platform may associate the searching user with the select profile and associate the searched user with a profile of the searching user’s account, each as discussed elsewhere herein.
  • FIG. 15 illustrates another exemplary implementation of a method for discovering a user on a digital platform 1500.
  • FIG. 15 illustrates another exemplary implementation of a method for discovering a user on a digital platform 1500.
  • some of the details, concepts, aspects, features, characteristics, examples, and/or alternatives discussed with respect to the discussion of method 1100 in FIG. 11, method 1200 in FIG. 12, method 1300 in FIG. 13, method 1400 of FIG. 14 and other implementations in this disclosure are not repeated in the discussion of FIG. 15. Any one or more of the like details, concepts, aspects, features, characteristics, examples, and alternatives may apply similarly here, except where noted.
  • method 1500 includes associating one or more profile discoverability identifiers with each user profile of a user account (e.g., user account 205 of FIG. 2, user account 405 of FIG. 4, user account 1005 of FIG. 10, etc.).
  • a user account e.g., user account 205 of FIG. 2, user account 405 of FIG. 4, user account 1005 of FIG. 10, etc.
  • a search request is received by the platform from a searching user via a user interface presented to a searching user.
  • the search request includes a search identifier.
  • step 1515 the digital platform compares the search identifier from step 1510 to profile discoverability identifiers across the platform. If the platform does not find a match, the method proceeds to step 1520 where a no search match response is taken. If the platform matches the search identifier to a profile discoverability identifier of the searched user’s account, the process proceeds to step 1525.
  • the search request is compared against one or more discoverability settings (e g., the profile discoverability settings of the profile of the searched user matching at step 1515) to determine if a match of the searched user (e.g., a profile of the searched user) is disallowed. If the match is not disallowed, the process proceeds to step 1530. It is contemplated that one or more of the aspects of the comparison at step 1525 may occur prior to (and possibly eliminate the need for) step 1515.
  • one or more of the aspects of the comparison at step 1525 may occur prior to (and possibly eliminate the need for) step 1515.
  • a request to connect the searching user to the searched user is presented to the searched user (e.g., via one or more user interfaces of the corresponding digital platform).
  • the request to connect includes a presentation to the searched user of an option to allow or not allow the connection. If allowed, the searched user is also presented with an option for the searched user to select a profile from one or more of the presenting to the searched user one or more profiles of the searched user’s account to which to associate the searching user.
  • the option presented includes an option to select from at least two of the user profiles of the searched user’s account (e.g., the profile corresponding to the profile discoverability identifier matched at step 1515 and at least one additional profile of the searched user’s account).
  • the at least two of the user profiles is a subset of all of the profiles of the searched user’s account.
  • the option presented includes an option to select from all of the profiles of the searched user’ s account.
  • One or more settings of the searched user’ s account may apply to the process of presenting a request to connect to the searched user, examples of which are discussed above.
  • step 1535 a response to the request to connect at step 1530 is received from the searched user by a corresponding digital platform.
  • step 1540 a request to connect the searching user to the searched user is presented to the searched user.
  • a request to connect may be similar to a request presented under step 1530.
  • a request to connect at step 1525 may also include information to the searched user related to the fact that the match to the search request was disallowed based on a setting of the searched user.
  • One or more settings of the searched user’s account may apply to the process of presenting a request to connect to the searched user, examples of which are discussed above.
  • a response to the request to connect at step 1540 is received from the searched user by a corresponding digital platform.
  • step 1545 if the response at step 1535 is to not allow a connection between the searched user and the searching user (i.e., a rejection of the search request), the process proceeds to step 1520 where a no match response is taken. If the response at step 1535 is to allow a connection between the searched user and the searching user, the process proceeds to step 1550.
  • the searching user is associated with the select profile.
  • the searching user is allowed to interact with the searched user based on the select profile.
  • such interaction includes an interaction object involving the searched user and the searching user.
  • Contact objects of a CPOL platform may be configured to be fluid with respect to their relationship to a user’s account such that the user can create interaction objects with contacts across their profiles while also retaining the benefit of projecting out a persona of a given profile to a given contact.
  • a user can associate each of their contacts (i.e., other users of the corresponding digital platform) with one of their user profiles having a set of profile object settings for projecting outwardly a persona of the user to their contacts in the interactions via the platform.
  • the platform retains a record of the association of a contact with a profile without limiting the use of the contact in other profile of the user (e.g., allowing the user to have an interaction object with the contact while a profile with which the contact is not associated is set as active in the platform for the user, using a contact associated with one profile with an interaction object associated with a PGO originating from a different profile, and combinations thereof).
  • FIG. 16 illustrates one exemplary implementation of a method of contact interaction management in a digital platform 1600 (such as one of the CPOL platforms disclosed herein).
  • a set of profile object settings is associated with each profile of a user account of a first user (e g., an initiating user) of a digital platform, such as a CPOL platform as disclosed herein.
  • a second user is associated with a first profile of the first user.
  • This first profile has a first set of profile object settings.
  • the first profile may also have one or more profile discoverability identifiers and/or one or more discoverability settings (e.g., used by a first contact user to find an initiating user having the first profile).
  • the digital platform is configured to govern how the first user is presented to the second user based on the first set of profile object settings (e.g., via one or more user interfaces of the platform).
  • FIG. 17 illustrates another exemplary implementation of a method of interacting in a digital platform 1700.
  • a set of profile object settings is associated with each profile of a user account of a first initiating user of a digital platform, such as a CPOL platform as disclosed herein.
  • a first contact user is associated with a first profile of the first user.
  • the first profile has a first set of profile object settings.
  • the first profile may also have one or more profile discoverability identifiers and/or one or more discoverability settings (e.g., used by a first contact user to find an initiating user having the first profile).
  • a second profile of the first initiating user is set as active in the digital platform for the first user.
  • Example aspects of setting a profile as active are discussed above.
  • a first interaction object with the first initiating user and the first contact user is generated while the second profile is still set as active (e.g., in one or more user interfaces of the digital platform presented to the first initiating user).
  • the first interaction object is presented to the first contact user such that the initiating user is presented to the first contact user based on the first set of profile object settings (i.e., not based on the profile object settings of the second profile). For example, within one or more displays of the corresponding digital platform that include a representation of the interaction object, the representations of the first initiating user will be based on the first set of profile object settings (e.g., profile image, profile username, etc.).
  • FIG. 18 illustrates yet another exemplary implementation of a method of interacting in a digital platform 1800.
  • a set of profile object settings is associated with each profile of a user account of a first initiating user of a digital platform, such as a CPOL platform as disclosed herein.
  • a first contact user is associated with a first profile of the first user.
  • the first profile has a first set of profile object settings.
  • the first profile may also have one or more profile discoverability identifiers and/or one or more discoverability settings (e.g., used by a first contact user to find an initiating user having the first profile).
  • a first interaction object with the first initiating user and the first contact user is generated (e.g., in one or more user interfaces of the digital platform presented to the first initiating user).
  • a PGO that originates from a second profile of the first user account is associated with the first interaction object.
  • the first contact user is still associated with the first profile and is not associated with the second profile.
  • the PGO includes a set of initiator privacy settings and a set of PGO recipient settings.
  • a PGO of a digital platform as disclosed herein may be associated with an interaction object in one or more of a variety of known and/or yet to be developed mechanisms.
  • Example mechanisms for associating a PGO with an interaction object include, but are not limited to, maintaining a link in the digital platform between the PGO and the interaction object, including a reference to the PGO within the object of the digital platform representing the interaction object, maintaining a link in the digital platform between the corresponding set of initiator settings and/or set of PGO recipient settings of the PGO and the interaction object, including a reference to the corresponding set of initiator settings and/or PGO recipient settings of the PGO within the object of the digital platform representing the interaction object, explicitly copying one or more values of a setting of a set of initiator privacy settings of the corresponding PGO to the object of the digital platform representing the interaction object, explicitly copying one or more values of a setting of a set of recipient privacy settings of the corresponding PGO to the object of the digital platform representing the interaction object, explicitly copying one or more values of a setting of a set of initiator privacy settings of the corresponding PGO to the object of the digital platform representing a subcomponent of the interaction object, explicitly copying one or
  • the interaction object is presented to the contact user.
  • the interaction object is governed by the associated PGO from step 1820.
  • the initiator privacy settings of the initiating user’s PGO apply to the interaction object for all users of the interaction object (e.g., even if a recipient user associates their own PGO from their account with the interaction object).
  • the privacy and security behavior of the interaction object across the platform and for all users is controlled by the initiator of the interaction object via the association of the PGO (and the corresponding initiator privacy settings) at step 1820.
  • An associated PGO to an interaction object may be changed to a different PGO of the initiating user’s account during the life of the interaction object and thereby changing the privacy and security settings applying to the interaction object.
  • any new subcomponent of the interaction object will have the new initiator privacy and security settings applied to that new subcomponent created after the change (i.e., until any additional changes in PGO association).
  • existing subcomponents retain the previously assigned initiator privacy settings of the associated PGO at the time of each subcomponent’s creation/initiation.
  • one or more existing subcomponents are reassigned the new initiator privacy settings of the new associated PGO.
  • the first initiating user is presented to the first contact user (i.e., the recipient of the interaction object) based on the set of profile object settings of the first profile (i.e., the profile in the initiating user’s account to which the first contact user is associated).
  • a user of a digital platform may change a profile to which another user is associated and change the corresponding set of profile object settings that apply to how the platform presents information about the profile owning user to that other user.
  • a digital platform is configured to change the one or more profile object settings used to present information about a user to a contact user with respect to an existing interaction object to the one or more profile object settings of the then current associated profile for the given contact user.
  • existing subcomponents of that interaction object continue to be presented such that information about the profile owning user are presented to a contact user based on the one or more profile object settings that correspond to the profile to which the contact user was associated at the time of the creation/initiation of the corresponding subcomponent of the interaction object.
  • existing subcomponents of that interaction object are presented such that information about the profile owning user are presented to a contact user based on the one or more profile object settings corresponding to the profile to which the contact user is associated at the time of presentation to the contact user.
  • a recipient of an interaction object may also have associated the initiating user with a profile of the recipient user’s account (e.g., where the initiating user is a contact to the recipient user within the recipient’s user account and associated with a profile of the recipient user according to method 1600 of FIG. 16).
  • the corresponding digital platform can be configured to present information about the recipient user to the initiating user based on one or more profile object settings of the profile to which the initiating user is associated in the recipient user’s account.
  • an interaction object may also be associated with a PGO of a recipient of the interaction object.
  • the initiator privacy settings of that recipient’s associated PGO do not govern the interaction object.
  • Each PGO of a digital platform may include one or more PGO recipient settings.
  • the PGO recipient settings of the PGO associated with an interaction object by a first user (e.g., an initiating user) of the interaction object apply to that interaction object as it is presented to the first user via one or more user interfaces of the corresponding digital platform and the PGO recipient settings of the PGO associated with an interaction object by another user (e.g., a recipient user) of the interaction object apply to that interaction object as it is presented to that other user via one or more user interfaces of the digital platform.
  • a first user e.g., an initiating user
  • another user e.g., a recipient user
  • An interaction object such as those discussed above with respect to methods 1800 and 1700 and other relevant implementations disclosed herein, can be a group interaction object for which there are more than one contact user included as a recipient of the interaction object from the initiating user.
  • each contact user is associated with one of the profiles of the initiating user’s user account (e.g., one or more of the contact users included as recipients may be associated with different profiles from each other, each contact user included as recipients may be associated with a different profile than a currently active profile, each contact user included as recipients may be associated with a different profile than the profile from which a PGO associated with the interaction object originated, and any combinations thereof).
  • the recipient contact user is presented information about the initiating user based on the profile object settings of the corresponding profile to which the given recipient contact user is associated within the user account of the initiating user.
  • An initiating user may include two or more of the initiating user’s contacts as recipients of an interaction object where some or all of the recipients are not yet contacts with each other in the digital platform.
  • a first user, Tim may initiate an interaction object with a second user, Mary, and a third user, John, where both Mary and John are contacts of Tim’s within the digital platform. In this example, however, Mary and John are not yet contacts in the digital platform.
  • a digital platform may handle how information of each user is presented to the other in relation to the interaction object in a manner suitable for the particular digital platform.
  • Example ways to handle presentation of user information to non-contacts include, but are not limited to, providing a user interface (e.g., at the reception of a group interaction object having non-contacts) to a recipient allowing a recipient to become contacts with another recipient of the interaction object, presenting default information about a user to another user (e.g., a default/non-contact-related profile image, profile username, etc.), presenting anonymized information about a user to another user, presenting pseudonymized information about a user to another user, presenting just a user name about a user, presenting information governed by a profile (e.g., by the profile object settings of the profile) selected by a user to be presented to non-contacts, and any combinations thereof.
  • a user interface e.g., at the reception of a group interaction object having non-contacts
  • presenting default information about a user to another user e.g., a default/non-contact-related profile image, profile username, etc.
  • FIG. 19 illustrates still another implementation of a method of interacting in a digital platform 1900.
  • a set of profile object settings is associated with each profile of a user account of a first initiating user of a digital platform, such as a CPOL platform as disclosed herein.
  • a first contact user is associated with a first profile of the first user.
  • the first profile has a first set of profile object settings.
  • a second contact user is associated with a second profile of the first user.
  • the second profile has a second set of profile object settings.
  • a first interaction object with the first initiating user, the first contact user, and second contact user is generated (e.g., in one or more user interfaces of the digital platform presented to the first initiating user).
  • a PGO that originates from a third profile of the first user account is associated with the first interaction object.
  • the first contact user is still associated with the first profile and the second user is still associated with the second profile (i.e., the first contact user and second contact user are not associated with the third profile).
  • the PGO includes a set of initiator privacy settings and a set of PGO recipient settings.
  • the interaction object is presented to the first contact user.
  • the interaction object is governed by the associated PGO from step 1925.
  • the initiator privacy settings of the initiating user’s PGO apply to the interaction object for all users of the interaction object (e.g., even if a recipient user associates their own PGO from their account with the interaction object).
  • the privacy and security behavior of the interaction object across the platform and for all users is controlled by the initiator of the interaction object via the association of the PGO (and the corresponding initiator privacy settings) at step 1920.
  • the first initiating user is presented to the first contact user based on the set of profile object settings of the first profile (i.e., the profile in the initiating user’s account to which the first contact user is associated).
  • the interaction object is presented to the second contact user.
  • the interaction object is governed by the associated PGO from step 1925.
  • the first initiating user is presented to the second contact user based on the set of profile object settings of the second profile (i.e., the profile in the initiating user’s account to which the second contact user is associated).
  • FIG. 20 illustrates still yet another implementation of a method for interacting in a digital platform 2000.
  • an interaction object is generated in a digital platform, such as a CPOL platform of the current disclosure.
  • the interaction object includes a first user (e.g., an initiating user) and at least one other user (e.g., a recipient user).
  • a first PGO of the first user’s account is associated with the interaction object.
  • a user account may include one or more PGO’s.
  • the first PGO includes a first set of initiator privacy settings and a first set of PGO recipient settings.
  • a PGO for each of the at least one other users is associated with the interaction object from a corresponding user account.
  • Each of such PGO’s includes a set of initiator privacy settings and a set of PGO recipient settings.
  • the interaction object is presented to the first user governed by the first set of initiator privacy settings and the first set of PGO recipient settings.
  • the interaction object is presented to each of the at least one other users governed by the first set of initiator privacy settings and the set of PGO recipient settings corresponding to the PGO associated with the interaction object for each user.
  • a digital platform may include a functionality to allow for a subset of the users involved in a group message room to participate in a side chat within the same message room as the group message room.
  • a group message is a type of interaction object involving messaging amongst two or more users.
  • a message room (or thread) is a display of a message interaction object’s subcomponents (e.g., message segments and other subcomponents) to the users that are members of the group message (e g., an initiating user and at least two recipient users).
  • a side chat is a sub message thread between less than all of the member users of a group message where the subcomponents of the side chat (“side chat subcomponents”) are shown in the same user interface of the digital platform that represents the message room as the subcomponents involving all of the group message members (“main subcomponents,” also referred to as “group message segments).
  • Such a user interface of a group message room may include more than one display screen or displayable panel without leaving the context of the group message room.
  • the side chat subcomponents are presented only to the side chat participants alongside the main subcomponents that are visible to all participants of the larger group message room.
  • Non-members of the side chat do not see the side chat subcomponents (i.e., only seeing the main subcomponents in the message room display). Additionally, only participating users in a side chat can generate message segments for the side chat.
  • a digital platform having a side chat functionality may be configured to present a user that wishes to start a side chat with a user interface for selecting participant for a side chat in a variety of ways.
  • a user interface for selecting participants for a side chat includes an additive type interface.
  • a user that wishes to start a side chat is given a user interface that allows them to add one or more users to be participants in the side chat.
  • a user interface for selecting participant for a side chat in a variety of ways (e.g., a user A of a group message room with other user B, user C, and user D starts a side chat and positively selects user C and user D to be participants in the side chat such that the participants in the side chat are user A, user C, and user D).
  • a user interface for selecting participants for a side chat includes a negative/sub stractive type interface.
  • a user that wishes to start a side chat is given a user interface that allows them to indicate one or more users of the group message room that will not be a participant in the side chat (e.g., a user A of a group message room with other user B, user C, and user D starts a side chat and selects user B to not be a participant in the side chat such that the participants are user A, user C, and user D).
  • a user interface for selecting participants for a side chat may include both a positive type feature and a subtractive type feature.
  • the presentation of the side chat subcomponents with respect to the main subcomponents can be by any of a variety of relative positions with respect to each other.
  • Example relative positions include, but are not limited to, interspersing side chat subcomponents in line with main subcomponents as the main subcomponents are displayed (e.g., in time as they occur), side chat subcomponents being displayed to the side of the main subcomponents, side chat subcomponents being displayed via a side chat display panel, side chat subcomponents being displayed in a pop-up screen or window (e.g., a screen or window that covers at least a portion of the display of the main subcomponents, a screen or window that covers all of the display of the main subcomponents, etc), side chat subcomponents being displayed via a slidable panel that covers all of the main subcomponents being displayed as the slidable panel is actuated by a user across a display screen, and side chat subcomponents being displayed via a slidable panel that covers a portion of the main subcomponents being displayed as the slidable panel is actuated by a user across a display screen.
  • the side chat subcomponents may be made distinctive from main subcomponents in the display to the side chat members using a side chat distinctive visual display feature.
  • a side chat distinctive visual display feature include, but are not limited to, a color difference, a message segment bubble shape difference, a textual indicator, a graphical indicator, a side chat display panel, and any combinations thereof.
  • a side chat display panel is a displayable element of a group message room that covers at least a portion of a display of one or more group message segments (those viewable to all members of the group message room) and allows members of a side chat of that group message room to view one or more side message segments (i.e., those of a side chat of the group message room).
  • a side chat display panel is configured to only cover a portion of a display of one or more group message segments of the group message room. In another example, a side chat display panel is configured to cover from view the entire display of the one or more group message segments of the group message room (e.g., as in the examples discussed with respect to FIGS. 27 A to 27E). Examples of a side chat display panel include, but are not limited to, a pop-up screen, a pop-up window, a slidable panel, and other screen display panels useable to display one or more side chat subcomponents within a group message room.
  • a group message room interaction object may be displayable to a user via one or more displayable screen elements.
  • a group message room may be configured with a single page display design in which main group message subcomponents and side chat subcomponents can be visibly displayed to a user at the same time (e.g., as shown in the example discussed with respect to FIGS. 22A to 22E or an example in which a side chat display panel only partially covers a display of the displayed main group message subcomponents).
  • a group message room may be configured such that a side chat display panel or other screen feature is actuated within a group message room such that the side chat display panel or other screen feature covers from display to a user the previous display of main group message subcomponents (e.g., as shown in the examples discussed with respect to FIGS. 27 A to 27E, 28A to 28D).
  • a side chat functionality allows a user to initiate, edit, add users to, view, and otherwise interact with a side chat message thread without leaving the context of the group message room within the platform (e.g., without having to navigate to a centralized message thread list or utilize a main message thread initiation process of the platform).
  • a user of a group message room can easily move back and forth from viewing message segments of the main group thread and side message segments of the side chat (e.g., while also visually being able to distinguish between the segments of the main group thread and those of a side chat, such as via one or more side chat distinctive visual display feature).
  • the one or more group message subcomponents and the one or more side chat subcomponents are part of the same group message interaction object (e.g., in implementations with a PGO associated with a group message interaction object, the one or more side chat subcomponents are governed by the same settings as the one or more group message subcomponents, such as initiator privacy settings for the object’s initiator PGO and PGO recipient settings where applicable for each recipient, except for any specific settings assigned by an initiator of a side chat where such settings (e.g., time of expiration of a side chat) are configured to be set by the initiator of the side chat).
  • initiator privacy settings for the object e.g., initiator PGO and PGO recipient settings where applicable for each recipient, except for any specific settings assigned by an initiator of a side chat where such settings (e.g., time of expiration of a side chat) are configured to be set by the initiator of the side chat).
  • display of message segments in a thread and/or the covering of a display of one set of message segments by a display of another set of message segments or another object takes into consideration that not all of the message segments of any given thread may be being currently displayed to the end user at any given time and that the concepts and ideas discussed herein may apply to only those parts of a message thread that are currently displayable on a device screen by a digital platform.
  • a group message room having a side chat functionality as described herein may or may not be part of a digital platform that also has one or more of the details, concepts, aspects, features, characteristics, examples, and/or alternatives discussed herein with respect to implementations, embodiments, and/or methodologies for other functionalities (e.g., wherein a group message interaction object includes assigned PGO’s and related settings by the initiator of the group message interaction object (e.g., initiator privacy settings) and PGO/settings of a recipient (non-initiator) of the group message interaction object (e.g., PGO recipient settings).
  • Such settings may include settings that impact the operation of a side chat functionality such that a side chat initiated in a group message room may be governed by such settings.
  • one or more settings governing the operation of a side chat functionality is set by a PGO assignment by the initiator of the group message interaction object.
  • one or more settings governing the operation of a side chat functionality is set by a PGO assignment by the initiator of the specific side chat within the group message interaction object.
  • one or more settings governing the operation of a side chat functionality is set by a PGO assignment by the initiator of the group message interaction object and another one or more of the settings governing the operation of a side chat functionality is set by a PGO assignment by a recipient user of the group message interaction object.
  • a digital platform may be configured such that a side chat may only have user members that are also members of the group message room.
  • a side chat within a group message room may be limited to participants of the group message room (e.g., the initiator of the group message room interaction object and other recipient users of the group message room interaction object) wherein the participants of a side chat are a subset of the users in the group message room.
  • a side chat can be initiated by a user of the group message room interaction object and that user is limited to adding any subset of the users of the group message room interaction object to the side chat within the group message room interaction object.
  • a digital platform may be configured to limit (e.g., by default, by a setting of a user, by a setting of a PGO associated with the group message room, etc.) the number of users from a group message room that can be added/invited to a side chat of the group message room (e.g., a default setting allowing a certain total number, such as two, users of the group message room to be part of a particular side chat, such as by being added by the side chat initiating user or being added by another user after the initiation of a side chat).
  • a default setting allowing a certain total number, such as two, users of the group message room to be part of a particular side chat, such as by being added by the side chat initiating user or being added by another user after the initiation of a side chat.
  • a user of a group message can request a side chat with another user of the group message (e.g., using a user interface function selector, such as a hover menu, a right click menu, slide tab, other side chat actuation control, etc.).
  • a platform may be configured to either require an acceptance from the other user before a side chat can commence or such that acceptance is not required (e.g., the side chart begins once the user requests it to begin and the other user has the side chat presented to them in the group message room).
  • Such a configuration may be toggled by one or more user side-chat settings (e.g., a setting allowing a side chat to be requested in a group message generally, a setting requiring acceptance of a side chat in a group message generally, a setting of a side-chat initiator allowing or disallowing such a request, a setting of a side-chat recipient allowing or disallowing such a request, a setting of a user to automatically accept requests for a side-chat, a setting of a user to automatically decline requests for a side-chat, a setting related to allowing a non-contact in a group message room to participate in a side chat with a user who is not their contact, a setting related to allowing a non-contact (e.g., a user who is not a contact with an initiating user) to start a side chat, and any combinations thereof).
  • a user side-chat settings e.g., a setting allowing a side chat to be requested in a group message generally, a setting
  • such a setting may be at the profile level (e.g., as part of a set of profile object settings that apply to a user’s contacts such that an interaction object between a user and a contact will have side-chat settings applied based on the profile to which a contact is associated).
  • such a setting may be at the PGO level (e g., as part of a set of PGO recipient settings such that the settings are applied via the association of a PGO to the interaction object representing the message room).
  • Such settings may also be part of a PGO’s initiator privacy settings and be governed by the PGO associated with a group message interaction object by the initiator of the group message interaction object.
  • a request for a side chat requires acceptance by a user.
  • a request for a side chat results in a side chat being initiated (e.g., the requesting user can send a first message segment of a side chat without waiting for an acceptance).
  • a side chat functionality could include the ability to allow the initiating user and/or the recipient user of the side chat to request that an additional user be added to the side chat (i.e., three or more users in a side chat).
  • Such an ability may be regulated by one or more user side chat settings similar to a side chat with respect to two users (e.g., requiring or not requiring acceptance, allowing such request generally as set by either of the two initial members of a side chat, etc.).
  • a side chat may have other side chat settings applied to it by the user initiating the side chat within the group message, the recipient of a side chat, and/or by the group message interaction object’s associated PGO (e.g., the PGO assigned by the initiator of the group message interaction object).
  • Examples of other side chat settings include, but are not limited to, a time period of auto deletion for a message segment of a side-chat, a number of times a message segment of a side chat may be viewed by a user, a time period until expiration of a side chat thread, a preference for a side chat distinctive visual display feature, a privacy setting, availability of option to invite a third or additional member to a side chat, and any combinations thereof.
  • a side chat setting is set by the initiator of a side chat (e.g., in a user interface for requesting a side chat that presents an option for a side chat setting).
  • a user interface may include a user actuatable element (e.g., a button, a toggle, a selector, and/or other user input) that allows the initiating user to set a setting (e.g., a time period at which the side chat will expire). It is contemplated that a setting related to expiration and the actual expiration of a side chat (or subcomponent thereof) may occur whether or not another user of the side chat has viewed or otherwise accessed the side chat or relevant subcomponent.
  • a digital platform may be configured (e.g., by default, by a user setting, etc.) such that an expiration time automatically deletes the relevant side chat or relevant subcomponent even if one or more of the users has not viewed or accessed the side chat or relevant subcomponent.
  • Automatic deletion e.g., at the expiration of a time period, after a number of user views, etc.
  • an object or objects
  • a platform device e.g., a server
  • the digital platform as a whole.
  • a side chat is configured (e.g., via a side chat setting) to start a timer related to automatic deletion at the creation of the side chat.
  • a side chat is configured (e g., via a side chat setting) to start a timer related to automatic deletion at the first opening of the side chat by a user other than the user starting the side chat.
  • a side chat is configured (e.g., via a side chat setting) to have a timer related to automatic deletion for each side message segment (e.g., such that each side message segment will delete at the expiration of its individual timer (e.g., started at creation, started at first reading, etc.) and the corresponding side chat will remain so long as any one of the side message segments has not had its timer for automatic deletion expire and/or until a timer related to the side chat as a whole automatically deleting expires).
  • Automatic deletion of a side chat can be done by a digital platform configured to delete from a user device of a user involved in a side chat, a server of a digital platform, and any combinations thereof. It is noted that platform may be configured to execute a deletion such that it occurs even if one or more of a side chat’s participants has not viewed/read the corresponding side chat or side message segment.
  • FIG. 21 illustrates a further implementation of a method for interacting in a digital platform 2100.
  • a group message room i.e., a display of at least a portion of a group message interaction object’s main group message segment(s)
  • a first user of a digital platform such as a CPOL platform of the current disclosure.
  • the interaction object is transmitted to a second user of the platform.
  • a request to initiate a side chat with the second user is received from the first user.
  • one or more side chat message segments are displayed to the first and second user via the same message room display as the at least one main group message segment.
  • the one or more side chat message segments are not displayed to the members of the group message that are not members of the side chat.
  • FIGS. 22A to 22E illustrate one exemplary implementation of a set of screen shots of a display screen of an exemplary group message room 2205 having a side chat.
  • Group message room shows a group message thread having main group message segments 2210 (from User 1), 2215 (from the user being displayed the user interface, the “main user”), 2220 (from User 2), and 2225 (also from User 2).
  • Main user wishes to request a side chat with User 2.
  • a user can right click on a main message segment to display a menu of options, a user can hard/long press a touch screen upon a main message segment to display a menu of options, a user may hover over a main message segment to display a menu of options, etc.).
  • a user uses a hard and/or long press of a touch screen over a message segment (e g., the main user in FIGS. 22A to 22E long presses the message segment 2225 from User 2).
  • FIG. 22B illustrates a pop-up menu of options 2230 displayed upon the main user long pressing on message segment 2225.
  • the platform receives a request to start a side-chat between the main user and User 2.
  • FIG. 22C illustrates a message entry portal 2235 that includes both textual (“You are sending a side-chat to User 2”) and graphical/color (blue distinctive color opposed to shades of pink/purple for main message segments 2210, 2215, 2220, 2225) side chat distinctive visual display features.
  • the main user inputs a first side chat message segment (“Hola Luli”) 2240 which is displayed in line with main message segments.
  • Side chat message segment 2240 is displayed with similar side chat distinctive visual display features (text and blue shading).
  • User 2 responds as a side chat (e.g., by long pressing side chat message segment 2240 and selecting a reply as side chat option) with side chat message segment 2245, which also is displayed using a blue shading and textual side chat distinctive visual display features.
  • FIGS. 27A to 27E illustrate various display screens for an exemplary implementation of a group message room of a digital platform where the group message room includes a side chat functionality.
  • FIG. 27A illustrates an exemplary implementation of a first display screen 2705 of the group message room interaction object’s interface.
  • the group message room includes a displayed title (in this example being “Italian cooking class,” which is abbreviated in the display) and group message room icon 2707.
  • the group message room includes a number of users of a digital platform.
  • the display screens of the group message room in FIGS. 27A to 27E are those displayable to a first user of the group message room (referred to in textual indicators as “You”).
  • a side chat functionality may provide a subset of the users taking part in the larger discussion within a group message room to easily (e.g., and temporarily) have a side discussion without leaving the contextual area of the group message room (e.g., maintaining user settings, such as those of assigned PGO(s) of the group message room and the related comfort of such settings for privacy, etc.).
  • First display screen 2705 of the group message room is for the display of a main group message thread that includes group message segments 2710 and 2712 from the first user and group message segments 2714 and 2716 from the group user, John Mason. A profile image 2718 for the user, John Mason, is also displayed.
  • First display screen 2705 also includes a user actuatable control element 2720 for displaying one or more settings (“Rules”) applicable to the group message room interaction object (e.g., user settings associated with the group message room via the assignment of a PGO to the group message room interaction object, such as initiator privacy settings).
  • a user actuates control element 2720 a contextual menu is displayed (e.g., as a popup menu) over the display of display screen 2705.
  • Such a pop-up contextual menu or other user actuatable display element for displaying any one or more user settings applicable to an interaction object may be included with any display of an interaction object described herein (e.g., to easily allow a user of an interaction object to know which privacy settings apply to a discussion or other interaction in an interaction object, even after a settings change such as occurs by an initiating user changing a PGO association such that a different set of initiator privacy setting apply to an interaction object than before).
  • First display screen 2705 also includes a user input element 2725 for allowing a user to input a message segment (e.g., via a pop-up on screen touch keyboard or other user input device associated with the user’s device) to the main group message thread.
  • a group message room may also include a user actuatable element to allow a user to navigate out of the group message room, such as user actuatable element 2727 (shown in this example as a user-selectable graphic arrow).
  • navigating out of a group message room may take a user to a display of any of a variety of other locations in a digital platform (e.g., a centralized message list showing message interaction objects between the device user and other users, a dashboard screen for the digital platform, a prior screen navigated from by the user, etc.).
  • a digital platform e.g., a centralized message list showing message interaction objects between the device user and other users, a dashboard screen for the digital platform, a prior screen navigated from by the user, etc.
  • First display screen 2705 includes a side chat actuation control element 2730 (shown as a graphical tab on the side of the first display screen 2705 including a textual description of “Side Chats” and an arrow).
  • a side chat actuation control element, such as side chat actuation control element 2730 may include a visual display graphic that is active when one or more new side chat segments are available to a user (e.g., a graphical indicator, a different color indicator, a blinking indicator, another type of indicator, and any combinations thereof).
  • a side chat actuation control element is a user selectable/actuatable display element that allows a user of a group message room to indicate or otherwise input to a digital platform an instruction to view one or more side message segments of a side chat (e.g., via a display of a side chat display panel).
  • Examples of a side chat actuation control element include, but are not limited to, a button, a tab, a graphic, a textual display, another type of user actuatable control, and any combinations thereof.
  • a side chat display panel may display any number of side chats currently active in the relevant group message room for the given user.
  • three different side chats are displayed as active.
  • Side chat 2734 includes users Kim Haris, the first user, and Robert Albert Stuart
  • side chat 2736 includes users Kim Harris and the first user
  • side chat 2738 includes users Kim Harris, the first user, and Bella (each of the side chats having textual and graphical indicators of the member users in the side chat).
  • Side chats 2734, 2736, and 2738 each include a user actuatable reply control 2740, 2742, and 2744, respectively.
  • a side chat displayable element such as that shown for side chats 2734, 2736, 2738, may be configured on a side chat display panel to show one or more of the current side chat message segments (also referred to as “side message segments”) of the relevant side chat (e.g., the most recent side message segment of the side chat) as a representative message segment with other message segments of the side chat temporarily hidden from view.
  • side chat display panel 2735 each of the displayed side chats have a representative side message segment displayed (in this example, the side message segment displayed is the first message segment from the side chat).
  • Side chat 2734 includes a textual and graphical (profile pictures overlaid) indicator 2750 that the side chat includes additional message segments (in this case “3 Replies” with the profile images of the members who replied displayed).
  • indicator 2750 is a user actuatable control 2752 configured to allow a user to select to display the additional side message segments associated with the “4 Replies”).
  • Side chat 2736 is shown without any indication of additional side message segments for the side chat (i.e., the first user has yet to respond to Kim Harris).
  • Side chat 2738 is shown with textual and graphical indicator 2754 (showing “1 answer” text and a profile picture for the user making the additional side message segment) that indicates the presence of an additional side message segment for side chat 2738.
  • Each of side chats 2734, 2736, 2738 includes an expiration graphical/textual indicator 2756, 2758, 2760, respectively (in this case each showing 5 minutes remaining).
  • An expiration graphical and/or textual indicator is a visual indicator to the user that is displayed to show the user the amount of time remaining before the object (e.g., side chat, side chat message segment, other object) expires and becomes no longer active (e.g., is deleted automatically, can no longer be accessed, can no longer be viewed, and/or can no longer be used to send additional message segments, etc.
  • an original time period for expiration can be set by a variety of ways, including, a user setting, by the platform, by a default setting, and/or by a setting input by the user initiating a side chat.
  • having a side chat expire within a predetermined period of time allows an initiating user the ability to control the lifespan (and possibly the privacy and/or dissemination) of a side chat and its contents (e.g., allowing users of a side chat to freely discuss side topics knowing the discussion will not be seen by other users of the main group message room and will not be retained).
  • a digital platform may be configured to allow for a side chat to not have an expiration (e.g., by default, by user selection, by user setting, by PGO setting, etc.).
  • Side chat display panel 2735 also includes a return actuation control 2762 (shown in this example as a user-actuatable graphical slide arrow) configured to easily allow a user to select/actuate control 2762 to return to the display of first display screen 2705 of the group message room.
  • Side chat display panel 2735 is part of the same group display room as first display screen 2705.
  • side chat display panel 2735 pops-up to cover at least a portion of first display screen 2705.
  • side chat display panel 2735 covers only a part of first display screen 2705 (e.g., a portion of the one or more group message segments displayed thereon is visible to a user at the same time side chats of side chat display panel 2735 are visible). In another such example, side chat display panel 2735 covers all of the display of the group message segments of first display screen 2705 (e.g., covers all of first display screen 2705 from view to a user). In another example, when a user actuates side chat actuation control 2730, side chat display panel 2735 slides over (e.g., side chat display panel is an example of a slide screen/slide panel) the display of first display screen 2705.
  • side chat display panel 2735 covers only a part of first display screen 2705. In another such example, side chat display panel 2735 covers all of the display of the group message segments of first display screen 2705 (e.g., covers all of first display screen 2705).
  • a side chat actuation control such as control 2730
  • various display actuation results and effects may occur. For example, a user can touch and hold a side chat actuation control and move the corresponding side chat display panel to one side (and optionally back to the other side) thereby moving the side chat display panel over the main group message thread segments of the same group message room.
  • FIGS. 28A to 28D below illustrate an example of a slide screen panel “sliding” across to cover a corresponding display screen of a main group message thread in a group message room.
  • FIG. 27C illustrates another view of side chat display panel 2735 viewable to a user upon actuation of user actuatable control 2752 of side chat 2734.
  • the display of side chat 2734 is exploded to display additional side message segments of side chat 2734.
  • three additional side message segments 2770, 2772, 2774 are displayed.
  • Side message segment 2770 is from Kim Harris: “Answer my side chat???
  • the display of side chat 2734 includes a user actuatable control 2776 (shown as an up arrow graphic) configured to allow a user to select/actuate control 2776 to hide the additional side message segments 2770, 2772, 2774 from view (i.e., return to the view of side chat display panel 2735 shown in FIG. 27B).
  • a user actuatable control 2776 shown as an up arrow graphic
  • reply control 2740 Upon actuation of reply control 2740 by the user of the current view of the message room, the first user “You”, the reply view 2780 of side chat display panel 2735 shown in FIG. 27D is displayed to the user to allow the user to enter a side chat message segment to side chat 2734.
  • Reply view 2780 display includes a user input element 2782 configured to allow a user to input a side chat message segment using screen display keyboard 2784.
  • Reply view 2780 also includes a user actuatable control 2786 (shown as a right facing arrow graphic) configured to allow a user to actuate control 2786 to return to the view of side chat display panel 2735 in FIG. 27C.
  • FIG. 27E illustrates a view of side chat display panel 2735 similar to that of FIG. 27C but with the addition of the display of new side message segment 2788 entered by user “You” via user input element 2782.
  • FIGS. 28A to 28D illustrate an example of a slide screen type side chat display panel “sliding” into displayable view.
  • a group message room 2805 e.g., the group message room of FIGS. 27A to 27E
  • Group message room 2805 includes a display of a first display screen 2810 for displaying a main group message thread of the group message room including the display of one or more group message segments.
  • Group message room 2805 includes a side chat actuation control 2815.
  • a side chat display panel 2820 of group message room 2805 begins to slide across into view over first display screen 2810. This sliding process is shown at two select points in FIG. 28B and FIG. 28C as side chat display panel 2820 moves to cover from view first display screen 2810.
  • FIG. 28D shows side chat display panel 2820 fully covering first display screen 2810.
  • a side chat display panel may include different display techniques for displaying side chat message segments than illustrated in the examples above.
  • a side chat display panel may include only a single side chat when viewed and the side message segments of such side chat may be displayed without a collapsed view such as that used in the displays of the three side chats in the example group message room of FIGS. 27A to 27E.
  • a side chat display panel may be displayed with no side chats or corresponding side message segments (e.g., when no active side chats for the group message room exist for the user viewing the side chat display panel).
  • a side chat display panel may include a feature to allow a user to initiate a new side chat and to select member users to participate in the side chat from the users in the group message room.
  • Such a feature may be any user actuatable element and/or user input element effective for starting the initiation of a new process and selecting users (e.g., user actuatable buttons, graphical elements, textual input fields, and other user input/actuation features/elements).
  • users e.g., user actuatable buttons, graphical elements, textual input fields, and other user input/actuation features/elements.
  • FIGS. 29A to 29D illustrate examples of displayable features and concepts for initiating a side chat within a group message room, such as the group message room of FIGS. 27A to 27E.
  • FIG. 29A illustrates an exemplary view 2905 of a side chat display panel having a user input element 2910 configured to allow a user to input to input element 2910 text for searching a user of the group message room for inclusion into a new side chat.
  • the side chat functionality is configured to only allow the addition of two additional users (for a total possible of three users) in a side chat (see the instructions displayed for input element 2910: “Select up to two participants to start a Side Chat”).
  • a digital platform and/or a particular side chat functionality may be configured in different ways to allow any number or a limited number of a subset of a group message room users to be part of a side chat.
  • View 2905 shows only a portion of side chat display panel and includes a display scroll bar 2915 to scroll to additional subject matter on the panel.
  • view 2905 of side chat display panel includes a display of a side chat 2920 similar to side chat 2734 of FIG. 27B, but with some similar elements located in different locations.
  • the side chat display panel shown in view 2905 includes a return actuation control 2925.
  • the view 2906 of the side chat display panel changes to display to the user the other users of the corresponding group message room that match the search criteria (in the example shown, three names of other users are displayed: “Magai Martins,” “Mark West,” and “Bruce Williams” along with their profile pictures 2930, 2935, 2940, respectively.
  • the display of the names and profile pictures 2930, 2935, 2940 is configured to allow a user to actuate/select a name for inclusion in the initiated side chat.
  • 29C illustrates the view 2907 of side chat display panel after a user selects user Magai Martins and user Bruce Williams to include in the side chat being initiated.
  • a graphical indicator (shown as a displayable check mark) 2945 is displayed next to the display of Magai Martins’ name and profile image 2930 to indicate the selection and a graphical indicator (shown as a displayable check mark) 2950 is displayed next to the display of Bruce Williams’ name and profile image 2940 to indicate the selection.
  • An additional displayable indicator 2955 of users added to the side chat is displayed at the top of the listing to indicate users added to the side chat with a user actuatable “x” configured to allow the initiating user to remove one or both of the selected users from the side chat.
  • the side chat display panel includes a user actuatable element 2960 (shown in the form of a graphical button with “Start a Side Chat” text) configured to allow a user to actuate element 2960 to complete the addition of users to the side chat and begin the side chat.
  • FIG. 29D illustrates a view 2908 of the side chat display panel that is displayed to the user after actuating element 2960.
  • a new side chat 2965 that includes the first user (“You”), Magai Martins, and Bruce Williams is displayed with a textual indicator of “You didn’t send any messages yet” and an expiration time visual indicator 2970 showing the amount of time remaining for side chat 2965.
  • Indicator 2970 may be configured to be user actuatable to allow the first user to select the amount of time (here shown as 5 minutes) (e.g., from a set of preset time options, from a custom time input element, and combinations thereof) for the expiration of a side chat, such as side chat 2965.
  • View 2908 also includes a user input element 2975 configured to allow a user to input a side message segment to side chat 2965 using a screen based keyboard 2980.
  • the side chat display panel in view 2908 also includes a return actuation control 2985.
  • a side chat display panel may include a user actuatable element to allow a user to add a user to a side chat.
  • a user actuatable element for adding a user to a side chat is displayed to a user that initiated a side chat (e.g., at the point of initiation, after initiation) to allow the user to add another user to a side chat.
  • a user actuatable element for adding a user to a side chat is displayed to a user that did not initiate a side chat.
  • a digital platform with a side chat functionality can be configured to allow only a side chat initiating user to add additional users to a side chat (e.g., by default, by user setting, by PGO setting, etc.) or, alternatively, can be configured to allow any user of a side chat to add an additional user (e.g., by default, by user setting, by PGO setting, etc.).
  • a digital platform may include human language translation functionality. Such a translation functionality may include automated translation of textual elements of an interaction object from one human language to another.
  • a user of a digital platform such as a CPOL platform according to the current disclosure, having a translation functionality may set one or more settings related to such translation functionality for their user account. In one example, such a setting may be set at an account level, at a profile level, at a PGO level, and/or for a specific contact.
  • a translation setting include, but are not limited to, an on/off setting for a translation functionality, an automatic translation setting (e.g., on/off, language of translation), a request for translation setting, a language of translation setting, an interface language setting, a spoken language setting, and any combinations thereof.
  • an automatic translation setting e.g., on/off, language of translation
  • a request for translation setting e.g., a language of translation setting, an interface language setting, a spoken language setting, and any combinations thereof.
  • a user may wish to have a language (or multiple languages, or all languages) for incoming textual elements of an interaction object translated to a designated language for display to the user on one or more user interfaces of a digital platform.
  • a digital platform can include functionality for performing a translation task and have one or more user settings for configuring one or more aspects of such tasks.
  • a digital platform may include a processing element and a database having translation data and intelligence (e.g., programming, machine learning components, artificial intelligence components, and related machine executable instructions, etc.).
  • translation data and intelligence e.g., programming, machine learning components, artificial intelligence components, and related machine executable instructions, etc.
  • One or more portions of an interaction object may be presented to such functionality of a digital platform to be translated from one language to another.
  • This functionality may be automatic based (e.g., based on a user setting) such that it automatically translates a textual portion (e.g., before displaying it to a user, upon a request to translate from the user, upon opening an interaction object or relevant subcomponent, etc.).
  • a digital platform may allow a user (e.g., via one or more user interfaces) to set one or more settings to have incoming message text of an interaction object translated automatically (e.g., if the incoming text matches a language set to be translated automatically, if the incoming text comes from a particular contact, if the interaction object is associated with a particular PGO with automatic translation set to on, etc.).
  • Such a functionality for performing a translation may reside upon one or more server computers (e.g., one or more server computers operated by or for the digital platform and/or one or more server computers operated by a third party that are connected to the platform, both of which considered a server of the corresponding platform).
  • a digital platform may be configured such that once a server computer to which a portion of an interaction object has been sent for translation has finished translating and has returned a translated portion, that no portion of the interaction object is retained at the server (e.g., it is deleted).
  • an interaction object may include multiple users (e.g., an initiating user and one or more recipient users).
  • An interaction object (and its subcomponents, such as a message segment) may include a header portion and a content portion.
  • a digital platform may be configured to have an interaction object sent to a server computer for translation by only sending a content portion to the server wherein the content portion does not include information that identifies a user (e.g., information that identifies an initiating user, information that identifies a recipient user, information that identifies any user associated with the interaction object, etc.).
  • such separation of information that identifies a user may be useful in a digital platform that delivers an interaction object to a recipient’s user device without storing the content portion or the interaction object itself at a server device or other computing device belonging to the operator of the digital platform such that if the translation functionality resides on a server of the platform, any textual element requiring translation needs to be sent (e.g., over a network) to the server for translation; a digital platform that uses a third party translation functionality such that a textual portion requiring translation needs to be sent (e.g., over a network) to a server of the third party (e.g., directly from a user device and/or from another server of the platform); and any combinations thereof.
  • a digital platform that delivers an interaction object to a recipient’s user device without storing the content portion or the interaction object itself at a server device or other computing device belonging to the operator of the digital platform such that if the translation functionality resides on a server of the platform, any textual element requiring translation needs to be sent (e
  • a header portion of an interaction object is the elements of an interaction object (or one of its subcomponents) used by a digital platform for the management of the object or for displaying in one or more user interfaces profile information about a user (e.g., information stored in a user’s profile and/or profile object settings).
  • a header portion includes information for managing the interaction object (e.g., its delivery to recipients, etc. via one or more networks used by the corresponding platform) and information that directly identifies a user associated with the interaction object (or one of its components), such as profile data and profile object settings (e.g., a profile image, a profile name, etc.).
  • Information that identifies a user includes, but is not limited to, a real name, a username, a profile image, a profile name, a profile discoverability identifier, another email address, another phone number, other profile information, and any combinations thereof.
  • information that identifies a user does not include information or a data element used solely by a digital platform to pseudonymously or anonymously route a portion of an interaction object to and/or from a user’s computing device (e.g., a machine address for a computing device, a session identifier for a session between a user computing device and a server computing device used by a platform to translate language, etc.).
  • a content portion of an interaction object is the substantive portions of an interaction object (or one of its subcomponents) that are input or associated therewith by a user for communicating that substantive portion to one or more other users as part of the interaction object.
  • a content portion includes a textual component of an interaction object that is a message room/thread wherein the textual component is part of a message from a user.
  • An interaction object residing on a computing device may require translation.
  • the textual element of the content portion requiring translation is identified and separated from information that identifies a user in the header portion.
  • a content portion may include one or more elements of information that identifies a user (e.g., a user inputs into a message text the name of another user, a phone number of another user, etc.) within the content portion itself (i.e., not in the header information). Examples of such information include, but are not limited to, information identifying a user input as text by a user, information in a file attachment of a content portion, and any combination thereof.
  • Such information may also be removed in one or more optional implementations (e.g., by using a text scan to compare known information about a user to text in a content portion and stripping such information from the content portion). Removal of such information that describes a user from a content portion itself prior to transmitting for translation may be impacted by one or more user settings (e.g., settings similar to other translation settings and located similarly as such settings including, but not limited to, an on/off setting for removal, a setting related to which types of information to remove, a setting regarding reinsertion of such information back into a content portion after translation, and any combinations thereof).
  • user settings e.g., settings similar to other translation settings and located similarly as such settings including, but not limited to, an on/off setting for removal, a setting related to which types of information to remove, a setting regarding reinsertion of such information back into a content portion after translation, and any combinations thereof).
  • a textual element of a content portion requiring translation may be identified for translation by a digital platform.
  • Example ways for identifying a content portion requiring translation include, but are not limited to, a portion of a content portion based on a translation setting (e.g., an automatic translation setting turned on, a setting identifying a type of content to be translated, etc.), a portion of a content portion requested to be translated by a user (e.g., a user viewing the content portion actuates an element of a user interface to request translation), and any combination thereof.
  • a translation setting e.g., an automatic translation setting turned on, a setting identifying a type of content to be translated, etc.
  • a portion of a content portion requested to be translated by a user e.g., a user viewing the content portion actuates an element of a user interface to request translation
  • the content portion requiring translation is then transmitted or otherwise electronically communicated to a server computing device of the platform (e.g., via a network) that includes a translation functionality without any removed information identifying a user (e.g., header information identifying a user and/or content portion information identifying a user).
  • a digital platform may utilize a pseudonymous or anonymous identifier for the data packet for purposes of routing the data to and from the server.
  • the server translates the received textual portion from one human language to another based upon one or more settings from the user sending the content portion for translation.
  • a data packet sent to the server may include information from a user’s translation settings that may be needed to effectively translate the content portion (e.g., information indicating which language into which to translate the content portion).
  • the translation of the content portion requiring translation is then transmitted or otherwise electronically communicated from the server to a computing device of the original user.
  • the server deletes the previously received content portion and translation thereof after transmission.
  • a translation of the content portion is presented to the user (e.g., via one or more user interfaces of the platform).
  • a digital platform is configured to remove one or more parts of a content portion that include information that identifies a user, such information may be added back to a translated content portion once the translated content portion is received at a user computing device.
  • FIG. 23 illustrates one exemplary implementation of a method for translating a content portion 2300.
  • an interaction object is received from a first user of a digital platform, such as a CPOL platform of the current disclosure.
  • the interaction object is a message room/thread that includes a content portion requiring translation.
  • the interaction object is a message room/thread that includes a message segment requiring translation.
  • the interaction object includes at least one other user (e.g., a recipient user).
  • the interaction object is received from a user computer of the first user at one or more server computers of the platform.
  • receiving the content portion includes receiving it at a portion of the digital platform on the first user’s computing device (e.g., an application including machine executable instructions of the platform) and then proceeding to step 2310 below without the use of a server computer (such as in a peer-to-peer configuration).
  • a portion of the digital platform on the first user’s computing device e.g., an application including machine executable instructions of the platform
  • a server computer such as in a peer-to-peer configuration
  • the interaction object is communicated to a user device of a second user of the digital platform.
  • the communication includes transmitting the interaction object from a server of the platform (e.g., via a network) to the second user’s computer device.
  • the communication includes transmitting the interaction object from the first user’s computing device (e.g., via a network) to the second user’s computing device.
  • a translation setting of the second user’s account e.g., an automatic translation setting, and translation on/off setting, a language setting indicating a target language to which to translate, a language setting indicating what language to translate, etc.
  • a content portion of the interaction object (which may be part of a subcomponent thereof, such as a content portion of a message segment) is received by the digital platform for translation.
  • the content portion is communicated from the second user’s computing device to a server of the platform having a translation functionality where the content portion is received.
  • Step 2315 may also include receiving from the second user via a user interface presented to the second user via the second user’s computing device an instruction to request translation.
  • the transmission to a server computer and reception by the server computer is initiated by a request from the second user to translate (e.g., supplemented by information from a setting or otherwise indicating a language preference).
  • the information that identifies a user in the header portion of the interaction object is not transmitted to (or received by) the server computer of the platform configured for translation.
  • one or more items of information that identifies a user from the content portion are also not transmitted (e.g., have been stripped from by the app on the user’s computer) to the server computer.
  • the textual elements of the content portion are translated at the server of the platform from one human language to a second human language (e.g., a language indicated by a language setting of the second user).
  • a second human language e.g., a language indicated by a language setting of the second user.
  • the translated content portion is transmitted to the user computer of the second user for presentation to the second user.
  • an information that identifies a user that was removed from the content portion prior to being translated at the server of the platform is added back to the content portion (e.g., by an application program portion of the platform on the user’s computer device).
  • a digital platform may include a functionality that limits or fully restricts a recipient user of an interaction object or a subcomponent thereof from forwarding the same to another user. Such a limitation may be imposed by a digital platform based upon, for example, a forwarding restriction setting of a user (e.g., via a PGO setting of a PGO associated with the corresponding interaction object, an initiating user of an interaction object, an initiating user of a subcomponent of an interaction object, etc.) and/or another forwarding restriction setup in the digital platform (e.g., by an administrator of a centrally managed profde, by the digital platform itself, etc.).
  • a forwarding restriction setting of a user e.g., via a PGO setting of a PGO associated with the corresponding interaction object, an initiating user of an interaction object, an initiating user of a subcomponent of an interaction object, etc.
  • another forwarding restriction setup in the digital platform e.g., by an administrator of a centrally managed profde, by the digital
  • Examples of a restriction on forwarding include, but are not limited to, a restriction disallowing any forwarding of an interaction object (or subcomponent thereof), a restriction allowing only a certain number of forwardings (e.g., only being able to forward a message segment once to another user, wherein the other user can then not forward the message segment further), a restriction limiting to which other one or more users an interaction object (or subcomponent thereof) may be forwarded (e.g., based on a degree of separation from an initiating user and/or a recipient user, such as being a contact of a contact, a contact of a contact’s contacts, etc.), another type of limitation or restriction on forwarding, and any combinations thereof.
  • An interaction object having a forwarding restriction may be a group interaction object.
  • the applicable forwarding restriction applies to all recipient users of the interaction object or subcomponent having the restriction.
  • the applicable forwarding restriction applies to only a subset of all of the recipient users of the interaction object or subcomponent having the restriction.
  • a digital platform may also include a functionality that allows a recipient user of an interaction object (or subcomponent thereof) to submit a request via a specific request user interface feature and/or functionality to the user responsible (e.g., a user responsible either by their settings or by initiating the interaction object/subcomponent from a profile or other part of their user account that set the limitation/restriction) for the limitation or restriction on forwarding of the interaction object (or subcomponent thereof).
  • a specific request user interface feature and/or functionality to the user responsible (e.g., a user responsible either by their settings or by initiating the interaction object/subcomponent from a profile or other part of their user account that set the limitation/restriction) for the limitation or restriction on forwarding of the interaction object (or subcomponent thereof). Examples of types of user interface features and/or functionalities that allow a user to input information and/or select to request an action are described elsewhere herein.
  • a forwarding request interface includes a functionality that allows a user to select (e.g., via a long press of a touch screen displayed object, via a mouse actuation, right clicking, hovering over, etc.) a subcomponent of an interaction object, such as a message segment of a message room/thread.
  • a subcomponent of an interaction object such as a message segment of a message room/thread.
  • selection may present an option (e.g., displayed via a pop-up menu) to request permission to forward (i.e., removal of a restriction) to the responsible user.
  • an option in a user interface for such a request may be omitted or greyed out as inactive.
  • the forwarding request received by the digital platform is presented to the responsible user (e.g., via one or more user interfaces).
  • the responsible user may then choose to take an action, such as removing all or part of the restriction, denying the request, or ignoring the request.
  • the user interface presenting the request to the user allows the user to provide an instruction related to the request (e.g., removing all of the forwarding restriction, allowing only some forwarding such as only a number of times and/or to certain users, accepting the request, denying the request, etc.).
  • the user interface presented to the user includes a display in the display of the interaction object similar to that of a subcomponent of the interaction object.
  • a special message segment generated by the platform in response to the specific interface selection by the recipient user is displayed (e.g., a graphical representation similar to other message segments (but with visual distinctive elements indicating it is a forwarding request) in line in the display with other message segments of a message thread/room) to the user indicating a request to remove a restriction.
  • the responsible/initiating user may indicate via the interface a selection of the message segment (e.g., via a long press of a touch screen displayed object, via a mouse actuation, hovering over, etc.) which causes the digital platform to present a user interface for the user to input, select, or otherwise indicate instructions related to the request.
  • the digital platform In response to a digital platform receiving instructions from the initiating/responsible user, the digital platform takes an action corresponding to the instructions.
  • the instructions being to reject the request, information about the rejection may be presented to the requesting user (e.g., via one or more user interfaces).
  • a specialized subcomponent of the corresponding interaction object is generated by the digital platform and presented to the user with information that the request was rejected.
  • the digital platform may take a corresponding action.
  • the digital platform allows the requesting user to forward the interaction object portion relevant to the request (e.g., limited by any remaining restriction on forwarding, such as only being able to forward once).
  • the digital platform prior to being allowed by the digital platform to forward the interaction object portion relevant to the request, the digital platform presents information to the requesting user to indicate to the user that the request was granted. It is noted that a removal of a forwarding restriction may only apply to the requesting user in a group interaction object and not apply to other users not making a forwarding request (e.g., the forwarding restrictions placed on an interaction object may only be removed for the particular subcomponent for which a request relates).
  • an interaction object that is governed by a PGO may have one or more settings (e.g., in a set of initiator privacy settings) that exclusively govern rules for all participant users of the interaction object with respect to forwarding limitations and requests for removal of any such limitations.
  • a platform may be configured such that an interaction object or subcomponent thereof is governed by both a setting related to automatic deletion/disappearance and a setting allowing for forwarding or requesting forwarding such that the platform may also be configured with respect to a priority of one such setting over another (e.g., an automatic deletion setting may override a forwarding allowance such that a message segment allowed to be forwarded is scheduled to delete and can no longer be forwarded thereafter, an express allowance to forward a message segment is given priority over a scheduled deletion of that message segment, and other variations on priority of settings).
  • an automatic deletion setting may override a forwarding allowance such that a message segment allowed to be forwarded is scheduled to delete and can no longer be forwarded thereafter, an express allowance to forward a message segment is given priority over a scheduled deletion of that message segment, and other variations on priority of settings).
  • a digital platform that controls the distribution of interaction objects to all users can control forwarding of an interaction object after it has been forwarded once relevant to a removal of a forwarding restriction.
  • the digital platform can govern further forwarding of the interaction object based on the initiating user’s remaining restrictions on forwarding.
  • a remaining restriction on forwarding/distribution is associated with the corresponding interaction object or subcomponent thereof (e.g., message segment), such as via a data element in the corresponding data object and/or via a table of information in the corresponding platform, and remains with the interaction object/ subcomponent after being forwarded.
  • a platform may be configured to have a remaining restriction on forwarding/distribution include a non-display of a user (e.g., an originating user of a message segment) name and/or other identity requirement with respect to a forwarded interaction object after it has been forwarded to another user (i.e., such that the other user cannot see who originated the message segment).
  • a non-display of a user e.g., an originating user of a message segment
  • identity requirement e.g., an originating user of a message segment
  • FIG. 24 illustrates one exemplary implementation of a method related to forwarding request functionality 2400.
  • a portion of an interaction object e.g., a subcomponent of an interaction object, such as a message segment
  • a restriction on forwarding associated with the portion is presented to a recipient user of the interaction object.
  • the digital platform receives a request from the recipient user for permission to forward the restricted portion of the interaction object.
  • the reception of the request is via a user interface presented to the recipient user by the digital platform specifically configured to receive a forwarding request.
  • a request to remove the forwarding restriction (e.g., all of the restriction, part of the restriction) based on the request received via the forward request interface is presented to the user that initiated the forwarding restriction.
  • a user initiating a forwarding restriction is the initiating user of the corresponding interaction object (e.g., a PGO associated with the interaction object includes a forwarding restriction, such as a forwarding restriction as part of a set of initiator privacy settings that apply to all users of an interaction object and all subcomponents).
  • a user initiating a forwarding restriction is the user that initiates a subcomponent of an interaction object (e.g., a message segment or other subcomponent in a digital platform is configured to allow such a user to set a forwarding restriction at the subcomponent level).
  • an alternative configuration for a digital platform includes a functionality for a user’s PGO recipient settings (or other settings) for a PGO associated with an interaction object to include a forwarding restriction setting that applies to subcomponents that are initiated by that user (e.g., with a variation where any such setting may be overridden by the initiator privacy settings of the user initiating the interaction object if conflicting with such initiator privacy settings).
  • the digital platform receives instructions from the initiating user regarding the forwarding request. If the instructions are to deny the request, the digital platform may take an action as discussed above (e.g., notification to the requesting user) and method 2400 may not continue to step 2425.
  • the digital platform allows the requesting user to forward the relevant portion of the interaction object for which the instructions from the initiating user allows forwarding (and to the extent allowed by any remaining restrictions).
  • any one or more of the aspects, ideas, concepts, implementations, examples, and embodiments described herein may be conveniently implemented using one or more machines (referred to hererin as a computing device, e.g., one or more user computing devices, one or more server devices,) programmed according to the teachings of the present disclosure, as will be apparent to those of ordinary skill in the computer art.
  • Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those of ordinary skill in the software and related platform arts.
  • Aspects, ideas, concepts, implementations, examples, and embodiments discussed herein may employ software and/or software modules and may also include appropriate hardware for assisting in the implementation of the machine executable instructions of the software and/or software module.
  • Such software may be a computer program product that employs a machine-readable storage medium.
  • a machine-readable storage medium may be any medium that is capable of storing and/or encoding a sequence of instructions for execution by a machine (e.g., a computing device) and that causes the machine to perform any one of the methodologies and/or embodiments described herein, except that a machine-readable storage medium is not a medium that simply transports data from one point to another without a time period (however short or long) of storage in a hardware material (e.g., a signal is not a machine-readable storage medium).
  • Examples of a machine-readable storage medium include, but are not limited to, a solid state memory, a flash memory, a random access memory (e.g., a static RAM “SRAM”, a dynamic RAM “DRAM”, etc.), , a magnetic memory (e.g., a hard disk, a tape, a floppy disk, etc.), an optical memory (e.g., a compact disc (CD), a digital video disc (DVD), a Blu-ray disc (BD); a readable, writeable, and/or re-writable disc, etc.), a read only memory (ROM), a programmable read-only memory (PROM), a field programmable read-only memory (FPROM), a one-time programmable non-volatile memory (OTP NVM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), and any combinations thereof., and any combinations thereof.
  • ROM read only memory
  • non-transitory in relation to a medium refers to a hardware storage medium that stores machine-readable instructions for a period of time, even if that time period is extremely small or temporary, and even if the storage of such instructions is fragile or reliant upon the provision of a continued electrical source.
  • the examples of a machine- readable storage medium listed above in this paragraph are considered non-transitory.
  • machine executable instructions for a CPOL platform may, in addition to one or more other machine- readable storage media, be stored in a RAM memory of a computing device (e.g., in RAM memory of a user computing device while a user accesses the digital platform, in RAM memory of a cloud computing device while the platform is being accessed and/or operating, in combination of memory locations in a distributed network environment, etc.) for short periods of time and/or only while the computing device is powered on.
  • the RAM memory may be referred to, for example, as a non-transitory medium
  • a machine-readable medium is intended to include a single medium as well as a collection of physically separate media (localized and/or dispersed physically as in a distributed digital platform having a portion of machine-executable instructions on one or more server computers and/or one or more user devices), such as, for example, a collection of compact disks, one or more hard disk drives in combination with a computer memory, an array of RAM modules, etc.
  • the term “memory” includes examples that would include one or more machine-readable storage media.
  • the term “machine-readable storage medium” does not include a signal, carrier wave, or similar non-hardware based forms of encoding data, by themselves such forms being transitory in nature.
  • Such software may also include information (e.g., data, instructions, etc.) carried as a data signal on a data carrier, such as a carrier wave.
  • a data carrier such as a carrier wave.
  • machine-executable information may be included as a data-carrying signal embodied in a data carrier in which the signal encodes a sequence of instruction, or portion thereof, for execution by a machine (e g., a computing device) and any related information (e g., data structures and data) that causes the machine to perform any one of the methodologies and/or embodiments described herein.
  • machine e g., a computing device
  • any related information e g., data structures and data
  • Such examples are not to be considered a machine-readable storage medium as that term is used herein. However, it is contemplated that such examples may be used in implementing one or more aspects, ideas, concepts, implementations, examples, and embodiments of the current disclosure if appropriate.
  • Machine-executable instructions may be disbursed across a plurality of computing devices (e.g., one or more user devices and one or more server computers) and connected via one or more networks, such as in the example shown in FIG. 1 above.
  • computing devices e.g., one or more user devices and one or more server computers
  • networks such as in the example shown in FIG. 1 above.
  • a computing device is any machine that is capable of executing machine-executable instructions to perform one or more tasks.
  • Examples of a computing device include, but are not limited to, a tablet, an electronic book reading device, a workstation computer, a terminal computer, a server computer, a laptop computer, a mobile telephone (e.g., a smartphone), a portable and/or handheld computing device, a wearable computing device (e.g., a watch), a web appliance, a network router, a network switch, a network bridge, one or more application specific integrated circuits, an application specific programmable logic device, an application specific field programmable gate array, any machine capable of executing a sequence of instructions that specify an action to be taken by that machine (e.g., an optical, chemical, biological, quantum and/or nanoengineered system and/or mechanism), and any combinations thereof.
  • a computing device may include and/or be included in, a kiosk.
  • a computing device is a smartphone.
  • a computing device may include and/or be programed with specific machine-executable instructions (e.g., to perform one or more of the features, aspects, examples, or implementation of the current disclosure; to operate the computing device generally) and include required circuitry and components such that the combination of the circuitry/components and the instructions allow it to perform as a specialized machine in one or more of the implementations disclosed in the current disclosure.
  • a computing device may utilize any of a variety of known or yet to be developed operating systems, firmware, and/or other software for its operation.
  • Examples of an operating system include, but are not limited to, Apple’s iOS, Amazon’s Fire OS, Google’s Android operating system, Microsoft’s Windows Phone operating system, Microsoft’s Windows operating system, Apple’s Operating System, a Linux-kernel based operating system, and any combinations thereof.
  • a network is a way for connecting two or more computing devices to each other for communicating information (e.g., data, machine-executable instructions, image files, video files, electronic messages, etc.).
  • Examples of a network include, but are not limited to, a wide area network (e.g., the Internet, an enterprise network), a local area network (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a short distance network connection, a telephone network, a data network associated with a telephone/voice provider (e.g., a mobile communications provider data and/or voice network), another data network, a direct connection between two computing devices (e.g., a peer-to-peer connection), a proprietary serviceprovider network (e.g., a cable provider network), a wired connection, a wireless connection (e g., a Bluetooth connection, a Wireless Fidelity (Wi-Fi) connection (such as an IEEE 802.11 connection), a Worldwide Interoperability
  • a network may employ one or more wired, one or more wireless, and/or one or more other modes of communication.
  • a network may include any number of network segment types and/or network segments.
  • a network connection between two computing devices may include a Wi-Fi connection between a sending computing device and a local router, an Internet Service Provider (ISP) owned network connecting the local router to the Internet, an Internet network (e.g., itself potentially having multiple network segments) connection connecting to one or more server computing devices and also to a wireless network (e g., mobile phone) provider of a recipient computing device, and a telephone-service-provider network connecting the Internet to the recipient computing device.
  • ISP Internet Service Provider
  • FIG. 25 illustrates one example diagrammatic representation of one implementation of a computing device 2500.
  • Computing device 2500 includes a processing element 2505, a memory 2510, a display generator 2515, a user input 2520, a networking element 2525, and a power supply 2530.
  • Processing element 2505 includes circuitry and/or machine-executable instructions (e.g., in the form of firmware stored within a memory element included with and/or associated with processing element 2505) for executing instructions for completing one or more tasks (e.g., tasks associated with one or more of the implementations, methodologies, features, aspects, and/or examples described herein). Examples of a processing element include, but are not limited to, a microprocessor, a microcontroller, one or more circuit elements capable of executing a machineexecutable instruction, and any combinations thereof.
  • Memory 2510 may be any device capable of storing data (e.g., user data as part of or affiliated with a CPOL platform or other digital platform, information input by a user, information stored by a user, information received at computing device 2500 as part of a CPOL or other digital platform, etc.), machine-executable instructions, an operating system, an “app” as part of a CPOL or other digital platform, a basic input/output system (BIOS) including basic routines that help to transfer information between components of a computing device, and/or other information related to one or more of the implementations, methodologies, features, aspects, and/or examples described herein.
  • a memory such as memory 2510, may include one or more machine-readable storage medium.
  • a memory may be removable from device 2500.
  • a memory such as memory 2510, may include and/or be associated with a memory access device.
  • a memory may include a medium for storage and an access device including one or more circuitry and/or other components for reading from and/or writing to the medium.
  • a computing device may include a port (e.g., a Universal Serial Bus (USB) port) for accepting a memory component (e.g., a removable flash USB memory device).
  • USB Universal Serial Bus
  • Device 2500 includes camera 2515 connected to processing element 2505 (and other components).
  • a camera include, but are not limited to, a still image camera, a video camera, and any combinations thereof.
  • Display component 2520 is connected to processing element 2505 for providing a display according to any one or more of the implementations, examples, aspects, etc. of the current disclosure (e.g., providing an interface, displaying separated display screens for each of a plurality of portions of an image, etc.).
  • a display component 2515 may include a display element, a driver circuitry, display adapter, a display generator, machine-executable instructions stored in a memory for execution by a processing element for displaying still and/or moving images on a screen, and/or other circuitry for generating one or more displayable images for display via a display element.
  • Example display elements are discussed below.
  • a display element is integrated with device 2500 (e.g., a built-in LCD touch screen).
  • a display element is associated with device 2500 in a different fashion (e.g., an external LCD panel connected via a display adapter of display component 2515).
  • User input 2525 is configured to allow a user to input one or more commands, instructions, and/or other information to computing device 2500.
  • user input 2525 is connected to processing element 2505 (and optionally to other components directly or indirectly via processing element 2505) to allow a user to interface with computing device 2500 (e.g., to actuate camera 2515, to input instructions, information, or other inputs for performing (or as otherwise needed for) one or more aspects and/or methodologies of the present disclosure).
  • Examples of a user input include, but are not limited to, a keyboard, a keypad, a screen displayable input (e.g., a screen displayable keyboard), a button, a toggle, a microphone (e.g., for receiving audio instructions), a pointing device, a joystick, a gamepad, a cursor control device (e.g., a mouse), a touchpad, an optical scanner, a video/image capture device (e.g., a camera), a touch screen of a display element/component, a pen device (e.g., a pen that interacts with a touch screen and/or a touchpad), and any combination thereof.
  • a user input include, but are not limited to, a keyboard, a keypad, a screen displayable input (e.g., a screen displayable keyboard), a button, a toggle, a microphone (e.g., for receiving audio instructions), a pointing device, a joystick, a gamepad, a cursor control
  • camera 2515 and/or a touch screen of a display element of display component 2520 may function also as an input element. It is also contemplated that one or more commands, data, and/or other information may be input to a computing device via a data transfer over a network and/or via a memory device (e.g., a removable memory device).
  • a user input, such as user input 2525, may be connected to computing device 2500 via an external connector (e.g., an interface port).
  • External interface element 2530 includes circuitry and/or machine-executable instructions (e.g., in the form of firmware stored within a memory element included with and/or associated with interface element 2530) for communicating with one or more additional computing devices and/or connecting an external device to computing device 2500.
  • An external interface element, such as element 2530 may include one or more external ports.
  • an external interface element includes an antenna element for assisting with wireless communication.
  • an external interface element examples include, but are not limited to, a network adapter, a Small Computer System Interface (SCSI), an advanced technology attachment interface (ATA), a serial ATA interface (SATA), an Industry Standard Architecture (ISA) interface, an extended ISA interface, a Peripheral Component Interface (PCI), a Universal Serial Bus (USB), an IEEE 1394 interface (FIREWIRE), and any combinations thereof.
  • a network adapter includes circuitry and/or machine-executable instructions configured to connect a computing device, such as computing device 2500, to a network.
  • Power supply 2530 is shown connected to other components of computing device 2505 to provide power for operation of each component.
  • Examples of a power supply include, but are not limited to, an internal power supply, an external power supply, a battery, a fuel cell, a connection to an alternating current power supply (e.g., a wall outlet, a power adapter, etc.), a connection to a direct current power supply (e g., a wall outlet, a power adapter, etc ), and any combinations thereof.
  • Components of device 2500 are shown as single components.
  • a computing device may include multiple components of the same type.
  • a function of any one component may be performed by any number of the same components and/or in conjunction with another component.
  • the functionality of any two or more of processing element 2505, memory 2510, camera 2515, display component 2520, user input 2525, interface element 2530, power supply 2535, and another component of a computing device may be combined in an integrated circuit.
  • a processor may include a memory for storing one or more machine executable instructions for performing one or more aspects and/or methodologies of the present disclosure. Functionality of any one or more components may also be distributed across multiple computing devices. Such distribution may be in different geographic locations (e.g., connected via a network). Components of device 2500 are shown as internal components to device 2500. A component of a computing device, such as device 2500, may be associated with the computing device in a way other than by being internally connected.
  • Examples of ways to connect components of a computing device include, but are not limited to, a bus, a component connection interface, another type of connection, and/or any combinations thereof.
  • Examples of a bus and/or component connection interface include, but are not limited to, a memory bus, a memory controller, a peripheral bus, a local bus, a parallel bus, a serial bus, a SCSI interface, an ATA interface, an SATA interface, an ISA interface, a PCI interface, a USB interface, a FIREWIRE interface, and any combinations thereof.
  • Various bus architectures are known. Select connections and components in device 2500 are shown.
  • a computing device may omit in certain implementations one or more of the shown components.
  • FIG. 26 illustrates one example of a portable handheld computing device in the form of a smartphone 2600.
  • Smartphone 2600 includes a body 2605, a microphone input element 2610, a display element 2615, and a speaker output element 2620.
  • Display element 2615 may be a touch screen to provide a user with additional input interface capabilities.
  • a computing device, such as smartphone 2600, may be used in a variety of ways with respect to any of the implementations, embodiments, and/or methodologies described herein.
  • Exemplary ways to utilize smartphone 2600 include, but are not limited to, receiving an instruction (and/or other input, request, etc.) from a user of a computing device, presenting information or other displayable aspects to a user of a digital platform, and any combinations thereof.
  • Examples of a display element or component include, but are not limited to, a computer monitor, a liquid crystal display (LCD) display screen, a light emitting diode (LED) display screen, a touch display, a cathode ray tube (CRT), a plasma display, a projection device, a holographic device, and any combinations thereof.
  • a display element may include, be connected with, and/or associated with adjunct elements to assist with the display of still and/or moving images.
  • an adjunct display elements include, but are not limited to, a display generator (e.g., image/image display circuitry), a display adapter, a display driver, machine-executable instructions stored in a memory for execution by a processing element for displaying still and/or moving images on a screen, and any combinations thereof.
  • display devices may be included in any of a variety of known forms including, but not limited to, a display element directly connected to a computing device, a display element connected to a computing device via a wire, a display element wirelessly connected, a display element of a headset device, a display element of a stand-alone device, a display element of an eyeglass device, and any combinations thereof.
  • a CPOL platform of the current disclosure includes one or more user interfaces that display images, text, and/or graphic elements to a user (e.g., via a display device associated with a user computing device) and allow a user to interact with a CPOL platform (e g., via one or more user inputs, such as a mouse, touch screen, etc ).
  • Multiple users can access and interact with exemplary implementations of a CPOL platform and, optionally, interact with each other (e.g., taking part in electronic messaging, scheduling time, event management, time management, lifestyle organization, business interactivity, interactive play, sharing of user generated content, sharing of third-party content, taking part in events presented via the CPOL platform, interacting as will be understood by those of ordinary skill by the current disclosure, otherwise interacting as is well known and common in online platforms, and combinations of such interactions).
  • each other e.g., taking part in electronic messaging, scheduling time, event management, time management, lifestyle organization, business interactivity, interactive play, sharing of user generated content, sharing of third-party content, taking part in events presented via the CPOL platform, interacting as will be understood by those of ordinary skill by the current disclosure, otherwise interacting as is well known and common in online platforms, and combinations of such interactions).
  • a user may interact with a user interface via actuation of user interface elements and inputting information.
  • Example input elements for interacting with a user include, but are not limited to, a radio button, a toggle switch, a pull-down menu, a text entry field, a hover button, a drag and drop functionality, a pop-up menu, a right-click menu, a screen displayed keyboard (e.g., a touchscreen keyboard), and any combinations thereof.
  • Examples of interactions with a user interface include, but are not limited to, providing instructions to a digital platform, inputting information to a digital platform (e g., information required for a user setting, information for an interaction object or subcomponent thereof, information for a request, etc.), actuating a user interface element, making a selection (e.g., selecting an option in a menu), make an association of one object with another object (e.g., associating a PGO with an interaction object, associating a user with a profile, associating a user with an interaction object, etc ), inputting text, typing (e.g., on an onscreen keyboard), hovering, and any combinations thereof.
  • Other example user input element actuations and combinations of actuations will be understood and applicable depending on the particular computing device, interface, display element, etc.
  • a user interface may be presented to a user as multiple screen displays presented at different times to a user (e.g., in succession). Additionally, multiple user interfaces may be provided as a combined interface (e.g., such that the combined interface displays combined functionality at the same time to a user). Examples of ways to combine functionality in a screen display interface include, but are not limited to, using different portions of a screen display of an interface for different functionality, superimposing a user actuatable element of a screen display over another element of a screen display (e.g., superimposing user actuatable elements for performing one or more functions over an interaction object or subcomponent thereof), and any combinations thereof. Examples of a user actuatable element include but are not limited to, a graphical element, a textual element, an image element, an element selectable using a pointer device, an element selectable using a touch screen actuation, and any combinations thereof.
  • a user of a digital platform may utilize one or more user interfaces of the platform to input, make a selection, provide, be presented to, otherwise provide information and/or otherwise interact with the platform (and/or other users) as required by any one or more of the details, concepts, aspects, features, characteristics, examples, and/or alternatives of an implementation, embodiment, method, and/or other methodology disclosed herein.
  • a method of interaction on a digital platform comprising: presenting a group message room to a first user of the platform, the group message room including participant users that are the first user and at least two additional users of the platform, the group message room displaying a message thread having one or more group message segments; receiving from the first user a first request to initiate a side chat with a second user of the at least two additional users; and displaying one or more side message segments of the side chat within the group message room along with the one or more group message segments when displaying the group message room to the first user and the second user while omitting the display of the one or more side message segments from the display of the group message room to any of the at least two additional users that are not a member of the side chat, wherein the display of the one or more side message segments includes a side chat distinctive visual display feature.
  • the group message room is a representation of an interaction object, the group message room being initiated by an initiating user of the participant users, the interaction object being associated with a first privacy governance object of a first account of the initiating user, the first privacy governance object including a first set of initiator privacy settings and a first set of recipient settings. 3. A method according to example 2, wherein the first set of initiator privacy settings applies to the interaction object regardless of which of the participant users are interacting with the interaction object.
  • each of the participant users that is not the initiating user are a recipient user, the interaction object being associated with a corresponding additional privacy governance object of a user account corresponding to each recipient user, each corresponding additional privacy governance object including an additional set of initiator privacy settings and an additional set of recipient settings.
  • each of participant users that is not the initiating user are a recipient user, the interaction object being associated with a corresponding additional privacy governance object of a user account corresponding to each recipient user, each corresponding additional privacy governance object including an additional set of initiator privacy settings and an additional set of recipient settings.
  • a method according to example 9 further comprising presenting the group message room to the initiating user based on the first set of recipient settings.
  • a method according to example 14, wherein the applying the second set of initiator privacy settings includes applying the second set of initiator privacy settings to all of the one or more group message segments and all of the one or more side message segments of the group message room.
  • applying the second set of initiator privacy settings includes: applying the second set of initiator privacy settings to any new message segments of the one or more group message segments created in the group message room after the receiving the second request; and maintaining the application of the first set of initiator privacy settings to any message segments of the one or more group message segments to which the first set of initiator privacy settings previously applied.
  • applying the second set of initiator privacy settings further includes: applying the second set of initiator privacy settings to any new message segments of the one or more side message segments created in the group message room after the receiving the second request; and maintaining the application of the first set of initiator privacy settings to any message segments of the one or more side message segments to which the first set of initiator privacy settings previously applied.
  • a method according to any one of examples 2 to 11, wherein a first message segment of the one or more group message segments and one or more side message segments is governed by a distribution restriction, the method further comprising: receiving from a first recipient user of the recipient users a third request via a request user interface to remove the distribution restriction from the first message segment; presenting a removal user interface to the initiating user, the removal user interface including information based on the third request and requesting the initiating user to remove the distribution restriction from the first message segment; receiving a distribution instruction from the initiating user to remove all or a portion of the distribution restriction; and allowing the first recipient user to forward the first message segment based on the distribution instruction from the initiating user.
  • a method according to example 23, wherein the limit on the number of times the first message segment can be forwarded is a number of times that is more than one time.
  • first privacy governance object and/or each of the additional privacy governance objects originates from a first profile of a plurality of profiles of a user account having the corresponding one of the first privacy governance object and/or additional privacy governance objects.
  • a set of initiator privacy settings is a set of settings governing the privacy and security behavior and environment of the interaction object.
  • a set of recipient settings is a set of settings governing a display and general behavior of the interaction object as the interaction object is presented to a user.
  • the first set of initiator privacy settings and/or any additional set of initiator privacy settings includes a setting selected from the group consisting of an interaction object expiration, a forwarding setting, a side chat setting, an encryption setting, a screen capture setting, a forwarding request setting, a calendar event sharing limitation, a storage limitation, a retention setting, and any combinations thereof.
  • the first set of recipient settings and/or any additional set of recipient settings includes a setting selected from the group consisting of a translation setting, a notification setting, a group notification setting, a display setting, a language setting, and any combinations thereof.
  • a method further comprising: receiving a first content portion of a second message segment of the one or more group message segments and the one or more side message segments from a user device of a third user of the group message room, the third user being one of the participant users that has access to the second message segment in the group message room, the receiving a first content portion being without header information of the second message segment that identifies a user of the group message room; translating the first content portion from a first human language to a second human language; transmitting the translated first content portion to the user device of the third user; and presenting the translated first content portion to the third user.
  • a method according to example 43 further comprising removing from the first content portion one or more pieces of identifying information from the first content portion itself that identifies a user of the group message room.
  • a method according to example 45 further comprising adding the one or more pieces of identifying information back to the translated first content portion prior to presenting the translated first content portion to the third user.
  • a method according to examples 44 further comprising adding the one or more pieces of identifying information back to the translated first content portion prior to presenting the translated first content portion to the third user.
  • the translation setting includes a setting selected from the group consisting of , an on/off setting for a translation functionality, an automatic translation setting (e.g., on/off, language of translation), a request for translation setting, a language of translation setting, an interface language setting, a spoken language setting, and any combinations thereof.
  • the translation setting includes an automatic translation setting that is set to on and the receiving a first content portion occurs based on the user device of the third user having automatically transmitted the first content portion based on the automatic translation setting.
  • the translation setting includes a setting that requires the third user to provide a translation instruction via the user device of the third user for the second message segment to be translated and the receiving the first content portion occurs based on the user device of the third user having transmitted the first content portion based on the translation instruction.
  • the translation setting includes a setting indicating which incoming message segment language is to be translated and the language of the first content portion matches the set incoming message segment language.
  • a method wherein one or more message segments of the group message room is governed by a distribution restriction, the group message room being initiated by an initiating user of the participant users, each of the other users of the participant users that is not the initiating user being a recipient user, the method further comprising: receiving from a first recipient user a fourth request via a request user interface to remove the distribution restriction from the one or more message segments; presenting a removal user interface to the initiating user, the removal user interface including information based on the fourth request and requesting the initiating user to remove the distribution restriction from the one or more message segments; receiving a distribution instruction from the initiating user via an instructions user interface, the distribution instruction including a direction to the digital platform to deny the fourth request or to remove all or a portion of the distribution restriction; and taking a removal related action based on the distribution instruction.
  • a method according to example 72, wherein the allowing the first recipient user to forward the one or more message segments includes a remaining restriction on distribution.
  • a method according to example 74, wherein the limit on the number of times the one or more message segments can be forwarded is a number of times that is more than one time.
  • the fourth request includes a request related to all message segments of the interaction object, and the removal related action relates to all message segments of the interaction object.
  • the group message room is a representation of an interaction object, the group message room being initiated by an initiating user that is the first user, the second user being associated with a select user profile of a first set of user profiles of a initiating user account, the select user profile having a select set of profile object settings, wherein when the initiating user interacts with the second user via the platform the platform presents the initiating user to the second user based on the first set of profile object settings and the displaying one or more side message segments occurs when a second user profile of the first set of user profiles is set as an active profile for the initiating user, the second user profile including a second set of profile object settings wherein at least one value of the second set of profile object settings is different from the corresponding value of the select set of profile object settings.
  • a method according to example 85 further comprising: associating a second contact user with the second user profile; presenting to the initiating user a fifth user interface wherein the first user profile is set as the active profile; and generating a second interaction object between the initiating user and the second contact user while the first user profile is the active profile wherein the second interaction object is presented to the second contact user governed by the second set of profile object settings.
  • a method according to example 85 further comprising: associating a second contact user with the second user profile; adding the second contact user to the first interaction object wherein the first interaction object is presented to the second contact user governed by the second set of profile object settings.
  • the first set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • the second set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • a method according to any one of examples 85 to 89, wherein the first profile is set as the active profile by a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • the side chat distinctive visual display feature includes a feature selected from the group consisting of a color difference, a message segment bubble shape difference, a textual indicator, a graphical indicator, and any combinations thereof.
  • the side chat distinctive visual display feature includes a feature selected from the group consisting of a color difference, a message segment bubble shape difference, a textual indicator, a graphical indicator, and any combinations thereof.
  • the presenting of the group message room includes a display of a side chat actuation control and the one or more side segments are displayed via a slide screen display that upon actuation of the side chat actuation control covers at least a portion of the one or more group message segments to display the one or more side message segments.
  • the presenting of the group message room includes a display of a side chat actuation control and the method further comprises: receiving from the first user or the second user via a respective mobile device an actuation of the side chat actuation control; displaying a side chat display screen over at least a portion of the one or more group chat messages to display the one or more side message segments.
  • the side chat display screen includes a return actuation control and the method further comprises: receiving from the first user or the second user via a respective mobile device an actuation of the return chat actuation control; removing the side chat display screen such that the one or more group message segments are viewable and the side chat display screen is not viewable.
  • a method further comprising: receiving from the first user or the second user a request to add an additional one or more users of the at least two users to the side chat; and allowing the additional one or more users to view a display of the one or more side message segments.
  • the one or more other side chat settings includes a setting selected from the group consisting of a time period of auto deletion for a message segment of a side-chat, a number of times a message segment of a side chat may be viewed by a user, a time period until expiration of a side chat thread, a preference for a side chat distinctive visual display feature, availability of option to invite a third or additional member to a side chat, and any combinations thereof.
  • the side chat distinctive visual display feature includes a feature selected from the group consisting of a color difference, a message segment bubble shape difference, a textual indicator, a graphical indicator, a pop-up screen or window, a side chat display panel, a slide screen, and any combinations thereof.
  • the side chat distinctive visual display feature includes a color difference.
  • a method of interaction on a digital platform comprising: presenting a group message room to a first user of the platform, the group message room including participant users that are the first user and at least two additional users of the platform, the group message room including a message thread having one or more group message segments; allowing the first user and a subset of users of the at least two additional users to participate in a side chat within the group message room, any of the at least two additional users not a part of the subset users being non-participating users; displaying one or more side message segments of the side chat within the group message room, the one or more side message segments being created by the first user and/or one or more of the subset users, wherein the one or more side message segments are only displayed in the group message room to the first user and the subset users and the one or more side message segments are not displayed in the group message room to any nonparticipating users.
  • the group message room is a representation of an interaction object, the group message room being initiated by an initiating user of the first user and the at least two additional users, the interaction object being associated with a first privacy governance object of a first account of the initiating user, the first privacy governance object including a first set of initiator privacy settings and a first set of recipient settings.
  • the first set of initiator privacy settings applies to the interaction object regardless of which of the participant users are interacting with the interaction object.
  • each of the participant users that is not the initiating user are a recipient user, the interaction object being associated with a corresponding additional privacy governance object of a user account corresponding to each recipient user, each corresponding additional privacy governance object including an additional set of initiator privacy settings and an additional set of recipient settings.
  • a method according to example 140 further comprising presenting the group message room to each recipient user based on the corresponding additional set of recipient settings for the corresponding recipient user.
  • a method according to example 142 wherein each of the participant users that is not the initiating user are a recipient user, the interaction object being associated with a corresponding additional privacy governance object of a user account corresponding to each recipient user, each corresponding additional privacy governance object including an additional set of initiator privacy settings and an additional set of recipient settings.
  • a method according to example 144 further comprising presenting the group message room to each recipient user based on the corresponding additional set of recipient settings for the corresponding recipient user.
  • a method according to any one of examples 136 to 147, further comprising: receiving a second request from the initiating user to change the association of the interaction object from being associated with the first privacy governance object to a second privacy governance object of the first account, the second privacy governance object including a second set of initiator privacy settings and a second set of recipient settings; and applying the second set of initiator privacy settings to the interaction object regardless of which of the participant users are interacting with the interaction object.
  • a method according to example 148, wherein the applying the second set of initiator privacy settings includes applying the second set of initiator privacy settings to all of the one or more group message segments and all of the one or more side message segments of the group message room.
  • a method according to example 149, wherein the applying the second set of initiator privacy settings includes: applying the second set of initiator privacy settings to any new message segments of the one or more group message segments created in the group message room after the receiving the second request; and maintaining the application of the first set of initiator privacy settings to any message segments of the one or more group message segments to which the first set of initiator privacy settings previously applied.
  • a method according to example 157, wherein the limit on the number of times the first message segment can be forwarded is a number of times that is more than one time.
  • a method further comprising: receiving a first content portion of a second message segment of the one or more group message segments and the one or more side message segments from a user device of a third user of the group message room, the third user being one of the participant users that has access to the second message segment in the group message room, the receiving a first content portion being without header information of the second message segment that identifies a user of the group message room; translating the first content portion from a first human language to a second human language; transmitting the translated first content portion to the user device of the third user; and presenting the translated first content portion to the third user.
  • a method according to example 177 further comprising removing from the first content portion one or more pieces of identifying information from the first content portion itself that identifies a user of the group message room.
  • a method according to example 179 further comprising adding the one or more pieces of identifying information back to the translated first content portion prior to presenting the translated first content portion to the third user.
  • the translation setting includes a setting selected from the group consisting of , an on/off setting for a translation functionality, an automatic translation setting (e.g., on/off, language of translation), a request for translation setting, a language of translation setting, an interface language setting, a spoken language setting, and any combinations thereof.
  • the translation setting includes an automatic translation setting that is set to on and the receiving a first content portion occurs based on the user device of the third user having automatically transmitted the first content portion based on the automatic translation setting.
  • a method according to any one of examples 185 to 192, wherein the translation setting includes a setting that requires the third user to provide a translation instruction via the user device of the third user for the second message segment to be translated and the receiving the first content portion occurs based on the user device of the third user having transmitted the first content portion based on the translation instruction.
  • the translation setting includes a setting indicating which incoming message segment language is to be translated and the language of the first content portion matches the set incoming message segment language.
  • the translation setting includes a setting indicating which destination language a message segment is to be translated to and the translating the first content portion includes translating to the destination language.
  • a method according to any one of examples 135 to 201, wherein one or more message segments of the group message room is governed by a distribution restriction, the group message room being initiated by an initiating user of the participant users, each of the other users of the participant users that is not the initiating user being a recipient user, the method further comprising: receiving from a first recipient user a fourth request via a request user interface to remove the distribution restriction from the one or more message segments; presenting a removal user interface to the initiating user, the removal user interface including information based on the fourth request and requesting the initiating user to remove the distribution restriction from the one or more message segments; receiving a distribution instruction from the initiating user via an instructions user interface, the distribution instruction including a direction to the digital platform to deny the fourth request or to remove all or a portion of the distribution restriction; and taking a removal related action based on the distribution instruction.
  • a method according to example 206, wherein the allowing the first recipient user to forward the one or more message segments includes a remaining restriction on distribution.
  • a method according to example 208, wherein the limit on the number of times the one or more message segments can be forwarded is a number of times that is more than one time.
  • the fourth request includes a request relates to all message segments of the interaction object, and the removal related action relates to all message segments of the interaction object.
  • the group message room is a representation of an interaction object, the group message room being initiated by an initiating user that is the first user, the second user being associated with a select user profile of a first set of user profiles of a initiating user account, the select user profile having a select set of profile object settings, wherein when the initiating user interacts with the second user via the platform the platform presents the initiating user to the second user based on the first set of profile object settings and the displaying one or more side message segments occurs when a second user profile of the first set of user profiles is set as an active profile for the initiating user, the second user profile including a second set of profile object settings wherein at least one value of the second set of profile object settings is different from the corresponding value of the select set of profile object settings.
  • a method according to example 219 further comprising: associating a second contact user with the second user profile; presenting to the initiating user a fifth user interface wherein the first user profile is set as the active profile; and generating a second interaction object between the initiating user and the second contact user while the first user profile is the active profile wherein the second interaction object is presented to the second contact user governed by the second set of profile object settings.
  • the first set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • the second set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a method according to any one of examples 135 to 228, wherein the presenting of the group message room includes a display of a side chat actuation control and the one or more side segments are displayed via a slide screen display that upon actuation of the side chat actuation control covers at least a portion of the one or more group message segments to display the one or more side message segments.
  • a method according to any one of examples 135 to 228, wherein the presenting of the group message room includes a display of a side chat actuation control and the method further comprises: receiving from the first user or one of the subset of users via a respective mobile device an actuation of the side chat actuation control; displaying a side chat display screen over at least a portion of the one or more group chat messages to display the one or more side message segments.
  • the side chat display screen slides over the at least a portion of the one or more group messages.
  • a method according to any one of examples 234 to 238, wherein the side chat screen display includes a return actuation control and the method further comprises: receiving from the first user or one of the subset of users via a respective mobile device an actuation of the return chat actuation control; removing the side chat screen display such that the one or more group message segments are viewable and the side chat screen display is not viewable.
  • a method according to any one of examples 135 to 239, further comprising: receiving from the first user or one of the subset of users a request to add an additional one or more users of the at least two users to the side chat; and allowing the additional one or more users to view a display of the one or more side message segments.
  • a method according to any one of examples 135 to 239, wherein the side chat, one or more side message segments, a side chat distinctive visual display feature, and/or any side chat display panel is governed by one or more other side chat settings.
  • a method according to any one of examples 135 to 260, wherein the displaying one or more side message segments includes a side chat distinctive visual display feature, wherein the side chat distinctive visual display feature includes a feature selected from the group consisting of a color difference, a message segment bubble shape difference, a textual indicator, a graphical indicator, a pop-up screen or window, a side chat display panel, a slide screen, and any combinations thereof.
  • a method according to example 261 wherein the side chat distinctive visual display feature includes a message segment bubble shape difference.
  • a method of interaction on a digital platform including a first user account for a first user of the digital platform, the first user account including a first profile set of at least two profiles, the method comprising: receiving from the first user at least one profile discoverability identifier for each profile of the first profile set via a first user interface of the platform, each profile of the first profile set having a set of discoverability settings and a set of profile object settings; receiving from a second user via a second user interface of the platform a search request including a first search identifier; matching the first search identifier to a first profile discoverability identifier of the at least one profile discoverability identifiers, the first profile discoverability identifier being for a first profile of the first profile set; presenting, based on said matching, a request to connect to the first user, said presenting including a third user interface of the platform, the third user interface including an option to associate the second user to one profile of the first profile set, wherein the option includes the first profile and at least one additional profile of the
  • a method further comprising: receiving from a side chat initiating user a first request to initiate a side chat with a side chat recipient user, the side chat initiating user and the side chat recipient user each being group member user; and displaying one or more side message segments of the side chat within the group message room along with the one or more group message segments when displaying the group message room to the side chat initiating user and the side chat recipient user while omitting the display of the one or more side message segments from the display of the group message room to any of group member users that are not a member of the side chat, wherein the display of the one or more side message segments includes a side chat distinctive visual display feature.
  • a method according to any one of examples 269 to 277, wherein the first interaction object includes a message thread and one or more message segments of the message thread is governed by a distribution restriction, the first interaction object being initiated by an initiating user of the first user and second user, the other user of the interaction object that is not the initiating user being a recipient user, the method further comprising: receiving from a first recipient user a fourth request via a request user interface to remove the distribution restriction from the one or more message segments; presenting a removal user interface to the initiating user, the removal user interface including information based on the fourth request and requesting the initiating user to remove the distribution restriction from the one or more message segments; receiving a distribution instruction from the initiating user via an instructions user interface, the distribution instruction including a direction to the digital platform to deny the fourth request or to remove all or a portion of the distribution restriction; and taking a removal related action based on the distribution instruction.
  • the first interaction object includes participant users that are the first user, the second user, and optionally at least one additional user of the platform, the first interaction object being initiated by an initiating user of the participant users, the interaction object being associated with a first privacy governance object of a first account of the initiating user, the first privacy governance object including a first set of initiator privacy settings and a first set of recipient settings.
  • a method according to any one of examples 269 to 282, wherein the first user is an initiating user of the first interaction object and the generating a first interaction object between the first user and the second user occurs when a second user profile of the initiating user account is set as an active profile for the initiating user, the second user profile including a second set of profile object settings wherein at least one value of the second set of profile object settings is different from the corresponding value of the select set of profile object settings.
  • a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a method according to example 292, wherein the option to associate includes the first profile and all other profiles of the first user account.
  • a method according to example 292, wherein the option to associate includes the first profile and a subset of all other profiles of the first user account.
  • a method according to any one of examples 269 to 300 further comprising allowing the first user to associate the second user with the first interaction object and/or a second interaction object when a user profile of the first profile set other than the select profile is set to active in one or more user interfaces of the digital platform for the first user.
  • a method according to any one of examples 269 to 303, wherein the platform includes a second user account associated with the second user, the method further comprising: associating a first plurality of privacy governance objects with the first user account, each of the first plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings; associating a second plurality of privacy governance objects with the second user account, each of the second plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings; receiving from the first user an association of the first interaction object with a first privacy governance object of the first plurality of privacy governance objects; receiving from the second user an association of the first interaction object with a second privacy governance object of the second plurality of privacy governance objects, wherein the platform applies the set of initiator privacy settings corresponding to the first privacy governance object to the first interaction object for both the first user and second user; and presenting the first interaction object to the first user based on the set of recipient settings corresponding to the first privacy governance object and to the second user based
  • the set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • a set of discoverability settings includes a setting selected from the group consisting of a setting indicating which profile discoverability identifier for a profile can be actively utilized to discover the user profile, a setting indicating a degree of separation from a user and/or contact required to be able to discover a profile, and any combinations thereof.
  • the first profile discoverability identifier is an identifier selected from the group consisting of a standard email address, a universal resource locator (URL), a phone number, a government issued identifier, and any combinations thereof.
  • a method of interaction on a digital platform comprising: receiving from a first user of the platform a first third party standard unique identifier via a first user interface of the platform, the first third party standard unique identifier used by the platform to associate the first user with a first user account, the first user account configured to have a first plurality of user profiles; receiving from the first user at least one profile discoverability identifier for each of the first plurality of user profiles, each of the first plurality of user profiles having a set of discoverability settings and a set of profile object settings; receiving from a second user via a second user interface of the platform a search request including a first identifier of the at least one profile discoverability identifier; allowing the second user to interact with the first user via a first profile of the first user, the first profile including the first identifier as a corresponding at least one profile discoverability identifier, the discoverability of the first profile by the second user being governed in the platform by a first set of discoverability settings corresponding to the first profile; and
  • the group message room includes group member users that are the first user, the second user, and at least one additional user, wherein the group message room includes a message thread having one or more group message segments.
  • a method further comprising: receiving from a side chat initiating user a first request to initiate a side chat with a side chat recipient user, the side chat initiating user and the side chat recipient user each being group member user; and displaying one or more side message segments of the side chat within the group message room along with the one or more group message segments when displaying the group message room to the side chat initiating user and the side chat recipient user while omitting the display of the one or more side message segments from the display of the group message room to any of group member users that are not a member of the side chat, wherein the display of the one or more side message segments includes a side chat distinctive visual display feature.
  • I l l allowing a side chat initiating user of the group member users and a subset of other users of the group member users to participate in a side chat within the group message room, any of the group member users not a part of the subset of other users being non-participating users; and displaying one or more side message segments of the side chat within the group message room, the one or more side message segments being created by the side chat initiating user and/or one or more of the subset of other users, wherein the one or more side message segments are only displayed in the group message room to the side chat initiating user and the subset of users and the one or more side message segments are not displayed in the group message room to any non-participating users.
  • a method according to any one of examples 311 to 319, wherein the first interaction object includes a message thread and one or more message segments of the message thread is governed by a distribution restriction, the first interaction object being initiated by an initiating user of the first user and second user, the other user of the interaction object that is not the initiating user being a recipient user, the method further comprising: receiving from a first recipient user a fourth request via a request user interface to remove the distribution restriction from the one or more message segments; presenting a removal user interface to the initiating user, the removal user interface including information based on the fourth request and requesting the initiating user to remove the distribution restriction from the one or more message segments; receiving a distribution instruction from the initiating user via an instructions user interface, the distribution instruction including a direction to the digital platform to deny the fourth request or to remove all or a portion of the distribution restriction; and taking a removal related action based on the distribution instruction.
  • the first interaction object includes participant users that are the first user, the second user, and optionally at least one additional user of the platform, the first interaction object being initiated by an initiating user of the participant users, the first interaction object being associated with a first privacy governance object of a first account of the initiating user, the first privacy governance object including a first set of initiator privacy settings and a first set of recipient settings.
  • a method according to any one of examples 311 to 324, wherein the first user is an initiating user of the first interaction object and the generating a first interaction object between the first user and the second user occurs when a second user profile of the initiating user account is set as an active profile for the initiating user, the second user profile including a second set of profile object settings wherein at least one value of the second set of profile object settings is different from the corresponding value of the first set of profile object settings.
  • a method according to example 325 further comprising: associating a second contact user with the second user profile; presenting to the initiating user a fifth user interface wherein the first user profile is set as the active profile; and generating a second interaction object between the initiating user and the second contact user while the first user profile is the active profile wherein the second interaction object is presented to the second contact user governed by the second set of profile object settings.
  • a method according to example 325 further comprising: associating a second contact user with the second user profile; adding the second contact user to the first interaction object wherein the first interaction object is presented to the second contact user governed by the second set of profile object settings.
  • the first set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • the second set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • a method according to any one of examples 325 to 327, wherein the first profile is set as the active profile by a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a method according to any one of examples 311 to 327, wherein said allowing the second user to intereact with the first user includes allowing based on the first set of discoverability settings.
  • a method according to example 333 further comprising presenting information about the first user to the second user in any interaction object generated after the change of association of the second user to the second profile based on the second set of profile object settings.
  • a method according to any one of examples 311 to 337, wherein the platform includes a second user account associated with the second user, the method further comprising: associating a first plurality of privacy governance objects with the first user account, each of the first plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings; associating a second plurality of privacy governance objects with the second user account, each of the second plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings; receiving from the first user an association of the first interaction object with a first privacy governance object of the first plurality of privacy governance objects; receiving from the second user an association of the first interaction object with a second privacy governance object of the second plurality of privacy governance objects, wherein the platform applies the set of initiator privacy settings corresponding to the first privacy governance object to the first interaction object for both the first user and second user; and presenting the first interaction object to the first user based on the set of recipient settings corresponding to the first privacy governance object and to the second user based
  • the first set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • the set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • a set of discoverability settings includes a setting selected from the group consisting of a setting indicating which profile discoverability identifier for a profile can be actively utilized to discover the user profile, a setting indicating a degree of separation from a user and/or contact required to be able to discover a profile, and any combinations thereof.
  • the first profile discoverability identifier is an identifier selected from the group consisting of a standard email address, a universal resource locator (URL), a phone number, a government issued identifier, and any combinations thereof.
  • a method of interaction on a digital platform including a user account for each user, each user account configured to have a plurality of user profiles, the method comprising: associating a first contact user with a first user profile associated with an initiating user account of an initiating user of the platform, the first user profile including a first set of profile object settings, wherein when the first contact user interacts with the initiating user via the platform the platform presents the initiating user to the first contact user based on the first set of profile object settings; presenting to the initiating user a fourth user interface wherein a second user profile of the initiating user account is set as an active profile for the initiating user, the second user profile including a second set of profile object settings wherein at least one value of the second set is different from the corresponding value of the first set; and generating a first interaction object between the initiating user and the first contact user while the second user profile is the active profile wherein the first interaction object is presented to the first contact user governed by the first set of profile object settings.
  • the group message room includes group member users that are a first user, a second user, and at least one additional user, the first user being the initiating user and the second user being the first contact user, wherein the group message room includes a message thread having one or more group message segments.
  • a method according to example 347 further comprising: receiving from a side chat initiating user a first request to initiate a side chat with a side chat recipient user, the side chat initiating user and the side chat recipient user each being group member user; and displaying one or more side message segments of the side chat within the group message room along with the one or more group message segments when displaying the group message room to the side chat initiating user and the side chat recipient user while omitting the display of the one or more side message segments from the display of the group message room to any of group member users that are not a member of the side chat, wherein the display of the one or more side message segments includes a side chat distinctive visual display feature.
  • a method according to example 347 further comprising: allowing a side chat initiating user of the group member users and a subset of other users of the group member users to participate in a side chat within the group message room, any of the group member users not a part of the subset of other users being non-participating users; and displaying one or more side message segments of the side chat within the group message room, the one or more side message segments being created by the side chat initiating user and/or one or more of the subset of other users, wherein the one or more side message segments are only displayed in the group message room to the side chat initiating user and the subset of users and the one or more side message segments are not displayed in the group message room to any non-participating users.
  • a method according to any one of examples 345 to 351, wherein the first interaction object includes a message thread, the method further comprising: receiving a first content portion of a second message segment of the first message thread from a user device of a third user of the first interaction object, the third user being one of the initiating user and the first contact user, the receiving a first content portion being without header information of the second message segment that identifies the initiating user or the first contact user; translating the first content portion from a first human language to a second human language; transmitting the translated first content portion to the user device of the third user; and presenting the translated first content portion to the third user.
  • a method according to any one of examples 345 to 353, wherein the first interaction object includes a message thread and one or more message segments of the message thread is governed by a distribution restriction, the first interaction object being initiated by the initiating user, the first contact user being a recipient user, the method further comprising: receiving from a first recipient user a fourth request via a request user interface to remove the distribution restriction from the one or more message segments; presenting a removal user interface to the initiating user, the removal user interface including information based on the fourth request and requesting the initiating user to remove the distribution restriction from the one or more message segments; receiving a distribution instruction from the initiating user via an instructions user interface, the distribution instruction including a direction to the digital platform to deny the fourth request or to remove all or a portion of the distribution restriction; and taking a removal related action based on the distribution instruction.
  • the first interaction object includes participant users that are a first user, a second user, and optionally at least one additional user of the platform, the first user being the initiating user and the second user being the first contact user, the first interaction object being initiated by the initiating user, the first interaction object being associated with a first privacy governance object of a first account of the initiating user, the first privacy governance object including a first set of initiator privacy settings and a first set of recipient settings.
  • a method further comprising: associating a second contact user with the second user profile; presenting to the initiating user a fifth user interface wherein the first user profile is set as the active profile; and generating a second interaction object between the initiating user and the second contact user while the first user profile is the active profile wherein the second interaction object is presented to the second contact user governed by the second set of profile object settings.
  • a method according to any one of examples 345 to 358, further comprising: associating a second contact user with the second user profile; adding the second contact user to the first interaction object wherein the first interaction object is presented to the second contact user governed by the second set of profile object settings.
  • a method wherein the platform includes a first contact user account associated with the first contact user and a second user account associated with the second contact user, the method further comprising: associating a first plurality of privacy governance objects with the initiating user account, each of the first plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings; associating a second plurality of privacy governance objects with the first contact user account, each of the second plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings; associating a third plurality of privacy governance objects with the second contact user account, each of the third plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings; receiving from the initiating user an association of the first interaction object with a first privacy governance object of the first plurality of privacy governance objects; associating the first interaction object with a second privacy governance object of the second plurality of privacy governance objects and with a third privacy governance object of the third plurality of privacy governance objects, where
  • a method according to any one of examples 345 to 359, wherein the platform includes a first contact user account associated with the first contact user, further comprising: associating a first plurality of privacy governance objects with the initiating user account, each of the first plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings; associating a second plurality of privacy governance objects with the first contact user account, each of the second plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings; receiving from the initiating user an association of the first interaction object with a first privacy governance object of the first plurality of privacy governance objects; associating the first interaction object with a second privacy governance object of the second plurality of privacy governance objects, wherein the platform applies the set of initiator privacy settings corresponding to the first privacy governance object to the first interaction object for both the initiating user and first contact user; and presenting the first interaction object to the initiating user based on the set of recipient settings corresponding to the first privacy governance object and to the first contact user
  • a method according to any one of examples 345 to 364, wherein the first profile is set as the active profile by a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a method of interaction on a digital platform including a user account for each user, each user account configured to have a plurality of user profiles, the method comprising: generating a first interaction object between a first user of the platform that is an initiating user and a second user of the platform, the platform including: an initiating user account for the initiating user, the initiating user account including a first plurality of privacy governance objects, each of the first plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings, each of the set of initiator privacy settings and set of recipient settings of at least one of the first plurality of privacy governance objects at least partially set by the initiating user; and a second user account for the second user, the second user account including a second plurality of privacy governance objects, each of the second plurality of privacy governance objects including a set of initiator privacy settings and a set of recipient settings, each of the set of initiator privacy settings and set of recipient settings of at least one of the second plurality of privacy governance objects at least partially set by the initiating user; and
  • the group message room includes group member users that are the first user, the second user, and at least one additional user, wherein the group message room includes a message thread having one or more group message segments.
  • a method according to example 368 further comprising: receiving from a side chat initiating user a first request to initiate a side chat with a side chat recipient user, the side chat initiating user and the side chat recipient user each being group member user; and displaying one or more side message segments of the side chat within the group message room along with the one or more group message segments when displaying the group message room to the side chat initiating user and the side chat recipient user while omitting the display of the one or more side message segments from the display of the group message room to any of group member users that are not a member of the side chat, wherein the display of the one or more side message segments includes a side chat distinctive visual display feature. 370.
  • a method according to example 368 further comprising: allowing a side chat initiating user of the group member users and a subset of other users of the group member users to participate in a side chat within the group message room, any of the group member users not a part of the subset of other users being non-participating users; and displaying one or more side message segments of the side chat within the group message room, the one or more side message segments being created by the side chat initiating user and/or one or more of the subset of other users, wherein the one or more side message segments are only displayed in the group message room to the side chat initiating user and the subset of users and the one or more side message segments are not displayed in the group message room to any non-participating users.
  • a method according to any one of examples 366 to 372, wherein the first interaction object includes a message thread, the method further comprising: receiving a first content portion of a second message segment of the first message thread from a user device of a third user of the first interaction object, the third user being one of the first user and the second user, the receiving a first content portion being without header information of the second message segment that identifies the first user or the second user; translating the first content portion from a first human language to a second human language; transmitting the translated first content portion to the user device of the third user; and presenting the translated first content portion to the third user.
  • a method according to any one of examples 366 to 374, wherein the first interaction object includes a message thread and one or more message segments of the message thread is governed by a distribution restriction, the first interaction object being initiated by the initiating user, the second user being a recipient user, the method further comprising: receiving from a first recipient user a fourth request via a request user interface to remove the distribution restriction from the one or more message segments; presenting a removal user interface to the initiating user, the removal user interface including information based on the fourth request and requesting the initiating user to remove the distribution restriction from the one or more message segments; receiving a distribution instruction from the initiating user via an instructions user interface, the distribution instruction including a direction to the digital platform to deny the fourth request or to remove all or a portion of the distribution restriction; and taking a removal related action based on the distribution instruction.
  • a method according to any one of examples 366 to 376, wherein the second user is associated with a first profile of the initiating user account, the first profile having a first set of profile object settings such that the first set of profile object settings apply to the presentation of information about the first user to the second user with respect to the first interaction object, the generating a first interaction object between the first user and the second user occurs when a second user profile of the initiating user account is set as an active profile for the initiating user, the second user profile including a second set of profile object settings wherein at least one value of the second set of profile object settings is different from the corresponding value of the first set of profile object settings.
  • a method according to example 377 further comprising: associating a second contact user with the second user profile; presenting to the initiating user a fifth user interface wherein the first user profile is set as the active profile; and generating a second interaction object between the initiating user and the second contact user while the first user profile is the active profile wherein the second interaction object is presented to the second contact user governed by the second set of profile object settings.
  • a method according to example 377 further comprising: associating a second contact user with the second user profile; adding the second contact user to the first interaction object wherein the first interaction object is presented to the second contact user governed by the second set of profile object settings.
  • the first set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • the second set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • a method according to any one of examples 377 to 379, wherein the first profile is set as the active profile by a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • the additional sets of initiator privacy settings do not apply to the interaction object.
  • a method according to example 387 further comprising presenting the group message room to the second user and any other recipient user based on the corresponding additional set of recipient settings for the corresponding and other recipient user.
  • a method according to example 389 further comprising presenting the group message room to the initiating user based on the first set of recipient settings.
  • a method according to examples 389 or 390 further comprising presenting the group message room to the second user based on the second set of recipient settings.
  • a method according to any one of examples 366 to 393, further comprising: receiving a second request from the initiating user to change the association of the interaction object from being associated with the first privacy governance object to a third privacy governance object of the first account, the third privacy governance object including a third set of initiator privacy settings and a third set of recipient settings; and applying the third set of initiator privacy settings to the interaction object regardless of which of the first user and second user are interacting with the interaction object.
  • a method according to example 395, wherein the applying the third set of initiator privacy settings includes: applying the third set of initiator privacy settings to any new message segments of the one or more group message segments created in the group message room after the receiving the second request; and maintaining the application of the first set of initiator privacy settings to any message segments of the one or more group message segments to which the first set of initiator privacy settings previously applied.
  • a set of initiator privacy settings is a set of settings governing the privacy and security behavior and environment of the interaction object.
  • a set of recipient settings is a set of settings governing a display and general behavior of the interaction object as the interaction object is presented to a user.
  • a method according to any one of examples 366 to 401, wherein the first set of initiator privacy settings and/or the second set of initiator privacy settings includes a setting selected from the group consisting of an interaction object expiration, a forwarding setting, a side chat setting, an encryption setting, a screen capture setting, a forwarding request setting, a calendar event sharing limitation, a storage limitation, a retention setting, and any combinations thereof.
  • a method according to any one of examples 366 to 402, wherein the first set of recipient settings and/or second set of recipient settings includes a setting selected from the group consisting of a translation setting, a notification setting, a group notification setting, a display setting, a language setting, and any combinations thereof.
  • a method according to any one of examples 366 to 404, wherein the first interaction object includes a first object segment and a second object segment, the method further comprising: receiving from the initiating user a change in association for the first interaction object from the first privacy governance object to a fourth privacy governance object of the first plurality of privacy governance objects, said receiving occurring between the generation of the first object segment and the second object segment; applying the set of initiator privacy settings corresponding to the fourth privacy governance object to the second object segment for the initiating user and the second user while maintaining the application of the set of initiator privacy settings corresponding to the first privacy governance object for the first object segment.
  • a method of interaction on a digital platform comprising: receiving a first interaction object from a first user of the platform; transmitting the first interaction object to a user device of a second user of the platform; based on a translation setting of the second user: receiving from the user device at a server of the platform a content portion of the first interaction object without header information identifying the first or second user; and translating the content portion from a first human language to a second human language; transmitting the translated content portion to the user device; presenting the translated content portion to the second user.
  • the group message room includes group member users that are the first user, the second user, and at least one additional user, wherein the group message room includes a message thread having one or more group message segments.
  • a method further comprising: receiving from a side chat initiating user a first request to initiate a side chat with a side chat recipient user, the side chat initiating user and the side chat recipient user each being group member user; and displaying one or more side message segments of the side chat within the group message room along with the one or more group message segments when displaying the group message room to the side chat initiating user and the side chat recipient user while omitting the display of the one or more side message segments from the display of the group message room to any of group member users that are not a member of the side chat, wherein the display of the one or more side message segments includes a side chat distinctive visual display feature.
  • a method according to any one of examples 406 to 412, wherein the first interaction object includes a message thread and one or more message segments of the message thread is governed by a distribution restriction, the first interaction object being initiated by an initiating user of the first user and second user, the other user of the interaction object that is not the initiating user being a recipient user, the method further comprising: receiving from a first recipient user a fourth request via a request user interface to remove the distribution restriction from the one or more message segments; presenting a removal user interface to the initiating user, the removal user interface including information based on the fourth request and requesting the initiating user to remove the distribution restriction from the one or more message segments; receiving a distribution instruction from the initiating user via an instructions user interface, the distribution instruction including a direction to the digital platform to deny the fourth request or to remove all or a portion of the distribution restriction; and taking a removal related action based on the distribution instruction.
  • a method according to any one of examples 406 to 414, wherein the first interaction object includes participant users that are the first user, the second user, and optionally at least one additional user of the platform, the first interaction object being initiated by an initiating user of the participant users, the first interaction object being associated with a first privacy governance object of a first account of the initiating user, the first privacy governance object including a first set of initiator privacy settings and a first set of recipient settings.
  • a method according to any one of examples 406 to 417, wherein the first user is an initiating user of the first interaction object and the generating a first interaction object between the first user and the second user occurs when a second user profile of the initiating user account is set as an active profile for the initiating user, the second user profile including a second set of profile object settings wherein at least one value of the second set of profile object settings is different from the corresponding value of the first set of profile object settings.
  • a method according to example 418 further comprising: associating a second contact user with the second user profile; presenting to the initiating user a fifth user interface wherein the first user profile is set as the active profile; and generating a second interaction object between the initiating user and the second contact user while the first user profile is the active profile wherein the second interaction object is presented to the second contact user governed by the second set of profile object settings.
  • a method according to example 418 further comprising: associating a second contact user with the second user profile; adding the second contact user to the first interaction object wherein the first interaction object is presented to the second contact user governed by the second set of profile object settings.
  • the first set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • the second set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • a method according to any one of examples 418 to 420, wherein the first profile is set as the active profile by a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a method according to example 425 further comprising adding the one or more pieces of identifying information back to the translated first content portion prior to presenting the translated first content portion to the first user.
  • a method according to examples 424 further comprising adding the one or more pieces of identifying information back to the translated first content portion prior to presenting the translated first content portion to the first user.
  • the privacy governance object of the user account of the first user is an associated privacy governance object that is associated within the user account of the first user with the group message room.
  • the translation setting includes a setting selected from the group consisting of , an on/off setting for a translation functionality, an automatic translation setting (e.g., on/off, language of translation), a request for translation setting, a language of translation setting, an interface language setting, a spoken language setting, and any combinations thereof.
  • the translation setting includes an automatic translation setting that is set to on and the receiving a first content portion occurs based on the user device of the first user having automatically transmitted the first content portion based on the automatic translation setting.
  • the translation setting includes a setting that requires the first user to provide a translation instruction via the user device of the first user for the second message segment to be translated and the receiving the first content portion occurs based on the user device of the first user having transmitted the first content portion based on the translation instruction.
  • a method according to any one of examples 431 to 441, wherein the translation setting includes a setting indicating which incoming message segment language is to be translated and the language of the first content portion matches the set incoming message segment language.
  • a method of interaction on a digital platform comprising: presenting one or more message segments of a message thread to a second user that is a recipient user, the message thread and/or a select message segment of the one or more message segments being governed by a distribution restriction set by a first user that is an initiating user, the distribution restriction limiting the forwarding of the message thread and/or select message segment; receiving via a fourth request user interface a request to remove the distribution restriction from the recipient user; presenting the fourth request to remove to the initiating user; presenting a removal user interface to the initiating user, the removal user interface including information based on the fourth request and requesting the initiating user to remove the distribution restriction from the one or more message segments; receiving a distribution instruction from the initiating user via an instructions user interface, the distribution instruction including a direction to the digital platform to deny the fourth request or to remove all or a portion of the distribution restriction; and taking a removal related action based on the distribution instruction.
  • a method further comprising: receiving from a side chat initiating user a first request to initiate a side chat with a side chat recipient user, the side chat initiating user and the side chat recipient user each being group member user; and displaying one or more side message segments of the side chat within the group message room along with the one or more group message segments when displaying the group message room to the side chat initiating user and the side chat recipient user while omitting the display of the one or more side message segments from the display of the group message room to any of group member users that are not a member of the side chat, wherein the display of the one or more side message segments includes a side chat distinctive visual display feature.
  • a method according to example 450 further comprising: allowing a side chat initiating user of the group member users and a subset of other users of the group member users to participate in a side chat within the group message room, any of the group member users not a part of the subset of other users being non-participating users; and displaying one or more side message segments of the side chat within the group message room, the one or more side message segments being created by the side chat initiating user and/or one or more of the subset of other users, wherein the one or more side message segments are only displayed in the group message room to the side chat initiating user and the subset of users and the one or more side message segments are not displayed in the group message room to any non-participating users.
  • a method according to any one of examples 448 to 454, further comprising: receiving a first content portion of a second message segment of the first message thread from a user device of a third user of the first interaction object, the third user being one of the first user and the second user, the receiving a first content portion being without header information of the second message segment that identifies the first user or the second user; translating the first content portion from a first human language to a second human language; transmitting the translated first content portion to the user device of the third user; and presenting the translated first content portion to the third user.
  • a method according to any one of examples 448 to 456, wherein the message thread is part of a first interaction object that includes participant users that are the first user, the second user, and optionally at least one additional user of the platform, the first interaction object being initiated by an initiating user of the participant users, the first interaction object being associated with a first privacy governance object of a first account of the initiating user, the first privacy governance object including a first set of initiator privacy settings and a first set of recipient settings.
  • a method according to any one of examples 448 to 459, wherein the one or more message segments are part of a first interaction object, the second user being associated with a first profile of the first user’s account, the first profile including a first set of profile object settings such that the first set of profile object settings apply to the presentation of information about the first user to the second user in interactions on the platform, and the first interaction object is initiated when a second user profile of the initiating user account is set as an active profile for the initiating user, the second user profile including a second set of profile object settings wherein at least one value of the second set of profile object settings is different from the corresponding value of the first set of profile object settings.
  • a method according to example 460 further comprising: associating a second contact user with the second user profile; presenting to the initiating user a fifth user interface wherein the first user profile is set as the active profile; and generating a second interaction object between the initiating user and the second contact user while the first user profile is the active profile wherein the second interaction object is presented to the second contact user governed by the second set of profile object settings.
  • a method according to example 460 further comprising: associating a second contact user with the second user profile; adding the second contact user to the first interaction object wherein the first interaction object is presented to the second contact user governed by the second set of profile object settings.
  • a method according to any one of examples 460 to 462, wherein the first profile is set as the active profile by a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a functionality that includes a functionality selected from the group consisting of, an active profile selector user interface that is selected by a user, by a default setting, selection of a particular contact that is associated with a profile, addition of a particular contact to an interaction object wherein the contact is associated with a profile, by user selection of a contact list including one or more contacts associated with a profile, by another mechanism that sets an active profile, and any combinations thereof.
  • a method according to example 468, wherein the removal related action includes: presenting information about the removal of all or a portion of the distribution restriction to the first recipient user via one or more user interfaces; and allowing the first recipient user to forward the one or more message segments based on the distribution instruction from the initiating user.
  • a method according to example 472, wherein the limit on the number of times the one or more message segments can be forwarded is a number of times that is more than one time.
  • Each of the method examples 1 to 482 can also be implemented as a machine-readable storage medium including machine/processor executable instructions for performing the method example (e.g., with method steps replaced by a set of instructions for performing the method step).
  • machine-readable storage medium examples are not repeated, but are contemplated as if expressly stated.
  • a method or machine-readable storage medium having a set of initiator privacy settings, wherein a set of initiator privacy settings include a setting selected from the group consisting of an interaction object expiration, a forwarding setting, a side chat setting, an encryption setting, a screen capture setting, a forwarding request setting, and any combinations thereof.
  • a method or machine-readable storage medium having a set of recipient settings, wherein a set of recipient settings include a setting selected from the group consisting of a translation setting, a notification setting, a group notification setting, a display setting, a language setting, and any combinations thereof.
  • a method or machine-readable storage medium having a translation setting, wherein a translation setting includes a setting selected from the group consisting of an on/off setting, an automatic translation setting, a request for translation setting, a language of translation setting, and any combinations thereof.
  • a method or machine-readable storage medium having a notification setting, wherein a notification setting includes a setting selected from the group consisting of a new interaction object available setting, a new message segment available indicator, a changed setting indicator, and any combinations thereof.
  • a method or machine-readable storage medium having a group notification setting, wherein a group notification setting includes a setting selected from the group consisting of a new interaction object available setting, a new message segment available setting, a group member change setting, a group expiration setting, a changed setting indicator, and any combinations thereof.
  • a method or machine-readable storage medium having a third party standard unique identifier, wherein the third party standard unique identifier includes an identifier selected from the group consisting of a standard email address, a universal resource locator (URL), a phone number (e.g., a mobile phone number), a government issued identifier (e.g., social security number, driver’s license number), and any combinations thereof.
  • the third party standard unique identifier includes an identifier selected from the group consisting of a standard email address, a universal resource locator (URL), a phone number (e.g., a mobile phone number), a government issued identifier (e.g., social security number, driver’s license number), and any combinations thereof.
  • a method or machine-readable storage medium having a set of discoverability settings, wherein each set of discoverability settings includes a setting selected from the group consisting of a setting indicating which profile discoverability identifier for a profile can be actively utilized to discover the user profile, a setting indicating a degree of separation from a user and/or contact required to be able to discover a profile, and any combinations thereof.
  • a method or machine-readable storage medium having a set of profile object settings, wherein each set of profile object settings includes a setting selected from the group consisting of a profile username, a notification setting, a group notification setting, a profile image, a visibility setting, a display setting, a mood setting, and any combinations thereof.
  • a method or machine-readable storage medium having a profile privacy setting, wherein a profile privacy setting includes a setting selected from the group consisting of a visibility setting, a last logged into the platform setting, a read confirmation setting, a typing indicator setting, a language setting, and any combinations thereof.
  • a method or machine-readable storage medium having a language setting, wherein a language setting includes a setting selected from the group consisting of a platform interface language, a spoken language for a user, a translation language for a user, and any combinations thereof.
  • a method or machine-readable storage medium having a display setting, wherein a display setting includes a setting selected from the group consisting of a background color, a text color, a font, and any combinations thereof.
  • a method or machine-readable storage medium having a mood setting, wherein a mood setting includes a setting selected from the group consisting of a shared mood statement setting, a shared mood graphic setting, and any combinations thereof.
  • shared mood graphic setting includes a setting selected from the group consisting of a still image setting, a video image setting, an audio/video setting, a graphic setting, and any combinations thereof.
  • a method or machine-readable storage medium having a mood setting, wherein the mood setting allows a user of the platform to select a mood object for display to a recipient of an interaction object.
  • a method or machine-readable storage medium having a mood object, wherein the mood object includes an object selected from the group consisting of an image, a video object, an audio object, a graphical object, an animation object, a moving image GIF object, and any combinations thereof. 499.
  • an interface of a corresponding digital platform includes an active status selector configured to allow a user to select an active profile for the first user account.
  • the platform when the active profile is the first profile, the platform includes a message list user interface configured to display to the first user the first message list and when the active profile is the second profile, the platform includes a message list user interface configured to display to the first user the second message list.
  • functionality described with respect to a single component/element is contemplated to be performable by a plurality of like components/elements (e.g., in a more dispersed fashion locally and/or remotely). Functionality described with respect to multiple components/elements may be performed by fewer like or different components/elements (e.g., in a more integrated fashion).
  • discoverability of a user of a digital platform e.g., those discussed with respect to FIGS. 11, 12, 13, 14, 15
  • interactions with contacts e.g., those discussed with respect to FIGS. 16, 17, 18, 19, 20
  • a side-chat functionality e.g., those discussed with respect to FIGS.
  • a forward request functionality e.g., those discussed with respect to FIG. 24
  • a CPOL Platform e.g., those discussed with respect to FIGS. 2, 3, 4, 10, 5, 6, 7, 8, 9
  • discoverability of a user of a digital platform e.g., those discussed with respect to FIGS. 11, 12, 13, 14, 15
  • interactions with contacts e.g., those discussed with respect to FIGS. 16, 17, 18, 19, 20.
  • a digital platform may be configured such that contact users that are associated with a profile may only be used for an interaction object that is also associated with the corresponding profile.
  • a digital platform can be alternatively configured such that an interaction object having a contact associated with one profile of a user account may only be associated with a PGO originating from the same profile.
  • Any setting of a user account, a user profile (e.g., a profile discoverability setting, a profile object setting), or a PGO (e.g., an initiator privacy setting, a PGO recipient setting) may include a default value (e.g., that is set by the corresponding digital platform initially). In such a case, a user may be allowed to change a default value of a setting. Additionally, a profile and/or a PGO may be configured within a digital platform to be a default profile or default PGO, respectively.
  • a user account may include (or be allowed to add) a default profile with certain settings of the profile pre-set to a value (e.g., with a user only needing to input values for setting that are unique to the user, such as profile discoverability identifier(s), with the option of changing/inputting values for other settings).
  • a digital platform may include a default profile geared towards a business use/personality/persona and/or a default profile geared towards a personal use/personality/persona.
  • a user account may include (or be allowed to add) a default PGO with certain settings of the PGO pre-set to a value with the option of changing/inputting values for settings).
  • a digital platform may include a default PGO geared towards tighter (i.e., more protective) privacy and security for use where such security and privacy are needed and/or a default PGO geared towards looser (i.e., less protective privacy and security for use where it is not as important interactions between users, such as where limitations on forwarding, lifespan, storage, etc. for an interaction object may not be needed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Databases & Information Systems (AREA)
  • Computing Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne des procédés, des systèmes et des supports lisibles par machine se rapportant à une plateforme de style de vie en ligne de confidentialité contextuelle comprenant des fonctionnalités qui comprennent une découvrabilité de profil, des objets de gouvernance de confidentialité, une flexibilité de profil, des restrictions de distribution sur des objets d'interaction et des segments de message associés conjointement avec leur retrait, une traduction sécurisée, des fonctionnalités de dialogue en ligne latérales, et toute combinaison de ceux-ci.
PCT/US2024/032202 2023-06-02 2024-06-03 Plateforme de style de vie en ligne de confidentialité contextuelle, systèmes et procédés associés Pending WO2024249978A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202363506056P 2023-06-02 2023-06-02
US63/506,056 2023-06-02
US202363582847P 2023-09-14 2023-09-14
US63/582,847 2023-09-14

Publications (2)

Publication Number Publication Date
WO2024249978A2 true WO2024249978A2 (fr) 2024-12-05
WO2024249978A3 WO2024249978A3 (fr) 2025-04-03

Family

ID=93658452

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/032202 Pending WO2024249978A2 (fr) 2023-06-02 2024-06-03 Plateforme de style de vie en ligne de confidentialité contextuelle, systèmes et procédés associés

Country Status (1)

Country Link
WO (1) WO2024249978A2 (fr)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130018960A1 (en) * 2011-07-14 2013-01-17 Surfari Inc. Group Interaction around Common Online Content
CA3003084A1 (fr) * 2014-10-23 2016-04-28 Dele Atanda Systeme intelligent de gestion d'informations personnelles
US10778831B2 (en) * 2017-02-17 2020-09-15 Whatsapp Inc. Methods and systems for displaying an ephemeral content message
US10348658B2 (en) * 2017-06-15 2019-07-09 Google Llc Suggested items for use with embedded applications in chat conversations
WO2021030288A1 (fr) * 2019-08-09 2021-02-18 Ruon Limited Système de serveur de plateforme multimédia d'utilisateur
EP4341805A1 (fr) * 2021-05-19 2024-03-27 Snap Inc. Combinaison de fonctions en raccourcis dans un système de messagerie

Also Published As

Publication number Publication date
WO2024249978A3 (fr) 2025-04-03

Similar Documents

Publication Publication Date Title
US12001587B2 (en) Data compliance management in recording calls
US20220353099A1 (en) Virtual reality systems and methods with cross platform interface for providing support
JP6110983B2 (ja) 統合通信アプリケーション
US11310295B1 (en) Integrated workspace on a communication platform
US11209964B1 (en) System and method for reacting to messages
US10009313B2 (en) Methods, systems, and computer readable media for managing multiple personas within end user applications
KR101984994B1 (ko) 신규한 통신 및 메시징 시스템
TWI459765B (zh) 用於語音及傳訊之一致規則
US10354226B1 (en) Systems and methods for capturing, predicting and suggesting user preferences in a digital huddle environment
US20150074825A1 (en) System and method for controlling privacy settings of user interface with internet applications
US20140082071A1 (en) Sandboxing individual applications to specific user folders in a cloud-based service
US20160100019A1 (en) Contextual Presence Systems and Methods
US20090248824A1 (en) Theme-based instant messaging communications
US10743151B2 (en) Enhanced modes of communication
US12166738B2 (en) Contextual discovery and design of application workflow
US11816173B2 (en) Method and apparatus for managing user profile
US10462637B1 (en) Information exchanging system
WO2024249978A2 (fr) Plateforme de style de vie en ligne de confidentialité contextuelle, systèmes et procédés associés
US11044218B1 (en) Systems and methods for reacting to messages
JP7601567B2 (ja) チャットルームでコンテンツ作成者をピックすることのできる方法、システム、および非一時的なコンピュータ読み取り可能な記録媒体
JP7779621B2 (ja) プライベートチャネルからパブリックチャネルへの変換
JP7732211B2 (ja) 情報処理装置及びプログラム
JP7732212B2 (ja) 情報処理装置及びプログラム
WO2024087533A1 (fr) Procédé et appareil de partage d'image d'expression, dispositif informatique et support de stockage
CN120235120A (zh) 文档编辑方法、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24816644

Country of ref document: EP

Kind code of ref document: A2