On 8/21/25 19:34, Olivier Dion wrote:
Regarding your comment on Discourse. Why do you think it would be a bad
choice? I don't know nothing about it but it seems like it's poppular
for open source communities.
It even has a emacs mode.
It is irritating for me, that for displaying static text I need to allow the
site to run JavaScript. These forums always feel sluggish to me. As far as I
know, one also needs to take precautions to make discourse searchable via search
engines. That may or may not be easy to do. When I see someone in an issue on
some git hoster tell me "Why don't you ask on our (discourse) forum?" I am
getting ready to grind my teeth, because why didn't their forum and the
potential answer to my question show up in a search result? And I definitely
don't want to have to create another account, just to be able to read the
friggin issues on their mandatory login forum, instead of a git hoster.
I also rarely see a discourse forum, that is well structured and gave me a good
overview of its hierarchy of topics.
Often the JS is hosted elsewhere, requiring me to allow third-party sources to
run in my browser, which is even worse than first-party JS. Usually people who
set up such contraptions do not shy away from trying to load some trackers as
well. Granted, with any GNU project, I don't think I need to fear someone doing
that, because that's not what GNU stands for, but the other points still stand.
I would expect of a forum, that every page or view is
linkable/bookmarkable/sharable with other people. A unique URL for each thing in
the forum. Each topic, each comment, each user profile, ... A JS app style of
forum, or SPA, or whatever you wanna call it usually struggles with that,
because it requires to take extra precautions. Similar for all standard browser
actions like going back and forth, right click context menus and so on.
--
repositories:https://codeberg.org/ZelphirKaltstahl
