Opened at 2016-03-29T13:37:17Z
Closed at 2016-04-29T22:27:34Z
#1252 closed defect (notabug)
bitlbee should hide from listed clients when jabber/XMPP account have negative priority
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Jabber | Version: | Unspecified |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Public server |
| OS version/distro: |
Description
jabber accounts with negative priority should be not receiving messages unless this device is directly contacted (by specifying full JID) and also not listed in others clients as connected client, which is common behavior.
Official server allows listing such client which leads to some missed messages due to routing messages to such device which can be not checked too often (because it shouldnt receive messages when other clients are not connected with the same jid but positive prio.
Attachments (0)
Change History (5)
comment:1 Changed at 2016-03-30T01:22:20Z by
comment:2 Changed at 2016-03-30T01:32:41Z by
Nope. This account in bitlbee which you set to have negative priority should as you say look as offline for rest of the world.
Just try it yourself.. connect to some jabber account from two jabber clients (eg. psi 0.14 looks behaving correctly) and on one set -1 priority.. you will not see this client listed in connected "devices".
comment:3 Changed at 2016-03-30T01:45:57Z by
psi 0.15 sends this from account 1:
<presence> <show>away</show> <priority>-1</priority> <c xmlns="http://jabber.org/protocol/caps" node="http://psi-im.org/caps" ver="caps-b75d8d2b25" ext="cs ep-notify-2 html"/> </presence>
Receives this in account 2
<presence from="dx-test1@dukgo.com/bolsa"> <show>away</show> <priority>-1</priority> <c xmlns="http://jabber.org/protocol/caps" node="http://psi-im.org/caps" ver="caps-b75d8d2b25" ext="cs ep-notify-2 html"/> </presence>
Displays it as away, not offline.
When trying to send a message to this priority -1 account the message is not delivered and an error comes from the server, which is not displayed in the psi UI, it just drops the message silently (log from the point of view of account 2)
<message type="chat" to="dx-test1@dukgo.com" id="aac7a"> <body>test</body> <active xmlns="http://jabber.org/protocol/chatstates"/> </message> <message from="dx-test1@dukgo.com" type="error" id="aac7a" to="dx-test2@dukgo.com/bolsa"> <error type="cancel"> <service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> </error> </message>
I still don't see what we're doing differently.
comment:5 Changed at 2016-04-29T22:27:34Z by
| Resolution: | → notabug |
|---|---|
| Status: | new → closed |
Closing this since it doesn't seem like a bug, but feel free to reopen if i'm wrong.
I don't understand this issue. Are you saying that other contacts with negative priority should appear as offline? Are you saying that bitlbee should make itself appear offline when priority is negative?