Age | Commit message (Collapse) | Author |
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Version 1.1.0 of Last Message Correction (0308) added clarifications
that break the way poezio handles corrections. Instead of linking
corrections to the previous correction/message as we were doing, we
are now required to link all corrections to the original messages.
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
only auto-reconnect if not already reconnecting, needs slixmpp!37
See merge request poezio/poezio!78
|
|
Fixes what 9da6f5328c714f6bdcbc89cb038e10116ab0bed6 intended to do.
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
|
|
If there's a human-readable explanation of the error, it should be there.
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Skip whitespace ping logging
See merge request poezio/poezio!75
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
|
|
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
It's currently impractical to use out-of-tree plugins that want to be
distributed via distribution channels.
Poezio now looks for every entry point registered in the
`poezio_plugins` entry group, and will use the first matching module
with the specified name.
This also helps specifically for the OMEMO plugin that has a conflicting
name (omemo / omemo) with the backend library.
Thanks jonas for pointing this out.
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
There is no apparent reason why a disco#info should be done on the
domain Jid rather than the bare Jid. MUCs advertize their MUC-y-ness on
the bare Jid. This will also fix cases like chat@dino.im which is a MUC
component itself (whereas dino.im is a user host), and biboumi
components that serves a mic of MUCs and (IRC) users.
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Use new `by_jid` API to search for any tab containing the barejid, and
then look at the type of Tab.
Move the Tab search at the top of the checks so that we stop searching
if we already have done all this work for previous stanzas.
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
This change transmits the original JID of the sender (in decrypt) or
receiver(s) (in encrypt).
Handling of MUC is not complete. It is possible that some participants
have access to realjids while others don't (e.g., moderators in
semi-anon MUCs).
The code currently doesn't handle this and this will cause at least two
issues:
- Sending an encrypted message in a semi-anon MUC would reveal the
sender's identity (public key)
- Recipients wouldn't be able to decrypt this message as they don't have
access to the sender's realjid. Unless they already have the bundle
available and then they could associate the public key with a jid
(another privacy issue/defeating the point of semi-anon rooms).
TODO: Fix this ^
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
|
|
|
|
|
|
|
|
|
|
|
- supported tab types is a list of tabs this plugin should be active in
(only chattabs)
- trust_states is a dict[str → set] containing only two keys: accepted
and rejected, whose values are the internal plugin states that should
allow encryption and the ones that should not
|
|
(yes, another one)
|
|
|
|
|