Skip to main content


Hello there ! :)

Do you know if someone is working on use #webxdc in #matrix ?

Actually I wonder how how much it's the same as widget? πŸ€”

#deltachat and #xmpp can already use it ! 😁

in reply to 🌈 Lascapi ⁂

TTBOMK there is no #webxdc for Matrix yet, but even in #Jabber it is only available on two clients (#cheogram, #monocles), both on Android, but not any other OS. Let's see, if this changes at some point…
in reply to Debacle

we've talked a bit about that with @larma at last Berlin sprint.

I'm curious: what are the use-cases beyond mini-games?

If we look at webxdc.org/apps/ , it's mostly games or things that should be proper apps (e.g., editors) or implemented with a real protocol (e.g., calendar, encryption).

I'm willing to implement #WebXDC eventually, but mini-games are low on my priority list. What other use-cases or killer apps do you expect from this?

in reply to Goffi

sandboxed webapps that can have collaboration/multi-user features via constrained encrypted chat channel is more flexible and useful than integrating every app into the protocol/client because it is much more work for every client to implement such features, they are a project on its own, while by just implementing #webxdc support the clients benefits from apps that were even designed for other platforms

@debacle @lascapi @larma

in reply to adb

Beside the mini-games we've already mentioned as good use-case, all mentioned examples are better done in XMPP directly (and actually many exemples are already).

That was the main topic of the talk we had with @larma in Berlin: outside of mini-games, the use-case seems limited.

Note that I'm willing to implement #webxdc at some point, just that mini-games are low in my priorities.

in reply to Goffi

😯 what #XMPP client has "p2p" (encrypted without server knowing)
collaborative editor? even then how is better that every client has to implement every app itself that was my main point, XEPs are hundreds but the problem is implementation

@debacle @lascapi @larma

in reply to adb

the design of XMPP and specifications in general is actually that many implementations can be done. If you do a single implementation without specification, you can as well make a separated app.

Various implementations means better integration.

There is no P2P "editor" feature at the moment in XMPP, but it could be done with e.g. Jingle + shared XML.

This entry was edited (1 week ago)
in reply to Goffi

There is actually saros-project.org/ but that's a full code IDE synchronized via XMPP.
⇧