jdev - 2022-10-24

  1. selurvedu

    > A bit of optimism pep., a bit of shooting yourself in the foot

  2. flow

    I think I would prefer xaddr over xid, because it's more of an address than an ID (of course, every address shares the same semantic as an ID)

  3. debacle

    I'll stay with JID for this century.

  4. MSavoritias (fae,ve)

    xid sounds cooler 🤷

  5. pulkomandy

    There's room for having multiple names for different things that are all called jid currently

  6. pep.

    Yeah, whenever I can I actually don't use jid

  7. pep.

    (nor xid nor xaddr)

  8. pep.

    Too generic

  9. flow

    having multiple names for the same thing is a recipe for confusion. I think that is why jid will be around for a while (probably the whole century, as debacle oracled)

  10. edhelas

    > lovetox, Jappix and Movim both went for xid in their code IIRC, but I find it a bit weird since so much documentation is about JID. Doubts (x) ↺

  11. pep.

    Which markdown flavor are you using? I'm not sure I understand

  12. edhelas

    Movimdown

  13. Link Mauve

    Source: https://github.com/jappix/jappix/search?q=xid

  14. edhelas

    But not Movim :p

  15. Link Mauve

    I was wrong there.

  16. Link Mauve

    But it makes searching the code much worse than if the normal accepted term was used.

  17. MattJ

    Yeah, I'm not sure why anyone would replace it

  18. MattJ

    It's called what it's called

  19. debacle

    Like Jabber :-)

  20. edhelas

    What is Jabber ? 🤔

  21. Zash

    Nobody can be told what Jabber is, you have to see it for yourself

  22. moparisthebest

    Jabber is some really old crappy software owned and sold by Cisco right?

  23. moparisthebest

    Wow today I learned: https://en.wikipedia.org/wiki/Ethernet#Jabber