| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Access roster from plugins
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Change all instances of *get_nick_from_roster to *get_name_from_roster
to match the convention of names in the roster itself.
|
| | |
|
| |
| |
| |
| |
| | |
Only display server contact information heading when we have actual
addresses.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes the bug mentioned in
https://github.com/profanity-im/profanity/issues/1478#issuecomment-794161606
The rest of https://github.com/profanity-im/profanity/issues/1478 I
can't reproduce. Seems to work fine.
|
|\ \
| | |
| | | |
Add support for XEP-0157 server contact information discovery
|
| | |
| | |
| | |
| | | |
Format the output of cons_show_disco_contact_information() so that it matches cons_show_disco_info().
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
Change some OMEMO Logging to info
|
|/ / |
|
|\ \
| | |
| | | |
Disable notifications by default
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since I didn't find a way to discover whether a notification server is
running I decided to disable them by default. So people without one will
not have such a bad lag due to timeout from libnotify.
Fix https://github.com/profanity-im/profanity/issues/977
|
|\ \ \
| | | |
| | | | |
Fix log rotation
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
See https://github.com/profanity-im/profanity/issues/1518
It has a good explanation of what happened:
```
Apparently, the _rotate_log_file function tried to extract user-provided
name from currently used mainlogfile and restart logging to the same
place after rotation, but currently this is interpreted as a full path
instead. As I understand, the log rotation is no longer done with
user-provided paths at all so this should be simply skipped altogether
now as passing any non-NULL value is interpreted as user-provided.
Replacing start with NULL appears to fix it for me.
```
In log_msg() we only rotate the log if not user_provided_log.
https://github.com/profanity-im/profanity/pull/1455 changed the
behaviour from user defined filename in the log dir to using full path.
|
|\ \ \
| |/ /
|/| | |
Escape all parameters in SQL statements
|
|/ /
| |
| |
| |
| | |
Some more parameters might contain quotes, so escape all of them
with %q by using sqlite3_mprintf.
|
| |
| |
| |
| | |
Changed in a5a0dd6c919a2b4f12ef2b4f57a0d9a2a9cabf34
|
| | |
|
| |
| |
| |
| | |
See https://github.com/profanity-im/profanity/issues/1521#issue-860017824
|
| |
| |
| |
| |
| | |
No need to check anymore since we are now saving per account.
Like this we also could reopen the same file again.
|
| | |
|
| |
| |
| |
| |
| | |
See
https://github.com/profanity-im/profanity/issues/1521#issue-860017824
|
| |
| |
| |
| |
| | |
See
https://github.com/profanity-im/profanity/issues/1521#issuecomment-854110973
|
| | |
|
|\ \
| | |
| | | |
XEP-0353: Display a notice when receiving a call
|
| | |
| | |
| | |
| | |
| | |
| | | |
Display a notice in the console when someone tries to call us.
Implement https://github.com/profanity-im/profanity/issues/1525
|
|/ / |
|
| |
| |
| |
| | |
Fix https://github.com/profanity-im/profanity/issues/1554
|
|\ \
| | |
| | | |
Add command to show single bookmark details
|
|/ /
| |
| |
| |
| |
| |
| | |
`/bookmark list` lists all bookmarks with its details.
`/bookmark list <jid>` shows the details of a single bookmark.
Implement https://github.com/profanity-im/profanity/issues/1558
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
OMEMO: Separate handling of device list
Two changes:
* First register the handler before sending the request
* Don't add own jid to handler
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In profanity are two handlers for device list:
* _handle_own_device_list
* _handle_device_list_start_session
I seems both handler will start a session via
omemo_start_device_session_handle_bundle
_handle_own_device_list will also make sure, that the own device is withing the
omemo device list. If we add the _handle_device_list_start_session into the
hashmap, we are not going the republish ourself, in case we clean-up the device
list from another client.
This will maybe fix #1552
99 Little Bugs in my Code.
Take one down.
Patch it around.
113 Bugs in my Code
|
|\ \ \
| | | |
| | | | |
Fix wrong message display when mention is triggered
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
`jubalh: jubalh jubalh` resulted in `20:32:34 - testuser1:
jubalh20:32:34 - testuser1: : jubalh20:32:34
- testuser1: jubalh`
Print date/nick only once at beginning of line.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
get_mentions() correctly counts utf-8 chars. So the positions of
mentions we get from there are correct.
But in _mucwin_print_mention() we set position equal to byte.
We need to use utf-8 safe functions here.
Regards https://github.com/profanity-im/profanity/issues/1231
|
|\ \ \
| |/ /
|/| | |
Message received without body error log
|
|/ /
| |
| |
| |
| |
| |
| | |
This is not an error, the message has no body because of
XEP-0085: Chat State Notifications.
Changed log level from error to info.
|
|\ \
| | |
| | | |
OMEMO: Don't encrypt to yourself (MUC)
|
| | |
| | |
| | |
| | | |
Use connection_get_barejid instead of connection_get_fulljid.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As defined in XEP-0384 the application should not encrypt the message to own
devices. Within a groupchat, yourself are a recipients as well.
We will check the recipients and filter out the own device of the own jid.
This Pull Request will fix Issue: #1541
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This bug was introduced in 1ec606540eb0f474f3d968d3566a7c56d778a367 when
`g_strdup_printf` was used instead of `asprintf`.
Problem discoverd by raspeguy.
Mistake discovered by optmzr and Martin.
Thanks to everybody involved!
|
|\ \ \
| | | |
| | | | |
Restart OMEMO Session after lost connection
|
| | | | |
|