| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Used uncrustify, with the configuration file in ./doc/uncrustify.cfg
Commit author set to "Indent <please@skip.me>" so that it's easier to
skip while doing git blame.
|
| |
|
|
|
| |
- http_incoming_data calling itself
- jabber_bs_free_transfer calling jabber_si_free_transfer
|
| |
|
|
|
|
| |
callback fails, we shouldn't try to continue the ft and dereference the NULL
ptr it returned.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Some hooks are missing so sending files doesn't work yet. Receiving also
still seems to have some issues. On the plus side, at least the MSN/Jabber
modules work again.
|
| | |
|
| | |
|
| |
|
|
|
| |
fixing another potential NULL pointer dereference.
|
| |
|
|
|
| |
"transfer" since all root commands are singular so far.
|
| | |
|
| |
|
|
|
|
| |
* both ends (proto&dcc) need to finish a transfer now for it to be finished
* moved throughput calc. and some messages to dcc (no need to implement in protocols)
|
| |
|
|
|
|
|
|
|
|
| |
Note that this is only used for sending. The default <local>;<auto> means let
the receiver try a direct connection first and then the proxy discovered from
the server (if any). If you know you're firewalled you can remove the <local>.
If you want to provide your own proxy try something like
"<local>;JID,HOST,PORT". E.g.
"<local>;proxy.somewhere.org,123.123.123.123,7777".
|
| |
|
|
|
|
| |
* not only query but also respect peer's features (i.e. abort ft if an important feature is not advertised)
* wait for proxy discovery to complete before starting the transfer (important for sending to people with auto accept)
|
| | |
|
| | |
|
| |
|
|
| |
for this!
|
| | |
|
| | |
|
| |
|
|
|
| |
only one buffer of 2k per transfer now.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* move from out_of_data to is_writable, eliminate buffers
* implement "transfers reject [id]"
* documentation in commands.xml
* implement throughput and cummulative throughput boundaries
* feature discovery before sending
* implement sending over a proxy
(proxy discovery, socks5 client handshake for sending, activate message)
* integrate toxik-mek-ft
|
|
|
only a few changes to bitlbees code, mainly the addition of the "transfers"
command.
This is known to work with Kopete, Psi, and Pidgin (formerly known as gaim).
At least with Pidgin also over a proxy. DCC has only been tested with irssi.
IPV6 is untested but should work.
Currently, only receiving via SOCKS5BYTESREAMS is implemented. I'm not sure if
the alternative(in-band bytestreams IBB) is worth implementing since I didn't
see a client yet that can do it. Additionally, it is probably very slow and
needs support by the server as well.
|
