weechat
jabber.py: Message Encription via Omemo (XEP-0384)
With OMEMO having conversations with multiple clients is easy and secure. It supersedes OTR.
The implementation of Message Cabons #186 is beneficial for this.
You can check the progress of other xmpp implementations at https://omemo.top/
If there's OMEMO support I will definitely abandon bitlbee and OTR, and use the native solution (weechat+jabber.py). I used to plan to work on libotr support for weechat but I decided to switch to OMEMO after I red some papers about it.
@wnereiz Since there has already been a lot of work on the purple plugin for OMEMO, and because bitlbee can use libpurple, they do seem to be attempting to integrate that.
@physkets For me the problem is that I feel bitlbee is not very easy to use with weechat together - especially the intigration. For example it's command format is completely different from weechat, and really hard to remember. It is painful to get used to it.
I don't understand. One needs Bitlbee commands only for the first time one sets it up. After that, one may use regular Weechat commands. That is what makes it very simple to use.
After setting it up, I just use /connect to open and connect to the bitlbee buffers. You can then use /join to go to rooms and /msg to talk to specific people. All these are Weechat commands.
@physkets Yes, but I add different buddies and join different xmpp rooms (you have to use chat add command for that) quite often. But anyway I know it is not important. You are right, once OMEMO support for libpurple will be done, I can use it with bitlbee.
@wnereiz I have rooms (groups) set so that it automatically /joins them when I /connect to bitlbee. If you already have the room added, just set weechat to auto-connect to it, just like an irc channel.
Hi, any work in progress on this issue ? I don't understand responses with Bitlbee (is it the IRC client you're speaking about ?)
@codeurimpulsif : nothing new for this feature, I still recommend to use bitlbee, this jabber.py script has some problems (like blocking WeeChat on network operations). Bitlbee is not an IRC client, it's a gateway between many instant protocols and IRC (so you can consider it as an IRC server and you can connect to it from WeeChat or any IRC client), see: https://www.bitlbee.org/
No progress is being made towards OMEMO in Bitlbee; @dequis over on their tracker in issue №1239 basically said he has no interest unless paid.* If I fix the issues, would you mind merging this @flashcode? I have one script here already but I wrote it a long long time ago: noirccolors.py. I am sure I could write something that would be performant.
* In re Bitlbee, I am trying to avoid diving into foreign (i.e. not my own) C codebases as they are such timesinks, but @dequis did write:
Unless we have a contract for an appropriate hourly rate, don't act like you're entitled to my time.
I might be able to offer some kind of grant for the work but I really don't know technically why we are just assuming Bitlbee is the better solution. It's true that Bitlbee exploits IRC protoccol to be more instantly usable on many clients, but because of this, it can't relay a lot of the features of the underlying protocols with any fidelity. Here's an example: images. Kitty (xterm-kitty) can support them easily. But Bitlbee-IRC will never be able to support them for e.g. Twitter DM or FB Messenger as anything but links.
Perhaps, @flashcode, what we actually want is a modern Bitlbee that translates other protocols to XMPP for private consumption, rather than IRC. Does such a thing exist?
@dequis over on their tracker in issue №1239 basically said he
*she
Perhaps, @flashcode, what we actually want is a modern Bitlbee that translates other protocols to XMPP for private consumption, rather than IRC. Does such a thing exist?
https://github.com/SpectrumIM/spectrum2
(but i don't see how this makes anything easier? unless your plan is to switch from weechat to profanity)
@dequis
*she
Sorry !
(but i don't see how this makes anything easier? unless your plan is to switch from weechat to profanity)
Not at all. But, well, then, either XMPP support could be added to WeeChat core or via a script if it's not done already, or Bitlbee could support it for the time being via its own XMPP support.