> As far as "web server", I think i know what you mean now, and admittedly I have my private matrix home server running behind nginx Sorry, I should have clari

> As far as "web server", I think i know what you mean now, and admittedly I have my private matrix home server running behind nginx Sorry, I should have clarified: when talking about "web" stuff, I meant hyperlinked HTML, intended for human consumption. Whilst sending/receiving HTTP is how most of these protocols work, at least parsing/printing JSON data in a standard format only presents quite a small attack surface, and can be set up "once and for all" (maybe tweaked as the standards slowly improve). It's quite another thing to be serving HTML, since it (like everything user-facing) tends towards bloat and churn (everyone has different tastes). That's fine, but it shouldn't require a server upgrade to fiddle with the UI (or complicating the server with dozens of configuration knobs that have nothing to do with its operation). In contrast, config files on disk are a safer way to perform admin jobs than accepting POSTs from the Internet, and using a separate client (dedicated, multi-protocol, bridging to another format, native or Web, etc.) means that the UI bloat and churn doesn't affect the server.