Should we enable the builtin chat? It kind of competes with our other chat channels. Try it out and discuss here.
- Yes
- No
0 voters
1 Like
I think chat should be enabled for only some categories like may be welcome or lounge. Otherwise it will compete with other support categories.
2 Likes
I think the chat is okay for a quick clarification, or pointing someone in need to a resource. For serious, long IM conversations, people should be re-directed to the Matrix rooms.
So my vote is “Yes, but…”.
1 Like
No unless we absolutely need it, or for developers only maybe?
Could be used in a quick pinch or discuss the forum moderation itself.
I believe it should be used only for the forum related matters, not KDE in general.
edit: Then again i do not have a dev hat so do what you will lol 
edit2: Just another realisation that if this is left public it adds more strain on moderating things.
1 Like
Moving something valuable from chat to this discussion…
@aronkvh pointed out that the chat is moving to matrix: Matrix protocol for chat - #13 by Falco - feature - Discourse Meta
This raises the tempting question: Can Discuss chat just be an interface onto the matrix chats we already use? If so, that would be a big win for user onboarding, while adding little-to-no new maintenance burden.
4 Likes
Having an additional chat system is going to create confusion and fragment communication.
Even if we set rules for how and when it should be used people aren’t going to follow them and it will be a mess.
7 Likes
Obviously we need to bridge the discourse chat into matrix 
No, I think we should have it disabled
Having an additional chat system is going to create confusion and fragment communication.
Yeah I gotta agree with this.
2 Likes
If it properly federates with Matrix eventually, I don’t really see the problem, since it just acts as a basic Matrix client.