The "webxdc evolve" project is now official and was just announced from one of our early followers and advisers, @ansuz , but it's not just a boilerplate announcement! Ansuz dives deep starting from his yearslong cryptpad maintainership history, his early involvement in #webxdc up to the present and future .... Very good reading if you want to understand some.foundational considerations around evolving an end-to-end encrypted, decentralized web app platform ... https://cryptography.dog/blog/announcing-webxdc-evolve/
@lutindiscret@ansuz@matrix sure, matrix and also signal and others could support webxdc and benefit from it. As far as we can tell, however, they are unlikely to jump on it soon. Fwiw matrix has "widgets" with application-specific server side hosting (tied to business interests) ... Whereas webxdc apps can be added by users to chats without requiring any application specific server side hosting. Webxdc has no "integration" server like matrix needs as apps are written in a P2P paradigm.
@delta actually @matrix itself doesn't have widgets. Widgets only exists in @element. The specification work is abandoned (https://github.com/matrix-org/matrix-spec-proposals/issues/3803#issuecomment-1472194956) and send people to a chatroom. I asked there and got no answers. So I think, there may be room for #webxdc in matrix as it's an already existing standard with existing impl. Other clients could start on this standard without waiting for "widgets". IMO, widgets and webxdc are different and both are legit.
Add comment