| Commit message (Collapse) | Author | Age | Lines |
|\ |
|
| |
| |
| |
| |
| | |
Most of the time that error meant a confusion on bitlbee's side, often a
server for which we sent a join request and never got a reply for.
|
| |
| |
| |
| | |
Holy crap this login method is *bad*
|
| |
| |
| |
| |
| |
| | |
Requires libpurple 2.12.0
Mostly relevant recently with slack-libpurple.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
RIP
This plugin relied on the skype linux client, which doesn't work
anymore. During login it just does exit(0) for mysterious reasons.
I guess that's the server trying to say that it's not supported.
This is officially dead now after a few years of kinda-almost-working.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
RIP
As per http://ismsndeadyet.com/ all versions up to MSNP22 died a few
months ago. We had a MSNP21 implementation, bought us two extra years.
Implementing MSNP24 is technically possible but also pointless given
skypeweb, and the authentication requires some fairly messed up crypto
and legacy old-skype-protocol servers. For a long time I tried to
reverse a potentially simpler method, and got fairly close, but never
completed that. I haven't done any attempts to continue it in the last
year, so I'm fine with giving up at this point.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is the presence needed to finalize a join to the channel, the
'from' field is our own user in the context of that channel:
<presence to="dx@server/resource" from="channel@gateway.server/dx">
<x xmlns="http://jabber.org/protocol/muc#user">
<status code="110"/>
<item jid="~dx@198.51.100.1" affiliation="none" role="participant"/>
</x>
</presence>
Bitlbee takes the stuff to <item jid="..."> as the "real" jid, as it
does for non-anonymous MUCs. It sets that to ext_jid, and uses it as the
handle internally.
In this particular case, that real jid is nonsense for us, so
imcb_chat_add_buddy() interprets that as yet another person joining the
channel, instead of the expected self-join.
This fixes it by checking if the buddy is our own user, and ignoring the
provided ext_jid in those cases.
Thanks to ivucica for reporting this, who was using Biboumi (a gateway
from XMPP to IRC)
|
| |
| |
| |
| | |
Add MUC buddies before applying nick changes
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
Silence the following compiler warning: format specifies type
'unsigned long long' but the argument has type 'guint64'. When
formatting a json_integer, use PRId64 for int64_t. When formatting
ordinary integers, use G_GUINT64_FORMAT for guint64.
|
| |
| |
| |
| | |
Noisy but often important
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In other words, "account jabber set away Message" resulted in away
status being set, but not "Message".
Fixes trac ticket 1291
This was broken by ac68733ad7a5127395d6367b655a2d9de5d911b5 (3.4.2)
That commit added another call of imc_away_state_find() with the fixed
string "away", so purple protocols can become away by setting away to
any string. But by doing so, it wiped the status message because it's
the same as the name of the away state.
|
|\| |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
Defaults to disabled to maintain the status quo.
|
| | |
|
|\| |
|
| |
| |
| |
| |
| | |
Followup to 701ab81 (included in 3.5) which was a partial fix which only
improved things for non-libpurple file transfers (that is, just jabber)
|
|\| |
|
| |
| |
| |
| |
| |
| | |
That is, flagged with PURPLE_MESSAGE_DELAYED. Those are safe to display.
This is similar to what adium does. Thanks EionRobb for the idea.
|
| |
| |
| |
| | |
Accidentally broke it in d57484d (from last week)
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
This constant is always available and meant to be used with
getnameinfo().
This fixes the build on Debian GNU/kFreeBSD.
|
| |
| |
| |
| | |
Credit for the idea goes to russian XMPP spammers. Thanks!
|
|\| |
|
| |
| |
| |
| |
| | |
This one was caught by the debian build scripts in travis. I had
format-security in my local cflags, not format-string. Welp.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds channel settings prefixed by purple_. For example jabber now
has purple_room and purple_server which are decomposed variants of our
own 'room' setting. Okay, that doesn't sound very useful.
It also adds some sync from the values returned by chat_info_defaults()
- so if the plugin figures something out in there, we save it in our
own settings.
In the case of SIPE this adds a new setting, purple_uri, which can be
set with the ma-chan:// uri for a persistent chat.
This solves the issue with the SIPE plugin only knowing how to do name
lookups after doing 'chat list' - now it just needs to work once, and we
save the real URI in our settings.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Just comparing the body of the last sent message. This isn't foolproof
and sending several messages quickly can make it fail, but it's less
annoying than before. The correct solution is still to fix the server.
In the case of slack I still recommend using the irc gateway instead.
|
| |
| |
| |
| |
| |
| | |
Because crashing asserts are bad, and maybe this helps fix the
captures_build_path issue with debian's reproducible builds
(those asserts probably include __FILE__)
|
| |
| |
| |
| | |
Nothing interesting.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The whitelist includes hangouts, funyahoo and icq.
These plugins tend to have numeric or meaningless usernames. With this
change, users don't have to do 'ac whatever set nick_format %full_name'
anymore. Just sugar.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
warn_unused_result on write() is particularly annoying. You can't just
add (void) to ignore it due to gcc bug 66425.
I replaced some of those with fwrite() and used a variable marked with
the G_GNUC_UNUSED attribute for the writes from signal handlers.
|
| |
| |
| |
| |
| |
| |
| | |
The room names in 'chat list' were missing the server part.
Jabber is the only prpl which implements this method as far as I can
see, and it's needed to get the full name.
|
|\| |
|
| | |
|
| |
| |
| |
| |
| | |
Some structs still have xml in their name but meh, at least that's not
visible to the user.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Turns out he already implemented pretty much the same thing in the
parson branch... last year.
The differences between the two approaches are subtle (there aren't too
many ways to do this, some lines are the exact same thing) but I decided
I like his version better, so this mostly reverts a handful of my
changes while keeping others. The main advantage of his approach is that
no fake protocols are registered, no actual prpl functions are called,
and the missing prpl is a singleton constant.
New things compared to the implementation in the other branch:
- The explain_unknown_protocol() function.
- Fixed named chatrooms throwing a warning and losing the "account"
setting when saving. See changes in irc_im.c
- Fixed the "server" setting dropping when saving. See account.c
Differences with my previous implementation:
- Accounts with missing protocols don't autoconnect
- 'account list' marks them as "(missing!)"
|
|\| |
|
| |
| |
| |
| | |
Which is -Werror'd in debian builds
|
| | |
|