A user reported issues with restoring Discourse from backup for large databases, leading to an interesting discussion about PostgreSQL permissions and potential timeout issues.
A detailed discussion about moderation challenges with spam prevention, particularly focusing on sophisticated spammer tactics and potential solutions for the Home Assistant community.
Arkshine released a new Watermark Image component that automatically adds watermarks to user-uploaded images. The component is receiving positive feedback and feature requests from the community.
nat shared comprehensive guidance on immediate actions to take during spam attacks, including recommended settings and preventative measures. The post sparked discussion about potential improvements to spam handling features.
Users noticed the “My Posts” menu option missing from the left panel after recent updates. Moin discovered this was an intentional change related to the new drafts feature, though sandra.mccollum suggested keeping both options would be beneficial.
Moin created a comprehensive guide on configuring the default sidebar for users, helping administrators better understand navigation customization options.
In #Site_feedback:
Mate reported an issue with suggestion vote limits, leading to a discussion about improving the UX for Trust Level 0 users.
Moin reported that the “My Posts” menu option is missing from the left panel after recent updates. mcwumbly explained this was a deliberate decision to simplify the sidebar, though they’re monitoring feedback about this change.
An interesting discussion emerged about hiding the “last seen” time for specific users, with CocoQuark providing a JavaScript solution while noting the limitations of client-side customization.
joffreyjaffeux introduced Discourse Rewind 2024, an experimental feature that provides users with personalized activity statistics and visualizations. The feature is currently available for testing but not accepting bug reports.
merefield proposed a new AI-powered moderation tool for automatically formatting code blocks, inspired by challenges faced on the OpenAI forum. sam suggested implementing an automation system with confidence thresholds.
A concerning issue was raised regarding Microsoft Defender detecting Wacatac malware during Discourse updates. david and the team investigated and identified it as related to the lefthook binary cache.
Discussion continued about the missing “My Posts” menu option in the left panel, with sam confirming the team is tracking the issue and lindsey will provide an update.
An active discussion about recommended SMTP providers continued, with users sharing experiences with various services including Mailgun and Amazon SES.
shannon1024 reported a critical issue with the AI plugin causing all posts to become unreadable in the latest Discourse version. Roman_Rizzi helped identify the root cause related to embeddings configuration.
A detailed discussion about user information exposure to LLMs in Discourse AI, where merefield clarified that only usernames and raw post content are sent to the models.
An interesting thread emerged about using Docker Compose with Discourse, with detailed discussion about installation approaches and benefits of the official setup.
RGJ suggested that the “Hide my public profile” option is incorrectly placed in the interface preferences, recommending it be moved to Security or Profile tabs instead.
Michael82 reported an issue with Google search results showing “Instagram” as their forum name, leading to an interesting discussion about Google’s site name generation behavior.
mwaniki announced an important PostgreSQL 15 upgrade for Discourse installations, including detailed migration instructions and warnings about disk space requirements for large databases.
Exciting news for content creators! lindsey announced that Discourse now supports multiple drafts, allowing users to work on multiple topics and replies simultaneously without losing their work.
markschmucker reported high CPU usage issues after upgrading to version 3.4.0.beta4-dev, with test sites showing similar behavior even without traffic.
An investigation into Redis memory issues is underway, with zogstrip looking into potential causes related to chat channels and user counts.
Users reported an issue with like limits for trust level 3 users, where Lilly provided guidance on configuring like count multipliers through site settings.
A discussion about Redis memory usage with large chat groups continued, with zogstrip investigating groups containing over 100,000 members.
Arkshine reported the “clock” icon missing from the default SVG subset, affecting GitHub PR oneboxes and pending posts displays. A PR was submitted to address this.
