18674419. MAINTAINING A MESSAGE THREAD WITH OPT-IN PERMANENCE FOR ENTRIES simplified abstract (Snap Inc.)

MAINTAINING A MESSAGE THREAD WITH OPT-IN PERMANENCE FOR ENTRIES

Organization Name

Snap Inc.

Inventor(s)

Evan Spiegel of Los Angeles CA (US)

Timothy Sehn of Marina Del Rey CA (US)

MAINTAINING A MESSAGE THREAD WITH OPT-IN PERMANENCE FOR ENTRIES - A simplified explanation of the abstract

This abstract first appeared for US patent application 18674419 titled 'MAINTAINING A MESSAGE THREAD WITH OPT-IN PERMANENCE FOR ENTRIES

The abstract describes a patent application for a server system that maintains a message thread between users of client devices. The system automatically deletes new text entries after a transitory display period unless a user interacts with the entry. Message thread state changes are collected and used to update the shared message thread state.

• The server system includes a processor and memory storing a message thread module.
• The message thread module serves new text entries to client devices in response to user requests.
• Message thread state changes are collected from client devices, indicating whether to delete new text entries.
• The system queues message thread state changes and updates the shared message thread state accordingly.
• The shared message thread state is stored and supplied to users upon request.

Potential Applications: - Messaging applications - Collaborative platforms - Social media networks

Problems Solved: - Efficient management of message threads - Automatic deletion of irrelevant content - Enhanced user experience

Benefits: - Streamlined communication - Reduced clutter in message threads - Improved user engagement

Commercial Applications: Title: "Enhanced Message Thread Management System" This technology can be used in messaging apps, social media platforms, and collaborative tools to improve user experience and streamline communication processes. The market implications include increased user engagement and retention rates.

Questions about the technology: 1. How does the system determine when to delete new text entries in the message thread? 2. What are the key advantages of updating the shared message thread state based on user interactions?

Frequently Updated Research: Stay updated on advancements in message thread management systems and user interaction analytics to enhance the efficiency and effectiveness of the technology.

Original Abstract Submitted

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. The message thread module serves a message thread with a new text entry to a client device in response to a request for the message thread from a user. Message thread state change is collected from the client device, where 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. The message thread state change is queued at the server along with additional message thread state changes associated with the collecting operation performed for additional users associated with the message thread. The message thread is revised based upon the message thread state change and the additional 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.