# Resumo Diário (5h UTC)

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

<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: [Março 14, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/772 "2026-03-14T05:01:43Z")

</div>

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

## Key Stats

- **New posts (last 24h): 43**
- **New topics (last 24h): 10**

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

- @Falco — **4 posts** , **15 likes** (e.g. capacity update in [read more](https://meta.discourse.org/t/-/390985/12?silent=true))
- @Canapin — **4 posts** , **5 likes** (active in community discussion: [read more](https://meta.discourse.org/t/-/398335/8?silent=true))
- @chapoi — **3 posts** , **5 likes** (docs pointer + fixes: [read more](https://meta.discourse.org/t/-/394773/13?silent=true))
- @LotusJeff — **3 posts** , **5 likes** (community-building insights: [read more](https://meta.discourse.org/t/-/398335/13?silent=true))
- @supermathie — **2 posts** , **4 likes** (email regression note + feature idea: [read more](https://meta.discourse.org/t/-/393621/23?silent=true))
- @ばこん — **2 posts** , **3 likes** (plugin question: [read more](https://meta.discourse.org/t/-/395104/28?silent=true))
- @pacharanero — **1 post** , **3 likes** (new guide: [read more](https://meta.discourse.org/t/-/398378/1?silent=true))
- @elmuerte — **1 post** , **3 likes** (migration + forum history: [read more](https://meta.discourse.org/t/-/398335/5?silent=true))
- @Ed_S — **1 post** , **2 likes** (forum origin story: [read more](https://meta.discourse.org/t/-/398335/6?silent=true))
- @satonotdead — **1 post** , **2 likes** (detailed recovery steps: [read more](https://meta.discourse.org/t/-/152978/9?silent=true))

* * *

## Interesting Topics

### #community-building Building

- @LotusJeff’s “elder forums” roll-call turned into a mini case study on _why some communities survive platform shifts_ (phpBB/vBulletin → Discourse, Facebook leakage, and the “Discourse bump”), with migration notes from @elmuerte and graphs from @Canapin. [How Old is Your Forum?](https://meta.discourse.org/t/-/398335/5?silent=true)

### #Announcements (#ai)

- Discourse AI hosted LLM capacity got a major bump across plans, plus model and performance improvements (token limits and speed). @Falco posted the new limits table and pointed folks to updated pricing. [Unlock All Discourse AI Features with Our Hosted LLM](https://meta.discourse.org/t/-/390985/12?silent=true)

### #Support

- A “randomly logging everyone out” mystery ended up being a classic Cloudflare-origin IP pitfall: ban one IP and you’ve effectively banned everyone. @Falco asked if the Cloudflare template is enabled in `app.yml`. [Our Forum Seems To Be Logging Everyone Out](https://meta.discourse.org/t/-/398408/3?silent=true)

- A staging upgrade to `2026.3.0-latest` appeared to stop showing **username + real name** together; a likely culprit is the “same username/name” suppression behavior + the setting to force both to display. [Username + real name not working in 2026.3.0-latest](https://meta.discourse.org/t/-/398407/2?silent=true)

- A subtle permissions/UI question: should **about-page hidden groups** stay hidden even for members of **about page extra groups** (e.g. admins)? The current behavior seemed surprising enough to warrant clarification. [About page hidden groups and about page extra groups](https://meta.discourse.org/t/-/398417/1?silent=true)

- Theme-specific gotcha: sites using the #ghost-theme noticed **views/reply counts only appear for categories that have subcategories** , due to how the theme’s container renders. [Subcategories and Categories with no subcategories don’t show views/reply counts](https://meta.discourse.org/t/-/398418/1?silent=true)

- A Chinese-language #ai support question reported tool-calling timeouts (`Operation timed out - FinalDestination::HTTP`); @Falco asked which specific tool was timing out to narrow next steps. [Discourse ai 的工具调用超时如何解决？](https://meta.discourse.org/t/-/398355/2?silent=true)

- A practical “recovery cookbook” got added for people migrating **uploads from S3 to local disk** and ending up with `transparent.png`: recreate missing `uploads` records from orphaned files, then rebake. [Re-adding missing uploads to the database](https://meta.discourse.org/t/-/152978/9?silent=true)

### #bug

- Two fresh tablet/search regressions were reported on [try.discourse.org](http://try.discourse.org): one where the **floating search box won’t close** after rotating to portrait, and another where typed characters appear **reversed** (e.g. “thing” → “gniht”). [Floating search box cannot be closed…](https://meta.discourse.org/t/-/398427/1?silent=true) and [The order of characters… is reversed](https://meta.discourse.org/t/-/398423/1?silent=true)

- Chat settings confusion resurfaced: disabling chat made the chat preferences section disappear (and `/preferences/chat` redirects away). A prior related report was referenced for comparison. [聊天功能被禁用后，其设置消失。](https://meta.discourse.org/t/-/398401/1?silent=true) (see also [Once chat is disabled it cannot be enabled any more](https://meta.discourse.org/t/-/217271/1?silent=true))

- Notifications edge-case: @chapoi noted that some “phantom notification” issues can be effectively _impossible to solve perfectly_ due to complexity—while still acknowledging the frustration and discouraging rants. [Discourse states i have a notification](https://meta.discourse.org/t/-/398328/5?silent=true)

### #contribute:feature

- A UX improvement proposal: admins on a **multisite guest** who hit `/sidekiq` currently get a confusing error; the request is to add an explanatory hint so it better matches the “law of least surprise.” [Hint to admin why they can’t see /sidekiq on a multisite guest](https://meta.discourse.org/t/-/398415/1?silent=true) (context: [read more](https://meta.discourse.org/t/-/398397/7?silent=true))

- Private calendar ergonomics continued to improve: authenticated ICS feed access is already in progress, but the follow-up is making User API Key generation _non-technical-user friendly_. [Authenticated ICS feeds for private calendar events](https://meta.discourse.org/t/-/393203/4?silent=true)

### #Dev

- Discourse dev + LLM workflows: a thread about Claude and Discourse-related development emphasized that models need _guardrails_ and up-to-date docs; @chapoi pointed out the dev docs are now back in the core repo. [Claude & Discourse-related development. How good is it?](https://meta.discourse.org/t/-/394773/13?silent=true)

- Markdown alternatives: replacing Markdown with Quarkdown was deemed not feasible without effectively extending `markdown-it` to replicate needed features. [Can Markdown be replaced with Quarkdown](https://meta.discourse.org/t/-/398341/2?silent=true)

### #users (#ai #mcp)

- A new step-by-step guide landed for connecting **Discourse MCP** to OpenCode CLI, framing MCP as three components (forum, MCP server, and client) and encouraging people to “use your LLM” to follow the setup. [Discourse MCP Setup in OpenCode CLI](https://meta.discourse.org/t/-/398378/1?silent=true) (related: [Discourse MCP setup in OpenAI Codex CLI](https://meta.discourse.org/t/-/397662/1?silent=true))

* * *

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

- **@Falco**

- **@chapoi**

- **@supermathie**

- **@sam**

* * *

_May your Cloudflare bans be un-banned, your uploads rebaked, and your tablet search boxes stop typing in reverse—see you tomorrow, Meta adventurers._

---

<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: [Março 15, 2026, 5:02am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/773 "2026-03-15T05:02:04Z")

</div>

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

## Key Stats

**In the last 24 hours (2026-03-14 → 2026-03-15):**

- **48** new posts
- **6** new topics (see today’s fresh threads: [forum acquisition](https://meta.discourse.org/t/-/398452/1?silent=true), [reversed floating search input](https://meta.discourse.org/t/-/398423/3?silent=true), [AI translation also translating tags](https://meta.discourse.org/t/-/398440/1?silent=true), [article list images / course-like structure](https://meta.discourse.org/t/-/398435/1?silent=true), [missing attachment click counters](https://meta.discourse.org/t/-/398453/1?silent=true), [Bilibili inline player TC](https://meta.discourse.org/t/-/398438/1?silent=true))

**Top posters (posts • likes received):**

- **@Falco** — 4 posts • 10 likes
- **@Timelord** — 5 posts • 4 likes
- **@itsbhanusharma** — 1 post • 4 likes
- **@nat** — 1 post • 4 likes
- **@Canapin** — 1 post • 4 likes
- **@darkpixlz** — 2 posts • 3 likes
- **@pfaffman** — 1 post • 2 likes
- **@satonotdead** — 3 posts • 2 likes
- **@chapoi** — 2 posts • 2 likes
- **@merefield** — 1 post • 1 like

> Quote of the day: while debugging a weird search issue, @Canapin suggested searching _only palindromes_ as a workaround—because why not? ([read more](https://meta.discourse.org/t/-/398423/2?silent=true))

* * *

## Interesting Topics

### #Support

- @Timelord asked how to merge content from another Discourse without a full backup/restore in **“Forum Aquisition”** , and @itsbhanusharma pointed to the canonical “move topics between instances” approach ([read more](https://meta.discourse.org/t/-/398452/1?silent=true); reference: [read more](https://meta.discourse.org/t/-/38930/1?silent=true)).

- In a Chinese-language support thread about AI translation, @nat explained that enabling the **“Experimental tag settings page”** lets admins edit tag localizations when AI translation also translates tag text ([read more](https://meta.discourse.org/t/-/398440/2?silent=true)).

- @Engineer_Abdallah explored using Discourse as an _articles + courses_ platform (with images/video/code/files), and @chapoi suggested the **Topic List Thumbnails** theme component to get more visual “front page” presentation ([read more](https://meta.discourse.org/t/-/398435/1?silent=true); suggested TC: [read more](https://meta.discourse.org/t/-/150602/1?silent=true)).

- @Eviepayne reported that **attachment click counters** no longer appear (even when using `|attachment`), and asked if the previous counter behavior can be restored ([read more](https://meta.discourse.org/t/-/398453/1?silent=true)).

- In a long-running “install on a VPS” help thread, the discussion ranged from DIY installs to safer maintenance workflows (including @pfaffman’s one-click upgrade dashboard mention) and what to expect from hosted support ([read more](https://meta.discourse.org/t/-/398340/8?silent=true); hosting/legal process note: [read more](https://meta.discourse.org/t/-/398340/12?silent=true)).

- A LinkedIn OAuth setup got unstuck when @alanr reminded folks the redirect URL must exactly match what LinkedIn expects (example callback path included) ([read more](https://meta.discourse.org/t/-/375899/4?silent=true)).

- A tricky sign-up failure investigation continued: @asc linked reproduction to toggling **local login** , along with errors mentioning missing MaxMind DB files and Discourse ID auth failures ([read more](https://meta.discourse.org/t/-/397895/14?silent=true)).

### #bug

- A fresh regression report claims the **new category settings UI** can leave “Solved” _stuck on_: once enabled, it can’t be deselected because the controls move/disappear between settings screens ([read more](https://meta.discourse.org/t/-/398439/1?silent=true)).

- Another bug report described the **floating search widget** reversing character order on certain setups; @Falco couldn’t reproduce on Edge/Android/Gboard and suggested testing other keyboards ([read more](https://meta.discourse.org/t/-/398423/3?silent=true)).

### #contribute:feature

- In the reactions/likes UI discussion, @soraiden asked how to expand the “and X more…” list of reactors, and @Falco confirmed the team is working on a new UI component to support this cleanly ([read more](https://meta.discourse.org/t/-/389820/24?silent=true); question context: [read more](https://meta.discourse.org/t/-/389820/23?silent=true)).

### #Integrations (#ai, #how-to)

- The **Google Programmable Search Engine / Custom Search API** situation appears to have shifted again: @Falco noted the relevant Google capability was discontinued and said Discourse is researching alternative providers (and thinking about supporting “native search tools” bundled with major LLM providers) ([read more](https://meta.discourse.org/t/-/307107/15?silent=true); more context: [read more](https://meta.discourse.org/t/-/307107/13?silent=true)).

### #customization:theme component

- A new theme component: **“Bilibili Inline Player”** was shared as a _no-rebuild_ alternative to the server-side plugin approach, with setup steps and a comparison to the existing OneBox/plugin solution ([read more](https://meta.discourse.org/t/-/398438/1?silent=true); related plugin thread: [read more](https://meta.discourse.org/t/-/389149/1?silent=true)).

- The **Banner Featured Links** component got a practical compatibility refresh: @eisammy swapped deprecated `htmlSafe` usage for `trustHTML`, and @Arkshine shipped an update/cleanup with a detailed changelog and tests ([read more](https://meta.discourse.org/t/-/327497/24?silent=true); update notes: [read more](https://meta.discourse.org/t/-/327497/27?silent=true)).

### #customization:plugin

- In the official **Discourse OpenID Connect (OIDC)** plugin thread, @Steradiant asked about syncing Discourse groups from OIDC group claims, pointing to an older PR that implemented it and asking whether it could be included ([read more](https://meta.discourse.org/t/-/103632/320?silent=true)).

- The **Geo Blocking** plugin thread clarified Cloudflare specifics: @RGJ confirmed it works with Cloudflare (with proper setup) and corrected a misunderstanding about what `CF-IPCountry` contains, while noting the plugin uses Discourse’s internal MaxMind DB ([read more](https://meta.discourse.org/t/-/227824/36?silent=true); question: [read more](https://meta.discourse.org/t/-/227824/35?silent=true); referenced Cloudflare guide: [read more](https://meta.discourse.org/t/-/293405/1?silent=true)).

### #Using Discourse

- In a reference thread on **filtering topic lists** , @cmdntd asked whether `/filter` can be used _within a category context_ to keep the left-side navigation (cat menu / sidebar) in place ([read more](https://meta.discourse.org/t/-/375558/19?silent=true)).

### #Support (#ai, #ai-sentiment)

- On AI Sentiment backfilling, @satonotdead asked about populating sentiment further back than the default window, and @Falco clarified that the last **60 days** backfill is automatic once enabled (and the thread continues with debugging questions) ([read more](https://meta.discourse.org/t/-/309270/16?silent=true); original question: [read more](https://meta.discourse.org/t/-/309270/15?silent=true)).

* * *

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

- **@Falco** weighed in on multiple product/ops threads:

- **@nat** provided the solution for AI translation translating tags: enable the **Experimental tag settings page** and edit localizations there ([read more](https://meta.discourse.org/t/-/398440/2?silent=true)).

- **@chapoi** helped connect “Discourse as articles/courses” needs to existing UI building blocks by recommending **Topic List Thumbnails** ([read more](https://meta.discourse.org/t/-/398435/2?silent=true)), and also questioned whether a “missing counts” report was truly theme-caused by checking the Ghost theme preview behavior ([read more](https://meta.discourse.org/t/-/398418/2?silent=true)).

* * *

If today’s search box starts typing backwards, remember @Canapin’s wisdom: _stick to palindromes and you’ll still get the right query_ ([read more](https://meta.discourse.org/t/-/398423/2?silent=true)).

---

<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: [Março 16, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/774 "2026-03-16T05:01:54Z")

</div>

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

## Key Stats

**In the last 24 hours (2026-03-15 → 2026-03-16):**

- **New posts:** 33
- **New topics:** 4

**Top posters (with likes received on their latest posts):**

| User | Posts | Likes |
| --- | --- | --- |
| @Canapin | 4 | 6 |
| **@awesomerobot** | 2 | 4 |
| @NateDhaliwal | 2 | 3 |
| @darkpixlz | 3 | 2 |
| @Tealk | 1 | 2 |
| @sk-or-v1-contents | 2 | 1 |
| **@Falco** | 2 | 1 |
| @merefield | 1 | 1 |
| @amotl | 2 | 1 |
| **@renato** | 2 | 1 |

> Team activity highlights are captured below, with direct links to the posts they participated in.

* * *

## Interesting Topics

### #ux

- @祁同伟 reported that when the composer has too many buttons, the later buttons become inaccessible; the thread explored horizontal scrolling affordances, gradient hints, and whether the scroll arrow should appear on touch devices (or only “narrow screens / coarse pointers”) in [编辑器按钮较多时，靠后的按钮不可见](https://meta.discourse.org/t/-/398473/1?silent=true) — including the “arrow hidden on touch” detail at [read more](https://meta.discourse.org/t/-/398473/6?silent=true) and the safe-mode observation at [read more](https://meta.discourse.org/t/-/398473/8?silent=true).

### #Site feedback

- In the ongoing experiment thread, @Canapin shared a clever (but now blocked) workflow for requesting edits to old posts via flags, and @darkpixlz offered a pragmatic solution by making the target post a wiki in [Experiment: Collaborative content gardening hub for meta](https://meta.discourse.org/t/-/397606/50?silent=true) (with the wiki workaround at [read more](https://meta.discourse.org/t/-/397606/51?silent=true)). The discussion also referenced the original content needing edits in [A way to monitor user uploaded files](https://meta.discourse.org/t/-/358635/2?silent=true) and the plugin follow-up in [Topic Gallery](https://meta.discourse.org/t/-/394953/1?silent=true).

- The same conversation pointed to a process note: staff-attention DMs often stay open and can be used to continue a moderation request without starting a new public thread, referencing [A post in “A way to monitor user uploaded files” requires staff attention](https://meta.discourse.org/t/-/396989/1?silent=true) as an example of where that workflow surfaced.

### #customization:plugin (#activitypub #experimental)

- ActivityPub implementers compared logs and confirmed repeatable behavior around handle validation / lookup flows (notably `/webfinger/handle/validate` followed by actor lookup), adding real-world diagnostics to the long-running [ActivityPub Plugin](https://meta.discourse.org/t/-/266794/478?silent=true) thread.

### #Support

- DiscourseAI users troubleshooting Sentiment found a classic self-hosting pitfall: missing internal IPs in `allowed internal hosts`. The thread then moved into whether a deeper historical backfill is feasible and safe in [Problems setting up Sentiment](https://meta.discourse.org/t/-/309270/19?silent=true), with staff pointing back to the canonical setup guide [Self-Hosting Sentiment and Emotion for DiscourseAI](https://meta.discourse.org/t/-/334451/1?silent=true) and clarifying questions at [read more](https://meta.discourse.org/t/-/309270/20?silent=true).

- A hosted customer asked how to recover _specific_ missing CDN assets (one image and two JSON attachments) after a hiccup in [Restoring individual CDN attachments after a hiccup](https://meta.discourse.org/t/-/398493/1?silent=true), including concrete examples of what disappeared at [read more](https://meta.discourse.org/t/-/398493/2?silent=true).

- A theme developer hit intermittent `500` errors when uploading via CLI tooling, prompting requests for logs and a side discussion on whether they meant the Discourse Theme CLI; see [Getting error while uploading theme](https://meta.discourse.org/t/-/398471/1?silent=true) with debugging guidance at [read more](https://meta.discourse.org/t/-/398471/2?silent=true). The thread also linked to the relevant docs: [Install the Discourse Theme CLI console app to help you build themes](https://meta.discourse.org/t/-/82950/1?silent=true) and [Installing a theme or theme component](https://meta.discourse.org/t/-/63682/1?silent=true).

- In that same upload issue, logs suggested plugin/theme interactions, and @merefield advised removing a noisy third-party plugin to stabilize the build in [Getting error while uploading theme](https://meta.discourse.org/t/-/398471/9?silent=true) (after the error-log excerpt surfaced at [read more](https://meta.discourse.org/t/-/398471/7?silent=true)).

- Tablet users reported a particularly strange UX bug: text entered into the _floating search widget_ appears in reverse order, which @sk-or-v1-contents traced to floating keyboard behavior (notably Sogou IME on Xiaomi) in [The order of characters when typing in the floating search widget is reversed](https://meta.discourse.org/t/-/398423/5?silent=true) and follow-ups at [read more](https://meta.discourse.org/t/-/398423/6?silent=true).

- A theme-related display regression was suspected when category lists stopped showing replies/views in categories _without_ subcategories; the discussion pointed toward #TAG ghost-theme as the likely cause in [Subcategories and Categories with no subcategories don’t show views/reply counts](https://meta.discourse.org/t/-/398418/3?silent=true).

- A request came in to embed videos from Bunny Stream, but Discourse only rendered a generic link preview; the thread asks what’s required for onebox/embed support in [Allow Embedded Video from Bunny CDN stream service](https://meta.discourse.org/t/-/398491/1?silent=true).

### #bug

- Anchor links that worked externally but failed _within_ a topic appeared resolved after a core change; the report was marked as no longer reproducible and queued for closure in [Anchor links not working within Discourse - but work from outside the topic](https://meta.discourse.org/t/-/397748/7?silent=true).

### #General

- A lively AI-admin anecdote: using Claude Code + SSH to revive and migrate a “dead” vBulletin forum sparked discussion about how coding agents are changing admin workflows in [Claude Code - Resurected Dead vBulletin from 2016](https://meta.discourse.org/t/-/398120/2?silent=true).

### #users (#ai #mcp)

- The OpenAI Codex CLI + MCP setup thread saw a follow-up post deleted by its author, leaving the main configuration discussion as the primary reference point in [Discourse MCP Setup in OpenAI Codex CLI](https://meta.discourse.org/t/-/397662/2?silent=true).

* * *

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

- @awesomerobot dug into mobile/touch behavior around horizontally scrollable composer toolbars, first suspecting theme CSS interference and recommending [safe mode](https://meta.discourse.org/t/53504?silent=true) checks in [编辑器按钮较多时，靠后的按钮不可见](https://meta.discourse.org/t/-/398473/4?silent=true), then explaining that Discourse intentionally hides the scroll arrow on touch devices (and questioning whether that should change) at [read more](https://meta.discourse.org/t/-/398473/6?silent=true).

- @renato added a nuanced UX refinement: instead of “touch device detection,” the arrow-display logic might be better keyed off _screen width_ or the presence of a “fine pointer,” since touch-enabled laptops complicate the current heuristic in [编辑器按钮较多时，靠后的按钮不可见](https://meta.discourse.org/t/-/398473/7?silent=true). @renato also confirmed an anchor-link issue appears fixed after a merged core PR and scheduled the report to close in [Anchor links not working within Discourse - but work from outside the topic](https://meta.discourse.org/t/-/397748/7?silent=true).

- @Falco continued support on DiscourseAI Sentiment, steering the reporter toward the self-hosting guide and then asking clarifying questions about whether any data (e.g., last 60 days) was successfully backfilled in [Problems setting up Sentiment](https://meta.discourse.org/t/-/309270/18?silent=true) and [read more](https://meta.discourse.org/t/-/309270/20?silent=true), with the referenced guide here: [Self-Hosting Sentiment and Emotion for DiscourseAI](https://meta.discourse.org/t/-/334451/1?silent=true).

* * *

If yesterday taught meta anything, it’s that _between resurrecting ancient vBulletin installs and chasing missing UI arrows, the real “scroll” was the troubleshooting we did along the 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: [Março 17, 2026, 5:02am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/775 "2026-03-17T05:02:21Z")

</div>

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

## Key Stats

- **New posts (last 24h):** 69
- **New topics (last 24h):** 9

### Top users (posts / likes)

| User | Posts | Likes | Recent reference |
| --- | --- | --- | --- |
| @chapoi | 6 | 12 | Debugging theme/component deprecations in [Templating of my “component” broke. How do I fix it?](https://meta.discourse.org/t/-/398553/7?silent=true) |
| @merefield | 4 | 8 | Handling proxy/republishing concerns in [My forum can be accessed using someone else’s URL](https://meta.discourse.org/t/-/398517/4?silent=true) |
| @das-g | 10 | 6 | Deep-diving theme modernization in [Templating of my “component” broke. How do I fix it?](https://meta.discourse.org/t/-/398553/1?silent=true) |
| @Lee_Ars | 1 | 5 | Updated field notes in [Using Discourse with Cloudflare: Best Practices](https://meta.discourse.org/t/-/293405/28?silent=true) |
| @dax | 2 | 4 | Category title placeholder update in [More friendly category creation](https://meta.discourse.org/t/-/390841/19?silent=true) |
| @martin | 2 | 4 | New defaults for Q&A-style categories in [Easily create Support categories using the discourse-solved plugin](https://meta.discourse.org/t/-/398338/1?silent=true) |
| @mae | 1 | 4 | New blog companion thread: [How Discourse Is Becoming a Community of Writers](https://meta.discourse.org/t/-/398571/1?silent=true) |
| @RGJ | 1 | 3 | Naming conventions discussion in [Is there a naming convention for theme component projects?](https://meta.discourse.org/t/-/398572/5?silent=true) |
| @ばこん | 3 | 3 | Proxy/URL mirroring concern in [My forum can be accessed using someone else’s URL](https://meta.discourse.org/t/-/398517/1?silent=true) |
| @awesomerobot | 1 | 2 | Repo naming guidance in [Is there a naming convention for theme component projects?](https://meta.discourse.org/t/-/398572/2?silent=true) |

### Other threads that saw fresh replies (worth a skim)

A handful of ongoing/older discussions also moved forward, including automations formatting quirks in [How can I enter special formatting like [wrap], in the text field of automations?](https://meta.discourse.org/t/-/391347/10?silent=true), Discourse AI tool timeouts in [Discourse ai 的工具调用超时如何解决？是否可以调整discourse超时时间，如何调整？](https://meta.discourse.org/t/-/398355/5?silent=true), Discourse ID signup troubleshooting in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/15?silent=true), and search/voting filtering tips in [Discourse Topic Voting](https://meta.discourse.org/t/-/40121/317?silent=true) (_plus a side question about category vs bug triage_ in [The order of characters when typing in the floating search widget is reversed](https://meta.discourse.org/t/-/398423/7?silent=true)).

* * *

## Interesting Topics

### #Dev

- @das-g’s footer sponsor component started rendering template directives _literally_ after updates; @chapoi traced it to modernization work and deprecated patterns like `registerConnectorClass`, pointing toward plugin outlets (e.g. `above-footer`) and newer theme structures ([read more](https://meta.discourse.org/t/-/398553/7?silent=true)). Background pointers referenced in-thread include modern outlet patterns ([read more](https://meta.discourse.org/t/-/32727/1?silent=true)) and theme docs ([read more](https://meta.discourse.org/t/-/91966/1?silent=true), [read more](https://meta.discourse.org/t/-/93648/1?silent=true)).

- Continuing that migration thread, @das-g asked how to correctly reference **theme assets** (images/fonts) from Glimmer/strict-mode templates without hitting scope errors (e.g. helper resolution failures), with a nudge toward `settings.theme_uploads...` usage ([read more](https://meta.discourse.org/t/-/398578/1?silent=true)). The discussion explicitly ties back to the broken footer work ([read more](https://meta.discourse.org/t/-/398553/1?silent=true)) and the long-running assets guide it builds on ([read more](https://meta.discourse.org/t/-/62459/1?silent=true)).

- Naming conventions for Discourse theme component repos got some practical proposals: while nothing is enforced, patterns like `discourse-` prefixes and community conventions like `discourse-tc-` surfaced as a way to quickly distinguish components vs themes vs plugins ([read more](https://meta.discourse.org/t/-/398572/2?silent=true)).

- A small but impactful docs fix: @das-g flagged broken links in the longstanding “Theme Developer Quick Reference Guide,” and @tshenry patched them promptly ([read more](https://meta.discourse.org/t/-/110448/11?silent=true)).

- Localization workflow clarity: when a PR needs translations, the guidance was that contributors handle **English** and automation/community translation processes take care of the rest ([read more](https://meta.discourse.org/t/-/398585/2?silent=true)).

### #Announcements / #bug

- Discourse made it _much_ easier to create Q&A-style **Support** categories by turning on sensible defaults for the #solved experience during category creation (notably “Allow topic owner and staff to mark a reply as the solution”) ([read more](https://meta.discourse.org/t/-/398338/1?silent=true)). In related #bug news, there’s also an acknowledged issue where some admins are **unable to disable solved** once enabled in a category—@martin indicated a fix is in progress ([read more](https://meta.discourse.org/t/-/398439/4?silent=true)). (For baseline context, the Solved plugin reference is here: [read more](https://meta.discourse.org/t/-/30155/1?silent=true).)

### #ux

- Category composition got another quality-of-life enhancement: you can now set **title placeholders per category** , and it’s been confirmed as “in core” (with commit references in-thread) ([read more](https://meta.discourse.org/t/-/390841/19?silent=true)). This dovetails with prior asks about category-specific title prompts ([read more](https://meta.discourse.org/t/-/205219/4?silent=true)).

### #Support

- A creative (and uncomfortable) scenario: a site owner reported their forum being accessible via someone else’s URL/proxy, and the pragmatic takeaway was that you can’t fully prevent public mirroring without making the site private—focus on account monitoring and privacy controls when needed ([read more](https://meta.discourse.org/t/-/398517/4?silent=true)).

- Cloudflare operational notes got two angles today: real-world configuration updates were added to the Cloudflare best-practices guide (including reminders like ensuring the Cloudflare template is in `app.yml`) ([read more](https://meta.discourse.org/t/-/293405/28?silent=true)), and a separate “everyone is getting logged out” report tied the symptoms to Cloudflare/IP visibility and moderation actions (e.g. banning what looks like a shared IP) ([read more](https://meta.discourse.org/t/-/398408/4?silent=true)).

- A “core bug” turned out to be a theme interaction: a report that “Username + real name” display wasn’t working on 2026.3.0-latest was resolved by using [safe mode](https://meta.discourse.org/t/53504?silent=true) to identify a theme setting (“Remove name suppression on posts”) as the culprit ([read more](https://meta.discourse.org/t/-/398407/5?silent=true)).

- Sidebar link normalization appears to be breaking certain external URLs: if an external URL contains the site’s own hostname _inside a query parameter_, the hostname may be stripped, breaking redirect-style flows (with a workaround involving URL-encoding / direct DB write) ([read more](https://meta.discourse.org/t/-/398537/1?silent=true)).

- Embedding video from Bunny Stream was solved with the straightforward approach: allow the provider’s iframe host via the `allowed iframes` setting, using Bunny’s embed URL format ([read more](https://meta.discourse.org/t/-/398491/2?silent=true)).

### #customization:plugin

- The #activitypub plugin thread continued diagnosing an actor-discovery mismatch: @pmusaraj could find `@announcements@meta.discourse.org` elsewhere, while the reporter on 2026.3.0-latest could not—prompting version/config comparisons ([read more](https://meta.discourse.org/t/-/266794/479?silent=true)).

### #Site feedback

- Meta’s own category re-organization work surfaced a UX gotcha: “index” links may be _visually present_ but effectively unclickable because the whole box captures the click, preventing link interaction—@mcwumbly confirmed the behavior and outlined why it happens ([read more](https://meta.discourse.org/t/-/396306/56?silent=true)).

### #blog

- Discourse published a reflection on internal culture and craft: writing as a core practice for clearer thinking, stronger collaboration, and better decision-making—now mirrored on Meta as a companion discussion topic ([read more](https://meta.discourse.org/t/-/398571/1?silent=true)).

* * *

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

- @chapoi helped troubleshoot a theme/component regression by connecting console deprecations (notably `registerConnectorClass`) to ongoing Glimmer modernization—and pointed to plugin outlets and theme documentation for refactoring paths ([Templating of my “component” broke. How do I fix it?](https://meta.discourse.org/t/-/398553/7?silent=true)). @chapoi also shipped/pointed to a structural fix so custom elements render consistently in category topic lists (with a PR reference) ([Subcategories and Categories with no subcategories don’t show views/reply counts](https://meta.discourse.org/t/-/398418/7?silent=true)).

- @awesomerobot clarified that there’s **no enforced naming convention** for theme components, but common signals include `discourse-` prefixes, `about.json` for themes/components, and `plugin.rb` for plugins ([Is there a naming convention for theme component projects?](https://meta.discourse.org/t/-/398572/2?silent=true)).

- @martin announced a streamlined “Support category” creation flow built on the #solved plugin defaults ([Easily create Support categories using the discourse-solved plugin](https://meta.discourse.org/t/-/398338/1?silent=true)), and followed up on a bug where disabling Solved after enabling can fail—flagging that a fix is coming ([Unable to disable the solved feature for categories after it has been enabled](https://meta.discourse.org/t/-/398439/4?silent=true)).

- @mae opened the companion discussion for Discourse’s latest blog post on writing culture and how it shapes the company and product ([How Discourse Is Becoming a Community of Writers](https://meta.discourse.org/t/-/398571/1?silent=true)).

- @dax highlighted that per-category **topic title placeholders** are now available in core ([More friendly category creation](https://meta.discourse.org/t/-/390841/19?silent=true)) and confirmed the same enhancement on an older support question ([Is it possible to change Topic Title prompt for a category?](https://meta.discourse.org/t/-/205219/4?silent=true)).

- @supermathie solved an embed issue by explaining how to allow Bunny Stream iframes via site settings, including an example `<iframe>` snippet ([Allow Embedded Video from Bunny CDN stream service](https://meta.discourse.org/t/-/398491/2?silent=true)).

- @pmusaraj continued troubleshooting in the experimental #activitypub plugin thread by asking for version details and comparing actor discovery behavior across instances ([ActivityPub Plugin](https://meta.discourse.org/t/-/266794/479?silent=true)); and also pushed forward diagnosis on Discourse ID signup failures by asking for credential regeneration and a review of auth-related settings ([New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/15?silent=true)).

- @Falco pressed for concrete reproduction details (tool + request specifics) to unblock debugging of Discourse AI tool-call timeouts ([Discourse ai 的工具调用超时如何解决？是否可以调整discourse超时时间，如何调整？](https://meta.discourse.org/t/-/398355/5?silent=true)).

- @renato shared that copying special formatting (like `[wrap]`) into automation fields has seen improvements via recent merges, while also outlining why rich clipboard HTML can interfere with markdown-intended input ([How can I enter special formatting like [wrap], in the text field of automations?](https://meta.discourse.org/t/-/391347/10?silent=true)).

- @tshenry fixed broken directory links after they were reported in the theme developer quick reference topic ([Theme Developer Quick Reference Guide](https://meta.discourse.org/t/-/110448/12?silent=true)).

* * *

Yesterday’s vibe: we taught footers to speak modern Glimmer _and_ made Support categories better at declaring “Solved”—a pretty on-brand day for 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: [Março 18, 2026, 5:02am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/776 "2026-03-18T05:02:13Z")

</div>

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

## Key Stats

In the last 24 hours, Meta saw **97 new posts** across **13 new topics** , spanning everything from account-security workflows to docs navigation experiments (e.g. [read more](https://meta.discourse.org/t/-/398627/1?silent=true), [read more](https://meta.discourse.org/t/-/398691/1?silent=true), [read more](https://meta.discourse.org/t/-/398616/1?silent=true)).

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

| User | Posts | Likes | Recent highlight |
| --- | --- | --- | --- |
| @gingerbeardman | 5 | 5 | iOS composer becoming unresponsive in-app: [read more](https://meta.discourse.org/t/-/398604/1?silent=true) |
| @chapoi | 5 | 4 | Clarifying iOS wrapper vs platform-specific behavior: [read more](https://meta.discourse.org/t/-/398604/5?silent=true) |
| @itsbhanusharma | 4 | 8 | Pushing back on “needs console” for hacked accounts: [read more](https://meta.discourse.org/t/-/398627/4?silent=true) |
| @dccmuseum | 4 | 3 | Detailing what’s still painful in compromised-account recovery: [read more](https://meta.discourse.org/t/-/398627/3?silent=true) |
| @merefield | 3 | 4 | Pointing to the _right_ way to set upload limits: [read more](https://meta.discourse.org/t/-/398601/3?silent=true) |
| @manuel | 3 | 3 | Digging into docs category UX + index duplication: [read more](https://meta.discourse.org/t/-/396306/58?silent=true) |
| @sam | 3 | 3 | Announcing an experimental “Suggested Edits” plugin: [read more](https://meta.discourse.org/t/-/398691/1?silent=true) |
| @Falco | 6 | 3 | Shipping authenticated ICS feeds + troubleshooting clients: [read more](https://meta.discourse.org/t/-/393203/5?silent=true) |
| @Moin | 2 | 4 | Review-queue triggers + dynamic group strategy: [read more](https://meta.discourse.org/t/-/398648/6?silent=true) |
| @Andro | 2 | 3 | Diagnosing “512m maximum allowed” upload confusion: [read more](https://meta.discourse.org/t/-/398601/1?silent=true) |

> Notable “sticky note” from self-hosting: **“data never goes from development to Production.”** — @merefield in a workflow discussion: [read more](https://meta.discourse.org/t/-/398655/3?silent=true)

* * *

## Interesting Topics

### #Self-hosting

- **Compromised account recovery UX vs needing Rails console:** @dccmuseum argued that mitigation steps (email/password/session reset) shouldn’t feel console-dependent, while @itsbhanusharma outlined admin-UI alternatives and tradeoffs (including suspension/deactivation) in [Dealing with a hacked user account should not require the console](https://meta.discourse.org/t/-/398627/1?silent=true).

- **“How do you move changes from dev to prod?” (and what _not_ to do):** A practical thread on deployment mindset for Docker installs, with @Falco pointing folks back to plugin/theme workflows and @merefield emphasizing backups aren’t a dev→prod transport in [What’s yall’s work-flow like?](https://meta.discourse.org/t/-/398655/1?silent=true).

- **Admin UI breakage after upgrading to v3.5.3:** A report (in Chinese) showing missing admin modules + safe-mode observations, with a reminder that v3.5.3 is out of support in [升级至v3.5.3之后管理员页面出现异常](https://meta.discourse.org/t/-/398634/1?silent=true).

### #Support

- **Per-user “always approve posts” moderation:** @haydenjames asked for a built-in way to force approval for specific users; @Moin suggested a dynamic-groups approach as a workaround strategy in [Force post approval for specific users only?](https://meta.discourse.org/t/-/398648/1?silent=true) (with pointers to review triggers [here](https://meta.discourse.org/t/-/398648/4?silent=true) and dynamic group logic [here](https://meta.discourse.org/t/-/398648/6?silent=true)).

- **Upload limits: nginx config resets + Docker best practice:** @Andro hit confusing “512m maximum allowed” failures even for a 30MB PDF, then realized container edits revert; @merefield pointed to updating `app.yml` correctly in [Maxmum upload size](https://meta.discourse.org/t/-/398601/1?silent=true).

- **Replacing Discourse search with SearchUnify:** A short “is this possible?” integration question in [SearchUnify Search bar](https://meta.discourse.org/t/-/398650/1?silent=true).

### #ux

- **Moderation queue wording confusion (“Is this post something else or spam?”):** @peternlewis flagged an awkward yes/no prompt and asked for clearer action labeling, with follow-up examples of other queue weirdness in [“Is this post something else or spam?”](https://meta.discourse.org/t/-/398686/1?silent=true).

- **What should the homepage be for doc categories (index vs latest vs overview)?** @mcwumbly proposed routing doc-category clicks to an index/overview, while @manuel raised deeper scanning/navigation issues with the current sidebar layout in [What should the homepage be for doc categories?](https://meta.discourse.org/t/-/398616/1?silent=true).

### #Site feedback

- **Meta category organization + docs index duplication:** @manuel noted that index topics can appear in multiple places (sidebar generation, pinned topic list, description links) and suggested simplifying, while @mcwumbly compared pin behavior and called it a docs-plugin usability gap in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/58?silent=true).

### #customization:plugin

- **Experimental plugin: “Suggested Edits” (Wikipedia-style contributions with reviewer control):** @sam announced **Discourse Suggested Edits** as an experimental plugin designed for granular review/acceptance of changes without granting full edit rights in [Discourse Suggested Edits](https://meta.discourse.org/t/-/398691/1?silent=true).

### #contribute:feature

- **Authenticated ICS feeds for private calendar events (merged) + client compatibility debugging:** @Falco merged authenticated feeds and then investigated why Google Calendar/Outlook might show no events despite valid VEVENTs, including mention of a fix for old recurring events in [Authenticated ICS feeds for private calendar events](https://meta.discourse.org/t/-/393203/5?silent=true).

### #bug

- **“Solved” category setting can’t be disabled after enabling (fix inbound):** @martin shared that a fix is coming and UI will be refined before merge in [Unable to disable the solved feature for categories after it has been enabled](https://meta.discourse.org/t/-/398439/5?silent=true).

- **Chat member list scrolling regressions on iOS/iPadOS (proposed fix):** A patch proposal to rework the scroll container and prevent width overflow for long usernames in [FIX: Further fix for Chat-settings/member list failing to scroll on IOS/iPadOS…](https://meta.discourse.org/t/-/398683/1?silent=true).

### #Support (Discourse ID)

- **New user signup failures + “can’t alloc thread” Sidekiq errors:** A debugging thread where safe-mode behavior, plugin/theme elimination, and resource constraints (1GB droplet + swap considerations) came up in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/22?silent=true).

### #community-building Building

- **Embedding Discourse as a comment platform: redirect-to-login causing junk topics (fixed):** @Falco reported reproducing and fixing an embedUrl redirect issue in the long-running thread [Should Discourse make an effort to become a viable comment platform?](https://meta.discourse.org/t/-/274455/69?silent=true).

* * *

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

- @chapoi focused on client/platform troubleshooting, asking for version constraints and noting iOS “wrapper” behavior isn’t the whole story in [Unable to exit editing post](https://meta.discourse.org/t/-/398604/2?silent=true), plus confirming there’s **no built-in per-user approval toggle** in [Force post approval for specific users only?](https://meta.discourse.org/t/-/398648/2?silent=true). (Also wrapped up a theme/dev support thread in [Templating of my “component” broke. How do I fix it?](https://meta.discourse.org/t/-/398553/13?silent=true).)

- @sam posted a new experimental plugin announcement for granular edit review in [Discourse Suggested Edits](https://meta.discourse.org/t/-/398691/1?silent=true), clarified localization/doc workflow expectations in [If a PR needs localization what do we do?](https://meta.discourse.org/t/-/398585/4?silent=true), and tied docs policy rethinking to Suggested Edits in [Discourse documentation policy](https://meta.discourse.org/t/-/322621/2?silent=true).

- @Falco had a packed day: merging authenticated ICS feeds and troubleshooting downstream calendar clients in [Authenticated ICS feeds for private calendar events](https://meta.discourse.org/t/-/393203/5?silent=true), advising proper self-hosted customization workflows in [What’s yall’s work-flow like?](https://meta.discourse.org/t/-/398655/2?silent=true), fixing an embed redirect bug in [Should Discourse make an effort to become a viable comment platform?](https://meta.discourse.org/t/-/274455/69?silent=true), and asking about API latency vs the 10s timeout in [Discourse ai 的工具调用超时如何解决？](https://meta.discourse.org/t/-/398355/7?silent=true).

- @manuel continued shaping Meta’s information architecture, discussing index-topic duplication and desired docs-category behavior in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/58?silent=true) and exploring navigation patterns in [What should the homepage be for doc categories?](https://meta.discourse.org/t/-/398616/2?silent=true).

- @mcwumbly raised the “doc category homepage” question directly in [What should the homepage be for doc categories?](https://meta.discourse.org/t/-/398616/1?silent=true) and compared pin/unpin behavior during the category re-org discussion in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/59?silent=true).

- @martin gave a concrete “fix is coming” update for a Solved-settings UI issue in [Unable to disable the solved feature for categories after it has been enabled](https://meta.discourse.org/t/-/398439/5?silent=true), and followed up on category templates for Solved-enabled support setups in [Easily create Support categories using the discourse-solved plugin](https://meta.discourse.org/t/-/398338/3?silent=true).

- @dax confirmed a UX improvement for banner creation workflows (pinning unlisted topics) in [Can no longer create global banners from restricted categories](https://meta.discourse.org/t/-/398306/15?silent=true).

- @awesomerobot corroborated that the composer can become unresponsive (also seen in PWA usage), helping validate the report in [Unable to exit editing post](https://meta.discourse.org/t/-/398604/6?silent=true).

- @pmusaraj prompted further investigation by requesting plugin details during signup troubleshooting in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/20?silent=true).

- @supermathie helped triage the same signup thread by verifying Discourse ID signups worked on their end and pointing out that “can’t alloc thread” suggests system-level constraints in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/24?silent=true).

* * *

Sign-off: After a day of **suggested edits, hacked-account hardening, and calendar-feed detective work** , Meta’s vibe is clear: ship the fix, refine the UX, and keep the puppies safe.

---

<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: [Março 19, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/777 "2026-03-19T05:01:44Z")

</div>

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

## Key Stats

- **New activity (last 24h):**  **94** new posts across **9** new topics.
- **Top users by recent activity (posts) + appreciation (likes):**

| User | Posts | Likes |
| --- | --- | --- |
| @Moin | 13 | 13 |
| @Arkshine | 2 | 10 |
| @david | 1 | 10 |
| @chapoi | 7 | 6 |
| @pmusaraj | 2 | 5 |
| @davidb | 1 | 4 |
| @WaitroseCarpark | 1 | 4 |
| @awesomerobot | 2 | 4 |
| @darkpixlz | 5 | 4 |
| @ChrisBeach | 2 | 3 |

- **Tags/themes showing up repeatedly:** #chat (e.g. [read more](https://meta.discourse.org/t/-/398401/11?silent=true), [read more](https://meta.discourse.org/t/-/397571/11?silent=true)), moderation/review UX (e.g. [read more](https://meta.discourse.org/t/-/398686/3?silent=true)), self-hosting & upgrades (e.g. [read more](https://meta.discourse.org/t/-/398634/11?silent=true)), and dev tooling changes (e.g. #dev-news via [read more](https://meta.discourse.org/t/-/398713/1?silent=true)).

- **More threads with fresh replies worth a peek (grab-bag):** plugin build bundling ([read more](https://meta.discourse.org/t/-/398713/1?silent=true)) and precompiled assets context ([read more](https://meta.discourse.org/t/-/376700/1?silent=true)); review-queue UX + related visual bugs ([read more](https://meta.discourse.org/t/-/398686/5?silent=true), [read more](https://meta.discourse.org/t/-/393403/1?silent=true)); “dismiss” admin notice expectations ([read more](https://meta.discourse.org/t/-/398754/1?silent=true), plus background at [read more](https://meta.discourse.org/t/-/329504/9?silent=true)); tablet table layout gap investigation ([read more](https://meta.discourse.org/t/-/333153/9?silent=true)); solved-category setup improvements ([read more](https://meta.discourse.org/t/-/398338/6?silent=true)) and solved toggle bug fix ([read more](https://meta.discourse.org/t/-/398439/6?silent=true)); email bounce docs update ([read more](https://meta.discourse.org/t/-/45343/207?silent=true)); and ongoing translation/UI-text concerns ([read more](https://meta.discourse.org/t/-/396962/4?silent=true)).

## Interesting Topics

### #Dev

- @david announced **a new, mostly backwards-compatible build system for plugin JavaScript** , aligning plugins with the modern theme build pipeline and enabling faster rebuilds, better caching, and native ES modules ([read more](https://meta.discourse.org/t/-/398713/1?silent=true)). This also ties into efforts to ship more precompiled assets for self-hosters ([read more](https://meta.discourse.org/t/-/376700/1?silent=true)).

### #ux

- A moderation-review wording/flow issue: the prompt **“Is this post something else or spam?”** confused people because “X or Y” is logically always “yes”; @awesomerobot suggested switching to more generic copy when multiple flag types are combined ([read more](https://meta.discourse.org/t/-/398686/5?silent=true)). Related: visual oddities in moderator actions were cross-referenced to an older report ([read more](https://meta.discourse.org/t/-/393403/1?silent=true)) and to a long-running lowercase-conversion translation problem ([read more](https://meta.discourse.org/t/-/325608/2?silent=true)).

- “Dismiss” that doesn’t dismiss: @darkpixlz reported that the **HTTPS / reverse-proxy advice banner reappears even after dismissal** , prompting discussion of whether “dismiss” is intended as a permanent hide vs. a “fix underlying issue” nudge ([read more](https://meta.discourse.org/t/-/398754/1?silent=true)). @Moin linked the broader explanation of current notice behavior and the idea of adding “snooze” in the future ([read more](https://meta.discourse.org/t/-/329504/9?silent=true)).

- RTL polish: a new report notes the **reply icon variant isn’t switching properly in the profile menu for RTL languages** like Arabic/Persian, despite other UI areas using an RTL-correct icon ([read more](https://meta.discourse.org/t/-/398766/1?silent=true)).

- Locale-aware title cleanup: a quick question about whether **`title_remove_extraneous_space` should be disabled by default** concluded with @Moin pointing out it’s already locale-overridden (enabled for English, disabled for non-English defaults) ([read more](https://meta.discourse.org/t/-/398709/2?silent=true)). Background: the original behavior discussion lives here ([read more](https://meta.discourse.org/t/-/134320/3?silent=true)) and the setting details were referenced here ([read more](https://meta.discourse.org/t/-/382521/1?silent=true)).

### #bug

- A long-running UI glitch where the page “jumps” after opening a user card got more data: @Arkshine reproduced it and suggested the **chat plugin’s CSS might be contributing** ([read more](https://meta.discourse.org/t/-/398327/14?silent=true)). The thread also re-covered troubleshooting via [safe mode](https://meta.discourse.org/t/53504?silent=true) to isolate customizations ([read more](https://meta.discourse.org/t/-/53504/1?silent=true)).

- Mobile/tablet rendering: the **large gap below tables on tablets** got a fix queued—@chapoi pointed to a change for permanent visibility ([read more](https://meta.discourse.org/t/-/333153/6?silent=true)) and later confirmed a targeted fix landed ([read more](https://meta.discourse.org/t/-/333153/9?silent=true)).

- Chat admin/settings reliability: in a Chinese-language report, **chat settings disappear after chat is disabled** ; @j.jaffeux indicated a fix would ship shortly and asked for confirmation if still broken ([read more](https://meta.discourse.org/t/-/398401/11?silent=true)).

- Another chat UX fix proposal: a patch thread continues work on **iOS/iPadOS scrolling issues and member-list layout overflow** , with @j.jaffeux planning to test and @chapoi leaving implementation feedback ([read more](https://meta.discourse.org/t/-/398683/2?silent=true), [read more](https://meta.discourse.org/t/-/398683/3?silent=true)).

### #Self-hosting

- Upgrade woes after moving to 2026.1.1: a self-hosted admin reported **admin pages breaking after upgrading** , but the deployment details revealed a Kubernetes + “web\_only” approach; replies clarified what’s supported and suggested typical rebuild steps, while noting the k8s approach is outside standard support paths ([read more](https://meta.discourse.org/t/-/398634/11?silent=true), [read more](https://meta.discourse.org/t/-/398634/13?silent=true)).

### #Announcements

- Free plan beta clarification: @mattdm asked whether the Free tier allows “public site + some private categories,” and @pmusaraj clarified **Free sites can be entirely public or entirely private, but can’t mix with additional private categories** (beyond the seeded Staff category) ([read more](https://meta.discourse.org/t/-/395632/35?silent=true)).

### #Support

- “Where can I try Chat?”: a new user asked for **examples of Discourse Chat “in the wild”** ; @Moin recommended trying it on the sandbox and explained options to experiment via hosted trials/free plan ([read more](https://meta.discourse.org/t/-/398769/2?silent=true)) referencing the Free plan beta topic ([read more](https://meta.discourse.org/t/-/395632/1?silent=true)).

### #contribute:feature

- Email templates refinement: a feature request proposes an option so notification emails can display **just the subcategory name** (when present) instead of always showing “Category/Subcategory” ([read more](https://meta.discourse.org/t/-/398772/1?silent=true)).

- Likes/reactions visibility: a new request argues that when a post has many likes, it’s **no longer possible to see the full list of users** ; the suggestion is to allow another click to fully expand the list ([read more](https://meta.discourse.org/t/-/398756/1?silent=true)). This was also merged into the broader, older feature conversation about exposing all reactions/likes ([read more](https://meta.discourse.org/t/-/389820/27?silent=true)).

- AI + automation ideas continue: a new #ai request asks whether Discourse would ship an **official OpenClaw “skill”** to let an authenticated user instruct an agent to perform forum actions (including reposting authorized content into categories with tags) ([read more](https://meta.discourse.org/t/-/398771/1?silent=true)). For context, there’s already an “OpenClaw plugin for Discourse integration” thread exploring adjacent workflows ([read more](https://meta.discourse.org/t/-/397239/8?silent=true)).

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

- @david introduced a **new plugin JS build system** with caching, ES module output, and a path toward bundling precompiled code for popular plugins ([read more](https://meta.discourse.org/t/-/398713/1?silent=true)), explicitly tying into the precompiled-assets direction for self-hosters ([read more](https://meta.discourse.org/t/-/376700/1?silent=true)).

- @awesomerobot jumped into the **review-queue UX confusion** around “Is this post something else or spam?”, identified a “standalone yes button” as a bug, and proposed more generic phrasing when multiple flag types are combined ([read more](https://meta.discourse.org/t/-/398686/3?silent=true), [read more](https://meta.discourse.org/t/-/398686/5?silent=true)).

- @chapoi had a busy day across UI and bugfixes: they investigated the **tablet table-builder gap** and linked/landed fixes ([read more](https://meta.discourse.org/t/-/333153/6?silent=true), [read more](https://meta.discourse.org/t/-/333153/9?silent=true)), reviewed a proposed **iOS/iPadOS chat scrolling fix** with some follow-up comments ([read more](https://meta.discourse.org/t/-/398683/3?silent=true)), and helped debug a **500 error when splitting/merging topics** by asking for browser-console clues and edge cases like solutions in the posts ([read more](https://meta.discourse.org/t/-/398678/4?silent=true)).

- @pmusaraj clarified Discourse’s **Free plan beta limitations** around private categories on otherwise public sites ([read more](https://meta.discourse.org/t/-/395632/35?silent=true)) and wrapped up a support thread by advising that “disabled” plugins may still run code—suggesting complete removal from `app.yml` while isolating login issues ([read more](https://meta.discourse.org/t/-/397895/25?silent=true)).

- @davidb confirmed a bug fix for **marking a reply as the solution after a merge** , linking to the commit and noting it was already deployed to the affected site ([read more](https://meta.discourse.org/t/-/398163/19?silent=true)).

- @j.jaffeux addressed multiple Chat-related items: they gave an imminent-fix ETA for **chat settings disappearing when chat is disabled** ([read more](https://meta.discourse.org/t/-/398401/11?silent=true)), acknowledged a patch thread and planned testing for **iOS/iPadOS scrolling/member-list overflow fixes** ([read more](https://meta.discourse.org/t/-/398683/2?silent=true)), and clarified that **pinned chat messages are not destroyed** ([read more](https://meta.discourse.org/t/-/397571/11?silent=true)).

- @martin noted progress on a bug where admins were **unable to disable “solved” after enabling it for categories** ([read more](https://meta.discourse.org/t/-/398439/6?silent=true)) and responded to feedback on the “support category” creation flow—agreeing to adjust confusing wording and avoid forced-lowercase strings that break translations ([read more](https://meta.discourse.org/t/-/398338/6?silent=true)).

- @sam helped triage a report of **500 errors when splitting topics** , requesting logs and clarifying whether the instance was hosted or self-hosted to guide next steps ([read more](https://meta.discourse.org/t/-/398678/2?silent=true), [read more](https://meta.discourse.org/t/-/398678/5?silent=true)).

- @mcwumbly did some housekeeping by closing a feature request as a duplicate and pointing to the canonical thread on **visibility of who has access to restricted categories** ([read more](https://meta.discourse.org/t/-/131575/7?silent=true), [read more](https://meta.discourse.org/t/-/20938/1?silent=true)).

* * *

If today’s threads taught anything, it’s that Meta users are as persistent as that “dismissed” reverse-proxy warning that keeps coming back ([read more](https://meta.discourse.org/t/-/398754/1?silent=true)).

---

<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: [Março 20, 2026, 5:02am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/778 "2026-03-20T05:02:33Z")

</div>

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

## Key Stats

- **New posts (last 24h): 102**
- **New topics (last 24h): 16**

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

| User | Posts | Likes |
| --- | --- | --- |
| @Moin | 20 | 21 |
| @david | 2 | 8 |
| @nat | 3 | 8 |
| @lindsey | 1 | 8 |
| @darkpixlz | 2 | 7 |
| @Canapin | 3 | 6 |
| @zogstrip | 2 | 6 |
| @awesomerobot | 2 | 5 |
| @nathank | 2 | 4 |
| @haydenjames | 2 | 3 |

* * *

## Interesting Topics

### #Announcements

- @lindsey published **Current Projects – March 2026** , highlighting shipped work like the now-official _Blog Post Styling_ component and hosted **Discourse AI credit limit increases** (plus continued work on AI Agents) — with a translation workflow question raised by @Moin about whether the component should land in Crowdin or via PRs [read more](https://meta.discourse.org/t/-/398565/1?silent=true). (Related: _Blog Post Styling_ [read more](https://meta.discourse.org/t/-/110841/1?silent=true))

- The **“Easily create Support categories using the discourse-solved plugin”** announcement thread continued with UI/text formatting and i18n nuance, as @Moin suggested using existing lowercase translation keys to avoid breaking style guidance [read more](https://meta.discourse.org/t/-/398338/8?silent=true). (Related formatting guidance: [read more](https://meta.discourse.org/t/-/324637/1?silent=true))

### #Dev

- In the #dev-news thread on the **new plugin build system** , @david confirmed the new compiler is now enabled by default on `latest`, marking a meaningful shift for plugin developers and build pipelines [read more](https://meta.discourse.org/t/-/398713/2?silent=true).

- A self-hosting-oriented question popped up in the long-running RFC on **Discourse versioning strategy** , asking what the _actual_ `app.yml` configuration should look like when pinning an ESR/release branch [read more](https://meta.discourse.org/t/-/383536/52?silent=true).

### #bug

- A spate of upload failures (422 with a generic “upload failed” error) was reported when trying to upload a GIF; @nat acknowledged the issue and then confirmed it was fixed shortly after [read more](https://meta.discourse.org/t/-/398808/1?silent=true). (Anecdotal “took several attempts” corroboration: [read more](https://meta.discourse.org/t/-/398808/2?silent=true))

- A report on **ActivityPub + Mastodon OAuth** failing with `The requested scope is invalid, unknown, or malformed` suggests a compatibility/config mismatch in the authorization step, with a video reproduction included [read more](https://meta.discourse.org/t/-/398803/1?silent=true).

- iPad/iOS Chat UI stability continued improving: a patch thread reported further fixes for **Chat settings/member list scrolling** and overflow issues, with additional iPadOS testing noted [read more](https://meta.discourse.org/t/-/398683/4?silent=true).

### #ux

- A German locale UI issue was flagged where “Click to upload…” text overflows the placeholder; @zogstrip pointed to a PR that will introduce a more robust layout (likely via wrapping/line breaks) [read more](https://meta.discourse.org/t/-/398782/1?silent=true).

- Discourse ID’s **referring-site branding** visibility was called out as too subtle at the moment users are deciding whether they’re in the right place; @pmusaraj requested mockups to explore clearer hierarchy between Discourse ID and the originating site [read more](https://meta.discourse.org/t/-/398828/1?silent=true). (Related “flow friction” follow-up: [read more](https://meta.discourse.org/t/-/397991/4?silent=true))

- Another RTL polish item: the **reply icon under profile for RTL languages** was acknowledged and queued for fix via PR, continuing the steady RTL UI refinement stream [read more](https://meta.discourse.org/t/-/398766/2?silent=true).

- A microcopy oddity was spotted in Discourse AI Agent messaging: **“Default llm” appearing redundantly before “Default LLM”** in an error string, raising questions about string composition or translation keys [read more](https://meta.discourse.org/t/-/398845/1?silent=true).

- A broader moderation-workflow UX debate continued around the flagging prompt **“Is this post something else or spam?”** with feedback that yes/no patterns and “Approve” labeling can be confusing when the moderator intent is “spam → delete/block” [read more](https://meta.discourse.org/t/-/398686/10?silent=true).

### #Site\_feedback

- A request to expand **[try.discourse.org](http://try.discourse.org)** so people can test admin/mod tooling (and concerns about the instance not “clean resetting”) drew pushback: community members emphasized why public admin access is unsafe, and suggested alternatives like spinning up free/trial instances instead [read more](https://meta.discourse.org/t/-/398843/1?silent=true). (Prior art: “[try.discourse.org](http://try.discourse.org) as moderator/admin” [read more](https://meta.discourse.org/t/-/187919/1?silent=true); free plan beta invite [read more](https://meta.discourse.org/t/-/395632/1?silent=true))

- Meta category organization discussion briefly reignited the long-running confusion around **pinned/unpin site settings** , with calls to improve descriptions and/or consolidate options so the user-default vs global settings are clearer [read more](https://meta.discourse.org/t/-/396306/62?silent=true). (Related: pinned settings usability thread [read more](https://meta.discourse.org/t/-/386365/7?silent=true); “official groups posts” reference point [read more](https://meta.discourse.org/t/-/386255/9?silent=true))

### #General

- A searchability gap was reported: the **Guidelines/FAQ don’t appear in search** , even for unique phrases, prompting discussion about `/guidelines` being a static page and/or category restrictions preventing indexing [read more](https://meta.discourse.org/t/-/398838/1?silent=true).

### #Support

- A discoverability complaint: **where to find “Releases”** now that releases have a dedicated site, with suggestions to add links in more obvious places (footer, tag descriptions, or “New to Discourse” onboarding) [read more](https://meta.discourse.org/t/-/398854/1?silent=true). (Pointers: January 2026 releases [read more](https://meta.discourse.org/t/-/393903/1?silent=true); introducing [releases.discourse.org](http://releases.discourse.org) [read more](https://meta.discourse.org/t/-/392712/1?silent=true); “New to Discourse” hub [read more](https://meta.discourse.org/t/-/1/1?silent=true))

- A least-privilege API snag: the **Discourse MCP server** fails validation with scoped “granular access” API keys because it can’t read `about.json`, raising a question of what endpoints should be required/allowed for MCP integrations [read more](https://meta.discourse.org/t/-/398792/1?silent=true).

- A new install enabling **discourse-subscriptions** hit “Error loading route” immediately; troubleshooting began by requesting logs/console output, while reminding that Stripe + webhooks + plugin settings need to be completed first [read more](https://meta.discourse.org/t/-/398809/1?silent=true). (Related canonical setup guide: [read more](https://meta.discourse.org/t/-/140818/1?silent=true); ongoing payment-method error concerns: [read more](https://meta.discourse.org/t/-/392185/2?silent=true))

* * *

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

- **@lindsey** kicked off the March roadmap update in #Announcements, outlining what shipped and what’s in progress (including AI changes and feature naming updates) in [Current Projects – March 2026](https://meta.discourse.org/t/-/398565/1?silent=true).

- **@david** delivered a key developer-facing update by noting the new plugin compiler is now on by default for `latest` in [Introducing a new build system for plugins](https://meta.discourse.org/t/-/398713/2?silent=true), and also followed up on compatibility questions in [Bundling more popular plugins with Discourse core](https://meta.discourse.org/t/-/373574/172?silent=true).

- **@nat** rapidly handled an operational issue: acknowledging and then confirming a fix for the upload failures in [I cannot upload a GIF…](https://meta.discourse.org/t/-/398808/3?silent=true) and [follow-up confirmation](https://meta.discourse.org/t/-/398808/4?silent=true); plus shipped a Meta theme tweak in [Meta Branded redesign: theme refresh](https://meta.discourse.org/t/-/397246/46?silent=true).

- **@zogstrip** confirmed UI fixes were in flight for two UX papercuts: German upload placeholder layout in [German upload text is wider than the image placeholder](https://meta.discourse.org/t/-/398782/2?silent=true) and RTL profile reply icon behavior in [Change reply icon under profile for RTL languages](https://meta.discourse.org/t/-/398766/2?silent=true).

- **@awesomerobot** weighed in on AI policy boundaries (no “agents acting as real users” without admin oversight) in the OpenClaw-related feature thread [Discourse官方会出个官方的openclaw skill么？](https://meta.discourse.org/t/-/398771/2?silent=true), and pointed to a forthcoming UI fix for German AI cost configuration spacing in [Field alignment issues in LLM cost configuration in German](https://meta.discourse.org/t/-/396948/7?silent=true).

- **@davidb** confirmed a fix for a visual cue issue (highlighting current user/bots) with a linked commit in [Highlighting current user and bots in posts](https://meta.discourse.org/t/-/321851/4?silent=true).

- **@pmusaraj** engaged on improving Discourse ID clarity for new users, requesting mockups/visuals in [Featuring the referring site’s logo and name more prominently in Discourse ID](https://meta.discourse.org/t/-/398828/2?silent=true).

- **@manuel** dug into the nuance of pinned-topic settings and whether the two related options are meaningfully distinct (and how to describe them better) in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/62?silent=true), then linked the discussion back to the dedicated UX thread in [Can we improve usability of pinned topic site settings?](https://meta.discourse.org/t/-/386365/7?silent=true).

- **@mcwumbly** added practical context to the pinned-topic mystery (possibly due to historical “read → auto-unpin” behavior), helping validate the most plausible explanation in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/66?silent=true).

* * *

Yesterday’s Meta mood: chasing down a vanishing GIF upload bug while also squeezing long German strings into tighter UI boxes—classic “polish the edges” day ([upload fix](https://meta.discourse.org/t/-/398808/4?silent=true), [German layout tweak](https://meta.discourse.org/t/-/398782/1?silent=true)).

---

<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: [Março 21, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/779 "2026-03-21T05:01:54Z")

</div>

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

## Key Stats

- **New posts (last 24h):** 86
- **New topics (last 24h):** 14

**Top posters (with likes received in the last 24h):**

| User | Posts | Likes |
| --- | --- | --- |
| @david | 10 | 31 |
| @Moin | 8 | 15 |
| @Falco | 4 | 14 |
| @Lilly | 5 | 7 |
| @chapoi | 3 | 11 |
| @gilles | 4 | 4 |
| @LeoDavidson | 3 | 5 |
| @markvanlan | 1 | 5 |
| @awesomerobot | 1 | 3 |
| @Don | 1 | 3 |

> The day skewed _heavily technical_: plugin build changes continued to ripple through real-world installs and dev environments (see ongoing discussion in [read more](https://meta.discourse.org/t/-/398713/4?silent=true) and the devcontainer compilation thread [read more](https://meta.discourse.org/t/-/398864/7?silent=true)).

* * *

## Interesting Topics

### #Announcements

- Discourse shipped **calendar subscription URLs** so users can subscribe to ICS feeds (bookmarked reminders, and plugin-powered event feeds) from **Preferences → Calendar** ([read more](https://meta.discourse.org/t/-/398902/1?silent=true)). Related: this builds on the #calendar-and-event ecosystem including the official plugin topic ([read more](https://meta.discourse.org/t/-/97376/1?silent=true)) and an “events not creating” gotcha that turned out to be about putting the event markup on the first line ([read more](https://meta.discourse.org/t/-/383728/9?silent=true)).

- In **Current Projects – March 2026** , @lindsey noted they’re investigating the best path for translations (Crowdin vs PR workflow), and promised a follow-up ([read more](https://meta.discourse.org/t/-/398565/7?silent=true)).

### #Dev

- A plugin author hit a **“Duplicate export” compile error** after upgrading to `2026.3.0-latest`, and @david linked a core fix that resolved it ([read more](https://meta.discourse.org/t/-/398882/3?silent=true)). The report was explicitly tied back to the new plugin build pipeline discussion ([read more](https://meta.discourse.org/t/-/398713/3?silent=true)).

- Discourse is **formally deprecating `.js.es6`** file extensions in themes/plugins, with removal planned after the next ESR—migration is simply renaming to `.js` ([read more](https://meta.discourse.org/t/-/398894/1?silent=true)).

- Discourse also deprecated **`.hbs` templates** in themes/plugins, nudging authors to adopt `.gjs` for future performance improvements; @david clarified that `2026.7` should still support `hbs`, with drop likely around `2026.8.0-latest` ([read more](https://meta.discourse.org/t/-/398896/3?silent=true)). For hands-on migration guidance, the team pointed people at the automation how-to ([read more](https://meta.discourse.org/t/-/368051/1?silent=true)).

- In a French-language dev question, @gilles asked how to get **Rich Text to “interpret HTML”** when inserting content via API; @Falco advised sending Markdown instead, since only a small subset of HTML is accepted ([read more](https://meta.discourse.org/t/-/398919/2?silent=true)).

### #Nested Replies Testing

- The experimental nested replies plugin got **UI clarity improvements** for “deep context view” (after ~10 levels, continuing in a dedicated thread page), with bolder styling to make the mode obvious; @Falco confirmed the visual cue reads clearly ([read more](https://meta.discourse.org/t/-/398910/2?silent=true)). Related ongoing feedback continues in the main test thread (including preference persistence questions) ([read more](https://meta.discourse.org/t/-/398759/67?silent=true)).

### #bug

- A dev workflow issue: a PR proposes compiling **missing Rollup plugin bundles on demand** in development to prevent enabled plugins (like Chat) from silently failing when manifests are stale; @david traced one cause to compilation timeouts and bumped timeouts to help slower environments ([read more](https://meta.discourse.org/t/-/398864/7?silent=true)). This stayed closely tied to the broader Rollup transition for plugins ([read more](https://meta.discourse.org/t/-/398713/4?silent=true)).

- A Chinese-language bug report described a confusing edge case where **permanently deleting a post within 5 minutes** triggers a “wait 5 minutes” message, then returns with the post unexpectedly restored to an undeleted state, requiring deletion again ([read more](https://meta.discourse.org/t/-/398938/1?silent=true)).

### #Support

- A self-host admin asked for **programmatic update notifications** (email or file touch) instead of relying on the web UI; @david pointed to built-in “new version emails” behavior (requires SMTP + contact email) ([read more](https://meta.discourse.org/t/-/398871/3?silent=true)). This question overlapped with ongoing community confusion about channels/versioning/docs ([read more](https://meta.discourse.org/t/-/383536/56?silent=true)) and “where did releases go?” site UX feedback ([read more](https://meta.discourse.org/t/-/398854/7?silent=true)).

- Sidebar/homepage navigation came up again: a site owner wanted the **hamburger/sidebar open with categories** on “landing”; replies covered default sidebar configuration and how `/categories` can be used or set as homepage ([read more](https://meta.discourse.org/t/-/398848/12?silent=true)). The canonical configuration guide was also referenced ([read more](https://meta.discourse.org/t/-/347764/1?silent=true)).

- Hosted customers asked why the admin dashboard shows **“last month” stats** instead of “this month so far”; discussion suggests “last month” is rolling, and can be verified against `/admin/reports/emails` counts ([read more](https://meta.discourse.org/t/-/398924/2?silent=true)).

- A hosted #patreon install reported **Patreon sync gaps and unexpectedly small group membership** , with sync apparently stalled and manual “sync now” button doing nothing; the report includes Cloudflare-like failures in logs and questions about rate limits ([read more](https://meta.discourse.org/t/-/398944/1?silent=true)). It pairs naturally with renewed pressure to move the Patreon plugin to API v2 ([read more](https://meta.discourse.org/t/-/386701/7?silent=true)).

### #customization:theme component / #mobile

- Two separate reports converged on the same culprit: the **F NAV mobile navigation tabs** theme component appears to crash/disrupt Android behavior on latest Discourse; the component maintainer shipped a fix and asked users to update ([read more](https://meta.discourse.org/t/-/342277/77?silent=true)), and the broader “Android app is broken” thread points back to the same component ([read more](https://meta.discourse.org/t/-/398873/2?silent=true)).

### #Data & reporting

- A user requested Discourse’s **Data Processing Agreement (DPA)** and clarity on how contact data is stored, protected, retained, and shared; replies pointed to the public privacy/legal pages and noted older privacy threads may be outdated ([read more](https://meta.discourse.org/t/-/398913/3?silent=true)), with the legacy privacy discussion referenced for context ([read more](https://meta.discourse.org/t/-/88391/6?silent=true)).

* * *

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

- **@Falco**

- **@david**

- **@chapoi**

- **@markvanlan**

- **@awesomerobot**

- **@zogstrip**

- **@lindsey**

* * *

Discourse spent the day shipping calendar feeds, tightening up nested replies, and politely telling old file extensions it’s time to pack their bags—while the daily-summary bot briefly dozed off and left the rest of us to pick up the clipboard ([read more](https://meta.discourse.org/t/-/291853/286?silent=true)).

---

<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: [Março 22, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/780 "2026-03-22T05:01:38Z")

</div>

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

## Key Stats

In the last 24 hours, Meta saw **71 new posts** across **14 new topics** , with conversation clustering around AI-assisted translation UX, calendar subscription exports, and a handful of upgrade/regression reports (e.g. [read more](https://meta.discourse.org/t/-/398990/1?silent=true), [read more](https://meta.discourse.org/t/-/398948/1?silent=true), [read more](https://meta.discourse.org/t/-/398902/1?silent=true)).

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

| User | Posts | Likes |
| --- | --- | --- |
| @Moin | 12 | 19 |
| @Falco | 5 | 10 |
| @eisammy | 4 | 4 |
| @NateDhaliwal | 4 | 2 |
| @darkpixlz | 3 | 5 |
| @Shauny | 2 | 4 |
| @Heliosurge | 2 | 3 |
| @mdoggydog | 2 | 2 |
| @R23D_Printing | 1 | 5 |
| @newkid | 1 | 2 |

* * *

## Interesting Topics

### #contribute:feature

- @Shauny proposed a smoother “translate” UX for individual posts (especially on mobile) and asked whether translations could be **saved/cached** to avoid repeated AI API calls in [Translate post with AI and save translation](https://meta.discourse.org/t/-/398950/1?silent=true); @Moin pointed to the closely-related prior request about storing translations as content localization in [Saving translations by AI Helper as content localization](https://meta.discourse.org/t/-/397477/1?silent=true), while @Falco noted that Discourse’s **automatic translation toggle** was built to address the “manual invoke” and “repeated cost” problems ([read more](https://meta.discourse.org/t/-/398950/3?silent=true)).

- @Steradiant requested parity between OAuth2 and OIDC by adding an option to disable email verification when using OpenID Connect in [Allow to disable email verification when using oidc](https://meta.discourse.org/t/-/398963/1?silent=true) (similar in spirit to existing “verified email” controls for other auth paths).

- @GaurangBlaze suggested a more graceful upgrade flow when disk space is low—prompting cleanup _before_ the upgrade to reduce downtime—in [Proposal to gracefully handle low disk space during a Discourse upgrade](https://meta.discourse.org/t/-/398989/1?silent=true).

- A long-running request for calendar export improvements got a concrete “done” update: @Falco confirmed iCal/CALDAV-oriented work is addressed via the newer subscription URL implementation in [Calendar plugin should offer ical export and caldav](https://meta.discourse.org/t/-/312279/19?silent=true), pointing people to [Calendar subscription URLs for external calendar apps](https://meta.discourse.org/t/-/398902/1?silent=true).

### #Announcements

- The new calendar subscription URLs landed and immediately drew UX/product feedback: some admins want the UI to avoid _prominently_ featuring proprietary calendar brands, or to make them optional at creation time, in [Calendar subscription URLs for external calendar apps](https://meta.discourse.org/t/-/398902/2?silent=true); @Falco suggested CSS hiding as a workaround ([read more](https://meta.discourse.org/t/-/398902/3?silent=true)) while others requested filtering per community/group ([read more](https://meta.discourse.org/t/-/398902/5?silent=true)). Related feature lineage: [Category-level ICS/GCal link](https://meta.discourse.org/t/-/293972/4?silent=true) and [Authenticated ICS feeds for private calendar events](https://meta.discourse.org/t/-/393203/11?silent=true).

- A small but positive “this is easier now” datapoint: @newkid reported improved day-to-day admin usability with the streamlined category flow in [Simplified category setup](https://meta.discourse.org/t/-/394971/27?silent=true).

### #Support

- A Discourse admin hit an exception while creating API keys, traced to a plugin adding a base path requirement; removing the plugin resolved it in [An error is occurring on the page where I am creating the API](https://meta.discourse.org/t/-/398948/1?silent=true). @Moin identified the likely culprit as the Dumbcourse plugin ([read more](https://meta.discourse.org/t/-/398948/2?silent=true)) which aligns with its implementation thread: [Dumbcourse: old-browser friendly UI](https://meta.discourse.org/t/-/395104/1?silent=true).

- After upgrading, @hellekin “lost” the banner topic UI controls; @Moin explained this is expected when the banner topic lives in a **private category** , and suggested moving/unlisting it in [I just upgraded to the latest tag, and lost banner topic!](https://meta.discourse.org/t/-/398976/1?silent=true), with background in [Can no longer create global banners from restricted categories](https://meta.discourse.org/t/-/398306/1?silent=true).

- @Muzzydex reported that `validations: required: true` does not block submission for `upload` fields in form templates in [Required: true not enforced for upload field in form templates](https://meta.discourse.org/t/-/398972/1?silent=true) (while other field types validate correctly), suggesting a field-type-specific gap.

- ActivityPub/anonymous-mode interaction raised privacy expectations: @Jagster observed federated posts going out both as anon and as the _real_ identity in [Federation doesn’t respect anonymous mode](https://meta.discourse.org/t/-/398961/1?silent=true), prompting questions about expected behavior vs. bug/regression.

- Dashboard labeling/expectations came up again: “Last month” was interpreted as calendar-month vs rolling-30-days, and the thread converged on clearer wording and date range cues in [How do I get the dashboard to show this months info?](https://meta.discourse.org/t/-/398924/3?silent=true) (with analogy to rolling windows elsewhere in the UI: [read more](https://meta.discourse.org/t/-/398924/6?silent=true)).

- A self-hosting migration question asked whether **group PM inbox messages** can be moved to another Discourse instance; @NateDhaliwal pointed to topic-moving docs but noted PMs likely need API/console work in [Transfering inbox group messages to another instance?](https://meta.discourse.org/t/-/398971/1?silent=true), referencing the existing general guide: [Move topics from one Discourse instance to another](https://meta.discourse.org/t/-/38930/1?silent=true).

### #ux

- A small composer UI regression: tags (and votes) appear visually “too low” in the “Your topic is similar to…” popup; @Moin narrowed it to a specific CSS margin rule in [Tags are too low in similar topic pop up](https://meta.discourse.org/t/-/398986/1?silent=true).

- @peternlewis noticed that after updating, the admin dashboard briefly still shows the old version until refresh—suggesting a caching/refresh flow improvement—in [After Update Dashboard shows the old version](https://meta.discourse.org/t/-/398990/1?silent=true).

- Discourse ID UX got more validation: @nathank strongly agreed that the referring site’s branding should be more prominent to reduce confusion (including in emails) in [Featuring the referring site’s logo and name more prominently in Discourse ID](https://meta.discourse.org/t/-/398828/5?silent=true).

### #bug

- @darkpixlz reported that failed “update reply” requests can cause the **Update** button to duplicate repeatedly, making the UI unusable, in [Unsuccessful update replies cause the update button to duplicate](https://meta.discourse.org/t/-/398947/1?silent=true).

- A Chinese-language bug thread continues: after enabling chat again, it still doesn’t appear on the site for one reporter; the thread includes troubleshooting suggestions ([safe mode](https://meta.discourse.org/t/53504?silent=true) + keeping official plugins enabled) in [聊天功能被禁用后，其设置消失。](https://meta.discourse.org/t/-/398401/12?silent=true).

### #customization:theme component / #Dev / #customization:plugin

- A “theme component” share drew installability feedback: several community members noted the repository lacks the expected skeleton structure (notably `about.json`) in [G-Translate - Fast and easy translate you entire Discourse Forum for free](https://meta.discourse.org/t/-/398973/4?silent=true), with guidance pointing back to the official structure in [discourse-theme-skeleton](https://meta.discourse.org/t/-/398973/8?silent=true).

- The theme skeleton itself got scrutiny (again): @Moin observed the “compatibility” entry being re-pinned/merged back into the skeleton despite prior concerns, in [The theme-skeleton compatibility has been pinned again](https://meta.discourse.org/t/-/398985/1?silent=true), continuing the earlier debate in [What is the purpose of the compatibility entry in the theme skeleton?](https://meta.discourse.org/t/-/369851/3?silent=true).

- Rich-text editor parity came up in a concrete way: @mdoggydog’s update to a composer toolbar component highlighted mismatches in `applyList/applySurround` behavior, and @renato responded that full abstraction parity isn’t the goal—complex operations should use ProseMirror commands via extensions—in [Composer Button Bonanza](https://meta.discourse.org/t/-/352525/31?silent=true) (team perspective: [read more](https://meta.discourse.org/t/-/352525/32?silent=true)).

- A new plugin announcement: @R23D_Printing shared a “daily challenge” gamification/check-in system with leaderboards and badges in [Discourse Daily Challenges](https://meta.discourse.org/t/-/398980/1?silent=true), including an install pointer to [How to install plugins in Discourse](https://meta.discourse.org/t/-/19157/1?silent=true).

_(Bonus “ecosystem watch” thread that’s still developing: the new plugin build system can break admin paths until rollout is disabled; the workaround `ROLLUP_PLUGIN_COMPILER=0` helped in [Custom Wizard Plugin 🧙](https://meta.discourse.org/t/-/73345/931?silent=true) with context from [Introducing a new build system for plugins](https://meta.discourse.org/t/-/398713/2?silent=true).)_

* * *

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

- @Falco was heavily involved in calendar + translation UX discussions:

- @j.jaffeux engaged on a chat regression report, pushing back on whether the described behavior is possible and helping triage the situation in [聊天功能被禁用后，其设置消失。](https://meta.discourse.org/t/-/398401/13?silent=true).

- @renato weighed in on rich-text editor integration expectations, explaining why some textarea-era abstraction APIs won’t have 1:1 parity and pointing developers toward ProseMirror extension commands in [Composer Button Bonanza](https://meta.discourse.org/t/-/352525/32?silent=true).

* * *

_That’s a wrap—may your calendar links stay neatly subscribable, your “Translate” button be one tap away, and your upgrade dashboard always refresh on the first try!_

---

<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: [Março 23, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/781 "2026-03-23T05:01:22Z")

</div>

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

## Key Stats

- **New activity (last 24h):**  **63** new posts · **7** new topics (per daily rollup).

- **Top posters & likes (last 24h):**

- **New topics opened today (7):**

- **Also active / worth a skim (ongoing threads with fresh updates):**

* * *

## Interesting Topics

### #Support

- @Richie reported that after upgrading to **2026.3.0-latest.1** , the admin UI claimed all theme components were failing with _“Error cloning git repository”_—even though manual “Check for updates” succeeds; @sam floated re-adding components and possible GitHub rate limiting as angles to investigate ([read more](https://meta.discourse.org/t/-/399003/1?silent=true), team reply: [read more](https://meta.discourse.org/t/-/399003/15?silent=true)).

- New site provisioning via **[id.discourse.com/create-site](http://id.discourse.com/create-site)** appeared to stall at _“Almost there…”_, then showed _“provisioned too many sites in the past hour”_; one workaround suggestion was simply trying another browser ([read more](https://meta.discourse.org/t/-/398993/1?silent=true), workaround note: [read more](https://meta.discourse.org/t/-/398993/3?silent=true)).

- A report on #activitypub described federation posts using the _original language_ content, but links showing up in **English** , which felt like a behavioral regression for multilingual setups using AI translations ([read more](https://meta.discourse.org/t/-/398996/1?silent=true)).

- Self-hosted admins continued comparing notes on **iOS/PWA push notifications** , including cases where badges appear but notifications don’t, and how troubleshooting can be tricky (especially around device-specific behavior) ([read more](https://meta.discourse.org/t/-/394149/3?silent=true)).

### #General

- A new thread explored interest in releasing an **open source Discourse mobile app template** ; discussion quickly turned to _what a native app adds beyond mobile web APIs_ ([read more](https://meta.discourse.org/t/-/398997/1?silent=true), motivation pushback: [read more](https://meta.discourse.org/t/-/398997/3?silent=true)). Related prior attempts were also referenced for context: Forumate iOS client ([read more](https://meta.discourse.org/t/-/267125/1?silent=true)) and Fig iOS client ([read more](https://meta.discourse.org/t/-/148352/111?silent=true)).

### #customization:theme component

- Feedback on the **G-Translate theme component** highlighted practical UX integration issues (e.g., button placement conflicting with fixed-position navigation components) and translation edge cases when content is already in another language ([read more](https://meta.discourse.org/t/-/398973/11?silent=true)).

### #Announcements

- The new **calendar subscription URLs** feature sparked follow-up questions about filtering feeds (e.g., by group/community) and whether previously generated URLs should remain visible without forcing regeneration; @Falco clarified expected behavior and tradeoffs ([read more](https://meta.discourse.org/t/-/398902/7?silent=true), follow-up: [read more](https://meta.discourse.org/t/-/398902/10?silent=true)). Related: an older-but-active report noted **rate limiting** on the `/discourse-post-event/events.ics` export and a pragmatic `webcal://` + `after=` workaround ([read more](https://meta.discourse.org/t/-/385342/24?silent=true)).

- The “Easily create Support categories using the discourse-solved plugin” announcement thread got a concrete update: @martin pointed to fixes landing via a core PR ([read more](https://meta.discourse.org/t/-/398338/10?silent=true)).

### #Dev

- A developer debugging a plugin that inserts YouTube links into posts found the output stayed as raw text instead of rendering as a onebox—until they realized they’d missed applying the appropriate onebox class (resolved with a quick self-follow-up) ([read more](https://meta.discourse.org/t/-/398998/1?silent=true), resolution: [read more](https://meta.discourse.org/t/-/398998/2?silent=true)).

- In the “new versioning strategy” RFC thread (#dev-news), a user reported knock-on effects when running a specific branch: the UI couldn’t detect available upgrades, blocking web-based update workflows ([read more](https://meta.discourse.org/t/-/383536/61?silent=true)).

### #ux

- A small-but-recurring annoyance: after an update, the **dashboard sometimes shows the old version** , prompting a suggestion that a “please refresh” banner might reduce confusion while still respecting caching optimizations ([read more](https://meta.discourse.org/t/-/398990/2?silent=true)).

### #bug

- On #activitypub, a Mastodon connection issue prompted @sam to flag a likely OAuth scope/security change and loop in internal experts for ideas ([read more](https://meta.discourse.org/t/-/398803/2?silent=true)).

- A confusing flow was highlighted where clicking **“New Post”** triggers a discard confirmation modal if the user already has a post pending approval; @sam agreed the overall “pending approval” UX can feel hostile and needs an end-to-end rethink ([read more](https://meta.discourse.org/t/-/397711/3?silent=true)).

### #Self-hosting

- A self-hoster raised alarms about Discourse potentially **leaking origin host IPs** when fetching remote resources for previews/embeds (undermining Cloudflare-only exposure), reviving long-running proxying discussions and asking for safer defaults ([read more](https://meta.discourse.org/t/-/399012/1?silent=true)). Background/related: “link previews through a proxy server” ([read more](https://meta.discourse.org/t/-/72720/1?silent=true)).

- Group inbox migration came up: one admin considered how to move **group PM inbox threads** to another instance, weighing manual copy vs. API approaches, with an idea to temporarily convert PMs to topics and back (with caveats) ([read more](https://meta.discourse.org/t/-/398971/3?silent=true), migration idea: [read more](https://meta.discourse.org/t/-/398971/4?silent=true)).

* * *

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

- **@sam** weighed in on the hard-to-reproduce theme update/git error reports, suggesting environmental causes (URL drift, rate limiting) and pragmatic remediation like removing/re-adding components ([read more](https://meta.discourse.org/t/-/399003/15?silent=true)).

- **@sam** flagged a likely OAuth/security scope change behind a Mastodon federation connection failure in the #activitypub space, looping in internal stakeholders for input ([read more](https://meta.discourse.org/t/-/398803/2?silent=true)).

- **@sam** also called out the broader UX problem around _pending approvals_ and the confusing discard modal, outlining key questions Discourse should answer for end users throughout that workflow ([read more](https://meta.discourse.org/t/-/397711/3?silent=true)).

- **@sam** followed up on the calendar ICS export/rate limiting investigation, asking whether anything is still broken and needs fixing (useful for turning “workarounds” into actionable bug reports) ([read more](https://meta.discourse.org/t/-/385342/26?silent=true)).

- **@Falco** responded to calendar subscription URL enhancement requests, challenging assumptions about group-filtered feeds and clarifying that URLs can be copied once, reused across clients, and regenerated when needed ([read more](https://meta.discourse.org/t/-/398902/7?silent=true)).

- **@martin** posted an update confirming fixes related to streamlined support category setup with #solved, pointing to a merged/ongoing core PR as the source of truth ([read more](https://meta.discourse.org/t/-/398338/10?silent=true)).

* * *

If yesterday taught us anything, it’s this: may your theme repos always clone successfully, and may your calendar feeds stay comfortably under the rate limit.

---

<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: [Março 24, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/782 "2026-03-24T05:01:38Z")

</div>

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

## Key Stats

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

- **New posts:** 76
- **New topics:** 17

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

| User | Posts | Likes |
| --- | --- | --- |
| @Moin | 5 | 20 |
| @awesomerobot | 3 | 14 |
| @david | 6 | 14 |
| @Ivan_Rapekas | 3 | 8 |
| @zogstrip | 3 | 6 |
| @pmusaraj | 5 | 5 |
| @nathank | 4 | 5 |
| @ondrej | 1 | 4 |
| @darkpixlz | 3 | 4 |
| @Richie | 4 | 3 |

**Quick pulse of what people were busy with:** debugging updates and UI quirks (e.g. Redis + email jobs in [No new version emails](https://meta.discourse.org/t/-/399014/4?silent=true) and mobile affordances in [Add a grip bar to post admin actions menu](https://meta.discourse.org/t/-/399043/1?silent=true)), plus polishing AI/search UX in [Discourse’s search broken?](https://meta.discourse.org/t/-/394348/13?silent=true) and shipping fixes for edge-case formatting in [topic voting + tags](https://meta.discourse.org/t/-/399039/6?silent=true).

* * *

## Interesting Topics

#### #contribute:site-feedback

- @NateDhaliwal spotted a formatting glitch where #topic-voting topics with _zero votes_ could show an odd trailing comma after the last #tags entry; @awesomerobot pushed an adjustment and confirmed it’s now fixed ([read more](https://meta.discourse.org/t/-/399039/6?silent=true)).

#### #bug

- Sites reported that **“new version” emails weren’t being sent** , with logs pointing to a failing `CallDiscourseHub` job and a Redis argument type error; @david traced the regression to a Redis gem update and linked the fix work ([read more](https://meta.discourse.org/t/-/399014/4?silent=true)).

- A small but visible UI polish issue— **tags sitting too low in the similar-topics popup** —got a straightforward fix queued up by @awesomerobot ([read more](https://meta.discourse.org/t/-/398986/2?silent=true)).

- A possible regression in **DiscoTOC positioning** : “Contents” and “Timeline” buttons appear to float unexpectedly depending on viewport sizing, with reports pointing back to the main DiscoTOC thread for context ([read more](https://meta.discourse.org/t/-/399082/1?silent=true)).

#### #Support

- Staff accounts missing **Associated Accounts** management turned out to be a _known interaction with 2FA requirements_; @Moin connected the dots and referenced the existing guidance ([read more](https://meta.discourse.org/t/-/399045/5?silent=true)).

- Admins on **2026.3.0-latest.1** saw theme updates fail with “Error cloning git repository…”, with suspicion falling on GitHub rate limits/outages given recent status history ([read more](https://meta.discourse.org/t/-/399003/17?silent=true)).

- A “how do I recreate this UI?” question: adding **custom links beneath the welcome banner** was answered with a pointer to the dedicated theme component that provides exactly that layout ([read more](https://meta.discourse.org/t/-/399111/2?silent=true)).

- ActivityPub troubleshooting continued: attempts to connect to certain Discourse instances failed with **client verification errors** , and early investigation suggested something specific to the meta actor behavior ([read more](https://meta.discourse.org/t/-/399066/3?silent=true)).

#### #Self-hosting

- A privacy-focused self-hosting thread asked how to **stop Discourse leaking host IPs** when fetching external resources/previews; replies explored proxy strategies (e.g. Tinyproxy + env vars) but also highlighted the practical maintenance trade-offs ([read more](https://meta.discourse.org/t/-/399012/5?silent=true)).

- Auto-update habits came back up: a self-hoster asked whether **cron-based unattended updates** are “still the way” in 2026, balancing fast security patching against the risk of breaking production ([read more](https://meta.discourse.org/t/-/241232/6?silent=true)).

#### #customization:theme-component

- A new component, **AI summary in the topic header** , landed to surface the Discourse AI summarize action in more prominent UI locations (sidebar/title area depending on device), effectively shipping an answer to earlier placement feedback ([read more](https://meta.discourse.org/t/-/399069/1?silent=true)).

- The **Quote Callouts** component got feedback about alias/title behavior in the editor list, and a fix was shipped to reduce confusion when titles are defined ([read more](https://meta.discourse.org/t/-/350962/53?silent=true)).

#### #contribute:feature

- A feature request proposed a **single-button workflow to update only themes/components** (separately from core updates), driven by the friction of many-click upgrades and occasional rate limits when doing lots of component updates ([read more](https://meta.discourse.org/t/-/399055/1?silent=true)).

#### #Data-&-reporting

- A new [Data Explorer](https://meta.discourse.org/t/32566?silent=true) recipe shared a SQL query for **listing event invitees with email addresses** , positioning it as a faster on-screen alternative to the built-in zipped RSVP export and noting dependencies on the Calendar (and Event) plugin ([read more](https://meta.discourse.org/t/-/399106/1?silent=true)).

* * *

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

- @awesomerobot shipped multiple UX fixes and clarifications: a formatting tweak for #topic-voting + #tags rendering ([read more](https://meta.discourse.org/t/-/399039/6?silent=true)), clearer messaging to distinguish semantic/AI search results from exact matches ([read more](https://meta.discourse.org/t/-/394348/13?silent=true)), and a fix for tag alignment in the similar-topics UI ([read more](https://meta.discourse.org/t/-/398986/2?silent=true)).

- @david investigated and explained several upgrade/admin pain points: he traced the long-standing “no new version emails” issue to a Redis gem change and pointed to the corrective PR ([read more](https://meta.discourse.org/t/-/399014/4?silent=true)), weighed in on GitHub outage/rate-limit plausibility behind failed theme git clones ([read more](https://meta.discourse.org/t/-/399003/17?silent=true)), and advised a site owner to remove/verify a questionable plugin causing resolver warnings post-update ([read more](https://meta.discourse.org/t/-/399080/2?silent=true)). He also guided a dev-news question by clarifying the .gjs migration commands should be run in a local dev environment ([read more](https://meta.discourse.org/t/-/368051/10?silent=true)), and shared a mitigation PR for Custom Wizard’s compiler transition ([read more](https://meta.discourse.org/t/-/73345/937?silent=true)).

- @zogstrip delivered a cluster of “this will be fixed by…” responses, each linking to upstream patches: enforcing `required: true` for upload fields in form templates ([read more](https://meta.discourse.org/t/-/398972/2?silent=true)), restoring post URLs in ICS exports for calendar/event flows ([read more](https://meta.discourse.org/t/-/399015/2?silent=true)), and fixing a permanently-delete edge case where posts could appear restored ([read more](https://meta.discourse.org/t/-/398938/2?silent=true)).

- @pmusaraj continued deep ActivityPub debugging: he identified Mastodon’s `scope` → `scopes` parameter change and drove a fix through to meta ([read more](https://meta.discourse.org/t/-/398803/3?silent=true); [read more](https://meta.discourse.org/t/-/398803/6?silent=true)), while also investigating Discourse-to-Discourse connection failures that appeared actor-specific ([read more](https://meta.discourse.org/t/-/399066/3?silent=true)).

- @sam refreshed and cleaned up the long-running “Searching for content effectively” documentation, deleting stale discussion and inviting folks to flag anything that now looks incorrect ([read more](https://meta.discourse.org/t/-/273328/23?silent=true)).

* * *

If yesterday taught us anything, it’s this: may your Redis jobs behave, your ActivityPub “scopes” stay properly plural, and your commas never wander off the end of a tag list.

---

<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: [Março 25, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/783 "2026-03-25T05:01:52Z")

</div>

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

## Key Stats

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

- **New posts:** 82
- **New topics:** 10

### Top contributors (posts + likes received)

| User | Posts | Likes |
| --- | --- | --- |
| @Moin | 14 | 17 |
| @Eilgnaw | 2 | 14 |
| @pfaffman | 5 | 2 |
| @awesomerobot | 2 | 3 |
| @putty | 2 | 4 |
| @david | 1 | 4 |
| @shortmort37 | 1 | 3 |
| @Noble_Fish | 1 | 3 |
| @Squidgemonster | 1 | 3 |
| @R23D_Printing | 1 | 5 |

### Quick extra links: more threads that were active

- Automation surprise in the content gardening experiment: adding a tag reopened a closed topic unexpectedly — [read more](https://meta.discourse.org/t/-/397606/60?silent=true)
- A CSS/admin UI layout regression report (with screenshots + suspected SCSS culprit) — [read more](https://meta.discourse.org/t/-/399120/1?silent=true)
- [Data Explorer](https://meta.discourse.org/t/32566?silent=true) API path + key requirements broke some tooling — [read more](https://meta.discourse.org/t/-/394388/3?silent=true)
- A question about mail-receiver TLS when the receiver domain differs from the forum domain — [read more](https://meta.discourse.org/t/-/49487/539?silent=true)
- A lively bikeshed on whether “Guidelines” sounds like “Rules” (and what “FAQ” should imply) — [read more](https://meta.discourse.org/t/-/397938/8?silent=true)
- Reports layout spacing concerns for empty dashboard reports — [read more](https://meta.discourse.org/t/-/395768/20?silent=true)
- Hidden flagged content visibility in “raw” URLs, and a suspected change source — [read more](https://meta.discourse.org/t/-/350051/23?silent=true)
- A fork/PR limbo update for PDF previews (mobile + PDF.js enhancements) — [read more](https://meta.discourse.org/t/-/157649/166?silent=true)
- Self-hosted push notifications “started working again” after revisiting configuration — [read more](https://meta.discourse.org/t/-/394149/8?silent=true)
- “Auto updates via cronjob” gets a cautionary take: convenience vs downtime risk — [read more](https://meta.discourse.org/t/-/241232/7?silent=true)
- A small but important doc cleanup on composer popup messages — [read more](https://meta.discourse.org/t/-/317734/11?silent=true)
- A merged fix for an “Update Discourse” sidebar entry appearing incorrectly — [read more](https://meta.discourse.org/t/-/398151/3?silent=true)

* * *

## Interesting Topics

### #customization:extras

- @Eilgnaw introduced **Dexo** , a native iOS Discourse client with multi-forum support, HTML rendering, and secure User API Key auth — [read more](https://meta.discourse.org/t/-/399129/1?silent=true)

### #customization:plugin

- A long-running **Custom Wizard** thread got a concrete win: @david confirmed a fix merged and asked for verification; follow-up confirmed it’s functional again — [read more](https://meta.discourse.org/t/-/73345/938?silent=true)

- @R23D_Printing released **Discourse Member Application** , a plugin that adds a public `/apply` form and an approval flow that issues invites after review (aimed at private/invite-only communities) — [read more](https://meta.discourse.org/t/-/399190/1?silent=true)

### #customization:theme-component

- The **Prefilled composer link generator** component hit deprecation warnings due to the `.hbs` changes; a PR was requested and later merged (with a note that tag-insertion is currently broken due to earlier tag-related changes) — [read more](https://meta.discourse.org/t/-/326460/4?silent=true)

- **Classic About Statistics** also surfaced deprecation warnings tied to the `.hbs` changes, prompting a request for PR review/approval — [read more](https://meta.discourse.org/t/-/336150/11?silent=true)

- **Inline PDF Previews** gained momentum via a community fork: mobile support, PDF.js rendering, zoom/navigation, and better handling for migrated PDFs were highlighted — [read more](https://meta.discourse.org/t/-/157649/166?silent=true)

### #Support

- A “move banner image to the very top” question turned into a practical CSS answer: use `.d-header .wrap` for styling the header background, plus a pointer to the official “custom CSS changes” guide — [read more](https://meta.discourse.org/t/-/399156/12?silent=true)

- Free plan provisioning hit a throttle: “ **You have provisioned too many sites in the past hour** ” blocked creation, and staff began investigating by requesting details of the domain field — [read more](https://meta.discourse.org/t/-/399186/3?silent=true)

- A new free-plan admin couldn’t find authentication settings; the thread clarified that on the free plan, login is managed via **Discourse ID** (social login flow) — [read more](https://meta.discourse.org/t/-/399201/2?silent=true)

- An inherited site with confusing [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) overrides led to a key realization: if [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) isn’t enabled, the override settings are essentially noise — [read more](https://meta.discourse.org/t/-/399081/4?silent=true)

### #Dev

- Dev container onboarding friction (email confirmation blocking first login) prompted a reminder that `bin/rails admin:create` exists; plus a handy note that **MailHog** can capture outbound email locally without “real” SMTP — [read more](https://meta.discourse.org/t/-/399187/5?silent=true)

- The `.hbs` template deprecation continues to ripple through themes/components, with requests to update guidance and references as people encounter outdated instructions — [read more](https://meta.discourse.org/t/-/398896/4?silent=true)

### #ux

- A thoughtful proposal argued **Anonymous Mode** is too hidden (avatar menu only), suggesting composer-level entry points and a clearer “you are anonymous” indicator while active — [read more](https://meta.discourse.org/t/-/399144/1?silent=true)

### #bug

- A serious workflow bug: clicking **“New Post”** when you already have a post pending approval triggers a discard modal and appears to block posting across categories; investigation also noted pending items showing up as drafts incorrectly — [read more](https://meta.discourse.org/t/-/397711/5?silent=true)

- A **subscriptions renewal** issue was reported with Stripe’s PaymentIntent complaining about a missing payment method, raising questions about how to clean up stale provider state for long-time supporters — [read more](https://meta.discourse.org/t/-/399179/1?silent=true)

* * *

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

- @david confirmed a **Custom Wizard** fix was merged and asked for verification steps to be re-run — [read more](https://meta.discourse.org/t/-/73345/938?silent=true)

- @awesomerobot shared a practical dev tip: use **MailHog** to view emails locally at `localhost:8025` (no external SMTP required) — [read more](https://meta.discourse.org/t/-/399187/5?silent=true) — and also updated documentation to clarify banner topics must live in a public category (with unlisting as an option) — [read more](https://meta.discourse.org/t/-/398306/18?silent=true)

- @sam performed doc maintenance by updating the **Composer Popup Messages Guide** (removing items) — [read more](https://meta.discourse.org/t/-/317734/11?silent=true) — and helped restore/undelete wiki content temporarily in a “searching effectively” guide thread to unblock further edits — [read more](https://meta.discourse.org/t/-/273328/25?silent=true)

- @HAWK acknowledged a free-plan provisioning throttle report (“too many sites in the past hour”) and escalated it for review — [read more](https://meta.discourse.org/t/-/399186/2?silent=true)

- @pedro followed up on the same free-plan provisioning issue, requesting the exact value entered in the “Community Domain” field to help diagnose — [read more](https://meta.discourse.org/t/-/399186/3?silent=true)

- @lindsey expanded a bug report showing that a discard confirmation modal can effectively prevent posting when any post is pending approval, and highlighted that the UX is confusing even when content isn’t truly lost — [read more](https://meta.discourse.org/t/-/397711/5?silent=true)

- @zogstrip responded to a bug report about the left sidebar incorrectly showing an “Update Discourse” option, pointing to a proposed fix PR for review — [read more](https://meta.discourse.org/t/-/398151/2?silent=true)

- @martin confirmed the above fix was merged and thanked the reporter — [read more](https://meta.discourse.org/t/-/398151/3?silent=true)

- @chapoi acknowledged an unintended automation side-effect in the collaborative gardening experiment and planned an adjustment — [read more](https://meta.discourse.org/t/-/397606/62?silent=true)

- @gerhard confirmed a translation/context issue should now be fixed — [read more](https://meta.discourse.org/t/-/395051/15?silent=true)

* * *

Yesterday’s theme: between launching shiny new apps and unblocking dev workflows with MailHog, Meta managed to both ship and debug at full speed—classic Discourse.

---

<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: [Março 26, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/784 "2026-03-26T05:01:09Z")

</div>

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

## Key Stats

- **Total new posts (last 24h): 74**
- **Total new topics (last 24h): 5**

### Top contributors (posts / likes)

- **@zogstrip** — **7** posts / **16** likes
- **@david** — **4** posts / **11** likes
- **@Moin** — **4** posts / **4** likes
- **@Falco** — **3** posts / **26** likes
- **@merefield** — **3** posts / **13** likes
- **@asc** — **3** posts / **5** likes
- **@R23D_Printing** — **3** posts / **4** likes
- **@mcdanlj** — **2** posts / **7** likes
- **@mat_pich_7894** — **2** posts / **4** likes
- **@Ed_S** — **1** post / **6** likes

### Threads that pulled people in (quick jump list)

- Release visibility + security-fix surprise in **#Support** : [read more](https://meta.discourse.org/t/-/399268/1?silent=true)
- Discourse as a comment platform (and Meta trying it on the blog) in **#community-building Building** : [read more](https://meta.discourse.org/t/-/274455/70?silent=true)
- Threading experiments in **#Nested Replies Testing** : [read more](https://meta.discourse.org/t/-/398759/69?silent=true)
- Admin reporting UX clarification in **#Announcements** (#dashboard-reports): [read more](https://meta.discourse.org/t/-/395768/23?silent=true)
- Mail-receiver + Cloudflare + TLS reality check in **#Self-Hosting** (#email): [read more](https://meta.discourse.org/t/-/49487/546?silent=true)
- Theme work continues in **#customization:theme** : [read more](https://meta.discourse.org/t/-/357665/42?silent=true)
- Calendar plugin versioning expectations in **#customization:plugin** (#included-in-core): [read more](https://meta.discourse.org/t/-/97376/573?silent=true)
- AI persona behavior control request in **#contribute:feature** (#ai #ai-bot): [read more](https://meta.discourse.org/t/-/399221/1?silent=true)
- Marketplace request for Kajabi integration in **#Marketplace** : [read more](https://meta.discourse.org/t/-/399279/1?silent=true)
- Horizon Theme mobile layout feedback in **#ux** (#horizon-theme): [read more](https://meta.discourse.org/t/-/399285/1?silent=true)
- P2P calling plugin interest + request for group calls in **#customization:plugin** : [read more](https://meta.discourse.org/t/-/398331/2?silent=true)
- Upload limits vs videos in **#Support** (#uploads): [read more](https://meta.discourse.org/t/-/397413/3?silent=true)
- Custom Wizard troubleshooting confirmation in **#customization:plugin** : [read more](https://meta.discourse.org/t/-/73345/940?silent=true)
- ActivityPub plugin version check-in in **#customization:plugin** (#activitypub): [read more](https://meta.discourse.org/t/-/266794/481?silent=true)
- “New groups not showing until refresh” resurfacing in **#bug** : [read more](https://meta.discourse.org/t/-/398285/2?silent=true) (with earlier related case: [read more](https://meta.discourse.org/t/-/386518/5?silent=true))

* * *

## Interesting Topics

### #Support

- @Ed_S raised concerns that **v2026.3.0-latest.1** (with “33 security fixes”) felt like a _stealth_ release, and asked for release posts to return to Announcements; @Falco pointed to background context and @david acknowledged the email-notifications issue and said the team is discussing Meta pointers to release info ([read more](https://meta.discourse.org/t/-/399268/1?silent=true), [read more](https://meta.discourse.org/t/-/399268/2?silent=true), [read more](https://meta.discourse.org/t/-/399268/5?silent=true)).

- A new free site hit provisioning rate limits (“You have provisioned too many sites in the past hour”), and @mat_pich_7894 confirmed it was resolved by using a different Community Domain value ([read more](https://meta.discourse.org/t/-/399186/5?silent=true)).

- A newly created community couldn’t enable Discourse ID / find the right authentication settings; @rishabh investigated and noted unusual volumes of auth-related setting changes in site logs ([read more](https://meta.discourse.org/t/-/399201/4?silent=true), [read more](https://meta.discourse.org/t/-/399201/5?silent=true)).

- Video upload constraints came up again—specifically that it would help to distinguish image vs video sizing limits, since they can differ by an order of magnitude ([read more](https://meta.discourse.org/t/-/397413/3?silent=true)).

### #bug

- In the long-running “whispers bumping” discussion (#whispers), @zogstrip confirmed inconsistent bump behavior and pointed to an upcoming fix—sparking debate about whether whispers _should_ bump for broader audiences or only for staff/trackers ([read more](https://meta.discourse.org/t/-/397588/2?silent=true)).

- X/Twitter oneboxes (#onebox) were called out as both broken _and_ impossible to prevent; @zogstrip linked a fix in progress ([read more](https://meta.discourse.org/t/-/397516/2?silent=true)).

- “Set Topic Timer may result in catastrophic failure” (#topic-timers): @zogstrip apologized and linked a PR to address multiple hidden bugs in the feature ([read more](https://meta.discourse.org/t/-/398284/2?silent=true)).

- A composer UX trap: a discard-confirmation modal appears when clicking “New Post” if a post is pending approval; @zogstrip shared that a fix is in the works and asked @martin for review ([read more](https://meta.discourse.org/t/-/397711/11?silent=true)).

- Digest emails still including topics from ignored users: @zogstrip confirmed a fix is coming via PR ([read more](https://meta.discourse.org/t/-/397622/2?silent=true)).

- Watched words for automatic tagging (#watched-words #tags) got a status update from @nat noting the fix shipped a while ago and encouraging folks to update ([read more](https://meta.discourse.org/t/-/397601/7?silent=true)).

### #community-building Building

- The “Discourse as comment platform” thread got a very concrete datapoint: @Falco announced the Discourse blog comments were swapped to the new embedded-topic system, with theme-component iteration planned before anything heads into core ([read more](https://meta.discourse.org/t/-/274455/70?silent=true)).

### #Announcements

- Reporting Improvements confusion: @zogstrip clarified that “Reporting improvements” is a simple **on/off** toggle (Everyone/No one) rather than group-scoped, and @martin added that the team plans to adjust wording so “Everyone” is less weird for admin-only features ([read more](https://meta.discourse.org/t/-/395768/23?silent=true), [read more](https://meta.discourse.org/t/-/395768/24?silent=true)).

- Carousel mode sizing expectations: @chapoi confirmed the carousel has a _fixed height_ to avoid jarring resizing between slides, and that customization requires CSS ([read more](https://meta.discourse.org/t/-/392955/16?silent=true)).

### #Dev

- Inline `<script type="text/discourse-plugin">` era officially ended: @david announced support for the old inline script tags has been removed in the latest Discourse version and linked the removal PR ([read more](https://meta.discourse.org/t/-/366482/49?silent=true)).

- Theme/plugin dev heads-up: `.hbs` deprecation guidance was reinforced—@david updated docs to better connect the `.hbs` deprecation steps and noted that [ask.discourse.com](http://ask.discourse.com) can help with small conversions ([read more](https://meta.discourse.org/t/-/398896/5?silent=true), [read more](https://meta.discourse.org/t/-/398896/7?silent=true)).

- Translation tooling throughput: @Moin asked how frequently the “find more context” tool updates; @gerhard explained that a background job is backfilling AI-generated string context and temporarily impacts some features ([read more](https://meta.discourse.org/t/-/395051/16?silent=true), [read more](https://meta.discourse.org/t/-/395051/17?silent=true)).

### #Self-Hosting

- Mail-receiver + Cloudflare proxying + TLS: @LotusJeff documented a Cloudflare-oriented setup and why inbound SMTP effectively requires separating the forum host from a DNS-only mail subdomain; @Simon_Manning refined/withdrew part of an earlier TLS identity assertion and ultimately praised the approach (notably the certbot renewal hook pattern) ([read more](https://meta.discourse.org/t/-/49487/541?silent=true), [read more](https://meta.discourse.org/t/-/49487/544?silent=true), [read more](https://meta.discourse.org/t/-/49487/546?silent=true)).

* * *

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

- **@Falco** engaged on release visibility and security-fix timing—sharing external context and acknowledging the feedback loop around where release info should appear on Meta ([read more](https://meta.discourse.org/t/-/399268/2?silent=true)).  
Separately, @Falco announced that Discourse’s blog comments have moved to embedded Discourse topics, and discussed theme-level fixes (forced light mode, padding polish) as the experience is refined ([read more](https://meta.discourse.org/t/-/274455/70?silent=true), [read more](https://meta.discourse.org/t/-/274455/72?silent=true)).

- **@david** responded candidly about the long-missed email issue and confirmed the team is discussing better Meta-level pointers to the centralized release system ([read more](https://meta.discourse.org/t/-/399268/5?silent=true)).  
On the dev side, @david marked the completion of removing inline script-tag templates from core ([read more](https://meta.discourse.org/t/-/366482/49?silent=true)) and updated `.hbs` deprecation guidance, including adding a note about using [ask.discourse.com](http://ask.discourse.com) for assistance ([read more](https://meta.discourse.org/t/-/398896/5?silent=true), [read more](https://meta.discourse.org/t/-/398896/7?silent=true)).

- **@zogstrip** had a particularly fix-heavy day across multiple **#bug** threads: whispers bump consistency (#whispers) ([read more](https://meta.discourse.org/t/-/397588/2?silent=true)), broken/unstoppable [x.com](http://x.com) oneboxes (#onebox) ([read more](https://meta.discourse.org/t/-/397516/2?silent=true)), catastrophic edge cases in topic timers (#topic-timers) ([read more](https://meta.discourse.org/t/-/398284/2?silent=true)), the “discard confirmation” composer annoyance when approvals are pending ([read more](https://meta.discourse.org/t/-/397711/11?silent=true)), and digest emails still surfacing ignored users’ topics ([read more](https://meta.discourse.org/t/-/397622/2?silent=true)).  
@zogstrip also clarified that the “Reporting improvements” Upcoming Change toggle is intentionally **not** group-scoped, and why “Everyone/No one” is expected there ([read more](https://meta.discourse.org/t/-/395768/23?silent=true)).

- **@martin** followed up on the reporting toggle UX, noting an upcoming adjustment so admin-only controls don’t misleadingly read as “Everyone” ([read more](https://meta.discourse.org/t/-/395768/24?silent=true)).

- **@chapoi** answered a Carousel Mode question, confirming fixed-height behavior and steering customization toward CSS ([read more](https://meta.discourse.org/t/-/392955/16?silent=true)).

- **@gerhard** explained temporary limitations in the translation-context tool due to a background backfill job for AI-generated string context ([read more](https://meta.discourse.org/t/-/395051/17?silent=true)).

- **@nat** posted a quick status update that the watched-words auto-tagging fix has already shipped, encouraging upgrades for anyone still affected ([read more](https://meta.discourse.org/t/-/397601/7?silent=true)).

- **@rishabh** investigated a Free-plan authentication/Discourse ID enablement issue, noting it didn’t appear widespread and asking what settings were being changed when the problem occurred ([read more](https://meta.discourse.org/t/-/399201/4?silent=true), [read more](https://meta.discourse.org/t/-/399201/5?silent=true)).

> That’s a wrap: yesterday managed to combine _33 security fixes_, a fresh wave of bug-fix PR links, and a real “Discourse-as-comments” rollout—so keep one eye on your update button and the other on those embedded topics.

---

<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: [Março 27, 2026, 5:02am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/785 "2026-03-27T05:02:21Z")

</div>

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

## Key Stats

- **New topics:** 12
- **New posts:** 88

**Top posters (last 24h)** _(posts / likes received)_

| User | Posts | Likes | Recent reference |
| --- | --- | --- | --- |
| @Moin | 8 | 19 | Added the new “icon” SiteSetting type in [read more](https://meta.discourse.org/t/-/370452/7?silent=true) |
| @Falco | 5 | 11 | Flagged the champagne emoji alias issue in [read more](https://meta.discourse.org/t/-/399338/2?silent=true) |
| @supermathie | 2 | 7 | Clarified why DiscourseID requires proper HTTPS in [read more](https://meta.discourse.org/t/-/399376/2?silent=true) |
| @meave | 1 | 6 | Reported the missing `:champagne:` shortcode in [read more](https://meta.discourse.org/t/-/399338/1?silent=true) |
| @tobiaseigen | 2 | 6 | Noted misaligned 2FA inputs on Meta in [read more](https://meta.discourse.org/t/-/399333/1?silent=true) |
| @david | 2 | 6 | Shared release comms context + links in [read more](https://meta.discourse.org/t/-/399268/10?silent=true) |
| @Lilly | 1 | 5 | Asked about `type: icon` inside theme setting object schemas in [read more](https://meta.discourse.org/t/-/370452/10?silent=true) |
| @nathank | 3 | 5 | Suggested a practical About-page workaround in [read more](https://meta.discourse.org/t/-/399286/4?silent=true) |
| @awesomerobot | 2 | 4 | Found the likely cause of the email-login 2FA layout bug in [read more](https://meta.discourse.org/t/-/399333/2?silent=true) |
| @Heliosurge | 2 | 3 | Discussed deletion behavior + options for uploads in [read more](https://meta.discourse.org/t/-/399315/2?silent=true) |

* * *

## Interesting Topics

### #Dev

- @Moin announced a new **SiteSetting “icon” type** , and the discussion quickly turned to whether `type: icon` could also work inside _theme component object schemas_ (raised by @Lilly) in [read more](https://meta.discourse.org/t/-/370452/7?silent=true). Related: the theme settings “objects” schema pattern in [read more](https://meta.discourse.org/t/-/305009/1?silent=true), and a follow-up on icon dropdown usability in [read more](https://meta.discourse.org/t/-/370555/10?silent=true).

- A new dev question: how to implement **avatar decorations/overlays driven by custom user fields** (e.g., `avatar_decoration_url`) via CSS/theme components, in [read more](https://meta.discourse.org/t/-/399394/1?silent=true).

- @Ethsim2 asked about **migrating replies between topics across different Discourse forums** , referencing prior Ruby tooling like `LightboxImageParser` and struggling with images/spreadsheets not moving cleanly in [read more](https://meta.discourse.org/t/-/399362/1?silent=true).

- @david shared that he’d be presenting Discourse’s **new plugin build system** at Ember Europe (and invited remote attendees) in [read more](https://meta.discourse.org/t/-/398713/5?silent=true).

### #bug

- A regression/compatibility report: the **Chat plugin fails to compile** under the rollup plugin compiler default, throwing `_assert is not a function`, with a clean self-hosted rebuild and third-party plugins disabled in [read more](https://meta.discourse.org/t/-/399321/1?silent=true).

- @rokejulianlockhart reported that **Horizon (and Meta) renders tables without `<thead>` as if they had a header divider**, which looks wrong when `<th>` is inside `<tbody>`—discussion and repro HTML in [read more](https://meta.discourse.org/t/-/399335/1?silent=true).

### #ux

- A delightfully specific one: the **champagne emoji** is labeled “Champagne” on hover but can’t be found via `:champagne:` (only via `:cork:`). @Falco suggested removing the misleading alias entry in [read more](https://meta.discourse.org/t/-/399338/2?silent=true).

- On Meta, **2FA input fields were left-aligned** (while the rest of the login content is centered) when the user logs in _via email link_. @awesomerobot reproduced/triaged and pointed to a fix PR in [read more](https://meta.discourse.org/t/-/399333/4?silent=true).

### #Self-hosting

- A DiscourseID setup gotcha: DiscourseID refused to enable because the site’s **Redirect URI must be HTTPS** , but `force_https` was disabled due to CSRF issues under a reverse proxy. @supermathie and @Falco both pushed the core point: fix proxy headers / HTTPS assumptions properly (not just “it works in the browser”) in [read more](https://meta.discourse.org/t/-/399376/2?silent=true). Related DiscourseID history: redirect URI collisions now handled in [read more](https://meta.discourse.org/t/-/396136/16?silent=true), and an alternate-email question in [read more](https://meta.discourse.org/t/-/398181/2?silent=true).

- A self-hosting upgrade workflow question: after the new versioning changes, switching `app.yml` to `version: esr` still appeared to install **`latest`**. The report + details are in [read more](https://meta.discourse.org/t/-/17014/34?silent=true).

- Incoming email infrastructure: discussion continued on running **mail-receiver** safely with Cloudflare—highlighting the risk of exposing the forum origin IP (bypassing WAF/DDoS protections) and considering running mail-receiver separately without the launcher doing a full Discourse install in [read more](https://meta.discourse.org/t/-/49487/547?silent=true).

### #Support

- On the free hosted plan, @Naoshi wanted an **“Announcements” category that’s read-only for creating new topics** (but still replyable). @Moin suggested using **topic approval** as an effective workaround—approve none unless staff-created—in [read more](https://meta.discourse.org/t/-/399298/2?silent=true).

- About page group display: a site wanted to show only “active” moderators while keeping trainees/founders in staff-access groups. The thread explored `about_page_hidden_groups` and even using dynamic group population to hide “not-active” moderators in [read more](https://meta.discourse.org/t/-/399286/10?silent=true). Related plugin mentioned: dynamic groups in [read more](https://meta.discourse.org/t/-/365342/1?silent=true).

- Topic list filtering: a request to filter for **category X OR tag Y** (not AND) using `/filter` highlighted a limitation—no boolean OR support today in advanced search/topic list filter—so a feature request was suggested in [read more](https://meta.discourse.org/t/-/399383/2?silent=true). Background docs cited: searching effectively in [read more](https://meta.discourse.org/t/-/273328/1?silent=true) and filter syntax in [read more](https://meta.discourse.org/t/-/375558/1?silent=true).

### #contribute:feature

- Calendar UX request: add **`.ics` iCal attachments in notification emails** for event topics, so email clients can offer native “Accept/Decline” without needing to click through Discourse. @Falco pointed to calendar subscription URLs, and noted event links were recently added to ICS sync output in [read more](https://meta.discourse.org/t/-/399329/4?silent=true). Related: subscription URLs in [read more](https://meta.discourse.org/t/-/398902/1?silent=true).

* * *

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

- **@Falco** weighed in on multiple threads:

- **@supermathie** focused on DiscourseID + HTTPS correctness:

- **@david** continued the release/process communication loop:

- **@awesomerobot** quickly reproduced and narrowed a UI oddity:

- **@pmusaraj** closed loops on DiscourseID support edge cases:

- **@chapoi** revisited a Horizon theme behavior:

* * *

Yesterday, Meta managed to be both _extra bubbly_ (emoji alias drama) and _extra practical_ (reverse proxy reality checks)—may your redirects be HTTPS and your champagne always searchable.

---

<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: [Março 28, 2026, 5:02am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/786 "2026-03-28T05:02:06Z")

</div>

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

## Key Stats

In the last 24 hours, Meta saw **100 new posts** across **14 new topics** , with a lot of the energy focused on release comms and self-hosting reliability (e.g. [release-site UX/RSS feedback](https://meta.discourse.org/t/-/399414/6?silent=true), [pinning Discourse versions/ESR](https://meta.discourse.org/t/-/399409/13?silent=true), and [plugin failures tied to CDN/CORS](https://meta.discourse.org/t/-/399466/2?silent=true)).

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

| User | Posts | Likes |
| --- | --- | --- |
| @david | 7 | 26 |
| @eisammy | 10 | 14 |
| @R23D_Printing | 11 | 10 |
| @RGJ | 2 | 10 |
| @darkpixlz | 4 | 8 |
| @mcdanlj | 3 | 7 |
| @manuel | 1 | 7 |
| @Falco | 3 | 6 |
| @patrickemin | 4 | 5 |
| @paco | 3 | 4 |

* * *

## Interesting Topics

### #General

- @mcdanlj and others shared actionable feedback on the new releases site experience (readability, “highlights” clarity), and @david responded by shipping an RSS feed quickly and inviting PRs to the open-source repo in [Releases.discourse.org feedback & suggestions](https://meta.discourse.org/t/-/399414/6?silent=true). Related reading: [Finding Discourse RSS feeds](https://meta.discourse.org/t/-/264134/1?silent=true) and [How to Be Notified of New Releases](https://meta.discourse.org/t/-/230675/1?silent=true).

- A discussion on whether an open-source “forum app for Discourse” makes sense quickly converged on the value of _multi-instance aggregation_—and the reminder that Discourse Hub already exists—in [Releasing a Open Source Forum App for Discourse](https://meta.discourse.org/t/-/398997/11?silent=true) ([read more](https://meta.discourse.org/t/-/398997/12?silent=true)).

### #community-building:praise

- @eisammy celebrated two years of their community (plus a couple of fun side projects like a radio and GIF component), with a warm community response in [Celebrating 2 years of my Instance](https://meta.discourse.org/t/-/399423/1?silent=true).

### #customization:plugin

- The Discourse Daily Challenges plugin hit real-world migration friction: @eisammy surfaced missing DB columns and `UnknownAttributeError`, and @R23D_Printing walked through rebuilds, a manual column add, and then shipped an update that resolved things in [Discourse Daily Challenges](https://meta.discourse.org/t/-/398980/28?silent=true) ([it works!](https://meta.discourse.org/t/-/398980/34?silent=true)).

### #Support

- A classic admin question—“can I hide the big red broken component banner?”—was firmly steered toward _fixing the component, not hiding the warning_, with @darkpixlz providing the practical explanation and @david underscoring the risk in [Getting rid of the big red banner, how?](https://meta.discourse.org/t/-/399461/3?silent=true). The underlying theme component was patched shortly after in [Chat Sidebar](https://meta.discourse.org/t/-/298829/17?silent=true).

- Notification confusion cropped up again: @ice.d wasn’t seeing the usual alerts, and @manuel pointed to per-topic notification levels (“Watching”) and global tracking settings in [Why won’t meta notify me?](https://meta.discourse.org/t/-/399412/2?silent=true).

- Reports came in that the Android app keyboard sometimes doesn’t appear when composing; @NateDhaliwal asked for version details and safe-mode testing steps in [Keyboard not appearing when creating posts - android](https://meta.discourse.org/t/-/399408/2?silent=true).

### #bug

- A strong field report identified Discourse’s crawler detection wrongly matching Facebook’s iOS in-app browser, causing “unstyled HTML” rendering; @david replied with a core PR to refine the default UA match in [Fix: Discourse renders as unstyled HTML in Facebook’s in-app browser on iPhone](https://meta.discourse.org/t/-/399440/2?silent=true).

- A painful composer failure: uploading HEIC images triggered an error + reload and the draft was lost, wiping ~25 minutes of writing in [Lost paragraphs / huge post due to HEIC upload](https://meta.discourse.org/t/-/399453/1?silent=true).

### #ux

- A small-but-real workflow gap was flagged: the system DM text says “reply to this message” after a revision request, but replying appears to go nowhere (no mod/admin loop) in [“reply to this message” goes nowhere?](https://meta.discourse.org/t/-/399477/1?silent=true).

- UI positioning feedback: the floating “Create category / Reset changes” box can cover lower settings during category creation in [Category creation floating box blocks out settings at the bottom](https://meta.discourse.org/t/-/399481/1?silent=true).

- Emoji housekeeping got a tiny quality win: @zogstrip added validation to prevent aliases pointing to emojis that don’t exist in [Trivial observation about the champagne emoji](https://meta.discourse.org/t/-/399338/3?silent=true).

- Documentation/link drift cleanup continued: guidance around the “FAQ → Guidelines” rename and where to opt in was clarified, with a focus on updating docs as the main action item in [Review and update topics related to FAQ & Guidelines links](https://meta.discourse.org/t/-/397938/12?silent=true). Related: [Renaming FAQ to Guidelines](https://meta.discourse.org/t/-/395099/1?silent=true), [Using Hidden Site Settings](https://meta.discourse.org/t/-/308773/1?silent=true), and the “Upcoming Changes” system discussion in [Introducing Upcoming Changes](https://meta.discourse.org/t/-/392894/11?silent=true).

### #Self-hosting

- Self-hosters compared strategies for pinning versions vs tracking “latest/release/esr”; @david clarified that tags _should_ work, explained proper `app.yml` usage, and warned about downgrades in [Help deploying older versions of Discourse](https://meta.discourse.org/t/-/399409/13?silent=true) ([read more](https://meta.discourse.org/t/-/399409/19?silent=true)). Supporting background: [Configure a supported tracking branch to get Discourse software updates](https://meta.discourse.org/t/-/17014/1?silent=true) and [Upcoming changes to the beta branch](https://meta.discourse.org/t/-/262063/1?silent=true).

- A site reported that “all plugins stopped functioning” (including Docker Manager), and early evidence pointed at CDN/CORS script loading failures; @darkpixlz suggested isolating via CORS testing and then tracking down the CDN cause in [All plugins not functioning](https://meta.discourse.org/t/-/399466/2?silent=true). (The reporter referenced a potentially-related dev issue here: [read more](https://meta.discourse.org/t/-/398864/8?silent=true).)

- A broader process critique argued that regressions keep breaking web-based updates; the immediate practical response was to recommend ESR for stability in [Unstable software - constantly breaking update processes](https://meta.discourse.org/t/-/399468/2?silent=true), with references back to earlier incidents like [upgrade abort: not enough unicorn workers running](https://meta.discourse.org/t/-/393003/1?silent=true) and a migration regression report at [read more](https://meta.discourse.org/t/-/393049/1?silent=true).

### #community-building Building

- Two “please review my forum” threads landed close together: one on a fresh community forum for Resonite with theme/component feedback in [Opinions on the forum I’ve built](https://meta.discourse.org/t/-/399434/1?silent=true), and another (Portuguese) asking whether categories/onboarding/homepage choices are organized well enough in [Eu tenho um fórum, mas não sei se ele está bem organizado o suficiente](https://meta.discourse.org/t/-/399483/1?silent=true).

* * *

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

- @david pushed hard on release communication improvements—confirming “Highlights” are curated, inviting design feedback, and shipping an RSS feed—within [Releases.discourse.org feedback & suggestions](https://meta.discourse.org/t/-/399414/6?silent=true) (and linked ongoing styling work). He also cautioned admins against hiding broken-component banners in [Getting rid of the big red banner, how?](https://meta.discourse.org/t/-/399461/3?silent=true), clarified self-host version pinning + the realities of downgrades in [Help deploying older versions of Discourse](https://meta.discourse.org/t/-/399409/13?silent=true), and turned a bug report into a core PR by responding in [Fix: Discourse renders as unstyled HTML in Facebook’s in-app browser on iPhone](https://meta.discourse.org/t/-/399440/2?silent=true).

- @derek acknowledged and incorporated specific accessibility/contrast feedback while working on the releases site styling refresh in [Releases.discourse.org feedback & suggestions](https://meta.discourse.org/t/-/399414/9?silent=true).

- @manuel helped troubleshoot missing notifications by pointing to per-topic notification levels and global tracking preferences in [Why won’t meta notify me?](https://meta.discourse.org/t/-/399412/2?silent=true).

- @Falco advanced two separate threads: confirming a Patreon plugin API v2 change was ready to merge (plus adding a clearer user agent for debugging) in [Upgrade Patreon Discourse Plugin to API v2](https://meta.discourse.org/t/-/386701/13?silent=true), and clarifying that GIF+text behavior in chat is longstanding (then moving it to a feature request) in [Gif + texte dans le même message dans chat](https://meta.discourse.org/t/-/399428/4?silent=true).

- @zogstrip made a small but meaningful robustness change by adding validation around emoji alias creation in [Trivial observation about the champagne emoji](https://meta.discourse.org/t/-/399338/3?silent=true).

- @mcwumbly guided the next steps for cleaning up outdated docs around Guidelines/FAQ links—prioritizing docs updates over old support topics—in [Review and update topics related to FAQ & Guidelines links](https://meta.discourse.org/t/-/397938/12?silent=true).

- @chapoi answered a theming/layout question with a concrete outlet suggestion (“before-sidebar-sections”) in [I want to lower the header icons down into the top part of the main outlet](https://meta.discourse.org/t/-/392522/6?silent=true).

- @Danielle introduced the purpose of the new Events area with a short “about” topic in [About the Events category](https://meta.discourse.org/t/-/399439/1?silent=true).

_That’s it for today—now excuse us while we sip celebratory “champagne emoji” and dance like Chandler because the RSS feed is live and the big red banner got fixed the right 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: [Março 29, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/787 "2026-03-29T05:01:28Z")

</div>

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

## Key Stats

In the last 24 hours, Meta saw **44 new posts** across **5 new topics** (plus ongoing updates in existing discussions). Reference snapshot: [read more](https://meta.discourse.org/t/-/399499/1?silent=true)

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

| User | Posts | Likes |
| --- | --- | --- |
| @ToddZ | 6 | 3 |
| @merefield | 4 | 4 |
| @Lilly | 3 | 3 |
| @NateDhaliwal | 3 | 1 |
| @awesomerobot | 2 | 4 |
| @Steven | 2 | 3 |
| @ferdnyc | 2 | 1 |
| @stephtara | 1 | 2 |
| @TomoftheFog | 1 | 2 |
| @supermathie | 1 | 1 |

**Team activity (Discourse Team)**: @awesomerobot, @supermathie, and @davidb all weighed in with debugging and polish-minded follow-ups — notably on HEIC/composer issues, API access ergonomics, and hashtag autocomplete fixes ([read more](https://meta.discourse.org/t/-/399453/2?silent=true), [read more](https://meta.discourse.org/t/-/398792/4?silent=true), [read more](https://meta.discourse.org/t/-/294830/8?silent=true)).

* * *

## Interesting Topics

### #Support

- @bck055 asked how to customize the sidebar to look like a “Docs-style” navigation, and the community pointed toward the **Discourse Doc Categories** plugin as the likely source of that UI ([read more](https://meta.discourse.org/t/-/399504/1?silent=true); plugin reference: [read more](https://meta.discourse.org/t/-/322376/1?silent=true)).

- A potentially broken or misunderstood setting: **`use_name_for_username_suggestions`** appears to have _no effect_ on the normal signup form, with confirmations from others and links to related prior behavior changes around username suggestions ([read more](https://meta.discourse.org/t/-/399499/1?silent=true); related: [read more](https://meta.discourse.org/t/-/391542/1?silent=true), [read more](https://meta.discourse.org/t/-/318791/1?silent=true)).

- In a solved thread about _real-name onboarding_, @Jesse_Starks wanted to hide or normalize the username field at signup; @ToddZ suggested using signup instructions via site text, and discussed the (imperfect-but-practical) CSS approach to visually hide the input ([read more](https://meta.discourse.org/t/-/399497/1?silent=true); solution: [read more](https://meta.discourse.org/t/-/399497/2?silent=true); CSS reference: [read more](https://meta.discourse.org/t/-/168101/1?silent=true)).

- For #TAG #mcp: an API user with granular access couldn’t read `about.json`, and the thread moved toward improving both access expectations and the clarity of error messaging for invalid credentials ([read more](https://meta.discourse.org/t/-/398792/3?silent=true); follow-up: [read more](https://meta.discourse.org/t/-/398792/4?silent=true)).

- “Tiny category image” styling continues to be thorny: users noted images being squashed into squares, and the discussion emphasized CSS workarounds if the default behavior doesn’t change ([read more](https://meta.discourse.org/t/-/380837/4?silent=true); follow-up: [read more](https://meta.discourse.org/t/-/380837/5?silent=true)).

### #bug

- A frustrating report described **lost paragraphs / unexpectedly huge posts** tied to uploading HEIC images; investigation focused on reliably reproducing the problem by pairing large text input with the same uploads ([read more](https://meta.discourse.org/t/-/399453/2?silent=true)).

- In hashtag/search UX: **autocomplete** was overriding the first choice when combining category+tag or tag+tag queries, and a fix was proposed in a PR-linked reply ([read more](https://meta.discourse.org/t/-/294830/8?silent=true)).

### #Community\_Building

- A forum owner asked whether their community was “organized enough,” prompting detailed feedback on tag strategy vs. categories, homepage choice (_Latest_ vs _Categories_), and ways to better showcase image-heavy areas using theme components like Topic List Previews ([read more](https://meta.discourse.org/t/-/399483/3?silent=true); Theme component: [read more](https://meta.discourse.org/t/-/209973/1?silent=true)).

- Another “please review my forum” thread highlighted mobile header/CSS rough edges and encouraged experimenting with theme options rather than settling for an “out of the box” generic feel ([read more](https://meta.discourse.org/t/-/399434/6?silent=true); continuing advice: [read more](https://meta.discourse.org/t/-/399434/8?silent=true)).

### #Self-hosting

- A self-hosted instance saw “all plugins not functioning” (tagged #cdn), with the site owner planning weekend tests and follow-up diagnostics ([read more](https://meta.discourse.org/t/-/399466/3?silent=true)).

- In a thread about deploying older Discourse versions (and the realities of downgrades), troubleshooting zeroed in on YAML formatting/indentation—specifically whether `version` was correctly nested under `params` ([read more](https://meta.discourse.org/t/-/399409/20?silent=true); key suggestion: [read more](https://meta.discourse.org/t/-/399409/21?silent=true)).

### #Site\_feedback / #General

- Meta’s branded redesign discussion kept rolling: readability/contrast concerns on dark theme palettes were raised, with direct comparisons between themes and a request for better legibility of linked text ([read more](https://meta.discourse.org/t/-/397246/47?silent=true); tags: #meta-theme-feedback #meta-redesign-2026).

- On [releases.discourse.org](http://releases.discourse.org) feedback, @ferdnyc documented multiple WCAG contrast failures (with specific ratios and affected UI elements), arguing for an accessibility review and concrete variable/color changes ([read more](https://meta.discourse.org/t/-/399414/10?silent=true); extended audit notes: [read more](https://meta.discourse.org/t/-/399414/11?silent=true)).

### #customization:plugin

- A new admin-focused plugin proposal, **Discourse Plugin Cleaner** , aims to audit and safely remove “orphaned” database residue left behind by uninstalled plugins—explicitly emphasizing an audit-first, no-auto-delete posture ([read more](https://meta.discourse.org/t/-/399505/1?silent=true); install guide reference: [read more](https://meta.discourse.org/t/-/19157/1?silent=true)).

- Discourse Daily Challenges shipped **v1.4.0** with “ChallengeBot” (optional) adding DM-based check-in confirmations, reminders, and mention-triggered personal stats commands—nudging engagement without noisy public replies ([read more](https://meta.discourse.org/t/-/398980/39?silent=true)).

* * *

### More notable drive-bys (still active in the last day)

These didn’t make the “top 15” list above, but they did see meaningful activity:

- A formatting-toolbar plugin update was pushed, with follow-up discussion about long-term maintenance and whether AI can help keep community plugins healthy ([read more](https://meta.discourse.org/t/-/40649/197?silent=true); discussion follow-up: [read more](https://meta.discourse.org/t/-/40649/198?silent=true)).
- The MD Topic List Mobile component got a “still holding up” status check-in from its author ([read more](https://meta.discourse.org/t/-/146341/66?silent=true)).
- Tag Intersection Navigator received maintenance + a practical new feature to restore banner notifications while browsing intersections ([read more](https://meta.discourse.org/t/-/368815/26?silent=true)).
- Landing Pages Plugin users reported an admin notice about code needing updates (`discourse.resolver-resolutions`) ([read more](https://meta.discourse.org/t/-/180967/157?silent=true)).
- A small celebration marked “2 years of my instance” in #community-building:praise ([read more](https://meta.discourse.org/t/-/399423/3?silent=true)).
- A Discourse ID / SSO thread reported that adding a secondary email now works again (marked solved) ([read more](https://meta.discourse.org/t/-/398181/3?silent=true)).
- A French #contribute:feature note flagged missing controls when chat is expanded (can’t switch channels or close without resizing) ([read more](https://meta.discourse.org/t/-/399495/1?silent=true)).
- A Chinese #contribute:feature/#ai discussion explored whether an official “openclaw skill” is needed—or whether scoped credentials can solve the workflow without a dedicated skill ([read more](https://meta.discourse.org/t/-/398771/3?silent=true)).

* * *

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

- @awesomerobot responded to a tricky composer/upload report, asking for reproducible steps and error details to help isolate what’s happening when HEIC uploads coincide with text loss/format issues ([read more](https://meta.discourse.org/t/-/399453/2?silent=true)).

- @awesomerobot also weighed in on whether a granular API key should be allowed to read `about.json`, noting it “seems reasonable” and moving toward an implementation change discussed in-thread ([read more](https://meta.discourse.org/t/-/398792/3?silent=true)).

- @supermathie followed up on the same API-access thread, highlighting a possibly misleading “invalid API username/key” error message and suggesting there’s room to improve the UX of that failure mode ([read more](https://meta.discourse.org/t/-/398792/4?silent=true)).

- @davidb posted that a fix for hashtag autocomplete overriding the first choice should land once merged, linking the thread to an actionable resolution path ([read more](https://meta.discourse.org/t/-/294830/8?silent=true)).

* * *

Yesterday, Meta was basically a triathlon of **contrast audits, signup UX mysteries, and HEIC-induced chaos** — may your links be readable, your username suggestions actually suggest, and your uploads keep every paragraph intact.

---

<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: [Março 30, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/788 "2026-03-30T05:01:35Z")

</div>

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

## Key Stats

In the last 24 hours (2026-03-29 → 2026-03-30), meta saw **56 new posts** across **5 new topics**.

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

| User | Posts | Likes |
| --- | --- | --- |
| @Lilly | 6 | 7 |
| @pfaffman | 3 | 7 |
| @merefield | 1 | 7 |
| @Moin | 2 | 5 |
| @Falco | 1 | 4 |
| @elmuerte | 1 | 3 |
| @tobiaseigen | 2 | 3 |
| @sam | 2 | 3 |
| @itsbhanusharma | 2 | 3 |
| @bartv | 1 | 2 |

**Most active [@team](https://meta.discourse.org/groups/team?silent=true) members (posts / likes received):**

- @Falco — **1 / 4**
- @sam — **2 / 3**
- @nat — **1 / 2**
- @HAWK — **3 / 1**
- @martin — **2 / 1**

* * *

## Interesting Topics

### #contribute:feature

- AI translations sparked a UX/product discussion when @tobiaseigen found that **1:1 PMs aren’t translated via backfill** , despite the UI implying “already translated” ([Help me troubleshoot why AI is not translating PMs on my site](https://meta.discourse.org/t/-/399524/1?silent=true)). @Moin clarified the current behavior and what the setting actually affects ([read more](https://meta.discourse.org/t/-/399524/2?silent=true)).

- Building on that, @Falco proposed evolving `ai_translation_backfill_limit_to_public_content` into a **multi-target selector** (including “all PMs”) to make translation scope explicit ([read more](https://meta.discourse.org/t/-/399524/4?silent=true)). @nat also noted upcoming work to _“translate these categories”_ and suggested the settings may be redesigned around clearer toggles ([read more](https://meta.discourse.org/t/-/399524/5?silent=true), plus the related feature request: [read more](https://meta.discourse.org/t/-/392993/1?silent=true)).

- The long-running request for an **AliExpress affiliate plugin** got another nudge, with renewed interest (and willingness to pay) from @Viddekla ([AliExpress affiliate plugin](https://meta.discourse.org/t/-/340991/3?silent=true)).

### #bug

- A report suggests the setting **“Use name for username suggestions”** currently has _no effect_ on the signup form. @HAWK validated behavior on [try.discourse.org](http://try.discourse.org) and moved the report into #bug for tracking ([“Use name for username suggestions”: no effect on signup form?](https://meta.discourse.org/t/-/399499/3?silent=true) #signup).

- A sudden wave of **Google Search Console `acceptedAnswer` structured data warnings** appeared after updating, despite the topic being old and stable. The report explicitly continues an earlier thread about Google’s expectations for solved/unsolved markup ([Google search console acceptedAnswer error](https://meta.discourse.org/t/-/399525/1?silent=true) ↔︎ prior discussion: [read more](https://meta.discourse.org/t/-/111809/3?silent=true)).

- “OpenClaw plugin for Discourse integration” hit a sharp edge: an integration page started returning 404 for at least one user. @sam suspected a routing issue and then identified it as **a missing Ember route** that deserves its own tracking topic ([OpenClaw plugin for Discourse integration](https://meta.discourse.org/t/-/397239/11?silent=true), follow-up: [read more](https://meta.discourse.org/t/-/397239/13?silent=true)).

### #Support

- Root-level convenience pages like `/faq`, `/about`, and `/privacy` are confusingly “topic-like” but behave specially. In “How do root level links work?”, @itsbhanusharma explained they’re effectively **hardcoded routes** , and suggested using **Page Publishing** for additional static pages ([How do root level links work?](https://meta.discourse.org/t/-/399520/2?silent=true), Page Publishing: [read more](https://meta.discourse.org/t/-/151971/1?silent=true)). @Lilly added that **permalinks** can provide friendly URLs that point at published pages ([read more](https://meta.discourse.org/t/-/399520/3?silent=true)).

- Scheduling posts + group mentions still has a sharp limitation: mentions **don’t fire when a scheduled topic is published**. The workaround is to edit after publishing, and @HAWK pointed to the canonical explanation ([Question about group mentions in a private category](https://meta.discourse.org/t/-/399539/1?silent=true), reference: [read more](https://meta.discourse.org/t/-/212342/2?silent=true) #groups #mentions #notifications).

- Printing/exporting a **single post** remains a practical need for teams that repost Discourse content into other tools. “Is there a way to print a single post in a topic?” revisited the **clean-export** approach and whether it should be available at lower trust levels ([Is there a way to print a single post in a topic?](https://meta.discourse.org/t/-/258689/16?silent=true), staff/TL discussion: [read more](https://meta.discourse.org/t/-/258689/18?silent=true)).

- Category styling friction: “Tiny category image” includes feedback that a recent change to `aspect-image` no longer preserving aspect ratio forced admins into CSS workarounds ([Tiny category image](https://meta.discourse.org/t/-/380837/6?silent=true)).

- A “Starter plan” constraint came up in “Customize registration form / hide or normalize username field”: @HAWK reiterated that certain UI/CSS customizations can’t be implemented there, even if it doesn’t resolve the underlying username-suggestion issue ([Customize registration form / hide or normalize username field](https://meta.discourse.org/t/-/399497/8?silent=true)).

### #Self-hosting

- A post-upgrade **CORS failure** left admins reporting “all plugins not functioning” when using a CDN (including [bunny.net](http://bunny.net)). @pfaffman linked it to a recent change in behavior and compared it with earlier CDN/CORS guidance ([All plugins not functioning due to CORS error after recent upgrade](https://meta.discourse.org/t/-/399466/4?silent=true), related [bunny.net](http://bunny.net) thread: [read more](https://meta.discourse.org/t/-/296333/1?silent=true) #cdn).

- “How to set up fine-grained admin permissions or limit export capability?” revisited the evergreen truth that admins have broad powers; still, a potential mitigation discussed was enforcing config via environment precedence (so UI changes won’t “win”) ([How to set up fine-grained admin permissions or limit export capability?](https://meta.discourse.org/t/-/399510/1?silent=true) #backups). The automation angle was tied back to standard guidance on scheduled backups ([read more](https://meta.discourse.org/t/-/14855/1?silent=true)).

- Deploying **older Discourse versions** got a practical “latest summary” in Chinese: set `params: version: esr` in `containers/app.yml` and rebuild; network conditions (notably for China) may be the biggest source of build failures ([Help deploying older versions of Discourse](https://meta.discourse.org/t/-/399409/24?silent=true)).

### #customization:plugin

- “Plugin Cleaner” prompted careful skepticism: @merefield praised the intent but highlighted tricky edge cases like plugin-created tables, migrations disappearing on uninstall, and risks around identifying core vs plugin custom fields ([Plugin Cleaner](https://meta.discourse.org/t/-/399505/2?silent=true)). @pfaffman noted the risk of breaking the DB is non-zero and questioned whether leftover tables are typically harmful ([read more](https://meta.discourse.org/t/-/399505/3?silent=true)); @elmuerte added foreign keys can complicate deletion and may need a core-level “disarm” pattern ([read more](https://meta.discourse.org/t/-/399505/4?silent=true)).

- “Discourse Daily Challenges” continued with implementation/ops questions about bot commands triggered via `@mention` and where responses should be sent (topic vs PM), plus practical styling work shared as CSS ([Discourse Daily Challenges](https://meta.discourse.org/t/-/398980/41?silent=true), mention behavior clarification: [read more](https://meta.discourse.org/t/-/398980/43?silent=true)).

- A quick localization request landed on the “Geo Blocking plugin”: a user asked whether the plugin could support **customizable prompt text** ([Geo Blocking plugin](https://meta.discourse.org/t/-/227824/37?silent=true)).

### #Announcements

- Form Templates keep evolving in the community’s imagination: a request asked for **sections/headings** , internal-only notes, and even generating the _topic title_ from the form definition ([Introducing Form Templates](https://meta.discourse.org/t/-/278631/88?silent=true) #form-templates #feedback #new-feature).

- Category UX for support workflows: @martin confirmed you can enable solved behavior per-category today (with a screenshot), and hinted at future UI improvements to make it more discoverable ([Easily create Support categories using the discourse-solved plugin](https://meta.discourse.org/t/-/398338/13?silent=true) #solved).

### #Integrations

- “Create a [Data Explorer](https://meta.discourse.org/t/32566?silent=true) query using the API” resurfaced integration pain points: a tooling break due to a path change was called “annoying,” and a possible bug was flagged where a **Global API key** seems required where read-only previously worked ([Create a Data Explorer query using the API](https://meta.discourse.org/t/-/394388/4?silent=true) #data-explorer #rest-api).

### #ux

- “Review and update topics related to FAQ & Guidelines links” got a quick historical update: @martin pointed out a related UI behavior was removed via a core PR a few weeks back ([Review and update topics related to FAQ & Guidelines links](https://meta.discourse.org/t/-/397938/15?silent=true)).

* * *

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

- @Falco weighed in on the AI translation PM confusion and proposed a clearer configuration model: turning a single boolean into a **targets dropdown** (public only → all topics → all topics + group PMs → all topics + all PMs) in [this reply](https://meta.discourse.org/t/-/399524/4?silent=true).

- @nat added that settings will likely be revisited soon, especially with _“translate these categories”_ on the way, and suggested splitting controls into explicit “translate PMs” plus a category selector ([read more](https://meta.discourse.org/t/-/399524/5?silent=true); related: [read more](https://meta.discourse.org/t/-/392993/1?silent=true)).

- @sam investigated a reported 404 in the OpenClaw integration thread, then concluded it looks like a core routing issue (“missing an Ember route”) and should be tracked separately ([read more](https://meta.discourse.org/t/-/397239/11?silent=true), follow-up: [read more](https://meta.discourse.org/t/-/397239/13?silent=true)).

- @HAWK did a sweep of support/bug triage: confirmed and re-categorized the username suggestion problem as a #bug with reproduction details ([read more](https://meta.discourse.org/t/-/399499/3?silent=true)), clarified plan limitations around CSS-based registration changes ([read more](https://meta.discourse.org/t/-/399497/8?silent=true)), and linked the canonical explanation for scheduled-mention notification behavior ([read more](https://meta.discourse.org/t/-/399539/3?silent=true)).

- @martin provided two “paper cut” clarifications: highlighted that an FAQ/guidelines behavior had already been removed upstream ([read more](https://meta.discourse.org/t/-/397938/15?silent=true)), and showed how to enable solved support behavior per-category (with notes about future UI improvements) ([read more](https://meta.discourse.org/t/-/398338/13?silent=true)).

* * *

If yesterday taught us anything, it’s that **PMs still have boundaries, routes still go missing, and plugins still need adults in the room** —happy shipping!

---

<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: [Março 31, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/789 "2026-03-31T05:01:40Z")

</div>

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

## Key Stats

In the last 24 hours (2026-03-30 → 2026-03-31), Meta saw **98 new posts** across **17 new topics**.

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

- **@Moin** — **16 posts** , **21 likes** (lots of localization deep-dives, starting with [AI tag translation issues](https://meta.discourse.org/t/-/399570/1?silent=true))
- **@david** — **5 posts** , **10 likes** (debugging a migration collision in [a bootstrap failure report](https://meta.discourse.org/t/-/399572/4?silent=true))
- **@nat** — **3 posts** , **9 likes** (quick follow-up on prompts in [AI tag translation quality](https://meta.discourse.org/t/-/399570/3?silent=true))
- **@zogstrip** — **5 posts** , **7 likes** (clarified a signup setting in [username suggestions behavior](https://meta.discourse.org/t/-/399499/4?silent=true))
- **@pfaffman** — **8 posts** , **5 likes** (tracked down the root cause in [the migration collision thread](https://meta.discourse.org/t/-/399572/5?silent=true))
- **@darkpixlz** — **5 posts** , **5 likes** (confirmed deletion emails are expected in [spam-account deletion notifications](https://meta.discourse.org/t/-/399576/2?silent=true))
- **@Falco** — **5 posts** , **4 likes** (suggested adding more context/tooling for translations in [the tag translations topic](https://meta.discourse.org/t/-/399570/4?silent=true))
- **@sam** — **2 posts** , **3 likes** (commented on router-related 404s in [OpenClaw integration discussion](https://meta.discourse.org/t/-/397239/15?silent=true))
- **@schleifer** — **1 post** , **3 likes** (noted a CDN endpoint was retired in [the invalid SSL report](https://meta.discourse.org/t/-/399543/3?silent=true))
- **@jrgong** — **1 post** , **3 likes** (enthusiastic feedback on PM translation progress in [AI PM translation troubleshooting](https://meta.discourse.org/t/-/399524/7?silent=true))

> Quote of the day: “If you want, I can also make it a little more **pfaffman-style blunt and short**.” — shared in the migration thread ([read more](https://meta.discourse.org/t/-/399572/2?silent=true))

## Interesting Topics

### #Site feedback

- @Moin catalogued hilarious-but-problematic AI tag localizations (e.g. _#composer → “Komponist”_) and raised the more serious issue of _colliding translations breaking meaning_ in [AI-generated tag translations do not work perfectly](https://meta.discourse.org/t/-/399570/1?silent=true); @nat planned prompt improvements ([read more](https://meta.discourse.org/t/-/399570/3?silent=true)), while @Falco floated tool-assisted context gathering ([read more](https://meta.discourse.org/t/-/399570/4?silent=true)) and discussion expanded to glossary/source grounding and what “localization” really needs ([read more](https://meta.discourse.org/t/-/399570/9?silent=true)). Related: [Introducing our new Composer](https://meta.discourse.org/t/-/369779/1?silent=true) and a prior German translation feedback thread ([read more](https://meta.discourse.org/t/-/374750/1?silent=true)).

- The ongoing Meta theme refresh continues: @manuel acknowledged color/accessibility rough edges and pointed to a new theme modifier to limit available color schemes in [Meta Branded redesign: theme refresh](https://meta.discourse.org/t/-/397246/48?silent=true); a “link highlighting” scare turned out to be local CSS bleed from an unrelated theme on @darkpixlz’s machine ([read more](https://meta.discourse.org/t/-/397246/53?silent=true)).

### #Self-hosting

- A bootstrap failure (“relation `ai_agent_mcp_servers` does not exist”) turned into a migration-version collision postmortem in [Bootstrap error… due to migration id collision](https://meta.discourse.org/t/-/399572/1?silent=true): @david confirmed the upstream migration order looked fine ([read more](https://meta.discourse.org/t/-/399572/4?silent=true)), and @pfaffman ultimately traced it to same-day migration-number overlap and fixed it by renumbering the schema migration locally ([read more](https://meta.discourse.org/t/-/399572/7?silent=true)).

- Self-hosters compared “rebuild vs replace” upgrade flows and release tracking expectations in [Production upgrades - correct procedure to follow](https://meta.discourse.org/t/-/399550/1?silent=true); @Moin emphasized understanding channels and the no-downgrade reality ([read more](https://meta.discourse.org/t/-/399550/4?silent=true)) with pointers to [Understanding Discourse release channels](https://meta.discourse.org/t/-/264400/1?silent=true) and [Configure a supported tracking branch](https://meta.discourse.org/t/-/17014/1?silent=true).

- CDN + modern JS module loading bit a site after an upgrade: the resolution in [All plugins not functioning due to CORS error after recent upgrade](https://meta.discourse.org/t/-/399466/6?silent=true) explains why `script type="module"` tightens CORS requirements and why setting headers fixes not only plugins, but other resources too.

- Older-version deployments got an extra clarification: @david explained why `git symbolic-ref` “failure” is expected for tags, and that the flow should still work, in [Help deploying older versions of Discourse](https://meta.discourse.org/t/-/399409/25?silent=true); @pfaffman added a warning about editing templates directly and how it can come back to bite later ([read more](https://meta.discourse.org/t/-/399409/26?silent=true)).

### #Support

- A report that `https://discourse-cdn-sjc1.com` had an invalid SSL cert led to the key context that the endpoint was retired years ago; @schleifer asked for a hosted-site link so support can confirm nothing was missed in [Discourse CDN with an invalid SSL cert?](https://meta.discourse.org/t/-/399543/3?silent=true).

- Moderation workflow question: should Discourse email accounts deleted for spam? In [Should Discourse notify users when accounts are deleted for spam?](https://meta.discourse.org/t/-/399576/1?silent=true), @darkpixlz confirmed the `account_deleted` email is expected behavior ([read more](https://meta.discourse.org/t/-/399576/2?silent=true)) and linked prior design discussion in [turning off emails to deleted users/spammers](https://meta.discourse.org/t/-/382412/11?silent=true).

- A tricky “Image could not be loaded” zoom issue appeared account/browser-state related: incognito worked while logged-in did not, in [“Image could not be loaded error” when click to zoom in](https://meta.discourse.org/t/-/399548/3?silent=true); troubleshooting focused on [safe mode](https://meta.discourse.org/t/53504?silent=true), alternate accounts, and hard reloads ([read more](https://meta.discourse.org/t/-/399548/4?silent=true)).

### #ux

- Signup UX expectations were reset: the `use name for username suggestions` setting only affects SSO/OAuth flows, not local signup, and @zogstrip updated the setting description in [“Use name for username suggestions”: no effect on signup form?](https://meta.discourse.org/t/-/399499/4?silent=true).

- A long-running papercut got a fix path: users couldn’t unfollow banned/suspended accounts without temporarily unsuspending them; @zogstrip responded with “That should fix it ;)” and linked a PR in [Banned members cannot be Unfollowed](https://meta.discourse.org/t/-/304256/3?silent=true).

- Review Queue visibility confusion: moderators can _see counts_ of “helpful flags” but can’t click through; the behavior looks unintended in [Why can’t we see helpful flags?](https://meta.discourse.org/t/-/399600/1?silent=true), with a workaround of filtering the review queue to Approved ([read more](https://meta.discourse.org/t/-/399600/2?silent=true)).

### #Dev

- A dependency ecosystem win: a contributor PR to support Sidekiq 8 in mini\_scheduler was merged and shipped quickly after @dmke’s post in [PR: Add Sidekiq 8 support to mini\_scheduler](https://meta.discourse.org/t/-/399560/2?silent=true).

- A “recent work surfaced this issue” moment: Google Search Console’s `acceptedAnswer` structured data error will be fixed via a linked PR, per @zogstrip in [Google search console acceptedAnswer error](https://meta.discourse.org/t/-/399525/2?silent=true).

### #General

- A community operator asked for real-world experiences running multilingual Discourse (rollout strategy, moderation, expectations) in [Seeking experience: Supporting a multilingual Discourse community](https://meta.discourse.org/t/-/399606/1?silent=true), and was pointed toward the newer AI localization overview at [Content localization (manual and automatic) with Discourse AI](https://meta.discourse.org/t/-/370969/1?silent=true).

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

- **@nat** followed up on tag localization quality: acknowledged the detailed examples, promised prompt work, and discussed predictable context strategies in [AI-generated tag translations do not work perfectly](https://meta.discourse.org/t/-/399570/3?silent=true) and [read more](https://meta.discourse.org/t/-/399570/5?silent=true).

- **@Falco** pushed for better grounding/context on AI translations (including tool access and source translation alignment) in [AI-generated tag translations do not work perfectly](https://meta.discourse.org/t/-/399570/4?silent=true) and later replies ([read more](https://meta.discourse.org/t/-/399570/11?silent=true)); they also set expectations about external calendar refresh delays in [Calendar subscription URLs for external calendar apps](https://meta.discourse.org/t/-/398902/12?silent=true).

- **@david** investigated the migration-order mystery in [Bootstrap error… due to migration id collision](https://meta.discourse.org/t/-/399572/4?silent=true), suggested mitigation ideas for AI-generated migrations ([read more](https://meta.discourse.org/t/-/399572/6?silent=true)), explained why modern plugin delivery needs correct CDN CORS headers in [All plugins not functioning due to CORS error after recent upgrade](https://meta.discourse.org/t/-/399466/6?silent=true), confirmed tag-based deploy logic in [Help deploying older versions of Discourse](https://meta.discourse.org/t/-/399409/25?silent=true), and merged/released the Sidekiq support update in [PR: Add Sidekiq 8 support to mini\_scheduler](https://meta.discourse.org/t/-/399560/2?silent=true).

- **@zogstrip** clarified signup setting scope (SSO/OAuth vs local) and updated copy in [“Use name for username suggestions”: no effect on signup form?](https://meta.discourse.org/t/-/399499/4?silent=true); offered a fix via PR for the unfollow-banned edge case in [Banned members cannot be Unfollowed](https://meta.discourse.org/t/-/304256/3?silent=true); flagged an attendee-management fix for recurring events in [Repeating Event “going” gets not deleted anymore](https://meta.discourse.org/t/-/335780/13?silent=true); and linked a forthcoming structured-data fix in [Google search console acceptedAnswer error](https://meta.discourse.org/t/-/399525/2?silent=true).

- **@sam** discussed the “two routers” tax and why `/llms.txt` should be fixed (even if `safe-mode` is “kind of OK”) in [OpenClaw plugin for Discourse integration](https://meta.discourse.org/t/-/397239/15?silent=true), and noted the AI-migration instruction is frequently ignored in the collision thread ([read more](https://meta.discourse.org/t/-/399572/8?silent=true)).

- **@manuel** acknowledged color/link consistency concerns and outlined the approach for iterating on the Meta theme using a new theme modifier in [Meta Branded redesign: theme refresh](https://meta.discourse.org/t/-/397246/48?silent=true), plus follow-up debugging questions ([read more](https://meta.discourse.org/t/-/397246/52?silent=true)).

- **@schleifer** provided historical context that the reported CDN host was retired (2019) and directed next steps for hosted support triage in [Discourse CDN with an invalid SSL cert?](https://meta.discourse.org/t/-/399543/3?silent=true).

- **@awesomerobot** confirmed a Horizon theme fix is coming (with a linked core change) in [Category creation floating box blocks out settings at the bottom](https://meta.discourse.org/t/-/399481/4?silent=true).

- **@chapoi** handled support triage and clarified intended chat fullscreen behavior (sidebar channel switching + dedicated page behavior) in [Pouvoir changer de canaux et de fermer en grande fenêtre chat](https://meta.discourse.org/t/-/399495/4?silent=true) (after requesting repro details in [read more](https://meta.discourse.org/t/-/399495/2?silent=true)).

_Sign-off:_ If today’s Meta taught us anything, it’s: don’t let your #composer turn into a “Komponist” and please—give your migrations real timestamps before they try to out-“pfaffman-style” @pfaffman.

---

<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: [Abril 1, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/790 "2026-04-01T05:01:43Z")

</div>

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

## Key Stats

In the last 24 hours (2026-03-31 → 2026-04-01), Meta saw **95 new posts** across **13 new topics** (plus continued discussion on several active threads), including the **2026.3 monthly release notes** and a big step forward for **Discourse AI + MCP**. ([read more](https://meta.discourse.org/t/-/399630/1?silent=true), [read more](https://meta.discourse.org/t/-/399668/1?silent=true))

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

- **@david** — 7 posts / 10 likes ([read more](https://meta.discourse.org/t/-/399630/1?silent=true), [read more](https://meta.discourse.org/t/-/399614/5?silent=true))
- **@Moin** — 5 posts / 3 likes ([read more](https://meta.discourse.org/t/-/399649/10?silent=true), [read more](https://meta.discourse.org/t/-/399611/2?silent=true))
- **@awesomerobot** — 4 posts / 7 likes ([read more](https://meta.discourse.org/t/-/341613/8?silent=true), [read more](https://meta.discourse.org/t/-/398894/5?silent=true))
- **@nat** — 3 posts / 9 likes ([read more](https://meta.discourse.org/t/-/399661/1?silent=true), [read more](https://meta.discourse.org/t/-/392993/5?silent=true))
- **@RGJ** — 3 posts / 6 likes ([read more](https://meta.discourse.org/t/-/399611/1?silent=true), [read more](https://meta.discourse.org/t/-/398896/10?silent=true))
- **@sam** — 2 posts / 9 likes ([read more](https://meta.discourse.org/t/-/399668/1?silent=true), [read more](https://meta.discourse.org/t/-/399667/1?silent=true))
- **@merefield** — 2 posts / 5 likes ([read more](https://meta.discourse.org/t/-/398896/9?silent=true), [read more](https://meta.discourse.org/t/-/398894/3?silent=true))
- **@Falco** — 2 posts / 4 likes ([read more](https://meta.discourse.org/t/-/399610/2?silent=true), [read more](https://meta.discourse.org/t/-/399606/4?silent=true))
- **@denvergeeks** — 2 posts / 3 likes ([read more](https://meta.discourse.org/t/-/398759/75?silent=true), [read more](https://meta.discourse.org/t/-/399466/11?silent=true))
- **@Ed_S** — 1 post / 3 likes ([read more](https://meta.discourse.org/t/-/399630/2?silent=true))

* * *

## Interesting Topics

### #Announcements

- **Discourse 2026.3 shipped** : @david published the **March 2026 monthly release** with links to the changelog and patch releases; @Ed_S reported a smooth switch to the `release` track and quick rebuild time. ([read more](https://meta.discourse.org/t/-/399630/1?silent=true), [read more](https://meta.discourse.org/t/-/399630/2?silent=true))

- **“Bring your own MCP!” lands for Discourse AI agents** : @sam announced that Discourse AI agents can now connect to any external **MCP server** (GitHub/Notion/Linear/etc.), positioning Discourse as both **MCP client and server** alongside the earlier “Discourse MCP is here!” work. ([read more](https://meta.discourse.org/t/-/399668/1?silent=true), [read more](https://meta.discourse.org/t/-/399667/1?silent=true), [read more](https://meta.discourse.org/t/-/386983/29?silent=true))

### #blog

- **Behind the scenes on multilingual support** : @nat posted “Building for Every Language”, recounting how Discourse’s multilingual story evolved over 13 years (and why the practical details still matter). ([read more](https://meta.discourse.org/t/-/399661/1?silent=true))

- **MCP feedback continues** : the older MCP thread kept drawing “what’s next?” suggestions—like hosting an MCP endpoint at a well-known URL and enabling LLMs to edit existing posts for wiki/KB workflows. ([read more](https://meta.discourse.org/t/-/386983/29?silent=true), [read more](https://meta.discourse.org/t/-/386983/30?silent=true))

### #Dev (#dev-news)

- **Theme/plugin template modernization: `.hbs` deprecation debate** : the discussion around deprecating `.hbs` escalated into a broader conversation about maintenance burden vs. platform velocity, with community members pointing to automated conversion guidance. ([read more](https://meta.discourse.org/t/-/398896/8?silent=true), [read more](https://meta.discourse.org/t/-/398896/10?silent=true), [read more](https://meta.discourse.org/t/-/368051/1?silent=true))

- **File extension cleanup: `.js.es6` deprecation and “compatibility fatigue”** : pushback continued, but the thread also surfaced concrete help—@awesomerobot offered to open PRs for open-source plugins, while others reiterated this is mostly a rename. ([read more](https://meta.discourse.org/t/-/398894/2?silent=true), [read more](https://meta.discourse.org/t/-/398894/5?silent=true))

### #Support

- **Ongoing translation in threads (and the “chat translation gap”)**: @malangali outlined a real-world need for paragraph-by-paragraph translation visibility across multiple languages; @Falco pointed to **content localization** as covering most needs, noting chat translation is still pending. ([read more](https://meta.discourse.org/t/-/399610/1?silent=true), [read more](https://meta.discourse.org/t/-/399610/2?silent=true), [read more](https://meta.discourse.org/t/-/370969/1?silent=true))

- **AI bot errors (“Not found”) tied to model configuration drift**: a support thread suggested deprecated model IDs/URLs might be behind errors from AI bots that “appeared from last year,” with guidance to review configured LLMs. ([read more](https://meta.discourse.org/t/-/399660/1?silent=true), [read more](https://meta.discourse.org/t/-/399660/2?silent=true))

- **Custom “/rules” and “/apply” pages (integrated, not `pub`)**: a new support topic asked for custom pages that sit alongside built-ins like **About** and **FAQ** , without Page Publishing’s URL structure. ([read more](https://meta.discourse.org/t/-/399679/1?silent=true), [read more](https://meta.discourse.org/t/-/151971/1?silent=true))

### #contribute:feature

- **Allow incoming email for automatic groups** : @RGJ requested making “email-in” configurable for automatic groups (to avoid awkward “shadow group” workarounds), noting the current UI is confusingly silent about the restriction. ([read more](https://meta.discourse.org/t/-/399611/1?silent=true), [read more](https://meta.discourse.org/t/-/62724/1?silent=true), [read more](https://meta.discourse.org/t/-/212147/3?silent=true))

- **AI translation controls are getting more granular** : a PR was shared to **limit topic translation to specific categories** , and the related “PM translation troubleshooting” thread reiterated how settings will migrate into clearer category/PM targeting. ([read more](https://meta.discourse.org/t/-/392993/5?silent=true), [read more](https://meta.discourse.org/t/-/399524/8?silent=true))

### #bug

- **Chat plugin failing to compile in the rollup plugin compiler** : @david followed up on a persistent `_assert is not a function` error and suspected something installation-specific given the lack of similar reports. ([read more](https://meta.discourse.org/t/-/399321/3?silent=true), [read more](https://meta.discourse.org/t/-/399321/5?silent=true))

- **Topic Voting “missing past votes” turned into a CDN/CORS investigation** : what looked like deprecated params breaking multiple plugins ended up pointing to new module loading + CDN header requirements; the same pattern connected back to the larger “all plugins not functioning due to CORS” discussion. ([read more](https://meta.discourse.org/t/-/399649/1?silent=true), [read more](https://meta.discourse.org/t/-/399649/14?silent=true), [read more](https://meta.discourse.org/t/-/399466/8?silent=true))

### #ux

- **Infinite “is replying…” presence indicator** : a rare stuck “replying” state appeared in multiple threads; suggestions included toggling `Presence enabled` and checking whether a bot account might be stuck. ([read more](https://meta.discourse.org/t/-/399655/1?silent=true), [read more](https://meta.discourse.org/t/-/399655/2?silent=true), [read more](https://meta.discourse.org/t/-/399655/3?silent=true))

- **“Reply to this message” goes nowhere when no contact is set** : @awesomerobot traced the UX trap to `site_contact_username` / `site_contact_group_name` and opened a PR to avoid telling people to reply when it would route to an unmonitored system account. ([read more](https://meta.discourse.org/t/-/399477/2?silent=true))

* * *

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

- **@david** drove updates and troubleshooting across the board: published the **2026.3 release announcement** ([read more](https://meta.discourse.org/t/-/399630/1?silent=true)), clarified why **downgrading to ESR breaks** due to schema incompatibility in a solved “Oops” thread ([read more](https://meta.discourse.org/t/-/399614/9?silent=true)), and continued investigating a **chat build failure** by asking about local customization/patching ([read more](https://meta.discourse.org/t/-/399321/5?silent=true)).

- **@sam** advanced Discourse’s MCP story in two places: the headline **“Bring your own MCP!”** announcement ([read more](https://meta.discourse.org/t/-/399668/1?silent=true)) and the detailed admin guide explaining how to register and assign MCP servers to agents ([read more](https://meta.discourse.org/t/-/399667/1?silent=true)).

- **@nat** kept multilingual/translation work moving: published the “Building for Every Language” companion discussion ([read more](https://meta.discourse.org/t/-/399661/1?silent=true)) and linked the PR that enables **translation targeting by category** (also echoed in the PM translation troubleshooting thread). ([read more](https://meta.discourse.org/t/-/392993/5?silent=true), [read more](https://meta.discourse.org/t/-/399524/8?silent=true))

- **@awesomerobot** focused on quality-of-life fixes and offering hands-on help: offered to update open-source plugins affected by file extension changes ([read more](https://meta.discourse.org/t/-/398894/5?silent=true)), opened/merged a PR to link “helpful flags” to the new review filter ([read more](https://meta.discourse.org/t/-/341613/8?silent=true)), probed the “infinite replying” bug for bot-like behavior ([read more](https://meta.discourse.org/t/-/399655/3?silent=true)), and filed a UX PR to prevent “reply to this message” dead-ends when contacts aren’t configured. ([read more](https://meta.discourse.org/t/-/399477/2?silent=true))

- **@Falco** helped connect multilingual needs to existing tooling: in the “ongoing translation” thread, @Falco pointed admins to **content localization** while setting expectations that **chat translation** isn’t there yet ([read more](https://meta.discourse.org/t/-/399610/2?silent=true)); and in the “supporting a multilingual community” discussion, shared how Discourse is applying this in practice (with examples in French/Chinese). ([read more](https://meta.discourse.org/t/-/399606/4?silent=true), [read more](https://meta.discourse.org/t/-/399495/1?silent=true), [read more](https://meta.discourse.org/t/-/391136/1?silent=true))

- **@Danielle** refined event organization on Meta: clarified how **webinars vs office hours** will be structured going forward ([read more](https://meta.discourse.org/t/-/399640/1?silent=true)) and quickly fixed a confusing time display in the moderator-program webinar listing. ([read more](https://meta.discourse.org/t/-/398295/6?silent=true))

- **@renato** followed up on a long-running composer quirk: noted a recent change ensuring the rich editor consistently serializes closed `[details]` blocks regardless of their UI state, and asked for confirmation if issues remain. ([read more](https://meta.discourse.org/t/-/377645/23?silent=true))

- **@HAWK** weighed in on embedding site metrics: responded to a “how do I embed activity/graphs on my website?” question and (after a plan mix-up) the thread continued toward self-hosted implementation details. ([read more](https://meta.discourse.org/t/-/399678/2?silent=true))

- **@featheredtoast** contributed to the “discourse/discourse docker image” thread: explained why you can’t realistically bolt plugins onto that image at boot, and outlined a path toward building and publishing custom images (including a personal example using a voice-room plugin). ([read more](https://meta.discourse.org/t/-/380646/25?silent=true), [read more](https://meta.discourse.org/t/-/389056/1?silent=true))

- **@j.jaffeux** revisited expected behavior in Calendar recurring events: clarified why “going” participants may not reset without per-date event entries, keeping the thread grounded in product constraints. ([read more](https://meta.discourse.org/t/-/335780/14?silent=true))

* * *

> If yesterday was any indication, the community’s theme files are getting renamed, plugins are getting CORS headers, and AI agents are out shopping for MCP servers—busy day to be a Discourse admin.

---

<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: [Abril 2, 2026, 5:01am UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/791 "2026-04-02T05:01:39Z")

</div>

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

## Key Stats

In the last 24 hours, Meta logged **112 new posts** across **7 new topics** , with much of the energy centered around the new **full-app embedding experience** ([read more](https://meta.discourse.org/t/-/399743/1?silent=true)), an **April Fools-ready splash-screen theme component** ([read more](https://meta.discourse.org/t/-/399690/1?silent=true)), and a **mobile viewport regression** traced to a theme component change ([read more](https://meta.discourse.org/t/-/399691/1?silent=true)).

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

| User | Posts | Likes |
| --- | --- | --- |
| @Moin | 15 | 19 |
| @Falco | 11 | 43 |
| @Lilly | 7 | 16 |
| @zogstrip | 6 | 6 |
| @R23D_Printing | 6 | 4 |
| @ToddZ | 5 | 6 |
| @WorldIsMine | 3 | 7 |
| @RGJ | 2 | 10 |
| @davidb | 1 | 8 |
| @nat | 1 | 4 |

* * *

## Interesting Topics

### #Announcements

- @Falco announced **“full app mode” embeds** , letting visitors _reply/like/quote_ directly inside an iframe—turning Discourse embedding into a true comment-system experience ([read more](https://meta.discourse.org/t/-/399743/1?silent=true)). Follow-up discussion covered trimmed embed UI choices and login behavior (e.g. prompting auth in a new tab) ([read more](https://meta.discourse.org/t/-/399743/7?silent=true)), with related “this is now possible” pointers dropped into older embedding/dev threads ([read more](https://meta.discourse.org/t/-/49811/10?silent=true), [read more](https://meta.discourse.org/t/-/360386/5?silent=true), [read more](https://meta.discourse.org/t/-/81473/9?silent=true)).

- Real-world feedback continued on **calendar subscription URLs** (bookmarks + events), including requests for permission-aware filtering and “show URLs until revoked” ergonomics ([read more](https://meta.discourse.org/t/-/398902/15?silent=true)). One common gotcha: you won’t see event subscriptions unless the `Discourse post event enabled` setting is on ([read more](https://meta.discourse.org/t/-/398902/17?silent=true)).

- The **Upcoming Changes** system got a usability nudge: @Moin asked for a way to sort by status (alpha/beta/experimental), and @martin agreed—planning status sorting and a “first appeared on your site” option ([read more](https://meta.discourse.org/t/-/392894/19?silent=true), [read more](https://meta.discourse.org/t/-/392894/20?silent=true)).

### #customization:theme component

- @RGJ released **Full Screen Cover Image** , a theme component that overlays a fullscreen splash/cover on page load—perfect for maintenance notices or _April 1st mischief_ ([read more](https://meta.discourse.org/t/-/399690/1?silent=true)). Community stories confirmed it’s effective at ensuring _everyone_ sees the message ([read more](https://meta.discourse.org/t/-/399690/8?silent=true)), and the topic includes [standard install](https://meta.discourse.org/t/142537?silent=true) references for theme newcomers ([read more](https://meta.discourse.org/t/-/63682/1?silent=true), [read more](https://meta.discourse.org/t/-/91966/1?silent=true)).

### #bug

- A **mobile viewport “blank topic”** issue hit Meta itself: pages showed only header/title with broken header links. It was confirmed by @dax, and later traced by @davidb to a recent change in the `discourse-tag-icons` theme component—with a temporary revert while the root cause is investigated ([read more](https://meta.discourse.org/t/-/399691/1?silent=true), [read more](https://meta.discourse.org/t/-/399691/2?silent=true), [read more](https://meta.discourse.org/t/-/399691/5?silent=true)).

- Archived topics showed **inconsistent “like/reaction” behavior** : posts with no reactions appeared “likeable” but then threw an error, pointing to edge-case logic in the #reactions integration. @zogstrip confirmed the logic problem and linked a fix in progress ([read more](https://meta.discourse.org/t/-/399681/1?silent=true), [read more](https://meta.discourse.org/t/-/399681/5?silent=true)).

- A #groups admin workflow bug: **bulk-adding emails** to a group could still send invitations even when “Notify users” was unchecked. @zogstrip confirmed and queued a fix ([read more](https://meta.discourse.org/t/-/397334/2?silent=true)).

### #ux

- Improving the #review-queue experience: when a post is **rejected** , users currently can’t easily edit-and-resubmit. @awesomerobot proposed a pragmatic fix—auto-create a draft from the rejected content and link the user to it—and opened a PR to implement it ([read more](https://meta.discourse.org/t/-/373992/19?silent=true)).

- The **Horizon theme sticky header** discussion continued: making only the navigation sticky (while the category heading collapses) isn’t straightforward with the current DOM structure, and a structural change risks theme regressions. @awesomerobot explained why CSS alone won’t solve it cleanly ([read more](https://meta.discourse.org/t/-/387267/11?silent=true)).

### #contribute:feature

- #tag-icons + #content-localization got a boost: @nat shared progress toward **translated tags support** in the tag icon component via a PR, with a promise to merge soon ([read more](https://meta.discourse.org/t/-/399594/3?silent=true)). This also pairs nicely with the earlier mobile regression discussion that involved the same component ecosystem ([read more](https://meta.discourse.org/t/-/399691/5?silent=true)).

- #gamification: “ **per leaderboard scoring values** ” resurfaced as a recurring need. @Falco shared an early implementation draft and noted it’s coming up across customers ([read more](https://meta.discourse.org/t/-/264619/9?silent=true)), while broader gamification discussion continues to explore how leaderboards should scope categories ([read more](https://meta.discourse.org/t/-/225916/451?silent=true), [read more](https://meta.discourse.org/t/-/225916/452?silent=true)).

- #ai #ai-bot: a request to make AI Personas respond only to **@mentions (not replies)** sparked a product-level debate. @sam worried about “option paralysis” and suggested mention-only might just be the better default; @Falco argued this is best handled via upcoming workflow tools rather than a niche setting ([read more](https://meta.discourse.org/t/-/399221/2?silent=true), [read more](https://meta.discourse.org/t/-/399221/3?silent=true)).

### #Support

- Troubleshooting **AI bot model configuration** : a support thread walked through proper Gemini model URLs (including differences between text vs image-generation models), with @Lilly providing concrete examples and screenshots for correct setup ([read more](https://meta.discourse.org/t/-/399660/6?silent=true)).

- The **Presence plugin “infinite is replying…”** indicator was resolved with a simple toggle reset: turning “Presence enabled” off and back on immediately cleared the stuck state ([read more](https://meta.discourse.org/t/-/399655/4?silent=true)).

- A search report described **title-word searches returning no results** (e.g. “Swimming” not found by “swim/swimming”) in a multilingual site, alongside 500s when AI semantic search embeddings are enabled—an issue likely to matter to many multilingual communities ([read more](https://meta.discourse.org/t/-/399693/1?silent=true)).

* * *

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

- @Falco shipped and supported the big headline: **full app mode for embeds** , including rationale for simplifying the embed UI and notes on login flow ([read more](https://meta.discourse.org/t/-/399743/1?silent=true), [read more](https://meta.discourse.org/t/-/399743/5?silent=true), [read more](https://meta.discourse.org/t/-/399743/7?silent=true)). He also back-linked the release into older embedding/dev requests to close the loop ([read more](https://meta.discourse.org/t/-/49811/10?silent=true), [read more](https://meta.discourse.org/t/-/360386/5?silent=true), [read more](https://meta.discourse.org/t/-/81473/9?silent=true)).

- @davidb identified the cause of Meta’s **mobile viewport breakage** as a recent change in `discourse-tag-icons`, and initiated a temporary revert while investigating further ([read more](https://meta.discourse.org/t/-/399691/5?silent=true)).

- @zogstrip drove multiple fixes and follow-ups: he confirmed a reactions/archiving logic bug and linked an in-flight fix ([read more](https://meta.discourse.org/t/-/399681/5?silent=true)), suggested a commit as a possible fix for a **Topic Voting** breakage ([read more](https://meta.discourse.org/t/-/399649/16?silent=true)), noted new support for disabling/hiding vote limits ([read more](https://meta.discourse.org/t/-/308402/44?silent=true)), and queued a fix for the **bulk group-invite notification** regression ([read more](https://meta.discourse.org/t/-/397334/2?silent=true)).

- @nat posted progress on **translated tags support** for the tag icons component, pointing to an active PR and near-term merge plan ([read more](https://meta.discourse.org/t/-/399594/3?silent=true)).

- @awesomerobot proposed a user-friendly improvement for rejected posts by creating an editable draft from rejected content ([read more](https://meta.discourse.org/t/-/373992/19?silent=true)), and clarified the layout/DOM constraints behind a **Horizon sticky header** request ([read more](https://meta.discourse.org/t/-/387267/11?silent=true)).

- @mcwumbly accepted edits for the **collaborative gardening hub** index maintenance effort ([read more](https://meta.discourse.org/t/-/397606/67?silent=true)) and later discussed a small workflow oddity around tagging fixed issues and auto-open/close behavior ([read more](https://meta.discourse.org/t/-/397606/69?silent=true)). He also left praise for the multilingual story in “Building for Every Language” ([read more](https://meta.discourse.org/t/-/399661/2?silent=true)).

- @dax confirmed the **mobile viewport regression** affecting Meta and flagged it for investigation ([read more](https://meta.discourse.org/t/-/399691/2?silent=true)).

- @david followed up on a **CORS / CDN-related outage pattern** after upgrades, explaining asset hosting differences (CDN vs S3) and pointing to a core fix requiring a full rebuild to apply NGINX config changes ([read more](https://meta.discourse.org/t/-/399466/12?silent=true), [read more](https://meta.discourse.org/t/-/399466/13?silent=true)).

- @lindsey provided a project-status check-in, noting translation work for blog styling is pending a Crowdin component step once someone returns from leave ([read more](https://meta.discourse.org/t/-/398565/10?silent=true)).

- @martin confirmed plans to extend **Upcoming Changes** with more sorting options, including status and “first appeared on your site” ([read more](https://meta.discourse.org/t/-/392894/20?silent=true)).

* * *

If you’re wondering why everyone looked mildly panicked yesterday, it might have been that fullscreen “this site has been seized” splash screen doing its job a little _too_ well.

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

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