`chathistory` Support #370

Add `id` component to messages, and record message id when available. Request all messages since last seen message or latest <=500 messages when joining a channel. Request <=500 older messages when scrolling to the top of channel buffer. Drop duplicate messages.

Initial timestamp-based depduplication.

…or of its utilization). Fix timestamp-based deduplication. Skip `RPL_TOPIC` and `RPL_TOPICWHOTIME` messages when looking for the oldest/latest message in a channel.

…p-to-date message reference. Add fuzz interval to timestamp based `chathistory` requests. Ignore messages received at/after `JOIN` when finding the latest message in a channel (replaces ignoring `RPL_TOPIC` and `RPL_TOPICWHOTIME` messages). Ignore internal messages when finding the oldest/latest message in a channel.

…when finding oldest/latest message in channel.

…herwise unrelated to `chathistory`).

…lication, then convert to `History::Partial` for all channels without a pane.

…d when joining a channel. Filter timestamp-based `chathistory` batches in order to reduce the need for record-time deduplication. Use hash of `Encoded` for client-side message-id (used to distinguish between timestamp-based `chathistory` messages with the same timestamp).

…ry` messages. Add preference for automatically loading older `chathistory` messages when scrolled to the top of channel history.

…g at the first message that belongs in the backlog. This way the backlog divider won't be moved when messages are added to the beginning of a message history via `chathistory`.

Renamed configuration option to more typical phrase.

Use `server_time` to position message with respect to unreferenceable messages.

Fix for `opened_at` calculation in `make_partial` (the earliest received message does not always appear at the beginning of the `unread_messages` vector).

Other simplifications and clarifications suggested by review.

Efficient deduplication via the new insertion strategy can be used in place of filtering received `chathistory` batches. Minor tweaks to insertion strategy: more stringent checking for triggering unread notification (to avoid false positives) and more relaxed matching for `JOIN`/`PART`/`QUIT` messages (to avoid false negatives).

… all `chathistory` subcommands. Switch from repeated `AFTER` subcommands to `LATEST` → repeated `BETWEEN` commands to receive history when joining a channel (`AFTER` can fail silently, with 0 returned messages, if the message reference is no longer in the history available from the server). Tweaks to `insert_message` (utilize same fuzz constant as `send_chathistory_request`) and to `is_referenceable_message` (disallow `RPL_TOPIC` and `RPL_TOPICWHOTIME` as message references).

Allow messages with matching content to match as duplicate without matching `server_time` iff the stored message is a sent message and the inserted message is a received message; reduced strictness to match sent messages where the server's copy will have a slightly different time than the client.

… channel. Messages retrieved when joining a channel are no longer properly deduplicated.

Channels will be marked as having unread messages even if those messages will ultimately wind up deduplicated.

…ssages sent while the user was disconnected from the server.

… is acknowledged.

…tory` requests that depend on supported message reference types. Increase precision of message reference retrieval functions.

…thistory` messages (and for persisting unread state across application close/open). Rearranges message storage.

…message history in order to store its `msgid`.

…launch.

…ed, in case support is later enabled.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`chathistory` Support #370

`chathistory` Support #370

Commits on Jun 25, 2024

chathistory Support #370

Are you sure you want to change the base?

chathistory Support #370

Commits on Jun 25, 2024

`chathistory` Support #370

`chathistory` Support #370