סיכום יומי (בשעה 13:00 UTC)

News and Events 摘要论坛
908

Today on meta.discourse.org…

Key Stats

In the past 24 hours, there have been 30 new topics and 106 new posts across meta.discourse.org, drawing 103 likes. The top contributors by likes this period were:

Interesting Topics

#Announcements

  • PostgreSQL 18 upgrade for self-hosters — Chrisr announced the rollout of PostgreSQL 18 in the Discourse Docker image, with detailed instructions for single-container and data-container setups, plus warnings about disk space (the check now requires 2x the DB size in free space). Commenters hit issues ranging from pg_dump failing on single-CPU hosts (@nachocaballero, @Ivan_Rapekas) to upgrade-loop recovery paths (@chrisc); Chrisr fixed the core-count detection to use nproc --ignore=1. read more

ux

  • Where did the version information go? — Kjell and others questioned why the redesigned admin dashboard dropped version/technical info, with Ed_S feeling it’s “marketing-led” over engineering-led. Lilly observed the dashboard is now geared to “community managers,” and Mcwumbly explained the team’s intent to consolidate version details into the “Manage updates” page. read more

  • I don’t see the red line for last visit — Ed_S briefly feared the “red line” indicating unread posts had been removed, but Lilly and Canapin confirmed it still displays normally; NateDhaliwal noted a transient miss after a page refresh but it returned. read more

development

  • Clarifying the ‘posts read’ TL3 promotion logic — NateDhaliwal struggled to understand why the TL3 requirement multiplied posts by a percentage and took a minimum; Mcwumbly explained that tl3_requires_posts_read is a percentage bounded by a cap, making the math clear. read more

  • Now in Beta: Plugin to see TL3 Progress for TL2 users — EricGT raised a nuanced edge case: muted categories can inflate the “posts read” requirement. He proposed a category-by-category breakdown in the plugin to show eligible vs. read posts, which NateDhaliwal noted core itself lacks. read more

#Self-hosting

  • Any cheaper alternatives to Hetzner? — Lilly, Merefield, and Jagster dug into running Discourse on minimal hardware. Jagster shared real-world numbers from a 4-vCPU / 8GB server running a dual-container setup with 1000–1500 daily visitors and needing 4GB swap during rebuilds; Merefield suggested 3+ cores for dual-container comfort. read more

  • Configure a supported tracking branch to get Discourse software updates — Ghorbani questioned whether git pull remains necessary in the daily upgrade workflow. David confirmed it’s effectively redundant—launcher auto-detects and pulls the latest commit—though Ed_S prefers to play it safe and run it anyway. read more

#Praise

  • Dependent Plugin Settings are … AWESOME! — Merefield showcased the new dependent settings feature (settings visible only when relevant), calling it “:sparkles: fantastic” for reducing plugin config clutter and cognitive load. He shared pointers to the schema docs and examples from the Chatbot plugin’s settings.yml. read more

Support

  • Hola, me gustó el theme actual que tiene Discourse — Picho_Pelis asked about Meta’s branded theme; Canapin explained it’s not public, linking to prior discussion about the custom nature of Meta’s look. read more

  • Cannot view post preview in mobile composer? — FishHead reported that the rich text editor toggle fails on markdown like [color=red]. Chapoi said the plan is to improve the toggle and only re-instate the preview button if that proves insufficient, recommending the community Mobile Composer Preview component for now. read more

  • Unable to switch accounts—Sign In automatically logs into the previous account — FlowCaffe described getting locked out of an admin account in Chrome; Pfaffman explained the Discourse ID single-sign-in flow, suggesting a logout at id.discourse.com or impersonation via the Admin user page. read more

  • What happened to claiming reviewables? — Darkpixlz couldn’t find the “claim” button in the review queue. Lilly and Moin traced it to an admin site setting (now optional), and Darkpixlz confirmed that solved it. read more

#Feature

  • Add interface preferences to individually hide Suggested and Related topics — Akanora proposed two separate user-level toggles (hide Suggested / hide Related) to reduce clutter, explaining his choice might vary per-community; Mcwumbly asked probing follow-ups about real-world usage patterns. read more

#Plugin

  • Discourse Chatbot :robot: — Merefield published a comprehensive PR round-up for the Chatbot plugin (v2.4.1), covering new local reasoning strategies, a semantic blocked-question gate using embedding similarity, replacement of the unsafe SafeRuby evaluator with Dentaku, and adoption of Zeitwerk loading. read more

  • Discourse Workflows — Sam announced a new PR adding interaction API support to Discourse Workflows and invited testing in a trial environment; Eviepayne also left feature-gap notes (e.g., missing pagination in the HTTP request block). read more

Activity by the Team Group

  • Chrisr posted the flagship PostgreSQL 18 upgrade guide, then worked through the comments: correcting the disk-space check to 2x DB size, fixing the single-CPU pg_dump job count bug, and explaining how to postpone or recover from failed upgrades. read more

  • Mcwumbly provided the canonical explanation of the TL3 “posts read” percentage calculation and cap, and offered a thoughtful breakdown of why the admin dashboard now targets “community manager” vs. “sysadmin” hats, directing users to the “Manage updates” page for version info. read more | read more

  • Chapoi responded to UI feedback in two threads: confirming the rich-text-editor preview toggle is being improved (with a third-party component as a temporary patch) and clarifying that the Welcome Banner is intentionally hidden on small screens, including a CSS snippet to override it. read more | read more

  • David clarified that ./launcher automatically pulls the latest discourse_docker commit, making a manual git pull unnecessary in standard workflows. read more

  • Sam acknowledged Daily Summary feedback and committed to a validation rework (“may take a week or 2”), and also shepherded a new Workflows PR adding interaction API support. read more | read more

  • Tgxworld stepped in on the Spanish-language install thread to tell Picho_Pelis that a recently pushed bug had been fixed and a launcher rebuild app should resolve the postgresql.conf failure. read more

  • Pfaffman diagnosed an account-switching lockout caused by Discourse ID single sign-on, suggesting logout at id.discourse.com or admin impersonation as workarounds. read more

Between the PostgreSQL 18 migration drama, a flood of Chatbot PRs, and a detour into music theory, it seems even the most technical days on meta can still end with a tune! :musical_notes:

909

Today on meta.discourse.org…

It’s been an action-packed 24 hours on the meta. From a major self-hosting upgrade to AI API additions and even some off‑topic music talk, the community has been buzzing. Here’s the daily digest.

Key Stats

  • 178 new posts and 46 new topics were created in the last day.
  • 249 likes were given across those posts.

Top users by posts and likes:

Interesting Topics

#Announcements

The big news of the day was the PostgreSQL 18 upgrade for self‑hosters, announced by Chrisr. The upgrade is now in the Docker image and requires ~2x database size free disk space. Many users shared their experience: Richie watched the migration live with a shell command, Sandra.Mccollum hit a snag that was resolved by manual steps, and Pfaffman reported successful upgrades via his dashboard. The thread also covers workarounds for single‑CPU hosts and changing locale provider read more.

In the same category, the emphasized admin dashboard redesign is attracting feedback. Kjell misses the quick access to version info and disk space, and Lilly simply reverted to the old dashboard on her sites. Mcwumbly points to a related discussion about the missing version info read more.

Finally, Sam announced the Gemini Interactions API support in Discourse AI. The new provider adds tool call streaming, code execution, and Google Maps integration, replacing the legacy generateContent API for new setups read more.

#Praise

A short but sweet topic celebrated the new dependent plugin settings feature. Merefield demonstrated how these settings hide irrelevant configuration options in Chatbot, calling it “really chef’s kiss”. NateDhaliwal asked for docs, and Merefield linked to the official schema and specs read more.

#Feature

The username template parameter in AI personas was merged into core. Falco merged the PR, but Sam later warned about potential system prompt churn in multi‑user chains. He also noted that some hosted models currently discard the name field and that a patch is in the works read more.

Another feature request, suppress notifications for tag changes from Steradiant, quickly received a pointer from Moin to existing site settings disable_tags_edit_notifications and disable_category_edit_notifications, as well as the bulk tagging modal’s notification checkbox read more.

Support

Several users reported problems after the PG18 update. Sandra.Mccollum’s site initially went down; she fixed it by manually updating PostgreSQL and libvips inside the container, and later successfully upgraded her second site via CLI instead of the web UI read more. Ed_S suggested that the web‑based updater may only do a single rebuild, which might not be enough for a DB major version bump read more.

In another thread, Scavin asked about database cleanup before the PG18 upgrade. Ed_S clarified that the needed free space is now 2x, and Falco noted that tables like ai_api_audit_logs have retention settings, while incoming_links and topic_views are meant to be kept forever read more.

On the mobile front, FishHead cannot view post preview in the mobile composer because the rich text editor doesn’t support some Markdown extensions like color tags. Chapoi acknowledged the limitation and said the toggle might be improved, or the preview button reinstated later read more.

A more exotic support issue involved using a Unix socket between Caddy and Discourse, leading to PG::InvalidTextRepresentation errors. Willy shared his config, Falco diagnosed a proxy misconfiguration, and Willy eventually suspected a stale socket after rebuilds read more.

#Community Building

A lively discussion on the drop in community activity for support forums was sparked by HAWK’s AI agent analysis. He argued that communities with direct audience relationships are better insulated from search volatility. Nickdb and Tris20 chimed in on AI hallucinations, while Nathank shared that he uses ask.discourse.org for quick answers and only returns to meta for complex questions read more.

In the same category, HAWK also posted about scalable engagement models like webinars and office hours, asking for other one‑to‑many formats. Mcwumbly highlighted how feature announcements are usually made by the people who built them, which invites direct community feedback read more.

enterprise

The discussion on scalable engagement was cross‑posted under enterprise (same topic as above). We grouped it under #Community Building, but since it’s also tagged enterprise, we’ll mention it here: HAWK’s topic drew practical advice on turning internal knowledge into reusable community sessions read more.

#Self-Hosting

Ghorbani asked about the necessity of git pull before rebuilds in the classic switching‑between‑release‑channels guide. David explained that the launcher automatically updates itself, and Ed_S added that manually running git pull is harmless. The OP was updated to reflect modern “channel” terminology read more.

ux

The interface for adding users to groups on mobile is borderline non‑functional, as Stephtara demonstrated with screenshots. Chapoi confirmed a larger redesign is planned but provided an immediate fix in a PR read more.

Closely related, Moin raised that the version information has disappeared from the admin dashboard. While the info exists in the browser console, he argued it should be available in safe mode as well, and Lilly wondered why the update page wasn’t a sufficient replacement read more.

Mcwumbly started a topic on improving the “update Discourse” page, inviting ideas. Asa contributed a detailed breakdown of status states, a version card, and a proposal to distinguish between “up to date”, “a few commits behind”, and “security update” read more.

development

A quick tip for theme developers: Andrew_Rowe asked how to inject HTML only on one page. Awesomerobot shared a Glimmer component using the router service and defaultHomepage() to conditionally render in the outlet read more.

#Plugin

The Discourse Chatbot had a major update to v2.4.1, as summarized by Merefield: new local reasoning strategies, a semantic blocked‑question gate, and a move from SafeRuby to Dentaku for calculations. He also highlighted a security fix for SafeRuby vulnerabilities read more.

Another plugin, Resenha, got a quick fix for an error when deleting voice rooms. Satonotdead reported the 500, Falco merged a PR, and the user confirmed the fix solved it read more.

Activity by the Team Group

  • Chrisr played a central role in the PostgreSQL 18 upgrade announcement and follow‑up. He explained the disk space requirements, corrected the 3x to 2x, addressed single‑CPU host issues with nproc --ignore=1, and gave guidance on postponing the update post 1, post 6, post 30.

  • Falco merged the PR for the username template parameter in AI personas post 5, clarified retention recommendations for database tables post 3, and fixed the Resenha deletion bug post 80. He also commented on the Caddy/Unix socket issue post 3.

  • Sam announced the Gemini Interactions API post 1 and contributed to the discussion on the username parameter, warning about potential system‑prompt thrashing post 8. He also acknowledged plans to improve the daily summary feature post 298.

  • Mcwumbly shared insights on scalable engagement models post 2, provided a link to the version info discussion post 47, started a topic on improving the update page post 1, and clarified the intent behind an update history view post 3. He also moved a discussion to a better category post 5.

  • David answered questions in the release channel switching guide, explaining that the launcher auto‑updates itself and that manual git pull is rarely needed post 39, post 45.

  • Zogstrip helped with two bug reports: he asked for additional context in the deletion of categories failure post 2 and acknowledged a fix for the grace period edits media review bypass post 3. He also noted that deeper changes to the review system would require more planning post 5.

  • Tgxworld provided a quick “please rebuild again” response to the installation failure topic after a recent bug was fixed post 3.

  • Awesomerobot shared a GLimmer component for conditional HTML injection post 2, gave advice on password resets with unknown emails post 2, and fixed the invite restricted issue with a combined PR post 3.

  • Martin responded to concerns about the new unified topic list view, explaining how unread counts are still available and offering to discuss a user preference for showing replies only post 39.

  • Chapoi was busy on mobile UX: he acknowledged the group‑adding interface problem and pointed to a PR post 3, commented on the missing preview in the composer post 19, reported a fix for the overflow in the activity‑by‑category section post 3, and explained the welcome banner behavior on mobile post 4.

Yesterday we saw everything from upgrading PostgreSQL to jamming on jazz piano — proving that this community can talk tech and tune‑ups in the same breath, with rhythm and harmony to spare! :musical_note:

910

Today on meta.discourse.org…

Key Stats

Over the last 24 hours, 196 new posts were created across 63 topics, clocking 285 likes in total. The conversation spanned everything from SSL installation nightmares and PostgreSQL 18 upgrades to AI strategy polls and mobile UX gripes.

Top users by number of likes received today:

User Likes Posts
HAWK 18 8
Chapoi 16 11
Moin 16 11
Merefield 16 10
Lilly 12 8
Sam 12 7
Satonotdead 9 9
Falco 9 4
Stephtara 8 7
Ed_S 8 2

Interesting Topics

#Self-hosting

#Community Building

#Announcements

  • The PostgreSQL 18 update for self-hosters thread stayed busy. Chrisr explained why data checksums are disabled during upgrades (alignment with internal benchmarking, plus a pg_upgrade gotcha if checksum settings differ), confirmed PG15 clients remain for backup/restore compatibility, and noted that a future OS upgrade on hosted platforms drove the switch to the new builtin locale provider. Richie shared a watch command to monitor migration progress (his 35GB migration took ~10 minutes), while Ed_S suggested a while loop with free -h to preserve output. Jericson reported that only the default site migrated on his multisite setup, prompting Pfaffman to share his manual multi-DB approach. Jimmy0017 asked about bypassing disk space checks and about Google Cloud SQL compatibility.

  • Sam announced support for the Gemini Interactions API in Discourse AI, recommending the new /v1/interactions endpoint and labeling the old one Google Gemini (Legacy API). The new provider adds tool call streaming, native code execution, and Google Maps integration, alongside existing Search and Fetch tools. One caveat: “no thinking” can no longer be set on 2.5 flash models.

  • The redesigned admin dashboard announcement drew continued feedback. Kjell lamented missing version info, backup/disk-space indicators, and problem checks; Lilly suggested keeping the old dashboard for admins alongside the new one; and Sren-1 noted the Docker manager plugin may have been removed from his install. Mcwumbly pointed to the version info discussion for more context.

Support

ux

  • Stephtara documented mobile UX problems when adding users to groups — half-hidden search results, un-findable selected states, plus a tag-selector flow that traps the composer. Moin linked the related mobile tag selector topic, and Chapoi noted a bigger replacement project is on the backlog with an interim fix PR. Stephtara also suggested the tag dropdown should roll up when the search field loses focus.

  • Mcwumbly solicited feedback for improving the “update Discourse” page. Asa offered a detailed proposal: distinguish “a few commits behind” (informational, no action needed) from actual release/security signals; bring back the version number prominently; render the cached version check immediately; show an update history with changelog links; display which components need ./launcher rebuild app; and surface .discourse-compatibility plugin pinning. A live mock was shared for anyone to poke at. Ed_S added backup advice and a note about posting a CLI rebuild fallback for failed updates.

  • In Where did the version information go?, Moin noted that /admin/update doesn’t work in safe mode because it depends on the docker_manager plugin, making version lookup cumbersome during troubleshooting.

#Site feedback

enterprise

Marketplace

  • T_Müller advertised a contract role for a Ruby + Discourse specialist to lead an integration with an existing Community app at a large US company — covering Okta/OIDC SSO, group mapping, Ruby adapters, webhook pipelines, feature flags, and a cutover/rollback plan. Several users responded with PMs expressing interest.

Activity by the Team Group

From SSL certificate exorcisms to AI citation pub-quizzes, today’s round-the-clock fixes and community shares prove there’s never a dull build — see you in the next git pull.

911

Today on meta.discourse.org…

Key Stats

Over the last 24 hours, the community has been buzzing with activity:

  • Total new posts: 161
  • Total new topics: 51

Top contributors (by likes received):

User Likes Posts
Moin 25 12
Lilly 21 12
Chapoi 20 15
Merefield 15 5
Nat 8 4
Don 8 2
Picho_Pelis 7 7
Jordan.Vidrine 7 5
Roke_Julian_Lockhart 7 4
Southpaw 7 2

Interesting Topics

Self-hosting

  • Ya estoy cansado, he instalado discourse en varios VPS ninguno me funcionan – A frustrating installation saga that ended with the surprising discovery that the domain debatehosting.co was never actually registered! Supermathie demonstrated via whois that the domain simply doesn’t exist, which explained the endless Let’s Encrypt and nginx errors. The topic also highlighted the importance of sharing solutions properly – Lilly gently reminded the OP to mark the helpful reply as the solution. Read more

  • How should a user request a password reset when they do not remember the e-mail address that one of their accounts utilises? – A deep discussion sparked by an OpenAI SSO change that left users without a password. Roke_Julian_Lockhart explained his use of email aliases and the struggle to recover an account when the email is unknown. The thread evolved into a broader conversation about the hide_email_address_taken setting and led to a feature request to always allow username‑based password resets. Read more

Support

  • Discourse-ID displays its own logo & name instead of my forum’s – Chapoi initially dismissed this as not a bug, but Moin's keen eye showed that some forums display their own name while others show only “Discourse”. Chapoi provided a workaround (clearing credentials and re‑enabling the plugin) that worked for the OP. Rishabh confirmed a dedicated “re‑register” button also exists in the admin panel, though it was disabled for some self‑hosters. Read more

  • Can I add additional languages to the Language Selector? – Karthik_K1 wanted to add Indian languages (Hindi, Telugu, Tamil, etc.) to the AI translator’s language selector. Nat explained that the selector changes the whole Discourse locale, not just post content, so unsupported languages aren’t available. He suggested a plugin to register additional locales, and Moin added that contributing translations to Crowdin would ultimately benefit everyone. Read more

  • How do I make my group mention notify group members? – Stephtara created a group and expected mentions to notify all members, but one member didn’t receive a notification. Lilly and Moin pointed out access restrictions (e.g., private categories) and suggested testing with a direct username mention to isolate the issue. The conversation linked to older discussions on group mentions and private category notifications. Read more

Announcements

  • Help Us Test the Composer Redesign – Chapoi unveiled an experimental new composer layout with a cleaner, document‑style title input, a bottom‑docked toolbar, and a slide‑up expanding editor on mobile. Early feedback from Darkpixlz, Don, and NateDhaliwal discussed the title size, the AI‑suggestion button placement, and the swiping behaviour. Chapoi promised fixes for colourless category icons and keyboard dismissal. Read more

  • Granular group-based permissions for anonymous and logged in users – This ongoing rollout saw new CSS classes (anonymous_users and logged_in_users) added to the official groups‑CSS theme component via a PR from Lilly. Martin also merged updates to several official components to use the new group resolution APIs, moving the feature forward. Read more

  • PostgreSQL 18 update for self-hosters – Lilly shared a detailed, step‑by‑step guide for upgrading to PostgreSQL 18 on a dual‑container setup behind Cloudflare, including backups, maintenance pages, and disk cleanup. Supermathie answered questions about Google Cloud SQL (test it!) and others discussed space‑check bypasses. Read more

Feature

  • “Regular mode” for admins and moderators (e.g. something like “sudo”) – Sam proposed inverting the default: admins should behave like regular users unless they explicitly toggle admin powers on. Mcwumbly agreed and suggested a header toggle with clear visual state. Lilly raised concerns about staff notifications and asked for a site setting to keep current behaviour. Read more

  • Always allow username-based password reset – Roke_Julian_Lockhart filed a feature request after the OpenAI SSO fiasco. Southpaw explained that the hide_email_address_taken setting (enabled by default) restricts the password reset form to email only. Pfaffman later admitted his earlier objections were misplaced and called the restriction “a terrible idea”. A PR is now under consideration. Read more

  • Multiple profiles for one user – FishEmoji proposed a PluralKit‑style system for Discourse, allowing a single user to post under multiple “proxy” personas (e.g., for roleplay or alt identities). Satonotdead acknowledged the idea’s appeal but noted the difficulty in integrating it with Chat. Read more

  • Automatically update translated category descriptions – Moin noticed that German category descriptions on Meta were out of sync after recent edits. Nat confirmed a fix had been merged (PR #42407) to re‑sync translations automatically. Read more

Site feedback

  • Meta error banner - MERGE_BRANCH deployment failed – Lilly reported a strange banner on Meta about a failed branch deployment. Tgxworld fixed it quickly, but NateDhaliwal noticed it persisted for a while. David explained it was a mistake in the hosting system that displayed an internal error to all users, and that it has been corrected. Read more

UX

  • Discourse meta icon missing on Discourse ID login page – Canapin spotted a broken logo on the Discourse ID login page. Jordan.Vidrine reproduced the issue and explained that Discourse only re‑sends logo URLs when site settings change, leading to stale links. A fix to gracefully fall back to the name is on the way. Read more

Development

  • Facebook-style Topic Modal - Is it better? – Don shared a detailed technical write‑up of his prototype that renders full topics in a modal using native Glimmer components instead of an iframe. He explained how he patches core services for routing, handles infinite scroll, and implements first‑paint skeletons. Damian_Boon expressed interest in testing it. Read more

Activity by the Team Group

The Team group was highly visible across Meta today, driving discussions, fixing bugs, and sharing updates.

  • Chapoi continued to lead the composer redesign effort, answering feedback on the new layout and confirming fixes for reported issues like colourless category icons and swipe‑to‑close behaviour. See his main announcement and his follow‑up on the AI title button.

  • Sam weighed in on the admin “sudo” mode discussion, suggesting a paradigm shift where admins start as regular users and enable admin powers temporarily, as seen here. He also fixed a JSON formatting bug in the AI plugin affecting local LLMs, described in this support thread.

  • Lilly was a whirlwind of activity: she helped troubleshoot group mentions, contributed to the PostgreSQL 18 upgrade thread with a comprehensive guide, and even submitted a PR to add anonymous/logged‑in user CSS classes to the groups theme component. Her handiwork is visible in the group permissions topic and the Postgres upgrade topic.

  • Nat clarified the language selector limitations and suggested plugin‑based workarounds, in this reply. He also confirmed a fix for stale category descriptions, linked in the translation topic.

  • Martin merged PRs for official components to adopt the new group permissions model and posted an update on the roadmap, as seen here. He also commented on the unified new view topic, reinforcing the decision not to add a separate new/unread split but offering to support theme components that do. Link

  • David and Tgxworld quickly addressed the Meta error banner and explained the root cause, as seen in this site feedback thread.

  • Rishabh clarified how the Discourse ID re‑registration button works and confirmed a fix for the missing icon issue, in this topic.

  • Jordan.Vidrine investigated the broken icon on the Discourse ID login page and provided a workaround, posting here.

  • Tannerabread fixed the bulk archiving messages visual glitch and the wrong join date in reviewable insights bug, sharing links to the PRs in this thread and that one.

  • Supermathie helped solve the installation mystery for the frustrated self‑hoster by checking the domain’s existence, in this post.

  • Tobiaseigen reported a broken link in the Custom Wizard plugin documentation, as seen here.

  • J.Jaffeux responded to feedback on the Discourse Workflows plugin, committing a fix for name collisions when pasting steps, announced here.

  • Ted confirmed a fix for the Patreon dashboard notice that persisted after the issue was resolved, in this support thread.

From unregistered domains causing midnight headaches to a sleek new composer on the horizon, it’s been a day of creative problem‑solving and collaborative debugging. Here’s to many more threads where the mystery is solved by a simple whois!

912

Today on meta.discourse.org…

Key Stats

Over the past 24 hours, the community has been buzzing with activity:

  • Total new posts: 150
  • Total new topics: 60
  • Total likes given: 313

Top contributors (by likes received):

User Likes Posts
Chapoi 22 9
Satonotdead 19 7
Moin 18 9
Awesomerobot 18 2
Canapin 17 6
Lilly 14 5
Pfaffman 14 5
Mostapha 14 3
NateDhaliwal 13 8
Nat 13 6

These power users drove discussions across design, feature requests, and self-hosting challenges.

Interesting Topics

Here’s a curated selection of the most engaging discussions from the last day, grouped by category.

#Announcements

#Community Building

  • For the Next Decade of the Internet (2026 Edition) – Mcwumbly revived the evergreen question about Discourse’s role in the future of online communication. Awesomerobot delivered a thoughtful analysis predicting that typing into boxes will remain the core interaction, while highlighting the threat of AI chatbots and the importance of community-owned spaces. Ed_S and Satonotdead added perspectives on polarization and the need for both public and hidden “spaces of resistance.”

#Feature

Support

ux

enterprise

  • Public vs Private Discussion – HAWK opened a strategic discussion about when to engage publicly versus privately on enterprise Discourse instances. Nickdb shared their community’s strict no-DM policy to maintain quality and oversight.

#Theme component

bug

Activity by the Team Group

Our dedicated Team members have been hard at work addressing feedback, fixing bugs, and engaging with the community:

That’s a wrap on a day filled with composer debates, PostgreSQL upgrades, and thoughtful musings on the next decade! May your threads stay lively and your ping counts stay low. :rocket:

913

Today on meta.discourse.org…

Key Stats

Over the past 24 hours, the community has been buzzing with 117 new posts across 54 topics, sparking 170 likes. The most active contributors were:

User Posts Likes
Awesomerobot 8 19
Moin 7 14
RGJ 7 13
Don 3 11
Heliosurge 7 8
Sk-Or-V1-Contents 5 8
Nat 3 8
Arkshine 2 7
NateDhaliwal 5 6
Mcdanlj 4 5

Interesting Topics

development

#Announcements

  • The composer redesign is open for testing. Heliosurge reported the tag icon is too small on mobile and found issues with the rollout settings initially, but it worked after a retest. Canapin noted a minor rounding inconsistency on the selector, and Sk-Or-V1-Contents demonstrated a flashy animation and a double-tap problem when minimizing the editor.

Support

ux

  • Moin raised a point about “vote returned” notifications even when vote limits are disabled. Awesomerobot agreed and referenced a PR to improve this.

  • Satonotdead wondered if “Me too” should be hidden on category description topics. Awesomerobot concurred and shared a PR to exclude those topics.

  • RGJ found that the “All members” button when creating a category assigns everyone even when login is required, which could accidentally expose private content. Chapoi asked Martin for thoughts, and RGJ suggested a three-button approach.

#Theme component

#Sysadmins

  • Raykholo asked about using Garage instead of Minio in Mcdanlj's deployment guide. Mcdanlj confirmed it’s feasible, and later shared a corrected transparent-huge-pages configuration. Raykholo then documented a deep-dive on running Discourse with Garage and Cloudflare, highlighting silent incompatibilities.

#Feature

  • The change to split “new” into “topics” and “replies” is being debated. Awesomerobot explained the reasoning, and Moin suggested a possible enhancement to the custom top navigation links component.

#Site feedback

bug

  • RGJ reported that a user’s bounce score doesn’t reset when their email is changed, suggesting it should be per-email rather than per-user.

Activity by the Team Group

The Team group has been active across several fronts, often responding to community feedback and fixing issues in real time.

  • Awesomerobot provided direct support on the composer redesign, discussing tag icon sizing, the storage_stats.json endpoint, and the logic behind the new “new” menu structure. He also implemented fixes for the “vote returned” notification and the “Me too” visibility on category description topics.

  • Moin helped users with translation settings, pointed to relevant feature requests, and engaged in the ongoing debate about the new “new” navigation, suggesting a possible configurable approach.

  • Nat clarified translation behaviours and promised to consider a feature request about restricting interface languages, while also updating the Content Localization documentation.

  • Martin investigated the composer redesign rollout issue and confirmed Meta’s own group-based settings.

  • Don responded to feedback on his topic modal component, adding new settings and rate-limiting to improve performance.

  • Falco swiftly contributed a pull request for the gamification workflow suggestion.

  • Tshenry fixed the Hide Likes theme component and is working with Moin on the Restrict uploads component.

  • Angus raised a PR in core to fix a niche custom field preloading bug affecting the Custom Wizard plugin.

  • Lindsey acknowledged the ZenDesk API token deprecation and said the team would review its impact.

Sign-off: With all these fixes and features landing, it seems like the Discourse team is on a roll — but let’s hope the topic modal doesn’t hit the rate limit before we do! :rocket:

914

Today on meta.discourse.org…

The sun never sets on the Discourse community—here’s your daily briefing on the latest happenings from the past 24 hours.

Key Stats

Over the last 24 hours, the community has been buzzing with activity:

  • 58 new posts and 28 new topics were created
  • 78 likes were given across all posts

Top Contributors by Likes Received:

User Likes Posts
Moin 32 5
Merefield 8 4
RGJ 6 2
HAWK 4 1
Sk-Or-V1-Contents 3 4
Eviepayne 3 2
Lilly 3 2
Weallwegot 3 1
DRRO 2 4
NateDhaliwal 2 4

Interesting Topics

Here’s what the community has been discussing, organized by category.

#Praise

  • Moin kicked off a wonderful contributor appreciation thread for the August 2026 release, thanking both code contributors and translators for their hard work over the past six months, with HAWK quickly expressing gratitude on behalf of the community. The thread also sheds light on the broader release announcement and community engagement strategy.

#Theme component

#Feature

#Announcements

Support

bug

  • RGJ reported a bug in email bounce score management: the score doesn’t reset when a user changes their email address, and the error message even says “some bounces were received recently from that email,” suggesting the score is being associated with the user rather than the specific address.

  • Moin confirmed a fix was merged for the monthly recurring automation not running as expected issue, and Gassim is planning to verify it works as intended next month.

  • Small-Lovely-Cat submitted a performance fix for Redis key traversal issues when clearing 404 topic cache, which could cause timeouts on large Redis databases and has been addressed in PR #42457.

  • Sk-Or-V1-Contents reported a jittery keyboard bug in the “languages I understand” input box on mobile, complete with detailed reproduction steps and a screen recording, in the content-localization area.

  • Dennisjbr shared an experience related to Gmail dot variant email issues, mentioning they’d had another report but couldn’t find their notes on it.

#Plugin

  • Jagster noted an admin warning about the locations plugin containing outdated code, but Merefield announced the resolution with a friendly nod to contributor Cvx—recent PRs have modernized the plugin’s core APIs, fixed security vulnerabilities, and improved error handling.

  • RGJ confirmed that a contributor had resolved the deprecation notices in the Discourse Dynamic Groups plugin, after they were originally reported by Nathank.

  • Gassim asked several questions about the Discourse Calendar and Events plugin, specifically about Zoom integration, whether “Ready for local test” suffices for the Zoom app, and how to restrict the “join meeting” button to logged-in users or specific groups.

  • Satonotdead raised a privacy concern about the Fingerprint browser fingerprinting plugin, wondering how the plugin handles users who actively spoof their fingerprints for privacy reasons, given their own privacy-conscious stance.

development

#Self-hosting

ux

Activity by the Team Group

Discourse team members have been active across several areas today:

With all these fixes rolling out, it looks like someone had a very productive day herding :cat_face: cats and squashing :bug: bugs! Now let’s see what tomorrow brings! :rocket:

915

Today on meta.discourse.org…

Key Stats

Over the last 24 hours, 76 new posts were created across 37 topics, accumulating 81 likes. Here are the top users by activity:

User Likes Posts
Moin 10 7
Merefield 10 4
Per1234 9 2
Kcahtoor 5 6
Chapoi 4 2
NateDhaliwal 3 5
Gassim 3 3
Chrisr 3 2
Lilly 3 2
Jay-C 3 1

Interesting Topics

#Feature

  • Add support for ‘personal notes’ on posts – Lilly suggested using private messages as a workaround, while Awesomerobot noted bookmarks are a natural fit. Later, Merefield announced building a plugin for this, and finally published it as Bookmark Notes – turning bookmarks into private personal notes attached to posts. Discuss

  • Discourse Calendar & Events: Webhook triggers & Automations plugin – Gassim requested richer webhook events (user going/not going/participation summary) and automation triggers for event interactions. Lindsey responded that these might be considered for the new Workflows feature. More

  • Could long footnotes be scrollable? – One1 asked about making footnote popups scrollable and reported a quoting bug. Lilly requested a separate bug topic for the quoting issue. Thread

  • More direct access to topics with new replies – NateDhaliwal suggested adding a sidebar link to /unread (which excludes new topics) for quicker access. Read

  • Multiple profiles for one user – FishEmoji wondered about PluralKit-like profiles for chat, with Heliosurge uncertain about feasibility. Topic

#Announcements

  • Help Us Test the Composer Redesign – Per1234 provided detailed feedback on the borderless design, including Enter key behavior and missing right margin. Chapoi is working on improvements. Watch it

  • PostgreSQL 18 update for self-hosters – Kcahtoor reported multisite migration issues. Chrisr merged a fix and provided detailed rollback steps. Update

  • Introducing the unified new view for the topic list – Newbit1337 questioned the Dismiss behavior, then found the “and stop tracking” option. Announcement

#Self-hosting

  • I upgraded to latest and lost everything – Kcahtoor described a multisite upgrade disaster, leading to Chrisr’s fix in the Postgres thread. Moin pointed to the resolution. Original

  • Fresh install/migrated! – ALinux shared that adding more CPU cores drastically improved performance on his old server. More

bug

ux

  • “All members” when creating a category assigns everyone – Martin responded to feedback, proposing a three-button UI (public / members only / private) and clarifying migration plans for everyone. Read

  • Scrollbar? in the post menu when removing a reaction – Moin spotted a visual jump when removing a like. Discussion

  • Discrepancy in display of user activity – Sterretje asked why the Topics tab doesn’t show post excerpts. Moin explained it’s because titles are sufficient for topic activity, while post activity needs content. Thread

Support

#Migration

  • Accepted solutions: plugin + migrating markers from Khoros – Gosia.Murawska asked about carrying over accepted solutions. Italo confirmed it’s possible if the plugin is active during import. More

#Data & reporting

  • DSA Content Moderation Reporting + Statements of Reasons Requirements – Jay-C outlined the need for structured suspending reasons and taxonomy alignment, asking for community advice. Read

#Plugin

  • Bookmark Notes (new plugin) – Merefield announced this plugin, turning bookmarks into private personal notes with Markdown, toggle buttons, and privacy controls. Explore

#Extras

  • nodeBook: CNL knowledge graphs in posts – G_N introduced a new component for rendering interactive knowledge graphs, concept maps, and Petri-net simulations directly in posts. Dive in

General

  • Sport communities and calendar? – Fuse asked how others use the calendar for sports, inspiring ideas about scheduling and chat. Join

Activity by the Team Group

  • Chrisr fixed the multisite PostgreSQL upgrade issue – he merged a patch and posted detailed steps to revert and retry. He also acknowledged the broken state earlier. Related: I upgraded to latest and lost everything

  • Sam responded to multiple bugs – he thanked the contributor of the Redis fix, suggested a workaround for bounce score reset, and tagged Martin about category permission issues.

  • Martin discussed category permission changes – he explained the intended migration plan and promised a three-button design. He also acknowledged the bug report.

  • Chapoi is actively iterating on the composer redesign – he responded to Horizon theme issues and asked Renato about Enter key behavior.

  • Lindsey provided direction on automation – she replied to the calendar event triggers request, steering towards the new Workflows feature.

  • Awesomerobot approved a plugin PR – he commented on the plugin outlet PR and was thanked by Merefield for the “approval on a Sunday”.

  • Renato is investigating the mobile composer paste bug – confirmed by Sam in this post.

That’s the pulse of meta.discourse.org for the past day – from Postgres rescue missions to bookmark-powered memory palaces. May your upgrades be smooth and your Redis keys be sparse! :rocket:

916

Today on meta.discourse.org…

It was another bustling day on Meta as community members showcased impressive new theme components, debated the finer points of category permissions and DSA compliance, and dove deep into AI agent behavior. :light_bulb:

Key Stats

Here’s a snapshot of activity on Meta over the last 24 hours:

Metric Count
New Posts 151
New Topics 56
Total Likes Received 227

Top Contributors by Likes

User Posts Likes
Merefield 11 23
Don 3 21
Falco 4 18
Moin 10 14
Damian_Boon 6 11
Jagster 8 10
RGJ 6 9
Sam 5 9
One1 11 8
NateDhaliwal 6 8

Interesting Topics

Here are the most interesting and active discussions from the past 24 hours, grouped by category:

#Theme-component

  • Don unveiled a brand-new Topic Preview Modal component that lets you open and interact with topics directly from the topic list without ever leaving it. The component renders the full interactive post stream—including likes, replies, edits, and bookmarks—inside a native modal, and Damian_Boon quickly contributed a workaround for Reddit-ish theme compatibility plus a configurable width read more. Jagster reported a math rendering glitch that Don promptly fixed in a commit, and NateDhaliwal queried why core’s PostList wasn’t reused—Don explained that the interactive post stream and bidirectional loading aren’t supported by that component read more.

  • Manuel quietly updated the Featured Topics component to fix a compatibility error reported by Helga_Razinkova, bringing the component back in line for everyone, and Cogdog confirmed the fix worked read more.

  • Roi submitted a pull request for the Clickable Social Icon Links on Profile component, which Weallwegot approved and merged shortly afterward read more.

  • Moin's update to the Restrict Uploads component was merged by Tshenry, meaning the component is now officially improved for everyone read more.

  • Moin's Mobile Composer Preview component received praise from Richie for restoring the preview button removed in a recent core change read more.

#Plugin

  • Merefield released Discourse Bookmark Notes, a plugin that turns bookmarks into private personal notes attached to posts and other bookmarkable content. The plugin keeps notes private per user, supports Markdown editing with preview, and integrates with existing bookmark reminders. A Pro extension available to GitHub sponsors adds a collapsible note panel, extended search, and a sortable notes column on topic lists read more. Jagster loved it (“something I didn’t know I need”), and Lilly applauded the sponsor-based approach to Pro extensions read more.

  • Roi flagged a deprecation warning in the User Response Times plugin, which RGJ acknowledged and said he’d fix in a few weeks read more.

  • Lebron reported ongoing issues with the Custom Wizard Plugin—wizards still can’t be accessed on non-staff accounts and settings revert to empty boxes despite saving read more.

  • A lively debate continued in the Discourse Fingerprint topic, with Overgrow arguing that browser fingerprinting isn’t a real privacy threat and has legitimate security use cases, countered by Jagster and Satonotdead pointing to EU legal precedents and class-action lawsuits against companies engaging in fingerprinting read more.

  • Tomve hit a stylesheet import error in the Landing Pages Plugin after a recent change, reporting an ActionView::Template::Error with a missing desktop stylesheet read more.

#Self-hosting

  • Wsmwktb asked whether opening a self-hosted Discourse to Discourse ID login poses signicant downsides. Falco dismantled each of the commonly cited “risks” as hallucinations, concluding that Discourse ID is a solid choice for getting many social logins with zero effort, provided you’re comfortable with not controlling exactly which login methods users see read more. Merefield cheekily suggested a staged rollout while linking to a search about the “downsides of walking along a seafront” read more.

  • The PostgreSQL 18 upgrade thread continued with Chrisr announcing a fix for broken multisite upgrades, providing detailed rollback steps for those affected read more. Peternlewis asked about a memory overcommit warning and noted his new database is significantly smaller than the old one, while Merefield reported the opposite trend on his instance read more.

  • Kcahtoor shared an insightful workaround after losing everything in an upgrade, explaining how the Postgres template file only targeted a single DB in multisite setups and providing a shell script to loop through all databases read more.

  • Ethsim2 documented a Let’s Encrypt/SSL edge case encountered while moving a standalone Discourse instance to a new VPS, where zero-byte .cer files blocked nginx from starting. The fix involved copying both the ssl/ directory and the letsencrypt/ state from the old server, with a full write-up on GitHub read more.

#Announcements (and blog)

  • Sam announced the release of delegated vision support in Discourse AI, enabling text-only models like DeepSeek v4 Flash to use the full feature set by delegating image understanding to a vision-capable model such as Qwen or Gemma. A new LLM configuration option now allows you to specify a separate model for image handling read more.

  • Chapoi posted a detailed progress update on the Composer Redesign, listing fixes implemented (title section rework, tag count, category name overflow, rounded borders) and feedback being worked on (keyboard behavior, flashy blue highlight, numeric tag counts) read more. Jagster reported a toolbar visibility bug that follows the original composer’s toolbar toggle state, which Chapoi confirmed read more.

  • The blog post “Introducing the All-New Admin Dashboard” was published, and Ed_S suggested adding a System section to make system stats (version, updates, disk space, backups) more visible read more.

  • Don shared insights from experimenting with animated SVGs for the Discourse splash screen, explaining that animating complex paths directly inside SVGs causes lag on mobile; wrapping the SVG in an HTML container and applying CSS transforms to the wrapper provides much smoother performance read more.

  • Moin clarified that the Ideas category type now acts as the toggle for Topic Voting; removing the type disables voting in that category read more.

Support

  • AkarinLiu was struggling to find the Font Awesome “seedling” icon in Discourse. Zogstrip explained it’s not in the default icon list and must be added to the SVG icon subset setting. Moin then walked through the steps, pointing out the regular (far-) version is a Pro icon while the solid version works once you add it without a prefix. AkarinLiu eventually realized they’d typed an extra prefix, quipping “I’m so silly, something that could have been done in a few minutes wasted dozens of them” read more.

  • Karthik_K1 asked how to restrict an AI Agent to only answer forum-related questions. NateDhaliwal suggested using the Forum Researcher or Forum Helper agents, but Karthik_K1 showed that even Forum Helper answered general questions. Falco then clarified that the test used the “Creative” agent, which has no system prompt, and recommended crafting a custom agent with a system prompt specifying how and when to answer—as done on ask.discourse.com read more.

  • NateDhaliwal reported that topics in muted categories don’t appear in /?state=muted, and Awesomerobot confirmed this is a gap—muted category topics are simply excluded from that view read more.

  • Soumya_Ranjan_Mishra asked about configuring self-hosted Claude/GPT API keys in Discourse AI. Satonotdead guided them to use the OpenAI provider for OpenAI-compatible endpoints and to consult the LLM docs for specific proxies, while Merefield offered paid support via GitHub sponsorship read more.

  • Moin confirmed that switching the interface language via the header dropdown no longer resets the content translation preference, saying “changing the interface language… no longer resets the content translation preference” read more.

  • One1 shared a detailed investigation of a mail-receiver deprecation warning persisting on the latest release image, tracing it to the mail-receiver code still posting the email parameter instead of email_encoded read more.

#Data-&-reporting

  • Jay-C raised the new DSA standardised Content Moderation Transparency Report requirements, explaining that Discourse’s current moderation tools can’t capture structured data like custom suspension reasons aligned with the DSA taxonomy, illegal-content vs. ToS violation indicators, contractual basis, or information source. HAWK, acknowledging they weren’t aware of the new template, committed to doing due diligence with their lawyer and coming back read more.

Marketplace

  • Thadeus confirmed they will proceed with Pacharanero for their Discourse UX Overhaul & Plugin Audit RFP, and left individual feedback for all other applicants read more.

ux

  • Sterretje noticed a discrepancy between the All, Replies, and Topics tabs in user activity—the Topics tab doesn’t show post excerpts. Moin explained this is by design: topic-focused activity uses a topic-list style, while post-focused activity benefits from content snippets. Awesomerobot noted it would be possible to display excerpts with a theme component, and suggested improving vague topic titles (or using the Workflows plugin to auto-improve them) read more.

  • Martin acknowledged that the “All members” option in new category creation assigning everyone is an unintended side effect and agreed with RGJ's suggestion to have three distinct buttons (public, members only, private) instead read more.

  • LWinterberg proposed replacing yes/no actions in the moderation review queue with concrete action buttons like Approve/Delete, to avoid the cognitive load of parsing questions where “Yes” means opposite things in rapid succession. One1 suggested going further with “Approve Topic”/“Reject Topic” labels read more.

  • One1 asked about creating a documentation category through the new simplified category creation flow, and HAWK pointed to the Discourse Doc Categories plugin and suggested creating a normal discussion category first read more.

#Feature

  • One1 proposed Previous/Next links for topics in Doc Categories, suggesting the category index could drive linear navigation with custom titles from the sidebar. Moin noted the idea of using doc index sections has come up before, and Satonotdead echoed that it’s a frequently requested feature for LMS content read more.

  • Gormus suggested adding a list of changed core and plugin settings to the Discourse Releases changelog and comparison views, similar to what staff_action_logs records read more.

  • One1 bumped the long-running personal notes on posts feature request with a link to Merefield's new Bookmark Notes plugin, which fulfills most of the request read more.

  • One1 revived a request for scrollable footnotes, and Canapin demonstrated the glitchy mobile behavior with a screen recording, while Jagster emphasized that footnotes are crucial for displaying AI-generated explanations read more.

  • Lindsey responded to a request for webhook triggers and automations in Discourse Calendar & Events, noting that the new Workflows feature is likely to supersede the Automations plugin, and these trigger types are “definitely on the table for Workflows” read more.

bug

  • RGJ raised concerns about the new category permission groups during beta, specifically the anonymous_users and logged_in_users groups. Martin acknowledged the concerns and discussed possible validations, while RGJ pushed back with examples of admin friction and implicit-permission complexity, leading Martin to agree the OP is a bug that will be fixed in the interim read more.

  • Falco provided a fix for the CDCK/MoM citations issue where summaries cited posts as “User1, User2, etc.” via pull request read more.

  • Tannerabread fixed the white screen on theme export in Theme Creator for the PWA, with a follow-up needed for the Hub read more.

  • Sam acknowledged a bug report about bounce score not resetting when a user’s email address changes, agreeing the real fix is to stop associating bounce score with users entirely and inviting a PR read more.

  • Sam thanked Zogstrip for merging a fix in avoiding Redis key traversal when clearing the 404 topic cache read more.

development

  • Damian_Boon thanked Don for getting the Facebook-style topic modal working, calling it “exactly what I was trying to achieve” read more.

#Migration

  • Gosia.Murawska asked whether accepted solution markers from Khoros can be carried over during import, and Italo confirmed yes—as long as the plugin is active during the import read more.

Community Building

General

  • Geoff asked about using the Discourse Calendar for sport communities, and Lilly shared her experience using it for a football schedule, including exporting the league schedule and training a bot to populate game dates read more.

Activity by the Team Group

A productive day for the Discourse core team, spread across announcements, fixes, and design iterations:

From topic modals that keep you browsing without a single click lost, to bookmark notes that finally remember what you were thinking — yesterday’s activity proved that the Discourse community can turn any “what if” into a shipped feature before lunch… just don’t ask us how much coffee was involved! :hot_beverage:

917

Today on meta.discourse.org…

Key Stats

In the last 24 hours, meta.discourse.org saw 171 new posts across 56 topics, receiving 214 likes in total. The most active members were:

Interesting Topics

#Community Building

Support

enterprise

#Theme component

#Feature

#Announcements

#Plugin

General

bug

Activity by the Team Group

From icon hunts to database migrations, the community keeps tackling every curveball — and if yesterday taught us anything, it’s that a good footnote scroll can make all the difference! :balloon:

918

Today on meta.discourse.org…

Key Stats

Over the last 24 hours, the community produced 117 new posts and 45 new topics, with 164 likes distributed across them. The most active contributors were:

Interesting Topics

#Community Building

  • OS_Corsair asked how to grow their community but struggled to articulate a clear purpose. NateDhaliwal and HAWK pressed for specifics, Moin questioned the value proposition, and Darkpixlz suggested the thread had run its course, recommending the user read existing advice. read more

Support

  • OS_Corsair asked where to create a banner topic. NateDhaliwal linked to the official guide, Twofoursixeight mentioned the pinning option, but OS_Corsair shared confusing screenshots. Awesomerobot advised more research and experimentation before asking. read more

  • Rinion reported that the AI bot kept auto-adding them to a private chat channel even though AI was disabled. Gabriel acknowledged the issue, implemented a fix, and confirmed that disabling the AI plugin or muting the channel should prevent it. read more

  • Wasd_The_Fourth wanted to know how to remove silences from flags for minor infractions. Moin linked to documentation on custom flags and questioned why off-topic flags would lead to automatic silences. read more

  • A user asked about FA icon seeding in Discourse. Zogstrip acknowledged good points and created a pull request to add proper search and pagination to the icon picker. read more

  • Marcozambi faced a restore failure due to S3 migration issues. Awesomerobot explained how to list missing uploads using rake posts:missing_uploads and suggested marking them as ignored to proceed. read more

enterprise

  • In the admin dashboard AMA thread, One1 asked if community managers could access the dashboard without admin rights. HAWK questioned the trust level, Ed_S noted the difference between admin and community manager roles, and Nickdb requested drill-down capabilities for user agents and geographies. Lindsey confirmed a more detailed traffic explorer is in the works. read more

  • Chau started a discussion about Voice of the Customer programs and how communities fit into them, inviting examples from others. Several people shared their experiences and asked clarifying questions. read more

#Announcements

  • Renato announced that pinned chat messages now stay in view with a sticky bar. The bar follows the user as they scroll, is dismissible, and can be managed through the existing pinning interface. Feedback is welcome. read more

  • In the Workflows preview topic, Satonotdead asked when to use Automations vs. Workflows. Lindsey recommended Workflows even for simple processes due to flexibility and visibility, and J.Jaffeux invited users to report anything they can’t do in Workflows but could in Automations. read more

  • The Solved improvements topic discussed allowing members to indicate they experience a reported issue. Sterretje asked if the button disappears when a solution is marked, and Moin confirmed with examples. read more

  • Jordan.Vidrine announced that the Post Type composer actions dropdown is moving to permanent and will be merged into core next week. read more

bug

  • Moin reported a sticky unread reply notification that couldn’t be cleared. Tannerabread reproduced it, found a fix in another PR, and confirmed the issue was resolved. read more

  • Kairo162 complained that Discourse was sending email app notifications instead of normal push notifications. NateDhaliwal explained email notification settings and suggested adjusting them to “only when away.” read more

  • Mr.Xurrent reported a missing admin sidebar on their forum. Moin helped debug with safe mode, found console errors linked to a known issue, and recommended further checks. read more

#Plugin

  • Don introduced a Custom Splash HTML Builder plugin that allows admin-defined HTML/CSS for splash screens, with better mobile performance than animated SVGs. The post includes before/after videos and detailed explanations. read more

#Data & reporting

  • Jay-C asked about DSA Content Moderation Reporting and statements of reasons, but declined to identify their employer. HAWK offered help and asked for specifics about gaps. read more

Activity by the Team Group

  • Lindsey participated in the admin dashboard AMA, confirming a traffic explorer is in development, and advised using Workflows for simple processes in the Workflows preview thread. admin dashboard · workflows

  • Renato announced the sticky pinned chat message bar and detailed its functionality. read more

  • Tannerabread fixed the sticky unread reply notification bug and also resolved the related “Can’t clear unread notification after being removed from a PM” issue. sticky notification · PM notification

  • Awesomerobot helped with banner topic guidance, explained the missing uploads rescue process, and discussed caching in the Allow clearing cache topic. banner · restore · caching

  • Gabriel fixed the AI bot chat channel issue and confirmed the behavior in a reply. read more

  • Zogstrip addressed the FA icon seeding problem and submitted a pull request to improve the icon picker. read more

  • Jordan.Vidrine announced the Post Type composer dropdown is moving to permanent and will be merged into core. read more

  • Sam engaged in the AI agent skills discussion, acknowledging the complexity and hinting at potential new concepts in Discourse AI. read more

  • Martin handled approvals for theme components and discussed permission groups, migration strategies, and setting validations. granular permissions · category permissions

  • NateDhaliwal provided support on multiple topics, including banner creation, email notifications, and muted category access, and also worked on a TL3 progress plugin. banner · email · muted categories · TL3 plugin

And yesterday’s cosmic eclipse may have been overshadowed by a meteor shower of pinned messages, but at least we got some sticky notifications out of it! :shooting_star:

919

Today on meta.discourse.org…

Key Stats

Over the last 24 hours, meta.discourse.org saw 106 new posts spread across 46 topics — a lively day of discussion, development, and community support. The most active contributors by likes and posts were:

User Likes Posts
Moin 20 16
Sam 14 2
NateDhaliwal 10 5
Don 9 7
Awesomerobot 8 1
WorldIsMine 8 1
HAWK 5 6
Rosiesherry 5 4
Rinion 4 4
Agemo 3 5

These numbers reflect the breadth of engagement—from feature requests and bug reports to plugin updates and lively enterprise discussions.

Interesting Topics

Below is a selection of the most compelling conversations from the past 24 hours, grouped by category. Each entry includes a brief recap and a direct link to the discussion.

#Feature

  • The delete user button in moderation queue is evil and needs a secondary prompt — WorldIsMine flagged a dangerous UX issue: admins can accidentally delete a legitimate user while trying to delete a post in the moderation queue. Moin linked to an earlier similar report, and Awesomerobot confirmed a fix is in progress via a PR that adds a confirmation step for irreversible actions. read more

  • Redirect the landing page for each subcategory to index file by default for documentation categories — Sren-1 shared a JavaScript workaround to automatically open a doc category with its index topic, while others discussed the need for a built-in option. The thread includes code samples and thoughts on improving navigation for documentation-heavy forums. read more

  • Add option of Start date to RSS Polling plugin — Heliosurge requested a start date option for RSS polling, to limit how much content is pulled from long-running feeds. Moin asked for the use case, and the discussion touched on filtering strategies. read more

#Announcements

  • Discourse AI subagents — Sam announced that subagent support has landed in Discourse AI, allowing users to delegate work to other agents, mix models, and increase concurrency. This is a major step forward for AI integration. read more

  • PostgreSQL 18 update for self-hosters — Moin and NateDhaliwal shared their experiences with the forced Postgres 18 upgrade, including a detailed workaround for those hitting errors. NateDhaliwal warned that a ChatGPT-generated fix may wipe the database, while Moin stressed the need for careful backup. read more

  • Solved improvements: Allowing members to indicate they’re experiencing a reported issue — Sterretje asked whether the “I have this problem too” button disappears when a reply is marked as a solution. Moin confirmed it does, and linked to an example. The thread discusses rollout and UX of the solved feature. read more

Support

  • AI bot keeps auto-adding me to a private chat channel even though disabled? — Rinion reported an annoying bug where the AI bot re-adds them to a private chat despite being disabled. Gabriel and Moin helped troubleshoot, ultimately manually removing the channel and deploying a fix. The thread also explains how updates work for hosted sites. read more

  • Discourse is sending me email app notifications instead of normal notifications — Kairo162 was puzzled by receiving only email notifications. NateDhaliwal explained the difference between email and push notifications and suggested checking preferences; further oddities were discussed. read more

#Plugin

  • Custom Wizard Plugin :mage: — Angus fixed several reported issues and merged PRs (including one for non-admin user creation). Satonotdead and Eviepayne shared persistent problems, and Angus suggested community contributions. The thread also discusses the plugin’s maintenance status. read more

  • Custom Splash HTML Builder — Don announced an update that adds a data-color-scheme attribute to #d-splash, allowing for light/dark splash logos with proper CSS handling. Agemo praised the feature as a long-awaited improvement. read more

  • ActivityPub Plugin — Tobiaseigen reported an issue where images from federated posts appear multiple times in Mastodon, suspecting a misconfiguration. The thread explores activitypub behavior and possible causes. read more

#Theme component

  • Guest Gate Theme Component — Don gave a comprehensive preview of Guest Gate 2.0, detailing a redesigned trigger system (page views, time, scroll, lightbox), new repeat behaviors, delayed display, and modernized implementation. The update promises backward compatibility and automatic migration of settings. read more

  • Quick Quote Theme Component — Merefield modernized the component and shared the PR, noting that its necessity may decrease with the built-in Nested View option. read more

enterprise

  • Public vs private discussion — Rosiesherry and HAWK engaged in a thoughtful debate about giving users granular control over content visibility, including AI crawlers and search indexing. Jagster raised real-world concerns about users wanting to block AI scraping while allowing search engines. read more

  • Ask me anything about the new admin dashboard — One1 shared insights about community managers’ roles and privileges, and HAWK asked clarifying questions about trust levels and permissions. The discussion also touches on potential improvements for admin controls. read more

  • Scalable engagement models — Rosiesherry described a successful program of unscripted 1:1 video conversations that brings new contributors into the fold. HAWK asked for examples, and Rosiesherry shared links to interview titles (content behind a paywall). read more

#Data & reporting

  • DSA Content Moderation Reporting + Statements of Reasons Requirements — HAWK announced that the team is spec’ing out work to add data fields for the machine-readable report and SOR database submissions, responding to Jay-C's earlier request. read more

Activity by the Team Group

The members of the Team group were quite active yesterday, contributing to a wide range of topics. Highlights include:

  • Sam announced Discourse AI subagents with a detailed post explaining the new feature and linking to the AI Agents documentation. He also followed up on Giving Discourse AI agent skills, discussing the possibility of introducing a top-level concept for “skills” in Discourse AI. AI subagents | AI skills

  • Awesomerobot confirmed he’s working on a fix for the dangerous delete-user button in the moderation queue, linking to the PR with a confirmation step. read more

  • Moin was everywhere: he helped in the AI bot thread (explaining deployment cycles and quoting GitHub), provided a workaround for PostgreSQL 18, clarified the Solved button behavior, and offered advice on Sending messages to all users (including a feature idea for a mass-email queue). He also reported the Changelog links inconsistency and investigated Granular group-based permissions issues. AI bot | PG18 | Solved improvements | Mass email | Changelog | Permissions

  • Martin responded to Moin's queries about theme setting migrations and discussed edge cases in the Granular group-based permissions thread, adding anonymous_users to disallowed groups. He also handled a question about the plugin’s behavior in Category permissions. Permissions | Category permissions

  • Gabriel was instrumental in resolving the AI bot issue, manually removing the problematic channel and triggering a deployment, after asking Rinion for screen recordings to isolate the bug. read more

  • Chapoi fixed the Safari PWA zooming bug (referencing PR #42303) and posted an announcement about moving AI title suggestions to the composer helper. Safari PWA | AI title suggestions

  • Zogstrip acknowledged a bug report about custom fields being cleared, linking to the PR that fixes it. read more

  • J.Jaffeux pointed Don to workflows as an alternative to a custom theme component for AI post analysis in chat. read more

  • Tobiaseigen reported an ActivityPub federation issue with images, asking for help diagnosing the cause. read more

  • Angus fixed multiple Custom Wizard issues and merged PRs, while also responding to community concerns about maintenance. He suggested users contribute PRs when they spot issues. read more

  • Merefield modernized the Quick Quote theme component and shared the PR, noting its reduced need due to core features. read more

  • HAWK and Rosiesherry engaged in deep conversations about public/private content control, scalable engagement, and the new admin dashboard. They also gave updates on DSA reporting. Public/private | Scalable engagement | Admin dashboard | DSA reporting

  • Rishabh (likely a team member) confirmed that a copy-link action for invitation links is being worked on. read more

That’s a wrap for today’s activity on meta.discourse.org. With everything from AI subagents to bulldozer-proof moderation safeguards, it seems the Discourse team and community are anything but idle. Here’s hoping tomorrow’s biggest challenge is choosing which shiny new feature to try first! :rocket:

920

Today on meta.discourse.org…

An active 24 hours with 78 posts across 41 topics, including 14 brand-new discussions. From big AI announcements to a sticker v2.0 facelift, Meta never sleeps.

Key Stats

Metric Count
Total new posts 78
Total active topics 41 (14 new)
Total likes received 108

Top contributing users (by likes received):

User Likes Posts
Sam 18 1
Moin 15 7
Awesomerobot 10 2
NateDhaliwal 7 3
Nickdb 6 2
Rishabh 5 1
Satonotdead 4 5
Zogstrip 4 3
Angus 4 2
Damian_Boon 4 2

Interesting Topics

#Announcements

  • Sam announced the landing of subagent support in Discourse AI, a feature that allows users to delegate work to specialized AI agents, mix and match language models, protect against context bloat, and increase concurrency. The announcement drew a remarkable 18 likes — easily the most-liked post of the day. read more

  • Chapoi shared that AI title suggestions have been moved into the composer helper menu, joining category and tag suggestions in the new inline AI composer flow. He invited feedback from communities that relied on the more prominent placement, stating this is not the end state. read more

#Community Building

  • OS_Corsair opened a wide-ranging discussion about whether Discourse — or more specifically this community — can “house and handle pluralistic diversity.” NateDhaliwal pointed to moderation tools and topic timers, Ondrej highlighted AI translations as a means of community inclusion, and Nickdb noted that Discourse is a framework you configure to suit your goals, adding that the question may be getting “the cart before the horse.” read more

ux

#Feature

  • Awesomerobot confirmed that a secondary confirmation prompt for deleting users from the moderation queue has been merged and will ship with upcoming Discourse updates — closing a long-running complaint that the delete button is “evil” and too easy to click by accident. read more

  • Polybos detailed a conflict with secure_uploads on S3-compatible backends that lack per-object ACL support: public avatars and assets break when the bucket is private, while secure post uploads work fine. They proposed either presigned URLs for public assets or support for separate buckets/prefixes as a cleaner boundary. read more

  • Heliosurge requested a start-date option for the RSS Polling plugin to control how much historical content gets pulled from long-running feeds like YouTube channels, arguing for parity with standard RSS readers. Moin asked for the use case, and Heliosurge clarified it’s about controlling ingestion volume. read more

#Plugin

  • In a very active thread for the Custom Wizard plugin, Angus released another set of fixes addressing issues reported by Eviepayne and Lebron, and — perhaps more importantly — pushed back gently on the idea that only a core maintainer should fix things, inviting users to submit PRs with a promise of quick reviews. Users confirmed the fixes work, though Eviepayne noted a theme-selection regression and broken “Users directed to wizard after signup” flow. read more

  • Don released Discourse Stickers v2.0, a significant modernization of the theme component: sticker configuration moves to Discourse’s native objects setting type, adds group filtering, category-specific stickers, per-channel chat controls, and automatic migration of the old JSON setting. Published stickers are also no longer lightbox-clickable, treating them more like genuine sticker content. read more

#Theme component

Support

  • In Cannot view post preview in mobile composer?, Moin reported that the rich text editor still fails on certain BBCode (e.g., [calendar]), and noticed that copying code blocks from Meta documentation into the Markdown editor results in unwanted backslash escaping that must be manually cleaned up. read more

  • Nacho_Caballero shared a detailed investigation into a ~40-second downtime window when running sv hup unicorn, attributing it to the pitchfork reload path which sends SIGTERM to the old master without a warm-up curl (and without a graceful QUIT). The proposed patch mirrors the unicorn path’s behavior — wait for the new master to actually serve before retiring the old one. read more

enterprise

  • In Ask me anything about the new admin dashboard, One1 and HAWK explored the role-based access gap between community managers and admins. One1's memorable analogy — “I trust you with my life, but not my wallet or my wife” — framed why community managers are kept at moderator trust levels, and Viddekla asked (in German) about faster stats refresh and exposing selected stats to the community. read more

Activity by the Team Group

From AI subagents politely learning to delegate to Discourse Stickers getting their v2.0 glow-up — and even the “evil” delete button earning a second thought — yesterday was a masterclass in turning oops into oh, nice!

921

Today on meta.discourse.org…

Here is a summary of the key activity and discussion that took place on Discourse Meta over the last 24 hours.

Key Stats

  • 37 new posts were published across 16 topics over the last day.
  • These posts received a total of 18 likes from the community.
  • Top contributors (by likes received):

Interesting Topics

Theme Component: Quick Profile Links Menu

Asa posted about the Quick Profile Links Menu — a theme component — noting that the border appears to be missing when used with the “Foundation” theme, with a screenshot illustrating the issue. Don, the component author, responded confirming the fix and announcing an updated version of the component.

Self-Hosting with Caddy in Front of Nginx

A new discussion was opened by @Ethsim2 describing their setup of running Caddy in front of Discourse’s own Nginx via Docker Compose, primarily to provide HTTP/3 at the edge without replacing Nginx entirely. A key part of this setup involved a persistent app.yml hook to make Nginx respect the X-Forwarded-For header from Caddy, so client IPs are recorded correctly. Pfaffman pointed to a related pull request on the Discourse Docker repo for comparison. Ethsim2 expanded on the configuration approach, including details about rotating Caddy access logs at 25 MB × 3 and explicitly disabling QUIC 0-RTT early data. Later, @Ethsim2 issued a correction, clarifying that disabling 0-RTT was not actually necessary — the Nginx-side header hook was what resolved the client IP issue, so they restored the default Caddy behaviour. Satonotdead suggested that HTTP/3 can also be achieved with vanilla Nginx by pointing to the official quic.nginx.org site.

Composer Redesign Testing Continues

The ongoing testing of the new composer brought more feedback. Sterretje noted a vertical space issue where the new composer takes up too much screen real estate when composing a new topic in Firefox on Windows 11. Nickdb reported that the mermaid plugin doesn’t render in the rich text editor, though a full page reload restored the older non-rich text editor which works; they attributed the edge case to a “beta-safarism” on macOS. Sk-Or-V1-Contents confirmed a couple of fixes — the minus button now works with one tap, but a URL bar jump remains an issue with the Sogou keyboard on Xiaomi, though not with Fcitx.

Workflow Modal Bug in Multiple Tabs

Per1234 raised a detailed bug report on the new Workflows plugin. The “Modal” step type appears persistently in every open browser tab when multiple tabs are open, and acting on those redundant copies produces a confusing “URL or resource could not be found” error. Slate confirmed the bug, agreeing that the misleading error message makes it feel like a failed action even though the step was already completed.

Feature Request: Removing Notifications from Feed

Twofoursixeight submitted a feature request proposing the ability to permanently remove old notifications — either a “clear all” button or an “X” to delete individual entries — so they no longer appear in the notification feed.

Deleting Ghost Bot with Admin Privileges

A Support thread in Chinese about how to delete a ghost bot user with admin privileges drew several replies. Kddkd pointed out that if the server itself is compromised, the bot is the least of one’s worries and advised securing SSH credentials. Sk-Or-V1-Contents asked when the bot was first noticed. NateDhaliwal questioned whether it’s the Discobot or AI plugin bot. The original poster AkarinLiu clarified it was the Discourse bot renamed. NateDhaliwal suggested checking the 2 setting. AkarinLiu noted the setting is on and shared an AI-generated guide for removing admin privileges via command line. Sk-Or-V1-Contents identified the user in question is actually 3, not discobot. Satonotdead warned about the risks of using the Rails console, linking to a guide on deleting users in Rails console and showing how to revoke admin privileges via u.revoke_admin! before deletion.

CSS Bug: Invisible Code Inside <small>

Sk-Or-V1-Contents commented on a reported bug where code is invisible when directly inside a <small> tag. They suspect it’s a theme-specific issue rather than a core bug, and suggested determining whether it’s a Discourse-maintained or custom theme before reporting it to the theme feedback area.

S3-Compatible Object Storage: Hetzner Suggestion

Thomas_Rother contributed to the self-hosting guide on S3-compatible object storage by recommending the EU-DSGVO compliant Hetzner object storage, which uses ISO/IEC 27001:2022-certified datacenters in Germany and Finland. They included an example configuration table and noted that the CDN warning will appear since Hetzner doesn’t offer a global CDN yet.

AWS SNS Topic ARN Allowlist

In the support discussion about configuring the AWS SNS topic ARN allowlist, Jonathan5 shared a link to another topic that helped. Deenius confirmed the solution works, noting the only pitfall was an incorrectly entered URL format.

Keyboard Jitter in “Languages I Understand” Field on Mobile

Testing continued on the jittery keyboard issue in the “languages I understand” input box on mobile. NateDhaliwal couldn’t reproduce the issue with Gboard or Samsung Keyboard, suggesting it might be device-keyboard dependent. Sk-Or-V1-Contents confirmed it’s still reproducible with the Sogou keyboard customized for Xiaomi, and added that Fcitx works fine, so unless someone else needs Sogou support, they won’t prioritise it.

WordPress Embed: Missing SEO Tags

Slate shared a practical shell command in the WordPress thread for detecting which existing topics published via WordPress embedded links lost their x-robots: noindex header, using curl against the sitemap. They emphasised that the header and canonical are independent signals that fail independently, and offered commands to check both.

phpBB Migration Speed

Mattash asked for updates on the tooling that could make phpBB-to-Discourse migrations faster.

Composer Model Override in Development

Jahan_Gagan opened a development question about migrating away from the deprecated api.modifyClass("model:composer", ...) pattern. They want to override Composer#save conditionally while still calling the original super.save(opts), and are wondering whether the new addModelMethod / addModelCallback APIs support this use case, or whether another extension point should be used instead.

Reply Button Not Visible on iOS PWA

In the bug report about the reply button not being visible when composing on iOS PWA, Blalor noted they’d created a separate topic on Safari PWA zooming, possibly duplicating this one. Nickdb reported that the issue recently reappeared on their hosted system and a fix was pushed, resolving it.

Safari PWA Zooming Bug Persists

Blalor updated a separate support thread on the Safari PWA zooming bug, stating the problem persists even after updating to the latest Discourse commit — they even uninstalled and reinstalled the PWA to purge cache, with no luck, and shared a recording of the issue in the original post.

Unicorn Reload Dropping Traffic

Nacho_Caballero started a support thread about ~40 seconds of downtime when running sv hup unicorn on their standalone container. They shared a detailed analysis produced with the help of Claude, which claims the issue is in the pitchfork code path of config/unicorn_launcher: it sends SIGTERM (immediate) rather than SIGQUIT (graceful) to the outgoing master, and retires it as soon as workers are spawned without waiting for the new master to actually serve requests. The report includes nginx error logs showing 499/502 responses during the window and a proposed diff to mirror the existing unicorn reload logic.

Activity by the Team Group

During the last 24 hours, there was no activity from members of the Team group in any of the forums. No posts, replies, or topic creations were recorded — the official Team members were apparently focused elsewhere, though several of the bug reports and feature requests above will likely catch their attention soon.

922

Today on meta.discourse.org…

Key Stats

The last 24 hours saw 109 new posts across 41 new topics, generating 80 likes from the community.

Top users by engagement:

User Posts Likes
NateDhaliwal 12 14
Moin 8 8
Martin 6 7
Twofoursixeight 4 7
Merefield 3 7
Chapoi 7 6
Satonotdead 5 2
Serkhelesheyi 3 2
Ethsim2 2 2
HAWK 2 2

Interesting Topics

#Announcements

  • Granular group-based permissions for anonymous and logged in users is advancing. Martin clarified that anonymous_users and logged_in_users groups are usable at any time and posted a plan of remaining work to eliminate the everyone group from site settings, acknowledging gaps when the upcoming change is disabled — including groups not being visible in the interface and theme setting issues raised by Moin (read more).

  • In the redesigned admin dashboard discussion, Skodde pointed out that Version and Backups info is only visible with the Docker Manager plugin active, calling the current dashboard unusable for many sysadmins. Chapoi confirmed that adding a selectable main block with the classic info is in the works (read more).

  • The PostgreSQL 18 update for self-hosters topic saw Chrisr explain that collation mismatch warnings during the dump-and-restore process are expected — they stem from the base image upgrading Debian Bookworm to Trixie and changing the glibc version — and that moving to C.UTF8 with the builtin provider will make future upgrades stable. Saiano shared an 80 GB database upgrade experience, and Jonathan5 confirmed a successful upgrade (read more).

  • AI title suggestions move to composer helper generated criticism from Jaroslav.Kovar, who noted that AI suggestions for categories and tags are now much less discoverable since users must manually click the combobox and select “AI Choose for me.” Chapoi acknowledged the feedback and made a note of it (read more).

#Plugin

  • NateDhaliwal published See TL3 Progress, a plugin that shows TL2 users a progress bar toward TL3 with optional detailed breakdowns of each requirement, next-closest stat, and warnings for TL3 users at risk of losing their level. Lilly helped catch a missing summary presentation bug, and Kairo162 asked about the plugin’s beta status (read more).

  • Asyntai AI Chatbot is a new theme component that adds an AI chat assistant to the corner of a forum, answering visitor questions from the site’s own content in 80+ languages. Moin questioned why the author tested against the 1-year-old Discourse 3.5 version (read more).

  • In Discourse Calendar and Events, Hellekin reported that the Peertube Live embed no longer displays the chat interface as it did last Summer, and the “Livestream button” is missing from the event interface.

  • AJ_Quick introduced Automatic Sitemap Linking, which imports an external sitemap, extracts page titles, and auto-links matching phrases in forum posts — similar to Watched Words but using sitemap-powered matching (read more).

development

  • Martin opened a new WIP companion topic, The road to stable, then permanent, for granular_anonymous_and_logged_in_groups_permissions, tracking high and low priority issues across core, plugins, and themes for truly removing the everyone pseudogroup from site settings — covering Discourse Templates, Discourse AI, Assign, Activity Pub, Suggested Edits, and Resenha (read more).

Support

  • A forum admin, AkarinLiu, reported a ghost bot user with admin privileges they can’t delete. Moin discovered that AI bot users lack the “Revoke admin” button visible for normal admins, and Satonotdead warned against removing the wrong AI bot via Rails console and linked the guide on deleting users with debotting concerns (read more).

  • In My Discourse forum deindexed from Google, Cnrtechspot.Com shared that their month-old forum is seeing “Crawled - but not indexed” across pages. Chapoi linked to Sam’s explanation that this is expected behavior for new forums without much content, and that Google will likely index it in time with enough content (read more).

  • Open pingable group that anyone can join or leave: Thatflyerguy asked if there’s a way to create an opt-in group for event pings. Heliosurge pointed out the freely joinable/leavable group options, and Moin noted the max_users_notified_per_group_mention limit and suggested watching a tag or category instead (read more).

bug

  • Footnote popup on mobile is partially off‑screen and does not scroll — Serkhelesheyi reported that long footnote popups are inaccessible on mobile because they don’t scroll or reposition. Moin noted a fix landed just last week, and Serkhelesheyi confirmed their instance was about three weeks out of date (read more).

  • code is invisible, solely when directly inside small was investigated by Roke_Julian_Lockhart, and Zogstrip confirmed the fix will land via discourse PR #42649 (read more).

General

  • Overgrow raised the alarm that browser_pageview_events grows unbounded by default — the table ballooned to 10M+ rows (~10 GB) in a month since core commit 39e21d063c9 — because persist_browser_pageview_events is true while clean_up_browser_pageview_events is false by default. Both settings are hidden, so sites unknowingly accumulate data with no cleanup (read more).

  • Does Discourse work on the lynx browser or SeaMonkey? — Twofoursixeight explained lynx is a text-only terminal browser with no JavaScript or CSS support, and SeaMonkey (Firefox 60 era) has been flagged as unsupported since 2023, pointing to the Dumbcourse plugin for old-browser compatibility. Merefield also linked a Termcourse plugin (read more).

#Sysadmins

  • The long-running Migrate a XenForo forum to Discourse topic saw Andrew_Bond share a heavily refactored XF 2.3 → Discourse import script supporting users, custom fields, PMs, Media Gallery, Resources, likes, and 750k posts with 20.7 GB of attachments in ~20 hours (read more).

#Feature

  • Twofoursixeight requested a “clear all” / remove notification ability in the feature request “Removing notifications,” but Chapoi noted the existing dismiss button already clears the feed, asking for clarification on what permanent removal would add (read more).

Activity by the Team Group

Given the day’s deep dive into group permissions, TL3 progress bars, and an unbounded pageview table, it’s safe to say the community didn’t just count rabbits — we counted every single one of our rows. :rabbit::bar_chart:

923

Today on meta.discourse.org…

Today on meta.discourse.org…

Today on meta.discourse.org…

You got a forum summary…

# Today on meta.discourse.org...

Today on meta.discourse.org…

The daily summary text is in this spirit…

Today on meta.discourse.org…

Today on meta.discourse.org…

**Key Stats

Today on meta.discourse.org

Key Stats

**Key Stats

Key Stats

**Key Stats **Key Stats

Key Stats

In the last 24 hours, meta.discourse.org saw 158 posts across 52 topics, with 177 likes given.

The most active and liked users were:

Interesting Topics

#Announcements

  • AI title suggestions have moved into the composer helper, and the community is weighing in on the trade-offs. Jaroslav.Kovar reported that users find the AI suggestions for categories and tags less discoverable after the move, while Chapoi acknowledged the added friction but explained the consolidation was needed for future features, noting that “the old version cost” too much noise for everyone who doesn’t want AI generation. read more

  • The redesigned admin dashboard continues to receive feedback from sysadmins. Skodde pointed out that the new dashboard lacks the classic Version and Backups information unless the Docker Manager plugin is installed, calling it “not usable for many sysadmins,” and Chapoi confirmed that “something along these lines is in the works.” read more

  • In the unified new topic list view discussion, Damian_Boon was confused about how /new changed, but Moin clarified that the change only combines /new and /unread, while /latest remains unaffected. read more

#Community Building

  • A fascinating thought experiment on whether money can be the only moderator of a forum generated a big discussion. Scoresby proposed a system where posting, replying, and upvoting all cost fees, with a community reward pool paid out to valuable users. Nickdb and Merefield were skeptical, pointing out the financial divide and the barrier to entry, while Ed_S mentioned Metafilter’s $5 sign-up fee as a successful model. Awesomerobot noted that bundling payments (like “gems” or Discord Nitro) is a more practical path than micro-payments. read more

#Plugin

  • NateDhaliwal released See TL3 Progress, a plugin that shows users their trust level 3 progress with optional detailed breakdowns, warnings, and locked status indicators. It’s a polished release with several screenshots, and Lilly caught a minor title summary typo which was quickly fixed. read more

  • J.Jaffeux added new building blocks to Discourse Workflows, including a data-explorer node that allows any kind of query to be used in workflows, with an example JSON attached. This responds to community requests for more flexible workflow automation. read more

  • AJ_Quick shared a new plugin for Automatic Sitemap Linking, which imports external sitemaps and auto-links page titles in forum posts, similar to watched words but with a catalog and safety gates for short words. read more

Support

  • Soumya_Ranjan_Mishra asked for help configuring Discourse AI with internal OpenAI-compatible APIs. Falco suggested selecting openai as the provider and configuring the URL, but the user hit an internal server error with a log trace in dialect.rb. Moin asked for more detailed logs, and Satonotdead noted the need to add internal IP domains to DISCOURSE_ALLOWED_INTERNAL_HOSTS. read more

  • A forum owner with a new forum asked for help after being deindexed from Google. Chapoi explained this is expected behavior for new forums and linked to Sam’s detailed post, noting that Google is a “black box” and indexing should come with more content. read more

  • Bootstrap mode being legacy continues to be a sore point. Sk-Or-V1-Contents suggested updating the old blog post and brought back the idea of an adjustable threshold for TL1 requirements, arguing that bootstrap mode was useful for forums with fewer than 30 posts. read more

#Self-hosting

  • A Nix package build failure for Discourse was reported by Fuguesoft. Ducks diagnosed the issue as a pnpm version mismatch in the Nix expression (10.34.4 vs the required 10.28.0) and suggested pinning the derivation to an older compatible pnpm. Fuguesoft plans to test the fix themselves. read more

  • Dennisjbr shared a parallel filesystem ops template to speed up Discourse rebuilds with millions of uploads by replacing recursive chmod/chown with parallel find/xargs pipelines. NateDhaliwal noted this is why S3 and CDNs exist, while Dennisjbr prefers JuiceFS for local mounting with S3 benefits. read more

  • Ed_S asked whether pitchfork is using too much memory on their modest forum, showing one worker with 2.2M requests and 500MB RSS plus 1.2GB swap usage. Falco called the RSS difference “normal,” but Ed_S notes recycling pitchforks freed 1.3GB and wants comparison stats from busier forums. read more

bug

  • A footnote popup issue on mobile was reported by Serkhelesheyi, where the popup is partially off-screen and doesn’t scroll. Moin pointed out there was a fix last week and Serkhelesheyi confirmed they simply hadn’t updated their instance in three weeks. read more

  • The reply button not visible when composing on iOS PWA bug persists for Appeltaartje even after a Communiteq update. RGJ noted a second fix that hasn’t been backported to stable and asked Chapoi about backporting, deferring to David for the final call. read more

#Feature

  • Tonja requested a way to hide 3rd-level categories on the categories homepage without losing the layout, as introducing a third nesting level switches the entire homepage to a long single-column list. The request is for a native setting or official option rather than CSS workarounds. read more

#Extras

  • Merefield migrated the > termcourse terminal client to Go, providing a single compiled executable, lower runtime overhead, and mouse control in the terminal. The migration includes a big cleanup of the interface and updated installation instructions. read more

events

  • Tomer1 asked when the next community retention webinar would be, and Danielle confirmed they’re working on a webinar with a guest speaker later this month, plus community office hours on September 9th. read more

development

  • Martin created a central topic tracking the road to stable and permanent for granular anonymous and logged-in groups permissions, listing high and low priority issues across core, plugins, and themes, including fixes for group pickers, guardian methods, and disallowed groups. read more

  • Ethsim2 reported a performance issue where SiteSerializer#category_types performs one DB query per SiteSetting in configuration schemas for staff users, showing 16 individual queries in a warm /latest load. They suggest batching the overridden-setting state and note the same path still exists on main. read more

#Sysadmins

  • Overgrow flagged a heads-up that the browser_pageview_events table grows unbounded by default because persist_browser_pageview_events is true while clean_up_browser_pageview_events is false, leading to 10M+ rows (~10 GB) in a month. Enabling the hidden setting via Rails console fixes it. read more

General

  • OS_Corsair asked whether Discourse works on Lynx or SeaMonkey browsers, and Merefield pointed out the AGPLv3 license in the repo, while OS_Corsair mentioned a friend wanting to create a federated forum from the software. read more

Activity by the Team Group

During the last 24 hours, Team members have been actively participating across forums:

  • Chapoi responded to feedback on AI title suggestions (discussed in #Announcements), noting the consolidation was needed for future features and that “it’ll get better later,” while acknowledging the added steps for tag/category AI. read more

  • Moin clarified the unified new topic list view change, explaining that /latest is unaffected and only /new combines topics and replies. read more

  • Moin also advised a user on the footnote popup bug, pointing them to a fix from last week, and followed up on the granular group permissions discussion, confirming issues with group visibility and aliasing. read more

  • Chapoi responded to feedback about the admin dashboard being missing classic Version/Backups info for sysadmins, stating that “something along these lines is in the works.” read more

  • Chapoi also provided SEO guidance on a forum being deindexed from Google, linking to Sam’s explanatory post and suggesting patience with content. read more

  • Chapoi and Moin both contributed to the reply button iOS PWA bug thread, discussing backporting with David. read more

  • Zogstrip confirmed fixes for the code invisible in small bug (PR #42649) and the workflow modal closed in every tab bug (PR #42651). read more

  • J.Jaffeux shared new Discourse Workflows building blocks, including a data-explorer node for queries, and offered help to users needing automation. read more

Well, with all that discussion about paying to post and pitchfork memory probes, yesterday’s meta conversation proved once again that even the wildest ideas deserve a good discourse! :top_hat:

924

Today on meta.discourse.org…

Key Stats

It was a busy 24 hours on Meta, with 43 new topics and 114 posts exchanged, earning a total of 125 likes :tada:

Top users by likes and posts:

User Posts Likes
Chapoi 9 12
Ed_S 9 11
Moin 8 10
Don 2 9
Mbauman 2 9
David 5 8
Merefield 4 8
Satonotdead 6 6
Hellekin 2 6
Andrew_Rowe 2 5

Interesting Topics

#Announcements

  • The unified new view for the topic list continued to polarise the community. Mbauman explained why the new view is confusing — it “intermingles an individual’s tracked state and global state” — and pointed to the reverted “new new” experiment from three years ago as evidence the approach was already tried and rejected.

  • Chapoi addressed feedback on the AI title suggestions move to composer helper, acknowledging the extra clicks for users but arguing the old star icon was “noisy” and costly to maintain, and teasing that the end goal is AI picking the best title “without any clicks at all.”

  • Lindsey introduced Zoom webinar livestreaming for the Events plugin, enabling members to join a Zoom webinar from the event topic, chat in real time, and even raise their hand — with post-event chat naturally flowing into forum topics.

#Community Building

#Feature

  • Digitalities presented a compelling case for allowing multiple OIDC sources simultaneously, explaining that their EU research forum needs both EU Login and EGI Check-in; Hellekin suggested using an Authentik federation proxy as a workaround in the meantime.

  • The Feedback for Ask Discourse thread had a humorous turn when Ed_S pasted the AI assistant producing pages of incoherent nonsense; Sam apologised, noting it was the result of an upgrade, and a follow-up confirmed the issue was resolved.

#Self-hosting

  • Ed_S raised concerns about Pitchfork using too much memory, sharing data showing 1.3GB freed after recycling pitchfork processes; David responded with production graphs explaining normal memory growth and revealed plans to enable reforking in the near future.

#Theme component

  • Topic Preview Modal gained a powerful new setting: Don's open_all_topic_links makes any topic link across the UI open in the preview modal, while Satonotdead asked about Horizon compatibility and Damian_Boon requested swipe-to-close on mobile.

ux

development

  • Don published a fascinating write-up on building a skeleton layout loader for Discourse, covering how administrators can select real UI elements to generate skeleton screens, why selector generation is harder than it looks, and the mantra that “the skeleton should not become a DOM-readiness gate.”

Support

bug

Activity by the Team Group

The Team group made significant contributions across the board over the last 24 hours:

From teaching Discobot about exotic shorthairs to watching AI assistants quote Orwell while pitchfork processes soak up RAM, it was a gloriously weird 24 hours on Meta — and we wouldn’t have it any other way. :tada:

925

Today on meta.discourse.org…

Key Stats

Over the last 24 hours, the community produced 93 new posts across 37 topics, with 147 likes on those posts, according to Meta Discourse latest activity.

Top User Posts Likes
Awesomerobot 5 17
Sam 3 16
Lindsey 3 13
Zogstrip 1 13
Moin 8 12
Ryan_Scott 4 9
Sk-Or-V1-Contents 6 5
Chapoi 4 5
David 1 5
Nickdb 4 4

Interesting Topics

#Announcements

  • Lindsey announced a new experimental likely crawlers category in the admin dashboard. It uses behavioral signals — automation user agents, datacenter ASNs, rapid navigation, session churn, and more — to separate bot pageviews from genuine human traffic, and is opt-in via Admin → Upcoming changes. Read more

  • Sam released detailed admin AI logs at /admin/plugins/discourse-ai/ai-logs, with new retention controls, streaming-response decoding, and rich filtering to help admins diagnose AI issues. Read more

  • Zogstrip introduced an experimental change that prioritizes your recently used tags in the empty tag picker, using tags from your 10 most recent topics instead of site-wide popular tags. Read more

  • The unified new view for the topic list continues to spark conversation. Awesomerobot acknowledged the extra-click complaint and shared a mock-up with split counts, while Mbauman pushed back on merging “new topics” and “new replies” into one list. Read more

Support

  • Ryan_Scott reported a calendar outage affecting all ~1,200 of his users after a Discourse update. It turned out the discourse post event enabled setting had been switched off during the core-bundling migration; Awesomerobot confirmed a fix was identified and applied to prevent it from happening for other sites. Read more

  • Sk-Or-V1-Contents hit flaky search behavior around stop words like it and we, plus exact-match quoting quirks. Awesomerobot explained why those words aren’t indexed and how fancy quotes can break phrase searches. Read more

  • In a random discussion about LLM setup, Sam confirmed that Gemini 3.7 Flash works via the interactions API and that Grok should work using the completion API.

  • A new self-hoster asked whether deployment requires email. The community clarified that SMTP is now optional thanks to Discourse ID login, and pointed to free mail providers like Mailgun and Brevo for transactional email. Read more

bug

#Community Building

#Feature

  • In Feedback for Ask Discourse, Ed_S reported occasional bad markup in AI answers and requested links open in a new tab by default. Falco noted the behavior should already respect the user’s “open external links in a new tab” preference, though Moin observed that preference is hidden from most users. Read more

ux

  • Markersocial highlighted confusing bulk delete confirmations: the “Permanently delete” message appears even when can_permanently_delete is false, and search results don’t visually distinguish topics from posts before choosing Delete Topics vs. Delete Posts. Read more

  • Moin reported that on tablets it’s now impossible to close a chat from the row menu; the only workaround is tapping the invisible close button on the timestamp. Renato asked for confirmation on mobile behavior and offered to follow up. Read more

Activity by the Team Group

From resurrecting calendars to teaching Discobot new links, it was a day of happy little fixes — may your tags be recent, your crawlers be flagged, and your “Post can’t be empty” errors finally be empty.

926

Today on meta.discourse.org…

A 24-hour wrap-up of the busiest conversations on the official Discourse Meta forum.

Key Stats

  • 154 posts were published across 39 active/new topics in the last 24 hours. Those posts collected 215 likes.
  • Top users by posts and likes received:
User Posts Likes received
Lindsey 2 21
Satonotdead 26 19
Sam 2 18
Nickdb 12 14
Moin 11 14
Happyhappy 5 13
HAWK 8 12
Mbauman 7 11
Chapoi 6 8
NateDhaliwal 6 8

Interesting Topics

#Announcements

  • Improved crawler detection is now optional for admins. Lindsey announced a new Likely Crawlers category in site traffic data, using behavioral heuristics such as datacenter ASNs, velocity, rapid navigation, session churn, and missing engagement to separate automation from real anonymous visitors. The feature is an experimental “upcoming change” and does not rate-limit or block requests; questions remain about whether likely-crawler pageviews will count toward plan limits. Read more

  • The August 2026 Current Projects update is out. Rishabh shared the newsletter, covering recently finished dashboard work, Events plugin/Zoom livestream improvements, AI image captions v2, and the work-in-progress Kanban plugin, Workflows, Discourse Helper Bot improvements, and composer redesign. Awesomerobot later clarified that Zoom livestream and Resenha/Livekit live-video paths are separate for now. Read more

  • Admins get detailed AI logs. Sam announced an admin-only AI logs page at /admin/plugins/discourse-ai/ai-logs, with retention controls, decoding of streaming responses, and rich filtering to help diagnose issues with Discourse AI. Commenters such as Nickdb are already using it to track automatic translation behavior. See also the Discourse AI guide. Read more

#Community Building

  • AI-written replies to farm trust levels are a growing headache. Divinebaboon asked how communities police users who use AI to auto-browse and auto-respond just to unlock trust-gated areas. Merefield noted AI-driven sock puppet conversations, Ed_S called for explicit LLM policies, Nickdb described using AI-detection agents with ~95% accuracy, and HAWK pushed back to focus on whether the content is valuable regardless of origin. Read more

  • The support-forum activity decline debate continued. In a long-running thread, Mbauman shared that the Julia programming community is losing new posters to AI, while Nickdb argued deeply technical topics still bring humans back and Mevo defended the value of human-guided AI-generated responses. HAWK later raised the paradox that blocking crawlers may prevent AI models from learning fresh human content. Read more

  • Members are showing off their Workflows. HAWK started a showcase thread and revealed Meta’s own weekly update reminder workflow, which serves progressively worse CSS to late check-ins. Zogstrip explained the LLM classifier and daily data explorer logic behind it, while Nickdb shared a simple automatic category-correcting workflow. Read more

#Translations

Support

  • Horizon’s new-topic button can float — with caveats. Satonotdead wanted to move the sidebar button to a fixed bottom-right position, and Chapoi reproduced a stacking-context oddity caused by position:sticky, suggesting a z-index:1 fix on .sidebar-wrapper. The result may overlap other elements, but the trick works, and the topic is tagged css and horizon-theme. Read more

  • Self-hosters don’t need email to deploy anymore. WuBarlynn asked whether a mail server is required, and Moin confirmed SMTP is now optional, thanks to Discourse ID login support introduced in the easier self-hosting installer. NateDhaliwal also noted free email tiers like Mailgun and Brevo for those who need transactional mail later. Read more

  • A hidden theme component caused an admin deprecation warning. Rbos investigated a console notice about deprecated htmlSafe imports and .hbs files. Moin found the source was the “Versatile Banner” theme component stored in the database; once updated, the warnings cleared. Read more

  • Nginx can crash-loop after restart due to Brotli loading. OxFilla documented a failure where the Discourse base image’s discourse.conf uses brotli_static, but the Debian nginx package never loads the Brotli module because /etc/nginx/nginx.conf lacks include /etc/nginx/modules-enabled/*.conf. A workaround is shared in the thread. Read more

ux

bug

  • iOS 16.7 photo uploads remain stubborn. Falco asked for a status check on the long-running upload bug. Sb56637 reports that raising upload limits and client_max_body_size usually helps, but the iPhone-only failure mode still lacks a clear explanation. Read more

#Plugin

  • Calendar/Events regressions are annoying mixed categories. Aurora reported two issues: recurring events can no longer be set to the fourth weekday of a month — only “last weekday” is offered — and categories with Events enabled now emphasize “New Event” over regular “New Topic,” hurting local-group categories that mix discussions and events. Read more

Activity by the Team Group

The Team group was especially visible in product announcements, feature explanations, and community troubleshooting.

And remember: if your screen suddenly starts wobbling, you might want to check whether your weekly update already floated away.

927

Today on meta.discourse.org…

Key Stats

Over the last 24 hours, the community has been busy:

  • 103 new posts and 40 new topics were created
  • 119 likes were given across those posts

Top Users by Likes & Posts

User Likes Received Posts
HAWK 18 6
Falco 13 4
Moin 10 14
NateDhaliwal 10 7
Don 8 3
Satonotdead 7 13
Darkpixlz 6 6
Nickdb 6 5
Awesomerobot 6 4
Zogstrip 6 2

Interesting Topics

#Community Building

#Announcements

  • Falco unveiled a complete refresh of chat notification sound packs, replacing the old options with five synthesized packs — from Soft marimba to Ethereal glass. Each pack distinguishes messages from mentions, and the sounds are generated in real time. One1 was happy to discover the preview option in preferences.

  • Newcomer Dowlass asked a series of questions about the Discourse Free plan beta in the now-official free plan. Awesomerobot clarified that the Starter plan has been removed, listed the default automatic groups, and explained “Discourse Hosted LLM”. Moin followed up with a primer on trust levels and default groups, and NateDhaliwal linked to the detailed explanation.

  • The crawler detection improvements announcement gained traction as Kris.Kotlarek confirmed that logged-in users are also scanned for automation signals, and Nickdb shared experience mapping obscure user agents to geos.

  • The composer redesign testing thread has been updated with a note from Awesomerobot that the redesign is behind an experimental setting, and Darkpixlz confirmed an earlier text input glitch is now fixed.

#Plugin

  • Resenha – Discord-style video and voice rooms received a major update from Falco: reworked AI noise suppression, direct calls from user cards, room invites, sound pack integration, live subtitles via a 2.5GB local AI model, and transcription backed by topic drafts. NateDhaliwal asked whether 1-to-1 calls could be restricted, and Falco confirmed they are disabled by default with group-based permissions.

#Theme Component

bug

  • Moin reported a Chat notification bug where replying to a message in a chat channel without threading enabled produces no unread indicator. The issue is reproducible and already linked to an older DM notification bug.

ux

#Feature

development

Support

  • Jagster was confused why AI-translated posts stopped appearing after switching interface languages. Moin pointed to the Content languages preference: if you list FI as a language you understand, Discourse will show the original Finnish instead of the English translation.

#Self-hosting

#Translations

  • The Basque language interface topic discussed using DeepL translations to bootstrap Crowdin. Moin shared his workflow for leveraging Crowdin’s automated suggestions while cautioning about consistency in terminology.

Activity by the Team Group

Whether it’s progressively ugly CSS, AI-powered noise suppression, or quests for trust levels, yesterday on Meta reminded us that the future of forums is equal parts automation and absurdity — and we wouldn’t have it any other way. See you in the next 24 hours! :robot: