ToddZ suggested the ability to administratively “re-parent” replies that were mistakenly posted as topic replies instead of direct responses to specific posts. This sparked a discussion about the pros and cons of such a feature, with considerations for topic clarity and user education. Read more.
A user reported issues with spell checking in Firefox on macOS while editing posts. Other users confirmed that spell checking was working correctly for them, suggesting it might be a local configuration issue. Read more.
A user reported that usercards reappear when scrolling away far enough to load new posts, even without clicking on them again. This unexpected behavior was demonstrated with a video, highlighting a potential UI glitch. Read more.
In the Discourse Chatbot plugin thread, exlabs encountered a gem activation error while trying to install the plugin. merefield suggested it might be due to a conflicting dependency with the Zendesk plugin and offered potential solutions. Read more.
A user encountered an error during the rebuild of their Discourse instance, specifically a NULL-Byte warning in the launcher script. pfaffman and RGJ provided troubleshooting steps and identified potential causes for the issue. Read more.
#Hosting
Heliosurge inquired about experiences with LeaseWeb as a hosting provider for Discourse. Lilly provided a link to a previous discussion about LeaseWeb experiences, offering some context for potential users. Read more.
Falco discussed the challenges of implementing HTTP/3 support in Discourse, explaining the complexities involved with nginx and potential alternatives like Caddy. He proposed a new template approach for experimenting with different web servers. Read more.
Lilly confirmed that the “arrive at topic” option for invites is still available and provided a screenshot demonstrating its presence in the invite creation dialog. Read more.
oga asked about the theme used on meta.discourse.org and the availability of the “Radiant” theme. Lilly clarified that multiple themes are used and provided information on finding and installing themes.
cosdesign sought help on using DiscourseConnect as a client only, aiming to allow website visitors to log in and register solely through Discourse. The discussion included steps taken and configuration attempts.
eisammy reported an issue with the /faq page not working correctly after deleting the logs category, resulting in an inability to edit the page and encountering an “Oops!” error upon refresh.
mcwumbly announced the release of Discourse 3.4.0.beta2, highlighting new features such as improved pageview metrics, multiple category moderator groups, and the ability to watch chat threads.
mcwumbly also announced Discourse 3.3.2, a security and maintenance release addressing several CVEs and including various bug fixes and improvements.
Falco provided an update on NSFW detection in Discourse AI, mentioning improved accuracy with the AI Post Classifier and ongoing development of Vision LLM-based solutions for Enterprise customers.
Tris20 suggested moving the “Proofread Text” AI button next to “Create Topic” to make it more visible for new users. lindsey mentioned that the design team is working on composer redesigns and considering how to better surface AI features. sam proposed ideas like teaching users about proofreading and background proofreading as you type. Read more.
EnergyInterest noticed double buttons in the posting section of their forum. Moin explained that these buttons allow users to change notification levels and reply while reading a topic, disappearing when scrolling to the bottom. awesomerobot clarified their purpose for replying or changing tracking status before reaching the end of a topic.
A discussion on Trust Level 4 promotion by community election poll continued, with Heliosurge explaining that the idea doesn’t need to be part of core Discourse due to its extensible design. Lilly reminded that users could build their own plugin for this functionality.
angus announced he’ll be providing regular support for the ActivityPub plugin until at least March next year. Users discussed federation between Discourse and Lemmy, with angus clarifying that the plugin complies with FEP-1b12 for group-based federation.
The Discourse AI Post Classifier can now be used to detect NSFW images and text in communities. Saif provided a guide on setting it up for administrators.
ToddZ provided an update on Mailgun pricing, noting that the Flex Plan is no longer available and current pricing starts at $15/month after the free tier.
xandra.cc reported an issue where users could no longer edit any posts since updating to 3.4.0.beta3-dev. Moin suggested a fix related to the discourse-reactions plugin, which resolved the problem.
Rick_Jing encountered a 500 internal server error when trying to create topics with tags via API. The community also advised on the importance of properly obscuring API keys in screenshots.
Shauny inquired about limiting AI token usage for users. Jagster explained that Discourse AI doesn’t have such limitations, but the Chatbot solution offers weekly request limits.
supermathie provided technical details about 2FA algorithms used in Discourse and offered troubleshooting assistance.
Saif inquired about the effectiveness of spam detection and NSFW content detection guides in combating increasingly sophisticated AI-generated spam.
lindsey updated the community on plans to improve search functionality, particularly in returning all results instead of limiting to the first 20.
sam acknowledged the need for a quota system for AI usage and mentioned plans to add group selectors with input/output counts and duration for each LLM.
NateDhaliwal introduced a new Discourse Persistent Banner theme component that displays a banner at the top of every page, which can only be hidden by admins. Lilly provided feedback and suggestions for improvements, including placement options and color customization.
The Filtered Topic Lists component encountered an issue where setting “Default List Filter: no subcategories” in a category prevents filtered topic lists from displaying in any outlets. gormus confirmed the findings and provided steps to reproduce the problem.
A user sought help to implement a specific category representation design on their Discourse-hosted community. Moin provided guidance on using the “Boxes with Subcategories” desktop category page style and adding CSS customizations.
RCheesley reported an error when clicking on the Billing tab in the user profile of a self-hosted Discourse instance with the subscriptions plugin installed. The error seemed to be related to the Who’s Online plugin.
Shauny asked about enabling the AI button in the toolbar, discovering that it was working but required text highlighting to activate. Moin explained that a recent change moved the button’s position, and users on the stable branch would need to wait for the next release.
RGJ encountered an issue where overridden text in translations suddenly reverted to the original, despite the override still being present in the admin panel. Moin suggested searching for the specific translation key to troubleshoot.
Lilly provided feedback and suggestions on the Discourse Persistent Banner theme component, offering insights on improving its functionality and customization options. She recommended adjustments for desktop placement, border customization, and color selection flexibility.
Thanks for reading, and I’ll see you again tomorrow!
ludwikc sought advice on duplicating a group to manage course access, with Lilly suggesting the use of API to populate the new group.
joo inquired about triggering AI-generated replies when users post, with sam mentioning an upcoming PR for personas while cautioning about potential noise.
sam addressed concerns about AI-generated spam, discussing the philosophical questions of value addition and content removal. He also mentioned ongoing work on AI-generated replies through personas.
Thomas_Rother reported an issue with wiki text functionality disappearing after upgrading to Discourse 3.4.0.beta3-dev. Moin suggested checking safe mode and the post menu site setting read more.
maiki discovered a validation issue with the Name field for AI tools in Discourse AI. They suggested adding validation in the UI to prevent errors when creating new tools read more.
Sidi_Codet reported responsiveness issues with the user preferences section on mobile devices when using the Central Theme. jordan-vidrine advised submitting feedback to the theme’s topic as it’s still experimental read more.
Epoch requested paid development for three different plugins or components, including color-coding user names based on group rankings and creating collapsible sidebar categories read more.
j127 shared insights on AI-based spam, discussing the challenges of distinguishing valuable AI-generated content from spam and the importance of maintaining trust in forum content read more.
Falco explained the functionality of AI-generated replies in response to joo’s inquiry about triggering AI responses when users post. He suggested validating the idea manually before automating read more.
sam addressed concerns about pageview metrics in the new site traffic report, clarifying that no information was lost and explaining how to access the previous data read more.
Users reported issues with “in reply to” links not working on a specific Discourse forum. Moin suggested it might be related to deleted posts or a forum-specific issue read more.
baronesh accidentally deleted a member and inquired about undoing the action. pfaffman explained that immediate deletion occurs for users with few or no posts read more.
ludwikc asked about marking all posts as read for users aiming to achieve “Inbox:0” on their Discourse instance. pfaffman clarified that Discourse doesn’t allow marking posts as read without actually reading them read more.
Falco addressed concerns about code scan vulnerabilities in self-hosted Discourse installations, explaining that off-the-shelf tools often produce false positives and recommending the use of HackerOne for reporting actual issues.
rishabh engaged in discussions about AI-powered user field collection in the Discourse Chatbot plugin, providing information on supported field types and limitations.
NateDhaliwal created a fun new theme component called Discourse Confetti Clicks that adds confetti animations when users click on the page. Some users suggested limiting it to specific pages or tying it to special events like member birthdays.
A discussion on gamification beyond leaderboards explored ideas for keeping users engaged, including customizing trust levels and badges.
Feature
There was renewed interest in indexing file contents for search, with mjbergman92 suggesting the development of a plugin integrating with Paperless for document management and search.
mcwumbly shared the Current Projects - October 2024 update, highlighting ongoing work on the composer redesign, a new look and feel config page, and other initiatives.
ted commented on the PG13 compatibility issue, sharing a potential fix and discussing considerations for backup restoration between different PostgreSQL versions.
Thanks for reading, and I’ll see you again tomorrow!
ganncamp discovered a useful auto-linking feature when pasting text, similar to Slack’s functionality. This accidental discovery will save many keystrokes for users.
renem asked about the possibility of creating a webhook for whisper posts. simon explained that while there’s no specific webhook for whispers, it’s possible to filter for them in a general Post Events webhook.
kendoer shared a solution for a restore failure related to a missing chat_mention function by updating the old server to the same version as the new installation before creating a backup.
A user encountered a “CSRF Detected” error when using the oauth2-basic plugin for OAuth2 login. supermathie suggested enabling force_https to potentially resolve the issue.
A discussion began about tactics to strengthen online communities, with forum administrators sharing their experiences and seeking advice on growing their communities.
A discussion continued about unexpected search behavior where certain terms like ‘/commands’ are not found when searching for ‘commands’. MarcP highlighted issues with searching GitHub and X (Twitter) links, emphasizing the impact on findability, especially in draft and staff sections.
A discussion about a Cryptocurrency Idea Submission Plugin explored the potential of expanding Discourse’s tag system to handle cryptocurrency data, with questions about tag performance and UI enhancements.
Amicable encountered a problem with AI-generated links in their locally hosted Chatbot, where topic titles were being replaced with “slug” in URLs. The issue was later identified as related to running on localhost without SSL.
AxelTerizaki faced difficulties with Redis and database errors during a Discourse installation. The issue was ultimately traced back to a virus scan removing PostgreSQL files, highlighting the importance of proper antivirus configuration in Discourse setups.
mcwumblyconfirmed experiencing scrolling issues similar to those reported by richb-hanover, particularly on laptops with trackpads.
samacknowledged a reproducible bug related to AI personas not changing as expected in private messages and committed to addressing the issue.
awesomerobotcontributed to the discussion about smooth scrolling problems, confirming similar experiences on laptops with trackpads.
tedprovided insights on a PostgreSQL compatibility issue, suggesting a workaround and inquiring about the circumstances that led to restoring a PG15 backup on PG13.
Lillyoffered assistance to a user experiencing problems with the Discourse summary feature, requesting more information about their configuration.
Thanks for reading, and I’ll see you again tomorrow!
Users reported issues with restoring backups due to a missing chat_mention function. RGJ explained that the problem stems from a migration with an older date stamp being committed later, which isn’t detected by the version metadata in the backup. The solution involves updating to the latest version or building a new instance with the same commit hash.
A user encountered a 502 Bad Gateway error on their Discourse instance. The community suggested running ./launcher rebuild app to resolve the issue, which was successful after about an hour.
sebix1 reported that generating 2FA backup codes is not immediately available after adding an authenticator. The page needs to be reloaded to see the “Add backup codes” button.
A discussion about the difficulty in finding the logout button in the new user menu continued, with a user thanking the community for a theme component that addresses this issue.
A user sought advice on configuring incoming email to create new topics or group messages, noting that the instructions may be outdated for version 3.2.2.
Teresations inquired about hosting live streams directly in their Discourse community using Streamyard or Restream, seeking guidance on the best approach.
darkpixlz initiated a poll to gauge interest in different designs for their Modern Theme, presenting options for a unibody design versus a detached/floating sidebar.
Users discussed the Discourse Advertising Plugin, with omarfilip noting that the content security policy guidance is outdated and requesting updated information.
A user encountered SMTP configuration errors while trying to install Discourse using the 1panel server panel docker, seeking assistance in troubleshooting the issue.
mryogi sought help with adding new posts using the API, encountering a 404 error. The community suggested checking the API key and path used in the request.
sam commented on the PG13 compatibility issue, acknowledging the need to update the open-source container to PostgreSQL 15 in the coming months.
jordan-vidrine addressed the issue of animations breaking on meta by removing transitions from a reader-mode component and requesting feedback on whether the animations are now working properly.
tobiaseigen shared an update on the creation of custom flags feature, including a screenshot of the new moderation flags admin page with the added toggle.
Lilly helped troubleshoot an issue with invites not working properly, confirming that invites are functioning as expected and suggesting where to look for redeemed invites.
A new blog post was published discussing how Discourse serves as a team collaboration tool. stella investigated an issue with the newsletter signup form reported by users.
