Implementations of the current disclosure relate generally to real-time electronic communications, and more specifically, to creating and displaying subsidiary channel-based thread communications in a group-based messaging system.
Electronic chat communications (which include chat room communications, instant messaging and text messaging, etc.) are an increasingly popular way for two or more people to communicate on-line in virtual real time. For example, chat sessions for conveying a quick note are often used in the workplace in lieu of having a phone call with multiple individuals. In some situations, an ability to quickly communicate with more than one person using chat communications often saves time and avoids costly mistakes in collaborative efforts, such as team projects. When multiple people, however, are participating in a chat session that may be established for a large project, current electronic chat communications are limited due the sequential, read-only, chronological presentation of exchanges between individuals or groups of individuals associated with the electronic chat session.
The disclosure is illustrated by way of example, and not by way of limitation, and will become apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
Implementations of the disclosure provide techniques for integrating actionable objects into an on-line chat communications platform. This may be advantageous in improving chat messaging technology by providing user perceivable actionable objects in a chat session that are executed by a client device to enhance communications between participants of the session.
To communicate typically, various different mediums use a number of different applications resulting in a loss of context and continuity in the communications. For example, some users may not be able to keep track of whether a message that was sent to or received from another user using different modes of communication (e.g., chat/email, etc.). In such cases, there is no organization flow associated with the messages nor is it possible to determine a response came before or after another message sent or received. Furthermore in traditional chat technology, information is extremely perishable. For example, once a message is off the top of the screen, it is rarely seen again, thus making it even harder to maintain the context of the message stream.
In accordance with the present disclosure a system is provided that is intended to be used as a system of record for an organization, work group, social group, etc., using various combinations of communication techniques. In some aspects, the system addresses the problems in chat technology of disjointed, ad hoc electronic communications. For example, by allowing one-to-one private messaging within a group chat channel this disclosure addresses a common problem of reply-to-all clutter while retaining context and continuity (place, time, meaning), and the flow of the conversation for each unique user. Further, by integrating a system of identifying and grouping together past messages from within a channel and even allowing those messages to be combined with other past messages from other channels, this disclosure addresses the problem of discussion archival and retrieval and by further still integrating actionable objects such as “Tasks”, “Ideas”, “Events”, “Surveys”, etc., into the system. This allows messages (e.g., chat messages) to be “typed” making them organized, searchable, referenceable, context oriented and actionable thereby enhancing communications, saving time and increasing productivity of users. The elements of this disclosure provide additional advantages that are further enhanced when the elements are combined and integrated together making possible a comprehensive and dynamic system of record. In some implementations, the disclosure can be implemented in accordance with numerous aspects consistent with the techniques presented herein.
Although implementations of the disclosure may be particularly beneficial in certain types of communication platforms (e.g., chat room communications), other types of communication platforms can be utilized in conjunction with the disclosure. For example, some of these communication platforms may include platforms for text messages, short message services (SMS), e-mails and other types of similar on-line communication platforms for facilitating information exchanges between client devices of a plurality of participants.
In the following description, numerous details are set forth. It will be apparent, however, to one skilled in the art, that the disclosure may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the disclosure.
The disclosure is related to a system for performing the operations herein. This system may be specially constructed for the required purposes or it may comprise a general purpose computing device selectively activated or reconfigured by a computer program stored therein. Such a computer program may be stored in a non-transitory computer readable storage medium, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, flash memory devices including universal serial bus (USB) storage devices (e.g., USB key devices) or any type of media suitable for storing electronic instructions, each of which may be coupled to a computer system bus.
In some implementations, the computer program product, or software may include a non-transitory machine-readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic devices) to perform a process according to the disclosure. A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable (e.g., computer-readable) medium includes a machine (e.g., a computer) readable storage medium (e.g., read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices, etc.), a machine (e.g., computer) readable transmission medium (non-propagating electrical, optical, or acoustical signals), etc.
In one implementation, the computer program product may be installed and/or a service may be selected from a cloud-computing environment in order to obtain the benefits of the techniques described herein. In an implementation, the computer program product may be downloaded onto a client device. For example, a participant may elect to download the computer program product from a service associated with an online server. The client device may transmit a request for the computer program product over a network and, in response, receive the computer program product from the service. The computer program product may be installed locally on the client device or stored at the service and may be accessed through the client device, for example, via a mobile web browser.
As shown in
Server device 140 may be at one node of network 195 and capable of directly and indirectly communicating with other nodes of the network 195. For example, the server device 140 may include a web server that may be capable of communicating with client devices 110, 120 and 130 via network 195 such that it uses the network 195 to transmit and display information to a participant on a display associated with client devices. In some implementations, the server device 140 may also include a plurality of computers that exchange information with different nodes of a network for the purpose of receiving, processing and transmitting data to the client devices 110, 120 and 130.
Referring to
Instructions 116 of the client device 110 may be a set of instructions to be executed directly (such as machine code) or indirectly (such as scripts) by the processor 112. In that regard, the terms “instructions,” “steps” and “programs” may be used interchangeably herein. The instructions 116 may be stored in object code format for direct processing by the processors 112, or in another computer language including scripts or collections of independent source code modules that are interpreted on demand or compiled in advance.
Data 118 may be retrieved, stored or modified by processors 112 in accordance with the instructions 116. For instance, although the present disclosure is not limited by a particular data structure, the data 118 may be stored in computer registers, in a relational database as a table having a plurality of different fields and records, XMIL documents, or flat files. The data 118 may also be formatted in a computer-readable format such as, but not limited to, binary values, ASCII or Unicode. By further way of example only, the data 118 may comprise information sufficient to identify the relevant information, such as numbers, descriptive text, proprietary codes, pointers, references to data stored in memory or information that is used by a function to calculate the relevant data. For example, the data 118 may include actionable objects 115 that may identify user perceivable action that can be included in a chat session.
Each of the actionable objects 115 may comprise an adjustable data structure (e.g., a memory array) comprising a plurality of fields that characterize a type category to associate with a chat message. By incorporating the actionable objects 115 into the creation of the chat messages, the system 100 is able to ascribe a value “type” to each message. In one implementation, when one or more actionable objects 115 are added or inserted into a chat message of the chat session, the actionable object executes a series of steps to be performed by a corresponding user perceivable action. The series of steps can be preprogrammed or variable based on the context of the type category for that action.
In some implementations, each client device may include an application 117 to facilitate different types of electronic communications between each client device and one or more other client devices via network 195, including providing interactive interface portals 118 for facilitating various operating functions of the disclosure. In one implementation, the application 117 may be installed and/or a service may be selected in order to obtain the benefits of the techniques described herein. In an implementation, the application 117 may be downloaded onto the client device 110. For example, a participant may elect to download the application from a service associated with an online server. The client device 110 may transmit a request for the application 117 over network 195 and, in response, receive the application 117 from the service.
The application 117 may be installed locally on the client device 110. Alternatively, the application 117 can be stored at the service and may be accessed through the client device 110, for example, via a mobile web browser. By using the application 117, the client device 110 may integrate into a chat session user perceivable actionable objects, such as actionable objects 115, which can be executed by the client device 110 to enhance communications between participants of that session. In an alternative implementation, the application 117 may be a firmware embedded in communication device.
As shown in
To facilitate integrating actionable objects into a chat session, the instructions 116 of the client device 110 may include actionable object integration module 119. The actionable object integration module 119 may generate and transmit user perceivable actionable objects in a chat session that can be executed by the client devices of system 100. The functionality of the module 119 can exist in a fewer or greater number of modules than what is shown, with such modules residing at one or more computing devices, which may be geographically dispersed. The systems may be operable in conjunction with components of the client device 110 from which it may receive chat message related data and other relevant information regarding the device 110.
Each device may include, for example, user input devices such as a keyboard 214 and mouse 216 and/or various other types of input devices such as pen-inputs, joysticks, buttons, touch screens, etc., as well as a display, which could include, for instance, a CRT, LCD, plasma screen monitor, TV, projector, touch screen, etc. Each device may be a personal computer, application server, etc. By way of example only, computing device 110 may be a mobile phone while computing device 260 may be a server. Databases, such as database 270, may be accessible to one or more of the computing devices or other devices of system 200. The database 270 may comprise data, such as state information 275, associated a chat session implemented on the client devices as well as store chat messages transmitted via system 200.
In one implementation, a resource associated with the system 200 may be used to maintain a consistency of the state information 275 and in such cases when there is a system failure. This is so that the chat session can continue uninterrupted without losing chat participant details. For example, a state manager (not shown) may maintain and transfer the state information 275 to state backup storage (not shown) for later retrieval. State backup storage may be accessible by any of the computing devices of system 200 via network connection 218 so that the chat session between the participants may be rerouted while the state information 275 is maintained, if a computing device of system 200 fails.
In some implementations, the state information 275 may correspond to a chat session between participants associated with the client devices of system 200. In some implementations, the state information 275 may be stored in database 270 by the state manager running on the server device 260 and/or the client devices or some combination thereof. In one implementation, the state information 275 may include, for example, information regarding the identity of participants of the chat session, the number of chat participants, actionable objects 119 that are applied to the chat session, a unique identifier associated with each of the action objects 119 and/or the chat message or session, and an order in which chat messages are received as well as other relevant information. When an actionable object 119 is applied in a particular chat session, the state information 275 for that session may be updated in accordance with the user perceivable action associated with the actionable object 119. This updating of the state information 275 in accordance with the actionable object 119 applied therein is further discussed below with respect to various interactive interfaces of the disclosure.
Embodiments of the disclosure provide actionable functionality to the contents of chat messages to distill and extract central elements of a single, one-to-one or group chat conversation. A participant of the chat sessions may be provided with a variety of different interactive interfaces to facilitate the transfer of an electronic communications between participants in a chat session. In some implementations, the interfaces allow the participants to integrate actionable objects, such as actionable objects 119 into the chat session to enhance the electronic communications between the participants. The interfaces may be flexibly configured to include various types of buttons, cursors, and tools as well as formatted content on a display on a client device. In one implementation, an application, such as application 117 of
With regards to
Each message that is entered into the text entry region 327 is displayed in the message window panel 320. In some implementations, the messages 325 can be flagged or marked (for example, by color) to isolate the message for later use. An advantage of marking individual messages is that it provides participants with a way to indicate, highlight or associate messages, for current use or future recall for themselves or others.
In some implementations, the interface portal 300 provides context relevant searching to display messages that match an inputted search criterion while simultaneously affording the search originator necessary message context. In one example, the participant taps on a control associated to a particular message in the message window 320 to bring up a palette of color tags. One or more colors may be used to tag the message. The user can select, add, delete and name colors in user settings. In some implementations, the search criterion can be typed, tapped, moved, imported, loaded from a saved file, written, spoken (entered by any known means) through the interface portal 300. The search criterion can be a single or combination of and/or Boolean search term (word, #tag, name, color, texture), color tags that may be defined and/or reserved. In one implementation, the context relevant searching allows for the discovery of messages that come before and after the “found” instances (“context”) to enhance search results. For example, when a User selects a found message, the message is displayed (for example, in the side panel 330) with messages that came immediately before and immediately after that message.
In some implementations, from time to time a user may wish to initiate or continue a dialog/thread/conversation with another member and may want to quickly identify all of the “mutual” chats/conversations, that is, chats they have in common with the other person. Quickly ascertaining mutual chats can save time and frustration for chat participants. In accordance with the present disclosure, a user can ascertain mutual chats, which allows the user to switch between chat groups, dialogs, threads or conversations. For example, the user can activate a control on a particular message in the message window 320 that in turn displays a list of “mutual” dialogs/conversations (e.g., in the side panel 330.) User can then select any dialog from the list to immediately switch to that conversation to be displayed in the message window 320.
In some implementations, the interface portal includes a text crawl region 340 where messages sent to one or more intended recipients are displayed. The text crawl region 340 may contain text, graphics, sounds or recorded messages (or any combination thereof). The text crawl region 340 can be placed, sized and/or moved to call attention or notice to the participants of the messages. For example, the text crawl region 340 may be enlarged, shrunken, hidden, tagged, named, saved, deleted, forwarded, edited, or remain a static size, random size or variable. Text and/or graphics the text crawl region 340 of the can appear in any color or combination of colors.
Users may have the option of defining the types and conditions under which they will accept, view or have the text crawl region 340 visible to them. A text crawl may be accompanied by a sound or vibration. Associated sounds can be varied depending upon the context and/or content and/or originator of the crawl. Some crawl message can be generated as a result of a subscription, membership or affiliation (e.g., based on defined criteria and linked to a social media account, feed or the like). Text crawl messages may also be automatically generated based upon certain criteria being met such as, for example, a location or proximity to a person, place, thing or an event, date or time. The crawl can be spawned by other third party applications as a result of a search being performed, an inquiry made or a purchase being made. In some implementations, text crawl can be a reminder, an alert, a message, an advertisement, an award, a receipt, a ticket, or other indication. A hypertext or other link can be embedded in the text crawl region 340. By moving a mouse cursor on the text crawl region 340 or selecting a particular message in the region 340 more information relating to the text crawl may be revealed and acted upon.
In some implementations, the text crawl may include a listing of text that meets a search criterion. For example, when by interacting with the text crawl region 340 (e.g., with a mouse cursor), the search criterion may automatically include all messages/objects that are tagged as “Crawl” objects. In one implementation, the search may be further refined to include text crawl messages that are included in the dialog chat messages between participants. Initially, the text crawl region 340 may display messages from a particular work group (e.g., that is subscribed to, accepted or originated by a current user to public or social or unknown users). Users may turn on or turn off the text crawl region 340 and can further set parameters such as (but not limited to) the type of crawls the user is willing to accept to be displayed in the text crawl region 340
In some implementations, crawl “objects” are tagged and can be linked to a single dialog or more than one dialog in the chat message panel 320. The crawl objects can be sent to one or more recipients, such as registered and non-registered participant. Some participant may receive a notification of the crawl object through mechanisms other than the interface portal 300, for example, email, text message or other mechanism. A link may be provided in the notification directing the participant to activate the crawl object. If the email or chat software of the recipient is capable with the interface portal 300, the crawl message may be displayed from within the recipient's email or chat service.
In some implementations, the creator of the crawl message may have the option to name the crawl message. The color of the text may be selected and can vary from character to character. The crawl message creator may choose to animate the text (e.g., text flashing). When receiving a crawl notification for the first time, the recipient may be prompted to with several options, such as to “Accept Crawls from the Sender Once, Reject Crawls from the Sender Once, Always accept Crawls from the Sender or Never accept crawls from the Sender.” The settings for the text crawl region 340 of interface portal 300 regarding crawl notifications may be set and later modified by the recipient.
In some implementations, a control (e.g., a window tab) on the portal 400 may be activated to display a listing of actionable objects 440 that can be utilized. For example, as shown in
Each actionable object 440 is associated with one or more data structures that provide enhanced functionality to chat communications. In some implementations, a user may select an icon, such as one of icons 450, associated with an actionable object to insert into the chat session. An advantage of inserting the actionable object 440 into chat messages is that it provides the basis of order and structure to the chat session to provide an interactive presentment of messaging activity. In some implementations, the actionable object 440 can be selected using various mechanisms, such as such as keyboard shortcuts.
Responsive to the selection an actionable object to insert into a chat session, at least one participant of a plurality of participants may be associated with the actionable object. For example, a user may add one or more participants to a dialog box 460 of the interface portal 400. The association indicates that the actionable object is directed to the identified participants, which may be presented on the participant's client device when the actionable object is transmitted, for example, by using network 195. In one implementation, the interface portal 400 provides a text input section 470 that may be used to add additional information 470 regarding the user perceivable action to be executed in accordance with the selected actionable object.
When a participant, via the interface portal 400, creates and sends a communication including the actionable object to the client device of a receiving participant, the receiving participant receives the communication (e.g., in the form of an actionable object control) in the chat session in which the participants are currently engaged. The application, such as application 117 of the receiving client device acts to initiate or enable the actionable object at the receiving participant end by executing the user perceivable action associated with the object. In this regard, the sending participant by sending the actionable object is requesting to escalate the chat session to a more content enriched form of communication. A recipient participant can activate the actionable object control or activate a communication session at the recipient client device in accordance with the user perceivable action of the actionable objects 440.
In some implementations, the actionable objects 440 may be used in combination. For example, the interface portal 400 may receive a selection of additional actionable objects from the plurality of actionable objects and combine these additional actionable objects with the actionable object in the chat session. The combination may change the characteristics of the user perceivable action to be performed based on a relative order of the inserted actionable objects 440 and other actionable objects 440 appearing elsewhere in the message flow of the chat session.
In one example, the interface portal 400 may detect the presence of two or more task type actionable objects, separated by three question type actionable objects. In this example, the order and/or grouping of the actions performed by the client device with regards to the questions may be adjusted. For example, the interface portal 400 may detect that one question objection has been inserted, which causes the portal 400 to prompt the user for further information. In some implementations, the presentation, input, characterization, appearance, or non-appearance of the actionable objects can vary based on the combination (or absence of) various actionable objects in a specific chat messages and/or chat session.
A. Question Objects
Turning to
In some implementations, the plurality of control objects 411 allows the sending participant to select a combination of different polling questions to provide to the chat session. In one implementation, the particular questions may be displayed in a questions region, such as questions region 415 and 416, of the side panel 430 for further adjusts by the sending participants. Although only two question regions are shown in
In some implementations, these polling question actionable objects may include, but not limited to, 1) a multiple/single choice object, 2) a ranking object, 3) a slider object, and 4) a narrative response, etc. If the multiple/single choice object is selected, this object provides one or more customizable fields. This object also allows the sending participants to upload, via the interface portal 400, a media or other file which is associated with the specific choice, such as choice 1 2 or 3 in questions region 415, which can be presented with the polling question. If the ranking object is selected, this object inserts or references a polling question into the side panel 430 along with inputted configuration settings on how the chat session is to display, categorize, and associate this polling question with regards to other polling questions in the chat session.
If the slider object is selected, the object inserts or references a polling question into the side panel 430 along with pull-down menu options (as shown in questions region 416) to allow the individual to customize selectable feedback options. For example, the selectable feedback options may include a determined list of slider attributes to allow the sending participant to customize the slider left, center and right attributes (e.g., Strongly Agree, Neither Agree nor Disagree or Strongly agree) to correspond with responses from the receiving participant. It should be noted that this is merely a few examples as other polling questions and question settings can be customized by the sending participant. An advantage of providing a slider object that can be incorporated into the chat session is that the responses can be structured and also viewed numerically (e.g., with reference to a specific position along a slider) as opposed to receiving unstructured narrative responses from the receiving participants that may be difficult to interpret.
In some implementations, the question actionable object can be associated or assigned to one or more receiving participants. For example, information regarding the receiving participants may be inserted into recipient field 413. In one implementation, the sending participant may send the question actionable objects to receiving participants in the chat session by activating a control 417 on the interface portal 400. In some implementations, the receiving participants of the polling question can include members and non-members of the chat session, or another team or participant in the chat system that is not in the chat session. In one implementation, non-members may be notified by through an electronic transmission, such as email that a polling question is waiting. A link may be provided in the email notification directing the non-member to move into a browser to view/participate in the polling question. In addition to being notified that a polling question is waiting, the non-member may be provided with other information regarding the polling question, such the identity of the sending participant. The link to the polling question may remain active until a determined period of time, such as an expiration date for the polling questions set by the sending participant.
Once the fields of the selected polling question actionable objects in the side panel 430 are completed, the sending participants may preview the objects before submitting them to the chat session. The polling question actionable objects are then embedded in the chat message as a “structured” data object that can be executed by the client device of a receiving participant. In some implementations, the objects of the side panel 430 can be associated or assigned to one or more receiving participants. For example, information regarding the receiving participants may be inserted into recipient field 413. In one implementation, the sending participant may send the polling question actionable object to receiving participant in the chat session by activating a control 417 on the interface portal 400. In some implementations, the receiving participants may configure certain preferences regarding receiving polling question actionable objects, such as a type of polling questions the participant is willing to accept, a minimum compensation for accepting and/or answering the polling questions, etc.
Responses to the polling questions by members as well as non-members are made available to the sending participants and other authorized members of the chat session. The sending participant may choose whether to make the results available to a respondent immediately after the respondent responds to the polling questions or only once the expiration date and time has passed. In some situations, the sending participants can reward the receiving participants with recognition points or other type of tokens that will be discussed later in the disclosure.
In
B. Task Objects
In
As shown in
Once the task entry fields 436 are completed, the sending participants may preview the task before submitting the tasks actionable object 431 to the chat session. The tasks actionable object is then embedded in the chat message as a “structured” data object that can be executed by the client device of a receiving participant. In some implementations, the tasks actionable object 431 can be associated or assigned to one or more receiving participants. For example, information regarding the receiving participants may be inserted into recipient field 433. In one implementation, the sending participant may send the tasks actionable object 431 to receiving participant in the chat session by activating a control 438 on the interface portal 400. In some implementations, the receiving participants may configure certain preferences regarding receiving task actionable objects, such as a type of task the participant is willing to accept, a minimum compensation for accepting the task, etc.
In some implementations, the receiving participants can include members and non-members of the chat session, or another team or participant in the chat system that is not in the chat session. In one implementation, non-members may be notified by through an electronic transmission, such as email that a task is waiting. A link may be provided in the email notification directing the non-member to move into a browser to view the task. In addition to being notified that a task is waiting, the non-member may be provided with other information regarding the task, such the identity of the sending participant.
In some implementations, a control object 439 (e.g., a slider display object) to control an input of response information is inserted into the chat session related to the actionable object executed on the client device of the participants. If an individual task is assigned to more than one participant than multiple control objects, such as slider object 439, may be displayed indicating the progress (% completed) of that corresponding participant. The control objects are adjustable only by the intended participant. In some implementations, the “Task” percent complete along with the date that the slider is last updated is shown in the control object. For example, a task 50% complete on a date that was 4 days prior to the current date may indicate something different than a note from the participant indicating that the task was 50% complete as of the current date. In some implementations, slider object 439 may appear in a certain color and can be adjusted by the receiving participant in accordance with a process status of the task, such as Green, Yellow and Red.
C. Idea Objects
With regards to
As shown in
In some implementations, the receiving participants can include members and non-members of the chat session, or another team or participant in the chat system that is not in the chat session. In one implementation, non-members may be notified by through an electronic transmission, such as email that a task is waiting. A link may be provided in the email notification directing the non-member to move into a browser to view the task. In addition to being notified that a task is waiting, the non-member may be provided with other information regarding the task, such the identity of the sending participant.
In some implementations, a control object 447 (e.g., a slider display object) to control an input of response information into the chat session related to the actionable object executed on the client device of the participants. If an individual idea is assigned to more than one participant then multiple control objects, such as slider object 439, may be displayed. The control objects are adjustable only by the intended participant. In some implementations, the slider can be updated to provide a uniform numerical response for the participant rather that unstructured data. In some implementations, the interface portal 500 may provide an indicator (e.g., a display icon) of a total number of respondents to the idea as well as an average score of all responses received based on the control objects 447 associated with each receiving participant.
A. Sidebar Selection
In some implementations, the system provides asymmetrical chat through chat channels that are generally visible to all or directed participants in an intended group. An advantage of this is that users can reply 1 to 1 to someone in a group chat rather than the typical limited and distracting Reply-To-All messaging technology. For example, a user can reply directly to someone in a group chat that can be kept private from other group members without having to engage the entire group, while retaining context and relativity to the broader conversation for the participants of the 1 to 1 conversation.
Turning to
In some implementation, a first chat participant, such as participant A, clicks on and/or hovers over the display name for a second chat participant, such as participant G, in the main window 520, a sidebar session 531 opens. In some implementations, the first chat participant may also initiate the sidebar session 531 by activating a control 533 associated with a message from the second chat participant. The sidebar session 531 allows the first chat participant to interact directly with the second chat participant outside of larger group session channel 525 that includes the other participants. The sidebar session 531 includes functions available to users of interface portal 500. For example, sidebar session 531 allows the first and second chat participants to integrate actionable objects, such as actionable objects 119, into the private chat session 535 to enhance the electronic communications between the participants.
B. Targeted Inclusion with Response Rules
In some implementations, the system of the present disclosure allows users to send and receive emails from a group chat channel. For example, a user may send a message to the e-mail address of someone outside of the system. When a response to the email comes back, the originator of the message can choose to share the entire incoming email or subset thereof with the group or directed participants of the group. To avoid unwanted, unsolicited messages and spam back into a chat channel, the system ascribes a unique identifier to each email sent and in combination with rules for the unique identifier. This permits the sender of an email from the system to define and associate response rules to outgoing messages for replying emails. These rules may be applied to accept or reject to the incoming emails and may include, but not limited to, only accepting a defined number of responses or only accepting responses that are received within a defined period of time (or any combination thereof), accepting a certain number of response (e.g., up to three responses even after the time period expires), accepting emails from associated accounts (e.g., an email may be sent to a user's work email but responses can still be accepted from another (personal) email account associated with the user in accordance with the rules) as well as other types of rules. By including the email message into the chat message stream at the time and place an email originated from and is received, the emails are placed into the discussion in context. Thus, the channel message stream retains meaning and immediate lasting context that is not available in typical chat technology.
In
After entering the relevant information into the email session panel 540, the sending participant may integrate the email session into chat session by activating a control 546 on the interface portal 500. In this regard, an indicator 544 of the email session that is incorporated in the chat session may be displayed on the main window 520 of the interface portal 500. During the determined time period, data may be received from the email session to be incorporated into the chat session. For example, the data may be displayed in the main window 520 of the interface portal 500 as chat messages. If it is detected that the time period has expired, an alert may be provided by the system to the e-mail session to indicate that data received from the email session is rejected for inclusion in the chat message session.
As shown in
C. Bundle Communications
With bundle communications, the system of the present disclosure allows users to parse through a previous channel discussion and assemble those messages and actions that the user desires to be saved for future reference. These Bundles can be appended to messages in the chat channel, for example by the creator or others participants if so constructed. In one example, the bundle communications can include a bundle message associated with a particular topic, such as a bundle of best practices or a bundle consisting of an important team discussion or decisions.
In
D. Token Items
With regards to
In some implementations, a participant may enter or select a value in the value field 562 to be associated with the token item 560. The sending participant may integrate the token item into chat session by activating a control 564 on the interface portal 500. When the sending participant activates the control 564, a transaction is registered with the system regarding the token item 560. A confirmation screen may appear along with legal disclaimer information, terms and conditions and/or requesting that the form of payment. If a form of payment is previously entered and saved in the payment method field 563 then the participant may be asked to confirm the saved information. Alternatively, if a credit balance exists in the sending participant's account may be debited. In one implementation, a bank account associated with the sending participant may be established and funded by credit, cash or otherwise. If the account is pre-funded with an amount, for example $50, then subsequent selected token item 560 and their corresponding costs would be debited from the account balance.
Each token item 560 is assigned a transaction identifier and encoded with a unique identifier and authentication code to ensure the token's authenticity. In some implementations, techniques of disclosure for providing the token items 560 can be directly integrated into the point-of-purchase payment system utilized by any specific vendor. In one implementation, the token items 560 can be linked to a physical card (e.g., gift card) associated with the vendor. In other implementations, an exchange system may be employed so that if a user wants to (for example) exchange their token items 560 for another type of token item. In this regard, the exchange may include determining an exchange rate to convert a value of one token item to an equivalent value of the other token, such as converting dollars to their equivalent miles.
In some implementations, a participant may select a token item from the vendor list 561. In one implementation, the participant may send a token as a reaction to a chat message by selecting the chat message in the main window 520 and selecting a control icon 533 associated with gifting the token items 560. In this example the participant selects to gift the token item to a recipient as represented by the gift token icon 565 in the chat session. In some implementations, the receiving participant may identify certain selections to indicate their preferred gift choices. In this manner, the sending participant of a gift is able to identify the gift preferences of the intended recipient. In one implementation, the sending participant may override the receiving participant preferred gifts and select a different gift to provide to the recipient. Some gifts may have monetary value while others may be associated with, for example, a points system of the specific vendor. In some implementations, the gift token icon 565 may display a group of gifts to select from that are provided by the sending participant.
In some implementations, the recipient of the token does not have to be member of the chat session. For example, the recipients may be selected by a charity or other entities engaged in fundraising. In this example, the sending participant may conduct a funding campaign to solicit donations from receiving participants, who may be members or non-members, in the chat session. The receiving participants may receive the token item and choose to contribute an amount towards to recipient. The total amount raised and/or goal may be indicated in the token item as displayed on the interface portal 500.
In some implementations, the token items 560 may represent items up for auction as indicated by the auction token icon 566. In this example, a product or item may be shown along with a current bid amount. Users can bid on items being offered. In this regard, certain rules can be established to represent what constitutes a winning bid and how many winners there can be amongst the participants. User can click on the auction token icon 566 to view more details, conditions, reviews, etc., regarding the auction. Bidding for an item may end based on the rules as well as the rules defined by the sending participant and related to the item being offered. Users and/or authorized 3rd party vendors or companies can post items to be auctioned.
In some implementations, the token items 560 may represent items up for sale as indicated by the sale token icon 567. In some implementations, users may select a group sale or flash sale associated with the sale token icon 567 or direct the sale of the item to a particular participant in the chat session. Receiving participants may hover over, select, click or otherwise activate the sale token icon 567 to indicate an interest in a specific message. The user may be able to view additional information about the item being offered for sale by hovering or clicking (selecting) the sale token icon 567. When the user activates the sale token icon 567, several choices may be displayed for the user to indicate an interest and how the pay for the item. For example, the payment options may include, but not limited to, “buy now”, “buy”, “finance”, etc. In an alternative implementation, the payment options may be pre-configured and associated with a credit card, debit card, ACH or another type of payment account.
To better aid in understanding implementations of some of the aspects described above that are, for example, related to integrating actionable objects into an on-line chat communications platform, reference is now made to the following flow diagrams. It should be noted that the following operations do not have to be performed in the precise order described below. Rather, various operations can be handled in a different order or simultaneously, and operations may be added or omitted.
Method 600 begins at block 610 where state information of a chat message session associated with a plurality of participants of a group is determined. In block 620, an actionable object of a plurality of actionable objects is selected based on the state information of the chat message session. Each actionable object comprises a type indicator to characterize a user perceivable action associated with the actionable object. In this regard, the type indicator comprises at least one of: a question indicator, a task indicator or an idea indicator associated with the group. At least one participant of the plurality of participants is associated with the actionable object in block 630. Thereupon, the actionable object is provided to the chat message session to be selectably executed by a client device associated with the at least one participant in block 640. In block 650, the state information associated with the chat message session is updated in accordance with the actionable object.
Method 700 begins at block 710 where state information of a first chat message session of one or more chat message sessions. The first chat message session is associated with a first participant for a plurality of participants of a group is determined. In block 720, a selection of a second participant of the plurality of participants is received. A side chat area of a user interface is provided in block 730 in accordance with the selection. The side bar area allows the first participant and the second participant to engage in chat messages of a second chat message session associated with the user interface in addition to the one or more chat message sessions. In this regard, the second chat message session is hidden from display to other participants of the first chat message session. In block 740, the state information of the first chat message session is updated based on the second chat message session.
Method 800 begins at block 810 where state information of a chat message session associated with a plurality of participants is determined. In block 820, an email session associated with the one of the plurality of participants is identified in response to receiving input the participant. A time period is associated in block 830 with the email session indicating that the chat message session is active to receive data, via a network connection, from the email session during the time period. In block 840, the email session is link to the chat message session. In block 850, the state information associated with the chat message session is updated in accordance with the data received from the email session.
The exemplary computer system 900 may be comprised of a processing device 902 (which may correspond to a processing device 112 within system 100 of FIG. 1), a main memory 904 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) (such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), a static memory 906 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 916, which communicate with each other via a bus 908.
In a further aspect, the computer system 900 may include a processing device 902 (which may correspond to processing device 112), a volatile memory 904 (e.g., random access memory (RAM)), a non-volatile memory 906 (e.g., read-only memory (ROM) or electrically-erasable programmable ROM (EEPROM)), and a data storage domain 916, which may communicate with each other via a bus 908.
Processing device 902 represents one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processing device may be complex instruction set computing (CISC) microprocessor, reduced instruction set computer (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processing device 902 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. Processing device 902 is configured to execute processing logic 926 for performing the operations and steps discussed herein.
Computer system 900 may further include a network interface device 922. Computer system 900 also may include a video display unit 910 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 912 (e.g., a keyboard), a cursor control device 914 (e.g., a mouse), and a signal generation device 920 (e.g., a speaker).
Data storage device 916 may include a machine-readable storage medium (or more specifically a computer-readable storage medium) 924 having one or more sets of instructions embodying any one or more of the methodologies of functions described herein, including instructions encoding the techniques including the actionable object integration module 119 of
Instructions 926 may also reside, completely or partially, within volatile memory 904 and/or within processing device 902 during execution thereof by computer system 900, hence, volatile memory 904 and processing device 902 may also constitute machine-readable storage media.
Sidebars and Asymmetrical Group Messaging Views
This explanation is further to the explanation above with regard to “SIDEBAR SELECTION” and
At present, group chat applications present all messages to all group participants. In fact, this is a basic premise of what group chat is. Inherent in this approach to group chat (channels, rooms, etc) is that unnecessary and meaningless messages are presented to all group participants (Symmetrical—everyone sees everything i.e. all messages). It would be desirable to participate in a group discussion without being subjected to or forced to read meaningless messages—and more to the point, it would be desirable for individual members to communicate privately with another member (or subset of members) from within a group channel. In order to retain situational context, the private messages are desirably viewed embedded within the general channel message stream but also to avoid possible confusion or lack of continuity, the related private messages are desirably also able to be viewed together without the noise of interspersed general channel messages. Presented here is a possible solution and attempt to achieve the aforementioned objectives. It reduces the channel clutter imposed by comments such as “Thanks” intended for one but forced upon all, and provides a mechanism to allow for private sidebar conversations among a subset of a group or channel—while retaining the situational context of the private comments within and related to the overall general conversation. In an exemplary embodiment of the present invention, only the parties to a sidebar conversation see the messages related to the sidebar conversation (unless other action is taken).
As shown, any participant to the conversation in the main conversation pane can respond to a message that has been designated as an anchor message, and the response can appear in the main conversation pane. The response to the anchor message that is entered into the main conversation pane (“a response) is visible to all other participants in the main conversation pane. Furthermore, a response to a message in the sidebar (“a further response”) is seen by the participants participating in the sidebar conversation, but participants to the conversation in the main conversation pane that are not included in the sidebar conversation are excluded from seeing the message.
As shown in the figures, the anchor message and the response received to the anchor message in the main conversation pane may be simultaneously displayed. Furthermore, a response to the anchor message in the main conversation pane and a response to the message in the sidebar may be simultaneously displayed. As shown, the messages that appear in the main message pane are displayed one below the other. Furthermore, the messages displayed in the sidebar may be displayed one below the other.
While a non-transitory machine-readable storage medium 928 is shown in an exemplary implementation to be a single medium, the term “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable storage medium” shall also be taken to include any medium that is capable of storing or encoding a set of instruction for execution by the machine and that causes the machine to perform any one or more of the methodologies of the disclosure. The term “machine-readable storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media.
Some portions of the detailed descriptions are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the video processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as “receiving”, “determining”, “associating”, “updating”, “providing”, “integrating”, “selecting”, “executing”, “processing”, or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
Examples described herein also relate to an apparatus for performing the methods described herein. This apparatus may be specially constructed for performing the methods described herein, or it may comprise a general-purpose computer system selectively programmed by a computer program stored in the computer system. Such a computer program may be stored in a computer-readable tangible storage medium.
The methods and illustrative examples described herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used in accordance with the teachings described herein, or it may prove convenient to construct more specialized apparatus to perform methods 300 and 400 and/or each of its individual functions, routines, subroutines, or operations. Examples of the structure for a variety of these systems are set forth in the description above.
Whereas many alterations and modifications of the disclosure will no doubt become apparent to a person of ordinary skill in the art after having read the foregoing description, it is to be understood that any particular implementation shown and described by way of illustration is in no way intended to be considered limiting. Therefore, references to details of various implementations are not intended to limit the scope of the claims, which in themselves recite only those features regarded as the disclosure.
This application is a Continuation of U.S. patent application Ser. No. 18/073,652, filed Dec. 2, 2022, which is a Continuation of U.S. patent application Ser. No. 17/065,494, filed Oct. 7, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/931,283 filed Jul. 16, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/712,952 filed Dec. 12, 2019, which is a Continuation of U.S. patent application Ser. No. 16/376,427, filed Apr. 5, 2019, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/014,578, filed Jun. 21, 2018, which is a Continuation-In-Part of U.S. patent application Ser. No. 15/858,696, filed Dec. 29, 2017, which is a Continuation-In-Part of Ser. No. 15/431,077, filed Feb. 13, 2017, which claims the benefit of priority under 35 U.S.C. 119(e) to U.S. Provisional Patent Application No. 62/446,067, filed Jan. 13, 2017, the disclosures of all of which are incorporated by reference herein in their entireties. This application is also a Continuation of U.S. patent application Ser. No. 18/073,652, filed Dec. 2, 2022, which a Continuation of U.S. patent application Ser. No. 17/065,494 filed Oct. 7, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/931,283 filed Jul. 16, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/746,412 filed Jan. 17, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/712,952 filed Dec. 12, 2019, which is a Continuation of U.S. patent application Ser. No. 16/376,427, filed Apr. 5, 2019, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/014,578, filed Jun. 21, 2018, which is a Continuation-in-Part of U.S. patent application Ser. No. 15/858,696, filed Dec. 29, 2017, which is a Continuation-In-Part of Ser. No. 15/431,077, filed Feb. 13, 2017, which claims the benefit of priority under 35 U.S.C. 119(e) to U.S. Provisional Patent Application No. 62/446,067, filed Jan. 13, 2017, the disclosures of all of which are incorporated by reference herein in their entireties. This application is also a Continuation of U.S. patent application Ser. No. 18/073,652, filed Dec. 2, 2022, which a Continuation of U.S. patent application Ser. No. 17/065,494 filed Oct. 7, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/931,283 filed Jul. 16, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/746,412 filed Jan. 17, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/376,427 filed Apr. 5, 2019, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/014,578 filed Jun. 21, 2018, which is a Continuation-In-Part of U.S. patent application Ser. No. 15/609,663, filed May 31, 2017, which is a Continuation of U.S. patent application Ser. No. 15/293,620, filed Oct. 14, 2016, which claims the benefit of priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 62/358,719, filed Jul. 6, 2016, and U.S. Provisional Patent Application No. 62/253,229, filed Nov. 10, 2015, the disclosures of all of which are incorporated by reference herein in their entireties. This application is also a Continuation of U.S. patent application Ser. No. 18/073,652, filed Dec. 2, 2022, which a Continuation of U.S. patent application Ser. No. 17/065,494 filed Oct. 7, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/931,283 filed Jul. 16, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/746,412 filed Jan. 17, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/376,427 filed Apr. 5, 2019, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/014,578 filed Jun. 21, 2018, which is a Continuation-In-Part of U.S. patent application Ser. No. 15/858,696 filed on Dec. 29, 2017, which a) is a Continuation-In-Part of U.S. patent application Ser. No. 15/431,077 filed Feb. 13, 2017, which claims the benefit of priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application 62/446,067 filed Jan. 13, 2017, and b) claims the benefit of priority under 35 U.S.C. 119(e) to U.S. Provisional Patent Application 62/518,905 filed on Jun. 13, 2017, the disclosures of all of which are incorporated by reference herein in their entireties. This application is also a Continuation of U.S. patent application Ser. No. 18/073,652, filed Dec. 2, 2022, which a Continuation of U.S. patent application Ser. No. 17/065,494 filed Oct. 7, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/931,283 filed Jul. 16, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/746,412 filed Jan. 17, 2020, which is a Continuation-In-Part of U.S. Ser. No. 16/376,427, filed Apr. 5, 2019, which claims the benefit of priority under 35 U.S.C. 119(e) to U.S. Provisional Patent Application 62/666,137, filed May 3, 2018, and U.S. Provisional Patent Application 62/783,410, filed Dec. 21, 2018, the disclosures of all of which are incorporated by reference herein in their entireties. This application is also a Continuation of U.S. patent application Ser. No. 18/073,652, filed Dec. 2, 2022, which a Continuation of U.S. patent application Ser. No. 17/065,494 filed Oct. 7, 2020, which is a Continuation-In-Part of U.S. patent application Ser. No. 16/931,283 filed Jul. 16, 2020, which claims the benefit of priority under 35 U.S.C. 119(e) to U.S. Provisional Patent Application 63/045,513, filed Jun. 29, 2020, the disclosure of which is incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
7945620 | Bou-Ghannam | May 2011 | B2 |
8819132 | Serr | Aug 2014 | B2 |
RE46309 | Go | Feb 2017 | E |
9722891 | Hanlon | Aug 2017 | B2 |
10298529 | Lee | May 2019 | B2 |
10866929 | Watanabe | Dec 2020 | B2 |
11194447 | Delanghe | Dec 2021 | B2 |
11341093 | Johnston | May 2022 | B2 |
11539649 | Rosania | Dec 2022 | B2 |
11586584 | Johnston | Feb 2023 | B2 |
11750539 | Treat | Sep 2023 | B2 |
20050131924 | Jones | Jun 2005 | A1 |
20060128404 | Klassen | Jun 2006 | A1 |
20090254843 | Van Wie | Oct 2009 | A1 |
20090282369 | Jones | Nov 2009 | A1 |
20100124322 | Bill | May 2010 | A1 |
20100142542 | Van Wie | Jun 2010 | A1 |
20100205541 | Rapaport | Aug 2010 | A1 |
20100257450 | Go | Oct 2010 | A1 |
20110047227 | Arthurs | Feb 2011 | A1 |
20120198360 | Wanderski | Aug 2012 | A1 |
20140067977 | Rasmussen | Mar 2014 | A1 |
20140229855 | Anderson | Aug 2014 | A1 |
20140304505 | Dawson | Oct 2014 | A1 |
20160344679 | Lane | Nov 2016 | A1 |
20160380940 | Lan | Dec 2016 | A1 |
20170142036 | Li | May 2017 | A1 |
20170163594 | Anderson | Jun 2017 | A1 |
20170272388 | Bern | Sep 2017 | A1 |
20170357422 | Jon | Dec 2017 | A1 |
20170366493 | Wilde | Dec 2017 | A1 |
20180287982 | Draeger | Oct 2018 | A1 |
20180293996 | Mortis | Oct 2018 | A1 |
20220353129 | Soman | Nov 2022 | A1 |
20230094375 | Cohen | Mar 2023 | A1 |
Number | Date | Country |
---|---|---|
2011141624 | Nov 2011 | WO |
Entry |
---|
“Die, Email, Diel A Flickr Cofounder Aims to Cut Us All Some Slack”, Readwriteweb, Lexisnexis, https://advance.lexis.com/api/permalink/33dd79e2-90f5-409d-ae27-5a2c7e86bf31/?context=1000516>. (dated Aug. 14, 2013, 4:15 PM) 2 pages. |
“How Slack changed the way we work by putting the customer experience first”, Repeat Customer Podcast, Episode 3, [online][retrieved May 9, 2019], Retrieved from the Internet: <URL: https://www.zendesk.com/resources/slack-customer-experience/, (2019) 13 pages. |
Adrienne LaFrance, “The Triumph of Email”, Atlantic Online, Lexisnexis, https://advance.lexis.com/api/permalink/32d7ddd9-d4c1-4a73-86f7-08ab5842fde6/?context=1000516, (dated Jan. 6, 2016) 5 pages. |
Alba, Davey, “Slack's New Threaded Messages Tame Your Meandering Chats,” Wired, Jan. 18, 2017, 5 pages. |
David Auberbach, “Re-Animator. How Stewart Butterfield created Flickr and Slack out of the ashes of failed projects” [online][retrieved May 9, 2019]. Retrieved from the Internet: <URL: https://slate.com/business/2014/05/stewart-butterfield-flickr-and-slack-how-he-snatched-victory-from-the-jaws-of-defeat.html>. (dated May 28, 2014, 2:48 PM) 8 pages. |
Ernie Smith, “Picking Up The Slack”, Tedium, [online][retrieved May 9, 2019], Retrieved from the Internet: <URL: https://tedium.co/2017/10/17/irc-vs-slack-chat-history/>. (dated Oct. 17, 2017) 8 pages. |
Florin, Hubert, “slack design—Threads in Slack: A Long Design Journey (Part 1 of 2),” Slack, undated, 9 pages. |
Florin, Hubert, “slack design—Threads in Slack: A Long Design Journey (Part 2 of 2),” Slack, undated, 12 pages. |
Internet Relay Chat, Wikipedia,, [online][retrieved May 30, 2019]. Retrieved from the Internet: <URL: https://en.wikipedia.org/wiki/Internet_Relay_Chat>. (dated May 28, 2019) 17 pages. |
Jonathan Vanian, “Why these startups think chat apps are the next big thing in workplace collaboration”, Gigaom, Lexisnexis, https://advance.lexis.com/api/permalink/e83778c8-09c8-43aa-9ba0-88526283de69/?context=1000516, (dated Aug. 1, 2014, 5:45 PM) 4 pages. |
Lynley, Matthew, “Slack launches threaded messaging to take conversations off to the side,” TechCrunch, Jan. 18, 2017, 5 pages. |
Matsumoto, T. et al., “Chocoa Communicator—A New Communication System Based on Awareness and Text Communications”, Fujitsu Sci. Tech. J., 36, 2, (Dec. 2000) pp. 154-161. |
Matthew Ingram, “Flickr co-founder launches Slack, an all-in-one messaging tool designed to kill email forever”, Gigaom, Lexisnexis, https://advance.lexis.com/api/permalink/0b676b7c-aec3-4560-861e-d030d 1dd008c/?context=1000516, (dated Feb. 12, 2014, 7:03 PM), 2 pages. |
Michael Carney, “Slack is thriving on a cocktail of whimsy and great timing”, Pandodaily, Lexisnexis, https://advance.lexis.com/api/permalink/dd2d4ee5-2ddf-4d3a-a1d9-3bcee5e38b74/?context=1000516, (dated Feb. 6, 2015, 2:12 AM) 3 pages. |
Mike Issac, “Slack, a Start-Up With an App to Foster Business Collaboration, is Valued at $1.1 Billion”, The New York Times Blogs (BITS), Lexisnexis, https://advance.lexis.com/api/permalink/3eb84b34-a8f9-4d7d-9573-89d9598a4963/? context=1000516>. (dated Oct. 31, 2014) 2 pages. |
Newton, Casey, “Slack adds threaded messages to take the clutter out of public channels,” The Verge, Jan. 18, 2017, 6 pages. |
Oikarinen, J. & Reed, D., “Internet Relay Chat Protocol”, Request for Comments: 1459, Network Working Group, [online][retrieved May 30, 2019], Retrieved from the Internet: <URL: https://www.rfc-editor.org/rfc/rfc1459.txt>. (dated May 1993) 57 pages. |
Rebecca Walberg, “Email biggest office waste of time: survey”, National Post, at FP10, Lexisnexis, https://advance.lexis.com/api/permalink/96268e3f-26ad-48ac-a98f-6c39804ebded/?context=1000516, (dated Mar. 4, 2014) 2 pages. |
Robert Hof, “Stewart Butterfield on How Slack Became A $2.8 Billion Unicorn”, Forbes, [online][retrieved May 9, 2019]. Retrieved from the Internet: <URL: https://www.forbes.com/sites/roberthof/2015/06/02/stewart-butterfield-on-how-slack-became-a-2-8-billion-unicorn-2/#7c31937d7d9c>. (dated Jun. 2, 2015, 3;25 PM), 4 pages. |
Rosania, Paul, “slack engineering—Weaving Threads,” Slack, undated, 8 pages. |
Slack, “Using Slack—Use threads to organize discussions,” undated, 9 pages. |
The Big Pivot w/ Slack's Stewart Butterfield, Masters of Scale Podcast, Episode 13 (Aired Nov. 14, 2017), https://mastersofscale.com/#/stewart-butterfield-the-big-pivot/, (dated Jan. 17, 2018) 21 pages. |
Yeung, Ken, “Slack introduces threaded replies,” VentureBeat, Jan. 18, 2017, 9 pages. |
Aaron Souppouris, “Twitch introduces ‘Cheering’ emotes for tipping streamers”, https://www.engadget.comn/2016-06-27-twitch-cheering-beta-bits-currency-tips.html, Updated Jun. 27, 2016, 8 pages. |
Matt Binder, “YouTube announces new ‘applause’ feature that allows users to pay creators directly”, https://mashable.com/article/youtube-applause-updates, Feb. 17, 2021, 1 page. |
Matt Binder, “YouTube rolls out a new revenue stream for creators, Super Thanks”, https://mashable.com/article/youtube-super-thanks-revenue-creators, Jul. 20, 2021, 7 pages. |
Natt Garun, “YouTube launches Super Chat, a tool that lets you pay to pin comments on live streatms”, https://www.theverge.com/2017/1/12/14249630/youtube-super-chat-pay-pin-comments-live-stream, Jan. 12, 2017, 5 pages. |
Neeraj Shukla, “YouTube Super Chat: What is YouTube Super Chat and How Does it Work?”, https://www.appypie.com/blog/youtube-super-chat, Updated Dec. 13, 2023, 1 page. |
Robin Fontaine, “Introducing Pinned Cheers”, Nov. 9, 2016, 5 pages. |
Robin Fontaine, “Pinned Cheers Updates: Thanks, Twitch Community!”, https://blog.twitch.tv/en/2016/11/10/pinned-cheers-updates-thanks-twitch-community-5db9d312561c/, Nov. 10, 2016, 5 pages. |
Number | Date | Country | |
---|---|---|---|
20240106775 A1 | Mar 2024 | US |
Number | Date | Country | |
---|---|---|---|
63045513 | Jun 2020 | US | |
62783410 | Dec 2018 | US | |
62666137 | May 2018 | US | |
62518905 | Jun 2017 | US | |
62446067 | Jan 2017 | US | |
62358719 | Jul 2016 | US | |
62253229 | Nov 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 18073652 | Dec 2022 | US |
Child | 18535572 | US | |
Parent | 17065494 | Oct 2020 | US |
Child | 18073652 | US | |
Parent | 16376427 | Apr 2019 | US |
Child | 16712952 | US | |
Parent | 15293620 | Oct 2016 | US |
Child | 15609663 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16931283 | Jul 2020 | US |
Child | 17065494 | US | |
Parent | 16746412 | Jan 2020 | US |
Child | 16931283 | US | |
Parent | 16712952 | Dec 2019 | US |
Child | 16746412 | US | |
Parent | 16712952 | Dec 2019 | US |
Child | 16746412 | US | |
Parent | 16376427 | Apr 2019 | US |
Child | 16712952 | US | |
Parent | 16014578 | Jun 2018 | US |
Child | 16376427 | US | |
Parent | 15858696 | Dec 2017 | US |
Child | 16014578 | US | |
Parent | 15609663 | May 2017 | US |
Child | 15858696 | US | |
Parent | 15431077 | Feb 2017 | US |
Child | 15858696 | US |