| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
A autoping is to make sure that there is still a connection between server and
client. If the application receives incoming stanza, the connection is fine.
There is no need to wait for response, if there are other incomings.
Issue: #1333 and #1315
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the new `/serversoftware` command.
```
/software user@domain.org/resource
/serversoftware domain.org
```
Fix https://github.com/profanity-im/profanity/issues/1338
|
|
|
|
| |
No effect here.
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
g_date_time_add_days() actually creates a new one.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Send a request (which we can't handle yet) :-)
Regards https://github.com/profanity-im/profanity/issues/660
|
| |
|
| |
|
|
|
|
|
|
| |
Default is on. `revail.os=false` in the `connection` section of the
config can disable it.
A command to configure this will follow.
|
|
|
|
|
| |
So far we only sent client name and version. Let's also send the OS
name.
|
|
|
|
|
|
|
|
|
|
| |
Cannot be configured for now.
Can be set via `adv.notify.discoversion` in the `notification` section.
Will notify about version requests via XEP-0092 and XEP-0232.
Client version can still be seen via caps (capabilities).
See `stanza_attach_caps()`.
|
|
|
|
| |
We will need this if we want to display the Name instead of the JID.
|
| |
|
| |
|
|
|
|
|
| |
It's not up to date.
Some time ago we changed from individual handlers to general ones.
|
|
|
|
|
| |
We sent `prof_prefix_uuid` as id. Where the prefix was also optional.
We don't need this at all.
|
| |
|
|
|
|
|
| |
Command form userdata were freed by iq_id_handler.
We should now free the command ourself.
|
| |
|
|
|
|
| |
Taken care of by the destructor.
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1148
|
|
|
|
|
| |
Free is done in destructor now.
Regards https://github.com/profanity-im/profanity/issues/1148
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so far only the key part was freed. We also need to free the actual
handler.
Fix:
```
==21171== 1,128 bytes in 47 blocks are definitely lost in loss record
3,476 of 3,670
==21171== at 0x483677F: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==21171== by 0x434248: iq_id_handler_add (iq.c:265)
==21171== by 0x4B122E: omemo_devicelist_request (omemo.c:46)
==21171== by 0x4AC411: omemo_start_session (omemo.c:409)
==21171== by 0x4AC37C: omemo_start_sessions (omemo.c:396)
==21171== by 0x447881: sv_ev_roster_received (server_events.c:189)
==21171== by 0x444019: roster_result_handler (roster.c:312)
==21171== by 0x433FC2: _iq_handler (iq.c:202)
==21171== by 0x5AF118E: ??? (in /usr/lib64/libmesode.so.0.0.0)
==21171== by 0x5AEDBDA: ??? (in /usr/lib64/libmesode.so.0.0.0)
==21171== by 0x5AFA43E: ??? (in /usr/lib64/libmesode.so.0.0.0)
==21171== by 0x6818AA4: ??? (in /usr/lib64/libexpat.so.1.6.8)
==21171== by 0x681A3AB: ??? (in /usr/lib64/libexpat.so.1.6.8)
==21171== by 0x681D7EB: XML_ParseBuffer (in
/usr/lib64/libexpat.so.1.6.8)
==21171== by 0x5AF0A63: xmpp_run_once (in
/usr/lib64/libmesode.so.0.0.0)
==21171== by 0x432E5D: connection_check_events (connection.c:104)
==21171== by 0x4323B3: session_process_events (session.c:255)
==21171== by 0x42C097: prof_run (profanity.c:128)
==21171== by 0x4B2627: main (main.c:172)
```
|
|
|
|
| |
Free id_handlers. Fix memory leaks.
|
|
|
|
|
|
|
|
|
| |
If Profanity is disconnected in any way before ping response is
received, the autoping timer will expire after the next connection
is established. As result, user will be disconnected immediately.
Cancel autoping timer in ev_disconnect_cleanup(), so it is done
for all kind of disconnections.
|
|
|
|
|
|
|
| |
When auto joining a MUC we don't have access to required information so
we just don't start OMEMO at this time.
Once we receive disco info we then try to start OMEMO.
|
|
|
|
| |
Add sv_ev_connection_features_received for that purpose
|
|
|
|
| |
Goal is to create other kind of callback no based on id cmp
|
| |
|
| |
|
|
|
|
| |
In order to avoid duplication with xep 0133 support in command execution
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Configuration windows are now being used by both muc and cmd.
|
|
|
|
| |
Also change wins_get_by_string prototype in order to handle const str.
|
| |
|
|
|
|
| |
Tested with ping from biboumi
|
|
|
|
| |
Also handle list result
|
|
|
|
| |
Initial commit to test commands API
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
XMPP_FEATURE_PING insted of STANZA_NS_PING
|
| |
|