| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Co-authored-by: Marvin W <git@larma.de>
|
| | |
|
| |
|
|
|
| |
fixes #179
fixes #812
|
| | |
|
| |
|
|
|
|
| |
Instances of `RegexError` are just asserted as `assert_not_reached` as
they cannot really fail except for allocation failure if the given regex
is valid.
|
| | |
|
| |
|
|
|
|
|
| |
The Jingle file transfer (XEP-0234) specifies that the receiver of the
file transfer is the one to terminate the session. Otherwise, there
might be a race condition between the XMPP stream and out-of-band SOCKS5
connections.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This means that we no longer rely on the remote end to close the
connection after sending the file, but additionally use the `<size>`
element from the initial file transfer `<description>` to check whether
the file transfer has been completed.
This was motivated by Conversations not closing the connection for
SOCKS5 file transfers.
|
| | |
|
| | |
|
| |
|
|
|
| |
This currently follows the same rules as HTTP file download for
accepting files.
|
|
|
This is still disabled by default until prioritization is implemented;
otherwise this could be preferred to HTTP uploads.
File sending only works via Jingle In-Band-Bytestreams right now, more
transports are going to be implemented.
To test this, uncomment the line with `JingleFileTransfer` in
libdino/src/application.vala.
|
