Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

muc mam seems broken in sure.im #19

Open
pravi opened this issue Oct 5, 2023 · 4 comments
Open

muc mam seems broken in sure.im #19

pravi opened this issue Oct 5, 2023 · 4 comments

Comments

@pravi
Copy link

pravi commented Oct 5, 2023

Describe the bug
This was noticed some time back and some discussion happened at xsf/xmpp-providers-website#66 (comment)

To Reproduce
Steps to reproduce the behavior:

  1. Create an muc and invite someone
  2. disable the account and ask other person to send messages while offline
  3. enable account and check for offline messages
  4. No offline message or unable to decrypt

Expected behavior
offline messages should be visible

Screenshots
8d3b2fc3-826c-4394-809e-fe3603143675

Desktop (please complete the following information):

  • OS: Debian bookworm
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: Android
  • OS: Android 10
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context

Tried on both monocles chat and gajim (also some other people reported issues earlier)

@woj-tek
Copy link
Contributor

woj-tek commented Oct 5, 2023

Quick comment:

No offline message or unable to decrypt

Those are two separate things:

  1. no offline message would indicate problem with MAM
  2. 'unable to decrypt' suggest problem with other clients not retrieving properly encryption keys…

Were you able to reproduce the issue using protocol itself, i.e. https://xmpp.org/extensions/xep-0313.html#query ?

@pravi
Copy link
Author

pravi commented Oct 5, 2023

For this query

<iq type='set' id='iyonog'>
  <query xmlns='urn:xmpp:mam:2' queryid='f27' />
</iq>

This was the result

<iq xmlns="jabber:client" to="[jid remove]/gajim.125U1Z4R" id="iyonog" type="result">
  <fin xmlns="urn:xmpp:mam:2" queryid="f27">
    <set xmlns="http://jabber.org/protocol/rsm">
      <count>1069</count>
      <last>5dafa2ca-7b7d-4533-afbc-89e46e12e2bd</last>
      <first>c9f40eb4-73f7-4132-b612-cb806c5c78ae</first>
</set>
</fin>
</iq>

@hantu85
Copy link
Contributor

hantu85 commented Oct 5, 2023

Actually, that is a correct response. However, additionally to this <iq/> result there are also separate messages sent with the actual messages being fetched from MUC MAM archive.

The <iq type="result"/> is sent by the server after sending all messages requested by the client, so the MUC MAM responded without any error.

If messages were sent to you or not, we will not know as you have not attached this part of the XMPP stream log.

Additionally, you've request MAM history fetch from your account MAM archive and not the MUC room MAM archive, so you are testing totally different thing.

@Neustradamus
Copy link

To follow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants