| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
| |
Fixes trac ticket 995 https://bugs.bitlbee.org/bitlbee/ticket/995
This is slightly pointless for the suggested use case (tor), since with
socks5 we already send a hostname instead of an IP address.
Either way, it was easy to implement, so I hope it helps.
|
|
|
|
|
| |
- GMail notifications stuff is now just 'mail_notifications'
- sed -i s/notify_handle/mail_notifications_handle/
|
|
|
|
|
|
|
| |
Saves some messing with g_strdup_printf for the callers, and
flags/sent_at weren't used anyway.
Also check if the mail_notifications setting is enabled
|
| |
|
|
|
|
|
| |
Purple just doesn't work with daemon mode anyway, but it's better to
show the intended error message than to crash while showing it.
|
|
|
|
|
|
|
| |
- Added support for PURPLE_REQUEST_INPUT
- Changed memory management to do the free() of data through
purple_request_close(), letting purple know that the request was
answered, and fixing use-after-free issues with it
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes trac bug 1190 ("Accepting SSL certs too late resets bitlbee-libpurple")
To reproduce:
1. Connect to server with self-signed ssl certificate (downgrading to
libpurple 2.10.9 might be required to actually get the request)
2. Disconnect the account
3. Type "yes"
4. Acquire segfault.
Normally, query_del_by_conn() would handle this, but some requests have
no account context at all. Yeah, it sucks. This is how pidgin handles it.
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 5ff46180e5378acd6d103d9314175c78530bda7e.
Turns out that libpurple really doesn't provide any context at all for
some queries.
Also, not going to say "Shouldn't affect anything" again. I'm getting
good at writing code that looks good, but actually breaks stuff.
That's not good. At all.
|
| |
|
|
|
|
|
| |
Shouldn't affect anything, and still doesn't allow initializing
libpurple more than once, but whatever.
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes warnings about passing signed chars to them (apparently they
are implemented as macros that do array lookups without checks in some
platforms, yay)
Specifically:
functions=isalnum|isalpha|isdigit|isspace|isxdigit|tolower|toupper
sed -ir "s/$functions/g_ascii_&/g" **/*.c
|
|
|
|
|
|
|
| |
my copyright mentions since some were getting pretty stale. Left files not
touched since before 2012 alone so that this change doesn't touch almost
EVERY source file.
|
| |
|
|
|
|
|
| |
unexpectedly being set to something already.
|
|
|
|
|
|
|
| |
This in response to #898. I could also try to make each split a separate
setting but that'd make the Jabber module very ugly for example, requiring
the user to split up his/her JID. Let's hope people read this help info..
|
|
|
|
|
| |
Mostly an attempt to explain what's up with #898.
|
|
|
|
|
|
| |
don't even know what's the difference, but this fixes Facebook nicks when
using libpurple.
|
|
|
|
|
|
| |
add new irc_usermsg, irc_usernotice.
deliver user-specific messages from libotr as notices to that user.
|
|
|
|
|
| |
libpurple versions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
doesn't have Twitter support by default and it's unlikely that someone will
prefer libpurple-twitter over BitlBee's Twitter code anyway.
Also automatically disable libpurple protocol modules if a native variant is
already set up. The linking conflict works the other way around (libpurple
modules may break if native modules for the same protocol are compiled in)
so this should mostly resolve the linking conflict problem.
|
|
|
|
|
| |
#679. Patch from "rover.orna".
|
|
|
|
|
| |
using /tmp so far but this wasn't a good idea. Try to use something saner.
|
|
|
|
|
|
|
|
|
|
| |
files, this finally gives proper dependencies, which means the end of
getting broken binaries around headerfile changes, etc.
Sure, this may not work on obscurux with superawesomeincompatiblecc while
autoconf does, but at least BitlBee's configure script still runs in <1s.
:-)
|
| |
|
|
|
|
|
| |
with contacts in multiple groups.
|
|
|
|
|
|
|
| |
a contact is in multiple groups, for now I'm not supporting it.
Also cleaning up query code to avoid calling NULL.
|
| |
|
| |
|
|
|
|
|
| |
would otherwise be a digit.
|
|
|
|
|
|
|
| |
the "struct irc" containing all data belonging to a session. Sanitise
memory management a little bit here. (There are some memory leaks in here
too that need to be fixed at some point.)
|
| |
|
| |
|
|
|
|
|
|
| |
build files in there. I need this to properly make Debian package variants
(i.e. libpurple and native).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
the file in it; protocol modules are mostly hardcoded to use the filename
from the filesystem with no way to override this.
Also improved robustness a little bit.
|
|
|
|
|
|
|
|
| |
for numerous reasons. Maybe libpurple 2.7.0 is less crappy and will
eventually allow (working) direct ft's again.
This somewhat works, but filename info is lost with some protocols.
|
|
|
|
|
| |
probably, not sure what sets the wants_to_die flag).
|
|
|
|
|
| |
beginning of the download already to make sure it doesn't stick around.
|
|
|
|
|
| |
serv_chat_invite() instead.
|