Bug 14954 - Presence in MUCs is always "online"
Summary: Presence in MUCs is always "online"
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: low enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
Depends on: 15747
  Show dependency treegraph
Reported: 2008-03-11 07:04 UTC by Simon McVittie
Modified: 2008-07-29 04:05 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Simon McVittie 2008-03-11 07:04:44 UTC
We always send "online" presence to MUCs, even if we're "away" on the connection itself.

(Setting separate presence for MUCs and the connection would need telepathy-spec changes, and should probably be done using Chat States instead. Anyway, it's out of scope for this bug.)
Comment 1 Simon McVittie 2008-04-28 08:17:25 UTC
Senko has implemented the requested feature, but I've rejected it at least for the moment. Sending our presence status to chatrooms seems like a huge privacy violation, given that the stated purpose of the (narrow) subscribe and publish lists is restricting access to our presence status!
Comment 2 Robert McQueen 2008-07-29 04:05:51 UTC
Over-ruled the objection, on the following basis:
  With a pedantic interpretation, this is arguable a spec violation because it
  exposes your presence to handles who are not on your "publish" list. However, I
  think that given other protocols (essentially, anything but XMPP) exist where
  joining a chat will always expose your presence, I don't think it's reasonable
  for clients or users to rely on this additional exposure not happening anyway.
  Consider the absurdity of expecting that you can be invisible even when you've
  joined a group chat. If someone wants the XMPP-specific semantics badly, we can
  add a RoomPresence interface or somesuch, and they can set a property in order
  to publish a per-room presence.

Merged in HEAD, should be included in Gabble 0.7.7.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.