XSF Communications Team - 2022-04-26


  1. MattJ

    emus, what's the best email address to contact you regarding commteam stuff? (want to forward you an email received to info@xmpp.org)

  2. emus

    Its not directlt a role out of commteam I recommend to reply to the mail I wrote from. But to answer your question: xsfcommteam@protonmail.com

  3. emus

    MattJ:

  4. emus

    so what ever is fine. but I dont get forwards to my private mail

  5. MattJ

    I'm not talking about the email you sent to info@, but an email received from someone else that is relevant to commteam

  6. emus

    Ah alright! yes please

  7. emus

    but if you cc the other mail I would be very happy ☺

  8. pep.

    protonmail? You know you could get your own @xmpp.org address certainly :p

  9. pep.

    Well especially since you're not the only one in commteam

  10. Licaon_Kter

    Ain't PGP dead? :)

  11. pep.

    ?

  12. MattJ

    pep., the problem is we don't run IMAP at xmpp.org, everything there is an alias/mailman, and commteam wanted to be able to send/receive email from a specific address, hence the 3rd party

  13. pep.

    :/

  14. MattJ

    i.e. we don't actually host any email *accounts*

  15. singpolyma

    MattJ: could still allow sending mail there, no? IMAP is just for storage/retrieval

  16. pep.

    Technically there still needs to be an account but yeah no IMAP indeed. The mail needs to be sent from the machine that has authority over the domain so receiving SMTP entities can have their various checks pass

  17. MattJ

    singpolyma, sure, but at the time there requirement was send+receive

  18. pep.

    Receive can be an alias

  19. MattJ

    We still don't have that ability for the newsletter, apparently

  20. pep.

    stil

  21. pep.

    still

  22. pep.

    Senders would have to go through hoops to be able to use it properly though :/

  23. pep.

    (That is for example, including the alias in every outgoing mail so everybody in the alias sees what's happening. Kind of a weird trick because of no IMAP :p)

  24. pep.

    But if it were just one person behind it might work ok

  25. emus

    pep.: the proton account I took over from you guys 😅 and yes, I requested that several times but was not interest to do it so far

  26. singpolyma

    pep.: That's how my while company does everything (cc the team alias on replies). Last thing I would ever want is a second IMAP to check, muh nicer to have stuff forwarded to me. Of course everyone has their own preferred workflow, but it works well for us :)

  27. singpolyma

    pep.: That's how my whole company does everything (cc the team alias on replies). Last thing I would ever want is a second IMAP to check, muh nicer to have stuff forwarded to me. Of course everyone has their own preferred workflow, but it works well for us :)

  28. singpolyma

    pep.: That's how my whole company does everything (cc the team alias on replies). Last thing I would ever want is a second IMAP to check, much nicer to have stuff forwarded to me. Of course everyone has their own preferred workflow, but it works well for us :)

  29. MattJ

    emus, interest in what, exactly? Aliases/forwards have always been available, just an actual email account is not (and that is not going to change any time soon)

  30. pep.

    Talking about infra, what happened to contracting somebody?

  31. MattJ

    Our main priority right now is that the server that all this is running on is 2003 hardware with an OS that needs an upgrade but there's no guarantee that the newer OS would boot on that machine (we already have that problem with at least one other server in the "fleet").

  32. singpolyma

    MattJ: it's an owned server?

  33. MattJ

    Right now I think it's up to Board to choose between seeking a sponsor of new hardware, purchasing a new machine, or switching to VPS

  34. MattJ

    singpolyma, yes, the XSF has several dedicated servers which have been donated or purchased

  35. MattJ

    I think at this point the one handling the mail is our oldest that's still alive

  36. singpolyma

    And then paying for rack space or also donated in someone's cage?

  37. MattJ

    But some of them have changed hostname during the years, so it's hard to keep track

  38. MattJ

    We have a donated rack at USSHC

  39. MattJ

    (shared with jabber.org, which is technically not an XSF thing)

  40. singpolyma

    32bit I guess, is that the main hw compatibility issue?

  41. MattJ

    32bit, and concerns about whether it can boot from a partition not in the first 1024 sectors (we believe yes, but there's only one way to know for certain...)

  42. MattJ

    A long queue of yaks reside in this infrastructure

  43. MattJ

    and I really regretted moving the website to a VPS a year or two back (it costs more $, but less time in the long term)

  44. MattJ

    and I *haven't* really regretted moving the website to a VPS a year or two back (it costs more $, but less time in the long term)

  45. MattJ

    Which is why I resist adding more self-hosted/self-managed stuff to maintain unless it's strictly necessary

  46. singpolyma

    Yeah, I don't mind my dedis but if the hardware gets old it's a few clicks to bring up a new one. Owned hardware is not something that has tempted me too much yet 😅️

  47. singpolyma

    The website is all static isn't it?

  48. MattJ

    I think back in the olden days when we were younger, before cloud and VMs were everywhere, if someone said "I have a server going spare, want it?" was not something you'd turn down

  49. MattJ

    Yeah, the website is all static these days

  50. pep.

    Tbh I could probably get you hosted in a squat somewhere if you wanted :P

  51. MattJ

    Sounds reliable ;)

  52. pep.

    That's overrated :P

  53. pep.

    Especially when we're hosting websites on solar power nowadays! (https://solar.lowtechmagazine.com/)

  54. pep.

    And email's got a 48h tolerance so it's all good :P

  55. singpolyma

    MattJ: right, so barely even needs VPS, could do it on anything. Email could do a-la-carte (either at a mail host or get some shlub like me to donate email server infra). I'm not saying you should do this per se, I'm just thinking out loud :)

  56. pep.

    As a selfhoster myself I'd rather not have the XSF go full third-parties (cloud and whatnot). I think that's a line we should not cross and I'd have the XSF pay for this not to happen.

  57. pep.

    There's already github, the thing for the agenda, gcalendar also, gdrive, the newsletter thing that's fortunately going away(?), and many others I'm forgetting?

  58. singpolyma

    pep.: it's third parties all the way down, though. Even currently the rack/cage/datacentre are third party. Putting the website on sourcehut pages (as an example) means you don't get to walk into the cage, but that would be true with a VPS too. It means someone else has root, but that's also true with the VPS, or even the current infra (physical access being root and all that)

  59. pep.

    singpolyma, I meant, just owning the domain and not the data. Yeah surely a VPS is already an abstraction and I'm compromising here

  60. pep.

    Not asking the XSF to get its own datacentre

  61. singpolyma

    pep.: it *has* it's own datacentre. We're wondering out loud if that's bad

  62. pep.

    It doesn't, it has its own hardware in someone's datacentre :p

  63. MattJ

    pep., the question is, where do you draw the line, and how do you decide that?

  64. MattJ

    I'm a self-hoster too (obviously), but it also has to be recognised that there are (often hidden) costs of self-hosting, and sometimes they aren't worth it

  65. MattJ

    So these have to balance against the problems with dependencies on third parties

  66. MattJ

    and I suspect the balance may shift depending on the service

  67. pep.

    We draw the line where we want to draw the line, but it has to be in line with the direction the XSF takes. I'm sure atm many people in the XSF wouldn't care because first they don't want to take care of the infra, and second they're part of this ideology and they're happy to give everything away and it's not an issue for them if the XSF reflects this

  68. pep.

    I'm not

  69. singpolyma

    Like, XSF could hire a contractor to run a mailserver. Or pay migadu. These seem effectively equivalent to me

  70. singpolyma

    It's only "self hosting" if you have a "self"

  71. pep.

    Self is the XSF? What else

  72. singpolyma

    XSF isn't a self, it's a comittee

  73. pep.

    It's a self enough to me

  74. singpolyma

    if XSF hires a contractor is that still "self" ?

  75. pep.

    As long as the XSF owns the data, that's a yes to me

  76. pep.

    Now that this chat has gone this far we can take it to infra@ if necessary, or we can pause here, whichever :)

  77. pep.

    I was mostly curious at first

  78. MattJ

    *iteam@

  79. pep.

    Thanks I was looking for it

  80. emus

    > MattJ escribió: > emus, interest in what, exactly? Aliases/forwards have always been available, just an actual email account is not (and that is not going to change any time soon) I just meant the email discussion I raised some time ago. but is fine now

  81. emus

    pep.: Thanks - It think if we hire someone, then in iTeam instead of commteam

  82. pep.

    emus, I just said so.

  83. pep.

    Anyway I don't have much more to say about this topic and I'm not pesonally going to reanimate it over there. Just that I'd be sad that the XSF stops owning their data and that's where I'd personally draw the line because that's what I want the XSF to reflect. I want to encourage small self-hosted entities everywhere.

  84. pep.

    But I'm happy to debate on what "owning" its data mean. Just getting to talk about this would already recentre the debate anyway and that's good to me

  85. pep.

    fwiw, I'm annoyed about being told offtopic this or that. This discussion makes sense here because it's the continuation of another one and not everybody participating in is on the other channel

  86. MattJ

    I didn't see anyone say anything about off-topic until you did... ??

  87. pep.

    Ok that's how I interpreted emus' last message

  88. pep.

    But it's not the first time anyway

  89. pep.

    People seems to quickly draw the offtopic card around here and that annoyws me

  90. pep.

    People seems to quickly draw the offtopic card around here and that annoys me

  91. MattJ

    Okay, I have noted your annoyance

  92. pep.

    :P

  93. MattJ

    Maybe we should make a dedicate channel for that

  94. MattJ

    Maybe we should make a dedicated channel for that

  95. pep.

    Good

  96. Sam

    Annoyance is offtopic in this channel, please take it elsewhere. *pokerface*

  97. Sam

    (sorry, I couldn't resist)

  98. pep.

    :)

  99. emus

    > pep. escribió: > Ok that's how I interpreted emus' last message > But it's not the first time anyway No, it didnt meant offtopic. I just run with this account. Id prefer an xsf owned thing, but for that we would need more resources in iTeam. That's why I came to the same conclusion as you. but also dont know what to do here :/

  100. emus

    > pep. escribió: > People seems to quickly draw the offtopic card around here and that annoys me ?

  101. emus

    > Sam escribió: > Annoyance is offtopic in this channel, please take it elsewhere. *pokerface* > (sorry, I couldn't resist) oh c'mon...

  102. Licaon_Kter

    That's a meme already emus, embrace it :)

  103. emus

    Licaon_Kter: offtopic 😉

  104. Licaon_Kter

    👍

  105. MattJ

    https://xmpp.org/rfcs/ is finally working :)

  106. emus

    so nice - I will try to remind to tweet :-)

  107. emus

    wurstsalat:

  108. MattJ

    I left a longer comment on wurstsalat's iteam issue, but nothing major

  109. MattJ

    I also just added a redirect for /rfcs/index.shtml which was the old index page that hasn't been updated for a long time

  110. emus

    cool