[…]

Joined by XMPP-messengers Cheogram and Monocles, and supported by many contributing experts in the background, we are playfully addressing the no-billionaire-platforms challenge with webxdc, a container format and API for “chat-shared web apps”. Technically, webxdc apps are network-sandboxed HTML5 apps and instead of the HTTP protocol they use Peer-to-Peer send/receive APIs implemented by webxdc-capable messengers, rebasing relations between developers and users by saying

  • Bye Bye to surveillance capitalism: Users have both the code and the data of their web apps in their hands and benefit from end-to-end encrypted messaging not only during regular chat messaging but also during their private web app usage.

  • Bye Bye to user policing (logins, passwords, OAUTH, TOS and privacy policies etc.): Web app developers never obtain or touch any user data or user identities, and can have peace of mind of not being responsible for any data, and not having to program identity management and social discovery UIs. Messengers already provide it through arranging chat groups or rooms.

  • Bye Bye to depending on a corp or org that enshittifies: Messengers, as decentralized runners of webxdc apps in chat groups, can not hold web app developers, their users or data hostage. Consult Cory Doctorow’s “Ulysses Pact” for why this is a good idea.

This all sounds too good to be true, right? But what if another reality is possible by just stretching out our hands and grabbing it?

[…]

  • amzd@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    1 day ago

    They are apps that use a messenger as backend, so basically your conversation with someone else has all the state of the webxdc. In Delta Chat that would be the encrypted email thread.

    To use a webxdc share it in any of the mentioned messaging apps.

    • MalReynolds@slrpnk.net
      link
      fedilink
      English
      arrow-up
      12
      ·
      1 day ago

      Clear as mud. (I actually dimly get it, I’m a dev, but mere mortals will be clueless and move on). Farcaster is right, you need to define terms and give examples of actually getting this up and running, you’ve got way too much internal context that you’re not making explicit. Not an attack, trying to help, project sounds cool.

      • stringere@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 day ago

        The captain’s right, it needs to be more accessible to get started using it. 30 years in tech and I’m also only vaguely understanding due to undefined process and procedure. Great project and I hope to see it move forward.