XMPP Service Operators - 2017-11-09

I don't have any, beside they'd be forced to be limited to a normal user use case of MAM willing it or not on my server.

I like InVerse implementation of MAM, only thing that quirks is the message doubles with room history on mica

On muc***

The client should send <history maxstanzas='0'/> or something when the room supports MAM, I guess.

Shouldn't historic stanzas have IDs?

Yes deduplication should work as well.

Also it seems to hickup with multiresource occupants... But I have to verify that.

Hm

another bug, it's not resetting the browser storage for mam when leaving a room. So messages keep being duplicated anytime you enter.

(for history and mam)

There might be a better place for reporting InVerse bugs :-)

What, and risk the inverse dev seeing this?

https://github.com/jcbrand/converse.js/issues/951 like this? You nuptas.

>.>

Such big mouths.

Tbh I'm not sure why it doesn't clear the browserstorage though, that seems like some 'distraction' mistake coding wise. ✏

JC Brand replied the ticket, I think the duplicates are because InVerse expects the MAM result message stanzas to always have the same id attribute *shrugs* instead of checking the id attribute of the forwarded message stanza.

-version conversejs.org

... And changing the id attrs in a way which was supposed to please converse/inverse.js didn't work either *mumbles*