Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update limitations section in readme
- Loading branch information
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,11 +10,11 @@ | |
| ### Limitations | ||
|
|
||
| - Not yet supported by [signal-cli](https://github.com/AsamK/signal-cli/issues): | ||
| - Quoting a message ([#213](https://github.com/AsamK/signal-cli/issues/213)) | ||
| - Adding @-mentions in sent messages ([#584](https://github.com/AsamK/signal-cli/issues/584)) | ||
| - Voice calls ([#80](https://github.com/AsamK/signal-cli/issues/80)) | ||
|
|
||
| - *Sending* read receipts for received messages. | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong. 
exquo
Author
Collaborator
|
||
| - "View once" and "expiring" messages. | ||
| - See also: open [issues](https://github.com/isamert/scli/issues). | ||
|
|
||
|
|
||
It's happening!! 😄
AsamK/signal-cli@27dbc67
edit: looking at the
signal-clicode, sending read receipts has been possible for a while now (a message is identified by its timestamp). Using the new--send-read-receiptsconfig flag inscli's daemon startup command would be easy, but sending read receipts on every message received isn't really what read receipts are about lol.