| Commit message (Collapse) | Author | Age | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 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.
|
|
|
|
|
|
| |
from other BitlBees won't be picked up accidentally. Might also want to
randomize the per-packet IDs because they're still predictable.
|
|
|
|
|
| |
I ever need SHA256 ;-)).
|
|
|
|
|
| |
that list. And adding some const stuff in the xmltree functions.
|
|
|
|
|
|
| |
work. This also solves the issue of underscores appearing and disappearing
in their nicknames when people leave/join a chat.
|
|
|
|
|
| |
nickname generation. IM fullnames and IRC nicknames are just *different*.
|
|
|
|
|
|
|
|
| |
nicknames for chatroom participants. There'll probably be a lot of
underscores now, but this is by far the cleanest way to implement this, I
think. At least now whispers will work properly. Also using this function
call to set names for ICQ contacts in a slightly saner way.
|
|
|
|
|
|
|
|
|
| |
callback, it's only called from inside IM-modules. This makes sure a buddy
only gets added to the BitlBee structures if the add was successful. This
gets rid of the weirdness described in #55. Unfortunately for now this
change breaks A) automatic renaming of ICQ contacts (if there are names
stored in the contact list) B) add -tmp.
|
|
|
|
|
|
|
| |
one isn't implemented yet, but I'll do that later.) At last I got rid of
the hack called get_status_string(). And now Yahoo seems to mess up away
messages...
|
|
|
|
|
|
| |
little bit, grouping things by category instead of original Gaim 0.58
filename.
|
|
|
|
|
| |
it's in acc too. wants_to_die is now an argument to imc_logout().
|
| |
|
|
|
|
|
|
|
|
| |
do_error_dialog() and (set|hide)_login_progress(_error)?() with things
that hopefully make more sense.
Although it's still not really great...
|
|
|
|
|
|
| |
will come tomorrow. It compiles, I'll leave the real testing up to someone
else. ;-)
|
|
|
|
|
|
|
|
| |
GLib for giving this very useful "s2 != NULL assertion failed" message
instead of just dereferencing the damn pointer so I can find a backtrace,
this sure makes debugging very easy, guys! Wasn't GLib supposed to SAVE
time?
|
| |
|
|
|
|
|
|
| |
stay synchronized with other clients logged into your account at the same
time.
|
|
|
|
|
|
| |
makes it easier to find out if an event handler has to be called for a
reply packet.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
login, and now sending proper error responses to IQ packets we can't
handle.
|
| |
|
|
|
|
|
| |
mess in iq.c!
|
|
|
|
|
|
|
| |
event handlers that can be set when sending a packet to handle the reply
to this specific packet. This should allow me to make the iq handler a
lot cleaner.
|
|
|
|
|
|
|
| |
by any client I know of. Also, they're already working on a (probably
completely incompatible) standard: JEP-191. Maybe BitlBee will implement
it too some day...
|
| |
|
|
|
|
|
| |
connecting to Google Talk.
|
| |
|
|
|
|
|
| |
to work perfectly though.
|
|
|
|
|
| |
got rid of the double <presence> tag sent because of presence_announce().
|
|
|
|
|
| |
properly working SASL authentication (although only PLAIN so far).
|
|
|
|
|
|
|
| |
against write()ing to sockets that are closed already, hopefully sane
detection for SASL support, and only sending type=unavailable presence
tag to logged in sessions.
|
| |
|
| |
|
| |
|
|
|