XSF Communications Team - 2025-02-07


  1. emus

    I think thats much better as a blogpost

  2. emus

    Hi, someone with access to the fosstodon account boosted a message on.software comparision. was it a mistake by myself?

  3. cal0pteryx

    I did that (on purpose)

  4. emus

    Lets rather stay away from Boosting etc. It puts more load overtime we cannot manage at the moment. Furthermore, Id rather prefer to make own posts on the services we have.

  5. singpolyma

    Isn't boosting rather less work than posting? While still providing value to followers (if the boosted content is useful of course)

  6. cal0pteryx

    emus: I disagree. It shows involvement, and creates no overhead.

  7. MattJ

    Agreed, I don't see any problem with boosting relevant posts

  8. MattJ

    Especially those by community members that would be of interest to people following @xmpp

    👍 2
  9. emus

    But what we boost, what not? If start so people expect we do it. We don't have the resources for this either.

  10. arne

    > Especially those by community members that would be of interest to people following @xmpp 👍

  11. Kris

    Up to the person(s) managing the account? Seems like a rare occurance anyways and better to allow it than have a blanket ban for no real reason.

  12. Kris

    (This is how we do it for the joinjabber account)

  13. singpolyma

    I'm not sure what resources would be required here? You mean if people start asking for boosts? Obviously if people start asking for it the correct solution is to ignore them, as that's not an appropriate thing to do generally

  14. emus

    When people ask for it they get their own posts. like today

  15. emus

    Well, if you have all the time we can expand our resources maintaining the accounts. Im not saying it should not be done, Im saying it comes with higher efforts over time. One also need read through hundreds of messages to check on every login.

  16. emus

    I think.the Newsletter can be merged. just check for the publish date

  17. gnemmi

    You mean s/05/07/ I'm the header?

  18. gnemmi

    I can do that right now if you want me to

  19. gnemmi

    date: 2025-02-05 -> date: 2025-02-07 ?

  20. emus

    yes

  21. emus

    because then the feeds catch it correctly

  22. emus

    and sorting

  23. gnemmi

    done

  24. gnemmi

    https://github.com/xsf/xmpp.org/pull/1476/commits/d4a1a28e0e8ce788534ff7a64e47177e10d18e62

  25. gnemmi

    also fixed 2 typos

  26. gnemmi

    > You mean s/05/07/ I'm the header? I really hate the bloody dictionary on my phone .. s/I'm/in/

  27. emus

    gnemmi: Do you have a question still?

  28. emus

    Can someone merge it?

  29. gnemmi

    Nope .. not really .. I did as much as I could .. I mean, some things could've eluded me, but all in all there's so much that I can do on my own after all.

  30. gnemmi

    I whish I could've worked on the Summit blog post. But in all honesty, I wasn't even there. It was my first ever Summit and I was only able to attend it remotely. I wasn't even there .. so I really wouldn't know where to start if I wanted to turn the 27th Summit summary into a full blog post. And that was the only reason why I didn't pick up that gauntlet. 🥺

  31. gnemmi

    I whish I could've work on the Summit blog post. But in all honesty, I wasn't even there. It was my first ever Summit and I was only able to attend it remotely. I wasn't even there .. so I really wouldn't know where to start if I wanted to turn the 27th Summit summary into a full blog post. And that was the only reason why I didn't pick up that gauntlet. 🥺

  32. gnemmi

    I still feel sorry about that 🙁

  33. emus

    gnemmi: All fine, we will manage

  34. emus

    Dont be sorry

  35. gnemmi

    > gnemmi: All fine, we will manage We surely will!