Extending homeserver functionality with WASM #1364
Labels
A-Application-Services
Issues affecting the AS API
A-S2S
Server-to-Server API (federation)
feature
Suggestion for a significant extension which needs considerable consideration
Application Services are a great way to extend the functionality of a homeserver, however they are relatively heavy-weight and make deployments more complex the more we want to supercharge the homeserver as every new piece of "functionality" means manually configuring a new trusted appservice that requires its own process or a whole different server to operate properly.
I'm currently prototyping an appservice that acts like a shell, it doesn't provide functionality out of the box, instead it allows the admin installing WebAssebly plugins later on. We want to offer easy to deploy homeservers that are extensible and having to configure just a single general purpose appservice is already a great improvement but it would be more interesting if said plugin system could be more integrated in the homeserver to for example allow single binary deployments and reduce the overhead that comes with serializing and passing data between the homeserver and appservice.
Glad to hear opinions and thoughts about integrating a WASM runtime in homeservers :)
The text was updated successfully, but these errors were encountered: