-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bitlbee support? #115
Comments
I have not tried it myself, but as far as I understand the plugin won't even load because of reasons not related to the plugin itself, but because of how Bitlbee handles libpurple plugins in general. |
I believe @dequis was planning what needed to be changed in bitlbee to load non-prpl plugins, but that hasn't happened yet |
What's the status on this? It would be really nice to be able to use this with bitlbee. :) |
@Hund so the trouble is that bitlbee doesn't have any way of loading libpurple plugins, only libpurple protocols - as a horrible way to workaround that, I made https://github.com/EionRobb/purple-plugins-prpl which adds a new protocol type that has all the libpurple plugins as contacts that you can enable and disable - seemed to work ok with lurch when I tried it last (many years ago) |
Thanks! I'll look into it. :) I wouldn't hesitate replacing bitlbee, but unfortunately there not a single XMPP-client that comes even close to be as usable as WeeChat with bitlbee. It just sucks that bitlbee doesn't have any modern features like support for OMEMO, carbons, http file uploads or message archive management. :/ |
Does anyone have lurch running with BitlBee (an IRC to IM gateway which can use libpurple) by any chance?
I've tried it (after double-checking that I'm indeed using XMPP via libpurple and not its own XMPP support), but unfortunately,
//lurch help
(with a double slash to escape it from my IRC client) just gets sent to the contact I'm speaking to - not sure how I could debug that kind of thing, so any help would be much appreciated!The text was updated successfully, but these errors were encountered: