XSF Communications Team - 2021-04-07

  1. MattJ

    Licaon_Kter, sorry, 4th/5th time of what?

  2. Licaon_Kter

    Snikket announced :) or is it that it wasn't announced "on that site" yet? :)

  3. MattJ

    Your link is the first announcement I ever wrote, over 12 months ago

  4. Licaon_Kter

    Oh, nvm me....I read April but the wrong year...sorry

  5. Licaon_Kter

    This was linked from a random Fedi post

  6. MattJ

    As for Snikket iOS, yeah, I'd have liked it to be out sooner

  7. Licaon_Kter

    Where's the holdup? Tigase, you or Apple?

  8. MattJ

    We're finalizing the work that's required before release

  9. MattJ

    A bit of everything (except for Apple)

  10. MattJ

    The plan was always to do the work in two halves (the first was OMEMO and some other stuff), the second half of the work hasn't happened yet

  11. MattJ

    It was going to be decided partly based on feedback from the beta testers, which has now happened

  12. Licaon_Kter

    You have 2-3 months of beta iirc What's the second part? Is Push solved? MUC push?

  13. MattJ

    and it will include a chunk of UX work, which is harder to specify to Tigase than "Implement OMEMO for MUC, kthx"

  14. Licaon_Kter

    _(sorry to OT)_

  15. MattJ

    Push is already solved, MUC push is 95% there - I've just been too busy to fix the remaining 5% (which would happen server-side)

  16. MattJ

    It will be fixed before the release

  17. MattJ

    and yeah, just realised this isn't the Snikket MUC... just woke up :)

  18. Licaon_Kter


  19. edhelas


  20. edhelas

    not sure about that move

  21. Licaon_Kter

    edhelas: there's a good thread here: https://nitter.snopyta.org/mcclure111/status/1379504328336097284 But were offtopic here

  22. emus (XSF Com. Team)

    edhelas: But I dont think we should post that directly

  23. edhelas

    no no, it's just to inform you, might help us to communicate and prepare things if we have some people that wants to migrate to other solutions

  24. Sam

    Might be worth someone here responding to: https://drewdevault.com/2021/04/07/The-next-chat-app.html

  25. Sam

    He *hates* XMPP IIRC so he didn't even mention it, but it mostly meets all the requirements he's talking about.

  26. Sam


  27. emus (XSF Com. Team)

    Well if he hates XMPP and does not even mention it knowingly, how should we convince him=

  28. emus (XSF Com. Team)


  29. Sam

    Yah, I don't know, that's why I bring it up here. It might not be about convincing him personally, but convincing others in the comments too.

  30. Sam

    Or maybe it's not worth it because he'll just get mad and shut down the conversation, I really don't know.

  31. emus (XSF Com. Team)

    (Our tweet for the Newsletter actually: https://nitter.nixnet.services/xmpp/status/1379503198352900102#m many thanks to whom it posted!)

  32. emus (XSF Com. Team)

    Sam, if you want we can try to update the website and point out those arguments?

  33. Sam

    I really don't know what's best, I just saw the post and was thinking out loud to see if others had any ideas :)

  34. Sam

    Maybe our own blog post would be a good idea? I could try to write something up this weekend

  35. Licaon_Kter

    @sir hates anything not IRC, then again XMPP (biboumi actually) is a good IRC citizen I heard, his Matrix complaints are against their EEE strategy that forces broken bridges onto IRC (and XMPP for that matter)

  36. Licaon_Kter

    > Sam, if you want we can try to update the website and point out those arguments? Sounds more adequate, in the myths section?

  37. Sam

    I don't think he really says anything about XMPP that would work in the myths section, but positioning XMPP as a thing to use instead of signal seems good (not that we can actually compete at all in terms of usability, but using this bitcoin thing as a way to drum up support for XMPP could be good)

  38. nicola

    > (Our tweet for the Newsletter actually: https://nitter.nixnet.services/xmpp/status/1379503198352900102#m many thanks to whom it posted!) Tks, already RT and Twitted mentioning @xmpp :-)

  39. Licaon_Kter

    Sam: yes, but this needs a more general feel than being _a reaction_ to every blog post somewhere

  40. Sam

    Licaon_Kter: yah, I was thinking it could be a thing about how XMPP wouldn't have some of the same problems as signal? Signal got a huge boost when whatsapp changed its TOS recently, maybe we could do the same thing and catch some of the people bailing from signal?

  41. Sam

    I dunno, maybe I'll just try to write something this weekend, I don't know if it really needs a response or not though.

  42. Licaon_Kter

    Sam: I feel we already answered back in January... https://xmpp.org/2021/01/instant-messaging-its-not-about-the-app/

  43. Licaon_Kter

    Sam: I feel XMPP already answered back in January... https://xmpp.org/2021/01/instant-messaging-its-not-about-the-app/

  44. Sam

    I'm thinking a current reaction to the signal thing, or maybe just a reply to point people at XMPP to the specific post I linked about it would be better.

  45. Sam

    Better than just having an older post I mean. We shoudl always be generating content.

  46. Licaon_Kter

    He closed his Fedi, if you find how to access that mailing list used for blog reaction, see if any XMPP answers too

  47. Sam

    yah, I'll keep an eye on it or possibly respond at some point.

  48. Sam

    https://lists.sr.ht/~sircmpwn/public-inbox, FWIW

  49. Sam

    If anyone has time to proof read, this is a first draft of a reply to that article just to get his list followers thinking about it: https://gist.github.com/SamWhited/bd4ae0c6b5c406f1d40593280a23066f

  50. Sam

    I think it might also be reasonable to have a blog post specifically targeting the Signal changes, but that can come later.

  51. Licaon_Kter


  52. Sam

    Cool, calling it "good enough" then since it's just a quick reply to a post :)

  53. Sam


  54. Sam


  55. Sam

    Cue a flood of people replying with how stupid this is, but at least I put XMPP out there as an option :)

  56. emus (XSF Com. Team)

    Hey Sam, thanks for the effort! I actually got you response wrong, as I thought you wanted to write an entire blog post to this. So such a reply is fine of course! Please ignore people nothing else to do than blameing you rpost

  57. Sam

    emus (XSF Com. Team): oh no, I want to do both :) a blog post would more be targeted at the signal thing, not just this post

  58. emus (XSF Com. Team)

    Actually we already covered this with the previous blog post, as its actually the same issue

  59. emus (XSF Com. Team)

    I would prefer to adjust the myth page or so

  60. emus (XSF Com. Team)

    --> anyway, if you would like to write a blog post, is fine

  61. emus (XSF Com. Team)

    I support it (unfortunately I dont have time or a big idea what to write)

  62. emus (XSF Com. Team)

    how can one read the entire thread on this page? 😀

  63. Sam

    I agree the topic is covered, I just think it helps to respond directly to the signal one and position ourselves as an alternative.

  64. Sam

    I think the thread will appear on that page when there are any other replies :)

  65. emus (XSF Com. Team)

    ok, I was looking for the flood of people you mentioned

  66. Sam

    Oh no, that was in anticipation of tons of angry messages about how bad XMPP is :)

  67. Sam

    I don't know how many people actually follow this list

  68. Sam

    I just know this guy has a pretty big following in general

  69. emus (XSF Com. Team)

    ah ok

  70. emus (XSF Com. Team)

    who is he?

  71. Sam

    Sourcehut, KnightOS, Gemini, etc. he just makes a bunch of random small projects that have kind of a cult status

  72. Sam

    Oh, and he wrote large chunks of Wayland

  73. emus (XSF Com. Team)

    ah ok, well not bad

  74. Licaon_Kter

    Sam: let it go, you had your say... let Drew do his own research :)