Opened at 2008-01-03T18:19:13Z
Closed at 2015-10-21T11:26:44Z
#342 closed defect (notabug)
In GTALK, setting a user to never show up removes them completely from bitlebee
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Jabber | Version: | 1.0.3 |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Public server |
OS version/distro: |
Description (last modified by )
In the gtalk interface in gmail, you can only show a small percentage of your contacts and so i usually set a few of them to never show up but it doesnt mean remove them, it just means when i need to talk to them, I have to find them in the contact list myself. However, i noticed that in bitlbee, the user is completely removed. and trying to talk to them results in a no nick in this channel.
09:58 -!- randomuser: No such nick/channel
some xmlconsole output.
adding a user to "auto" show up
10:01 <xmlconsole> RX: <iq to="me@randomdomain/BitlBeeFDE957C3" id="3D83D624" type="set"><query xmlns="jabber:iq:roster"><item jid="randomuser@randomdomain.com" subscription="both"/></query></iq>
making a user "never" show up
10:01 <xmlconsole> RX: <iq to="me@randomdomain/BitlBeeFDE957C3" id="3D83D721" type="set"><query xmlns="jabber:iq:roster"><item jid="randomuser@randomdomain.com" subscription="remove"/></query></iq>
Attachments (0)
Change History (3)
comment:1 Changed at 2008-03-15T23:04:39Z by
Component: | BitlBee → Jabber |
---|
comment:2 follow-up: 3 Changed at 2015-03-16T03:20:45Z by
Description: | modified (diff) |
---|
Huh, this still applies. It's the server literally telling us to remove the contact from the roster, though. I'd say we're doing the right thing here and it's not a bug.
(edited description to add code blocks)
comment:3 Changed at 2015-10-21T11:26:44Z by
Resolution: | → notabug |
---|---|
Status: | new → closed |
Replying to dx:
Huh, this still applies. It's the server literally telling us to remove the contact from the roster, though. I'd say we're doing the right thing here and it's not a bug.
Closing for that reason.
Changing component. Keeping this bug for after the 1.2 release, probably.