# Dagelijkse samenvatting (21.00 uur UTC)
**URL:** https://meta.discourse.org/t/daily-summary-9pm-utc/291850
**Category:** Forum summaries
**Created:** [16 januari 2024 om 21:56 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850 "2024-01-16T21:56:19Z")
**Posts on this page:** 20
**Page:** 31
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [10 mei 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/858 "2026-05-10T21:02:12Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **36 new posts** across Meta in the last 24 hours, including active threads like [AI translation model errors](https://meta.discourse.org/t/-/402477/10?silent=true), [Quote Callouts UX tweaks](https://meta.discourse.org/t/-/350962/66?silent=true), and a fresh [MCP subfolder install bug report](https://meta.discourse.org/t/-/402609/1?silent=true).
- **7 new topics** were created, including:
- [Why is the word “regular” under user’s username?](https://meta.discourse.org/t/-/402579/1?silent=true)
- [游客对于 /activity/reactions 页面的查看权限修改](https://meta.discourse.org/t/-/402588/1?silent=true)
- [Badges Error launching](https://meta.discourse.org/t/-/402594/1?silent=true)
- [Error encountered while inspecting Live URL](https://meta.discourse.org/t/-/402595/1?silent=true)
- [“New topic approval” and “New reply approval” require global default values](https://meta.discourse.org/t/-/402590/1?silent=true)
- [Looking for advice on how to establish facts from logs](https://meta.discourse.org/t/-/402581/1?silent=true)
- [MCP bug when subfolder-install in](https://meta.discourse.org/t/-/402609/1?silent=true)
**Top contributors (posts / likes in the last 24h)**
| User | Posts | Likes | Recent reference |
| --- | --- | --- | --- |
| **@Lilly** | 5 | 13 | Helped explain profile titles in [“regular” title thread](https://meta.discourse.org/t/-/402579/2?silent=true) and asked about disabling Upcoming Changes alerts without CSS in [Upcoming Changes](https://meta.discourse.org/t/-/392894/23?silent=true) |
| **@Moin** | 2 | 9 | Clarified that “regular” is a selectable title in [this reply](https://meta.discourse.org/t/-/402579/3?silent=true) and pointed to UX discussion for anon reactions access in [this reply](https://meta.discourse.org/t/-/402588/2?silent=true) |
| **@Noble_Fish** | 3 | 1 | Raised moderation defaults gap in [approval settings request](https://meta.discourse.org/t/-/402590/1?silent=true) and flagged potential duplicate badge issue in [Badges thread](https://meta.discourse.org/t/-/402594/8?silent=true) |
| **@Arkshine** | 1 | 2 | Investigated edge cases + shortcut ideas for Quote Callouts in [this update](https://meta.discourse.org/t/-/350962/67?silent=true) |
| **@merefield** | 1 | 2 | Posted a deployment + sponsor-feature split update in [Locations plugin](https://meta.discourse.org/t/-/69742/1240?silent=true) |
| **@Falco** _(team)_ | 1 | 0 | Advised on structured outputs model requirements in [AI translations errors](https://meta.discourse.org/t/-/402477/11?silent=true) |
* * *
## Interesting Topics
### #Support
- @kairo162 noticed the label “regular” showing under usernames and across profiles; @Lilly connected it to trust-level naming ([post](https://meta.discourse.org/t/-/402579/2?silent=true)), and @Moin clarified it’s a selectable **Title** (often from trust-level badges) that users can enable in preferences ([solution](https://meta.discourse.org/t/-/402579/3?silent=true)). [read more](https://meta.discourse.org/t/-/402579/1?silent=true)
- In Chinese-language support, @jack222 reported that anonymous visitors can’t view `/activity/reactions` and suggested either enabling read-only access or improving the error message ([report](https://meta.discourse.org/t/-/402588/1?silent=true)); @Moin pointed to an existing UX request discussing exactly that permission/UX gap ([reply](https://meta.discourse.org/t/-/402588/2?silent=true)) and referenced the related feature request ([Allow /activity/reactions to be visible by anon](https://meta.discourse.org/t/-/366430/1?silent=true)). [read more](https://meta.discourse.org/t/-/402588/1?silent=true)
- @cshll hit a “Badges” page failure and suspected configuration issues ([report](https://meta.discourse.org/t/-/402594/1?silent=true)); @NateDhaliwal suggested checking the `enable_badges` site setting ([reply](https://meta.discourse.org/t/-/402594/2?silent=true)), while @Noble_Fish asked whether it duplicates an earlier thread ([dup-check](https://meta.discourse.org/t/-/402594/8?silent=true)) and probed whether the install looked non-standard ([follow-up](https://meta.discourse.org/t/-/402594/12?silent=true)). [read more](https://meta.discourse.org/t/-/402594/1?silent=true)
- @cshll also posted an SEO/validation screenshot about “inspecting Live URL,” but without details yet—likely a “needs repro steps” thread unless more context lands ([topic](https://meta.discourse.org/t/-/402595/1?silent=true)). [read more](https://meta.discourse.org/t/-/402595/1?silent=true)
- @Noble_Fish requested **global defaults** for “New topic approval” and “New reply approval,” noting that current global settings only cover _Everyone except selected groups_ and don’t match the workflow where a subset of users later gets moved into “must be reviewed” mode across all categories ([feature request](https://meta.discourse.org/t/-/402590/1?silent=true)). [read more](https://meta.discourse.org/t/-/402590/1?silent=true)
- In a self-hosting migration discussion, @Lilly shared a recent real-world migration (Ubuntu 24.04 → Ubuntu 24.04) and highlighted practical tips like shortening DNS TTL and planning for backup upload time ([migration notes](https://meta.discourse.org/t/-/402512/4?silent=true)). [read more](https://meta.discourse.org/t/-/402512/4?silent=true)
### #bug
- @janbolmeson reported that `@discourse/mcp` fails when connecting to Discourse installed in a **subfolder** (e.g. `/forum`) because tool calls drop the subpath—breaking validation and subsequent API calls ([bug report](https://meta.discourse.org/t/-/402609/1?silent=true)). [read more](https://meta.discourse.org/t/-/402609/1?silent=true)
- In an ongoing structured-data issue, @Richie noted Google tests still failing for three URLs due to missing `mainEntity.suggestedAnswer.text`, despite partial improvements ([status update](https://meta.discourse.org/t/-/399974/28?silent=true)). [read more](https://meta.discourse.org/t/-/399974/28?silent=true)
- AI translation troubleshooting continued: @RBoy encountered a 400 error tied to unsupported `json_schema` response formatting with a model change ([error details](https://meta.discourse.org/t/-/402477/10?silent=true)), and @Falco explained translations need a model that supports **structured outputs** (common in recent SOTA models) ([guidance](https://meta.discourse.org/t/-/402477/11?silent=true)). [read more](https://meta.discourse.org/t/-/402477/10?silent=true)
### #customization:theme component
- Quote Callouts got a UX + edge-case sweep: @nathank observed rendering issues in excerpts/Oneboxes ([note](https://meta.discourse.org/t/-/350962/65?silent=true)), @scavin flagged the default shortcut as risky on macOS because users may hit `⌘+Q` and quit the browser ([macOS concern](https://meta.discourse.org/t/-/350962/66?silent=true)), and @Arkshine weighed alternative key combos while tracking excerpt/Onebox behavior ([response](https://meta.discourse.org/t/-/350962/67?silent=true)). [read more](https://meta.discourse.org/t/-/350962/67?silent=true)
### #Announcements
- The “Upcoming Changes” notification system drew feedback on notification noise: @Lilly asked if alerts can be disabled **without** CSS (preferring a setting-level solution) and shared a temporary CSS workaround ([request + snippet](https://meta.discourse.org/t/-/392894/23?silent=true)); @NateDhaliwal pointed out a likely remaining unread-count indicator even if notifications are hidden ([reply](https://meta.discourse.org/t/-/392894/24?silent=true)). [read more](https://meta.discourse.org/t/-/392894/23?silent=true)
### #customization:plugin
- The Locations plugin thread got a substantial update: @merefield announced a fix now deployed (plus compatibility work) and described how Early Access differs from the public version—including a 3D globe users map and IP-based location lookup ([release notes](https://meta.discourse.org/t/-/69742/1240?silent=true)); @gilles thanked them for the quick turnaround ([thanks](https://meta.discourse.org/t/-/69742/1241?silent=true)). [read more](https://meta.discourse.org/t/-/69742/1240?silent=true)
### #development
- Theme authoring guidance discussions continued: @BrianC asked how to approach forking a theme while ensuring the parent stays updated over time—raising the common long-term maintenance question for serious customizations ([question](https://meta.discourse.org/t/-/401629/9?silent=true)). [read more](https://meta.discourse.org/t/-/401629/9?silent=true)
### #General
- A complex “facts from logs” question landed: @Sukenik asked how a forensic expert might establish whether historical suspensions carried over during a 2023 migration from Discourse to a custom forum ([scenario](https://meta.discourse.org/t/-/402581/1?silent=true)); @Andrew_Rowe highlighted how hosting model and log retention matter, and that three years is a long time for server logs to survive ([initial response](https://meta.discourse.org/t/-/402581/2?silent=true)). [read more](https://meta.discourse.org/t/-/402581/1?silent=true)
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Falco helped unblock AI translation troubleshooting by explaining that translation workflows require a model that supports **structured outputs** , and that most modern SOTA models now include this capability ([AI translations guidance](https://meta.discourse.org/t/-/402477/11?silent=true), context in [error report](https://meta.discourse.org/t/-/402477/10?silent=true)).
* * *
If you made it through today’s feed without accidentally hitting **⌘+Q** while trying to insert a callout, you’ve earned your _Regular_ title the hard way.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [11 mei 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/859 "2026-05-11T21:02:04Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 97** (spread across threads like the iOS PWA push investigation in [read more](https://meta.discourse.org/t/-/402645/1?silent=true) and the new bulk tag workflow announcement in [read more](https://meta.discourse.org/t/-/402693/1?silent=true))
- **New topics (last 24h): 13** (including new reports like the Edge mobile modal sizing issue in [read more](https://meta.discourse.org/t/-/402663/1?silent=true), plus new how-tos like standardizing sidebar categories in [read more](https://meta.discourse.org/t/-/402479/1?silent=true))
**Top users (posts / likes in the last 24h)**
| User | Posts | Likes | Recent activity sample |
| --- | --- | --- | --- |
| **@Lilly** | 15 | 21 | Automation troubleshooting in [read more](https://meta.discourse.org/t/-/402664/6?silent=true) and theme/login guidance in [read more](https://meta.discourse.org/t/-/402685/2?silent=true) |
| **@Moin** | 10 | 12 | Sidebar defaults discussion in [read more](https://meta.discourse.org/t/-/402479/2?silent=true) and passkeys setting tip in [read more](https://meta.discourse.org/t/-/402697/2?silent=true) |
| **@chapoi** | 9 | 7 | Confirming old modal UI and next steps in [read more](https://meta.discourse.org/t/-/402663/2?silent=true) |
| **@klappradla** | 2 | 7 | Deep-dive + PR proposal for iOS PWA push in [read more](https://meta.discourse.org/t/-/402645/1?silent=true) |
| **@RGJ** | 2 | 5 | Klipy + infinite search limit bug analysis in [read more](https://meta.discourse.org/t/-/402679/1?silent=true) |
| **@denvergeeks** | 7 | 3 | Repro attempts for repeated image uploads in the RTE in [read more](https://meta.discourse.org/t/-/402566/5?silent=true) |
| **@nat** | 1 | 3 | Translation/quote attribute investigation in [read more](https://meta.discourse.org/t/-/402420/3?silent=true) |
| **@lindsey** | 1 | 3 | Announcing the new bulk tag management modal in [read more](https://meta.discourse.org/t/-/402693/1?silent=true) |
| **@sniper756** | 1 | 3 | Reporting the Edge mobile “permanent delete” modal width issue in [read more](https://meta.discourse.org/t/-/402663/1?silent=true) |
| **@fzngagan** | 1 | 4 | Publishing a sidebar-standardization how-to in [read more](https://meta.discourse.org/t/-/402479/1?silent=true) |
* * *
## Interesting Topics
#### #Announcements
- Staff introduced a cleaner bulk-tag workflow: a single **Manage Tags** modal replaces separate add/replace/remove actions, prompting follow-up feedback about revision history clarity and missing UI affordances in [Better bulk tag management](https://meta.discourse.org/t/-/402693/1?silent=true). Related: the missing tag info button discussion in [read more](https://meta.discourse.org/t/-/402436/1?silent=true) and the older feature request this essentially fulfills in [read more](https://meta.discourse.org/t/-/276709/1?silent=true).
#### #Site Management
- A practical admin recipe for making everyone’s sidebar categories consistent (by resetting `default navigation menu categories` and applying “historically”) landed in [How to set the same sidebar categories for all the users](https://meta.discourse.org/t/-/402479/1?silent=true), followed by questions about _why_ the “two-step + wait” approach matters in [read more](https://meta.discourse.org/t/-/402479/2?silent=true).
#### #bug
- A detailed report found iOS #pwa #push-notifications subscription can **silently fail** when the service worker isn’t controlling the app yet, complete with repro steps and a proposed fix PR in [Push notification subscription in iOS PWA silently failing…](https://meta.discourse.org/t/-/402645/1?silent=true). There’s active discussion on whether adding `skipWaiting()` / `clients.claim()` to the main SW is the right long-term move in [read more](https://meta.discourse.org/t/-/402645/3?silent=true).
- A #gifs integration snag: when **“Limit infinite search results”** is enabled, Klipy categories trigger `loadMore` incorrectly and can error due to missing query params, with a plugin PR suggested in [Klipy issue when “Limit infinite search results” is set](https://meta.discourse.org/t/-/402679/1?silent=true). This also cross-connects with earlier Klipy oddities like repeated results in [read more](https://meta.discourse.org/t/-/399155/1?silent=true).
- Composer/RTE weirdness: users are chasing a tricky edge-case where dragging an **unselected** image in rich text editor mode can re-upload it repeatedly, with reproduction attempts and browser hypotheses in [When dragging an unselected image in a rich text editor, it is uploaded repeatedly](https://meta.discourse.org/t/-/402566/1?silent=true). (Edge-specific testing details continued in [read more](https://meta.discourse.org/t/-/402566/13?silent=true).)
- A localization/SEO fix is underway: a PR was filed to ensure `hreflang` stays compliant while preserving internal locale params in [Unerwarteter Sprachcode](https://meta.discourse.org/t/-/402544/1?silent=true).
- A reported #mcp issue affecting subfolder installs got a confirmed fix PR pointer in [MCP bug when subfolder-install in](https://meta.discourse.org/t/-/402609/1?silent=true).
#### #ux
- Mobile Edge users spotted a cramped “Permanent delete” confirmation dialog; staff confirmed it’s an older modal codepath that hasn’t moved to the modern d-modal yet in [手机微软edge浏览器“永久删除”弹出窗口太窄](https://meta.discourse.org/t/-/402663/1?silent=true), with confirmation in [read more](https://meta.discourse.org/t/-/402663/2?silent=true).
- The “Permanent” filter on the upcoming changes page appears confusing given optional workflow steps; that nuance is discussed in [What is the purpose of the “Permanent” filter on the upcoming changes page?](https://meta.discourse.org/t/-/402433/1?silent=true), including staff reflection in [read more](https://meta.discourse.org/t/-/402433/2?silent=true).
- Another mobile layout paper-cut: the Automation UI’s “last run” column can collide with the edit button in portrait orientation, shown in [Automation last run overlapping edit button in mobile](https://meta.discourse.org/t/-/402695/1?silent=true).
#### #Support
- A support thread dug into why a #automation job ([Data Explorer](https://meta.discourse.org/t/32566?silent=true) PM scheduling) triggers manually but won’t fire on schedule—debugging ideas ranged from time zones and “missed jobs” to logs and possibly special characters in names in [Debug Why Timed Automation is not Automatically Running](https://meta.discourse.org/t/-/402664/1?silent=true). The “monthly vs frequent interval” suspicion sharpened later in [read more](https://meta.discourse.org/t/-/402664/10?silent=true). (Background reference: Discourse Automation plugin in [read more](https://meta.discourse.org/t/-/195773/1?silent=true).)
- A quick UI/feature clarity question—_“what are cheers?”_—got routed to existing documentation and feature background in [Does anybody know what cheers are?](https://meta.discourse.org/t/-/402615/1?silent=true), with prior art including [What is a cheer?](https://meta.discourse.org/t/-/235686/1?silent=true), [What are Discourse cheers supposed to be?](https://meta.discourse.org/t/-/223867/1?silent=true), and [What’s a cheer and how do you enable it?](https://meta.discourse.org/t/-/295988/1?silent=true), plus overall context in [Discourse Gamification](https://meta.discourse.org/t/-/225916/1?silent=true).
- Admins wanting to remove “Log in with your access key” were pointed toward the hidden `enable_passkeys` setting and/or CSS approaches in [How to remove “Log in with your access key”](https://meta.discourse.org/t/-/402697/1?silent=true), with hidden settings explained in [read more](https://meta.discourse.org/t/-/308773/1?silent=true).
#### #Self-hosting
- A migration/restore failure involving Cloudflare R2 and checksum incompatibilities surfaced during a server move; troubleshooting and environment details are collected in [迁移Discourse恢复数据失败](https://meta.discourse.org/t/-/402623/1?silent=true), including an R2-specific env-var suggestion in [read more](https://meta.discourse.org/t/-/402623/7?silent=true).
- A “badges error launching” support thread turned into a broader self-hosting health-check: plugin overload, incorrect SMTP settings, and risky storage choices were called out in [Badges Error launching](https://meta.discourse.org/t/-/402594/1?silent=true), with concrete “remove unofficial plugins first” guidance in [read more](https://meta.discourse.org/t/-/402594/17?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@chapoi** confirmed the Edge mobile delete-modal is legacy UI and praised the report in [read more](https://meta.discourse.org/t/-/402663/2?silent=true), continued triage on the repeated-upload-in-RTE report in [read more](https://meta.discourse.org/t/-/402566/2?silent=true), and helped narrow self-hosting/plugin troubleshooting steps (including [safe mode](https://meta.discourse.org/t/53504?silent=true)) in [read more](https://meta.discourse.org/t/-/402594/20?silent=true). @chapoi also pulled @nat into localization/quote metadata concerns in [read more](https://meta.discourse.org/t/-/402420/2?silent=true), and confirmed a fix got merged for reaction long-press behavior in [read more](https://meta.discourse.org/t/-/402269/3?silent=true).
- **@fzngagan** posted a clear step-by-step guide for enforcing consistent sidebar categories for all users in [read more](https://meta.discourse.org/t/-/402479/1?silent=true), sparking follow-up testing/edge-case questions from others in [read more](https://meta.discourse.org/t/-/402479/2?silent=true).
- **@lindsey** announced the consolidated bulk tag management modal and invited feedback in [read more](https://meta.discourse.org/t/-/402693/1?silent=true), which immediately surfaced UX expectations around tag tooling and revisions in [read more](https://meta.discourse.org/t/-/402693/3?silent=true).
- **@nat** analyzed why translated quotes lose useful source info (with German being hit hardest) and noted more evaluation work is needed in [read more](https://meta.discourse.org/t/-/402420/3?silent=true).
- **@sam** linked a fix PR for a reported MCP subfolder-install issue in [read more](https://meta.discourse.org/t/-/402609/2?silent=true).
- **@manuel** clarified how the “skills” track and the Blocks API should remain maintainable over time (and what to expect if you fork examples) in [read more](https://meta.discourse.org/t/-/401629/10?silent=true).
- **@awesomerobot** acknowledged the “Permanent” filter confusion on Upcoming Changes and explained it as an optional workflow step that was skipped for some items in [read more](https://meta.discourse.org/t/-/402433/2?silent=true).
- **@gerhard** proposed a concrete Cloudflare R2 workaround using AWS checksum-related env vars (plus rebuild steps) for restore failures in [read more](https://meta.discourse.org/t/-/402623/7?silent=true).
- **@HAWK** responded to an SEO console “Live URL inspection” concern, suggesting the issue is likely due to new/empty sitemaps and minimal public content in [read more](https://meta.discourse.org/t/-/402595/2?silent=true).
- **@supermathie** requested environment details (object store specifics) to unblock troubleshooting for the restore/migration failure in [read more](https://meta.discourse.org/t/-/402623/4?silent=true).
* * *
Yesterday’s theme was “tiny modals, missing automations, and service workers refusing to take charge”—may today’s builds be smooth, your tags tidy, and your push subscriptions actually land where they should.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [12 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/860 "2026-05-12T21:01:58Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 53**
- **New topics (last 24h): 12**
**Top contributors (posts / likes received on their recent activity):**
| User | Posts | Likes |
| --- | --- | --- |
| @Falco | 2 | 23 |
| @Lilly | 5 | 8 |
| @chapoi | 3 | 3 |
| @zogstrip | 3 | 2 |
| @bayardo.rivas | 2 | 2 |
| @putty | 2 | 2 |
| @martin | 1 | 2 |
| @awesomerobot | 1 | 2 |
| @ferdnyc | 2 | 1 |
| @RGJ | 1 | 1 |
* * *
## Interesting Topics
### #Announcements
- @Falco shipped **new client-side image optimizations** , including **GIF → animated WebP conversion** and more knobs via #upcoming-changes in [New client side image optimizations for Discourse](https://meta.discourse.org/t/-/402705/1?silent=true) — with historical context in earlier discussions like [faster and smaller uploads](https://meta.discourse.org/t/-/196998/1?silent=true), the long-running “convert GIFs” debate ([read more](https://meta.discourse.org/t/-/16739/1?silent=true)), and prior WebP plugin ideas ([read more](https://meta.discourse.org/t/-/36470/2?silent=true)).
- In [Introducing Upcoming Changes](https://meta.discourse.org/t/-/392894/25?silent=true), @Lilly shared a way to reduce “admin noise” by dismissing notifications (and confirmed behavior changes discussed in-thread) — a practical follow-up for anyone piloting feature rollouts via #upcoming-changes.
- Admin reporting toggles sparked UI/wording feedback: @martin noted that “Everyone” can be a misleading label when a change only applies to staff in [Admin Reporting & Analysis: Incremental Changes](https://meta.discourse.org/t/-/395768/27?silent=true).
- A quick feature wish popped up again: after seeing Chat notification quick replies, @NateDhaliwal asked whether similar “quick reply” UX could come to topics in [Quick replies for Discourse Chat notifications](https://meta.discourse.org/t/-/245358/9?silent=true).
- Boosts continued to get product-shaping feedback: configuration and “boosts vs reactions” positioning was debated further in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/84?silent=true).
### #Support
- A tricky embedding case: @Pavel_Kravets tried to embed Discourse into Salesforce Experience Cloud via iframe/full-app mode; @Falco outlined the practical paths forward (shared base domain **or** adjusting `same_site_cookies`) in [Salesforce Community iframe embedding](https://meta.discourse.org/t/-/402712/4?silent=true).
- Category reorg anxiety, resolved: @bayardo.rivas asked whether renaming categories requires extra steps; replies clarified **name vs slug vs ID** , and reassured that links keep working after slug changes in [Does renaming my old Categories requires any other changes?](https://meta.discourse.org/t/-/402804/1?silent=true) (see also the slug/ID clarifications in [post 2](https://meta.discourse.org/t/-/402804/2?silent=true) and [post 6](https://meta.discourse.org/t/-/402804/6?silent=true)).
- A REST API regression report: `/admin/users/list/active.json` intermittently 500s due to `main_user_record[:silenced_till]` nil; discussion centered on upgrading and a prior fix landing later than v3.5.2 in [API calls fail due issue with main\_user\_record silenced\_till](https://meta.discourse.org/t/-/402752/1?silent=true) (with @zogstrip pointing to the likely fix [here](https://meta.discourse.org/t/-/402752/3?silent=true)).
- Redirect UX: admins asked how to redirect visitors who hit non-existent pages; the community pointed to a canonical solution thread in [How to make a redirect from non-existent pages](https://meta.discourse.org/t/-/402807/2?silent=true), referencing the “redirect all 404 pages” approach ([read more](https://meta.discourse.org/t/-/235187/15?silent=true)).
### #bug
- A reproducible editor/navigation bug (reported in Chinese): after expanding replies → “jump to post” → edit → save, users can hit “URL/resource not found”; @chapoi confirmed and @zogstrip started a fix in [出错了：找不到请求的 url 或资源](https://meta.discourse.org/t/-/402747/1?silent=true) (related duplicate report: [出错了：找不到请求的 url 或资源。](https://meta.discourse.org/t/-/402737/1?silent=true)).
- Recurring automation scheduling may be mixing up “calendar day” vs “nth weekday”: @Lilly’s investigation suggests monthly rules are using `BYDAY` when `BYMONTHDAY` may be required, in [Monthly triggered recurring automation is not running as expected](https://meta.discourse.org/t/-/402664/13?silent=true).
- Rich text composer oddity: dragging an unselected image in the RTE appeared to re-upload repeatedly, but investigation suggested only a single stored upload might occur in [When dragging an unselected image in a rich text editor, it is uploaded repeatedly](https://meta.discourse.org/t/-/402566/16?silent=true) (plus follow-up reasoning in [post 17](https://meta.discourse.org/t/-/402566/17?silent=true)).
- iOS PWA push subscriptions: a PR update aims to ensure the service worker controls the PWA immediately (preventing silent failures) in [Push notification subscription in iOS PWA silently failing](https://meta.discourse.org/t/-/402645/5?silent=true).
- A small #ai settings UX glitch: changing the default LLM doesn’t update agent labels until a reload in [Minor UI bug changing default LLM](https://meta.discourse.org/t/-/402792/1?silent=true).
### #ux
- Mobile layout papercut: the **automation “last run” chip** overlapped the edit button on mobile; a fix is queued in [Automation last run overlapping edit button in mobile](https://meta.discourse.org/t/-/402695/2?silent=true).
- More mobile automation UX: configuration screens for Automation are hard to use at small viewports (especially with new foundation experiments) in [Automation script configuration page on mobile is difficult to use](https://meta.discourse.org/t/-/402713/1?silent=true).
### #General
- Bot report fatigue: the “Web Crawler User Agents” report has ballooned, driven by Qwantbot variants whose numeric suffix changes; suggestion was to consolidate these strings in reporting in [Web Crawler user agents - Qwantbot agents growing in number](https://meta.discourse.org/t/-/402766/1?silent=true).
- A product-direction check-in: a third-party asked whether communities want **gamification beyond trust levels** (XP, streaks, currencies, progression paths) and whether an integration is worth building in [Gamification for Discourse communities beyond trust levels](https://meta.discourse.org/t/-/402802/1?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Falco led the day’s biggest ship: **client-side image pipeline upgrades** (including GIF → animated WebP) in [New client side image optimizations for Discourse](https://meta.discourse.org/t/-/402705/1?silent=true). He also helped unblock a complex Salesforce embed/login situation by recommending either **same base domain** or adjusting **SameSite cookies** in [Salesforce Community iframe embedding](https://meta.discourse.org/t/-/402712/4?silent=true).
- @chapoi jumped on two fronts: confirmed and narrowed down a reproducible navigation/edit bug in [出错了：找不到请求的 url 或资源](https://meta.discourse.org/t/-/402747/2?silent=true), and reinforced trust-level integrity (no “reading time scripts”) in [怎么刷阅读时长？](https://meta.discourse.org/t/-/402738/4?silent=true) (and follow-up clarification in [post 6](https://meta.discourse.org/t/-/402738/6?silent=true)).
- @zogstrip followed up with engineering momentum: he reproduced the “URL/resource not found” editing issue and started a fix in [出错了：找不到请求的 url 或资源](https://meta.discourse.org/t/-/402747/4?silent=true); he also pointed an API error report toward a known fix/upgrade path in [API calls fail due issue with main\_user\_record silenced\_till](https://meta.discourse.org/t/-/402752/3?silent=true); and he escalated the suspected monthly automation logic mismatch by looping in a maintainer in [Monthly triggered recurring automation is not running as expected](https://meta.discourse.org/t/-/402664/14?silent=true).
- @awesomerobot acknowledged and queued a fix for a mobile overlap regression in [Automation last run overlapping edit button in mobile](https://meta.discourse.org/t/-/402695/2?silent=true).
- @martin provided UI semantics/product feedback about misleading “Everyone” labeling for staff-only changes in [Admin Reporting & Analysis: Incremental Changes](https://meta.discourse.org/t/-/395768/27?silent=true).
- @supermathie supported a migration troubleshooting thread by pointing to the relevant guide and asking for a redacted ENV block to diagnose further in [迁移Discourse恢复数据失败](https://meta.discourse.org/t/-/402623/9?silent=true).
- @pmusaraj posted an official status update that backporting has begun and should land in minor releases soon for an OpenID Connect group-sync bug in [OpenID Connect group can kick users out of all unsynced groups](https://meta.discourse.org/t/-/402416/9?silent=true).
- @sam checked in on whether a Gemini Pro budgeting edge case still reproduces in [Thinking budget for Gemini Pro, error when using 0 or -1](https://meta.discourse.org/t/-/388485/5?silent=true).
* * *
Yesterday’s theme was _making things smaller, smoother, and less surprising_—may your GIFs shrink into WebPs, your automations land on the right day of the month, and your 404s politely find their way home.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [13 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/861 "2026-05-13T21:01:35Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
**In the last 24 hours (2026-05-12 → 2026-05-13):**
- **New posts:** 95
- **New topics:** 15
A lot of the conversation clustered around major product updates like **nested replies** ([read more](https://meta.discourse.org/t/-/402812/1?silent=true)) and improvements to **#solved** workflows via the new _“Me too”_ button ([read more](https://meta.discourse.org/t/-/402498/1?silent=true)), plus a steady stream of bug reports and fixes (e.g., the **grid lightbox order** issue: [read more](https://meta.discourse.org/t/-/402817/1?silent=true)).
**Top users (posts / likes in the last 24h):**
| User | Posts | Likes |
| --- | --- | --- |
| @markvanlan | 5 | 40 |
| @Lilly | 8 | 25 |
| @lindsey | 2 | 13 |
| @NateDhaliwal | 3 | 6 |
| @martin | 3 | 6 |
| @awesomerobot | 4 | 6 |
| @gilles | 6 | 6 |
| @zogstrip | 2 | 5 |
| @Richie | 3 | 4 |
| @merefield | 2 | 3 |
* * *
## Interesting Topics
### #Announcements
- **Introducing nested replies** — @markvanlan unveiled an early look at Discourse’s new fully-threaded topic view and the admin controls behind it ([read more](https://meta.discourse.org/t/-/402812/1?silent=true)). Follow-up discussion covered practical rollout concerns like bulk-toggling existing topics ([read more](https://meta.discourse.org/t/-/402812/8?silent=true)), reversibility and how nested mode is represented in the DB ([read more](https://meta.discourse.org/t/-/402812/16?silent=true)), and why threading is intentionally _not_ a per-user preference ([read more](https://meta.discourse.org/t/-/402812/19?silent=true)).
- **Solved improvements: “Me too” for unsolved support topics** — @lindsey announced a new _“Me too”_ button for #solved topics in support categories to help members signal impact and opt into solution notifications ([read more](https://meta.discourse.org/t/-/402498/1?silent=true)). Feedback quickly turned toward admin-side reporting/threshold alerts ([read more](https://meta.discourse.org/t/-/402498/2?silent=true)) and whether “Me too” should bump older threads ([read more](https://meta.discourse.org/t/-/402498/3?silent=true)); @awesomerobot also clarified how it differs from experimental “boost” behavior ([read more](https://meta.discourse.org/t/-/402498/11?silent=true)).
- **Granular group-based permissions for anonymous and logged in users** — @martin explained the deprecation of the confusing `@everyone` pseudogroup in favor of two explicit automatic groups: `anonymous (ID 4)` and `logged_in_users (ID 5)` (behind an upcoming change) ([read more](https://meta.discourse.org/t/-/402273/1?silent=true)). A key clarification: this won’t unexpectedly lock down public categories, because category/tag permissions treat “everyone” differently ([read more](https://meta.discourse.org/t/-/402273/4?silent=true)).
* * *
### #bug
- **Grid lightbox images show in the wrong order** (#lightbox) — @Shauny reported that arrow-key navigation in a grid-based lightbox didn’t follow upload order ([read more](https://meta.discourse.org/t/-/402817/1?silent=true)). @zogstrip traced it, fixed it, and linked the core PR for review ([read more](https://meta.discourse.org/t/-/402817/3?silent=true)).
- **Users cannot see who is a group owner** — A regression left “group owner” info present in page data but no longer rendered for regular users ([read more](https://meta.discourse.org/t/-/402886/1?silent=true)). @awesomerobot confirmed it was likely an unintentional change from a 2023 refactor and opened a PR to restore visibility ([read more](https://meta.discourse.org/t/-/402886/2?silent=true)).
- **Norwegian locale mismatch in AI locale detection vs content-localization locales** (#ai) — A report showed Norwegian being detected as `no` while translation targets used `nb_NO/nb-NO`, causing near-identical translations and wasted credits ([read more](https://meta.discourse.org/t/-/402859/1?silent=true)). @nat suggested a quick mitigation by duplicating the locale detection agent and adjusting its prompt ([read more](https://meta.discourse.org/t/-/402859/2?silent=true)); the reporter found `nb-NO` wording worked best in practice ([read more](https://meta.discourse.org/t/-/402859/5?silent=true)).
- **Assign/Re-assign on mobile: can’t type in the search field** (#mobile, #assign) — Continued reports suggest the assign modal can error out on mobile, preventing typing and producing JS exceptions (including attempts at safe-guarding `targetElement`) ([read more](https://meta.discourse.org/t/-/400986/12?silent=true)).
- **Incorrect ActivityPub handler addresses shown in `/ap/about`** (#activitypub) — A small but impactful formatting bug: displayed handles were missing a leading `@`, making them harder to copy into ActivityPub clients ([read more](https://meta.discourse.org/t/-/402848/1?silent=true)).
* * *
### #development
- **Discourse-patch-triage bot: how to work with forks** — @Lilly asked how to collaborate effectively with the new `discourse-patch-triage` bot, especially when the PR is from a fork and the bot suggests changes ([read more](https://meta.discourse.org/t/-/402898/1?silent=true)). @isaac clarified how to invoke it (`@patch-triage` + plain English), what it can do, and that it **cannot** commit onto forks (and promised clearer messaging + internal discussion about permissions) ([read more](https://meta.discourse.org/t/-/402898/2?silent=true), [read more](https://meta.discourse.org/t/-/402898/5?silent=true)).
- **Potential upcoming plugin name clash: “Workflow”** — @merefield flagged a possible collision: a core PR appears to introduce “Workflow” while a long-standing plugin with the same name already exists, risking admin UI confusion ([read more](https://meta.discourse.org/t/-/402854/1?silent=true)). Related background: the existing plugin’s Meta topic and ongoing compatibility updates ([read more](https://meta.discourse.org/t/-/347110/21?silent=true)).
- **MiniScheduler + Sidekiq 8 integration PR merged and released** — A quick turnaround: @dmke requested another look, and @david confirmed the PR was merged and released ([read more](https://meta.discourse.org/t/-/400645/2?silent=true), [read more](https://meta.discourse.org/t/-/400645/3?silent=true)).
* * *
### #Support
- **Hide user cards for anonymous users** (#solved) — In a French-language support thread, @gilles asked how to prevent user cards from displaying to anonymous visitors ([read more](https://meta.discourse.org/t/-/402846/1?silent=true)). @chapoi pointed to the relevant site setting and the topic was marked solved ([read more](https://meta.discourse.org/t/-/402846/2?silent=true)).
- **Translation only translates the title, not the post** (#content-localization) — A report described post body translation failing while topic titles translated normally ([read more](https://meta.discourse.org/t/-/402858/1?silent=true)). @nat noted a post-length limit can block translation and indicated it could likely be increased; shortly after, the content did translate ([read more](https://meta.discourse.org/t/-/402858/2?silent=true)).
- **Fresh install: activation email not sent (but test email works)** (#email) — A self-host admin found that registration/activation emails didn’t arrive even though `discourse-doctor` test email delivered immediately ([read more](https://meta.discourse.org/t/-/402893/1?silent=true)). Troubleshooting focused on verifying whether the mails were logged/sent via `EmailLog` and checking `/logs` + `/sidekiq` for enqueue/sending behavior ([read more](https://meta.discourse.org/t/-/402893/2?silent=true)), with follow-up evidence showing only the test message present in `EmailLog` ([read more](https://meta.discourse.org/t/-/402893/3?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@markvanlan** drove the launch discussion for **nested replies** , covering enabling options, bulk actions, and reversibility ([read more](https://meta.discourse.org/t/-/402812/1?silent=true), [read more](https://meta.discourse.org/t/-/402812/8?silent=true), [read more](https://meta.discourse.org/t/-/402812/16?silent=true)). He also clarified why threading is an admin-level decision rather than user preference ([read more](https://meta.discourse.org/t/-/402812/19?silent=true)).
- **@lindsey** shipped and discussed the new **#solved “Me too”** workflow, inviting ideas for admin-facing reporting and surfacing mechanisms ([read more](https://meta.discourse.org/t/-/402498/1?silent=true), [read more](https://meta.discourse.org/t/-/402498/4?silent=true)).
- **@martin** explained the new **anonymous/logged-in pseudogroups** and reassured admins that category visibility won’t unexpectedly change when the upcoming change is enabled ([read more](https://meta.discourse.org/t/-/402273/1?silent=true), [read more](https://meta.discourse.org/t/-/402273/4?silent=true)). He also landed a clarity improvement related to reporting permissions options in an ongoing announcements thread ([read more](https://meta.discourse.org/t/-/395768/28?silent=true)).
- **@awesomerobot** handled multiple fixes and clarifications: distinguishing “Me too” from “boost” in #solved contexts ([read more](https://meta.discourse.org/t/-/402498/11?silent=true)), confirming the **group owner visibility** regression and opening a PR ([read more](https://meta.discourse.org/t/-/402886/2?silent=true)), and pushing an update to the **Air Theme** to address reported issues ([read more](https://meta.discourse.org/t/-/197703/604?silent=true)). He also opened a PR for a minor **LLM default selection UI** improvement ([read more](https://meta.discourse.org/t/-/402792/2?silent=true)).
- **@zogstrip** fixed the **grid lightbox ordering** bug and linked the core PR ([read more](https://meta.discourse.org/t/-/402817/3?silent=true)). Separately, he noted a mention-check fix revealed a new edge case affecting AI agent mentions and linked the PR tracking that nuance ([read more](https://meta.discourse.org/t/-/401292/6?silent=true)).
- **@nat** helped diagnose translation behavior (including post-length limits) in #Support ([read more](https://meta.discourse.org/t/-/402858/2?silent=true)) and acknowledged the **Norwegian locale detection** mismatch, proposing prompt-level mitigations while a core prompt update is considered ([read more](https://meta.discourse.org/t/-/402859/2?silent=true)).
- **@chapoi** provided the solved answer for disabling user cards for anonymous visitors via a site setting ([read more](https://meta.discourse.org/t/-/402846/2?silent=true)).
- **@dax** jumped into the “Me too” launch thread to explain it wasn’t enabled on Meta, then enabled it for testing on [try.discourse.org](http://try.discourse.org) (with a brief “power went out” interruption mid-setup) ([read more](https://meta.discourse.org/t/-/402498/6?silent=true), [read more](https://meta.discourse.org/t/-/402498/9?silent=true)).
- **@Falco** supported self-hosted Discourse AI sentiment users by noting an upstream model PR wasn’t merged yet and recommending pointing to his branch directly, with updated docker guidance ([read more](https://meta.discourse.org/t/-/334451/15?silent=true)).
- **@isaac** closed the loop on the `discourse-patch-triage` bot workflow, detailing how to interact with it, what actions it supports, and why forks can’t receive bot commits—then followed up to raise fork write-access internally ([read more](https://meta.discourse.org/t/-/402898/2?silent=true), [read more](https://meta.discourse.org/t/-/402898/5?silent=true)).
* * *
If yesterday was any indication, today’s going to be _deeply threaded_—just try to keep your debugging sessions shorter than the neighborhood power outages.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [14 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/862 "2026-05-14T21:01:22Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 50**
- **New topics (last 24h): 5**
- **Thread hotspots:** nested-reply UX and clarity came up repeatedly (from the nested replies announcement itself to theme-level tweaks), plus a steady stream of plugin and bug triage—see [nested replies](https://meta.discourse.org/t/-/402812/22?silent=true), [reply button label clarity](https://meta.discourse.org/t/-/402911/2?silent=true), and [“Me too” issue reporting improvements](https://meta.discourse.org/t/-/402498/14?silent=true).
**Top users (posts / likes in the last 24h)**
| User | Posts | Likes |
| --- | --- | --- |
| **@Lilly** | 7 | 24 |
| **@EricGT** | 8 | 8 |
| **@ice.d** | 4 | 4 |
| **@ted** | 2 | 5 |
| **@NateDhaliwal** | 3 | 2 |
| **@RGJ** | 3 | 2 |
| **@putty** | 2 | 2 |
| **@jpishgar** | 1 | 3 |
| **@HAWK** | 1 | 2 |
| **@ToddZ** | 1 | 2 |
A few of the most-referenced/active conversations to catch up on quickly: [Discourse Reply Button Labels](https://meta.discourse.org/t/-/402911/1?silent=true), [Hide Votes Left](https://meta.discourse.org/t/-/402966/1?silent=true), [What are some common breaking points as communities grow?](https://meta.discourse.org/t/-/402716/6?silent=true), [Custom dropdown user field contains unselectable value](https://meta.discourse.org/t/-/402557/3?silent=true), and [Norwegian locale detection](https://meta.discourse.org/t/-/402859/6?silent=true).
* * *
## Interesting Topics
### #customization:theme component
- @Lilly shipped a lightweight component to make **reply actions less ambiguous** by differentiating _topic_ vs _post_ replies—sparked by nested reply UX concerns raised by @EricGT and others ([original component](https://meta.discourse.org/t/-/402911/1?silent=true), [why it matters w/ nested replies](https://meta.discourse.org/t/-/402911/2?silent=true), [update enabling customization for both labels](https://meta.discourse.org/t/-/402911/9?silent=true), [ToddZ’s wording suggestions](https://meta.discourse.org/t/-/402911/6?silent=true) — [read more](https://meta.discourse.org/t/-/402911/1?silent=true))
- @putty introduced a small UI tweak to **hide the “votes left” line** when admins simulate “unlimited” voting by setting huge limits—followed by a discussion on whether it should reappear when votes get low ([theme component](https://meta.discourse.org/t/-/402966/1?silent=true), [threshold idea](https://meta.discourse.org/t/-/402966/2?silent=true), [intent/constraints](https://meta.discourse.org/t/-/402966/3?silent=true) — [read more](https://meta.discourse.org/t/-/402966/1?silent=true))
### #Enterprise (#enterprise-ready)
- Community scaling pain points got a thoughtful deep-dive: @jpishgar highlighted _taxonomy breakpoints_ and “buried knowledge” as activity explodes ([taxonomy/structure breakpoint](https://meta.discourse.org/t/-/402716/6?silent=true)), @ice.d shared the lived reality of _moderation load_ and owner absence ([staff burden story](https://meta.discourse.org/t/-/402716/7?silent=true)), and @ted pushed on how to design transparent moderation at scale ([systems question](https://meta.discourse.org/t/-/402716/8?silent=true) — [read more](https://meta.discourse.org/t/-/402716/6?silent=true))
### #Announcements
- The newly announced “Me too” capability for #solved topics continued to evolve via feedback: @NateDhaliwal helped folks find it under **Admin → Upcoming Changes** ([where to enable it](https://meta.discourse.org/t/-/402498/13?silent=true)), @EricGT proposed a complementary **“Works for me now”** signal to reflect real-time recoveries ([suggestion](https://meta.discourse.org/t/-/402498/16?silent=true)), and @RGJ questioned whether the counter should start at **0 vs 1** and asked for visibility into _who_ clicked it ([counter + attribution](https://meta.discourse.org/t/-/402498/20?silent=true) — [read more](https://meta.discourse.org/t/-/402498/14?silent=true))
- Third-party client implications of nested replies kept rolling in: @nicolsdennis asked whether the **Top/New/Old** sort could be exposed via the _existing_ flat topic JSON endpoint so clients can benefit without adopting nested rendering ([API/sort question](https://meta.discourse.org/t/-/402812/22?silent=true) — [read more](https://meta.discourse.org/t/-/402812/22?silent=true))
- Admin UX snag: @EricGT reported that when opening Upcoming Changes from inbox notification URLs, the **Preview link disappears** , making it easy to miss the intended workflow ([report](https://meta.discourse.org/t/-/392894/26?silent=true) — [read more](https://meta.discourse.org/t/-/392894/26?silent=true))
- A UI regression report landed on the long-running Foundation modernization thread: @NateDhaliwal noted **severe overlap** in the pinned state menu options ([screenshot + report](https://meta.discourse.org/t/-/395331/83?silent=true) — [read more](https://meta.discourse.org/t/-/395331/83?silent=true))
### #bug
- A subtle signup edge case around custom user fields got a concrete fix direction: @ted confirmed inconsistent sanitization between signup vs profile update, and posted a PR to align behavior ([analysis](https://meta.discourse.org/t/-/402557/3?silent=true) — [read more](https://meta.discourse.org/t/-/402557/3?silent=true))
- AI localization configuration: Norwegian was being detected as `no` while the localization setting expects `nb_NO`; @nat confirmed the correct approach and planned prompt improvements so it respects **supported languages** settings ([team confirmation](https://meta.discourse.org/t/-/402859/6?silent=true) — [read more](https://meta.discourse.org/t/-/402859/6?silent=true))
### #contribute:feature
- Moderation ergonomics: @ice.d suggested a **multi-select “flag as spam/off-topic”** workflow to reduce repetitive clicking and potentially enable batch handling in the review queue (#moderation #review-queue) ([proposal](https://meta.discourse.org/t/-/402928/1?silent=true) — [read more](https://meta.discourse.org/t/-/402928/1?silent=true))
- Branding/UX for first impressions: @Ethsim2 proposed a separate **mobile\_logo\_dark** (or login-specific) setting for the login/signup splash screen so admins don’t have to compromise between the unauthenticated splash and the compact logged-in header (#login #ux) ([feature request](https://meta.discourse.org/t/-/402949/1?silent=true) — [read more](https://meta.discourse.org/t/-/402949/1?silent=true))
### #Self-hosting
- Security heads-up: @AquaL1te shared a write-up on chaining an nginx rewrite-engine RCE with a kernel LPE, and @RGJ clarified it **doesn’t apply to a standard Discourse install** (still useful reading for self-hosters with bespoke nginx setups) ([advisory link](https://meta.discourse.org/t/-/402978/1?silent=true), [scope clarification](https://meta.discourse.org/t/-/402978/2?silent=true) — [read more](https://meta.discourse.org/t/-/402978/1?silent=true))
### #Support
- API posting warnings (Chinese language thread): @sniper756 investigated a warning seen during API-created posts and observed it _disappeared_ after toggling the AI plugin; @Ethsim2 suggested collecting timing and reproducibility data—especially since the environment is **ARM64** ([more environment details](https://meta.discourse.org/t/-/402855/3?silent=true), [toggle results](https://meta.discourse.org/t/-/402855/4?silent=true), [debug checklist](https://meta.discourse.org/t/-/402855/5?silent=true), [plan to disable AI longer](https://meta.discourse.org/t/-/402855/6?silent=true) — [read more](https://meta.discourse.org/t/-/402855/5?silent=true))
- Composer mode issue confirmed as plugin-related: @Hasimir reported the **default\_composition\_mode** bug goes away when disabling Custom Wizard, but noted the real constraint is “we need the Wizard” ([confirmation](https://meta.discourse.org/t/-/401379/9?silent=true) — [read more](https://meta.discourse.org/t/-/401379/9?silent=true))
### #customization:plugin
- Discourse Workflow plugin got a usability upgrade: @merefield added a new **visual editor** to make step editing less opaque, and bundled fixes for some deprecations ([visual editor PR announcement](https://meta.discourse.org/t/-/347110/22?silent=true) — [read more](https://meta.discourse.org/t/-/347110/22?silent=true))
- Discourse Subscriptions (#official) saw a serious real-world edge case report: a Stripe PaymentIntent is allegedly created without a valid payment method in certain “expired card then update” flows, causing silent failures for end users ([bug report](https://meta.discourse.org/t/-/140818/751?silent=true) — [read more](https://meta.discourse.org/t/-/140818/751?silent=true))
_(More threads that also saw activity, if you’re doing a broader scan: Graceful theme discussion + pattern replacement work ([Graceful](https://meta.discourse.org/t/-/93040/162?silent=true)); OpenID Connect username edge case ([OIDC](https://meta.discourse.org/t/-/103632/325?silent=true)); “anonymous email” category issue persisting in 2026.5.0 ([bug thread](https://meta.discourse.org/t/-/42871/31?silent=true)); signup URL parameter behavior ([support](https://meta.discourse.org/t/-/402890/4?silent=true)); Custom Wizard maintenance concerns ([plugin thread](https://meta.discourse.org/t/-/73345/946?silent=true)); plus install/how-to docs referenced by new theme components ([theme install guide](https://meta.discourse.org/t/-/63682/1?silent=true), [themes beginner guide](https://meta.discourse.org/t/-/91966/1?silent=true)).)_
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@HAWK** weighed in on scalable moderation governance—emphasizing trusted people, regular comms, documented processes, and clear appeals—continuing the “breaking points as communities grow” thread in #Enterprise ([reply](https://meta.discourse.org/t/-/402716/9?silent=true) — [read more](https://meta.discourse.org/t/-/402716/9?silent=true))
- **@awesomerobot** shared an important update for #topic-voting admins: a new site setting **`Topic voting enable vote limits`** can remove limits entirely, reducing the need for huge “workaround” limits (while still noting the theme component’s value for mixed trust-level configurations) ([vote-limit setting note](https://meta.discourse.org/t/-/402966/4?silent=true) — [read more](https://meta.discourse.org/t/-/402966/4?silent=true))
- **@awesomerobot** also addressed a design concern in the official Graceful theme: after noting the pattern’s association risk, they proposed swapping it for a different traditional Japanese pattern and linked the PR ([context + PR](https://meta.discourse.org/t/-/93040/162?silent=true) — [read more](https://meta.discourse.org/t/-/93040/162?silent=true))
- **@nat** confirmed how to fix Norwegian locale mis-detection for AI localization and noted an upcoming improvement to the generic system prompt so it better respects configured supported languages ([confirmation + plan](https://meta.discourse.org/t/-/402859/6?silent=true) — [read more](https://meta.discourse.org/t/-/402859/6?silent=true))
* * *
_That’s a wrap: yesterday’s meta was all about making tiny UI labels do big clarity work—while “Me too” counters, vote limits, and nested reply sorting all tried to politely line up and behave._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [15 mei 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/863 "2026-05-15T21:02:33Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 60**
- **New topics (last 24h): 13**
**Top users (posts / likes received in the last 24h):**
- @Moin — **7 posts** , **12 likes**
- @ted — **4 posts** , **11 likes**
- @Lilly — **5 posts** , **8 likes**
- @chapoi — **5 posts** , **4 likes**
- @nathank — **3 posts** , **3 likes**
- @RGJ — **2 posts** , **9 likes**
- @martin — **2 posts** , **6 likes**
- @Falco — **1 post** , **2 likes**
- @tobiaseigen — **1 post** , **3 likes**
- @markvanlan — **1 post** , **3 likes**
**Threads that drew quick attention (likes + replies):**
- A near-miss UX moment: the **Delete** button positioning while editing categories raised alarms in [this report](https://meta.discourse.org/t/-/403037/1?silent=true).
- Bookmark UI polish: a confusing toggle/button in the edit-bookmark modal sparked a fix in [this thread](https://meta.discourse.org/t/-/403018/1?silent=true).
- Horizon theme news: **high context topic cards** are now default (with lots of love for the theme) in [the announcement](https://meta.discourse.org/t/-/402843/1?silent=true).
- Docs UX friction: how to get **TOC** back (and where “toggle translations” went) came up in [this discussion](https://meta.discourse.org/t/-/403003/1?silent=true).
- Composer edge case: an HR line stealing focus from the emoji picker was captured (with repro steps) in [this bug report](https://meta.discourse.org/t/-/403019/1?silent=true).
**Also active across the site (support, plugins, and product feedback):**
- “Me too” semantics for Solved’s reported-issue counter got debated in [Solved improvements](https://meta.discourse.org/t/-/402498/22?silent=true).
- Topic Voting UI tweaks (hiding “votes left”) continued in [Hide Votes Left](https://meta.discourse.org/t/-/402966/7?silent=true).
- Upload defaults: the visibility/impact of PNG→JPEG settings resurfaced in [Missing PNG to JPEG settings](https://meta.discourse.org/t/-/395964/5?silent=true).
- Wizard workflows: a plugin regression + UX questions were handled in [Custom Wizard Plugin 🧙](https://meta.discourse.org/t/-/73345/947?silent=true).
- Docs navigation components: DiscoTOC compatibility questions popped up in [DiscoTOC](https://meta.discourse.org/t/-/111143/486?silent=true).
- SEO cleanup ideas: auto-redirecting bad page numbers to reduce crawl errors was suggested in [Googlebot 404 errors due to page numbers](https://meta.discourse.org/t/-/96337/15?silent=true).
- A mobile calendar/event fix progressed (new PR linked) in [Bug calendar event on mobile](https://meta.discourse.org/t/-/372658/8?silent=true).
- Admin UX consistency: sidebar defaults not overriding user customizations was re-tested in [Sidebar categories for all users](https://meta.discourse.org/t/-/402479/6?silent=true).
- API performance warnings: more diagnostics were suggested (including `curl -w` timing) in [API posting warning thread](https://meta.discourse.org/t/-/402855/8?silent=true).
- Anti-bump needs: preventing repeated self-bumps was asked about in [No Bump First Post Plugin](https://meta.discourse.org/t/-/385290/6?silent=true).
- Gamification admin UX: creating a new leaderboard wiping an older one was raised in [Discourse Gamification](https://meta.discourse.org/t/-/225916/453?silent=true).
- Upcoming Changes metadata: optional “Feedback” and “Preview” links were clarified in [Upcoming Changes](https://meta.discourse.org/t/-/392894/27?silent=true).
* * *
## Interesting Topics
### #Announcements
- @martin announced that **high context topic cards** are now enabled by default in the Horizon theme (with a recap of signals like _Solved_ / _Voting_ / _Assign_ / tags / excerpts) — [read more](https://meta.discourse.org/t/-/402843/1?silent=true).
_(Related: the original Horizon cards intro is here: [read more](https://meta.discourse.org/t/-/393470/1?silent=true), plus plugin refs for [Discourse Solved](https://meta.discourse.org/t/-/30155/1?silent=true), [Topic Voting](https://meta.discourse.org/t/-/40121/1?silent=true), and [Assign](https://meta.discourse.org/t/-/58044/1?silent=true).)_
- In the nested replies rollout, @markvanlan explained why the team didn’t extend Post Voting to achieve the same effect, emphasizing maintainability and UX in [this reply](https://meta.discourse.org/t/-/402812/27?silent=true).
### #ux
- @RGJ flagged that the **Delete category** action appears far more prominent than **Save** in the simplified category screen, creating a risky “oops” moment in [this UX report](https://meta.discourse.org/t/-/403037/1?silent=true).
- @ted questioned whether a “superfluous” toggle/button belongs in the **edit bookmark** dialog; @chapoi ultimately removed the toggle (and linked a PR) in [the follow-up](https://meta.discourse.org/t/-/403018/6?silent=true) (#bookmarks #fixed).
- @Moin asked how to **re-enable the TOC on docs** (after clicking timeline) and noted that “Toggle translations” becomes hard to reach in simple mode in [this thread](https://meta.discourse.org/t/-/403003/1?silent=true) (#disco-toc #doc-categories #content-localization).
- @ted proposed showing **uneditable user fields** as disabled inputs (instead of hiding them) to reduce confusion; @chapoi raised questions about hidden-field use cases in [the discussion](https://meta.discourse.org/t/-/403015/2?silent=true) (#user-custom-fields).
### #bug
- A composer edge case: placing the cursor before a horizontal rule and pressing ↓ can cause the HR to steal focus and close the emoji picker; repro + recording are in [this bug report](https://meta.discourse.org/t/-/403019/1?silent=true) (#composer #emoji).
- A subscriptions issue: silent subscription failures were moved for visibility into #Contribute > Bug by @nathank in [this moderation note](https://meta.discourse.org/t/-/403082/2?silent=true) (#subscriptions).
### #customization:theme component
- @Lilly shipped improvements to **Discourse Reply Button Labels** , including a new setting to show the _topic reply button label_ on mobile viewports (with notes on why post-reply labels would break the mobile footer) in [this update](https://meta.discourse.org/t/-/402911/14?silent=true).
### #contribute:feature
- @Moin suggested suppressing the **“New features available!”** notice on brand-new forums, arguing that _everything_ is “new” for first-time admins in [this feature request](https://meta.discourse.org/t/-/402999/1?silent=true).
- @Ethsim2 opened a draft PR to support a separate **dark-mode login/signup splash image** (new `splash_screen_image_dark` setting) in [this implementation update](https://meta.discourse.org/t/-/402949/2?silent=true) (#login #ux).
- In feedback about Discourse Embedding, @Falco confirmed the **login friction loop** (new tab → logged in → iframe still logged out until refresh) is now fixed and pointed to an update path in [this reply](https://meta.discourse.org/t/-/400721/55?silent=true) (#embedding).
### #Enterprise
- A cautionary scaling story: a community’s information architecture collapsed under _thousands_ of categories, and @HAWK reinforced why scalable IA (and tags) matter in [this exchange](https://meta.discourse.org/t/-/402717/4?silent=true) (#enterprise-ready).
### #Site feedback
- Meta’s #Wiki “simple mode” test prompted concerns about contributor recognition and discoverability; @Moin argued visible authorship matters _more_ (not less) in wiki-style docs in [this feedback topic](https://meta.discourse.org/t/-/403006/1?silent=true).
_(Related background links mentioned in-thread: [new homes for official/community docs](https://meta.discourse.org/t/-/322620/6?silent=true) and [documentation contribution opportunities](https://meta.discourse.org/t/-/326614/1?silent=true).)_
### #General
- A community member suggested nominating Discourse for the **Digital Public Goods Alliance registry** as both a values and marketing win, with links to the registry process in [this topic](https://meta.discourse.org/t/-/403061/1?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @chapoi jumped into several UX/product threads: they confirmed the bookmark dialog toggle is overkill and ultimately removed it in [Superfluous button in edit bookmark dialog?](https://meta.discourse.org/t/-/403018/6?silent=true), and they also probed for more context on uneditable profile fields in [Show uneditable user fields…](https://meta.discourse.org/t/-/403015/2?silent=true).
- @martin shipped Horizon theme news by announcing the new default for topic list cards in [High context topic cards are now enabled by default in the Horizon theme](https://meta.discourse.org/t/-/402843/1?silent=true), and clarified configuration expectations for Upcoming Changes metadata in [Upcoming Changes](https://meta.discourse.org/t/-/392894/27?silent=true).
- @markvanlan added strategic context around nesting and long-term maintainability, including how it relates to post-voting-style experiences, in [Introducing nested replies](https://meta.discourse.org/t/-/402812/27?silent=true).
- @Falco closed the loop on a key embed/conversion pain point, confirming the improved embedded-login flow is now fixed in [Tecnoblog’s Experience With Discourse Comments](https://meta.discourse.org/t/-/400721/55?silent=true).
- @HAWK contributed scaling and community-building guidance: they shared research on sustaining power users in [What are some common breaking points as communities grow?](https://meta.discourse.org/t/-/402716/14?silent=true) and reinforced the “too many categories” cautionary tale in [The risks of scaling too late vs. too early](https://meta.discourse.org/t/-/402717/4?silent=true).
- @lindsey clarified why the Solved “me too” counter starts at 1 (representing the topic author) in [Solved improvements: Allowing members to indicate they’re experiencing a reported issue](https://meta.discourse.org/t/-/402498/22?silent=true).
- @awesomerobot suggested a layout alternative for the bookmark modal toggle (before it was removed) in [Superfluous button in edit bookmark dialog?](https://meta.discourse.org/t/-/403018/5?silent=true).
_That’s a wrap—may your emoji picker keep focus, your category editor keep “Delete” far away from “Save,” and your bookmarks stay blissfully toggle-free._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [16 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/864 "2026-05-16T21:01:53Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 81**
- **New topics (last 24h): 14**
**Top users (posts / likes in the last 24h):**
| User | Posts | Likes |
| --- | --- | --- |
| @Lilly | 18 | 17 |
| @martin | 1 | 12 |
| @Arkshine | 1 | 5 |
| @darkpixlz | 4 | 5 |
| @sam | 1 | 5 |
| @Falco | 2 | 4 |
| @Moin | 3 | 3 |
| @EricGT | 7 | 3 |
| @NateDhaliwal | 2 | 3 |
| @Jagster | 1 | 2 |
**Most active [@team](https://meta.discourse.org/groups/team?silent=true) (Discourse Team) members:**
- @martin (1 post, 12 likes) — [read more](https://meta.discourse.org/t/-/401309/1?silent=true)
- @sam (1 post, 5 likes) — [read more](https://meta.discourse.org/t/-/403121/5?silent=true)
- @Falco (2 posts, 4 likes) — [read more](https://meta.discourse.org/t/-/403151/4?silent=true), [read more](https://meta.discourse.org/t/-/403161/12?silent=true)
- @j.jaffeux (1 post, 0 likes) — [read more](https://meta.discourse.org/t/-/402854/4?silent=true)
* * *
## Interesting Topics
### #Announcements
- **Easier Events category setup (Calendar + Events plugin)**: @martin announced a streamlined “Events” category type that auto-enables the right settings for #calendar-and-event and #events workflows, building on the same “category setup initiative” as easier support/ideas categories. [read more](https://meta.discourse.org/t/-/401309/1?silent=true) (Related: [Calendar and Event plugin](https://meta.discourse.org/t/-/97376/1?silent=true), [Support categories via Solved](https://meta.discourse.org/t/-/398338/1?silent=true), [Ideas categories via Voting](https://meta.discourse.org/t/-/399365/1?silent=true))
### #Support
- **Nginx CVE-2026-42945—are Discourse containers vulnerable?** A security question kicked off with @k0tsk, @darkpixlz pushed back on scope, and @sam confirmed Discourse will update the base image and noted default rewrite rules aren’t vulnerable. [read more](https://meta.discourse.org/t/-/403121/1?silent=true), [read more](https://meta.discourse.org/t/-/403121/3?silent=true), [read more](https://meta.discourse.org/t/-/403121/5?silent=true)
- **Discourse AI translation “not working” turned out to be a preference toggle** : @EricGT reported translation confusion, and @Lilly/@Moin helped trace it to the “show original language” preference (and the topic-level toggle tied to it). [read more](https://meta.discourse.org/t/-/403160/1?silent=true), [read more](https://meta.discourse.org/t/-/403160/6?silent=true), [read more](https://meta.discourse.org/t/-/403160/9?silent=true) (Background referenced: _Viewing localized content_ [read more](https://meta.discourse.org/t/-/370969/1?silent=true))
- **Trouble deleting topics, plus nested replies edge cases** : In a “why can’t I delete topics?” thread, @Falco clarified the user-facing rule (_only if no replies and \<24h old_), while follow-ups suggested #Nested Replies Testing can interfere with moderation/admin actions in nested view. [read more](https://meta.discourse.org/t/-/403151/1?silent=true), [read more](https://meta.discourse.org/t/-/403151/4?silent=true), [read more](https://meta.discourse.org/t/-/403151/11?silent=true) (Related: wrench actions failing in nested mode [read more](https://meta.discourse.org/t/-/403155/1?silent=true), deleted nested topic causing issues [read more](https://meta.discourse.org/t/-/403161/12?silent=true), permissions reference mentioned [read more](https://meta.discourse.org/t/-/224824/1?silent=true))
- **/about page group visibility: hidden groups vs overlapping visible groups** : @Ethsim2 documented a scenario where hiding a group section on `/about` didn’t prevent a user from showing up via another visible group, and asked whether that’s intended behavior. [read more](https://meta.discourse.org/t/-/403162/1?silent=true)
- **Tags on the hosted Free plan** : A quick clarification thread noted that tags aren’t available on the hosted free tier right now (upgrade/self-host needed). [read more](https://meta.discourse.org/t/-/403137/1?silent=true), [read more](https://meta.discourse.org/t/-/403137/2?silent=true) (Related: Free plan beta announcement [read more](https://meta.discourse.org/t/-/395632/1?silent=true))
### #bug
- **Theme Creator export shows a white screen (mobile-only repro so far)**: @kairo162 reported a broken export flow, and @Lilly confirmed it reproduces on mobile (desktop OK), leaving the page stuck blank. [read more](https://meta.discourse.org/t/-/403108/1?silent=true), [read more](https://meta.discourse.org/t/-/403108/2?silent=true)
- **How do you close full-screen reactions on mobile?** @Lilly described getting trapped in a full-screen reactions UI on iPhone/Chrome with no obvious dismissal except reloading the site—hard to reproduce, but disruptive. [read more](https://meta.discourse.org/t/-/403149/1?silent=true)
- **Flags requiring a message can crash and fail to submit (TypeError)**: @cuo_wu reported an uncaught error when submitting `require_message` flags (e.g. “Something else”), with a console stack trace and root-cause notes. [read more](https://meta.discourse.org/t/-/403133/1?silent=true)
- **Nested mode breaks post admin “wrench” actions (and related deletion/recovery pain)**: @Lilly reported that wrench actions appear but fail silently in nested view, requiring switching back to flat mode for moderation actions. [read more](https://meta.discourse.org/t/-/403155/1?silent=true) (Related nested/deletion symptoms: [read more](https://meta.discourse.org/t/-/403151/11?silent=true), [read more](https://meta.discourse.org/t/-/403161/12?silent=true))
### #wordpress
- **Older WordPress-embedded topics missing `noindex` + canonical** : @Thiago_Mobilon reported older embed-created topics losing the `X-Robots-Tag: noindex` header and canonical back to WordPress; @angus asked targeted questions to narrow down what changed. [read more](https://meta.discourse.org/t/-/403109/1?silent=true), [read more](https://meta.discourse.org/t/-/403109/2?silent=true) (Possibly related embed/nested behavior observed elsewhere: [read more](https://meta.discourse.org/t/-/400721/56?silent=true))
### #development
- **Upcoming plugin name clash: “Workflow”** : In a naming dispute, @j.jaffeux advised third-party developers to avoid “Discourse X” style names to reduce collisions (suggesting explicit vendor namespaces), with the plugin author disagreeing. [read more](https://meta.discourse.org/t/-/402854/4?silent=true), [read more](https://meta.discourse.org/t/-/402854/5?silent=true)
- **Dev bootstrap: creating the first admin without email + what the dev toolbar does** : @Ethsim2 summarized a clearer mental model for admin creation in dev (`d/boot_dev --init`, MailHog, `rails admin:create`), and @Moin pointed out the vertical **developer toolbar** and its toggles ([safe mode](https://meta.discourse.org/t/53504?silent=true), verbose localization, outlets, etc.). [read more](https://meta.discourse.org/t/-/399187/6?silent=true), [read more](https://meta.discourse.org/t/-/399187/7?silent=true) (Toolbar intro: [read more](https://meta.discourse.org/t/-/346215/1?silent=true))
### #customization:theme component
- **Quote Callouts: updates to history rendering, excerpts, and shortcut** : @Arkshine shipped improvements so callouts render in revision history, onebox excerpts strip the marker, and the keyboard shortcut changed to `ctrl/⌘ + alt + c`. [read more](https://meta.discourse.org/t/-/350962/68?silent=true)
### #contribute:feature
- **Change the “More…” reactions icon when any-emoji reactions are enabled** : A feature request proposes replacing the gray smiley used as the “More…” affordance in #reactions, continuing the earlier thread about reactions UX. [read more](https://meta.discourse.org/t/-/403116/1?silent=true) (Context: [read more](https://meta.discourse.org/t/-/227785/35?silent=true))
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@martin** shipped an #Announcements guide to streamline creating Events categories—automatically enabling key calendar/event settings and wiring the category into the events calendar configuration. [read more](https://meta.discourse.org/t/-/401309/1?silent=true)
- **@sam** responded to the Nginx CVE thread, saying Discourse will update the base image and noting default rewrite rules aren’t vulnerable. [read more](https://meta.discourse.org/t/-/403121/5?silent=true)
- **@Falco** clarified topic-deletion limits for regular users (_no replies, under 24h_), and separately flagged what looks like a bug path involving deleted nested topics (planning to investigate). [read more](https://meta.discourse.org/t/-/403151/4?silent=true), [read more](https://meta.discourse.org/t/-/403161/12?silent=true)
- **@j.jaffeux** weighed in on a plugin naming conflict, recommending developers avoid “Discourse X” naming to reduce clashes and adopt explicit namespaces. [read more](https://meta.discourse.org/t/-/402854/4?silent=true)
* * *
Yesterday’s vibe check: we made event planning easier while simultaneously discovering that nested replies can hide the moderation wrench—so if your tools go missing, try “flat mode” before you start blaming Nginx. (See: [events category setup](https://meta.discourse.org/t/-/401309/1?silent=true), [nested wrench issue](https://meta.discourse.org/t/-/403155/1?silent=true), [Nginx CVE thread](https://meta.discourse.org/t/-/403121/5?silent=true))
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [17 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/865 "2026-05-17T21:01:58Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h):** 36
- **New topics (last 24h):** 4
- **Top users (posts / likes):**
- **@Crown1** — 8 posts / 5 likes
- **@darkpixlz** — 5 posts / 1 like
- **@mcwumbly** — 4 posts / 2 likes
- **@Ethsim2** — 4 posts / 3 likes
- **@Lilly** — 2 posts / 7 likes
- **@NateDhaliwal** — 3 posts / 5 likes
- **@Eviepayne** — 3 posts / 1 like
- **@Falco** — 1 post / 2 likes
- **@sniper756** — 1 post / 1 like
- **@Moin** — 1 post / 1 like
* * *
## Interesting Topics
### #Support
- @Crown1 reported that upgrading from Free to Starter didn’t appear possible (only Pro showed up), raising concerns about forced trials and plan visibility (#hosted-support #free-plan). The thread includes comparison screenshots and hints of potential A/B testing, with staff investigating and attempting a quick fix. [read more](https://meta.discourse.org/t/-/403167/1?silent=true)
Relevant posts: [plan option discrepancy](https://meta.discourse.org/t/-/403167/2?silent=true), [staff diagnosis questions](https://meta.discourse.org/t/-/403167/7?silent=true), [attempted fix + follow-up](https://meta.discourse.org/t/-/403167/12?silent=true)
- @Eviepayne asked for a _declarative_ way to persist `set_real_ip_from` / `real_ip_header X-Forwarded-For` inside Discourse’s container Nginx when running behind HAProxy, after seeing client IPs collapse to the load balancer and triggering 429s (#unsupported-install #nginx). The discussion distinguishes host-vs-container nginx concerns and lands on using `replace` in `app.yml` to survive rebuilds. [read more](https://meta.discourse.org/t/-/403181/1?silent=true)
Key context: [why the load balancer IP caused trouble](https://meta.discourse.org/t/-/403181/5?silent=true), [suggested `replace` injection snippet](https://meta.discourse.org/t/-/403181/6?silent=true)
- In a permissions/regression-style support question, a user reported they _can’t delete topics anymore_ and is awaiting a fix; @Prempavee closed with appreciation while waiting. [read more](https://meta.discourse.org/t/-/403151/12?silent=true)
### #bug
- @TroLLoBlogger documented a crash after attempting to update via the admin UI, then recovered by rebuilding from the terminal (`./launcher rebuild app`). The error log points to a plugin asset compilation timeout, and the thread pivots into practical guidance on update workflow and resource constraints. [read more](https://meta.discourse.org/t/-/403196/1?silent=true)
Notable replies: @Lilly on avoiding admin-UI updates for self-hosting [read more](https://meta.discourse.org/t/-/403196/2?silent=true), and @Falco requesting server specs to understand the 120s build timeout [read more](https://meta.discourse.org/t/-/403196/3?silent=true)
- In an older-but-still-active bug report, @Moin pointed to a fix PR for the “Thanks for Contributing” popup still appearing after the intended limit had been passed. [read more](https://meta.discourse.org/t/-/373048/23?silent=true)
### #ux
- @sniper756 reported that, on mobile browsers, the admin tag-group management page renders incorrectly (noted alongside “Modernize Foundation theme”), with a screenshot showing layout issues. [read more](https://meta.discourse.org/t/-/403180/1?silent=true)
### #community-building Building
- A discussion on using Discourse for small town government sites focused less on software capability and more on _institutional realities_: moderation ownership, what counts as “official,” authentication, security, and user expectations. @Ethsim2 emphasized that the human/process side is the hard part [read more](https://meta.discourse.org/t/-/403146/2?silent=true), while @NateDhaliwal highlighted privacy implications—whoever hosts has “absolute access.” [read more](https://meta.discourse.org/t/-/403146/3?silent=true)
### #Support (site setting behavior & governance)
- @Ethsim2 proposed clearer behavior for `/about` group listings when “hidden groups” and “extra groups” overlap, including the idea of a boolean site setting like `about_page_exclude_hidden_group_members` to prevent unintended exposure through alternate group sections (#groups #about-page). [read more](https://meta.discourse.org/t/-/403162/4?silent=true)
The back-and-forth covers what each setting actually controls and where group visibility rules apply: [Nate’s interpretation of the two settings](https://meta.discourse.org/t/-/403162/2?silent=true), [Ethsim’s reproduction/edge case](https://meta.discourse.org/t/-/403162/3?silent=true), and the nuance that group interaction settings may still affect `/about` rendering [read more](https://meta.discourse.org/t/-/403162/6?silent=true)
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@mcwumbly** jumped into a heated hosted-pricing/support thread to clarify that Starter has been deprioritized on the pricing page but _should still be available_ from Free upgrades, then began troubleshooting where the upgrade flow was being triggered. See: initial clarification and question [read more](https://meta.discourse.org/t/-/403167/7?silent=true), confirmation it “should” appear and plan to investigate [read more](https://meta.discourse.org/t/-/403167/11?silent=true), an attempted quick fix [read more](https://meta.discourse.org/t/-/403167/12?silent=true), and the final “hang tight” update pending deeper review [read more](https://meta.discourse.org/t/-/403167/15?silent=true).
- **@Falco** investigated a self-host update crash tied to plugin asset compilation timeouts, narrowing suspicion to the plugin build exceeding the two-minute limit and requesting server specs to confirm whether resources were the bottleneck. [read more](https://meta.discourse.org/t/-/403196/3?silent=true)
* * *
_May all your upgrade buttons reveal the plan you actually want—and may every `./launcher rebuild app` finish before the timeout gremlins notice._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [18 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/866 "2026-05-18T21:01:56Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 80**
- **New topics (last 24h): 11**
**Top users by activity (posts) + appreciation (likes)**
- @Lilly — **10 posts** , **16 likes** (e.g. helping debug signup flows in [read more](https://meta.discourse.org/t/-/403198/2?silent=true), and advising on nested replies limitations in [read more](https://meta.discourse.org/t/-/403257/2?silent=true))
- @Falco — **8 posts** , **15 likes** (e.g. investigating update/build constraints in [read more](https://meta.discourse.org/t/-/403196/7?silent=true), and shipping nested-replies fixes via PRs referenced in [read more](https://meta.discourse.org/t/-/403155/6?silent=true))
- @awesomerobot — **3 posts** , **11 likes** (e.g. tightening up reactions UX consistency in [read more](https://meta.discourse.org/t/-/403116/2?silent=true))
- @Thomas_Rother — **1 post** , **7 likes** (sharing a community-building case study in [read more](https://meta.discourse.org/t/-/403219/1?silent=true))
- @TroLLoBlogger — **2 posts** , **6 likes** (sharing swap + resource context for update crashes in [read more](https://meta.discourse.org/t/-/403196/6?silent=true))
- @lindsey — **2 posts** , **6 likes** (announcing recurring-event RSVP improvements in [read more](https://meta.discourse.org/t/-/402827/1?silent=true))
- @greymont — **3 posts** , **4 likes** (closing the loop on a hosted signup/verification confusion in [read more](https://meta.discourse.org/t/-/403198/4?silent=true))
- @david — **1 post** , **4 likes** (clarifying how prebuilt assets are distributed and where plugin builds can bite in [read more](https://meta.discourse.org/t/-/403196/8?silent=true))
- @nat — **2 posts** , **4 likes** (sharing quick updates on bulk-tagging + AI locale detection in [read more](https://meta.discourse.org/t/-/402693/4?silent=true) and [read more](https://meta.discourse.org/t/-/402859/7?silent=true))
- @Richie — **2 posts** , **3 likes** (confirming a theme-component update after a PR merge in [read more](https://meta.discourse.org/t/-/345494/10?silent=true))
> A lot of today’s “hands-on admin reality” clustered around updates + nested replies behavior (see [read more](https://meta.discourse.org/t/-/403196/12?silent=true), [read more](https://meta.discourse.org/t/-/403155/6?silent=true), and [read more](https://meta.discourse.org/t/-/403161/17?silent=true)).
* * *
## Interesting Topics
### #Announcements
- Discourse Events got a usability boost: recurring-event RSVPs now let members choose _“this occurrence only”_ vs _“this and all future occurrences”_, helping organizers interpret attendance and reminders more accurately (#calendar-and-event) — [read more](https://meta.discourse.org/t/-/402827/1?silent=true)
- The Horizon theme now enables “high context” topic cards by default, and feedback immediately surfaced around making that configurability more granular (ideally per-category) (#horizon-theme) — [read more](https://meta.discourse.org/t/-/402843/3?silent=true)
- A request for group notifications for upcoming events resurfaced in the context of the new RSVP workflow (and the historic workaround of group PMs) — [read more](https://meta.discourse.org/t/-/401634/1?silent=true)
- “Upcoming Changes” admin UI got a small-but-useful confirmation: the **Preview** button now appears with the expected filtered URL, helping admins validate which flags they’re previewing (#upcoming-changes) — [read more](https://meta.discourse.org/t/-/392894/28?silent=true)
### #bug
- Self-hosters reported update crashes and rebuild pain, with discussion centering on resource constraints (notably **single vCPU** setups) and how non-core plugins can force asset builds that tip low-resource servers over — [read more](https://meta.discourse.org/t/-/403196/7?silent=true)
- Nested replies continues to shake out: the post-admin wrench actions can fail in nested mode, and the emerging guidance is to switch to flat mode as a workaround while fixes land (#nested-replies) — [read more](https://meta.discourse.org/t/-/403155/1?silent=true)
- Related nested-replies fallout: recovery actions for deleted posts were discussed alongside references to fixes in progress (#nested-replies) — [read more](https://meta.discourse.org/t/-/403161/17?silent=true)
- A report flagged a **TypeError** when submitting certain custom flag flows (“require\_message” flags), and the team invited reproduction details (and even PRs) — [read more](https://meta.discourse.org/t/-/403133/2?silent=true)
- AI plugin link-click behavior was reported as “no response” in a Chinese-language bug report (#ai) — [read more](https://meta.discourse.org/t/-/403201/1?silent=true)
### #Support
- A brand-new hosted admin hit a confusing “Oops! page doesn’t exist or is private” during email verification; the root cause appeared to be testing while still authenticated as admin in another window/session — [read more](https://meta.discourse.org/t/-/403198/4?silent=true)
- “Change Ownership” appeared to do nothing for an admin using nested replies; switching to flat mode resolved it, reinforcing that nested mode is still blocking some post-admin tooling (#nested-replies) — [read more](https://meta.discourse.org/t/-/403257/2?silent=true)
- A moderation best-practices thread asked whether Discourse ships with a default profanity/abuse list; the answer highlighted **Watched Words** as the built-in mechanism, but without a default list (you bring/import your own) — [read more](https://meta.discourse.org/t/-/403261/3?silent=true)
- A UX-writing/editor question: users want an easy “post-number mention” shortcut (e.g. `#123`) to link to a reply without quoting; today’s best workaround remains copying the post link, or implementing custom behavior via theme component — [read more](https://meta.discourse.org/t/-/403237/1?silent=true)
### #contribute:feature
- A feature request proposed adding **Group** selection when bulk converting _Topics → Messages_, enabling a smoother “convert a category into a group inbox” workflow rather than ending up with messages limited to current participants — [read more](https://meta.discourse.org/t/-/403267/1?silent=true)
- A smaller admin-cleanup request asked for auto-purging silenced spam accounts with no posts after X days; discussion pointed back to existing cleanup tools and the “delete and block” spam flow — [read more](https://meta.discourse.org/t/-/403208/4?silent=true)
### #customization:theme component
- “Normalized Profile Links” got maintenance love: @Lilly’s PR fixed array deprecations and was merged, with confirmations that updates worked cleanly on live sites — [read more](https://meta.discourse.org/t/-/345494/8?silent=true)
- “Quote Callouts” received a CSS fix for `` styling in callout titles (alignment/visual consistency, especially noticeable with certain fonts and CJK text sizing) — [read more](https://meta.discourse.org/t/-/350962/70?silent=true)
### #Self-hosting
- A self-host admin lockout scenario: disabling Discourse ID before establishing local admin access can leave “no login methods configured”; recovery guidance centered around creating an admin via Rails (`rake admin:create`) — [read more](https://meta.discourse.org/t/-/403202/3?silent=true)
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @lindsey shipped an Events quality-of-life improvement: recurring RSVPs now distinguish between “next occurrence only” and “all future occurrences,” reducing reminder noise and clarifying attendance for organizers (#calendar-and-event) — [read more](https://meta.discourse.org/t/-/402827/1?silent=true). She also pointed older support threads to the new behavior to close the loop (see follow-up linking in [read more](https://meta.discourse.org/t/-/335780/17?silent=true)).
- @Falco spent time in the trenches on nested replies + admin tooling: clarifying expected behavior boundaries and pointing bug reports into the right funnel in [read more](https://meta.discourse.org/t/-/403155/4?silent=true), then linking an in-flight fix for wrench-action failures in [read more](https://meta.discourse.org/t/-/403155/6?silent=true). He also referenced a fix for deleted-post recovery issues in [read more](https://meta.discourse.org/t/-/403161/17?silent=true), and helped diagnose low-resource update failures in [read more](https://meta.discourse.org/t/-/403196/7?silent=true).
- @david weighed in on update crash analysis, clarifying how **prebuilt assets** should be pulled even during web-based updates, and narrowing the likely culprit to non-core plugin asset build time rather than core itself — [read more](https://meta.discourse.org/t/-/403196/8?silent=true).
- @awesomerobot pushed forward on UX consistency: agreeing that the “More…” emoji trigger should be consistent when allowing any emoji for reactions (#reactions) and working on a fix — [read more](https://meta.discourse.org/t/-/403116/2?silent=true). He also recommended the “delete and block” spam flow as best practice while discussing account noise cleanup — [read more](https://meta.discourse.org/t/-/403208/4?silent=true) — and incorporated feedback into solved-status counting behavior — [read more](https://meta.discourse.org/t/-/402498/27?silent=true).
- @nat provided two quick “this is landing” style updates: noting a returning capability around bulk-tagging management — [read more](https://meta.discourse.org/t/-/402693/4?silent=true) — and confirming that the default AI locale detection agent now includes better language-code handling for Norwegian/Greek (#ai) — [read more](https://meta.discourse.org/t/-/402859/7?silent=true).
- @HAWK expanded on moderation tooling: confirming there is **no default blocked-word list** , but detailing the breadth of **Watched Words** actions (block/require approval/flag/censor/etc.) and import/export capabilities — [read more](https://meta.discourse.org/t/-/403261/3?silent=true). He also reassured Enterprise users that calendar/events work is active and video conferencing is on the roadmap — [read more](https://meta.discourse.org/t/-/402716/16?silent=true).
- @featheredtoast responded to concerns about the `discourse/discourse` Docker image update cadence, explaining a slowdown was an unintended ESR-branch side effect and would be corrected — [read more](https://meta.discourse.org/t/-/380646/29?silent=true).
- @sam acknowledged a bug report around a flag-submission TypeError and invited more info (and potential community PRs) — [read more](https://meta.discourse.org/t/-/403133/2?silent=true).
* * *
Yesterday’s vibes: if your recurring RSVPs are finally behaving _and_ your 1vCPU server survived an update cycle, you’ve basically cleared Discourse hard mode.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [19 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/867 "2026-05-19T21:01:50Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
In the last 24 hours (2026-05-18 → 2026-05-19), Meta saw **87 new posts** spread across **16 new topics** , including multiple product announcements like **starring AI conversations** ([read more](https://meta.discourse.org/t/-/403285/1?silent=true)) and a **docked composer for AI bot chats** ([read more](https://meta.discourse.org/t/-/403327/1?silent=true)), plus an **intermediate security release** ([read more](https://meta.discourse.org/t/-/403279/1?silent=true)).
### Top users (posts + likes in the last 24h)
| User | Posts | Likes | Recent activity (linked) |
| --- | --- | --- | --- |
| @sam | 1 | 15 | Shipped **starred AI conversations** (#ai) ([read more](https://meta.discourse.org/t/-/403285/1?silent=true)) |
| @Lilly | 7 | 11 | Dug into **Horizon Theme mobile layout quirks** ([read more](https://meta.discourse.org/t/-/360486/82?silent=true)) and advised on **redundant-container backups** ([read more](https://meta.discourse.org/t/-/14855/142?silent=true)) |
| @keegan | 1 | 9 | Announced **AI bot docked composer** (#ai-bot) ([read more](https://meta.discourse.org/t/-/403327/1?silent=true)) |
| @Falco | 3 | 8 | Pointed to nested reply read-state linkage in a **mobile 404 report** ([read more](https://meta.discourse.org/t/-/403277/2?silent=true)) and shared new splash SVG results ([read more](https://meta.discourse.org/t/-/395100/32?silent=true)) |
| @david | 1 | 7 | Posted **May 19 intermediate releases** (#release-notes) ([read more](https://meta.discourse.org/t/-/403279/1?silent=true)) |
| @Danielle | 1 | 5 | Published **Office Hours replay** for MCP + [Data Explorer](https://meta.discourse.org/t/32566?silent=true) ([read more](https://meta.discourse.org/t/-/403330/1?silent=true)) |
| @awesomerobot | 3 | 5 | Confirmed you can customize the **“Me too”** string ([read more](https://meta.discourse.org/t/-/402498/30?silent=true)) and improved **new-site feature popups** ([read more](https://meta.discourse.org/t/-/402999/2?silent=true)) |
| @chapoi | 1 | 5 | Introduced **FormKit checkbox redesign** upcoming change ([read more](https://meta.discourse.org/t/-/403284/1?silent=true)) |
| @Ethsim2 | 8 | 4 | Helped troubleshoot **phpBB import slowness / Redis timeouts** ([read more](https://meta.discourse.org/t/-/403319/6?silent=true)) and **PG18 backup failures** ([read more](https://meta.discourse.org/t/-/403289/2?silent=true)) |
| @Architect | 1 | 3 | Shared progress on adopting Discourse for **small-town government** ([read more](https://meta.discourse.org/t/-/403146/4?silent=true)) |
* * *
## Interesting Topics
### #Announcements
- @sam announced a quality-of-life improvement for Discourse AI: you can now **star common AI bot conversations** so they remain pinned at the top of your chat list (toggle coming under upcoming changes) — a small tweak aimed at making AI chats feel more “messaging-like.” ([read more](https://meta.discourse.org/t/-/403285/1?silent=true))
- @keegan unveiled a new **docked composer** for #ai #ai-bot conversations, keeping the input persistently available at the bottom of the topic so you don’t have to click **Reply** for every turn in a back-and-forth chat. ([read more](https://meta.discourse.org/t/-/403327/1?silent=true))
- @david posted **May 19th 2026 intermediate releases** , pointing admins to critical/security update streams and changelogs for multiple supported lines. ([read more](https://meta.discourse.org/t/-/403279/1?silent=true))
- Follow-up on **Solved improvements (“Me too” for reported issues)**: admins asked whether the “Me too (%{count})” text is customizable, and @awesomerobot confirmed it’s safe to change via site text. ([read more](https://meta.discourse.org/t/-/402498/28?silent=true), [read more](https://meta.discourse.org/t/-/402498/30?silent=true))
- The Events team published an **Office Hours replay** featuring a deep dive on **MCP + [Data Explorer](https://meta.discourse.org/t/32566?silent=true)**, demonstrating how AI assistants can generate queries and translate community analytics into natural language workflows. ([read more](https://meta.discourse.org/t/-/403330/1?silent=true))
### #ux
- @chapoi introduced an upcoming-change flag for a **Form checkbox redesign** (FormKit), visually hiding the native checkbox while preserving functionality and enabling smoother styling/animation. ([read more](https://meta.discourse.org/t/-/403284/1?silent=true))
- “Where did the tag info button go?” got an official answer: it was removed after adding a dedicated tag settings page, and @awesomerobot opened a PR to **bring it back** with a refreshed banner aligned to category banner styles. ([read more](https://meta.discourse.org/t/-/402436/7?silent=true))
### #customization:theme / #Theme\_component
- The official **Horizon Theme** thread saw renewed attention on small-screen ergonomics: users reported odd “suggested threads” rendering on mobile emulation and raised concerns that the pinned category/tag navigation consumes too much vertical space; @Lilly traced the behavior to `navigation-container` and suggested CSS workarounds for button/text layout. ([read more](https://meta.discourse.org/t/-/360486/81?silent=true), [read more](https://meta.discourse.org/t/-/360486/86?silent=true), [read more](https://meta.discourse.org/t/-/360486/89?silent=true))
- **Discourse Mermaid** users asked about the cadence for updating the underlying mermaid.js library (specifically to reach newer chart types like Wardley Mapping), and @Falco encouraged contributors to submit a PR. ([read more](https://meta.discourse.org/t/-/218242/53?silent=true), [read more](https://meta.discourse.org/t/-/218242/54?silent=true))
### #support:migration
- A large **phpBB → Discourse migration** prompted performance troubleshooting: the importer was running ~440–450 items/min while CPU stayed low, with Redis timeouts and skipped posts appearing in logs; discussion focused on I/O/DB bottlenecks, Redis diagnostics, and the tradeoffs of bulk importers. ([read more](https://meta.discourse.org/t/-/403319/1?silent=true), [read more](https://meta.discourse.org/t/-/403319/6?silent=true), [read more](https://meta.discourse.org/t/-/403319/7?silent=true))
### #Support
- A self-hosting admin reported that **backups fail with PostgreSQL 18** due to a `pg_dump` client/server version mismatch (container has pg\_dump 15.x vs server 18.3), raising the practical question of whether to align Postgres versions, upgrade the client, or segregate DB clusters. ([read more](https://meta.discourse.org/t/-/403289/1?silent=true), [read more](https://meta.discourse.org/t/-/403289/2?silent=true), [read more](https://meta.discourse.org/t/-/403289/6?silent=true))
- A report of **Internal Server Error when approving new users** (with OAuth2 auth) focused on where to look first: `/logs`, browser console, and approval workflow diagnostics. ([read more](https://meta.discourse.org/t/-/403296/1?silent=true), [read more](https://meta.discourse.org/t/-/403296/2?silent=true))
### #bug
- A tricky bug hunt continued for a **TypeError when submitting “require message” flags** , where `postActionFor` can return `undefined` in certain “nested replies” situations; repro steps narrowed in on flagging in nested mode and then selecting another notify-type reason. ([read more](https://meta.discourse.org/t/-/403133/5?silent=true), [read more](https://meta.discourse.org/t/-/403133/6?silent=true), [read more](https://meta.discourse.org/t/-/403133/4?silent=true))
- A mobile-only issue reported a **404 at the bottom of a nested replies testing topic** , suspected to relate to recent nested read-state behavior; additional context connected to broader “topic list state / old topics showing” weirdness. ([read more](https://meta.discourse.org/t/-/403277/1?silent=true), [read more](https://meta.discourse.org/t/-/403277/2?silent=true), [read more](https://meta.discourse.org/t/-/400459/9?silent=true))
- Voting UI regression watch: users can’t **view who voted on a closed topic** when topic voting is enabled, with both the UI and API returning empty voter lists—raising concern that an older bug may have resurfaced. ([read more](https://meta.discourse.org/t/-/403286/1?silent=true))
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @sam shipped **Star common AI conversations** to keep frequently used bot chats surfaced (#Announcements, #ai) ([read more](https://meta.discourse.org/t/-/403285/1?silent=true)).
- @keegan announced the **docked composer for AI bot conversations** , now available behind an upcoming-changes flag (#Announcements, #ai-bot) ([read more](https://meta.discourse.org/t/-/403327/1?silent=true)).
- @david published **May 19th 2026 intermediate releases** with pointers to the official changelog streams (#Announcements, #release-notes) ([read more](https://meta.discourse.org/t/-/403279/1?silent=true)).
- @Danielle posted the **Office Hours replay** : a guided walkthrough of **MCP + [Data Explorer](https://meta.discourse.org/t/32566?silent=true)** and how AI can assist with community analytics workflows (#events) ([read more](https://meta.discourse.org/t/-/403330/1?silent=true)).
- @chapoi introduced an upcoming-change flag for the **Form checkbox redesign** (#ux) ([read more](https://meta.discourse.org/t/-/403284/1?silent=true)).
- @awesomerobot confirmed **site text customization for “Me too”** in Solved’s reported-issue UX (#Announcements, #solved) ([read more](https://meta.discourse.org/t/-/402498/30?silent=true)), noted that brand new sites won’t be spammed by historical **“New features available!”** notices (#contribute:feature) ([read more](https://meta.discourse.org/t/-/402999/2?silent=true)), and opened work to restore the **tag info button** UX (#ux) ([read more](https://meta.discourse.org/t/-/402436/7?silent=true)).
- @Falco connected a **mobile nested-replies 404** report to recent nested read-state changes (#bug, #nested-replies) ([read more](https://meta.discourse.org/t/-/403277/2?silent=true)), encouraged contributions to **Discourse Mermaid** update cadence (#Theme\_component) ([read more](https://meta.discourse.org/t/-/218242/54?silent=true)), and shared improved custom SVG splash examples (#Announcements, #splash) ([read more](https://meta.discourse.org/t/-/395100/32?silent=true)).
- @mae shared that Discourse was **submitted to the Digital Public Goods Alliance registry** (a step toward broader public-interest adoption) (#General) ([read more](https://meta.discourse.org/t/-/403061/3?silent=true)).
- @nat merged a fix after adding specs for a **language-code-related bug** , thanking the contributor for the PR (#bug, #translation) ([read more](https://meta.discourse.org/t/-/402544/6?silent=true)).
- @isaac marked updates to **@patch-triage** , enabling review/rebase/commit requests and improving fork behavior (#development) ([read more](https://meta.discourse.org/t/-/402898/8?silent=true)).
* * *
Yesterday’s theme was unmistakable: Meta got a bit more “chatty,” with AI conversations now star-able and the bot composer docking itself like it owns the place.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [20 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/868 "2026-05-20T21:01:57Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
In the last 24 hours, meta saw **63 new posts** across **16 new topics** —with conversations spanning everything from _open web values_ to _chat quirks_ and _migration performance_. Activity clustered around threads like the #blog post on staying browser-first ([read more](https://meta.discourse.org/t/-/403381/1?silent=true)), the #support:migration importer tuning discussion ([read more](https://meta.discourse.org/t/-/403319/8?silent=true)), and a handful of fresh #bug / #ux reports (e.g. [read more](https://meta.discourse.org/t/-/403420/1?silent=true), [read more](https://meta.discourse.org/t/-/403423/1?silent=true)).
**Top users (posts / likes)**
- **@ducks** — 1 post / 12 likes ([read more](https://meta.discourse.org/t/-/403381/1?silent=true))
- **@NateDhaliwal** — 5 posts / 10 likes (e.g. [read more](https://meta.discourse.org/t/-/403374/3?silent=true), [read more](https://meta.discourse.org/t/-/403413/2?silent=true))
- **@cocococosti** — 1 post / 6 likes ([read more](https://meta.discourse.org/t/-/403319/8?silent=true))
- **@martin** — 1 post / 4 likes ([read more](https://meta.discourse.org/t/-/401309/5?silent=true))
- **@EricGT** — 1 post / 4 likes ([read more](https://meta.discourse.org/t/-/402498/32?silent=true))
- **@angus** — 2 posts / 3 likes ([read more](https://meta.discourse.org/t/-/403297/2?silent=true))
- **@RGJ** — 2 posts / 3 likes ([read more](https://meta.discourse.org/t/-/403423/1?silent=true), [read more](https://meta.discourse.org/t/-/403296/4?silent=true))
- **@Richie** — 2 posts / 3 likes ([read more](https://meta.discourse.org/t/-/403413/1?silent=true))
- **@davidb** — 1 post / 3 likes ([read more](https://meta.discourse.org/t/-/403390/1?silent=true))
- **@merefield** — 2 posts / 2 likes ([read more](https://meta.discourse.org/t/-/347110/23?silent=true))
* * *
## Interesting Topics
### #blog
- @ducks argued that **Discourse won’t force mobile users into an app** , positioning Discourse as explicitly _pro–open web_ in contrast to app-first lock-in trends ([read more](https://meta.discourse.org/t/-/403381/1?silent=true)). @NateDhaliwal also flagged a housekeeping detail about the topic author attribution ([read more](https://meta.discourse.org/t/-/403381/2?silent=true)).
### #support:migration (#phpbb)
- A deep-dive on speeding up **phpBB → Discourse imports** focused on database I/O bottlenecks, with @cocococosti recommending pragmatic tactics like adding indexes/views and tuning DB settings—and teasing “new tooling” aimed at dramatically faster migrations ([read more](https://meta.discourse.org/t/-/403319/8?silent=true)). The thread also includes real-world importer failure logs from an ongoing run, useful for diagnosing repeatable edge cases ([read more](https://meta.discourse.org/t/-/403319/9?silent=true)).
### #ux
- @Richie requested small consistency tweaks for the expanded search UI—specifically the **casing of dropdown options** and removing an unnecessary ellipsis—while @NateDhaliwal noted that lower-case options read better in-sentence (“Where topics are closed…”) and agreed the other dropdown likely needs standardizing ([read more](https://meta.discourse.org/t/-/403413/1?silent=true), [read more](https://meta.discourse.org/t/-/403413/2?silent=true), [read more](https://meta.discourse.org/t/-/403413/4?silent=true)).
- @RGJ spotted an auditability gap: **restoring (undeleting) a post does not create a staff action log entry**, unlike deleting/restoring topics—making it harder to see who restored content without digging into system logs ([read more](https://meta.discourse.org/t/-/403423/1?silent=true)).
### #Announcements
- Building on the Events + Calendar work, @martin explored whether Discourse could **auto-enable an upcoming-events sidebar block** when the “right sidebar blocks” component is present, and @nathank proposed a more unified Events category view combining _calendar-style “upcoming” visibility_ with a topic list ([read more](https://meta.discourse.org/t/-/401309/5?silent=true), [read more](https://meta.discourse.org/t/-/401309/6?silent=true)).
- In the “Me Too” + Solved improvements thread, @EricGT suggested making “Me Too in closed topics” a **customization option** , and floated an approach where “Me Too” on a closed issue could prompt creation of a new topic after AI checks for duplicates ([read more](https://meta.discourse.org/t/-/402498/32?silent=true)). The discussion also branched into whether the button should appear in deleted/closed contexts, referencing a related layout thread ([read more](https://meta.discourse.org/t/-/403333/1?silent=true)).
- @davidb announced an opt-in layout tweak for sites using Discourse Reactions: **moving reply count to the right** to keep reactions alignment consistent, enabled via upcoming changes as `Enable new post reply count position` ([read more](https://meta.discourse.org/t/-/403390/1?silent=true)).
### #wordpress
- For WooCommerce + [WP Discourse](https://github.com/discourse/wp-discourse) setups, @angus clarified that **usernames don’t need to remain in sync** : [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) maps accounts via `external_id` (WP user id), not the WordPress username—so letting users change their Discourse username shouldn’t break SSO matching ([read more](https://meta.discourse.org/t/-/403297/2?silent=true)).
- A WordPress embed SEO issue: older embedded topics were missing **x-robots noindex and canonical tags** , and @angus narrowed it to missing `topic_embed` records required for canonical-url-for-embeds—while @Thiago_Mobilon argued for a more robust category-level “noindex all topics” checkbox to avoid reliance on embed records ([read more](https://meta.discourse.org/t/-/403109/6?silent=true), [read more](https://meta.discourse.org/t/-/403109/7?silent=true)).
### #Support
- A site admin asked how to **export all site data** (not just a personal archive). @NateDhaliwal pointed them toward **Admin → Backups** for a full instance backup suitable for upgrades and server moves ([read more](https://meta.discourse.org/t/-/403374/1?silent=true), [read more](https://meta.discourse.org/t/-/403374/3?silent=true)).
- A theme-component update attempt hit `about.json does not exist` during import; responders suspected **ZIP structure issues** (parent directory nesting differences across OS zip tools). @Moin demonstrated that re-zipping with the right folder structure fixed installation ([read more](https://meta.discourse.org/t/-/403447/1?silent=true), [read more](https://meta.discourse.org/t/-/403447/2?silent=true)).
- Postgres tooling friction surfaced again: a self-host reported **backups failing with Postgres 18** , prompting advice to install matching postgres client packages inside the container and then persist that setup via `app.yml` rebuild hooks—plus a pointer to prior related discussions about upgrading the postgres client ([read more](https://meta.discourse.org/t/-/403289/7?silent=true), [read more](https://meta.discourse.org/t/-/403289/9?silent=true), [read more](https://meta.discourse.org/t/-/215063/1?silent=true)).
- A small but impactful paper-cut: the “update available” email included a **broken release-notes link** due to a missing `v` prefix in the changelog URL ([read more](https://meta.discourse.org/t/-/403389/1?silent=true)).
- Pricing anxiety continued: a user tracked visible shifts on the Discourse pricing page and reported previously-available features now appearing **“Upgrade to unlock”** on a recently created community, connecting their concerns to earlier free-plan beta discussion and a “no starter option” thread ([read more](https://meta.discourse.org/t/-/403393/1?silent=true), [read more](https://meta.discourse.org/t/-/395632/14?silent=true), [read more](https://meta.discourse.org/t/-/403167/8?silent=true)).
### #bug
- @Moin reported a **Unicode edge case in emoji autocomplete** (notably with `ü`) where selection via “more” fails to replace typed text; in chat it escalates into a console error (`emojiTermStart` null) and broken selection behavior ([read more](https://meta.discourse.org/t/-/403420/1?silent=true)). The report also cross-referenced an older “revision despite grace period” observation triggered while reproducing ([read more](https://meta.discourse.org/t/-/396501/5?silent=true)).
- Starred chat UX bug: @Shauny described how the Chat “Back” button **forgets you were in Starred** , always returning to Channels/DMs, undermining the time-saving intent of starring channels—and pointed to the original “star your favorite chat channels” feature announcement for context ([read more](https://meta.discourse.org/t/-/403431/1?silent=true), [read more](https://meta.discourse.org/t/-/390713/1?silent=true)).
- A #tag-icons regression hunt: @AquaL1te noticed tag icons rendering inconsistently (sidebar OK, topics not), and @Lilly hypothesized an underscore-vs-dash slug mismatch introduced by a component change—suggesting updating slugs in config rather than renaming tags ([read more](https://meta.discourse.org/t/-/403428/1?silent=true), [read more](https://meta.discourse.org/t/-/403428/4?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @ducks published the day’s headline #blog thread asserting Discourse’s browser-first stance: **“Discourse Will Never Block You From the Web”** ([read more](https://meta.discourse.org/t/-/403381/1?silent=true)).
- @cocococosti advised on accelerating phpBB imports by targeting the typical bottleneck— **database I/O** —and recommended indexing/views/tuning to make repeated imports less painful, while hinting at upcoming faster migration tooling ([read more](https://meta.discourse.org/t/-/403319/8?silent=true)).
- @martin chimed in on Events category creation UX, noting a potentially valuable integration point with right-sidebar blocks and proposing investigation into enabling an events block when the relevant component is installed ([read more](https://meta.discourse.org/t/-/401309/5?silent=true)).
- @davidb announced an upcoming change for sites using Reactions: an opt-in **reply-count position adjustment** to improve alignment consistency, enabled via the upcoming-changes UI ([read more](https://meta.discourse.org/t/-/403390/1?silent=true)).
- @markvanlan followed up on a reported 404 at the bottom of a nested replies testing page, noting they **couldn’t reproduce** at the time but would keep an eye out for recurrence ([read more](https://meta.discourse.org/t/-/403277/4?silent=true)).
* * *
Yesterday’s energy was all about _staying on the open web_—even as folks simultaneously shipped new UI polish and dreamed up native app experiences—so however you’re browsing today, at least you’ve got options.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [21 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/869 "2026-05-21T21:01:30Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
**In the last 24 hours (2026-05-20 → 2026-05-21):**
- **New posts:** 67
- **New topics:** 9
**Top contributors (posts / likes received in the last 24h):**
| User | Posts | Likes |
| --- | --- | --- |
| @saquetim | 1 | 12 |
| @zogstrip | 6 | 7 |
| @Lilly | 5 | 6 |
| @NateDhaliwal | 3 | 5 |
| @Tris20 | 1 | 5 |
| @kairo162 | 3 | 4 |
| @pfaffman | 1 | 3 |
| @david | 1 | 3 |
| @HAWK | 3 | 3 |
| @Crown1 | 3 | 3 |
> Biggest “headline” drop: a new **reading-first “simple mode” for Doc Categories** landed as an announcement — [read more](https://meta.discourse.org/t/-/403366/1?silent=true)
* * *
## Interesting Topics
### #Announcements
- **A new “simple mode” for Doc Categories (reading-first docs, replies behind a toggle).** @saquetim introduced a documentation-shaped topic experience in **#Announcements** with #doc-categories, including auto-expanding when linking directly to replies and a simplified “Updated” list column — [read more](https://meta.discourse.org/t/-/403366/1?silent=true) (background: [Discourse Doc Categories plugin](https://meta.discourse.org/t/-/322376/1?silent=true), and a real-world “oops, I missed earlier replies” example: [Backup from command line](https://meta.discourse.org/t/-/64364/37?silent=true))
### #bug
- **iOS PWA nested replies layout gap (username/profile spacing).** @kairo162 reported an odd spacing issue in nested replies on iOS PWA, and @markvanlan said they’ll dig in — [read more](https://meta.discourse.org/t/-/403532/1?silent=true) (team acknowledgment: [read more](https://meta.discourse.org/t/-/403532/4?silent=true); related testing thread: [Nested Replies testing](https://meta.discourse.org/t/-/398759/115?silent=true))
- **Horizon theme header breaks on mid-size/folding-phone viewports (640–767px).** @nathank shared screenshots where the search/avatar vanish at a specific width range, with @Lilly offering a CSS workaround and tying it to viewport-based mode switching — [read more](https://meta.discourse.org/t/-/403484/1?silent=true) (CSS investigation: [read more](https://meta.discourse.org/t/-/403484/2?silent=true); related discussion on mobile/desktop switching: [read more](https://meta.discourse.org/t/-/384280/10?silent=true))
- **Core reactions “+1 hover popover” stuck loading due to URL encoding.** @PortChange traced the issue to `reaction_value=+1` being interpreted as a space, and @zogstrip pointed to a fix; the reporter confirmed it was working quickly after — [read more](https://meta.discourse.org/t/-/403520/1?silent=true) (fix noted: [read more](https://meta.discourse.org/t/-/403520/2?silent=true))
- **Mobile UX: browser back button while reaction list modal is open.** @Canapin reported the reaction list staying open and the page jumping to the footer on Chrome Android; @Moin connected it to earlier reaction-modal work — [read more](https://meta.discourse.org/t/-/403509/1?silent=true) (related earlier posts: [read more](https://meta.discourse.org/t/-/389820/78?silent=true), [read more](https://meta.discourse.org/t/-/389820/81?silent=true))
- **Emoji autocomplete + special characters (e.g., “ü”).** @renato linked a proposed fix PR for emoji autocomplete behavior involving special characters — [read more](https://meta.discourse.org/t/-/403420/3?silent=true)
- **“Users for approval” notification claims approvals exist, but the queue is empty.** @Christian_Bailey confirmed they’re hitting the same “phantom approvals” bug (and that they’re the only admin, ruling out someone else approving) — [read more](https://meta.discourse.org/t/-/262853/15?silent=true)
- **Flagged post restoration is confusing when a “reason given” blocks restore.** @zogstrip credited a community find and pointed to a fix-incoming PR — [read more](https://meta.discourse.org/t/-/401900/3?silent=true)
### #Support
- **Hosted upgrade UX: “Starter” plan not selectable (only Pro shown), partially fixed.** @Crown1 reported that Starter details appeared but couldn’t be selected from some upgrade surfaces; later confirmed “Manage Account” now works, and @rishabh explained the underlying recommendation logic issue (Free/Starter staff-limit parity) and promised a fix — [read more](https://meta.discourse.org/t/-/403167/18?silent=true) (confirmation it worked via Manage Account: [read more](https://meta.discourse.org/t/-/403167/22?silent=true); team follow-up: [read more](https://meta.discourse.org/t/-/403167/23?silent=true))
- **Free plan / pricing structure confusion: category types and missing feature-matrix rows.** @HAWK clarified the Free plan is still new/being tuned, noted transactional-email limits (and an “email in” oversight that got reverted), and agreed feedback about the feature matrix and category-type changes is fair — [read more](https://meta.discourse.org/t/-/403393/3?silent=true) (category type concerns: [read more](https://meta.discourse.org/t/-/403393/4?silent=true); follow-up: [read more](https://meta.discourse.org/t/-/403393/5?silent=true))
- **Backups failing with Postgres 18: solved with package changes.** A backup failure thread ended with a working solution flow (installing/upgrading Postgres packages), plus @pfaffman recommending pinning client packages and moving commands into `app.yml` — [read more](https://meta.discourse.org/t/-/403289/10?silent=true) (follow-up advice: [read more](https://meta.discourse.org/t/-/403289/11?silent=true))
- **View count doesn’t increment on one topic (others are fine).** @Prempavee asked why a single topic isn’t counting views; @NateDhaliwal asked for specifics and suggested testing [safe mode](https://meta.discourse.org/t/53504?silent=true) to rule out theme/component interference — [read more](https://meta.discourse.org/t/-/403522/1?silent=true) (triage questions: [read more](https://meta.discourse.org/t/-/403522/2?silent=true))
### #General
- **A native iOS+Android Discourse client app (preview) and what it needs to work broadly.** In #show-and-tell, @nicolsdennis explained the app isn’t store-published yet, and that some features depend on an accompanying plugin + configuration like `Allowed user API auth redirects` — [read more](https://meta.discourse.org/t/-/403429/1?silent=true) (implementation details: [read more](https://meta.discourse.org/t/-/403429/6?silent=true))
### #customization:plugin
- **Chat UX: floating chat + browser history causing confusion.** @sam confirmed a reported “back button” issue is specific to _floating chat_ mode and argued floating chat shouldn’t participate in page history; @zogstrip noted it should improve once a fix is merged — [read more](https://meta.discourse.org/t/-/403431/2?silent=true) (status update: [read more](https://meta.discourse.org/t/-/403431/4?silent=true))
- **Discourse Automation: can an auto-reply mention the user?** A question in the official automation thread asks whether automated replies can @mention the newly-posting user (useful for “first post” onboarding patterns) — [read more](https://meta.discourse.org/t/-/195773/184?silent=true)
### #customization:theme component
- **Featured Topics component: possible collision with a Pavilion dropdown header.** @TestingRico reported that previewing the Featured Topics component seems to make the Pavilion dropdown header disappear, asking if it’s known and how to keep both working — [read more](https://meta.discourse.org/t/-/217580/61?silent=true) (related component referenced: [pavilion dropdown header](https://meta.discourse.org/t/-/217580/61?silent=true))
### #wordpress
- **WordPress embeds: old embedded topics missing `x-robots: noindex` and canonical tags.** @angus explained canonical URLs should work, but missing embed records imply some external deletion/operation; @Thiago_Mobilon argued category-level indexing control should be native and that republishing isn’t viable at large scale — [read more](https://meta.discourse.org/t/-/403109/8?silent=true) (SEO feature request argument: [read more](https://meta.discourse.org/t/-/403109/9?silent=true))
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@saquetim** shipped an announcement introducing **Doc Categories “simple mode”** (a reading-first docs view with replies one click away) — [read more](https://meta.discourse.org/t/-/403366/1?silent=true)
- **@zogstrip** had a busy bug-fix/status-update day:
- **@david** responded on the folding-device/mobile-mode discussion, noting Discourse design work assumes viewport-based mobile mode remains enabled and that Horizon should be fixed without toggling that setting — [read more](https://meta.discourse.org/t/-/384280/11?silent=true)
- **@HAWK** engaged on hosted-plan expectations and market-fit iteration (Free plan, email constraints, category type changes), and took feedback to raise internally — [read more](https://meta.discourse.org/t/-/403393/3?silent=true) (follow-up: [read more](https://meta.discourse.org/t/-/403393/5?silent=true)); also continued the growth/process conversation in #Enterprise — [read more](https://meta.discourse.org/t/-/402716/18?silent=true)
- **@markvanlan** acknowledged and agreed to investigate the iOS PWA **nested replies spacing** bug report — [read more](https://meta.discourse.org/t/-/403532/4?silent=true)
- **@featheredtoast** updated self-hosters using the official Docker image that the next build should restore expected upgrade behavior (and later confirmed it was back) — [read more](https://meta.discourse.org/t/-/380646/32?silent=true)
- **@sam** clarified the **floating chat** context for a back-button report and suggested floating-mode chat should avoid participating in browser history — [read more](https://meta.discourse.org/t/-/403431/2?silent=true)
- **@rishabh** apologized for the hosted-plan upgrade confusion and explained why Starter was incorrectly skipped by the recommender, promising an update once fixed — [read more](https://meta.discourse.org/t/-/403167/23?silent=true)
- **@renato** linked a fix PR for **emoji autocomplete** issues involving special characters — [read more](https://meta.discourse.org/t/-/403420/3?silent=true)
- **@supermathie** asked for more details on a Chinese-language support post about the review queue (“what reason was given for the flag?”) — [read more](https://meta.discourse.org/t/-/403507/2?silent=true)
* * *
Yesterday’s vibe: between _simple-mode docs_, _folding-phone headers_, and _reaction popovers that don’t like plus signs_, Meta was basically a usability escape room—now with better lighting and fewer hidden toggles.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [22 mei 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/870 "2026-05-22T21:02:28Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 90**
- **New topics (last 24h): 10**
**Top users (posts / likes in the last 24h)**
| User | Posts | Likes | Recent reference |
| --- | --- | --- | --- |
| **@Lilly** | 15 | 15 | Tracked down a Foundation/“Modernize” font-size regression and shared a CSS workaround in [this thread](https://meta.discourse.org/t/-/403614/2?silent=true) |
| **@Moin** | 13 | 9 | Reported and investigated “Approve” failures for users in [Approval button on user’s profile doesn’t work](https://meta.discourse.org/t/-/403620/1?silent=true) |
| **@sniper756** | 7 | 3 | Reported tiny homepage typography after rebuild in [this UX report](https://meta.discourse.org/t/-/403614/1?silent=true) |
| **@darkpixlz** | 4 | 6 | Requested feature parity for action-log notes in nested/threaded view in [this UX topic](https://meta.discourse.org/t/-/403660/1?silent=true) |
| **@Ed_S** | 4 | 3 | Confirmed and escalated the approval/phantom queue issue, linking it to the new report in [this post](https://meta.discourse.org/t/-/262853/19?silent=true) |
| **@awesomerobot** _(team)_ | 3 | 10 | Weighed pros/cons of AI crawler access in [the Agent Ready discussion](https://meta.discourse.org/t/-/403594/5?silent=true) |
| **@supermathie** _(team)_ | 3 | 4 | Diagnosed clipboard-formatting behavior for syntax highlighting in [this debugging reply](https://meta.discourse.org/t/-/403639/7?silent=true) |
| **@Orioni** | 3 | 4 | Added SEO/AI nuance about #llms-txt in [this reply](https://meta.discourse.org/t/-/403594/6?silent=true) |
| **@Tris20** | 1 | 3 | Shared enterprise migration “breaking points” context in [this ongoing enterprise thread](https://meta.discourse.org/t/-/402716/19?silent=true) |
| **@Discourse** | 1 | 6 | Published the “Agent Ready” blog companion topic [here](https://meta.discourse.org/t/-/403594/1?silent=true) |
**Top contributors from the [@team](https://meta.discourse.org/groups/team?silent=true) group (posts / likes)**
- **@awesomerobot** (3 / 10): [read more](https://meta.discourse.org/t/-/403615/2?silent=true)
- **@supermathie** (3 / 4): [read more](https://meta.discourse.org/t/-/403639/9?silent=true)
- **@techAPJ** (1 / 1): [read more](https://meta.discourse.org/t/-/327291/23?silent=true)
**Other active threads that picked up replies (quick link roundup):**
[Phantom approval notifications](https://meta.discourse.org/t/-/262853/16?silent=true), [Doc categories “simple mode” follow-up](https://meta.discourse.org/t/-/403366/3?silent=true), [Tags UI spacing feedback](https://meta.discourse.org/t/-/399588/2?silent=true), [Voting button got smaller](https://meta.discourse.org/t/-/40121/319?silent=true), [Calendar event UX question](https://meta.discourse.org/t/-/97376/579?silent=true), [Docker dev install gotcha (UID 1000)](https://meta.discourse.org/t/-/102009/326?silent=true), [Shortlink Router README/guide](https://meta.discourse.org/t/-/401542/9?silent=true), and an ongoing discussion on [Daily Summary formatting](https://meta.discourse.org/t/-/291853/289?silent=true).
* * *
## Interesting Topics
### #blog
- @Discourse published **“Discourse is Agent Ready”** , sparking a practical debate about whether communities should _welcome or block_ AI crawlers; @awesomerobot framed it as “depends on whether your forum is support vs social,” while others raised GDPR/LGPD and scraping concerns in the companion thread [read more](https://meta.discourse.org/t/-/403594/1?silent=true).
### #bug
- A potentially serious moderation workflow issue emerged: admins report the **“Approve” button on a user profile can fail** , leaving users unapproved yet missing from the review queue; @Moin’s repro and @Ed_S’s “me too” add weight to the report in [Approval button on user’s profile doesn’t work](https://meta.discourse.org/t/-/403620/1?silent=true) (closely related to the “phantom approvals” thread [here](https://meta.discourse.org/t/-/262853/19?silent=true)).
- A copy/paste edge case: syntax highlighting colours **don’t reliably carry over** when copying code blocks into external clients; @supermathie showed that the **codeblock “Copy” button** yields plain text, while selecting rendered HTML can preserve formatting—then the thread narrowed to browser/client behavior differences in [this bug report](https://meta.discourse.org/t/-/403639/1?silent=true).
- Good news on email polish: the “update available” email had a **broken release-notes URL** (missing a `v`), and a fix was prepared and then confirmed merged in [Email with update available has invalid link to release notes](https://meta.discourse.org/t/-/403389/4?silent=true).
- iOS PWA composer UX: when text size is set smaller, the **Reply button can disappear** in the iOS PWA (while Safari works), with a fresh report and screen recordings in [Reply button not visible when composing on iOS PWA](https://meta.discourse.org/t/-/403662/1?silent=true) (noting a possibly related earlier thread [here](https://meta.discourse.org/t/-/322220/1?silent=true)).
### #ux
- Foundation theming regression watch: after a rebuild/update, some sites saw **very small font sizes on category-homepage layouts** , and @Lilly traced it to “Modernize Foundation theme” and offered an SCSS variable fix in [刚才rebuild更新后，首页字体变的很小](https://meta.discourse.org/t/-/403614/1?silent=true) (#foundation-theme).
- Threaded/nested UI parity request: in nested/threaded view, admins can’t easily **add notes to action-log entries** , even though it’s possible in the flat view—feature request and screenshots in [Can’t add note to admin action in threaded view](https://meta.discourse.org/t/-/403660/1?silent=true) (#nested-replies).
- Audit trail completeness: “undeleting a post” apparently **doesn’t create a staff log entry** , and a PR was opened to address the gap in [Undeleting a post does not create a log entry](https://meta.discourse.org/t/-/403423/2?silent=true).
### #Support
- Free-tier clarity: @awesomerobot explained what “minimum activity” means for hosted free sites— **roughly a couple users + a handful of topics in the first ~3 weeks** , with notices at ~3 and ~6 weeks—while confirming the embed setup looked correct in [What is the minimum required activity?](https://meta.discourse.org/t/-/403615/2?silent=true) (#free-plan).
- Mobile navigation oddity (Chinese support): a report suggests iOS Chrome’s back button can behave inconsistently on Meta—sometimes returning to an _older_ page instead of the immediate prior view—in [Chrome浏览器返回键的bug](https://meta.discourse.org/t/-/403608/1?silent=true).
- Moderation conflict-of-interest design question: can **category moderators be prevented from reviewing flags on their own posts** (or routed to full mods/admins only)? The thread explores policy vs. technical enforcement in [Can category moderators be prevented from reviewing flags on their own posts?](https://meta.discourse.org/t/-/403661/1?silent=true) (#moderation #review-queue).
### #Site feedback
- Attribution vs simplification: @Lilly asked for **“simple mode” to be disabled (or contributors restored)** in the #Wiki category, arguing the current presentation can unintentionally erase visible credit for non-staff authors in [this feedback topic](https://meta.discourse.org/t/-/403006/2?silent=true).
- Meta’s own digest mechanics were discussed again in the long-running “daily summary” thread, including how top-user callouts and references get presented in [Daily Summary Feedback](https://meta.discourse.org/t/-/291853/289?silent=true).
### #Announcements
- The nested replies rollout continues to spur customization discussion: one thread revisited how to handle reply-label language/translation tradeoffs, pointing from the nested replies announcement toward a dedicated labels solution in [Introducing nested replies](https://meta.discourse.org/t/-/402812/29?silent=true) (see also the linked labels topic [here](https://meta.discourse.org/t/-/402911/1?silent=true)).
### #customization:plugin
- In #topic-voting, admins reported the familiar **big “Vote” button** has become a **small arrow** that users overlook, prompting requests for UI reversal or customization guidance in [Discourse Topic Voting](https://meta.discourse.org/t/-/40121/319?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@awesomerobot** engaged in the “agent-ready” discussion, outlining when AI visibility might be a net positive (support/answers) versus harmful (social community goals) in [this reply](https://meta.discourse.org/t/-/403594/5?silent=true), and also cautioned that blocking scrapers isn’t foolproof if content is public in [this follow-up](https://meta.discourse.org/t/-/403594/8?silent=true).
They also clarified free-tier inactivity expectations and timelines in [the free-plan support thread](https://meta.discourse.org/t/-/403615/2?silent=true).
- **@supermathie** broke down why syntax highlighting colours don’t always paste into other apps—distinguishing the Discourse “copy button” vs selecting rendered HTML—in [this diagnostic post](https://meta.discourse.org/t/-/403639/7?silent=true), adding additional troubleshooting steps in [this follow-up](https://meta.discourse.org/t/-/403639/9?silent=true), and explaining Firefox vs Chromium style-inlining differences in [this technical note](https://meta.discourse.org/t/-/403639/11?silent=true).
- **@techAPJ** confirmed how the “help answer similar questions” PM chooses suggested topics (and how “limit suggested to category” affects it) in [the solved reminders thread](https://meta.discourse.org/t/-/327291/23?silent=true).
* * *
If yesterday’s Meta felt like a mashup of _AI crawler ethics_, _mysteriously tiny fonts_, and _haunted approval queues_, that’s because it absolutely was.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [23 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/871 "2026-05-23T21:01:22Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
In the last 24 hours, Meta saw **36 new posts** across **9 new topics** , with most of the churn concentrated around #bug triage, permission/UX refinement, and a couple of theme-component releases (e.g. [read more](https://meta.discourse.org/t/-/403692/1?silent=true), [read more](https://meta.discourse.org/t/-/403674/1?silent=true), [read more](https://meta.discourse.org/t/-/403702/1?silent=true)).
**Top users (posts / likes in the last 24h):**
| User | Posts | Likes | Recent highlight |
| --- | --- | --- | --- |
| @Ethsim2 | 9 | 2 | Reported a bundled #reactions serializer regression ([read more](https://meta.discourse.org/t/-/403692/1?silent=true)) and tied it back to broader “update all” fallout ([read more](https://meta.discourse.org/t/-/403672/4?silent=true)) |
| @Lilly | 4 | 1 | Pointed out likely incompatibility between #nested-replies and #post-voting ([read more](https://meta.discourse.org/t/-/403696/2?silent=true)) and helped debug missing Like UI ([read more](https://meta.discourse.org/t/-/403674/4?silent=true)) |
| @bird | 3 | 1 | Confirmed Likes were suppressed by Topic Voting and applied a CSS fix ([read more](https://meta.discourse.org/t/-/403674/8?silent=true)) |
| @wenqin | 1 | 4 | Raised cross-cultural/generational UX concerns about reply order discoverability ([read more](https://meta.discourse.org/t/-/403691/1?silent=true)) |
| @mcmcclur | 1 | 3 | Released a KaTeX-based theme component to typeset topic titles ([read more](https://meta.discourse.org/t/-/403702/1?silent=true)) |
| @Ryan_Hyer | 1 | 2 | Reported infinite scroll breakage in the user directory tied to a theme component ([read more](https://meta.discourse.org/t/-/403699/1?silent=true)) |
| @pfaffman | 1 | 1 | Recommended a rebuild after an “update all” incident with missing assets ([read more](https://meta.discourse.org/t/-/403672/5?silent=true)) |
| @dax | 1 | 1 | Clarified Meta usage boundaries and redirected functional testing to [try.discourse.org](http://try.discourse.org) ([read more](https://meta.discourse.org/t/-/403511/8?silent=true)) |
| @Moin | 1 | 1 | Investigated a confusing “approval button” flow involving prior reviewables ([read more](https://meta.discourse.org/t/-/403620/5?silent=true)) |
| @rokejulianlockhart | 1 | 1 | Added Chromium-oriented investigation angles to copy/paste syntax highlighting limitations ([read more](https://meta.discourse.org/t/-/403639/12?silent=true)) |
* * *
## Interesting Topics
### #contribute:feature
- @wenqin shared cross-cultural and generational feedback on **topic reply order** and _discoverability for older users_, suggesting admins should be able to choose a default “newest-first” view while still allowing per-user overrides ([read more](https://meta.discourse.org/t/-/403691/1?silent=true)); @jack222 echoed the friction of landing at the bottom and needing to scroll to understand context ([read more](https://meta.discourse.org/t/-/403691/2?silent=true)).
- @Ethsim2 proposed splitting the broad permission **`delete_all_posts_and_topics_allowed_groups`** into _own-content vs global-content_ capabilities to better support least-privilege role design (especially around deletion footprint vs moderation power) ([read more](https://meta.discourse.org/t/-/403671/1?silent=true)), then dug into how `PostGuardian` checks differ for “seeing deleted posts” vs “seeing deleted post bodies” ([read more](https://meta.discourse.org/t/-/403671/2?silent=true)).
### #ux
- Continuing the permissions thread, @Ethsim2 asked for clearer wording on **“delete removed posts after”** to distinguish the _author-facing removal action_ from _later automatic cleanup_, and to clarify what staff/regular users can see during the window ([read more](https://meta.discourse.org/t/-/403690/1?silent=true)).
### #bug
- After “ **update all** ”, @ice.d hit an intermittent “forum issues” situation that looked like a stale-tab vs rebuilt-asset mismatch; @Falco asked to check `/logs` ([read more](https://meta.discourse.org/t/-/403672/2?silent=true)), @Ethsim2 identified missing Propshaft chunks _and_ connected a separate backend exception to the bundled reactions regression ([read more](https://meta.discourse.org/t/-/403672/4?silent=true)), and @pfaffman advised a command-line rebuild ([read more](https://meta.discourse.org/t/-/403672/5?silent=true)).
- @Ryan_Hyer reported **broken infinite scroll** in the user directory when a specific theme component is enabled, with `loadMore` failing because `this.model` is undefined (tagged #user-card-directory) ([read more](https://meta.discourse.org/t/-/403699/1?silent=true)).
- @cuo_wu found a **500 error** when enabling both #nested-replies and #post-voting, triggering `undefined method 'post_number' for nil` in `NestedReplies::PostTreeSerializer` ([read more](https://meta.discourse.org/t/-/403696/1?silent=true)); @Lilly suggested the two features likely aren’t compatible _yet_, linking to prior nested replies discussion ([read more](https://meta.discourse.org/t/-/402812/27?silent=true)).
- @Ethsim2 reported a **NameError: `ReactionsSerializerHelpers`** during topic load on `2026.5.0-latest.1`, pointing at a bundled #reactions serialization path ([read more](https://meta.discourse.org/t/-/403692/1?silent=true)) and noting they opened a PR to move/load the helper earlier in the chain ([read more](https://meta.discourse.org/t/-/403692/2?silent=true)).
- A longer-running issue about **copy/paste of syntax highlighting** (where destinations that support coloured text still lose the colours) picked up further investigation ideas from @rokejulianlockhart, including looking for relevant Chromium source references ([read more](https://meta.discourse.org/t/-/403639/12?silent=true)).
- The **“Approval button on user’s profile doesn’t work”** thread deepened: @Moin hypothesized the issue may relate to users being reviewed before (and not being reviewable again in the expected way), sharing analysis around `suspect_user` and reviewable states ([read more](https://meta.discourse.org/t/-/403620/5?silent=true)); @Ed_S later found similar evidence and tied it to possible historical ID reuse / deleted-user artifacts ([read more](https://meta.discourse.org/t/-/403620/6?silent=true)), also referencing an older related report ([read more](https://meta.discourse.org/t/-/161720/1?silent=true)).
### #Support
- In a Chinese-language support thread, @bird asked why the **Like button wasn’t visible** ; @supermathie found Likes are suppressed in categories using Topic Voting and linked the canonical explanation from the voting plugin docs ([read more](https://meta.discourse.org/t/-/403674/5?silent=true)). The thread also referenced how to re-enable both Like + Vote ([read more](https://meta.discourse.org/t/-/101252/2?silent=true)) and noted enabling reactions can make a Like-like control appear in voting contexts ([read more](https://meta.discourse.org/t/-/40121/311?silent=true)). @bird ultimately confirmed success via a CSS component workaround ([read more](https://meta.discourse.org/t/-/403674/8?silent=true)).
- A solved report about a **Chrome back-button bug** appears to be language/translation dependent: @NateDhaliwal suspected a translation mismatch (“theme” vs “topic”) ([read more](https://meta.discourse.org/t/-/403608/3?silent=true)), and @jack222 observed the issue disappears when switching UI language to English ([read more](https://meta.discourse.org/t/-/403608/4?silent=true)).
- A moderation-permissions question asked whether **category moderators can be prevented from reviewing flags on their own posts** ; @Ethsim2 reasoned through role trade-offs (TL4 vs category moderator) and emphasized that theme components shouldn’t be treated as security boundaries ([read more](https://meta.discourse.org/t/-/403661/4?silent=true)).
### #customization:theme component
- @mcmcclur published **“KaTeX titles”** , a theme component that typesets math in topic titles using KaTeX (with notes about MathJax conflicts) ([read more](https://meta.discourse.org/t/-/403702/1?silent=true)). The motivation references prior requests for math in titles and the constraints around title formatting ([read more](https://meta.discourse.org/t/-/143762/1?silent=true), [read more](https://meta.discourse.org/t/-/143762/2?silent=true)).
- The long-running **“Discourse Indented Subcategories”** theme component thread saw a post removed by its author, a small but notable moderation/maintenance blip in an actively used sidebar-related component discussion (#sidebar) ([read more](https://meta.discourse.org/t/-/393838/15?silent=true)).
### #customization:plugin
- In the official **Discourse Calendar (and Event)** topic, @nathank noted an idea would make an excellent #Contribute > UX topic, and mentioned it’s timely given a recently implemented edit button on the preview ([read more](https://meta.discourse.org/t/-/97376/580?silent=true)).
### #community-building Building
- A “New community” thread received a firm but constructive reminder from @dax: Meta isn’t for running functional tests or promoting trial sites; use the demo instead, and avoid unsolicited PM outreach for testing workflows ([read more](https://meta.discourse.org/t/-/403511/8?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @supermathie diagnosed why Likes were missing in a Voting-enabled context (Likes are automatically disabled), pointed to the relevant canonical docs, and suggested possible paths forward (CSS workaround / Reactions) in the support thread “[请问一下点赞按钮如何显示](https://meta.discourse.org/t/-/403674/5?silent=true)” ([read more](https://meta.discourse.org/t/-/403674/5?silent=true)).
- @Falco responded to “Bug? forum issues” by directing the reporter to inspect `/logs` as the first step in narrowing down the incident after an update ([read more](https://meta.discourse.org/t/-/403672/2?silent=true)).
- @dax clarified appropriate usage of Meta in “New community,” steering testing to **[try.discourse.org](http://try.discourse.org)** and discouraging direct PMs for test-related outreach ([read more](https://meta.discourse.org/t/-/403511/8?silent=true)).
_That’s all for today—yesterday’s Meta energy was basically “votes ate my likes, nested replies fought post voting, and KaTeX tried to sneak math into titles anyway.”_
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [24 mei 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/872 "2026-05-24T21:02:49Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 37**
Activity clustered around nested replies UX, moderation workflow edge-cases, and admin-quality-of-life requests like logging setting changes (e.g. [read more](https://meta.discourse.org/t/-/403691/8?silent=true), [read more](https://meta.discourse.org/t/-/262853/27?silent=true), [read more](https://meta.discourse.org/t/-/403721/1?silent=true)).
- **New topics (last 24h): 3**
Fresh reports/questions included a docs UX overlap issue ([read more](https://meta.discourse.org/t/-/403721/1?silent=true)), a self-hosting reverse-proxy setup question ([read more](https://meta.discourse.org/t/-/403720/1?silent=true)), and how to disable “invite accepted” notifications ([read more](https://meta.discourse.org/t/-/403724/1?silent=true)).
- **Top posters & most-liked (last 24h):**
## Interesting Topics
### #contribute:feature
- @wenqin gathered cross-cultural feedback on **default reply order** (oldest-first vs newest-first) and the _discoverability_ of jumping around long topics; discussion touched nested replies behavior and the presence/absence of the right-hand timeline ([read more](https://meta.discourse.org/t/-/403691/1?silent=true), [read more](https://meta.discourse.org/t/-/403691/6?silent=true), [read more](https://meta.discourse.org/t/-/403691/9?silent=true)).
### #Announcements
- The rollout discussion for **#nested-replies** continued, with skepticism about whether nesting reduces the “thousands of replies” problem—or simply adds cognitive load—while still welcoming choice ([read more](https://meta.discourse.org/t/-/402812/30?silent=true), plus related testing feedback in [read more](https://meta.discourse.org/t/-/398759/118?silent=true)).
- In **#doc-categories** , “simple mode” sparked UI overlap reports: @Moin noted tags colliding with edit counts and dates, and the comparison to [safe mode](https://meta.discourse.org/t/53504?silent=true) suggested a theme/component interaction or layout regression ([read more](https://meta.discourse.org/t/-/403366/4?silent=true), with a similar overlap symptom noted in [read more](https://meta.discourse.org/t/-/403721/2?silent=true)).
### #blog
- The “Agent Ready” post drew pointed commentary about **regulation, licensing, and copyright enforcement** , with @ted arguing that existing frameworks have already been ignored at scale ([read more](https://meta.discourse.org/t/-/403594/9?silent=true)).
### #ux
- A brand-new report showed the **“pending suggested edit” banner** overlapping the wiki edit-history pencil/date in docs, and also highlighted missing tagging/organization around suggested-edits documentation ([read more](https://meta.discourse.org/t/-/403721/1?silent=true), referencing suggested edits context in [read more](https://meta.discourse.org/t/-/398691/1?silent=true)).
### #bug
- A long-running annoyance resurfaced: notifications claiming **“X users for approval”** when none can be found. @RGJ argued the cause has been clear for years and asked for a fresh team look ([read more](https://meta.discourse.org/t/-/262853/27?silent=true), pointing back to earlier diagnosis in [read more](https://meta.discourse.org/t/-/262853/9?silent=true)).
- Account approvals hit another snag: the **“Approve” button on a user profile** appears non-functional in some cases, with suspicion of malformed `ReviewableUser` records, silent failures, and review queue omissions ([read more](https://meta.discourse.org/t/-/403620/8?silent=true), [read more](https://meta.discourse.org/t/-/403620/9?silent=true)).
### #Support
- A Chinese-language thread investigated an iOS **Chrome back-button** issue that may actually be tied to Chrome’s _page translation_ interfering with Discourse navigation/history state, rather than a theme-specific bug ([read more](https://meta.discourse.org/t/-/403608/7?silent=true), with clarifying questions in [read more](https://meta.discourse.org/t/-/403608/5?silent=true)).
- Admins asked for a way to **turn off “accepted your invitation” notifications** (#invites). The current answer appears to be “not configurable,” with a pointer to an older forgotten request and a workaround via a “dummy inviter” account ([read more](https://meta.discourse.org/t/-/403724/1?silent=true), historic feature request: [read more](https://meta.discourse.org/t/-/150633/1?silent=true)).
- A moderation integrity question: can **category moderators** be prevented from reviewing flags on their _own_ posts (#moderation #category-moderators #review-queue)? @Heliosurge advocated for removing temptation via finer-grained controls or #Customization workarounds, and linked to tooling ideas ([read more](https://meta.discourse.org/t/-/403661/5?silent=true), [read more](https://meta.discourse.org/t/-/403661/6?silent=true), plugin mention: [read more](https://meta.discourse.org/t/-/324765/1?silent=true)).
### #Self-hosting
- A self-hoster asked for **reverse-proxy config guidance when Nginx and Discourse run on separate machines** , including how `proxy_pass` should map compared with the single-box unix-socket examples in the docs ([read more](https://meta.discourse.org/t/-/403720/1?silent=true)).
### #Integrations
- The long-running embedding thread got a fresh question: can you import **Discourse-style comments into a mobile app** “these days”? @Falco noted the embedded comments list is essentially read-only unless you build more around it, and asked for details to guide the approach ([read more](https://meta.discourse.org/t/-/31963/486?silent=true), [read more](https://meta.discourse.org/t/-/31963/487?silent=true)).
### #customization:theme component
- The official **Unformatted Code Detector** (#official #unformatted-code-detector) briefly showed “Error cloning the Git repository,” but it resolved; @Moin suggested GitHub rate limiting as a plausible cause and linked a related “error cloning” discussion ([read more](https://meta.discourse.org/t/-/112773/67?silent=true), [read more](https://meta.discourse.org/t/-/112773/70?silent=true), related: [read more](https://meta.discourse.org/t/-/399003/6?silent=true)).
### #community-building Building
- In a #automation thread about messaging users at scale, @haydenjames and @Moin discussed the pain of **silent setting changes after updates** and the desire for better auditability. A concrete suggestion emerged: log update-driven setting changes in staff logs, and optionally automate admin notifications when settings change ([read more](https://meta.discourse.org/t/-/383691/20?silent=true), proposal: [read more](https://meta.discourse.org/t/-/383705/1?silent=true), notification automation idea: [read more](https://meta.discourse.org/t/-/208961/11?silent=true)).
### #support:migration
- A #phpbb migration story: after completing an import, @Mattash realized passwords weren’t imported and planned a restart—this time pruning low-value posts (“half million jello and count down posts”) to speed things up ([read more](https://meta.discourse.org/t/-/403319/11?silent=true)).
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Falco weighed in on a feature request about **reply order and navigation discoverability** , pointing out the timeline jump behavior and noting nested replies already address some “reply order” goals—but also acknowledging design gaps: the nested-replies timeline was added briefly, deemed lacking, and reverted while the team explores a better approach ([read more](https://meta.discourse.org/t/-/403691/3?silent=true), [read more](https://meta.discourse.org/t/-/403691/9?silent=true), related nested replies testing: [read more](https://meta.discourse.org/t/-/398759/1?silent=true)).
- @Falco answered an integrations question about embedding Discourse comments into a **mobile app** , clarifying current constraints (read-only embed list) and inviting more specifics to tailor guidance ([read more](https://meta.discourse.org/t/-/31963/487?silent=true)).
Yesterday’s theme was clear: if you can’t find what you need, it’s either one click on the timeline—or nested replies temporarily ate the timeline while everyone argues about discoverability.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [25 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/873 "2026-05-25T21:01:40Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 41**
- **New topics (last 24h): 9**
**Top users by recent activity (posts) & appreciation (likes):**
| User | Posts | Likes |
| --- | --- | --- |
| @Moin | 8 | 13 |
| @Lilly | 6 | 11 |
| @Jagster | 3 | 3 |
| @haydenjames | 2 | 2 |
| @dax | 1 | 5 |
| @ToddZ | 1 | 4 |
| @Eviepayne | 1 | 4 |
| @fitzy | 1 | 3 |
| @RGJ | 1 | 2 |
| @manuel | 1 | 2 |
A few threads attracted quick, high-signal replies—like the UX discussion on installing duplicate theme components ([read more](https://meta.discourse.org/t/-/403741/3?silent=true)), and the new theme component to reduce admin notification clutter ([read more](https://meta.discourse.org/t/-/403729/1?silent=true)).
* * *
## Interesting Topics
### #ux
- @Jagster flagged that “Featured components” can look like they’re re-installable even when already present, which feels like it should at least _signal_ “installed”; @dax clarified it’s intentional to allow the same component across multiple themes with different configs, while @Moin dug into inconsistent detection behavior ([read more](https://meta.discourse.org/t/-/403741/1?silent=true)) ([context from @dax](https://meta.discourse.org/t/-/403741/3?silent=true)) ([follow-up from @Moin](https://meta.discourse.org/t/-/403741/4?silent=true))
### #customization:theme component (#TAG: #notifications)
- @Lilly published **“Dismiss Admin Noise!”** , a lightweight theme component to auto-dismiss specific admin-only user-menu notifications; the thread includes install info and even Rails-console snippets to generate test notifications ([read more](https://meta.discourse.org/t/-/403729/1?silent=true)) ([testing tips](https://meta.discourse.org/t/-/403729/3?silent=true)) ([install guide reference](https://meta.discourse.org/t/-/63682/1?silent=true))
### #Marketplace (#TAG: #meta-theme-feedback, #meta-redesign-2026)
- A discussion about whether you can “copy the meta branded theme” turned into a reality-check on brand/design licensing and what commissioning a _similar_ theme might cost; @manuel also pointed folks toward building blocks/components as a practical alternative ([read more](https://meta.discourse.org/t/-/403747/1?silent=true)) ([cost/licensing perspective](https://meta.discourse.org/t/-/403747/3?silent=true)) ([theme skills link](https://meta.discourse.org/t/-/401629/1?silent=true))
### #bug (#TAG: #nested-replies)
- @Moin reported that a Suggested Topics link pointing to a nested-reply post can 404 and leave the UI header in a broken state; console logs show a failing `.json` fetch, and @Falco noted the likely failing branch location in `nested.js` ([read more](https://meta.discourse.org/t/-/403743/1?silent=true)) ([console detail](https://meta.discourse.org/t/-/403743/3?silent=true)) ([team triage note](https://meta.discourse.org/t/-/403743/5?silent=true)) ([referenced nested post](https://meta.discourse.org/t/-/398759/113?silent=true))
### #Support
- A long-running “phantom pending approvals” issue was solved: @PHolder exported users, filtered `approved=false`, and manually approved the stragglers—fixing the persistent “X users awaiting approval” nag; the thread also links prior related reports and workarounds ([read more](https://meta.discourse.org/t/-/403731/1?silent=true)) ([solution steps](https://meta.discourse.org/t/-/403731/3?silent=true)) ([related notification report](https://meta.discourse.org/t/-/262853/21?silent=true)) ([older related bug reference](https://meta.discourse.org/t/-/240731/4?silent=true)) ([additional reference](https://meta.discourse.org/t/-/262853/9?silent=true))
### #Support (#TAG: #invites)
- “Turn off invite accepted notifications?” got a practical answer: @Lilly pointed directly to the new **Dismiss Admin Noise** theme component as a way to cut down that admin dropdown clutter ([read more](https://meta.discourse.org/t/-/403724/3?silent=true)) ([theme component](https://meta.discourse.org/t/-/403729/1?silent=true))
### #Support
- “If local logins are disabled”: a newcomer wrestling with SMTP limits on DigitalOcean explored going social-only; replies covered DO’s SMTP blocking realities and how to disable local logins or use Discourse ID, plus concrete SMTP config examples for common providers ([read more](https://meta.discourse.org/t/-/403735/1?silent=true)) ([disable local logins tip](https://meta.discourse.org/t/-/403735/4?silent=true)) ([Discourse ID explainer](https://meta.discourse.org/t/-/379565/1?silent=true)) ([Mailgun setup reference](https://meta.discourse.org/t/-/40590/1?silent=true))
### #Support (#TAG: #activitypub)
- A feature request asked for a **public** , dynamic list of ActivityPub handles for federated categories (the current list lives behind an admin-only URL), to enable easier linking from external public pages ([read more](https://meta.discourse.org/t/-/403769/1?silent=true))
### #Support (#TAG: #composer)
- @Moin questioned how `educate_until_posts` interacts with recent behavior changes in `check_education_message`, after seeing the “education banner” appear fewer times than expected even with a higher threshold—backed with code references and a reproducible test scenario ([read more](https://meta.discourse.org/t/-/403727/1?silent=true)) ([related prior discussion](https://meta.discourse.org/t/-/373048/24?silent=true))
### #Announcements
- Image optimization discussion continued: a request for broader WebP usage (including PNG conversions/compression) got a candid reply from @Falco about tradeoffs—especially the settings explosion that would be required to keep admin control flexible while shipping sane defaults ([read more](https://meta.discourse.org/t/-/402705/2?silent=true)) ([team response](https://meta.discourse.org/t/-/402705/3?silent=true))
### #support:migration (#TAG: #phpbb)
- In the phpBB migration performance thread, @cocococosti reiterated a crucial point: **passwords aren’t imported** (and generally shouldn’t be), and users should reset passwords post-migration—best communicated proactively to reduce confusion ([read more](https://meta.discourse.org/t/-/403319/12?silent=true))
### #Self-hosting
- A Chinese-language self-hosting thread asked whether others noticed **smaller Docker image sizes after rebuild** (e.g., ~7GB down to ~5GB), likely reflecting recent image/build changes ([read more](https://meta.discourse.org/t/-/403758/1?silent=true))
### #customization:plugin (#TAG: #official, #calendar-and-event, #included-in-core)
- In the long-running Discourse Calendar thread, a missing/changed French translation string surfaced; @Moin suggested contributing upstream via Crowdin so all sites benefit, rather than patching locally ([read more](https://meta.discourse.org/t/-/97376/581?silent=true)) ([translation diagnosis](https://meta.discourse.org/t/-/97376/583?silent=true)) ([translation contribution guide](https://meta.discourse.org/t/-/14882/1?silent=true))
### #Enterprise (#TAG: #enterprise-ready)
- The “community breaking points” conversation added a strategy angle: @HAWK emphasized intentionally supporting _fragmentation into semi-autonomous subgroups_ as communities scale, citing “mitosis” style lifecycle thinking ([read more](https://meta.discourse.org/t/-/402716/21?silent=true))
### #blog
- In the “Agent Ready” blog discussion, @Eviepayne suggested that making **Anubis** a supported captcha would be a strong complement to the broader agent-readiness direction ([read more](https://meta.discourse.org/t/-/403594/10?silent=true))
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @dax weighed in on the UX concern about duplicate theme component installs, explaining the behavior is an **intentional design choice** to support multiple themes/configurations and testing workflows ([read more](https://meta.discourse.org/t/-/403741/3?silent=true)).
- @manuel replied in the marketplace thread about copying Meta’s branded theme, reiterating brand language constraints and pointing people to official learning resources for building similar homepage components ([read more](https://meta.discourse.org/t/-/403747/4?silent=true)) ([skills resource](https://meta.discourse.org/t/-/401629/1?silent=true)).
- @fitzy closed the loop on the Nginx CVE work, confirming completion and pointing to the updated base/default images (via linked PRs) ([read more](https://meta.discourse.org/t/-/403121/6?silent=true)).
- @Falco left two notable technical touchpoints: a quick triage note on the nested-replies link breakage pointing to `nested.js` ([read more](https://meta.discourse.org/t/-/403743/5?silent=true)), and a detailed reply on why broader WebP/compression controls likely need many settings (and why there’s limited appetite internally right now) ([read more](https://meta.discourse.org/t/-/402705/3?silent=true)).
- @HAWK contributed scaling guidance in the enterprise discussion, recommending processes that help large communities split into semi-autonomous groups while retaining shared identity ([read more](https://meta.discourse.org/t/-/402716/21?silent=true)).
- @cocococosti clarified migration best practice: **do not import passwords** during phpBB migrations; plan instead for password resets and set expectations with users ([read more](https://meta.discourse.org/t/-/403319/12?silent=true)).
* * *
_That’s a wrap—may your approvals be real, your nested links not 404, and your admin notifications politely dismiss themselves overnight._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [26 mei 2026 om 21:00 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/874 "2026-05-26T21:00:53Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
**In the last 24 hours (2026-05-25 → 2026-05-26):**
- **New posts:** 77
- **New topics:** 9
- Activity clustered around product changes like **default reactions** ([read more](https://meta.discourse.org/t/-/403795/1?silent=true)) and a steady stream of **bug triage + fixes** (e.g. [nested replies + post voting](https://meta.discourse.org/t/-/403696/3?silent=true), [suggested-topics nested link](https://meta.discourse.org/t/-/403743/6?silent=true), [approval button edge cases](https://meta.discourse.org/t/-/403620/10?silent=true)).
**Top users (posts / likes in the last 24h):**
| User | Posts | Likes |
| --- | --- | --- |
| @martin | 2 | 11 |
| @markvanlan | 4 | 8 |
| @Lilly | 6 | 8 |
| @zogstrip | 3 | 5 |
| @rishabh | 1 | 5 |
| @Falco | 3 | 4 |
| @darkpixlz | 4 | 4 |
| @david | 1 | 4 |
| @Moin | 6 | 4 |
| @Bas | 1 | 3 |
* * *
## Interesting Topics
### #Announcements
- @martin announced an upcoming rollout to **enable Discourse Reactions by default** across new and existing sites, with discussion about how this overlaps (or doesn’t) with “Boosts” and longer-term engagement strategy ([read more](https://meta.discourse.org/t/-/403795/1?silent=true)).
- GitHub Oneboxes got nicer: PR oneboxes now show **live pull request statuses inline** , powered by a core change linked from the announcement thread ([read more](https://meta.discourse.org/t/-/390900/21?silent=true)).
- Feedback continued on the “ **me too** ” button/label in Solved topics—highlighting that the phrase can feel loaded in some communities and pointing out that the label is customizable via Site Text (`shared_issue`) ([read more](https://meta.discourse.org/t/-/402498/34?silent=true)).
### #bug
- A compatibility problem between #nested-replies and #post-voting moved toward a practical fix: make post voting explicitly **incompatible** with nested reply topics (plus related PR links for implementation) ([read more](https://meta.discourse.org/t/-/403696/3?silent=true)).
- The “suggested topics” widget had a **broken link to nested topics** , and a fix PR was shared for the issue ([read more](https://meta.discourse.org/t/-/403743/6?silent=true)).
- A self-host upgrade to 2026.4.1 triggered repeated **“can’t alloc thread”** errors; after diagnostics around ulimit/cgroups/PID ceilings, a CLI rebuild appeared to stabilize things, with follow-up questions about browser upgrade safety checks ([read more](https://meta.discourse.org/t/-/403784/1?silent=true)).
- An ongoing crawler-related exception— **“Document tree depth limit exceeded”** —was reported as resurfacing even after being “fixed twice,” now seen again after upgrading to 2026.4.1 ([read more](https://meta.discourse.org/t/-/403831/1?silent=true)).
- A plugin-side regression/bug: #user-card-directory **infinite scroll** broke with a `loadMore` error, and a fix was applied via a plugin PR ([read more](https://meta.discourse.org/t/-/403699/3?silent=true)).
### #Support
- A self-host email deliverability/config thread dug into DigitalOcean’s blocked SMTP ports and Resend configuration; the “gotcha” turned out to be **curly quotes in YAML** (plus follow-on port guidance and a suggestion to run a diagnostic rake task) ([read more](https://meta.discourse.org/t/-/403735/6?silent=true)).
### #Site feedback
- A UI/UX gripe surfaced: on Meta, **user info appears hidden on wiki posts** due to “simple mode” behavior; discussion pointed back to the “simple mode for docs” rollout and included a userstyle workaround ([read more](https://meta.discourse.org/t/-/403798/1?silent=true)).
### #development
- Mobile/desktop mode behavior moved forward with an important cleanup: **legacy mobile mode has been removed** , referenced directly by commit link in the dev-news thread ([read more](https://meta.discourse.org/t/-/384280/12?silent=true)).
### #contribute:feature
- A request proposed **webhook/event support for Discourse AI artifacts** (key-value updates), with @Falco hinting this may align better once “Workflows” lands as a new automation approach ([read more](https://meta.discourse.org/t/-/403865/1?silent=true)).
### #ux
- A docs usability workaround was shared: when TOC/timeline seems missing in docs, scrolling down to “ **show N comments** ” can re-surface related UI—flagged as a likely side-effect worth checking ([read more](https://meta.discourse.org/t/-/403003/2?silent=true)).
### #Marketplace
- A moderation workflow need hit the Marketplace: a request for a **moderator-friendly “recent replies” view** (last X hours) beyond the review queue—seeking plugin/theme/[Data Explorer](https://meta.discourse.org/t/32566?silent=true) approaches ([read more](https://meta.discourse.org/t/-/403876/1?silent=true)).
### #community-building:praise
- A long-form success story celebrated a **multi-site install** and described replacing Trello workflows (and scaling moderation operations) using Discourse, while testing hardware limits and operational patterns ([read more](https://meta.discourse.org/t/-/403869/1?silent=true)).
### #customization:theme component
- The **MD Topic List Mobile** component was checked against the viewport-switching changes; it still works on latest but now throws a **deprecation warning** about accessing `site.mobileView` / `site.desktopView` during initialization ([read more](https://meta.discourse.org/t/-/146341/68?silent=true)).
### #Integrations
- A renewed discussion about embedding Discourse comments via JavaScript clarified “read-only” vs **full commenting** expectations; a newer guide thread for embedding as a full comment system was recommended as the next stop ([read more](https://meta.discourse.org/t/-/31963/488?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @martin introduced the plan to **enable reactions by default** and answered questions about prioritization and how reactions/likes/boosts might converge in the future ([announcement](https://meta.discourse.org/t/-/403795/1?silent=true), [follow-up](https://meta.discourse.org/t/-/403795/3?silent=true)). Related background: the core Reactions feature thread ([read more](https://meta.discourse.org/t/-/183261/1?silent=true)).
- @rishabh shipped a polish win for developers: **PR status support inside GitHub oneboxes** , linking the implementation PR directly from the announcement thread ([read more](https://meta.discourse.org/t/-/390900/21?silent=true)).
- @david noted a platform simplification: **legacy mobile mode removal** as part of improving automatic switching between mobile/desktop modes ([read more](https://meta.discourse.org/t/-/384280/12?silent=true)).
- @markvanlan drove two separate #nested-replies bugfix efforts: proposing an incompatibility guard for #post-voting when nesting is enabled and sharing the PR, plus posting the fix PR for broken nested-topic links from “suggested topics” ([post voting + nested replies](https://meta.discourse.org/t/-/403696/3?silent=true), [PR link](https://meta.discourse.org/t/-/403696/4?silent=true), [suggested topics fix](https://meta.discourse.org/t/-/403743/6?silent=true)).
- @zogstrip continued a strong run of bugfix PRs: addressing **approval button edge cases** ([read more](https://meta.discourse.org/t/-/403620/10?silent=true)), fixing a “ **users for approval** but none found” notification issue ([read more](https://meta.discourse.org/t/-/262853/28?silent=true)), and confirming an upcoming fix for **topic voting voter visibility on closed topics** ([read more](https://meta.discourse.org/t/-/403286/3?silent=true)).
- @awesomerobot applied a fix for the **infinite scroll `loadMore` error** in the user card directory plugin and asked reporters to confirm after updating ([read more](https://meta.discourse.org/t/-/403699/3?silent=true)).
- @Bas clarified confusion around **billing/pageview-based reporting and migration status** , offering a path for customers who want to switch over ([read more](https://meta.discourse.org/t/-/402288/9?silent=true)).
- @lindsey pointed out that the “ **me too** ” label is configurable via Site Text (`shared_issue`), helping admins adjust terminology to match their communities ([read more](https://meta.discourse.org/t/-/402498/36?silent=true)).
- @Falco responded across multiple threads: aligning AI artifact webhooks with future **Workflows/Automation direction** ([read more](https://meta.discourse.org/t/-/403865/2?silent=true)), linking an alternative PR in the nested replies + post voting investigation ([read more](https://meta.discourse.org/t/-/403696/5?silent=true)), and steering an embedding discussion toward the “full comment system” approach and API alternatives ([read more](https://meta.discourse.org/t/-/31963/489?silent=true), plus the recommended guide: [read more](https://meta.discourse.org/t/-/399743/1?silent=true)).
- @supermathie added a practical troubleshooting step for outbound email failures: run `rake emails:test`, pointing to the canonical “troubleshoot email” how-to ([read more](https://meta.discourse.org/t/-/403735/10?silent=true), background guide: [read more](https://meta.discourse.org/t/-/16326/1?silent=true)).
* * *
Yesterday’s energy in one line: between _curly quotes breaking YAML_, _PIDs hitting limits_, and _reactions getting switched on for everyone_, Meta managed to be both a debugging clinic and a celebration of tiny-but-mighty UX wins.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [27 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/875 "2026-05-27T21:01:49Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 69**
- **New topics (last 24h): 5**
**Top users (posts / likes received in the last 24h):**
| User | Posts | Likes |
| --- | --- | --- |
| @Lilly | 7 | 3 |
| @jdc20181 | 6 | 6 |
| @NateDhaliwal | 6 | 2 |
| @sam | 3 | 3 |
| @pmusaraj | 3 | 2 |
| @david | 2 | 9 |
| @chapoi | 2 | 1 |
| @renato | 1 | 5 |
| @RGJ | 1 | 4 |
| @martin | 1 | 3 |
| @Danielle | 1 | 2 |
**A quick “where the action was” sampling (for source/reference):** discussions ranged from admin/security UX in [email edit controls](https://meta.discourse.org/t/-/403930/1?silent=true), to localization quirks in the [composer typographer](https://meta.discourse.org/t/-/403905/6?silent=true), to self-hosting setup blockers like [Discourse ID registration](https://meta.discourse.org/t/-/403951/1?silent=true), plus ongoing threads on [nested replies vs post voting](https://meta.discourse.org/t/-/403696/8?silent=true), [Reactions default enablement](https://meta.discourse.org/t/-/403795/5?silent=true), and a doc update on [pinning versions via d-compat branches](https://meta.discourse.org/t/-/272665/7?silent=true).
> If you only have five minutes today, scan the “Interesting Topics” section and then peek at the team roundup for official guidance and next steps.
* * *
## Interesting Topics
### #contribute:feature
- @jdc20181 proposed adding finer-grained controls so **admins can edit user emails** even when “Edit email after signup” is disabled—while @Lilly argued the current friction is a _security feature_, eventually converging on the idea of a **sudo/2FA/password-confirm** style guardrail for high-risk actions ([read more](https://meta.discourse.org/t/-/403930/1?silent=true), plus the evolving security angle in [this reply](https://meta.discourse.org/t/-/403930/6?silent=true)).
- In Discourse AI, @sam supported the idea of **server-side webhooks for AI artifact key-value updates** , ideally scoped to an artifact id—positioning it as both automation-enabling _and_ a showcase for artifacts as a storage primitive ([read more](https://meta.discourse.org/t/-/403865/4?silent=true)).
- A follow-up on category-scoped translation landed: after a technical change, Discourse now defaults to translating broadly, and admins should use **`ai_translation_excluded_categories`** to exclude categories; @pmusaraj asked folks to report any migration issues ([read more](https://meta.discourse.org/t/-/392993/7?silent=true)).
- The long-running request to **use translated posts when emailing users** remains on the roadmap; @pmusaraj asked for clarification/screenshots around “custom remarks,” and confirmed there’s no timeline yet ([read more](https://meta.discourse.org/t/-/383546/4?silent=true), and the roadmap note in [this post](https://meta.discourse.org/t/-/383546/6?silent=true)).
### #bug
- A French-language report showed the composer “replacing special characters” (e.g., `j'ai` becoming `j>ai`): @renato identified this as **markdown typographer** behavior and pointed to adjusting `markdown_typographer_quotation_marks` or disabling `enable_markdown_typographer` as immediate mitigation ([read more](https://meta.discourse.org/t/-/403905/6?silent=true), with confirmation in [this follow-up](https://meta.discourse.org/t/-/403905/8?silent=true)).
- In the intersection of #post-voting and #nested-replies, @markvanlan decided to **disable post voting for nested replies** for now, with a future-looking suggestion to build a more native “vote” feature directly into nested replies ([read more](https://meta.discourse.org/t/-/403696/8?silent=true)).
### #Support
- For “Middleware document tree depth exceeded,” @sam noted @Falco had already written a guard and that the fix requires **three commits** , meaning upgrading to the latest release (or waiting for the next monthly) ([read more](https://meta.discourse.org/t/-/403831/2?silent=true)).
- A self-hosting setup went sideways when local logins were disabled and SMTP settings broke the rebuild; @Lilly diagnosed an incorrect `app.yml` and walked through droplet sizing, swap, and quoting pitfalls, while @NateDhaliwal highlighted “smart quotes” breaking config and suggested alternative SMTP ports/hosts ([read more](https://meta.discourse.org/t/-/403735/14?silent=true) and the quoting callout in [this reply](https://meta.discourse.org/t/-/403735/17?silent=true)).
- Discourse on UXP-browser forks (e.g., Pale Moon): @Lilly pointed to Discourse’s supported browser baseline, @NateDhaliwal suggested the “dumbcourse” UI plugin as a workaround, and @david recommended checking the dev console for the failing JS/CSS feature detections ([read more](https://meta.discourse.org/t/-/403890/2?silent=true), workaround pointer [here](https://meta.discourse.org/t/-/403890/4?silent=true), and debugging tip [here](https://meta.discourse.org/t/-/403890/5?silent=true)).
- A new question asked how to **keep registrations disabled** while still allowing private-group invite links for existing users—especially in an SSO-paid-access context ([read more](https://meta.discourse.org/t/-/403941/1?silent=true)).
### #Self-Hosting
- A fresh install hit “Failed to automatically register with Discourse ID” due to a redirect URI HTTPS requirement; the thread quickly moved to checking `/logs`, enabling `force_https`, and using `rake admin:create` from inside the container as a recovery path ([read more](https://meta.discourse.org/t/-/403951/4?silent=true) and the admin-create steps in [this post](https://meta.discourse.org/t/-/403951/7?silent=true)).
- On DiscourseAI sentiment/emotion, a request resurfaced for **connecting sentiment analysis to other LLMs** (with Gemini cited); @Falco replied that support was added “yesterday” and should appear soon ([read more](https://meta.discourse.org/t/-/334451/17?silent=true) and the update in [this reply](https://meta.discourse.org/t/-/334451/18?silent=true)).
### #Developer Guides / #Announcements / #events
- The “d-compat/\*” versioning strategy doc was updated: @david revised guidance for **pinning plugin/theme versions** for older Discourse installs, referencing the newer strategy work ([read more](https://meta.discourse.org/t/-/272665/7?silent=true), background: [RFC topic](https://meta.discourse.org/t/-/383536/1?silent=true)).
- On enabling **Discourse Reactions by default** , @martin explained the historical reluctance to change defaults, and noted upcoming rollout improvements that make opt-out, low-risk default changes more practical ([read more](https://meta.discourse.org/t/-/403795/5?silent=true)).
- The “Community Retention” webinar thread got its promised **relay + recap** , posted by @Danielle ([read more](https://meta.discourse.org/t/-/401266/3?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @david updated guidance on the new **`d-compat/*` strategy** in the version pinning doc ([read more](https://meta.discourse.org/t/-/272665/7?silent=true)), and suggested using the browser dev console to identify failed feature-detections for UXP browsers ([read more](https://meta.discourse.org/t/-/403890/5?silent=true)).
- @renato diagnosed the “apostrophe becomes `>`” composer issue as **typographer replacement behavior** , pointing admins to `enable_markdown_typographer` and quotation mark settings as immediate workarounds ([read more](https://meta.discourse.org/t/-/403905/6?silent=true)).
- @sam provided fix guidance for “Middleware document tree depth exceeded,” noting required commits and release timing ([read more](https://meta.discourse.org/t/-/403831/2?silent=true)), and endorsed adding **server-side webhooks** for AI artifact updates ([read more](https://meta.discourse.org/t/-/403865/4?silent=true)).
- @martin expanded on operational philosophy and tooling behind flipping defaults, in the announcement about **Reactions being enabled by default** ([read more](https://meta.discourse.org/t/-/403795/5?silent=true)).
- @Danielle posted the **webinar recap** for the Community Retention event ([read more](https://meta.discourse.org/t/-/401266/3?silent=true)).
- @pmusaraj clarified the updated mechanics for **category-scoped translation exclusions** via `ai_translation_excluded_categories` ([read more](https://meta.discourse.org/t/-/392993/7?silent=true)), and followed up on translated-email discussions by requesting more detail while confirming it remains on the roadmap ([read more](https://meta.discourse.org/t/-/383546/4?silent=true)).
- @Falco replied that DiscourseAI **sentiment support for additional LLM connections** was added and should roll out soon ([read more](https://meta.discourse.org/t/-/334451/18?silent=true)).
- @markvanlan decided to **disable post voting in nested replies** for now, suggesting a future built-in vote feature more native to nested UX ([read more](https://meta.discourse.org/t/-/403696/8?silent=true)).
- @chapoi provided admin guidance for anonymizing/disconnecting users in the WordPress SSO context ([read more](https://meta.discourse.org/t/-/396112/2?silent=true)), and suggested systematic extension/browsers checks for weird translated-text formatting reports on Debian/Linux ([read more](https://meta.discourse.org/t/-/400723/2?silent=true)).
* * *
**Sign-off:** Yesterday’s energy was peak Meta: half the forum chased down why an apostrophe could turn into a `>` ([read more](https://meta.discourse.org/t/-/403905/1?silent=true)), while the other half debated how to make “sudo-mode” admin actions safer _and_ less painful ([read more](https://meta.discourse.org/t/-/403930/6?silent=true)).
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [28 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/876 "2026-05-28T21:01:47Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h):** 111
- **New topics (last 24h):** 16
**Top users (posts / likes in the last 24h)**
| User | Posts | Likes |
| --- | --- | --- |
| @Lilly | 17 | 26 |
| @abeen | 13 | 12 |
| @merefield | 7 | 12 |
| @chapoi | 5 | 9 |
| @rishabh | 1 | 8 |
| @system | 1 | 8 |
| @haydenjames | 2 | 7 |
| @Moin | 5 | 7 |
| @darkpixlz | 3 | 6 |
| @loic | 1 | 6 |
**Notable drops & updates**
- The **May 2026 monthly release (v2026.05)** shipped with a full changelog in the announcement thread — [read more](https://meta.discourse.org/t/-/403981/1?silent=true)
- The **Current Projects** newsletter landed, recapping recent plugin improvements and what’s next — [read more](https://meta.discourse.org/t/-/403907/1?silent=true)
- Discourse’s **Discover May Roundup** companion topic went live — [read more](https://meta.discourse.org/t/-/403962/1?silent=true)
## Interesting Topics
### #Self-hosting
- @abeen asked for real-world guidance choosing **Vultr vs DigitalOcean** (with SMTP blocks and install gotchas becoming the real pain point), and got a mix of “host doesn’t matter—email does” and “avoid DO Marketplace installs” advice — [read more](https://meta.discourse.org/t/-/403964/1?silent=true) (plus related install/email context in [If local logins are disabled](https://meta.discourse.org/t/-/403735/23?silent=true) and the evergreen [Troubleshoot email on a new Discourse install](https://meta.discourse.org/t/-/16326/1?silent=true))
- A self-hoster hit an upgrade snag where `db:seed_fu` fails on `002_groups.rb` due to “Name has already been taken”, and shared a workaround by manually inserting the new system groups — [read more](https://meta.discourse.org/t/-/404037/1?silent=true)
- Discourse ID setup trouble was resolved after the admin enabled Discourse ID login in site settings, after initially working around onboarding via `rake` — [read more](https://meta.discourse.org/t/-/403951/9?silent=true)
### #bug
- “ **Phantom Unreads** ” struck again: `/unread` showed empty while the header counter claimed 14 unreads; the team confirmed the bug, and @Lilly provided a Rails/SQL “mark all as read” workaround that cleared counts site-wide — [read more](https://meta.discourse.org/t/-/403986/1?silent=true) (team acknowledgement: [read more](https://meta.discourse.org/t/-/403986/3?silent=true), workaround script: [read more](https://meta.discourse.org/t/-/403986/5?silent=true))
### #Support
- Admins discovered a hidden setting controlling the **impersonation time limit** (`experimental_impersonation_time_limit_minutes`) and discussed how to change it via Rails console (and why it’s not visible in the UI) — [read more](https://meta.discourse.org/t/-/403961/1?silent=true) (background: [Using hidden site settings](https://meta.discourse.org/t/-/308773/1?silent=true))
- A high-scale integrator needed to **create Chat channels via API** ; it turns out the endpoint exists (`POST /chat/api/channels`), and the thread now includes example parameters (notably `chatable_id`) — [read more](https://meta.discourse.org/t/-/403979/1?silent=true)
- A “ **Community Groups** ” landing-page request (show only specific groups like CoPs) was solved by pointing to the **Landing Pages plugin** approach — [read more](https://meta.discourse.org/t/-/403988/1?silent=true) (plugin thread: [read more](https://meta.discourse.org/t/-/180967/1?silent=true))
- Form Templates + tag groups: a **tag-chooser dropdown** populated but wouldn’t allow selection; initial debugging focused on tag group restrictions matching the configured tag groups — [read more](https://meta.discourse.org/t/-/404021/1?silent=true)
- The **Survey plugin** docs claim `min`/`max` attributes, but a report says they aren’t enforced (and client-side values can be manipulated), raising questions about validation and implementation — [read more](https://meta.discourse.org/t/-/404023/1?silent=true)
- UX feedback: mobile users struggle to find **“Sign Up”** when only “Log In” is visible; the thread explores UI alternatives and points to a combined auth button component as a workaround — [read more](https://meta.discourse.org/t/-/404022/1?silent=true) (related component: [read more](https://meta.discourse.org/t/-/401215/1?silent=true))
- A site owner asked whether there’s a setting to default **linked-post previews** (expanded vs collapsed) when linking to other posts/topics — [read more](https://meta.discourse.org/t/-/404036/1?silent=true) (related older discussion: [read more](https://meta.discourse.org/t/-/101972/3?silent=true))
### #contribute:feature
- The request to let admins **always edit user emails** even when “Edit email after signup” is disabled continued, with discussion of security/social engineering tradeoffs and the need for more granular admin permissions — [read more](https://meta.discourse.org/t/-/403930/10?silent=true)
- Long-running topic-timers request: **category-level auto-delete** (analogous to auto-close) got a forward-looking nod that it should be cleanly solvable via Discourse Workflows — [read more](https://meta.discourse.org/t/-/138361/18?silent=true)
### #Announcements
- The **Current Projects – May 2026** post highlighted completed work, including **Topic Voting** improvements and easier **Calendar/Events** setup — [read more](https://meta.discourse.org/t/-/403907/1?silent=true) (referenced: [Discourse Topic Voting](https://meta.discourse.org/t/-/40121/1?silent=true), [Voting improvements](https://meta.discourse.org/t/-/401156/1?silent=true), [New voting badges](https://meta.discourse.org/t/-/401731/1?silent=true), [Discourse Calendar and Event](https://meta.discourse.org/t/-/97376/1?silent=true), [Easier events categories](https://meta.discourse.org/t/-/401309/1?silent=true))
- The **May 2026 monthly release** announcement posted the canonical “what changed” link for v2026.5.0 — [read more](https://meta.discourse.org/t/-/403981/1?silent=true)
### #community-building:praise
- A self-hoster reversed course and praised **bundled (pre-installed) plugins**, noting how enabling them without rebuilds is a real production win — [read more](https://meta.discourse.org/t/-/404014/1?silent=true)
### #community-building Building
- Managing product announcements across many products and versions: the community brainstorm kicked off around **tags vs categories** , subscription strategy, and how to avoid notification fatigue as release cadence increases — [read more](https://meta.discourse.org/t/-/404039/1?silent=true)
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @chapoi confirmed the team is actively working on the **phantom unread counter** bug — \> “We are aware of this bug and trying to resolve it.” [read more](https://meta.discourse.org/t/-/403986/3?silent=true)
- @chapoi unblocked an integrator by pointing to the **Chat channel creation API endpoint** , and followed up to encourage marking the solution — [read more](https://meta.discourse.org/t/-/403979/2?silent=true) and [read more](https://meta.discourse.org/t/-/403979/4?silent=true)
- @chapoi helped triage a **Form Templates tag-chooser** issue by validating whether the category’s tag-group restrictions included the referenced tag groups — [read more](https://meta.discourse.org/t/-/404021/2?silent=true)
- @chapoi consolidated Horizon feedback by folding a “category badges are distracting” thread into the main **Horizon Theme** discussion to keep feedback centralized — [read more](https://meta.discourse.org/t/-/360486/92?silent=true)
- @rishabh published **Current Projects – May 2026** , summarizing recently finished work and inviting questions — [read more](https://meta.discourse.org/t/-/403907/1?silent=true)
- @loic posted the official **May 2026 monthly release** announcement and changelog pointer for v2026.5 — [read more](https://meta.discourse.org/t/-/403981/1?silent=true)
- @sam noted that **category-level auto-delete topics** should be “solvable quite cleanly” with Discourse Workflows — [read more](https://meta.discourse.org/t/-/138361/18?silent=true)
- @markvanlan reported that a version of an idea discussed in **Testing Nested Replies on Meta** was implemented — [read more](https://meta.discourse.org/t/-/398759/119?silent=true)
- @manuel shipped improvements to the **Announcement Bar** theme component (localized strings, localStorage dismiss, responsive layout, BEM classes) — [read more](https://meta.discourse.org/t/-/286352/31?silent=true) — and later clarified support expectations for **Featured Topics** feedback requests — [read more](https://meta.discourse.org/t/-/217580/63?silent=true)
- @pmusaraj thanked a reporter for clarifying translation behavior in the “translated posts in emails” feature discussion — [read more](https://meta.discourse.org/t/-/383546/8?silent=true)
- @Falco pointed a Gamification user to the official guide for integrating points with an external system — [read more](https://meta.discourse.org/t/-/225916/456?silent=true)
Yesterday’s moral: keep your YAML tidy, your plugin toggles handy, and your Unread counter firmly grounded in reality.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [29 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/877 "2026-05-29T21:01:41Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
In the last 24 hours (2026-05-28 → 2026-05-29), Meta saw **82 new posts** and **12 new topics** (with plenty of follow-up activity across ongoing threads like [nested replies](https://meta.discourse.org/t/-/402812/31?silent=true) and admin UX tweaks [read more](https://meta.discourse.org/t/-/404049/1?silent=true)).
**Top users (posts • likes in the last 24h)**
| User | Posts | Likes |
| --- | --- | --- |
| @Lilly | 11 | 8 |
| @merefield | 6 | 10 |
| @chapoi | 3 | 6 |
| @sam | 2 | 25 |
| @awesomerobot | 2 | 18 |
| @ted | 2 | 7 |
| @Eviepayne | 2 | 4 |
| @darkpixlz | 2 | 4 |
| @zogstrip | 2 | 3 |
| @david | 1 | 26 |
* * *
## Interesting Topics
**#Announcements**
- @david announced a major core dev milestone: a **new JavaScript build system** moving from `ember-cli/webpack` to **rolldown** (Rust bundler), with **~80% faster dev builds** while staying backwards compatible for production installs: [read more](https://meta.discourse.org/t/-/403908/1?silent=true). This builds on the earlier direction toward precompiled assets for self-hosters ([referenced here](https://meta.discourse.org/t/-/376700/1?silent=true)).
- @sam shared a change many admins have wanted: **“small action” posts** (close/open/assign/admin actions) are being **excluded from Watched/Tracked lists** to reduce notification noise, and it’s **not optional** : [read more](https://meta.discourse.org/t/-/404058/1?silent=true).
- @awesomerobot introduced an improved **event creation flow** in the #calendar-and-events plugin: an **interactive editor embedded in the composer** (plus clearer RSVP/attendance settings): [read more](https://meta.discourse.org/t/-/404041/1?silent=true) (plugin background: [Discourse Calendar and Events](https://meta.discourse.org/t/-/97376/1?silent=true)).
- Ongoing feedback continued on the **docked composer for AI bot conversations** , with requests to make “Enter to submit” optional and reports of image upload issues when using the new flow: [read more](https://meta.discourse.org/t/-/403327/2?silent=true).
* * *
**#bug**
- A tricky edge case was reported: incoming email handling can crash with **Gmail dot-variant addresses** (e.g. `user.name@gmail.com` vs `username@gmail.com`), hitting `Validation failed: Primary email has already been taken` when processing inbound mail or adding a secondary email: [read more](https://meta.discourse.org/t/-/404042/1?silent=true).
- A regression/upgrade snag: `db:seed_fu` can fail if a site already has a user or group named **`anonymous`** , leading to a “Name has already been taken” validation error during upgrade: [read more](https://meta.discourse.org/t/-/404037/2?silent=true).
- A UX/permissions mismatch in #reactions: if a post is hidden, the **reaction counter can still render** , but clicking it can cause an infinite loading loop due to a 403 from the reactions endpoint: [read more](https://meta.discourse.org/t/-/404053/1?silent=true).
- A report noted email notifications don’t mirror the web UI’s “display name” preference: even with full names shown in-app, **emails still show usernames** when mentioning people: [read more](https://meta.discourse.org/t/-/404075/1?silent=true).
- A support-facing warning appeared as a bug report from the field: Firefox users on Ubuntu saw **“Unfortunately, your browser is unsupported”** despite running a current version; debugging started with console checks and a related browser-support reference: [read more](https://meta.discourse.org/t/-/404070/1?silent=true).
* * *
**#ux**
- Creating a request-only group without an owner yields an unhelpful generic **FAILED** message; the thread also surfaced additional state/validation inconsistencies (private group + public request policy) and a fix direction toward better backend errors: [read more](https://meta.discourse.org/t/-/404049/1?silent=true) (plus historical related behavior: [“You cannot allow membership requests without any owners”](https://meta.discourse.org/t/-/64760/1?silent=true)).
- The keyboard shortcuts modal had **misaligned key hints** after a redesign, and the fix was quickly identified as legacy margin/CSS fallout: [read more](https://meta.discourse.org/t/-/404060/1?silent=true).
* * *
**#Support**
- Form Templates customization came up again: a marketplace-style category needs **structured “product card” post layouts** , but Form Templates output is linear; discussion covered “closest out-of-the-box” options vs building a theme component (and noted that some existing options are topic-list oriented): [read more](https://meta.discourse.org/t/-/404068/1?silent=true) (referenced: [Topic List Thumbnails](https://meta.discourse.org/t/-/150602/1?silent=true), [Topic Cards](https://meta.discourse.org/t/-/296048/1?silent=true)).
- Accessibility troubleshooting: a JAWS screen reader user’s shortcuts conflicted with Discourse shortcuts; guidance covered toggling JAWS virtual cursor mode and investigating where category/subcategory reading becomes unusable: [read more](https://meta.discourse.org/t/-/404095/1?silent=true).
- Category visibility management resurfaced: “Exclude category from latest” discussions continued, including guidance on the difference between **muted vs suppressed** categories and plugin-based approaches: [read more](https://meta.discourse.org/t/-/402209/17?silent=true) (related: [“Suppress category from latest topics” discussion](https://meta.discourse.org/t/-/133894/101?silent=true), and the recommended plugin: [discourse-categories-suppressed](https://meta.discourse.org/t/-/357254/7?silent=true)).
- A UI behavior question asked if local “linked post” oneboxes can default to **expanded** ; the conclusion was basically “no setting,” and any workaround risks rebakes/formatting tradeoffs: [read more](https://meta.discourse.org/t/-/404036/2?silent=true).
* * *
**#contribute:feature**
- Discussion continued on making “Sign Up” easier to find on mobile; follow-ups focused on whether the new link will be manageable/removable from the community section customization UI: [read more](https://meta.discourse.org/t/-/404022/12?silent=true).
- A request to **use translated posts in emails** for users with a specific user-language setting saw progress, with a fix merged and linked from the feature thread: [read more](https://meta.discourse.org/t/-/383546/9?silent=true).
* * *
**#bug** (nested replies ecosystem)
- Nested replies kept drawing real-world rollout feedback (including breakage reports, theme incompatibilities, and testing workflows). Separately, a bug around **suggested-topic links to nested topics** was discussed, including redirect/404 behavior and clarifying unread-count semantics in nested view: [read more](https://meta.discourse.org/t/-/403743/8?silent=true) and broader nested discussion: [read more](https://meta.discourse.org/t/-/402812/31?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @david laid out the roadmap and technical rationale for Discourse core’s **new JS build system** (rolldown, ES Modules, big dev speedups) and set expectations around backwards compatibility: [read more](https://meta.discourse.org/t/-/403908/1?silent=true).
- @sam announced the in-progress rollout to **stop tracking/watching “small action” posts** , aiming to reduce admin-notification noise: [read more](https://meta.discourse.org/t/-/404058/1?silent=true). @sam also tied the “phantom unread” experience back to that rollout in a related bug thread: [read more](https://meta.discourse.org/t/-/403986/7?silent=true).
- @awesomerobot shipped a smoother **create-event flow** in the composer for the #calendar-and-events plugin: [read more](https://meta.discourse.org/t/-/404041/1?silent=true). @awesomerobot also advised on JAWS shortcut conflicts and asked clarifying questions to pinpoint the categories/subcategories UX issue: [read more](https://meta.discourse.org/t/-/404095/2?silent=true).
- @chapoi helped clarify post-layout customization limits and the likely need for a theme component (vs Form Templates alone): [read more](https://meta.discourse.org/t/-/404068/2?silent=true). @chapoi also identified the keyboard-shortcut modal misalignment as legacy styling after a redesign: [read more](https://meta.discourse.org/t/-/404060/3?silent=true).
- @zogstrip reproduced and solved a Form Templates issue where mixed-case tag names prevented selecting a group tag, and linked the resulting fix: [read more](https://meta.discourse.org/t/-/404021/7?silent=true).
- @Danielle posted a status update that a webinar recap was available (closing the loop on the event thread): [read more](https://meta.discourse.org/t/-/398295/21?silent=true).
- @tannerabread confirmed that **copy/paste and drag/drop into a composer inside a form template** is now available on `latest`, and invited verification: [read more](https://meta.discourse.org/t/-/402250/13?silent=true).
- @markvanlan responded on nested reply link behavior, noting the link update and plans to improve redirects (avoiding flat-view 404s), and clarified how unread counts do/don’t map to nested structures: [read more](https://meta.discourse.org/t/-/403743/8?silent=true) and [read more](https://meta.discourse.org/t/-/403743/10?silent=true).
- @southpaw clarified what Discourse-hosting “cluster backups” are (catastrophic recovery only), and what support can do instead for full backups including uploads: [read more](https://meta.discourse.org/t/-/122710/69?silent=true).
- @pmusaraj noted a fix was merged for sending emails using translated content for users with a configured user language: [read more](https://meta.discourse.org/t/-/383546/9?silent=true).
* * *
If yesterday taught us anything, it’s this: may your builds be 80% faster, your “small actions” stay blissfully silent, and your nested links always land somewhere that isn’t a 404.
[Previous page](https://meta.discourse.org/t/daily-summary-9pm-utc/291850.md?page=30)
[Next page](https://meta.discourse.org/t/daily-summary-9pm-utc/291850.md?page=32)