# Résumé quotidien (13h UTC)
**URL:** https://meta.discourse.org/t/daily-summary-1pm-utc/291852
**Category:** Forum summaries
**Created:** [Janvier 16, 2024, 10:00 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852 "2024-01-16T22:00:28Z")
**Posts on this page:** 20
**Page:** 35
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 3, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/908 "2026-08-03T13:01:19Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
In the past 24 hours, there have been **30 new topics** and **106 new posts** across [meta.discourse.org](http://meta.discourse.org), drawing **103 likes**. The top contributors by likes this period were:
- **@Chrisr** — 17 likes, 5 posts
- **@Merefield** — 12 likes, 12 posts
- **@Ed_S** — 9 likes, 7 posts
- **@Canapin** — 8 likes, 4 posts
- **@Mcwumbly** — 8 likes, 4 posts
- **@Lilly** — 7 likes, 10 posts
- **@NateDhaliwal** — 6 likes, 6 posts
- **@Jagster** — 5 likes, 7 posts
- **@Kjell** — 5 likes, 1 post
- **@One1** — 3 likes, 3 posts
* * *
## Interesting Topics
### #Announcements
- **PostgreSQL 18 upgrade for self-hosters** — @Chrisr announced the rollout of PostgreSQL 18 in the Discourse Docker image, with detailed instructions for single-container and data-container setups, plus warnings about disk space (the check now requires **2x** the DB size in free space). Commenters hit issues ranging from `pg_dump` failing on single-CPU hosts ([@nachocaballero](https://meta.discourse.org/t/-/406194/11?silent=true), [@Ivan\_Rapekas](https://meta.discourse.org/t/-/406194/10?silent=true)) to upgrade-loop recovery paths ([@chrisc](https://meta.discourse.org/t/-/406194/13?silent=true)); @Chrisr fixed the core-count detection to use `nproc --ignore=1`. [read more](https://meta.discourse.org/t/-/406194/1?silent=true)
### #ux
- **Where did the version information go?** — @Kjell and others questioned why the redesigned admin dashboard dropped version/technical info, with @Ed_S feeling it’s “marketing-led” over engineering-led. @Lilly observed the dashboard is now geared to “community managers,” and @Mcwumbly explained the team’s intent to consolidate version details into the “Manage updates” page. [read more](https://meta.discourse.org/t/-/407416/5?silent=true)
- **I don’t see the red line for last visit** — @Ed_S briefly feared the “red line” indicating unread posts had been removed, but @Lilly and @Canapin confirmed it still displays normally; @NateDhaliwal noted a transient miss after a page refresh but it returned. [read more](https://meta.discourse.org/t/-/409097/1?silent=true)
### #development
- **Clarifying the ‘posts read’ TL3 promotion logic** — @NateDhaliwal struggled to understand why the TL3 requirement multiplied posts by a percentage and took a minimum; @Mcwumbly explained that `tl3_requires_posts_read` is a _percentage_ bounded by a cap, making the math clear. [read more](https://meta.discourse.org/t/-/409057/1?silent=true)
- **Now in Beta: Plugin to see TL3 Progress for TL2 users** — @EricGT raised a nuanced edge case: muted categories can inflate the “posts read” requirement. He proposed a category-by-category breakdown in the plugin to show eligible vs. read posts, which @NateDhaliwal noted core itself lacks. [read more](https://meta.discourse.org/t/-/408543/24?silent=true)
### #Self-hosting
- **Any cheaper alternatives to Hetzner?** — @Lilly, @Merefield, and @Jagster dug into running Discourse on minimal hardware. @Jagster shared real-world numbers from a 4-vCPU / 8GB server running a dual-container setup with 1000–1500 daily visitors and needing 4GB swap during rebuilds; @Merefield suggested 3+ cores for dual-container comfort. [read more](https://meta.discourse.org/t/-/409037/18?silent=true)
- **Configure a supported tracking branch to get Discourse software updates** — @Ghorbani questioned whether `git pull` remains necessary in the daily upgrade workflow. @David confirmed it’s effectively redundant—launcher auto-detects and pulls the latest commit—though @Ed_S prefers to play it safe and run it anyway. [read more](https://meta.discourse.org/t/-/17014/35?silent=true)
### #Praise
- **Dependent Plugin Settings are … AWESOME!** — @Merefield showcased the new dependent settings feature (settings visible only when relevant), calling it “✨ fantastic” for reducing plugin config clutter and cognitive load. He shared pointers to the schema docs and examples from the Chatbot plugin’s `settings.yml`. [read more](https://meta.discourse.org/t/-/409148/1?silent=true)
### #Support
- **Hola, me gustó el theme actual que tiene Discourse** — @Picho_Pelis asked about Meta’s branded theme; @Canapin explained it’s not public, linking to prior discussion about the custom nature of Meta’s look. [read more](https://meta.discourse.org/t/-/409101/1?silent=true)
- **Cannot view post preview in mobile composer?** — @FishHead reported that the rich text editor toggle fails on markdown like `[color=red]`. @Chapoi said the plan is to improve the toggle and only re-instate the preview button if that proves insufficient, recommending the community [Mobile Composer Preview](https://meta.discourse.org/t/mobile-composer-preview/408784?silent=true) component for now. [read more](https://meta.discourse.org/t/-/408352/18?silent=true)
- **Unable to switch accounts—Sign In automatically logs into the previous account** — @FlowCaffe described getting locked out of an admin account in Chrome; @Pfaffman explained the Discourse ID single-sign-in flow, suggesting a logout at `id.discourse.com` or impersonation via the Admin user page. [read more](https://meta.discourse.org/t/-/409100/1?silent=true)
- **What happened to claiming reviewables?** — @Darkpixlz couldn’t find the “claim” button in the review queue. @Lilly and @Moin traced it to an admin site setting (now optional), and @Darkpixlz confirmed that solved it. [read more](https://meta.discourse.org/t/-/409099/1?silent=true)
### #Feature
- **Add interface preferences to individually hide Suggested and Related topics** — @Akanora proposed two separate user-level toggles (hide Suggested / hide Related) to reduce clutter, explaining his choice might vary per-community; @Mcwumbly asked probing follow-ups about real-world usage patterns. [read more](https://meta.discourse.org/t/-/409086/1?silent=true)
### #Plugin
- **Discourse Chatbot 🤖** — @Merefield published a comprehensive PR round-up for the Chatbot plugin (v2.4.1), covering new local reasoning strategies, a semantic blocked-question gate using embedding similarity, replacement of the unsafe SafeRuby evaluator with Dentaku, and adoption of Zeitwerk loading. [read more](https://meta.discourse.org/t/-/256652/1124?silent=true)
- **Discourse Workflows** — @Sam announced a new PR adding interaction API support to Discourse Workflows and invited testing in a trial environment; @Eviepayne also left feature-gap notes (e.g., missing pagination in the HTTP request block). [read more](https://meta.discourse.org/t/-/407100/13?silent=true)
* * *
## Activity by the @Team Group
- **@Chrisr** posted the flagship [PostgreSQL 18 upgrade guide](https://meta.discourse.org/t/-/406194/1?silent=true), then worked through the comments: correcting the disk-space check to 2x DB size, fixing the single-CPU `pg_dump` job count bug, and explaining how to postpone or recover from failed upgrades. [read more](https://meta.discourse.org/t/-/406194/6?silent=true)
- **@Mcwumbly** provided the canonical explanation of the TL3 “posts read” percentage calculation and cap, and offered a thoughtful breakdown of why the admin dashboard now targets “community manager” vs. “sysadmin” hats, directing users to the “Manage updates” page for version info. [read more](https://meta.discourse.org/t/-/409057/2?silent=true) | [read more](https://meta.discourse.org/t/-/407416/19?silent=true)
- **@Chapoi** responded to UI feedback in two threads: confirming the rich-text-editor preview toggle is being improved (with a third-party component as a temporary patch) and clarifying that the Welcome Banner is intentionally hidden on small screens, including a CSS snippet to override it. [read more](https://meta.discourse.org/t/-/408352/19?silent=true) | [read more](https://meta.discourse.org/t/-/409078/4?silent=true)
- **@David** clarified that `./launcher` automatically pulls the latest `discourse_docker` commit, making a manual `git pull` unnecessary in standard workflows. [read more](https://meta.discourse.org/t/-/17014/39?silent=true)
- **@Sam** acknowledged Daily Summary feedback and committed to a validation rework (“may take a week or 2”), and also shepherded a new Workflows PR adding interaction API support. [read more](https://meta.discourse.org/t/-/291853/298?silent=true) | [read more](https://meta.discourse.org/t/-/407100/13?silent=true)
- **@Tgxworld** stepped in on the Spanish-language install thread to tell @Picho_Pelis that a recently pushed bug had been fixed and a `launcher rebuild app` should resolve the `postgresql.conf` failure. [read more](https://meta.discourse.org/t/-/409113/3?silent=true)
- **@Pfaffman** diagnosed an account-switching lockout caused by Discourse ID single sign-on, suggesting logout at `id.discourse.com` or admin impersonation as workarounds. [read more](https://meta.discourse.org/t/-/409100/2?silent=true)
* * *
Between the PostgreSQL 18 migration drama, a flood of Chatbot PRs, and a detour into music theory, it seems even the most technical days on meta can still end with a tune! 🎶
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 4, 2026, 1:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/909 "2026-08-04T13:02:17Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
It’s been an action-packed 24 hours on the meta. From a major self-hosting upgrade to AI API additions and even some off‑topic music talk, the community has been buzzing. Here’s the daily digest.
* * *
## Key Stats
- **178 new posts** and **46 new topics** were created in the last day.
- **249 likes** were given across those posts.
**Top users by posts and likes:**
- @Merefield — 15 posts, 44 likes
- @Chrisr — 7 posts, 23 likes
- @HAWK — 6 posts, 18 likes
- @Falco — 5 posts, 17 likes
- @Ed_S — 10 posts, 12 likes
- @Pfaffman — 4 posts, 11 likes
- @Moin — 6 posts, 10 likes
- @Sandra.Mccollum — 9 posts, 9 likes
- @Mcwumbly — 5 posts, 8 likes
- @Chapoi — 5 posts, 7 likes
* * *
## Interesting Topics
### #Announcements
The big news of the day was the [PostgreSQL 18 upgrade for self‑hosters](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/1?silent=true), announced by @Chrisr. The upgrade is now in the Docker image and requires ~2x database size free disk space. Many users shared their experience: @Richie watched the migration live with a shell command, @Sandra.Mccollum hit a snag that was resolved by manual steps, and @Pfaffman reported successful upgrades via his dashboard. The thread also covers workarounds for single‑CPU hosts and changing locale provider [read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/34?silent=true).
In the same category, the [emphasized admin dashboard redesign](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528/1?silent=true) is attracting feedback. @Kjell misses the quick access to version info and disk space, and @Lilly simply reverted to the old dashboard on her sites. @Mcwumbly points to a related discussion about the missing version info [read more](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528/46?silent=true).
Finally, @Sam announced the [Gemini Interactions API](https://meta.discourse.org/t/gemini-interactions-api/409240/1?silent=true) support in Discourse AI. The new provider adds tool call streaming, code execution, and Google Maps integration, replacing the legacy `generateContent` API for new setups [read more](https://meta.discourse.org/t/gemini-interactions-api/409240/1?silent=true).
### #Praise
A short but sweet topic celebrated the new [dependent plugin settings feature](https://meta.discourse.org/t/dependent-plugin-settings-are-awesome/409148/1?silent=true). @Merefield demonstrated how these settings hide irrelevant configuration options in Chatbot, calling it “really chef’s kiss”. @NateDhaliwal asked for docs, and @Merefield linked to the official schema and specs [read more](https://meta.discourse.org/t/dependent-plugin-settings-are-awesome/409148/3?silent=true).
### #Feature
The [username template parameter in AI personas](https://meta.discourse.org/t/add-username-as-a-template-param-in-ai-persona-system-prompts/406846/1?silent=true) was merged into core. @Falco merged the PR, but @Sam later warned about potential system prompt churn in multi‑user chains. He also noted that some hosted models currently discard the name field and that a patch is in the works [read more](https://meta.discourse.org/t/add-username-as-a-template-param-in-ai-persona-system-prompts/406846/8?silent=true).
Another feature request, [suppress notifications for tag changes](https://meta.discourse.org/t/allow-to-suppress-notifications-for-tag-changes/409242/1?silent=true) from @Steradiant, quickly received a pointer from @Moin to existing site settings `disable_tags_edit_notifications` and `disable_category_edit_notifications`, as well as the bulk tagging modal’s notification checkbox [read more](https://meta.discourse.org/t/allow-to-suppress-notifications-for-tag-changes/409242/2?silent=true).
### #Support
Several users reported problems after the PG18 update. @Sandra.Mccollum’s site initially went down; she fixed it by manually updating PostgreSQL and libvips inside the container, and later successfully upgraded her second site via CLI instead of the web UI [read more](https://meta.discourse.org/t/latest-update-this-morning-08-3-2026-broke-my-discourse-is-it-just-me/409155/9?silent=true). @Ed_S suggested that the web‑based updater may only do a single rebuild, which might not be enough for a DB major version bump [read more](https://meta.discourse.org/t/latest-update-this-morning-08-3-2026-broke-my-discourse-is-it-just-me/409155/7?silent=true).
In another thread, @Scavin asked about [database cleanup before the PG18 upgrade](https://meta.discourse.org/t/database-cleanup-before-postgresql-18-upgrade-recommended-retention-period-for-log-statistics-tables/409130/1?silent=true). @Ed_S clarified that the needed free space is now 2x, and @Falco noted that tables like `ai_api_audit_logs` have retention settings, while `incoming_links` and `topic_views` are meant to be kept forever [read more](https://meta.discourse.org/t/database-cleanup-before-postgresql-18-upgrade-recommended-retention-period-for-log-statistics-tables/409130/3?silent=true).
On the mobile front, @FishHead [cannot view post preview in the mobile composer](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352/18?silent=true) because the rich text editor doesn’t support some Markdown extensions like color tags. @Chapoi acknowledged the limitation and said the toggle might be improved, or the preview button reinstated later [read more](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352/19?silent=true).
A more exotic support issue involved using a Unix socket between Caddy and Discourse, leading to `PG::InvalidTextRepresentation` errors. @Willy shared his config, @Falco diagnosed a proxy misconfiguration, and @Willy eventually suspected a stale socket after rebuilds [read more](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).
### #Community Building
A lively discussion on the [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/76?silent=true) was sparked by @HAWK’s AI agent analysis. He argued that communities with direct audience relationships are better insulated from search volatility. @Nickdb and @Tris20 chimed in on AI hallucinations, while @Nathank shared that he uses [ask.discourse.org](http://ask.discourse.org) for quick answers and only returns to meta for complex questions [read more](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/78?silent=true).
In the same category, @HAWK also posted about [scalable engagement models](https://meta.discourse.org/t/scalable-engagement-models/409187/1?silent=true) like webinars and office hours, asking for other one‑to‑many formats. @Mcwumbly highlighted how feature announcements are usually made by the people who built them, which invites direct community feedback [read more](https://meta.discourse.org/t/scalable-engagement-models/409187/2?silent=true).
### #enterprise
The discussion on scalable engagement was cross‑posted under #enterprise (same topic as above). We grouped it under #Community Building, but since it’s also tagged enterprise, we’ll mention it here: @HAWK’s topic drew practical advice on turning internal knowledge into reusable community sessions [read more](https://meta.discourse.org/t/scalable-engagement-models/409187/1?silent=true).
### #Self-Hosting
@Ghorbani asked about the necessity of `git pull` before rebuilds in the [classic switching‑between‑release‑channels guide](https://meta.discourse.org/t/switching-between-discourse-release-channels-versions/17014/35?silent=true). @David explained that the launcher automatically updates itself, and @Ed_S added that manually running `git pull` is harmless. The OP was updated to reflect modern “channel” terminology [read more](https://meta.discourse.org/t/switching-between-discourse-release-channels-versions/17014/45?silent=true).
### #ux
The [interface for adding users to groups on mobile](https://meta.discourse.org/t/interface-for-adding-users-to-groups-on-mobile-borderline-non-functional/409232/1?silent=true) is borderline non‑functional, as @Stephtara demonstrated with screenshots. @Chapoi confirmed a larger redesign is planned but provided an immediate fix in a PR [read more](https://meta.discourse.org/t/interface-for-adding-users-to-groups-on-mobile-borderline-non-functional/409232/3?silent=true).
Closely related, @Moin raised that the [version information has disappeared](https://meta.discourse.org/t/where-did-the-version-information-go/407416/21?silent=true) from the admin dashboard. While the info exists in the browser console, he argued it should be available in [safe mode](https://meta.discourse.org/t/53504?silent=true) as well, and @Lilly wondered why the update page wasn’t a sufficient replacement [read more](https://meta.discourse.org/t/where-did-the-version-information-go/407416/21?silent=true).
@Mcwumbly started a [topic on improving the “update Discourse” page](https://meta.discourse.org/t/improving-the-update-discourse-page/409245/1?silent=true), inviting ideas. @Asa contributed a detailed breakdown of status states, a version card, and a proposal to distinguish between “up to date”, “a few commits behind”, and “security update” [read more](https://meta.discourse.org/t/improving-the-update-discourse-page/409245/2?silent=true).
### #development
A quick tip for theme developers: @Andrew_Rowe asked how to [inject HTML only on one page](https://meta.discourse.org/t/inject-html-only-on-one-page/409186/1?silent=true). @Awesomerobot shared a Glimmer component using the `router` service and `defaultHomepage()` to conditionally render in the outlet [read more](https://meta.discourse.org/t/inject-html-only-on-one-page/409186/2?silent=true).
### #Plugin
The [Discourse Chatbot](https://meta.discourse.org/t/discourse-chatbot/256652/1124?silent=true) had a major update to v2.4.1, as summarized by @Merefield: new local reasoning strategies, a semantic blocked‑question gate, and a move from SafeRuby to Dentaku for calculations. He also highlighted a security fix for SafeRuby vulnerabilities [read more](https://meta.discourse.org/t/discourse-chatbot/256652/1124?silent=true).
Another plugin, [Resenha](https://meta.discourse.org/t/resenha-add-discord-style-voice-rooms-to-your-community/389056/79?silent=true), got a quick fix for an error when deleting voice rooms. @Satonotdead reported the 500, @Falco merged a PR, and the user confirmed the fix solved it [read more](https://meta.discourse.org/t/resenha-add-discord-style-voice-rooms-to-your-community/389056/81?silent=true).
* * *
## Activity by the @Team Group
- **@Chrisr** played a central role in the **PostgreSQL 18 upgrade** announcement and follow‑up. He explained the disk space requirements, corrected the 3x to 2x, addressed single‑CPU host issues with `nproc --ignore=1`, and gave guidance on postponing the update [post 1](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/1?silent=true), [post 6](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/6?silent=true), [post 30](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/30?silent=true).
- **@Falco** merged the PR for the **username template parameter** in AI personas [post 5](https://meta.discourse.org/t/add-username-as-a-template-param-in-ai-persona-system-prompts/406846/5?silent=true), clarified retention recommendations for database tables [post 3](https://meta.discourse.org/t/database-cleanup-before-postgresql-18-upgrade-recommended-retention-period-for-log-statistics-tables/409130/3?silent=true), and fixed the **Resenha** deletion bug [post 80](https://meta.discourse.org/t/resenha-add-discord-style-voice-rooms-to-your-community/389056/80?silent=true). He also commented on the Caddy/Unix socket issue [post 3](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/3?silent=true).
- **@Sam** announced the **Gemini Interactions API** [post 1](https://meta.discourse.org/t/gemini-interactions-api/409240/1?silent=true) and contributed to the discussion on the username parameter, warning about potential system‑prompt thrashing [post 8](https://meta.discourse.org/t/add-username-as-a-template-param-in-ai-persona-system-prompts/406846/8?silent=true). He also acknowledged plans to improve the daily summary feature [post 298](https://meta.discourse.org/t/daily-summary-feedback/291853/298?silent=true).
- **@Mcwumbly** shared insights on scalable engagement models [post 2](https://meta.discourse.org/t/scalable-engagement-models/409187/2?silent=true), provided a link to the version info discussion [post 47](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528/47?silent=true), started a topic on improving the update page [post 1](https://meta.discourse.org/t/improving-the-update-discourse-page/409245/1?silent=true), and clarified the intent behind an update history view [post 3](https://meta.discourse.org/t/improving-the-update-discourse-page/409245/3?silent=true). He also moved a discussion to a better category [post 5](https://meta.discourse.org/t/where-should-open-ended-discussion-about-the-product-happen/406248/5?silent=true).
- **@David** answered questions in the **release channel switching** guide, explaining that the launcher auto‑updates itself and that manual `git pull` is rarely needed [post 39](https://meta.discourse.org/t/switching-between-discourse-release-channels-versions/17014/39?silent=true), [post 45](https://meta.discourse.org/t/switching-between-discourse-release-channels-versions/17014/45?silent=true).
- **@Zogstrip** helped with two bug reports: he asked for additional context in the **deletion of categories failure** [post 2](https://meta.discourse.org/t/deletion-of-categories-fails/409236/2?silent=true) and acknowledged a fix for the **grace period edits media review bypass** [post 3](https://meta.discourse.org/t/grace-period-edits-bypass-skip-review-media-groups-media-review/408899/3?silent=true). He also noted that deeper changes to the review system would require more planning [post 5](https://meta.discourse.org/t/grace-period-edits-bypass-skip-review-media-groups-media-review/408899/5?silent=true).
- **@Tgxworld** provided a quick “please rebuild again” response to the **installation failure** topic after a recent bug was fixed [post 3](https://meta.discourse.org/t/ayudeme-no-he-podido-instalar/409113/3?silent=true).
- **@Awesomerobot** shared a GLimmer component for conditional HTML injection [post 2](https://meta.discourse.org/t/inject-html-only-on-one-page/409186/2?silent=true), gave advice on password resets with unknown emails [post 2](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), and fixed the **invite restricted** issue with a combined PR [post 3](https://meta.discourse.org/t/invite-restricted-cant-remove/409058/3?silent=true).
- **@Martin** responded to concerns about the new unified topic list view, explaining how unread counts are still available and offering to discuss a user preference for showing replies only [post 39](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728/39?silent=true).
- **@Chapoi** was busy on mobile UX: he acknowledged the group‑adding interface problem and pointed to a PR [post 3](https://meta.discourse.org/t/interface-for-adding-users-to-groups-on-mobile-borderline-non-functional/409232/3?silent=true), commented on the missing preview in the composer [post 19](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352/19?silent=true), reported a fix for the overflow in the activity‑by‑category section [post 3](https://meta.discourse.org/t/activity-by-category-section-overflows-with-long-category-names/409202/3?silent=true), and explained the welcome banner behavior on mobile [post 4](https://meta.discourse.org/t/welcome-banner-shows-on-desktop-but-not-on-mobile/409078/4?silent=true).
* * *
> Yesterday we saw everything from upgrading PostgreSQL to jamming on jazz piano — proving that this community can talk tech and tune‑ups in the same breath, with rhythm and harmony to spare! 🎵
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 5, 2026, 1:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/910 "2026-08-05T13:02:57Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
* * *
## Key Stats
Over the last 24 hours, **196 new posts** were created across **63 topics** , clocking **285 likes** in total. The conversation spanned everything from SSL installation nightmares and PostgreSQL 18 upgrades to AI strategy polls and mobile UX gripes.
**Top users by number of likes received today:**
| User | Likes | Posts |
| --- | --- | --- |
| @HAWK | 18 | 8 |
| @Chapoi | 16 | 11 |
| @Moin | 16 | 11 |
| @Merefield | 16 | 10 |
| @Lilly | 12 | 8 |
| @Sam | 12 | 7 |
| @Satonotdead | 9 | 9 |
| @Falco | 9 | 4 |
| @Stephtara | 8 | 7 |
| @Ed_S | 8 | 2 |
* * *
## Interesting Topics
### #Self-hosting
- @Picho_Pelis opened a [frustrated topic about failing Discourse installations](https://meta.discourse.org/t/ya-estoy-cansado-he-instalado-discourse-en-varios-vps-ninguno-me-funcionan/409294?silent=true) across multiple VPSes, hitting repeated SSL certificate errors (`PEM_read_bio_X509_AUX() failed`). @Merefield suggested validating connectivity to Let’s Encrypt and tailing the `acme.sh.log`, while @Pfaffman diagnosed likely [Let’s Encrypt rate-limiting](https://meta.discourse.org/t/ya-estoy-cansado-he-instalado-discourse-en-varios-vps-ninguno-me-funcionan/409294/20?silent=true) after many failed rebuilds, and recommended trying a `www` subdomain or waiting out the rate limit. @Satonotdead and @Jdc20181 flagged Cloudflare proxying as a common gotcha, which @Picho_Pelis confirmed he’d disabled. The thread wraps with the organizer confirming the domain was blocked by Let’s Encrypt and closing the topic — a helpful walkthrough for anyone about to reinstall.
- @Roke_Julian_Lockhart raised a [question about password resets when users forget their registered email address](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?silent=true), sparked by an experience on another Discourse community (OpenAI) where SSO was silently disconnected. @Southpaw explained that the `hide_email_address_taken` setting (enabled by default) disables the username-based reset form, which @Moin later clarified in the thread. @Roke_Julian_Lockhart subsequently filed a [feature request to always allow username-based password reset](https://meta.discourse.org/t/always-allow-username-based-password-reset/409326?silent=true) — worth a look if your site toggles that setting.
### #Community Building
- @Danielle kicked off a [conversation inviting members to share the story behind their communities](https://meta.discourse.org/t/what-s-the-story-behind-your-community/409282?silent=true). Among the responses, @Jagster described fleeing Facebook groups due to poor moderation; @Canapin shared his experience migrating old forums and the nuances of preserving community knowledge; and @Newkid outlined his real-estate journey community for New Zealand and Australia, complete with a “front door” metaphor @HAWK praised as a great framing.
- The [discussion on drastic drops in Support forum activity](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401?silent=true) continued with @HAWK sharing AI-gathered market intel on search volatility, noting that communities owning direct audience relationships are structurally insulated from search churn. @Nickdb and @Tris20 shared experiences with LLMs fabricating results with conviction; @Nathank mused that traffic will likely be lower but higher quality as AI handles easy questions; and @Satonotdead advised running your own [SearXNG metadata search instance](https://github.com/searxng/searxng) for real results.
### #Announcements
- The [PostgreSQL 18 update for self-hosters](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194?silent=true) thread stayed busy. @Chrisr explained why data checksums are disabled during upgrades (alignment with internal benchmarking, plus a `pg_upgrade` gotcha if checksum settings differ), confirmed PG15 clients remain for backup/restore compatibility, and noted that a future OS upgrade on hosted platforms drove the switch to the new builtin locale provider. @Richie shared a `watch` command to monitor migration progress (his 35GB migration took ~10 minutes), while @Ed_S suggested a `while` loop with `free -h` to preserve output. @Jericson reported that only the default site migrated on his multisite setup, prompting @Pfaffman to share his manual multi-DB approach. @Jimmy0017 asked about bypassing disk space checks and about Google Cloud SQL compatibility.
- @Sam announced [support for the Gemini Interactions API](https://meta.discourse.org/t/gemini-interactions-api/409240/1?silent=true) in Discourse AI, recommending the new `/v1/interactions` endpoint and labeling the old one `Google Gemini (Legacy API)`. The new provider adds tool call streaming, native code execution, and Google Maps integration, alongside existing Search and Fetch tools. One caveat: “no thinking” can no longer be set on 2.5 flash models.
- The [redesigned admin dashboard announcement](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528?silent=true) drew continued feedback. @Kjell lamented missing version info, backup/disk-space indicators, and problem checks; @Lilly suggested keeping the old dashboard for admins alongside the new one; and @Sren-1 noted the Docker manager plugin may have been removed from his install. @Mcwumbly pointed to the [version info discussion](https://meta.discourse.org/t/where-did-the-version-information-go/407416?silent=true) for more context.
### #Support
- @Karthik_K1 reported that [Discourse-ID displayed its own logo and name instead of the forum’s branding](https://meta.discourse.org/t/discourse-id-displays-its-own-logo-name-instead-of-my-forums/409028?silent=true) during login. @Chapoi initially brushed it off as expected behavior, but @Moin's comparison with the related feature request clarified it as a real regression. @Chapoi then prototyped a workaround — clearing `discourse_id_client_id`/`discourse_id_client_secret` in the Rails console and toggling Discourse ID — which resolved it for @Karthik_K1. @Rishabh from the Discourse ID team confirmed a button on the admin config page does the same, though @Chapoi noted the button was disabled on his test site, and discussions continue about making the process clearer for self-hosters.
- @Satonotdead asked [how to update models on LLM agents](https://meta.discourse.org/t/how-to-update-models-on-llm-agents/409274?silent=true); @Falco traced the confusion to the “info” icon in AI chat showing the model used for PM title generation rather than the completion request, and filed an [improvement PR](https://github.com/discourse/discourse/pull/42326) to make that clearer in the UI.
### #ux
- @Stephtara documented [mobile UX problems when adding users to groups](https://meta.discourse.org/t/interface-for-adding-users-to-groups-on-mobile-borderline-non-functional/409232?silent=true) — half-hidden search results, un-findable selected states, plus a tag-selector flow that traps the composer. @Moin linked the related [mobile tag selector topic](https://meta.discourse.org/t/how-i-am-supposed-to-know-how-to-close-the-tag-selector-on-mobile/400390?silent=true), and @Chapoi noted a bigger replacement project is on the backlog with an interim [fix PR](https://github.com/discourse/discourse/pull/42304). @Stephtara also suggested the tag dropdown should roll up when the search field loses focus.
- @Mcwumbly solicited feedback for [improving the “update Discourse” page](https://meta.discourse.org/t/improving-the-update-discourse-page/409245?silent=true). @Asa offered a detailed proposal: distinguish “a few commits behind” (informational, no action needed) from actual release/security signals; bring back the version number prominently; render the cached version check immediately; show an update history with changelog links; display which components need `./launcher rebuild app`; and surface `.discourse-compatibility` plugin pinning. A [live mock](https://dynamic-changi-gne2.pagedrop.io/) was shared for anyone to poke at. @Ed_S added backup advice and a note about posting a CLI rebuild fallback for failed updates.
- In [Where did the version information go?](https://meta.discourse.org/t/where-did-the-version-information-go/407416?silent=true), @Moin noted that `/admin/update` doesn’t work in [safe mode](https://meta.discourse.org/t/53504?silent=true) because it depends on the docker\_manager plugin, making version lookup cumbersome during troubleshooting.
### #Site feedback
- @Lilly flagged a [Meta error banner displaying “MERGE\_BRANCH deployment failed”](https://meta.discourse.org/t/meta-error-banner-merge-branch-deployment-failed/409333?silent=true). @Tgxworld initially confirmed a fix, but @NateDhaliwal reported the banner persisting; @David then explained the root cause — a branch deployment for a test community config leaked the error banner broadly — and confirmed the banner was removed for good, with @Merefield musing on its unusual appearance.
### #enterprise
- @Mae posted a [poll asking how much AI search factors into enterprise community strategy](https://meta.discourse.org/t/how-much-is-ai-search-part-of-your-enterprise-community-strategy-now/409298?silent=true), referencing recent blog posts on LLM visibility, and invited members to share what AI search looks like in practice, the hard parts (content, measurement, or buy-in), and where they stand today.
### #Marketplace
- @T_Müller advertised a [contract role for a Ruby + Discourse specialist](https://meta.discourse.org/t/ruby-discourse-specialist-wanted-contract-remote/409266?silent=true) to lead an integration with an existing Community app at a large US company — covering Okta/OIDC SSO, group mapping, Ruby adapters, webhook pipelines, feature flags, and a cutover/rollback plan. Several users responded with PMs expressing interest.
* * *
## Activity by the @Team Group
- @Sam announced the [Gemini Interactions API](https://meta.discourse.org/t/gemini-interactions-api/409240/1?silent=true), then followed up in the [Discourse AI structured output thread](https://meta.discourse.org/t/discourse-ai-structured-output-response-was-not-valid-json/408821?silent=true) with a [fix PR](https://github.com/discourse/discourse/pull/42339) after @Lilydjwg's detailed report on escaped newlines breaking JSON. He also joined the [regular mode discussion](https://meta.discourse.org/t/regular-mode-for-admins-and-moderators-e-g-something-like-sudo/211617?silent=true) with a thought experiment about inverting admin permissions by default.
- @David and @Tgxworld resolved the [Meta error banner](https://meta.discourse.org/t/meta-error-banner-merge-branch-deployment-failed/409333?silent=true), with @David explaining the leaked branch-deployment config and confirming the fix.
- @Chapoi shipped one [fix PR](https://github.com/discourse/discourse/pull/42304) improving mobile group-member search visibility and another [PR to fix dashboard category-name overflow](https://meta.discourse.org/t/activity-by-category-section-overflows-with-long-category-names/409202?silent=true), while continue investigating the [Discourse-ID branding issue](https://meta.discourse.org/t/discourse-id-displays-its-own-logo-name-instead-of-my-forums/409028?silent=true) across additional forums.
- @Lilly flagged the [Meta deployment banner](https://meta.discourse.org/t/meta-error-banner-merge-branch-deployment-failed/409333?silent=true), provided support in the [VPS SSL saga](https://meta.discourse.org/t/ya-estoy-cansado-he-instalado-discourse-en-varios-vps-ninguno-me-funcionan/409294?silent=true), and noted in the [Bot enter button fix](https://meta.discourse.org/t/bot-enter-button-fix-for-discourse-ai/408513?silent=true) that the component is deprecated because the AI team added native preferences for docked composer control.
- @Merefield provided detailed [Let’s Encrypt connectivity tests and log-tailing advice](https://meta.discourse.org/t/ya-estoy-cansado-he-instalado-discourse-en-varios-vps-ninguno-me-funcionan/409294/6?silent=true) in the VPS topic, responded to the [marketplace job posting](https://meta.discourse.org/t/ruby-discourse-specialist-wanted-contract-remote/409266?silent=true), and chimed in on the [Meta banner oddity](https://meta.discourse.org/t/meta-error-banner-merge-branch-deployment-failed/409333?silent=true).
- @Moin analyzed the [Discourse-ID branding issue](https://meta.discourse.org/t/discourse-id-displays-its-own-logo-name-instead-of-my-forums/409028?silent=true) with comparison screenshots, addressed [suppressing notifications for tag changes](https://meta.discourse.org/t/allow-to-suppress-notifications-for-tag-changes/409242?silent=true) by pointing to the existing site settings, corrected the default for `hide_email_address_taken` in the [password reset discussion](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?silent=true), and flagged the [safe-mode limitation](https://meta.discourse.org/t/where-did-the-version-information-go/407416?silent=true) for admin version lookups.
- @Falco clarified the model-display behavior in [LLM agents](https://meta.discourse.org/t/how-to-update-models-on-llm-agents/409274?silent=true) and opened an [improvement PR](https://github.com/discourse/discourse/pull/42326); he also made the Resenha voice-room plugin’s [slug editable](https://github.com/discourse/resenha/pull/77).
- @Mcwumbly ran the [update page improvement discussion](https://meta.discourse.org/t/improving-the-update-discourse-page/409245?silent=true), clarified how “update history” would work on his proposal, redirected to the [version information topic](https://meta.discourse.org/t/where-did-the-version-information-go/407416?silent=true), and [re-scoped the #contribute:ux category](https://meta.discourse.org/t/where-should-open-ended-discussion-about-the-product-happen/406248?silent=true) to better fit general design discussions.
- @Awesomerobot confirmed the [Patreon dashboard advice bug](https://meta.discourse.org/t/dashboard-advice-regarding-patreon-persists-after-issue-is-fixed/389807?silent=true) with a [fix merged](https://github.com/discourse/discourse/pull/42332), added missing button classes in the [docker\_manager PR](https://meta.discourse.org/t/start-updating-button-lacks-a-button-styling/409034?silent=true), and discussed the email-hide setting in [password reset](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?silent=true).
- @Zogstrip investigated a [category deletion failure](https://meta.discourse.org/t/deletion-of-categories-fails/409236?silent=true) and acknowledged in [grace-period edits bypass media review](https://meta.discourse.org/t/grace-period-edits-bypass-skip-review-media-groups-media-review/408899?silent=true) that the whole review system needs more planning for editing flows.
- @Rishabh confirmed the [Discourse-ID re-registration button](https://meta.discourse.org/t/discourse-id-displays-its-own-logo-name-instead-of-my-forums/409028?silent=true) is the proper way for self-hosters to refresh credentials, with hosted sites handling it automatically.
- @Renato clarified in [Cannot view post preview in mobile composer?](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352?silent=true) that the rich-text dismiss toggle doesn’t modify raw markdown, and noted that BBCode rich-mode support is in progress via a [pull request](https://github.com/discourse/discourse-bbcode/pull/107).
- @Danielle started the [community story topic](https://meta.discourse.org/t/what-s-the-story-behind-your-community/409282?silent=true) to gather origin stories.
- @Mae launched the [AI search strategy poll](https://meta.discourse.org/t/how-much-is-ai-search-part-of-your-enterprise-community-strategy-now/409298?silent=true) for enterprise communities.
- @NateDhaliwal tracked the [Meta banner](https://meta.discourse.org/t/meta-error-banner-merge-branch-deployment-failed/409333?silent=true) persistence and previewed [TL3 progress plugin updates](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543?silent=true), including work on showing the lowest stat when a user is over TL3 and queries for muted-category content.
- @Markvanlan clarified in [Introducing nested replies](https://meta.discourse.org/t/introducing-nested-replies/402812?silent=true) that enabling the setting applies per-site via `Nested replies default`, per-topic via the admin wrench, and per-category via category settings.
- @Jordan.Vidrine acknowledged the [Discourse ID branding feedback](https://meta.discourse.org/t/featuring-the-referring-sites-logo-and-name-more-prominently-in-discourse-id/398828?silent=true) and committed to taking it forward for UX polish.
- @HAWK reprieved a [read-only Free plan instance](https://meta.discourse.org/t/help-with-accessing-the-admin-dashboard-for-read-only-discourse-group-instance/409211?silent=true) after @AJHalili2006 explained the inactivity trigger, and shared [automation insights](https://meta.discourse.org/t/sharing-approaches-to-using-automation-to-send-messages-to-members/383691?silent=true) in the community-building thread.
* * *
From SSL certificate exorcisms to AI citation pub-quizzes, today’s round-the-clock fixes and community shares prove there’s never a dull build — see you in the next `git pull`.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 6, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/911 "2026-08-06T13:01:43Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
Over the last 24 hours, the community has been buzzing with activity:
- **Total new posts:** 161
- **Total new topics:** 51
**Top contributors (by likes received):**
| User | Likes | Posts |
| --- | --- | --- |
| @Moin | 25 | 12 |
| @Lilly | 21 | 12 |
| @Chapoi | 20 | 15 |
| @Merefield | 15 | 5 |
| @Nat | 8 | 4 |
| @Don | 8 | 2 |
| @Picho_Pelis | 7 | 7 |
| @Jordan.Vidrine | 7 | 5 |
| @Roke_Julian_Lockhart | 7 | 4 |
| @Southpaw | 7 | 2 |
* * *
## Interesting Topics
### Self-hosting
- **Ya estoy cansado, he instalado discourse en varios VPS ninguno me funcionan** – A frustrating installation saga that ended with the surprising discovery that the domain `debatehosting.co` was never actually registered! @Supermathie demonstrated via `whois` that the domain simply doesn’t exist, which explained the endless Let’s Encrypt and nginx errors. The topic also highlighted the importance of sharing solutions properly – @Lilly gently reminded the OP to mark the helpful reply as the solution. [Read more](https://meta.discourse.org/t/ya-estoy-cansado-he-instalado-discourse-en-varios-vps-ninguno-me-funcionan/409294?silent=true)
- **How should a user request a password reset when they do not remember the e-mail address that one of their accounts utilises?** – A deep discussion sparked by an OpenAI SSO change that left users without a password. @Roke_Julian_Lockhart explained his use of email aliases and the struggle to recover an account when the email is unknown. The thread evolved into a broader conversation about the `hide_email_address_taken` setting and led to a [feature request](https://meta.discourse.org/t/always-allow-username-based-password-reset/409326?silent=true) to always allow username‑based password resets. [Read more](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?silent=true)
### Support
- **Discourse-ID displays its own logo & name instead of my forum’s** – @Chapoi initially dismissed this as not a bug, but @Moin's keen eye showed that some forums display their own name while others show only “Discourse”. @Chapoi provided a workaround (clearing credentials and re‑enabling the plugin) that worked for the OP. @Rishabh confirmed a dedicated “re‑register” button also exists in the admin panel, though it was disabled for some self‑hosters. [Read more](https://meta.discourse.org/t/discourse-id-displays-its-own-logo-name-instead-of-my-forums/409028?silent=true)
- **Can I add additional languages to the Language Selector?** – @Karthik_K1 wanted to add Indian languages (Hindi, Telugu, Tamil, etc.) to the AI translator’s language selector. @Nat explained that the selector changes the whole Discourse locale, not just post content, so unsupported languages aren’t available. He suggested a plugin to register additional locales, and @Moin added that contributing translations to Crowdin would ultimately benefit everyone. [Read more](https://meta.discourse.org/t/can-i-add-additional-languages-to-the-language-selector/409353?silent=true)
- **How do I make my group mention notify group members?** – @Stephtara created a group and expected mentions to notify all members, but one member didn’t receive a notification. @Lilly and @Moin pointed out access restrictions (e.g., private categories) and suggested testing with a direct username mention to isolate the issue. The conversation linked to older discussions on group mentions and private category notifications. [Read more](https://meta.discourse.org/t/how-do-i-make-my-group-mention-notify-group-members/409389?silent=true)
### Announcements
- **Help Us Test the Composer Redesign** – @Chapoi unveiled an experimental new composer layout with a cleaner, document‑style title input, a bottom‑docked toolbar, and a slide‑up expanding editor on mobile. Early feedback from @Darkpixlz, @Don, and @NateDhaliwal discussed the title size, the AI‑suggestion button placement, and the swiping behaviour. @Chapoi promised fixes for colourless category icons and keyboard dismissal. [Read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849?silent=true)
- **Granular group-based permissions for anonymous and logged in users** – This ongoing rollout saw new CSS classes (`anonymous_users` and `logged_in_users`) added to the official groups‑CSS theme component via a PR from @Lilly. @Martin also merged updates to several official components to use the new group resolution APIs, moving the feature forward. [Read more](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273?silent=true)
- **PostgreSQL 18 update for self-hosters** – @Lilly shared a detailed, step‑by‑step guide for upgrading to PostgreSQL 18 on a dual‑container setup behind Cloudflare, including backups, maintenance pages, and disk cleanup. @Supermathie answered questions about Google Cloud SQL (test it!) and others discussed space‑check bypasses. [Read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194?silent=true)
### Feature
- **“Regular mode” for admins and moderators (e.g. something like “sudo”)** – @Sam proposed inverting the default: admins should behave like regular users unless they explicitly toggle admin powers on. @Mcwumbly agreed and suggested a header toggle with clear visual state. @Lilly raised concerns about staff notifications and asked for a site setting to keep current behaviour. [Read more](https://meta.discourse.org/t/regular-mode-for-admins-and-moderators-e-g-something-like-sudo/211617?silent=true)
- **Always allow username-based password reset** – @Roke_Julian_Lockhart filed a feature request after the OpenAI SSO fiasco. @Southpaw explained that the `hide_email_address_taken` setting (enabled by default) restricts the password reset form to email only. @Pfaffman later admitted his earlier objections were misplaced and called the restriction “a terrible idea”. A PR is now under consideration. [Read more](https://meta.discourse.org/t/always-allow-username-based-password-reset/409326?silent=true)
- **Multiple profiles for one user** – @FishEmoji proposed a PluralKit‑style system for Discourse, allowing a single user to post under multiple “proxy” personas (e.g., for roleplay or alt identities). @Satonotdead acknowledged the idea’s appeal but noted the difficulty in integrating it with Chat. [Read more](https://meta.discourse.org/t/multiple-profiles-for-one-user/409329?silent=true)
- **Automatically update translated category descriptions** – @Moin noticed that German category descriptions on Meta were out of sync after recent edits. @Nat confirmed a fix had been merged (PR #42407) to re‑sync translations automatically. [Read more](https://meta.discourse.org/t/automatically-update-translated-category-descriptions/399587?silent=true)
### Site feedback
- **Meta error banner - MERGE\_BRANCH deployment failed** – @Lilly reported a strange banner on Meta about a failed branch deployment. @Tgxworld fixed it quickly, but @NateDhaliwal noticed it persisted for a while. @David explained it was a mistake in the hosting system that displayed an internal error to all users, and that it has been corrected. [Read more](https://meta.discourse.org/t/meta-error-banner-merge-branch-deployment-failed/409333?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 reproduced the issue and explained that Discourse only re‑sends logo URLs when site settings change, leading to stale links. A fix to gracefully fall back to the name is on the way. [Read more](https://meta.discourse.org/t/discourse-meta-icon-missing-on-discourse-id-login-page/409441?silent=true)
### Development
- **Facebook-style Topic Modal - Is it better?** – @Don shared a detailed technical write‑up of his prototype that renders full topics in a modal using native Glimmer components instead of an iframe. He explained how he patches core services for routing, handles infinite scroll, and implements first‑paint skeletons. @Damian_Boon expressed interest in testing it. [Read more](https://meta.discourse.org/t/facebook-style-topic-modal-is-it-better/408565?silent=true)
* * *
## Activity by the @Team Group
The @Team group was highly visible across Meta today, driving discussions, fixing bugs, and sharing updates.
- @Chapoi continued to lead the **composer redesign** effort, answering feedback on the new layout and confirming fixes for reported issues like colourless category icons and swipe‑to‑close behaviour. [See his main announcement](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/1?silent=true) and [his follow‑up on the AI title button](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/4?silent=true).
- @Sam weighed in on the **admin “sudo” mode** discussion, suggesting a paradigm shift where admins start as regular users and enable admin powers temporarily, [as seen here](https://meta.discourse.org/t/regular-mode-for-admins-and-moderators-e-g-something-like-sudo/211617/39?silent=true). He also fixed a JSON formatting bug in the AI plugin affecting local LLMs, [described in this support thread](https://meta.discourse.org/t/discourse-ai-structured-output-response-was-not-valid-json/408821?silent=true).
- @Lilly was a whirlwind of activity: she helped troubleshoot **group mentions** , contributed to the **PostgreSQL 18** upgrade thread with a comprehensive guide, and even submitted a PR to add anonymous/logged‑in user CSS classes to the groups theme component. Her handiwork is visible in [the group permissions topic](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/30?silent=true) and [the Postgres upgrade topic](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/43?silent=true).
- @Nat clarified the **language selector** limitations and suggested plugin‑based workarounds, [in this reply](https://meta.discourse.org/t/can-i-add-additional-languages-to-the-language-selector/409353/2?silent=true). He also confirmed a fix for stale category descriptions, [linked in the translation topic](https://meta.discourse.org/t/automatically-update-translated-category-descriptions/399587/4?silent=true).
- @Martin merged PRs for official components to adopt the new group permissions model and posted an update on the roadmap, [as seen here](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/33?silent=true). He also commented on the **unified new view** topic, reinforcing the decision not to add a separate new/unread split but offering to support theme components that do. [Link](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728/48?silent=true)
- @David and @Tgxworld quickly addressed the **Meta error banner** and explained the root cause, [as seen in this site feedback thread](https://meta.discourse.org/t/meta-error-banner-merge-branch-deployment-failed/409333/2?silent=true).
- @Rishabh clarified how the **Discourse ID** re‑registration button works and confirmed a fix for the missing icon issue, [in this topic](https://meta.discourse.org/t/discourse-id-displays-its-own-logo-name-instead-of-my-forums/409028/20?silent=true).
- @Jordan.Vidrine investigated the broken icon on the Discourse ID login page and provided a workaround, [posting here](https://meta.discourse.org/t/discourse-meta-icon-missing-on-discourse-id-login-page/409441/2?silent=true).
- @Tannerabread fixed the **bulk archiving messages** visual glitch and the **wrong join date in reviewable insights** bug, sharing links to the PRs in [this thread](https://meta.discourse.org/t/bulk-archiving-messages-does-not-show-until-page-refresh/379082/6?silent=true) and [that one](https://meta.discourse.org/t/wrong-join-date-and-post-count-in-reviewable-insights/391232/10?silent=true).
- @Supermathie helped solve the installation mystery for the frustrated self‑hoster by checking the domain’s existence, [in this post](https://meta.discourse.org/t/ya-estoy-cansado-he-instalado-discourse-en-varios-vps-ninguno-me-funcionan/409294/31?silent=true).
- @Tobiaseigen reported a broken link in the Custom Wizard plugin documentation, [as seen here](https://meta.discourse.org/t/custom-wizard-plugin/73345/969?silent=true).
- @J.Jaffeux responded to feedback on the **Discourse Workflows** plugin, committing a fix for name collisions when pasting steps, [announced here](https://meta.discourse.org/t/discourse-workflows/407100/15?silent=true).
- @Ted confirmed a fix for the Patreon dashboard notice that persisted after the issue was resolved, [in this support thread](https://meta.discourse.org/t/dashboard-advice-regarding-patreon-persists-after-issue-is-fixed/389807/5?silent=true).
* * *
_From unregistered domains causing midnight headaches to a sleek new composer on the horizon, it’s been a day of creative problem‑solving and collaborative debugging. Here’s to many more threads where the mystery is solved by a simple `whois`!_
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 7, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/912 "2026-08-07T13:01:16Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
Over the past 24 hours, the community has been buzzing with activity:
- **Total new posts:** 150
- **Total new topics:** 60
- **Total likes given:** 313
**Top contributors** (by likes received):
| User | Likes | Posts |
| --- | --- | --- |
| @Chapoi | 22 | 9 |
| @Satonotdead | 19 | 7 |
| @Moin | 18 | 9 |
| @Awesomerobot | 18 | 2 |
| @Canapin | 17 | 6 |
| @Lilly | 14 | 5 |
| @Pfaffman | 14 | 5 |
| @Mostapha | 14 | 3 |
| @NateDhaliwal | 13 | 8 |
| @Nat | 13 | 6 |
These power users drove discussions across design, feature requests, and self-hosting challenges.
## Interesting Topics
Here’s a curated selection of the most engaging discussions from the last day, grouped by category.
### #Announcements
- [Help Us Test the Composer Redesign](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/1?silent=true) – @Chapoi opened up a major redesign of the composer for community testing, moving the toolbar to the bottom and revamping the mobile experience. Feedback poured in: @Canapin found the toolbar harder to reach on mobile, while @Satonotdead championed the change. @NateDhaliwal reported a bug where category icons lost their color, which @Chapoi promptly fixed.
- [PostgreSQL 18 Update for Self-Hosters](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/42?silent=true) – @Lilly shared a comprehensive step-by-step guide for upgrading to PostgreSQL 18 in both standalone and dual-container setups, including disk cleanup and optimization commands. @Tobias_1 provided a workaround for a common ownership error, and @Pfaffman discussed staging strategies for large databases.
- [Introducing a Docked Composer for AI Bot Conversations](https://meta.discourse.org/t/introducing-a-docked-composer-for-ai-bot-conversations/403327/22?silent=true) – @Moin asked about enabling the docked composer preference on [ask.discourse.com](http://ask.discourse.com), and @Keegan pointed to the appearance settings. @Martin suggested renaming “Fonts & Appearance” to something clearer like “Interface settings” to avoid confusion.
- [Granular Group-Based Permissions for Anonymous and Logged In Users](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/29?silent=true) – @Martin updated official components to use the new `resolve_group_membership` and `disallowed_groups` APIs, with PR contributions from @Lilly for adding CSS classes. The discussion also covered future plans for reducing reliance on the `everyone` group.
- [Easier Account Signup Using Email Codes](https://meta.discourse.org/t/easier-account-signup-using-email-codes/407068/22?silent=true) – @Thomas_Rother praised the feature as a secure alternative to traditional passwords, noting its growing popularity across platforms.
### #Community Building
- [For the Next Decade of the Internet (2026 Edition)](https://meta.discourse.org/t/for-the-next-decade-of-the-internet-2026-edition/409454/1?silent=true) – @Mcwumbly revived the evergreen question about Discourse’s role in the future of online communication. @Awesomerobot delivered a thoughtful analysis predicting that typing into boxes will remain the core interaction, while highlighting the threat of AI chatbots and the importance of community-owned spaces. @Ed_S and @Satonotdead added perspectives on polarization and the need for both public and hidden “spaces of resistance.”
### #Feature
- [Redirect the Landing Page for Subcategories to Index File](https://meta.discourse.org/t/redirect-the-landing-page-for-each-subcategory-to-index-file-by-default-for-documentation-categories/409470/1?silent=true) – @Mostapha requested an option for doc categories to default to the index page instead of a list of posts. He later discovered a duplicate request and linked to it, while @Merefield suggested keeping the topic open because the other wasn’t a vote-tracked feature.
- [Always Allow Username-Based Password Reset](https://meta.discourse.org/t/always-allow-username-based-password-reset/409326/4?silent=true) – @Pfaffman argued against the current behavior where `hide_email_address_taken` prevents username-based resets, pointing out that it hurts long-time users who forget their email. @Awesomerobot explained the intentional change and noted that the setting is now on by default.
- [Automatically Update Translated Category Descriptions](https://meta.discourse.org/t/automatically-update-translated-category-descriptions/399587/3?silent=true) – @Moin reported that changes to category descriptions don’t propagate to translated versions unless the original locale is English. @Nat confirmed a fix was merged via [PR #42407](https://github.com/discourse/discourse/pull/42407).
- [More Direct Access to Topics with New Replies](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/10?silent=true) – @Martin acknowledged feedback about losing the split between “new” and “unread” counts, but stated no plans to change it. @Frederic_Bertrand and @Shauny shared community complaints, prompting @Lindsey to move the discussion to a feature topic for further voting.
- [Copy Workflow Step Names](https://meta.discourse.org/t/copy-workflow-step-names/409410/1?silent=true) – @Per1234 filed a detailed feature request asking that copied and pasted workflow steps preserve their custom names, including a thorough reproduction walkthrough. The request highlights a collision-handling concern that could be addressed with unique suffix logic.
### #Support
- [Setting Translation to One Language Only](https://meta.discourse.org/t/setting-translation-to-one-language-only/409504/1?silent=true) – @Marzena_Cudecka wanted to limit content translation languages to German, but found all languages listed. @Nat and @Moin clarified that content translations are admin-controlled, while interface languages are user-selectable. @Nat also noted a possible bug where the language switcher showed Spanish unexpectedly.
- [Zendesk API Tokens Will Be Permanently Deactivated on April 30, 2027](https://meta.discourse.org/t/zendesk-api-tokens-will-be-permanently-deactivated-on-april-30-2027/409411/1?silent=true) – @Vishal_Ahir raised the upcoming Zendesk API token sunset. @Lilly provided thorough documentation and linked to the relevant plugin topic, noting that the plugin will likely need OAuth migration.
- [Is There Any Built-In Chatbot or Conversational Assistant?](https://meta.discourse.org/t/is-there-any-built-in-chatbot-or-conversational-assistant-available-in-discourse/409513/1?silent=true) – @Soumya_Ranjan_Mishra asked about built-in AI chat options. @RGJ pointed to the AI Bot plugin and @Merefield's Chatbot plugin, plus an external service example.
### #ux
- [The Meta Branded Theme Lacks Margins on Single Group Pages](https://meta.discourse.org/t/the-meta-branded-theme-lacks-margins-on-single-group-pages/409450/1?silent=true) – @Canapin reported a layout issue on group pages. @Manuel acknowledged the missing body class and said they would investigate.
- [“All Members” When Creating a Category Assigns Everyone](https://meta.discourse.org/t/all-members-when-creating-a-category-assigns-everyone/409508/1?silent=true) – @RGJ highlighted a security pitfall where choosing “all members” sets permissions to `everyone`, which can expose content after login requirement is disabled. @Chapoi asked @Martin for thoughts, and @RGJ proposed a three-button solution.
### #enterprise
- [Public vs Private Discussion](https://meta.discourse.org/t/public-vs-private-discussion/409484/1?silent=true) – @HAWK opened a strategic discussion about when to engage publicly versus privately on enterprise Discourse instances. @Nickdb shared their community’s strict no-DM policy to maintain quality and oversight.
### #Theme component
- [Quote Callouts](https://meta.discourse.org/t/quote-callouts/350962/78?silent=true) – @Heliosurge reported a breaking error after upgrading. @祁同伟 forked the project and submitted a PR, and @Arkshine quickly pushed a fix.
### #bug
- [Category Moderators May Receive Incorrect Number of Pending Reviews](https://meta.discourse.org/t/category-moderators-may-receive-incorrect-number-of-pending-reviews/409494/1?silent=true) – @Small-Lovely-Cat reported a notification syncing issue where category moderators see inflated pending review counts until refreshing. Troubleshooting is ongoing.
## Activity by the @Team Group
Our dedicated @Team members have been hard at work addressing feedback, fixing bugs, and engaging with the community:
- @Chapoi led the [composer redesign testing](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/1?silent=true), responding to each piece of feedback, fixing the colorless category icon bug, and clarifying design intentions. He also [replied to a Right Sidebar Blocks query](https://meta.discourse.org/t/right-sidebar-blocks/231067/203?silent=true) confirming functionality.
- @Awesomerobot shared an insightful [long-form post about the future of the internet](https://meta.discourse.org/t/for-the-next-decade-of-the-internet-2026-edition/409454/3?silent=true) and later [explained the history behind the username-reset behavior](https://meta.discourse.org/t/always-allow-username-based-password-reset/409326/6?silent=true).
- @Martin contributed across multiple areas: he [approved PRs for group permissions](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/33?silent=true), [clarified CSS class usage](https://meta.discourse.org/t/granular-group-based-permissions.../402273/29?silent=true), [responded to the “more direct access” feedback](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/10?silent=true), and [suggested better wording for the docked composer preference](https://meta.discourse.org/t/introducing-a-docked-composer-for-ai-bot-conversations/403327/25?silent=true).
- @Nat handled several localization questions: he [asked for screenshots on language settings](https://meta.discourse.org/t/setting-translation-to-one-language-only/409504/2?silent=true), [recommended plugin approaches for new locales](https://meta.discourse.org/t/can-i-add-additional-languages-to-the-language-selector/409353/5?silent=true), and [confirmed a fix for translated category descriptions](https://meta.discourse.org/t/automatically-update-translated-category-descriptions/399587/4?silent=true).
- @J.Jaffeux promptly [fixed a workflow issue](https://meta.discourse.org/t/discourse-workflows/407100/15?silent=true) based on community feedback.
- @Lindsey [moved feedback about new/unread counts to a feature request](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/14?silent=true) to gather more votes.
- @Jordan.Vidrine [acknowledged and fixed the Discourse ID logo loading issue](https://meta.discourse.org/t/discourse-meta-icon-missing-on-discourse-id-login-page/409441/2?silent=true), and later [confirmed the root cause and mitigation](https://meta.discourse.org/t/discourse-meta-icon-missing-on-discourse-id-login-page/409441/3?silent=true).
- @Manuel [accepted responsibility for the group page margin bug](https://meta.discourse.org/t/the-meta-branded-theme-lacks-margins-on-single-group-pages/409450/3?silent=true) and promised to look into it.
- @Davidb [fixed a confusing email validation error](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) and explained the underlying uniqueness rule.
- @Rishabh [discussed Discourse ID metadata refresh mechanics](https://meta.discourse.org/t/discourse-id-displays-its-own-logo-name-instead-of-my-forums/409028/23?silent=true) and tested the regeneration flow.
- @Keegan [guided @Moin to the correct setting](https://meta.discourse.org/t/introducing-a-docked-composer-for-ai-bot-conversations/403327/23?silent=true) for the docked composer preference.
* * *
That’s a wrap on a day filled with composer debates, PostgreSQL upgrades, and thoughtful musings on the next decade! May your threads stay lively and your ping counts stay low. 🚀
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 8, 2026, 1:00 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/913 "2026-08-08T13:00:56Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
Over the past 24 hours, the community has been buzzing with **117 new posts** across **54 topics** , sparking **170 likes**. The most active contributors were:
| User | Posts | Likes |
| --- | --- | --- |
| @Awesomerobot | 8 | 19 |
| @Moin | 7 | 14 |
| @RGJ | 7 | 13 |
| @Don | 3 | 11 |
| @Heliosurge | 7 | 8 |
| @Sk-Or-V1-Contents | 5 | 8 |
| @Nat | 3 | 8 |
| @Arkshine | 2 | 7 |
| @NateDhaliwal | 5 | 6 |
| @Mcdanlj | 4 | 5 |
## Interesting Topics
### #development
- @Don showcased a [Facebook-style topic modal](https://meta.discourse.org/t/facebook-style-topic-modal-is-it-better/408565/23?silent=true) theme component, which drew praise from @David_Ghost, @Andrew_Rowe, and @Canapin. However, @Awesomerobot flagged excessive network requests, prompting @Don to add rate-limit safeguards and make the component [more configurable](https://meta.discourse.org/t/facebook-style-topic-modal-is-it-better/408565/29?silent=true).
- @Satonotdead asked about [automating gamification points](https://meta.discourse.org/t/automating-gamification-points/409452/2?silent=true). @Awesomerobot suggested a Workflows action, and @Falco quickly followed up with a [pull request](https://github.com/discourse/discourse/pull/42447) to implement it.
### #Announcements
- The [composer redesign](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849?silent=true) is open for testing. @Heliosurge reported the tag icon is too small on mobile and found issues with the rollout settings initially, but it worked after a retest. @Canapin noted a minor rounding inconsistency on the selector, and @Sk-Or-V1-Contents demonstrated a flashy animation and a double-tap problem when minimizing the editor.
### #Support
- After updating to v2026.8.0, @M_Terenui noticed the backup and free-space metrics vanished from the admin dashboard. @Moin pointed to a [related discussion](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528/46?silent=true) and @Awesomerobot suggested a `storage_stats.json` endpoint as a temporary workaround.
- @Marzena_Cudecka wanted to limit [content translations to German only](https://meta.discourse.org/t/setting-translation-to-one-language-only/409504/1?silent=true). @Nat and @Moin explained the settings hierarchy, and @Nat noted the team would consider a feature request about limiting interface languages.
- A new user asked about [built-in chatbots](https://meta.discourse.org/t/is-there-any-built-in-chatbot-or-conversational-assistant-available-in-discourse/409513/1?silent=true). @RGJ recommended the AI Bot and the Chatbot plugin, while @Awesomerobot highlighted the Discourse AI features like auto-categorization and [ask.discourse.com](http://ask.discourse.com).
### #ux
- @Moin raised a point about [“vote returned” notifications](https://meta.discourse.org/t/vote-returned-notification-in-case-of-unlimited-votes/409518/1?silent=true) even when vote limits are disabled. @Awesomerobot agreed and referenced a [PR](https://github.com/discourse/discourse/pull/42448) to improve this.
- @Satonotdead wondered if “Me too” should be hidden on category description topics. @Awesomerobot concurred and shared a [PR](https://github.com/discourse/discourse/pull/42444) to exclude those topics.
- @RGJ found that the “All members” button when creating a category assigns `everyone` even when login is required, which could accidentally expose private content. @Chapoi asked @Martin for thoughts, and @RGJ suggested a three-button approach.
### #Theme component
- @Heliosurge reported errors in the [Alternative User PMs Button](https://meta.discourse.org/t/alternative-user-pms-button-for-admin/260952/2?silent=true) component. @Arkshine fixed it quickly, earning praise.
- Likewise, the [Quote Callouts](https://meta.discourse.org/t/quote-callouts/350962/79?silent=true) component broke after an update. 祁同伟 submitted a fork fix, and @Arkshine pushed a proper fix.
### #Sysadmins
- @Raykholo asked about using Garage instead of Minio in @Mcdanlj's deployment guide. @Mcdanlj confirmed it’s feasible, and later shared a corrected transparent-huge-pages configuration. @Raykholo then documented a deep-dive on running Discourse with Garage and Cloudflare, highlighting silent incompatibilities.
### #Feature
- The change to split “new” into “topics” and “replies” is being debated. @Awesomerobot explained the reasoning, and @Moin suggested a possible enhancement to the custom top navigation links component.
### #Site feedback
- @NateDhaliwal noticed the Uncategorized category seemed to have returned. @Moin linked it to a recent [discussion about removing Uncategorized](https://meta.discourse.org/t/removing-uncategorized-and-migrating-to-a-standard-category/406373?silent=true).
### #bug
- @RGJ reported that a user’s bounce score doesn’t reset when their email is changed, suggesting it should be per-email rather than per-user.
## Activity by the @Team Group
The @Team group has been active across several fronts, often responding to community feedback and fixing issues in real time.
- @Awesomerobot provided direct support on the composer redesign, discussing tag icon sizing, the `storage_stats.json` endpoint, and the logic behind the new “new” menu structure. He also implemented fixes for the “vote returned” notification and the “Me too” visibility on category description topics.
- @Moin helped users with translation settings, pointed to relevant feature requests, and engaged in the ongoing debate about the new “new” navigation, suggesting a possible configurable approach.
- @Nat clarified translation behaviours and promised to consider a feature request about restricting interface languages, while also updating the Content Localization documentation.
- @Martin investigated the composer redesign rollout issue and confirmed Meta’s own group-based settings.
- @Don responded to feedback on his topic modal component, adding new settings and rate-limiting to improve performance.
- @Falco swiftly contributed a pull request for the gamification workflow suggestion.
- @Tshenry fixed the Hide Likes theme component and is working with @Moin on the Restrict uploads component.
- @Angus raised a PR in core to fix a niche custom field preloading bug affecting the Custom Wizard plugin.
- @Lindsey acknowledged the ZenDesk API token deprecation and said the team would review its impact.
* * *
**Sign-off:** With all these fixes and features landing, it seems like the Discourse team is on a roll — but let’s hope the topic modal doesn’t hit the rate limit before we do! 🚀
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 9, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/914 "2026-08-09T13:01:02Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
> The sun never sets on the Discourse community—here’s your daily briefing on the latest happenings from the past 24 hours.
* * *
## Key Stats
Over the last 24 hours, the community has been buzzing with activity:
- **58 new posts** and **28 new topics** were created
- **78 likes** were given across all posts
**Top Contributors by Likes Received:**
| User | Likes | Posts |
| --- | --- | --- |
| @Moin | 32 | 5 |
| @Merefield | 8 | 4 |
| @RGJ | 6 | 2 |
| @HAWK | 4 | 1 |
| @Sk-Or-V1-Contents | 3 | 4 |
| @Eviepayne | 3 | 2 |
| @Lilly | 3 | 2 |
| @Weallwegot | 3 | 1 |
| @DRRO | 2 | 4 |
| @NateDhaliwal | 2 | 4 |
* * *
## Interesting Topics
Here’s what the community has been discussing, organized by category.
### #Praise
- @Moin kicked off a wonderful [contributor appreciation thread](https://meta.discourse.org/t/contributor-appreciation-august-feb-2026/409592/1?silent=true) for the August 2026 release, thanking both code contributors and translators for their hard work over the past six months, with @HAWK quickly expressing gratitude [on behalf of the community](https://meta.discourse.org/t/contributor-appreciation-august-feb-2026/409592/3?silent=true). The thread also sheds light on the broader release announcement and community engagement strategy.
### #Theme component
- @Eviepayne reported a [critical avatar upload failure](https://meta.discourse.org/t/topic-list-previews-tlp/209973/761?silent=true) with the error “no implicit conversion of Hash into String,” which @Merefield [identified and fixed](https://meta.discourse.org/t/topic-list-previews-tlp/209973/764?silent=true) as a compatibility issue in the TLP sidecar plugin—[resolved via PR #183](https://github.com/merefield/discourse-topic-previews-sidecar-pro/pull/183) within hours.
- @Weallwegot [merged a long-awaited PR](https://meta.discourse.org/t/clickable-social-icon-links-on-profile/158136/104?silent=true) to update the Twitter icon to X in the Clickable Social Icon Links on Profile component, with @Roi [proposing a follow-up PR](https://meta.discourse.org/t/clickable-social-icon-links-on-profile/158136/105?silent=true) that has some directory conflicts requiring resolution.
- @Satonotdead asked if the [Created Topic Sort](https://meta.discourse.org/t/created-topic-sort/321521/25?silent=true) component could support A-Z ordering, but @Alteras [explained](https://meta.discourse.org/t/created-topic-sort/321521/26?silent=true) that alphabetical sorting isn’t currently possible due to TopicQuery limitations, suggesting the Doc Categories plugin or using `/filter` with `order:title` instead.
- @Damian_Boon [expressed interest](https://meta.discourse.org/t/facebook-style-topic-modal-is-it-better/408565/30?silent=true) in open-sourcing the Facebook-style Topic Modal component, and @Don [recently added](https://meta.discourse.org/t/facebook-style-topic-modal-is-it-better/408565/32?silent=true) new settings for `trigger_style` and `plugin_outlet` to improve flexibility for custom layouts.
### #Feature
- @DRRO [resumed discussion](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/24?silent=true) about adding personal notes to posts, and @Awesomerobot [suggested bookmarks as a natural fit](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/25?silent=true) for this functionality, while @Lilly [shared her approach](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/26?silent=true) of using a running PM to oneself as a practical workaround.
- @Seanblue [shared valuable feedback](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/19?silent=true) on the new/direct access topics change, arguing that reverting to the old “new vs unread” structure was necessary in both Discourse communities they participate in—the vast majority of users preferred the simpler original design. The [discussion](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522?silent=true) continues, with @NateDhaliwal [suggesting a possible sidebar link](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/20?silent=true) to `/unread` as a possible alternative.
- @Gassim [requested enhanced webhook triggers and automations](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623/1?silent=true) for the Discourse Calendar & Events plugin, specifically around user participation in events (going, not going, interested) and suggested automation use cases like adding attendees to groups and sending welcome messages.
- @One1 [proposed making long footnotes scrollable](https://meta.discourse.org/t/could-long-footnotes-be-scrollable/409613/1?silent=true) in a new feature request, noting the tradeoffs between popups and end notes, and also reported a related quoting bug.
### #Announcements
- @Sk-Or-V1-Contents [provided detailed feedback](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/29?silent=true) on the new Composer redesign, reporting a flashy blue highlight animation on Android, the need to tap the minus button twice to minimize the keyboard, and [reiterated a call for a mobile preview button](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352?silent=true). The [team is actively iterating](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/31?silent=true) on this based on feedback.
- @NateDhaliwal [reported a PostgreSQL connection issue](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/46?silent=true) in the DevContainers setup for the PostgreSQL 18 update, and the discussion on the [Postgres upgrade](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194?silent=true) is ongoing.
### #Support
- @Viddekla [raised an issue](https://meta.discourse.org/t/admin-hinweise-nach-letztem-update/409587/1?silent=true) about two new admin warnings appearing after a recent update, related to the `discourse-locations` plugin and a general “legacy array-like object” reference. @Moin [offered guidance](https://meta.discourse.org/t/admin-hinweise-nach-letztem-update/409587/2?silent=true) on contacting plugin authors for compatibility updates.
- @Satonotdead [asked about overriding restricted tags](https://meta.discourse.org/t/overriding-restricted-tags-on-admins-staff/409542/3?silent=true) for admins and staff, seeking confirmation before opening a formal feature request.
- @Satonotdead [asked about preventing Discourse from overriding](https://meta.discourse.org/t/how-to-skip-override-overrided-localizations/409604/1?silent=true) already-customized translations on every core update—the workarounds discussed include using the content-localization features to manage custom strings more effectively.
### #bug
- @RGJ [reported a bug](https://meta.discourse.org/t/bounce-score-does-not-reset-when-email-address-is-changed/409581/1?silent=true) in email bounce score management: the score doesn’t reset when a user changes their email address, and the error message even says “some bounces were received recently from **that** email,” suggesting the score is being associated with the user rather than the specific address.
- @Moin [confirmed a fix](https://meta.discourse.org/t/monthly-triggered-recurring-automation-is-not-running-as-expected/402664/23?silent=true) was merged for the monthly recurring automation not running as expected issue, and @Gassim [is planning to verify](https://meta.discourse.org/t/monthly-triggered-recurring-automation-is-not-running-as-expected/402664/24?silent=true) it works as intended next month.
- @Small-Lovely-Cat [submitted a performance fix](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622/1?silent=true) for Redis key traversal issues when clearing 404 topic cache, which could cause timeouts on large Redis databases and has been addressed in [PR #42457](https://github.com/discourse/discourse/pull/42457).
- @Sk-Or-V1-Contents [reported a jittery keyboard bug](https://meta.discourse.org/t/jittery-keyboard-in-languages-i-understand-input-box-on-mobile/409628/1?silent=true) in the “languages I understand” input box on mobile, complete with detailed reproduction steps and a screen recording, in the content-localization area.
- @Dennisjbr [shared an experience](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/5?silent=true) related to Gmail dot variant email issues, mentioning they’d had another report but couldn’t find their notes on it.
### #Plugin
- @Jagster [noted an admin warning](https://meta.discourse.org/t/locations-plugin/69742/1243?silent=true) about the locations plugin containing outdated code, but @Merefield [announced the resolution](https://meta.discourse.org/t/locations-plugin/69742/1245?silent=true) with a friendly nod to contributor @Cvx—recent PRs have modernized the plugin’s core APIs, fixed security vulnerabilities, and improved error handling.
- @RGJ [confirmed that a contributor](https://meta.discourse.org/t/discourse-dynamic-groups/365342/25?silent=true) had resolved the deprecation notices in the Discourse Dynamic Groups plugin, after they were originally reported by @Nathank.
- @Gassim [asked several questions](https://meta.discourse.org/t/discourse-calendar-and-events/97376/610?silent=true) about the Discourse Calendar and Events plugin, specifically about Zoom integration, whether “Ready for local test” suffices for the Zoom app, and how to restrict the “join meeting” button to logged-in users or specific groups.
- @Satonotdead [raised a privacy concern](https://meta.discourse.org/t/discourse-fingerprint-browser-fingerprinting-plugin/114890/74?silent=true) about the Fingerprint browser fingerprinting plugin, wondering how the plugin handles users who actively spoof their fingerprints for privacy reasons, given their own privacy-conscious stance.
### #development
- @Damian_Boon [suggested a follow-up](https://meta.discourse.org/t/facebook-style-topic-modal-is-it-better/408565/31?silent=true) on Don’s topic list preview component, noting that open-sourcing it could add real value to the community—it could be a great theme component for others.
- @Satonotdead [explored automation options](https://meta.discourse.org/t/automating-gamification-points/409452/5?silent=true) for gamification points and noted they’re looking for ongoing solutions, with the official Workflows feature on the roadmap.
- @NateDhaliwal [pointed to an existing discussion](https://meta.discourse.org/t/reply-text-box-as-alternative-to-current-button-approach/197407/13?silent=true) about implementing a reply text box as an alternative to the current button approach, suggesting a theme component could be the way forward.
### #Self-hosting
- @ALinux [shared their experience](https://meta.discourse.org/t/fresh-install-migrated/409595/1?silent=true) after migrating from phpBB to Discourse, noting initial performance concerns that @Darkpixlz [reassured them about](https://meta.discourse.org/t/fresh-install-migrated/409595/2?silent=true), and they later [reported improved performance after scaling up](https://meta.discourse.org/t/fresh-install-migrated/409595/3?silent=true).
- @Dopler [offered advice on hosting pricing](https://meta.discourse.org/t/any-cheaper-alternatives-to-hetzner/409037/24?silent=true), suggesting comparisons should factor in CPU type, RAM, storage and network limits instead of raw vCPU counts, while @Satonotdead [suggested OVHcloud’s VPS](https://meta.discourse.org/t/any-cheaper-alternatives-to-hetzner/409037/25?silent=true) as an alternative.
### #ux
- @Satonotdead [raised a question about language overrides in the UI](https://meta.discourse.org/t/how-to-skip-override-overrided-localizations/409604/1?silent=true)—specifically, how to stop Discourse from overwriting their customized translations after each core update. The content-localization features were the main suggestion for handling this more gracefully.
* * *
## Activity by the @Team Group
Discourse team members have been active across several areas today:
- **@Moin** has been on fire, posting a [beautiful contributor appreciation thread](https://meta.discourse.org/t/contributor-appreciation-august-feb-2026/409592/1?silent=true) acknowledging the many community members who have improved Discourse, and [helpfully guiding @Viddekla](https://meta.discourse.org/t/admin-hinweise-nach-letztem-update/409587/2?silent=true) on how to address plugin compatibility warnings. They also [shared a suggestion](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/31?silent=true) about the privacy implications of linking PMs publicly and [confirmed a fix](https://meta.discourse.org/t/monthly-triggered-recurring-automation-is-not-running-as-expected/402664/23?silent=true) for the monthly recurring automation issue.
- **@Merefield** [diagnosed the avatar upload bug](https://meta.discourse.org/t/topic-list-previews-tlp/209973/762?silent=true) affecting TLP sidecar users within an hour of it being reported, [deployed a fix via PR](https://github.com/merefield/discourse-topic-previews-sidecar-pro/pull/183), and [announced the resolution](https://meta.discourse.org/t/locations-plugin/69742/1245?silent=true) of the locations plugin admin warning, crediting contributor @Cvx for the modernization work.
- **@NateDhaliwal** [reported the PostgreSQL connection issue](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/46?silent=true) in the DevContainers setup, [suggested a possible sidebar link workaround](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/20?silent=true) for the new/unread navigation debate, [pointed to a thread about a reply text box alternative](https://meta.discourse.org/t/reply-text-box-as-alternative-to-current-button-approach/197407/13?silent=true), and [recommended a plugin approach](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/30?silent=true) for creating pre-filled personal message links.
- **@Chapoi** [acknowledged feedback](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/31?silent=true) on the Composer redesign, confirming that Horizon theme support is still in progress while Foundation works well.
- **@Awesomerobot** [suggested bookmarks as a solution](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/25?silent=true) for personal notes on posts, noting their searchability, topic-level linkability, and PM support—while acknowledging the single-line text field as a potential limitation.
* * *
> With all these fixes rolling out, it looks like someone had a very productive day herding 🐱 cats and squashing 🐛 bugs! Now let’s see what tomorrow brings! 🚀
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 10, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/915 "2026-08-10T13:01:15Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
Over the last 24 hours, **76 new posts** were created across **37 topics** , accumulating **81 likes**. Here are the top users by activity:
| User | Likes | Posts |
| --- | --- | --- |
| @Moin | 10 | 7 |
| @Merefield | 10 | 4 |
| @Per1234 | 9 | 2 |
| @Kcahtoor | 5 | 6 |
| @Chapoi | 4 | 2 |
| @NateDhaliwal | 3 | 5 |
| @Gassim | 3 | 3 |
| @Chrisr | 3 | 2 |
| @Lilly | 3 | 2 |
| @Jay-C | 3 | 1 |
## Interesting Topics
### #Feature
- **Add support for ‘personal notes’ on posts** – @Lilly [suggested](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/26?silent=true) using private messages as a workaround, while @Awesomerobot [noted](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/25?silent=true) bookmarks are a natural fit. Later, @Merefield [announced](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/32?silent=true) building a plugin for this, and finally [published it](https://meta.discourse.org/t/bookmark-notes/409685/1?silent=true) as **Bookmark Notes** – turning bookmarks into private personal notes attached to posts. [Discuss](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798?silent=true)
- **Discourse Calendar & Events: Webhook triggers & Automations plugin** – @Gassim [requested](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623/1?silent=true) richer webhook events (user going/not going/participation summary) and automation triggers for event interactions. @Lindsey [responded](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623/2?silent=true) that these might be considered for the new Workflows feature. [More](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623?silent=true)
- **Could long footnotes be scrollable?** – @One1 [asked](https://meta.discourse.org/t/could-long-footnotes-be-scrollable/409613/1?silent=true) about making footnote popups scrollable and reported a quoting bug. @Lilly [requested](https://meta.discourse.org/t/could-long-footnotes-be-scrollable/409613/2?silent=true) a separate bug topic for the quoting issue. [Thread](https://meta.discourse.org/t/could-long-footnotes-be-scrollable/409613?silent=true)
- **More direct access to topics with new replies** – @NateDhaliwal [suggested](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522/20?silent=true) adding a sidebar link to `/unread` (which excludes new topics) for quicker access. [Read](https://meta.discourse.org/t/more-direct-access-to-topics-with-new-replies/409522?silent=true)
- **Multiple profiles for one user** – @FishEmoji [wondered](https://meta.discourse.org/t/multiple-profiles-for-one-user/409329/10?silent=true) about PluralKit-like profiles for chat, with @Heliosurge [uncertain](https://meta.discourse.org/t/multiple-profiles-for-one-user/409329/11?silent=true) about feasibility. [Topic](https://meta.discourse.org/t/multiple-profiles-for-one-user/409329?silent=true)
### #Announcements
- **Help Us Test the Composer Redesign** – @Per1234 [provided](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/34?silent=true) detailed feedback on the borderless design, including Enter key behavior and missing right margin. @Chapoi is [working](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/36?silent=true) on improvements. [Watch it](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849?silent=true)
- **PostgreSQL 18 update for self-hosters** – @Kcahtoor [reported](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/47?silent=true) multisite migration issues. @Chrisr [merged](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/49?silent=true) a fix and provided detailed rollback steps. [Update](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194?silent=true)
- **Introducing the unified new view for the topic list** – @Newbit1337 [questioned](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728/48?silent=true) the Dismiss behavior, then found the “and stop tracking” option. [Announcement](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728?silent=true)
### #Self-hosting
- **I upgraded to latest and lost everything** – @Kcahtoor [described](https://meta.discourse.org/t/i-upgraded-to-latest-and-lost-everything/409647/1?silent=true) a multisite upgrade disaster, leading to @Chrisr’s fix in the Postgres thread. @Moin [pointed](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/50?silent=true) to the resolution. [Original](https://meta.discourse.org/t/i-upgraded-to-latest-and-lost-everything/409647?silent=true)
- **Fresh install/migrated!** – @ALinux [shared](https://meta.discourse.org/t/fresh-install-migrated/409595/3?silent=true) that adding more CPU cores drastically improved performance on his old server. [More](https://meta.discourse.org/t/fresh-install-migrated/409595?silent=true)
### #bug
- **FIX: Avoid traversing Redis keys when clearing 404 topic cache** – @Small-Lovely-Cat [submitted](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622/1?silent=true) a performance fix, which @Sam [confirmed](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622/2?silent=true) was merged. [PR](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622?silent=true)
- **Monthly triggered recurring automation is not running as expected** – @Moin [noted](https://meta.discourse.org/t/monthly-triggered-recurring-automation-is-not-running-as-expected/402664/23?silent=true) a previous fix, and @Gassim [agreed](https://meta.discourse.org/t/monthly-triggered-recurring-automation-is-not-running-as-expected/402664/24?silent=true) to test again. [Thread](https://meta.discourse.org/t/monthly-triggered-recurring-automation-is-not-running-as-expected/402664?silent=true)
- **Jittery keyboard in “languages I understand” input box on mobile** – @Sk-Or-V1-Contents [reported](https://meta.discourse.org/t/jittery-keyboard-in-languages-i-understand-input-box-on-mobile/409628/1?silent=true) a mobile-only keyboard glitch. [Details](https://meta.discourse.org/t/jittery-keyboard-in-languages-i-understand-input-box-on-mobile/409628?silent=true)
- **Problem pasting HTML into Markdown composer on mobile** – @Sam [acknowledged](https://meta.discourse.org/t/problem-pasting-html-into-markdown-composer-on-mobile-until-pasting-once-into-rich-text-editor/409530/3?silent=true) the issue and noted @Renato is investigating. [Original](https://meta.discourse.org/t/problem-pasting-html-into-markdown-composer-on-mobile-until-pasting-once-into-rich-text-editor/409530?silent=true)
### #ux
- **“All members” when creating a category assigns everyone** – @Martin [responded](https://meta.discourse.org/t/all-members-when-creating-a-category-assigns-everyone/409508/4?silent=true) to feedback, proposing a three-button UI (public / members only / private) and clarifying migration plans for `everyone`. [Read](https://meta.discourse.org/t/all-members-when-creating-a-category-assigns-everyone/409508?silent=true)
- **Scrollbar? in the post menu when removing a reaction** – @Moin [spotted](https://meta.discourse.org/t/scrollbar-in-the-post-menu-when-removing-a-reaction/409641/1?silent=true) a visual jump when removing a like. [Discussion](https://meta.discourse.org/t/scrollbar-in-the-post-menu-when-removing-a-reaction/409641?silent=true)
- **Discrepancy in display of user activity** – @Sterretje [asked](https://meta.discourse.org/t/discrepancy-in-display-of-user-activity-all-replies-vs-topic/409671/1?silent=true) why the Topics tab doesn’t show post excerpts. @Moin [explained](https://meta.discourse.org/t/discrepancy-in-display-of-user-activity-all-replies-vs-topic/409671/3?silent=true) it’s because titles are sufficient for topic activity, while post activity needs content. [Thread](https://meta.discourse.org/t/discrepancy-in-display-of-user-activity-all-replies-vs-topic/409671?silent=true)
### #Support
- **How can I restrict an AI Agent to answer only questions related to my forum?** – @Karthik_K1 [asked](https://meta.discourse.org/t/how-can-i-restrict-an-ai-agent-to-answer-only-questions-related-to-my-forum/409672/1?silent=true) about preventing off-topic answers. @NateDhaliwal [suggested](https://meta.discourse.org/t/how-can-i-restrict-an-ai-agent-to-answer-only-questions-related-to-my-forum/409672/2?silent=true) using Forum Helper agents, but @Karthik_K1 [showed](https://meta.discourse.org/t/how-can-i-restrict-an-ai-agent-to-answer-only-questions-related-to-my-forum/409672/3?silent=true) it still answers general questions. [Help](https://meta.discourse.org/t/how-can-i-restrict-an-ai-agent-to-answer-only-questions-related-to-my-forum/409672?silent=true)
- **How do I access topics in muted categories?** – @NateDhaliwal [queried](https://meta.discourse.org/t/how-do-i-access-topics-in-muted-categories/409676/1?silent=true) about viewing muted categories via filters, suspecting a bug. [Follow](https://meta.discourse.org/t/how-do-i-access-topics-in-muted-categories/409676?silent=true)
### #Migration
- **Accepted solutions: plugin + migrating markers from Khoros** – @Gosia.Murawska [asked](https://meta.discourse.org/t/accepted-solutions-plugin-migrating-markers-from-khoros/409686/1?silent=true) about carrying over accepted solutions. @Italo [confirmed](https://meta.discourse.org/t/accepted-solutions-plugin-migrating-markers-from-khoros/409686/2?silent=true) it’s possible if the plugin is active during import. [More](https://meta.discourse.org/t/accepted-solutions-plugin-migrating-markers-from-khoros/409686?silent=true)
### #Data & reporting
- **DSA Content Moderation Reporting + Statements of Reasons Requirements** – @Jay-C [outlined](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/1?silent=true) the need for structured suspending reasons and taxonomy alignment, asking for community advice. [Read](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681?silent=true)
### #Plugin
- **Bookmark Notes** (new plugin) – @Merefield [announced](https://meta.discourse.org/t/bookmark-notes/409685/1?silent=true) this plugin, turning bookmarks into private personal notes with Markdown, toggle buttons, and privacy controls. [Explore](https://meta.discourse.org/t/bookmark-notes/409685?silent=true)
### #Extras
- **nodeBook: CNL knowledge graphs in posts** – @G_N [introduced](https://meta.discourse.org/t/nodebook-cnl-knowledge-graphs-in-posts-concept-maps-inference-petri-net-simulation/409634/1?silent=true) a new component for rendering interactive knowledge graphs, concept maps, and Petri-net simulations directly in posts. [Dive in](https://meta.discourse.org/t/nodebook-cnl-knowledge-graphs-in-posts-concept-maps-inference-petri-net-simulation/409634?silent=true)
### #General
- **Sport communities and calendar?** – @Fuse [asked](https://meta.discourse.org/t/sport-communities-and-calendar/409643/1?silent=true) how others use the calendar for sports, inspiring ideas about scheduling and chat. [Join](https://meta.discourse.org/t/sport-communities-and-calendar/409643?silent=true)
## Activity by the @Team Group
- @Chrisr **fixed the multisite PostgreSQL upgrade issue** – he [merged](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/49?silent=true) a patch and posted detailed steps to revert and retry. He also [acknowledged](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/48?silent=true) the broken state earlier. Related: [I upgraded to latest and lost everything](https://meta.discourse.org/t/i-upgraded-to-latest-and-lost-everything/409647/5?silent=true)
- @Sam **responded to multiple bugs** – he [thanked](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622/2?silent=true) the contributor of the Redis fix, [suggested](https://meta.discourse.org/t/bounce-score-does-not-reset-when-email-address-is-changed/409581/2?silent=true) a workaround for bounce score reset, and [tagged](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/4?silent=true) @Martin about category permission issues.
- @Martin **discussed category permission changes** – he [explained](https://meta.discourse.org/t/all-members-when-creating-a-category-assigns-everyone/409508/4?silent=true) the intended migration plan and promised a three-button design. He also [acknowledged](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/5?silent=true) the bug report.
- @Chapoi **is actively iterating on the composer redesign** – he [responded](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/31?silent=true) to Horizon theme issues and [asked](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/36?silent=true) @Renato about Enter key behavior.
- @Lindsey **provided direction on automation** – she [replied](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623/2?silent=true) to the calendar event triggers request, steering towards the new Workflows feature.
- @Awesomerobot **approved a plugin PR** – he [commented](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/33?silent=true) on the plugin outlet PR and was thanked by @Merefield for the “approval on a Sunday”.
- @Renato is **investigating the mobile composer paste bug** – confirmed by @Sam in [this post](https://meta.discourse.org/t/problem-pasting-html-into-markdown-composer-on-mobile-until-pasting-once-into-rich-text-editor/409530/3?silent=true).
* * *
That’s the pulse of [meta.discourse.org](http://meta.discourse.org) for the past day – from Postgres rescue missions to bookmark-powered memory palaces. May your upgrades be smooth and your Redis keys be sparse! 🚀
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 11, 2026, 1:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/916 "2026-08-11T13:02:10Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
It was another bustling day on Meta as community members showcased impressive new theme components, debated the finer points of category permissions and DSA compliance, and dove deep into AI agent behavior. 💡
* * *
## Key Stats
Here’s a snapshot of activity on Meta over the last 24 hours:
| Metric | Count |
| --- | --- |
| **New Posts** | 151 |
| **New Topics** | 56 |
| **Total Likes Received** | 227 |
**Top Contributors by Likes**
| User | Posts | Likes |
| --- | --- | --- |
| @Merefield | 11 | 23 |
| @Don | 3 | 21 |
| @Falco | 4 | 18 |
| @Moin | 10 | 14 |
| @Damian_Boon | 6 | 11 |
| @Jagster | 8 | 10 |
| @RGJ | 6 | 9 |
| @Sam | 5 | 9 |
| @One1 | 11 | 8 |
| @NateDhaliwal | 6 | 8 |
* * *
## Interesting Topics
Here are the most interesting and active discussions from the past 24 hours, grouped by category:
### #Theme-component
- @Don unveiled a brand-new **Topic Preview Modal** component that lets you open and interact with topics directly from the topic list without ever leaving it. The component renders the full interactive post stream—including likes, replies, edits, and bookmarks—inside a native modal, and @Damian_Boon quickly contributed a workaround for **Reddit-ish** theme compatibility plus a configurable width [read more](https://meta.discourse.org/t/topic-preview-modal/409712/1?silent=true). @Jagster reported a math rendering glitch that @Don promptly fixed in a [commit](https://meta.discourse.org/t/topic-preview-modal/409712/10?silent=true), and @NateDhaliwal queried why core’s `PostList` wasn’t reused—@Don explained that the interactive post stream and bidirectional loading aren’t supported by that component [read more](https://meta.discourse.org/t/topic-preview-modal/409712/10?silent=true).
- @Manuel quietly updated the **Featured Topics** component to fix a compatibility error reported by @Helga_Razinkova, bringing the component back in line for everyone, and @Cogdog confirmed the fix worked [read more](https://meta.discourse.org/t/featured-topics/217580/70?silent=true).
- @Roi submitted a pull request for the **Clickable Social Icon Links on Profile** component, which @Weallwegot approved and merged shortly afterward [read more](https://meta.discourse.org/t/clickable-social-icon-links-on-profile/158136/106?silent=true).
- @Moin's update to the **Restrict Uploads** component was merged by @Tshenry, meaning the component is now officially improved for everyone [read more](https://meta.discourse.org/t/restrict-uploads/112688/35?silent=true).
- @Moin's **Mobile Composer Preview** component received praise from @Richie for restoring the preview button removed in a recent core change [read more](https://meta.discourse.org/t/mobile-composer-preview/408784/24?silent=true).
### #Plugin
- @Merefield released **Discourse Bookmark Notes** , a plugin that turns bookmarks into private personal notes attached to posts and other bookmarkable content. The plugin keeps notes private per user, supports Markdown editing with preview, and integrates with existing bookmark reminders. A Pro extension available to GitHub sponsors adds a collapsible note panel, extended search, and a sortable notes column on topic lists [read more](https://meta.discourse.org/t/bookmark-notes/409685/1?silent=true). @Jagster loved it (“something I didn’t know I need”), and @Lilly applauded the sponsor-based approach to Pro extensions [read more](https://meta.discourse.org/t/bookmark-notes/409685/4?silent=true).
- @Roi flagged a deprecation warning in the **User Response Times** plugin, which @RGJ acknowledged and said he’d fix in a few weeks [read more](https://meta.discourse.org/t/user-response-times/303542/9?silent=true).
- @Lebron reported ongoing issues with the **Custom Wizard Plugin** —wizards still can’t be accessed on non-staff accounts and settings revert to empty boxes despite saving [read more](https://meta.discourse.org/t/custom-wizard-plugin/73345/973?silent=true).
- A lively debate continued in the **Discourse Fingerprint** topic, with @Overgrow arguing that browser fingerprinting isn’t a real privacy threat and has legitimate security use cases, countered by @Jagster and @Satonotdead pointing to EU legal precedents and class-action lawsuits against companies engaging in fingerprinting [read more](https://meta.discourse.org/t/discourse-fingerprint-browser-fingerprinting-plugin/114890/75?silent=true).
- @Tomve hit a stylesheet import error in the **Landing Pages Plugin** after a recent change, reporting an `ActionView::Template::Error` with a missing `desktop` stylesheet [read more](https://meta.discourse.org/t/landing-pages-plugin/180967/168?silent=true).
### #Self-hosting
- @Wsmwktb asked whether opening a self-hosted Discourse to Discourse ID login poses signicant downsides. @Falco dismantled each of the commonly cited “risks” as hallucinations, concluding that Discourse ID is a solid choice for getting many social logins with zero effort, provided you’re comfortable with not controlling exactly which login methods users see [read more](https://meta.discourse.org/t/are-there-significant-downsides-or-problems-to-opening-my-self-hosted-discourse-to-participating-discourse-sites-accounts/409729/3?silent=true). @Merefield cheekily suggested a staged rollout while linking to a search about the “downsides of walking along a seafront” [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/4?silent=true).
- The **PostgreSQL 18 upgrade** thread continued with @Chrisr announcing a fix for broken multisite upgrades, providing detailed rollback steps for those affected [read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/48?silent=true). @Peternlewis asked about a memory overcommit warning and noted his new database is significantly smaller than the old one, while @Merefield reported the opposite trend on his instance [read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/53?silent=true).
- @Kcahtoor shared an insightful workaround after losing everything in an upgrade, explaining how the Postgres template file only targeted a single DB in multisite setups and providing a shell script to loop through all databases [read more](https://meta.discourse.org/t/i-upgraded-to-latest-and-lost-everything/409647/5?silent=true).
- @Ethsim2 documented a Let’s Encrypt/SSL edge case encountered while moving a standalone Discourse instance to a new VPS, where zero-byte `.cer` files blocked nginx from starting. The fix involved copying both the `ssl/` directory and the `letsencrypt/` state from the old server, with a full write-up on GitHub [read more](https://meta.discourse.org/t/move-your-discourse-instance-to-a-different-server/15721/104?silent=true).
### #Announcements (and #blog)
- @Sam announced the release of **delegated vision support in Discourse AI** , enabling text-only models like DeepSeek v4 Flash to use the full feature set by delegating image understanding to a vision-capable model such as Qwen or Gemma. A new LLM configuration option now allows you to specify a separate model for image handling [read more](https://meta.discourse.org/t/delegated-vision-for-text-only-models-in-discourse-ai/409746/1?silent=true).
- @Chapoi posted a detailed progress update on the **Composer Redesign** , listing fixes implemented (title section rework, tag count, category name overflow, rounded borders) and feedback being worked on (keyboard behavior, flashy blue highlight, numeric tag counts) [read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/39?silent=true). @Jagster reported a toolbar visibility bug that follows the original composer’s toolbar toggle state, which @Chapoi confirmed [read more](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/38?silent=true).
- The blog post **“Introducing the All-New Admin Dashboard”** was published, and @Ed_S suggested adding a System section to make system stats (version, updates, disk space, backups) more visible [read more](https://meta.discourse.org/t/introducing-the-all-new-admin-dashboard/409764/2?silent=true).
- @Don shared insights from experimenting with animated SVGs for the **Discourse splash screen** , explaining that animating complex paths directly inside SVGs causes lag on mobile; wrapping the SVG in an HTML container and applying CSS transforms to the wrapper provides much smoother performance [read more](https://meta.discourse.org/t/branding-the-discourse-splash-screen-with-custom-svg-images/395100/34?silent=true).
- @Moin clarified that the **Ideas category type** now acts as the toggle for Topic Voting; removing the type disables voting in that category [read more](https://meta.discourse.org/t/easily-create-ideas-categories-using-the-topic-voting-plugin/399365/4?silent=true).
### #Support
- @AkarinLiu was struggling to find the Font Awesome “seedling” icon in Discourse. @Zogstrip explained it’s not in the default icon list and must be added to the `SVG icon subset` setting. @Moin then walked through the steps, pointing out the regular (`far-`) version is a Pro icon while the solid version works once you add it without a prefix. @AkarinLiu eventually realized they’d typed an extra prefix, quipping “I’m so silly, something that could have been done in a few minutes wasted dozens of them” [read more](https://meta.discourse.org/t/discourse-fa-seeding/409783/4?silent=true).
- @Karthik_K1 asked how to restrict an AI Agent to only answer forum-related questions. @NateDhaliwal suggested using the Forum Researcher or Forum Helper agents, but @Karthik_K1 showed that even Forum Helper answered general questions. @Falco then clarified that the test used the “Creative” agent, which has no system prompt, and recommended crafting a custom agent with a system prompt specifying how and when to answer—as done on [ask.discourse.com](http://ask.discourse.com) [read more](https://meta.discourse.org/t/how-can-i-restrict-an-ai-agent-to-answer-only-questions-related-to-my-forum/409672/5?silent=true).
- @NateDhaliwal reported that topics in muted categories don’t appear in `/?state=muted`, and @Awesomerobot confirmed this is a gap—muted category topics are simply excluded from that view [read more](https://meta.discourse.org/t/how-do-i-access-topics-in-muted-categories/409676/2?silent=true).
- @Soumya_Ranjan_Mishra asked about configuring self-hosted Claude/GPT API keys in Discourse AI. @Satonotdead guided them to use the OpenAI provider for OpenAI-compatible endpoints and to consult the LLM docs for specific proxies, while @Merefield offered paid support via GitHub sponsorship [read more](https://meta.discourse.org/t/is-there-any-built-in-chatbot-or-conversational-assistant-available-in-discourse/409513/9?silent=true).
- @Moin confirmed that switching the interface language via the header dropdown no longer resets the content translation preference, saying “changing the interface language… no longer resets the content translation preference” [read more](https://meta.discourse.org/t/is-resetting-the-original-content-preference-when-switching-interface-language-in-the-header-dropdown-intended/406258/2?silent=true).
- @One1 shared a detailed investigation of a **mail-receiver deprecation warning** persisting on the latest release image, tracing it to the mail-receiver code still posting the `email` parameter instead of `email_encoded` [read more](https://meta.discourse.org/t/mail-receiver-deprecation-warning-on-email-parameter/363900/2?silent=true).
### #Data-&-reporting
- @Jay-C raised the new **DSA standardised Content Moderation Transparency Report** requirements, explaining that Discourse’s current moderation tools can’t capture structured data like custom suspension reasons aligned with the DSA taxonomy, illegal-content vs. ToS violation indicators, contractual basis, or information source. @HAWK, acknowledging they weren’t aware of the new template, committed to doing due diligence with their lawyer and coming back [read more](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/3?silent=true).
### #Marketplace
- @Thadeus confirmed they will proceed with @Pacharanero for their **Discourse UX Overhaul & Plugin Audit** RFP, and left individual feedback for all other applicants [read more](https://meta.discourse.org/t/rfp-discourse-ux-overhaul-theme-customization-plugin-audit/408040/9?silent=true).
### #ux
- @Sterretje noticed a discrepancy between the _All_, _Replies_, and _Topics_ tabs in user activity—the Topics tab doesn’t show post excerpts. @Moin explained this is by design: topic-focused activity uses a topic-list style, while post-focused activity benefits from content snippets. @Awesomerobot noted it would be possible to display excerpts with a theme component, and suggested improving vague topic titles (or using the Workflows plugin to auto-improve them) [read more](https://meta.discourse.org/t/discrepancy-in-display-of-user-activity-all-replies-vs-topic/409671/3?silent=true).
- @Martin acknowledged that the “All members” option in new category creation assigning `everyone` is an unintended side effect and agreed with @RGJ's suggestion to have three distinct buttons (public, members only, private) instead [read more](https://meta.discourse.org/t/all-members-when-creating-a-category-assigns-everyone/409508/4?silent=true).
- @LWinterberg proposed replacing yes/no actions in the moderation review queue with concrete action buttons like **Approve/Delete** , to avoid the cognitive load of parsing questions where “Yes” means opposite things in rapid succession. @One1 suggested going further with “Approve Topic”/“Reject Topic” labels [read more](https://meta.discourse.org/t/moderation-avoid-yes-no-actions/409773/1?silent=true).
- @One1 asked about creating a documentation category through the new simplified category creation flow, and @HAWK pointed to the Discourse Doc Categories plugin and suggested creating a normal discussion category first [read more](https://meta.discourse.org/t/more-friendly-category-creation/390841/21?silent=true).
### #Feature
- @One1 proposed **Previous/Next links for topics in Doc Categories** , suggesting the category index could drive linear navigation with custom titles from the sidebar. @Moin noted the idea of using doc index sections has come up before, and @Satonotdead echoed that it’s a frequently requested feature for LMS content [read more](https://meta.discourse.org/t/previous-next-links-for-topics-in-doc-categories/409780/1?silent=true).
- @Gormus suggested adding a list of changed core and plugin settings to the Discourse Releases changelog and comparison views, similar to what `staff_action_logs` records [read more](https://meta.discourse.org/t/add-a-list-of-changed-core-and-plugin-settings-in-releases/409703/1?silent=true).
- @One1 bumped the long-running **personal notes on posts** feature request with a link to @Merefield's new Bookmark Notes plugin, which fulfills most of the request [read more](https://meta.discourse.org/t/add-support-for-personal-notes-on-posts/261798/34?silent=true).
- @One1 revived a request for **scrollable footnotes** , and @Canapin demonstrated the glitchy mobile behavior with a screen recording, while @Jagster emphasized that footnotes are crucial for displaying AI-generated explanations [read more](https://meta.discourse.org/t/could-long-footnotes-be-scrollable/409613/3?silent=true).
- @Lindsey responded to a request for **webhook triggers and automations in Discourse Calendar & Events** , noting that the new Workflows feature is likely to supersede the Automations plugin, and these trigger types are “definitely on the table for Workflows” [read more](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623/2?silent=true).
### #bug
- @RGJ raised concerns about the new **category permission groups** during beta, specifically the `anonymous_users` and `logged_in_users` groups. @Martin acknowledged the concerns and discussed possible validations, while @RGJ pushed back with examples of admin friction and implicit-permission complexity, leading @Martin to agree the OP is a bug that will be fixed in the interim [read more](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/7?silent=true).
- @Falco provided a fix for the **CDCK/MoM citations** issue where summaries cited posts as “User1, User2, etc.” via pull request [read more](https://meta.discourse.org/t/cdck-mom-cites-posts-as-user1-user2-etc-llm-quality-issue/409526/4?silent=true).
- @Tannerabread fixed the **white screen on theme export** in Theme Creator for the PWA, with a follow-up needed for the Hub [read more](https://meta.discourse.org/t/in-theme-creator-exporting-themes-results-in-a-white-screen/403108/8?silent=true).
- @Sam acknowledged a bug report about **bounce score not resetting when a user’s email address changes** , agreeing the real fix is to stop associating bounce score with users entirely and inviting a PR [read more](https://meta.discourse.org/t/bounce-score-does-not-reset-when-email-address-is-changed/409581/2?silent=true).
- @Sam thanked @Zogstrip for merging a fix in **avoiding Redis key traversal when clearing the 404 topic cache** [read more](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622/2?silent=true).
### #development
- @Damian_Boon thanked @Don for getting the **Facebook-style topic modal** working, calling it “exactly what I was trying to achieve” [read more](https://meta.discourse.org/t/facebook-style-topic-modal-is-it-better/408565/33?silent=true).
### #Migration
- @Gosia.Murawska asked whether **accepted solution markers from Khoros** can be carried over during import, and @Italo confirmed yes—as long as the plugin is active during the import [read more](https://meta.discourse.org/t/accepted-solutions-plugin-migrating-markers-from-khoros/409686/2?silent=true).
### #Community Building
- @OS_Corsair asked how to grow their new community at [corsairsoscorsairs.discourse.group](http://corsairsoscorsairs.discourse.group). @HAWK pointed to community-building resources and asked for more context, while @Jagster noted the name felt more product-oriented than community-oriented, and @Merefield advised filling it with lots of relevant content to attract search traffic [read more](https://meta.discourse.org/t/how-do-i-grow-my-community/409760/5?silent=true).
### #General
- @Geoff asked about using the **Discourse Calendar for sport communities** , and @Lilly shared her experience using it for a football schedule, including exporting the league schedule and training a bot to populate game dates [read more](https://meta.discourse.org/t/sport-communities-and-calendar/409643/2?silent=true).
* * *
## Activity by the @Team Group
A productive day for the Discourse core team, spread across announcements, fixes, and design iterations:
- @Sam released **delegated vision support** for text-only models in Discourse AI, a significant new capability detailed in the [announcement topic](https://meta.discourse.org/t/delegated-vision-for-text-only-models-in-discourse-ai/409746/1?silent=true). He also thanked @Zogstrip for merging the [404 cache fix](https://meta.discourse.org/t/fix-avoid-traversing-redis-keys-when-clearing-404-topic-cache/409622/2?silent=true) and weighed in on the [bounce score bug](https://meta.discourse.org/t/bounce-score-does-not-reset-when-email-address-is-changed/409581/2?silent=true), proposing the real fix is to decouple bounce score from users entirely.
- @Zogstrip answered a [support question](https://meta.discourse.org/t/discourse-fa-seeding/409783/2?silent=true) about the “seedling” Font Awesome icon, explaining how to add it via the SVG icon subset setting.
- @Chapoi handled the ongoing [Composer Redesign feedback thread](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/39?silent=true), implementing several fixes (title reformatting, category/tag overflow, rounded borders, preview margin) and confirming he’s working through remaining keyboard and highlight feedback.
- @Awesomerobot discussed the [user activity topic excerpt gap](https://meta.discourse.org/t/discrepancy-in-display-of-user-activity-all-replies-vs-topic/409671/6?silent=true), suggesting a theme component approach and recommending title quality improvements, and confirmed the [muted categories gap](https://meta.discourse.org/t/how-do-i-access-topics-in-muted-categories/409676/2?silent=true) in the `?state=muted` view.
- @Martin acknowledged the “All members” category creation bug and committed to a fix with three buttons (public, members only, private) in [this topic](https://meta.discourse.org/t/all-members-when-creating-a-category-assigns-everyone/409508/4?silent=true). He also engaged deeply with @RGJ on the [category permissions discussion](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/8?silent=true), sharing his vision for future ACL-based permission UIs while agreeing the interim bug needs fixing.
- @Tannerabread fixed the [theme export white screen issue](https://meta.discourse.org/t/in-theme-creator-exporting-themes-results-in-a-white-screen/403108/8?silent=true) for the PWA, with a Hub follow-up planned.
- @HAWK responded to the [DSA compliance topic](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/3?silent=true), acknowledging the new standardised transparency template and committing to review it with legal counsel. He also offered welcoming advice and community-building resources to [a new community owner](https://meta.discourse.org/t/how-do-i-grow-my-community/409760/5?silent=true).
- @Lindsey indicated that the [Discourse Calendar & Events webhook/automation request](https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623/2?silent=true) is “definitely on the table for Workflows,” signaling a shift away from the older Automations plugin.
* * *
_From topic modals that keep you browsing without a single click lost, to bookmark notes that finally remember what you were thinking — yesterday’s activity proved that the Discourse community can turn any “what if” into a shipped feature before lunch… just don’t ask us how much coffee was involved!_ ☕
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 12, 2026, 1:08 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/917 "2026-08-12T13:08:03Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
In the last 24 hours, [meta.discourse.org](http://meta.discourse.org) saw **171 new posts** across **56 topics** , receiving **214 likes** in total. The most active members were:
- @Moin — **15 posts** , **30 likes**
- @HAWK — **8 posts** , **20 likes**
- @Zogstrip — **4 posts** , **13 likes**
- @One1 — **12 posts** , **10 likes**
- @NateDhaliwal — **7 posts** , **10 likes**
- @Merefield — **9 posts** , **9 likes**
- @Ed_S — **4 posts** , **8 likes**
- @Canapin — **2 posts** , **8 likes**
- @Satonotdead — **11 posts** , **7 likes**
- @Lilly — **4 posts** , **7 likes**
## Interesting Topics
### #Community Building
- [How do I grow my community?](https://meta.discourse.org/t/-/409760?silent=true) – @OS_Corsair asked for advice on growing a newly formed FOSS community. @HAWK pointed to the [community lifecycle guide](https://blog.discourse.org/2025/11/the-community-lifecycle-from-launch-to-legacy/) and @Moin encouraged starting with concrete content, asking _“Why would someone join your forum?”_ The thread eventually ended with @Darkpixlz suggesting a fresh start. ([post 1](https://meta.discourse.org/t/-/409760/1?silent=true), [post 7](https://meta.discourse.org/t/-/409760/7?silent=true), [post 17](https://meta.discourse.org/t/-/409760/17?silent=true), [post 23](https://meta.discourse.org/t/-/409760/23?silent=true))
### #Support
- [Discourse 的 FA 图标 seeding 在哪里呢？](https://meta.discourse.org/t/-/409783?silent=true) – @AkarinLiu sought a missing icon; @Zogstrip explained it’s not part of the default list, and @Moin demonstrated adding it to the **SVG icon subset**. The fix involved using the correct prefix, and @Zogstrip later promised better icon search/pagination. ([post 2](https://meta.discourse.org/t/-/409783/2?silent=true), [post 7](https://meta.discourse.org/t/-/409783/7?silent=true), [post 10](https://meta.discourse.org/t/-/409783/10?silent=true))
- [How do I remove silences from flags?](https://meta.discourse.org/t/-/409787?silent=true) – @Wasd_The_Fourth asked about disabling auto‑silence; @Awesomerobot and @Moin clarified the relevant site settings, noting that TL3 users shouldn’t be affected. The mystery remains why they were. ([post 1](https://meta.discourse.org/t/-/409787/1?silent=true), [post 2](https://meta.discourse.org/t/-/409787/2?silent=true), [post 3](https://meta.discourse.org/t/-/409787/3?silent=true))
- [How can I restrict an AI Agent to answer only questions related to my forum?](https://meta.discourse.org/t/-/409672?silent=true) – @Karthik_K1 showed how easily a chatbot can be tricked. @Falco suggested two‑pass workflows or fine‑tuned models, while @Merefield promoted his chatbot’s new _blocked‑question gate_. ([post 7](https://meta.discourse.org/t/-/409672/7?silent=true), [post 8](https://meta.discourse.org/t/-/409672/8?silent=true), [post 9](https://meta.discourse.org/t/-/409672/9?silent=true))
- [Where do l create the banner topic?](https://meta.discourse.org/t/-/409896?silent=true) – @OS_Corsair wanted a site‑wide banner; @NateDhaliwal provided the [official guide](https://meta.discourse.org/t/creating-a-banner-to-display-at-the-top-of-your-site/153718?silent=true) and @Twofoursixeight mentioned the pin‑to‑banner option. ([post 1](https://meta.discourse.org/t/-/409896/1?silent=true), [post 2](https://meta.discourse.org/t/-/409896/2?silent=true), [post 3](https://meta.discourse.org/t/-/409896/3?silent=true))
### #enterprise
- [Ask me anything about the new admin dashboard](https://meta.discourse.org/t/-/409830?silent=true) – @Lindsey hosted a lively AMA about the redesigned dashboard. She answered questions on report automation, non‑admin access, and hinted at a future traffic explorer. @HAWK and @One1 debated the roles of community managers vs. admins. ([post 1](https://meta.discourse.org/t/-/409830/1?silent=true), [post 3](https://meta.discourse.org/t/-/409830/3?silent=true), [post 11](https://meta.discourse.org/t/-/409830/11?silent=true))
### #Theme component
- [Topic Preview Modal](https://meta.discourse.org/t/-/409712?silent=true) – @Don released fixes for math rendering and added configurable width. @Damian_Boon demonstrated a swipe‑to‑close mobile enhancement, and @Eisammy questioned the CSS border‑top. The component is gaining traction for improving reading flow. ([post 10](https://meta.discourse.org/t/-/409712/10?silent=true), [post 11](https://meta.discourse.org/t/-/409712/11?silent=true), [post 14](https://meta.discourse.org/t/-/409712/14?silent=true))
### #Feature
- [Previous/Next links for topics in Doc Categories](https://meta.discourse.org/t/-/409780?silent=true) – @One1 requested automatic previous/next navigation based on the category index. @Moin linked to an earlier idea, and @Satonotdead supported the feature for LMS content. ([post 1](https://meta.discourse.org/t/-/409780/1?silent=true), [post 2](https://meta.discourse.org/t/-/409780/2?silent=true), [post 3](https://meta.discourse.org/t/-/409780/3?silent=true))
- [Could long footnotes be scrollable?](https://meta.discourse.org/t/-/409613?silent=true) – @Zogstrip merged a [PR](https://github.com/discourse/discourse/pull/42516) to make long footnotes scrollable, closing a related mobile scrolling bug. ([post 7](https://meta.discourse.org/t/-/409613/7?silent=true))
### #Announcements
- [Help Us Test the Composer Redesign](https://meta.discourse.org/t/-/407849?silent=true) – @Chapoi implemented several fixes: visual grip, tag count, and rounded borders, while still working on keyboard animations. @Canapin video‑documented lagging drag and praised the redesign overall. ([post 39](https://meta.discourse.org/t/-/407849/39?silent=true), [post 40](https://meta.discourse.org/t/-/407849/40?silent=true))
- [PostgreSQL 18 update for self‑hosters](https://meta.discourse.org/t/-/406194?silent=true) – Self‑hosters shared upgrade tales: @Peternlewis worried about overcommit warnings, @Agemo hit disk‑space issues and reverted, and @Andrew_Rowe succeeded with tips from @Lilly. ([post 52](https://meta.discourse.org/t/-/406194/52?silent=true), [post 56](https://meta.discourse.org/t/-/406194/56?silent=true), [post 59](https://meta.discourse.org/t/-/406194/59?silent=true))
### #Plugin
- [Bookmark Notes](https://meta.discourse.org/t/-/409685?silent=true) – @Merefield released Pro updates with easier note editing and unfurling. @Eviepayne’s compatibility question was answered by @Moin – the plugin requires a newer core outlet. ([post 5](https://meta.discourse.org/t/-/409685/5?silent=true), [post 7](https://meta.discourse.org/t/-/409685/7?silent=true), [post 9](https://meta.discourse.org/t/-/409685/9?silent=true))
### #General
- [Sport communities and calendar?](https://meta.discourse.org/t/-/409643?silent=true) – @Fuse asked about calendar usage in sport communities; @Lilly shared how she runs a football schedule bot and links game discussions, though engagement didn’t change much. ([post 2](https://meta.discourse.org/t/-/409643/2?silent=true), [post 4](https://meta.discourse.org/t/-/409643/4?silent=true))
### #bug
- [Category permissions and the new permission groups](https://meta.discourse.org/t/-/409511?silent=true) – @Martin detailed his plans to overhaul category permissions with validation, while @RGJ raised concerns about complexity and implicit permissions. The immediate bug will be fixed shortly. ([post 8](https://meta.discourse.org/t/-/409511/8?silent=true), [post 9](https://meta.discourse.org/t/-/409511/9?silent=true))
## Activity by the @Team Group
- @Zogstrip assisted with icon seeding by explaining the SVG icon subset and later promised improved search/pagination ([icon topic](https://meta.discourse.org/t/-/409783/2?silent=true)). He also merged the scrollable footnotes fix ([footnotes PR](https://meta.discourse.org/t/-/409613/7?silent=true)).
- @Lindsey ran the admin dashboard AMA, answering questions on automation and non‑admin access, and teased a future traffic explorer ([AMA response](https://meta.discourse.org/t/-/409830/3?silent=true)).
- @Chapoi implemented multiple composer redesign fixes based on community feedback ([composer feedback](https://meta.discourse.org/t/-/407849/39?silent=true)).
- @Awesomerobot clarified auto‑silence settings and identified the “First‑post checklist” as a third‑party plugin feature ([silence settings](https://meta.discourse.org/t/-/409787/2?silent=true), [first‑post checklist](https://meta.discourse.org/t/-/409845/2?silent=true)).
- @Falco discussed AI agent restrictions, suggesting workflows or fine‑tuned models as more reliable than prompts ([AI restriction](https://meta.discourse.org/t/-/409672/9?silent=true)).
- @Martin shared his roadmap for category permission improvements and acknowledged the current bug ([category permissions](https://meta.discourse.org/t/-/409511/8?silent=true)).
- @Tshenry merged @Moin’s update to the Restrict Uploads component ([restrict uploads](https://meta.discourse.org/t/-/112688/35?silent=true)).
- @Angus updated the Custom Wizard plugin to fix a non‑admin issue and provided a demonstration ([custom wizard](https://meta.discourse.org/t/-/73345/976?silent=true), [video proof](https://meta.discourse.org/t/-/73345/978?silent=true)).
- @Tannerabread confirmed a fix for email privacy mode, linking to a pending PR that re‑adds topic links in outgoing emails ([email fix](https://meta.discourse.org/t/-/401078/3?silent=true)).
* * *
From icon hunts to database migrations, the community keeps tackling every curveball — and if yesterday taught us anything, it’s that a good footnote scroll can make all the difference! 🎈
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 13, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/918 "2026-08-13T13:01:07Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
Over the last 24 hours, the community produced **117 new posts** and **45 new topics** , with **164 likes** distributed across them. The most active contributors were:
- @Moin — 20 posts, 22 likes
- @Awesomerobot — 5 posts, 14 likes
- @NateDhaliwal — 6 posts, 12 likes
- @HAWK — 5 posts, 12 likes
- @Renato — 1 post, 11 likes
- @Don — 6 posts, 9 likes
- @Lindsey — 2 posts, 9 likes
- @Darkpixlz — 4 posts, 8 likes
- @Tannerabread — 5 posts, 7 likes
- @J.Jaffeux — 2 posts, 5 likes
## Interesting Topics
### #Community Building
- @OS_Corsair asked how to **grow their community** but struggled to articulate a clear purpose. @NateDhaliwal and @HAWK pressed for specifics, @Moin questioned the value proposition, and @Darkpixlz suggested the thread had run its course, recommending the user read existing advice. [read more](https://meta.discourse.org/t/how-do-i-grow-my-community/409760?silent=true)
### #Support
- @OS_Corsair asked where to **create a banner topic**. @NateDhaliwal linked to the official guide, @Twofoursixeight mentioned the pinning option, but @OS_Corsair shared confusing screenshots. @Awesomerobot advised more research and experimentation before asking. [read more](https://meta.discourse.org/t/where-do-l-create-the-banner-topic/409896?silent=true)
- @Rinion reported that the **AI bot kept auto-adding them to a private chat channel** even though AI was disabled. @Gabriel acknowledged the issue, implemented a fix, and confirmed that disabling the AI plugin or muting the channel should prevent it. [read more](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914?silent=true)
- @Wasd_The_Fourth wanted to know how to **remove silences from flags** for minor infractions. @Moin linked to documentation on custom flags and questioned why off-topic flags would lead to automatic silences. [read more](https://meta.discourse.org/t/how-do-i-remove-silences-from-flags/409787?silent=true)
- A user asked about **FA icon seeding** in Discourse. @Zogstrip acknowledged good points and created a [pull request](https://github.com/discourse/discourse/pull/42554) to add proper search and pagination to the icon picker. [read more](https://meta.discourse.org/t/discourse-fa-seeding/409783?silent=true)
- @Marcozambi faced a **restore failure due to S3 migration issues**. @Awesomerobot explained how to list missing uploads using `rake posts:missing_uploads` and suggested marking them as ignored to proceed. [read more](https://meta.discourse.org/t/restore-fails-due-to-s3-migration-failure/409771?silent=true)
### #enterprise
- In the **admin dashboard AMA** thread, @One1 asked if community managers could access the dashboard without admin rights. @HAWK questioned the trust level, @Ed_S noted the difference between admin and community manager roles, and @Nickdb requested drill-down capabilities for user agents and geographies. @Lindsey confirmed a more detailed traffic explorer is in the works. [read more](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830?silent=true)
- @Chau started a discussion about **Voice of the Customer programs** and how communities fit into them, inviting examples from others. Several people shared their experiences and asked clarifying questions. [read more](https://meta.discourse.org/t/how-does-community-fit-into-your-voice-of-the-customer-program/409947?silent=true)
### #Announcements
- @Renato announced that **pinned chat messages now stay in view with a sticky bar**. The bar follows the user as they scroll, is dismissible, and can be managed through the existing pinning interface. Feedback is welcome. [read more](https://meta.discourse.org/t/pinned-chat-messages-now-stay-in-view-with-a-sticky-bar/409089?silent=true)
- In the **Workflows preview** topic, @Satonotdead asked when to use Automations vs. Workflows. @Lindsey recommended Workflows even for simple processes due to flexibility and visibility, and @J.Jaffeux invited users to report anything they can’t do in Workflows but could in Automations. [read more](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990?silent=true)
- The **Solved improvements** topic discussed allowing members to indicate they experience a reported issue. @Sterretje asked if the button disappears when a solution is marked, and @Moin confirmed with examples. [read more](https://meta.discourse.org/t/solved-improvements-allowing-members-to-indicate-theyre-experiencing-a-reported-issue/402498?silent=true)
- @Jordan.Vidrine announced that the **Post Type composer actions dropdown** is moving to permanent and will be merged into core next week. [read more](https://meta.discourse.org/t/introducing-a-new-post-type-composer-actions-dropdown/403635?silent=true)
### #bug
- @Moin reported a **sticky unread reply notification** that couldn’t be cleared. @Tannerabread reproduced it, found a fix in another PR, and confirmed the issue was resolved. [read more](https://meta.discourse.org/t/sticky-unread-reply-notification/384961?silent=true)
- @Kairo162 complained that **Discourse was sending email app notifications** instead of normal push notifications. @NateDhaliwal explained email notification settings and suggested adjusting them to “only when away.” [read more](https://meta.discourse.org/t/discourse-is-sending-me-email-app-notifications-instead-of-normal-notifications/409952?silent=true)
- @Mr.Xurrent reported a **missing admin sidebar** on their forum. @Moin helped debug with [safe mode](https://meta.discourse.org/t/53504?silent=true), found console errors linked to a known issue, and recommended further checks. [read more](https://meta.discourse.org/t/admin-seitenleiste-nicht-mehr-vorhanden/409913?silent=true)
### #Plugin
- @Don introduced a **Custom Splash HTML Builder** plugin that allows admin-defined HTML/CSS for splash screens, with better mobile performance than animated SVGs. The post includes before/after videos and detailed explanations. [read more](https://meta.discourse.org/t/custom-splash-html-builder/409871?silent=true)
### #Data & reporting
- @Jay-C asked about **DSA Content Moderation Reporting** and statements of reasons, but declined to identify their employer. @HAWK offered help and asked for specifics about gaps. [read more](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681?silent=true)
## Activity by the @Team Group
- @Lindsey participated in the **admin dashboard AMA** , confirming a traffic explorer is in development, and advised using Workflows for simple processes in the **Workflows preview** thread. [admin dashboard](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830/12?silent=true) · [workflows](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990/23?silent=true)
- @Renato announced the **sticky pinned chat message bar** and detailed its functionality. [read more](https://meta.discourse.org/t/pinned-chat-messages-now-stay-in-view-with-a-sticky-bar/409089/1?silent=true)
- @Tannerabread fixed the **sticky unread reply notification** bug and also resolved the related “Can’t clear unread notification after being removed from a PM” issue. [sticky notification](https://meta.discourse.org/t/sticky-unread-reply-notification/384961/8?silent=true) · [PM notification](https://meta.discourse.org/t/cant-clear-unread-notification-after-being-removed-from-a-pm/311995/23?silent=true)
- @Awesomerobot helped with **banner topic** guidance, explained the **missing uploads rescue process** , and discussed caching in the **Allow clearing cache** topic. [banner](https://meta.discourse.org/t/where-do-l-create-the-banner-topic/409896/6?silent=true) · [restore](https://meta.discourse.org/t/restore-fails-due-to-s3-migration-failure/409771/2?silent=true) · [caching](https://meta.discourse.org/t/allow-clearing-cache/408791/2?silent=true)
- @Gabriel fixed the **AI bot chat channel** issue and confirmed the behavior in a reply. [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)
- @Zogstrip addressed the **FA icon seeding** problem and submitted a pull request to improve the icon picker. [read more](https://meta.discourse.org/t/discourse-fa-seeding/409783/13?silent=true)
- @Jordan.Vidrine announced the **Post Type composer dropdown** is moving to permanent and will be merged into core. [read more](https://meta.discourse.org/t/introducing-a-new-post-type-composer-actions-dropdown/403635/19?silent=true)
- @Sam engaged in the **AI agent skills** discussion, acknowledging the complexity and hinting at potential new concepts in Discourse AI. [read more](https://meta.discourse.org/t/giving-discourse-ai-agent-skills/408666/9?silent=true)
- @Martin handled approvals for theme components and discussed permission groups, migration strategies, and setting validations. [granular permissions](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/35?silent=true) · [category permissions](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/12?silent=true)
- @NateDhaliwal provided support on multiple topics, including **banner creation** , **email notifications** , and **muted category access** , and also worked on a **TL3 progress plugin**. [banner](https://meta.discourse.org/t/where-do-l-create-the-banner-topic/409896/2?silent=true) · [email](https://meta.discourse.org/t/discourse-is-sending-me-email-app-notifications-instead-of-normal-notifications/409952/2?silent=true) · [muted categories](https://meta.discourse.org/t/how-do-i-access-topics-in-muted-categories/409676/4?silent=true) · [TL3 plugin](https://meta.discourse.org/t/now-in-beta-plugin-to-see-tl3-progress-for-tl2-users/408543/29?silent=true)
* * *
And yesterday’s cosmic eclipse may have been overshadowed by a meteor shower of pinned messages, but at least we got some sticky notifications out of it! 🌠
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 14, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/919 "2026-08-14T13:01:31Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
Over the last 24 hours, **[meta.discourse.org](http://meta.discourse.org)** saw **106 new posts** spread across **46 topics** — a lively day of discussion, development, and community support. The most active contributors by likes and posts were:
| User | Likes | Posts |
| --- | --- | --- |
| @Moin | 20 | 16 |
| @Sam | 14 | 2 |
| @NateDhaliwal | 10 | 5 |
| @Don | 9 | 7 |
| @Awesomerobot | 8 | 1 |
| @WorldIsMine | 8 | 1 |
| @HAWK | 5 | 6 |
| @Rosiesherry | 5 | 4 |
| @Rinion | 4 | 4 |
| @Agemo | 3 | 5 |
These numbers reflect the breadth of engagement—from feature requests and bug reports to plugin updates and lively enterprise discussions.
* * *
## Interesting Topics
Below is a selection of the most compelling conversations from the past 24 hours, grouped by category. Each entry includes a brief recap and a direct link to the discussion.
### #Feature
- **The delete user button in moderation queue is evil and needs a secondary prompt** — @WorldIsMine flagged a dangerous UX issue: admins can accidentally delete a legitimate user while trying to delete a post in the moderation queue. @Moin linked to an earlier similar report, and @Awesomerobot confirmed a fix is in progress via a PR that adds a confirmation step for irreversible actions. [read more](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025?silent=true)
- **Redirect the landing page for each subcategory to index file by default for documentation categories** — @Sren-1 shared a JavaScript workaround to automatically open a doc category with its index topic, while others discussed the need for a built-in option. The thread includes code samples and thoughts on improving navigation for documentation-heavy forums. [read more](https://meta.discourse.org/t/redirect-the-landing-page-for-each-subcategory-to-index-file-by-default-for-documentation-categories/409470?silent=true)
- **Add option of Start date to RSS Polling plugin** — @Heliosurge requested a start date option for RSS polling, to limit how much content is pulled from long-running feeds. @Moin asked for the use case, and the discussion touched on filtering strategies. [read more](https://meta.discourse.org/t/add-option-of-start-date-to-rss-polling-plugin/410065?silent=true)
### #Announcements
- **Discourse AI subagents** — @Sam announced that subagent support has landed in Discourse AI, allowing users to delegate work to other agents, mix models, and increase concurrency. This is a major step forward for AI integration. [read more](https://meta.discourse.org/t/discourse-ai-subagents/410055?silent=true)
- **PostgreSQL 18 update for self-hosters** — @Moin and @NateDhaliwal shared their experiences with the forced Postgres 18 upgrade, including a detailed workaround for those hitting errors. @NateDhaliwal warned that a ChatGPT-generated fix may wipe the database, while @Moin stressed the need for careful backup. [read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194?silent=true)
- **Solved improvements: Allowing members to indicate they’re experiencing a reported issue** — @Sterretje asked whether the “I have this problem too” button disappears when a reply is marked as a solution. @Moin confirmed it does, and linked to an example. The thread discusses rollout and UX of the solved feature. [read more](https://meta.discourse.org/t/solved-improvements-allowing-members-to-indicate-theyre-experiencing-a-reported-issue/402498?silent=true)
### #Support
- **AI bot keeps auto-adding me to a private chat channel even though disabled?** — @Rinion reported an annoying bug where the AI bot re-adds them to a private chat despite being disabled. @Gabriel and @Moin helped troubleshoot, ultimately manually removing the channel and deploying a fix. The thread also explains how updates work for hosted sites. [read more](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914?silent=true)
- **Discourse is sending me email app notifications instead of normal notifications** — @Kairo162 was puzzled by receiving only email notifications. @NateDhaliwal explained the difference between email and push notifications and suggested checking preferences; further oddities were discussed. [read more](https://meta.discourse.org/t/discourse-is-sending-me-email-app-notifications-instead-of-normal-notifications/409952?silent=true)
### #Plugin
- **Custom Wizard Plugin 🧙** — @Angus fixed several reported issues and merged PRs (including one for non-admin user creation). @Satonotdead and @Eviepayne shared persistent problems, and @Angus suggested community contributions. The thread also discusses the plugin’s maintenance status. [read more](https://meta.discourse.org/t/custom-wizard-plugin/73345/981?silent=true)
- **Custom Splash HTML Builder** — @Don announced an update that adds a `data-color-scheme` attribute to `#d-splash`, allowing for light/dark splash logos with proper CSS handling. @Agemo praised the feature as a long-awaited improvement. [read more](https://meta.discourse.org/t/custom-splash-html-builder/409871?silent=true)
- **ActivityPub Plugin** — @Tobiaseigen reported an issue where images from federated posts appear multiple times in Mastodon, suspecting a misconfiguration. The thread explores activitypub behavior and possible causes. [read more](https://meta.discourse.org/t/activitypub-plugin/266794/489?silent=true)
### #Theme component
- **Guest Gate Theme Component** — @Don gave a comprehensive preview of Guest Gate 2.0, detailing a redesigned trigger system (page views, time, scroll, lightbox), new repeat behaviors, delayed display, and modernized implementation. The update promises backward compatibility and automatic migration of settings. [read more](https://meta.discourse.org/t/guest-gate-theme-component/225107/161?silent=true)
- **Quick Quote Theme Component** — @Merefield modernized the component and shared the PR, noting that its necessity may decrease with the built-in Nested View option. [read more](https://meta.discourse.org/t/quick-quote-theme-component/143621/66?silent=true)
### #enterprise
- **Public vs private discussion** — @Rosiesherry and @HAWK engaged in a thoughtful debate about giving users granular control over content visibility, including AI crawlers and search indexing. @Jagster raised real-world concerns about users wanting to block AI scraping while allowing search engines. [read more](https://meta.discourse.org/t/public-vs-private-discussion/409484?silent=true)
- **Ask me anything about the new admin dashboard** — @One1 shared insights about community managers’ roles and privileges, and @HAWK asked clarifying questions about trust levels and permissions. The discussion also touches on potential improvements for admin controls. [read more](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830/14?silent=true)
- **Scalable engagement models** — @Rosiesherry described a successful program of unscripted 1:1 video conversations that brings new contributors into the fold. @HAWK asked for examples, and @Rosiesherry shared links to interview titles (content behind a paywall). [read more](https://meta.discourse.org/t/scalable-engagement-models/409187/7?silent=true)
### #Data & reporting
- **DSA Content Moderation Reporting + Statements of Reasons Requirements** — @HAWK announced that the team is spec’ing out work to add data fields for the machine-readable report and SOR database submissions, responding to @Jay-C's earlier request. [read more](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/9?silent=true)
* * *
## Activity by the @Team Group
The members of the @Team group were quite active yesterday, contributing to a wide range of topics. Highlights include:
- @Sam announced **Discourse AI subagents** with a detailed post explaining the new feature and linking to the AI Agents documentation. He also followed up on **Giving Discourse AI agent skills** , discussing the possibility of introducing a top-level concept for “skills” in Discourse AI. [AI subagents](https://meta.discourse.org/t/discourse-ai-subagents/410055/1?silent=true) | [AI skills](https://meta.discourse.org/t/giving-discourse-ai-agent-skills/408666/9?silent=true)
- @Awesomerobot confirmed he’s working on a fix for the dangerous delete-user button in the moderation queue, linking to the PR with a confirmation step. [read more](https://meta.discourse.org/t/the-delete-user-button-in-moderation-queue-is-evil-and-needs-a-secondary-prompt/410025/3?silent=true)
- @Moin was everywhere: he helped in the **AI bot** thread (explaining deployment cycles and quoting GitHub), provided a workaround for **PostgreSQL 18** , clarified the **Solved** button behavior, and offered advice on **Sending messages to all users** (including a feature idea for a mass-email queue). He also reported the **Changelog links** inconsistency and investigated **Granular group-based permissions** issues. [AI bot](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914/13?silent=true) | [PG18](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/63?silent=true) | [Solved improvements](https://meta.discourse.org/t/solved-improvements-allowing-members-to-indicate-theyre-experiencing-a-reported-issue/402498/60?silent=true) | [Mass email](https://meta.discourse.org/t/sending-messages-to-all-users-on-a-discourse-site/229341/8?silent=true) | [Changelog](https://meta.discourse.org/t/changelog-links-show-changes-not-yet-available-in-my-forum/410023/1?silent=true) | [Permissions](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/38?silent=true)
- @Martin responded to @Moin's queries about theme setting migrations and discussed edge cases in the **Granular group-based permissions** thread, adding `anonymous_users` to disallowed groups. He also handled a question about the plugin’s behavior in **Category permissions**. [Permissions](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/35?silent=true) | [Category permissions](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/12?silent=true)
- @Gabriel was instrumental in resolving the **AI bot** issue, manually removing the problematic channel and triggering a deployment, after asking @Rinion for screen recordings to isolate the bug. [read more](https://meta.discourse.org/t/ai-bot-keeps-auto-adding-me-to-a-private-chat-channel-even-though-disabled/409914/12?silent=true)
- @Chapoi fixed the Safari PWA zooming bug (referencing PR #42303) and posted an announcement about moving AI title suggestions to the composer helper. [Safari PWA](https://meta.discourse.org/t/safari-pwa-zooming-is-buggy/407806/7?silent=true) | [AI title suggestions](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/1?silent=true)
- @Zogstrip acknowledged a bug report about custom fields being cleared, linking to the PR that fixes it. [read more](https://meta.discourse.org/t/potential-bug-where-data-in-custom-fields-is-cleared-if-certain-fields-change/410050/3?silent=true)
- @J.Jaffeux pointed @Don to workflows as an alternative to a custom theme component for AI post analysis in chat. [read more](https://meta.discourse.org/t/ai-post-analyzer-for-chat/364355/20?silent=true)
- @Tobiaseigen reported an ActivityPub federation issue with images, asking for help diagnosing the cause. [read more](https://meta.discourse.org/t/activitypub-plugin/266794/489?silent=true)
- @Angus fixed multiple Custom Wizard issues and merged PRs, while also responding to community concerns about maintenance. He suggested users contribute PRs when they spot issues. [read more](https://meta.discourse.org/t/custom-wizard-plugin/73345/985?silent=true)
- @Merefield modernized the Quick Quote theme component and shared the PR, noting its reduced need due to core features. [read more](https://meta.discourse.org/t/quick-quote-theme-component/143621/66?silent=true)
- @HAWK and @Rosiesherry engaged in deep conversations about public/private content control, scalable engagement, and the new admin dashboard. They also gave updates on DSA reporting. [Public/private](https://meta.discourse.org/t/public-vs-private-discussion/409484/6?silent=true) | [Scalable engagement](https://meta.discourse.org/t/scalable-engagement-models/409187/8?silent=true) | [Admin dashboard](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830/15?silent=true) | [DSA reporting](https://meta.discourse.org/t/dsa-content-moderation-reporting-statements-of-reasons-requirements/409681/9?silent=true)
- @Rishabh (likely a team member) confirmed that a copy-link action for invitation links is being worked on. [read more](https://meta.discourse.org/t/invitation-links-nearly-impossible-to-find/410006/6?silent=true)
* * *
That’s a wrap for today’s activity on [meta.discourse.org](http://meta.discourse.org). With everything from AI subagents to bulldozer-proof moderation safeguards, it seems the Discourse team and community are anything but idle. Here’s hoping tomorrow’s biggest challenge is choosing which shiny new feature to try first! 🚀
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 15, 2026, 1:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/920 "2026-08-15T13:02:48Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
> An active 24 hours with 78 posts across 41 topics, including 14 brand-new discussions. From big AI announcements to a sticker v2.0 facelift, Meta never sleeps.
* * *
## Key Stats
| Metric | Count |
| --- | --- |
| Total new posts | **78** |
| Total active topics | **41** (14 new) |
| Total likes received | **108** |
**Top contributing users (by likes received):**
| User | Likes | Posts |
| --- | --- | --- |
| @Sam | 18 | 1 |
| @Moin | 15 | 7 |
| @Awesomerobot | 10 | 2 |
| @NateDhaliwal | 7 | 3 |
| @Nickdb | 6 | 2 |
| @Rishabh | 5 | 1 |
| @Satonotdead | 4 | 5 |
| @Zogstrip | 4 | 3 |
| @Angus | 4 | 2 |
| @Damian_Boon | 4 | 2 |
* * *
## Interesting Topics
### #Announcements
- @Sam [announced](https://meta.discourse.org/t/-/410055/1?silent=true) the landing of **subagent support in Discourse AI** , a feature that allows users to delegate work to specialized AI agents, mix and match language models, protect against context bloat, and increase concurrency. The announcement drew a remarkable 18 likes — easily the most-liked post of the day. [read more](https://meta.discourse.org/t/-/410055?silent=true)
- @Chapoi [shared](https://meta.discourse.org/t/-/410074/1?silent=true) that **AI title suggestions have been moved into the composer helper menu** , joining category and tag suggestions in the new inline AI composer flow. He invited feedback from communities that relied on the more prominent placement, stating this is not the end state. [read more](https://meta.discourse.org/t/-/410074?silent=true)
### #Community Building
- @OS_Corsair opened a [wide-ranging discussion](https://meta.discourse.org/t/-/410059/1?silent=true) about whether Discourse — or more specifically this community — can “house and handle pluralistic diversity.” @NateDhaliwal pointed to moderation tools and topic timers, @Ondrej highlighted AI translations as a means of community inclusion, and @Nickdb noted that Discourse is a framework you configure to suit your goals, adding that the question may be getting “the cart before the horse.” [read more](https://meta.discourse.org/t/-/410059?silent=true)
### #ux
- In the [Invitation Links Nearly Impossible to Find](https://meta.discourse.org/t/-/410006/6?silent=true) thread, @Rishabh acknowledged the missing copy-link action on the invites list and confirmed the team is working on it; @Jordan.Vidrine later added that he’d be working on it “today” and that the improvement should arrive “fairly soon.” [read more](https://meta.discourse.org/t/-/410006?silent=true)
- @Moin demonstrated the [new icon grid picker](https://meta.discourse.org/t/-/294219/11?silent=true) for sidebar links, noting that the compact layout — powered by changes in [discourse#42554](https://github.com/discourse/discourse/pull/42554) — makes browsing available icons faster and less language-dependent. [read more](https://meta.discourse.org/t/-/294219?silent=true)
- In [What should the homepage be for doc categories?](https://meta.discourse.org/t/-/398616/6?silent=true), @Jordan.Vidrine agreed it makes sense for doc categories to land on the index topic, and floated building a dedicated UI page from the index in the future. He also praised @Mostapha's suggestion of automatic prev/next navigation for docs. Meanwhile, @Sren-1 [shared a JavaScript workaround](https://meta.discourse.org/t/-/409470/4?silent=true) for redirecting doc category listings to an index topic until a built-in option exists. [read more](https://meta.discourse.org/t/-/398616?silent=true)
### #Feature
- @Awesomerobot [confirmed](https://meta.discourse.org/t/-/410025/4?silent=true) that a secondary confirmation prompt for deleting users from the moderation queue has been merged and will ship with upcoming Discourse updates — closing a long-running complaint that the delete button is “evil” and too easy to click by accident. [read more](https://meta.discourse.org/t/-/410025?silent=true)
- @Polybos [detailed](https://meta.discourse.org/t/-/410069/1?silent=true) a conflict with `secure_uploads` on S3-compatible backends that lack per-object ACL support: public avatars and assets break when the bucket is private, while secure post uploads work fine. They proposed either presigned URLs for public assets or support for separate buckets/prefixes as a cleaner boundary. [read more](https://meta.discourse.org/t/-/410069?silent=true)
- @Heliosurge [requested](https://meta.discourse.org/t/-/410065/1?silent=true) a start-date option for the RSS Polling plugin to control how much historical content gets pulled from long-running feeds like YouTube channels, arguing for parity with standard RSS readers. @Moin asked for the use case, and @Heliosurge clarified it’s about controlling ingestion volume. [read more](https://meta.discourse.org/t/-/410065?silent=true)
### #Plugin
- In a [very active thread](https://meta.discourse.org/t/-/73345/985?silent=true) for the Custom Wizard plugin, @Angus released another set of fixes addressing issues reported by @Eviepayne and @Lebron, and — perhaps more importantly — pushed back gently on the idea that only a core maintainer should fix things, inviting users to submit PRs with a promise of quick reviews. Users confirmed the fixes work, though @Eviepayne noted a theme-selection regression and broken “Users directed to wizard after signup” flow. [read more](https://meta.discourse.org/t/-/73345?silent=true)
- @Don released [Discourse Stickers v2.0](https://meta.discourse.org/t/-/280873/12?silent=true), a significant modernization of the theme component: sticker configuration moves to Discourse’s native `objects` setting type, adds group filtering, category-specific stickers, per-channel chat controls, and automatic migration of the old JSON setting. Published stickers are also no longer lightbox-clickable, treating them more like genuine sticker content. [read more](https://meta.discourse.org/t/-/280873?silent=true)
### #Theme component
- @Manuel [merged a community PR](https://meta.discourse.org/t/-/201280/25?silent=true) migrating the [Category List with Banners](https://meta.discourse.org/t/-/201280?silent=true) component to `.gjs`, fixing the console errors that had plagued it. The component remains listed as unmaintained pending further style polish, but it should render cleanly again. [read more](https://meta.discourse.org/t/-/201280?silent=true)
### #Support
- In [Cannot view post preview in mobile composer?](https://meta.discourse.org/t/-/408352/24?silent=true), @Moin reported that the rich text editor still fails on certain BBCode (e.g., `[calendar]`), and noticed that copying code blocks from Meta documentation into the Markdown editor results in unwanted backslash escaping that must be manually cleaned up. [read more](https://meta.discourse.org/t/-/408352?silent=true)
- @Nacho_Caballero [shared a detailed investigation](https://meta.discourse.org/t/-/410127/1?silent=true) into a **~40-second downtime window** when running `sv hup unicorn`, attributing it to the pitchfork reload path which sends `SIGTERM` to the old master without a warm-up curl (and without a graceful `QUIT`). The proposed patch mirrors the unicorn path’s behavior — wait for the new master to actually serve before retiring the old one. [read more](https://meta.discourse.org/t/-/410127?silent=true)
### #enterprise
- In [Ask me anything about the new admin dashboard](https://meta.discourse.org/t/-/409830/14?silent=true), @One1 and @HAWK explored the role-based access gap between community managers and admins. @One1's memorable analogy — “I trust you with my life, but not my wallet or my wife” — framed why community managers are kept at moderator trust levels, and @Viddekla asked (in German) about faster stats refresh and exposing selected stats to the community. [read more](https://meta.discourse.org/t/-/409830?silent=true)
* * *
## Activity by the @Team Group
- **@Sam** kicked off the day with the [Discourse AI subagents announcement](https://meta.discourse.org/t/-/410055/1?silent=true), earning 18 likes — the day’s top post.
- **@Moin** was the most prolific team member, touching 7 topics: announcing support for the [icon type theme setting in objects settings](https://meta.discourse.org/t/-/410092/1?silent=true), investigating [mobile composer preview gaps](https://meta.discourse.org/t/-/408352/24?silent=true), testing [calendar parameters](https://meta.discourse.org/t/-/283773/21?silent=true) that appear broken, troubleshooting [poll voting failures on Safari](https://meta.discourse.org/t/-/410085/5?silent=true), showcasing the [icon grid picker](https://meta.discourse.org/t/-/294219/11?silent=true) in sidebar settings, asking about [RSS polling start dates](https://meta.discourse.org/t/-/410065/2?silent=true), and reproducing the [Android tablet chat fullscreen bug](https://meta.discourse.org/t/-/410038/2?silent=true) in Chrome.
- **@Awesomerobot** merged the [confirmation step for user deletion](https://meta.discourse.org/t/-/410025/4?silent=true) in the moderation queue and followed up on the [long-running UX thread](https://meta.discourse.org/t/-/390533/8?silent=true) about the same issue.
- **@NateDhaliwal** helped explain moderation features in the [pluralistic discussions topic](https://meta.discourse.org/t/-/410059/2?silent=true), indicated readiness to publish the [TL3 progress plugin](https://meta.discourse.org/t/-/408543/30?silent=true) as a customization topic, and attempted to reproduce the [mobile keyboard jitter](https://meta.discourse.org/t/-/409628/3?silent=true) without success on Gboard or Samsung keyboards.
- **@Rishabh** acknowledged the [invitation link discoverability problem](https://meta.discourse.org/t/-/410006/6?silent=true) and promised an update soon.
- **@Zogstrip** shipped a fix for [Copy Workflow step names](https://meta.discourse.org/t/-/409410/3?silent=true), acknowledged and PR’d a fix for the [calendar custom fields clearing bug](https://meta.discourse.org/t/-/410050/3?silent=true), and asked for browser/OS details in the [poll voting thread](https://meta.discourse.org/t/-/410085/4?silent=true) to narrow down the cause.
- **@Angus** published another batch of [Custom Wizard plugin fixes](https://meta.discourse.org/t/-/73345/985?silent=true) and encouraged community contributions with an open review policy in [his follow-up](https://meta.discourse.org/t/-/73345/987?silent=true).
- **@Jordan.Vidrine** said invite-list improvements are coming [fairly soon](https://meta.discourse.org/t/-/410006/7?silent=true) and shared his vision for the [doc category homepage](https://meta.discourse.org/t/-/398616/6?silent=true), including interest in prev/next navigation for docs.
- **@Tannerabread** requested console output to debug the [missing admin sidebar](https://meta.discourse.org/t/-/409913/17?silent=true) issue and reported being [unable to reproduce](https://meta.discourse.org/t/-/409628/2?silent=true) the mobile keyboard jitter on a Pixel 10 Pro emulator.
- **@Chapoi** announced the relocation of [AI title suggestions to the composer helper](https://meta.discourse.org/t/-/410074/1?silent=true), and solicited feedback on the change.
* * *
> From AI subagents politely learning to delegate to Discourse Stickers getting their v2.0 glow-up — and even the “evil” delete button earning a second thought — yesterday was a masterclass in turning _oops_ into _oh, nice!_
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 16, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/921 "2026-08-16T13:01:34Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
Here is a summary of the key activity and discussion that took place on Discourse Meta over the last 24 hours.
## Key Stats
- **37 new posts** were published across **16 topics** over the last day.
- These posts received a total of **18 likes** from the community.
- **Top contributors** (by likes received):
- @Asa — 4 likes
- @Ethsim2 — 3 likes (3 posts)
- @Don — 3 likes
- @Sk-Or-V1-Contents — 2 likes (6 posts)
- @Per1234 — 2 likes
- @Pfaffman — 2 likes
- @Nickdb — 1 like
- @Twofoursixeight — 1 like
## Interesting Topics
### Theme Component: Quick Profile Links Menu
@Asa [posted about the Quick Profile Links Menu — a theme component](https://meta.discourse.org/t/quick-profile-links-menu/338591/39?silent=true) — noting that the border appears to be missing when used with the “Foundation” theme, with a screenshot illustrating the issue. @Don, the component author, [responded confirming the fix and announcing an updated version of the component](https://meta.discourse.org/t/quick-profile-links-menu/338591/40?silent=true).
### Self-Hosting with Caddy in Front of Nginx
A new [discussion was opened by @Ethsim2 describing their setup](https://meta.discourse.org/t/caddy-in-front-of-app-s-nginx-via-docker-compose/410123/1?silent=true) of running Caddy in front of Discourse’s own Nginx via Docker Compose, primarily to provide HTTP/3 at the edge without replacing Nginx entirely. A key part of this setup involved a persistent `app.yml` hook to make Nginx respect the `X-Forwarded-For` header from Caddy, so client IPs are recorded correctly. @Pfaffman [pointed to a related pull request](https://meta.discourse.org/t/caddy-in-front-of-app-s-nginx-via-docker-compose/410123/2?silent=true) on the Discourse Docker repo for comparison. @Ethsim2 [expanded on the configuration approach](https://meta.discourse.org/t/caddy-in-front-of-app-s-nginx-via-docker-compose/410123/3?silent=true), including details about rotating Caddy access logs at 25 MB × 3 and explicitly disabling QUIC 0-RTT early data. Later, [@Ethsim2 issued a correction](https://meta.discourse.org/t/caddy-in-front-of-app-s-nginx-via-docker-compose/410123/4?silent=true), clarifying that disabling 0-RTT was not actually necessary — the Nginx-side header hook was what resolved the client IP issue, so they restored the default Caddy behaviour. @Satonotdead [suggested that HTTP/3 can also be achieved with vanilla Nginx](https://meta.discourse.org/t/caddy-in-front-of-app-s-nginx-via-docker-compose/410123/5?silent=true) by pointing to the official [quic.nginx.org](http://quic.nginx.org) site.
### Composer Redesign Testing Continues
The ongoing testing of the new composer brought more feedback. @Sterretje [noted a vertical space issue](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/43?silent=true) where the new composer takes up too much screen real estate when composing a new topic in Firefox on Windows 11. @Nickdb [reported that the mermaid plugin doesn’t render in the rich text editor](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/44?silent=true), though a full page reload restored the older non-rich text editor which works; they attributed the edge case to a “beta-safarism” on macOS. @Sk-Or-V1-Contents [confirmed a couple of fixes](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/45?silent=true) — the minus button now works with one tap, but a URL bar jump remains an issue with the Sogou keyboard on Xiaomi, though not with Fcitx.
### Workflow Modal Bug in Multiple Tabs
@Per1234 [raised a detailed bug report on the new Workflows plugin](https://meta.discourse.org/t/workflow-modal-must-be-closed-in-every-discourse-tab/410129/1?silent=true). The “Modal” step type appears persistently in every open browser tab when multiple tabs are open, and acting on those redundant copies produces a confusing “URL or resource could not be found” error. @Slate [confirmed the bug](https://meta.discourse.org/t/workflow-modal-must-be-closed-in-every-discourse-tab/410129/2?silent=true), agreeing that the misleading error message makes it feel like a failed action even though the step was already completed.
### Feature Request: Removing Notifications from Feed
@Twofoursixeight [submitted a feature request](https://meta.discourse.org/t/feature-request-removing-notifications/410141/1?silent=true) proposing the ability to permanently remove old notifications — either a “clear all” button or an “X” to delete individual entries — so they no longer appear in the notification feed.
### Deleting Ghost Bot with Admin Privileges
A #Support thread in Chinese about [how to delete a ghost bot user with admin privileges](https://meta.discourse.org/t/410144/1?silent=true) drew several replies. @Kddkd [pointed out that if the server itself is compromised, the bot is the least of one’s worries](https://meta.discourse.org/t/410144/2?silent=true) and [advised securing SSH credentials](https://meta.discourse.org/t/410144/3?silent=true). @Sk-Or-V1-Contents [asked when the bot was first noticed](https://meta.discourse.org/t/410144/4?silent=true). @NateDhaliwal [questioned whether it’s the Discobot or AI plugin bot](https://meta.discourse.org/t/410144/5?silent=true). The original poster @AkarinLiu [clarified it was the Discourse bot renamed](https://meta.discourse.org/t/410144/6?silent=true). @NateDhaliwal [suggested checking the 2 setting](https://meta.discourse.org/t/410144/7?silent=true). @AkarinLiu [noted the setting is on and shared an AI-generated guide for removing admin privileges via command line](https://meta.discourse.org/t/410144/8?silent=true). @Sk-Or-V1-Contents [identified the user in question is actually 3](https://meta.discourse.org/t/410144/9?silent=true), not discobot. @Satonotdead [warned about the risks of using the Rails console](https://meta.discourse.org/t/410144/10?silent=true), linking to a guide on [deleting users in Rails console](https://meta.discourse.org/t/deleting-users-in-rails-console/141540/?silent=true) and showing how to revoke admin privileges via `u.revoke_admin!` before deletion.
### CSS Bug: Invisible Code Inside ``
@Sk-Or-V1-Contents [commented on a reported bug](https://meta.discourse.org/t/code-is-invisible-solely-when-directly-inside-small/410078/2?silent=true) where code is invisible when directly inside a `` tag. They suspect it’s a theme-specific issue rather than a core bug, and suggested determining whether it’s a Discourse-maintained or custom theme before reporting it to the theme feedback area.
### S3-Compatible Object Storage: Hetzner Suggestion
@Thomas_Rother [contributed to the self-hosting guide on S3-compatible object storage](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916/510?silent=true) by recommending the EU-DSGVO compliant Hetzner object storage, which uses ISO/IEC 27001:2022-certified datacenters in Germany and Finland. They included an example configuration table and noted that the CDN warning will appear since Hetzner doesn’t offer a global CDN yet.
### AWS SNS Topic ARN Allowlist
In the support discussion about [configuring the AWS SNS topic ARN allowlist](https://meta.discourse.org/t/how-do-i-properly-configure-the-aws-sns-topic-arn-allowlist/406734/6?silent=true), @Jonathan5 shared a link to another topic that helped. @Deenius [confirmed the solution works](https://meta.discourse.org/t/how-do-i-properly-configure-the-aws-sns-topic-arn-allowlist/406734/7?silent=true), noting the only pitfall was an incorrectly entered URL format.
### Keyboard Jitter in “Languages I Understand” Field on Mobile
Testing continued on the [jittery keyboard issue in the “languages I understand” input box on mobile](https://meta.discourse.org/t/jittery-keyboard-in-languages-i-understand-input-box-on-mobile/409628/3?silent=true). @NateDhaliwal couldn’t reproduce the issue with Gboard or Samsung Keyboard, suggesting it might be device-keyboard dependent. @Sk-Or-V1-Contents [confirmed it’s still reproducible with the Sogou keyboard customized for Xiaomi](https://meta.discourse.org/t/jittery-keyboard-in-languages-i-understand-input-box-on-mobile/409628/4?silent=true), and [added that Fcitx works fine](https://meta.discourse.org/t/jittery-keyboard-in-languages-i-understand-input-box-on-mobile/409628/5?silent=true), so unless someone else needs Sogou support, they won’t prioritise it.
### WordPress Embed: Missing SEO Tags
@Slate [shared a practical shell command in the WordPress thread](https://meta.discourse.org/t/old-topics-published-via-wordpress-embed-are-missing-x-robots-noindex-and-canonical-tags/403109/11?silent=true) for detecting which existing topics published via WordPress embedded links lost their `x-robots: noindex` header, using curl against the sitemap. They emphasised that the header and canonical are independent signals that fail independently, and offered commands to check both.
### phpBB Migration Speed
@Mattash [asked for updates on the tooling that could make phpBB-to-Discourse migrations faster](https://meta.discourse.org/t/phpbb-to-discourse-migration-speed-optimization/403319/19?silent=true).
### Composer Model Override in Development
@Jahan_Gagan [opened a development question](https://meta.discourse.org/t/recommended-replacement-for-modifyclass-model-composer-when-overriding-save/410125/1?silent=true) about migrating away from the deprecated `api.modifyClass("model:composer", ...)` pattern. They want to override `Composer#save` conditionally while still calling the original `super.save(opts)`, and are wondering whether the new `addModelMethod` / `addModelCallback` APIs support this use case, or whether another extension point should be used instead.
### Reply Button Not Visible on iOS PWA
In the bug report about the [reply button not being visible when composing on iOS PWA](https://meta.discourse.org/t/reply-button-not-visible-when-composing-on-ios-pwa/403662/7?silent=true), @Blalor noted they’d created a separate topic on Safari PWA zooming, possibly duplicating this one. @Nickdb [reported that the issue recently reappeared on their hosted system and a fix was pushed](https://meta.discourse.org/t/reply-button-not-visible-when-composing-on-ios-pwa/403662/8?silent=true), resolving it.
### Safari PWA Zooming Bug Persists
@Blalor [updated a separate support thread on the Safari PWA zooming bug](https://meta.discourse.org/t/safari-pwa-zooming-is-buggy/407806/8?silent=true), stating the problem persists even after updating to the latest Discourse commit — they even uninstalled and reinstalled the PWA to purge cache, with no luck, and shared a recording of the issue in the original post.
### Unicorn Reload Dropping Traffic
@Nacho_Caballero [started a support thread about ~40 seconds of downtime](https://meta.discourse.org/t/sv-hup-unicorn-dropping-traffic/410127/1?silent=true) when running `sv hup unicorn` on their standalone container. They shared a detailed analysis produced with the help of Claude, which claims the issue is in the pitchfork code path of `config/unicorn_launcher`: it sends SIGTERM (immediate) rather than SIGQUIT (graceful) to the outgoing master, and retires it as soon as workers are spawned without waiting for the new master to actually serve requests. The report includes nginx error logs showing 499/502 responses during the window and a proposed diff to mirror the existing unicorn reload logic.
## Activity by the @Team Group
During the last 24 hours, there was **no activity from members of the @Team group** in any of the forums. No posts, replies, or topic creations were recorded — the official @Team members were apparently focused elsewhere, though several of the bug reports and feature requests above will likely catch their attention soon.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 17, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/922 "2026-08-17T13:01:34Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
* * *
## Key Stats
The last 24 hours saw **109 new posts** across **41 new topics** , generating **80 likes** from the community.
**Top users by engagement:**
| User | Posts | Likes |
| --- | --- | --- |
| @NateDhaliwal | 12 | 14 |
| @Moin | 8 | 8 |
| @Martin | 6 | 7 |
| @Twofoursixeight | 4 | 7 |
| @Merefield | 3 | 7 |
| @Chapoi | 7 | 6 |
| @Satonotdead | 5 | 2 |
| @Serkhelesheyi | 3 | 2 |
| @Ethsim2 | 2 | 2 |
| @HAWK | 2 | 2 |
* * *
## Interesting Topics
### #Announcements
- **Granular group-based permissions for anonymous and logged in users** is advancing. @Martin clarified that `anonymous_users` and `logged_in_users` groups are usable at any time and posted a plan of remaining work to eliminate the `everyone` group from site settings, acknowledging gaps when the upcoming change is disabled — including groups not being visible in the interface and theme setting issues raised by @Moin ([read more](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/41?silent=true)).
- In the **redesigned admin dashboard** discussion, @Skodde pointed out that Version and Backups info is only visible with the Docker Manager plugin active, calling the current dashboard unusable for many sysadmins. @Chapoi confirmed that adding a selectable main block with the classic info is in the works ([read more](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528/53?silent=true)).
- The **PostgreSQL 18 update for self-hosters** topic saw @Chrisr explain that collation mismatch warnings during the dump-and-restore process are expected — they stem from the base image upgrading Debian Bookworm to Trixie and changing the glibc version — and that moving to `C.UTF8` with the `builtin` provider will make future upgrades stable. @Saiano shared an 80 GB database upgrade experience, and @Jonathan5 confirmed a successful upgrade ([read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/71?silent=true)).
- **AI title suggestions move to composer helper** generated criticism from @Jaroslav.Kovar, who noted that AI suggestions for categories and tags are now much less discoverable since users must manually click the combobox and select “AI Choose for me.” @Chapoi acknowledged the feedback and made a note of it ([read more](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/4?silent=true)).
### #Plugin
- @NateDhaliwal published **[See TL3 Progress](https://meta.discourse.org/t/see-tl3-progress/410166?silent=true)**, a plugin that shows TL2 users a progress bar toward TL3 with optional detailed breakdowns of each requirement, next-closest stat, and warnings for TL3 users at risk of losing their level. @Lilly helped catch a missing summary presentation bug, and @Kairo162 asked about the plugin’s beta status ([read more](https://meta.discourse.org/t/see-tl3-progress/410166/4?silent=true)).
- **Asyntai AI Chatbot** is a new theme component that adds an AI chat assistant to the corner of a forum, answering visitor questions from the site’s own content in 80+ languages. @Moin questioned why the author tested against the 1-year-old Discourse 3.5 version ([read more](https://meta.discourse.org/t/asyntai-ai-chatbot/410164/2?silent=true)).
- In **Discourse Calendar and Events** , @Hellekin reported that the [Peertube Live embed](https://meta.discourse.org/t/discourse-calendar-and-events/97376/612?silent=true) no longer displays the chat interface as it did last Summer, and the “Livestream button” is missing from the event interface.
- @AJ_Quick introduced **Automatic Sitemap Linking** , which imports an external sitemap, extracts page titles, and auto-links matching phrases in forum posts — similar to Watched Words but using sitemap-powered matching ([read more](https://meta.discourse.org/t/automatic-sitemap-linking/410169/1?silent=true)).
### #development
- @Martin opened a new WIP companion topic, **The road to stable, then permanent, for granular\_anonymous\_and\_logged\_in\_groups\_permissions** , tracking high and low priority issues across core, plugins, and themes for truly removing the `everyone` pseudogroup from site settings — covering Discourse Templates, Discourse AI, Assign, Activity Pub, Suggested Edits, and Resenha ([read more](https://meta.discourse.org/t/the-road-to-stable-then-permanent-for-granular-anonymous-and-logged-in-groups-permissions/410178/1?silent=true)).
### #Support
- A forum admin, @AkarinLiu, reported a **ghost bot user with admin privileges** they can’t delete. @Moin discovered that AI bot users lack the “Revoke admin” button visible for normal admins, and @Satonotdead warned against removing the wrong AI bot via Rails console and linked the guide on deleting users with debotting concerns ([read more](https://meta.discourse.org/t/topic/410144/12?silent=true)).
- In **My Discourse forum deindexed from Google** , @Cnrtechspot.Com shared that their month-old forum is seeing “Crawled - but not indexed” across pages. @Chapoi linked to Sam’s explanation that this is [expected behavior for new forums](https://meta.discourse.org/t/seo-pages-crawled-but-not-indexed/379309/4?silent=true) without much content, and that Google will likely index it in time with enough content ([read more](https://meta.discourse.org/t/my-discourse-forum-deindexed-from-google/410177/2?silent=true)).
- **Open pingable group that anyone can join or leave** : @Thatflyerguy asked if there’s a way to create an opt-in group for event pings. @Heliosurge pointed out the freely joinable/leavable group options, and @Moin noted the `max_users_notified_per_group_mention` limit and suggested watching a tag or category instead ([read more](https://meta.discourse.org/t/open-pingable-group-that-anyone-can-join-or-leave/410168/4?silent=true)).
### #bug
- **Footnote popup on mobile is partially off‑screen and does not scroll** — @Serkhelesheyi reported that long footnote popups are inaccessible on mobile because they don’t scroll or reposition. @Moin noted a fix landed just last week, and @Serkhelesheyi confirmed their instance was about three weeks out of date ([read more](https://meta.discourse.org/t/footnote-popup-on-mobile-is-partially-off-screen-and-does-not-scroll-the-long-footnotes-cannot-be-viewed/410196/3?silent=true)).
- `code` **is invisible, solely when directly inside `small`** was investigated by @Roke_Julian_Lockhart, and @Zogstrip confirmed the fix will land via [discourse PR #42649](https://github.com/discourse/discourse/pull/42649) ([read more](https://meta.discourse.org/t/code-is-invisible-solely-when-directly-inside-small/410078/5?silent=true)).
### #General
- @Overgrow raised the alarm that `browser_pageview_events` grows unbounded by default — the table ballooned to 10M+ rows (~10 GB) in a month since core commit `39e21d063c9` — because `persist_browser_pageview_events` is true while `clean_up_browser_pageview_events` is false by default. Both settings are hidden, so sites unknowingly accumulate data with no cleanup ([read more](https://meta.discourse.org/t/browser-pageview-events-grows-unbounded-by-default/410199/1?silent=true)).
- **Does Discourse work on the lynx browser or SeaMonkey?** — @Twofoursixeight explained lynx is a text-only terminal browser with no JavaScript or CSS support, and SeaMonkey (Firefox 60 era) has been flagged as unsupported since 2023, pointing to the [Dumbcourse plugin](https://meta.discourse.org/t/dumbcourse-old-browser-friendly-ui-at-dumb-d-pad-small-screens/395104?silent=true) for old-browser compatibility. @Merefield also linked a [Termcourse plugin](https://meta.discourse.org/t/termcourse-read-post-on-discourse-instances-from-the-terminal/395285?silent=true) ([read more](https://meta.discourse.org/t/does-discourse-work-on-the-lynx-browser-or-the-sea-monkey-browser/410160/3?silent=true)).
### #Sysadmins
- The long-running **Migrate a XenForo forum to Discourse** topic saw @Andrew_Bond share a heavily refactored XF 2.3 → Discourse import script supporting users, custom fields, PMs, Media Gallery, Resources, likes, and 750k posts with 20.7 GB of attachments in ~20 hours ([read more](https://meta.discourse.org/t/migrate-a-xenforo-forum-to-discourse/45232/141?silent=true)).
### #Feature
- @Twofoursixeight requested a **“clear all” / remove notification** ability in the feature request “Removing notifications,” but @Chapoi noted the existing dismiss button already clears the feed, asking for clarification on what permanent removal would add ([read more](https://meta.discourse.org/t/feature-request-removing-notifications/410141/2?silent=true)).
* * *
## Activity by the @Team Group
- @Martin was very active across the group permissions work: he posted detailed updates on the granular permissions roadmap in [post #41](https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/41?silent=true), created the new WIP tracking topic [The road to stable, then permanent](https://meta.discourse.org/t/the-road-to-stable-then-permanent-for-granular-anonymous-and-logged-in-groups-permissions/410178/1?silent=true), answered questions on [Category permissions and the new permission groups](https://meta.discourse.org/t/category-permissions-and-the-new-permission-groups/409511/14?silent=true), and clarified the routing behavior for the new unified topic list 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/51?silent=true).
- @Chapoi engaged with multiple community threads: he confirmed that version/backup info restoration for sysadmins is on the roadmap 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/54?silent=true), clarified the existing dismiss-button behavior in [Feature request: Removing notifications](https://meta.discourse.org/t/feature-request-removing-notifications/410141/2?silent=true), acknowledged feedback on the AI title suggestion UX in [AI title suggestions move to composer helper](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/5?silent=true), pointed a new forum admin to the canonical SEO guidance in [My Discourse forum deindexed from Google](https://meta.discourse.org/t/my-discourse-forum-deindexed-from-google/410177/4?silent=true), and discussed flag alignment in [National Flags (fork)](https://meta.discourse.org/t/national-flags-fork/384423/7?silent=true).
- @Zogstrip confirmed and fixed the invisible `code` rendering bug inside `small` elements, linking to the [upstream PR #42649](https://meta.discourse.org/t/code-is-invisible-solely-when-directly-inside-small/410078/5?silent=true).
- @Chrisr explained the root cause of PostgreSQL 18 collation warnings — the Debian Trixie glibc upgrade — and reassured self-hosters that dump-and-restore is safe, in [PostgreSQL 18 update for self-hosters](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/71?silent=true).
* * *
Given the day’s deep dive into group permissions, TL3 progress bars, and an unbounded pageview table, it’s safe to say the community didn’t just count rabbits — we counted _every single one of our rows_. 🐇📊
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 18, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/923 "2026-08-18T13:01:38Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
# Today on [meta.discourse.org](http://meta.discourse.org)…
Today on [meta.discourse.org](http://meta.discourse.org)…
You got a forum summary…
# Today on meta.discourse.org...
# Today on [meta.discourse.org](http://meta.discourse.org)…
The daily summary text is in this spirit…
# Today on [meta.discourse.org](http://meta.discourse.org)…
# Today on [meta.discourse.org](http://meta.discourse.org)…
* * *
# \*\*Key Stats
Today on meta.discourse.org
* * *
## Key Stats
\*\*Key Stats
* * *
## Key Stats
\*\*Key Stats \*\*Key Stats
* * *
**Key Stats**
In the last 24 hours, [meta.discourse.org](http://meta.discourse.org) saw **158 posts** across **52 topics** , with **177 likes** given.
The most active and liked users were:
- @NateDhaliwal (11 posts, 21 likes)
- @Scoresby (12 posts, 14 likes)
- @Chapoi (10 posts, 14 likes)
- @Merefield (8 posts, 14 likes)
- @Moin (8 posts, 11 likes)
- @Nickdb (3 posts, 9 likes)
* * *
**Interesting Topics**
### #Announcements
- **AI title suggestions have moved into the composer helper** , and the community is weighing in on the trade-offs. @Jaroslav.Kovar reported that users find the AI suggestions for categories and tags less discoverable after the move, while @Chapoi acknowledged the added friction but explained the consolidation was needed for future features, noting that “the old version cost” too much noise for everyone who doesn’t want AI generation. [read more](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/8?silent=true)
- The **redesigned admin dashboard** continues to receive feedback from sysadmins. @Skodde pointed out that the new dashboard lacks the classic Version and Backups information unless the Docker Manager plugin is installed, calling it “not usable for many sysadmins,” and @Chapoi confirmed that “something along these lines is in the works.” [read more](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528/53?silent=true)
- In the **unified new topic list view** discussion, @Damian_Boon was confused about how `/new` changed, but @Moin clarified that the change only combines `/new` and `/unread`, while `/latest` remains unaffected. [read more](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728/52?silent=true)
### #Community Building
- A fascinating thought experiment on **whether money can be the only moderator of a forum** generated a big discussion. @Scoresby proposed a system where posting, replying, and upvoting all cost fees, with a community reward pool paid out to valuable users. @Nickdb and @Merefield were skeptical, pointing out the financial divide and the barrier to entry, while @Ed_S mentioned Metafilter’s $5 sign-up fee as a successful model. @Awesomerobot noted that bundling payments (like “gems” or Discord Nitro) is a more practical path than micro-payments. [read more](https://meta.discourse.org/t/can-money-be-the-only-moderator-of-a-forum/410209/31?silent=true)
### #Plugin
- @NateDhaliwal released **See TL3 Progress** , a plugin that shows users their trust level 3 progress with optional detailed breakdowns, warnings, and locked status indicators. It’s a polished release with several screenshots, and @Lilly caught a minor title summary typo which was quickly fixed. [read more](https://meta.discourse.org/t/see-tl3-progress/410166/1?silent=true)
- @J.Jaffeux added new building blocks to **Discourse Workflows** , including a data-explorer node that allows any kind of query to be used in workflows, with an example JSON attached. This responds to community requests for more flexible workflow automation. [read more](https://meta.discourse.org/t/discourse-workflows/407100/17?silent=true)
- @AJ_Quick shared a new plugin for **Automatic Sitemap Linking** , which imports external sitemaps and auto-links page titles in forum posts, similar to watched words but with a catalog and safety gates for short words. [read more](https://meta.discourse.org/t/automatic-sitemap-linking/410169/1?silent=true)
### #Support
- @Soumya_Ranjan_Mishra asked for help **configuring Discourse AI with internal OpenAI-compatible APIs**. @Falco suggested selecting `openai` as the provider and configuring the URL, but the user hit an `internal server error` with a log trace in `dialect.rb`. @Moin asked for more detailed logs, and @Satonotdead noted the need to add internal IP domains to `DISCOURSE_ALLOWED_INTERNAL_HOSTS`. [read more](https://meta.discourse.org/t/configuring-discourse-ai-with-internal-openai-apis/410238/13?silent=true)
- A forum owner with a new forum asked for help after being **deindexed from Google**. @Chapoi explained this is expected behavior for new forums and linked to Sam’s detailed post, noting that Google is a “black box” and indexing should come with more content. [read more](https://meta.discourse.org/t/my-discourse-forum-deindexed-from-google/410177/2?silent=true)
- **Bootstrap mode being legacy** continues to be a sore point. @Sk-Or-V1-Contents suggested updating the old blog post and brought back the idea of an adjustable threshold for TL1 requirements, arguing that bootstrap mode was useful for forums with fewer than 30 posts. [read more](https://meta.discourse.org/t/bootstrap-mode-is-legacy/402468/19?silent=true)
### #Self-hosting
- A **Nix package build failure for Discourse** was reported by @Fuguesoft. @Ducks diagnosed the issue as a pnpm version mismatch in the Nix expression (10.34.4 vs the required 10.28.0) and suggested pinning the derivation to an older compatible pnpm. @Fuguesoft plans to test the fix themselves. [read more](https://meta.discourse.org/t/discourse-package-fails-to-build-through-nix-shell/410198/10?silent=true)
- @Dennisjbr shared a **parallel filesystem ops template** to speed up Discourse rebuilds with millions of uploads by replacing recursive `chmod`/`chown` with parallel `find`/`xargs` pipelines. @NateDhaliwal noted this is why S3 and CDNs exist, while @Dennisjbr prefers JuiceFS for local mounting with S3 benefits. [read more](https://meta.discourse.org/t/do-your-rebuilds-take-forever-with-millions-of-uploads-try-adding-this-template/410278/1?silent=true)
- @Ed_S asked whether **pitchfork is using too much memory** on their modest forum, showing one worker with 2.2M requests and 500MB RSS plus 1.2GB swap usage. @Falco called the RSS difference “normal,” but @Ed_S notes recycling pitchforks freed 1.3GB and wants comparison stats from busier forums. [read more](https://meta.discourse.org/t/is-pitchfork-using-too-much-memory/410280/1?silent=true)
### #bug
- A **footnote popup issue on mobile** was reported by @Serkhelesheyi, where the popup is partially off-screen and doesn’t scroll. @Moin pointed out there was a fix last week and @Serkhelesheyi confirmed they simply hadn’t updated their instance in three weeks. [read more](https://meta.discourse.org/t/footnote-popup-on-mobile-is-partially-off-screen-and-does-not-scroll-the-long-footnotes-cannot-be-viewed/410196/2?silent=true)
- The **reply button not visible when composing on iOS PWA** bug persists for @Appeltaartje even after a Communiteq update. @RGJ noted a second fix that hasn’t been backported to stable and asked @Chapoi about backporting, deferring to @David for the final call. [read more](https://meta.discourse.org/t/reply-button-not-visible-when-composing-on-ios-pwa/403662/11?silent=true)
### #Feature
- @Tonja requested a way to **hide 3rd-level categories on the categories homepage without losing the layout** , as introducing a third nesting level switches the entire homepage to a long single-column list. The request is for a native setting or official option rather than CSS workarounds. [read more](https://meta.discourse.org/t/option-to-hide-3rd-level-categories-on-the-categories-homepage-without-losing-the-layout/410242/1?silent=true)
### #Extras
- @Merefield migrated the **`> termcourse` terminal client to Go** , providing a single compiled executable, lower runtime overhead, and mouse control in the terminal. The migration includes a big cleanup of the interface and updated installation instructions. [read more](https://meta.discourse.org/t/termcourse-read-post-on-discourse-instances-from-the-terminal/395285/27?silent=true)
### #events
- @Tomer1 asked when the next **community retention webinar** would be, and @Danielle confirmed they’re working on a webinar with a guest speaker later this month, plus community office hours on September 9th. [read more](https://meta.discourse.org/t/webinar-community-retention-how-to-define-and-drive-return-behavior/401266/5?silent=true)
### #development
- @Martin created a central topic tracking the road to stable and permanent for **granular anonymous and logged-in groups permissions** , listing high and low priority issues across core, plugins, and themes, including fixes for group pickers, guardian methods, and disallowed groups. [read more](https://meta.discourse.org/t/the-road-to-stable-then-permanent-for-granular-anonymous-and-logged-in-groups-permissions/410178/1?silent=true)
- @Ethsim2 reported a performance issue where **`SiteSerializer#category_types` performs one DB query per SiteSetting** in configuration schemas for staff users, showing 16 individual queries in a warm `/latest` load. They suggest batching the overridden-setting state and note the same path still exists on `main`. [read more](https://meta.discourse.org/t/staff-siteserializer-category-types-performs-one-db-query-per-sitesetting-in-configuration-schemas/410304/1?silent=true)
### #Sysadmins
- @Overgrow flagged a heads-up that the `browser_pageview_events` table **grows unbounded by default** because `persist_browser_pageview_events` is true while `clean_up_browser_pageview_events` is false, leading to 10M+ rows (~10 GB) in a month. Enabling the hidden setting via Rails console fixes it. [read more](https://meta.discourse.org/t/browser-pageview-events-grows-unbounded-by-default/410199/1?silent=true)
### #General
- @OS_Corsair asked whether **Discourse works on Lynx or SeaMonkey browsers** , and @Merefield pointed out the AGPLv3 license in the repo, while @OS_Corsair mentioned a friend wanting to create a federated forum from the software. [read more](https://meta.discourse.org/t/does-discourse-work-on-the-lynx-browser-or-the-sea-monkey-browser/410160/6?silent=true)
* * *
**Activity by the @Team Group**
During the last 24 hours, @Team members have been actively participating across forums:
- @Chapoi responded to feedback on **AI title suggestions** (discussed in #Announcements), noting the consolidation was needed for future features and that “it’ll get better later,” while acknowledging the added steps for tag/category AI. [read more](https://meta.discourse.org/t/ai-title-suggestions-move-to-composer-helper/410074/8?silent=true)
- @Moin clarified the **unified new topic list view** change, explaining that `/latest` is unaffected and only `/new` combines topics and replies. [read more](https://meta.discourse.org/t/introducing-the-unified-new-view-for-the-topic-list/404728/53?silent=true)
- @Moin also advised a user on the **footnote popup** bug, pointing them to a fix from last week, and followed up on the **granular group permissions** discussion, confirming issues with group visibility and aliasing. [read more](https://meta.discourse.org/t/footnote-popup-on-mobile-is-partially-off-screen-and-does-not-scroll-the-long-footnotes-cannot-be-viewed/410196/2?silent=true)
- @Chapoi responded to feedback about the **admin dashboard** being missing classic Version/Backups info for sysadmins, stating that “something along these lines is in the works.” [read more](https://meta.discourse.org/t/better-insights-into-your-community-with-the-redesigned-admin-dashboard/404528/53?silent=true)
- @Chapoi also provided SEO guidance on a forum being **deindexed from Google** , linking to Sam’s explanatory post and suggesting patience with content. [read more](https://meta.discourse.org/t/my-discourse-forum-deindexed-from-google/410177/2?silent=true)
- @Chapoi and @Moin both contributed to the **reply button iOS PWA** bug thread, discussing backporting with @David. [read more](https://meta.discourse.org/t/reply-button-not-visible-when-composing-on-ios-pwa/403662/11?silent=true)
- @Zogstrip confirmed fixes for the **`code` invisible in `small`** bug ([PR #42649](https://github.com/discourse/discourse/pull/42649)) and the **workflow modal closed in every tab** bug ([PR #42651](https://github.com/discourse/discourse/pull/42651)). [read more](https://meta.discourse.org/t/workflow-modal-must-be-closed-in-every-discourse-tab/410129/4?silent=true)
- @J.Jaffeux shared new **Discourse Workflows** building blocks, including a data-explorer node for queries, and offered help to users needing automation. [read more](https://meta.discourse.org/t/discourse-workflows/407100/17?silent=true)
* * *
Well, with all that discussion about paying to post and pitchfork memory probes, yesterday’s meta conversation proved once again that even the wildest ideas deserve a good discourse! 🎩
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 19, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/924 "2026-08-19T13:01:47Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
It was a busy 24 hours on Meta, with **43 new topics** and **114 posts** exchanged, earning a total of **125 likes** 🎉
**Top users by likes and posts:**
| User | Posts | Likes |
| --- | --- | --- |
| @Chapoi | 9 | 12 |
| @Ed_S | 9 | 11 |
| @Moin | 8 | 10 |
| @Don | 2 | 9 |
| @Mbauman | 2 | 9 |
| @David | 5 | 8 |
| @Merefield | 4 | 8 |
| @Satonotdead | 6 | 6 |
| @Hellekin | 2 | 6 |
| @Andrew_Rowe | 2 | 5 |
## Interesting Topics
### #Announcements
- The [unified new view for the topic list](https://meta.discourse.org/t/-/404728/56?silent=true) continued to polarise the community. @Mbauman explained why the new view is confusing — it “intermingles an individual’s tracked state and global state” — and pointed to the reverted “new new” experiment from three years ago as evidence the approach was already tried and rejected.
- @Chapoi addressed feedback on the [AI title suggestions move to composer helper](https://meta.discourse.org/t/-/410074/8?silent=true), acknowledging the extra clicks for users but arguing the old star icon was “noisy” and costly to maintain, and teasing that the end goal is AI picking the best title “without any clicks at all.”
- @Lindsey introduced [Zoom webinar livestreaming for the Events plugin](https://meta.discourse.org/t/-/410355/1?silent=true), enabling members to join a Zoom webinar from the event topic, chat in real time, and even raise their hand — with post-event chat naturally flowing into forum topics.
### #Community Building
- The debate over whether [money can be the only moderator of a forum](https://meta.discourse.org/t/-/410209/34?silent=true) deepened as @Scoresby explained how a “money-moderated” forum could work with good UX, @Andrew_Rowe explored non-real-money alternatives, and @Ed_S cautioned that “there’s always someone richer than you” — while @Merefield worried a paywall would cripple engagement.
- In the thread about a [drastic drop in community activity for Support forums](https://meta.discourse.org/t/-/405401/82?silent=true), @Satonotdead shared striking data showing Reddit’s citation share in ChatGPT collapsed from 3.83% to 0.52% in a single day, leading to a wider conversation about AI’s symbiotic (and parasitic) relationship with forum content.
### #Feature
- @Digitalities presented a compelling case for [allowing multiple OIDC sources](https://meta.discourse.org/t/-/304290/3?silent=true) simultaneously, explaining that their EU research forum needs both EU Login and EGI Check-in; @Hellekin suggested using an Authentik federation proxy as a workaround in the meantime.
- The [Feedback for Ask Discourse](https://meta.discourse.org/t/-/336805/26?silent=true) thread had a humorous turn when @Ed_S pasted the AI assistant producing pages of incoherent nonsense; @Sam apologised, noting it was the result of an upgrade, and a follow-up confirmed the issue was resolved.
### #Self-hosting
- @Ed_S raised concerns about [Pitchfork using too much memory](https://meta.discourse.org/t/-/410280/3?silent=true), sharing data showing 1.3GB freed after recycling pitchfork processes; @David responded with production graphs explaining normal memory growth and revealed plans to enable [reforking](https://github.com/shopify/pitchfork) in the near future.
### #Theme component
- [Topic Preview Modal](https://meta.discourse.org/t/-/409712/19?silent=true) gained a powerful new setting: @Don's `open_all_topic_links` makes _any_ topic link across the UI open in the preview modal, while @Satonotdead asked about Horizon compatibility and @Damian_Boon requested swipe-to-close on mobile.
### #ux
- @Moin found that the [icon picker search doesn’t support capital letters](https://meta.discourse.org/t/-/410385/1?silent=true), which is especially annoying on tablets where auto-capitalisation kicks in; @Chapoi fixed it with both case-insensitive search and disabled auto-capitalisation in [PR #42714](https://github.com/discourse/discourse/pull/42714).
### #development
- @Don published a fascinating write-up on [building a skeleton layout loader for Discourse](https://meta.discourse.org/t/-/410338/1?silent=true), covering how administrators can select real UI elements to generate skeleton screens, why selector generation is harder than it looks, and the mantra that “the skeleton should not become a DOM-readiness gate.”
### #Support
- In [can we create topics and replies using AI?](https://meta.discourse.org/t/-/410343/3?silent=true), @ThisSource asked whether Discourse supports AI-generated topics with internet-fetched content; @Moin linked to a bot-populated forum experiment, and @Awesomerobot pointed to the Workflows plugin for scheduled AI posting.
- A [sudden loss of chat and poll options in Firefox](https://meta.discourse.org/t/-/410371/1?silent=true) on forum.tardis.guide turned out to be caused by Cloudflare’s WebMCP setting, which @Shauny confirmed “can’t be switched on with Discourse as it affects some browsers.”
### #bug
- The persistent [Reply button not visible when composing on iOS PWA](https://meta.discourse.org/t/-/403662/10?silent=true) issue received new attention: @Appeltaartje confirmed it’s still broken, @Chapoi said a second fix is being backported, and @Blalor reported it’s only partially resolved on v2026.7.1.
- @Sk-Or-V1-Contents uncovered a quirk where [Discobot breaks when given unexpected links](https://meta.discourse.org/t/-/410406/4?silent=true) during its tutorial; @Chapoi found the brittle regex in the code, @Martin suggested adding `Exotic_Shorthair` to the allowed links, and the [fix PR](https://github.com/discourse/discourse/pull/42715) was merged.
## Activity by the @Team Group
The @Team group made significant contributions across the board over the last 24 hours:
- @David clarified [Pitchfork memory behaviour](https://meta.discourse.org/t/-/410280/4?silent=true) with production cluster graphs and confirmed plans to enable “reforking”; proposed a new [composer-minimum-post-length transformer](https://meta.discourse.org/t/-/410125/5?silent=true) for plugins needing to override validation; and pushed for a [discourse\_docker performance improvement](https://meta.discourse.org/t/-/410278/5?silent=true) to skip unnecessary chowns.
- @Chapoi landed the [icon picker search fix](https://meta.discourse.org/t/-/410385/2?silent=true), drove the [iOS PWA composer fix](https://meta.discourse.org/t/-/403662/16?silent=true) and its [backports](https://meta.discourse.org/t/-/407806/11?silent=true), explained the reasoning behind the [AI title suggestion UX](https://meta.discourse.org/t/-/410074/8?silent=true), diagnosed and fixed the [Discobot tutorial bug](https://meta.discourse.org/t/-/410406/4?silent=true), and shared a [CSS snippet](https://meta.discourse.org/t/-/410141/4?silent=true) for hiding read notifications.
- @Sam apologised for the [Ask Discourse outage](https://meta.discourse.org/t/-/336805/27?silent=true) and flagged the remaining markup issue for @Falco.
- @J.Jaffeux supported Workflows users with a [data-explorer node example](https://meta.discourse.org/t/-/407100/17?silent=true) and pointed to the [bump topic operation](https://meta.discourse.org/t/-/407100/22?silent=true) for manual bumps.
- @Lindsey announced the [Zoom webinar livestream integration](https://meta.discourse.org/t/-/410355/1?silent=true) and answered questions about the [30-minute dashboard refresh](https://meta.discourse.org/t/-/409830/24?silent=true) on the new admin dashboard.
- @Awesomerobot removed the over-broad styles causing the [dark-mode composer input colour bug](https://meta.discourse.org/t/-/410289/2?silent=true) and recommended the [Workflows plugin](https://meta.discourse.org/t/-/410343/6?silent=true) for AI-scheduled posts.
- @Martin confirmed the quick [Discobot regex fix](https://meta.discourse.org/t/-/410406/5?silent=true) proposed by @Chapoi.
- @Rishabh shared two new [admin invite improvements](https://meta.discourse.org/t/-/407727/14?silent=true) via PRs #42557 and #42652, and clarified the username step during [email-code signup](https://meta.discourse.org/t/-/407068/23?silent=true).
- @Renato suggested the long-press workaround for [closing chat channels](https://meta.discourse.org/t/-/297444/8?silent=true) on mobile devices.
- @Jordan.Vidrine asked for OS details in order to reproduce the [Arabic text padding bug](https://meta.discourse.org/t/-/409392/10?silent=true).
- @Falco confirmed that [chat and polls work in current Firefox builds](https://meta.discourse.org/t/-/410371/2?silent=true), helping narrow the issue to a Cloudflare configuration on the affected site.
* * *
From teaching Discobot about exotic shorthairs to watching AI assistants quote Orwell while pitchfork processes soak up RAM, it was a gloriously weird 24 hours on Meta — and we wouldn’t have it any other way. 🎉
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 20, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/925 "2026-08-20T13:01:05Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
Over the last 24 hours, the community produced **93 new posts** across **37 topics** , with **147 likes** on those posts, according to [Meta Discourse latest activity](https://meta.discourse.org/latest).
| Top User | Posts | Likes |
| --- | --- | --- |
| @Awesomerobot | 5 | 17 |
| @Sam | 3 | 16 |
| @Lindsey | 3 | 13 |
| @Zogstrip | 1 | 13 |
| @Moin | 8 | 12 |
| @Ryan_Scott | 4 | 9 |
| @Sk-Or-V1-Contents | 6 | 5 |
| @Chapoi | 4 | 5 |
| @David | 1 | 5 |
| @Nickdb | 4 | 4 |
## Interesting Topics
### #Announcements
- @Lindsey announced a new experimental **likely crawlers** category in the admin dashboard. It uses behavioral signals — automation user agents, datacenter ASNs, rapid navigation, session churn, and more — to separate bot pageviews from genuine human traffic, and is opt-in via Admin → Upcoming changes. [Read more](https://meta.discourse.org/t/-/409316/1?silent=true)
- @Sam released detailed **admin AI logs** at `/admin/plugins/discourse-ai/ai-logs`, with new retention controls, streaming-response decoding, and rich filtering to help admins diagnose AI issues. [Read more](https://meta.discourse.org/t/-/410499/1?silent=true)
- @Zogstrip introduced an experimental change that prioritizes **your recently used tags** in the empty tag picker, using tags from your 10 most recent topics instead of site-wide popular tags. [Read more](https://meta.discourse.org/t/-/410419/1?silent=true)
- The [unified new view for the topic list](https://meta.discourse.org/t/-/404728/58?silent=true) continues to spark conversation. @Awesomerobot acknowledged the extra-click complaint and shared a mock-up with split counts, while @Mbauman pushed back on merging “new topics” and “new replies” into one list. [Read more](https://meta.discourse.org/t/-/404728/59?silent=true)
### #Support
- @Ryan_Scott reported a [calendar outage](https://meta.discourse.org/t/-/410469/1?silent=true) affecting all ~1,200 of his users after a Discourse update. It turned out the `discourse post event enabled` setting had been switched off during the core-bundling migration; @Awesomerobot confirmed a fix was identified and applied to prevent it from happening for other sites. [Read more](https://meta.discourse.org/t/-/410469/5?silent=true)
- @Sk-Or-V1-Contents hit [flaky search behavior](https://meta.discourse.org/t/-/410429/1?silent=true) around stop words like `it` and `we`, plus exact-match quoting quirks. @Awesomerobot explained why those words aren’t indexed and how fancy quotes can break phrase searches. [Read more](https://meta.discourse.org/t/-/410429/5?silent=true)
- In a [random discussion about LLM setup](https://meta.discourse.org/t/-/410507/21?silent=true), @Sam confirmed that Gemini 3.7 Flash works via the interactions API and that Grok should work using the completion API.
- A new self-hoster asked whether [deployment requires email](https://meta.discourse.org/t/-/410508/1?silent=true). The community clarified that SMTP is now optional thanks to Discourse ID login, and pointed to free mail providers like Mailgun and Brevo for transactional email. [Read more](https://meta.discourse.org/t/-/410508/3?silent=true)
### #bug
- @Sk-Or-V1-Contents found that [Discobot’s tutorial breaks](https://meta.discourse.org/t/-/410406/1?silent=true) when users send links outside a small hard-coded Wikipedia set. @Chapoi opened a [fix PR](https://github.com/discourse/discourse/pull/42715), and @Martin confirmed the regex addition. [Read more](https://meta.discourse.org/t/-/410406/4?silent=true)
- @Blalor reported that the [Safari PWA zooming bug](https://meta.discourse.org/t/-/407806/12?silent=true) still occurs on v2026.7.1 when tapping into the textarea. @Chapoi couldn’t reproduce it and asked whether the site is using a small font-size that could trigger iOS auto-zoom. [Read more](https://meta.discourse.org/t/-/407806/13?silent=true)
### #Community Building
- @Nickdb and others returned to the question of whether [AI is eating support-forum activity](https://meta.discourse.org/t/-/405401/86?silent=true). The thread ranged from model quality concerns to the observation that deeply technical, context-heavy forums are less vulnerable than generic Q&A communities. [Read more](https://meta.discourse.org/t/-/405401/93?silent=true)
- @WebBuilder asked how communities handle [external video content](https://meta.discourse.org/t/-/410459/1?silent=true). @Andrew_Rowe pointed to oneboxing, the [Discourse Livestream plugin](https://meta.discourse.org/t/discourse-livestream/341335?silent=true), the [Video Stream plugin](https://meta.discourse.org/t/discourse-video-stream/388754?silent=true), and the Discord-style Resenha voice/video rooms plugin. [Read more](https://meta.discourse.org/t/-/410459/2?silent=true)
### #Feature
- In [Feedback for Ask Discourse](https://meta.discourse.org/t/-/336805/28?silent=true), @Ed_S reported occasional bad markup in AI answers and requested links open in a new tab by default. @Falco noted the behavior should already respect the user’s “open external links in a new tab” preference, though @Moin observed that preference is hidden from most users. [Read more](https://meta.discourse.org/t/-/336805/31?silent=true)
### #ux
- @Markersocial highlighted [confusing bulk delete confirmations](https://meta.discourse.org/t/-/410444/1?silent=true): the “Permanently delete” message appears even when `can_permanently_delete` is false, and search results don’t visually distinguish topics from posts before choosing Delete Topics vs. Delete Posts. [Read more](https://meta.discourse.org/t/-/410444/1?silent=true)
- @Moin reported that on tablets it’s now [impossible to close a chat](https://meta.discourse.org/t/-/297444/7?silent=true) from the row menu; the only workaround is tapping the invisible close button on the timestamp. @Renato asked for confirmation on mobile behavior and offered to follow up. [Read more](https://meta.discourse.org/t/-/297444/8?silent=true)
## Activity by the @Team Group
- @Awesomerobot helped resolve the [calendar outage](https://meta.discourse.org/t/-/410469/5?silent=true) and confirmed a preventive fix, explained [search stop-word behavior](https://meta.discourse.org/t/-/410429/5?silent=true), and shared a mock-up to address [unified topic list feedback](https://meta.discourse.org/t/-/404728/59?silent=true).
- @Lindsey announced the new [likely crawler detection feature](https://meta.discourse.org/t/-/409316/1?silent=true) and answered questions about [dashboard refresh caching](https://meta.discourse.org/t/-/409830/24?silent=true).
- @Sam shipped [detailed admin AI logs](https://meta.discourse.org/t/-/410499/1?silent=true), flagged [Ask Discourse feedback](https://meta.discourse.org/t/-/336805/29?silent=true) for the team, and confirmed Gemini/Grok support in the [LLM setup discussion](https://meta.discourse.org/t/-/410507/21?silent=true).
- @Zogstrip announced [recently used tag prioritization](https://meta.discourse.org/t/-/410419/1?silent=true).
- @David updated the [composer minimum post length transformer](https://meta.discourse.org/t/-/410125/7?silent=true) to also address the editor’s “Post can’t be empty” validation.
- @Chapoi diagnosed and fixed the [Discobot tutorial bug](https://meta.discourse.org/t/-/410406/4?silent=true), added capital-letter support to the [icon picker](https://meta.discourse.org/t/-/410385/2?silent=true), and investigated the [Safari PWA zoom regression](https://meta.discourse.org/t/-/407806/13?silent=true).
- @Martin confirmed the [Discobot regex fix](https://meta.discourse.org/t/-/410406/5?silent=true).
- @Rishabh shared [admin invite improvements](https://meta.discourse.org/t/-/407727/14?silent=true) and clarified the username step in [email-code signup](https://meta.discourse.org/t/-/407068/23?silent=true).
- @Falco noted that Ask Discourse links should respect the user’s [external links in a new tab preference](https://meta.discourse.org/t/-/336805/31?silent=true).
- @Renato asked for confirmation on the tablet [chat close behavior](https://meta.discourse.org/t/-/297444/8?silent=true).
* * *
_From resurrecting calendars to teaching Discobot new links, it was a day of happy little fixes — may your tags be recent, your crawlers be flagged, and your “Post can’t be empty” errors finally be empty._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 21, 2026, 1:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/926 "2026-08-21T13:02:11Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
A 24-hour wrap-up of the busiest conversations on the official Discourse Meta forum.
## Key Stats
- **154 posts** were published across **39 active/new topics** in the last 24 hours. Those posts collected **215 likes**.
- **Top users by posts and likes received:**
| User | Posts | Likes received |
| --- | --- | --- |
| @Lindsey | 2 | 21 |
| @Satonotdead | 26 | 19 |
| @Sam | 2 | 18 |
| @Nickdb | 12 | 14 |
| @Moin | 11 | 14 |
| @Happyhappy | 5 | 13 |
| @HAWK | 8 | 12 |
| @Mbauman | 7 | 11 |
| @Chapoi | 6 | 8 |
| @NateDhaliwal | 6 | 8 |
## Interesting Topics
### #Announcements
- **Improved crawler detection is now optional for admins.** @Lindsey [announced](https://meta.discourse.org/t/improving-how-we-detect-and-flag-likely-crawlers-in-your-traffic-data/409316/1?silent=true) a new `Likely Crawlers` category in site traffic data, using behavioral heuristics such as datacenter ASNs, velocity, rapid navigation, session churn, and missing engagement to separate automation from real anonymous visitors. The feature is an experimental “upcoming change” and does not rate-limit or block requests; questions remain about whether likely-crawler pageviews will count toward plan limits. [Read more](https://meta.discourse.org/t/improving-how-we-detect-and-flag-likely-crawlers-in-your-traffic-data/409316/1?silent=true)
- **The August 2026 Current Projects update is out.** @Rishabh [shared the newsletter](https://meta.discourse.org/t/current-projects-august-2026/410518/1?silent=true), covering recently finished dashboard work, Events plugin/Zoom livestream improvements, AI image captions v2, and the work-in-progress Kanban plugin, Workflows, Discourse Helper Bot improvements, and composer redesign. @Awesomerobot later [clarified](https://meta.discourse.org/t/current-projects-august-2026/410518/5?silent=true) that Zoom livestream and Resenha/Livekit live-video paths are separate for now. [Read more](https://meta.discourse.org/t/current-projects-august-2026/410518/1?silent=true)
- **Admins get detailed AI logs.** @Sam [announced](https://meta.discourse.org/t/detailed-admin-ai-logs/410499/1?silent=true) an admin-only AI logs page at `/admin/plugins/discourse-ai/ai-logs`, with retention controls, decoding of streaming responses, and rich filtering to help diagnose issues with Discourse AI. Commenters such as @Nickdb are already using it to track automatic translation behavior. See also the [Discourse AI guide](https://meta.discourse.org/t/discourse-ai/259214?silent=true). [Read more](https://meta.discourse.org/t/detailed-admin-ai-logs/410499/1?silent=true)
### #Community Building
- **AI-written replies to farm trust levels are a growing headache.** @Divinebaboon [asked how communities police users](https://meta.discourse.org/t/how-do-you-guys-deal-with-users-that-use-ai-to-automatically-reply-to-threads-so-they-can-gain-trust-level/410556/1?silent=true) who use AI to auto-browse and auto-respond just to unlock trust-gated areas. @Merefield noted AI-driven sock puppet conversations, @Ed_S called for explicit LLM policies, @Nickdb described using AI-detection agents with ~95% accuracy, and @HAWK pushed back to focus on whether the content is valuable regardless of origin. [Read more](https://meta.discourse.org/t/how-do-you-guys-deal-with-users-that-use-ai-to-automatically-reply-to-threads-so-they-can-gain-trust-level/410556/1?silent=true)
- **The support-forum activity decline debate continued.** In a long-running thread, @Mbauman shared that the Julia programming community is losing new posters to AI, while @Nickdb argued deeply technical topics still bring humans back and @Mevo defended the value of human-guided AI-generated responses. @HAWK later raised the paradox that blocking crawlers may prevent AI models from learning fresh human content. [Read more](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/93?silent=true)
- **Members are showing off their Workflows.** @HAWK [started a showcase thread](https://meta.discourse.org/t/show-us-your-workflows/410589/1?silent=true) and revealed Meta’s own weekly update reminder workflow, which serves progressively worse CSS to late check-ins. @Zogstrip explained the LLM classifier and daily [data explorer](https://meta.discourse.org/t/32566?silent=true) logic behind it, while @Nickdb shared a simple automatic category-correcting workflow. [Read more](https://meta.discourse.org/t/show-us-your-workflows/410589/1?silent=true)
### #Translations
- **Basque speakers are rallying for a locale.** @Happyhappy [asked when Basque could become an interface option](https://meta.discourse.org/t/basque-language-interface-option/410511/1?silent=true). @Moin explained that languages need about 50% translation before being added; Basque is currently around 13%, so @Happyhappy is recruiting volunteers on Crowdin and exploring machine-assisted translation to accelerate the effort. [Read more](https://meta.discourse.org/t/basque-language-interface-option/410511/1?silent=true)
### #Support
- **Horizon’s new-topic button can float — with caveats.** @Satonotdead [wanted to move the sidebar button](https://meta.discourse.org/t/position-of-the-new-topic-button-on-horizon/410535/1?silent=true) to a fixed bottom-right position, and @Chapoi reproduced a stacking-context oddity caused by `position:sticky`, suggesting a `z-index:1` fix on `.sidebar-wrapper`. The result may overlap other elements, but the trick works, and the topic is tagged #css and #horizon-theme. [Read more](https://meta.discourse.org/t/position-of-the-new-topic-button-on-horizon/410535/1?silent=true)
- **Self-hosters don’t need email to deploy anymore.** @WuBarlynn [asked whether a mail server is required](https://meta.discourse.org/t/topic/410508/1?silent=true), and @Moin confirmed SMTP is now optional, thanks to Discourse ID login support introduced in the [easier self-hosting installer](https://meta.discourse.org/t/self-hosting-discourse-just-got-a-whole-lot-easier/393915?silent=true). @NateDhaliwal also noted free email tiers like Mailgun and Brevo for those who need transactional mail later. [Read more](https://meta.discourse.org/t/topic/410508/1?silent=true)
- **A hidden theme component caused an admin deprecation warning.** @Rbos [investigated a console notice](https://meta.discourse.org/t/admin-notice-one-of-your-themes-or-plugins-contains-code-which-needs-updating-id-discourse-html-safe-helper/410553/1?silent=true) about deprecated `htmlSafe` imports and `.hbs` files. @Moin found the source was the “Versatile Banner” theme component stored in the database; once updated, the warnings cleared. [Read more](https://meta.discourse.org/t/admin-notice-one-of-your-themes-or-plugins-contains-code-which-needs-updating-id-discourse-html-safe-helper/410553/1?silent=true)
- **Nginx can crash-loop after restart due to Brotli loading.** @OxFilla [documented a failure](https://meta.discourse.org/t/nginx-crash-loops-after-container-restart-base-image-ships-brotli-static-in-discourse-conf-but-never-loads-the-module-unknown-directive/410530/1?silent=true) where the Discourse base image’s `discourse.conf` uses `brotli_static`, but the Debian `nginx` package never loads the Brotli module because `/etc/nginx/nginx.conf` lacks `include /etc/nginx/modules-enabled/*.conf`. A workaround is shared in the thread. [Read more](https://meta.discourse.org/t/nginx-crash-loops-after-container-restart-base-image-ships-brotli-static-in-discourse-conf-but-never-loads-the-module-unknown-directive/410530/1?silent=true)
### #ux
- **Could profile pages be simplified?** @Satonotdead [proposed merging Security into Account](https://meta.discourse.org/t/about-merging-profile-sections-pages/410570/1?silent=true), and possibly Following with Notifications, to reduce the clutter on profile pages. The discussion frames this as the last “rough edge” in the modern Discourse profile experience. [Read more](https://meta.discourse.org/t/about-merging-profile-sections-pages/410570/1?silent=true)
- **Bulk topic deletion is coming, but not yet.** @Satonotdead raised confusion about why “Delete Topics” is missing from bulk actions, and @Zogstrip [confirmed the team is improving bulk mode](https://meta.discourse.org/t/bulk-actions-confusion-delete-topics/410444/3?silent=true), pointing to pull request #42776 that will add the missing action. [Read more](https://meta.discourse.org/t/bulk-actions-confusion-delete-topics/410444/3?silent=true)
### #bug
- **iOS 16.7 photo uploads remain stubborn.** @Falco [asked for a status check](https://meta.discourse.org/t/issue-with-ios-16-7-photo-upload/408404/35?silent=true) on the long-running upload bug. @Sb56637 reports that raising upload limits and `client_max_body_size` usually helps, but the iPhone-only failure mode still lacks a clear explanation. [Read more](https://meta.discourse.org/t/issue-with-ios-16-7-photo-upload/408404/35?silent=true)
### #Plugin
- **Calendar/Events regressions are annoying mixed categories.** @Aurora [reported two issues](https://meta.discourse.org/t/discourse-calendar-and-events/97376/614?silent=true): recurring events can no longer be set to the _fourth_ weekday of a month — only “last weekday” is offered — and categories with Events enabled now emphasize “New Event” over regular “New Topic,” hurting local-group categories that mix discussions and events. [Read more](https://meta.discourse.org/t/discourse-calendar-and-events/97376/614?silent=true)
## Activity by the @Team Group
The @Team group was especially visible in product announcements, feature explanations, and community troubleshooting.
- **@Sam** released [detailed admin AI logs](https://meta.discourse.org/t/detailed-admin-ai-logs/410499/1?silent=true) and helped LLM testers by confirming in [Random discussion about Discourse LLM setup](https://meta.discourse.org/t/random-discussion-about-discourse-llm-setup/410507/21?silent=true) that Gemini 3.7 Flash now works through the interactions API.
- **@Lindsey** launched [likely crawler detection](https://meta.discourse.org/t/improving-how-we-detect-and-flag-likely-crawlers-in-your-traffic-data/409316/1?silent=true), answered [pageview-limit questions](https://meta.discourse.org/t/improving-how-we-detect-and-flag-likely-crawlers-in-your-traffic-data/409316/6?silent=true), and explained the feature is experimental and still being tuned.
- **@Kris.Kotlarek** added [crawler detection details](https://meta.discourse.org/t/improving-how-we-detect-and-flag-likely-crawlers-in-your-traffic-data/409316/9?silent=true), confirming that even logged-in trust-level-0 users scanning Meta have been caught by the heuristics.
- **@Rishabh** published [Current Projects – August 2026](https://meta.discourse.org/t/current-projects-august-2026/410518/1?silent=true), recapping recent work on the [admin dashboard](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/1?silent=true), [Zoom webinar livestream](https://meta.discourse.org/t/zoom-webinar-livestream-in-the-events-plugin/410355?silent=true), [AI image captions](https://meta.discourse.org/t/making-post-images-more-accessible-with-discourse-ai/408323?silent=true), [admin invites](https://meta.discourse.org/t/improving-admin-invites/407727?silent=true), [Workflows](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990?silent=true), and the [composer redesign](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849?silent=true).
- **@Awesomerobot** [explained the relationship](https://meta.discourse.org/t/current-projects-august-2026/410518/5?silent=true) between Zoom livestream and Resenha/Livekit, noting the two live-video paths are separate for now and that Livestream supports YouTube, Twitch, Kick, TikTok, Instagram, and Facebook.
- **@Zogstrip** detailed the [weekly update workflow](https://meta.discourse.org/t/show-us-your-workflows/410589/6?silent=true) Meta uses to chase late team check-ins, including an LLM classifier and daily [data explorer](https://meta.discourse.org/t/32566?silent=true) queries, and shared a [pull request](https://meta.discourse.org/t/bulk-actions-confusion-delete-topics/410444/3?silent=true) that adds delete to bulk actions.
- **@Chapoi** helped with the [Horizon new-topic button CSS](https://meta.discourse.org/t/position-of-the-new-topic-button-on-horizon/410535/4?silent=true), and was transparent about the intentionally terrible CSS used in the [weekly update workflow](https://meta.discourse.org/t/show-us-your-workflows/410589/3?silent=true).
- **@HAWK** opened the [Workflows showcase](https://meta.discourse.org/t/show-us-your-workflows/410589/1?silent=true), contributed to the [AI and trust-level discussion](https://meta.discourse.org/t/how-do-you-guys-deal-with-users-that-use-ai-to-automatically-reply-to-threads-so-they-can-gain-trust-level/410556/9?silent=true), asked whether [blocking crawlers hurts AI data regeneration](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/115?silent=true), and commented on dashboard refresh timing in the [admin dashboard AMA](https://meta.discourse.org/t/ask-me-anything-about-the-new-admin-dashboard/409830/26?silent=true).
- **@Falco** followed up on the [iOS 16.7 upload issue](https://meta.discourse.org/t/issue-with-ios-16-7-photo-upload/408404/35?silent=true), asking reporters whether the bug was still happening.
* * *
_And remember: if your screen suddenly starts wobbling, you might want to check whether your weekly update already floated away._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 22, 2026, 1:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/927 "2026-08-22T13:01:00Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
Over the last 24 hours, the community has been busy:
- **103** new posts and **40** new topics were created
- **119** likes were given across those posts
### Top Users by Likes & Posts
| User | Likes Received | Posts |
| --- | --- | --- |
| @HAWK | 18 | 6 |
| @Falco | 13 | 4 |
| @Moin | 10 | 14 |
| @NateDhaliwal | 10 | 7 |
| @Don | 8 | 3 |
| @Satonotdead | 7 | 13 |
| @Darkpixlz | 6 | 6 |
| @Nickdb | 6 | 5 |
| @Awesomerobot | 6 | 4 |
| @Zogstrip | 6 | 2 |
## Interesting Topics
### #Community Building
- @HAWK kicked off [Show us your Workflows](https://meta.discourse.org/t/show-us-your-workflows/410589/1?silent=true) with a genuinely hilarious approach to nudging team members to post their weekly updates: progressively worse CSS the later they are. @Zogstrip explained the full [workflow engine](https://meta.discourse.org/t/discourse-workflows/407100/24?silent=true) behind it, including an LLM classifier and data tables, while @Chapoi admitted to building the “ugliest theme ever”. @NateDhaliwal is apparently happy to run it.
- The ongoing debate about [dealing with users who rely on AI to gain trust level](https://meta.discourse.org/t/how-do-you-guys-deal-with-users-that-use-ai-to-automatically-reply-to-threads-so-they-can-gain-trust-level/410556/8?silent=true) heated up. @NateDhaliwal suggested warnings and suspensions, @HAWK argued first principles—“is the content valuable?”—while @Satonotdead described building a custom karma system with human _quests_. @Mbauman cautioned that AI-generated spam can destroy community goodwill after spammers retroactively edit posts to include links.
- The long-running thread on [drastic drops in support forum activity](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/116?silent=true) saw @Satonotdead sharing dystopian thoughts on AI training and human interaction, with @HAWK countering that human ideas are an endless resource.
### #Announcements
- @Falco unveiled a complete refresh of [chat notification sound packs](https://meta.discourse.org/t/new-chat-notification-sound-packs/410644/1?silent=true), replacing the old options with five synthesized packs — from **Soft marimba** to **Ethereal glass**. Each pack distinguishes messages from mentions, and the sounds are generated in real time. @One1 was happy to discover the preview option in preferences.
- Newcomer @Dowlass asked a series of questions about the [Discourse Free plan beta](https://meta.discourse.org/t/youre-invited-to-try-the-discourse-free-plan-beta/395632/36?silent=true) in the now-official free plan. @Awesomerobot clarified that the Starter plan has been removed, listed the default automatic groups, and explained “Discourse Hosted LLM”. @Moin followed up with a primer on [trust levels](https://meta.discourse.org/t/discourse-trust-levels-a-detailed-explanation/396792?silent=true) and default groups, and @NateDhaliwal linked to the detailed explanation.
- The [crawler detection improvements](https://meta.discourse.org/t/improving-how-we-detect-and-flag-likely-crawlers-in-your-traffic-data/409316/9?silent=true) announcement gained traction as @Kris.Kotlarek confirmed that logged-in users are also scanned for automation signals, and @Nickdb shared experience mapping obscure user agents to geos.
- The [composer redesign testing thread](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/47?silent=true) has been updated with a note from @Awesomerobot that the redesign is behind an experimental setting, and @Darkpixlz confirmed an earlier text input glitch is now fixed.
### #Plugin
- [Resenha – Discord-style video and voice rooms](https://meta.discourse.org/t/resenha-add-discord-style-video-and-voice-rooms-to-your-community/389056/84?silent=true) received a major update from @Falco: reworked AI noise suppression, direct calls from user cards, room invites, sound pack integration, live subtitles via a 2.5GB local AI model, and transcription backed by topic drafts. @NateDhaliwal asked whether 1-to-1 calls could be restricted, and @Falco confirmed they are disabled by default with group-based permissions.
### #Theme Component
- @Don pushed several updates to the [Topic Preview Modal](https://meta.discourse.org/t/topic-preview-modal/409712/23?silent=true), including [nested view support](https://github.com/VaperinaDEV/discourse-topic-preview-modal/pull/3), a fix for Horizon theme compatibility, and a new [mobile/desktop switch](https://github.com/VaperinaDEV/discourse-topic-preview-modal/pull/4). @Damian_Boon was grateful.
### #bug
- @Moin reported a [Chat notification bug](https://meta.discourse.org/t/chat-notifications-not-showing-for-replies-in-chat-channels/410620/1?silent=true) where replying to a message in a chat channel without threading enabled produces no unread indicator. The issue is reproducible and already linked to an older DM notification bug.
### #ux
- In the [Bulk actions confusion topic](https://meta.discourse.org/t/bulk-actions-confusion-delete-topics/410444/3?silent=true), @Zogstrip confirmed that the “Delete Topics” action isn’t yet available in bulk mode, but linked to a [PR](https://github.com/discourse/discourse/pull/42776) that will fix that.
### #Feature
- @Satonotdead proposed [renaming chat titles on Discourse AI conversations](https://meta.discourse.org/t/renaming-chat-titles-on-discourse-ai-conversations/410641/1?silent=true), aligning with LLM chat UI conventions to let users customize conversation titles.
- In the [Feedback for Ask Discourse](https://meta.discourse.org/t/feedback-for-ask-discourse/336805/33?silent=true) thread, @Ed_S confirmed the setting to manage content language preferences is now working.
### #development
- @Ethsim2 published a [PR to eliminate N+1 queries in Staff SiteSerializer](https://meta.discourse.org/t/staff-siteserializer-category-types-performs-one-db-query-per-sitesetting-in-configuration-schemas/410304/3?silent=true), batching SiteSetting overrides and passing regression coverage. The PR is already through CI.
### #Support
- @Jagster was confused why [AI-translated posts](https://meta.discourse.org/t/how-can-i-see-ai-translated-posts/410684/1?silent=true) stopped appearing after switching interface languages. @Moin pointed to the `Content languages` preference: if you list `FI` as a language you understand, Discourse will show the original Finnish instead of the English translation.
### #Self-hosting
- A new Chinese-language topic asked about [accelerating downloads of 2 assets in mainland China](https://meta.discourse.org/t/topic/410639/1?silent=true) where installs crawl. @Darkpixlz explained that the slowness is likely from ISPs or hosting providers, @Merefield tracked down the [discourse-assets GitHub repo](https://github.com/discourse/discourse-assets), and @Awesomerobot linked to the [pre-compiled JS assets announcement](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/?silent=true).
### #Translations
- The [Basque language interface](https://meta.discourse.org/t/basque-language-interface-option/410511/7?silent=true) topic discussed using DeepL translations to bootstrap Crowdin. @Moin shared his workflow for leveraging Crowdin’s automated suggestions while cautioning about consistency in terminology.
## Activity by the @Team Group
- @HAWK shared the [Weekly Update Reminder Workflow](https://meta.discourse.org/t/show-us-your-workflows/410589/1?silent=true) and reflected on [AI-generated replies and trust levels](https://meta.discourse.org/t/how-do-you-guys-deal-with-users-that-use-ai-to-automatically-reply-to-threads-so-they-can-gain-trust-level/410556/9?silent=true). He also engaged in the [support forum activity drop](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/117?silent=true).
- @Falco announced the [new chat notification sound packs](https://meta.discourse.org/t/new-chat-notification-sound-packs/410644/1?silent=true) and posted the extensive [Resenha update](https://meta.discourse.org/t/resenha-add-discord-style-video-and-voice-rooms-to-your-community/389056/84?silent=true), covering everything from noise suppression to transcription.
- @NateDhaliwal participated in [Show us your Workflows](https://meta.discourse.org/t/show-us-your-workflows/410589/2?silent=true), offered moderation advice in the [AI trust level thread](https://meta.discourse.org/t/how-do-you-guys-deal-with-users-that-use-ai-to-automatically-reply-to-threads-so-they-can-gain-trust-level/410556/8?silent=true), welcomed a new user to the [Free plan beta](https://meta.discourse.org/t/youre-invited-to-try-the-discourse-free-plan-beta/395632/42?silent=true), reminded a member about topic etiquette on the [Horizon button placement](https://meta.discourse.org/t/position-of-the-new-topic-button-on-horizon/410535/8?silent=true) thread, and answered a question about [return paths after login](https://meta.discourse.org/t/does-discourse-has-return-path-or-return-link-i-can-leverage-to-redirect-to-previous-link-after-log-in-complete/410565/2?silent=true).
- @Zogstrip detailed the inner workings of the [workflow yellow/blue boxes](https://meta.discourse.org/t/show-us-your-workflows/410589/6?silent=true) and confirmed the upcoming fix for [deleting topics in bulk mode](https://meta.discourse.org/t/bulk-actions-confusion-delete-topics/410444/3?silent=true).
- @Awesomerobot helped clarify the [Free plan differences and automatic groups](https://meta.discourse.org/t/youre-invited-to-try-the-discourse-free-plan-beta/395632/38?silent=true), noted existing [search filter autocompletion](https://meta.discourse.org/t/add-search-filter-autocompletion/409524/2?silent=true), and gave release-channel advice for [testing the composer redesign](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/47?silent=true).
- @Chapoi owned up to creating the deliberately terrible CSS in the [Weekly Update Workflow](https://meta.discourse.org/t/show-us-your-workflows/410589/3?silent=true), and suggested the Blocks API for [moving category boxes](https://meta.discourse.org/t/how-to-move-category-boxes-to-the-top/410585/4?silent=true).
- @Kris.Kotlarek replied in the [crawler detection announcement](https://meta.discourse.org/t/improving-how-we-detect-and-flag-likely-crawlers-in-your-traffic-data/409316/9?silent=true), explaining how likely bots are identified even when using legitimate user agents.
- @Nat jumped into the [Conversational AI Search discussion](https://meta.discourse.org/t/conversational-ai-search-coming-to-discourse-ai/355939/21?silent=true), asking for clarification on what “does not work” means and requesting settings details.
* * *
Whether it’s progressively ugly CSS, AI-powered noise suppression, or quests for trust levels, yesterday on Meta reminded us that the future of forums is equal parts automation and absurdity — and we wouldn’t have it any other way. See you in the next 24 hours! 🤖
[Previous page](https://meta.discourse.org/t/daily-summary-1pm-utc/291852.md?page=34)
[Next page](https://meta.discourse.org/t/daily-summary-1pm-utc/291852.md?page=36)