jdev - 2020-11-25

Why I Am Here?

Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator Creator

Library maintainers: if the user of your library doesn't set an ID on message and/or presence stanzas where it's not required, do you do it for them even though technically the spec doesn't require it?

Or can you think of any reason (other than syscalls for randomness being somewhat expensive) not to? Eg. is there some common use case where the user would *want* to send an empty ID?

configurable, defaults to no

flow: is that something an existing library does, or just a suggestion? I'd be curious to see what other actual libraries are doing too

depending on the version, smack

ah cool, thanks

I also don't think there is a reason get randomness via syscall for every stanza id, there should be secure enough user-space rng's that if seeded correctly are good enough

but strictly speaking, that is also configurable in smack, i.e. a user could configure smack to use the randomness source of his wishing for stanza id generation

I think there might be an argument for id-less stanzas for certain systems, i.e. where every byte on the wire that can be safed should be safed

https://github.com/horazont/aioxmpp/blob/devel/aioxmpp/stream.py#L2058 I don’t discriminate

That's fair

thanks jonas’

if no ID is set, a random one will be generated. sending ID-less stanzas is just a recipe for pain once you start any type of tracking and I don’t want users to have to bother with that.

Sam Whited, setting a @id is a SHOULD in the RFC though.

(And a MUST on iq of course.)

Link Mauve: I think that's just for stream start, not stanzas, right? I just read through the stanza semantics section again and didn't see that

oh, it's in the section specifically about the ID attribute (8.1.3) where it's a RECOMMENDED. Fair enough.

Right.

Cool, no need to overthink it anymore then, I'm just going to do that. Thanks for pointing that out!

The really nasty evil thing you should NEVER EVER do is to set an @id on *received* packets.

s/packets/stanzas

Yes, I can see how that would lead to confusion :)

I've seen issues when certain things reused the @id for replies to message stanzas.

Hi guys 🙂

o/

do you guys know if there's support of ephemeral messages in some XMPP clients ?

https://xmpp.org/extensions/inbox/ephemeral-messages.html