There are a couple I have in mind. Like many techies, I am a huge fan of RSS for content distribution and XMPP for federated communication.

The really niche one I like is S-expressions as a data format and configuration in place of json, yaml, toml, etc.

I am a big fan of Plaintext formats, although I wish markdown had a few more features like tables.

  • 0x0@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    XMPP is very old

    Seriously? That’s your argument? So is the wheel.

    Requirement of permanent tcp ip connection doesn’t work well for mobile

    I was under the impression PubSub was created for that.

    Still, it’s an open extensible protocol.

    • endofline@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      2 months ago

      Seriously, if you do take one verse from the whole response, you get straw men you fighting with.

      I just told you that jabber / xmpp was created in the times almost nobody knew or believed mobile phones can be a thing. Thus it got created in that way: many similarities of xmpp and e-mail, irc or icq which didn’t stand the passage of time.

      Of course, you’re right xmpp evolved to get PubSub extension as an “optional feature” but because of its availability (or rather lack) - most servers didn’t support it even the client did support, xmpp didn’t win the acceptance of the end-users. It got some attention in the business world (cisco jabber) but not in the retail.

      Business cannot work forever without clients willing to pay or at least use, so it died off even in the business.

      End of story, try not to fighting with the straw men you created.

      • 0x0@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        Of course, you’re right xmpp evolved to get PubSub extension as an “optional feature” but because of its availability (or rather lack) - most servers didn’t support it even the client did support, xmpp didn’t win the acceptance of the end-users. It got some attention in the business world (cisco jabber) but not in the retail.

        That XMPP’s extensibility is in itself a strength and a weakness is indeed a valid argument, as you’ve exemplified. I was expecting you’d criticize OMEMO though…

        Business cannot work forever without clients willing to pay or at least use, so it died off even in the business.

        No, it didn’t die off, it’s still used. IRC is still used as well, probably more or less at the same level. But if you define usage as “used in business” well then probably just a few cases, yes.

        I hadn’t heard of Cisco Jabber but i’ve heard of Google and Facebook - both companies’ messengers were, initially, based on XMPP but they EEE’d it once they got enough users and walled their gardens, dealing a major blow to the protocol.

        End of story, try not to fighting with the straw men you created.

        Can i fight my inner daemons at least? Please?

    • MonkderVierte@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      XMPP is very old

      Seriously? That’s your argument? So is the wheel.

      They elaborated how that relates; usage scenario changed with mobile phones. XMPP is a bad match.