| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This patch was provided by @paulfertser and applied by @jubalh.
Thanks a lot Paul!
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I think this PR already solves and improves the MAM situation a lot.
What's @MarcoPolo-PasTonMolo still wanted to do in this branch is:
* MAM for mucs
* Check if url and quotes autocompletion works fine
* Check if the api still works fine
* Resolve conflicts
Conflicts are solved with this commit.
MAM for mucs can be another feature PR.
The rest we can check while being on master. And more people can help
testing.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This prevents scrolling to top and initiating another MAM request while
still fetching the initial one.
Also free timestamp object in database.c
|
| |
| |
| |
| |
| |
| | |
Did this by waiting for a batch of MAM messages to arrive before
prepending them to the buffer. Also limited the number of messages
to fetch to 10 so that the user gets more frequent updates.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Fetch from mam without displaying when all mam messages get received
display new messages from db.
Unstable, initial mam doesn't get displayed unless we start scrolling.
|
| | |
|
| |
| |
| |
| |
| | |
Taken from here:
https://github.com/modernxmpp/modernxmpp/commit/cd3e871e55c2cff45dffd05d6e50380b99845849
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Only nicknames, photos, birthdays, addresses, telephone numbers, emails,
JIDs, titles, roles, notes, and URLs are supported
Due to the synopsis array not having enough space, `/vcard photo
open-self` and `/vcard photo save-self` are not documented properly in
the synopsis section of the `/vcard` command, but they are documented in
the arguments section
Fixed memory leak in vcard autocomplete (thanks to debXwoody)
|
|\ \
| | |
| | | |
Replace `call_external`'s implementation with an async one
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Drawback is that we can't check the exitcode anymore.
But we were unsure why/when we need this, see:
https://github.com/profanity-im/profanity/pull/1760/files#r980868708
Fixes https://github.com/profanity-im/profanity/issues/1759
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
In the function stanza_create_avatar_metadata_publish_iq, use the format
string `"%"G_GSIZE_FORMAT` instead of "%lu", for an argument of type
gsize.
|
| |
| |
| |
| |
| |
| | |
in before it just used the input command line as it was but this fixes
this by adding formatting using `format_call_external_argv` which is
already used in `url open` executable.
|
| |
| |
| |
| | |
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* save SM state and send-queue entries on disconnect
* restore SM state and send-queue entries on reconnect
fixes #698
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
| |
| |
| |
| |
| | |
Most likely they didnt trust/sign the key. Which is described in the
profanity-ox-setup man page.
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
MarcoPolo-PasTonMolo/fix/chat-with-self-duplicate-msgs
Fix duplicate messages in chat with oneself.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Messages would get duplicated when you chat with yourself, worse if you
had omemo enabled the duplicated message would say something along the
lines of "Your client doesn't support OMEMO". The cause was carbons
when the message was sent from another client, whilst it was a sent
and received message when profanity was the one to send it. This commit
ignores the carbon message in the 1st case and ignores the received one
in the 2nd.
Fixes https://github.com/profanity-im/profanity/issues/1595
|
|\ \
| | |
| | | |
Add `/avatar set` command to publish avatar
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use `/avatar set <path>` where <path> is an image file to upload a new
avatar for the current user. When the avatar is too big it gets scaled
down. Scaling code copied from dino.
Fixes https://github.com/profanity-im/profanity/issues/1687
|
|\ \ \
| |_|/
|/| | |
Update capabilities of muc on available presence
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Muc configuration in profanity used to not update until next login, ie:
make muc non_anonymous and members_only but be unable to start omemo
until next login. Now a disco info request is sent after forrm submit
and chatroom details are changed accordingly.
Fixes https://github.com/profanity-im/profanity/issues/1347
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Profanity would ignore the silent nick change in some places. The roster
and history would show the correct nick, new messages from the current
user and the "Autojoined <jid> as <nick>" message would show the wrong
one. This commit fixes that problem.
Fixes https://github.com/profanity-im/profanity/issues/757
|
|/
|
|
|
|
|
|
|
| |
`/ox discover` segfaults on some misconfigured? nodes because there are
newlines before and after some pubkey-metadata stanzas so the newlines
get treated as seperate stanzas. This commit just skips each stanza in
public-keys-list that doesn't have a fingerprint.
Fixes https://github.com/profanity-im/profanity/issues/1713
|
|
|
|
|
|
| |
Now whenever the name of a room changes, either in profanity or another
client, it gets updated inside profanity.
Fixes https://github.com/profanity-im/profanity/issues/1710
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We only want to have the decrypted message or the alternative body in
message->plain.
Also let's print error messages if it makes sense and log other issues.
Partly addresses the commit in the comit mesage of:
2dc0cc489c872941e18a622c091f74bf5b0b043f
|
|
|
|
| |
To make the destinction clearer and easier to search.
|
|
|
|
|
|
|
| |
Should have been done alogn with e9f218cdf6e15f4469d77cbaee59cc8501ed4e82.
Like this people who are not in the roster can get our public key and
write messages to use.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
________________________________________
< No comment - should be much better now >
----------------------------------------
\
\
\ >()_
(__)__ _
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix https://github.com/profanity-im/profanity/issues/1693
```
@StefanKropp @DebXWoody please check `_handle_ox_chat()` I don't
understand what you are doing there.
1)
First plain is assigned `message->plain =
p_ox_gpg_decrypt(xmpp_stanza_get_text(ox));`
and then in the same if block you overwrite this with `message->plain =
xmpp_stanza_get_text(b);` without freeing the old value as far as I can
see.
2)
Sometimes even doing `message->plain = "OX error: No payload found";`.
Shouldn't there be a `strdup()`? I think later on we try to free the
whole message struct. So we can't mix this static things.
```
|
| |\
| | |
| | | |
Fix SIGABRT when using wrong argument order for receiving ox key
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Asserting here is not the right thing to do at all.
A person could have a typo in the fingerprint. Or like in the case of
the reported bug just confuse the arguments.
An additional check for valid jid should be added later to the calling
function maybe.
Fix https://github.com/profanity-im/profanity/issues/1698
|