| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | | |
Format the output of cons_show_disco_contact_information() so that it matches cons_show_disco_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.
|
|/ /
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| | |
`/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
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`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
|
|/ /
| |
| |
| |
| |
| |
| | |
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!
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the connection has been re-established, chat and groupchat with OMEMO
should restat the OMEMO Session.
Fix: #1530
* Added HAVE_OMEMO
* clang-format and user output
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If we are not able to publish our own device list, we just ignored it.
This commit will show at least an error message and informs the user that this
device is currently not in the list of devices.
See Issue: #1538
Next task will be to handle the <precondition-not-met/> conflict properly.
|
|\ \ \
| | | |
| | | | |
Feature - attention flag
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Display the `[ATTENTION]` hint in the titlebar for both chatwins and
mucwins.
* Use THEME_TITLE_TEXT instead of THEME_TITLE_ENCRYPT
* Have separate function `_show_attention` and don't do it in unrelated
`_show_privacy`.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
When the user enables or disabled the attention flag, a message will be
displayed in the chat window.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Attention flag for groupchat and display the windows via "/wins attention"
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
User is able to toggle a flag for chat windows. This flag should be used to mark
the window for "Attention".
Use Ctrl+f to mark the window.
|
|/ / |
|
|\ \
| | |
| | | |
Display OMEMO device ID
|
| | |
| | |
| | |
| | |
| | | |
Display the OMEMO device ID which has been generated, when the user generated
OMEMO crytographic materials via /omemo gen.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The most loggings has been set to debug. Just in case of error / problem the
logging should be done with log-level ERROR or WARNING.
We will see later, which loggings should be switched to log-level INFO.
This improvement has been done to find OMEMO bugs.
See also: #1070 #1530 #1538
|
| | |
|
| |
| |
| |
| |
| | |
Found by DebXWoody.
Led to always be true (which still made it work in most cases).
|
| |
| |
| |
| | |
So users don't get surprised if they don't know the barejid of the nick.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In https://github.com/profanity-im/profanity/issues/1070 we have:
`OMEMO encryption for MUC PM (OMEMO MUCs are not anonymous, so we should
start a regular 1:1 in this case instead of MUC PM. A discussion started
to make this a general feature #1531)`
In https://github.com/profanity-im/profanity/issues/1531 we have the
general issue to start regular 1:1 messages instead of MUC PMs if the
room is non-anonymous.
This is like suggested in https://docs.modernxmpp.org/client/groupchat/.
|