XMPP Service Operators - 2019-08-18

  1. morgan

    xmpp:suicide@conference.conversations.im?join

  2. Licaon_Kter

    morgan: why the sad muc?

  3. morgan

    Im feeling so bad

  4. morgan

    aj: ok

  5. tom

    >Conversations has a grant at the moment for implementing A/V, and some money comes in from commercial requests That's good. Curious which orgranizations are requesting jingle in their conversations

  6. pep.

    tom, they're probably not requesting Jingle but A/V

  7. tom

    is there a difference

  8. pep.

    Sure. Jingle is an implementation detail

  9. pep.

    Only the end result matters to them I'm sure, that A/V works

  10. tom

    speaking of adding av support to things

  11. tom

    How difficult do you think it would be to fork Gajim 0.16.9 and replace the dependence on gstreamer-0.1 and libfarstream with ffmpeg?

  12. tom

    another thing that could be useful is reworking session management to use elogind rather than python-gnome2

  13. tom

    that way it should be WM agnostic and work fine with i3wm etc

  14. tom

    It's something I've been thinking about for a while now since gajim 1.X is only buildable against the gtk3 graphical toolkit, (which I and many other people I know find untolerable on a desktop) and replaces menus/icons with hamburger buttons

  15. tom

    forces animations, bezels etc and keeps breaking it's api

  16. tom

    me and a few others have masked updating to the gajim 1.x series until we figure something else out.

  17. tom

    unfortunately it doesn't look like psi+ fills those needs or any other XMPP client that I know of

  18. tom

    and Gajim 0.16.X being pretty much perfect already minus the dependence on deprecated libs for jingle extensions

  19. tom

    I can program in python just fine, but most people I know are not programmers

  20. tom

    and the Gajim 0.16.X code...... needs some cleanup

  21. tom

    and uses one letter variables which I'd have to figure out what it really is and fix.

  22. tom

    It's not like similar projects haven't been completed in the path. There was a drastic need for a plain old SIP softphone because sflphone somehow morphed into a giant multi-hundred megabyte blob with support for like 2 different p2p networks

  23. tom

    and linphone became some sort of android-to-linux port even though it started out as a workstation program. weird. It's like they kept re-writing the whole thing from scratch every major release until the thing was practically a different program

  24. tom

    because of this some guy decided he had enough and hunkered down to patch up TwinklePhone to build on modern systems

  25. tom

    and now a lot of people connecting their SIP telephone service use Twinkle