Opened 12 years ago

Last modified 17 months ago

#2448 new enhancement

Allow users to "Send To" specific XMPP resources

Reported by: kentyman Owned by: deryni
Milestone: Component: XMPP
Version: 1.x Keywords: send to xmpp jabber resource resources
Cc: IceWil, jojoo, peacehh, daks, PeterFab9845, smove


I think the Send To menu should allow messages to be sent to specific XMPP resources. For example, if I am logged in at Home and Work, and want to send myself a message from one location to another, I can just change Send To to the other resource (even though it would have a lower priority since it'd be idle).

This is similar too, but slightly different than, ticket #188.

Change History (23)

comment:1 Changed 12 years ago by deryni

While the request here is different my response to the other ticket indicates that as far as I'm concerned (and as far as I can imagine) the same solution is needed and fixes both. Which is why I commented on Sent To resources there.

comment:2 Changed 12 years ago by seanegan

  • Component changed from pidgin (gtk) to XMPP
  • Owner set to nwalp

comment:3 Changed 11 years ago by CrazyTerabyte

Both Psi and Kopete have this feature. Heck, even Bombus, which is an open-source jabber client for mobile phones, written in Java ME, has this feature!

comment:4 Changed 11 years ago by desss

so.. we got 2.3.1 version and enhancement still in todo-list. Or not? :D

comment:5 Changed 11 years ago by Oktoplus

This is definitely a behaviour I miss. Though, Pidgin doesn't seem to distinguish my resources of one XMPP account.

Be my account oktoplus@myjabberserver. On my desktop PC I set resource to "Home", on my laptop to "Laptop". If I add a buddy oktoplus@myjabberserver/Laptop, it will always be online as long as ANY resource of my account is online, no matter if I'm even logged in on my laptop.

So what I'd like to see in my buddy list is an entry which contains either one specific resource or any resource but the one Pidgin itself uses. If I could set an entry for each resource, I could group them in one contact and then have the ability to choose which one to send a message.

I think Gajim handles this quite nice. Though, I really want to stick with Pidgin since it's a great piece of software :)

comment:6 Changed 11 years ago by deryni

  • Owner changed from nwalp to deryni

To the best of my knowledge, you cannot add a full jid (user@server/resource) to your roster on XMPP, that is not allowed. Roster entries (really presence subscriptions) are always based on the bare jid (no resources). That being said as I commented in my initial response what needs to happen in pidgin is that the Send To menu needs to list resources for the buddy the same way it lists alternate buddies. I started looking into this a little while back but didn't get far because I was afraid that the changes required would interact badly in places I didn't test and so I gave up on it for the time being. If someone wants to attempt to do this they should feel free to do so, I will gladly accept a well-written well-tested patch for this (any such patch should keep in mind the idea that thread-id:s should also eventually be made available in the Send To menu).

comment:7 Changed 10 years ago by deryni

Ticket #7993 has been marked as a duplicate of this ticket.

comment:8 Changed 9 years ago by p90

Hi, this was marked for version 1.x Now we are at 2.6 but it is still missing this important feature (especially if you, as I do, use several laptops and desktops and have to send messages between them or to transfer files)

Any progress made on this one?

comment:9 Changed 9 years ago by darkrain42

Ticket #11617 has been marked as a duplicate of this ticket.

comment:10 Changed 8 years ago by byte

would this feature ever be added?

comment:11 Changed 8 years ago by kentyman

I sure hope so. I think it would be really slick, especially with so many people online at home/work/mobile all at the same time. When I can't be sure it'll go to the right resource, I often have to resort to text messaging or something equally lame.

comment:12 Changed 7 years ago by p90

Thats not all. If you can send to spezific resources you can easily send yourself messages or even files making filetransfers between devices like my phone, my home pc or my pc at work a piece of cake.

comment:13 Changed 6 years ago by jojoo

Guys, please make this work.

This has been around for 6 years. Now, that xmpp is heavily used from people with different devices (Tablet + Phone + Laptop + Desktop) it's really time to support this.

I'm annoying the hell out of my friends, constantly writing to the wrong device.

comment:14 Changed 6 years ago by notphilipfry

GUI should offer resources to which one has subscribed first listing those which are available (or otherwise online) and those not, as well as a free field for composing other resource

In tandem consider

XEP-0280 Message Carbons XEP-0184 Delivery Receipts

The mobile clients GibberBot? and Xabber, respectively, implement resource selection.

Last edited 6 years ago by notphilipfry (previous) (diff)

comment:15 Changed 6 years ago by daggett

I would change the severity of this bug if I could because it breaks XMPP messaging :

  • user A is connected multiple times via XMPP (several places/devices),
  • user B is also connected multiple times via XMPP,
  • user B wants to send a message to user A,
  • when user B sends a message to user A, but he can not choose to which ressource of user A to send it,
  • Pidgin sends the message to one of the devices/places,
  • so user B has no mean to ensure he can really start a conversation with user A
  • same thing for user A if he wants to send a message to user B,
  • those two users can't communicate using Pidgin.

=> the communication is broken, so this really is a bug, not a feature or enhancement, and as it breaks messaging, it should be flagged as "urgent".

I was surprised that this resource selection / choice is implemented when sending a file :

  • user B wants to send a file to user A (right-click on user A, send file),
  • he chooses a file,
  • Pidgin asks to which resource he wants to send the file !
  • he chooses the resource, then the file gets sent to the right resource

Regards, Daggett

comment:16 Changed 6 years ago by daggett

I'm having new issues when communicating with friends using OTR when connected on multiple devices :

  • user B is connected on his phone AND on his computer,
  • computer client is Pidgin + OTR ("trusted"), phone client is some XMPP Android client supporting OTR,
  • both phone and computer have the status "away",
  • user A sends an OTR message to user B using Pidgin + OTR, he can not choose the ressource to which send the message,
  • Pidgin decides to send it to one, i.e. : the phone,
  • the phone is not "trusted" by OTR,
  • so Pidgin or OTR tries to send it to the computer, but somehow OTR states the message is "malformed",
  • so it tries again and again to resend the message, alternatively to one ressource then the other.

The only way to get out of this loop would be to be able to choose the ressource to which send a message. But for now, there does not seem to be any other choice than close then restart Pidgin.

One can say that the loop is OTR's fault, but it wouldn't happen if Pidgin had a way to choose to which ressource to send a message.

So Pidgin is breaking the communication by not implementing the ressources' selection that an XMPP client should allow to do.

Regards, Daggett

comment:17 Changed 5 years ago by lameventanas

I also need this function in pidgin. Without it I can't answer properly to my contacts when they are logged in from more than one place, which really sucks.

I can't believe this bug report has been here for 6 years without any official word.

comment:18 Changed 5 years ago by daks

Guys, what plans do you have regarding this enhancement request if any? Pidgin is almost the only client that doesn't support resource selection.

Reagrds, Dmitriy

comment:19 Changed 5 years ago by smove

Hey guys,

is anyone actually looking into this issue?

AFAIK, there are plenty people requesting this enhancement (which I would rather consider a bug, to be honest).

Especially the situation that Daggett describes is a huge problem. I can't just easily get up from the couch and switch to my PC or laptop and continue the conversation.

Also, it's a pitty that this ticket is already 7 years old.

Regards, Jan

comment:20 Changed 4 years ago by lameventanas

This bug makes Pidgin pretty much useless for XMPP, which is strange because it should be the best supported protocol since its opensource.

It is sad that this bug is still present after 7 years, and the developers haven't tried to fix it. Heck, its not even recognized as a bug, its marked as "new enhancement".

And we are not even talking about some complicated thing like audio or video.

Last edited 4 years ago by lameventanas (previous) (diff)

comment:21 Changed 4 years ago by Toadtown

Well, so much about "chat client used by millions". Millions of flys can't be wrong, isn't it? That's just pathetic. XMPP resources are an essential feature, but obviously they seem to only add stuff which only affects the developers by themselves. Not even stuff like online notifications are included by default without being platform independent. And yes, I just signed up to say this, as I'm pissed that somebody seriously said to me that Pidgin would be as good as Miranda NG! What a bad joke. 7 YEARS! And sorry if this sounds offensive.

Last edited 4 years ago by Toadtown (previous) (diff)

comment:22 Changed 2 years ago by Sur3

Any updates on this?

comment:23 Changed 17 months ago by Sur3

Belated Happy 10 Years Birthday, Bug! :-/

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!