每日总结（UTC下午1点）

新闻和活动 论坛摘要
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: