lksjdflksjdfDoes anyone know a public server that only has mam:1 for testing purposes?
Link MauveIIRC OpenFire did, at least until recently.
Link MauveI don’t know of public services running it though.
WojtekTigase supports only mam:1 - you can check tigase.im/sure.im
Link MauveWojtek, any reason it still hasn’t been updated to mam:2? The spec has been out for almost three years and many clients rely on its guarantees.
GuusOpenfire's latest updates attempt to support both MAM:1 and 2. You could install an older plugin. Not sure about the quality of support though.
lksjdflksjdfLink Mauve, psst don't inspire them to upgrade, we'll loose test servers :]
lksjdflksjdfthanks for the pointer Wojtek
WojtekLink Mauve - no particular reason in itself
Wojtekon a separate note - why 0359 defines new element/namespace instead of requiring generation stanzas' IDs as UUID?
Link MauveI wish it did, but maybe it isn’t discoverable properly.
Link MauveAlso at some point it was a workaround for MUC being allowed to rewrite the sender’s @id (MUC has been fixed since then).
MattJIt's not a question of discovery, as much as the id attribute is chosen by the sender, not the server
Link MauveMattJ, the origin-id is also chosen by the sender.
MattJ<stanza-id> was originally <archived by='...' id='...'/> and then it was decided that the id should be made generic and not just a part of MAM
MattJYes, <origin-id> is more of a hack that should probably be dropped (but some people still have arguments in favour of it iirc)
MattJIn the switch from <archived> -> <stanza-id> we've actually lost a way for the server to indicate whether a stanza was/wasn't archived (but maybe that's fine if we tighten up the rules about what a server should/shouldn't archive)
ZashMattJ, did we?
KevDid we what?
ZashIs the server supposed to stamp <stanza-id> on non-archived stanzas?
MattJIt MUST stamp them on archived stanzas, but nothing says it can't stamp them on non-archived stanzas
ZashDon't think we don't not do that maybe.
KevMy assumption was that it wouldn't.
KevBut hadn't realised that we'd left it open.
lksjdflksjdfWojtek, unfortunately it doesn't seem to be possible to register a tigase.im/sure.im account 🙁 they don't do in-band registration and the website is broken - clicking on register account -> next simply doesn't do anything.
WojtekI'm aware of this issue (since a couple of minutes ago) - there is a problem with websocket, which we fixed a while back but installation wasn't updated yet
Wojtekwrite to me in private message and I can create you an account
ZashDoes Tigase not support SASL EXTERNAL for server-to-server authentication?
Wojtekit's implemented recently, but not yet deployed
lksjdflksjdfWojtek, great, thanks! 🙂
Wojtekyeah, it was long time needed
lksjdflksjdfhm trying to set the tigase.im mam archiving preference to anything other than "never" with conversations doesn't work, I haven't found out yet if it's a conversations or tigase (or a user) issue, though
Wojtekhmm, having XML log would be helpful :-)
lksjdflksjdfWhen I send the stanzas manually, it works 🤷 so either a conversations bug or my fault for using it wrongly 🙂
Wojtekno I'm curious what's happening between conversation and Tigase because... it should just work :-)
Wojciech Kapciahas joined
Wojciech Kapciahas left
lksjdflksjdfWojtek, I don't know how to get an XML log out of conversations (that's not the client I'm currently testing, I just wanted to use it for that setting 😉 ), but I guess you should be able to reproduce the problem if you want to investigate it.
Wojtekwell, if it works with XML and it works with our clients... ;-)