diff --git a/content/blog/posts/2024-10-18_introducing-QChat-chat-rooms-in-QGIS.md b/content/blog/posts/2024-10-18_introducing-QChat-chat-rooms-in-QGIS.md
index d402e57..db99364 100644
--- a/content/blog/posts/2024-10-18_introducing-QChat-chat-rooms-in-QGIS.md
+++ b/content/blog/posts/2024-10-18_introducing-QChat-chat-rooms-in-QGIS.md
@@ -149,6 +149,8 @@ Note that:
 
 We've seen the client side of QChat in QGIS. To route the messages through WebSockets, there’s also a backend. [The GitHub repository is available here](https://github.com/geotribu/gischat).
 
+The question might be: why is it not based on a chat standard, like `xmpp` or `matrix`? This is a good question: following the [KISS](https://en.m.wikipedia.org/wiki/KISS_principle) principle, we developed this backend quickly with Qt's websocket availability in QGIS, in order to make it as simple as possible using some trivial message. Making the plugin compatible with a chat standard is under consideration and will probably represent the next consistent step.
+
 ### Set up your own instance
 
 If you'd like to set up your own QChat backend, [you can follow the instructions on the repository](https://github.com/geotribu/gischat#deploy-a-self-hosted-instance). There's no need for a database, as it’s stateless and simply relies on WebSockets. It’s a [simple Docker image](https://hub.docker.com/r/gounux/gischat) that runs with a few environment variables.