Thank you! @sam 
5 Likes
Thank you for this exciting update!
I installed the chat plugin on my instance and it mostly seems to be working perfectly.
However, the emojis are not working. Instead of icons, they are represented by text, like this:
Itās not just me or my browser, itās like this for all users. And here on Meta the chat emojis are displayed just fine when using the same browser.
Any ideas about what might be going on?
Do I need to install a separate icon pack or something like that for the emojis to work?
Thank you in advance for helping me sort this out!
4 Likes
How do you appear all the people of my forum in the chat? Instead of I add one by one? This would be more practical and intuitive than find and add 1 by 1 for I could speak
3 Likes
Can we delete chat rooms?
4 Likes
I donāt think so, not yet, but we will get that added
7 Likes
Iām on the latest version and it supports deleting chat rooms.
I think it is already very functional. I wouldnāt call it pre-alphaā¦ maybe RC1
9 Likes
Yeah, I think it is very reasonable to call chat ābetaā now ā¦ @codinghorror any objection to giving it that official title - we already have multiple beta users now. Calling chat alpha is a bit misleading.
21 Likes
Sure letās beta it up! Ī²
24 Likes
This will be a huge feature for my community. Iāve been wanting an ad-hoc, synchronous way for users to communicate but I didnāt want to add another disjointed platform into the mix. Canāt wait for this be GA!
13 Likes
Feature request:
I could use some help transitioning my users to the chat by automatically mass-joining them to some channels
5 Likes
I would like this as well. Maybe even just a Group setting where one could add the chat channels to which members of a group would be auto-joined, similar to how many of the multi-select settings work.
Similar to this but I think different enough. The one below is more about auto-creation of a chat channel for the specific group:
https://meta.discourse.org/t/chats-for-discourse-groups/223967?u=jimkleiber
6 Likes
This looks very promising, with the new āBetaā label, when can we regular folk expect to install the plugin?
Maybe it makes sense to make the plugin available for easy installation with large āBetaā warnings, this way you get more testers.
This is under the assumption that we can update it easily via the admin
4 Likes
You can already install it on your self-hosted instance. It also follows the normal update system of all plugins in Discourse, so you can update from the web UI the same as everything else.
3 Likes
I see, seemās Iāll need to follow the below steps
Was there a way through a link or admin panel Iām missing?
5 Likes
You install it via editing the app.yml indeed, as said in the guide. Updating it after that can be done via the UI.
5 Likes
Is it still the plan to make chat public here on Meta?
3 Likes
Weāre still full steam ahead working on the plugin, but since we are daily driving it internally with great success it should be open to all Meta users soon.
11 Likes
Do you know what hosted plans this will be available on?
3 Likes
Eventually we plan to allow this on all plans, but we are yet to set limits and timelines for deployment.
For now, we are looking for beta testers
- Ideally Enterprise plan, but will accept standard/business in exceptional cases
- critical we can not beta test a ghost town, needs to be reasonably active - say 500 chat messages a day an up.
8 Likes
Iāve installed this plugin and enjoyed using it.
However, when I delete a user, after I have some communication with him in a private channel, I got this error:
rsvp.js:26 Uncaught TypeError: Cannot read properties of null (reading āidā)
And the chat is broken. I guess this is because one of the user is removed there, and it cannot read attribute of it.
And from now, I cannot use chat because of this. Itās always broken evenif I try to refresh.
Can anyone help me with this please?
1 Like