XSF Discussion - 2017-10-03


  1. moparisthebest

    Link Mauve: 2017 hmm so is that Jan 7th 2020 or java.util.Date might see that as the 20th month of 2017 and therefore August 1st, 2018 not real sure what you mean there

  2. moparisthebest

    I'll... Let myself out

  3. Guus

    jonasw - can I merge that xep list pr?

  4. Guus

    (and fix the nginx config?)

  5. Guus

    it appears to be working for me, when running in docker

  6. jonasw

    Guus: I think so šŸ˜ŗ

  7. jonasw

    just waiting for someone to do it and fix tge nginx cfg. and confirm that it works šŸ˜ŗ

  8. Guus

    Merged now. Will do ngingx later today.

  9. jonasw

    \o/

  10. Guus

    ngingx config updated

  11. Guus

    looks good

  12. Guus

    thanks jonas!

  13. jonasw

    \o/

  14. jonasw

    then I can finally send the update mails :D

  15. mathieui

    jonasw, now we only need to translate the ~256 terminal colors to CbCr

  16. jonasw

    mathieui, I think I put some wording in there on how to match an existing palette

  17. mathieui

    yeah

  18. mathieui

    still needs to map to the values :p

  19. jonasw

    not sure what youā€™re asking

  20. jonasw

    mathieui, is something missing?

  21. mathieui

    nope

  22. mathieui

    not in the XEP

  23. mathieui

    (but I need to make a 256color CbCr palette to match against)

  24. jonasw

    I have some code for that somewhere

  25. jonasw

    but I first need to prepare some updates which were discussed here.

  26. pep.

    Where can I find documentation about MSN (the MUC one)

  27. Zash

    '45?

  28. pep.

    hmm, yeah.. I wasn't looking for the correct keyword

  29. Zash

    There may have been something on the wiki, look there

  30. mathieui

    thereā€™s https://wiki.xmpp.org/web/Multi-Session_Nicks

  31. pep.

    "Multi-session nicks are not currently defined in this document."

  32. pep.

    mathieui, thanks

  33. Zash

    It boils down to "implementation detail/policy" right?

  34. pep.

    https://github.com/jsxc/jsxc/issues/577#issuecomment-314475666 this is BS right? I understand not recognising others in semi-anonymous MUCs, maybe, if one doesn't keep track of who's who, but not self

  35. jonasw

    pep., it applies as long as you donā€™t share the same nickname

  36. pep.

    Ok, so it can be done if one uses MSN?

  37. jonasw

    yeah

  38. pep.

    worksforme

  39. jonasw

    if you use MSN itā€™s probably tricky to *not* see the messages as from self :)

  40. pep.

    heh

  41. pep.

    And MSN would only be required in semi-anon rooms right

  42. pep.

    There's no problem in non-anonymous rooms

  43. jonasw

    not sure

  44. jonasw

    but yeah

  45. pep.

    Well you see realjids

  46. jonasw

    yeah

  47. pep.

    rr I always mix [] and () for links in github

  48. jonasw

    is that the webchat with the XSS vulnerability?

  49. zinid

    pep.: write a few tens of posts everyday on github and you'll be fine :)

  50. pep.

    jonasw, I don't know I don't use it, a user of movim just linked to that issue though

  51. Link Mauve

    ā€œ11:43:33 jonasw> is that the webchat with the XSS vulnerability?ā€, is there a webchat without XSS vulnerabilities? :p

  52. Zash

    Is there a web thing without?

  53. Kev

    elinks?

  54. Link Mauve

    My JS-less website with HTTPS and CSP enforced shouldnā€™t have any, hopefully.

  55. pep.

    I suppose Zash was talking about client apps

  56. pep.

    I suppose Zash was talking about client apps, Kev

  57. mathieui

    Link Mauve, letā€™s not forget your CSS-less website

  58. Link Mauve

    Of course, it looks better that way.

  59. Zash

    I mean the amount of warnings you get if you throw some of those web vuln scanners at a static text file served over http is staggering

  60. pep.

    mathieui, the best of all worlds :P

  61. pep.

    He should just serve txt

  62. Link Mauve

    pep., I would serve it over gopher, but browsers lately have been shutting that down. :(

  63. MattJ

    :(

  64. jonasw

    Link Mauve, yeah, itā€™s a shae

  65. jonasw

    Link Mauve, yeah, itā€™s a shame

  66. jonasw

    I even wrote a gopher server when I learnt about it :)

  67. Zash

    Where's my mod_gopher

  68. intosi

    Zash: removed due to overwhelming popularity, mod_http got jealy.

  69. Guus

    Kev: any news on the getting-scam-access-to-twitter front?

  70. Kev

    It seems I was wrong and I don't have the Twitter password. I'll try to remember to chase someone who has it (bear, I think).

  71. Guus

    ah, to bad.

  72. Tobias

    yeah.. bear gave me twitter access at least

  73. Tobias

    via tweetdeck

  74. Kev

    Yeah, I don't want tweetdeck access, I actually want the password :)

  75. Tobias

    yeah..everbody wants that :P

  76. mathieui

    recovery email is bo***@x***.***

  77. mathieui

    so, @xmpp.org

  78. jonasw

    probably board@ :-)

  79. mathieui

    then asking for a reset should allow anyone in board to take control and give the password to Kev

  80. Kev

    Or just wait for bear to respond and send me the password :)

  81. SamWhited

    I get so frustrated with thoseā€¦ every time something says "do you want to send an email to s**@samwhited.com?" ā€¦ *facepalm*

  82. mathieui

    SamWhited, secret email!

  83. Ge0rG

    Isn't board@ members only?

  84. Zash stumbles upon the xep-377 thread

  85. Zash

    Was there any conclusion in that?

  86. SamWhited

    What was the 0377 thread? I remember it happening (I think I started it), but as usual can't find it nowā€¦

  87. SamWhited

    Oh, or maybe the discussion happened on the thread where it was deferred and I was just glancing right over it thinking that was a different thing.

  88. SamWhited

    Zash: I don't think there was a resolution, but the resolution in my mind is that I rename it "blocking reasons" or something. The "dependency" it introduces that people are complaining about is intentional, and I think forces a good user experience so I'm not keen to break it.

  89. SamWhited

    or just merge it into 0191.