Comments on: Why XMPP Part 2- Saving Your Resources https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/ Linux. GNU. Freedom. Wed, 20 Sep 2017 12:29:42 +0000 hourly 1 https://wordpress.org/?v=4.9-alpha-41547 By: Kent https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-93743 Sun, 23 Mar 2008 08:09:22 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-93743 Just found this blog while looking for an explanation for something.
As of today, I noticed gtalk is now coercing the hand-coded resource ID into a manipulated one with the random signuture, completely invalidating the whole notion of it representing a distinct endpoint, and now totally messing up my PSI conversations. ( psi treats every resource identifier as a distinct client/person so one can have 2 conversations with the same person via different resources simultaneously as it only uses the priority to identify which entity to make the primary connection to, not to relay every separate message )

Personally I think its a shocking shame google should so blatantly mess up the Jabber protocol like they have, its as bad as Internet Explorer back in the day adding their own custom weird random non-standard extensions which as we see now, have held the internet back from developing properly. ( ie: their non-standard file transmission system completely incompatible with the standard )

I'm going to have to start trying to push people from gTalk onto /real/ Jabber clients just to avoid the pain google is introducing.

]]>
By: LINUX-Блоґ.org.ua » Чому XMPP. Частина 2. Зберігаючи ваші ресурси https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-67099 Thu, 30 Aug 2007 14:23:38 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-67099 [...] “Why XMPP Part 2- Saving Your Resources”, Aaron [...]

]]>
By: Hoàng Đức Hiếu https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-64728 Sat, 11 Aug 2007 07:48:51 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-64728 @#5 by Askrates:

Fortunately Gajim has a really helpful toolstip for the Resource input box, if the user doesn't find it too lengthy to start reading.

]]>
By: Jelmer Vernooij https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61558 Mon, 16 Jul 2007 00:15:02 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61558 @Bogomips
BitlBee doesn't have randomized resource strings at all. I agree with Aaron's comments on being able to set resources and BitlBee fully supports customizing resources or directing messages at specific resources.

]]>
By: Aaron https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61501 Sun, 15 Jul 2007 14:37:53 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61501 @Evan- Quite to the contrary. I see no where within the client where I can change the priority to fit my needs. The first connection gives a priority of 0, then each subsequent connection increases by 1. This is all generated in the client itself. The same is true for libgaim/libpurple clients.

Upon further investigation, you're right about the resource. I can change this when I want, and only the Gmail.com provider appends the random hash, rather than the client. This is good news. At least that is something in the right direction. I have updated the post to reflect the correct nature of these clients.

]]>
By: Evan Schoenberg https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61500 Sun, 15 Jul 2007 14:29:05 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61500 Pidgin does allow you to specify the resource and to specify a priority associated with your status.

As aadam indicated, *every* Google Talk connection is going to have a server-generated or server-modified resource name; this has nothing to do with the client in use. Pidgin and all other libpurple clients (including Adium) allow specifying of the resource you want to use.

It'd be nice if you'd edit your post to indicate that Pidgin, Adium, and other clients are just as capable in regards to resource and priority as the other XMPP clients you describe. As it is, it is highly misleading.

]]>
By: Bogomips https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61320 Sat, 14 Jul 2007 11:40:24 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61320 @Jelmer
But isn't one of the advantages of resources the fact that you can add someone to your list with someone@someserver.com/work and messages sent to that person would only be delivered to the client that had the "work" resource set?

Wouldn't server side (or even client side) random resource string generation take away that advantage?

]]>
By: Askrates https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61244 Fri, 13 Jul 2007 23:12:51 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61244 I really like the idea of being able to set resources manually. However, it just occurred to me after looking at your screenshot that most people would be absolutely clueless when presented with a box marked "resource". It can be misinterpreted very easily.
I suggest hiding options like this under an "advanced" tab, or at least doing something to make it more usable.

]]>
By: Jelmer Vernooij https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61230 Fri, 13 Jul 2007 21:30:13 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61230 Just to clarify: BitlBee has never used libgaim/libpurple. It was based on an older version of gaim, but except for a major part of the oscar implementation, it doesn't contain any of the gaim code anymore. The Jabber implementation was written from scratch.

Other than that, keep up the XMPP blog post. They're an interesting read!

]]>
By: Peter Saint-Andre https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61204 Fri, 13 Jul 2007 17:39:16 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61204 @Aadaam: It is NOT TRUE that distinguishing resources by resource strings will be deprecated. However, we are going to recommend (but not require) that servers generate resource strings on behalf of clients -- there are some security concerns related to client-generated resource identifiers.

]]>
By: Aadaam https://pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61193 Fri, 13 Jul 2007 16:36:57 +0000 http://www.pthree.org/2007/07/13/why-xmpp-part-2-saving-your-resources/#comment-61193 Distinguishing resources by resource strings will be deprecated in the upcoming version of XMPP.

As for the resource hash appended to the end, it's probbaly not pidgin's fault, but it's a GTalk "feature": in core XMPP standard (rfc 3920-21), it is written that a server CAN force a resource ID, and so does google.

]]>