gajim merge requestshttps://dev.gajim.org/gajim/gajim/-/merge_requests2022-09-28T20:44:11Zhttps://dev.gajim.org/gajim/gajim/-/merge_requests/588WIP: HTTPUpload: Filename obfuscation feature2022-09-28T20:44:11ZRaleighWIP: HTTPUpload: Filename obfuscation featureInstead of sending the actual filename to the server, user can choose to send a SHA1 hash. This can be useful when you use encryption and don't want to leak the filenames.Instead of sending the actual filename to the server, user can choose to send a SHA1 hash. This can be useful when you use encryption and don't want to leak the filenames.https://dev.gajim.org/gajim/gajim/-/merge_requests/758Add an info message if some of the paths are skipped during a drag&drop.2021-11-29T21:58:52ZMarcin MielniczukAdd an info message if some of the paths are skipped during a drag&drop.Related to #10544Related to #10544https://dev.gajim.org/gajim/gajim/-/merge_requests/863change: Add FileTransferSelector as a central page for sending files2022-11-24T22:34:54ZDaniel Brötzmannchange: Add FileTransferSelector as a central page for sending filesThis MR introduces a new `FileTransferSelector` page within the ChatFunctionPage.
This new page gets opened whenever a file transfer action is invoked by the user:
* click on 'Send File' button
* click on 'Send File Directly / Upload F...This MR introduces a new `FileTransferSelector` page within the ChatFunctionPage.
This new page gets opened whenever a file transfer action is invoked by the user:
* click on 'Send File' button
* click on 'Send File Directly / Upload File' in the chat menu
* drag and drop
* pasting image from clipboard
Files will be previewed in a list, and further files can be added there via file selector or drag and drop.
A suitable transfer method will be chosen, if the user's preferred method can't be used. The `FileTransferSelector` makes use of the `ResourceSelector` widget, if Jingle is chosen as transfer method.
Fixes #9511
![image](/uploads/a18361fdbce38bc8351b6f7721702e78/image.png)https://dev.gajim.org/gajim/gajim/-/merge_requests/866Draft: imprv: Disable Jingle file transfer action if chat is encrypted2022-11-24T20:52:17ZDaniel BrötzmannDraft: imprv: Disable Jingle file transfer action if chat is encryptedThis avoids accidentally sending files unencrypted when using Jingle.
Jingle Encrypted Transfer (JET) is the long term solution for this, see gajim/gajim-plugins#481This avoids accidentally sending files unencrypted when using Jingle.
Jingle Encrypted Transfer (JET) is the long term solution for this, see gajim/gajim-plugins#481https://dev.gajim.org/gajim/gajim/-/merge_requests/869change: Jingle: Remove XTLS support2022-11-26T12:30:20ZDaniel Brötzmannchange: Jingle: Remove XTLS supportXTLS has never been standardized, see https://datatracker.ietf.org/doc/html/draft-meyer-xmpp-e2e-encryption
Gajim used this for file transfers, but there probably was no other client supporting this now obsolete feature.
Today, using XEP...XTLS has never been standardized, see https://datatracker.ietf.org/doc/html/draft-meyer-xmpp-e2e-encryption
Gajim used this for file transfers, but there probably was no other client supporting this now obsolete feature.
Today, using XEP-0396: Jingle Encrypted Transports - OMEMO would be the preferred solution.
Part of #11160https://dev.gajim.org/gajim/gajim/-/merge_requests/942draft: perf: Save pasted images asynchronously2023-05-27T11:01:55ZDaniel Brötzmanndraft: perf: Save pasted images asynchronouslyFixes #11489Fixes #11489https://dev.gajim.org/gajim/gajim/-/merge_requests/945perf: File transfer: Don't re-compress pasted PNG images2023-05-27T11:01:55Zmjkperf: File transfer: Don't re-compress pasted PNG imagesNote that this has subtle privacy implications: PNG file data supplied by the
source application is sent as-is, including possible metadata, while the user
might reasonably assume that only raw pixels are being pasted into Gajim.
This i...Note that this has subtle privacy implications: PNG file data supplied by the
source application is sent as-is, including possible metadata, while the user
might reasonably assume that only raw pixels are being pasted into Gajim.
This is basically "!942 Lite". It doesn't attempt to do anything with GUI, just optimizes away redundant stuff, making #11489 considerably less serious. There's still a silent delay if the source application takes its time to produce the data, like Firefox does with large (dimensions-wise) images. I think some serious refactoring is needed to alleviate that. Namely, the file transfer dialog needs to be able to receive rich Python objects instead of file URI strings, and likely *not* using the glib action ABI foos.
Tested pasting from Firefox & Chromium (using [this](https://www.learningcontainer.com/wp-content/uploads/2020/07/Large-Sample-Image-download-for-Testing.jpg) image) and also LXQt's ScreenGrab.