| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
For some time users could choose to have the old way "unanimous" where
all the MUC history is just grey (or whatever was set). Now it is always
just displayed like regular new incoming MUC text.
|
| |
|
|
|
|
|
| |
Fix mistake in a condition. Also add sanity check to
win_refresh_with_subwin().
|
|
|
|
| |
sorry.. doing too many things at once..
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1321
|
| |
|
|
|
|
| |
Protect against invalid reads by checking the length.
|
| |
|
|
|
|
| |
Fixup for 86af6925d9fc0b2656eac15b0c8c7aba60589ce5
|
|
|
|
| |
No effect here.
|
| |
|
|
|
|
| |
Follow up for a6fa8e8e0d6b86c669ac2fb2b7be44812604c21f
|
|
|
|
|
|
|
| |
Setting the local pointer to NULL has no effect.
_destroy_tab() is used for g_hash_table_new_full() so we cant use a **
and set tab to NULL.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This actually only set the local ran pointer to NULL.
But we want an effect on the outside variable.
|
|
|
|
| |
Use another name.
|
|
|
|
| |
Let's use another name.
|
|
|
|
| |
Not needed anymore since 0942d98c6116dc4b9b608e7483f1d6a8f62c84d7
|
|
|
|
|
| |
Each of those should only occur one time. But let's make sure we only
write/alloc one time to be on the safe side.
|
| |
|
|\
| |
| | |
OMEMO Device List only for non anonymous MUCs
|
| |
| |
| |
| |
| |
| |
| | |
Profanity request the OMEMO Device List for all members, also if the MUC is
anonymouse. If the user is Admin / Owner, the device list will be requtest.
Issue #1315
|
|/ |
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1314
|
|
|
|
|
|
|
|
| |
That's actually not good practise.
Realized this when checking for multiple symbol definition in issue
mentioned below.
Regards https://github.com/profanity-im/profanity/issues/1314
|
| |
|
| |
|
|
|
|
|
| |
Some stuff just floods the log file. We only need this when debugging.
Others are useless without more info.
|
|
|
|
|
|
|
|
|
|
| |
glib functions can allocate a GError object that must be freed with
g_error_free(). Otherwise a memory leak happens.
There are similar unfixed places in omemo, check:
grep "&error" src/omemo/omemo.c
Fixes #1304.
|
|
|
|
|
|
|
|
|
|
|
| |
MUCPMs and regular chat messages get printed with the same code.
But we don't save MUC PMs in the sqldb, because another jid could use
the same nick the next time.
And if we would take the log out we would need a different routine,
checking for resourcepart too.
Fix https://github.com/profanity-im/profanity/issues/1312
|
|
|
|
| |
g_date_time_add_days() actually creates a new one.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Only when we start the conversation.
Not yet when we get messaged and a new window is opened.
Need to have sorting of messages in the window buffer then, I guess.
Also MAM IQ should only be send one time in such a case.
If MAM is enabled history from sql backend will not be shown.
`mam` in profrc enables experimental MAM.
Can change soon again. Don't rely on stuff in this stage ;)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Later we will have several options.
Getting everything since last timestamp (if none everything at all).
Getting everything since today + configure time (1 week).
Should also have a reload all command like conversations once you
cleared the history.
All MAM messages should be written into sql db.
And then probably displayed from there so that regular history works
too.
|
| |
|
|
|
|
|
| |
Is usefult in many cases if we want cleaner code.
Hope this edit didn't break anything though ;-)
|
| |
|
| |
|
|
|
|
| |
Let's not crash :-)
|
|
|
|
|
|
|
|
| |
MAM messages don't have a type nor a from.
If we detect a message without type let's log it and exit without
continuing to try to parse it.
Otherwise we go into _handle_chat() and crash on the no from.
|
|
|
|
|
|
| |
Send a request (which we can't handle yet) :-)
Regards https://github.com/profanity-im/profanity/issues/660
|
| |
|
|
|
|
|
|
|
|
|
| |
Our search was too broad, and thus incorrect.
One of the various mistakes it can cause was
https://github.com/profanity-im/profanity/issues/1308
Fix https://github.com/profanity-im/profanity/issues/1308
|
|\
| |
| | |
Fix use-after-free in stanza_create_caps_from_query_element()
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The function creates a form to find such strings as software, os, etc.
It remembers the strings allocated by form_create() and use them below
in caps_create(). The issue is that the form is destroyed before and as
result the strings are freed too.
As solution, allocate own copy of strings.
|
|/ |
|
|
|
|
| |
So we don't have to check for MUC another way.
|