XSF Discussion - 2021-01-20

  1. jonas’

    SamWhited, I seem to recall the XEP was full of suggestions for use, and then people complained that it had no business in the XSF and all that was moved to https://docs.modernxmpp.org/client/design/#auto-generated-colors

  2. Ge0rG

    jonas’: I wonder if we as the XSF can add a non-normative link to that URL with a short sentence along the lines of "An IM client implementation may use this approach to achieve consistency with other IM clients: "

  3. jonas’

    yes, I put that on my mental todo this morning.

  4. mathieui

    stp, on the whole coloring thing, looking at poezio, as we had a limited supply of colors available, the first way coloring was implemented on mucs was "more active users get more distinguishable colors", and that is an interesting take but ultimately it’s a pain in the neck for most people to adapt to

  5. Ge0rG

    mathieui: especially if it's inconsistent over time

  6. Ge0rG

    the xmpp.org XMPP server doesn't have IPv6 since October. Is that deliberate? Permanent?

  7. MattJ

    Not deliberate or permanent

  8. MattJ

    Oh, Docker?

  9. Zash

    Not Docker

  10. edhelas

    Docker doesn't support IPv6 ?

  11. Ge0rG

    IPv6 doesn't support Docker

  12. MattJ

    It disables it by default

  13. edhelas


  14. stp

    mathieui, The problem with that concept is that colors of users would change on-the-fly which isn't good.

  15. Zash

    Ge0rG, I don't see any problem with IPv6.

  16. Ge0rG

    Zash: I'm sorry, I was confused. Or rather, my local smokeping instance is confused and incapable of pinging xmpp.xmpp.org for $yak_reasons

  17. Ge0rG

    But well, maybe it's not a yak but a cat.

  18. Ge0rG

    Is there a special IPv6-related Schrödinger's Cat?

  19. jonas’


  20. mdosch

    | <- xmpp.org [s2sin55d0298c9cf0] (authenticated) (SASL) (encrypted) (IPv6) | -> xmpp.org [s2sout55d028db5c30] (authenticated) (SASL) (encrypted) (IPv6)

  21. mdosch

    My prosody claims to use v6 for s2s to xmpp.org…

  22. SamWhited

    jonas’: thanks, I hadn't seen that one

  23. Zash

    Possibly Jingle-related: I see there's a whole pile of RFCs published in the last few days, many seem related to video conferencing

  24. emus

    Still open for review or additional link suggestions: https://github.com/xsf/xmpp.org/pull/871

  25. marc

    Hard on mobile :D

  26. marc

    Hard to read on mobile :D

  27. emus

    marc, I understand. try "Files changed" one of the mid-ribbon tabs, then switch from raw view to preview

  28. emus


  29. emus

    hope this works

  30. mathieui

    emus, l39, " – and if not yet, it is open for your modification in the future - and if not yet, it is open for you to make modifications in the future to make it do what you need." ?

  31. emus

    yes, if forgot to change

  32. emus

    one told me yeasterfay

  33. emus


  34. emus


  35. emus

    Actually, is there any approval necessary for blog articles?

  36. Ge0rG

    emus: I wanted to read and provide some comments as well

  37. Ge0rG

    emus: ping?

  38. emus


  39. Ge0rG

    emus: how would you like feedback to the PR? GH comments? direct message? In here?

  40. emus

    I most appreaciate comments in the PR, but everything is fine what suits you best

  41. emus

    Anyone plan further feedback on the blog post?

  42. SamWhited

    I was going to ask if you wanted feedback on the English or if someone was planning on giving it a general editing pass before publishing?

  43. SamWhited

    I don't want to nitpick grammar and what not if it's not helpful

  44. Zash

    SamWhited, just do it!

  45. emus

    I dont know which native has been reading it yet, so that would be highly appreciated

  46. SamWhited

    I'll try to do a pass over it after work today then

  47. emus


  48. emus

    I see that link mauve has open several PRs with good improvements, may we have any volunteers being able to review or define necessary questions/actions? https://github.com/xsf/xmpp.org/pulls/linkmauve