[04:14:16]
<Echo1> maranda committed --
{...}: add markers MUC logs and advertise support.
-> https://github.com/maranda/metronome/commit/5ce691b1ccb2e691b5ed5dd65bc2fee90aff0f06
[13:02:22]
<soupsoupsoup> I think metronome might be carbon-forwarding messages with the wrong namespace: The contained message has the namespace urn:xmpp:forward:0 instead of jabber:client. Version 3.12
[13:13:40]
<Maranda> soupsoupsoup: i think your client library or client isnt traversing tne forwarded stanza correctly
[13:15:20]
<Maranda> Carbon copies do contain a forwarded payload inside either received or sent
[13:15:28]
<Maranda> Or
[13:15:38]
<soupsoupsoup> Maranda, https://paste.yunohost.org/yaxavaqoso.js I got this xml element from the client-side logs
[13:16:13]
<soupsoupsoup> I'm talking about line 6: {urn:xmpp:forward:0}:message
[13:16:43]
<Maranda> soupsoupsoup: that stanza is correct
[13:16:59]
<Maranda> Read what I said above
[13:18:42]
<soupsoupsoup> Maranda, The stanza isn't correct, see here: https://xmpp.org/extensions/xep-0280.html#example-10
[13:19:00]
<Maranda> Dino is not traversing the stanza correctly
[13:19:25]
<soupsoupsoup> the stanza within the forwarded element should have a "xmlns='jabber:client'", however it doesn't
[13:20:51]
<Maranda> There's nothing that says that the inner message stanza should be requalified with a jabber:client ns explicitly
[13:21:36]
<soupsoupsoup> all the examples in the XEP specification say so...
[13:21:50]
<Maranda> The inner message stanza doesnt have a xlmns attribute
[13:22:32]
<Maranda> Examples in a spec arent mandatory my friend, the text is
[13:24:06]
<soupsoupsoup> let me put it differently: The only server I had problems with so far is metronome, all other servers implemet it with the jabber:client namespace. People _will_ run into problems with metronome if it's the only server that behaves differently
[13:26:05]
<Maranda> Good and let me put it that dino is the first client to have issues with metronome carbons implementation and that's years old 🤓
[13:28:01]
<Maranda> So why instead dont you open a ticket instead on the metronome tracker? Like everyone normally would?
[13:28:34]
<soupsoupsoup> I first wanted to check if my problem assesment was correct
[13:30:00]
<Maranda> In reality the problem is with dino's stanza parsing
[13:31:13]
<Maranda> As I already said
[13:32:27]
<soupsoupsoup> So you say that all other servers behave wrongly?
[13:35:55]
<Maranda> No I'm saying that dino's carbons implementation is wrong and shouldn't assume namespaces that way to traverse a stanza and that metronome es conforming to the spec and that it's the first client to have issues with that
[13:37:08]
<soupsoupsoup> > shouldn't assume namespaces that way to traverse a stanza
I don't really undestand what you mean. You mean Dino shouldn't check for namespaces?
[13:39:39]
<Maranda> No I mean that it's pointless in this case and shouldn't require the forwarded inner message stanza to be requalified
[13:42:19]
<Maranda> Irregardless, instead of just making an argument here you should, just, post a ticket 😉
[13:43:54]
<soupsoupsoup> Yeah sure. I can open a ticket. I was just puzzled by you insisting on that behaviour - would you fix it if there was an issue open?
[13:44:11]
<soupsoupsoup> or s/fix/change if you so want
[13:50:22]
<Maranda> soupsoupsoup: putting a COMPAT for dino 🦕 and "fixing" are two different things, even because it's puzzling it complains for carbons but not for MAM (doesn't it?) 😉
[13:52:42]
<soupsoupsoup> Maranda, where did I say that it works with MAM? I don't know if it does.
[14:00:41]
<Curator> and the dumb fellow obviously didn't post the ticket
[14:01:11]
<Curator> 🤛 🤛 🤛 🤛
[14:03:21]
<soupsoupsoup> Curator, the fact that I didn't do something right away is hardly a reason to insult me
[14:29:16]
<Echo1> maranda committed --
{...}: add COMPAT for Dino.
-> https://github.com/maranda/metronome/commit/b3e34db2bb4fe4f849cffff89a1850b6e2b1f037
[20:40:35]
<jim> Maranda: thank you. I was the one who raised the issue on Dino's MUC, and I could already patch my server and it works just fine.
[20:49:42]
<Maranda> jim: but the problem is Dino tbh the compat was really trivial anyways
[20:52:17]
<jim> I could see that. But anyways, thanks for the quick fix.
[20:53:48]
<jim> (And as a end user, I cannot tell where the problem lied, all I can see is that I got good support from both communities, and that's amazing)
[22:11:11]
<Maranda> jim, but still it will need 3.13.0 to end into yunohost anyways