| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Send a request (which we can't handle yet) :-)
Regards https://github.com/profanity-im/profanity/issues/660
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
xmpp_stanza_add_child() takes own reference to the child stanza.
Therefore we have to release our reference or the child is lost
and not freed otherwise.
|
|
|
|
| |
We need to unref the temp datetimes again.
|
|
|
|
|
|
|
|
| |
So far the correction is sent. But the UI in Profanity itself is not
updated.
Also autocompletion for `/correct` with the last sent message is
missing.
|
|
|
|
| |
"retrieve1" should have been only for testing.
|
| |
|
|
|
|
| |
Introduced in bf2e09feee1697c570fcfb9e1e44a8ec991bd196.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far we saved the timestamp which also had the `from`.
But we need this only to find out whether it's MUC history.
For displaying we should use the oldest delay timestamp.
Also in
https://github.com/profanity-im/profanity/commit/61f66966ddfe8ebd8bae26dd7ff92d777004edda#diff-4926fd4577a336bd3eb240f8104a5c5bL837
a error was introduced.
Before we saved the timestamp in all cases. And only if timestamp AND
from was given we went into MUC history case.
Normal timestamp saving was not done anymore only if it also had a from
attribute.
Regards https://github.com/profanity-im/profanity/issues/1254
|
|
|
|
| |
Have two helper functions one for XEP-0203 and one for XEP-0091.
|
| |
|
|
|
|
|
| |
Proof of concept.
Needs error checking, a nice interface, general cleanup..
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1227
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/profanity-im/profanity/issues/1190 had another issue:
Sometimes servers send multiple </delay> and we just checked the first
one we got and only used it if the 'from' attribute was fitting.
However it could be that we actually wanted the second </delay> element
and there the 'from' would have been right.
So we need to loop through them until we get the one with the fitting
'from'.
Fix https://github.com/profanity-im/profanity/issues/1190
|
|
|
|
| |
Fix bug introduced in 68af0aad65d243e654866eac5a7cd728ee293aa0.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem is that in _handle_groupchat() we look for
STANZA_NS_STABLE_ID which will result in origin-id or stanza-id.
It seems like prosody servers send origin-id first, so this worked in
all my tests. But actually we cannot be sure of the order.
So far we stopped after the first element was found.
I only found xmpp_stanza_get_child_by_ns() and
xmpp_stanza_get_child_by_name() in libstrophe. But we need a combination
of both.
So I created stanza_get_child_by_name_and_ns() for Profanity. I need to
remember to upstream this to libstrophe later (if they really don't have
such a function).
Fix https://github.com/profanity-im/profanity/issues/1223
|
|
|
|
|
| |
We sent `prof_prefix_uuid` as id. Where the prefix was also optional.
We don't need this at all.
|
|
|
|
|
|
|
|
| |
Double-check that a <delay/> tag on a groupchat message was actually
added by the MUC service (rather than the sending client) before
assuming it was received from the MUC history.
Fixes #1173.
|
| |
|
|
|
|
| |
https://github.com/profanity-im/profanity/issues/1085
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1085
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
We try to reconfigure node and publish again.
If it fails again then we give up.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Store hints are required has some server might discard messages without
body. Here we ensure OMEMO messages are stored on server and delivered
to client when they connect back.
It's really important since it avoid libsignal to desynchronize
counters.
|
|
|
|
| |
Fix {signed,}_pre_key store
|
| |
|
| |
|
|
|
|
| |
Devicelist subscription can be done directly with caps_add feature.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Add support for xep 0050 ad-hoc commands, without multi-step
|
| | |
|
| |
| |
| |
| | |
Tested with ping from biboumi
|
| |
| |
| |
| | |
Also handle list result
|
| |
| |
| |
| | |
Initial commit to test commands API
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Move `p_sha1_hash()` from `common.c` to `xmpp/stanza.c` as it is only
used in this file and now depends on libstrophe so xmpp is a better
namespace folder.
Renaming it as `_stanza_create_sha1_hash()`. And making static since
only used here.
The function cannot be tested in the unit tests anymore.
Once functional tests are working again we should write a test for the
sha1 functionality.
|
|
|
|
|
|
|
|
|
|
|
| |
create_unique_id() was changed to use UUIDs instead of a counter in the
last commit. Since now it depends on connection_create_uuid() which is
in the xmpp subfolder the function should also be moved there.
Renamed it to connection_create_stanza_id() and moved it to
src/xmpp/connection.c.
Discussion happened in https://github.com/boothj5/profanity/pull/1010
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|