Apparatus and Method for Maintaining a Message Thread with Opt-In Permanence for Entries

• US 20140359032A1
• Filed: 05/09/2014
• Published: 12/04/2014
• Est. Priority Date: 05/30/2013
• Status: Active Grant

• Current Assignee: Snap, Inc.
• Original Assignee: Snap, Inc.
• Inventors: Spiegel, Evan, Sehn, Timothy
• Granted Patent: US 9,742,713 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads

Abstract

A server has a processor and a memory storing a message thread module with instructions executed by the processor to maintain a message thread between users of client devices. Message thread state changes are queued at the server. The message thread is revised based upon the message thread state changes to form shared message thread state. The shared message thread state is stored. The shared message thread state is supplied in response to a request for the message thread from a user

Claims

1. A server, comprising:

a processor; and

a memory storing a message thread module with instructions executed by the processor to maintain a message thread between users of client devices by

serving a message thread with a new text entry to a client device in response to a request for the message thread from a user;

collecting message thread state change from the client device, wherein the message thread state change represents an indication to automatically delete the new text entry of the message thread after the duration of a transitory display period on the client device unless an indication of a gesture applied to a display screen presenting the new text entry of the message thread is received from the client device during the transitory display period;

queuing the message thread state change at the server along with additional message thread state changes associated with the collecting operation performed for additional users associated with the message thread;

revising the message thread based upon the message thread state change and the additional message thread state changes to form shared message thread state;

storing the shared message thread state; and

supplying the shared message thread state in response to a request for the message thread from a user.

2. The server of claim 1 wherein revising includes asynchronous batch mode processing.

3. The server of claim 1 wherein queuing is performed in response to a user exit from a message thread.