AWS

What’s Font Awesome? Discourse uses a free set of icons from Font Awesome throughout its interface. You see these on toolbars, badges, buttons, etc… here’s our composer toolbar: Since 2018 we’ve been using Font Awesome 5 (original announcement), and in the meantime Font Awesome 6 has been released. Version 6 includes new icons, some general style updates, and renames. As of today, Discourse will start using version 6 too! Specifically, version 6.6.0. This isn’t an enormous visual change, but you’ll notice some differences: What does this upgrade involve? This upgrade was a little more complicated to implement because it involves a number of renames. Font Awesome did this to make their naming conventions more consistent. Because of the renames, changes will be rolled out in multiple phases: Today - Font Awesome upgraded to v6, icons will be automatically remapped Soon - deprecation messages will be enabled to help theme/plugin authors update their icon names Q4 2024 - admin warning banner enabled for any remaining deprecations Q2 2025 - removal of automatic remapping What do I need to do today? Nothing at all ! Once Discourse is updated, you’ll have the new version of the icons. Discourse will automatically remap old icon names to new icon names, and the old icons will all be replaced. This includes icons used in the interface by default as well as badges, group/user flair, sidebar items, and additional icons added by themes and plugins. What do theme and plugin authors need to know? The methods covered in Introducing Font Awesome 5 and SVG icons will still work for adding new and custom icons. We don’t want to carry the long list of remaps forever, so the old names will eventually stop working. We want to give developers ample time to replace old icon names, so we will start showing console warnings like this soon: If you see one of these warnings, all you need to do is update your theme or plugin with the new icon name. Later in 2024 we’ll show admins a banner drawing their attention to these warnings. Once the admin deprecation warning is shown, you’ll have a minimum of a few months to swap in the new icon names. At some point in Q2 2025 we will remove the remapping of the old names, and if you haven’t updated icon names by then, you’ll see blank spaces where some of your icons used to be. There are lots of new icons! The upgrade from version 5 to 6 introduces hundreds of new free-to-use icons, almost 500 in total! You can browse the full set here, this is sorted to show the newest additions first — and the search is very handy: Search Icons & Find the Perfect Design | Font Awesome 21 posts - 9 participants Read full topic View the full article

We’ve redesigned the /about page in Discourse. Learn more about configuration options in the documentation topic: Understanding and customizing the About page You can see it right here by heading to /about. Here’s a screenshot: Notable additions Banner image at the top of the page Extended description that supports HTML/markdown 2-columns layout to reduce the amount of white space on wide screens Expandable/collapsible lists of admins and moderators Visitors and EU visitors stats to enable site owners to comply with the Digital Services Act (DSA). This requires the display_eu_visitor_stats setting to be enabled. Feedback If you encounter a bug with or have suggestions for the new /about page or its admin config area, please let us know right here in this topic. 64 posts - 24 participants Read full topic

We’ve been working on redesigning the /about page in Discourse and we’re finally ready to make it available to try it out. If you’re logged in to Meta, you can see it right here by heading to /about. Here’s a screenshot: Notable additions Banner image at the top of the page Extended description that supports HTML/markdown 2-columns layout to reduce the amount of white space on wide screens Expandable/collapsible lists of admins and moderators Visitors and EU visitors stats to enable site owners to comply with the Digital Services Act (DSA). This requires the display_eu_visitor_stats setting to be enabled. How to enable it Go to the admin site settings page and add the groups that you want to see the new page to the experimental redesigned about page groups setting. If you want all logged-in users to see the page, add the trust_level_0 group. It’s not possible at the moment to make the new page available to anonymous users. Configuration Admins can customize the new /about page via the admin config area for the /about page, which is available at /admin/config/about for all sites. Feedback If you encounter a bug with or have suggestions for the new /about page or its admin config area, please let us know right here in this topic. 40 posts - 19 participants Read full topic View the full article

New features in v3.4.0.beta1 “Hot” replaces “Top” in default menu items “Hot” is the newest topic sorting option that helps you discover what’s currently trending in your community based on recent likes and lively discussions. We are now replacing “Top” with “Hot” topics for sites that have not modified the top menu site setting. Learn more. Unseen feature indicator In the admin sidebar, the “What’s New” link will now feature a blue dot indicating new features are available if the user has not seen those features yet. Polls can show absolute numbers Polls now support absolute numbers in addition to percentages. 3 posts - 3 participants Read full topic

New features in v3.4.0.beta1 “Hot” replaces “Top” in default menu items “Hot” is the newest topic sorting option that helps you discover what’s currently trending in your community based on recent likes and lively discussions. We are now replacing “Top” with “Hot” topics for sites that have not modified the top menu site setting. Learn more. Unseen feature indicator In the admin sidebar, the “What’s New” link will now feature a blue dot indicating new features are available if the user has not seen those features yet. Polls can show absolute numbers Polls now support absolute numbers in addition to percentages. 3 posts - 3 participants Read full topic View the full article

Discourse 3.3.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 This release includes the following minor bug fixes and performance improvements: FIX: Badge image uploader (#28188) (#28521) · discourse/discourse@d3ad2ec · GitHub DEV: Allow disabling problem checks programatically (#28440) (#28441) · discourse/discourse@eaa40bb · GitHub DEV: Switch back to Chrome for running QUnit tests (#28430) · discourse/discourse@6cc856c · GitHub DEV: Update mini_racer (#28363) (#28428) · discourse/discourse@9e7be60 · GitHub DEV: Add backup helpers for specs (#28394) (#28426) · discourse/discourse@93d4b53 · GitHub DEV: Add plugin outlet for below wizard field (#28371) (#28384) · discourse/discourse@9cb28a2 · GitHub FIX: Return additional message types properly · discourse/discourse@c500dbd · GitHub FIX: system badges can be disabled (#28169) (#28171) · discourse/discourse@ac30a79 · GitHub 1 post - 1 participant Read full topic

Discourse 3.3.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 This release includes the following minor bug fixes and performance improvements: FIX: Badge image uploader (#28188) (#28521) · discourse/discourse@d3ad2ec · GitHub DEV: Allow disabling problem checks programatically (#28440) (#28441) · discourse/discourse@eaa40bb · GitHub DEV: Switch back to Chrome for running QUnit tests (#28430) · discourse/discourse@6cc856c · GitHub DEV: Update mini_racer (#28363) (#28428) · discourse/discourse@9e7be60 · GitHub DEV: Add backup helpers for specs (#28394) (#28426) · discourse/discourse@93d4b53 · GitHub DEV: Add plugin outlet for below wizard field (#28371) (#28384) · discourse/discourse@9cb28a2 · GitHub FIX: Return additional message types properly · discourse/discourse@c500dbd · GitHub FIX: system badges can be disabled (#28169) (#28171) · discourse/discourse@ac30a79 · GitHub 1 post - 1 participant Read full topic View the full article

We have recently made our new documentation plugin available for testing and feedback. This plugin is designed to enhance the navigation and accessibility of documentation hosted on Discourse, providing a more accessible and friendly experience for all users. Note that this plugin is still in development. The development of this plugin stems from our ongoing effort to improve documentation, which has already been enhanced by a new sidebar. The sidebar work laid the foundation for a much improved documentation experience, and the new plugin incrementally builds upon that work. The new plugin in action The plugin is currently active and powering the documentation on our official Discourse documentation. We invite you to explore its features and share your experiences with us. Your feedback is invaluable in helping us refine and enhance the plugin. The core features included in the new plugin are: Settings to define which categories are used for documentation A new documentation sidebar populated by index topics within each category Two new reports to help maintain the integrity and accuracy of index topics With more in development as we continually improve the available features. The new plugin is available to download and install today: Discourse Doc Categories Transitioning from the Discourse Docs plugin As we innovate and move forward, we will be sunsetting our older Discourse Docs plugin. You can rest assured, however, that we will continue to support it until the new plugin is fully ready for a widespread release. We have also ensured that the new plugin will redirect URLs from the old plugin, so switching over won’t result in any broken links. Please note that the new plugin is still in its experimental stages. While we aim to provide a seamless experience, there may be some areas that require further improvement. Your constructive feedback will be crucial to its success. Let us know what you think We would appreciate your thoughts, experiences, and feedback. Feel free to share your experiences and any insights you gather while using the new documentation plugin, either by navigating through the documentation on Meta, or installing the plugin on your own site. Our goal is to shape a better documentation experience for the entire Discourse community, so all feedback is welcome! Full plugin details available here: Discourse Doc Categories plugin Summary Discourse Doc Categories provides the ability for particular categories to be set aside for documentation, enabling additional features for them. Repository Link https://github.com/discourse/discourse-doc-categories Install Guide How to install plugins in Discourse Note that this plugin is in active development and not yet fully complete. Features The Discourse Doc Categories plugin that allows you to host str… 10 posts - 7 participants Read full topic

We have recently made our new documentation plugin available for testing and feedback. This plugin is designed to enhance the navigation and accessibility of documentation hosted on Discourse, providing a more accessible and friendly experience for all users. Note that this plugin is still in development. The development of this plugin stems from our ongoing effort to improve documentation, which has already been enhanced by a new sidebar. The sidebar work laid the foundation for a much improved documentation experience, and the new plugin incrementally builds upon that work. The new plugin in action The plugin is currently active and powering the documentation on our official Discourse documentation. We invite you to explore its features and share your experiences with us. Your feedback is invaluable in helping us refine and enhance the plugin. The core features included in the new plugin are: Settings to define which categories are used for documentation A new documentation sidebar populated by index topics within each category Two new reports to help maintain the integrity and accuracy of index topics With more in development as we continually improve the available features. The new plugin is available to download and install today: Discourse Doc Categories Transitioning from the Discourse Docs plugin As we innovate and move forward, we will be sunsetting our older Discourse Docs plugin. You can rest assured, however, that we will continue to support it until the new plugin is fully ready for a widespread release. We have also ensured that the new plugin will redirect URLs from the old plugin, so switching over won’t result in any broken links. Please note that the new plugin is still in its experimental stages. While we aim to provide a seamless experience, there may be some areas that require further improvement. Your constructive feedback will be crucial to its success. Let us know what you think We would appreciate your thoughts, experiences, and feedback. Feel free to share your experiences and any insights you gather while using the new documentation plugin, either by navigating through the documentation on Meta, or installing the plugin on your own site. Our goal is to shape a better documentation experience for the entire Discourse community, so all feedback is welcome! Full plugin details available here: Discourse Doc Categories plugin Summary Discourse Doc Categories provides the ability for particular categories to be set aside for documentation, enabling additional features for them. Repository Link https://github.com/discourse/discourse-doc-categories Install Guide How to install plugins in Discourse Note that this plugin is in active development and not yet fully complete. Features The Discourse Doc Categories plugin that allows you to host str… 10 posts - 7 participants Read full topic View the full article

Happy Anniversary to us! On August 26, 2014, we released Discourse v1.0 and introduced hosting services. We have been full throttle ever since. Now that we’ve hit this milestone we’re taking a look back to see how far we’ve come. This is a companion discussion topic for the original entry at https://blog.discourse.org/2024/08/celebrating-a-decade-of-discourse 11 posts - 11 participants Read full topic

Happy Anniversary to us! On August 26, 2014, we released Discourse v1.0 and introduced hosting services. We have been full throttle ever since. Now that we’ve hit this milestone we’re taking a look back to see how far we’ve come. This is a companion discussion topic for the original entry at https://blog.discourse.org/2024/08/celebrating-a-decade-of-discourse 11 posts - 11 participants Read full topic View the full article

I’m excited to announce some updates to how we handle documentation to ensure clarity and collaboration while maintaining the quality of information provided. Read on to understand how our new documentation setup works. Official documentation We’ve updated the Documentation category to be dedicated solely to official documentation. This means that all content in its subcategories is maintained by Discourse team members, ensuring the information is accurate and up-to-date. If you’re looking for the most authoritative guides and references, this is the place! Why only team members? Restricting the creation and editing of official documentation to our team ensures consistency and reliability. We aim to provide precise, well-maintained resources for everyone, from new users to seasoned developers. All community members can still reply to these topics to discuss the content or suggest changes. Community wiki Don’t worry, there’s plenty of space for your contributions too! All community-contributed documentation can now be found in the Community wiki category. This is where the expertise, tips, and collective knowledge of our vibrant community come together. Who can contribute? Users of Trust Level 2 and above have the power to create and edit topics in Community wiki. This empowers experienced users to share their knowledge, adding richness and diversity to our community resources. It also means that trusted community members can edit any community documentation they find that is incorrect or outdated. Why this change? This policy is designed to balance the need for official, maintained documentation and the valuable input that our community provides. It also delivers a clear structure for users seeking information - whether they need official guidance or community advice. We value the contributions from all of you, and we believe the move to a dedicated space for your documentation contributions will help them thrive, and receive the attention they deserve. We need you! The community wiki already has a head start on being a robust, community-driven space for learning and knowledge-sharing, and we’d love more of your input. If you have great tutorials, configurations, or advice, Community wiki awaits your contributions! You can find this documentation policy in its permanent home here: Discourse documentation policy site feedback There are two locations for Discourse documentation - one for official content, created and supported by the Discourse team, and one for community-contributed content. Official documentation Documentation is the home for official Discourse documentation. At Discourse, official documentation means the following: It is written by members of the Discourse team. It can only be edited by members of the Discourse team. It is supported by Discourse. It follows (or will be updated to follow) the doc… 8 posts - 4 participants Read full topic

I’m excited to announce some updates to how we handle documentation to ensure clarity and collaboration while maintaining the quality of information provided. Read on to understand how our new documentation setup works. Official documentation We’ve updated the Documentation category to be dedicated solely to official documentation. This means that all content in its subcategories is maintained by Discourse team members, ensuring the information is accurate and up-to-date. If you’re looking for the most authoritative guides and references, this is the place! Why only team members? Restricting the creation and editing of official documentation to our team ensures consistency and reliability. We aim to provide precise, well-maintained resources for everyone, from new users to seasoned developers. All community members can still reply to these topics to discuss the content or suggest changes. Community wiki Don’t worry, there’s plenty of space for your contributions too! All community-contributed documentation can now be found in the Community wiki category. This is where the expertise, tips, and collective knowledge of our vibrant community come together. Who can contribute? Users of Trust Level 2 and above have the power to create and edit topics in Community wiki. This empowers experienced users to share their knowledge, adding richness and diversity to our community resources. It also means that trusted community members can edit any community documentation they find that is incorrect or outdated. Why this change? This policy is designed to balance the need for official, maintained documentation and the valuable input that our community provides. It also delivers a clear structure for users seeking information - whether they need official guidance or community advice. We value the contributions from all of you, and we believe the move to a dedicated space for your documentation contributions will help them thrive, and receive the attention they deserve. We need you! The community wiki already has a head start on being a robust, community-driven space for learning and knowledge-sharing, and we’d love more of your input. If you have great tutorials, configurations, or advice, Community wiki awaits your contributions! You can find this documentation policy in its permanent home here: Discourse documentation policy site feedback There are two locations for Discourse documentation - one for official content, created and supported by the Discourse team, and one for community-contributed content. Official documentation Documentation is the home for official Discourse documentation. At Discourse, official documentation means the following: It is written by members of the Discourse team. It can only be edited by members of the Discourse team. It is supported by Discourse. It follows (or will be updated to follow) the doc… 8 posts - 4 participants Read full topic View the full article

On Thursday, August 29, 2024 4:00 AM UTC, we hosted the Community Manager Mindset office hours with the Discourse Customer Success team, where we discussed: Developing your mindset as a Community Manager. Approaching the Community Manager role. The truth behind benchmarks and KPIs. Plus, we answered your submitted questions! Replay Office Hours: Community Manager Mindset & Resources Introductions These office hours were hosted by @jenny, @bas, and @danielle from the Discourse Customer Success team. The information shared is based on our in-depth experience with a variety of communities and not necessarily a top-down dissemination of strategies from Discourse as a whole. Community Manager Basics What is a Community Manager? “Community management is the act of growing and sustaining a community in which customers, employees, partners, and others help each other achieve their goals.” FeverBee - The Beginner’s Guide To Community Management “A community manager is a marketing professional responsible for the management and development of a company’s online community. They are responsible for building, growing and managing the company’s community online and engaging with customers.” Indeed - Career Guide “The one essential role for every community is the ‘in the trenches’ community manager. This is the person who spends nearly all their time directly engaging with members…. {Without a community manager} members won’t get the quality and quantity of responses they deserve. There won’t be someone they can trust and build a good relationship with.” The ‘In The Trenches’ Community Manager by FeverBee Community Managers are the driving forces behind thriving communities! Definitions Don’t Matter Community Managers need to be managed upward. Everyone needs to understand what your community is actually doing, and this recognition must happen by the decision makers, such as your CEO. You need to define the why and ROI behind your community. Without clear objectives and alignment with your organization’s needs, the impact of your work may go unnoticed. Community Managers must continuously advocate for their community while also making the business case for its value. -@Bas Towing the Line: Speaking About Community There’s a duality in how Community Managers communicate, balancing the need to connect with both community members and corporate decision-makers. Community Members: Connection Engagement Trust Corporate/Decision Makers Demonstrating ROI Metrics Strategic Value That’s why clear goals, being proactive, and receiving feedback are crucial. Goals, Benchmarks, & KPIs What goals should I set for my community? At Discourse, we’re often asked, ‘What goals should I set for my community?’ The truth is, the answer depends on your community’s specific purpose and objectives. Each community is unique, so the goals you set should align with the core mission of your community and the needs of its members. Support Community: Goals might include improving response times, increasing issue resolution rates, and enhancing member satisfaction. Product or Service Community: Goals could focus on tracking member interaction with your product or service, gathering valuable feedback, boosting overall engagement, and even driving sales or upgrades. Employee or Team Member Community: Goals might revolve around better connections among team members, increasing their self-sufficiency, and raising awareness of organizational updates and initiatives. Start at the Origin Revisit the reason your community was created. Ask yourself: Why was this community started? What problem were you looking to solve? Understand the original purpose to help identify key areas to measure. Connect to Business Goals Reflect on how your community ties back to the main business or organizational goals. Consider how the community can support these objectives, whether it’s improving customer satisfaction, increasing brand loyalty, or enhancing employee collaboration. This will give you a clear framework for identifying relevant metrics. Something critical to note: It doesn’t matter if your community is active—what truly matters is how well your community’s goals align with your organization’s business objectives. You can have thousands of active users and millions of posts, but if your community’s impact isn’t tied to the business’s goals, it risks being shut down. Community Managers must connect their efforts to tangible business outcomes to ensure long-term success. Always start by asking, 'Why do we have this community, and how does it drive our business forward? -@Bas Derive KPIs Once you have a clear understanding of your community’s purpose and how it supports broader goals, you can derive Key Performance Indicators (KPIs) that align with these objectives. KPIs might include specific targets for growth, engagement, or impact, tailored to your community’s unique needs. As a Community Manager, your priority isn’t just to engage with the community but to ensure your efforts align with the broader business objectives. It’s not enough to say, ‘I want to increase engagement.’ You need to set specific, measurable goals—like increasing engagement by 10% over the next six months—that directly contribute to the business’s success. Always monitor, adjust, and align your community strategy with the organization’s changing goals to drive real value. -@Danielle Models & Resources Discourse Discover Discourse Resources FeverBee: Free Community Management Course FeverBee: ROI Guide CMX Hub: SPACES Modes: The Framework for Defining Your Community’s Business Value Q&A View Answers (click for more details) Upcoming Office Hours AMA with Discourse Design Team, October 2024 Yearly Recap & Latest Releases, December 2024 13 posts - 10 participants Read full topic

On Thursday, August 29, 2024 4:00 AM UTC, we hosted the Community Manager Mindset office hours with the Discourse Customer Success team, where we discussed: Developing your mindset as a Community Manager. Approaching the Community Manager role. The truth behind benchmarks and KPIs. Plus, we answered your submitted questions! Replay Office Hours: Community Manager Mindset & Resources Introductions These office hours were hosted by @jenny, @bas, and @danielle from the Discourse Customer Success team. The information shared is based on our in-depth experience with a variety of communities and not necessarily a top-down dissemination of strategies from Discourse as a whole. Community Manager Basics What is a Community Manager? “Community management is the act of growing and sustaining a community in which customers, employees, partners, and others help each other achieve their goals.” FeverBee - The Beginner’s Guide To Community Management “A community manager is a marketing professional responsible for the management and development of a company’s online community. They are responsible for building, growing and managing the company’s community online and engaging with customers.” Indeed - Career Guide “The one essential role for every community is the ‘in the trenches’ community manager. This is the person who spends nearly all their time directly engaging with members…. {Without a community manager} members won’t get the quality and quantity of responses they deserve. There won’t be someone they can trust and build a good relationship with.” The ‘In The Trenches’ Community Manager by FeverBee Community Managers are the driving forces behind thriving communities! Definitions Don’t Matter Community Managers need to be managed upward. Everyone needs to understand what your community is actually doing, and this recognition must happen by the decision makers, such as your CEO. You need to define the why and ROI behind your community. Without clear objectives and alignment with your organization’s needs, the impact of your work may go unnoticed. Community Managers must continuously advocate for their community while also making the business case for its value. -@Bas Towing the Line: Speaking About Community There’s a duality in how Community Managers communicate, balancing the need to connect with both community members and corporate decision-makers. Community Members: Connection Engagement Trust Corporate/Decision Makers Demonstrating ROI Metrics Strategic Value That’s why clear goals, being proactive, and receiving feedback are crucial. Goals, Benchmarks, & KPIs What goals should I set for my community? At Discourse, we’re often asked, ‘What goals should I set for my community?’ The truth is, the answer depends on your community’s specific purpose and objectives. Each community is unique, so the goals you set should align with the core mission of your community and the needs of its members. Support Community: Goals might include improving response times, increasing issue resolution rates, and enhancing member satisfaction. Product or Service Community: Goals could focus on tracking member interaction with your product or service, gathering valuable feedback, boosting overall engagement, and even driving sales or upgrades. Employee or Team Member Community: Goals might revolve around better connections among team members, increasing their self-sufficiency, and raising awareness of organizational updates and initiatives. Start at the Origin Revisit the reason your community was created. Ask yourself: Why was this community started? What problem were you looking to solve? Understand the original purpose to help identify key areas to measure. Connect to Business Goals Reflect on how your community ties back to the main business or organizational goals. Consider how the community can support these objectives, whether it’s improving customer satisfaction, increasing brand loyalty, or enhancing employee collaboration. This will give you a clear framework for identifying relevant metrics. Something critical to note: It doesn’t matter if your community is active—what truly matters is how well your community’s goals align with your organization’s business objectives. You can have thousands of active users and millions of posts, but if your community’s impact isn’t tied to the business’s goals, it risks being shut down. Community Managers must connect their efforts to tangible business outcomes to ensure long-term success. Always start by asking, 'Why do we have this community, and how does it drive our business forward? -@Bas Derive KPIs Once you have a clear understanding of your community’s purpose and how it supports broader goals, you can derive Key Performance Indicators (KPIs) that align with these objectives. KPIs might include specific targets for growth, engagement, or impact, tailored to your community’s unique needs. As a Community Manager, your priority isn’t just to engage with the community but to ensure your efforts align with the broader business objectives. It’s not enough to say, ‘I want to increase engagement.’ You need to set specific, measurable goals—like increasing engagement by 10% over the next six months—that directly contribute to the business’s success. Always monitor, adjust, and align your community strategy with the organization’s changing goals to drive real value. -@Danielle Models & Resources Discourse Discover Discourse Resources FeverBee: Free Community Management Course FeverBee: ROI Guide CMX Hub: SPACES Modes: The Framework for Defining Your Community’s Business Value Q&A View Answers (click for more details) Upcoming Office Hours AMA with Discourse Design Team, October 2024 Yearly Recap & Latest Releases, December 2024 13 posts - 10 participants Read full topic View the full article

If you’ve seen our previous announcement, then you are aware that we are shifting to prefer LLM preferred solutions as they provide a vastly superior experience. Hence, coming soon we’ll be decommissioning the NSFW module in favor of Discourse AI Post Classifier - Automation rules This will be a beta experience so expect changes to occur to the feature. Why are we doing this? For the same reasons… What's next for Toxicity detection in Discourse AI Previously using the Toxicity module meant… You were stuck using a single pre-defined model No customization for your community-specific needs Confusing threshold metrics Subpar performance LLMs have come a long way and can now provide a better performing and customizable experience. Whats new? What's next for Toxicity detection in Discourse AI Discourse AI Post Classifier - Automation rule can be used to triage posts for Toxicity (amongst other ways) and enforce communities to specific code of conducts. This means… Multiple LLMs supported for different performance requirements Easy to define what and how content should be treated Customizable prompts for community-specific needs Flag content for review and much more. To assist with the transition we have already written out guides Setting up toxicity/code of conduct detection in your community Setting up spam detection in your community Setting up NSFW detection in your community We will add another guide specifically for NSFW detection to help with the transition. What happens to NSFW? This announcement should be considered very early, until we are ready to decommission you can continue to use NSFW. When we do it, we will be decommissioning the module, and removing all code from the Discourse AI plugin and associated services from our servers. The deprecation will only happen after AI Triage is ready to handle images which will be done soon. 5 posts - 1 participant Read full topic

If you’ve seen our previous announcement, then you are aware that we are shifting to prefer LLM preferred solutions as they provide a vastly superior experience. Hence, coming soon we’ll be decommissioning the NSFW module in favor of Discourse AI Post Classifier - Automation rules This will be a beta experience so expect changes to occur to the feature. Why are we doing this? For the same reasons… What's next for Toxicity detection in Discourse AI? Previously using the Toxicity module meant… You were stuck using a single pre-defined model No customization for your community-specific needs Confusing threshold metrics Subpar performance LLMs have come a long way and can now provide a better performing and customizable experience. Whats new? What's next for Toxicity detection in Discourse AI? Discourse AI Post Classifier - Automation rule can be used to triage posts for Toxicity (amongst other ways) and enforce communities to specific code of conducts. This means… Multiple LLMs supported for different performance requirements Easy to define what and how content should be treated Customizable prompts for community-specific needs Flag content for review and much more. To assist with the transition we have already written out 2 guides Setting up toxicity/code of conduct detection in your community Setting up spam detection in your community Setting up NSFW detection in your community We will add another guide specifically for NSFW detection to help with the transition. What happens to NSFW? This announcement should be considered very early, until we are ready to decommission you can continue to use NSFW. When we do it, we will be decommissioning the module, and removing all code from the Discourse AI plugin and associated services from our servers. The deprecation will only happen after AI Triage is ready to handle images which will be done soon. 4 posts - 1 participant Read full topic View the full article

Today we are announcing good bye to the Discourse AI - Toxicity module in favor of Discourse AI Post Classifier - Automation rules, leveraging the power of Large Languge Models (LLMs) to provide a superior experience. This will be a beta experience so expect changes to occur to the feature. Why are we doing this? Previously using the Toxicity module meant… You were stuck using a single pre-defined model No customization for your community-specific needs Confusing threshold metrics Subpar performance LLMs have come a long way and can now provide a better performing and customizable experience. Whats new? Discourse AI Post Classifier - Automation rule can be used to triage posts for Toxicity (amongst other ways) and enforce communities to specific code of conducts. This means… Multiple LLMs supported for different performance requirements Easy to define what and how content should be treated Customizable prompts for community-specific needs Flag content for review and much more. To assist with the transition we have already written out 2 guides Setting up toxicity/code of conduct detection in your community Setting up spam detection in your community What happens to Toxicity? This announcement should be considered very early, until we are ready to decommission you can continue to use Toxicity. When we do it, we will be decommissioning the module and removing all code from the Discourse AI plugin and associated services from our servers. 8 posts - 4 participants Read full topic

Today we are announcing good bye to the Discourse AI - Toxicity module in favor of Discourse AI Post Classifier - Automation rules, leveraging the power of Large Languge Models (LLMs) to provide a superior experience. This will be a beta experience so expect changes to occur to the feature. Why are we doing this? Previously using the Toxicity module meant… You were stuck using a single pre-defined model No customization for your community-specific needs Confusing threshold metrics Subpar performance LLMs have come a long way and can now provide a better performing and customizable experience. Whats new? Discourse AI Post Classifier - Automation rule can be used to triage posts for Toxicity (amongst other ways) and enforce communities to specific code of conducts. This means… Multiple LLMs supported for different performance requirements Easy to define what and how content should be treated Customizable prompts for community-specific needs Flag content for review and much more. To assist with the transition we have already written out 2 guides Setting up toxicity/code of conduct detection in your community Setting up spam detection in your community What happens to Toxicity? This announcement should be considered very early, until we are ready to decommission you can continue to use Toxicity. When we do it, we will be decommissioning the module and removing all code from the Discourse AI plugin and associated services from our servers. 7 posts - 4 participants Read full topic View the full article

We are proud to announce that we have finally shipped the new LLM settings page available through the Discourse AI plugin (/admin/plugins/discourse-ai/ai-llms) Whats new? A dedicated page for all the LLMs settings you need for Discourse AI features Be able to create and add multiple LLM connections and configure them We’ve made it easy to add all popular LLM connections by pre-populating some of the information so all you’ll really need is the API key We’ve removed 20+ site settings and moved them over to the relevant LLM provider to reduce clutter. When you select a provider you see everything in one place Test to make sure connections are working properly Enable for AI Bot and other AI features once the connections are added successfully Give it a try and let us know what you think Full details are available here. Discourse AI - Large Language Model (LLM) settings page Site Management This topic covers the LLM settings page which is part of the Discourse AI plugin. Overview The dedicated settings page is designed to have everything related to Large Language Models (LLMs) used for Discourse AI features in one place. Depending on the Discourse AI feature enabled, an LLM might be needed. Please check each Discourse AI feature to know if an LLM is a pre-requisite [CleanShot 2024-08-02 at 15.06.50@2x] [CleanShot 2024-08-02 at 15.07.09@2x] … 2 posts - 2 participants Read full topic View the full article

Discourse 3.2.5 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. Security Updates This release includes fixes for these security issues reported by our community and HackerOne . XSS via Onebox system (CVE-2024-37165) Iframe injection though default site setting (CVE-2024-39320) DoS via Tag Group (CVE-2024-37299) 1 post - 1 participant Read full topic View the full article

New features in v3.3.0.beta5 Simplified topic map The new topic map dramatically simplifies layout by highlighting useful information, with details available behind one click. Learn more. Improved topic bulk actions Changes in the menu include a loading spinner while operations occur, all options being available from one click, and support for additional options, i.e - Close Silently. Now available on all sites by default. Additional messaging for custom moderation flags Admins can now prompt users to provide additional reasoning when flagging posts. These reasons will show up in the moderation queue. New feature announcements The “What’s New” page now displays new features grouped by month and version numbers. Security Updates This release includes fixes for these security issues reported by our community and HackerOne . XSS via Onebox system (CVE-2024-37165) Iframe injection though default site setting (CVE-2024-39320) DoS via Tag Group (CVE-2024-37299) 2 posts - 2 participants Read full topic View the full article

Discourse 3.3 is here! This release includes significant improvements including… Enhanced community discoverability Keeping up with trending topics Discourse AI configurable personas, newer LLMs, and automation support Simplified admin navigation … and so much more! Check out our blog post, as well as all the 3.3.0.beta5 release-notes topics for details. Discourse – 30 Jul 24 Celebrating Discourse release 3.3 Discourse 3.3 is here! This new release contains powerful new features to enhance the discoverability of your community and the content within it 1 post - 1 participant Read full topic View the full article

Discourse 3.3 is here! This new release contains powerful new features to enhance the discoverability of your community and the content within it. With Discourse Discover, members can easily find and join your community, even when on-the-go by using the Discourse Hub mobile app. Additionally, the new Hot topic list surfaces trending topics so your members can keep up with the most popular conversations in your community. This is a companion discussion topic for the original entry at https://blog.discourse.org/2024/07/celebrating-discourse-3-3 6 posts - 6 participants Read full topic View the full article

Every day, customers are building, growing, and managing successful communities powered by Discourse. Today, we're highlighting the Revolut Community, a remarkable success story inspired by true Revolut fans who organically emerged on social media. With consumers at the heart of everything they do, Revolut wanted to create a dedicated platform for their customers to share feedback and receive official information. This is a companion discussion topic for the original entry at https://blog.discourse.org/2024/07/how-revolut-built-a-thriving-community-with-discourse 4 posts - 3 participants Read full topic View the full article