XSF Communications Team - 2019-10-19


  1. vanitasvitae

    The heise article got updated. The recommendation is for Cisco Jabber now.

  2. vanitasvitae

    Maybe @xmpp could issue a statement/recommendation towards open implementations?

  3. emus

    vanitasvitae: please NĂ¿co But as always, stay polite & progressive

  4. emus

    we should mention this aswell in the newsletter?

  5. vanitasvitae

    Maybe something along the lines of "While we appreciate the EU Parliament taking control over their communications by using a self-hosted solution (Cisco Jabber is self hosted right?), we ask why not go a step further and chose a truely open system based on a truely open standard like XMPP?" with a link to xmpp.org's server software page plus maybe a link that clarifies the differences between Cisco Jabber and XMPP.

  6. vanitasvitae

    And maybe replace "we ask why not" with "we encourage them to".

  7. Martin

    vanitasvitae: Is there something official describing the differences?

  8. vanitasvitae

    I'd assume

  9. vanitasvitae

    AFAIK Holger once wrote something (unofficial?) but there should be more resources.

  10. emus

    > AFAIK Holger once wrote something (unofficial?) but there should be more resources. yep, if they really continue about that topic, the XSF CommTeam (!) should provide some more resources

  11. pep.

    vanitasvitae, technically, while I'm not especially happy with Cisco Jabber, we can probably still federate right?

  12. pep.

    But yeah they wouldn't have the same disparate^Wawesome experience as most XMPP users experience nowadays :)

  13. pep.

    But yeah they wouldn't have the same disparate^Wawesome experience as most XMPP users nowadays :)

  14. vanitasvitae

    Hm, is Cisco Jabber iOS actually useful? :D

  15. emus

    I think they (and others) should know what is what