XSF Discussion - 2020-02-21


  1. Ellenor Malik

    Kev: use a dns challenge

  2. dwd

    Daniel and Guus's emails on '198 almost made me spit my tea over my keyboard.

  3. dwd

    But also, yeah, Pando is 100% mobile at the moment and uses 198 resumption because Hospital Wifi is even worse than Guus's parents'.

  4. Kev

    That sounds like a pretty unanimous "I should be using DNS challenges". I'll look into it when I have some cycles - which is certainly not this week. Today is "playing Gloomhaven all day before doing night two of the show" day.

  5. jonas’

    Yes, you should be using DNS challenge

  6. Kev

    đź‘Ť

  7. Ellenor Malik

    Jeans

  8. Guus

    dwd, if Pando is interested in selling my Parents' wifi to their customers as an upgrade, let me know.

  9. jonas’

    I wonder what would happen if I made a MUC roon service *send* a presence-join to another MUC room

  10. jonas’

    from playing the scenario in my head, this might end up with a very bare bones bridge between the rooms

  11. jonas’

    all messages from the respectively "remote" room will appear under the same nickname

  12. fippo

    dmuc or fmuc probably have lengthy xml examples for that

  13. jonas’

    are they based on that pattern?

  14. Zash

    Yes

  15. Zash

    At least one of them

  16. jonas’

    interesting

  17. jonas’

    I'd like to have a read-only aggregate feed of all the XSF MUCs and I was wondering on how to implement that

  18. Guus

    jonas’ what you're suggesting would affect all users of the MUCs. Maybe aggregrate through archiving instead?

  19. Zash

    Poll MAM? Hm

  20. jonas’

    Guus: sure, I didn't mean to *implement* it that way

  21. jonas’

    it just crossed my mind while thinking about iz

  22. jonas’

    it just crossed my mind while thinking about it

  23. Guus

    like fippo, what you suggested made me think of XEP-0289

  24. Guus

    should be feasible.

  25. dwd

    jonas’, Don't you end up with FMUC, sort of?

  26. dwd

    jonas’, But also, it's unclear to me you could hold an archive of someone else's room within GDPR. Looks very sketchy on that basis.

  27. moparisthebest

    so just have someone in US or UK do it

  28. dwd

    moparisthebest, UK is covered by GDPR anyway, but besides, it's not quite the point.

  29. Guus

    mopar might be referring to a news snippet that I've read this morning

  30. dwd

    Guus, Google thing? Yeah. Unclear WTF is happening as usual.

  31. Guus

    something about the <something> moving data from ireland to the US to no longer need to be compliant with privacy legislation post brexit.

  32. dwd

    Guus, But for now, at least, DPA-2018 covers us for GDPR under the same regime as GDPR.

  33. moparisthebest

    laws aside, I'm not sure how someone can post something in a public channel open to anyone and reasonably assume one of those members might not keep+share it

  34. jonas’

    dwd: if the room is public I don't see a gdpr issue

  35. jonas’

    the data was "manifestly made public" IMO

  36. jonas’

    also, I'd probably only keep archives for sync purposes and otherwise only relay live data

  37. moparisthebest

    that seems right, room owner is making it available for download for anyone on the internet to grab already

  38. dwd

    jonas’, Would it still be subject to a SAR, etc? I think probably, and in addition, correction rights etc might exist.

  39. jonas’

    dwd: probably. hence only keep sync archives

  40. jonas’

    then there is a technical reason for non-deletion and correction can be done by the user through (ab-)use of LMC

  41. jonas’

    do folks think it’d be useful to announce editor messages in this channel, too? (in addition to standards@)

  42. lovetox

    jonas’, do you plan changes on the muclumbus http api?

  43. jonas’

    lovetox, no

  44. lovetox

    great

  45. lovetox

    and the xmpp api will migrate to the xep you just propsed i guess?

  46. jonas’

    yes

  47. jonas’

    does anyone know if we (Editors) need Board and/or Council Approval for this? https://github.com/xsf/xeps/pull/896/files

  48. Guus

    I don't know, but I'd be surprised. This is a change to tooling, not so much to published specifications.

  49. jonas’

    it’s changing how we suggest people write their XEPs tho

  50. jonas’

    xep-template.xml is a suggestion

  51. Guus

    sure - but it doesn't affect the actual process of acceptance of the XEP.

  52. Guus

    for that, we still have Council.

  53. Guus

    Do previous changes to that file make reference to approval of anyone?

  54. jonas’

    nope

  55. MattJ

    Go for it. If you want a clear conscience, just post to standards@ about the update

  56. jonas’

    going for it

  57. jonas’

    done & done