@debacle @lascapi 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 https://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?
@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
@adbenitez @debacle @lascapi @larma 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.
@adbenitez @debacle @lascapi @larma 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.
@Goffi you can have multiple implementations/mini-apps of editors in webxdc and they will then be available in parallel in all clients, my point here is that as a XMPP client developer it brings you more to the table to just add support for #webxdc than having to implement some collaborative editor and whatnot into your app yourself
@adbenitez @Goffi @debacle @lascapi
Implementing WebXDC is not free and not easily possible for many clients.
I think WebXDC is more relevant when the chat identity is used within the WebXDC app and it's significantly tied to the chat room.
Some of the usecases presented already show issues when bound to a specific chat room. Calendar events and notepad are actually examples for that, as the boundary of the chat room will make these less user-friendly.
