# 每日摘要（UTC晚上九点） **URL:** \ **Category:** Forum summaries\ **Created:** [2024年一月16日 21:56 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850 "2024-01-16T21:56:19Z")\ **Posts on this page:** 20\ **Page:** 35
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年七月29日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/938 "2026-07-29T21:01:39Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats Over the past **24 hours** , the community produced: - **270** new posts across **65** new topics, generating **479** likes. ### 🏆 Top Contributors | User | Likes Received | Posts Written | | --- | --- | --- | | @Damian_Boon | 34 | 19 | | @Moin | 30 | 9 | | @JammyDodger | 27 | 8 | | @Chapoi | 26 | 14 | | @Ed_S | 26 | 14 | | @Sam | 23 | 5 | | @Alltiagocom | 22 | 15 | | @Lilly | 22 | 12 | | @Andrew_Rowe | 22 | 6 | | @EricGT | 19 | 5 | * * * ## Interesting Topics ### #Community Building [Anyone else seeing a drastic drop in community activity for Support forums?](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401?silent=true) @Damian_Boon kicked off a deep, multi‑voice conversation about how AI and Google’s changing search landscape are reducing organic traffic to forums. @Canapin shared notes on AI reliability, @Ed_S contributed traffic‑source data, and @Tris20 offered a hopeful vision for a future golden age of human‑heavy communities. [read more](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401?silent=true) ### #enterprise [Access and engagement strategies](https://meta.discourse.org/t/access-and-engagement-strategies/408558?silent=true) @HAWK explored why internal teams feel unqualified to engage on Meta. @Canapin reflected on the “hidden costs” of staff participation, @Andrew_Rowe suggested pragmatic reply strategies, and @Mae stepped in to clarify that marketing roles have a place – just not for deep technical questions. [read more](https://meta.discourse.org/t/access-and-engagement-strategies/408558?silent=true) ### #Announcements [July 2026 monthly release](https://meta.discourse.org/t/july-2026-monthly-release/408729?silent=true) @Loic announced v2026.7.0 and its ESR status. The release sparked immediate discussion about ESR labeling, pinning, and the desire for a “grace period” before automatic rollover. @Ed_S shared a helpful write‑up of what to expect when moving from 2026.1. [read more](https://meta.discourse.org/t/july-2026-monthly-release/408729?silent=true) [Composer preview toggle now lives with the other window controls](https://meta.discourse.org/t/composer-preview-toggle-now-lives-with-the-other-window-controls/408690?silent=true) @Chapoi announced the reorganisation of composer top‑right controls – the preview toggle joins the minimise and fullscreen buttons, and the minimise icon switches to a standard dash. [read more](https://meta.discourse.org/t/composer-preview-toggle-now-lives-with-the-other-window-controls/408690?silent=true) [New default for pending user approval reminders](https://meta.discourse.org/t/new-default-for-pending-user-approval-reminders/408429?silent=true) @Zogstrip introduced an upcoming change that lowers the default reminder delay for approving new members from 8 hours to 30 minutes – only applicable to sites that require staff approval. [read more](https://meta.discourse.org/t/new-default-for-pending-user-approval-reminders/408429?silent=true) [Introducing a docked composer for AI bot conversations](https://meta.discourse.org/t/introducing-a-docked-composer-for-ai-bot-conversations/403327?silent=true) @Keegan merged an update that moves the send‑shortcut setting to core, making it available for AI bot conversations. The docked composer now respects user preferences for send behaviour. [read more](https://meta.discourse.org/t/introducing-a-docked-composer-for-ai-bot-conversations/403327?silent=true) ### #Support [How far can we push Discourse in customization?](https://meta.discourse.org/t/how-far-can-we-push-discourse-in-customization/408829?silent=true) @Alltiagocom asked about the limits of customisation without breaking on upgrades. @Awesomerobot gave practical guidance on using CSS variables vs. bare selectors, @Merefield noted that staging servers are essential for heavy customisation, and @Andrew_Rowe encouraged starting small with themes and components. [read more](https://meta.discourse.org/t/how-far-can-we-push-discourse-in-customization/408829?silent=true) [Jumping from 2026.1 ESR to 2026.7 – What I found](https://meta.discourse.org/t/jumping-from-2026-1-esr-to-2026-7-what-i-found/408779?silent=true) @Haydenjames published a thorough, researched guide covering security advisories, the `version: stable` pitfall, and a checklist of behaviour changes – including a note that YouTube embedding still breaks due to the `Referrer-Policy` header. [read more](https://meta.discourse.org/t/jumping-from-2026-1-esr-to-2026-7-what-i-found/408779?silent=true) [Cannot view post preview in mobile composer?](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352?silent=true) @Seanblue and others lamented the loss of the preview button. @Awesomerobot demonstrated minor WYSIWYG‑to‑markdown formatting shifts, and @Moin promptly released a theme component to restore the feature. [read more](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352?silent=true) ### #ux [Site in staff only mode – no need to show signup or login](https://meta.discourse.org/t/site-in-staff-only-mode-no-need-to-show-signup-or-login/408703?silent=true) @EricGT reported that the OpenAI forum, in staff‑only mode, still displays sign‑up and login prompts – frustrating for read‑only visitors. @Zogstrip fixed the issue within 12 hours via [PR #42101](https://github.com/discourse/discourse/pull/42101), now live on the OpenAI site. [read more](https://meta.discourse.org/t/site-in-staff-only-mode-no-need-to-show-signup-or-login/408703?silent=true) ### #development [Now in Beta: Plugin to see TL3 Progress for TL2 users](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543?silent=true) @NateDhaliwal continued refining the plugin – addressing progress‑bar alignment, adding a `modal_bottom_text` setting for site‑specific TL3 benefits, and working on a “closest stat” indicator. [read more](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543?silent=true) [Any way to change at what width the small logo appears?](https://meta.discourse.org/t/any-way-to-change-at-what-width-the-small-logo-appears/408767?silent=true) @Sb56637 struggled with the full‑width component forcing the primary logo in scrolled‑down topic view. @Awesomerobot solved it by adding a “use default logo behavior” setting to the Full Width component. [read more](https://meta.discourse.org/t/any-way-to-change-at-what-width-the-small-logo-appears/408767?silent=true) ### #Extras [Improving accuracy of AI reporting through validation](https://meta.discourse.org/t/improving-accuracy-of-ai-reporting-through-validation/408794?silent=true) @Sam introduced a new “Fact Checker” agent in Discourse Workflows that reviews draft AI reports for mistakes before posting, dramatically improving quality without requiring a model upgrade. [read more](https://meta.discourse.org/t/improving-accuracy-of-ai-reporting-through-validation/408794?silent=true) [Giving Discourse AI agent skills](https://meta.discourse.org/t/giving-discourse-ai-agent-skills/408666?silent=true) @Sam detailed how to approximate an agent‑skills system using custom tools that read from a dedicated category – each skill a topic with frontmatter, discoverable by the agent. [read more](https://meta.discourse.org/t/giving-discourse-ai-agent-skills/408666?silent=true) ### #bug [Issue with iOS 16.7 photo upload?](https://meta.discourse.org/t/issue-with-ios-16-7-photo-upload/408404?silent=true) @David and @Falco investigated upload failures on older iOS devices. @Falco’s fix was included in v2026.7.0, but some users report it didn’t resolve the issue – possibly linked to tight upload image size limits. [read more](https://meta.discourse.org/t/issue-with-ios-16-7-photo-upload/408404?silent=true) [Permanently Delete does not show (even after 5 minutes)](https://meta.discourse.org/t/permanently-delete-does-not-show-even-after-5-minutes/408754?silent=true) @Tkforbes discovered that the “Permanently Delete” option is missing from the topic‑level wrench menu, and the bulk‑delete modal misleadingly claims deletion is permanent when it is not for moderators. @Lilly guided troubleshooting. [read more](https://meta.discourse.org/t/permanently-delete-does-not-show-even-after-5-minutes/408754?silent=true) ### #Self‑hosting [Updated to esr, but “578 new changes are available”](https://meta.discourse.org/t/updated-to-esr-but-578-new-changes-are-available/408738?silent=true) @Ed_S noted a confusing dashboard message after upgrading to the new ESR. @David fixed a server‑side version‑check bug; the false alert will clear after a forced version check. [read more](https://meta.discourse.org/t/updated-to-esr-but-578-new-changes-are-available/408738?silent=true) * * * ## Activity by the @Team Group - @Sam kicked off two important AI‑focused discussions: one on [validating AI reports with a Fact Checker agent](https://meta.discourse.org/t/improving-accuracy-of-ai-reporting-through-validation/408794?silent=true) and another on [giving agents“skills” via custom tools](https://meta.discourse.org/t/giving-discourse-ai-agent-skills/408666?silent=true). - @Chapoi was active across several threads: explaining why [some staff feel unqualified to engage](https://meta.discourse.org/t/access-and-engagement-strategies/408558?silent=true) on Meta, addressing the [missing mobile preview](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352?silent=true), responding to a [Vietnamese translator request](https://meta.discourse.org/t/request-to-be-a-reviewer-for-vietnamese-language/408681?silent=true), and pointing out a [icon mix‑up in the review queue](https://meta.discourse.org/t/why-an-upload-icon-for-copying-a-link/408680?silent=true). He also [announced the composer control reorganisation](https://meta.discourse.org/t/composer-preview-toggle-now-lives-with-the-other-window-controls/408690?silent=true). - @Awesomerobot helped users with [logo‑width customisation](https://meta.discourse.org/t/any-way-to-change-at-what-width-the-small-logo-appears/408767?silent=true) by adding a setting to the Full Width component, investigated an [empty banner box](https://meta.discourse.org/t/empty-banner-box/408667?silent=true), and provided [examples of WYSIWYG formatting quirks](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352?silent=true) in the mobile composer discussion. - @David confirmed the [July ESR release](https://meta.discourse.org/t/july-2026-monthly-release/408729?silent=true) and explained pinning, resolved the [“578 new changes” false alert](https://meta.discourse.org/t/updated-to-esr-but-578-new-changes-are-available/408738?silent=true), and assisted with [iOS upload failures](https://meta.discourse.org/t/issue-with-ios-16-7-photo-upload/408404?silent=true) – noting that the fix might not cover all cases. - @Zogstrip [fixed the staff‑only mode sign‑up prompts](https://meta.discourse.org/t/site-in-staff-only-mode-no-need-to-show-signup-or-login/408703?silent=true) (live within 12 hours), introduced the [pending‑user reminder default change](https://meta.discourse.org/t/new-default-for-pending-user-approval-reminders/408429?silent=true), and landed fixes for [Outlook reply‑by‑email](https://meta.discourse.org/t/reply-by-email-from-outlook-drops-everything-after-a-numbered-list/408194?silent=true) and [IMDB oneboxes](https://meta.discourse.org/t/fetch-response-rejects-http-202-breaking-imdb-oneboxes/407725?silent=true). - @Falco addressed [ESR update questions](https://meta.discourse.org/t/july-2026-monthly-release/408729?silent=true) and [continued investigating iOS upload issues](https://meta.discourse.org/t/issue-with-ios-16-7-photo-upload/408404?silent=true), and clarified that the [AI structured‑output warning](https://meta.discourse.org/t/discourse-ai-structured-output-response-was-not-valid-json/408821?silent=true) is not an error. - @Nat traced the [empty banner box](https://meta.discourse.org/t/empty-banner-box/408667?silent=true) to stale translation overrides from a December script and removed them, and [merged a date‑picker](https://meta.discourse.org/t/request-for-a-date-picker-in-ai-translate-settings/405828?silent=true) for AI Translate settings. - @Keegan updated the [docked AI composer](https://meta.discourse.org/t/introducing-a-docked-composer-for-ai-bot-conversations/403327?silent=true) to respect the user’s send‑shortcut preference. - @Mcwumbly chimed in on the [ESR pinning discussion](https://meta.discourse.org/t/july-2026-monthly-release/408729?silent=true), provided feedback on [AI reporting workflows](https://meta.discourse.org/t/improving-accuracy-of-ai-reporting-through-validation/408794?silent=true), and confirmed that the [Chat API](https://meta.discourse.org/t/discourse-chat/230881?silent=true) is fully accessible though not yet documented. - @Mae shared her perspective on [why marketing staff are not the right people for technical questions](https://meta.discourse.org/t/access-and-engagement-strategies/408558?silent=true), while also committing to produce less‑technical content on Meta in the future. * * * That’s all for today – between AI agents gaining skills and forums feeling the heat from Google’s overviews, yesterday’s conversations proved that **even a quiet forum can still spark a blazing debate** 🔥. ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年七月30日 21:00 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/939 "2026-07-30T21:00:35Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, the community generated **250 posts** across **66 topics** , with **345 likes** distributed across the discussions. The most active and liked users were: | User | Likes | Posts | | --- | --- | --- | | @Moin | 38 | 17 | | @Alltiagocom | 25 | 15 | | @Merefield | 19 | 13 | | @Awesomerobot | 18 | 10 | | @Damian_Boon | 17 | 17 | | @Ed_S | 16 | 11 | | @Nickdb | 14 | 6 | | @Sam | 14 | 3 | | @JammyDodger | 12 | 3 | | @David | 11 | 8 | ## Interesting Topics ### #Community Building - A deep and passionate debate unfolded in **“Anyone else seeing a drastic drop in community activity for Support forums?”** – @Ed_S challenged the “AI is inevitable” stance, leading to a reflective discussion on how forums must offer more than Q&A to survive. @Damian_Boon, @Nickdb, and @Alltiagocom weighed in on the value of human connection vs. AI convenience. [Read more](https://meta.discourse.org/t/-/405401/61?silent=true) - **“Forums that forbid AI content… How’s it going?”** – @Nickdb shared a detailed AI-detection prompt used to flag AI-generated posts, and @Merefield agreed that overly structured AI slop kills engagement. @Takiro added perspective from an art community that bans AI content. [Read more](https://meta.discourse.org/t/-/405659/26?silent=true) ### #Theme component - **“Mobile Composer Preview”** – @Moin released a theme component restoring the mobile preview button, which was removed from core. Users @Lilly, @Jagster, and others celebrated its return. @Sk-Or-V1-Contents reported a minor display bug that was resolved. [Read more](https://meta.discourse.org/t/-/408784/1?silent=true) - **“Topic List Previews (TLP)”** – @Ed_S reported an error on ESR 2026.7, which @Merefield quickly patched. The fix addressed a `TypeError` in preview-edits.gjs. Later, @Merefield previewed a “Horizon-lite” fork that works with TLP and Bars. [Read more](https://meta.discourse.org/t/-/209973/750?silent=true) - **“Colored Tag Styles”** – @Manuel refactored this component to allow fully customisable color styles via theme settings instead of eight fixed colours. [Read more](https://meta.discourse.org/t/-/214871/19?silent=true) - **“Closed Sidebar by Default”** – @Don contributed a smarter JavaScript snippet that initialises the sidebar closed but then remembers user preference, and @Nathank rolled it into the component. [Read more](https://meta.discourse.org/t/-/408578/8?silent=true) ### #Support - **“How far can we push Discourse in customization?”** – @Alltiagocom asked about limits. @Awesomerobot advised using CSS variables for stability; @Merefield noted that customisation always requires maintenance. @Andrew_Rowe suggested hiring a professional developer. [Read more](https://meta.discourse.org/t/-/408829/1?silent=true) - **“Jumping from 2026.1 ESR to 2026.7 – What I found”** – @Haydenjames documented 17 security fixes and a YouTube embed workaround. @Mcwumbly emphasised that patch-first is still valid for two months. @Merefield recommended a staging server. [Read more](https://meta.discourse.org/t/-/408779/1?silent=true) - **“Failed to optimize image” error from discourse-topic-previews-sidecar** – @Takiro encountered an avatar upload failure. @David identified the backtrace pointing to an archived plugin and advised removing it. [Read more](https://meta.discourse.org/t/-/408911/5?silent=true) - **“Issue with iOS 16.7 photo upload?”** – @Sb56637, @Sok777, and @Falco investigated uploads stuck at 0% on iOS. The fix for iOS 16.7 was landed, but users on iOS 26 also faced issues, possibly due to server-side settings. [Read more](https://meta.discourse.org/t/-/408404/12?silent=true) ### #development - **“Any way to change at what width the small logo appears?”** – @Sb56637 asked about the full-width component overriding logo behaviour. @Awesomerobot added a new setting (“use default logo behaviour”) to the component, and @Sb56637 confirmed it works on ESR. [Read more](https://meta.discourse.org/t/-/408767/5?silent=true) - **“Facebook-style Topic Modal – Is it better?”** – @Damian_Boon shared a demo of a modal-based topic view, getting feedback on load speed and mobile behaviour. He continued iterating on the concept. [Read more](https://meta.discourse.org/t/-/408565/14?silent=true) ### #Announcements - **“July 2026 monthly release”** – Discussion around ESR rollover: @Ed_S wanted to stay on the previous ESR longer, @Mcwumbly questioned the difference, @Elmuerte suggested a “grace period” label, and @Moin clarified that ESR only gets security fixes. [Read more](https://meta.discourse.org/t/-/408729/9?silent=true) - **“Introducing the unified new view for the topic list”** – @Overgrow reported that suggested topics no longer prioritise unread tracked topics. @Martin acknowledged it was unintentional and plans a fix. @Seanblue flagged count sync issues. [Read more](https://meta.discourse.org/t/-/404728/27?silent=true) ### #Extras - **“Improving accuracy of AI reporting through validation”** – @Sam detailed a new Workflows-based pipeline that chains a report runner with a fact-checker agent, using Dreamlike and Luna models. The post includes technical screenshots and JavaScript code. [Read more](https://meta.discourse.org/t/-/408794/1?silent=true) ### #ux - **“Image makes post events Onebox too big / dominant”** – @Nathank noted that event images in Oneboxes can overpower a post and shared a CSS workaround. The suggestion was to omit images from Oneboxes or provide a mini version. [Read more](https://meta.discourse.org/t/-/408878/1?silent=true) ### #bug - **“Chat search results cannot be scrolled on mobile”** – @Tonja reported a missing scroll gesture on mobile chat search. @Awesomerobot added a fix in [PR #42188](https://github.com/discourse/discourse/pull/42188). [Read more](https://meta.discourse.org/t/-/408922/1?silent=true) ### #Event - **“Bringing Community Conversations Into Your Website – Office Hours Replay”** – @Danielle posted the replay of a session covering the new full-page embedded discussion experience, with key takeaways on setup and SSO. [Read more](https://meta.discourse.org/t/-/408914/1?silent=true) ## Activity by the @Team Group - **@Sam** authored the **“Improving accuracy of AI reporting through validation”** topic, describing the new Workflows pipeline. He also helped @Dennisjbr with a Gemini model issue in the Workflows thread. [Read more](https://meta.discourse.org/t/-/408794/1?silent=true) and [Workflows thread](https://meta.discourse.org/t/-/407100/6?silent=true) - **@David** resolved the “failed to optimize image” error by identifying the deprecated plugin and advised on avatar upload issues. [Read more](https://meta.discourse.org/t/-/408911/4?silent=true). He also explained the “578 changes” version-check bug in [v2026.7.0 ESR misreport](https://meta.discourse.org/t/-/408738/3?silent=true) and helped debug iOS photo uploads. [Read more](https://meta.discourse.org/t/-/408404/13?silent=true) - **@Awesomerobot** added a setting to the full-width component to restore default logo behaviour. [Read more](https://meta.discourse.org/t/-/408767/6?silent=true). He also clarified a WYSIWYG markdown rounding issue in the mobile preview topic, [read more](https://meta.discourse.org/t/-/408352/15?silent=true), and fixed the mobile chat search scroll bug. [Read more](https://meta.discourse.org/t/-/408922/2?silent=true). He also responded to the ActivityPub domain change topic. [Read more](https://meta.discourse.org/t/-/408845/2?silent=true) - **@Falco** helped diagnose iOS upload issues and identified the root cause in a security fix. [Read more](https://meta.discourse.org/t/-/408404/21?silent=true). He also addressed the Turkish translation problem, promising a prompt fix. [Read more](https://meta.discourse.org/t/-/408915/4?silent=true). He merged a PR for Resenha voice rooms. [Read more](https://meta.discourse.org/t/-/389056/72?silent=true) - **@Zogstrip** confirmed adding an input option for Boolean fields in Call Workflow steps. [Read more](https://meta.discourse.org/t/-/408827/4?silent=true). He also fixed a duplicate poll title in email notifications. [Read more](https://meta.discourse.org/t/-/408875/3?silent=true) - **@Chapoi** linked to the mobile preview component in the “Cannot view post preview in mobile composer” topic. [Read more](https://meta.discourse.org/t/-/408352/13?silent=true). He also asked for more info in a non-streaming request thread. [Read more](https://meta.discourse.org/t/-/408506/4?silent=true) - **@Mcwumbly** discussed ESR rollover and suggested a grace period label. [Read more](https://meta.discourse.org/t/-/408729/9?silent=true). He clarified that patch-first remains a legitimate option for ESR. [Read more](https://meta.discourse.org/t/-/408779/4?silent=true). He also responded in the Chat API topic. [Read more](https://meta.discourse.org/t/-/230881/211?silent=true) - **@Merefield** fixed the Topic List Previews error. [Read more](https://meta.discourse.org/t/-/209973/755?silent=true). He encouraged using staging servers for upgrades. [Read more](https://meta.discourse.org/t/-/408779/5?silent=true). He also participated in the customization limits discussion. [Read more](https://meta.discourse.org/t/-/408829/15?silent=true) - **@Nat** removed empty manual overrides that caused an empty banner box. [Read more](https://meta.discourse.org/t/-/408667/4?silent=true). She also pushed a PR for multi-language preferences. [Read more](https://meta.discourse.org/t/-/381116/22?silent=true) - **@Danielle** published the Office Hours replay on embedded discussions. [Read more](https://meta.discourse.org/t/-/408914/1?silent=true) - **@Lindsey** reminded users that the “me too” button in Solved is a category-specific setting. [Read more](https://meta.discourse.org/t/-/402498/55?silent=true) - **@Angus** pushed fixes and updates to the Custom Wizard plugin. [Read more](https://meta.discourse.org/t/-/73345/966?silent=true) - **@Martin** acknowledged the unread priority regression in suggested topics and plans a fix. [Read more](https://meta.discourse.org/t/-/404728/29?silent=true) - **@Don** contributed JavaScript to improve the “Closed Sidebar by Default” component. [Read more](https://meta.discourse.org/t/-/408578/8?silent=true) * * * _Between AI translation quandaries and the eternal question of community vs. LLM, yesterday proved that the human keyboard is still mightier than the chatbot — even if it takes two taps longer to preview a post._ ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年七月31日 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/940 "2026-07-31T21:02:05Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… Welcome to your daily digest of the vibrant activity happening in the Discourse community over the last 24 hours. From deep dives into AI moderation to new plugin updates, there’s plenty to catch up on. Let’s dive into the numbers and conversations that shaped the day. * * * ## Key Stats - **Total new posts:** 172 - **Total new topics:** 56 - **Total likes given:** 212 **Top contributors** (by posts and likes received): | User | Posts | Likes | | --- | --- | --- | | @Zogstrip | 7 | 20 | | @Moin | 19 | 17 | | @Falco | 6 | 17 | | @Merefield | 6 | 14 | | @Nathank | 8 | 11 | | @Takiro | 5 | 11 | | @Alltiagocom | 5 | 9 | | @Nickdb | 5 | 9 | | @HAWK | 1 | 8 | | @Awesomerobot | 3 | 7 | * * * ## Interesting Topics ### #Community Building - **Forums that forbid AI content… How’s it going?** @Nickdb shared how their forum uses a custom AI agent to flag AI-generated posts from new members, with a detailed prompt example that checks for “overly polished” language. @Merefield agreed, noting that AI-style posts feel like “walking through treacle”, while @Takiro explained their art community’s strict AI ban and how they moderate reports without witch hunts. The conversation also touched on the overuse of em dashes as a “telltale” sign — with @HAWK joking that he refuses to lower his own standards just to appear human. [Read more](https://meta.discourse.org/t/forums-that-forbid-ai-content-hows-it-going/405659?silent=true) - **Anyone else seeing a drastic drop in community activity for Support forums?** A lively discussion evolved into a philosophical debate about AI’s role in communities. @Alltiagocom argued that LLMs will “unclog your toilet” by telling you how, while @Nickdb countered that they provide “generic, lowest common-denominator advice”. @Tris20 shared his fatigue with AI-generated content, longing for “messy human text”. [Read more](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401?silent=true) ### #Plugin - **Resenha - Add Discord-style Voice Rooms to Your Community** @Falco merged fixes for reported UI issues (private room icon size and participant list accessibility) and announced several new capabilities: coturn auth for STUN/TURN, LiveKit session recording, flagging of call participants, right-click menus on video tiles, and opt-in higher bitrate streaming. @Nathank provided detailed feedback that led to those fixes. [Read more](https://meta.discourse.org/t/resenha-add-discord-style-voice-rooms-to-your-community/389056?silent=true) ### #Feature - **Allow use of input for value of manually mapped Call workflow Boolean type fields** A feature request by @Per1234 was quickly picked up by @Zogstrip, who implemented it via a PR. @Renato independently created another PR, and the team coordinated to merge both. The thread shows how responsive core development can be when the community provides clear use cases. [Read more](https://meta.discourse.org/t/allow-use-of-input-for-value-of-manually-mapped-call-workflow-boolean-type-fields/408827?silent=true) ### #Support - **Failed to optimize image error from discourse-topic-previews-sidecar** @Takiro reported avatar upload failures and traced them to a type mismatch in the deprecated topic-previews-sidecar plugin. @David identified the archived plugin and recommended removal. After disabling it, @Takiro confirmed everything worked again. A perfect example of community support solving a real-world issue. [Read more](https://meta.discourse.org/t/failed-to-optimize-image-error-from-discourse-topic-previews-sidecar/408911?silent=true) - **Maintenance page workaround - can this be done?** @Alltiagocom proposed a Cloudflare Worker + KV solution (from Claude) to show a maintenance page without touching nginx. @Canapin questioned the need, while @Merefield suggested moving to a two-container setup so rebuilds take seconds. The thread offers practical alternatives for downtime management. [Read more](https://meta.discourse.org/t/maintenance-page-workaround-can-this-be-done/408967?silent=true) - **Mostrar “Proximos Eventos” en todas las Categorias** A Spanish-language question about showing upcoming events in all categories. @Moin provided a concise solution using a value transformer (`discourse-calendar-upcoming-events-show-cross-category`) inside a theme component. The original poster confirmed it worked, and @Nathank later suggested making it a built-in parameter. [Read more](https://meta.discourse.org/t/mostrar-proximos-eventos-en-todas-las-categorias/408904?silent=true) ### #Announcements - **Introducing the unified new view for the topic list** @Martin fixed an issue where suggested topics lost priority in unread results, and @Seanblue reported persistent unread count sync problems. @Chapoi explained that hiding the “new/unread” line in Horizon was intentional for decluttering, but @Martin will adjust the logic to keep unread priority. [Read more](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728?silent=true) - **Solved improvements: Allowing members to indicate they’re experiencing a reported issue** The community gave feedback on the “me too” button. @Lillian and @RGJ expressed concerns that it might discourage detailed replies, but @Lindsey reminded everyone that it’s now a category-specific setting that can be turned off. The discussion highlights the need for flexible moderation tools. [Read more](https://meta.discourse.org/t/solved-improvements-allowing-members-to-indicate-theyre-experiencing-a-reported-issue/402498?silent=true) ### #Theme component - **Mobile Composer Preview** @Moin restored a preview button for the mobile composer and helped @Sk-Or-V1-Contents debug a missing button in theme creator. The thread also covers the difference between RTE and Markdown modes, with @Jagster noting that even RTE users have switched to preview mode because it suppresses the keyboard. [Read more](https://meta.discourse.org/t/mobile-composer-preview/408784?silent=true) ### #events - **Bringing Community Conversations Into Your Website - Office Hours Replay** @Danielle shared the replay of the office hours session on the new full-page embedded discussion experience. Key takeaways include automatic companion topic creation, routing to specific categories, and styling options. This is a major step for integrating Discourse into any website. [Read more](https://meta.discourse.org/t/bringing-community-conversations-into-your-website-office-hours-replay/408914?silent=true) ### #bug - **Chat search results cannot be scrolled on mobile (touch swipe unresponsive)** @Tonja’s thorough bug report was acknowledged by @Awesomerobot, who added a fix in PR #42188. The issue prevented scrolling in chat search results on both iOS and Android, making it impossible to see all results. The quick fix will be included in the next release. [Read more](https://meta.discourse.org/t/chat-search-results-cannot-be-scrolled-on-mobile-touch-swipe-unresponsive/408922?silent=true) - **Opening forum goes to topics 1 day ago or older, not recent topics** @Zogstrip traced the problem to `bfcache-compatible` headers and prepared a fix in PR #42207. Users like @NateDhaliwal expressed relief after months of the issue. This shows how persistent users and core devs work together to squash tricky bugs. [Read more](https://meta.discourse.org/t/opening-forum-goes-to-topics-1-day-ago-or-older-not-recent-topics/400459?silent=true) ### #enterprise - **Access and engagement strategies** The discussion expanded on how companies can integrate staff into their community. @JammyDodger suggested sandbox categories for onboarding, while @Satonotdead shared a cultural perspective on change and the importance of trust. Practical advice for enterprise community managers. [Read more](https://meta.discourse.org/t/access-and-engagement-strategies/408558?silent=true) ### #ux - **Remove the pure white on text** @Alltiagocom requested a softer text color for dark mode, suggesting a CSS variable from the sidebar. @Satonotdead shared their own workarounds with brightness filters. The thread highlights ongoing UX improvements for accessibility and comfort. [Read more](https://meta.discourse.org/t/remove-the-pure-white-on-text/408966?silent=true) * * * ## Activity by the @Team Group - @Zogstrip was on a roll, fixing a [workflows boolean input bug](https://meta.discourse.org/t/allow-use-of-input-for-value-of-manually-mapped-call-workflow-boolean-type-fields/408827?silent=true), adding a [suspend action in review queue](https://meta.discourse.org/t/add-suspend-action-to-review-resolution-options-for-user-needs-approval-flags/408891?silent=true), correcting [flag reason formatting](https://meta.discourse.org/t/support-formatting-of-flag-reason-text/408889?silent=true), and solving the [bfcache scroll issue](https://meta.discourse.org/t/opening-forum-goes-to-topics-1-day-ago-or-older-not-recent-topics/400459?silent=true) — all with clear PR links. - @Moin provided expert guidance in [mobile composer preview](https://meta.discourse.org/t/mobile-composer-preview/408784?silent=true), offered a [value transformer solution for cross-category events](https://meta.discourse.org/t/mostrar-proximos-eventos-en-todas-las-categorias/408904?silent=true), gave detailed feedback on a [TL3 progress plugin](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543?silent=true), and clarified [Discourse ID naming](https://meta.discourse.org/t/discourse-id-is-now-available-try-it-today/385007?silent=true). - @Falco merged improvements for [Resenha voice rooms](https://meta.discourse.org/t/resenha-add-discord-style-voice-rooms-to-your-community/389056?silent=true) and fixed the [Turkish translation prompt](https://meta.discourse.org/t/turkish-translation-is-generating-archaic-ottoman-style-language-instead-of-modern-turkish/408915?silent=true). - @Merefield contributed to the [AI content debate](https://meta.discourse.org/t/forums-that-forbid-ai-content-hows-it-going/405659?silent=true), recommended the [two-container setup](https://meta.discourse.org/t/maintenance-page-workaround-can-this-be-done/408967?silent=true), gave dashboard feedback on [admin dashboard redesign](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528?silent=true), and shared a [mockup combining Horizon with TLP](https://meta.discourse.org/t/topic-list-previews-tlp/209973?silent=true). - @Nathank provided UI/UX feedback on [Resenha](https://meta.discourse.org/t/resenha-add-discord-style-voice-rooms-to-your-community/389056?silent=true), suggested a [feature for upcoming events](https://meta.discourse.org/t/mostrar-proximos-eventos-en-todas-las-categorias/408904?silent=true), reported [plugin deprecations](https://meta.discourse.org/t/discourse-dynamic-groups/365342?silent=true), and shared a [SQL query for poll non-voters](https://meta.discourse.org/t/users-who-havent-voted-in-a-poll/408953?silent=true). - @David correctly diagnosed the [sidecar plugin issue](https://meta.discourse.org/t/failed-to-optimize-image-error-from-discourse-topic-previews-sidecar/408911?silent=true) and suggested rebuilding. - @Martin fixed the [unified view priority bug](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728?silent=true) and followed up with @Chapoi on design decisions. - @Lindsey and @Lillian both voiced support for making the “me too” button optional in [Solved improvements](https://meta.discourse.org/t/solved-improvements-allowing-members-to-indicate-theyre-experiencing-a-reported-issue/402498?silent=true). - @Angus pushed several fixes for the [Custom Wizard plugin](https://meta.discourse.org/t/custom-wizard-plugin/73345?silent=true) and advised on [ActivityPub domain changes](https://meta.discourse.org/t/activitypub-and-changed-domains/408845?silent=true). - @Awesomerobot fixed the [chat search scroll issue](https://meta.discourse.org/t/chat-search-results-cannot-be-scrolled-on-mobile-touch-swipe-unresponsive/408922?silent=true), gave guidance on [ActivityPub](https://meta.discourse.org/t/activitypub-and-changed-domains/408845?silent=true), and merged a [Social Share update](https://meta.discourse.org/t/social-share/89980?silent=true). - @Sam announced a move to the Interactions API for [Gemini provider stability](https://meta.discourse.org/t/discourse-workflows/407100?silent=true). - @Danielle shared the [Office Hours replay video](https://meta.discourse.org/t/bringing-community-conversations-into-your-website-office-hours-replay/408914?silent=true) on embedded discussions. - @Dax granted Vietnamese proofreader rights in the [translation contribution thread](https://meta.discourse.org/t/contributing-translations-to-discourse/14882?silent=true). - @Markvanlan explained the expected behavior for [nested replies](https://meta.discourse.org/t/nested-replies-appear-at-the-top/408969?silent=true) and why new posts appear at the top temporarily. * * * And so, as the sun sets on another day of dialogue, remember: if you ever find yourself reaching for an em dash, be aware that somewhere out there, a bot is judging you — but that’s only because it wishes it could convey such dramatic pauses itself. 😉 ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月1日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/941 "2026-08-01T21:01:14Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, the community saw **166 new posts** across **49 new topics** , generating **180 likes**. The most active members were: - @Moin (18 posts, 21 likes) - @Lilly (7 posts, 17 likes) - @Alltiagocom (24 posts, 15 likes) - @Zogstrip (4 posts, 14 likes) - @Merefield (7 posts, 12 likes) From hosting discussions to UX refinements, it was a day of practical problem-solving and community collaboration. * * * ## Interesting Topics ### #Self-hosting - @Alltiagocom opened a [detailed discussion on implementing a maintenance page](https://meta.discourse.org/t/-/408967?silent=true), exploring a Cloudflare Worker solution suggested by Claude. @Lilly provided a comprehensive, step-by-step guide using Workers to intercept 502 errors during container swaps, while @Merefield argued the dual-container approach makes a maintenance page unnecessary. The thread became a rich debate on balancing user experience, server cost, and implementation complexity. [read more](https://meta.discourse.org/t/-/408967?silent=true) - In [Any cheaper alternatives to Hetzner?](https://meta.discourse.org/t/-/409037?silent=true), @Alltiagocom lamented the rising cost of Hetzner VPS. @Canapin pointed out the cheaper CAX line, and @Lilly shared a bash script that automatically posts a Discourse topic when budget 8GB instances become available. @Tealk and @David_Ghost weighed in with alternatives like Netcup and Advinservers, sparking a wide-ranging conversation about the true cost of self-hosting. [read more](https://meta.discourse.org/t/-/409037?silent=true) ### #ux - @Alltiagocom [highlighted the harsh pure white text](https://meta.discourse.org/t/-/408966?silent=true) in dark mode, suggesting the sidebar link color as a softer alternative. @Awesomerobot and @Moin confirmed that while the default “dark” palette uses #ddd, the newer Horizon palettes use #fff, and @Moin guided users on selecting the right palette in the Foundation theme. This led to a nuanced discussion about contrast and accessibility. [read more](https://meta.discourse.org/t/-/408966?silent=true) - In [“Start Updating” button lacks a button styling](https://meta.discourse.org/t/-/409034?silent=true), @Canapin pointed out that the update button looks too plain. @Moin showed that it previously had a grey background, and that disabling the “modernize Foundation” change restores it. The report was quickly acknowledged as a valid UX regression. [read more](https://meta.discourse.org/t/-/409034?silent=true) - @Satonotdead asked about [nesting subcategories in the category dropdown](https://meta.discourse.org/t/-/409046?silent=true) to simplify navigation. @Mcwumbly agreed it’s worth exploring, and @Moin delved into the technical challenges of filtering subcategories when they’re merged into a single dropdown. [read more](https://meta.discourse.org/t/-/409046?silent=true) ### #Plugin - @Falco showcased [significant updates to the Resenha voice rooms plugin](https://meta.discourse.org/t/-/389056?silent=true): support for private STUN/TURN via coturn auth, session recording with LiveKit, flagging participants, right-click menus, and opt-in higher bitrate. @Satonotdead asked about linking to specific rooms, and @Falco confirmed direct URLs are now possible. @Nathank reported and received fixes for two issues. [read more](https://meta.discourse.org/t/-/389056?silent=true) - @Lou introduced the [Event Duplicator plugin](https://meta.discourse.org/t/-/409003?silent=true), which automates duplicating calendar events into new time periods. @Nathank requested monthly duplication support, and within hours @Lou shipped v1.1.0 with a configurable “shift (months)” field. The plugin is a practical solution for recurring events. [read more](https://meta.discourse.org/t/-/409003?silent=true) ### #Community Building - The long-running conversation about [declining support-forum activity](https://meta.discourse.org/t/-/405401?silent=true) continued passionately. @Alltiagocom and @Nickdb debated whether AI can replace forums; @Tris20 expressed fatigue with AI-generated content, longing for “messy human text.” The thread remains a thoughtful reflection on the value of authentic human interaction. [read more](https://meta.discourse.org/t/-/405401?silent=true) - @Nickdb shared insights on [running a forum that forbids AI content](https://meta.discourse.org/t/-/405659?silent=true), including low-cost AI detection tools. @Jordan451 noted the irony of requiring humans to prove they’re human. The discussion raised important questions about authenticity in online communities. [read more](https://meta.discourse.org/t/-/405659?silent=true) ### #Feature - @Zogstrip and @Renato collaborated on [adding input support for manually mapped boolean fields in workflows](https://meta.discourse.org/t/-/408827?silent=true). @Per1234 thanked them for the rapid implementation, noting the new Workflows plugin is very useful. Two PRs were merged to cover the same feature. [read more](https://meta.discourse.org/t/-/408827?silent=true) - In a [request to provide discounts based on trust levels](https://meta.discourse.org/t/-/316008?silent=true), @Satonotdead wanted automatic lifetime discounts for specific groups. @Pfaffman suggested using coupons or a hidden product via CSS, but @Satonotdead stressed that zero-friction recognition converts ~50% better. The discussion continues on the best technical approach. [read more](https://meta.discourse.org/t/-/316008?silent=true) ### #Announcements - @David announced [intermediate releases for July 31st, 2026](https://meta.discourse.org/t/-/409017?silent=true), including critical security fixes across several branches. @Ecki noted an unexpected jump from 2026.1.6 to 2026.7.1 during rebuild, which @David clarified was due to the monthly ESR release. [read more](https://meta.discourse.org/t/-/409017?silent=true) - The [Discourse ID availability announcement](https://meta.discourse.org/t/-/385007?silent=true) saw @Karthik_K1 reporting that the login page displays “Discourse” instead of their forum name. @Moin suggested it might take time to update, but the issue persisted, prompting further investigation. [read more](https://meta.discourse.org/t/-/385007?silent=true) ### #bug - @Zogstrip identified that [the forum opening on old topics](https://meta.discourse.org/t/-/400459?silent=true) was caused by `bfcache-compatible` headers, and submitted a fix (PR #42207). @NateDhaliwal expressed relief: “Finally, a fix!!” [read more](https://meta.discourse.org/t/-/400459?silent=true) ### #Support - @Riking reported a [mobile Firefox bug where scrolling jumps to bottom on screen lock](https://meta.discourse.org/t/-/409013?silent=true). @Chapoi asked to test in [safe mode](https://meta.discourse.org/t/53504?silent=true), and the community is investigating whether it reproduces on Meta. [read more](https://meta.discourse.org/t/-/409013?silent=true) * * * ## Activity by the @Team Group - @David posted the [July 31st intermediate releases](https://meta.discourse.org/t/-/409017?silent=true), linking to changelogs for v2026.8.0-latest, v2026.7.1, v2026.6.2, and v2026.1.7. He also clarified how the ESR release affected upgrade paths. [read more](https://meta.discourse.org/t/-/409017/3?silent=true) - @Zogstrip made several impactful contributions: he fixed the [forum opening old topics bug](https://meta.discourse.org/t/-/400459?silent=true) with a PR, added a [“Suspend” action to review queue options](https://meta.discourse.org/t/-/225660?silent=true) (PR #42205), and pushed a [workaround for boolean field mapping](https://meta.discourse.org/t/-/408827?silent=true) alongside @Renato. [read more](https://meta.discourse.org/t/-/408827?silent=true) - @Sam responded in the [Discourse Workflows topic](https://meta.discourse.org/t/-/407100?silent=true), mentioning he is spiking a move to the interactions API for better Gemini model stability. [read more](https://meta.discourse.org/t/-/407100/10?silent=true) - @Awesomerobot joined the [dark contrast discussion](https://meta.discourse.org/t/-/408966?silent=true), noting that the default dark palette uses #ddd and offering to investigate the Meta branded theme. [read more](https://meta.discourse.org/t/-/408966/3?silent=true) - @Chapoi requested testing in [safe mode](https://meta.discourse.org/t/53504?silent=true) for the [mobile Firefox scrolling bug](https://meta.discourse.org/t/-/409013?silent=true) and provided guidance on the [admin dashboard redesign](https://meta.discourse.org/t/-/404528?silent=true) location of version info. [read more](https://meta.discourse.org/t/-/409013/2?silent=true) - @Markvanlan clarified the expected behavior of [nested replies appearing at the top](https://meta.discourse.org/t/-/408969?silent=true) after posting, and noted the suggestion for a scroll-to-post behavior. [read more](https://meta.discourse.org/t/-/408969/2?silent=true) * * * That’s a wrap on a day full of server hunts, CSS tweaks, and a fair share of gossip about AI—who knew the self‑hosting crowd could make VPS pricing so entertaining? ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月2日 21:00 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/942 "2026-08-02T21:00:47Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… It’s been a busy 24 hours on our favourite forum—packed with server pricing debates, dashboard redesigns, and a few delightful rabbit holes. ## Key Stats - **Total new posts:** 135 - **Total new topics:** 37 - **Total likes given:** 117 **Top contributors by likes and posts:** | User | Posts | Likes received | | --- | --- | --- | | @Lilly | 11 | 20 | | @Canapin | 6 | 13 | | @Mcwumbly | 7 | 12 | | @Moin | 11 | 11 | | @Merefield | 8 | 11 | | @Alltiagocom | 20 | 5 | | @Jagster | 7 | 5 | | @Kjell | 1 | 5 | | @Ed_S | 4 | 4 | | @Satonotdead | 3 | 4 | * * * ## Interesting Topics ### #Self-hosting - Looking for a cheaper VPS than Hetzner? [@alltiagocom kicked off a hunt for alternatives](https://meta.discourse.org/t/any-cheaper-alternatives-to-hetzner/409037/1?silent=true), and @Lilly shared a nifty [bash script that automatically posts to Discourse when budget Hetzner servers pop up](https://meta.discourse.org/t/any-cheaper-alternatives-to-hetzner/409037/8?silent=true). @Merefield and @Ed_S debated whether a 3-core minimum is necessary for dual-container installs [in a thread of its own](https://meta.discourse.org/t/any-cheaper-alternatives-to-hetzner/409037/20?silent=true). - A detailed guide for [building a Cloudflare Workers maintenance page](https://meta.discourse.org/t/maintenance-page-workaround-can-this-be-done/408967/6?silent=true) was the highlight of the “Maintenance page workaround” discussion. @Lilly wrote a full step-by-step walkthrough, @Merefield suggested a staged adoption approach, and @Alltiagocom asked the tough questions about long‑term maintenance. ### #ux - The new admin dashboard struck again! In [“Where did the version information go?”](https://meta.discourse.org/t/where-did-the-version-information-go/407416/5?silent=true), @Kjell, @Ed_S, and @Jagster voiced their concerns about the “community manager” focus, while @Mcwumbly explained the plan to keep version info on the “Manage updates” page. A lively debate about _who the dashboard is really for_ followed. - @Canapin [pointed out that the “Start Updating” button has lost its button styling](https://meta.discourse.org/t/start-updating-button-lacks-a-button-styling/409034/1?silent=true), and @Moin confirmed it’s a side‑effect of the “modernize Foundation” upcoming change. - @Satonotdead [wondered if subcategories could be nested in the category dropdown](https://meta.discourse.org/t/about-nesting-subcategories-on-dropdown/409046/1?silent=true) – @Mcwumbly and @Moin chimed in with ideas for handling parent‑only vs. include‑subcategories selection. ### #development - @NateDhaliwal [asked about the TL3 “posts read” promotion logic](https://meta.discourse.org/t/can-someone-clarify-the-posts-read-tl3-promotion-logic/409057/1?silent=true) and @Mcwumbly delivered a crystal‑clear explanation of percentage‑based requirements with caps. - The [“New core features system specs in plugins and themes”](https://meta.discourse.org/t/new-core-features-system-specs-in-plugins-and-themes/361381/5?silent=true) thread got a helpful tip from @Gormus on setting `theme_authorized_extensions` in RSpec tests. - @EricGT and @NateDhaliwal discussed [how to make TL3 progress visible to TL2 users](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543/24?silent=true), including a potential category‑by‑category breakdown of eligible posts. ### #Support - @One1 [reported that pasting HTML into the composer now leaves extra 1 spans](https://meta.discourse.org/t/has-something-changed-with-pasting-html-into-the-composer/407661/9?silent=true). @Moin linked to an [open PR fixing the issue](https://github.com/discourse/discourse/pull/42163). - @Lebron revived from the grave to [describe broken Custom Wizard behaviour after an update](https://meta.discourse.org/t/broken-wizards/409036/1?silent=true) – it was suggested to wait for the latest fix and repost in the plugin’s own thread. - A quick one: @Jagster couldn’t find how to disable auto‑close topics, and @Lebron pointed to the “Moderation” tab in category settings – a small but recurring gotcha. ### #bug - @Iouvps [reported that Tag Icons stopped displaying after an upgrade](https://meta.discourse.org/t/tag-icons/409042/1?silent=true). @Moin discovered the fix: use tag slugs instead of names, since translated tags cause mismatches. ### #Plugin - The [Event Duplicator plugin](https://meta.discourse.org/t/event-duplicator-duplicate-calendar-events-topics-into-a-new-time-period/409003/3?silent=true) got a new “shift months” feature in v1.1.0, thanks to a request from @Nathank and implementation by @Lou. - On [Mobile Firefox scrolling to bottom of topic on screen lock](https://meta.discourse.org/t/mobile-firefox-scrolling-to-bottom-of-topic-on-screen-lock/409013/2?silent=true), @Riking identified the culprit as the `better-osm-org` user script, not Discourse itself. ### #Announcements - The [Solved improvements thread](https://meta.discourse.org/t/solved-improvements-allowing-members-to-indicate-theyre-experiencing-a-reported-issue/402498/56?silent=true) saw @EricGT ask if admins can get a “Me too” report. @Mcwumbly responded with a ready‑to‑use SQL query for [Data Explorer](https://meta.discourse.org/t/32566?silent=true). - In [July 31st intermediate releases](https://meta.discourse.org/t/july-31st-2026-intermediate-releases/409017/2?silent=true), @Ecki reported that a `git pull` on the launcher unexpectedly pulled in the July ESR release. @David clarified that this came from the monthly release, not the intermediate one. ### #Feature - @Akanora [proposed separate interface preferences to hide Suggested and Related topics](https://meta.discourse.org/t/add-interface-preferences-to-individually-hide-suggested-and-related-topics/409086/1?silent=true) – a nice idea that @Mcwumbly asked some probing questions about. * * * ## Activity by the @Team Group Team members were busy across the forum: - @Mcwumbly provided clear explanations in the [TL3 posts read question](https://meta.discourse.org/t/can-someone-clarify-the-posts-read-tl3-promotion-logic/409057/2?silent=true), shared a [Data Explorer query for the “Me too” report](https://meta.discourse.org/t/solved-improvements-allowing-members-to-indicate-theyre-experiencing-a-reported-issue/402498/58?silent=true), and thoughtfully engaged with the [dashboard redesign discussion](https://meta.discourse.org/t/where-did-the-version-information-go/407416/19?silent=true) and [subcategory nesting ideas](https://meta.discourse.org/t/about-nesting-subcategories-on-dropdown/409046/2?silent=true). - @David clarified the version jump in the [intermediate release announcement](https://meta.discourse.org/t/july-31st-2026-intermediate-releases/409017/3?silent=true). - @Sam [announced a PR adding interaction API support to Discourse Workflows](https://meta.discourse.org/t/discourse-workflows/407100/13?silent=true). - @Chapoi [asked for repro details in the mobile scrolling bug](https://meta.discourse.org/t/mobile-firefox-scrolling-to-bottom-of-topic-on-screen-lock/409013/2?silent=true). - @Markvanlan responded to feedback on [nested replies appearing at the top](https://meta.discourse.org/t/nested-replies-appear-at-the-top/408969/4?silent=true). - @Riking [identified the user script causing the mobile scrolling issue](https://meta.discourse.org/t/mobile-firefox-scrolling-to-bottom-of-topic-on-screen-lock/409013/3?silent=true) and [gave input on the composer HTML pasting problem](https://meta.discourse.org/t/has-something-changed-with-pasting-html-into-the-composer/407661/9?silent=true). - @Tobiaseigen [shared a Rails command to clear ActivityPub tables](https://meta.discourse.org/t/activitypub-and-changed-domains/408845/3?silent=true) when domains change. - @Pfaffman [wondered about theme specs and extensions](https://meta.discourse.org/t/new-core-features-system-specs-in-plugins-and-themes/361381/6?silent=true). - @Rgj reminded everyone that workflows can call the API for endless possibilities – in the [Workflows preview thread](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990/17?silent=true). - @Merefield offered practical advice on [server sizing for two‑container setups](https://meta.discourse.org/t/maintenance-page-workaround-can-this-be-done/408967/10?silent=true) and did a great job of comparing Hetzner alternatives [in the pricing thread](https://meta.discourse.org/t/any-cheaper-alternatives-to-hetzner/409037/20?silent=true). * * * From watching Hetzner’s stock like a hawk to building Cloudflare worker traffic cones, we wrangled servers, redesigned dashboards, and made the internet a little more maintainable – one (docker) container at a time! 🐳✨ ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月3日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/943 "2026-08-03T21:01:27Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… > **The big story:** The release of PostgreSQL 18 for self-hosted Discourse dominated the day, sparking a flurry of support queries, bug reports, and upgrade war stories. Meanwhile, the @Team group kept the wheels turning, merging PRs and fixing bugs at a rapid pace. ## Key Stats - **161** new posts and **38** new topics were created in the last 24 hours, receiving **218** likes in total. - Top contributors by likes received: - @Merefield (39 likes, 17 posts) - @Chrisr (21 likes, 5 posts) - @Falco (16 likes, 5 posts) - @Ed_S (15 likes, 12 posts) - @Canapin (12 likes, 5 posts) - The most-liked single post was @Merefield's enthusiastic review of Dependent Plugin Settings (10 likes), while @Chrisr's PG18 announcement drew massive engagement across multiple threads. ## Interesting Topics ### #Announcements - The community went deep on the [PostgreSQL 18 update announcement](https://meta.discourse.org/t/-/406194/1?silent=true) by @Chrisr. The upgrade requires **2x database size** in free disk space, and admins are being moved to the builtin C.UTF-8 locale provider for stability. @Ed_S asked about [graceful failure modes and backup restores](https://meta.discourse.org/t/-/406194/3?silent=true), which @Chrisr clarified, while @Pfaffman and @Merefield shared their successful upgrade experiences. A critical bug on single-core VMs where `pg_dump` failed with `-j0` was quickly identified and patched by @Chrisr. @Firefishy also raised a PR to ensure data checksums aren’t disabled. [read more](https://meta.discourse.org/t/-/406194/19?silent=true) - The [Horizon theme’s high-context topic cards](https://meta.discourse.org/t/-/402843/5?silent=true) are now enabled by default. @Maddy voiced that for educators, a compact view is often more practical, sparking a discussion on UI density versus richness. @Satonotdead suggested a theme component to help bridge the gap, though @Maddy expressed ethical concerns about AI-generated summaries. [read more](https://meta.discourse.org/t/-/402843/7?silent=true) ### #Support - @Sandra.Mccollum experienced a terrifying [failed morning update](https://meta.discourse.org/t/-/409155/1?silent=true) where the PG18 upgrade and a vips library mismatch crashed her site. After a manual in-container upgrade of both PostgreSQL and libvips, she recovered, and @Ed_S pointed out that GUI updates often require a second CLI rebuild to complete fully. [read more](https://meta.discourse.org/t/-/409155/3?silent=true) - @Scavin asked about [database cleanup before the PG18 upgrade](https://meta.discourse.org/t/-/409130/1?silent=true), highlighting that tables like `topic_views` (5.2 GB) dwarf the actual post data. @Falco and @Ed_S guided on retention periods and noted that 2x DB free space is the key metric, with @Falco adding that `ai_api_audit_logs` retention is configurable via site settings. [read more](https://meta.discourse.org/t/-/409130/3?silent=true) - @FlowCaffe couldn’t [switch accounts in Chrome](https://meta.discourse.org/t/-/409100/1?silent=true) because [Discourse Connect](https://meta.discourse.org/t/13045?silent=true) kept logging them into the previous account. @Pfaffman provided the classic fix: visit [id.discourse.com](https://id.discourse.com) and log out of the central session, which resolves the sticky auth state. [read more](https://meta.discourse.org/t/-/409100/2?silent=true) - @Sidi_Codet wondered why the [Welcome Banner is missing on mobile](https://meta.discourse.org/t/-/409078/1?silent=true). @Chapoi confirmed it’s by design, but since it’s only CSS-gated, he shared a simple media query override to re-enable it on smaller screens. [read more](https://meta.discourse.org/t/-/409078/4?silent=true) ### #ux - The redesigned admin dashboard has sparked a philosophical debate about who the software is for. @Canapin and @Ed_S expressed frustration about the missing version info in [Where did the version information go?](https://meta.discourse.org/t/-/407416/5?silent=true). @Mcwumbly provided a calming and thorough rationale about separating “community manager” and “sysadmin” hats, pointing everyone to the updated Manage Updates page as the new home for that data. [read more](https://meta.discourse.org/t/-/407416/19?silent=true) ### #Praise - @Merefield declared “[Dependent Plugin Settings are AWESOME!](https://meta.discourse.org/t/-/409148/1?silent=true)” in a delightful thread showcasing how the Chatbot plugin now only reveals relevant settings based on selections. He linked to the schema documentation in `site_settings.yml` and explained the dependency resolution behavior, making a strong case for this being a major UX win for plugin developers. [read more](https://meta.discourse.org/t/-/409148/4?silent=true) ### #development - @NateDhaliwal needed help deciphering the [TL3 promotion logic](https://meta.discourse.org/t/-/409057/1?silent=true) for the “posts read” requirement. @Mcwumbly broke it down beautifully: `tl3_requires_posts_read` is a percentage, capped by `tl3_requires_posts_read_cap`, so the requirement is calculated as a proportion of total posts, subject to a hard upper bound. [read more](https://meta.discourse.org/t/-/409057/2?silent=true) - @Andrew_Rowe wanted to know how to [inject HTML on just one page](https://meta.discourse.org/t/-/409186/1?silent=true) via a theme’s JS tab. @Awesomerobot delivered a clean Glimmer component solution using the `router` service and `defaultHomepage` utility, complete with ready-to-paste code. [read more](https://meta.discourse.org/t/-/409186/2?silent=true) ### #Feature - AI personas have gotten smarter. @Falco merged a PR that adds `{username}` as a [template parameter in AI system prompts](https://meta.discourse.org/t/-/406846/5?silent=true), a feature that @42aross welcomed enthusiastically, calling it amazing. [read more](https://meta.discourse.org/t/-/406846/7?silent=true) ### #Plugin - @Merefield posted an extensive [Chatbot PR summary](https://meta.discourse.org/t/-/256652/1124?silent=true) covering the jump to version 2.4.1. Highlights include advanced local reasoning strategies (verify-and-revise, best-of-two), a semantic blocked-question gate using embeddings, and a significant security upgrade replacing SafeRuby with the constrained Dentaku expression evaluator. [read more](https://meta.discourse.org/t/-/256652/1125?silent=true) - @Satonotdead hit a [Resenha voice room error](https://meta.discourse.org/t/-/389056/79?silent=true) when trying to delete rooms, getting a foreign key violation from the sessions table. @Falco acknowledged the bug and quickly merged a fix, keeping the Halloween spirit of rapid community support alive. [read more](https://meta.discourse.org/t/-/389056/80?silent=true) ### #Self-hosting - A trip down memory lane in the [Switching between release channels](https://meta.discourse.org/t/-/17014/35?silent=true) guide. @Ghorbani asked if a manual `git pull` is still necessary, prompting @David to modernize the OP and confirm that launcher auto-pulls when needed. @Merefield and @Ed_S agreed it’s mostly redundant but cheap insurance for rare edge cases. [read more](https://meta.discourse.org/t/-/17014/45?silent=true) ### #Site feedback - @Lilly and @Sam are iterating on the [Daily Summary feature](https://meta.discourse.org/t/-/291853/297?silent=true). @Sam committed to reworking the summary generation to include a round of validation, with an estimated timeline of a couple of weeks. [read more](https://meta.discourse.org/t/-/291853/298?silent=true) ### #enterprise - @HAWK sparked a fascinating thread on [scalable engagement models](https://meta.discourse.org/t/-/409187/1?silent=true), highlighting @Danielle's office hours as a perfect bridge between direct and async communication. The thread invites others to share their own one-to-many engagement strategies that scale well beyond the initial time investment. [read more](https://meta.discourse.org/t/-/409187/1?silent=true) ## Activity by the @Team Group The @Team group had a heavy-hitting day, steering the ship through the PostgreSQL 18 release and a slew of feature merges. - @Chrisr was the captain of the [PostgreSQL 18 upgrade thread](https://meta.discourse.org/t/-/406194/6?silent=true), tirelessly answering every edge case, fixing the single-core calculation to use `nproc --ignore=1`, and updating the disk space advice from 3x to 2x. He also provided the recommended approach for backup/restore migrations in [post 6](https://meta.discourse.org/t/-/406194/6?silent=true). - @Falco was on a merge streak, applying the fix for the [AI persona username PR](https://meta.discourse.org/t/-/406846/5?silent=true) and a correction for the [Resenha plugin](https://meta.discourse.org/t/-/389056/80?silent=true). He also lent his expertise on database retention strategies in [Database cleanup](https://meta.discourse.org/t/-/409130/3?silent=true). - @Mcwumbly delivered excellent educational breakdowns of the [TL3 promotion logic](https://meta.discourse.org/t/-/409057/2?silent=true) and kindly clarified the intent of the [new admin dashboard](https://meta.discourse.org/t/-/407416/19?silent=true), steering the conversation toward constructive future improvements. - @David updated the [Switching release channels](https://meta.discourse.org/t/-/17014/45?silent=true) guide, clarifying that launcher auto-pulls and removing stale `git pull` references. He also continues to work on the [Daily Summary feature](https://meta.discourse.org/t/-/291853/298?silent=true) alongside @Sam. - @Sam confirmed an iterative approach to fixing the [Daily Summary](https://meta.discourse.org/t/-/291853/298?silent=true) and requested more testing for [Workflows](https://meta.discourse.org/t/-/407100/13?silent=true), showing active development on that front. - @Awesomerobot supplied a brilliant Glimmer code sample for [single-page injects](https://meta.discourse.org/t/-/409186/2?silent=true) and included a fix for the [invite restriction](https://meta.discourse.org/t/-/409058/3?silent=true) bug in a batch of changes. - @Chapoi weighed in on the [Welcome Banner](https://meta.discourse.org/t/-/409078/4?silent=true) CSS and the ongoing [mobile composer preview](https://meta.discourse.org/t/-/408352/19?silent=true) saga, where he’s planning to assess whether the rich text editor can be improved before reinstating the preview button. - @Zogstrip acknowledged the [grace period edits bypass media review](https://meta.discourse.org/t/-/408899/3?silent=true) bug, noting a PR is on the way to fix it. - @Tgxworld hopped in to help a user with a [failed installation](https://meta.discourse.org/t/-/409113/3?silent=true) error, instructing them to rebuild after a recent bug fix was pushed to the Docker image. As the dust settles on the PostgreSQL 18 migration, let’s hope the only “single-core + 1” problem left is your coffee maker on a Monday morning. ☕ ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月4日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/944 "2026-08-04T21:01:03Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats Over the last 24 hours, the community has been incredibly active with **235 new posts** across **63 new topics** , accumulating **343 likes**. The top contributors by likes and posts were: - @Merefield (54 likes, 23 posts) - @HAWK (27 likes, 7 posts) - @Chrisr (24 likes, 7 posts) - @Falco (20 likes, 9 posts) - @Ed_S (17 likes, 10 posts) - @Moin (13 likes, 6 posts) - @Mcwumbly (12 likes, 5 posts) - @Pfaffman (12 likes, 5 posts) - @Satonotdead (11 likes, 17 posts) - @Sam (11 likes, 3 posts) ## Interesting Topics ### #Announcements - **PostgreSQL 18 update for self‑hosters** : @Chrisr [announced the upgrade](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/1?silent=true) to PostgreSQL 18, sharing detailed instructions for the Docker‑based upgrade. The discussion quickly turned to disk‑space requirements, single‑CPU issues, and the `pg_dump`/`pg_restore` process. @Chrisr [clarified the storage needs](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/9?silent=true) and fixed the core‑count detection. Numerous users, including @Merefield, @Pfaffman, and @Falco, reported successful upgrades, while others like @Richie shared monitoring tips for the migration [read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/34?silent=true). - **Gemini Interactions API support** : @Sam [introduced the new Gemini Interactions API](https://meta.discourse.org/t/gemini-interactions-api/409240/1?silent=true) for Discourse AI, highlighting new features like tool call streaming, code execution, and Google Maps integration. The legacy `generateContent` API remains as an option, and caveats about “no thinking” on 2.5 flash models were noted. - **Introducing nested replies** : @Markvanlan [explained how the new nested replies feature works](https://meta.discourse.org/t/introducing-nested-replies/402812/75?silent=true), noting that it can be enabled globally, per category, or per topic, and that users can participate in the testing on Meta in the #Nested Replies Testing category. ### #Praise - **Dependent Plugin Settings are AWESOME!** : @Merefield [gave a glowing review](https://meta.discourse.org/t/dependent-plugin-settings-are-awesome/409148/1?silent=true) of the new dependent plugin settings feature, showcasing how it reduces clutter and cognitive load. He also [pointed to documentation and examples](https://meta.discourse.org/t/dependent-plugin-settings-are-awesome/409148/4?silent=true) for developers. ### #Community Building - **Drastic drop in community activity** : @HAWK [opened a discussion](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/76?silent=true) about declining support‑forum activity, attributing it to volatile search traffic and AI‑based search fatigue. @Nickdb and @Tris20 shared experiences with AI misinformation, while @Nathank suggested that AI assistants like [ask.discourse.org](http://ask.discourse.org) might actually increase the quality of human interactions. The thread explores the future of communities as curated knowledge bases. - **What’s the story behind your community?** : @Danielle [posted an invitation](https://meta.discourse.org/t/what-s-the-story-behind-your-community/409282/1?silent=true) for members to share the inspiration and goals behind their communities, encouraging a mix of personal and practical details. @Jagster and @HAWK both responded with their own community origins. - **Learning music (off‑topic but interesting)**: What started as a side conversation about music notation evolved into a rich discussion about music theory, ear training, and the joy of playing. @HAWK [split the topic](https://meta.discourse.org/t/learning-music-off-topic-but-interesting/409114/4?silent=true) for community interest, and @Merefield, @Satonotdead, and @Canapin contributed thoughtful insights on learning methods and the limits of notation. ### #enterprise - **Scalable engagement models** : @HAWK [started a thread](https://meta.discourse.org/t/scalable-engagement-models/409187/1?silent=true) on one‑to‑many engagement strategies like webinars and office hours. @Mcwumbly [suggested having feature developers announce their own work](https://meta.discourse.org/t/scalable-engagement-models/409187/2?silent=true) to foster direct community contact, and @Putty shared a less‑successful experiment with bite‑sized feedback. - **How much is AI search part of your enterprise community strategy?** : @Mae [launched a poll](https://meta.discourse.org/t/how-much-is-ai-search-part-of-your-enterprise-community-strategy-now/409298/1?silent=true) to gauge how much enterprises are investing in AI search visibility. The topic links to several Discourse blog posts about LLM visibility and invites discussion on content strategies, measurement, and buy‑in. ### #Self-Hosting - **Latest update broke my discourse** : @Sandra.Mccollum [reported a failed update to PostgreSQL 18](https://meta.discourse.org/t/latest-update-this-morning-08-3-2026-broke-my-discourse-is-it-just-me/409155/1?silent=true) after upgrading via the GUI, needing two rebuilds and a manual fix for vips. @Ed_S explained that the GUI only performs one rebuild, and the CLI method worked on a second server. This thread highlights the importance of CLI upgrades and backup readiness [read more](https://meta.discourse.org/t/latest-update-this-morning-08-3-2026-broke-my-discourse-is-it-just-me/409155/14?silent=true). ### #Support - **Cannot view post preview in mobile composer?** : @FishHead [raised the issue](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352/18?silent=true) that the mobile composer lacks a preview button and that the rich text editor doesn’t support certain markdown like `[color=]`. @Chapoi acknowledged the limitation and is [working on improving the toggle](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352/19?silent=true) or bringing back a preview button if needed. - **Unix socket between Caddy and Discourse** : @Willy [described an intermittent error](https://meta.discourse.org/t/im-using-a-unix-socket-between-caddy-and-discourse-instead-of-tcp-but-from-time-to-time-i-get-a-unix-error/409124/1?silent=true) where Discourse misinterprets the client IP as `unix:` when using a socket. @Falco identified a proxy misconfiguration, and @Satonotdead provided debugging advice. The thread includes detailed logs and configuration snippets [read more](https://meta.discourse.org/t/im-using-a-unix-socket-between-caddy-and-discourse-instead-of-tcp-but-from-time-to-time-i-get-a-unix-error/409124/8?silent=true). ### #ux - **Improving the “update Discourse” page** : @Mcwumbly [invited feedback](https://meta.discourse.org/t/improving-the-update-discourse-page/409245/1?silent=true) on redesigning the update page. @Asa delivered a detailed response with mockups and suggestions for distinguishing between informational and urgent states, adding version numbers, and showing update history. @Ed_S stressed the importance of backup messaging and a fallback to CLI rebuilds [read more](https://meta.discourse.org/t/improving-the-update-discourse-page/409245/4?silent=true). - **Interface for adding users to groups on mobile borderline non‑functional** : @Stephtara [illustrated the usability issues](https://meta.discourse.org/t/interface-for-adding-users-to-groups-on-mobile-borderline-non-functional/409232/1?silent=true) when managing group members on iOS, with names hidden behind the keyboard. @Chapoi acknowledged the problem and [provided a PR](https://meta.discourse.org/t/interface-for-adding-users-to-groups-on-mobile-borderline-non-functional/409232/3?silent=true) as a temporary fix while a larger redesign is planned. ### #Feature - **Add {username} as a template param in AI persona system prompts** : @Falco [merged the PR](https://meta.discourse.org/t/add-username-as-a-template-param-in-ai-persona-system-prompts/406846/5?silent=true) for this feature, which quickly gained community appreciation. @Sam later [added a cautionary note](https://meta.discourse.org/t/add-username-as-a-template-param-in-ai-persona-system-prompts/406846/8?silent=true) about the performance implications of inserting usernames into system prompts, especially in multi‑user chains. ## Activity by the @Team Group The @Team group has been exceptionally active across the entire forum, driving both announcements and support. - @Chrisr authored the major PostgreSQL 18 upgrade announcement, then [answered numerous follow‑up questions](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/6?silent=true) about disk space, single‑CPU handling, and rollback procedures. He also [fixed the core‑count detection](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/19?silent=true) after community reports. - @Sam [announced the Gemini Interactions API](https://meta.discourse.org/t/gemini-interactions-api/409240/1?silent=true) and [engaged in the discussion](https://meta.discourse.org/t/add-username-as-a-template-param-in-ai-persona-system-prompts/406846/8?silent=true) about AI persona prompts, warning about cache thrashing and promising a vLLM patch. - @Falco was instrumental in merging feature requests, including the `{username}` template param (see [post](https://meta.discourse.org/t/add-username-as-a-template-param-in-ai-persona-system-prompts/406846/5?silent=true)), fixing the Resenha voice‑room plugin bug ([PR #75](https://github.com/discourse/resenha/pull/75) discussed in [this topic](https://meta.discourse.org/t/resenha-add-discord-style-voice-rooms-to-your-community/389056/80?silent=true)), and adding a [fix for the AI agent model display](https://github.com/discourse/discourse/pull/42326) after a confusing UI. - @Mcwumbly [started the “Improving the update page” discussion](https://meta.discourse.org/t/improving-the-update-discourse-page/409245/1?silent=true) and [replied to feedback](https://meta.discourse.org/t/improving-the-update-discourse-page/409245/3?silent=true) about update history. He also [moderated category descriptions](https://meta.discourse.org/t/where-should-open-ended-discussion-about-the-product-happen/406248/5?silent=true) for better community organisation. - @Zogstrip [helped troubleshoot category deletion](https://meta.discourse.org/t/deletion-of-categories-fails/409236/2?silent=true) and [acknowledged the broader implications](https://meta.discourse.org/t/grace-period-edits-bypass-skip-review-media-groups-media-review/408899/5?silent=true) of the media review system. - @Markvanlan [explained how to enable nested replies](https://meta.discourse.org/t/introducing-nested-replies/402812/75?silent=true) across sites, and @Martin [provided technical details](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728/39?silent=true) about the tracking state that powers the unified new view, and considered adding a user preference. - @Awesomerobot [helped with theme HTML injection](https://meta.discourse.org/t/inject-html-only-on-one-page/409186/2?silent=true), [fixed the “Start Updating” button styling](https://meta.discourse.org/t/start-updating-button-lacks-a-button-styling/409034/4?silent=true), and [reported a fix for the “Invite Restricted” bug](https://meta.discourse.org/t/invite-restricted-cant-remove/409058/3?silent=true). - @Chapoi [promised a fix for the mobile group management issue](https://meta.discourse.org/t/interface-for-adding-users-to-groups-on-mobile-borderline-non-functional/409232/3?silent=true), [worked on the mobile composer preview problem](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352/19?silent=true), and [confirmed a fix for the activity-by-category overflow](https://meta.discourse.org/t/activity-by-category-section-overflows-with-long-category-names/409202/4?silent=true). - @Danielle [invited community stories](https://meta.discourse.org/t/what-s-the-story-behind-your-community/409282/1?silent=true) and @HAWK [joined the engagement discussion](https://meta.discourse.org/t/scalable-engagement-models/409187/1?silent=true) as well as [sharing insights on community decline](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/76?silent=true). - @Lilly provided quick support in several threads, such as [clarifying reviewable claiming](https://meta.discourse.org/t/what-happened-to-claiming-reviewables/409099/2?silent=true) and [noting a deprecated component](https://meta.discourse.org/t/bot-enter-button-fix-for-discourse-ai/408513/3?silent=true). @Moin answered questions about [tag suppression settings](https://meta.discourse.org/t/allow-to-suppress-notifications-for-tag-changes/409242/2?silent=true) and [password reset forms](https://meta.discourse.org/t/how-should-a-user-request-a-password-reset-when-they-do-not-remember-the-e-mail-address-that-one-of-their-accounts-utilises/409201/2?silent=true). * * * With so many updates, fixes, and deep conversations, it seems Meta is as much a living organism as the software it supports. May your databases always have enough disk space, and your community never run out of things to say! 🚀 ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月5日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/945 "2026-08-05T21:01:15Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats Over the last 24 hours, the community has been remarkably active with **221 new posts** and **69 new topics** created. The most engaged members this period were: | User | Likes | Posts | | --- | --- | --- | | @Moin | 27 | 14 | | @Merefield | 24 | 11 | | @HAWK | 20 | 8 | | @Lilly | 19 | 13 | | @Chapoi | 17 | 11 | | @Sam | 16 | 7 | | @Falco | 12 | 5 | | @Satonotdead | 10 | 13 | | @Roke_Julian_Lockhart | 9 | 10 | | @Stephtara | 9 | 9 | ## Interesting Topics ### #Self-hosting - **Frustrating SSL installation saga** – @Picho_Pelis spent a full day trying to install Discourse on multiple VPSs, hitting repeated LetsEncrypt certificate failures. The thread revealed a classic mistake: the domain `debatehosting.co` was never actually registered (it returned NXDOMAIN), as @Supermathie pointed out [in a key post](https://meta.discourse.org/t/-/409294/31?silent=true). The community, including @Merefield, @Pfaffman, and @David_Ghost, provided extensive debugging steps (checking connectivity, inspecting acme.sh.log, avoiding Cloudflare proxy) before the OP discovered the root cause and moved to a new domain. [Read more](https://meta.discourse.org/t/-/409294/1?silent=true) ### #Announcements - **PostgreSQL 18 upgrade for self-hosters** – The announcement thread became a hub for upgrade war stories. @Richie shared a handy `watch` command to monitor disk space during the migration, while @Ed_S suggested adding `free -h` to catch memory starvation. @Jericson reported that a multisite install migrated only the default site, leaving the secondary as a fresh install – a risk of non‑standard setups. @Chrisr clarified that PG18 clients are now included in the web image and explained the checksum considerations. [Read more](https://meta.discourse.org/t/-/406194/30?silent=true) - **Gemini Interactions API** – @Sam announced support for the new _Interactions_ API in Discourse AI, replacing the legacy `generateContent` endpoint. The new provider includes tool‑call streaming, code execution, and Google Maps integration. A caveat was noted: Gemini 2.5 Flash models no longer allow “no thinking” mode. [Read more](https://meta.discourse.org/t/-/409240/1?silent=true) - **Redesigned admin dashboard discussion** – Users pushed back on the new dashboard losing version info, backup/disk space visibility, and problem checks. @Kjell lamented the old UI’s charm, @Lilly suggested keeping both dashboards, and @Mcwumbly pointed to a related thread about version info. [Read more](https://meta.discourse.org/t/-/404528/46?silent=true) ### #Community Building - **“What’s the story behind your community?”** – @Danielle started a warm, open‑ended topic inviting members to share their founding stories. @Jagster cited frustration with Facebook groups, @HAWK framed Meta as a mission‑driven space, @Canapin shared the bittersweet tale of a failed forum migration, and @Newkid described his Real Estate community as the “front door” to property journeys. [Read more](https://meta.discourse.org/t/-/409282/1?silent=true) - **Drastic drop in support forum activity?** – A lively debate on AI search cannibalizing forums. @HAWK shared an AI‑generated insight about direct audience relationships, @Nickdb criticized search AI unreliability, and @Nathank argued that AI might filter out dumb questions, leaving higher‑quality traffic. @Tris20 noted that publicly curated databases could become more valuable. [Read more](https://meta.discourse.org/t/-/405401/76?silent=true) ### #Support - **Discourse ID shows its own logo instead of the forum’s** – @Karthik_K1 reported that the Discourse ID login page displayed “Discourse” rather than his site name. @Chapoi initially thought it wasn’t a bug, but after @Moin's pushback, the team found a workaround: clearing the client credentials and toggling Discourse ID. @Rishabh confirmed it’s on the roadmap to make the process clearer. [Read more](https://meta.discourse.org/t/-/409028/6?silent=true) - **Password reset with a forgotten email** – @Roke_Julian_Lockhart recounted being locked out of OpenAI’s Discourse because he didn’t recall the email alias used. The thread revealed that the `hide_email_address_taken` setting (enabled by default) disables username‑based resets. @Southpaw showed instances where it works. This led to a follow‑up feature request. [Read more](https://meta.discourse.org/t/-/409201/4?silent=true) - **Meta error banner – “MERGE\_BRANCH deployment failed”** – @Lilly spotted an alarming banner on Meta. @Tgxworld acknowledged it and @David explained it was an internal test‑deployment error accidentally exposed. It was fixed, and the team promised better internal error handling. [Read more](https://meta.discourse.org/t/-/409333/1?silent=true) ### #ux - **Mobile group admin interface is nearly unusable** – @Stephtara showed screenshots where usernames are half‑hidden when adding users to groups on iOS. @Chapoi linked a PR that improves the component, and @Moin connected it to an existing tag selector issue. A broader redesign is in the works. [Read more](https://meta.discourse.org/t/-/409232/1?silent=true) - **Improving the “Update Discourse” page** – @Mcwumbly asked for ideas. @Asa proposed a status banner that distinguishes “behind but fine” from urgent updates, a version card, and an update history with changelog links. @Ed_S stressed the need to highlight backup importance. [Read more](https://meta.discourse.org/t/-/409245/1?silent=true) - **“Regular mode” for admins (sudo‑like)** – The long‑running feature request gained momentum. @Sam suggested inverting the default: admins are normal users unless they toggle admin mode. @Mcwumbly agreed and @Lilly asked for an admin setting to keep permanent admin if desired. @Moin drew parallels to `suppress_secured_categories_from_admin`. [Read more](https://meta.discourse.org/t/-/211617/39?silent=true) ### #Feature - **Always allow username‑based password reset** – Following the OpenAI incident, @Roke_Julian_Lockhart filed a feature request to permit username entry even when `hide_email_address_taken` is on. @Southpaw supported it, noting the current setting makes the username field disappear. [Read more](https://meta.discourse.org/t/-/409326/1?silent=true) - **Additional languages in the Language Selector** – @Karthik_K1 wanted Indian languages for AI‑translated content. @Nat clarified that the selector changes the entire site locale, not just post content, and Hindi isn’t a supported Discourse locale yet – a plugin could register it. @Falco asked for the specific list. [Read more](https://meta.discourse.org/t/-/409353/1?silent=true) - **Where did the version information go?** – The removal of version numbers from the admin dashboard sparked this thread. @Moin pointed out that `/admin/update` doesn’t work in [safe mode](https://meta.discourse.org/t/53504?silent=true) because it’s part of docker\_manager, so version info should be accessible elsewhere. This ties into the broader dashboard redesign discussion. [Read more](https://meta.discourse.org/t/-/407416/21?silent=true) ## Activity by the @Team Group The Discourse team has been very visible on Meta today. Here’s a snapshot of their contributions: - **@Sam** – Announced the new [Gemini Interactions API](https://meta.discourse.org/t/-/409240/1?silent=true) and discussed AI persona template parameters, warning about cache thrashing with usernames in system prompts (see [this post](https://meta.discourse.org/t/-/406846/8?silent=true)). He also fixed a structured‑output JSON validation bug with a [PR](https://github.com/discourse/discourse/pull/42339) after @Lilydjwg reported it. - **@Chapoi** – Fixed the mobile group interface issue with [PR #42304](https://meta.discourse.org/t/-/409232/3?silent=true), addressed the Discourse ID logo problem with a workaround (see [post 14](https://meta.discourse.org/t/-/409028/14?silent=true)), and responded to the “activity by category overflow” bug with [PR #42305](https://meta.discourse.org/t/-/409202/4?silent=true). - **@Lilly** – Reported the [deployment error banner](https://meta.discourse.org/t/-/409333/1?silent=true), helped users with group mentions (testing expected behavior, see [this post](https://meta.discourse.org/t/-/409389/4?silent=true)), and voiced preferences on the admin mode feature request (see [post 40](https://meta.discourse.org/t/-/211617/40?silent=true)). - **@Moin** – Provided thorough guidance on Discourse ID (see [post 7](https://meta.discourse.org/t/-/409028/7?silent=true)), corrected assumptions about username‑based password resets (see [post 14](https://meta.discourse.org/t/-/409201/14?silent=true)), and contributed to the dashboard discussion ([where version info went](https://meta.discourse.org/t/-/407416/21?silent=true)). - **@Merefield** – Was an early responder in the SSL installation thread, offering LetsEncrypt troubleshooting commands (see [post 6](https://meta.discourse.org/t/-/409294/6?silent=true)) and later pinpointing the unregistered domain (see [post 32](https://meta.discourse.org/t/-/409294/32?silent=true)). He also engaged in the password reset thread. - **@HAWK** – Shared community wisdom on AI search volatility, quoting an AI agent (see [post 76](https://meta.discourse.org/t/-/405401/76?silent=true)), and welcomed a new community story in the “What’s the story?” thread ([post 3](https://meta.discourse.org/t/-/409282/3?silent=true)). - **@David** – Fixed the deployment banner issue and explained the internal context (see [post 4](https://meta.discourse.org/t/-/409333/4?silent=true)? and [post 6](https://meta.discourse.org/t/-/409333/6?silent=true)). - **@Falco** – Clarified how to check AI agent model usage and added a [PR](https://github.com/discourse/discourse/pull/42326) to improve that UI (see [post 6](https://meta.discourse.org/t/-/409274/6?silent=true)). He also updated the Resenha plugin making slugs editable ([see post](https://meta.discourse.org/t/-/389056/82?silent=true)). - **@Tgxworld** – Acknowledged the deployment banner report and noted it was fixed (see [post 2](https://meta.discourse.org/t/-/409333/2?silent=true)). - **@Rishabh** – Confirmed the Discourse ID workaround and promised clearer UI for it (see [post 20](https://meta.discourse.org/t/-/409028/20?silent=true)). - **@Mcwumbly** – Actively participated in the “Improving the update Discourse page” and “Regular mode” discussions, sharing design perspectives (see [post 41](https://meta.discourse.org/t/-/211617/41?silent=true)). - **@Jordan.Vidrine** – Noted upcoming design modernizations for modals and select‑kits, promising a fix for the tag selector on mobile (see [post 6](https://meta.discourse.org/t/-/400390/6?silent=true)). - **@Martin** – Explained the unified new view behavior and internal discussion on preferences (see [post 39](https://meta.discourse.org/t/-/404728/39?silent=true)). * * * > _Yesterday’s biggest mystery turned out to be a domain that didn’t exist — proof that even the most frustrating SSL errors can be just a registrar away from sanity!_ ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月6日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/946 "2026-08-06T21:01:40Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… What a whirlwind 24 hours on Meta! The Discourse community has been buzzing with activity, from major designer test programs to deep philosophical debates about the future of the internet. Here’s your comprehensive digest: * * * ## Key Stats The past 24 hours saw **192 new posts** across **62 topics** , generating **348 likes** from the community. This represents a healthy mix of product feedback, support troubleshooting, and community discussions. **Top contributors by likes:** - @Chapoi led the pack with **28 likes** across 16 posts, heavily involved in the new [composer redesign testing](https://meta.discourse.org/t/-/407849?silent=true) - @Moin earned **26 likes** in 12 posts - @Lilly followed closely with **22 likes** across 10 posts - @Pfaffman contributed **15 likes** in 8 posts - @Canapin rounded out the top five with **14 likes** in 4 posts, including [sharp UX observations](https://meta.discourse.org/t/-/407849/16?silent=true) Other prolific contributors included @Don (14 likes, 3 posts), @Satonotdead (13 likes, 12 posts), @Merefield (13 likes, 5 posts), @NateDhaliwal (10 likes, 9 posts), and @Mcwumbly (10 likes, 3 posts). * * * ## Interesting Topics ### #Announcements - @Chapoi announced the [experimental composer redesign](https://meta.discourse.org/t/-/407849/1?silent=true), which moves the toolbar to the bottom, integrates the title into the editor, and massively improves mobile composing with an expanding editor. The feedback has been passionate — @Satonotdead compared adapting to the change to when “I was one of the folks who DIDN’T want a touchscreen on my cell phone” while @Don noted it solves the long-standing problem where the [context menu covers the editor button bar on mobile](https://meta.discourse.org/t/-/251059?silent=true). @Shauny raised concerns about muscle memory and accidental posts, but @Canapin pushed back, saying the bottom toolbar “makes much more sense on mobile. Way easier to reach it” ([read more](https://meta.discourse.org/t/-/407849/21?silent=true)). - The [PostgreSQL 18 update](https://meta.discourse.org/t/-/406194/38?silent=true) continues to generate discussion. @Pfaffman shared his manual multi-database migration approach, while @Supermathie offered guidance on Google Cloud SQL upgrades. @Lilly posted a [detailed step-by-step walkthrough](https://meta.discourse.org/t/-/406194/43?silent=true) for dual-container setups behind Cloudflare, including disk cleanup commands, scheduled maintenance page strategies via Cloudflare workers, and the proper rebuild order. @Tobias_1 shared a fix for the “cluster is owned by group id 993” error that plagues some upgrades ([read more](https://meta.discourse.org/t/-/406194/45?silent=true)). - @Sam revived the long-running discussion on [admin “regular mode”](https://meta.discourse.org/t/-/211617/39?silent=true) (a sudo-like feature), suggesting that “maybe by default admins are just like any other user, except that they have a special page where they click a button to get temporary admin permissions.” @Mcwumbly strongly agreed, proposing a toggle in the header with state clearly indicated. @Lilly pushed back, saying she’d prefer an admin setting so she doesn’t have to “toggle into admin mode to get to /admin,” and @Moin drew parallels to the existing `suppress_secured_categories_from_admin` setting ([read more](https://meta.discourse.org/t/-/211617/43?silent=true)). ### #Self-hosting - A truly epic saga unfolded in the Spanish-language topic [“Ya estoy cansado, he instalado discourse en varios VPS ninguno me funcionan”](https://meta.discourse.org/t/-/409294/22?silent=true) (“I’m already tired, I’ve installed Discourse on several VPS and none of them work”). After extensive troubleshooting involving @Jdc20181's Cloudflare insights, it turned out the domain `debatehosting.co` **didn’t exist at all** — @Supermathie demonstrated this with a whois query showing “DOMAIN NOT FOUND.” @Merefield noted the OP cancelled the domain during troubleshooting, which made it look like SSL issues. @Satonotdead explained the real culprit: repeated attempts to get certificates hit Let’s Encrypt rate limits, which is “not the same as ‘SSL blocked my domain’” ([read more](https://meta.discourse.org/t/-/409294/39?silent=true)). - In a thoughtful discussion about [password reset security](https://meta.discourse.org/t/-/409201/11?silent=true), @Roke_Julian_Lockhart described being locked out when OpenAI disconnected their SSO integration, replacing it with an unfamiliar email alias. The thread sparked a genuinely moving exchange where @Pfaffman publicly apologized: “I was a jerk and I humbly repent.” @Pfaffman went on to acknowledge that “it’s not that uncommon for users in a long lasting community to no longer remember their email address” and questioned the logic of `hide_email_address_taken` requiring the email field, since “resetting the password with the username does not expose an email address” ([read more](https://meta.discourse.org/t/-/409201/17?silent=true)). This led @Roke_Julian_Lockhart to file a [feature request for username-based password resets](https://meta.discourse.org/t/-/409326/1?silent=true). - @Picho_Pelis returned with a [SMTP configuration question](https://meta.discourse.org/t/-/409418/1?silent=true) after the domain debacle, getting a prompt “try port 2525, port 587 is likely blocked” from @Pfaffman, plus a security reminder from @NateDhaliwal to censor credentials in public posts. ### #Support - @Karthik_K1 reported that [Discourse ID displays its own logo and name](https://meta.discourse.org/t/-/409028/6?silent=true) instead of the forum’s branding. @Moin correctly pointed out the difference between this reported bug and the existing feature request. After @Chapoi initially dismissed it as standard OAuth behavior (“I was most likely wrong”), a workaround emerged — clearing the `discourse_id_client_id` and `discourse_id_client_secret` in the Rails console and toggling the login, which worked for @Karthik_K1. @Rishabh from the Discourse ID team confirmed this is being looked at and noted there’s a button on the admin settings page to regenerate credentials ([read more](https://meta.discourse.org/t/-/409028/20?silent=true)). - @Karthik_K1 also asked about [adding Indian languages like Hindi, Telugu, and Tamil](https://meta.discourse.org/t/-/409353/1?silent=true) to the language selector for AI translations. @Nat clarified that the selector controls the entire site locale, not just AI post translations, and pointed to plugin options for registering additional locales. @Moin suggested the plugin approach as a short-term solution while contributing interface translations via Crowdin for the long term ([read more](https://meta.discourse.org/t/-/409353/5?silent=true)). - @Stephtara wondered why [mentioning a group didn’t notify its members](https://meta.discourse.org/t/-/409389/1?silent=true). @Lilly tested it and confirmed it should work, while @Moin and @Lilly suggested the likely culprit: if the topic is in a private category the group doesn’t have access to, they won’t receive notifications. A [helpful guide on configuring group notifications for private categories](https://meta.discourse.org/t/-/96424?silent=true) was shared ([read more](https://meta.discourse.org/t/-/409389/6?silent=true)). ### #Feature - A [feature request for multiple profiles per user](https://meta.discourse.org/t/-/409329/1?silent=true) (inspired by Discord’s PluralKit system) gained traction. @A_Lilian made a compelling case: “Autonomy and expressiveness through online profiles matter. They give us the smallest window to the people past our screens and as such, are one of the primary pillars for building a humane web.” @Satonotdead noted how the technical challenge lies in the fact that Discourse Chat “is built entirely into static user profiles” ([read more](https://meta.discourse.org/t/-/409329/4?silent=true)). ### #Site feedback - @Lilly spotted an [error banner on Meta](https://meta.discourse.org/t/-/409333/1?silent=true) reading “MERGE\_BRANCH deployment failed.” @Tgxworld confirmed it was fixed, then @NateDhaliwal noted it persisted, and @David explained the root cause: a hosting system for deploying git branches was throwing a merge conflict error that “wasn’t supposed to be displayed to everyone.” It’s now fixed for real ([read more](https://meta.discourse.org/t/-/409333/4?silent=true)). ### #Community Building - @Mcwumbly kicked off a fascinating [discussion about the next decade of the internet](https://meta.discourse.org/t/-/409454/1?silent=true), reflecting on Discourse’s original 2013 promise. @Awesomerobot delivered a brilliant response arguing that “I expect to be talking to people in 2036 the same way I was talking to people in 2013: typing words into boxes” and warned about AI chatbots seeking to “shortcut the web entirely,” while affirming Discourse can be “a safe harbor where you’re not subject to the massive unknowable algorithms.” @Ed_S added concerns about increasing legal regulations (like the UK’s Online Safety Act) making it harder to run independent platforms, and @Satonotdead outlined two possible futures — a hub format with deeper integrations, or a hardened, cypherpunk-esque decentralized platform ([read more](https://meta.discourse.org/t/-/409454/5?silent=true)). ### #ux - @Canapin reported that the [Discourse meta icon is missing on the Discourse ID login page](https://meta.discourse.org/t/-/409441/1?silent=true), showing a broken image URL. @Jordan.Vidrine took a look and identified a deeper issue where Discourse only re-sends icon URLs when site settings change; if the stored URL becomes invalid, it breaks. The fix will only show the logo if it loads properly, otherwise just the forum name ([read more](https://meta.discourse.org/t/-/409441/2?silent=true)). - @Canapin also flagged that the [Meta branded theme lacks margins on single group pages](https://meta.discourse.org/t/-/409450/1?silent=true), with @Manuel confirming they’d investigate whether a body class is missing. ### #development - @Don unveiled a [native Glimmer implementation of a Facebook-style topic modal](https://meta.discourse.org/t/-/408565/21?silent=true), avoiding iframes entirely. He detailed how the modal reuses Discourse’s own `Post` components with a patched `postStream`, handles direct links and internal routing without escaping the modal, implements infinite scroll via IntersectionObserver, and even adds a skeleton loading state. @Damian_Boon reacted enthusiastically: “I’d love to test your version ❤” ### #Theme component - @Scavin released [Clean Share URL](https://meta.discourse.org/t/-/409352/1?silent=true), a theme component that adds a per-user preference to strip usernames from shared links (`?u=username`), addressing privacy concerns for users who don’t want their username attribution in shares. The component supports an optional custom user field for confirmation ([read more](https://meta.discourse.org/t/-/409352/1?silent=true)). ### #bug - 25-year-tech-explainer @Lilly contributed to the [“flags or something else increase the number of reactions” bug](https://meta.discourse.org/t/-/375520/2?silent=true) — confirming it was fixed in PR [#36138](https://github.com/discourse/discourse/pull/36138). The topic received a #fixed tag. * * * ## Activity by the @Team Group Our hardworking @Team members have been extremely active across many fronts: - **@Chapoi** delivered the biggest announcement of the day with the [experimental composer redesign](https://meta.discourse.org/t/-/407849/1?silent=true), spent considerable time [answering feedback on mobile behavior](https://meta.discourse.org/t/-/407849/7?silent=true), [fixing accidental design bugs](https://meta.discourse.org/t/-/407849/12?silent=true), and helping users work around the [Discourse ID logo issue](https://meta.discourse.org/t/-/409028/14?silent=true). He also checked in on a [custom HTML question](https://meta.discourse.org/t/-/231067/203?silent=true) in the Right Sidebar Blocks component and followed up on [an API tags issue](https://meta.discourse.org/t/-/407095/5?silent=true). - **@Sam** weighed in on the [admin “regular mode” feature proposal](https://meta.discourse.org/t/-/211617/39?silent=true), suggesting an inverted approach where admins default to regular user status. He also personally investigated the [AI structured output JSON error](https://meta.discourse.org/t/-/408821/5?silent=true), recommending a more capable model for spam detection and issued [a quick fix](https://meta.discourse.org/t/-/408821/9?silent=true) via [PR #42339](https://github.com/discourse/discourse/pull/42339). - **@David** fixed the [Meta error banner display bug](https://meta.discourse.org/t/-/409333/4?silent=true) and explained the internal hosting deployment system that caused it. - **@Tgxworld** confirmed and fixed the initial [deployment banner issue](https://meta.discourse.org/t/-/409333/2?silent=true). - **@Martin** responded to feedback on the [granular group-based permissions](https://meta.discourse.org/t/-/402273/29?silent=true) upcoming change, showing how CSS classes work and approving @Lilly's PR to update the [groups CSS classes theme component](https://github.com/discourse/discourse-groups-css-classes-in-body/pull/37). He also [merged several official component PRs](https://meta.discourse.org/t/-/402273/33?silent=true) to support the new permissions system and provided an update on the [unified new view](https://meta.discourse.org/t/-/404728/48?silent=true), stating a user preference for splitting counts is “not in our plans at this time.” - **@Nat** clarified the [language selector limitations](https://meta.discourse.org/t/-/409353/2?silent=true) around AI translations, linked resources for [adding new locales](https://meta.discourse.org/t/-/409353/6?silent=true), confirmed a [fix for auto-updating translated category descriptions](https://meta.discourse.org/t/-/399587/4?silent=true) via [PR #42407](https://github.com/discourse/discourse/pull/42407), and helped diagnose a [private category translation issue](https://meta.discourse.org/t/-/407914/8?silent=true) with a [data explorer](https://meta.discourse.org/t/32566?silent=true) query. - **@J.Jaffeux** pushed a commit to address [bug fixes in Discourse Workflows](https://meta.discourse.org/t/-/407100/15?silent=true) based on community feedback. - **@Jordan.Vidrine** investigated and fixed the [missing Discourse icon on the Discourse ID login page](https://meta.discourse.org/t/-/409441/2?silent=true), and responded to UX feedback about [closing the mobile tag selector](https://meta.discourse.org/t/-/400390/6?silent=true), noting a bottom-sheet redesign is in progress. - **@Awesomerobot** contributed a thoughtful and widely-praised post on the [future of the internet discussion](https://meta.discourse.org/t/-/409454/3?silent=true), and addressed a [Patreon dashboard advice issue](https://meta.discourse.org/t/-/389807/5?silent=true). - **@Mcwumbly** started the [provocative “next decade of the internet” topic](https://meta.discourse.org/t/-/409454/1?silent=true), shared thoughts on the [admin “regular mode” proposal](https://meta.discourse.org/t/-/211617/41?silent=true), and explored the idea that admins should have “more explicit signaling” when acting outside normal user workflows. - **@Ted** investigated the [Patreon dashboard notice persistence issue](https://meta.discourse.org/t/-/389807/5?silent=true), noting the refresh button is “a bit redundant.” - **@Rishabh** provided authoritative clarification on the [Discourse ID registration process](https://meta.discourse.org/t/-/409028/20?silent=true), noting the admin button to regenerate credentials and explaining how hosting handles it automatically. - **@Tobiaseigen** flagged a broken documentation link in the [Custom Wizard plugin](https://meta.discourse.org/t/-/73345/969?silent=true), directing to the correct pavilion.tech docs URL. - **@Manuel** acknowledged the [Meta theme margin issue on group pages](https://meta.discourse.org/t/-/409450/3?silent=true) and promised to investigate a missing body class. - **@Dax** confirmed agreement on the [profile spam review queue feature](https://meta.discourse.org/t/-/257972/21?silent=true), noting the topic will be updated once the feature is implemented in the review queue. - **@Tannerabread** fixed the [bulk message archiving refresh bug](https://meta.discourse.org/t/-/379082/6?silent=true) via [PR #42379](https://github.com/discourse/discourse/pull/42379) and resolved the [wrong join date in reviewable insights](https://meta.discourse.org/t/-/391232/10?silent=true) via [PR #42145](https://github.com/discourse/discourse/pull/42145). - **@Lilly** documented [setting up Gemini API keys on Google Cloud service accounts](https://meta.discourse.org/t/-/320688/3?silent=true) with a helpful disco-docs link, and contributed a thorough [PostgreSQL 18 upgrade walkthrough](https://meta.discourse.org/t/-/406194/43?silent=true) for dual-container Cloudflare setups. - **@Renato** confirmed a [composer HTML pasting fix](https://meta.discourse.org/t/-/407661/11?silent=true) was merged via [PR #42163](https://github.com/discourse/discourse/pull/42163). - **@PortChange** shared that the [email reply trimmer fixes](https://meta.discourse.org/t/-/144802/9?silent=true) were merged, noting the fix lives in [email\_reply\_trimmer PR #25](https://github.com/discourse/email_reply_trimmer/pull/25) — closing a 9-year-old topic! @Merefield appropriately quipped “9 years later… wow” ([read more](https://meta.discourse.org/t/-/70767/5?silent=true)). - **@Supermathie** provided authoritative answers on [PostgreSQL 18 for Google Cloud SQL](https://meta.discourse.org/t/-/406194/42?silent=true), proved the now-infamous domain [debatehosting.co didn’t exist](https://meta.discourse.org/t/-/409294/31?silent=true), and shared his own experience with the [standard data container migration](https://meta.discourse.org/t/-/406194/38?silent=true). - **@Davidb** merged a fix for the [Gmail dot-variant email validation](https://meta.discourse.org/t/-/404042/4?silent=true) so the UI now shows a clear explanation instead of a raw error. - **@NateDhaliwal** announced new features in the [TL3 progress plugin beta](https://meta.discourse.org/t/-/408543/28?silent=true), showing the lowest stat when a user exceeds TL3 and working out queries for muted categories. * * * And in a day where @Pfaffman publicly repented, @Satonotdead mused on her pre-touchscreen cell phone days, and we learned that a missing domain name caused infinite Spanish-language pain… never forget: **if your Discourse won’t install, make sure the domain you’re pointing at actually exists first** — SSL can’t negotiate with a domain that isn’t there! 🏠💨 ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月7日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/947 "2026-08-07T21:01:36Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **Total new posts:** 194 - **Total new topics:** 75 - **Top users (posts + likes):** - @Awesomerobot (10 posts, 30 likes) - @Moin (11 posts, 25 likes) - @Satonotdead (9 posts, 24 likes) - @Chapoi (9 posts, 22 likes) - @Canapin (7 posts, 21 likes) - @Don (5 posts, 20 likes) - @Lilly (6 posts, 15 likes) - @NateDhaliwal (8 posts, 14 likes) - @Pfaffman (5 posts, 14 likes) - @Mostapha (3 posts, 14 likes) * * * ## Interesting Topics ### #Announcements - 🧪 **Help Us Test the Composer Redesign** – @Chapoi unveiled an experimental [composer redesign](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/1?silent=true) featuring a relocated toolbar, a more document-like title, and an expanding editor for mobile. The community quickly weighed in: @Darkpixlz questioned the new title placement, @Don loved the bottom toolbar, @Canapin noted a missing rounded border on the selector, and @Heliosurge couldn’t get the group-based rollout to work initially (later resolved). The topic drew 80+ likes and ongoing testing feedback from mobile users. [Read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/1?silent=true) - 🗄 **PostgreSQL 18 update for self-hosters** – @Supermathie and @Lilly shared detailed upgrade instructions for dual‑container setups, while @Pfaffman clarified disk space requirements and @Tobias_1 provided a fix for a group ownership error during the upgrade. The thread is a goldmine for anyone running self‑hosted installations. [See the full guide](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/1?silent=true) - 🔑 **Easier account signup using email codes** – @Thomas_Rother praised the new one‑time code feature, highlighting its low‑friction MFA benefits. This is part of a broader push to modernise authentication. [Join the discussion](https://meta.discourse.org/t/easier-account-signup-using-email-codes/407068/1?silent=true) - 🤖 **Introducing a docked composer for AI bot conversations** – @Keegan and @Martin explained how to enable the new chat‑style composer for AI bots via user preferences, with @Moin confirming the location under “Fonts & Appearance”. The feature is now available on [ask.discourse.com](http://ask.discourse.com). [Learn more about the docked composer](https://meta.discourse.org/t/introducing-a-docked-composer-for-ai-bot-conversations/403327/1?silent=true) - 👥 **Granular group‑based permissions for anonymous and logged‑in users** – @Martin updated official components to use `resolve_group_membership` and shared a [list of merged PRs](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/33?silent=true). @Lilly also contributed a PR to add the `anonymous_users` and `logged_in_users` CSS classes to a community component. This feature is steadily evolving. [Track the changes](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/1?silent=true) ### #Community Building - 🌍 **For the next decade of the internet (2026 edition)** – @Mcwumbly kicked off a reflective thread asking what Discourse should look like by 2036. @Awesomerobot delivered a memorable reply predicting “typing words into boxes” remains the norm, while @Satonotdead and @Ed_S discussed decentralisation and the importance of safe spaces. A thought‑provoking read. [Join the conversation](https://meta.discourse.org/t/for-the-next-decade-of-the-internet-2026-edition/409454/1?silent=true) ### #development - 🎨 **Facebook‑style Topic Modal – Is it better?** – @Don shared a theme component that opens topics in a modal, and demoed it [on Theme Creator](https://discourse.theme-creator.io/theme/Don/topic-modal). The community loved the speed and feel, but @Awesomerobot warned about rate‑limiting due to prefetching. @Don responded by adding a `max_prefetches_per_minute` safety net. [Try the modal](https://meta.discourse.org/t/facebook-style-topic-modal-is-it-better/408565/1?silent=true) ### #Feature - 📚 **Redirect the landing page for each subcategory to index file by default for documentation categories** – @Mostapha requested that doc categories default to the index page rather than a topic list. He later [acknowledged an existing request](https://meta.discourse.org/t/what-should-the-homepage-be-for-doc-categories/398616?silent=true) and wanted to close his own topic, but @Merefield suggested keeping it open as a separate tracking item. [See the feature request](https://meta.discourse.org/t/redirect-the-landing-page-for-each-subcategory-to-index-file-by-default-for-documentation-categories/409470/1?silent=true) - 💬 **More direct access to topics with new replies** – @Martin explained that a user preference to split “new” and “unread” isn’t planned, but he offered to add plugin APIs for theme developers. @Shauny and @Frederic_Bertrand pushed back, and @Awesomerobot proposed alternative default settings. @Lindsey moved the feedback to a separate feature topic for continued input. [Share your thoughts](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/1?silent=true) - 🔑 **Always allow username‑based password reset** – @Pfaffman argued that requiring an email address for password reset is a regression, especially for long‑time users who forget their sign‑up email. @Awesomerobot linked the change to a [GitHub PR](https://github.com/discourse/discourse/pull/15362) and questioned whether the hardening rationale still holds. The discussion also covers abuse prevention and rate limiting. [Vote on the feature](https://meta.discourse.org/t/always-allow-username-based-password-reset/409326/1?silent=true) - 🎮 **Automating gamification points** – @Satonotdead is exploring using Workflows and AI to award gamification points automatically. @Awesomerobot suggested adding an “award cheers” action to the Workflows plugin, and @Falco pointed to a [related PR](https://github.com/discourse/discourse/pull/42447). This could become a powerful engagement tool. [Discuss gamification automation](https://meta.discourse.org/t/automating-gamification-points/409452/1?silent=true) ### #Support - 📊 **Looking for storage details after Discourse update** – @M_Terenui praised the new admin dashboard but noted the missing backup and free space stats. @Moin linked to related discussions about the old dashboard’s removals, and @Awesomerobot provided a temporary workaround via the `storage_stats.json` endpoint. [Find the solution](https://meta.discourse.org/t/looking-for-storage-details-after-discourse-update/409553/1?silent=true) - 🌐 **Setting translation to one language only** – @Marzena_Cudecka wanted to limit content translation to German, but the UI allowed all languages. @Nat and @Moin explained that interface languages are user‑controllable, and @Nat noted an existing [feature request](https://meta.discourse.org/t/allow-only-specific-languages/290434?silent=true) for restricting languages. The team is also thinking about synergies with content localization. [Explore the thread](https://meta.discourse.org/t/setting-translation-to-one-language-only/409504/1?silent=true) ### #ux - 🐛 **Discourse meta icon missing on Discourse ID login page** – @Canapin spotted a broken logo on the Discourse ID login page. @Jordan.Vidrine investigated and found a caching issue where the logo isn’t re‑sent on changes; he implemented a fix that hides the broken image and shows the name only. [Read the fix details](https://meta.discourse.org/t/discourse-meta-icon-missing-on-discourse-id-login-page/409441/1?silent=true) - 🎨 **The meta branded theme lacks margins on single group pages** – @Canapin noticed the [composer‑testers group page](https://meta.discourse.org/g/composer-testers) has no margins, and @Manuel confirmed it’s a likely missing body class. A quick but appreciated UX polish request. [Report the margin issue](https://meta.discourse.org/t/the-meta-branded-theme-lacks-margins-on-single-group-pages/409450/1?silent=true) * * * ## Activity by the @Team Group The @Team group has been busy across many topics. Here’s a snapshot of their contributions in the last 24 hours: - @Chapoi spearheaded the [Composer Redesign test](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/1?silent=true), responding to feedback on the toolbar placement, mobile behaviour, and tag icons. He also fixed a missing category icon colour and continued iterating on the design. - @Martin provided updates on the [granular permissions](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/1?silent=true) feature, merging multiple PRs for official components, and clarified policy on the “new/unread” split in [this thread](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/10?silent=true). He also discussed options for the [docked composer](https://meta.discourse.org/t/introducing-a-docked-composer-for-ai-bot-conversations/403327/25?silent=true) and offered plugin API support. - @Awesomerobot contributed to several discussions: he suggested a better “award points” action for [gamification automation](https://meta.discourse.org/t/automating-gamification-points/409452/2?silent=true), explained the rationale behind the [password reset change](https://meta.discourse.org/t/always-allow-username-based-password-reset/409326/6?silent=true), and recommended a workaround for the [missing storage stats](https://meta.discourse.org/t/looking-for-storage-details-after-discourse-update/409553/3?silent=true). He also fixed the “Me too” visibility on category description topics via [PR #42444](https://github.com/discourse/discourse/pull/42444). - @Jordan.Vidrine addressed the [Discourse ID logo bug](https://meta.discourse.org/t/discourse-meta-icon-missing-on-discourse-id-login-page/409441/2?silent=true) and updated the [Foundation theme thread](https://meta.discourse.org/t/modernizing-the-foundation-theme/395331/117?silent=true) with gratitude for community feedback. - @Nat handled translation‑related queries, linking to a [localization PR](https://github.com/discourse/discourse/pull/42407), and clarified settings in [this support topic](https://meta.discourse.org/t/setting-translation-to-one-language-only/409504/2?silent=true). They also updated [content localization documentation](https://meta.discourse.org/t/content-localization-manual-and-automatic-with-discourse-ai/370969/66?silent=true). - @Davidb fixed a scroll‑position regression for `/u/:username/activity` and improved the error message for Gmail alias handling in [this bug thread](https://meta.discourse.org/t/validation-failed-primary-email-has-already-been-taken-when-trying-to-handle-gmail-dot-variants-or-add-secondary-emails/404042/4?silent=true). - @Keegan explained how to enable the chat‑style composer for AI bots in [the docked composer topic](https://meta.discourse.org/t/introducing-a-docked-composer-for-ai-bot-conversations/403327/23?silent=true), and @J.Jaffeux addressed workflow feature requests in [Discourse Workflows](https://meta.discourse.org/t/discourse-workflows/407100/15?silent=true). - @Lindsey moved the “new/unread” feedback to a dedicated feature topic and acknowledged the Zendesk API migration in [this thread](https://meta.discourse.org/t/zendesk-api-tokens-will-be-permanently-deactivated-on-april-30-2027/409411/6?silent=true). - @Manuel confirmed the group page margin issue on Meta and flagged the deprecated Category List Banners component as [deprecated](https://meta.discourse.org/t/category-list-with-banners/201280/23?silent=true). - @System posted the monthly [Discourse Discover](https://meta.discourse.org/t/discourse-discover-building-in-the-physical-world/409404/1?silent=true) blog roundup. * * * _And with 194 posts, 75 topics, and a slew of PRs being merged, it seems the puppies are not the only ones wagging their tails today – the composer redesign has everyone’s fingers wagging on their keyboards! 🐾_ ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月8日 21:00 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/948 "2026-08-08T21:00:53Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats Over the past 24 hours, **[meta.discourse.org](http://meta.discourse.org)** saw **135 new posts** across **60 new topics** , with **210 likes** given. The community was buzzing with activity, from theme component updates to deep dives into new features like the Composer Redesign and AI bot integrations. **Top contributors** this week: - @Moin — 9 posts, 28 likes - @Awesomerobot — 8 posts, 20 likes - @RGJ — 8 posts, 15 likes - @Don — 4 posts, 12 likes - @Heliosurge — 7 posts, 8 likes - @Sk-Or-V1-Contents — 5 posts, 8 likes - @Nat — 3 posts, 8 likes - @NateDhaliwal — 5 posts, 7 likes - @Merefield — 4 posts, 7 likes - @Arkshine — 2 posts, 7 likes * * * ## Interesting Topics ### #development - **Facebook-style Topic Modal** — A lively thread where @Don showcased his [new theme component](https://meta.discourse.org/t/-/408565/23?silent=true) that opens topics in a slick modal instead of a full page. Multiple users praised its speed, while @Awesomerobot noted network request rate limits on standard layouts. @Don responded by adding settings for `max_prefetches_per_minute` and a “button” trigger style to tailor the component for custom themes, promising an open-source release after broader testing [read more](https://meta.discourse.org/t/-/408565/29?silent=true). - **Automating gamification points** — @Awesomerobot suggested an “award cheers” action for the Workflows plugin, which @Falco quickly implemented in [this PR](https://github.com/discourse/discourse/pull/42447). Discussion also touched on using [custom forms](https://meta.discourse.org/t/-/409452/4?silent=true) or the Custom Wizard plugin to automate rewards, though some users prefer staying within core Discourse tools [read more](https://meta.discourse.org/t/-/409452/5?silent=true). ### #Praise - **Contributor appreciation August (& Feb) 2026** — @Moin compiled two heartfelt threads thanking [all code contributors and translators](https://meta.discourse.org/t/-/409592/1?silent=true) over the past 6 months, including a special mention for the ES-release period. Community members voiced their gratitude, with @HAWK simply replying “Thank you @Moin, appreciated” [read more](https://meta.discourse.org/t/-/409592/3?silent=true). ### #Announcements - **Help Us Test the Composer Redesign** — Testers shared feedback on mobile: @Heliosurge reported settings not applying initially (later resolved), @NateDhaliwal found tag buttons getting cut off with long category names, and @Sk-Or-V1-Contents pushed for a preview button on mobile, linking to a [related proposal](https://meta.discourse.org/t/-/407849/29?silent=true). The team acknowledged the feedback and promised further refinement [read more](https://meta.discourse.org/t/-/407849/22?silent=true). ### #Support - **Looking for storage details after Discourse update** — @M_Terenui praised the new admin dashboard but missed seeing backup space and free disk usage. @Moin pointed to [relevant topics](https://meta.discourse.org/t/-/409553/2?silent=true) about the redesign, and @Awesomerobot provided a workaround using the `/admin/reports/storage_stats.json` endpoint until the data is re-added to the UI [read more](https://meta.discourse.org/t/-/409553/3?silent=true). - **Setting translation to one language only** — @Marzena_Cudecka wanted to limit content translation to just German, but found users could pick any language. @Nat explained that interface language and content language are separate, while @Moin shared a [feature request](https://meta.discourse.org/t/-/409504/4?silent=true) to restrict allowed interface languages. The team is reviewing the request [read more](https://meta.discourse.org/t/-/409504/5?silent=true). - **Is there any built-in chatbot or conversational assistant?** — @Soumya_Ranjan_Mishra asked about chatbots beyond Discobot. @RGJ mentioned the Discourse AI bot and @Merefield's [Chatbot plugin](https://meta.discourse.org/t/-/409513/2?silent=true), while @Awesomerobot highlighted that Discourse AI includes features like auto-categorize and auto-tagging, and can power a dedicated AI conversation page [read more](https://meta.discourse.org/t/-/409513/5?silent=true). ### #Feature - **More direct access to topics with new replies** — The community debated the recent “New” vs “Unread” change. @Lindsey stated there are no immediate plans to revert, but moved the discussion to a feature request category for iterative improvement. @Awesomerobot explained the design rationale and asked if adding a “never” tracking option or a default for “replies” would help. @Seanblue provided detailed feedback about wanting both options visible [read more](https://meta.discourse.org/t/-/409522/19?silent=true). ### #ux - **“Vote returned” notification in case of unlimited votes** — @Moin reported that closing a topic sends a “vote returned” notification even when vote limits are disabled. @Awesomerobot agreed it doesn’t make sense and submitted a fix in [PR #42448](https://github.com/discourse/discourse/pull/42448), while noting additional nuances with the plugin’s vote limiting [read more](https://meta.discourse.org/t/-/409518/2?silent=true). - **Should ‘Mee too’ be hidden on category descriptions topics?** — @Satonotdead asked if the “Me too” reaction should be hidden on category description topics that serve as indexes. @Awesomerobot agreed and created a [PR to exclude them](https://github.com/discourse/discourse/pull/42444), thanking the report [read more](https://meta.discourse.org/t/-/409537/2?silent=true). ### #Theme component - **Alternative User PMs Button For Admin** — @Heliosurge reported a JS error after updating Discourse, and @Arkshine fixed it within hours. The rapid turnaround earned praise from the community [read more](https://meta.discourse.org/t/-/260952/4?silent=true). - **Quote Callouts** — A similar update issue surfaced for this component; @祁同伟 forked the repo to fix it, and @Arkshine pushed an official fix shortly after [read more](https://meta.discourse.org/t/-/350962/80?silent=true). - **Topic List Previews (TLP)** — @Eviepayne reported a critical bug where avatar uploads failed (`no implicit conversion of Hash into String`). @Merefield traced it to the TLP sidecar plugin and released a [fix via PR](https://github.com/merefield/discourse-topic-previews-sidecar-pro/pull/183), confirming the resolution [read more](https://meta.discourse.org/t/-/209973/765?silent=true). ### #Sysadmins - **MKJ’s Opinionated Discourse Deployment Configuration** — @Raykholo asked about using Garage instead of Minio, sparking a detailed write-up of their experience with Garage under a Cloudflare tunnel. @Mcdanlj confirmed the Garage works and corrected documentation on disabling transparent huge pages [read more](https://meta.discourse.org/t/-/193355/43?silent=true). The thread is a goldmine for self-hosters exploring S3-compatible storage [read more](https://meta.discourse.org/t/-/193355/46?silent=true). ### #Site feedback - **Uncategorized category?** — @NateDhaliwal noticed an unexpected “Uncategorized” category appeared on Meta. @Moin linked it to a [broader migration topic](https://meta.discourse.org/t/-/409501/2?silent=true), suggesting it might be part of a test or a recent change. Discussion continues [read more](https://meta.discourse.org/t/-/409501/1?silent=true). * * * ## Activity by the @Team Group The @Team group was highly active today, tackling bugs, responding to feedback, and shipping fixes: - @Awesomerobot was prolific: they engaged with the **Topic Modal** thread on rate limits, explained the “New” functionality in [More direct access](https://meta.discourse.org/t/-/409522/16?silent=true), suggested an “award cheers” action for Workflows plugins, fixed the **“Vote returned” notification** with a [PR](https://meta.discourse.org/t/-/409518/2?silent=true), hid “Mee too” on category descriptions via another [PR](https://meta.discourse.org/t/-/409537/2?silent=true), and advised on storage stats endpoint workarounds [read more](https://meta.discourse.org/t/-/409553/3?silent=true). - @Martin responded to testers in the **Composer Redesign** thread, confirming Meta uses a specific group setting and troubleshooting mobile issues [read more](https://meta.discourse.org/t/-/407849/25?silent=true). - @Nat clarified translation settings in [Setting translation to one language only](https://meta.discourse.org/t/-/409504/4?silent=true) and updated documentation links in the **Content Localization** topic [read more](https://meta.discourse.org/t/-/370969/66?silent=true). - @Lindsey addressed user concerns in [More direct access](https://meta.discourse.org/t/-/409522/14?silent=true), explaining lack of immediate changes and moving the discussion to a feature category, and also noted they’d review the Zendesk token impact [read more](https://meta.discourse.org/t/-/409411/6?silent=true). - @Falco implemented the workflow action for gamification points [in a PR](https://meta.discourse.org/t/-/409452/3?silent=true). - @Davidb fixed a bug where `/u/:username/activity` lost scroll position after navigating back, shared in [this commit](https://github.com/discourse/discourse/commit/b5961484c99bd554fa2532d0105da369d0f4b887) [read more](https://meta.discourse.org/t/-/406292/2?silent=true). - @Rishabh tested and discussed the **Discourse-ID logo/name** issue, noting that changes to site settings should automatically update the identity provider [read more](https://meta.discourse.org/t/-/409028/23?silent=true). - @Chapoi engaged in UX feedback threads, such as asking @Martin for thoughts on category permission logic [read more](https://meta.discourse.org/t/-/409508/2?silent=true). * * * > From Facebook-style modals to clever bug fixes, it was a day of innovation—who knew a topic modal could spark so much excitement? Come for the feature previews, stay for the lightning-fast maintenance! ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月9日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/949 "2026-08-09T21:01:46Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… Welcome to the daily wrap-up of activity on the Discourse Meta forum for the past 24 hours. It was a busy day full of plugin updates, core discussions, and helpful community contributions. Let’s jump into the stats, highlights, and team activity. * * * ## Key Stats - **Total new posts:** 64 - **Total new topics:** 32 - **Total likes received:** 89 **Top contributors by likes and posts:** | User | Posts | Likes | | --- | --- | --- | | @Moin | 5 | 34 | | @Merefield | 6 | 11 | | @RGJ | 2 | 7 | | @HAWK | 2 | 4 | | @Sk-Or-V1-Contents | 4 | 3 | | @NateDhaliwal | 3 | 3 | | @Eviepayne | 2 | 3 | | @Lilly | 2 | 3 | | @Weallwegot | 1 | 3 | | @DRRO | 4 | 2 | > 👏 A special shout-out to @Moin for not only posting the much‑appreciated _Contributor Appreciation_ thread but also earning the most reactions today. * * * ## Interesting Topics Here are some of the most engaging discussions from the past 24 hours, grouped by category. ### #Praise - **Contributor Appreciation August & February 2026** – @Moin launched this heartfelt thank-you to all the contributors and translators who helped improve Discourse over the past six months. The thread (with a bonus February segment) celebrates community PRs, translations, and Meta participation. [read more](https://meta.discourse.org/t/contributor-appreciation-august-feb-2026/409592/1?silent=true) ### #Feature - **Add support for ‘personal notes’ on posts** – @DRRO continued the discussion on personal notes, exploring bookmarks, PMs, and drafts as workarounds. @Awesomerobot suggested bookmarks as a natural fit, while @Lilly shared a simple PM trick. @Merefield then announced he is building a plugin and even got approval for a core PR. [read more](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/24?silent=true) - **More direct access to topics with new replies** – @Seanblue pushed back on the recent redesign of the “new” and “unread” filters, sharing that both communities he admins reverted the change. @NateDhaliwal proposed a simple `/unread` sidebar link as an alternative. [read more](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/19?silent=true) ### #Announcements - **Help Us Test the Composer Redesign** – @Sk-Or-V1-Contents provided feedback on mobile display, including a blue flash when expanding the editor and keyboard issues. @Chapoi acknowledged several quirks and is actively iterating on the design. [read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/29?silent=true) - **PostgreSQL 18 update for self‑hosters** – @NateDhaliwal asked for help with a dev environment connection error, while others shared tips on upgrading. The thread is a good place to track issues and solutions for the new PostgreSQL version. [read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/46?silent=true) ### #Support - **Admin‑Hinweise nach letztem Update** – @Viddekla reported two admin notices after an update, related to the `discourse-locations` plugin and a legacy theme API. @Moin explained how to identify and fix the plugin warnings. (This thread is in German.) [read more](https://meta.discourse.org/t/admin-hinweise-nach-letztem-update/409587/1?silent=true) - **How to skip override-overrided localizations** – @Satonotdead asked how to stop core updates from overwriting custom Spanish translations. Several users shared workarounds and pointed to the content‑localization plugin. [read more](https://meta.discourse.org/t/how-to-skip-override-overrided-localizations/409604/1?silent=true) ### #bug - **Bounce score does not reset when email address is changed** – @RGJ reported that bounce scores persist after a user updates their email to a correct address, which can wrongly flag good addresses. The expected behavior would be to reset the score on email change. [read more](https://meta.discourse.org/t/bounce-score-does-not-reset-when-email-address-is-changed/409581/1?silent=true) - **Monthly triggered recurring automation is not running as expected** – @Gassim followed up on a previously reported bug. @Moin pointed to a merged fix (#40747) and @Gassim is now testing the next month’s trigger. [read more](https://meta.discourse.org/t/monthly-triggered-recurring-automation-is-not-running-as-expected/402664/23?silent=true) - **FIX: Avoid traversing Redis keys when clearing 404 topic cache** – @Small-Lovely-Cat submitted a PR to fix a performance issue when clearing the page‑not‑found cache, which could cause 500 errors on large sites. [read more](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622/1?silent=true) ### #Plugin - **Locations Plugin** – @Jagster and @Viddekla both noted the admin notice about deprecated code. @Merefield announced that fixes have been merged, including contributions from @Cvx and @Angusmcleod, and the plugin now uses modern APIs. [read more](https://meta.discourse.org/t/locations-plugin/69742/1243?silent=true) - **Discourse Calendar and Events** – @Gassim asked detailed questions about Zoom webinar integration, permissions, and whether webhook triggers could be expanded to include event attendance actions. This is a great candidate for future core/plugin enhancements. [read more](https://meta.discourse.org/t/discourse-calendar-and-events/97376/610?silent=true) ### #Theme component - **Topic List Previews (TLP)** – @Eviepayne reported an avatar‑upload error caused by the TLP sidecar. @Merefield quickly identified a core compatibility issue and released a fix via a PR, which resolved the problem. [read more](https://meta.discourse.org/t/topic-list-previews-tlp/209973/761?silent=true) - **Clickable Social Icon Links on Profile** – @Weallwegot merged the long‑awaited Twitter → X change and offered to handle the next PR. @Roi reported two conflicts in the PR that need resolution. [read more](https://meta.discourse.org/t/clickable-social-icon-links-on-profile/158136/104?silent=true) - **Social Share** – @Patrickemin suggested adding the new European network “W Social” to the official component. This could be a simple PR for anyone interested in expanding share options. [read more](https://meta.discourse.org/t/social-share/89980/97?silent=true) ### #Self-hosting - **Fresh install/migrated!** – @ALinux shared a successful migration from phpBB and asked about performance. @Darkpixlz provided feedback on loading times, and @ALinux later added more CPU cores, which improved speed significantly. [read more](https://meta.discourse.org/t/fresh-install-migrated/409595/1?silent=true) - **Any cheaper alternatives to Hetzner?** – @Dopler and @Satonotdead compared Hetzner pricing with OVH and other providers, discussing CPU, RAM, and network trade‑offs. [read more](https://meta.discourse.org/t/any-cheaper-alternatives-to-hetzner/409037/24?silent=true) ### #development - **Facebook‑style Topic Modal** – @Damian_Boon asked if @Don’s modal component could be open‑sourced. @Don agreed to test it in production and added new settings for more flexible layouts. [read more](https://meta.discourse.org/t/facebook-style-topic-modal-is-it-better/408565/30?silent=true) - **Deprecating .hbs file extension in themes and plugins** – @Willy shared that they updated a plugin using Claude and agreed that consistency in the ecosystem is crucial. [read more](https://meta.discourse.org/t/deprecating-hbs-file-extension-in-themes-and-plugins/398896/21?silent=true) ### #Extras - **nodeBook: CNL knowledge graphs in posts** – @G_N introduced a new theme component that renders controlled natural language as interactive knowledge graphs, concept maps, and even Petri‑net simulations directly in posts. A fascinating addition for science and education. [read more](https://meta.discourse.org/t/nodebook-cnl-knowledge-graphs-in-posts-concept-maps-inference-petri-net-simulation/409634/1?silent=true) * * * ## Activity by the @Team Group The Discourse team was active on several fronts today, offering support, engaging with feedback, and driving forward core improvements. - @Moin posted the [Contributor Appreciation thread](https://meta.discourse.org/t/contributor-appreciation-august-feb-2026/409592/1?silent=true), thanking community contributors and translators, and later replied to @HAWK’s thank‑you in the same thread. - In the [personal notes feature discussion](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/25?silent=true), @Awesomerobot suggested that bookmarks could serve as a natural base for personal notes and asked what additional features would be needed. - @Chapoi engaged with testers of the [composer redesign](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/31?silent=true), acknowledging known issues on non‑Foundation themes and promising continued polish. - @Moin also helped a German‑speaking admin by explaining how to address plugin deprecation notices in the [Admin‑Hinweise thread](https://meta.discourse.org/t/admin-hinweise-nach-letztem-update/409587/2?silent=true). - @Moin chimed in on the [monthly automation bug](https://meta.discourse.org/t/monthly-triggered-recurring-automation-is-not-running-as-expected/402664/23?silent=true), pointing to a merged fix. - @Awesomerobot approved a plugin‑support PR for @Merefield’s personal notes plugin, showing ongoing collaboration between staff and developers. [Read more on the topic](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/32?silent=true) * * * _That’s a wrap on a day full of gratitude, bug hunting, and creative plugin ideas — let’s hope the only bounce we see tomorrow is in the number of new topics, not email bounce scores!_ 🎉 ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月10日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/950 "2026-08-10T21:01:15Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats Over the last 24 hours, the community has been incredibly active, with **116 new posts** distributed across **53 topics** and **143 likes** given. Here are the top contributors: | User | Posts | Likes Received | | --- | --- | --- | | @Merefield | 7 | 19 | | @Moin | 7 | 13 | | @Falco | 4 | 10 | | @Per1234 | 2 | 9 | | @Don | 2 | 8 | Other notable participants include @NateDhaliwal (5 posts, 7 likes), @Kcahtoor (6 posts, 5 likes), and @Chapoi (2 posts, 4 likes). The buzz centered around new plugin releases, bug fixes, and constructive feedback on recent UI changes. * * * ## Interesting Topics ### #Feature - **Personal Notes on Posts** – @DRRO proposed a system for private notes attached to posts. @Awesomerobot suggested bookmarks as a natural fit, and @Lilly offered a workaround using PMs. The discussion spurred @Merefield to develop the [Bookmark Notes](https://meta.discourse.org/t/bookmark-notes/409685?silent=true) plugin, which turns bookmarks into editable private notes. An initial PR was [approved](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/25?silent=true) and the feature is now moving forward. [Read more](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798?silent=true) - **Calendar & Events Webhook Triggers** – @Gassim requested webhook events for attendee actions (going, interested) and automations for post-event summaries. @Lindsey acknowledged the request and hinted that the new [Workflows feature](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990?silent=true) may absorb these needs. [Read more](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623?silent=true) - **List of Changed Settings in Releases** – @Gormus suggested adding a section to release notes and comparison views that lists changes to core and plugin settings, similar to the staff action log. This would help admins track configuration changes between versions. [Read more](https://meta.discourse.org/t/add-a-list-of-changed-core-and-plugin-settings-in-releases/409703?silent=true) ### #Announcements - **Help Us Test the Composer Redesign** – @Chapoi shared the redesigned composer for testing. Feedback rolled in: @Per1234 highlighted usability issues with the borderless design and missing right margin in preview, @Noble_Fish noted a border on Horizon, and @Jagster found that the toolbar disappears if hidden before switching to the new composer. @Chapoi is actively addressing these concerns. [Read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849?silent=true) - **PostgreSQL 18 Update for Self‑Hosters** – After @Kcahtoor reported a broken multisite upgrade, @Chrisr merged a fix ensuring all databases upgrade properly. Users were instructed to restore their data and rebuild. The topic also included a detailed workaround for those who had already lost data. [Read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194?silent=true) - **Branding the Discourse Splash Screen** – @Don shared optimization techniques for animated SVGs on the splash screen, recommending CSS animations on a wrapper `div` to achieve smooth performance on mobile. [Read more](https://meta.discourse.org/t/branding-the-discourse-splash-screen-with-custom-svg-images/395100?silent=true) ### #Plugin - **Bookmark Notes Plugin** – Published by @Merefield, this plugin transforms bookmarks into private personal notes with a Markdown editor, reminder preservation, and a post‑level button to reopen the note. A Pro extension adds collapsible panels and advanced search. @Jagster praised it as “something I didn’t know I need.” [Read more](https://meta.discourse.org/t/bookmark-notes/409685?silent=true) ### #Support - **Restricting an AI Agent to Forum‑Specific Questions** – @Karthik_K1 sought to stop their Discourse AI bot from answering off‑topic queries (e.g., “Who owns Uber?”). @Falco explained that the “Creative” agent has no system prompt, and recommended crafting a custom agent with a tailored prompt. @Ed_S pointed to [ask.discourse.com](http://ask.discourse.com) as a working example. [Read more](https://meta.discourse.org/t/how-can-i-restrict-an-ai-agent-to-answer-only-questions-related-to-my-forum/409672?silent=true) ### #Self-hosting - **Discourse ID Authentication Risks** – @Wsmwktb asked about the downsides of allowing login via Discourse ID. @Falco debunked common fears, noting that trust levels are not transferred, and clarified that Discourse ID simply aggregates social logins. @Merefield suggested rolling it out in stages. [Read more](https://meta.discourse.org/t/are-there-significant-downsides-or-problems-to-opening-my-self-hosted-discourse-to-participating-discourse-sites-accounts/409729?silent=true) - **“I Upgraded to Latest and Lost Everything”** – @Kcahtoor faced a catastrophic data loss after a multisite Postgres upgrade. After troubleshooting, @Chrisr provided a fix for the broken upgrade script and recovery steps. The issue highlighted the complexity of multi‑database upgrades. [Read more](https://meta.discourse.org/t/i-upgraded-to-latest-and-lost-everything/409647?silent=true) ### #Theme component - **Topic Preview Modal** – @Don released a theme component that lets users open topics in a native modal directly from the topic list, without losing their place. The modal supports full interaction (replies, bookmarks, reactions). @Damian_Boon provided a compatibility fix for the Reddit‑ish theme. [Read more](https://meta.discourse.org/t/topic-preview-modal/409712?silent=true) ### #ux - **Discrepancy in User Activity Display** – @Sterretje noticed that the `Topics` tab on user profiles doesn’t show excerpts, unlike `All` and `Replies`. @Moin explained the design rationale, and @Awesomerobot suggested a theme component using the existing Topic List Excerpts to add excerpts specifically to profile topic lists. [Read more](https://meta.discourse.org/t/discrepancy-in-display-of-user-activity-all-replies-vs-topic/409671?silent=true) - **“All Members” Category Permissions** – @RGJ reported that creating a category with “All members” assigns `everyone`, which is problematic. @Martin acknowledged the unintended side effect and agreed to improve the UI with three distinct buttons (public, members only, private). The discussion also touched on the new permission groups. [Read more](https://meta.discourse.org/t/all-members-when-creating-a-category-assigns-everyone/409508?silent=true) ### #Migration - **Accepted Solutions from Khoros** – @Gosia.Murawska asked if accepted‑solution markers could be mapped during import from Khoros. @Italo confirmed it’s possible if the plugin is active during the import, and offered guidance on custom import tooling. [Read more](https://meta.discourse.org/t/accepted-solutions-plugin-migrating-markers-from-khoros/409686?silent=true) ### #Data & reporting - **DSA Content Moderation Reporting** – @Jay‑C highlighted challenges complying with the EU’s DSA standardized reporting and Statements of Reasons, specifically needing custom suspension reasons and structured moderation data. @HAWK acknowledged the issue and is consulting with legal counsel. [Read more](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681?silent=true) * * * ## Activity by the @Team Group The Discourse team was heavily involved across multiple topics: - @Awesomerobot contributed to the **personal notes** discussion, suggesting bookmarks as a natural fit and later [approving a PR](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/25?silent=true) that enabled the plugin development. He also provided insight on showing excerpts in user activity and confirmed a gap in muted‑category topic visibility. [View topics](https://meta.discourse.org/t/how-do-i-access-topics-in-muted-categories/409676?silent=true) and [quote](https://meta.discourse.org/t/discrepancy-in-display-of-user-activity-all-replies-vs-topic/409671/6?silent=true). - @Chapoi is leading the **Composer Redesign** testing process, acknowledging issues with Horizon borders, mobile toolbar visibility, and preview margins. He also asked @Renato about improving the Title‑to‑body Enter key behavior. [Read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/36?silent=true) - @Martin addressed **category permission** feedback, agreeing to revise the “All members” option and discussed potential migrations for `everyone` permissions to the new `logged_in_users` groups. He also acknowledged other unintended side effects in the permission groups. [Read more](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/5?silent=true) - @Sam commented on a **Redis cache fix** for 404 topic clearing, thanking @Small-Lovely-Cat for the contribution, and suggested a workaround for bounce‑score resetting on email changes. [Read more](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622/2?silent=true) and [here](https://meta.discourse.org/t/bounce-score-does-not-reset-when-email-address-is-changed/409581/2?silent=true). - @Chrisr resolved the **PostgreSQL 18 multisite upgrade** bug and provided step‑by‑step recovery instructions. [Read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/49?silent=true) - @Renato is investigating the **mobile Markdown paste** problem, as flagged by @Sam, and is reviewing the composer redesign feedback. [Read more](https://meta.discourse.org/t/problem-pasting-html-into-markdown-composer-on-mobile-until-pasting-once-into-rich-text-editor/409530/3?silent=true) - @Lindsey responded to the **calendar webhook** request, indicating that the upcoming Workflows feature may serve as the platform for such triggers. [Read more](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623/2?silent=true) - @Italo confirmed the viability of mapping **accepted solutions from Khoros** during migration. [Read more](https://meta.discourse.org/t/accepted-solutions-plugin-migrating-markers-from-khoros/409686/2?silent=true) - @HAWK acknowledged the **DSA compliance** challenges and is working with legal to address the reporting requirements. [Read more](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/3?silent=true) * * * With a day packed with plugin launches, critical bug fixes, and collaborative design improvements, the community is clearly thriving—here’s to another day of building better forums together! 🚀 ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月11日 21:04 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/951 "2026-08-11T21:04:40Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, the Discourse community has been as busy as ever. Here are the key numbers: | Metric | Value | | --- | --- | | **New Posts** | 210 | | **New Topics** | 70 | | **Total Likes** | 298 | **Top Contributors** of the day, ranked by likes received and total posts: | User | Likes | Posts | | --- | --- | --- | | @Merefield | 28 | 14 | | @Moin | 23 | 15 | | @Falco | 23 | 7 | | @Don | 23 | 3 | | @Damian_Boon | 12 | 6 | | @Jagster | 11 | 8 | | @One1 | 10 | 12 | | @Lilly | 10 | 5 | | @NateDhaliwal | 9 | 6 | | @RGJ | 9 | 6 | ## Interesting Topics A collection of the most engaging and important discussions from the past 24 hours, organized by category. ### #Theme-Component - @Don unveiled a stunning new theme component called **Topic Preview Modal** , which allows users to open and interact with topics directly from the topic list in a native modal. The component reuses core Discourse post components within a DModal, enabling full interaction (replies, likes, bookmarks) without leaving the list. @Damian_Boon quickly found compatibility issues with the **Reddit-ish theme** , providing a detailed workaround for the row trigger, and later showed off integrating nested replies. @RGJ requested a configurable width, which @Don quickly added, while @Jagster reported on math rendering issues that were fixed in a commit. [Read more](https://meta.discourse.org/t/topic-preview-modal/409712/15?silent=true). The excitement was palpable, with @Eisammy asking a technical question about `.topic-avatar` borders and @Eviepayne suggesting a toggle for notification clicks to open the modal. This is definitely a must-try component for improving topic list browsing fluency. [Read more](https://meta.discourse.org/t/topic-preview-modal/409712/1?silent=true) ### #Plugin - @Merefield published a new plugin called **Bookmark Notes** , which turns bookmarks into private, personal notes attached to posts. The plugin adds a markdown body to existing bookmarks, keeping them private to the owner, and includes settings to toggle the feature and a post button. A Pro extension available to GitHub Sponsors adds a collapsible panel, bookmark search integration, and a notes column in topic lists. @DRRO asked about linking to notes, which @Merefield clarified is simply the bookmark link itself. @Jagster expressed that this is a feature they didn’t know they needed, while @Lilly appreciated the sponsor-based pro model. [Read more](https://meta.discourse.org/t/bookmark-notes/409685/11?silent=true). It’s a great way to keep context attached to content you save for later. [Read more](https://meta.discourse.org/t/bookmark-notes/409685/1?silent=true) ### #Announcements - The team behind the **Composer Redesign** continues to iterate based on community feedback. @Chapoi acknowledged and implemented several fixes including a visual grip handle, a tag count indicator, and a reformatted title input. They also noted the toolbar visibility issue reported by @Jagster is expected to be resolved once the toggle is removed. @Canapin provided a detailed video demonstrating a choppy drag animation, praising the redesign as a “very nice improvement to something I think is hard to improve.” [Read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/40?silent=true) - @Sam announced **Delegated Vision** support for text-only models in Discourse AI. This allows admins to use lean, text-only models like DeepSeek v4 Flash while still enjoying the full feature set, by delegating image understanding to a separate vision-capable model like Qwen or Gemma. The new option is available under the LLM configuration, making AI-powered image recognition accessible and cost-effective. @Lilly praised the feature as “cool and useful.” [Read more](https://meta.discourse.org/t/delegated-vision-for-text-only-models-in-discourse-ai/409746/1?silent=true) - The long-running **PostgreSQL 18 update** for self-hosters saw its share of discussion. @Chrisr fixed a critical bug affecting multisite upgrades and provided clear instructions for users who encountered botched upgrades. @Peternlewis raised questions about a Redis memory overcommit warning and a smaller database size after migration. @Andrew_Rowe reported success following the update and appreciated @Lilly's tips on checking disk space. This update remains a major focal point for self-hosted admins. [Read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/59?silent=true) - @Jay-C brought up the daunting challenge of **DSA (Digital Services Act) Compliance**, specifically the new standardized Content Moderation Transparency Report and Statements of Reasons requirements. They highlighted limitations in Discourse’s moderation tools for capturing structured data like custom suspension reasons aligned with DSA taxonomy. @HAWK acknowledged being unaware of the new template, promising due diligence with their lawyer, and showing solidarity with “we’re all in this together!” [Read more](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/5?silent=true) - The [discourse.org](http://discourse.org) blog announced the **All-New Admin Dashboard** , designed to bring community metrics together around the question every admin cares about. @Ed_S offered feedback requesting a “System” section for easy visibility of version, updates, and disk space. [Read more](https://meta.discourse.org/t/introducing-the-all-new-admin-dashboard/409764/3?silent=true). The team also launched an asynchronous **AMA** on the new dashboard, inviting all questions and feedback. [Read more](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830/1?silent=true) ### #Self-hosting - @Wsmwktb asked whether opening a self-hosted forum to **Discourse ID authentication** has significant downsides. @Falco dismantled the common fears listed in an old Google search result, calling them “hallucinations,” and provided a pragmatic take: “Use Discourse ID if you want to get many social logins with zero effort.” @Merefield's signature humor was present with a hypothetical Google search for “downsides of walking along a seafront,” which @Falco matched with an appropriate GIF. [Read more](https://meta.discourse.org/t/are-there-significant-downsides-or-problems-to-opening-my-self-hosted-discourse-to-participating-discourse-sites-accounts/409729/6?silent=true) - A user facing a **lost everything** scenario after upgrading provided a custom script to loop through all databases during a Postgres migration, highlighting a painful edge case in the multisite upgrade process. This was a collaborative effort to solve a serious issue. [Read more](https://meta.discourse.org/t/i-upgraded-to-latest-and-lost-everything/409647/5?silent=true) ### #Support - @Karthik_K1 needed help restricting an **AI Agent** to only answer questions related to their forum. @Falco, the Discourse AI lead, clarified that the “Creative” agent has no system prompt and suggested crafting a custom agent. He acknowledged that system prompts aren’t foolproof, as @Karthik_K1 demonstrated by tricking the agent on [ask.discourse.com](http://ask.discourse.com). @Falco suggested Workflows for a two-pass moderation or fine-tuned models for stricter control, offering a realistic look at the limits of prompt-only enforcement. [Read more](https://meta.discourse.org/t/how-can-i-restrict-an-ai-agent-to-answer-only-questions-related-to-my-forum/409672/9?silent=true) - @Wasd_The_Fourth asked how to **remove silences from flags** , a common concern for moderators. @Awesomerobot pointed to site settings like `num_users_to_silence_new_user` and `silence_new_user_sensitivity`. @Moin added nuance, noting that TL3 users shouldn’t be auto-silenced and suggested checking the types of flags being used, which is useful advice for fair moderation. [Read more](https://meta.discourse.org/t/how-do-i-remove-silences-from-flags/409787/4?silent=true) - @AkarinLiu struggled to find the **seedling icon** in the Font Awesome seeder. @Zogstrip pointed out it wasn’t in the default SVG list, and @Moin guided them through adding it correctly to the `SVG icon subset` setting, even demonstrating it. The user’s eventual success was a humorous moment: “I just added a prefix extra, I’m really dumb, what took minutes took tens of minutes.” [Read more](https://meta.discourse.org/t/discourse-fa-seeding/409783/9?silent=true) ### #Feature - @One1 proposed adding **Previous/Next links for topics in Doc Categories** , leveraging the linear order of the category index for documentation. The discussion built on earlier ideas, with @Moin linking to a related suggestion and @Satonotdead noting the long history of such requests for LMS content. Users hope for automatic navigation without manual linking. [Read more](https://meta.discourse.org/t/previous-next-links-for-topics-in-doc-categories/409780/6?silent=true) - @One1 also sparked a discussion about making **long footnotes scrollable** , as they render poorly and glitchy, especially on mobile. @Jagster emphasized the importance for displaying AI explanations. The request gained traction, culminating in a fix from @Zogstrip in [PR #42516](https://forum.discourse.org/...), which should improve the experience significantly. [Read more](https://meta.discourse.org/t/could-long-footnotes-be-scrollable/409613/8?silent=true) ### #ux - @Sterretje asked about a **discrepancy** where user activity in “All/Replies” shows text excerpts, but the “Topics” tab does not. @Moin explained the rationale: for post-level activity, context is needed, whereas topic-level lists rely on titles. @Awesomerobot suggested theme components could add excerpts and encouraged descriptive titles to improve the experience. [Read more](https://meta.discourse.org/t/discrepancy-in-display-of-user-activity-all-replies-vs-topic/409671/6?silent=true) - @NateDhaliwal reported a gap where **muted categories’ topics are not accessible** via the standard `?state=muted` filter. @Awesomerobot acknowledged the limitation and confirmed the user’s intent to view topics from all muted categories, indicating a possible area for future improvement. [Read more](https://meta.discourse.org/t/how-do-i-access-topics-in-muted-categories/409676/3?silent=true) ### #Community Building - @OS_Corsair asked for advice on how to **grow their new community**. @HAWK suggested starting with basics and linking to the community lifecycle blog post. @Merefield gave a blunt but effective piece of advice: “It’s empty? Start filling it with lots and lots of relevant content.” The thread took an interesting turn when @OS_Corsair explained their background and motivations, leading to a broader discussion about open-source and policing. [Read more](https://meta.discourse.org/t/how-do-i-grow-my-community/409760/12?silent=true) ## Activity by the @Team Group The @Team group has been instrumental in driving forward several key initiatives today. Here’s a snapshot of their contributions: - **@Sam** announced the new **Delegated Vision** feature for text-only AI models, expanding the capabilities of Discourse AI with a link to the [announcement](https://meta.discourse.org/t/delegated-vision-for-text-only-models-in-discourse-ai/409746/1?silent=true). He also acknowledged a bug report on category permissions and facilitated its review, [linking @martin](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/4?silent=true), and merged a contributor’s PR for clearing the 404 topic cache, [thanking @zogstrip](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622/2?silent=true). He also discussed the bounce score issue in [this thread](https://meta.discourse.org/t/bounce-score-does-not-reset-when-email-address-is-changed/409581/2?silent=true) and passed along a mobile pasting bug to @Renato in a [linked topic](https://meta.discourse.org/t/problem-pasting-html-into-markdown-composer-on-mobile-until-pasting-once-into-rich-text-editor/409530/3?silent=true). - **@Martin** took ownership of the **category permissions bug** reported in [this topic](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/5?silent=true), engaging deeply with @RGJ's concerns about the new permission groups. He outlined his long-term vision and acknowledged the complexity, ensuring a careful approach to changes. He also clarified his intent for the “All members” migration issue in [another topic](https://meta.discourse.org/t/all-members-when-creating-a-category-assigns-everyone/409508/4?silent=true). - **@Zogstrip** provided the fix for **long footnotes** to make them scrollable in [this topic](https://meta.discourse.org/t/could-long-footnotes-be-scrollable/409613/7?silent=true). He also helped a user with a **FA icon seeding** question, guiding them on where to add the `seedling` icon in [the documentation thread](https://meta.discourse.org/t/discourse-fa-seeding/409783/2?silent=true). - **@Awesomerobot** contributed to various support threads, including explaining **auto-silencing settings** for flags in [this topic](https://meta.discourse.org/t/how-do-i-remove-silences-from-flags/409787/2?silent=true), addressing the **muted categories issue** for @NateDhaliwal in [this topic](https://meta.discourse.org/t/how-do-i-access-topics-in-muted-categories/409676/2?silent=true), and suggesting the feasibility of adding an excerpt display to user profiles in the [activity display discussion](https://meta.discourse.org/t/discrepancy-in-display-of-user-activity-all-replies-vs-topic/409671/6?silent=true). - **@Chapoi** is at the forefront of the **Composer Redesign** initiative, delivering a batch of fixes and improvements based on feedback in the [dedicated testing topic](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/39?silent=true). This includes title reformatting and addressing tag display issues. - **@Tannerabread** fixed the **white screen export issue in Theme Creator** , specifically for the PWA, with a [pull request](https://meta.discourse.org/t/in-theme-creator-exporting-themes-results-in-a-white-screen/403108/8?silent=true), and noted follow-up work for the Hub. They also linked to a fix for the **private email link issue** in [this topic](https://meta.discourse.org/t/with-private-email-enabled-we-should-still-link-the-topic-in-outgoing-emails/401078/3?silent=true). - **@Lindsey** engaged with users on the **Discourse Calendar & Events** plugin, suggesting that Workflows is the future for triggers rather than the legacy Automations plugin in [this topic](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623/2?silent=true). They also hosted the **AMA for the new Admin Dashboard** in [this topic](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830/1?silent=true), where @HAWK asked about automating standard reports, and responded to **Zoom Livestream integration** questions in [this topic](https://meta.discourse.org/t/questions-about-the-zoom-livestream-integration/409816/3?silent=true). - **@HAWK** took on the heavy topic of **DSA compliance** , acknowledging the new reporting template and promising internal legal review in [this thread](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/3?silent=true). They also provided advice on community growth in [this topic](https://meta.discourse.org/t/how-do-i-grow-my-community/409760/5?silent=true) and pointed out how to create documentation categories in [this thread](https://meta.discourse.org/t/more-friendly-category-creation/390841/21?silent=true). - **@Tshenry** updated their **Restrict Uploads** component after @Moin's improvements were merged in this [topic](https://meta.discourse.org/t/restrict-uploads/112688/35?silent=true). - **@Angus** of Pavilion (Custom Wizard) was active, providing fixes and support for the **Custom Wizard Plugin** , specifically addressing access issues for non-staff users and field-saving bugs. They confirmed the fix for @Lebron's issue in [this post](https://meta.discourse.org/t/custom-wizard-plugin/73345/976?silent=true) and followed up with more guidance when problems persisted. * * * It was a day where a simple idea for a “Facebook-style topic modal” blossomed into a community-driven component so popular that even the @Team group took a break from drafting release notes just to install it on their own forums! ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月12日 21:00 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/952 "2026-08-12T21:00:26Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats It was a busy 24 hours on Meta, with **64 new topics** and **213 posts** created, accumulating **307 likes** across the community. Discourse continues to be a thriving hub for support, feature discussion, and community building. **Top contributors** (based on likes received on their posts): | User | Posts | Likes | | --- | --- | --- | | @Moin | 26 | 44 | | @HAWK | 9 | 22 | | @Awesomerobot | 9 | 18 | | @Zogstrip | 5 | 17 | | @NateDhaliwal | 7 | 13 | | @Lindsey | 5 | 13 | | @Merefield | 10 | 12 | | @One1 | 12 | 11 | | @Satonotdead | 12 | 10 | | @Tannerabread | 6 | 9 | * * * ## Interesting Topics ### #Community Building - @OS_Corsair asked for advice on growing a brand-new community at [corsairsoscorsairs.discourse.group](https://corsairsoscorsairs.discourse.group/), sparking a lively discussion about purpose, target audience, and content strategy. @NateDhaliwal provided a detailed checklist of questions to consider, @Moin shared practical tips, and @HAWK (politely) suggested hitting the manual first. [Read more](https://meta.discourse.org/t/how-do-i-grow-my-community/409760/1?silent=true) ### #Support - @AkarinLiu couldn’t locate the Font Awesome `seedling` icon in Discourse’s icon picker, despite adding it to the SVG subset. @Moin quickly spotted the issue—the regular (`far-`) version is a Pro icon—and @Zogstrip merged a PR to improve icon search and pagination. [Read more](https://meta.discourse.org/t/discourse-fa-seeding/409783/1?silent=true) - @Wasd_The_Fourth wanted to disable the automatic silence that occurs when moderators or TL4 users flag posts, as it was causing TL3 users to lose trust level for minor infractions. @Awesomerobot explained the relevant site settings, and @Moin suggested custom flag types as a possible workaround. [Read more](https://meta.discourse.org/t/how-do-i-remove-silences-from-flags/409787/1?silent=true) - @OS_Corsair asked where to place a “banner topic” on their new forum. @NateDhaliwal pointed to the [official banner topic guide](https://meta.discourse.org/t/creating-a-banner-to-display-at-the-top-of-your-site/153718?silent=true), while @Twofoursixeight and @Awesomerobot offered additional pointers—though @Awesomerobot reminded everyone to search and experiment first. [Read more](https://meta.discourse.org/t/where-do-l-create-the-banner-topic/409896/1?silent=true) - @Rinion reported that the Discourse Helper Bot kept opening a private chat channel on their forum even though AI features were disabled. @Gabriel acknowledged the unexpected behavior and said a fix is in the works. [Read more](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914/1?silent=true) - @Satonotdead found that the Proofread helper (AI) was stripping line breaks and mangling quotes and images. @Falco confirmed the bug and referenced a fix PR. [Read more](https://meta.discourse.org/t/proofread-helper-strips-lines-on-meta/409804/1?silent=true) ### #enterprise - @Lindsey launched an asynchronous AMA about the redesigned admin dashboard. @HAWK asked about automating reporting, @One1 wondered if community managers (non-admins) could see the dashboard, and @Nickdb requested more granular pageview drill‑downs. @Lindsey confirmed a traffic explorer is coming. [Read more](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830/1?silent=true) ### #Feature - @One1 proposed adding previous/next links to topics inside #doc-categories, using the category index order. The idea received support from @Satonotdead and @Moin, who noted similar past requests. [Read more](https://meta.discourse.org/t/previous-next-links-for-topics-in-doc-categories/409780/1?silent=true) ### #Plugin - @Merefield updated Bookmark Notes (Pro) with several UX improvements, including direct editing from the topic list. However, @Eviepayne reported issues on older ESR versions, and @Moin explained compatibility constraints. [Read more](https://meta.discourse.org/t/bookmark-notes/409685/4?silent=true) - @Don released a new plugin, **Custom Splash HTML Builder** , to solve mobile performance problems with animated SVG splash screens. The plugin allows admin-defined HTML/CSS for the splash, resulting in dramatically smoother animations—videos included. [Read more](https://meta.discourse.org/t/custom-splash-html-builder/409871/1?silent=true) - The long-standing **Custom Wizard** plugin saw fixes: @Angus resolved a core-update compatibility issue and demonstrated working category creation, though @Lebron and @Eviepayne reported persisting quirks with certain fields. [Read more](https://meta.discourse.org/t/custom-wizard-plugin/73345/974?silent=true) ### #Announcements - @Chapoi provided an update on the composer redesign, listing five fixes implemented (grip, tag button, border radius, keyboard minimisation, markdown preview margin) and outlining next steps. User feedback remains positive: @Canapin called it “just better.” [Read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/39?silent=true) - @Renato unveiled a new Chat feature: **pinned messages now show in a sticky bar** at the top of the channel. This makes important pins impossible to miss while browsing. [Read more](https://meta.discourse.org/t/pinned-chat-messages-now-stay-in-view-with-a-sticky-bar/409089/1?silent=true) - The **PostgreSQL 18 upgrade** for self‑hosters continued generating discussion, with several users sharing migration experiences. @Agemo detailed a disk‑space incident and a successful restore, while @Merefield and @Ed_S offered tips to avoid running out of room. [Read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/52?silent=true) ### #bug - @Tannerabread confirmed that a fix for the sticky unread-reply notification was merged, resolving both the [original report](https://meta.discourse.org/t/sticky-unread-reply-notification/384961/1?silent=true) and a related PM‑removal case. @Moin reproduced the issue and verified the fix works. [Read more](https://meta.discourse.org/t/sticky-unread-reply-notification/384961/4?silent=true) - @Ethsim2 identified the exact cause of `Access Denied` errors for incoming emails with embedded media and opened a PR to keep media moderation intact while fixing the regression. The same user also submitted a PR for the mail‑receiver deprecated parameter. [Read more](https://meta.discourse.org/t/incoming-emails-with-signatures-tables-inline-images-rejected-with-access-denied/409538/2?silent=true) ### #Self-Hosting - @Peternlewis noticed a Redis warning about memory overcommit and a significantly smaller database directory after the PG18 upgrade; @Merefield and others reassured that the size drop is normal. [Read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/52?silent=true) - @ALinux shared their successful migration to a more powerful server, and @Darkpixlz explained why CPU threads matter more than raw clock speed for web services. [Read more](https://meta.discourse.org/t/fresh-install-migrated/409595/4?silent=true) ### #Data & Reporting - @Jay‑C asked about DSA content moderation reporting and statements of reasons requirements. @HAWK engaged with questions about public DSA reports and the gaps remaining after the standardised template. [Read more](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/4?silent=true) ### #General - @Fuse was curious about using the calendar plugin for sport communities. @Lilly shared her experience with a football forum: a bot populated the calendar from the league schedule, and while engagement didn’t shift dramatically, the calendar itself is heavily used by members. [Read more](https://meta.discourse.org/t/sport-communities-and-calendar/409643/2?silent=true) ### #ux - @LWinterberg proposed replacing the “Yes/No” buttons in the review queue with more explicit actions (e.g., _Approve/Delete_) to speed up moderation and reduce confusion. @One1 suggested “Approve Topic/Reject Topic” for clarity. [Read more](https://meta.discourse.org/t/moderation-avoid-yes-no-actions/409773/1?silent=true) * * * ## Activity by the @Team Group The Discourse Core team was highly visible in the last 24 hours, addressing bugs, answering questions, and engaging with the community. - @Zogstrip fixed the missing Font Awesome icon issue and initiated a PR to improve the icon picker’s search and pagination. He also improved long footnotes with a [commit](https://github.com/discourse/discourse/pull/42516). [Read more](https://meta.discourse.org/t/discourse-fa-seeding/409783/2?silent=true) - @Lindsey ran an AMA on the new admin dashboard, answering questions about report automation and promising a traffic explorer in a [future release](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830/1?silent=true). She also recommended using Workflows over Automations for simple processes in the [Workflows preview topic](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990/23?silent=true). - @Tannerabread confirmed and merged fixes for unread notification issues, including the sticky reply and PM‑removal bugs. She also coordinated with @Moin on a reproduction and verified the fix works. [Read more](https://meta.discourse.org/t/sticky-unread-reply-notification/384961/8?silent=true) - @Awesomerobot helped users with flag settings, banner topics, and _First‑post checklist_ queries, often reminding folks to search and experiment first. [Read more](https://meta.discourse.org/t/how-do-i-remove-silences-from-flags/409787/2?silent=true) - @Chapoi thanked users for composer redesign feedback and reported on five implemented fixes, with more in the pipeline. [Read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/39?silent=true) - @Renato announced the new sticky pinned‑chat bar and explained how it works. [Read more](https://meta.discourse.org/t/pinned-chat-messages-now-stay-in-view-with-a-sticky-bar/409089/1?silent=true) - @Gabriel acknowledged and committed to fixing the unwanted auto‑DM from the AI bot. [Read more](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914/3?silent=true) - @J.Jaffeux encouraged users to report any automation tasks that can’t be done in Workflows. [Read more](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990/25?silent=true) - @Martin discussed upcoming permissions redesign and confirmed he’ll fix the immediate category permission bug. [Read more](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/8?silent=true) - @Falco fixed the Proofread helper stripping lines with a [PR](https://github.com/discourse/discourse/pull/42524) and offered insights into restricting AI agent topics. [Read more](https://meta.discourse.org/t/proofread-helper-strips-lines-on-meta/409804/3?silent=true) - @Lindsey also confirmed Zoom Livestream meeting support and clarified app configuration details in the [Zoom integration topic](https://meta.discourse.org/t/questions-about-the-zoom-livestream-integration/409816/3?silent=true). The team’s consistent presence and rapid responses kept Meta humming—here’s hoping the only sticky thing on Monday is the new chat bar, not a bug. * * * _Would you like to see more daily summaries like this? Let us know in the comments below!_ ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月13日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/953 "2026-08-13T21:01:28Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… * * * ## Key Stats In the last 24 hours, **146 new posts** were created across **53 topics** , with **196 likes** given. The community continues to buzz with activity, from bug reports to feature announcements and hearty discussions on community building. **Top contributors by posts and likes:** | User | Posts | Likes | | --- | --- | --- | | @Moin | 27 | 29 | | @Don | 8 | 15 | | @HAWK | 6 | 14 | | @Awesomerobot | 5 | 14 | | @NateDhaliwal | 7 | 13 | | @Renato | 1 | 12 | | @Darkpixlz | 4 | 9 | | @Lindsey | 2 | 9 | | @Rinion | 5 | 8 | | @Tannerabread | 5 | 7 | * * * ## Interesting Topics ### Support - @Rinion reported an [annoying AI bot issue](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914?silent=true) where the Discourse Helper Bot kept auto-opening a private chat channel despite AI features being disabled. @Gabriel acknowledged the unexpected behaviour, implemented a fix, and after a follow-up video and a hard refresh, the issue was resolved. This incident also sparked a discussion about how updates are deployed to hosted sites, with @Moin explaining the deployment cadence. - @Marcozambi struggled with a failed [restore due to S3 migration problems](https://meta.discourse.org/t/restore-fails-due-to-s3-migration-failure/409771?silent=true). @Awesomerobot explained that the restore failure counter is just a flag count and walked through the `rake posts:missing_uploads` tasks to list and repair missing uploads before taking a fresh backup. - @Kairo162 was puzzled by [email app notifications instead of in-app ones](https://meta.discourse.org/t/discourse-is-sending-me-email-app-notifications-instead-of-normal-notifications/409952?silent=true). @NateDhaliwal clarified the difference between email and push notifications, and after adjusting settings, the user confirmed the fix. - @Wasd_The_Fourth asked about [removing silences from flags](https://meta.discourse.org/t/how-do-i-remove-silences-from-flags/409787?silent=true) in a moderation context. @Moin pointed to the moderation flags overview and the fact that off-topic flags leading to auto-silence is unusual, prompting further discussion. - In a German-language thread, @Mr.Xurrent reported a [missing admin sidebar](https://meta.discourse.org/t/admin-seitenleiste-nicht-mehr-vorhanden/409913?silent=true) on their forum. @Moin guided them through [safe mode](https://meta.discourse.org/t/53504?silent=true) and browser console checks, leading to a likely cause: a JavaScript error from an outdated plugin or theme interaction. The community pitched in with debugging steps. ### Announcements - @Renato announced that [pinned chat messages now stay in view with a sticky bar](https://meta.discourse.org/t/pinned-chat-messages-now-stay-in-view-with-a-sticky-bar/409089?silent=true). The new feature shows the most relevant pinned message at the top of the channel, follows the user’s scroll position, and is dismissible for non-managers. It ships as part of the Chat pinned messages upcoming change. - The [new Workflows feature](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990?silent=true) gained traction, with @Satonotdead asking when to use Workflows over Automations + queries. @Lindsey recommended using Workflows for flexibility and better visibility, while @J.Jaffeux invited users to report any missing capabilities. - The [Solved improvements](https://meta.discourse.org/t/solved-improvements-allowing-members-to-indicate-theyre-experiencing-a-reported-issue/402498?silent=true) continue to evolve, with @Sterretje asking whether the “I have this problem too” button disappears after a solution is marked. @Moin confirmed it does, citing an example topic. - @Tobiaseigen shared progress on [ActivityPub plugin](https://meta.discourse.org/t/activitypub-plugin/266794?silent=true) where images from federated posts are duplicating on Mastodon, seeking advice on configuration. - @Agemo praised the [bulk user deletion feature](https://meta.discourse.org/t/bulk-user-deletion-for-staff-now-available/345786?silent=true) and requested additional bulk actions like de-activation and group tagging, sparking a broader conversation about user management tools. ### Bug - @Moin reproduced and helped isolate a [sticky unread reply notification](https://meta.discourse.org/t/sticky-unread-reply-notification/384961?silent=true) issue. @Tannerabread confirmed that a fix from another PR (also related to notifications after removal from a PM) resolved it, and @Moin confirmed the notification was cleared. - @Kairo162’s [notification issue](https://meta.discourse.org/t/discourse-is-sending-me-email-app-notifications-instead-of-normal-notifications/409952?silent=true) (already listed under Support) also fits here as a bug report, but the root cause was user preferences. - @ばこん reported [a large number of poll requests being canceled](https://meta.discourse.org/t/a-large-number-of-poll-requests-will-be-canceled/410007?silent=true) with a video showing the behavior, along with an unread notification toggle glitch. No response yet, but the community may pick it up. ### Feature - @WorldIsMine raised a UX concern about the [delete user button in the moderation queue](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025?silent=true) being too easy to click accidentally. @Moin linked to a similar earlier report, and the discussion suggests adding a confirmation prompt. - @Ice.D proposed a [plugin idea to auto cross-post from Fandom Wiki to a Discourse category](https://meta.discourse.org/t/feature-plugin-idea-auto-cross-post-from-fandom-wiki-to-a-discourse-category/409960?silent=true). The community is exploring the concept, though no official response yet. ### Plugin - @Don introduced a [Custom Splash HTML Builder](https://meta.discourse.org/t/custom-splash-html-builder/409871?silent=true) that lets admins define custom splash screens with HTML/CSS, focusing on smoother mobile animations. They also added `data-color-scheme` support for light/dark themes, and @Agemo praised it as long-awaited. - @Merefield back-ported improvements to the [Locations Plugin](https://meta.discourse.org/t/locations-plugin/69742?silent=true) from early access, and @Don updated several theme components: [Guest Gate](https://meta.discourse.org/t/guest-gate-theme-component/225107?silent=true) (v2.0 planned), [Offline Indicator](https://meta.discourse.org/t/offline-indicator-theme-component/225130?silent=true), [Quick Profile Links Menu](https://meta.discourse.org/t/quick-profile-links-menu/338591?silent=true), and [AI Post Analyzer for Chat](https://meta.discourse.org/t/ai-post-analyzer-for-chat/364355?silent=true). ### Community Building - @OS_Corsair asked [how to grow their community](https://meta.discourse.org/t/how-do-i-grow-my-community/409760?silent=true) and received blunt but honest advice from @HAWK, @Moin and @Darkpixlz, who suggested pausing to read up on community building basics before seeking specific guidance. The thread eventually wound down. ### Enterprise - The [admin dashboard AMA](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830?silent=true) saw @Lindsey fielding questions about access for non-admin community managers. @One1 wanted to share the dashboard without granting full admin rights, while @HAWK and @Nickdb offered perspectives on typical role separation. @Lindsey hinted at a future in-depth traffic explorer. ### Data & reporting - @Jay-C asked about [DSA content moderation reporting and statements of reasons requirements](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681?silent=true). @HAWK provided guidance and later updated that the team is spec’ing out additional data fields for the machine-readable report and SOR database submissions. ### Development - @NateDhaliwal announced a [plugin in beta to display TL3 progress for TL2 users](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543?silent=true). They added features to show locked status, muted category counts, and pending expiry, and are seeking feedback. ### Theme Component - @Don outlined major improvements coming in [Guest Gate 2.0](https://meta.discourse.org/t/guest-gate-theme-component/225107?silent=true), including a new trigger system (page views, time, scroll, lightbox), varied repeat behaviours, delayed display, and better modal customisation. Existing settings will be migrated. * * * ## Activity by the @Team Group The Discourse team has been busy across multiple fronts: - @Gabriel actively fixed the AI bot channel bug, manually removed the problematic channel, and deployed an update for the user, as seen in the [AI bot topic](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914?silent=true). They also asked for a screen share to diagnose persistence issues. - @Lindsey answered questions about the admin dashboard in the [AMA](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830?silent=true) and explained when to use Workflows over Automations in the [Workflows preview](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990?silent=true). - @Renato announced the new sticky pinned chat messages feature in the [announcement topic](https://meta.discourse.org/t/pinned-chat-messages-now-stay-in-view-with-a-sticky-bar/409089?silent=true). - @Tannerabread fixed the sticky unread notification bug, referencing a PR merge that resolved both issues; see the [bug report](https://meta.discourse.org/t/sticky-unread-reply-notification/384961?silent=true). They also confirmed the fix in the [Can’t clear unread notification](https://meta.discourse.org/t/cant-clear-unread-notification-after-being-removed-from-a-pm/311995?silent=true) thread. - @J.Jaffeux encouraged users to report workflow gaps, noting that all post menu actions can now be done via workflows in the [AI Post Analyzer thread](https://meta.discourse.org/t/ai-post-analyzer-for-chat/364355?silent=true). - @Awesomerobot provided support for the S3 restore issue, discussed cache clearing constraints in [Allow clearing cache](https://meta.discourse.org/t/allow-clearing-cache/408791?silent=true), and answered Zoom integration questions in [Questions about the Zoom Livestream integration](https://meta.discourse.org/t/questions-about-the-zoom-livestream-integration/409816?silent=true). - @HAWK moderated conversations in the [How do I grow my community?](https://meta.discourse.org/t/how-do-i-grow-my-community/409760?silent=true) topic, contributed to the admin dashboard AMA, and gave updates on DSA reporting in the [DSA topic](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681?silent=true). - @NateDhaliwal answered numerous support questions, including notifications, banner topics, and muted categories, and shared progress on the TL3 plugin in the [Development topic](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543?silent=true). - @Zogstrip addressed FA icon seeding queries and opened a PR to add search/pagination to the icon component in the [Chinese support thread](https://meta.discourse.org/t/discourse-fa-seeding/409783?silent=true). - @Jordan.Vidrine announced the composer actions dropdown moving to core and merged a PR in the [new “Post Type” topic](https://meta.discourse.org/t/introducing-a-new-post-type-composer-actions-dropdown/403635?silent=true). They also asked for clarification on Arabic text padding in [Not enough bottom padding for Arabic text](https://meta.discourse.org/t/not-enough-bottom-padding-for-arabic-text/409392?silent=true). - @Sam responded to a question about AI agent skills, hinting at a potential new top-level concept in Discourse AI in the [Giving Discourse AI agent skills](https://meta.discourse.org/t/giving-discourse-ai-agent-skills/408666?silent=true) thread. - @Martin helped with theme component group permissions, approving a PR and explaining migration best practices in the [Granular group-based permissions](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273?silent=true) and [Category permissions](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511?silent=true) topics. - @Tobiaseigen discussed ActivityPub federation image duplication in the [ActivityPub plugin thread](https://meta.discourse.org/t/activitypub-plugin/266794?silent=true). - @Angus fixed a custom wizard issue with category settings and acknowledged the plugin’s occasional neglect, promising a fix in the [Custom Wizard topic](https://meta.discourse.org/t/custom-wizard-plugin/73345?silent=true). - @Chapoi confirmed a fix for Safari PWA zooming bug in the [Safari PWA topic](https://meta.discourse.org/t/safari-pwa-zooming-is-buggy/407806?silent=true). - @Chau started a discussion on Voice of the Customer programs in the enterprise category, asking how communities contribute to feedback loops in [How does Community fit into your VoC?](https://meta.discourse.org/t/how-does-community-fit-into-your-voice-of-the-customer-program/409947?silent=true). - @Darkpixlz offered pragmatic advice on community growth and hardware considerations for self-hosted forums, rounding out several threads. * * * _May your pins stay sticky, your notifications never get stuck, and your admin sidebar always appear!_ ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月14日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/954 "2026-08-14T21:01:28Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… Another bustling 24 hours on Meta, with a flurry of bug reports, feature requests, and some fantastic community contributions. From dangerous delete buttons to AI subagents, the team and community have been hard at work. Here’s your daily digest. ## Key Stats In the last 24 hours, Meta has seen a total of **130 new posts** across **58 distinct topics** , generating **187 likes**. It’s been a busy day of problem-solving and discussion! The most active and liked members today were: - @Moin (29 likes, 21 posts) - @Awesomerobot (21 likes, 3 posts) - @Sam (19 likes, 2 posts) - @NateDhaliwal (12 likes, 6 posts) - @WorldIsMine (12 likes, 1 post) - @Don (10 likes, 8 posts) - @Rosiesherry (6 likes, 4 posts) - @Nickdb (6 likes, 1 post) - @HAWK (5 likes, 6 posts) - @Rishabh (5 likes, 1 post) ## Interesting Topics ### #Feature - @WorldIsMine sounded the alarm that the delete user button in the moderation queue is a [one-click catastrophe waiting to happen](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025/1?silent=true), as admins have accidentally wiped legitimate users while approving hundreds of items. @Awesomerobot came to the rescue, implementing a [confirmation step for irreversible actions](https://github.com/discourse/discourse/pull/42605) that has now been [merged](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025/4?silent=true) and will be available in upcoming updates. This also addresses the earlier report on the [Moderation UI being too easy to misuse](https://meta.discourse.org/t/moderation-ui-too-easy-to-delete-a-valid-user/390533/8?silent=true). - @Cogdog highlighted the frustrating UX of [finding invitation links](https://meta.discourse.org/t/invitation-links-nearly-impossible-to-find/410006/1?silent=true), which currently requires navigating a convoluted edit/update sequence. @Rishabh and @Jordan.Vidrine from the team confirmed this is a valid feedback point and that a [copy link action on each row](https://meta.discourse.org/t/invitation-links-nearly-impossible-to-find/410006/6?silent=true) is now being worked on, with a simple fix likely arriving soon. - For those using documentation categories, @Sren-1 shared a [client-side JavaScript workaround](https://meta.discourse.org/t/redirect-the-landing-page-for-each-subcategory-to-index-file-by-default-for-documentation-categories/409470/4?silent=true) to redirect subcategory landing pages to a specific index topic, picking up on the ongoing discussion about what the [homepage for doc categories should be](https://meta.discourse.org/t/what-should-the-homepage-be-for-doc-categories/398616/6?silent=true). @Jordan.Vidrine also chimed in with agreement that landing on the index page makes sense and floated the idea of a purpose-built UI for it in the [related design discussion](https://meta.discourse.org/t/what-should-the-homepage-be-for-doc-categories/398616/6?silent=true). - @Moin continued a discussion from a previous topic, confirming that the [Icon type SiteSetting is now available](https://meta.discourse.org/t/icon-type-theme-setting-in-objects-type-settings/410092/1?silent=true) via a new pull request, and suggesting a new topic for supporting `type: icon` inside object schemas for theme settings. - @Per1234 reported an issue with copying workflow step names, which @Zogstrip has confirmed will be fixed by a [new pull request](https://meta.discourse.org/t/copy-workflow-step-names/409410/3?silent=true). ### #Announcements - In an exciting development, @Sam announced the landing of [subagent support in Discourse AI](https://meta.discourse.org/t/discourse-ai-subagents/410055/1?silent=true). This powerful new feature allows you to delegate tasks to other AI agents, enabling you to mix and match language models, protect against context bloat, and increase concurrency. The announcement was met with significant interest from the community. - @Chapoi announced that [AI title suggestions have moved to the composer helper](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/1?silent=true), integrating them with the other AI helpers in the composer menu. This is part of a broader effort to refine the AI UX, and feedback is welcome on this change. - There was further activity on the [Solved improvements topic](https://meta.discourse.org/t/solved-improvements-allowing-members-to-indicate-theyre-experiencing-a-reported-issue/402498/59?silent=true), with @Sterretje asking a clarifying question about the “I have this problem too” button. @Moin confirmed that the button disappears once a post is marked as the solution, pointing to an example in the #Support category. ### #Support - The thread about the [AI bot auto-adding a user to private chat channels](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914/7?silent=true) saw some deep debugging. @Gabriel deployed a fix and had to manually remove the channel after the user provided video evidence of the issue persisting. @Moin took the opportunity to explain the nuance between a site being on the “latest” branch versus having all the latest builds deployed. - @Damian_Boon took a firm stance in the [Expansion of Discussions in Discourse](https://meta.discourse.org/t/expansion-of-discussions-in-discourse/410059/4?silent=true) topic, advising the original poster that they were “on about” and should not base their community design on this meta-forum, suggesting they use AI to grasp the basics instead. @Ondrej offered a more constructive angle, pointing out [AI translation tools](https://meta.discourse.org/t/expansion-of-discussions-in-discourse/410059/5?silent=true) and @Nickdb provided a nuanced perspective on what Discourse is. - @Heliosurge reported a concerning Android behavior where [Discourse asks for permission to access other apps](https://meta.discourse.org/t/discourse-asked-for-permission-to-access-other-apps/410063/1?silent=true) when posting in a specific plugin topic, a new one for the bug hunters. - A user reported that some of their members [cannot vote in polls](https://meta.discourse.org/t/voting-in-polls-sometimes-doesn-t-work-for-a-user/410085/1?silent=true), seeing only a blank space instead of vote buttons. @Zogstrip from the team asked for more details like browser versions and OS to help debug the issue, while another user confirmed it works on their Pixel 10, pointing to a potential Safari/iOS-specific problem. - @Kairo162 was puzzled by receiving [email notifications instead of in-app notifications](https://meta.discourse.org/t/discourse-is-sending-me-email-app-notifications-instead-of-normal-notifications/409952/2?silent=true), and @NateDhaliwal walked them through the notification settings and potential causes like paused notifications. ### #Plugin - The long-running [Custom Wizard Plugin](https://meta.discourse.org/t/custom-wizard-plugin/73345/981?silent=true) thread saw a burst of activity. @Angus confirmed a potential fix for category settings, but @Lebron and @Eviepayne reported further issues with tags and user groups. @Angus followed up with [another set of fixes](https://meta.discourse.org/t/custom-wizard-plugin/73345/985?silent=true) and addressed the topic of plugin maintenance, suggesting that if users rely on it heavily, they could contribute PRs. After further testing, @Lebron and @Eviepayne confirmed the [updates appear to work](https://meta.discourse.org/t/custom-wizard-plugin/73345/988?silent=true), though a theme selection issue was still noted. - In the [Guest Gate Theme Component](https://meta.discourse.org/t/guest-gate-theme-component/225107/161?silent=true) thread, @Don provided support for customizing the component and teased the upcoming [Guest Gate 2.0](https://meta.discourse.org/t/guest-gate-theme-component/225107/161?silent=true), which promises a redesigned trigger system (page views, time, scroll, lightbox), new repeat behaviors, delayed display options, and more customization, with automatic migration from old settings. - @Don also showcased the release of [Discourse Stickers v2.0](https://meta.discourse.org/t/discourse-stickers/280873/12?silent=true), a significant modernization that includes a redesigned sticker configuration using Discourse’s native ‘objects’ setting type, support for sticker groups and filters, category-specific stickers, and more control over chat sticker availability. ### #bug - @Dubwoc reported a potential bug where [data in custom fields is cleared when certain other fields change](https://meta.discourse.org/t/potential-bug-where-data-in-custom-fields-is-cleared-if-certain-fields-change/410050/3?silent=true) in the Calendar and Events feature. This was quickly acknowledged by @Zogstrip, who confirmed it will be fixed by a [new pull request](https://github.com/discourse/discourse/pull/42624). ### #ux - @Moin filed a UX complaint about [changelog links showing changes not yet available](https://meta.discourse.org/t/changelog-links-show-changes-not-yet-available-in-my-forum/410023/1?silent=true) on their forum, noting that the link and the GitHub equivalent reference his specific version, but the changelog link does not. ### #Site feedback - In the ongoing [Rebuilding the Meta Branded theme](https://meta.discourse.org/t/rebuilding-the-meta-branded-theme-new-icons-a-custom-homepage-and-a-first-look-at-the-blocks-api/400013/31?silent=true) discussion, @Twofoursixeight reported a minor UI issue where the star icon in chat looks identical whether starred or not, on this specific theme. ## Activity by the @Team Group The @Team group has been exceptionally active, driving fixes and engaging with the community: - @Awesomerobot identified and swiftly fixed the dangerous delete-user issue, merging a confirmation prompt to prevent accidental user deletion in the [moderation queue](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025/3?silent=true). This also resolved the older [Moderation UI topic](https://meta.discourse.org/t/moderation-ui-too-easy-to-delete-a-valid-user/390533/8?silent=true). - @Sam announced the release of [AI subagents](https://meta.discourse.org/t/discourse-ai-subagents/410055/1?silent=true), a major feature for the AI plugin, and also contributed to the discussion on [giving Discourse AI agent skills](https://meta.discourse.org/t/giving-discourse-ai-agent-skills/408666/9?silent=true), hinting at potential new top-level concepts to make this more accessible. - @Rishabh and @Jordan.Vidrine responded to feedback on [invite link discoverability](https://meta.discourse.org/t/invitation-links-nearly-impossible-to-find/410006/6?silent=true), confirming work on adding a copy link action to the invite list and committing to implementing it soon. - @Zogstrip confirmed fixes for two separate bugs: a [custom fields clearing issue](https://meta.discourse.org/t/potential-bug-where-data-in-custom-fields-is-cleared-if-certain-fields-change/410050/3?silent=true) and a [workflow copy name issue](https://meta.discourse.org/t/copy-workflow-step-names/409410/3?silent=true). - @Chapoi detailed the move of AI title suggestions to the composer helper in an [announcement](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/1?silent=true). - @Martin engaged in a detailed technical discussion about theme component settings and group permissions, clarifying PR merging and suggesting migration strategies for [granular group-based permissions](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/35?silent=true) and [category permissions](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/12?silent=true). - @Tannerabread actively investigated an elusive admin sidebar bug, asking for more technical details and console output from the reporter to try and reproduce the [issue on their end](https://meta.discourse.org/t/admin-seitenleiste-nicht-mehr-vorhanden/409913/17?silent=true). - @HAWK provided updates on [DSA Content Moderation reporting](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/9?silent=true), noting that work is being spec’d out for additional data fields. - @NateDhaliwal offered assistance across various topics, including [notification settings](https://meta.discourse.org/t/discourse-is-sending-me-email-app-notifications-instead-of-normal-notifications/409952/2?silent=true), [Discourse expansion](https://meta.discourse.org/t/expansion-of-discussions-in-discourse/410059/2?silent=true), and is preparing to create a plugin topic for [TL3 progress tracking](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543/30?silent=true). - @Moin was a hive of activity, helping users on topics ranging from [PostgreSQL upgrades](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/63?silent=true) and [modal confirmation dialogs](https://meta.discourse.org/t/icon-type-theme-setting-in-objects-type-settings/410092/1?silent=true) to documenting [calendar creation bugs](https://meta.discourse.org/t/creating-and-managing-calendars/283773/21?silent=true) and [mobile composer issues](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352/24?silent=true). - @Gabriel provided direct support for the [AI chat channel bug](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914/12?silent=true), going as far as manually removing the channel and triggering a new deployment to resolve the user’s issue. * * * And in the end, the team came together to remind the user that yes, deleting a user is, in fact, a bit “evil,” but at least we now have a confirmation popup to stop us from being quite so villainous. ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月15日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/955 "2026-08-15T21:01:03Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… Another vibrant day on Meta! From AI subagents to a bevy of bug reports and theme updates, the community was buzzing with activity. Let’s dive into the last 24 hours. ## Key Stats In the last 24 hours, the community has been hard at work. Here’s a snapshot of the activity: - **83** new posts were created - **43** new & updated topics were generated - **117** likes were given across these posts Here are the top contributors from the last 24 hours: | User | Posts | Likes Received | | --- | --- | --- | | @Sam | 1 | 18 | | @Moin | 6 | 15 | | @Awesomerobot | 2 | 10 | | @NateDhaliwal | 3 | 7 | | @Nickdb | 2 | 6 | | @Rishabh | 1 | 5 | | @Satonotdead | 5 | 4 | | @Don | 3 | 4 | | @Zogstrip | 3 | 4 | | @Angus | 2 | 4 | The most-liked post of the day was @Sam's announcement about **Discourse AI subagents** , which received 18 likes. A close second was @OS_Corsair's new topic on **Expansion of Discussions in Discourse** , which garnered 17 likes across the discussion. ## Interesting Topics The community discussed a wide variety of topics. Here’s a curated overview of the most interesting discussions, grouped by their category. ### #Announcements - **@Sam** unveiled the latest feature for Discourse AI: [subagents](https://meta.discourse.org/t/discourse-ai-subagents/410055/1?silent=true). This new capability allows users to delegate work to other agents from a main agent, enabling tasks to be decomposed into saner pieces, mixing and matching language models, protecting against context bloat, and increasing concurrency and speed. For example, a “Web Researcher” subagent or a “Fact validation” subagent can be created. This is a significant step forward for the AI integration. [read more](https://meta.discourse.org/t/discourse-ai-subagents/410055/1?silent=true) - **@Chapoi** announced that [AI title suggestions have moved to the composer helper](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/1?silent=true). The feature is now located with other AI helpers in the AI composer menu, following the earlier integration of category and tag suggestions into an inline format. Further improvements to ease of use are planned, and the team is interested in hearing from anyone who heavily relies on the feature’s previous prominent placement. [read more](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/1?silent=true) - The **Help Us Test the Composer Redesign** thread saw continued feedback. @Sterretje noted the new composer takes up a lot of vertical real estate, [requiring resizing when composing new topics](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/43?silent=true). @Nickdb reported issues with the mermaid plugin in the rich text editor, though a page reload resolved it, and @Sk-Or-V1-Contents confirmed a fix for a keyboard-related glitch. [read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/45?silent=true) ### #Community Building - @OS_Corsair sparked a discussion on the [expansion of discussions in Discourse](https://meta.discourse.org/t/expansion-of-discussions-in-discourse/410059/1?silent=true), asking if Discourse can house and handle the “pluralistic diversity” of its users. @NateDhaliwal highlighted moderation tools like topic timers and slow mode, while @Ondrej pointed to AI translations for inclusivity. @Nickdb provided a grounded perspective, noting that “Discourse is a framework, a bag of tools to build your own community” and that users need a solid idea of what they want to achieve first. [read more](https://meta.discourse.org/t/expansion-of-discussions-in-discourse/410059/7?silent=true) ### #ux - @Rishabh confirmed the team is working on a [copy link action for invite rows](https://meta.discourse.org/t/invitation-links-nearly-impossible-to-find/410006/6?silent=true) to make invitation links easier to find, following feedback from @Cogdog. @Jordan.Vidrine added that they would be working on bringing new info to the `/invites` list imminently. [read more](https://meta.discourse.org/t/invitation-links-nearly-impossible-to-find/410006/7?silent=true) - **@Awesomerobot** announced a fix for the dangerously easy user deletion in the moderation queue, stating they have [merged a change](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025/4?silent=true) that adds a confirmation step. This directly addresses the concerns raised in the parallel topic on the [Moderation UI and user deletion](https://meta.discourse.org/t/moderation-ui-too-easy-to-delete-a-valid-user/390533/8?silent=true). [read more](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025/4?silent=true) - @Moin shared a tip on how to [choose icons for links in custom sidebar sections](https://meta.discourse.org/t/how-to-choose-icons-for-links-in-custom-section/294219/11?silent=true). Thanks to new changes, it’s now possible to scroll through all available icons on the forum, making the selection process less language-dependent. [read more](https://meta.discourse.org/t/how-to-choose-icons-for-links-in-custom-section/294219/11?silent=true) - The discussion on **What should the homepage be for doc categories?** continued. @Jordan.Vidrine agreed that landing on the index page makes sense and floated the idea of [building a new UI for it](https://meta.discourse.org/t/what-should-the-homepage-be-for-doc-categories/398616/6?silent=true) in the future, while also praising the idea of automatic previous/next buttons for doc navigation. [read more](https://meta.discourse.org/t/what-should-the-homepage-be-for-doc-categories/398616/6?silent=true) ### #Feature - @Moin pointed out that **icon type theme settings** are now available for objects types, and suggested creating a feature request if icon support is desired in object schemas for themes. [read more](https://meta.discourse.org/t/icon-type-theme-setting-in-objects-type-settings/410092/1?silent=true) - @Zogstrip confirmed a fix for the **Copy Workflow step names** bug, which will be resolved by a pull request. [read more](https://meta.discourse.org/t/copy-workflow-step-names/409410/3?silent=true) - @Heliosurge requested an option to add a [start date to the RSS Polling plugin](https://meta.discourse.org/t/add-option-of-start-date-to-rss-polling-plugin/410065/1?silent=true) for better control over how much content from long-running feeds, like YouTube channels, is polled. @Moin asked for clarification on the use case. [read more](https://meta.discourse.org/t/add-option-of-start-date-to-rss-polling-plugin/410065/2?silent=true) - @Polybos filed a feature request for [secure-uploads support for S3 backends without per-object ACLs](https://meta.discourse.org/t/feature-request-secure-uploads-for-s3-backends-without-per-object-acls/410069/1?silent=true). The core conflict is that avatars/assets require public unauthenticated reads, while secure uploads need an authenticated path, and the system currently cannot distinguish between them without per-object ACLs. [read more](https://meta.discourse.org/t/feature-request-secure-uploads-for-s3-backends-without-per-object-acls/410069/1?silent=true) ### #Plugin - @Angus posted another set of fixes for the **Custom Wizard Plugin** in response to reported issues. A lively discussion also emerged about plugin maintenance, where @Satonotdead suggested finding more maintainers, and @Angus gently encouraged community contributions, noting that “if you have the capacity to overhaul your stack… you probably have the capacity to run codex or claude once in a while to make a PR.” [read more](https://meta.discourse.org/t/custom-wizard-plugin/73345/985?silent=true) - **@Don** released a massive v2.0 update for the **Discourse Stickers** theme component. The update features a completely redesigned sticker configuration using native objects, support for sticker groups, category-specific stickers, and more control over chat sticker availability. Crucially, existing sticker configurations are automatically migrated to the new format. [read more](https://meta.discourse.org/t/discourse-stickers/280873/12?silent=true) - @Jesse_Mba_Commons reported that the **Discourse Calendar and Events** `Upcoming Events` route omits all Open Graph and Twitter-card metadata from the initial server-rendered HTML, which is a problem for social crawlers like LinkedIn. [read more](https://meta.discourse.org/t/discourse-calendar-and-events/97376/611?silent=true) ### #bug - @Dubwoc reported a [potential bug where data in custom fields is cleared if certain fields change](https://meta.discourse.org/t/potential-bug-where-data-in-custom-fields-is-cleared-if-certain-fields-change/410050/1?silent=true) for the calendar/events plugin. @Zogstrip confirmed the report and announced it would be fixed with a pull request. [read more](https://meta.discourse.org/t/potential-bug-where-data-in-custom-fields-is-cleared-if-certain-fields-change/410050/3?silent=true) - @Tannerabread is investigating an issue where the [admin sidebar is not appearing](https://meta.discourse.org/t/admin-seitenleiste-nicht-mehr-vorhanden/409913/17?silent=true). They are asking the reporter to run a specific console command to diagnose a potential issue with the `admin_config_login_routes` data. [read more](https://meta.discourse.org/t/admin-seitenleiste-nicht-mehr-vorhanden/409913/17?silent=true) - @Twofoursixeight reported that the [fullscreen chat container on Android tablets is too tall](https://meta.discourse.org/t/the-fullscreen-chat-container-on-android-tablets-is-too-tall/410038/1?silent=true), causing the title to vanish. @Moin was able to reproduce the issue and provided a workaround using the sidebar. [read more](https://meta.discourse.org/t/the-fullscreen-chat-container-on-android-tablets-is-too-tall/410038/2?silent=true) - @Roke_Julian_Lockhart discovered a CSS bug where `code` is [invisible when directly inside a 4 tag](https://meta.discourse.org/t/code-is-invisible-solely-when-directly-inside-small/410078/1?silent=true) within blockquotes, as the background color is identical to the quote’s. [read more](https://meta.discourse.org/t/code-is-invisible-solely-when-directly-inside-small/410078/1?silent=true) - @Per1234 filed a detailed bug report about the new [Workflows feature requiring a modal to be closed in every Discourse tab](https://meta.discourse.org/t/workflow-modal-must-be-closed-in-every-discourse-tab/410129/1?silent=true). The bug causes the modal to appear persistently in all tabs, and resolving it in one tab leads to errors in others. [read more](https://meta.discourse.org/t/workflow-modal-must-be-closed-in-every-discourse-tab/410129/1?silent=true) ### #Support - @Shauny is seeking help for a [poll voting issue where some users cannot see the vote buttons](https://meta.discourse.org/t/voting-in-polls-sometimes-doesn-t-work-for-a-user/410085/1?silent=true) on Safari. @Zogstrip has asked for more details, including OS/browser versions, adblockers, and browser extensions, to help diagnose the issue. [read more](https://meta.discourse.org/t/voting-in-polls-sometimes-doesn-t-work-for-a-user/410085/4?silent=true) - @Heliosurge flagged a [strange Android permission prompt](https://meta.discourse.org/t/discourse-asked-for-permission-to-access-other-apps/410063/1?silent=true) that appeared when posting, although no new permissions were visible in the app settings. [read more](https://meta.discourse.org/t/discourse-asked-for-permission-to-access-other-apps/410063/1?silent=true) ### #Self-hosting - @Ethsim2 shared their experience setting up **Caddy in front of the app’s Nginx** via Docker Compose to provide HTTP/3 support, and is gauging interest for a step-by-step guide. @Pfaffman pointed to a relevant PR on the discourse\_docker repo. [read more](https://meta.discourse.org/t/caddy-in-front-of-app-s-nginx-via-docker-compose/410123/1?silent=true) - @Thomas_Rother contributed information about using **[hetzner.de](http://hetzner.de) as an EU-DSGVO compliant S3-compatible storage provider** for uploads, with an example configuration table. [read more](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916/510?silent=true) ### #development - @NateDhaliwal announced that the **[TL3 Progress plugin for TL2 users is now in beta](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543/30?silent=true)** and updated the link for tracking preferences. @Satonotdead wondered if the base could be used for similar progress related to badges. [read more](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543/31?silent=true) ### #enterprise - The **Ask me anything about the new admin dashboard** topic saw a deep dive into community management. @One1 explained how their community managers are given moderator status rather than admin, and how they wish they had a “sudo” mode to turn on their superpowers only when needed. [read more](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830/14?silent=true) ## Activity by the @Team Group The @Team group was busy across several fronts today. Here is a summary of their activities: - **@Sam** announced the launch of [AI subagents](https://meta.discourse.org/t/discourse-ai-subagents/410055/1?silent=true), a major new feature for the Discourse AI plugin. [read more](https://meta.discourse.org/t/discourse-ai-subagents/410055/1?silent=true) - **@Awesomerobot** fixed the dangerous **delete user button** in the moderation queue, adding a [secondary confirmation prompt](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025/4?silent=true) and addressing the related [UI concerns](https://meta.discourse.org/t/moderation-ui-too-easy-to-delete-a-valid-user/390533/8?silent=true). [read more](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025/4?silent=true) - **@Rishabh** responded to feedback on [invitation links](https://meta.discourse.org/t/invitation-links-nearly-impossible-to-find/410006/6?silent=true), confirming that a copy link action is being worked on. [read more](https://meta.discourse.org/t/invitation-links-nearly-impossible-to-find/410006/6?silent=true) - **@Jordan.Vidrine** also contributed to the invitation links topic, stating they would be [working on bringing new info to the /invites list](https://meta.discourse.org/t/invitation-links-nearly-impossible-to-find/410006/7?silent=true). He also gave feedback on [doc category homepages](https://meta.discourse.org/t/what-should-the-homepage-be-for-doc-categories/398616/6?silent=true). [read more](https://meta.discourse.org/t/what-should-the-homepage-be-for-doc-categories/398616/6?silent=true) - **@Angus** was active on the **Custom Wizard Plugin** thread, pushing out [another set of fixes](https://meta.discourse.org/t/custom-wizard-plugin/73345/985?silent=true) and encouraging community contributions to the open-source plugin. [read more](https://meta.discourse.org/t/custom-wizard-plugin/73345/987?silent=true) - **@Zogstrip** confirmed fixes for the [Copy Workflow step names](https://meta.discourse.org/t/copy-workflow-step-names/409410/3?silent=true) and the [custom fields data clearing bug](https://meta.discourse.org/t/potential-bug-where-data-in-custom-fields-is-cleared-if-certain-fields-change/410050/3?silent=true). He also requested more info on the [poll voting issue](https://meta.discourse.org/t/voting-in-polls-sometimes-doesn-t-work-for-a-user/410085/4?silent=true). [read more](https://meta.discourse.org/t/copy-workflow-step-names/409410/3?silent=true) - **@Moin** shared a trick for [choosing sidebar icons](https://meta.discourse.org/t/how-to-choose-icons-for-links-in-custom-section/294219/11?silent=true), flagged a potential bug with [calendar settings](https://meta.discourse.org/t/creating-and-managing-calendars/283773/21?silent=true), and reported an issue with the [fullscreen chat on Android tablets](https://meta.discourse.org/t/the-fullscreen-chat-container-on-android-tablets-is-too-tall/410038/2?silent=true). [read more](https://meta.discourse.org/t/creating-and-managing-calendars/283773/21?silent=true) - **@Tannerabread** is actively investigating the [admin sidebar bug](https://meta.discourse.org/t/admin-seitenleiste-nicht-mehr-vorhanden/409913/17?silent=true) and is [trying to reproduce the jittery keyboard issue](https://meta.discourse.org/t/jittery-keyboard-in-languages-i-understand-input-box-on-mobile/409628/2?silent=true) on mobile. [read more](https://meta.discourse.org/t/admin-seitenleiste-nicht-mehr-vorhanden/409913/17?silent=true) - **@NateDhaliwal** provided feedback on the [Expansion of Discussions](https://meta.discourse.org/t/expansion-of-discussions-in-discourse/410059/2?silent=true) topic, updated the link for the [TL3 Progress plugin](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543/30?silent=true), and is also trying to reproduce the [keyboard issue](https://meta.discourse.org/t/jittery-keyboard-in-languages-i-understand-input-box-on-mobile/409628/3?silent=true). [read more](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543/30?silent=true) - **@Chapoi** announced the move of [AI title suggestions to the composer helper](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/1?silent=true). [read more](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/1?silent=true) * * * Today’s Meta activity was a whirlwind of innovation and troubleshooting, all leading to a better platform for everyone! Looks like the only thing not being sub-contracted out to an AI subagent is the coffee run, but we’re sure that feature is in the works. ☕ ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月16日 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/956 "2026-08-16T21:02:27Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, the community produced **50 new posts** across **23 new topics** , demonstrating solid engagement. **Top contributors (by likes and posts):** | User | Likes | Posts | | --- | --- | --- | | @Asa | 4 | 1 | | @Ethsim2 | 3 | 3 | | @Don | 3 | 1 | | @Sk-Or-V1-Contents | 2 | 6 | | @Andrew_Bond | 2 | 1 | These users sparked meaningful conversations across the board. * * * ## Interesting Topics ### #Theme component - @Don confirmed an [update to the Quick Profile Links Menu component](https://meta.discourse.org/t/-/338591/40?silent=true), fixing the issue reported by @Asa. [See the reply](https://meta.discourse.org/t/-/338591/40?silent=true) and [original inquiry](https://meta.discourse.org/t/-/338591/1?silent=true) for context on the improvement. - @Asyntai [introduced the Asyntai AI Chatbot component](https://meta.discourse.org/t/-/410164/1?silent=true), which places an AI assistant in the corner of your forum, answering questions in over 80 languages from your content. The component is free and compatible with Discourse 3.5, with a [preview and install repository](https://github.com/asyntai/discourse-asyntai-chatbot). [Learn more about the topic](https://meta.discourse.org/t/-/410164/1?silent=true). ### #Self-hosting - @Ethsim2 [detailed their setup of Caddy in front of Discourse’s nginx](https://meta.discourse.org/t/-/410123/1?silent=true) to provide HTTP/3 on a self-hosted forum, sparking discussion on alternatives and optimizations. @Pfaffman [pointed to a relevant PR](https://meta.discourse.org/t/-/410123/2?silent=true), while @Satonotdead [mentioned nginx’s native QUIC support](https://meta.discourse.org/t/-/410123/5?silent=true). [Read the full exchange](https://meta.discourse.org/t/-/410123/1?silent=true). - @Sigmike asked whether anyone has [deployed Discourse with Kamal](https://meta.discourse.org/t/-/410153/1?silent=true), noting that Kamal’s zero-downtime deploys might mitigate the standalone template’s downtime. [Join the discussion](https://meta.discourse.org/t/-/410153/1?silent=true). ### #Announcements - In the [Composer Redesign test thread](https://meta.discourse.org/t/-/407849/43?silent=true), @Sterretje reported the new composer consumes vertical space, @Nickdb encountered mermaid plugin issues with a workaround (toggle to markdown), and @Sk-Or-V1-Contents confirmed a fix to the keyboard-related minus button. The discussion continues with feedback from testers. [View @nickdb’s observations](https://meta.discourse.org/t/-/407849/44?silent=true) and [@sk-or-v1-contents’s update](https://meta.discourse.org/t/-/407849/45?silent=true). - On [PostgreSQL 18 upgrade for self-hosters](https://meta.discourse.org/t/-/406194/70?silent=true), @Saiano recounted collation errors and was advised to consider fresh installs, citing staff guidance to test and have a rollback plan; @Andrew_Rowe asked about disk space and version details. [Read the exchange](https://meta.discourse.org/t/-/406194/68?silent=true). ### #Sysadmins - @Andrew_Bond [shared a refactored XenForo 2.3 to Discourse import script](https://meta.discourse.org/t/-/45232/141?silent=true), supporting custom fields, PMs, media galleries, and resources. Tested on a 750k-post forum, the script includes mount points and robust handling. [Dive into the breakdown](https://meta.discourse.org/t/-/45232/141?silent=true). ### #bug - @Per1234 [reported a workflow modal bug](https://meta.discourse.org/t/-/410129/1?silent=true) where the modal appears in every open tab and must be closed individually, showing a misleading error when acting on duplicates. @Slate [confirmed the behavior](https://meta.discourse.org/t/-/410129/2?silent=true). [See the full report](https://meta.discourse.org/t/-/410129/1?silent=true). - @Roke_Julian_Lockhart [clarified the 0 visibility issue inside 1](https://meta.discourse.org/t/-/410078/3?silent=true), showing examples where the code background is missing. @Sk-Or-V1-Contents [suggested checking theme components](https://meta.discourse.org/t/-/410078/2?silent=true). [View the topic](https://meta.discourse.org/t/-/410078/1?silent=true). ### #Support - @AkarinLiu [asked how to remove a bot with admin privileges](https://meta.discourse.org/t/-/410144/1?silent=true). The community identified the bot as a leftover `discourse-bot` user and suggested revoking admin via Rails console; @Sk-Or-V1-Contents [clarified the distinction from discobot](https://meta.discourse.org/t/-/410144/9?silent=true), while @Satonotdead [provided console commands and a warning](https://meta.discourse.org/t/-/410144/10?silent=true). [Follow the saga](https://meta.discourse.org/t/-/410144/1?silent=true). - @Jonathan5 [shared a fix for configuring AWS SNS topic ARN allowlist](https://meta.discourse.org/t/-/406734/6?silent=true), which @Deenius confirmed working after correcting the URL format. [Read the resolution](https://meta.discourse.org/t/-/406734/6?silent=true). ### #Feature - @Twofoursixeight [proposed a feature to permanently clear notifications](https://meta.discourse.org/t/-/410141/1?silent=true), suggesting a “clear all” button or per-notification dismiss-and-remove. [Share your thoughts on notifications](https://meta.discourse.org/t/-/410141/1?silent=true). ### #General - @OS_Corsair asked if [Discourse works on Lynx or SeaMonkey browsers](https://meta.discourse.org/t/-/410160/1?silent=true). @Merefield [responded](https://meta.discourse.org/t/-/410160/2?silent=true) that only the major browsers are supported, but challenges users to test and report. [Discuss browser compatibility](https://meta.discourse.org/t/-/410160/1?silent=true). ### #Plugin - @Hellekin [reported issues with Peertube Live embedding in Discourse Calendar and Events](https://meta.discourse.org/t/-/97376/612?silent=true), noting the livestream chat no longer appears as expected. [Investigate the plugin behavior](https://meta.discourse.org/t/-/97376/612?silent=true). - @Merefield [announced cache optimizations in the Discourse Chatbot plugin](https://meta.discourse.org/t/-/256652/1127?silent=true) via a [PR](https://github.com/merefield/discourse-chatbot/pull/172), aiming to reduce API costs. [Read the optimization details](https://meta.discourse.org/t/-/256652/1127?silent=true). ### #Self-hosting (continued) - @Thomas_Rother [suggested using Hetzner’s S3-compatible object storage](https://meta.discourse.org/t/-/148916/510?silent=true) for EU-DSGVO compliance, providing example configuration. Hetzner’s storage is ISO 27001 certified. [See the post](https://meta.discourse.org/t/-/148916/510?silent=true). ### #development - @Jahan_Gagan asked about [replacing the deprecated 3 with new APIs for overriding Composer#save](https://meta.discourse.org/t/-/410125/1?silent=true), seeking guidance on delegating to the original method using `addModelMethod`. [Explore the development question](https://meta.discourse.org/t/-/410125/1?silent=true). ### #Migration - @Mattash [asked for updates on PHPBB migration speed optimization tools](https://meta.discourse.org/t/-/403319/19?silent=true). [Check the status](https://meta.discourse.org/t/-/403319/19?silent=true). ### #wordpress - @Slate provided [a bash one-liner to find topics missing X-Robots-Tag](https://meta.discourse.org/t/-/403109/11?silent=true) after issues with WordPress embeds. The script also warns about checking canonical separately. [Use the tip](https://meta.discourse.org/t/-/403109/11?silent=true). ### #bug (continued) - @Blalor [reported that Reply button not visible on iOS PWA persists and is linked to Safari PWA zooming](https://meta.discourse.org/t/-/403662/7?silent=true), reaffirming the bug after an update. [Read the original issue](https://meta.discourse.org/t/-/403662/1?silent=true). - @Blalor [also updated the Safari PWA zooming bug topic](https://meta.discourse.org/t/-/407806/8?silent=true) with the issue still present after updating; @Moin suggested tracking the latest branch since it might not be backported. [Discuss the fix](https://meta.discourse.org/t/-/407806/8?silent=true). ### #Support (continued) - @Nacho_Caballero [shared a detailed report on unicorn reloads dropping traffic](https://meta.discourse.org/t/-/410127/1?silent=true), with Claude-generated diagnosis and a suggested fix, asking for community sanity check. [Review the technical issue](https://meta.discourse.org/t/-/410127/1?silent=true). * * * ## Activity by the @Team Group In the last 24 hours, the @Team group participated in the Caddy configuration discussion. @Pfaffman [pointed to a PR on Discourse Docker](https://meta.discourse.org/t/-/410123/2?silent=true) that addresses HTTP/3 support, providing helpful context for @Ethsim2's setup. No other official team members posted in the selected threads, but the topic remains active and waiting for input. [See the full thread](https://meta.discourse.org/t/-/410123/1?silent=true) for team involvement. * * * _From battling bots to polishing Caddy setups, a day filled with fine-tuning and troubleshooting—may your deploys always be zero-downtime!_ ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2026年八月17日 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/957 "2026-08-17T21:01:34Z")
## Today on [meta.discourse.org](http://meta.discourse.org)… **Date:** August 17, 2026 * * * ### Key Stats Over the past 24 hours, the community has been buzzing with **51 new topics** and **165 new posts** , accumulating **150 likes** across all contributions. The most active members this period were: | User | Likes | Posts | | --- | --- | --- | | @NateDhaliwal | 18 | 13 | | @Merefield | 15 | 11 | | @Moin | 13 | 10 | | @Scoresby | 11 | 11 | | @Chapoi | 10 | 7 | | @Nickdb | 8 | 4 | | @Twofoursixeight | 8 | 4 | | @Martin | 7 | 6 | | @HAWK | 7 | 3 | | @Satonotdead | 4 | 7 | * * * ### Interesting Topics We’ve grouped the most engaging discussions by category. Each topic includes a brief summary and a direct link. #### Community Building - **Can money be the only moderator of a forum?** — @Scoresby proposed a radical idea where posts, replies, and upvotes cost small fees, with ranking determined by community investment. @Nickdb and @Merefield were skeptical, pointing out financial divides and the expectation of free internet, while @NateDhaliwal and @Andrew_Rowe explored virtual “topic bucks” and gamification mechanics as middle grounds. [view topic](https://meta.discourse.org/t/can-money-be-the-only-moderator-of-a-forum/410209?silent=true) #### Plugin - **See TL3 Progress** — @NateDhaliwal released a new plugin that shows TL2 users a detailed progress bar toward TL3, including optional warnings and breakdowns. The community quickly tested it, with @Lilly spotting a missing summary (later fixed). [view topic](https://meta.discourse.org/t/see-tl3-progress/410166?silent=true) #### General - **Does discourse work on the lynx browser or the sea monkey browser?** — @OS_Corsair asked about legacy browsers. @Twofoursixeight explained Lynx’s text-only limitations and linked to a plugin for older browsers, while @Merefield showcased `termcourse` for terminal-based Discourse access. [view topic](https://meta.discourse.org/t/does-discourse-work-on-the-lynx-browser-or-the-sea-monkey-browser/410160?silent=true) #### Support - **Configuring Discourse AI with internal OpenAI APIs** — @Soumya_Ranjan_Mishra sought help using an OpenAI-compatible internal endpoint. @Falco suggested choosing the `openai` provider, but the user hit errors. @Kddkd shared configuration screenshots and troubleshooting steps, while @Moin advised checking logs for more detail. [view topic](https://meta.discourse.org/t/configuring-discourse-ai-with-internal-openai-apis/410238?silent=true) #### Announcements - **Granular group-based permissions for anonymous and logged in users** — @Martin continued the rollout discussion, clarifying that `anonymous_users` and `logged_in_users` groups are usable now and that a dedicated topic tracks remaining work. @Moin raised UI visibility issues when the feature is disabled. [view topic](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273?silent=true) - **AI title suggestions move to composer helper** — @Jaroslav.Kovar reported declining usage after moving the AI suggestion star into the combobox, a sentiment echoed by @Satonotdead. @Chapoi noted the feedback and @Jagster shared a user-perspective screenshot. [view topic](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074?silent=true) #### Theme component - **Asyntai AI Chatbot** — @Asyntai introduced a theme component that adds an AI chat assistant based on your own content. @Moin questioned why they tested on the outdated Discourse 3.5, prompting a response about compatibility. [view topic](https://meta.discourse.org/t/asyntai-ai-chatbot/410164?silent=true) #### Announcements - **Better insights into your community with the redesigned admin dashboard** — @Skodde criticized the new dashboard for hiding version/backup info behind the Docker Manager plugin and asked for a classic block. @Chapoi confirmed that a solution is in the works. [view topic](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528?silent=true) - **PostgreSQL 18 update for self-hosters** — @Saiano shared collation mismatch issues during upgrade, and @Chrisr explained that dump-and-restore is the safer path, with collation warnings being benign. @Jonathan5 confirmed a successful upgrade after following the guidance. [view topic](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194?silent=true) #### Self-hosting - **Caddy in front of app’s Nginx via Docker Compose** — @Ethsim2 corrected earlier advice about HTTP/3 and 0-RTT, noting that disabling 0-RTT wasn’t necessary for fixing client-IP issues. @Satonotdead mentioned vanilla nginx can also do HTTP/3, and @Ethsim2 compared both approaches. [view topic](https://meta.discourse.org/t/caddy-in-front-of-app-s-nginx-via-docker-compose/410123?silent=true) #### Feature - **Feature request: Removing notifications** — @Twofoursixeight asked for the ability to permanently delete notifications. @Chapoi clarified that a dismiss button already exists, and the request may be about making the list empty after dismissal. [view topic](https://meta.discourse.org/t/feature-request-removing-notifications/410141?silent=true) #### Bug - **Footnote popup on mobile is partially off‑screen and does not scroll; long footnotes cannot be viewed** — @Serkhelesheyi reported a UI bug where footnote popups are cut off on mobile. @Moin noted a recent fix (in a prior topic) and suggested updating the instance, which resolved the issue for the reporter. [view topic](https://meta.discourse.org/t/footnote-popup-on-mobile-is-partially-off-screen-and-does-not-scroll-the-long-footnotes-cannot-be-viewed/410196?silent=true) #### Sysadmins - **Migrate a XenForo forum to Discourse** — @Andrew_Bond shared a comprehensive import script for XF 2.3, covering users, PMs, media, and more, with performance notes on a 750k-post forum. Community members discussed tweaks and troubleshooting. [view topic](https://meta.discourse.org/t/migrate-a-xenforo-forum-to-discourse/45232?silent=true) #### Support - **My Discourse forum deindexed from Google** — @Cnrtechspot.Com worried about being “Crawled – but not indexed”. @Chapoi reassured them this is normal for new sites and linked to expert advice, while the user pondered the impact of category homepage layouts on SEO. [view topic](https://meta.discourse.org/t/my-discourse-forum-deindexed-from-google/410177?silent=true) #### Feature - **Feedback for Ask Discourse** — @Twofoursixeight highlighted that many sidebar links on [ask.discourse.com](http://ask.discourse.com) lead to useless pages for regular users, suggesting they be hidden. @HAWK explained the default URL hides those, but @Twofoursixeight demonstrated ways to access them accidentally. [view topic](https://meta.discourse.org/t/feedback-for-ask-discourse/336805?silent=true) * * * ### Activity by the @Team Group The Discourse team has been very active, weighing in on multiple threads with valuable feedback and updates. - **@Martin** continued driving the granular group permissions work, posting a detailed roadmap in “[The road to stable, then permanent, for granular\_anonymous\_and\_logged\_in\_groups\_permissions](https://meta.discourse.org/t/the-road-to-stable-then-permanent-for-granular-anonymous-and-logged-in-groups-permissions/410178?silent=true)” and clarifying the behavior of `anonymous_users` and `logged_in_users` in the [original permissions topic](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273?silent=true). He also answered questions about the unified new view in [Introducing the unified new view for the topic list](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728?silent=true). - **@Chapoi** acknowledged feedback on the AI title suggestions relocation (noting it in [AI title suggestions move to composer helper](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074?silent=true)), confirmed that dashboard improvements are underway in [Better insights into your community with the redesigned admin dashboard](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528?silent=true), and reassured a user about Google indexing in [My Discourse forum deindexed from Google](https://meta.discourse.org/t/my-discourse-forum-deindexed-from-google/410177?silent=true). He also clarified notification dismissal behavior in [Feature request: Removing notifications](https://meta.discourse.org/t/feature-request-removing-notifications/410141?silent=true). - **@Moin** provided helpful insights on multiple fronts: he suggested the `openai` provider in [Configuring Discourse AI with internal OpenAI APIs](https://meta.discourse.org/t/configuring-discourse-ai-with-internal-openai-apis/410238?silent=true), flagged a plugin testing an old Discourse version in [Asyntai AI Chatbot](https://meta.discourse.org/t/asyntai-ai-chatbot/410164?silent=true), explained group mention limits in [Open pingable group that anyone can join or leave](https://meta.discourse.org/t/open-pingable-group-that-anyone-can-join-or-leave/410168?silent=true), and pointed out a recent fix for the footnote popup in [Footnote popup on mobile is partially off‑screen and does not scroll](https://meta.discourse.org/t/footnote-popup-on-mobile-is-partially-off-screen-and-does-not-scroll-the-long-footnotes-cannot-be-viewed/410196?silent=true). He also contributed to discussions on ghost bots in [How to delete a ghost bot with admin rights](https://meta.discourse.org/t/topic/410144?silent=true) and suggested edits in [Report Content to Group](https://meta.discourse.org/t/report-content-to-group/249323?silent=true). - **@HAWK** added a humorous touch to the money-forum debate with “Discoin” in [Can money be the only moderator of a forum?](https://meta.discourse.org/t/can-money-be-the-only-moderator-of-a-forum/410209?silent=true), explained the Ask Discourse default URL in [Feedback for Ask Discourse](https://meta.discourse.org/t/feedback-for-ask-discourse/336805?silent=true), and helped with the bot-removal issue in [How to delete a ghost bot with admin rights](https://meta.discourse.org/t/topic/410144?silent=true). - **@Zogstrip** confirmed fixes for two bugs: the invisible code inside `` in [8 is invisible, solely when directly inside 9](https://meta.discourse.org/t/code-is-invisible-solely-when-directly-inside-small/410078?silent=true) and the workflow modal issue in [Workflow modal must be closed in every Discourse tab](https://meta.discourse.org/t/workflow-modal-must-be-closed-in-every-discourse-tab/410129?silent=true). - **@Lindsey** answered questions about the admin dashboard in [Ask me anything about the new admin dashboard](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830?silent=true), suggesting the `/about` page for community-visible stats. - **@Danielle** shared upcoming webinar plans in [Webinar: Community Retention: How to Define and Drive Return Behavior](https://meta.discourse.org/t/webinar-community-retention-how-to-define-and-drive-return-behavior/401266?silent=true). - **@Awesomerobot** responded to a question about app permissions in [Discourse asked for Permission to access other apps?](https://meta.discourse.org/t/discourse-asked-for-permission-to-access-other-apps/410063?silent=true) and offered alternative APIs for overriding composer save in [Recommended replacement for modifyClass(“model:composer”)](https://meta.discourse.org/t/recommended-replacement-for-modifyclass-model-composer-when-overriding-save/410125?silent=true). - **@Chrisr** clarified the PostgreSQL upgrade process and collation warnings in [PostgreSQL 18 update for self-hosters](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194?silent=true). * * * That’s all for today! If money can’t buy you love, at least it can’t buy you a forum moderation system… yet. But we hear the next big plugin might charge per like 😉 Happy posting! [上一頁](https://meta.discourse.org/t/daily-summary-9pm-utc/291850.md?page=34) [下一頁](https://meta.discourse.org/t/daily-summary-9pm-utc/291850.md?page=36)