Topics

Introducing Advanced Sentiment Analysis: Powerful New Insights for Your Discourse Community We’re excited to announce a significant enhancement to Discourse AI with our new Sentiment Analysis Report feature. Building on last year’s Sentiment overview, this powerful tool gives administrators deeper insights into community sentiment across your forum. Where to Find It Navigate to your admin dashboard and look under the Reports section in the sidebar. You’ll find the new Sentiment analysis option alongside the existing Sentiment overview report. Flexible Analysis Options This comprehensive report empowers you to: Filter by specific parent categories Group results by categories or tags Customize time periods for targeted analysis Easily export data for further processing Actionable Community Insights The true power of this feature lies in its ability to help you identify trends and potential issues before they escalate. With a single click, you can drill down into any category to examine specific posts that are driving sentiment in your community. Availability and Implementation This feature is now available to all customers on our official hosting at no additional cost. Self-hosted Discourse instances can enable this functionality by following our existing setup guides for Discourse AI. Get Started Today We encourage all community managers to explore this powerful new tool and discover valuable insights about your forum’s emotional landscape. Share your experiences with us as you put sentiment analysis to work! 1 post - 1 participant Read full topic

For licensing reasons, we had to change the emoji sets. The following existing sets have been migrated automatically to a new set: apple → twemoji facebook_messenger → unicode google → noto google_classic → noto win10 → fluentui emoji_one → twemoji twitter → twemoji On top of fluent ui, noto, twemoji, and unicode, we also added the openmoji set. Admins can change the set at /admin/site_settings/category/all_results?filter=Emoji%20set If there’s an existing open-source set you would like to see available in Discourse, please let us know. We understand that changing emojis can be a very visible change, but we didn’t have any other way around it. We prefer to lay a good foundation for the future by only supporting fully open-source sets. 3 posts - 2 participants Read full topic

At Discourse, we are committed to fostering safe and healthy online communities. To support this, we’re introducing an important update that allows forum administrators to access and manage group chats within their communities. This update ensures that community leaders can effectively manage group chat memberships, enforce guidelines, and respond to safety concerns when needed. It also helps communities align with evolving online safety legislation, providing admins with the necessary tools to maintain a secure and welcoming space for all members. We believe this change will empower admins to uphold community standards while continuing to provide a space for meaningful and productive discussions. As always, we remain dedicated to building features that balance user experience, moderation needs, and community well-being. This feature will be available for all Discourse sites in the coming days, and was added in these two pull requests: github.com/discourse/discourse FEATURE: Allow admins to remove users from chat DMs main ← feature/admin-remove-users-from-chat-dms opened 10:13AM - 17 Feb 25 UTC Drenmi +375 -17 ### What is this feature? This feature allows admins to remove users from cha…nnels. This is allowed for category channels and group DMs, but not one-on-one DMs, as that wouldn't make any sense. 😉 **Screenshot:** <img width="263" alt="Screenshot 2025-02-19 at 10 59 49 AM" src="https://github.com/user-attachments/assets/049aa77d-67ae-42f8-a190-f640e4285118" /> ### Implementation details This PR attempts to follow the existing structure as much as possible. The major moving parts are: - A new back-end service for removing users from channels. - A guardian extension checking the ability to do so. This is also propagated to the front-end. - A new method in the front-end chat API. - UI changes. - Tests. ### Known limitations - When removing a member from a group DM, the header doesn't update to reflect this. This is a pre-existing issue. (It also doesn't update when adding members.) I have created a task to fix this separately. - The terms `users` and `members` are mixed throughout the code base. I tried as best I could to follow the terminology of the _directly adjacent code_. We could potentially fix this up later. github.com/discourse/discourse FEATURE: Allow admins to access group chats main ← feature/admins-access-group-chats opened 05:45AM - 21 Feb 25 UTC Drenmi +36 -1 ### What is this change? In #31366, we added the ability for admins to remove… people from group chats. However, that only works as long as the admin is already in the group chat. For forum-side group messages, admins can join any of them at will. This PR extends that same ability to chat for parity. 1 post - 1 participant Read full topic

Invision Community 5.0.3 is now available via your Admin Control Panel This release focuses on bugs reported since the release of 5.0.2 and features many UI improvements. You can see the full list of fixes in our release notes section. What's next? We expect 5.0.4 to follow within two to three weeks as we work in some larger fixes that will require more testing. We may release a beta release ahead of the full release to ensure that any bugs from those larger fixes are caught and fixed early. If we see anything more pressing, we'll release a patch which can be applied via your Admin Control Panel. As always, thank you for your testing and reports. It really does help us!

Discourse 3.4.1 Stable Release Discourse strongly recommends that all sites follow the default tests-passed branch of Discourse. The “stable” branch is more focused on lack of change than lack of bugs - all releases, including those on tests-passed and beta are production ready. Bug Fixes Improve group name validation (31315) Wikipedia onebox images and sections (31384) Language parser matches with dashes or underscores (31381) Ensure revoke_ungranted_titles! works with user_ids (31371) Adds further support for ‘prioritize_full_name_in_ux’ setting (31346) Make permalink search work even when there’re 100+ permalinks (31354) Don’t show &nbsp; in date to button (31352) Missing link to deleted post in /my/deleted-posts (31342) Image uploads in site-settings and profile (31350) Prevents double set in the same computation (31348) Relative date format consistency (31349) Post revision respects ‘prioritize_full_name_in_ux’ setting (31293) Minimum username length should be validated (31332) Keep user in same context after login (31314) Ensures fields are correctly unregistered (31329) Calculate reaction_users_count in the bulk import script (30964) Automatically redirect logged in users to topic when… (31301) Do not show confirmation modal (31304) Limit displayed groups in <GroupChooser /> to 100 groups (31288) User profile not loading with an empty export (31290) Correctly display label (31282) Don’t load all groups when rendering <GroupChooser /> (31271) JS error when .header-cloak isn’t present (31281) Invalid CSP directive sources should allow site to boot with valid CSP directives (31256) Improvements for uploads:disable_secure_uploads task (31231) Incorrect topic per-minute invitation rate limit (31252) Automatic auth flow with full page login/signup V3 (31072) Do not notify admins about PMs when suppress is on (31232) Correct typo in property name for save button component (31221) Set the correct state of the dark mode checkbox user preference (31214) Adjust badge selector for proper nesting in plugin list (31218) Only include custom plugin config routes in tabs for old show page (31213) Clean up not secure uploads with access_control_post_id (31189) Correctly check for hasData in admin-report (31197) Propagate pointerdown events on DMenu trigger when the menu isn’t expanded (31104) Correct mobile height of badge and ownership modals (31187) UX Changes Increase limit in chat channel fetcher (31406) Remove old menu border hack (31344) Prevent long category names from overflowing on mobile topic list (31335) Hide powered-by on admin invite page (31303) Add enter key hints for search (31298) Remove main-outlet-wrapper margin reset for mobile (31286) Add confirmation to crawler settings (31269) Update banner image field to use help text (30666) Fix horizontal group nav on mobile (31259) Switch group pages to horizontal nav (31243) Use icon for create topic btn on mobile (31237) Omit date in user stream for small action posts (31236) User stream alignment fix for likes (31234) Do not use generic username suggestions for invites (31175) Conditionally refresh page on wizard styling step (31193) Remove enable_quote_copy site setting (31191) Fix HTML showing in delete user button (31201) Fix layout of invite modal errors (31199) Left-align dropdown menu button text (31198) Fix wrapping of topic map links with counter (31184) Update bot-indicator styling (31108) Multiple drafts menu improvements (31195) Show parent category name for category hashtags (31188) Ensure all children of .with-topic-progress are clickable (31176) Performance Defer consolePrefix() calculation for transformers (31367) Admin plugin preload settings routes (31215) Accessibility Fix post control button contrast issue for WCAG colors (31177) 2 posts - 2 participants Read full topic