From 4c5483da1f420e4746729cf2ce3c83b541e93788 Mon Sep 17 00:00:00 2001 From: "http://phil.0x539.de/" Date: Sat, 10 Nov 2012 18:50:47 +0000 Subject: Added a comment --- .../comment_3_6d72ea32c111e605be30ad2153fc71c9._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/design/assistant/blog/day_114__xmpp/comment_3_6d72ea32c111e605be30ad2153fc71c9._comment (limited to 'doc') diff --git a/doc/design/assistant/blog/day_114__xmpp/comment_3_6d72ea32c111e605be30ad2153fc71c9._comment b/doc/design/assistant/blog/day_114__xmpp/comment_3_6d72ea32c111e605be30ad2153fc71c9._comment new file mode 100644 index 000000000..6d2147d37 --- /dev/null +++ b/doc/design/assistant/blog/day_114__xmpp/comment_3_6d72ea32c111e605be30ad2153fc71c9._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://phil.0x539.de/" + nickname="Philipp Kern" + subject="comment 3" + date="2012-11-10T18:50:46Z" + content=""" +Sure, I could, as I'm operating my own server anyway. Others might not be willing to go to some random server and create another account, though. + +Reviewing RFC 6121: Did you try negative priorities for your resources already? It's possible that Gtalk does something weird but in theory they should be ignored for messages directed to non-qualified JIDs (i.e. without an explicit resource setting). Setting \"xa\" alone won't help you anything, it will only cause the others to see you as \"xa\" but that's a perfectly valid common chat status where you expect messages to be queued in the client until the user returns. +"""]] -- cgit v1.2.3