XSF Discussion - 2014-03-02

  1. ralphm


  2. ralphm

    It appears we need to do a better job at explaining when people like Adewale keep spreading misinformation.

  3. Zash


  4. Kev

    I note that he links to an "Android not really XMPP" thread in which Google say that if only XMPP had resumption and EXI, it'd have been great.

  5. Kev

    I also wonder if, six years later, it's possible that the expense of zlib vs radio on a phone processor isn't the same as it used to be.

  6. Kev

    ralphm: Hopefully this satisfies your requirement of explaining stuff: https://plus.google.com/+AdeOshineye/posts/YbsTNU43rV9

  7. ralphm

    Kev: that's pretty good indeed.

  8. ralphm

    Kev: I've been thinking, for a while, that I wanted to do a series of blog posts on XMPP myths.

  9. Kev

    I wouldn't frame it in that way.

  10. Tobias

    yeah...a XMPP Mythbuster show :D

  11. Kev

    But yes, I was thinking that a blog post about how to use XMPP in ways that myth says it doesn't work would be good.

  12. ralphm

    There are many such misconceptions as I discovered over last few weeks, following Twitter mentions of XMPP.

  13. ralphm

    I'm open to suggestions for positive framing.

  14. Kev

    The other side is that this Twitter stalking of yours may help us work out areas we need to improve :)

  15. ralphm

    my biggests wishes: 1. good, pretty, native and energy efficient XMPP client with MUC support on every mobile platform. 2. working file transfer based on Jingle. 3. E2e encryption beyond OTR.

  16. ralphm

    I'm also excited about the push stuff

  17. fippo

    ralphm: i'll hopefully have a chance to look closer at datachannels + jingle filetransfer soon

  18. ralphm

    where 'datachannels' really doesn't have anything to do with webrtc except for using the same protocols for data transfer over udp, right?

  19. ralphm

    fippo: ^