docs: update documentation for SSE migration
This commit is contained in:
+10
-6
@@ -8,7 +8,7 @@ Its ultimate goal is to provide a fast and efficient user interface for Signal c
|
||||
The tech stack is Elisp and SQLite (for storing conversations)
|
||||
|
||||
** Setup
|
||||
The project assumes a working installation of signal-cli and interfaces with that via JSON-RPC.
|
||||
The project assumes a working installation of signal-cli and interfaces with that via JSON-RPC. Noise uses Server-Sent Events (SSE) to receive messages in real-time.
|
||||
|
||||
** Dependencies
|
||||
|
||||
@@ -138,11 +138,15 @@ Once signal-cli is running and Noise is installed:
|
||||
- =M-x noise-new-chat-sync-contacts= — re-sync contacts from signal-cli
|
||||
- =M-x noise-receive= — fetch new messages from signal-cli once
|
||||
|
||||
While =noise-mode= is enabled, Noise polls signal-cli for new messages
|
||||
every =noise-receive-interval= seconds (default 5). Incoming messages,
|
||||
delivery/read receipts, typing indicators, and messages sent from your
|
||||
other linked devices are all stored locally and reflected in open
|
||||
buffers automatically.
|
||||
While =noise-mode= is enabled, Noise connects to signal-cli's SSE
|
||||
endpoint at =/api/v1/events= for real-time message reception. Incoming
|
||||
messages, delivery/read receipts, typing indicators, and messages sent
|
||||
from your other linked devices are all stored locally and reflected in
|
||||
open buffers automatically.
|
||||
|
||||
The SSE connection automatically reconnects with exponential backoff
|
||||
if the connection is lost. You can configure the maximum reconnect
|
||||
delay via =noise-sse-max-reconnect-delay= (default 60 seconds).
|
||||
|
||||
If signal-cli has more than one account registered, set =noise-account=
|
||||
to the phone number you want to use (E.164 format), or run
|
||||
|
||||
Reference in New Issue
Block a user