# Dagelijkse samenvatting (5.00 uur UTC)

**URL:** https://meta.discourse.org/t/daily-summary-5am-utc/291851
**Category:** Forum summaries
**Created:** [16 januari 2024 om 21:58 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851 "2024-01-16T21:58:09Z")
**Posts on this page:** 20
**Page:** 27

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [22 februari 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/752 "2026-02-22T05:02:14Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New posts:** 84
- **New topics:** 15
- **Top contributors (posts / likes):**
  - @Moin — 8 posts / 15 likes
  - @NateDhaliwal — 7 posts / 11 likes
  - @Canapin — 6 posts / 10 likes
  - @ondrej — 2 posts / 7 likes
  - @asa — 1 post / 6 likes
  - @stephtara — 5 posts / 5 likes
  - @ばこん — 2 posts / 5 likes
  - @tobiaseigen — 5 posts / 4 likes
  - @merefield — 2 posts / 4 likes
  - @hipp0 — 11 posts / 4 likes

* * *

## Interesting Topics

### #Announcements

- On #Announcements, @ばこん reported the splash screen loading bar extending beyond its background in [post 26](https://meta.discourse.org/t/-/395100/26?silent=true) and @asa shared an [SVG update with clipPaths](https://meta.discourse.org/t/-/395100/30?silent=true) to constrain overflow.

### #Feature

- @NateDhaliwal demonstrated how to [add custom icons to usernames](https://meta.discourse.org/t/-/396567/10?silent=true) via his proof-of-concept plugin on [GitHub](https://github.com/NateDhaliwal/add-custom-icons-to-username).

- @hipp0 suggested making the users page sortable by name and time read in [this feature request](https://meta.discourse.org/t/-/396697/1?silent=true) following [previous discussions](https://meta.discourse.org/t/-/396697/2?silent=true).

- @ecki proposed new settings to limit the Welcome Banner’s visibility, sparking discussion in [Make the Welcome Banner less intrusive](https://meta.discourse.org/t/-/396685/1?silent=true) and detailed use-case feedback in [mcwumbly’s follow-up](https://meta.discourse.org/t/-/396685/8?silent=true).

- @ToddZ explored **crypto payments** integration using [Stripe’s on-ramp API](https://meta.discourse.org/t/-/396664/3?silent=true), while @hipp0 highlighted [integration challenges](https://meta.discourse.org/t/-/396664/4?silent=true).

- @hipp0 outlined requirements for **subscriber flairs and trust levels** , leading to an exchange on [Subscriber Group Trust Level and Subscriber Flair/Badge](https://meta.discourse.org/t/-/396667/1?silent=true) and group-based [permission workarounds](https://meta.discourse.org/t/-/396667/5?silent=true).

### #Support

- @ondrej guided a newcomer on customizing the sidebar with the [Discourse Doc Categories plugin](https://meta.discourse.org/t/-/396687/2?silent=true) in [Need Help on Category on left sidebar](https://meta.discourse.org/t/-/396687/1?silent=true).

- @Moin shared console-based steps to regain admin access after a URL structure change in [How to access Discourse admin after URL change?](https://meta.discourse.org/t/-/396669/3?silent=true) following [initial reports](https://meta.discourse.org/t/-/396669/1?silent=true).

### #Bug

- @gormus identified issues using `tag-chooser` fields—IDs appearing in previews and restrictions blocking tag saves—in [Tag-chooser tags are not allowed](https://meta.discourse.org/t/-/396679/1?silent=true) and confirmed the fix via [tag group config](https://meta.discourse.org/t/-/396679/3?silent=true).

- @Noble_Fish highlighted confusing GIF pause behavior showing only the first frame in [GIF always shows the first frame when paused](https://meta.discourse.org/t/-/396691/1?silent=true) and suggested improved pause handling in the [main topic](https://meta.discourse.org/t/-/396691?silent=true).

- @newbit1337 reported that **“Arrive at topic”** is dropped when resending invites in [Arrive at topic ignored when re-sending invites](https://meta.discourse.org/t/-/396704/1?silent=true), with @tobiaseigen confirming steps in [this follow-up](https://meta.discourse.org/t/-/396704/3?silent=true).

- @Luna_Mora discovered that opening an archived chat channel triggers the wrong modal and errors in [Open Channel action on Archived Channel triggers Close Channel modal](https://meta.discourse.org/t/-/396707/1?silent=true).

### #UX

- @darkpixlz suggested hiding the **Digest Summary UI** for free plan users in [Digest UI should be hidden on free plan](https://meta.discourse.org/t/-/396673/1?silent=true), a point echoed by @ondrej in [this reply](https://meta.discourse.org/t/-/396673/2?silent=true).

- @Luna_Mora discovered the **full-screen chat settings menu** on the Sublime theme overflows off-screen in [Full Screen Chat Window Height overflow on Sublime theme](https://meta.discourse.org/t/-/394864/5?silent=true) and awaits a fix in the [topic overview](https://meta.discourse.org/t/-/394864?silent=true).

### #Plugin

- @merefield rolled out **Kanban support** for Discourse Workflow with drag-and-drop lanes, keyboard moves, and overdue indicators in [his huge update](https://meta.discourse.org/t/-/347110/18?silent=true) and detailed the [GitHub PR](https://github.com/merefield/discourse-workflow/pull/16).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @zogstrip fixed Ruby/JS regex inconsistencies for number matching in watched words in [Rules for Number Matching in Watched Words](https://meta.discourse.org/t/-/396110/5?silent=true).
- @mcwumbly shaped translation organization discussions in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/19?silent=true) and chimed in on banner settings in [Make the Welcome Banner less intrusive](https://meta.discourse.org/t/-/396685/8?silent=true).

* * *

From SVG quirks to crypto curiosities and banner banter, the forum really came alive—no puppies were harmed in the making of this roundup!

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [23 februari 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/753 "2026-02-23T05:02:10Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New posts:** 134

- **New topics:** 22

- **Top users (likes, posts):**

- **Top [@team](https://meta.discourse.org/groups/team?silent=true) members (likes, posts):**

* * *

## Interesting Topics

- **#Support** @stephtara asked how to [display full topic text on a category page and add direct subcategory access in the navbar](https://meta.discourse.org/t/-/396715/1?silent=true), and @NateDhaliwal and @Moin debated Theme Component solutions versus collated pages with lazy loading for performance. [read more](https://meta.discourse.org/t/-/396715?silent=true)

- **#Support** @kgreed wondered how to hide public details about who liked their post, and @Canapin along with @Moin explained the “Hide my public profile” preference and site settings like `default hide profile` and `hide user profiles from public`. [read more](https://meta.discourse.org/t/-/396748?silent=true)

- **#Support** @stephtara reported that updating an existing link in the composer replaces custom link text with the topic title, prompting @ToddZ to suggest using Markdown or a custom component to preserve link labels when changing destinations. [read more](https://meta.discourse.org/t/-/396732?silent=true)

- **#Support** @long was puzzled why a [calendar shortcode](https://meta.discourse.org/t/-/396758/1?silent=true) didn’t surface event creation options, and @nat and @nathank guided them to use the “Create event” action in the OP composer rather than the per-reply `[@calendar]` syntax. [read more](https://meta.discourse.org/t/-/396758?silent=true)

- **#UX** @Steradiant requested quick toggles between the public badge pages and their admin configuration, and @stephtara linked this to broader quality-of-life improvements around Trust Levels and group privileges. [read more](https://meta.discourse.org/t/-/396734?silent=true)

- **#UX** @newbit1337 noticed that re-sent invite emails dropped the “arrive at topic” subject and body details, and @JammyDodger confirmed the UX discrepancy before moving the discussion to #UX for a fix. [read more](https://meta.discourse.org/t/-/396704?silent=true)

- **#UX** @stephtara flagged that the term `large_icon` in the **Logo & Icons** admin UI is unclear, leading @nathank and @Moin to locate the relevant `datetime_formats` and `month_names` strings in Crowdin and propose translations updates. [read more](https://meta.discourse.org/t/-/396713?silent=true)

- **#Feature** @Noble_Fish proposed a unified interface for **customizable keyboard shortcuts** , aiming to resolve conflicts like Ctrl+F vs site search and accidental Ctrl+Enter, sparking debate over per-site defaults and user exports/imports. [read more](https://meta.discourse.org/t/-/396717?silent=true)

- **#Feature** @markersocial asked for an API endpoint to **delete uploads** , observing that only “create” is available in the scope settings and suggesting a custom automation as a potential workaround. [read more](https://meta.discourse.org/t/-/396741?silent=true)

- **#Feature** @nathank outlined a case for allowing admins to edit and activate changed email addresses directly in `/admin/users` to avoid Rails console workarounds, echoing a common self-hosting pain point. [read more](https://meta.discourse.org/t/-/396760?silent=true)

- **#contribute:translations** @stephtara discovered that **published page dates** appear as “month/day” in French instead of “day month,” and @Moin mapped out the site text and Crowdin files (`datetime_formats`, `month_names`) for correction. [read more](https://meta.discourse.org/t/-/396733?silent=true)

- **#contribute:translations** @stephtara questioned why the English menu reads “Page Publishing” instead of an active “Publish Page,” and @ToddZ and @Moin compared it to German “als Seite veröffentlichen.” [read more](https://meta.discourse.org/t/-/396711?silent=true)

- **#Self-hosting support** @Ricardo_Viteri explored how to **archive a decade-old Discourse forum** into a static site to cut hosting costs, and @Canapin pointed to archival tools that may require community maintenance. [read more](https://meta.discourse.org/t/-/396731?silent=true)

- **#Plugin** @elmuerte introduced **Discourse Indisposable Email** to block disposable addresses via multiple external validators, warning about false negatives and recommending redundant service configurations. [read more](https://meta.discourse.org/t/-/396730?silent=true)

- **#Plugin** in a longstanding thread, @Heliosurge praised the experimental **Resenha voice rooms** plugin while @Falco noted missing UI elements and suggested tagging it #experimental. [read more](https://meta.discourse.org/t/-/389056?silent=true)

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @nat jumped into **#Support** to help @long troubleshoot the calendar plugin syntax in [Calendar showing but can’t create even with a post](https://meta.discourse.org/t/-/396758/2?silent=true).

- @nat responded to a **#Bug** report on Chinese localization in [官方meta中文语言下，搜索页面显示的一处错误](https://meta.discourse.org/t/-/396757/3?silent=true), confirming an upcoming translation fix.

- @sam updated the **Discourse AI bot** after deprecated header changes in [Discourse AI - AI bot](https://meta.discourse.org/t/-/266012/183?silent=true).

- @HAWK clarified the difference between the category-top calendar and in-topic embeds in [Calendar on top of category shows events, but embedded calendar doesn’t](https://meta.discourse.org/t/-/396716/2?silent=true).

* * *

After a full day of calendaring, translations, API dreams, and plugin schemes, our community clocks out—see you when the next theme component lands!

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [24 februari 2026 om 05:01 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/754 "2026-02-24T05:01:46Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New posts:** 105
- **New topics:** 16
- **Top users:**
  - @chapoi (8 posts, 25 likes)
  - @sam (9 posts, 16 likes)
  - @Moin (8 posts, 16 likes)
  - @NateDhaliwal (6 posts, 12 likes)
  - @merefield (4 posts, 11 likes)
  - @pfaffman (4 posts, 9 likes)
  - @Jesse_Starks (4 posts, 8 likes)
  - @Canapin (7 posts, 7 likes)
  - @Falco (4 posts, 6 likes)
  - @awesomerobot (1 post, 6 likes)

* * *

## Interesting Topics

### #Support

- **How to publish my theme component publicly** : @ClickandPledge wanted to share a Theme component in #Theme component but found it read-only; @chapoi explained that you must join the `theme_authors` group to publish and linked the docs. [read more](https://meta.discourse.org/t/-/396798/1?silent=true)

- **Changing the default homepage to a specific category** : @Jesse_Starks asked how to redirect logged-in users to a chosen category instead of the latest feed; @Moin showed how to reorder the `top menu` setting or use a custom homepage component. [read more](https://meta.discourse.org/t/-/396806/1?silent=true)

- **How do I disable the hot feature?** : @Jesse_Starks didn’t want “hot” post labels on a small community; darkpixlz and @Jesse_Starks removed the hot category and top-nav link in the Horizon theme. [read more](https://meta.discourse.org/t/-/396803/1?silent=true)

- **Registration for non-Facebook Users** : @shortmort37 needs `must_approve_users` globally but allow auto-approval for Facebook signups; the community discussed plugin options. [read more](https://meta.discourse.org/t/-/396834/1?silent=true)

- **Request to Verify Admin Rights for Discourse API Key** : @Apoorva_Johari asked why their API key can’t fetch group permissions; @NateDhaliwal pointed to scoped-key docs and @pfaffman recommended the [Data Explorer](https://meta.discourse.org/t/32566?silent=true) for reports. [read more](https://meta.discourse.org/t/-/396777/1?silent=true)

- **Calendar on top of category shows events, but embedded calendar doesn’t** : @Lou was puzzled why `[calendar]` in a post behaves differently than the category header calendar; @HAWK confirmed topic calendars and category calendars are distinct. [read more](https://meta.discourse.org/t/-/396716/3?silent=true)

### #Bug

- **Admin user export does not work in subfolder setup** : @RGJ reported the short-url export link 404s under a subfolder; @zogstrip merged a fix in PR 37996. [read more](https://meta.discourse.org/t/-/396783/1?silent=true)

- **Group filter includes deleted posts** : @Moin noticed deleted topics still appear in `group:` filters; @zogstrip addressed this in [PR 38000](https://meta.discourse.org/t/-/396807/3?silent=true). [read more](https://meta.discourse.org/t/-/396807/1?silent=true)

- **Open Channel action on Archived Channel triggers Close Channel modal** : @lindsey flagged that archived chats still show “Open Channel,” which opens the wrong modal; @sam suggested hiding the button. [read more](https://meta.discourse.org/t/-/396707/2?silent=true)

- **Links not opening in a new tab** : @long set the external-link target to `_blank` but links kept replacing the current tab; @HAWK asked about personal preference overrides. [read more](https://meta.discourse.org/t/-/396856/1?silent=true)

- **Minor edit on first post creates revision despite grace period when tagging is enabled** : @sam confirmed this is a regression after the tag refactor; @isaac fixed it in [PR 37989](https://meta.discourse.org/t/-/396501/3?silent=true). [read more](https://meta.discourse.org/t/-/396501/2?silent=true)

### #Self-hosting support

- **Is it safe to upgrade pgvector to 0.8.0 before running migration?** : @Andrés_Tarrío asked if Discourse 3.4.5 is compatible with pgvector 0.8.0; @Falco confirmed it’s safe for hosted PostgreSQL services. [read more](https://meta.discourse.org/t/-/396794/2?silent=true)

- **All IPv6 IP addresses show up as 172.17.0.1** : @pfaffman found Docker’s default proxy caused evicted IPv6 addresses in logs; setting `"userland-proxy": false` in `daemon.json` resolved it. [read more](https://meta.discourse.org/t/-/396819/1?silent=true)

### #Feature

- **GIF always shows the first frame when paused** : @Noble_Fish asked for consistent pause behavior; @sam said precise pause requires manual rendering via Canvas and recommended using MP4 for perfect frame control. [read more](https://meta.discourse.org/t/-/396691/5?silent=true)

- **Show create tag form to all users who may create tags** : @Sunilkumar wants TL3+ users to see the tag-creation form; @chapoi questioned the use case and default admin assignment. [read more](https://meta.discourse.org/t/-/396738/2?silent=true)

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @chapoi guided publishing of a theme component [396798/2](https://meta.discourse.org/t/-/396798/2?silent=true) and clarified the #trust-levels documentation [396792/1](https://meta.discourse.org/t/-/396792/1?silent=true).

- @sam weighed in on GIF pausing consistency [396691/2](https://meta.discourse.org/t/-/396691/2?silent=true) and confirmed the tag-chooser regression [396679/7](https://meta.discourse.org/t/-/396679/7?silent=true).

- @Falco explained safe pgvector upgrades [396794/2](https://meta.discourse.org/t/-/396794/2?silent=true) and defended removing the two-container install option [29413/138](https://meta.discourse.org/t/-/29413/138?silent=true).

- @awesomerobot sketched UI improvements for simplified category setup [394971/25](https://meta.discourse.org/t/-/394971/25?silent=true) and discussed the future of the Canvas theme foundations [352730/21](https://meta.discourse.org/t/-/352730/21?silent=true).

- @zogstrip fixed the subfolder export bug [396783/2](https://meta.discourse.org/t/-/396783/2?silent=true) and addressed deleted posts in group filters [396807/3](https://meta.discourse.org/t/-/396807/3?silent=true).

- @martin set up redirects for broken [Data Explorer](https://meta.discourse.org/t/32566?silent=true) links [396815/3](https://meta.discourse.org/t/-/396815/3?silent=true).

- @isaac provided a quick fix for the minor edit revision regression [396501/3](https://meta.discourse.org/t/-/396501/3?silent=true).

- @derek merged the poll mention-pill overlap fix [395463/9](https://meta.discourse.org/t/-/395463/9?silent=true).

- @mcwumbly investigated unused translation strings in topic filters [375610/2](https://meta.discourse.org/t/-/375610/2?silent=true).

- @pmusaraj merged the usercard cloak fix for mobile [319061/4](https://meta.discourse.org/t/-/319061/4?silent=true).

* * *

> After 105 new posts and 16 fresh topics—plus a slew of bugs squashed and features refined—it’s safe to say [meta.discourse.org](http://meta.discourse.org) never sleeps (and neither do our bookmarks).

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [25 februari 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/755 "2026-02-25T05:02:17Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

**New posts:** 141  
**New topics:** 14

**Top users (last 24 h):**

- @Moin: 24 posts, 27 likes
- @chapoi: 4 posts, 20 likes
- @Canapin: 10 posts, 18 likes
- @zogstrip: 8 posts, 14 likes
- @awesomerobot: 7 posts, 14 likes
- @long: 11 posts, 9 likes
- @merefield: 2 posts, 7 likes
- @pmusaraj: 2 posts, 6 likes
- @martin: 5 posts, 6 likes
- @Ed_S: 2 posts, 5 likes

_(Data sourced from the daily summary report.)_

## Interesting Topics

- #Announcements Admin Reporting & Analysis: Incremental Changes — @chapoi introduced the first step in **reworking the admin dashboard** , grouping reports into Engagement, Traffic, Members, Content & Health, Moderation, and Security, while also cleaning up unused charts [read more](https://meta.discourse.org/t/-/395768/1?silent=true) and see the [Admin Dashboard Report Reference Guide](https://meta.discourse.org/t/240233/1?silent=true).

- #Support What “login with” options currently work? — @long asked for an **updated list** of OAuth providers, @Falco confirmed that the options used on [Discourse ID sign-up](https://id.discourse.com/signup) remain supported [solution](https://meta.discourse.org/t/-/396932/2?silent=true), and @awesomerobot detailed Apple login requirements alongside a [Discourse ID alternative](https://meta.discourse.org/t/-/171485/61?silent=true).

- #UX Changing to Full Width — @Steve_Walmsley flagged **narrow text** on ultrawide displays; @NateDhaliwal linked to the [Discourse full-width component](https://meta.discourse.org/t/292496/1?silent=true), and @chapoi discussed **readability guidelines** with Baymard Institute references [read more](https://meta.discourse.org/t/-/396884/1?silent=true).

- #UX Why are “Required” and “Enum” hardcoded in AI tool parameter configuration? — @Moin spotted non-translatable labels in the AI Tools UI, and @zogstrip promptly [merged a fix](https://github.com/discourse/discourse/pull/38045) to make those strings translatable [topic](https://meta.discourse.org/t/-/396939/1?silent=true).

- #UX Long-press l to react with an emoji instead of a regular like? — @Canapin proposed a **long-press** on l to open the emoji selector, igniting discussion on keyboard shortcut conventions [read more](https://meta.discourse.org/t/-/396907/1?silent=true).

- #Bug [Resolved] Search “in this topic” checkbox seems to be lost after the last update — @small-lovely-cat reported missing **in-topic search** on mobile, and @Canapin confirmed its presence with screenshots in the mobile view [update](https://meta.discourse.org/t/-/396892/2?silent=true).

- #Support Links not opening in a new tab — @long and @NateDhaliwal investigated **external link behavior** , and @long shared a theme component snippet that forces `target="_blank"` and `rel="noopener noreferrer"` on outside links [details](https://meta.discourse.org/t/-/396856/3?silent=true).

- #Self-hosting support Error on login page about SMTP server not being configured — @R23D_Printing saw a banner stating email was disabled despite successful tests, and community members guided them through the [Google Workspace SMTP relay setup](https://meta.discourse.org/t/237662/1?silent=true).

- #Self-hosting support Problem during `./launcher rebuild`, Redis not starting the second time — @Wanderer shared a **rebuild failure** due to a lingering Redis process; a community-supplied `pkill redis-server` hook in `app.yml` ensures reliable rebuilds [read more](https://meta.discourse.org/t/-/396912/1?silent=true).

- #Support Send New Users to Topic After Confirming Registration — @long wanted to **redirect newcomers** post-confirmation; @Moin examined the default flow and SSO implications, sparking deeper discussion about the wizard UI and possible site-setting solutions [topic](https://meta.discourse.org/t/-/396895/1?silent=true).

- #UX Field alignment issues in LLM cost configuration in German — @Moin observed that **longer German labels** misalign input fields in the AI cost settings interface, highlighting the need for improved multi-language UI support [discussion](https://meta.discourse.org/t/-/396948/1?silent=true).

- #blog Elfsight: How a Wishlist Category Shaped 700 Feature Releases — The system post showcased **Elfsight’s no-code widget roadmap** and how community-driven wishlist discussions powered hundreds of releases [read more](https://meta.discourse.org/t/-/396937/1?silent=true).

- #UX Error popup when suggesting tags in topic already having tags — @NateDhaliwal and @Canapin debugged an **unexpected popup** during tag suggestions on already-tagged topics and weighed whether it qualifies as a bug [conversation](https://meta.discourse.org/t/-/396857/3?silent=true).

- #Support iPad – Composer peek mode button causes editor to go off screen — @Jesse_Starks reported a **UI glitch** in peek mode on iPad, prompting multi-browser tests but no fix yet [issue](https://meta.discourse.org/t/-/396942/1?silent=true).

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @chapoi kicked off **#Announcements** with [Admin Reporting & Analysis: Incremental Changes](https://meta.discourse.org/t/-/395768/1?silent=true), gathering early feedback on the new grouping and cleanup approach.

- @Falco stepped in on **#Support** at [What “login with” options currently work?](https://meta.discourse.org/t/-/396932/2?silent=true), confirming OAuth providers in use on Discourse ID.

- @awesomerobot further enriched that same thread by outlining Apple login requirements and pointing to the [Discourse ID alternative](https://meta.discourse.org/t/-/171485/61?silent=true).

- @chapoi weighed in under **#UX** on [Changing to Full Width](https://meta.discourse.org/t/-/396884/4?silent=true), defending line-length best practices with UX citations.

- @zogstrip resolved the translation issue in **#UX** via [Why are “Required” and “Enum” hardcoded](https://meta.discourse.org/t/-/396939/2?silent=true), merging a PR to expose those labels for i18n.

- @Canapin contributed fixes in two threads: he clarified the mobile search checkbox under **#Bug** at [Resolved Search “in this topic”](https://meta.discourse.org/t/-/396892/2?silent=true) and addressed the tag suggestion popup in **#UX** at [Error popup when suggesting tags](https://meta.discourse.org/t/-/396857/3?silent=true).

—  
And that’s a wrap—no puppies were harmed in the making of today’s summary! 🐶

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [26 februari 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/756 "2026-02-26T05:02:03Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New posts** : 186
- **New topics** : 21

**Top users** (posts, likes in past 24 hrs):

- @Moin (23 posts, 38 likes)
- @Canapin (15 posts, 35 likes)
- @RGJ (5 posts, 27 likes)
- @Danielle (2 posts, 22 likes)
- @ToddZ (9 posts, 19 likes)
- @stephtara (16 posts, 16 likes)
- @chapoi (9 posts, 12 likes)
- @R23D_Printing (9 posts, 8 likes)
- @Jesse_Starks (12 posts, 7 likes)
- @mcwumbly (9 posts, 6 likes)

* * *

## Interesting Topics

### #Site feedback

- **Volunteer Moderators introduced**  
@Danielle introduced the [Volunteer Moderators program](https://meta.discourse.org/t/-/397009/1?silent=true), outlining their stewardship role in keeping Meta organized without staff-level permissions.

- **Category reorganization underway**  
@mcwumbly kicked off layout updates for #categories in the [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/20?silent=true) roadmap, soliciting feedback on the new sidebar defaults.

### #customization:theme component

- **Discourse Age Check**  
@RGJ released the [Discourse Age Check](https://meta.discourse.org/t/-/397002/1?silent=true) theme component to verify user age on signup, sparking GDPR compliance discussions with @awesomerobot’s insights.

### #Announcements

- **Discourse Free plan beta**  
@rishabh invited community members to trial the [Discourse Free plan beta](https://meta.discourse.org/t/-/395632/24?silent=true), igniting conversations around feature limitations and self-hosting options.

- **Foundation theme modernization**  
Discussions on streamlining the #Foundation theme continued as @manuel reviewed theme updates in [Canvas Theme Template](https://meta.discourse.org/t/-/352730/22?silent=true) ahead of the modernized defaults.

### #Customization

- **CSS selectors for user groups**  
@ToddZ shared tips for locating editor and group-based selectors in the [Finding CSS selectors for page layout, user groups](https://meta.discourse.org/t/-/397044/1?silent=true) topic, helping tailor UI by Trust Level or group.

### #Self-hosting

- **SMTP configuration bug**  
@supermathie confirmed an incorrect “SMTP not configured” warning on the login page in [Error on login page about SMTP server not being configured](https://meta.discourse.org/t/-/396943/18?silent=true), while @R23D_Printing worked around it with a temporary theme component.

### #customization:plugin

- **Docs sidebar behavior**  
@stephtara raised UX concerns about disappearing admin links in [Discourse Doc Categories](https://meta.discourse.org/t/-/322376/153?silent=true), leading @ToddZ to suggest CSS tweaks for a distinct crawler layout.

### #contribute:feature

- **Upload deletion via API**  
@markersocial explored automated workflows for removing uploads through endpoints outlined in [Upload Deletion via API](https://meta.discourse.org/t/-/396741/3?silent=true), with @RGJ pointing to the Legal Compliance plugin.

### #Support

- **Comprehensive admin guide**  
@Glaudeman sought a holistic resource in [Newbie question: Is there a comprehensive guide to configuring and administering Discourse instance?](https://meta.discourse.org/t/-/397040/1?silent=true), and community members pointed to #Documentation and #Community Wiki.

### #ux

- **Subcategory search visibility**  
@mcwumbly proposed counting hidden subcategories in the filter dropdown in [Finding subcategories via the category dropdown](https://meta.discourse.org/t/-/397016/1?silent=true) to ensure the search field appears for all users.

### #bug

- **Quote attribution in RTE**  
@Moin isolated a bug where the rich text editor drops full names in quotes in [Display full name not username when attributing quote in RTE](https://meta.discourse.org/t/-/397049/12?silent=true), confirming markdown mode works as designed.

- **iPad composer peek-mode glitch**  
@chapoi and @Jesse_Starks debugged the Horizon theme’s peek-mode on tablets in [Ipad - Composer peek mode button causes editor to go off screen](https://meta.discourse.org/t/-/396942/7?silent=true), narrowing the issue to theme-specific breakpoints.

### #Marketplace

- **Senior Discourse Developer needed**  
@Max_Schwab posted a [Paid Senior Discourse Developer role](https://meta.discourse.org/t/-/396977/1?silent=true) focusing on SSO, infrastructure, and accessibility, with @RGJ offering Communiteq’s expertise.

- **Automated feed integration**  
@JeroenR introduced a [Paid feed integration service](https://meta.discourse.org/t/-/397038/1?silent=true) for RSS, XML, and YouTube feeds, highlighting custom templates and high-frequency polling options.

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @Danielle unveiled the Volunteer Moderators initiative and addressed group selection criteria in [Introducing Volunteer Moderators on Meta](https://meta.discourse.org/t/-/397009/1?silent=true).

- @chapoi provided feedback on admin reporting interfaces in [Admin Reporting & Analysis: Incremental Changes](https://meta.discourse.org/t/-/395768/9?silent=true) and documented TL2 edge-cases in [TL2 promotion seemingly only counts public contributions](https://meta.discourse.org/t/-/396458/15?silent=true).

- @mcwumbly implemented the first round of category layout changes in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/20?silent=true) and drafted guidelines for the new #Customization category in [About the Customization category](https://meta.discourse.org/t/-/396993/1?silent=true).

- @supermathie confirmed and escalated the SMTP error display issue on the login page in [Error on login page about SMTP server not being configured](https://meta.discourse.org/t/-/396943/18?silent=true).

- @awesomerobot weighed in on GDPR compliance for the Discourse Age Check component in [Discourse Age Check](https://meta.discourse.org/t/-/397002/4?silent=true).

- @zogstrip patched the chat UI by hiding the open button on archived channels in [Open Channel action on Archived Channel triggers Close Channel modal](https://meta.discourse.org/t/-/396707/3?silent=true).

- @manuel reviewed upcoming Foundation updates and flagged obsolete styles in [Canvas Theme Template](https://meta.discourse.org/t/-/352730/22?silent=true).

- @martin clarified the upcoming changes localization setting in [Issue with enabling upcoming changes](https://meta.discourse.org/t/-/395881/25?silent=true).

* * *

With volunteer mods on patrol and themes being tweaked, it’s been a pupperiffic day—here’s hoping your notifications are as well-behaved as those new volunteer moderators! 🐶

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [27 februari 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/757 "2026-02-27T05:02:33Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New posts (last 24h):** 125
- **New topics (last 24h):** 12

**Top users (posts / likes in the last 24h):**

| User | Posts | Likes |
| --- | --- | --- |
| @ToddZ | 15 | 19 |
| @Moin | 13 | 19 |
| @merefield | 4 | 14 |
| @mcwumbly | 7 | 13 |
| @Canapin | 8 | 12 |
| @Danielle | 2 | 8 |
| @stephtara | 6 | 7 |
| @rishabh | 1 | 7 |
| @zogstrip | 1 | 6 |
| @tgxworld | 1 | 6 |

* * *

## Interesting Topics

### #Site feedback

- **Meta’s category re-org continues to iterate** (#meta-redesign-2026): @mcwumbly explored whether “category groups” might work better than parent categories, and shipped tweaks like restricting posting in container categories and improving subcategory discovery (including “boxes”)—with ongoing debate about _above-the-fold_ topic visibility on tablets. See the latest checkpoint update [read more](https://meta.discourse.org/t/-/396306/43?silent=true), plus the “category groups” direction via the existing theme component idea [read more](https://meta.discourse.org/t/-/200874/1?silent=true) and prior context on admin UX friction like multi-tag setup [read more](https://meta.discourse.org/t/-/390796/1?silent=true).

- **Volunteer moderators program: messaging visibility + “how do I join?”** Meta’s new volunteer initiative moved forward as @Danielle confirmed the [@VolunteerMods](https://meta.discourse.org/groups/volunteermods?silent=true) group is now visible and messageable, and clarified that expansion will come later once the pilot stabilizes [read more](https://meta.discourse.org/t/-/397009/13?silent=true).

- **New tagging request: track accessibility palette-specific issues** : @Moin proposed adding a dedicated #wcag-palettes tag so palette-specific bugs (especially contrast/visibility) can be triaged more easily [read more](https://meta.discourse.org/t/-/397116/1?silent=true). (The tag was subsequently created and applied to example topics [read more](https://meta.discourse.org/t/-/397116/2?silent=true).)

- **Should unlisted topics appear in “Related”?** A discussion popped up around whether unlisted topics should be excluded from the “Related” panel the way they are from search results, to reduce noise during research workflows [read more](https://meta.discourse.org/t/-/397174/1?silent=true).

### #Support

- **Heading hierarchy in the composer (H1 vs H2 vs H3) meets accessibility reality**: A thread on proper heading levels dug into SEO myths _and_ screen-reader structure (including the surprising hidden heading structure per-post), with suggestions to hide H1/H2 buttons and standardize on deeper headings for content [read more](https://meta.discourse.org/t/-/397100/19?silent=true). Related historical context: “disable headers in replies” [read more](https://meta.discourse.org/t/-/81775/1?silent=true) and the evergreen formatting reference guide [read more](https://meta.discourse.org/t/-/239348/1?silent=true).

- **Migration sizing question: 800k topics and 12k DAU** : A large-scale migration inquiry asked whether Discourse needs special architecture at that size, and what “enough server” looks like beyond RAM numbers (pageviews were the next key question) [read more](https://meta.discourse.org/t/-/397151/1?silent=true).

- **Gate a marketplace category until someone “likes” the rules topic** (#automation): A self-hosted admin explored how to require a “rules acknowledgement” (via like → badge → group → permission) before granting posting rights in a Buy/Sell/Trade category [read more](https://meta.discourse.org/t/-/397191/5?silent=true), with a possible alternative approach using Discourse Policy workflows mentioned for comparison [read more](https://meta.discourse.org/t/-/88557/1?silent=true).

### #ux

- **Free-plan polish: hide digest UI that’s not available** (#free-plan, #activity-summary): A UX paper-cut where the digest controls were visible on the Free plan (even though the feature isn’t) was addressed, adding upgrade messaging and removing confusion [read more](https://meta.discourse.org/t/-/396673/5?silent=true).

- **User cards opened from the like list jump to the top-left** (#user-card): A repro GIF shows user cards snapping to the page corner after opening from the like-list avatar, suggesting a positioning/hover edge case [read more](https://meta.discourse.org/t/-/397122/1?silent=true).

- **Subcategory navigation friction: finding subcats in the topic-list dropdown** (#meta-redesign-2026): Continued feedback on how people discover and drill into subcategories during browsing, especially when hierarchy grows and “direct access” matters [read more](https://meta.discourse.org/t/-/397016/1?silent=true).

- **Make inline links to subcategories less… gigantic?** (#meta-redesign-2026): Following on from the category re-org, a new UX thread proposes improving how subcategory links render inline so they read more naturally in sentences [read more](https://meta.discourse.org/t/-/397217/1?silent=true).

### #bug

- **Content localization toggle has no visible “on/off” state under WCAG palettes** (#content-localization, #wcag-palettes): A report shows the translation toggle’s state is effectively invisible when high-contrast palettes are enabled—an issue that becomes clearer once you compare prior UI behavior and palette constraints [read more](https://meta.discourse.org/t/-/397115/1?silent=true). Background: WCAG palette feature reference [read more](https://meta.discourse.org/t/-/168795/1?silent=true) and related palette-visibility reports like quoted mentions [read more](https://meta.discourse.org/t/-/293324/1?silent=true) and icon visibility in menus [read more](https://meta.discourse.org/t/-/370721/1?silent=true).

- **RTE quoting attribution shows full name instead of username** (#composer): A bug fix landed after root-cause work, resolving quote attribution behavior in the rich-text editor [read more](https://meta.discourse.org/t/-/397049/16?silent=true).

- **Upcoming Changes UI: “staff enabled” state not reflected after reload** (#translation, #upcoming-changes): A repro indicates the saved value can be `"staff"` while the UI select expects a literal group name (e.g. “Team”), causing the dropdown to fall back and display “no one” after refresh [read more](https://meta.discourse.org/t/-/395881/26?silent=true).

### #Self-hosting

- **SMTP not configured warning appearing on login (regression found + fix queued)** (#email): A self-hosting report was traced to a regression, with a fix identified and linked for upgrade/rebuild guidance [read more](https://meta.discourse.org/t/-/396943/24?silent=true).

- **Dashboard confusion: “Latest” version equals “Installed”** : A version-check endpoint issue was corrected after a semver formatting hiccup (“leading zeros”), and the discussion hints at future UX improvements for versioning clarity [read more](https://meta.discourse.org/t/-/396994/4?silent=true). Related self-hosting troubleshooting threads that stayed active: external proxy SSL detection gotchas [read more](https://meta.discourse.org/t/-/397128/1?silent=true) and reverse-proxy setup notes for Caddy [read more](https://meta.discourse.org/t/-/54716/22?silent=true).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @mcwumbly continued hands-on iteration on Meta’s category structure experiment—balancing container categories vs. “postable” parents, and improving discovery mechanics (like showing subcategories) [read more](https://meta.discourse.org/t/-/396306/43?silent=true). They also created the requested #wcag-palettes tag for better triage [read more](https://meta.discourse.org/t/-/397116/2?silent=true), and spun off follow-up UX discussion about subcategory link formatting [read more](https://meta.discourse.org/t/-/397217/1?silent=true).

- @Danielle advanced the Volunteer Moderators rollout by enabling visibility/messaging for the group, and clarified the “pilot first, expand later” path [read more](https://meta.discourse.org/t/-/397009/13?silent=true).

- @rishabh clarified why Discourse ID must remain enabled on the Free plan (it’s the only login method there) and noted an update preventing admins from toggling it off [read more](https://meta.discourse.org/t/-/395632/32?silent=true).

- @tgxworld identified the regression behind the SMTP warning-on-login problem and linked the upstream fix PR for affected self-hosters [read more](https://meta.discourse.org/t/-/396943/24?silent=true).

- @zogstrip credited good root-cause analysis and shipped a fix for the RTE quote attribution bug (full name vs username) [read more](https://meta.discourse.org/t/-/397049/16?silent=true).

- @keegan addressed Free plan UX by hiding digest controls where they aren’t usable and adding an upgrade indicator [read more](https://meta.discourse.org/t/-/396673/5?silent=true).

- @Falco confirmed the renamed anonymous-search rate limit setting (`rate_limit_search_anon_global_per_minute`), helping unblock admins tuning defenses against automated search spam [read more](https://meta.discourse.org/t/-/110706/28?silent=true).

- @chapoi completed dashboard/reporting polish (alphabetical sorting that respects UI language) and dug into feedback about report deprecations and why certain “anti-gaming” reports matter [read more](https://meta.discourse.org/t/-/395768/12?silent=true) and [read more](https://meta.discourse.org/t/-/395768/14?silent=true).

- @awesomerobot advised using admin permalinks to preserve SEO equity when merging topics (301 redirect via `/admin/config/permalinks`) [read more](https://meta.discourse.org/t/-/396497/2?silent=true).

- @david fixed the “latest version” display confusion caused by a semver edge case, and noted that the dashboard currently shows released versions only (with planned UX improvements) [read more](https://meta.discourse.org/t/-/396994/4?silent=true).

* * *

If yesterday taught us anything, it’s that Meta can debate _category boxes above the fold_ with the same intensity it reserves for whether your post headings should start at **H2** … or **H3**.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [28 februari 2026 om 05:01 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/758 "2026-02-28T05:01:06Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

Over the last 24 hours, Meta saw **129 new posts** across **13 new topics**. Source: [read more](https://meta.discourse.org/t/-/397246/1?silent=true)

**Top contributors (posts • likes received)**

- @manuel — **4 posts • 26 likes** ([read more](https://meta.discourse.org/t/-/397246/5?silent=true))
- @merefield — **7 posts • 18 likes** ([read more](https://meta.discourse.org/t/-/69742/1227?silent=true))
- @Moin — **12 posts • 17 likes** ([read more](https://meta.discourse.org/t/-/397246/2?silent=true))
- @Canapin — **6 posts • 16 likes** ([read more](https://meta.discourse.org/t/-/397315/1?silent=true))
- @NateDhaliwal — **11 posts • 14 likes** ([read more](https://meta.discourse.org/t/-/397232/2?silent=true))
- @angus — **1 post • 13 likes** ([read more](https://meta.discourse.org/t/-/397246/14?silent=true))
- @RGJ — **8 posts • 11 likes** ([read more](https://meta.discourse.org/t/-/397002/11?silent=true))
- @Falco — **3 posts • 9 likes** ([read more](https://meta.discourse.org/t/-/397246/33?silent=true))
- @nathank — **1 post • 9 likes** ([read more](https://meta.discourse.org/t/-/397246/3?silent=true))
- @ToddZ — **3 posts • 9 likes** ([read more](https://meta.discourse.org/t/-/395768/19?silent=true))

> “Part of good design is also daring to prune away things.” — @chapoi ([read more](https://meta.discourse.org/t/-/395768/18?silent=true))

* * *

## Interesting Topics

### #Site feedback

- @NateDhaliwal noticed the _Meta Branded_ theme shifting (notably **purple accents** , rounded controls, and a new font), and @manuel confirmed this is part of aligning Meta with updated brand guidelines (including the important caveat that these brand choices **aren’t intended to be user-adjustable** ) [read more](https://meta.discourse.org/t/-/397246/5?silent=true). Related: the broader rollout plan in _Updating Meta’s theme and structure_ (#meta-redesign-2026) [read more](https://meta.discourse.org/t/-/396304/4?silent=true), and the “themes restricting color schemes” gap (including discussion of #TargetableColorSchemes) [read more](https://meta.discourse.org/t/-/276967/1?silent=true) and the “override selected palette” confirmation [read more](https://meta.discourse.org/t/-/397246/36?silent=true).

### #customization:extras

- A new OpenClaw integration plugin was announced, enabling agents to **read/search/filter** and optionally **create/reply** to topics, with @Bas urging strong defaults and clear labeling whenever AI writes content [read more](https://meta.discourse.org/t/-/397239/2?silent=true). (It builds around “find unanswered questions” workflows) [read more](https://meta.discourse.org/t/-/397239/1?silent=true).

### #Self-hosting

- A “404 Not Found” during console install turned out to be a subtle URL typo (`discourse-docker` vs `discourse_docker`), and the thread also clarified why the documented `wget -qO- ... | sudo bash` matters for expected behavior [read more](https://meta.discourse.org/t/-/397232/6?silent=true).

### #Support

- Folks hunting for “Form Templates” learned the feature is no longer just a hidden experimental setting; it’s now managed via **Admin → Upcoming Changes** , as @renato explained (and this also prompted a call to update older announcement/docs) [read more](https://meta.discourse.org/t/-/397297/6?silent=true). Related references: the original announcement topic (#form-templates) [read more](https://meta.discourse.org/t/-/278631/1?silent=true) and the central _Upcoming changes_ page [read more](https://meta.discourse.org/t/-/395390/1?silent=true).

### #Support

- A deep dive into **“Request Revision”** highlighted a confusing moderation flow where a rejected first post + user silencing can leave the author unable to respond or iterate, prompting comparisons to UX ideas in _Allow the ability to Edit post on rejection_ (#review-queue) [read more](https://meta.discourse.org/t/-/397258/1?silent=true) and the linked UX brainstorm [read more](https://meta.discourse.org/t/-/373992/1?silent=true).

### #bug

- A new bug report shows the **Styleguide page can crash for anonymous users** when “Styleguide allowed groups” is set to _everyone_, due to a missing admin component import (`discourse/admin/components/highlighted-code`) [read more](https://meta.discourse.org/t/-/397317/1?silent=true).

### #ux

- A small-but-annoying UX issue: the **sidebar wrapper blocks clicking the logo** (home navigation) on Foundation/Meta Branded themes, with screenshots showing the click target being covered [read more](https://meta.discourse.org/t/-/397257/1?silent=true).

### #contribute:translations

- Missing translated strings cropped up again post-release; @gerhard traced it to Crowdin not returning all translated strings and said he’s investigating to restore them ASAP [read more](https://meta.discourse.org/t/-/395098/8?silent=true).

### #General

- On whether Discourse should “nudge” large third‑party instances with serious UX problems, @chapoi noted outreach is rare unless things are truly dramatic—and community members pointed out **[safe mode](https://meta.discourse.org/t/53504?silent=true)** as a practical workaround to bypass problematic customizations [read more](https://meta.discourse.org/t/-/397212/2?silent=true).

### #support:migration

- A migration planning thread for **800k topics / 12k DAU** continued: guidance emphasized that default search usually holds up at scale, while @Falco flagged **disk IOPS and DB caching** as likely bottlenecks to watch (especially in the first month) [read more](https://meta.discourse.org/t/-/397151/7?silent=true).

### #community-building Building

- A side conversation from an “age check” component spun into a focused GDPR thread on storing date of birth: the discussion centered on lawful basis, transparency, retention, and the idea that GDPR is about _control_, not a blanket prohibition [read more](https://meta.discourse.org/t/-/397231/5?silent=true). (The split was noted from the original theme-component discussion) [read more](https://meta.discourse.org/t/-/397002/11?silent=true).

### #Site Management

- A Discourse AI spam-detection troubleshooting post asked why a locally-created “spam” topic didn’t enter the review queue despite matching stated thresholds, and responders pointed to the built-in **testing tool** in `/admin/plugins/discourse-ai/ai-spam` for validating rule behavior [read more](https://meta.discourse.org/t/-/343541/27?silent=true).

### #contribute:feature

- A small but meaningful GDPR-related request: **exported data should include the Discourse post ID** —@awesomerobot said a PR is already open to implement it [read more](https://meta.discourse.org/t/-/397074/2?silent=true).

### #Support

- Clarification on `hide_user_profiles_from_public`: even if the UI redirects anonymous users away from `/u`, aggregated stats can still be visible via API; @j.jaffeux framed it as “not airtight protection” and explained the tradeoffs [read more](https://meta.discourse.org/t/-/397252/2?silent=true).

### #wordpress

- WP‑Discourse “Path to your Login Page” confusion was resolved: the behavior was correct, but a third-party membership plugin (Memberium) was interfering—fixed temporarily via a custom WP plugin patch while awaiting upstream fixes [read more](https://meta.discourse.org/t/-/397070/5?silent=true).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @manuel engaged heavily in the Meta brand refresh thread—confirming the **brand alignment is intentional** , acknowledging accessibility/comfort concerns, and explaining why _Meta Branded_ currently conflicts with user color schemes (and why “restrict color schemes per theme” would be the cleaner long-term fix) [read more](https://meta.discourse.org/t/-/397246/5?silent=true) and [read more](https://meta.discourse.org/t/-/397246/32?silent=true).

- @mcwumbly linked the live changes back to the broader #meta-redesign-2026 plan and explicitly invited ongoing feedback in the dedicated theme thread [read more](https://meta.discourse.org/t/-/396304/4?silent=true) and [read more](https://meta.discourse.org/t/-/397246/7?silent=true).

- @Falco added team perspective on the refreshed look (preferring it over the prior Meta Branded iteration) [read more](https://meta.discourse.org/t/-/397246/33?silent=true), and gave practical scaling guidance on migration hardware—especially around disk performance and early monitoring [read more](https://meta.discourse.org/t/-/397151/7?silent=true). @Falco also chimed in on AI-assisted plugin development, stressing good local context and pointing to the in-repo AI agent guidance [read more](https://meta.discourse.org/t/-/397330/3?silent=true).

- @Bas responded to the OpenClaw plugin announcement with a clear moderation-minded plea: **don’t let agents post unlabeled AI content** , while endorsing “civilized defaults” like agent signatures [read more](https://meta.discourse.org/t/-/397239/2?silent=true).

- @renato solved confusion around Form Templates by pointing admins to **Upcoming Changes** , noting older announcement material needs updating to match the new reality [read more](https://meta.discourse.org/t/-/397297/6?silent=true) (and reiterating the same in the original announcement topic) [read more](https://meta.discourse.org/t/-/278631/83?silent=true).

- @chapoi confirmed an iPad composer issue (peek mode pushing the editor off-screen) and said a fix is being investigated [read more](https://meta.discourse.org/t/-/396942/9?silent=true). @chapoi also explained the rationale behind pruning admin reports in the reporting refresh—preferring observable feedback over indefinitely maintaining “extra” UI sections [read more](https://meta.discourse.org/t/-/395768/18?silent=true).

- @gerhard acknowledged the translation regression reports and indicated active investigation into Crowdin’s incomplete string returns [read more](https://meta.discourse.org/t/-/395098/8?silent=true).

- @j.jaffeux clarified the nuance behind `hide_user_profiles_from_public`, emphasizing it doesn’t fully block aggregated stats exposure through the API [read more](https://meta.discourse.org/t/-/397252/2?silent=true).

- @awesomerobot provided a crisp explanation for why the new Meta Branded theme appears to override chosen palettes (“theme overrides any selected color palette”) [read more](https://meta.discourse.org/t/-/397246/36?silent=true), and separately kicked off implementation work for adding **post IDs** to data exports [read more](https://meta.discourse.org/t/-/397074/2?silent=true).

* * *

Purple took center stage yesterday—may your buttons be rounded, your palettes intentional, and your feedback threads delightfully on-topic.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [1 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/759 "2026-03-01T05:02:11Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New posts (last 24h): 38**
- **New topics (last 24h): 5**
- **Where the conversation happened:** UX polish and editor/linking quirks (e.g. [read more](https://meta.discourse.org/t/-/397335/1?silent=true), [read more](https://meta.discourse.org/t/-/397345/1?silent=true)), plus admin/support edge-cases (e.g. [read more](https://meta.discourse.org/t/-/397334/1?silent=true), [read more](https://meta.discourse.org/t/-/397350/1?silent=true)).

**Top users (posts / likes in the last 24h)**

| User | Posts | Likes |
| --- | --- | --- |
| @RGJ | 4 | 14 |
| @Canapin | 5 | 13 |
| @Moin | 6 | 11 |
| @jack222 | 2 | 4 |
| @shortmort37 | 1 | 3 |
| @awesomerobot | 1 | 2 |
| @NateDhaliwal | 2 | 2 |
| @Luna_Mora | 1 | 2 |
| @k4rtik | 1 | 1 |
| @mcmcclur | 1 | 1 |

**Team activity snapshot (posts / likes)**

| Team user | Posts | Likes |
| --- | --- | --- |
| @awesomerobot | 1 | 2 |
| @mcwumbly | 1 | 1 |
| @sam | 1 | 0 |

* * *

## Interesting Topics

### #ux

- @RGJ flagged that **category mentions can trigger the “repeated link” warning** (even when you’re just referencing something like #bug), and argued category/tag mentions should be excluded from that prompt; discussion branched into category/tag name collisions and whether internal duplicates are ever helpful ([read more](https://meta.discourse.org/t/-/397335/1?silent=true)).  
Related: @mcwumbly pointed at a “make subcategory links more concise” parallel thread ([read more](https://meta.discourse.org/t/-/397217/1?silent=true)).

- @Moin noticed **inconsistent opacity cues for hidden revisions** (opacity applied to the “previous version” and also the right-side heading, but _not_ the content) and asked whether the UI is behaving intentionally or accidentally ([read more](https://meta.discourse.org/t/-/397345/1?silent=true)).

### #bug

- @Luna_Mora reported a **#chat image viewer regression** : after uploading an image, clicking it won’t open full-screen on first view until chat is toggled (mini/full) or the page is refreshed; reproduces across Chromium/mobile ([read more](https://meta.discourse.org/t/-/397353/1?silent=true)).  
Related older report that was believed fixed: [read more](https://meta.discourse.org/t/-/352881/1?silent=true).

- The long-running iOS upload UX snag resurfaced: **iPad landscape mode still makes file uploads painful in the iOS app** , while Safari remains a workaround ([read more](https://meta.discourse.org/t/-/395144/1?silent=true)).

### #Support

- @Ethsim2 found that **bulk-adding email addresses to a group may still send invitation emails even when “Notify users” is unchecked** , raising the question of whether the invite flow for non-existing/staged users overrides that checkbox (and whether the UI is ambiguous or there’s a regression) ([read more](https://meta.discourse.org/t/-/397334/1?silent=true)).  
Related docs/discussion on invites: [read more](https://meta.discourse.org/t/-/124096/1?silent=true).

- @Jesse_Starks asked if there’s a **querystring parameter to sort group members by `last_seen_at` descending** (the view loads ascending by default); @NateDhaliwal noted an `asc` filter in code but couldn’t get it working via URL ([read more](https://meta.discourse.org/t/-/397350/1?silent=true)).

- In a Chinese-language support thread, @AkarinLiu shared a practical deliverability workaround: **switching from Aliyun mail push to Brevo** after Outlook delivery problems / IP rejection ([read more](https://meta.discourse.org/t/-/396468/1?silent=true)).

### #support:migration

- A large-scale migration thread (800k topics / 12k DAU) continued: @jack222 confirmed they’re moving off a privately developed PHP forum system and reiterated why Discourse feels like a better long-term fit, sparking community encouragement around support quality and forward momentum ([read more](https://meta.discourse.org/t/-/397151/9?silent=true)).

### #Dev

- A Chinese-language Dev discussion on “AI dev skills” drew concrete field notes from @Canapin: Claude can help build plugins, but _minimal coding skill is still important_, especially to catch security flaws; they linked both an AI-dev experience thread and a mostly-AI-written plugin they audited heavily before publishing ([read more](https://meta.discourse.org/t/-/397330/4?silent=true)).  
Related: AI dev experience thread ([read more](https://meta.discourse.org/t/-/394773/1?silent=true)) and the “Topic Gallery” plugin showcase ([read more](https://meta.discourse.org/t/-/394953/1?silent=true)).

- Theme creation “best practices” got a +1 watcher: @stephtara echoed they expect to hit similar issues and are tracking the thread for guidance ([read more](https://meta.discourse.org/t/-/397315/2?silent=true)).

### #Developer Guides

- In the #reference #theme-guides “Alternative icons” guide, @Canapin asked how to find the **complete set of icons used by core** (noting missing mappings like `palette`), and @Moin pointed to `svg_sprite.rb` plus suggested repo searching for registered icons—especially across plugins and #included-in-core extensions ([read more](https://meta.discourse.org/t/-/206693/16?silent=true)).

### #customization:theme component

- “Custom Header Links” support: a theme-component update error turned out to mirror an older Matrix URL issue; @Moin suggested the permalink workaround and it solved @raghukamath’s problem ([read more](https://meta.discourse.org/t/-/90588/219?silent=true)).  
Related prior report: [read more](https://meta.discourse.org/t/-/352433/1?silent=true).

### #customization:plugin

- In “Private Topics Plugin”, @RGJ shipped a fix (noting the prior warning was harmless) after a report came in—quick maintenance on an established plugin thread ([read more](https://meta.discourse.org/t/-/268646/103?silent=true)).

### #contribute:feature

- OpenGraph improvements got a positive field report: @shortmort37 said adding `og:image:width`, `og:image:height`, and `og:image:type` now integrates “quite nicely” with Facebook on the latest update ([read more](https://meta.discourse.org/t/-/395484/7?silent=true)).

- @k4rtik requested a way to **activate/confirm a changed email address from the Admin UI** , specifically for staged users who only interact via email and where Rails console access isn’t available ([read more](https://meta.discourse.org/t/-/396760/2?silent=true)).  
Related personalization discussion: using first names (and even vocatives) in greetings instead of usernames ([read more](https://meta.discourse.org/t/-/387763/2?silent=true)).

### #Site feedback

- Meta’s redesign feedback continued: @NateDhaliwal reported a visual bug where **wrapping tags onto a second line can clip the rounded corners** due to the tag field’s rounding/overflow interaction ([read more](https://meta.discourse.org/t/-/397246/37?silent=true)).

### #Site Management

- In the “Discourse AI - AI bot” how-to (#ai #ai-bot), @sam encouraged folks to open a dedicated topic with specific questions—confirming the feature is widely implemented, but troubleshooting is best handled case-by-case ([read more](https://meta.discourse.org/t/-/266012/185?silent=true)).  
Related AI ops thread: spam detection inconsistencies and testing conditions (e.g., mod vs new-user behavior) ([read more](https://meta.discourse.org/t/-/343541/29?silent=true)).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @awesomerobot weighed in on the “repeated link” warning + category/tag mention confusion, noting that a **#bug tag can still be useful in private subcategories** , but also floated that it may be worth cleaning up since it’s not used much ([read more](https://meta.discourse.org/t/-/397335/7?silent=true)).

- @mcwumbly supported **cleaning up the overlapping #bug tag** , and cross-linked a related UX thread about making inline links to subcategories more concise ([read more](https://meta.discourse.org/t/-/397335/8?silent=true); related: [read more](https://meta.discourse.org/t/-/397217/1?silent=true)).

- @sam replied in the Discourse AI bot how-to thread, confirming **many sites are using it** and steering follow-ups toward opening a dedicated topic with specifics for better support ([read more](https://meta.discourse.org/t/-/266012/185?silent=true)).

* * *

Yesterday’s vibe: if you didn’t get a “repeated link” warning while debating the fate of #bug and admiring shiny new icon sets, were you even on Meta?

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [2 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/760 "2026-03-02T05:02:38Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New posts (last 24h): 48**
- **New topics (last 24h): 7**

### Top posters & liked contributors

| User | Posts | Likes |
| --- | --- | --- |
| @sam | 12 | 4 |
| @Canapin | 3 | 4 |
| @RGJ | 3 | 4 |
| @pfaffman | 2 | 7 |
| @agemo | 2 | 2 |
| @Lou | 2 | 3 |
| @martin | 1 | 0 |
| @mcmcclur | 1 | 2 |
| @Moin | 1 | 2 |
| @merefield | 1 | 2 |
| @Andrew_Rowe | 1 | 2 |

### [@team](https://meta.discourse.org/groups/team?silent=true) quick glance

- Most active [@team](https://meta.discourse.org/groups/team?silent=true) members: **@sam (12 posts, 4 likes)** and **@martin (1 post)** (see details in the [@team](https://meta.discourse.org/groups/team?silent=true) section below).

### Also getting attention (more threads to skim)

A few other conversations that picked up replies today: heading anchor behavior in #Support ([read more](https://meta.discourse.org/t/-/397388/2?silent=true)), reply-button CSS effects in #Dev ([read more](https://meta.discourse.org/t/-/397387/1?silent=true)), strengthening age-check workflows in #customization:theme-component ([read more](https://meta.discourse.org/t/-/397002/14?silent=true)), category calendars vs embedded calendars in #Support with #calendar-and-event ([read more](https://meta.discourse.org/t/-/396716/6?silent=true)), the “Dumbcourse” pagination discussion in #customization:plugin ([read more](https://meta.discourse.org/t/-/395104/27?silent=true)), missing icons in “Alternative icons” in #Developer-Guides ([read more](https://meta.discourse.org/t/-/206693/19?silent=true)), category icon styling help request in #Support ([read more](https://meta.discourse.org/t/-/371966/4?silent=true)), defaulting filters for Topic Status Filter in #customization:theme-component ([read more](https://meta.discourse.org/t/-/111307/13?silent=true)), moderating plugin-collected feedback in #customization:plugin ([read more](https://meta.discourse.org/t/-/219002/54?silent=true)), and a return to the perennial markup debate in #contribute:feature ([read more](https://meta.discourse.org/t/-/133200/5?silent=true)).

* * *

## Interesting Topics

### #Announcements

- **Discourse AI credentials go centralized.** @sam announced a refactor that moves _all_ Discourse AI credentials (LLMs, embeddings, tools) into a central store—aiming to make tool distribution with secrets, credential rotation, and adding models significantly easier ([read more](https://meta.discourse.org/t/-/397408/1?silent=true); companion guide: [read more](https://meta.discourse.org/t/-/397407/1?silent=true)).

### #Site-Management

- **A deep-dive guide: “Managing AI credentials” (#ai, #how-to).** The new documentation explains how credentials are created once and referenced everywhere (LLMs/embeddings/tools), including lifecycle protections and API management ([read more](https://meta.discourse.org/t/-/397407/1?silent=true)).

- **Using Discourse AI to auto-move topics by timestamps (and whether AI is needed).** In a #rest-api + #ai management workflow discussion, @jdc20181 described moving “temporary ban” log topics after an expiration date, and @sam suggested using _topic timers_ (or core logging + [Data Explorer](https://meta.discourse.org/t/32566?silent=true) access) instead of reaching for AI automation ([read more](https://meta.discourse.org/t/-/397384/1?silent=true); @sam’s suggestion: [read more](https://meta.discourse.org/t/-/397384/2?silent=true)).

### #bug

- **Chat uploads: first image click not opening fullscreen (#chat).** @sam asked for a re-test on latest after submitting a patch, implying the issue should now be addressed in current builds ([read more](https://meta.discourse.org/t/-/397353/2?silent=true)).

- **Anonymous (and non-staff) styleguide crash.** @sam noted the issue impacts more than anonymous users and linked an upstream fix in core via a PR ([read more](https://meta.discourse.org/t/-/397317/2?silent=true)).

- **“Upcoming changes” enablement error (#translation, #upcoming-changes).** @martin posted a fix link for the problem (via a core PR), unblocking admins experimenting with the upcoming-changes flow ([read more](https://meta.discourse.org/t/-/395881/29?silent=true)).

- **Tag suggestion popup error when a topic already has tags (#tags, #ai).** @sam linked the core fix PR and reclassified it as a “bug” due to an obvious code flaw ([read more](https://meta.discourse.org/t/-/396857/4?silent=true)).

### #ux

- **Select-kit dropdown contrast problems (accessibility).** In an #accessibility discussion, @BrettH traced “invisible text/icons on selection” to an older custom palette missing newer `selected`/`hover` colors, and suggested explicitly defining those colors (plus a thought: could future fallbacks consider text contrast?) ([read more](https://meta.discourse.org/t/-/396146/11?silent=true)).

- **German UI alignment issues in LLM cost configuration (#ai).** @sam flagged that 4 columns may be too cramped (even in English) and suggested restructuring the inputs into 3 rows for better spacing and layout resilience across locales ([read more](https://meta.discourse.org/t/-/396948/2?silent=true)).

### #Support

- **Will Discourse ever get pagination? (infinite scroll vs page numbers).** The recurring pagination request resurfaced, with @agemo asking for an admin/user option ([read more](https://meta.discourse.org/t/-/355213/19?silent=true)), @merefield pointing to the “Dumbcourse” plugin as an option today ([read more](https://meta.discourse.org/t/-/355213/20?silent=true); plugin: [read more](https://meta.discourse.org/t/-/395104/27?silent=true)), and @mcmcclur arguing pagination may become necessary—citing broader concerns about infinite scroll and addictive design patterns ([read more](https://meta.discourse.org/t/-/355213/21?silent=true)).

- **NodeBB (MongoDB) → Discourse importer error: `post` is nil.** While migrating from NodeBB 4.9.x, @Twissell hit a crash in `NodeBB::Mongo#post` during post import ([read more](https://meta.discourse.org/t/-/126553/17?silent=true); output context: [read more](https://meta.discourse.org/t/-/126553/19?silent=true)). @pfaffman diagnosed the immediate cause—`post` is `nil`—and suggested the importer isn’t reading post data correctly (likely around key lookup / retrieval), while setting expectations that importer support is limited and may require deeper hands-on debugging ([read more](https://meta.discourse.org/t/-/126553/20?silent=true)).

- **Error 500 when enabling plugins: “asset not found” + possible mounted-volume gotcha (#hosting, #unsupported-install).** @sistason reported consistent 500s on plugin activation with a Propshaft asset resolution error referencing `plugins/discourse-translator.js` ([read more](https://meta.discourse.org/t/-/397370/1?silent=true)). @RGJ noted those plugins work on 2026.1.1 for their clients and suggested the mounted docker volume to `/var/www/discourse/plugins` might be the culprit ([read more](https://meta.discourse.org/t/-/397370/3?silent=true)). (Related translator reference: [read more](https://meta.discourse.org/t/-/397370/2?silent=true)).

- **Sorting group members by “last seen” via querystring.** @Moin linked a prior thread for admins trying to force descending last-seen ordering when viewing group members—highlighting this as a repeat pain point ([read more](https://meta.discourse.org/t/-/397350/3?silent=true)).

### #contribute:feature

- **Collapsible category calendar (#calendar-and-event).** @Lou proposed making the category-top Events calendar optionally collapsed by default to reduce vertical space, ideally remembering user preference per category ([read more](https://meta.discourse.org/t/-/397381/1?silent=true)). @nathank echoed the usability issue and pointed to a related request around toggling calendars when browsing event lists ([read more](https://meta.discourse.org/t/-/397381/2?silent=true)). (Context from the support side: [read more](https://meta.discourse.org/t/-/396716/6?silent=true)).

- **When an AI model hits limits, fade it out + offer upgrade path (#subscriptions, #ai).** @sam responded with a broader product direction: reduce decision paralysis by moving toward a “just talk to the robot” experience where the system selects the best model automatically—while also questioning what “upgrade subscription” means in practice (instance plan vs admin configuration changes, etc.) ([read more](https://meta.discourse.org/t/-/396047/2?silent=true)).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- **@sam shipped/announced a major Discourse AI improvement: centralized credentials.** The announcement frames this as solving long-standing tool distribution + secret management issues, and points to the new admin guide ([read more](https://meta.discourse.org/t/-/397408/1?silent=true); documentation: [read more](https://meta.discourse.org/t/-/397407/1?silent=true)).

- **@sam nudged an automation use case back toward core tools (timers/logs) rather than AI.** In the “move topics by timestamp” thread, @sam recommended using topic timers to auto-move topics after time passes, and suggested leveraging existing ban/log history via [Data Explorer](https://meta.discourse.org/t/32566?silent=true) instead of custom AI flows ([read more](https://meta.discourse.org/t/-/397384/2?silent=true)).

- **@sam coordinated multiple fixes and follow-ups across bugs/UX:**

- **@sam set expectations (and offered a UX idea) on delayed NSFW scanning.** While noting the feature isn’t supported _yet_, he warned about potential LLM costs from “upload-button playing,” and floated an _“Awaiting content scanning” placeholder_ approach as a possible design direction ([read more](https://meta.discourse.org/t/-/397401/2?silent=true)).

- **@sam reinforced Meta’s bot policy in two related OpenClaw integration threads.** He cited `llms.txt` and requested confirmation that the “skill” respects the rule that AI systems must not create accounts or post content ([read more](https://meta.discourse.org/t/-/397239/5?silent=true); Chinese-language counterpart: [read more](https://meta.discourse.org/t/-/396086/4?silent=true)).

- **@sam weighed in on “model limits UI” with a long-term direction: hide complexity for most users.** Rather than surfacing upgrade prompts directly on model selection, he suggested moving toward a system that routes requests to the best model automatically, and asked clarifying questions about what “upgrade subscription” should mean ([read more](https://meta.discourse.org/t/-/396047/2?silent=true)).

- **@sam added practical guidance on tokenizers for AI models.** He noted many coding agents simply estimate tokens, and that `cl100k` is “plenty fine” for most LLM use cases even with slightly different tokenizers ([read more](https://meta.discourse.org/t/-/391238/4?silent=true)).

- **@martin provided a fix for the “upcoming changes” enablement issue.** He linked the PR addressing the bug in the #translation / #upcoming-changes area ([read more](https://meta.discourse.org/t/-/395881/29?silent=true)).

* * *

_That’s a wrap: yesterday Meta managed to wrangle secret keys, tame a few bugs, and still found time to rekindle the eternal “pagination vs infinite scroll” debate._

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [3 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/761 "2026-03-03T05:02:18Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

> **In the last 24 hours:**  **82** new posts across **14** new topics.  
> Much of the conversation clustered around responsive UX changes, AI/admin polish, and self-hosting ops questions—see discussions like [AI credentials](https://meta.discourse.org/t/-/397408/2?silent=true), [responsive layouts](https://meta.discourse.org/t/-/397463/2?silent=true), and [hiding AI reports when disabled](https://meta.discourse.org/t/-/397487/2?silent=true).

### Top users (posts / likes)

| User | Posts | Likes |
| --- | --- | --- |
| @awesomerobot | 7 | 20 |
| @Lilly | 2 | 18 |
| @Moin | 7 | 15 |
| @discojan | 5 | 13 |
| @derek | 2 | 7 |
| @Falco | 3 | 6 |
| @featheredtoast | 2 | 5 |
| @RGJ | 1 | 5 |
| @merefield | 3 | 5 |
| @Luna_Mora | 1 | 5 |

### A few threads that saw notable momentum

- Responsive design tradeoffs and capability-based UI logic: [No more switchable mobile/desktop layouts?](https://meta.discourse.org/t/-/397463/2?silent=true) and the follow-up implementation details from @awesomerobot ([read more](https://meta.discourse.org/t/-/397463/5?silent=true)).

- AI/admin UX cleanup continued, including a confirmed dashboard bug: [Don’t show AI reports if AI is not enabled](https://meta.discourse.org/t/-/397487/2?silent=true) plus related dashboard documentation friction in [Admin dashboard report reference guide](https://meta.discourse.org/t/-/240233/41?silent=true) and the “Search or create…” control critique in [Site settings… that don’t search](https://meta.discourse.org/t/-/397503/1?silent=true).

- Several “small but sharp” UI issues and fixes landed or were queued: [Suggested/Related tab underline misalignment](https://meta.discourse.org/t/-/397448/1?silent=true), [hidden revision opacity oddities](https://meta.discourse.org/t/-/397345/2?silent=true), and [content translation enabled indicator](https://meta.discourse.org/t/-/397115/2?silent=true).

- Self-hosting/admin ops questions kept flowing, from mail-receiver config nuance in [Mail-Receiver direct delivery guide](https://meta.discourse.org/t/-/49487/536?silent=true) to security basics like [fail2ban guidance](https://meta.discourse.org/t/-/397473/1?silent=true) and apt warnings in [legacy trusted.gpg keyring](https://meta.discourse.org/t/-/397470/1?silent=true).

* * *

## Interesting Topics

### #Announcements

- @Lilly celebrated easier key rotation and model management after **AI credentials** shipped, and also flagged a mobile layout hiccup; @derek followed up with a mobile stacking fix in the same announcement thread ([read more](https://meta.discourse.org/t/-/397408/5?silent=true)).

### #ux

- A key shift toward width-based responsiveness was confirmed in **No more switchable mobile/desktop layouts?** —@featheredtoast outlined why the explicit toggle is going away ([read more](https://meta.discourse.org/t/-/397463/2?silent=true)), while @awesomerobot shared capability-aware template patterns to replace initializer-time device logic ([read more](https://meta.discourse.org/t/-/397463/5?silent=true)).

- **The underline indicator below “Suggested” and “Related” tabs** was reported as vertically misaligned; @awesomerobot noted upcoming tab changes should address it ([read more](https://meta.discourse.org/t/-/397448/2?silent=true)).

- Admin setting UX got a spotlight: **Site settings with “Search or create…” that don’t search** argues the hint text is misleading when entries require exact manual keys (great companion to dashboard docs discussion in [Admin dashboard report reference guide](https://meta.discourse.org/t/-/240233/41?silent=true)) ([read more](https://meta.discourse.org/t/-/397503/1?silent=true)).

- RTL polish request: **External link icon not RTL** flags a directionality issue when using featured links in titles ([read more](https://meta.discourse.org/t/-/397432/1?silent=true)).

- A subtle styling inconsistency in moderation history UI was diagnosed: **Understanding opacity in hidden revisions** appears to be caused by fragile CSS selectors, with a fix moving toward explicit class targeting ([read more](https://meta.discourse.org/t/-/397345/2?silent=true)).

### #bug

- **Don’t show AI reports if AI is not enabled** : emotion/admin AI reports still appear even with AI disabled; @sam confirmed it’s a bug and agreed they should be hidden when AI is off ([read more](https://meta.discourse.org/t/-/397487/2?silent=true)).

- **No indicator whether content translation is enabled or not** : missing/unclear UI affordance was acknowledged, with an update queued to improve it ([read more](https://meta.discourse.org/t/-/397115/2?silent=true)).

- **Chat image not opening full screen** appears resolved—@Luna_Mora reported the latest patch fixed the issue in testing ([read more](https://meta.discourse.org/t/-/397353/3?silent=true)).

### #contribute:feature

- **Saving translations by AI-helper as content localization** proposes letting moderators save an AI-helper translation directly into localization (mirroring the AI-helper “explain” workflow that can add footnotes) ([read more](https://meta.discourse.org/t/-/397477/1?silent=true)).

- **Custom User Field Required for All, but only Editable ONCE** highlights a tricky onboarding gap for OAuth/SSO signups and proposes “editable-until-filled” logic so “required for all” fields can be locked after first completion ([read more](https://meta.discourse.org/t/-/397456/1?silent=true)).

- Calendar UX feedback continued: **Collapse category calendar** asks for an on/off or collapse control because the current always-on display affects both visuals and usability ([read more](https://meta.discourse.org/t/-/397381/3?silent=true)).

### #Support

- **Size restrictions on videos?** asks what levers admins really have for self-hosted screencast uploads beyond extension allowlists and max upload size settings ([read more](https://meta.discourse.org/t/-/397413/1?silent=true)).

- **Recommended fail2ban configuration?** surfaces a common “is `apt install fail2ban` enough?” question—useful for admins spotting the mention in [official install](https://meta.discourse.org/t/142537?silent=true) docs ([read more](https://meta.discourse.org/t/-/397473/1?silent=true)).

### #Self-Hosting

- **Docker compose addition** : @featheredtoast clarified there’s still no officially supported compose template, but shared a maintained personal template for those who want to experiment ([read more](https://meta.discourse.org/t/-/395815/2?silent=true)).

### #blog

- @Falco published a companion discussion for **Three Ways to Deploy AI in Community Platforms (and Why Choice Matters)**, arguing communities need flexible AI integration approaches rather than a single hardcoded provider path ([read more](https://meta.discourse.org/t/-/397498/1?silent=true)).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @awesomerobot was everywhere in UX triage: they explained the rationale and offered capability-based coding patterns in [No more switchable mobile/desktop layouts?](https://meta.discourse.org/t/-/397463/5?silent=true), asked for concrete examples and scope on community translation quality in [Request to be Arabic translation reviewer](https://meta.discourse.org/t/-/397444/4?silent=true), and queued fixes/changes for UI inconsistencies like [hidden revision opacity selectors](https://meta.discourse.org/t/-/397345/2?silent=true) and the [Suggested/Related underline indicator](https://meta.discourse.org/t/-/397448/2?silent=true). They also acknowledged a forthcoming improvement for translation state visibility in [No indicator whether content translation is enabled](https://meta.discourse.org/t/-/397115/2?silent=true).

- @derek responded quickly to real-world UI feedback: after @Lilly pointed out a mobile viewport issue in [Announcing AI credentials](https://meta.discourse.org/t/-/397408/3?silent=true), @derek shipped a “stack the labels” improvement on mobile ([read more](https://meta.discourse.org/t/-/397408/5?silent=true)). Separately, they proposed a clearer layout approach for localized admin forms in [Field alignment issues in LLM cost configuration in German](https://meta.discourse.org/t/-/396948/3?silent=true).

- @featheredtoast confirmed the product direction on responsive design in [No more switchable mobile/desktop layouts?](https://meta.discourse.org/t/-/397463/2?silent=true), and later set expectations around Docker Compose support while providing a practical stopgap template in [Docker compose addition](https://meta.discourse.org/t/-/395815/2?silent=true).

- @Falco mixed product guidance with builder-energy: they suggested using topic custom fields and form templates (and even new workflow filters) to solve automation needs in [Creating a system to move topics based on timestamp/criteria](https://meta.discourse.org/t/-/397384/4?silent=true), then pointed to a visualization option via [Kanban Board](https://meta.discourse.org/t/-/397384/6?silent=true). They also kicked off the broader AI strategy discussion in [Three Ways to Deploy AI…](https://meta.discourse.org/t/-/397498/1?silent=true).

- @chapoi continued tightening admin reporting UX by adding clearer units/labels to charts in [Units for reports](https://meta.discourse.org/t/-/205974/11?silent=true), and pointed feedback back toward the ongoing umbrella thread referenced there ([read more](https://meta.discourse.org/t/-/205974/11?silent=true)).

- @sam confirmed an admin dashboard issue and aligned behavior with expectations: AI reports should not display when AI is disabled in [Don’t show AI reports if AI is not enabled](https://meta.discourse.org/t/-/397487/2?silent=true).

- @supermathie dug into a self-hosting report about YAML quoting and mail-receiver behavior, asking for deeper reproduction details in the long-running [Mail-Receiver direct-delivery incoming email guide](https://meta.discourse.org/t/-/49487/537?silent=true).

* * *

Yesterday’s theme: _make it responsive, make it clearer, and make sure the AI bits behave themselves_—now if only every underline indicator could stay perfectly aligned while your folding phone unfolds.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [4 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/762 "2026-03-04T05:02:26Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

**In the last 24 hours (2026-03-03 → 2026-03-04), Meta recorded 136 new posts across 19 new topics** (see the full set of new threads below).

### Top contributors (posts / likes)

| User | Posts | Likes | Recent reference |
| --- | --- | --- | --- |
| @Moin | 16 | 29 | Suggested using a table to preserve spacing in posts: [read more](https://meta.discourse.org/t/-/397551/5?silent=true) |
| @gerhard | 3 | 12 | Shared plans to improve translation review workflows: [read more](https://meta.discourse.org/t/-/397444/7?silent=true) |
| @Falco | 7 | 11 | Flagged UX issues with chat pinned messages visibility: [read more](https://meta.discourse.org/t/-/397571/4?silent=true) |
| @chapoi | 7 | 10 | Confirmed the mobile/desktop layout toggle is fully removed: [read more](https://meta.discourse.org/t/-/397463/10?silent=true) |
| @tobiaseigen | 3 | 9 | Reproduced a chat composer “rounding eats text” issue: [read more](https://meta.discourse.org/t/-/397246/39?silent=true) |
| @lindsey | 3 | 8 | Announced new chat pinning functionality: [read more](https://meta.discourse.org/t/-/397571/1?silent=true) |
| @Canapin | 7 | 8 | Helped clarify rebuild/update steps for self-hosters: [read more](https://meta.discourse.org/t/-/397520/7?silent=true) |
| @vin100 | 5 | 8 | Reported and resolved a self-hosting update crash: [read more](https://meta.discourse.org/t/-/397520/1?silent=true) |
| @ToddZ | 5 | 7 | Shared a CSS-based workaround for custom word spacing: [read more](https://meta.discourse.org/t/-/397551/7?silent=true) |
| @manuel | 3 | 6 | Reproduced and began investigating the chat rounding issue on mobile: [read more](https://meta.discourse.org/t/-/397246/42?silent=true) |

### New topics opened (19)

- #Announcements / #chat — [Pin chat messages for increased visibility](https://meta.discourse.org/t/-/397571/1?silent=true)

- #bug / #onebox — [Impossible to prevent x.com oneboxes (and they’re broken)](https://meta.discourse.org/t/-/397516/1?silent=true)

- #bug — [Whispers only temporarily bump topics](https://meta.discourse.org/t/-/397588/1?silent=true)

- #bug / #file-management — [phpBB import problem](https://meta.discourse.org/t/-/397586/1?silent=true)

- #contribute:feature — [Honor the “asc” querystring parameter on group sort](https://meta.discourse.org/t/-/397541/1?silent=true)

- #contribute:feature / #badges — [Skip unchanged users for badge mass edit](https://meta.discourse.org/t/-/397539/1?silent=true)

- #contribute:feature / #chat — [Show pinned messages at top of chat instead of in separate page](https://meta.discourse.org/t/-/397519/1?silent=true)

- #contribute:feature / #translation — [Use CHATGPT for translating the forum](https://meta.discourse.org/t/-/285776/2?silent=true)

- #contribute:feature — [Patterns](https://meta.discourse.org/t/-/397582/1?silent=true)

- #Support — [Extra spaces within text](https://meta.discourse.org/t/-/397551/1?silent=true)

- #Support / #Customization — [Translation keys reference](https://meta.discourse.org/t/-/397547/1?silent=true)

- #Support — [How to make it easy to specify if content is human-written, ai-assisted, or ai-generated?](https://meta.discourse.org/t/-/397548/1?silent=true)

- #Support / #groups — [Nested groups or auto-sync membership: mention all sub-group members with a single @mention](https://meta.discourse.org/t/-/397577/1?silent=true)

- #Support / #activitypub — [Quote Boost support?](https://meta.discourse.org/t/-/397569/1?silent=true)

- #Support — [Carte de sujet n’est pas visible](https://meta.discourse.org/t/-/397562/1?silent=true)

- #Support — [Add terms when make new topic](https://meta.discourse.org/t/-/397581/1?silent=true)

- #Site feedback / #tags — [Misspelled tag](https://meta.discourse.org/t/-/397587/1?silent=true)

- #contribute:translations — [Links to Translation Resources and Language Topics](https://meta.discourse.org/t/-/397558/1?silent=true)

- #ux / #ai — [The title suggester button is placed outside of the title field when editing a translated title](https://meta.discourse.org/t/-/397553/1?silent=true)

### Continuing conversations that stayed active (not necessarily new)

- #ux / #mobile — [No more switchable mobile/desktop layouts?](https://meta.discourse.org/t/-/397463/8?silent=true)

- #customization:plugin — [Resenha - Add Discord-style Voice Rooms to Your Community](https://meta.discourse.org/t/-/389056/35?silent=true)

- #customization:theme component / #sidebar — [Discourse Sidebar Menu Reorder](https://meta.discourse.org/t/-/394049/8?silent=true)

- #ux / #ai — [The underline indicator below the “Suggested” and “Related” tabs](https://meta.discourse.org/t/-/397448/3?silent=true)

- #customization:theme component / #tag-icons — [Tag Icons](https://meta.discourse.org/t/-/109757/162?silent=true)

- #customization:theme component / #mobile — [Sticky Avatars for Mobile](https://meta.discourse.org/t/-/225657/5?silent=true)

- #bug / #ai-sentiment — [Don’t show AI reports if AI is not enabled](https://meta.discourse.org/t/-/397487/3?silent=true)

- #Support — [How to Understand the Request Revision Feature](https://meta.discourse.org/t/-/397258/4?silent=true)

- #contribute:feature / #content-localization — [Feature request: Limit topic translation to specific categories](https://meta.discourse.org/t/-/392993/2?silent=true)

- #Self-hosting — [CSS compile (MiniRacer?) error while rebuilding app](https://meta.discourse.org/t/-/396722/4?silent=true)

## Interesting Topics

### #Announcements

- Discourse chat gained **message pinning** (including a pinned-messages list and “unread pins” indicator), but early feedback suggested the UI may be _too subtle_ and missing a visible date in the pinned list: [read more](https://meta.discourse.org/t/-/397571/1?silent=true) and [read more](https://meta.discourse.org/t/-/397571/4?silent=true)

### #Site feedback

- The ongoing **Meta Branded redesign** feedback thread surfaced a chat composer rendering bug where rounded corners can “eat” the first/last line when typing in long messages (especially in the drawer): [read more](https://meta.discourse.org/t/-/397246/38?silent=true) and [read more](https://meta.discourse.org/t/-/397246/42?silent=true)

### #bug

- Blocking `x.com` / `twitter.com` via `blocked_onebox_domains` appears ineffective, and **X/Twitter oneboxes are rendering broken HTML regardless of configuration** , raising questions about onebox handling and domain blocks: [read more](https://meta.discourse.org/t/-/397516/1?silent=true)

- A regression (or long-standing edge case) was reported where **whispers bump topics only until refresh** , then Latest reverts to the last public activity time: [read more](https://meta.discourse.org/t/-/397588/1?silent=true)

- A small but satisfying housekeeping fix: the misspelled tag `#file-managment` was corrected to **#file-management** : [read more](https://meta.discourse.org/t/-/397587/1?silent=true) and [read more](https://meta.discourse.org/t/-/397587/2?silent=true)

- A phpBB importer edge case: posts containing multiple _different_ attachments with the same `real_filename` can become **duplicate images after import** , suggesting the converter should key off the hashed “physical filename” instead: [read more](https://meta.discourse.org/t/-/397586/1?silent=true)

### #ux

- The removal of the old **mobile/desktop layout toggle** continues to ripple through theme expectations—confirmation arrived that it’s not merely a UI change, but the _underlying toggling structure_ has been removed: [read more](https://meta.discourse.org/t/-/397463/10?silent=true)

- A UI bug/side-effect around the **Suggested/Related tabs** showed up on mobile (tabs disappeared entirely), with a fix already in motion: [read more](https://meta.discourse.org/t/-/397448/3?silent=true) and [read more](https://meta.discourse.org/t/-/397448/4?silent=true)

- AI Helper UI polish: the **title suggester “star” button** ends up positioned outside the title field when editing a translated title, likely due to the “Editing English translation” header: [read more](https://meta.discourse.org/t/-/397553/1?silent=true)

### #Support

- Formatting problem of the day: users wanting **persistent extra spacing** in prose found the most “Discourse-native” answer was to switch to a Markdown table (with optional CSS approaches for special cases): [read more](https://meta.discourse.org/t/-/397551/1?silent=true) and [read more](https://meta.discourse.org/t/-/397551/5?silent=true)

- Moderation/content integrity: a community asked how to add a per-reply **“content origin” selector** (_human-written / AI-assisted / AI-generated_)—discussion explored tag limitations (topic-only) and theme-component/plugin approaches: [read more](https://meta.discourse.org/t/-/397548/1?silent=true)

- A practical groups/mentions scaling issue: the need for a “group-of-groups” to @mention many working groups at once prompted suggestions to use dynamic membership approaches (rather than manual syncing): [read more](https://meta.discourse.org/t/-/397577/1?silent=true)

### #Self-hosting

- A self-hosted update failure traced back to a **Ruby version mismatch** (`Gemfile` expects ~\> 3.4) and a classic “wrong directory” pitfall—resolved by running rebuild steps from the proper location: [read more](https://meta.discourse.org/t/-/397520/1?silent=true) and [read more](https://meta.discourse.org/t/-/397520/4?silent=true)

### #contribute:feature

- A small-but-impactful tweak: Discourse will now honor `asc=false` when sorting group members (e.g. `order=last_seen_at`), unblocking “most recently seen first” group lists: [read more](https://meta.discourse.org/t/-/397541/1?silent=true) and [read more](https://meta.discourse.org/t/-/397541/2?silent=true)

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @lindsey shipped and documented the new **chat message pinning** experience, including roles/permissions and how pinned messages are surfaced in-channel: [read more](https://meta.discourse.org/t/-/397571/1?silent=true). They also discussed whether pinned-message entries should display a full date in the pins UI: [read more](https://meta.discourse.org/t/-/397571/5?silent=true). Finally, they updated the older “ability to pin messages in chat” feature thread to mark it as completed and point folks to the announcement: [read more](https://meta.discourse.org/t/-/276793/12?silent=true)

- @Falco pressure-tested the chat pin UX, calling out that pins can be _easy to miss_ and that the pinned list lacks a clear “how old is this?” date signal: [read more](https://meta.discourse.org/t/-/397571/4?silent=true) and [read more](https://meta.discourse.org/t/-/397571/7?silent=true). They also flagged a mobile regression where Suggested/Related tabs disappeared and asked if it was related to ongoing work: [read more](https://meta.discourse.org/t/-/397448/3?silent=true)

- @j.jaffeux explained why pinned items currently don’t show a hover-date (the row is intentionally “fully clickable” instead), and suggested showing a full date as a possible improvement: [read more](https://meta.discourse.org/t/-/397571/6?silent=true)

- @manuel investigated a **chat composer clipping** issue in the Meta Branded refresh thread, requested reproduction details, and confirmed they could reproduce it on mobile (with follow-up planned): [read more](https://meta.discourse.org/t/-/397246/40?silent=true) and [read more](https://meta.discourse.org/t/-/397246/42?silent=true). Separately, they advised on building a “simple theme,” recommending starting points like the Canvas Theme Template and warning about layout inconsistencies requiring exceptions: [read more](https://meta.discourse.org/t/-/397315/3?silent=true)

- @chapoi clarified that the mobile/desktop toggle removal is structural (not just hidden in the sidebar), which impacts older customization approaches: [read more](https://meta.discourse.org/t/-/397463/10?silent=true). They also guided formatting and CSS possibilities in the “extra spaces” thread: [read more](https://meta.discourse.org/t/-/397551/2?silent=true), and closed out an admin reporting/plugin visibility complaint by pointing to the relevant reporting changes thread: [read more](https://meta.discourse.org/t/-/397487/3?silent=true)

- @awesomerobot delivered a fix for group sorting so `asc=false` works as expected (with a PR linked for tracking): [read more](https://meta.discourse.org/t/-/397541/2?silent=true). They also confirmed the missing Suggested/Related tabs on mobile were related and noted a fix was incoming: [read more](https://meta.discourse.org/t/-/397448/4?silent=true). In moderation tooling, they asked clarifying questions about an unclear “request revision” approval UI so it can be improved: [read more](https://meta.discourse.org/t/-/397258/4?silent=true)

- @gerhard reported that a translation removal issue was found and fixed (with translations expected to be restored), linking the underlying PR for visibility: [read more](https://meta.discourse.org/t/-/395098/9?silent=true). They also gave concrete guidance to new translation reviewers and outlined a plan to add tooling to “remove approvals when new suggestions arrive” so strings re-enter review intentionally: [read more](https://meta.discourse.org/t/-/397444/7?silent=true). Finally, they explained how a release rollover sync issue affected translation files and why the earlier fix should address it: [read more](https://meta.discourse.org/t/-/397146/2?silent=true)

- @mcwumbly handled quick taxonomy cleanup by fixing the misspelled tag to #file-management: [read more](https://meta.discourse.org/t/-/397587/2?silent=true)

- @nat acknowledged the recurring request to limit topic translation by category and indicated they were going to investigate prior related requests/workarounds: [read more](https://meta.discourse.org/t/-/392993/3?silent=true)

_That’s a wrap—may your chat pins be more visible than a broken [x.com](http://x.com) onebox, and your whispers keep their bump after refresh._

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [5 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/763 "2026-03-05T05:02:40Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New activity (last 24h):**  **119** new posts across **15** new topics
- **Top contributors (posts / likes):**
  - **@Moin** — **16** posts, **22** likes
  - **@mcwumbly** — **10** posts, **15** likes
  - **@RGJ** — **3** posts, **14** likes
  - **@NateDhaliwal** — **9** posts, **12** likes
  - **@pangbo** — **3** posts, **9** likes
  - **@supermathie** — **7** posts, **9** likes
  - **@sam** — **2** posts, **8** likes
  - **@Jagster** — **3** posts, **7** likes
  - **@Canapin** — **1** post, **7** likes
  - **@Andrew_Rowe** — **5** posts, **7** likes

* * *

## Interesting Topics

### #contribute:site-feedback

- @mcwumbly kicked off an **experiment to coordinate “content gardening”** (retagging, deduping, marking solutions, and general housekeeping) in a single coordination hub: [read more](https://meta.discourse.org/t/-/397606/1?silent=true). The thread quickly turned practical—e.g., how documentation topics should consistently use the “document type” tags described in the documentation tagging guidelines [read more](https://meta.discourse.org/t/-/309628/1?silent=true), and how “Upcoming Changes” topics should be tagged consistently [read more](https://meta.discourse.org/t/-/392894/1?silent=true) / [read more](https://meta.discourse.org/t/-/395390/1?silent=true). It also surfaced real permission constraints (TL3 limitations in docs categories) and a workaround was implemented to unblock retagging work [read more](https://meta.discourse.org/t/-/397606/31?silent=true).

- Tag hygiene had its own mini-spotlight: a **misspelled tag** and confusion between similar tags (e.g. `#phpbb` variants) were raised by @NateDhaliwal and contextualized by @Moin as likely a tag-group restriction side effect: [read more](https://meta.discourse.org/t/-/397587/3?silent=true). The downstream impact matters for discoverability—especially as migration/import threads keep coming up (e.g. phpBB importer edge cases) [read more](https://meta.discourse.org/t/-/397586/1?silent=true).

- @NateDhaliwal noticed Meta’s **Suggested/Related topics UX** seemed to have regressed (showing “Suggested” only): [read more](https://meta.discourse.org/t/-/397599/1?silent=true). They then linked it to an already-tracked UI issue and an unmerged fix, pointing to the earlier discussion and patch reference [read more](https://meta.discourse.org/t/-/397448/3?silent=true) / [read more](https://meta.discourse.org/t/-/397448/4?silent=true).

- The long-running conversation about **inconsistent “Solved / Completed / Fixed” usage** got pulled back into the spotlight when the new gardening hub was announced as an action-oriented place to improve consistency: [read more](https://meta.discourse.org/t/-/361193/31?silent=true). In the same orbit, tag governance came up (e.g. whether `#fixed` vs `#completed` distinctions are worth it, and who should be allowed to apply them) [read more](https://meta.discourse.org/t/-/361193/33?silent=true), plus practical “when should staff mark solutions?” scenarios [read more](https://meta.discourse.org/t/-/397606/21?silent=true).

### #contribute:feature

- The **“AI Persona” → “AI Agent” rename** gained momentum again: @sam argued “nobody knows what an AI Persona is; everyone knows what an AI Agent is” [read more](https://meta.discourse.org/t/-/368198/8?silent=true), and @Falco agreed it’s overdue and should happen ASAP [read more](https://meta.discourse.org/t/-/368198/12?silent=true). @Moin highlighted the _translation workload_ and asked about more efficient bulk-updating approaches (especially on Crowdin) [read more](https://meta.discourse.org/t/-/368198/9?silent=true). (Related AI docs/ops threads continue to orbit this naming and discoverability problem, e.g. AI credentials announcements [read more](https://meta.discourse.org/t/-/397408/1?silent=true).)

- In calendar land, @Lou proposed **more configurable category calendar behavior** : default display mode (month/week) by device, and tighter admin controls—plus a database-level question about event description length constraints: [read more](https://meta.discourse.org/t/-/397617/1?silent=true). This builds directly on earlier requests about collapsing the category calendar [read more](https://meta.discourse.org/t/-/397381/1?silent=true), and sits adjacent to real-world workarounds users are building for private calendar consumption [read more](https://meta.discourse.org/t/-/393203/3?silent=true).

- A small-but-important UX polish request: @Moin asked if **sorting a group table** could update the URL (so the sort state is shareable/bookmarkable), similar to how `/latest` reflects state: [read more](https://meta.discourse.org/t/-/397541/3?silent=true).

### #Community Building

- The thread on **how to label human-written vs AI-assisted vs AI-generated content** continued with grounded admin experience: @Jagster argued tags aren’t visible enough and prefers _in-content indicators_ (e.g. `<details class='ai-quote'>…`) [read more](https://meta.discourse.org/t/-/397548/9?silent=true). @Canapin added a cautionary tale about communities feeling misled when they realize they’ve been “debating an AI,” underscoring why _clear disclosure_ matters socially, not just technically [read more](https://meta.discourse.org/t/-/397548/12?silent=true). (Related: the Quote Callouts component that can help make these disclosures more visible in-post [read more](https://meta.discourse.org/t/-/350962/1?silent=true).)

- In a lighter admin-tools vein, the perennial “what survey tool do you use?” thread got a nudge to include Discourse’s official option—@merefield suggested linking the **official Discourse Surveys plugin** into the conversation: [read more](https://meta.discourse.org/t/-/241829/9?silent=true), pointing to the surveys plugin topic directly [read more](https://meta.discourse.org/t/-/308679/1?silent=true).

### #Dev

- A classic dev question got a 2026 refresh: **“Interact with Discourse from Python?”** @remidm asked what the “current standard” is, and @supermathie replied that you can often skip wrappers and just use `requests`, leveraging the official API spec and tools like Postman to generate starter code [read more](https://meta.discourse.org/t/-/87543/20?silent=true). When asked about admin-only metrics like pageviews, they recommended using the browser Network tab to discover undocumented endpoints—basically “reverse-engineer the API” [read more](https://meta.discourse.org/t/-/87543/22?silent=true) (see also [read more](https://meta.discourse.org/t/-/20576/1?silent=true)). @pfaffman suggested an alternate route: query via [Data Explorer](https://meta.discourse.org/t/32566?silent=true) and pull results via API [read more](https://meta.discourse.org/t/-/87543/23?silent=true) (paired with [read more](https://meta.discourse.org/t/-/120063/1?silent=true)).

- Documentation drift was flagged: @pangbo noted that the **`api.modifyClass` example still uses legacy syntax** and likely needs updating in the Developer Guides context: [read more](https://meta.discourse.org/t/-/262064/26?silent=true).

### #bug

- @RGJ reported a clear behavioral mismatch: **topics by ignored users still appear in digest emails** , because `Topic.for_digest` doesn’t exclude ignored-user authors: [read more](https://meta.discourse.org/t/-/397622/1?silent=true). This is one of those “paper cut” bugs that directly affects user trust in preference controls.

- @pangbo hit an admin UX snag: **watched words “tag” actions error out** when adding automatic tagging rules, and they traced it to what looks like a front-end serialization problem: [read more](https://meta.discourse.org/t/-/397601/1?silent=true).

### #Support

- Passkeys looked shaky: @agr reported **passkey registration failures** (including HTTP 500s on `register_passkey.json`) across browsers and OSes, even though the hardware key works on [webauthn.io](http://webauthn.io); @supermathie reproduced errors on Meta and concluded browser privacy requirements have likely shifted since the feature’s initial implementation [read more](https://meta.discourse.org/t/-/397642/10?silent=true) (starting report: [read more](https://meta.discourse.org/t/-/397642/1?silent=true)).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- **@mcwumbly** launched and stewarded the new **content gardening coordination hub** [read more](https://meta.discourse.org/t/-/397606/1?silent=true), then implemented a pragmatic permissions workaround so TL3 users can help fix titles/tags in documentation categories without opening the floodgates [read more](https://meta.discourse.org/t/-/397606/31?silent=true). They also suggested enabling “notify OP and answerer when staff accepts an answer” as part of tidying up solved states [read more](https://meta.discourse.org/t/-/397606/33?silent=true), referencing the underlying feature setting discussion [read more](https://meta.discourse.org/t/-/58388/1?silent=true).

- **@supermathie** delivered hands-on dev support in the Python API thread—showing how to use the raw HTTP API and generated snippets [read more](https://meta.discourse.org/t/-/87543/20?silent=true), then explaining how to discover admin-only endpoints via Network tab inspection [read more](https://meta.discourse.org/t/-/87543/22?silent=true). They also investigated passkey failures on Meta and flagged likely WebAuthn/browser policy changes as the culprit [read more](https://meta.discourse.org/t/-/397642/10?silent=true).

- **@sam** pushed hard for clearer product language, advocating the **AI Persona → AI Agent** rename as an overdue “rip the band-aid off” move [read more](https://meta.discourse.org/t/-/368198/8?silent=true).

- **@Falco** backed the same rename decisively—_“better late than never”_—and called for doing it ASAP [read more](https://meta.discourse.org/t/-/368198/12?silent=true). They also jumped into a support request where non-admin users saw endless loading, asking for a site link to debug further [read more](https://meta.discourse.org/t/-/397644/5?silent=true).

- **@chapoi** handled quick-turn gardening actions (tagging updates requested in the hub), and clarified tag intent around documentation tag types [read more](https://meta.discourse.org/t/-/397606/5?silent=true).

- **@awesomerobot** started triage on the “non-admin users can’t load the homepage” report by requesting scope + [safe mode](https://meta.discourse.org/t/53504?silent=true) testing and browser console errors [read more](https://meta.discourse.org/t/-/397644/2?silent=true).

- **@featheredtoast** provided an update on the status of the `discourse/discourse` Docker image being officially supported/marked production-ready, noting internal hosting dependency blockers but also that they’re already using it successfully for hosted sites [read more](https://meta.discourse.org/t/-/380646/21?silent=true).

- **@HAWK** suggested **form templates** as a way to require users to acknowledge terms / provide structured info when posting, and clarified why a “policy widget” isn’t the same solution [read more](https://meta.discourse.org/t/-/397581/3?silent=true) / [read more](https://meta.discourse.org/t/-/397581/5?silent=true) (related docs: [read more](https://meta.discourse.org/t/-/397564/1?silent=true)).

- **@j.jaffeux** weighed in on chat UX semantics, noting that “pin” can coexist with “favorites” (they’re different behaviors/features) [read more](https://meta.discourse.org/t/-/397571/9?silent=true).

- **@lindsey** published/maintained documentation for **Creating form templates** —including how they’re enabled via Upcoming Changes and where admins manage them [read more](https://meta.discourse.org/t/-/397564/1?silent=true).

* * *

_That’s a wrap—yesterday’s Meta was equal parts pruning the garden and teaching our “Personas” to become proper “Agents”; may your digests respect your ignore list and your solutions wear their green checkboxes proudly._

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [6 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/764 "2026-03-06T05:02:09Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

In the last 24 hours (2026-03-05 → 2026-03-06):

- **New posts:** 122
- **New topics:** 14

**Top users (posts / likes received):**

| User | Posts | Likes |
| --- | --- | --- |
| @Moin | 14 | 13 |
| @stephtara | 12 | 12 |
| @nat | 3 | 10 |
| @ToddZ | 3 | 7 |
| @chapoi | 3 | 7 |
| @mcwumbly | 8 | 6 |
| @Andrew_Rowe | 3 | 6 |
| @darkpixlz | 4 | 5 |
| @merefield | 4 | 5 |
| @Bas | 2 | 4 |

* * *

## Interesting Topics

### #contribute:site-feedback

- @mcwumbly kicked off a broader rethink of how Meta’s support spaces should work—covering _who support categories are for_, why marking solutions matters, and how to nudge “drive-by” askers to click the green checkbox in [Improving the experience in our support categories](https://meta.discourse.org/t/-/397742/1?silent=true). Related threads being pulled into the conversation include the gardening experiment [read more](https://meta.discourse.org/t/-/397606/1?silent=true) and the long-running “Solved culture” discussion [read more](https://meta.discourse.org/t/-/292790/1?silent=true).

- The “gardening hub” experiment continued to surface tactical improvements—like better OP messaging when staff marks a solution and whether the copy could come from an existing string—in [Experiment: Collaborative content gardening hub for meta](https://meta.discourse.org/t/-/397606/44?silent=true). The same thread also pointed at tooling ideas like the Solved reminders plugin [read more](https://meta.discourse.org/t/-/340336/1?silent=true) and staff/OP notifications when staff accepts an answer [read more](https://meta.discourse.org/t/-/58388/1?silent=true).

- In the ongoing navigation clean-up, @manuel argued that “General” isn’t very informative on Meta and suggested it should be aggressively pruned and/or renamed to something more accurate (e.g., Off-topic / Watercooler) in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/54?silent=true).

- A practical iOS app issue cropped up with the refreshed Meta theme: text selection handles and selection behavior appear broken on the “Meta Branded” theme but not on Horizon, suggesting a theme-level regression in [Meta Branded redesign: theme refresh](https://meta.discourse.org/t/-/397246/45?silent=true).

- Meta’s “grab bag” thread about solved-status inconsistency was formally retired: @mcwumbly closed it in favor of focusing on targeted use-cases and routing discussion through the gardening hub and the new support-categories thread in [Inconsistent marking of Topics as Solved…](https://meta.discourse.org/t/-/361193/34?silent=true).

### #blog

- Discourse’s multilingual direction got a dedicated spotlight: @nat announced the “Discourse Without Borders” series and laid out why language support is strategic (and what’s coming) in [Every Language is Welcome](https://meta.discourse.org/t/-/397784/1?silent=true).

### #Community Building

- A moderation-trust question landed bluntly: in [Prevent Staff Flag Review](https://meta.discourse.org/t/-/397678/4?silent=true), @chapoi pushed back on “technical restrictions” to prevent moderators from reviewing flags, emphasizing that moderation is fundamentally about trusted community members—not guardrails for bad appointments.

- Communities wrestling with AI-heavy replies continued to trade norms: the thread explored whether Discourse should support labeling content as human-written vs AI-assisted vs AI-generated in [How to make it easy to specify if content is human-written, ai-assisted, or ai-generated?](https://meta.discourse.org/t/-/397548/1?silent=true). (This aligns with related AI-permissions concerns like “everyone” group handling in [Discourse AI does not respect the “everyone” group](https://meta.discourse.org/t/-/292048/1?silent=true).)

### #bug

- Deep-linking to headings is acting oddly _inside_ a topic: anchor links that work from email/new tabs scroll to the top when clicked in-page, with suspicion around Ember routing in [Anchor links not working within Discourse - but work from outside the topic](https://meta.discourse.org/t/-/397748/1?silent=true). A possibly-related older report was cited too: [read more](https://meta.discourse.org/t/-/240512/1?silent=true).

- Passkey/auth work had a busy day: @keegan shipped a fix for passkey setup failures in [Cant set up passkey on any discourse](https://meta.discourse.org/t/-/397642/18?silent=true), but follow-ups showed additional errors still possible during login; plus @supermathie reported a UX gap where passkey login is missing from a forced-2FA external-auth error screen in [Passkey option missing on “Enforce second factor on external auth” error screen](https://meta.discourse.org/t/-/397772/1?silent=true).

- A composer/approval edge case: users with a post pending approval get repeatedly hit with a “discard draft” confirmation when trying to post again, until refresh, in [A discard confirmation modal appears when clicking ‘New Post’ if a post is pending approval](https://meta.discourse.org/t/-/397711/1?silent=true).

- Ops/devs running migrations in parallel hit serious instability (dead workers / segfault), even when trying to dial concurrency back, in [Running multisite:migrate concurrently fails](https://meta.discourse.org/t/-/397755/1?silent=true).

### #Support

- Tag slug configuration became a two-part story: first, a new “tag slugs” capability was revealed as gated behind an experimental flag in [怎么在 Discourse 更改标签的 slug？](https://meta.discourse.org/t/-/397713/6?silent=true); then a follow-up report claimed that when slug generation is set to “none,” the new tag edit experience can break due to missing `tag_slug` params in [在 Slug 生成方法为 none 情况下…](https://meta.discourse.org/t/-/397789/1?silent=true).

- A nasty account-deletion failure turned out to be caused by reviewable note foreign keys: @chapoi suggested checking for flagged content with notes, and deleting the note first solved the issue in [User deletion problem, returns “Error 500” on delete all posts](https://meta.discourse.org/t/-/397700/2?silent=true).

### #contribute:feature

- A calendar/events enhancement request asked for raising the event description limit above 1000 characters (database type and Google Calendar carry-over use-cases were cited) in [Increase event description limit](https://meta.discourse.org/t/-/397771/1?silent=true).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- **@mcwumbly** led the push to rethink Meta support workflows and incentives (including solution-marking nudges and possible process experiments) in [Improving the experience in our support categories](https://meta.discourse.org/t/-/397742/1?silent=true), then connected the dots back to the broader “Solved culture” discussion in [Creating a community culture of marking topics as solved](https://meta.discourse.org/t/-/292790/15?silent=true). They also kept the gardening initiative focused by deprioritizing the git-synced docs category in [Experiment: Collaborative content gardening hub for meta](https://meta.discourse.org/t/-/397606/40?silent=true), and wrapped up the older “Solved inconsistency” grab-bag thread in [Inconsistent marking of Topics as Solved…](https://meta.discourse.org/t/-/361193/34?silent=true).

- **@nat** delivered the solution for brand-new tag slug controls—clarifying it’s gated behind `experimental_tag_settings_page`—in [怎么在 Discourse 更改标签的 slug？](https://meta.discourse.org/t/-/397713/6?silent=true), acknowledged an incoming fix for auto-tagging watched words in [Cannot add watched words for automatic tagging](https://meta.discourse.org/t/-/397601/4?silent=true), and published the multilingual-focused announcement in [Every Language is Welcome](https://meta.discourse.org/t/-/397784/1?silent=true).

- **@chapoi** emphasized that moderator powers rely on _trust_ rather than technical constraints in [Prevent Staff Flag Review](https://meta.discourse.org/t/-/397678/4?silent=true), and provided the key troubleshooting direction that resolved a user-deletion 500 error in [User deletion problem, returns “Error 500” on delete all posts](https://meta.discourse.org/t/-/397700/2?silent=true). They also asked targeted debugging questions on a staff-side 500 during moderation operations in [Error 500 when moving posts](https://meta.discourse.org/t/-/397654/2?silent=true).

- **@Bas** asked for real-world context (hypothetical vs actual incident) while diagnosing moderation-review concerns in [Prevent Staff Flag Review](https://meta.discourse.org/t/-/397678/6?silent=true), and clarified Mastodon “boost” terminology in the ActivityPub support question [Quote Boost support?](https://meta.discourse.org/t/-/397569/3?silent=true).

- **@awesomerobot** shipped multiple UX polish fixes: they removed CSS believed to cause WCAG palette quote-mention contrast issues in [Quoted @mention in tertiary color using wcag color palettes](https://meta.discourse.org/t/-/293324/3?silent=true), improved mobile staff log filtering UI in [Staff action logs filters don’t look great on mobile](https://meta.discourse.org/t/-/396131/3?silent=true), and queued layout fixes for badges admin UI in [Long description text box for Badges extends beyond boundary](https://meta.discourse.org/t/-/396167/17?silent=true). They also confirmed current limitations around video-specific upload controls in [Size restrictions on videos?](https://meta.discourse.org/t/-/397413/2?silent=true).

- **@j.jaffeux** weighed in on chat UX alternatives (status message or channel description) for pinned content visibility in [Show pinned messages at top of chat instead of in separate page](https://meta.discourse.org/t/-/397519/10?silent=true).

- **@gerhard** improved translation tooling clarity by fixing stale/badly imported git history data and showing clearer PR relationships across branches in [How can you find more context for a text?](https://meta.discourse.org/t/-/395051/11?silent=true) (with an additional fix noted shortly after: [read more](https://meta.discourse.org/t/-/395051/13?silent=true)).

- **@manuel** continued Meta’s information architecture debate by challenging the usefulness of “General” and proposing cleanup/renaming in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/54?silent=true).

- **@keegan** pushed out a code fix for passkey setup failures (with a pointer to update to latest) in [Cant set up passkey on any discourse](https://meta.discourse.org/t/-/397642/18?silent=true).

- **@supermathie** provided concrete error logging for passkey login failures (suggesting additional edge cases remain after the initial fix) in [Cant set up passkey on any discourse](https://meta.discourse.org/t/-/397642/21?silent=true), and raised a UX gap for passkey login on the external-auth enforced-2FA screen in [Passkey option missing on “Enforce second factor on external auth” error screen](https://meta.discourse.org/t/-/397772/1?silent=true).

- **@sam** confirmed cleanup is needed around allowing “everyone” as a selectable group in AI-related settings in [Discourse AI does not respect the “everyone” group](https://meta.discourse.org/t/-/292048/7?silent=true).

* * *

Yesterday’s Meta energy in one line: may your tag slugs be editable, your passkeys authenticate, and every support thread earn its well-deserved green check.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [7 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/765 "2026-03-07T05:02:08Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New activity (last 24h):**  **52** new posts across **6** new topics
- **Most active participants (posts / likes received):**
  - @Falco — **1** post / **12** likes _(see update in [read more](https://meta.discourse.org/t/-/389056/39?silent=true))_
  - @ice.d — **2** posts / **11** likes _(new praise thread: [read more](https://meta.discourse.org/t/-/397851/1?silent=true))_
  - @elmuerte — **3** posts / **9** likes _(language feature testing: [read more](https://meta.discourse.org/t/-/397784/3?silent=true))_
  - @NateDhaliwal — **3** posts / **7** likes _(Windows dev setup help: [read more](https://meta.discourse.org/t/-/397803/2?silent=true))_
  - @merefield — **3** posts / **6** likes _(WSL2 + workflow tips: [read more](https://meta.discourse.org/t/-/397803/3?silent=true))_
  - @Andrew_Rowe — **3** posts / **6** likes _(event description limit clarifications: [read more](https://meta.discourse.org/t/-/397771/4?silent=true))_
  - @noahl — **3** posts / **6** likes _(AI-assisted “mark solved” ideas: [read more](https://meta.discourse.org/t/-/397742/20?silent=true))_
  - @nat — **2** posts / **4** likes _(language setting + tag slug bug acknowledgment: [read more](https://meta.discourse.org/t/-/397784/4?silent=true), [read more](https://meta.discourse.org/t/-/397789/9?silent=true))_
  - @gilles — **3** posts / **4** likes _(dev setup question in French: [read more](https://meta.discourse.org/t/-/397803/1?silent=true))_
  - @RGJ — **3** posts / **3** likes _(post sorting plugin discussion: [read more](https://meta.discourse.org/t/-/397808/2?silent=true))_

* * *

## Interesting Topics

### #customization:plugin

- @Falco shipped a substantial round of improvements to Resenha voice rooms— **badges** , **AFK detection** , **push-to-talk** , **stage rooms** , and even early **analytics** surfaced in a single update: [read more](https://meta.discourse.org/t/-/389056/39?silent=true)

- The long-running **Locations plugin** funding effort ticked forward again, with @merefield noting the remaining monthly gap and thanking contributors: [read more](https://meta.discourse.org/t/-/69742/1229?silent=true)

### #community-building:praise

- @ice.d posted a heartfelt community appreciation note, calling out how helpful Meta regulars are and thanking both community members and staff: [read more](https://meta.discourse.org/t/-/397851/1?silent=true)

### #Support

- A French-language thread asked whether the **Windows development setup docs** are still current; replies recommended WSL2 or a Linux VM, and pointed to established install guides and Docker-based workflows: [read more](https://meta.discourse.org/t/-/397803/1?silent=true) (see also: WSL path [read more](https://meta.discourse.org/t/-/14727/1?silent=true), Docker dev install [read more](https://meta.discourse.org/t/-/102009/1?silent=true))

- “How do I enable SSO?” came up again—@awesomerobot responded by clarifying which SSO approach is being used and linked people to [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) and Auth0/OAuth guidance: [read more](https://meta.discourse.org/t/-/397816/2?silent=true) (related guides: [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) [read more](https://meta.discourse.org/t/-/13045/1?silent=true), Auth0 via oauth2-basic [read more](https://meta.discourse.org/t/-/64633/1?silent=true))

- A site admin questioned whether Discourse emits a **“legacy trusted.gpg keyring”** warning after upgrading Ubuntu in place, and confirmed they might address it as follow-up maintenance: [read more](https://meta.discourse.org/t/-/397470/11?silent=true)

### #Site feedback

- In the ongoing effort to improve support workflows, discussion continued around _nudging_ OPs to mark solutions—@noahl argued context-blind reminders can backfire, and proposed AI-assisted nudges that cite likely solution posts more thoughtfully:

- A separate experiment thread on building a **collaborative content gardening hub** for Meta cross-linked the support-category improvements conversation, reinforcing that “solved” workflows and gardening practices are tightly connected: [read more](https://meta.discourse.org/t/-/397606/47?silent=true) (context: [read more](https://meta.discourse.org/t/-/397742/19?silent=true))

- A related (older, but newly-updated) community-building thread revisited how to create a culture of marking topics as solved—again circling back to the idea that AI could help identify likely “solution” replies after inactivity: [read more](https://meta.discourse.org/t/-/292790/16?silent=true)

### #blog

- A lighthearted (and slightly destructive) test of the “Every Language is Welcome” theme surfaced: @elmuerte posted cuneiform-like text, then reported editing issues and odd posting metadata; @nat stepped in to normalize the post language: [read more](https://meta.discourse.org/t/-/397784/3?silent=true) (moderation note: [read more](https://meta.discourse.org/t/-/397784/4?silent=true))

### #bug

- A #tags issue was reported where `slug_generation_method = none` breaks editing newly-created tags on the experimental tag settings page; @Moin provided clear repro steps and @nat confirmed a fix is forthcoming: [read more](https://meta.discourse.org/t/-/397789/6?silent=true), [read more](https://meta.discourse.org/t/-/397789/9?silent=true) (background mention: [read more](https://meta.discourse.org/t/-/397713/10?silent=true))

- A small but sharp UX/translation bug: creating a tag group with no tags shows the raw i18n key (`tagging.groups.cannot_save.no_tags`) instead of the translated string; the report includes repro and confirmation: [read more](https://meta.discourse.org/t/-/397853/1?silent=true)

- A concurrency-related failure running `multisite:migrate` led to investigation around forking and `mini_racer`; after discussion, the OP narrowed it down to chaining rake tasks (seed + migrate) in one command: [read more](https://meta.discourse.org/t/-/397755/5?silent=true), [read more](https://meta.discourse.org/t/-/397755/6?silent=true)

- A persistent “Error 500 when moving posts” debugging thread continued, with container logs suggesting the cause may be deeper (possibly DB-side) than nginx itself: [read more](https://meta.discourse.org/t/-/397654/6?silent=true)

### #ux

- In a small-but-polishy admin UX report, a missing `i18n()` call was identified as the reason the UI renders the translation _key_ instead of the translation _value_—the kind of detail that makes admin tools feel rough when it leaks through: [read more](https://meta.discourse.org/t/-/397853/3?silent=true)

### #customization:theme component / #Announcements / #Dev

- Theme ecosystem updates kept rolling: the **Topic Excerpts & AI Gists Button** component was refactored to match the **Modernized Foundation** styling while preserving compatibility with the original: [read more](https://meta.discourse.org/t/-/394885/6?silent=true) (Foundation thread context: [read more](https://meta.discourse.org/t/-/395331/59?silent=true))

- In the Foundation modernization thread, additional UI edge cases were reported—tag color rendering and PM card height/misalignment issues—continuing the steady “polish pass” feedback loop: [read more](https://meta.discourse.org/t/-/395331/60?silent=true)

- A developer shared a consolidated theme-component approach to tag presentation—combining “remove tag dashes”, tag styles, and tag icons into a single configurable component concept: [read more](https://meta.discourse.org/t/-/397792/1?silent=true)

### #contribute:feature

- A feature request asked to **increase the event description limit** (#calendar-and-event), motivated by real-world “route directions” use cases that need to survive calendar exports; follow-up clarified the constraint is visible in downstream calendar entries: [read more](https://meta.discourse.org/t/-/397771/3?silent=true), [read more](https://meta.discourse.org/t/-/397771/4?silent=true)

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @Falco posted a packed progress update on the Resenha voice rooms plugin—introducing a basic badge system, AFK detection, push-to-talk, stage rooms, and analytics scaffolding: [read more](https://meta.discourse.org/t/-/389056/39?silent=true)

- @nat jumped into two threads: they normalized the detected language on a “cuneiform” blog-comment experiment: [read more](https://meta.discourse.org/t/-/397784/4?silent=true), and confirmed the team has logged the `slug_generation_method = none` / tag editor issue and expects to ship a fix soon: [read more](https://meta.discourse.org/t/-/397789/9?silent=true)

- @tgxworld investigated a tricky `multisite:migrate` concurrency failure—asking for environment details, spotting `mini_racer` in the backtrace, and sharing a direction to harden fork behavior: [read more](https://meta.discourse.org/t/-/397755/4?silent=true), [read more](https://meta.discourse.org/t/-/397755/5?silent=true)

- @awesomerobot guided an admin who couldn’t find SSO settings, clarifying the type of SSO and linking to the appropriate setup documentation: [read more](https://meta.discourse.org/t/-/397816/2?silent=true)

- @tshenry reported a UI string regression where an i18n key leaks into a modal when creating tag groups without tags—complete with a screen recording: [read more](https://meta.discourse.org/t/-/397853/1?silent=true)

- @keegan followed up on ongoing #passkey troubleshooting, pushing another fix upstream and asking for confirmation that the issue is fully resolved: [read more](https://meta.discourse.org/t/-/397642/25?silent=true)

- @chapoi responded on a user deletion / “delete all posts” error case, noting it likely wasn’t fixed on the default branch and that an internal report would be filed (while confirming the workaround succeeded): [read more](https://meta.discourse.org/t/-/397700/4?silent=true)

* * *

If today’s Meta had a theme, it’d be _“hold my beer… in cuneiform… while we fix your tag slugs and keep your voice rooms from going AFK.”_

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [8 maart 2026 om 05:01 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/766 "2026-03-08T05:01:40Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

In the last 24 hours (covering **2026-03-07 → 2026-03-08** ), Meta saw:

- **Total new posts:**  **88**
- **Total new topics:**  **12**

### Top contributors (posts + likes in the last 24h)

| User | Posts | Likes |
| --- | --- | --- |
| @stephtara | 25 | 13 |
| @Moin | 8 | 11 |
| @darkpixlz | 8 | 8 |
| @NateDhaliwal | 10 | 5 |
| @jdc20181 | 3 | 7 |
| @RGJ | 1 | 4 |
| @Falco | 1 | 4 |
| @merefield | 2 | 3 |
| @satonotdead | 1 | 3 |
| @SubStrider | 1 | 2 |

### What drove the conversation?

- Admin UX and onboarding questions clustered around #discobot configuration and testing (see: [Discobot struggles…](https://meta.discourse.org/t/-/397872/1?silent=true), [Narrative bot settings and texts](https://meta.discourse.org/t/-/397873/1?silent=true), and customizing variables in bot copy: [Customizing Discobot for your site](https://meta.discourse.org/t/-/103633/42?silent=true)).
- Theme/component builders shipped and iterated quickly—especially around tag UI customization (launch: [Tag Style Tool](https://meta.discourse.org/t/-/397885/1?silent=true)) and theme updates (new tweaks: [Pyx’s Modern Theme](https://meta.discourse.org/t/-/357665/41?silent=true)).
- AI performance and operational impact was a recurring theme, including reports of servers pegging CPU after enabling semantic search (report: [Enabling AI search crippled my server](https://meta.discourse.org/t/-/397869/1?silent=true)) and broader support workflow thinking (team note: [Improving the experience in our support categories](https://meta.discourse.org/t/-/397742/23?silent=true)).

* * *

## Interesting Topics

### #Support

- @stephtara explored how to get a more useful Google Sheets preview (Facebook-style) and ended up improving an embed via CSS—then brainstormed ways to make it _non-technical-member friendly_ (including a “toolbar button that inserts an iframe”) in [Google Sheet Preview: is there any way?](https://meta.discourse.org/t/-/391504/4?silent=true) (with practical CSS guidance in [this reply](https://meta.discourse.org/t/-/391504/10?silent=true) and composer-button ideas later in the thread: [read more](https://meta.discourse.org/t/-/391504/19?silent=true)).

- Discobot testing pain points came up: welcome messages that only send once, closed PM threads, and confusion about what can/can’t be restarted for onboarding verification—plus reminders that Discobot is disabled on Meta—in [Discobot struggles: closing welcome message…](https://meta.discourse.org/t/-/397872/1?silent=true) (and a follow-on about broader onboarding alternatives like Automation: [read more](https://meta.discourse.org/t/-/397872/9?silent=true)).

- Chat vs PM permissions got untangled: @stephtara wanted _restricted PM creation_ while still allowing _anyone to contact staff/helpers_, and the thread clarified that messaging a **group** depends on group settings (and pointed toward the staff-PM plugin) in [Access rights for chat and messages between users](https://meta.discourse.org/t/-/397864/1?silent=true) (related: [Allow PM to staff plugin](https://meta.discourse.org/t/-/260946/1?silent=true), earlier chat-permission discussion: [Can individual chat be disabled for certain users but not channels?](https://meta.discourse.org/t/-/391301/1?silent=true), and a linked reference: [read more](https://meta.discourse.org/t/-/316079/17?silent=true)).

- AI semantic search load concerns: @SubStrider reported that enabling **“AI embeddings semantic search enabled”** immediately drove CPU to 100% and created a major Sidekiq backlog, which resolved quickly after disabling semantic search, in [Enabling AI search crippled my server](https://meta.discourse.org/t/-/397869/1?silent=true).

- An SSO setup question (Laravel → Discourse) turned into a “can’t find the setting” troubleshooting moment, where the key insight was “you’ve got a filter applied,” plus a reminder that the instance looked outdated, in [How to enable sso on discourse?](https://meta.discourse.org/t/-/397816/3?silent=true) ([follow-up](https://meta.discourse.org/t/-/397816/5?silent=true)).

- Testing unsupported browsers surfaced a weird “can’t scroll” experience in basic-html view—ultimately chalked up to the test being _too extreme_ (ancient Chrome), with a suggestion to test by spoofing UA instead, in [Inability to Scroll Page in basic-html View](https://meta.discourse.org/t/-/397861/1?silent=true) (solution context: [read more](https://meta.discourse.org/t/-/397861/2?silent=true)).

- Mobile display debugging got harder as legacy overrides fade: a user tried multiple desktop browsers to force “mobile view” for menu tweaking; the thread notes the historical `?mobile_view=1` approach and that Discourse is moving to viewport-based responsiveness, in [Which browser loads the correct mobile display?](https://meta.discourse.org/t/-/397891/1?silent=true) (with deprecation context: [No more switchable mobile/desktop layouts](https://meta.discourse.org/t/-/397463/10?silent=true) and background doc: [Designing for different devices…](https://meta.discourse.org/t/-/367810/1?silent=true)).

- A self-host admin hit a silent failure creating accounts via Discourse ID: verification succeeded, but signup “does nothing,” plus anonymous-console 404s for source maps and plugin assets; the report includes environment notes (no SMTP, 2026.3.0-latest) in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/1?silent=true).

* * *

### #bug

- An iPad Pro/Safari composer bug report showed the composer “flying off screen” when switching input fields, seemingly related to the on-screen keyboard resizing/layout shifts, in [Ipad pro - safari - composer disappears off screen…](https://meta.discourse.org/t/-/397892/1?silent=true) (extra capture and workaround attempt: [read more](https://meta.discourse.org/t/-/397892/2?silent=true)).

- Passkeys: a previously reported inability to set up passkeys appears resolved; a user confirmed fast turnaround and successful testing with Nitrokey for 2FA flows in [Cant set up passkey on any discourse](https://meta.discourse.org/t/-/397642/26?silent=true).

* * *

### #customization:theme component

- A new theme component aimed at consolidating tag styling tricks landed: **Tag Style Tool** , with discussion immediately turning to “which Font Awesome set/version is supported?” and whether a _color picker_ could be built into the settings UI, in [Tag Style Tool](https://meta.discourse.org/t/-/397885/1?silent=true) (author follow-up progress: [read more](https://meta.discourse.org/t/-/397885/8?silent=true)).

- A classic dev-support confusion: “How do I install a PR?” was answered with “you don’t install PRs; you update after merge,” and then clarified that the fix had already been merged (update the component), in [Discourse Category Headers theme component](https://meta.discourse.org/t/-/148682/196?silent=true) ([merge/update clarification](https://meta.discourse.org/t/-/148682/198?silent=true), confirmation: [read more](https://meta.discourse.org/t/-/148682/199?silent=true)).

* * *

### #customization:plugin

- Assign “done-ness” remains a workflow question: @stephtara asked how to mark an assigned topic as completed, with responses outlining internal patterns (close topic + tag, or unassign + comment) and pointing to assign statuses and Kanban for richer flows, in [Discourse Assign](https://meta.discourse.org/t/-/58044/230?silent=true) (status hint: [read more](https://meta.discourse.org/t/-/58044/232?silent=true), team workflow detail: [read more](https://meta.discourse.org/t/-/58044/234?silent=true)).

- A sharp security reminder: if you add `everyone` to a “private topics” category, it breaks the intended privacy model—and maybe needs an even bigger UI warning—raised in [Private Topics Plugin](https://meta.discourse.org/t/-/268646/106?silent=true).

* * *

### #community-building Building

- Site structure and “built-in page” semantics were questioned: the mismatch between _FAQ link → Guidelines_, what the About page is “for,” and localization-friendly slugs (e.g. `/a-propos`) prompted a broader “what value do these built-ins add?” discussion in [FAQ/Guidelines and “About” pages](https://meta.discourse.org/t/-/397882/1?silent=true) (with historical context linked: [Why is Guidelines called FAQ?](https://meta.discourse.org/t/-/35534/1?silent=true)).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @Falco jumped into the theme-component conversation to unblock a common UI need: color picking. In response to the new tag styling component thread, he pointed out there’s now a native HTML color input (`<input type="color">`) and that Discourse wraps it for easier use in [Tag Style Tool](https://meta.discourse.org/t/-/397885/6?silent=true).

- @chapoi clarified a practical limitation in Assign workflows: there’s **no built-in “done” state** , and Discourse’s own process tends to be “close topic + tag it `fixed`/`completed`” (or similar), in [Discourse Assign](https://meta.discourse.org/t/-/58044/231?silent=true).

- @mcwumbly expanded on internal operational practice around assignment tracking: keep it simple (unassign + reply, close when appropriate), and when work needs richer status tracking across multiple items/people, they reach for the Kanban theme component—while also noting they may revisit this area more seriously later, in [Discourse Assign](https://meta.discourse.org/t/-/58044/234?silent=true).

- @sam weighed in on support-category workflow design, noting that “extremely sophisticated agents” already exist in Discourse AI and wondering how to make those kinds of workflows easier to configure—ending with an invitation to sync up—in [Improving the experience in our support categories](https://meta.discourse.org/t/-/397742/23?silent=true).

* * *

Yesterday’s Meta energy in one sentence: may your tag colors be pickable, your iframes be full-width, and your onboarding bots never leave you on “read.”

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [9 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/767 "2026-03-09T05:02:03Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

**In the last 24 hours (2026-03-08 → 2026-03-09):**

- **New posts:**  **32**
- **New topics:**  **4**

**Top users (posts / likes received):**

| User | Posts | Likes |
| --- | --- | --- |
| @ToddZ | 3 | 3 |
| @NateDhaliwal | 3 | 2 |
| @gilles | 2 | 2 |
| @Ethsim2 | 1 | 2 |
| @stephtara | 2 | 1 |
| @merefield | 1 | 1 |
| @Don | 1 | 1 |
| @one1 | 1 | 1 |
| @jdc20181 | 1 | 1 |
| @Falco | 2 | 0 |

> Activity highlights ranged from Ruby version gotchas in local dev setups to SEO canonicals for localized pages, plus more automation and theme customization ideas.

* * *

## Interesting Topics

### #Self-hosting

- @gilles hit a Ruby version mismatch while following the Windows 11 dev setup guide, and @NateDhaliwal pointed to several recent “Ruby mismatch”/upgrade threads as common fixes; @merefield clarified that `3.4.0.dev` can be considered _older_ than the Gemfile requirement and suggested managing Ruby versions via rbenv (or similar). [read more](https://meta.discourse.org/t/-/282227/18?silent=true) (see also: [Ruby mismatch thread](https://meta.discourse.org/t/-/396317/1?silent=true), [crash during update](https://meta.discourse.org/t/-/397520/1?silent=true), [“big scary red button” update advice](https://meta.discourse.org/t/-/396452/3?silent=true), and the resolution using Ruby 3.4.8 [here](https://meta.discourse.org/t/-/282227/21?silent=true))

### #Support

- A request for a _transparent_ Discourse theme (Discord-style) led to a pragmatic answer: for “just me” customization, use a personal browser stylesheet; for _group-scoped_ theming, it’s not built-in, but there are CSS-based approaches to “show/hide themes for specific groups.” [read more](https://meta.discourse.org/t/-/397921/2?silent=true) (related: [Show/hide themes for specific groups?](https://meta.discourse.org/t/-/115459/1?silent=true))

- As an alternative approach to “theme for a small group,” @NateDhaliwal suggested using a component that exposes CSS classes for a user’s groups—handy for targeting styling to members (with the tradeoff that users can’t opt out if it’s baked into the main theme). [read more](https://meta.discourse.org/t/-/397921/3?silent=true) (related: [CSS classes for current user’s groups](https://meta.discourse.org/t/-/226068/1?silent=true))

- A site running #content-localization flagged that `?tl=fr` translated pages were not being indexed due to canonical tags pointing at the non-translated URL; the report notes that Google treats these as “Alternate page with proper canonical tag,” preventing indexing of localized variants. [read more](https://meta.discourse.org/t/-/397925/1?silent=true)

- @Falco replied that this canonical behavior matches what’s been described as expected elsewhere (and matches what’s seen on Meta), quoting prior guidance about focusing indexing on canonical pages. [read more](https://meta.discourse.org/t/-/397925/2?silent=true) (referenced quote context: [nat on canonicals](https://meta.discourse.org/t/-/370969/62?silent=true))

- A self-host admin asked if a Google Sheets onebox/preview workflow could be personalized _per user_; @NateDhaliwal suggested leveraging custom user fields (accessible via code) to inject user-specific content into composer text, with a caveat that it may require a web request depending on implementation. [read more](https://meta.discourse.org/t/-/391504/21?silent=true)

- A report that enabling #ai #ai-search “crippled” a server prompted @sam to explain that long-running `Jobs::GenerateEmbeddings` durations are expected when calling an external embeddings service, but high CPU is _not_; both @sam and @Falco asked for deeper diagnostics (server specs, DB specs, provider, processes consuming CPU, topic counts). [read more](https://meta.discourse.org/t/-/397869/3?silent=true) (and @Falco’s follow-up questions: [read more](https://meta.discourse.org/t/-/397869/4?silent=true))

- A “mobile display looks wrong” thread ended with the OP finding that some `@media` queries were interfering with Brave’s mobile rendering; after adjustment, Chrome and mobile behavior aligned better across browsers. [read more](https://meta.discourse.org/t/-/397891/6?silent=true)

- An iPad Pro Safari composer “disappearing” issue was marked solved after the reporter observed it wasn’t reproducing the next day (possibly a transient cache/UI quirk). [read more](https://meta.discourse.org/t/-/397892/3?silent=true)

- A new topic about “Pangolin Discourse Self Host” (#unsupported-install #hosting) was deleted by its author shortly after posting, suggesting either a false start or an off-topic/unsupported path. [read more](https://meta.discourse.org/t/-/397932/1?silent=true)

### #community-building Building

- A discussion about FAQ/Guidelines and “About” pages surfaced confusion around the recent “FAQ renamed to Guidelines” changes (and differences between hosted vs self-hosted behavior); @ToddZ highlighted the `/admin/config/about` editor and dug into why some self-host sites still show “FAQ” in the sidebar while rendering Guidelines content. [read more](https://meta.discourse.org/t/-/397882/4?silent=true) (background: [Renaming FAQ to Guidelines](https://meta.discourse.org/t/-/395099/1?silent=true), referenced hosted-default note: [read more](https://meta.discourse.org/t/-/396672/5?silent=true), and @HAWK’s hosted-context correction: [read more](https://meta.discourse.org/t/-/397882/5?silent=true))

### #bug

- A bug report claims restricted-visibility #tags / #tag-groups still appear on `/tags` even when they should be hidden from users without permissions, noting this was “previously fixed” in an older report and appears to regress when a specific setting is enabled. [read more](https://meta.discourse.org/t/-/397930/1?silent=true) (older reference: [restricted tags showing on /tags](https://meta.discourse.org/t/-/116165/8?silent=true))

### #Site Management

- Auto-bumping configuration came up again: @one1 asked whether “1” is the minimum topics-per-day bump (and why fractional values like `.25` won’t persist), aiming to bump a “resources” topic only every few days rather than daily. [read more](https://meta.discourse.org/t/-/262158/28?silent=true)

### #contribute:feature

- On math-heavy communities, @Ethsim2 proposed improving quoting behavior for math by intercepting selected HTML, extracting TeX from MathJax wrapper annotations, and reinserting `$...$`/`$$...$$` before Discourse converts back into Markdown—possibly as a small theme-component patch. [read more](https://meta.discourse.org/t/-/148342/6?silent=true) (#pr-welcome)

- A feature request to split Discourse Automations into explicit **Triggers → Filters → Actions** gained momentum, with @sam linking to an exploration of “automation pipelines” and calling the chain approach “far more flexible and clear.” [read more](https://meta.discourse.org/t/-/384262/2?silent=true) (#automation)

### #Developer Guides

- A brief but important correction landed in a thread about theme setting types: a user noted the “correct” value should be `upload` (context: “Objects type for theme setting”). [read more](https://meta.discourse.org/t/-/305009/32?silent=true) (#how-to #theme-guides)

### #customization:theme component

- In the “Tag Style Tool” component topic, a commenter suggested that a style-builder UX would be a “killer feature,” hinting at demand for more guided tag styling tools. [read more](https://meta.discourse.org/t/-/397885/9?silent=true) (#tags)

### #Sysadmins

- The NodeBB → Discourse migration script discussion got a practical improvement: sorting MongoDB “posts:pid” keys by score ascending to keep post order chronological within topics. [read more](https://meta.discourse.org/t/-/126553/23?silent=true) (#how-to)

### #customization:plugin

- The long-running Events Plugin thread noted a broken link to Angus’ support site for community-based support/discussion, which may affect users looking for plugin help. [read more](https://meta.discourse.org/t/-/69776/890?silent=true)

### #blog

- Meta’s “Every Language is Welcome” blog conversation continued with reflections on the realities (and resource costs) of supporting _all_ languages for readers. [read more](https://meta.discourse.org/t/-/397784/7?silent=true)

_(Related ongoing meta process note: support workflow UX and automation flexibility were also tied together in the “Improving the experience in our support categories” discussion, which cross-linked back to the automation pipeline request.)_ [read more](https://meta.discourse.org/t/-/397742/24?silent=true)

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @sam weighed in on the “AI search crippled my server” report, clarifying that embeddings backfills can show long job durations due to external API calls (normal), while unexpected CPU pressure points to DB/process constraints—and requested concrete diagnostics to proceed. [read more](https://meta.discourse.org/t/-/397869/3?silent=true)

- @sam also engaged with automation design, endorsing a **Trigger → Filter → Action → Action** chain model and linking to a pipeline-style exploration to make automations more flexible and understandable. [read more](https://meta.discourse.org/t/-/384262/2?silent=true)

- @HAWK corrected context in the FAQ/Guidelines/About-page discussion (hosted vs self-hosted expectations), and flagged likely documentation gaps after realizing the “FAQ link in the sidebar” behavior differs across environments. [read more](https://meta.discourse.org/t/-/397882/5?silent=true)

- @Falco responded to the localized-page indexing concern by pointing to existing guidance that translated/alternate pages may be intentionally canonicalized to the primary URL (and that this matches what Meta itself sees). [read more](https://meta.discourse.org/t/-/397925/2?silent=true)

- @Falco also followed up in the AI search performance thread, noting the job-duration graph looked like expected embedding backfill, then asking for specifics (provider, self-hosting vs third-party, topic count, DB specs) to identify the real CPU bottleneck. [read more](https://meta.discourse.org/t/-/397869/4?silent=true)

* * *

Yesterday’s vibe: _people tried to make Discourse transparent, quotable (especially math), and indexable (especially translations)… and Discourse pushed back with canonicals, CSS realities, and a little bit of Ruby version chaos._

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [10 maart 2026 om 05:01 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/768 "2026-03-10T05:01:54Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

Over the last 24 hours—spanning discussions like _OpenAI service tiers for Discourse AI_ and _[DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) privacy_—Meta saw **82 new posts** across **9 new topics** ([read more](https://meta.discourse.org/t/-/397937/1?silent=true), [read more](https://meta.discourse.org/t/-/397980/1?silent=true)).

### Top users (posts / likes)

| User | Posts | Likes | Where they were active (sample) |
| --- | --- | --- | --- |
| @sam | 1 | 10 | Announced OpenAI/Azure provider tier selection ([read more](https://meta.discourse.org/t/-/397937/1?silent=true)) |
| @ToddZ | 7 | 8 | Helped triage docs cleanup + dashboard graph UX ([read more](https://meta.discourse.org/t/-/397938/6?silent=true), [read more](https://meta.discourse.org/t/-/397956/2?silent=true)) |
| @jdc20181 | 5 | 6 | Shipped fixes/iterations on Tag Style Tool UX ([read more](https://meta.discourse.org/t/-/397885/12?silent=true)) |
| @merefield | 3 | 5 | Reported dashboard report scaling pain point ([read more](https://meta.discourse.org/t/-/397956/1?silent=true)) |
| @gilles | 5 | 4 | Explored plugin approach for BoardGameGeek API integration ([read more](https://meta.discourse.org/t/-/397948/1?silent=true)) |
| @NateDhaliwal | 4 | 4 | Solved “Require TOS acceptance” with user-field pattern ([read more](https://meta.discourse.org/t/-/397955/2?silent=true)) |
| @asc | 5 | 3 | Shared traces for Discourse ID signup failures ([read more](https://meta.discourse.org/t/-/397895/5?silent=true)) |
| @mentalstring | 3 | 3 | Debugged cakeday rebuild failures on older stable ([read more](https://meta.discourse.org/t/-/373574/167?silent=true)) |
| @noahl | 2 | 3 | Expanded the “Triggers & Actions” automation redesign idea ([read more](https://meta.discourse.org/t/-/384262/5?silent=true)) |
| @Falco | 4 | 3 | Weighed in on SSO privacy + onebox image caching behavior ([read more](https://meta.discourse.org/t/-/397980/4?silent=true), [read more](https://meta.discourse.org/t/-/325769/23?silent=true)) |

* * *

## Interesting Topics

### #Announcements

- Discourse AI gained **service tier selection** for OpenAI and Azure providers (standard/flex/priority), plus guidance to use the **Responses** endpoint for better caching on newer reasoning models—shared by @sam in **#ai** ([read more](https://meta.discourse.org/t/-/397937/1?silent=true)).

- A self-hosted instance on **v3.5.4** hit a confusing rebuild failure after the _cakeday_ plugin moved into core; @david explained the warning can appear during unrelated rebuild failures and suggested cleaning up the plugin directory before cloning again (with a working `rm -rf discourse-cakeday` hook) ([read more](https://meta.discourse.org/t/-/373574/168?silent=true)).

### #Site feedback

- A mini “docs gardening” effort kicked off to **review/update outdated FAQ & Guidelines references** , including clarifying that self-hosters must enable the hidden `rename_faq_to_guidelines` setting; @Danielle said the team will align on a process and report back ([read more](https://meta.discourse.org/t/-/397938/7?silent=true)). Related references being flagged include _Renaming FAQ to Guidelines_ ([read more](https://meta.discourse.org/t/-/395099/1?silent=true)) and _Using Hidden Site Settings_ ([read more](https://meta.discourse.org/t/-/308773/1?silent=true)), plus older docs that may need edits: _Customizing FAQs and Guidelines_ ([read more](https://meta.discourse.org/t/-/286911/1?silent=true)) and _Update the FAQ, Privacy Policy, and Terms of Service_ ([read more](https://meta.discourse.org/t/-/18074/1?silent=true)).

### #bug

- A dashboard UX request asked whether the **Site Traffic graph** should _re-scale the Y-axis_ when toggling series like crawlers/bots; @nat confirmed changes are underway and an update is coming soon ( **#dashboard-reports** ) ([read more](https://meta.discourse.org/t/-/397956/4?silent=true)).

- In a Chinese-language **#tags** report, @nat confirmed a fix for a case where _Slug generation = none_ could break the “new edit tag” UI after creating tags, pointing to an upstream patch ([read more](https://meta.discourse.org/t/-/397789/10?silent=true)).

- A report that **restricted-visibility tag groups** still appeared on `/tags` turned out to be environment-related; after a rebuild, the reporter confirmed visibility rules worked as expected and the issue was marked resolved ( **#tags** / **#tag-groups** ) ([read more](https://meta.discourse.org/t/-/397930/4?silent=true)).

### #contribute:feature

- A **security/privacy** concern noted that when Discourse acts as a **[DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) Provider**, the user email is included in the (Base64-encoded) redirect payload; @Falco agreed a _non-default_ site setting to omit email would be **#pr-welcome** to preserve compatibility ([read more](https://meta.discourse.org/t/-/397980/4?silent=true)). The discussion references the provider documentation (_Use Discourse as an identity provider_) ([read more](https://meta.discourse.org/t/-/32974/1?silent=true)).

- The long-running request to **split Automations into Triggers and Actions** gained more detail: @noahl argued it improves scalability and observability, while @stephtara emphasized the value of **delays** for onboarding/drip sequences ( **#automation** ) ([read more](https://meta.discourse.org/t/-/384262/4?silent=true)).

- Onebox privacy concerns resurfaced: a user worried remote sites can track visitors via onebox images/favicons (and potential GDPR implications). @Falco demonstrated that _final cooked posts_ load assets from the Discourse CDN, and clarified retroactive changes likely require rebaking the posts that include oneboxes ([read more](https://meta.discourse.org/t/-/325769/23?silent=true)).

### #Support

- “ **Require TOS acceptance** ” was solved with a practical pattern: create a required custom user field; users may toggle it, but cannot save preferences unless it’s checked (effectively enforcing acceptance at save time) ([read more](https://meta.discourse.org/t/-/397955/2?silent=true)).

- A Discourse instance saw **new-user signup failures** (button does nothing) alongside widespread 404s for source maps and repeated `can't alloc thread` errors; @pmusaraj requested the backtrace/env to diagnose the resource exhaustion and unblock signup, especially for **#discourse-id** flows ([read more](https://meta.discourse.org/t/-/397895/4?silent=true)). A related older Discourse ID “redirect URI already exists” support thread remains relevant background ([read more](https://meta.discourse.org/t/-/396136/14?silent=true)).

- Mobile browsers: the **text-selection popup** (“Quote”, “Copy Quote”, etc.) was reported as non-functional on some devices even in [safe mode](https://meta.discourse.org/t/53504?silent=true); @supermathie attempted repro and found Mi Browser crashing/behaving abnormally, suggesting escalation to the browser vendor rather than Discourse core ([read more](https://meta.discourse.org/t/-/397943/4?silent=true)).

### #General

- A site owner wanted to require both an **intro post** and a **like/ack** of guidelines before unlocking the main community; @awesomerobot suggested combining the **Discourse Policy** plugin (for explicit “I accept” gating) with **Discourse Automation** + a badge-driven group membership workaround for “posted an intro” style checks ([read more](https://meta.discourse.org/t/-/397978/2?silent=true)). Handy references included: _Discourse Policy_ ([read more](https://meta.discourse.org/t/-/88557/1?silent=true)), _Discourse Automation_ ([read more](https://meta.discourse.org/t/-/195773/1?silent=true)), and _Triggered custom badge queries_ ([read more](https://meta.discourse.org/t/-/19336/1?silent=true)).

### #customization:theme component

- The **Tag Style Tool** theme component got rapid iteration: users reported the “builder” button disappearing and some Font Awesome SVG icons not rendering; @jdc20181 pushed fixes, shared a beta bundle, and discussed fallbacks/overrides for tag icon + color behavior ( **#tags** ) ([read more](https://meta.discourse.org/t/-/397885/14?silent=true)).

### #Self-hosting

- A self-hoster hit “ **Application with this redirect URI already exists** ” when re-enabling **#discourse-id** after reinstalling; @pmusaraj offered to clear the existing credentials via PM and noted a better workflow is in progress ([read more](https://meta.discourse.org/t/-/397991/2?silent=true)).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @sam shipped a Discourse AI improvement: admins can now choose **OpenAI/Azure service tiers** (standard/flex/priority) and are advised to use `https://api.openai.com/v1/responses` for better caching on newer models ( **#ai** ) ([read more](https://meta.discourse.org/t/-/397937/1?silent=true)).

- @Danielle acknowledged the growing list of outdated “FAQ/Guidelines” guidance and committed to coordinating a process with the team, with a follow-up planned ([read more](https://meta.discourse.org/t/-/397938/7?silent=true)).

- @HAWK offered to tag/assign or otherwise help structure the FAQ/Guidelines cleanup effort, deferring to the docs/mod workflow preference ([read more](https://meta.discourse.org/t/-/397938/5?silent=true)).

- @david debugged the “cakeday plugin merged into core” rebuild confusion on older stable versions, explaining why the warning message can be misleading and providing a concrete cleanup hook workaround ([read more](https://meta.discourse.org/t/-/373574/168?silent=true)).

- @nat responded to dashboard report feedback about traffic graph scaling and confirmed the team is already working on improvements ([read more](https://meta.discourse.org/t/-/397956/4?silent=true)); separately, @nat confirmed a **#tags** fix landed for a slug-generation edge case ([read more](https://meta.discourse.org/t/-/397789/10?silent=true)).

- @Falco engaged on two privacy-adjacent threads: clarifying the [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) redirect payload isn’t encrypted (Base64 + HMAC integrity) and welcoming a non-breaking setting to omit email by default ( **#pr-welcome** ) ([read more](https://meta.discourse.org/t/-/397980/4?silent=true)); and explaining onebox media caching behavior plus the likely need to rebake posts for retroactive changes ([read more](https://meta.discourse.org/t/-/325769/23?silent=true)).

- @awesomerobot helped troubleshoot a tag-group visibility report (couldn’t reproduce, requested verification of tag group visibility settings) ([read more](https://meta.discourse.org/t/-/397930/2?silent=true)), and suggested a practical “policy + automation + badges” approach to gate access based on guideline acceptance and an intro post ([read more](https://meta.discourse.org/t/-/397978/2?silent=true)).

- @supermathie investigated a mobile-browser quoting issue, attempted reproduction on Android emulation, and concluded Mi Browser instability likely points to an upstream browser bug ([read more](https://meta.discourse.org/t/-/397943/4?silent=true)).

- @tshenry closed the loop on a UX papercut around tag groups after a fix was confirmed, thanking @NateDhaliwal for the improvement ([read more](https://meta.discourse.org/t/-/397853/4?silent=true)).

- @pmusaraj actively triaged two **#discourse-id** support issues: requesting diagnostic details for a “signup button does nothing” incident involving `can't alloc thread` failures ([read more](https://meta.discourse.org/t/-/397895/4?silent=true)), and offering to clear duplicate redirect-URI credentials after a reinstall ([read more](https://meta.discourse.org/t/-/397991/2?silent=true)).

_Bonus meta-gardening signals:_ the ongoing cleanup conversation also cross-linked efforts like the “collaborative content gardening hub” initiative ([read more](https://meta.discourse.org/t/-/397606/48?silent=true)) and related About/Guidelines discussions that may need pruning/updating ([read more](https://meta.discourse.org/t/-/397882/4?silent=true), [read more](https://meta.discourse.org/t/-/324212/1?silent=true), [read more](https://meta.discourse.org/t/-/332161/1?silent=true), [read more](https://meta.discourse.org/t/-/396672/8?silent=true), [read more](https://meta.discourse.org/t/-/283213/32?silent=true)).

* * *

If yesterday taught us anything, it’s that **flex tiers are cheaper, cakedays can vanish on older stables, and Mi Browser will absolutely choose chaos**.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [11 maart 2026 om 05:01 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/769 "2026-03-11T05:01:44Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

Over the last 24 hours, meta saw **52 new posts** across **11 new topics** (plus ongoing discussions), spanning everything from #Self-hosting setup questions to #bug reports and #Dev theme API gotchas.

**Top users (posts / likes in the last 24h):**

| User | Posts | Likes |
| --- | --- | --- |
| @Falco | 3 | 9 |
| @Monikas | 3 | 5 |
| @Huskijore | 1 | 4 |
| @DavidO | 1 | 3 |
| @Lilly | 3 | 3 |
| @ToddZ | 3 | 3 |
| @lucy.sierracircuits | 2 | 2 |
| @RGJ | 2 | 2 |
| @martin | 1 | 2 |
| @awesomerobot | 2 | 2 |

* * *

## Interesting Topics

### #Self-hosting

- @Huskijore asked for a more direct way to jump into #chat—especially from iOS home screen shortcuts—and @awesomerobot pointed to a helpful theme component that can set a default chat channel [read more](https://meta.discourse.org/t/-/398082/3?silent=true) (see also: Default Chat Channel theme component [read more](https://meta.discourse.org/t/-/387112/1?silent=true)).

- @hritik explored running Discourse on a **sub-path** of a WordPress site for SEO reasons, and @ToddZ linked the canonical guide for “path prefix” installs [read more](https://meta.discourse.org/t/-/398033/2?silent=true) (related how-to: Serve Discourse from a subfolder/path prefix [read more](https://meta.discourse.org/t/-/30507/1?silent=true)).

- A long-running Cloudflare best-practices thread got fresh real-world WAF rule notes from @haydenjames, including protecting write endpoints while skipping WAF where appropriate for admin tooling [read more](https://meta.discourse.org/t/-/293405/26?silent=true) (with a nod to the [Data Explorer](https://meta.discourse.org/t/32566?silent=true) plugin context [read more](https://meta.discourse.org/t/-/32566/1?silent=true)).

### #customization:plugin

- @Monikas announced an ambitious “points mall” plugin—check-ins, shop, orders, makeup cards, and a ledger—while also flagging it’s still rough around the edges and _not yet recommended for production installs_ [read more](https://meta.discourse.org/t/-/398080/2?silent=true).

### #Support

- A permissions edge case came up: @eisammy wanted to disable #chat for moderators (keeping it admins-only), but responders noted moderators are always included when chat is enabled—changing that likely requires custom development [read more](https://meta.discourse.org/t/-/398048/3?silent=true).

- @pHneutre reported the “Upcoming events” menu icon showing as a default link icon under #calendar-and-event; @Falco confirmed it’s already fixed in newer Discourse versions (upgrade required) [read more](https://meta.discourse.org/t/-/398052/2?silent=true).

- @lucy.sierracircuits investigated why some members can’t upload multiple images per post; @Lilly suggested verifying settings, [safe mode](https://meta.discourse.org/t/53504?silent=true) tests, and checking browser console errors to narrow down theme/plugin interference [read more](https://meta.discourse.org/t/-/398088/4?silent=true).

- A multilingual admin question: @yingdong asked how to localize **badge** and **group** names so they follow the site/theme language switch [read more](https://meta.discourse.org/t/-/398127/1?silent=true).

- A moderation UX snag resurfaced: @Lydia2 couldn’t find an “unsilence” button for a mistakenly silenced user, and @Bas suggested toggling “silence” again to reset a potentially broken state [read more](https://meta.discourse.org/t/-/105988/11?silent=true).

- Theme devs revisited “custom fields in the post header”: @MarkDoerr explained older widget-based snippets are outdated, and shared a modern Glimmer Component pattern using `api.renderAfterWrapperOutlet` [read more](https://meta.discourse.org/t/-/106928/7?silent=true) (background: upcoming post stream/theme changes [read more](https://meta.discourse.org/t/-/372063/1?silent=true)).

### #bug

- @RGJ reported that **localized tags** aren’t being slugified in a way that’s safe for output (e.g., body classes like `tag-mijn-naam" (123)`), causing whitespace/quote-related breakage; @nat stepped in to investigate [read more](https://meta.discourse.org/t/-/398105/4?silent=true) (adjacent discussion referenced: “slug none” thread [read more](https://meta.discourse.org/t/-/397789/10?silent=true)).

### #ux

- In the #foundation-theme, @singi2016cn flagged a wrapped/awkward search button layout; @awesomerobot said they’ll prevent button text wrapping so the issue won’t recur after updating [read more](https://meta.discourse.org/t/-/398038/2?silent=true).

### #Dev

- Theme/JS modernization continued: @mattyoung tried migrating inline `<script type="text/discourse-plugin">` code into the newer admin JS pipeline, discovered `onPageChange` nuances, and shared a working `apiInitializer("1.0", ...)` solution [read more](https://meta.discourse.org/t/-/366482/50?silent=true).

### #Site Management

- Discourse AI’s spam tooling prompted a reporting/data question: @LotusJeff asked for detailed scan results behind the admin spam summary, and @Falco shared a simple [Data Explorer](https://meta.discourse.org/t/32566?silent=true) query hitting `ai_spam_logs` [read more](https://meta.discourse.org/t/-/343541/33?silent=true) ([Data Explorer](https://meta.discourse.org/t/32566?silent=true) plugin reference [read more](https://meta.discourse.org/t/-/32566/1?silent=true)).

- Form Templates got into the weeds on validation: @Eingang asked what _regex flavor_ is expected and why patterns appeared to “pass” unexpectedly [read more](https://meta.discourse.org/t/-/397564/6?silent=true).

### #blog

- @martin posted a companion discussion for the Discourse blog article on **Upcoming Changes** —a system designed to support gradual rollouts across highly customized instances [read more](https://meta.discourse.org/t/-/398118/1?silent=true).

### #General

- @DavidO shared a practical story about using Claude Code (via SSH/SFTP) to troubleshoot and revitalize a neglected forum stack, including config fixes and migration cleanup—an encouraging “AI as a sysadmin copilot” anecdote [read more](https://meta.discourse.org/t/-/398120/1?silent=true) (includes an S3/Spaces saga reference [read more](https://meta.discourse.org/t/-/391139/20?silent=true)).

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @Falco helped close the loop on an AI naming update, noting the “AI Persona → AI Agent” rename work landed via a PR from @sam [read more](https://meta.discourse.org/t/-/368198/13?silent=true).

- @Falco confirmed a known #calendar-and-event icon issue is already fixed in current Discourse and recommended updating for the “Upcoming events” icon regression [read more](https://meta.discourse.org/t/-/398052/2?silent=true).

- @Falco shared a practical [Data Explorer](https://meta.discourse.org/t/32566?silent=true) query for Discourse AI spam logs (`SELECT * FROM ai_spam_logs...`) to surface detailed scan data beyond the summary box [read more](https://meta.discourse.org/t/-/343541/33?silent=true).

- @awesomerobot guided a new #chat usability question toward an existing theme component (default chat channel) as a partial workaround for “open chat directly” requests [read more](https://meta.discourse.org/t/-/398082/3?silent=true).

- @awesomerobot acknowledged and patched a #foundation-theme UI issue by preventing button text wrapping; fix to land with the next Discourse update [read more](https://meta.discourse.org/t/-/398038/2?silent=true).

- @sam chimed in on the localized tag slugification bug with a related pointer (and helped route the investigation toward core changes) [read more](https://meta.discourse.org/t/-/398105/2?silent=true).

- @nat took ownership of investigating the localized-tag slugification/output issue after @RGJ’s detailed reproduction and explanation [read more](https://meta.discourse.org/t/-/398105/4?silent=true).

- @Bas responded to a tricky moderation UI state (missing unsilence control), suggesting a “toggle silence” reset as a pragmatic recovery step [read more](https://meta.discourse.org/t/-/105988/11?silent=true).

- @isaac confirmed a fix for “Error when editing a Wiki Topic” landed via core PR, and followed up when additional 500 errors were reported post-fix [read more](https://meta.discourse.org/t/-/397964/5?silent=true).

- @MarkDoerr provided updated guidance for post header customization in the post-stream’s modern component world, including a Glimmer component example and outlet usage [read more](https://meta.discourse.org/t/-/106928/7?silent=true).

- @gerhard weighed in on improving translation workflows (dreaming of in-context translations inside Discourse), noting practical constraints with Crowdin project structure [read more](https://meta.discourse.org/t/-/397946/4?silent=true).

_That’s a wrap—may your tags be safely slugified, your chat be one-tap-away, and your “resurrected” forums stay permanently undead (in a good way)._

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [12 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/770 "2026-03-12T05:02:19Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

**Last 24 hours (2026-03-11 → 2026-03-12)**

- **New posts:** 91
- **New topics:** 17

**Top users (posts / likes):**

| User | Posts | Likes |
| --- | --- | --- |
| @ToddZ | 7 | 8 |
| @Canapin | 4 | 7 |
| @Falco | 6 | 6 |
| @darkpixlz | 5 | 5 |
| @Lilly | 4 | 5 |
| @merefield | 1 | 5 |
| @Noble_Fish | 5 | 3 |
| @awesomerobot | 3 | 3 |
| @donaldsoncd | 1 | 3 |
| @pfaffman | 5 | 2 |

**Most active Discourse Team members (posts / likes):** @Falco (6/6), @awesomerobot (3/3), plus drive-by debugging and fixes from @martin, @Bas, @nat, @gerhard, @pmusaraj, and @sam across multiple threads (see details below).

* * *

## Interesting Topics

### #Support

- A tricky edge case with the #solved workflow appeared after a topic merge: @Silas-Inservio-Pax couldn’t mark _one specific_ reply as the solution, even though other replies worked; @martin traced it to an existing solved-record tied to the pre-merge topic and repaired it, while also flagging it for a preventative fix later. [read more](https://meta.discourse.org/t/-/398163/1?silent=true)

- The [Data Explorer](https://meta.discourse.org/t/32566?silent=true) API changed behavior: `limit=ALL` began returning invalid-parameter errors for hosted customers, and @Falco explained this was an intentional tightening (with practical guidance for paging results instead). The debugging trail is documented in the original report and follow-ups. [read more](https://meta.discourse.org/t/-/398172/1?silent=true) (also see the “reverse engineer” API tip that helped confirm endpoints: [read more](https://meta.discourse.org/t/-/20576/1?silent=true))

- Several “official” theme components mysteriously broke right after upgrading to `2026.3.0-latest`, but the root cause turned out to be an unrelated plugin error; @awesomerobot pointed to a missing module import and suggested confirming via [Safe Mode](https://meta.discourse.org/t/53504?silent=true) with plugins disabled to isolate the issue. [read more](https://meta.discourse.org/t/-/398143/1?silent=true) (related: the plugin being implicated was already discussed as broken elsewhere: [read more](https://meta.discourse.org/t/-/317785/1?silent=true))

- A practical theming question: how to add an intro paragraph above the groups list on `/g` without heavy customization. @ToddZ outlined a lightweight theme-component approach using the **After Header** outlet and scoped CSS, plus discussed why “two instances of the same theme component” is usually a fork-and-maintain situation. [read more](https://meta.discourse.org/t/-/398174/1?silent=true) (background references: [read more](https://meta.discourse.org/t/-/140787/1?silent=true), and the Versatile Banner idea: [read more](https://meta.discourse.org/t/-/109133/1?silent=true))

- Moderator capability boundaries came up: by default moderators _can_ delete users, but the thread converged on **category moderators** as the safer least-privilege fit for many communities (and included a nice “how we implemented it” mini-runbook). [read more](https://meta.discourse.org/t/-/398136/1?silent=true) (helpful related docs linked in-thread: permissions reference [read more](https://meta.discourse.org/t/-/224824/1?silent=true) and staff action logs overview [read more](https://meta.discourse.org/t/-/58022/1?silent=true))

- Assignments + API tokens: @ganncamp hit a mismatch where a read-scoped user token didn’t show group assignments the same way the UI does; @Falco clarified that the answer depends on the endpoint (and pointed to notifications filtering and a `direct` parameter behavior to include group-assigned items). [read more](https://meta.discourse.org/t/-/398168/1?silent=true)

- Onebox / OpenGraph failures that _only happen on one site_ were diagnosed as a TLS/certificate-chain issue: the same URL oneboxed on Meta, but failed on the reporter’s instance until they identified the server-side certificate chain problem. [read more](https://meta.discourse.org/t/-/398149/1?silent=true) (related troubleshooting guide referenced: [read more](https://meta.discourse.org/t/-/239715/1?silent=true))

- User deletion ran into a database constraint: deleting a user’s posts failed with `PG::ForeignKeyViolation` involving `reviewable_notes`; @darkpixlz confirmed it’s a bug and provided a current workaround (delete the note/comment first). [read more](https://meta.discourse.org/t/-/398175/1?silent=true) (workaround pointer: [read more](https://meta.discourse.org/t/-/397700/3?silent=true))

- Multilingual communities asked for localization of custom **badges** and **groups** (beyond posts/categories/tags). Current answer: it’s not supported yet, and only core strings will follow UI locale. [read more](https://meta.discourse.org/t/-/398127/1?silent=true)

- A “bot pacing” request: admins want AI Agents to respond _hours later_ (1–4h) so the bot feels like a participant rather than a chatbot. The current state: not supported as an AI feature; it likely belongs under future #automation improvements. [read more](https://meta.discourse.org/t/-/398209/1?silent=true) (closely related discussion: AI Agents thread [read more](https://meta.discourse.org/t/-/306099/29?silent=true) and scheduled replies feature request/precedent [read more](https://meta.discourse.org/t/-/149584/11?silent=true))

### #bug

- Form Templates appear to have a persistence bug: admins can select multiple templates for a category and see it work, but after refresh only one remains; @awesomerobot reproduced it and shared a short-term workaround (disable simplified category creation in upcoming changes). [read more](https://meta.discourse.org/t/-/398176/1?silent=true) (feature background: [read more](https://meta.discourse.org/t/-/278631/1?silent=true))

- A shared-edits wiki edge case: editing the latest version from post history opens the _wrong editor_ (non-collab), then saving errors and can temporarily blank the post until refresh. The report includes a suspected `PUT /t/.../tags` 422 angle and raises UX questions about hiding the button vs. enforcing the collaborative editor. [read more](https://meta.discourse.org/t/-/398145/1?silent=true)

- `discourse-subscriptions` boot failures on `v2026.3.0` were reported due to an apparently removed constant and confusing stack traces; @sam confirmed the constant exists in core routes and shipped a PR to remove the deprecation path. [read more](https://meta.discourse.org/t/-/398212/1?silent=true)

- A separate Form Templates/UI oddity was also flagged: changing the target audience for “Enable form templates” incorrectly creates an “Update Discourse” option in the left sidebar. [read more](https://meta.discourse.org/t/-/398151/1?silent=true)

### #ux

- Login page polish: the top logo alignment can shift off-center when a language switcher or dark/light toggle appears on the right, prompting a UX report with a clear screenshot. [read more](https://meta.discourse.org/t/-/398159/1?silent=true)

### #contribute:feature

- A new report idea was proposed: a **user self-engagement** report that professionals could generate as evidence for CPD/continuing education—filterable by date ranges and broken down by categories/tags/topics and types of engagement (read vs posted). [read more](https://meta.discourse.org/t/-/398148/1?silent=true)

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- **@martin** investigated and _directly fixed_ the “can’t mark reply as solution after merge” case by removing the conflicting solved-record (and noted it for a future preventative fix). [read more](https://meta.discourse.org/t/-/398163/13?silent=true)

- **@Falco** helped admins adapt to API and feature constraints across multiple threads: he explained why [Data Explorer](https://meta.discourse.org/t/32566?silent=true) no longer allows `limit=ALL` and how to page results safely [read more](https://meta.discourse.org/t/-/398172/6?silent=true), clarified which endpoint best matches the “assigned” UI list for automation work [read more](https://meta.discourse.org/t/-/398168/2?silent=true), and set expectations that “delayed AI replies” belongs to a future #automation overhaul rather than an AI toggle. [read more](https://meta.discourse.org/t/-/306099/30?silent=true)

- **@awesomerobot** narrowed down a post-upgrade “official components broken” report to a plugin import error and suggested [Safe Mode](https://meta.discourse.org/t/53504?silent=true) validation steps [read more](https://meta.discourse.org/t/-/398143/2?silent=true); reproduced the multi Form Templates persistence issue and shared a workaround via upcoming changes [read more](https://meta.discourse.org/t/-/398176/2?silent=true); and confirmed current limitations around localizing custom badges/groups for multilingual sites. [read more](https://meta.discourse.org/t/-/398127/2?silent=true)

- **@Bas** chimed in on an “unsilence” UI oddity with the memorable framing that the system “failed successfully,” while encouraging further reports if it recurs. [read more](https://meta.discourse.org/t/-/105988/13?silent=true)

- **@nat** confirmed a reported wiki editing error was fixed and merged upstream, pointing reporters to the merged core fix. [read more](https://meta.discourse.org/t/-/397964/10?silent=true)

- **@gerhard** supported translation contributors by explaining how “identical translation already saved” works in Crowdin workflows and offered to investigate specific language strings with the reporter. [read more](https://meta.discourse.org/t/-/14882/159?silent=true)

- **@pmusaraj** continued troubleshooting “new users can’t sign up” on small droplets by proposing a controlled reproduction on a fresh 1GB install to validate whether memory constraints are the true culprit. [read more](https://meta.discourse.org/t/-/397895/13?silent=true)

- **@sam** investigated the `discourse-subscriptions` boot crash report, clarified the deprecation/constant situation, looped in relevant maintainers, and followed up with a PR to remove the problematic deprecated usage path. [read more](https://meta.discourse.org/t/-/398212/2?silent=true)

* * *

If yesterday proved anything, it’s that on Meta _even when a task “fails successfully,”_ someone still finds the stray solved-record, pages the query instead of `limit=ALL`, and gets you back to green before your coffee cools.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [13 maart 2026 om 05:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/771 "2026-03-13T05:02:23Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

## Key Stats

- **New activity (last 24h):**  **80 new posts** across **12 new topics** , spanning #Support, #bug, #customization:plugin, #Announcements, and more (see today’s fresh threads like the webinar announcement [read more](https://meta.discourse.org/t/-/398295/1?silent=true) and the new banner workflow discussion [read more](https://meta.discourse.org/t/-/398306/1?silent=true)).

- **New topics opened (12):**  
#Announcements: [Webinar: Creating & Nurturing a Moderator Program](https://meta.discourse.org/t/-/398295/1?silent=true)  
#Support [Can no longer create global banners from restricted categories](https://meta.discourse.org/t/-/398306/1?silent=true), [How to understand the “Solved” locked status](https://meta.discourse.org/t/-/398266/1?silent=true)  
#Plugin: [📞 diskuz Call – Voice and video calls inside Discourse (P2P, no external apps)](https://meta.discourse.org/t/-/398331/1?silent=true)  
#Community\_Building: [How Old is Your Forum?](https://meta.discourse.org/t/-/398335/1?silent=true)  
#Marketplace [Install on my VPS](https://meta.discourse.org/t/-/398340/1?silent=true)  
#Bug: [Discourse states i have a notification](https://meta.discourse.org/t/-/398328/1?silent=true), [Bug clicked on user profile then scrolled](https://meta.discourse.org/t/-/398327/1?silent=true), [Discourse stopped polling my POP3 server](https://meta.discourse.org/t/-/398324/1?silent=true), [Group drop downs are not refreshed correctly with new groups](https://meta.discourse.org/t/-/398285/1?silent=true), [Set Topic Timer May Result in Catastrophic Failure](https://meta.discourse.org/t/-/398284/1?silent=true), [Category creation form loses entered data](https://meta.discourse.org/t/-/398275/1?silent=true)

- **Top users (posts / likes in the last 24h):**

> **Notable “still moving” threads:** localization fixes landed for tags [read more](https://meta.discourse.org/t/-/398105/7?silent=true), form templates got a fix merged [read more](https://meta.discourse.org/t/-/398176/4?silent=true), and a long-running “terminal Discourse” project shipped realtime notifications [read more](https://meta.discourse.org/t/-/395285/18?silent=true).

* * *

## Interesting Topics

#### #Support

- @nat dug into the reality of multilingual custom badges/groups: seeded badges are i18n-ready, but _custom_ badges aren’t fully supported without console access—plus a correction on why `/admin/customize/site_texts` can’t find keys that don’t exist yet (with a Rails-console `TranslationOverride` workaround) [read more](https://meta.discourse.org/t/-/398127/8?silent=true)

- A workflow change surprised admins: topics in read-restricted categories can’t be used as **global banners** anymore, prompting discussion about access control vs. practical “staff drafting areas,” plus interim workarounds like unlisted topics + automation scripts [read more](https://meta.discourse.org/t/-/398306/1?silent=true)

- “Solved” edge cases keep coming: one admin reported a _locked solution state_ where the solution can’t be deselected despite admin/mod context, hinting at a potential bug in how the “solved” control renders/locks [read more](https://meta.discourse.org/t/-/398266/1?silent=true)

- POP3 email-in reliability: a self-hosted site saw `Net::ReadTimeout` and Discourse stopped polling POP3 consistently, despite version updates and restarts—suggesting either provider latency, network changes, or retry/backoff behavior worth inspecting [read more](https://meta.discourse.org/t/-/398324/1?silent=true)

- Attachment pain on mobile: admins compared settings and symptoms around users being unable to upload multiple images at once (with hints toward “newuser max embedded media” and device-specific testing gaps) [read more](https://meta.discourse.org/t/-/398088/9?silent=true)

#### #bug

- A dashboard UX nuance: the **Site Traffic graph** may not rescale the Y-axis when toggling series—good for comparable metrics, confusing when one series dwarfs others—so the report scaling behavior may get smarter [read more](https://meta.discourse.org/t/-/397956/9?silent=true)

- A crisp regression report on category admin UX: typing into **“Position on category page”** can jump the view to the submit button and wipe previously-entered form fields, turning category creation into a frustrating redo loop [read more](https://meta.discourse.org/t/-/398275/1?silent=true)

- Group dropdowns may show newly-created groups in _some_ category settings (security) but not others (moderators) until a full page reload—suggesting stale client-side state or caching differences in admin UI [read more](https://meta.discourse.org/t/-/398285/1?silent=true)

- A “catastrophic failure” repro: scheduling a draft topic for later publishing with a missing/empty destination category, then trying again, allegedly triggers an unresponsive UI and repeating headers—strong symptoms of a front-end state corruption scenario [read more](https://meta.discourse.org/t/-/398284/1?silent=true)

- Notification “phantoms”: a user saw Discourse insist there was an unread notification even after reading it, raising the usual suspects (reload/cache) and broader frustration about async UI state consistency [read more](https://meta.discourse.org/t/-/398328/1?silent=true)

- User-card layering oddity: scrolling after opening a user card caused it to vanish and later render _over the composer/editor_, a classic z-index/positioning interaction bug report [read more](https://meta.discourse.org/t/-/398327/1?silent=true)

- Localized tags got a concrete fix: tag names produced via localization flows were coming back “dirty” (not slugified), but a merged cleanup + migration now aims to normalize existing and future tag outputs [read more](https://meta.discourse.org/t/-/398105/7?silent=true)

#### #customization:plugin

- A new entrant in Discourse calling: **diskuz Call** proposes peer-to-peer WebRTC voice/video inside Discourse, with signaling handled by the server and optional TURN for tough networks—calls from a floating button or 1:1 chat composer [read more](https://meta.discourse.org/t/-/398331/1?silent=true)

- The official **Discourse Signatures** plugin picked up meaningful new controls (group restrictions, category display rules, first-post-only mode, length and image caps, URL validation hardening), now merged upstream [read more](https://meta.discourse.org/t/-/42263/213?silent=true)

#### #Announcements

- A new webinar is on deck: **Creating & Nurturing a Moderator Program** , covering moderator models, role definition, and long-term engagement—with a replay promised after the event [read more](https://meta.discourse.org/t/-/398295/1?silent=true)

#### #Community\_Building

- “How old is your forum?” prompted community storytelling: migrations from mailing lists, phpBB, Ning, and more—plus the perennial comparison of longevity vs. “active since year one” retention [read more](https://meta.discourse.org/t/-/398335/1?silent=true)

#### #Marketplace

- A self-host install request sparked a reminder that Discourse’s official installer is effectively a one-liner (and includes options like free subdomains), making “VPS setup” less intimidating than it sounds [read more](https://meta.discourse.org/t/-/398340/2?silent=true)

#### #customization:extras

- The “Clip To Discourse” Chrome extension shipped **text selection support** , auto-detecting highlighted content and adding a dedicated “Text Selection” clip style—while aiming toward Discourse User API authorization for easier onboarding [read more](https://meta.discourse.org/t/-/392335/7?silent=true)

- `termcourse` (terminal-based Discourse client) added realtime notifications via MessageBus so you can refresh when topic lists update—plus discussion about aligning keyboard shortcuts with core Discourse for muscle-memory parity [read more](https://meta.discourse.org/t/-/395285/18?silent=true)

* * *

## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group

- @nat corrected and refined guidance on custom badge localization—first explaining i18n behavior, then clarifying that custom badge translation keys don’t exist in the admin UI unless created (e.g., via Rails console `TranslationOverride`) [read more](https://meta.discourse.org/t/-/398127/8?silent=true). @nat also shared that a fix and migration landed for “dirty” localized tag names [read more](https://meta.discourse.org/t/-/398105/7?silent=true).

- @Danielle announced the upcoming moderator-program webinar and confirmed that a replay will be posted after the live event [read more](https://meta.discourse.org/t/-/398295/3?silent=true).

- @dax explained why banner topics are now gated (read-restricted topics can’t be used as banners), and outlined a workaround using **unlisted** topics plus the Automation script approach [read more](https://meta.discourse.org/t/-/398306/2?silent=true), with a follow-up reinforcing the automation requirement when the UI pin flow disappears for unlisted topics [read more](https://meta.discourse.org/t/-/398306/11?silent=true).

- @isaac clarified the access-control risk behind restricted-category banners: banner content can become visible broadly, and admins may not realize the visibility implications when drafting privately [read more](https://meta.discourse.org/t/-/398306/6?silent=true).

- @supermathie marked a pragmatic support boundary for broken mobile-browser text-selection toolbars, recommending supported browsers and noting limits when the problematic browser isn’t available through normal channels for reproduction/testing [read more](https://meta.discourse.org/t/-/397943/6?silent=true).

- @jamie.wilson merged improvements into the official Discourse Signatures plugin (new restrictions, caps, and hardened URL validation), keeping defaults backward-compatible [read more](https://meta.discourse.org/t/-/42263/213?silent=true).

- @chapoi acknowledged that the dashboard graph scaling behavior was intentional but doesn’t fit the reported scenario well, and committed to exploring smarter rescaling [read more](https://meta.discourse.org/t/-/397956/9?silent=true). @chapoi also pointed to a fix for an iPad composer peek-mode layout issue [read more](https://meta.discourse.org/t/-/396942/10?silent=true).

- @awesomerobot merged a fix for multiple “Form templates” per category not working, noting it should be available after updating Discourse [read more](https://meta.discourse.org/t/-/398176/4?silent=true). @awesomerobot also requested console-error inspection on a potentially bugged “Solved” locked state [read more](https://meta.discourse.org/t/-/398266/4?silent=true), and responded on AI sentiment analysis compliance questions by emphasizing provider/config dependence and recommending local legal counsel for regulatory certainty [read more](https://meta.discourse.org/t/-/355901/7?silent=true).

- @martin confirmed that a fix is in progress for a “cannot mark reply as solution after merge” workflow issue, suggesting a near-term workaround while engineering continues [read more](https://meta.discourse.org/t/-/398163/16?silent=true).

* * *

If yesterday proved anything, it’s that Discourse can host a webinar, a banner debate, _and_ a terminal client—while someone, somewhere, is already trying to place a WebRTC call from inside a topic.

[Previous page](https://meta.discourse.org/t/daily-summary-5am-utc/291851.md?page=26)

[Next page](https://meta.discourse.org/t/daily-summary-5am-utc/291851.md?page=28)