Undesirable behaviour when multiple clients are connected to irssi_proxy

Bug #1026820 reported by Tim Angus on 2012-07-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
irssi (Ubuntu)

Bug Description

This is a bug I have filed against upstream (with a working patch), but it doesn't look like irssi is being actively developed. Maybe the patch could be applied to the Ubuntu package directly? For what it's worth I've been using the patch for about 6 months now.

The bug is on irssi's tracker at: http://bugs.irssi.org/index.php?do=details&task_id=832&project=5&order=id&sort=desc

This is the text from the above bug report:

"Irssi proxy is great; I have been using it for many years without problem. There has always been one thing that annoyed me though. Consider the following: I have a copy of Irssi running permanently on a server, another proxy IRC client connected to it that runs on my home machine and a second proxy IRC client running on my machine at work. For the most part, this works just fine. Where things go a bit awry is when I enter into a /query with another user. On the local client (let's say it's my work one) and Irssi itself, the conversation might look as follows:

<me> Hi, how's it going?
<them> Not bad, what are you up to?
<me> Just reporting this bug in Irssi that I've patched...
<them> Hopefully they'll commit it then?
<me> Yes that would be lovely!
* me grins :D

Unfortunately on other proxy clients (e.g. the home one), the conversation looks like this:

window 1:

<me> Hi, how's it going?
<me> Just reporting this bug in Irssi that I've patched...
<me> Yes that would be lovely!
* me grins :D

window 2:

<them> Not bad, what are you up to?
<them> Hopefully they'll commit it then?

In other words the conversation is split up into separate parts, my half and the reply half. This isn't really a big deal since you don't care about a conversation you've already had right? I guess so but it's annoying having to clean up the non-sensical windows on the other client, and if you want to continue the conversation on said client it's difficult to refer back to the previous conversation.

The reason it happens is that you can't cause an arbitrary IRC client (Irssi included) to display the correct UI as if it had sent the PRIVMSG itself. The other clients receive PRIVMSGs of your lines from the proxy but display them as if the messages are coming TO you, not FROM you. This makes perfect sense in a channel context since in that case to and from are the same thing.

My solution is when you're sending a PRIVMSG to an individual, the other proxy clients receive your lines FROM the person you sent them TO, prefixed with your nick. In case that doesn't make any sense (believe me, it didn't to me to begin with), here's how the conversation looks on the other proxy clients:

<them> <me> Hi, how's it going?
<them> Not bad, what are you up to?
<them> <me> Just reporting this bug in Irssi that I've patched...
<them> Hopefully they'll commit it then?
<them> <me> Yes that would be lovely!
<them> * me grins :D

Now, I fully accept this isn't exactly ideal, but I think it's the best solution available, and the behaviour is certainly better than what happens right now. I guess how you display your nick on the other clients might be a bit contentious? e.g. should it say "<them> <me> Hi, how's it going?" or "<them> me> Hi, how's it going?" or just "<them> > Hi, how's it going?" etc. You can't really second guess how arbitrary IRC clients display things so I just settled on the usual IRC defaults.

For what it's worth, I've been using the attached patch for a few weeks now without any obvious problems.

Thanks for the great client! :)"

Tim Angus (tim-ngus) wrote :

The attachment "Fix multi client irssi_proxy behaviour" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers