| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1435
So far we didn't print the error if it contained `<error
type="cancel">`. It appears that the code always thought this is a
service-not-available (so one is either blocked or the account doesn't
exist) and printed `Recipient not found`.
But there can be other errors as well. Like in above mentioned issue
`not-allowed`.
Let's just print the text.
In case of the cancel type we still remove the jid from the chat
sessions. I'm not entirely sure whether this needs to be done in other
cases too.
|
|
|
|
|
| |
This part of the code was waiting for xmpp_stanza_new_from_string() from
libstrophe 0.10.0.
|
|
|
|
|
|
|
|
| |
xmpp_stanza_get_child_by_name_and_ns
Replace our own stanza_get_child_by_name_and_ns() with the upstreamed
xmpp_stanza_get_child_by_name_and_ns() provided by the new
libstrophe/libmesode 0.10.0.
|
|
|
|
|
| |
jid_create() for attribute "to" was called twice and the 1st object was
lost.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add stable stanza IDs to ProfMessage struct.
We parse this for 1:1 messages (MUC needs to be done too).
<stanza-id> for live messages
<result id="x"> for MAM messages
Regards MAM: https://github.com/profanity-im/profanity/issues/660
Regards Stable IDs: https://github.com/profanity-im/profanity/issues/1207
|
| |
|
|
|
|
|
|
| |
This reverts commit 9b55f2dec0ea27a9ce4856e303425e12f866cea2.
Sorting the includes creates some problems.
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1396
|
|
|
|
| |
This one will always be set.
|
|
|
|
|
| |
So that we don't have to pass the wrapping stanza and can handle
the error nicer.
|
|
|
|
|
| |
Trying to simplify the conditions so we don't have duplicate code
in both of those functions.
|
|
|
|
| |
Since its done in both cases.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Authored by DebXWoody in:
https://github.com/profanity-im/profanity/pull/1369
Regards: https://github.com/profanity-im/profanity/issues/1366
Since I'm in the process of cleaning up message.c I take this now
so he doesn't have to rebase.
I also omitted the _handle_normal() case since I'm not sure that would
be correct.
Probably will be addressed again when continuing the cleanup.
|
|
|
|
|
|
|
|
| |
Messages from Conversations contains:
<request xmlns='urn:xmpp:receipts'/>
And would not be displayed in Profanity as it never reached
_handle_chat(..).
|
| |
|
|
|
|
|
| |
So far we logged when we receive a message without a type. Which is
actually quite common and makes no sense.
|
|
|
|
|
| |
RFC 6121 allows only few types.
So we can also remove that check in _handle_chat().
|
|
|
|
| |
Both cases are tested before entering that function.
|
|
|
|
|
| |
AFAIK it can only be one.
Except at STANZA_NS_MUC_USER which is used in several cases.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Fix for some build cases introduced in 2c94ee5a88f64332a3f41f41a4d314fc52200e31
Fix https://github.com/profanity-im/profanity/issues/1376
|
|
|
|
|
|
|
|
|
| |
Basic implementation of XEP-0373: OpenPGP for XMPP.
https://xmpp.org/extensions/xep-0373.html
Command /ox
Issue: #1331
|
|
|
|
| |
Check for pointer to be NULL before dereferencing it.
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1342
|
|
|
|
| |
Instead of connection_get_fulljid() and then creating a Jid from it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With d1d0ad8d1a8e28690aa8723566dd64c1ccdcf9d6 we set a timestamp to now
for all messages upon receival. Even if the original message didn't
contain any timestamp. So we can use the timestamp of retrieval for
logging and displaying and don't get them at each of those location
where they might differ.
This means that timestamp will never be NULL.
I don't see why we would want to check for the chat state only if
timestamp isn't there.
Probably because in XEP-0085 there is not timestamp defined.
So if it thats stanza it's not there and we can parse quicker, but there
is nothing forbidden it to be there.
Related to https://github.com/profanity-im/profanity/issues/1339
|
| |
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
| |
The mucuser boolean is not now needed anymore.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Timestamps are only set if a message is delayed.
If none is set let's set it upon recaival so we don't have to set it
when it gets displayed.
This means we will also have it for logs etc in the ProfMessage.
|
|
|
|
|
|
|
|
| |
win_println_incoming_muc_msg() always used the current time. Now let's
use whatever is sent int he message struct (from the delay stanza or
the current time that we set now once the message is received).
No playing with the time upon display anymore.
|
|
|
|
| |
Fix init. mistake introduced in e9c5c1979d836ed75c37d48651710b4fd125cfb2
|
|
|
|
| |
We need to unref the timestamp before setting a new one.
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1261
|