From 684aa20924c1d31d208b4c0c06eb6027a208aab4 Mon Sep 17 00:00:00 2001 From: gounux Date: Thu, 24 Oct 2024 11:24:47 +0200 Subject: [PATCH 1/2] blo(qchat) add paragraph --- .../posts/2024-10-18_introducing-QChat-chat-rooms-in-QGIS.md | 2 ++ 1 file changed, 2 insertions(+) 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..5c7e793 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 : 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. From 2e9a50827e1022bfc2520c740b1866ee67f40d87 Mon Sep 17 00:00:00 2001 From: Guilhem Allaman <40383801+gounux@users.noreply.github.com> Date: Thu, 24 Oct 2024 12:07:20 +0200 Subject: [PATCH 2/2] Update content/blog/posts/2024-10-18_introducing-QChat-chat-rooms-in-QGIS.md Co-authored-by: Julien Signed-off-by: Guilhem Allaman <40383801+gounux@users.noreply.github.com> --- .../posts/2024-10-18_introducing-QChat-chat-rooms-in-QGIS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 5c7e793..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,7 +149,7 @@ 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 : 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. +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