about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Dont filter out own MUC messages if muc history is set to 'regular'Michael Vetter2020-02-213-5/+5
| | | | | | | | We use the same incoming function as for regular incoming text here. But don't want to filter out our own messages since we didn't print them during sending. Follow up to 8ee2cdadc88978ea26e6b6eb56f2aaa1fd5a81df
* Improve setting encryption char error handlingMichael Vetter2020-02-213-16/+27
|
* Expand omemo error messageMichael Vetter2020-02-211-2/+2
|
* pref: Use helper functions for setting/getting the encryption charMichael Vetter2020-02-211-38/+24
| | | | Dont duplicate code.
* win_print_incoming() strdup the charactarMichael Vetter2020-02-211-1/+1
| | | | | Fix bug introduced in 1f8b1eb740391941e79e1004ad041f8178a2b674. Forgot to strdup() here.
* Fix missing change from last commitMichael Vetter2020-02-201-1/+1
|
* Allow utf8 symbols as omemo/pgp/otr indicator charMichael Vetter2020-02-2020-620/+641
| | | | Fix https://github.com/profanity-im/profanity/issues/1264
* Fix theme setting correction charMichael Vetter2020-02-201-1/+1
| | | | Copy paste error. We actually set the omemo char..
* Parse mentions and triggers in muc history if display is 'regular'Michael Vetter2020-02-204-22/+30
| | | | Fix https://github.com/profanity-im/profanity/issues/1261
* Put getting mentions in own functionMichael Vetter2020-02-203-10/+17
| | | | | | So we can use it somewhere else too. Regards https://github.com/profanity-im/profanity/issues/1261
* Add option to color MUC history like regular messagesMichael Vetter2020-02-207-17/+72
| | | | | | | | | `/logging group color` has: * `unanimous` which will color it with one unanimous color. Like it was done always. * `regular` which colors it like regular incoming messages. Regards https://github.com/profanity-im/profanity/issues/1261
* Refactor mucwin_history()Michael Vetter2020-02-193-8/+9
| | | | Just pass ProfMessage.
* Add define names to commentMichael Vetter2020-02-192-7/+6
|
* Merge pull request #1269 from wstrm/add-sr.ht-ciMichael Vetter2020-02-171-2/+1
|\ | | | | Add builds.sr.ht CI for OpenBSD
| * Add builds.sr.ht CI for OpenBSDWilliam Wennerström2020-02-171-2/+1
| | | | | | | | | | | | | | | | * Add .builds/openbsd.yml for builds.sr.ht * Update travis-build.sh -> ci-build.sh with OpenBSD case * Fix libdl check in configure.ac (OpenBSD has libdl built-in) * Fix some minor issues found when compiling on OpenBSD with GCC (e.g. uninitialized variables)
* | omemo: switch to 12 byte IVMichael Vetter2020-02-171-1/+1
| | | | | | | | | | | | | | We decrypt both 12 and 16 bytes. And send 12 instead of 16 bytes now. Close https://github.com/profanity-im/profanity/issues/1272
* | Refactor win_print_history()Michael Vetter2020-02-174-14/+6
| | | | | | | | We never use the printf like behaviour anyways.
* | Refactor win_print_outgoing_muc_msg()Michael Vetter2020-02-173-15/+7
| | | | | | | | We never use the printf like behaviour anyways.
* | Refactor win_println_incoming_muc_msg()Michael Vetter2020-02-173-15/+7
| | | | | | | | We never use the printf like behaviour anyways.
* | Refactor win_print_outgoing()Michael Vetter2020-02-174-19/+10
| | | | | | | | We never use the printf like behaviour anyways.
* | Fix typoMichael Vetter2020-02-171-1/+1
| |
* | Mention how to enable unencrypted file transerMichael Vetter2020-02-171-2/+2
| | | | | | | | Regards https://github.com/profanity-im/profanity/pull/1270
* | Make /sendfile in PGP session configurableMichael Vetter2020-02-176-3/+33
| | | | | | | | | | | | `/pgp sendfile on` allows unencrypted file transfer in an PGP session. Regards https://github.com/profanity-im/profanity/pull/1270
* | Make /sendfile in OTR session configurableMichael Vetter2020-02-177-6/+47
| | | | | | | | | | | | `/otr sendfile on` allows unencrypted file transfer in an OMEMO session. Regards https://github.com/profanity-im/profanity/pull/1270
* | Make /sendfile in OMEMO session configurableMichael Vetter2020-02-177-10/+54
| | | | | | | | | | | | | | `/omemo sendfile on` allows unencrypted file transfer in an OMEMO session. Regards https://github.com/profanity-im/profanity/pull/1270
* | Disallow sendfile in e2ee chat sessionsmoppman2020-02-171-0/+35
|/
* Add workaround for compiler warningMichael Vetter2020-02-141-1/+1
| | | | Regards https://github.com/profanity-im/profanity/issues/1265
* xep-0308: Add note about tab completionMichael Vetter2020-02-141-1/+2
|
* xep-0308: add note about where corrections are possibleMichael Vetter2020-02-141-1/+2
|
* xep-0308: only allow /correct when corrections are enabledMichael Vetter2020-02-141-0/+5
|
* xep-0308: add caution noteMichael Vetter2020-02-141-1/+1
| | | | | We need to change the buffer structure first, so that we save the from field there.
* Rename buffer->from to buffer->display_fromMichael Vetter2020-02-143-10/+12
|
* xep-0308: enable for carbon copied messagesMichael Vetter2020-02-142-1/+15
| | | | | | | If we are connected with another client and send a message, then correct it. We now display it correctly in Profanity. Id wasn't saved for carbon copied messages too so far.
* xep-0308: enable correction in outgoing messages with delivery receiptsMichael Vetter2020-02-143-8/+10
|
* Always send delivery receipts if enabledMichael Vetter2020-02-141-14/+1
| | | | | | | | | | | | | So far receipts are only send if we have enabled it and the other client supports it. But it could be that the other person is connected with several clients. One supporting it and the other which doesn't. If the not supporting one is active and we send to a fulljid, then we won't get receipts. Probably it's best to just always send them if they are enabled in Profanity. And not try to find out the capabilities of the other client. Fix https://github.com/profanity-im/profanity/issues/1268
* Rename win_print_with_receipt() -> win_print_outgoing_with_receipt()Michael Vetter2020-02-143-4/+4
|
* Add myself to copyrightMichael Vetter2020-02-144-0/+4
|
* Rename `win_println_them_message()` -> `win_println_incoming_muc_msg()`Michael Vetter2020-02-143-3/+3
| | | | | | | | In aa3693daa211b36c78d136d5a1ee9f3258e21352 I renamed `win_println_me_message()` -> `win_print_outgoing_muc_msg()`. Now: `win_println_them_message()` -> `win_println_incoming_muc_msg()` to be more consistent and descriptive.
* Fix testsMichael Vetter2020-02-141-7/+7
|
* xep-0308: remove replace_id from privwin signatureMichael Vetter2020-02-143-4/+4
| | | | No `/correct` allowed in privwins
* xep-0308: only replace messages if the user enabled the featureMichael Vetter2020-02-141-3/+3
| | | | Outgoing `/correct` will still work.
* xep-0308: Make /correct work without quotation marksMichael Vetter2020-02-144-11/+14
| | | | | | Now we can specify an unlimited amount of arguments for commands. Maybe this is also helpful for other commands that use quotation marks so far.
* xep-0308: Fix sending corrections for multiple wordsMichael Vetter2020-02-143-4/+7
|
* xep-0308: Add autocompletion of last message for /correctMichael Vetter2020-02-141-4/+29
|
* xep-0308: Implement LMC for outgoing MUC messagesMichael Vetter2020-02-1410-17/+71
| | | | | | Including OMEMO encrypted ones. Also rename `win_println_me_message()` to `win_print_outgoing_muc_msg() as I think it's a more descriptive name.
* Rename MUC PM handlerMichael Vetter2020-02-141-3/+3
| | | | | Rename from _private_chat_handler() to _handle_muc_private_message() to be more consistent with other handler names.
* xep-0308: Dont allow to correct MUC PMsMichael Vetter2020-02-143-10/+0
| | | | | People could change messages of other people if the nick isn't registered.
* xep-0308: correct incoming MUC PMsMichael Vetter2020-02-121-0/+14
|
* xep-0308: Display corrected incoming MUC messages correctlyMichael Vetter2020-02-124-5/+21
|
* xep-0308: Don't check whether receiving clients supports this featureMichael Vetter2020-02-121-16/+1
| | | | | | | | | | | | | | | | | | | | | | | | | XEP-0308 Version 1.1.0 (2019-05-15) states "It is expected that clients will not send message corrections to clients that do not support them, as non-supporting clients will render these as duplicate (corrected) messages" ``` 10:12:47 - jubalh: Do clients actually check whether other clients support xep0308 (LMC) before sending? 10:13:13 - pep.: not poezio, and I doubt anybody does. it's the "but carbons/MAM" argument 10:13:49 - jubalh: Profanity doesnt support this yet. So I always get the message twice. One time the message, and then the corrected ones. And I think that's right. But I understood xep0308 correctly it sais a client shouldnt sent a message with 'replace' if the client doesnt support it? I don't see why 10:14:50 - Ge0rG: jubalh: because you might also use Conversations and read the backlog from MAM on conversations 10:15:51 - jubalh: Ge0rG: sorry? 10:16:36 - Ge0rG: jubalh: when I'm sending you a message, I don't know which client you'll use to read it. So it doesn't make sense to limit the features I use 10:27:57 - jubalh: Yes. That's why I'm confused by thestatement in the XEP 10:28:13 - jubalh: "It is expected that clients will not send message corrections to clients that do not support them, as non-supporting clients will render these as duplicate (corrected) messages. " 10:28:37 - Holger: Yes, you're both saying the same thing. And yes I agree, that part of the XEP is nonsense. We have that "check whether the peer's client supports it" stuff in various XEPs that depend on recipient's features and it never makes sense as it doesn't cope with multi-device, MAM, groupchat. 10:28:53 - jubalh: First: You don't know if he is connected with several clients. Some supporting it and some not. Second: Why not just resend the new corrected message? Then he has both messages and no information is lost. If he only gets the first one information is lost 10:29:20 - jubalh: Okay 10:29:30 - jubalh: Then I won't implement it this way. Thanks guys! 10:29:34 - Holger: Well UX is a bit meh if the recipient doesn't support it (I'm an MCabber user and know what I'm talking about) but I see no better solution, yes. ``` So it makes more sense to just always send it. Non supporting clients will then get the message and the corrected message. So they get it "twice". Which is the right thing to do in my opinion.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-08-04 13:17:50 +0000