| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes https://github.com/boothj5/profanity/issues/1079
|
|
|
|
| |
There is a typo here. So this actually never worked ;-)
|
|
|
|
|
| |
`/privileges on` lists `Moderator`, `Visitor` etc. Formatting was wrong
here. Printing privilige followed by nickaname in the same line.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Wrapping for the occupants panel like already exists for the roster
panel. See `/occupants wrap on`.
Regards https://github.com/boothj5/profanity/issues/690
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
`/occupants header char` now sets a character that is displayed before
the role (moderator, visitor..) in a room. Similar to `/roster header
char` is displaying a char for the roster.
Regards https://github.com/boothj5/profanity/issues/690
|
| |
|
|
|
|
| |
Indent the jid one more space than nick.
|
| |
|
|
|
|
| |
And when not connected.
|
|
|
|
|
|
|
|
| |
Roster has a `/roster contact indent` option.
Now we have the same for occupants. So contacts in roster and in MUC can
have configurable indentation.
Regards https://github.com/boothj5/profanity/issues/690
|
| |
|
|\
| |
| | |
Handle presence received before roster
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Presence of contact not found in roster are filtered out.
But sometimes roster is received after a first few presences.
We choose to store presences until we receive roster and then process
this presences.
Fixes #1050
|
| |
| |
| |
| | |
Fixes https://github.com/boothj5/profanity/issues/1069
|
|/
|
|
| |
This should close #1052
|
|
|
|
|
|
|
| |
When auto joining a MUC we don't have access to required information so
we just don't start OMEMO at this time.
Once we receive disco info we then try to start OMEMO.
|
|
|
|
|
|
|
| |
This should never happens since we should ensure MUC is Non-Anonymous
before enabling OMEMO.
But we should neither segfault if this happens.
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is 3 policy:
- manual: OMEMO session are only started manually
- automatic: OMEMO session are only started if they have been started
manually before
- always: OMEMO session are always started unless they have been ended
manually before
Closes #1040 and fixes #1052
|
|\
| |
| |
| |
| | |
paulfariello/hotfix/OMEMO-ensure-muc-is-nonanonymous
Ensure MUC is Non-Anonymous before starting OMEMO
|
| |
| |
| |
| |
| |
| | |
Store MUC anonymous type in mucwin for that purpose.
Fixes #1065
|
|/
|
|
| |
Fixes #1055
|
|\
| |
| |
| |
| | |
paulfariello/hotfix/handle-message-without-id-in-muc
Handle message without id in MUC
|
| |
| |
| |
| | |
Some clients seems to send message without id.
|
| |
| |
| |
| |
| | |
We should not remove signed prekey and prekey from persistent storage
when cleaning OMEMO store on disconnect.
|
| |
| |
| |
| |
| | |
If OMEMO identity.txt is malformed just abort loading.
User should be able to call `/omemo gen` again.
|
|/
|
|
|
|
|
| |
If OMEMO wasn't loaded, removing key would create empty identity.txt
file. Then at load time it would segfault profanity.
Another commit should fix load of malformed identity.txt.
|
|
|
|
|
|
|
|
| |
When connecting for the first time or when creating a new account don't
use only 'profanity' as default resource.
Some server don't support having 2 connection with same resource. Using
profanity as default lead to deconnections.
|
| |
|
|
|
|
|
|
|
|
| |
When decrypting first message with prekey, libsignal wants to remove
used prekey from storage. Return value on success should be 0.
We used to return number of deleted keys. Thus libsignal was considering
we failed to remove the key and we were ignoring plaintext.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Stop using "jid:device_id" keys. And move long term storage to its own
file: trust.txt.
|
|
|
|
| |
Add sv_ev_connection_features_received for that purpose
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Reflected messages can't be filtered by nick only otherwise you might
ignore messages comming from you on another devices.
Consequently we maintain a list of sent messages id in mucwin.
To be sure the id will be correctly reflected we use the origin-id
stanza.
|
| |
|
|
|
|
| |
devicelist handler should be kept after trigger
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We try to reconfigure node and publish again.
If it fails again then we give up.
|