Commit graph

23 commits

Author SHA1 Message Date
af33cd41e5
Learn about chain length: new should_heartbeat method
With this commit, slixmpp-omemo now reads the ratchet chain length,
(both receiving and sending), that we should track to know when to send
a heartbeat message.

This allows us to signal other devices that we are still active and
listening. Some clients will stop encrypting to us if we haven't replied
for a certain number of messages.

The current 0384 spec (0.7) says we should send a heartbeat message at
least once this number goes over 53 (fair dice roll). It doesn't say
when a client may/should stop encrypting to us, or what it should do at
all once we go over 53.

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2021-07-13 20:29:14 +02:00
38701075e9
echo_client: fix wrong variable error
Thanks mathieui

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2021-07-13 20:28:19 +02:00
59e82ec9ee
echo_bot: implement basic commands
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2021-07-12 23:25:57 +02:00
ba028d98c8
echo_bot: Don't pass the whole message to plain_reply and encrypted_reply anymore
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2021-07-12 23:12:09 +02:00
cea2345f29
echo_bot: change messages style
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2021-07-12 19:26:24 +02:00
e6ce39bcc9
Echo_bot: Add documentation for expect_problems
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-09-02 02:28:39 +02:00
153edfb564
Echo_bot: Use expect_problems and handle MissingBundleException
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-09-02 02:21:53 +02:00
2dc08c9d2f
Echo_bot: prevent loops when decrypting/encrypting
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-09-02 02:21:00 +02:00
79a4f417ed
Adapt example to new decrypt API
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-09-02 02:18:16 +02:00
7449e5c908
Remove wrong return types for now; Remove unused JID import
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-27 13:34:40 +00:00
36e385a6ea
example-bot: specify why we automatically trust when encrypting
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-27 12:15:06 +00:00
1496becac7
example-bot: Add note about encrypting for MUCs
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-27 11:45:21 +00:00
34226fbea7
Fix typo in bot docstring
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 18:25:55 +00:00
478d56803a
Add TODO for NoEligibleDevicesException and MissingBundleException
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 17:28:15 +00:00
72c8acca85 example-bot: add TODO for expect_problems
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 12:28:06 +00:00
63dc98b07b example-bot: Add catchall except in decryption and encryption
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 12:28:06 +00:00
9e70954a0e example-bot: attempt at returning encrypted messages
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 12:28:06 +00:00
af8c731307 example-bot: Use async methods instead
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 12:28:06 +00:00
c7983d176d Remove handler on message_encryption
This event is being sent by slixmpp's EME plugin, when a message
contains an EME tag. I can already test for this myself, so I'd rather
not hook this event to remove duplicated messages.

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 12:28:06 +00:00
b71a367bcb Remove the while loop; add dummy encrypted_reply
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 12:28:06 +00:00
368bbd9005 Add some more comments in NoAvailableSession handling
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 12:28:06 +00:00
643b1695a1 Change undecided/untrusted exceptions' comment
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 12:28:06 +00:00
3061aa3372 First attempt at an example
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-02-24 12:28:06 +00:00