about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
| * Update ui_ask_password to support confirmationThorben Günther2021-03-113-5/+9
| | | | | | | | | | Just prints a different string to console. Useful for changing passwords or account registration.
* | Update to the newest version of XEP 0363 (HTTP Upload)Maximilian Wuttke2021-03-115-36/+67
|/ | | | | | | | | | | | | Main changes: 1. Attributes instead of tags 2. Read the optional <header> tags and send them in the HTTP PUT header: * Authorization * Cookie * Expires Co-authored-by: Martin Dosch <martin@mdosch.de>
* Merge pull request #1496 from mwuttke97/omemo-bugfixesMichael Vetter2021-03-106-78/+128
|\ | | | | [OMEMO]: Fix bundle publishing
| * [OMEMO]: Fix bundle publishingMaximilian Wuttke2021-03-091-14/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the following options in `omemo_bundle_publish()`: - "pubsub#persist_items" = "true" - "pubsub#access_model" = "open" The same options are also used in Gajim. I've tested this on two different servers. The bundle was successfully added as a new PEP node. Test cases: 1. Normal use on my main account 2. Log in into a fresh tesst account on a different server 3. `/omemo clear_device_list`. In this case, the client(s) may have to be restarted. Note: In `_omemo_bundle_publish_result`, there's a route that is taken when the bundle publish stanza failed. In this case, the node is configured manually, i.e. the access_model is set to 'open'. I have manually tested this case, but this case didn't naturally occur for me. Note: The option "pubsub#max_items=max" is REQUIRED for the bundle publication, as per XEP-0384. However, this is not done in other clients (I've checked the source code of Gajim and Conversations), and it is also not supported by Prosody. Cf. <https://github.com/xsf/xeps/pull/988>.
| * Logging [OMEMO]Maximilian Wuttke2021-03-091-1/+26
| | | | | | | | | | Also "handle" some errors in `_omemo_bundle_publish_configure` if the stanzas can't be found
| * Variadic version of `stanza_attach_publish_options`Maximilian Wuttke2021-03-092-16/+37
| |
| * Logging [OMEMO]Maximilian Wuttke2021-03-091-6/+10
| |
| * Logging [CONNECTION]Stefan2021-03-091-0/+1
| |
| * Changes logging format to [OMEMO]Stefan2021-03-091-48/+49
| |
| * OMEMO - Removed start session after roster receivedStefan2021-03-091-4/+0
| | | | | | | | | | Reduce the request during startup of profanity Removed omemo_start_sessions from sv_ev_roster_received
* | Remove "file://" from file namesMaximilian Wuttke2021-03-091-0/+3
|/ | | | | Rationale: When copying an image in some application, a URL instead of a path is copied to the clipboard.
* Cmd definitions: Add offline option to occupantsThorben Günther2021-03-081-2/+5
|
* Merge pull request #1495 from xenrox/offline-membersMichael Vetter2021-03-0810-10/+96
|\ | | | | MUC: Show offline members in sidebar
| * MUC: Show offline members in sidebarThorben Günther2021-03-0810-10/+96
| |
* | Prevent segfault in sv_ev_incoming_message()Michael Vetter2021-03-051-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Regards https://github.com/profanity-im/profanity/issues/1488 Actually I would have loved to see the stanza that caused the segfault since I'm not entirely sure whether this actually means that we do something wrong earlier on. Right now I don't know why the to_jid should be empty. Let's prevent the segfault for now and see whether we get further bugreports later. Segfaulting issue got introduced with dd566d8d561099bbfc81b2fab22318bbad0cf3da.
* | Draw wintitle using fputs and fprintf instead of /bin/echo.Akce2021-02-281-25/+8
|/
* Merge pull request #1484 from kaffeekanne/calm-openbsd-syslogMichael Vetter2021-02-151-5/+5
|\ | | | | Calm OpenBSD syslog
| * Calm OpenBSD syslogkaffeekanne2021-02-151-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | On every write to `chatlog.db` syslog throws ``` profanity: vfprintf %s NULL in "INSERT INTO `ChatLogs` (`from_jid`, `from_resource`, `to_jid`, `to_resource`, `message`, `timestamp`, `stanza_id`, `archive_id`, `replace_id`, `type`, `encryption`) SELECT '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s' WHERE NOT EXISTS (SELECT 1 FROM `ChatLogs` WHERE `archive_id` = '%s')" ``` in `/var/log/messages`. Checking for `NULL` except in the fields the DB is expected to throw errors for, satisfies OpenBSDs security measures
* | Remove forgotten debug lineMichael Vetter2021-02-151-1/+0
| |
* | Bugfix: Titlebar show name without room nameStefan2021-02-141-1/+1
|/ | | | | | | Error log: GLib-CRITICAL - g_string_insert_len: assertion 'len == 0 || val != NULL' failed Check if a room name exists, before adding the name into the title bar.
* Correct command synopsis for mamMichael Vetter2021-02-091-1/+1
|
* Use correct time for MAM messagesMichael Vetter2021-02-041-8/+17
| | | | | | We need the delay value from the <forward> element. Regards https://github.com/profanity-im/profanity/issues/660
* Add /mam commandMichael Vetter2021-01-286-3/+38
| | | | Regards https://github.com/profanity-im/profanity/issues/660
* Enable error logging on MAM RSMMichael Vetter2021-01-281-4/+1
|
* Get MAM from last 7 daysMichael Vetter2021-01-281-1/+1
| | | | Probably should make this configurable later.
* MAM: Request more pages via RSMMichael Vetter2021-01-281-6/+22
| | | | Send another request with same jid and last id we got.
* Adapt MAM RSM code to latest functionsMichael Vetter2021-01-281-3/+3
| | | | | | Some functions changed in the meantime. stanza_get_child_by_name_and_ns() got dropped and xmpp_stanza_get_child_by_name_and_ns() from newer libstrophe is used.
* wip: add rsm after we get the first couple of mam messagesMichael Vetter2021-01-283-5/+46
|
* mam: Use correct ID in rsm handlerMichael Vetter2021-01-281-3/+1
| | | | Thanks to DebXWoody for the help.
* mam: fix logging messageMichael Vetter2021-01-281-1/+1
|
* Start working on MAM RSM to get more pagesMichael Vetter2021-01-282-1/+27
| | | | Regards https://github.com/profanity-im/profanity/issues/660
* Dont reload theme when disconnecting on purposeMichael Vetter2021-01-221-21/+0
| | | | | | | | I don't see why would need to. Also this only happens upon `/disconnect` not on a network outage or server related disconnect. Fixes https://github.com/profanity-im/profanity/issues/1472
* Simplify console notification codeMichael Vetter2021-01-211-29/+15
| | | | | | | Functions had some duplicate code: * cons_show_incoming_room_message() * cons_show_incoming_message() * cons_show_incoming_private_message()
* Fix old chlog reference in helpMichael Vetter2021-01-171-7/+7
| | | | Fixes https://github.com/profanity-im/profanity/issues/1470
* Update copyrightMichael Vetter2021-01-0833-35/+35
|
* Add `/executable (urlsave|urlopen)` migrationsWilliam Wennerström2020-12-183-10/+36
|
* Remove not needed includeMichael Vetter2020-12-161-1/+0
|
* Merge pull request #1459 from wstrm/issue-1359Michael Vetter2020-12-153-91/+57
|\ | | | | Restore old behavior when executing eval_password command
| * Do not inherit stdin of main processWilliam Wennerström2020-12-151-1/+1
| | | | | | | | I see no reason to inherit the stdin, so let's have it disabled.
| * Use popen for eval_password (reintroduce old behavior)William Wennerström2020-12-151-20/+35
| | | | | | | | | | Old commit that implemented the old behavior: bc9e6b79cdc246f7e97f6ddff7ea81474a698b05
| * Refactor call_externalWilliam Wennerström2020-12-113-91/+42
| |
* | Set input window size to max window sizekaffeekanne2020-12-111-2/+2
| | | | | | | | Input window size was one cell off, therefore terminal themes with background color set were rendered incorrectly, fixes #1458
* | Remove blank line after trackbarkaffeekanne2020-12-111-2/+0
| | | | | | | | Remove added blank line after trackbar, introduced by 606c1e51e688cb111b9837579a35460508324b63
* | Remove old TODOMichael Vetter2020-12-111-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | It was added in f7fe87dd4e7e14112fbcb0ae8794d90ffee64f2f when I rewrote window functions to include more infos (not just char* but whole jid struct I think). The same todo was added to win_print_outgoing_muc() but removed in f3d9de133e90ed10b5b7bd61196619eab1fedb19. This TODO should have been removed in f3d9de133e90ed10b5b7bd61196619eab1fedb19 since there we added the myjid parameter.
* | Fix color for win_print_outgoing()Michael Vetter2020-12-111-1/+1
|/ | | | | | | | | | | | | Discovered by @aba-hollerer. Mistake was introduced in b6b7dd5ad497a71e250b8b3cef0bb987314b141d probably due to a wrong copy/paste. First wasn't reproducible because I had `/receipts request on` and thus win_print_outgoing_receipts() is used which has the correct THEME_TEXT_ME. Fixes https://github.com/profanity-im/profanity/issues/1441
* Adapt profanity --help outputMichael Vetter2020-12-111-1/+1
|
* Only rotate logs if user didn't specify a log fileMichael Vetter2020-12-112-2/+8
|
* Remove log_reinit()Michael Vetter2020-12-112-15/+0
| | | | Not needed anymore.
* Shared log file needs a restartMichael Vetter2020-12-112-2/+2
| | | | Tell user about this change.
* Use whole path as logfile when defined via -fMichael Vetter2020-12-111-8/+14
| | | | | | | | | `profanity -f my` created ~/.local/share/profanity/logs/my.log`. It would be nicer if one could define the actual path, so one can choose another directory or even use /dev/null. Fixes https://github.com/profanity-im/profanity/issues/1442
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-14 20:25:16 +0000