Bug 14482 - Receiving D-Bus messages from the past on a MUC D-Bus tube
Summary: Receiving D-Bus messages from the past on a MUC D-Bus tube
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
Depends on:
Reported: 2008-02-13 10:01 UTC by Alban Crequy
Modified: 2019-12-03 19:17 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Alban Crequy 2008-02-13 10:01:08 UTC
When I join a MUC channel, I get the last few messages sent by people when I was not there because theses messages are stored by the MUC server, so that it can send them to me.

According to http://telepathy.freedesktop.org/xmpp/muc-bytestream.html D-Bus messages are encapsuled in a <message/> stanza. So they are also saved by the server.

I use telepathy-python/examples/tube-dbus-muc.py to test this:
1. launch the initiator
2. wait until a few signals "Hello" are emitted
3. launch the client
4. the client receives all signals emitted before the client join the chatroom.

So the client receives D-Bus messages from the past.

It sounds undesirable. On the client, Gabble should drop messages containing D-Bus messages if they are sent before the client join the chatroom.
Comment 1 Guillaume Desmottes 2008-02-14 01:35:11 UTC
Isn't the goal of these markups to avoid that?

<amp xmlns='http://jabber.org/protocol/amp'>
    <rule condition='deliver' value='stored' action='error'/>
    <rule condition='match-resource' value='exact' action='error'/>
Comment 2 Alban Crequy 2008-02-14 02:51:22 UTC
> Isn't the goal of these markups to avoid that?

I don't know whether these markups (XEP-0079) can be used on MUC, but they seem to be not implemented on current Jabber servers, see http://bugs.freedesktop.org/show_bug.cgi?id=14485#c2
Comment 3 GitLab Migration User 2019-12-03 19:17:25 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/5.

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.