jdev - 2025-10-25


  1. lovetox

    world would be so good if we all would use sortable UUIDs :/

  2. MattJ

    Prosody and ejabberd do, I don't know if you will ever reach "all" :)

  3. lovetox

    yeah i know ejabberd does, since when does prosody?

  4. lovetox

    this is great, now can we have a mam-feature that advertises the fact, then i can also depend on it

  5. lovetox

    this is great, now can we have a mam-feature that advertises the fact, than i can also depend on it

  6. lovetox

    or maybe it should be a 0359 feature

  7. MattJ

    Prosody since 13.0.0 I think

  8. Martin

    > world would be so good if we all would use sortable UUIDs :/ Doesn't some xep demand to use uuid v4, which is not sortable.

  9. lovetox

    no

  10. Martin

    Seems xep-0388 requires a uuidv4 vor the user agent ID and as I have one getID() function I use everywhere, I use an v4 everywhere now. :D

  11. singpolyma

    I use uuidv7 everywhere for similar reason

  12. singpolyma

    0388 says it requires UUID because it wants to avoid someone picking a garbage id. The actual requirement that it be uuidv4 isn't really there in practise

  13. Martin

    Maybe the xep could be changed to require uuid >= v4.

  14. lovetox

    Why?

  15. lovetox

    This is for the client id

  16. lovetox

    The criterion is that's it must be unique

  17. lovetox

    No use case comes to mind why you would want to sort client ids

  18. lovetox

    They are not even generated by the same entity

  19. singpolyma

    Sure. But also it doesn't matter. It should probably say "a suitably unique identifier, such as uuidv4"

  20. lovetox

    Yes it should

  21. lovetox

    But it's not really relevant to the the stanza id debate, there it has a use

  22. Martin

    lovetox: I find it better to have one getID() that I use everywhere, than having to use getIDv4() for one thing and another one for others. That's why I would prefer the client id from 388 to be more flexible and not nailed to v4.

  23. Martin

    That's the reason I currently use v4 everywhere. :)

  24. lovetox

    The server cannot verify if you used a uuid 😉

  25. theTedd

    UUIDv4 has some bits that are fixed, so it is possible to verify when it hasn't been used (except in the case where those bits coincidentally match)

  26. lovetox

    You can match a form, you can not verify if it's unique

  27. lovetox

    at least not globally, the server of course can check if its unique within his user base, not sure if this has any implications somewhere else

  28. lovetox

    reading it looks more like a, client better use something unique, otherwise they shoot themself in the foot

  29. theTedd

    UUID doesn't guarantee global uniqueness either, it's just on the balance of probabilities

  30. lovetox

    thats true, still good enough

  31. Martin

    > The server cannot verify if you used a uuid 😉 True, but I usually don't knowingly violate the XEP. :D

  32. lovetox

    tell me you are a new xmpp developer, without telling me

  33. Martin

    lol

  34. Martin

    So, you'd say UUIDv7 would also do, as the spirit of the xep demanding v4 is just to assure a "minimum quality"?

  35. singpolyma

    Yes

  36. Martin

    Will I be considered an experienced xmpp developer once I knowingly violate a xep? :D

    🤣 1
  37. theTedd

    And the XSF awards you a _Veteran XMPP Developer_ medal

  38. moparisthebest

    they are just suggestions