| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds an OPT_SELFMESSAGE flag that can be passed to imcb_buddy_msg()
or imcb_chat_msg() to indicate that the protocol knows that the message
being sent is a self message.
This needs to be explicit since the old behavior is to silently drop
these messages, which also removed server echoes.
This commit doesn't break API/ABI, the flags parameters that were added
are all internal (between protocols and UI code)
On the irc protocol side, the situation isn't very nice, since some
clients put these messages in the wrong window. Irssi, hexchat and mirc
get this wrong. Irssi 0.8.18 has a fix for it, and the others have
scripts to patch it.
But meanwhile, there's a "self_messages" global setting that lets users
disable this, or get them as normal messages / notices with a "->"
prefix, which loosely imitates the workaround used by the ZNC
"privmsg_prefix" module.
|
|
|
|
|
| |
Mostly no-op for now. Puts registration on hold, supports the basic
commands, and NAKs everything
|
|
|
|
|
|
| |
Because many other ircds do that.
(But actually mostly because @SaberUK said so)
|
|
|
|
|
|
|
|
|
|
|
| |
- Show version as part of the initial message of &bitlbee
- Use g_strerror() to show actual errors when saving xml configs
- Only show "The nick is (probably) not registered" for ENOENT, use
g_strerror() for the rest of OS errors when loading xml configs
- Show "Protocol not found: <name>" when find_protocol() returns null,
useful when the user uninstalls a plugin accidentally.
- Suggest the user to check the system clock when getting error 401 from
the twitter stream (other REST endpoints show a better error message)
|
|
|
|
|
|
|
| |
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 allows for users to be declared as being special, which does not
have any specific meaning. The meaning of being special is different
from protocol-to-protocol, which many protocols do not even implement.
This functionality is mainly geared towards a special user state which
only some protocols may actually need to define. For example, with the
third-party Steam plugin, this can be used for denoting a user which is
actively playing a game.
By default, this mode will not actually be used by any plugin. However,
it does default to the half-operator user mode.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This might look like a simple diff, but those 'lies' made this not very
straightforward.
The NSS bug itself is simple: NSS detects a fork happened after the
initialization, and refuses to work because shared CSPRNG state is bad.
The bug has been around for long time. I've been aware of it for 5
months, which says something about this mess. Trac link:
http://bugs.bitlbee.org/bitlbee/ticket/785
This wasn't a big deal because the main users of NSS (redhat) already
applied a different patch in their packages that workarounded the issue
somewhat accidentally. And this is the ticket for the 'lies' in unix.c:
http://bugs.bitlbee.org/bitlbee/ticket/1159
Basically a conflict with libotr that doesn't happen anymore. Read that
ticket for details on why ignoring those comments is acceptable.
Anyway: yay!
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
for reasons not entirely clear to me. Instead of suppressing a PING to the
client if we're still waiting for a response to a previous one, just keep
sending them. One PONG will be enough to stay connected but that's okay.
|
|
|
|
|
|
| |
add new irc_usermsg, irc_usernotice.
deliver user-specific messages from libotr as notices to that user.
|
| |
|
|
|
|
|
| |
really empty). Bug #657 and confusing BitlBee users since probably 2002.
|
|
|
|
|
| |
accounts. Fixed now.
|
| |
|
|
|
|
|
|
| |
using libpurple). This was leaking memory and indirectly caused the bug
fixed by the previous revision.
|
|\
| |
| |
| |
| |
| | |
Not 100% sure about the OpenSSL merge, should double check that but I'm
currently offline.
|
| |
| |
| |
| |
| | |
into the executable.
|
| | |
|
|/
|
|
|
| |
sense of the word, more in a way that core files don't have to include otr.h.
|
|
|
|
|
|
|
| |
was only meant to ease migration, people are now complaining that
"set show_offline off" doesn't work. Make this work, but at the same time
start hiding these two options to discourage people from using them.
|
|
|
|
|
|
|
|
|
|
| |
BitlBee used by a user, and if it looks like s/he hasn't used this one
before, show a list of new features that may be interesting.
Since I don't think im.bitlbee.org users will read any changelogs ever,
this is probably not a bad idea. If you hate it, the following command
should get rid of it forever: set last_version 9999999
|
| |
|
|
|
|
|
|
|
| |
line (if stdin is a TTY). This hopefully answers a FAQ. Also moved stuff
around in README a little bit, daemon mode should be described before
obsolete inetd stuff.
|
|
|
|
|
| |
the last_channel variable, like for any other user.
|
| |
|
|
|
|
|
| |
documentation.
|
|
|
|
|
| |
once.
|
| |
|
| |
|
|
|
|
|
| |
connection a quit message instead of just breaking the connection.
|
|
|
|
|
| |
groupchats not reimplemented yet but that's the next step.
|
|
|
|
|
|
| |
old-style BitlBee. This so that the IRC client will show the notification
in query windows as well. Make it a setting though, for bug #539.
|
|
|
|
|
|
|
| |
in response to PRIVMSG if one was sent recently - some IRC clients including
irssi don't do this very well (when talking to >1 people who are away for
example).
|
| |
|
|
|
|
|
| |
now. Getting *very* close to "feature parity" now!
|
| |
|
|
|
|
|
| |
s/he joins.
|
| |
|
|\ |
|
| |\ |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
changes that happened since 1.2.4.
|
| |\| | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
mainline). Once I add ft support glue to protocols/purple/ I guess this will
all go into killerbee.
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
modules.
|
| |\ \ \ \ \ |
|
| |\ \ \ \ \ \ |
|