# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
**In the last 24 hours (2026-03-07 → 2026-03-08)**, Meta saw **36 new posts** across **5 new topics** , with discussion spread across support troubleshooting, theming experiments, and self-host/dev setup snags (e.g. [read more](https://meta.discourse.org/t/-/397891/1?silent=true), [read more](https://meta.discourse.org/t/-/397885/4?silent=true), [read more](https://meta.discourse.org/t/-/282227/18?silent=true)).
**Top posters & most-liked (last 24h)**
| User | New posts | Likes received | Where they were active |
| --- | --- | --- | --- |
| @NateDhaliwal | 4 | 4 | Mobile debugging questions [read more](https://meta.discourse.org/t/-/397891/3?silent=true) and onebox/composer customization ideas [read more](https://meta.discourse.org/t/-/391504/19?silent=true) |
| @stephtara | 3 | 2 | Follow-ups on the tag styling tool [read more](https://meta.discourse.org/t/-/397885/5?silent=true) and per-user embed customization [read more](https://meta.discourse.org/t/-/391504/22?silent=true) |
| @Lilly | 2 | 5 | Clarifying legacy mobile mode deprecation [read more](https://meta.discourse.org/t/-/397891/5?silent=true) and safe-mode troubleshooting + deprecation notes [read more](https://meta.discourse.org/t/-/397644/7?silent=true) |
| @jdc20181 | 2 | 4 | Progress updates on a style builder + color picker direction [read more](https://meta.discourse.org/t/-/397885/8?silent=true) |
| @darkpixlz | 2 | 4 | Noting `?mobile_view=1` removal context [read more](https://meta.discourse.org/t/-/397891/4?silent=true) and theme maintenance for the upcoming default theme [read more](https://meta.discourse.org/t/-/357665/41?silent=true) |
| @gilles | 2 | 2 | Windows dev setup Ruby mismatch resolution [read more](https://meta.discourse.org/t/-/282227/21?silent=true) |
| @Falco (**[@team](https://meta.discourse.org/groups/team?silent=true)**) | 1 | 4 | Pointing to native HTML color input + Discourse wrapper component [read more](https://meta.discourse.org/t/-/397885/6?silent=true) |
| @sam (**[@team](https://meta.discourse.org/groups/team?silent=true)**) | 1 | 2 | Brainstorming “agentic” support workflows in Discourse AI [read more](https://meta.discourse.org/t/-/397742/23?silent=true) |
| @ToddZ | 1 | 1 | Guidance on mobile/desktop layout overrides shifting over time [read more](https://meta.discourse.org/t/-/397891/2?silent=true) |
| @merefield | 1 | 1 | Explaining why Ruby `3.4.0.dev` can fail Gemfile constraints [read more](https://meta.discourse.org/t/-/282227/20?silent=true) |
_Also bubbling up on the sidelines:_ a multilingual blog thread got fresh replies [read more](https://meta.discourse.org/t/-/397784/7?silent=true), and the long-running events plugin topic flagged a broken external support link [read more](https://meta.discourse.org/t/-/69776/890?silent=true).
* * *
## Interesting Topics
### #customization:theme-component
- @jdc20181’s **Tag Style Tool** thread continued evolving into a mini “style builder” discussion, including Font Awesome icon support, UX requests for linking resources in settings, and experiments toward a color-picker UI [read more](https://meta.discourse.org/t/-/397885/4?silent=true) (plus a progress demo [read more](https://meta.discourse.org/t/-/397885/8?silent=true)).
### #Support
- A “why can’t I see the mobile UI on desktop browsers?” investigation explored the fading legacy of `?mobile_view=1` [read more](https://meta.discourse.org/t/-/397891/2?silent=true), with pointers that it’s deprecated/legacy behavior [read more](https://meta.discourse.org/t/-/397891/5?silent=true) and may have been removed recently [read more](https://meta.discourse.org/t/-/397463/10?silent=true); the deeper direction is viewport/capability-based styling [read more](https://meta.discourse.org/t/-/367810/1?silent=true).
- A self-host admin reported **Discourse ID signups silently failing** (button does nothing) and noted anonymous-only console 404s like `vendor.map`/`start-discourse.map`, seeking configuration/debug guidance [read more](https://meta.discourse.org/t/-/397895/1?silent=true) (#discourse-id).
- A new SEO/localization report suggested **translated `?tl=` pages aren’t being indexed** because the canonical tag points to the non-translated URL (Google treating localized pages as “alternate with proper canonical”) [read more](https://meta.discourse.org/t/-/397925/1?silent=true) (#content-localization).
- A self-hoster described **AI Search resource impact** and others asked for “hardware profile” details before enabling it themselves [read more](https://meta.discourse.org/t/-/397869/2?silent=true) (#ai #ai-search).
- A theming question asked how to create a **transparent “Discord-like” look** , ideally _per-user_ or for a small group—highlighting the common constraint that theme components typically apply instance-wide [read more](https://meta.discourse.org/t/-/397921/1?silent=true).
- An iPadOS Safari oddity where the **composer “flies off screen”** when focusing different fields was reported—and then (mysteriously) stopped reproducing the next day, leading the OP to mark it resolved/withdrawn [read more](https://meta.discourse.org/t/-/397892/1?silent=true) (resolution update [read more](https://meta.discourse.org/t/-/397892/3?silent=true)) (#composer #tablet).
- In a solved #onebox thread, @NateDhaliwal suggested a **composer button that inserts an iframe** (theme-component feasible), and the discussion moved toward _per-user personalization_ via custom user fields and access patterns [read more](https://meta.discourse.org/t/-/391504/19?silent=true) (and follow-up on user-specific values [read more](https://meta.discourse.org/t/-/391504/21?silent=true)).
- A “non-admin users can’t load pages” support thread got a familiar first-line check: “does it work in [safe mode](https://meta.discourse.org/t/53504?silent=true)?”, plus a reminder that the _advanced search banner_ component is deprecated and its functionality moved into core/banner patterns [read more](https://meta.discourse.org/t/-/397644/7?silent=true) ([safe mode](https://meta.discourse.org/t/53504?silent=true) reference [read more](https://meta.discourse.org/t/-/53504/1?silent=true), deprecation notice [read more](https://meta.discourse.org/t/-/122939/1?silent=true), and the current banner guide [read more](https://meta.discourse.org/t/-/153718/1?silent=true)).
### #Self-hosting
- The Windows 11 dev environment guide saw a fresh round of **Ruby version mismatch** troubleshooting (`3.4.0.dev` vs Gemfile `~> 3.4`), with links to common “build fails / update fails” cousins and a confirmed fix by installing Ruby `3.4.8` [read more](https://meta.discourse.org/t/-/282227/18?silent=true) (related: build mismatch thread [read more](https://meta.discourse.org/t/-/396317/1?silent=true), crash-during-update [read more](https://meta.discourse.org/t/-/397520/1?silent=true), and the “big scary red button” update thread [read more](https://meta.discourse.org/t/-/396452/3?silent=true)) (#dev-install).
### #contribute:site-feedback
- In the ongoing “improving support categories” conversation, @sam pointed out Discourse AI already supports sophisticated agents and asked how to make advanced workflows easier to configure, tying into a parallel “split automations into triggers/actions” feature direction [read more](https://meta.discourse.org/t/-/397742/23?silent=true) (feature request context [read more](https://meta.discourse.org/t/-/384262/1?silent=true)).
### #customization:theme
- **Pyx’s Modern Theme** shipped an update aimed at compatibility with the upcoming default theme, including restoring a cursor-active behavior (under a new name) and tweaking button borders with an option to disable if it has side effects [read more](https://meta.discourse.org/t/-/357665/41?silent=true).
### #Site-Management
- A question on **auto-bumping configuration** asked whether “1” is effectively the minimum daily bump, after `.25` (every 4 days) didn’t persist—raising practical concerns about overwhelming the feed in “resources” categories [read more](https://meta.discourse.org/t/-/262158/28?silent=true).
### #Sysadmins
- In the NodeBB → Discourse migration guide, a contributor shared a tweak to `mongo.rb` to ensure **posts within a topic sort chronologically** via `sort(score: 1)`, improving import ordering [read more](https://meta.discourse.org/t/-/126553/23?silent=true) (#how-to).
### #contribute:feature
- A “Math should be quotable” proposal suggested a theme-component approach to improve quoting of MathJax/KaTeX-heavy posts by replacing math wrappers with original TeX source before quote-to-Markdown conversion [read more](https://meta.discourse.org/t/-/148342/6?silent=true) (#pr-welcome).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Falco jumped into the **Tag Style Tool** discussion to note there’s a native HTML color picker input (``) and that Discourse wraps it for easier usage—useful for turning a “maybe-plugin” idea into a realistic theme-component enhancement [read more](https://meta.discourse.org/t/-/397885/6?silent=true).
- @sam weighed in on **improving support workflows** , pointing out that Discourse AI already supports “extremely sophisticated agents,” and raised the key product question: how to expose these capabilities so admins can configure advanced workflows without heavy bespoke work [read more](https://meta.discourse.org/t/-/397742/23?silent=true).
* * *
If yesterday was any indication, today’s Meta motto is: _may your mobile views be viewport-driven and your color pickers be delightfully native_ ([read more](https://meta.discourse.org/t/-/367810/1?silent=true), [read more](https://meta.discourse.org/t/-/397885/6?silent=true)).
---
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 77**
- **New topics (last 24h): 12**
**Top posters (with likes received in the last 24h)**
| User | Posts | Likes |
| --- | --- | --- |
| @sam | 3 | 12 |
| @ToddZ | 7 | 10 |
| @jdc20181 | 5 | 6 |
| @HAWK | 3 | 5 |
| @gilles | 5 | 4 |
| @merefield | 3 | 4 |
| @Falco | 6 | 4 |
| @NateDhaliwal | 5 | 4 |
| @nat | 2 | 3 |
| @mentalstring | 3 | 3 |
* * *
## Interesting Topics
### #Announcements
- @sam announced **service tiers for OpenAI/Azure providers** (including guidance on the _responses_ endpoint for caching/costs) in [Service tiers on Open AI providers](https://meta.discourse.org/t/-/397937/1?silent=true), with a pointer back to the [LLM settings page](https://meta.discourse.org/t/-/319903/1?silent=true) for configuration.
- In the long-running “bundled plugins” discussion, @mentalstring reported a **surprising rebuild failure + missing cakeday UI** on an older stable install in [Bundling more popular plugins with Discourse core](https://meta.discourse.org/t/-/373574/164?silent=true), and @david explained the warning behavior + offered a cleanup hook workaround ([read more](https://meta.discourse.org/t/-/373574/168?silent=true)).
### #Site feedback
- A docs-audit thread kicked off around **FAQ vs Guidelines vs About links** , clarifying differences between hosted vs self-hosted behavior and calling out the hidden setting `rename_faq_to_guidelines` in [Review and update topics related to FAQ & Guidelines links](https://meta.discourse.org/t/-/397938/6?silent=true), referencing the earlier announcement [Renaming FAQ to Guidelines](https://meta.discourse.org/t/-/395099/1?silent=true) and the how-to [Using Hidden Site Settings](https://meta.discourse.org/t/-/308773/1?silent=true).
### #Support
- Dashboard UX feedback: @merefield asked whether the **Site Traffic graph should rescale its Y-axis when toggling series** in [Site Traffic graph: should reselection of included series re-scale the Y axis?](https://meta.discourse.org/t/-/397956/1?silent=true), and @nat confirmed changes are underway ([read more](https://meta.discourse.org/t/-/397956/4?silent=true)).
- “Can Discourse force a one-way TOS acceptance?” was answered with a **custom user field pattern that blocks saving until checked** (marked solved) in [Require TOS acceptance](https://meta.discourse.org/t/-/397955/2?silent=true).
- Two separate #discourse-id support threads saw admins run into workflow snags: one about **duplicate redirect URIs after reinstall** in [Can’t set up Discourse ID: Application with this redirect URI already exists](https://meta.discourse.org/t/-/397991/1?silent=true) and another where **signups appear to do nothing (404/console/log issues)** in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/1?silent=true).
- A big ops/perf report: enabling #ai #ai-search caused heavy load while backfilling embeddings for a large site (millions of posts) in [Enabling AI search crippled my server](https://meta.discourse.org/t/-/397869/5?silent=true), after earlier requests for server/DB/provider specifics ([read more](https://meta.discourse.org/t/-/397869/3?silent=true)).
- Mobile UX regression report: the **text-selection popup (Quote / Copy Quote) fails on some mobile browsers**, reproducible even in [safe mode](https://meta.discourse.org/t/53504?silent=true), in [The three buttons that pop up after selecting text on a mobile browser do not work when clicked](https://meta.discourse.org/t/-/397943/1?silent=true).
- A theme/CSS question explored options for making a theme “transparent” and selectively available, in [How can I make a theme that is transparent?](https://meta.discourse.org/t/-/397921/2?silent=true), with related references to [Show/hide themes for specific groups?](https://meta.discourse.org/t/-/115459/1?silent=true) and the component idea [CSS classes for current user’s groups](https://meta.discourse.org/t/-/226068/1?silent=true).
- A tricky error log around **editing wiki posts for some users** (with `create_errors_json called with unrecognized type`) landed in [Error when editing a Wiki Topic](https://meta.discourse.org/t/-/397964/1?silent=true).
- Privacy/GDPR concerns surfaced again around oneboxes: @max.l questioned whether **onebox preview images/favicons are fetched remotely (tracking risk)** in [Cache onebox images and/or serve them from the main domain](https://meta.discourse.org/t/-/325769/20?silent=true), and @Falco walked through live testing and clarified behavior differences between composer preview and baked posts ([read more](https://meta.discourse.org/t/-/325769/21?silent=true)).
### #bug
- Tag permissions: @jdc20181 reported **restricted tag groups still visible on `/tags`** in [Restricted visibility tag groups are still visible on /tags page](https://meta.discourse.org/t/-/397930/1?silent=true), referencing an older “we fixed this” note in [Tags that are supposed to be only visible to staff are shown on /tags for everyone](https://meta.discourse.org/t/-/116165/8?silent=true).
- @nat dropped a confirmed fix for a tags UI issue affecting certain slug-generation settings in [在 Slug 生成方法为 none 情况下，创建新标签后无法正常显示新版编辑标签功能](https://meta.discourse.org/t/-/397789/10?silent=true) (with the upstream PR linked in-post).
### #customization:theme component
- A fast-moving iterative debug session continued for the **Tag Style Tool** , including a disappearing builder button and icon rendering quirks, in [Tag Style Tool](https://meta.discourse.org/t/-/397885/11?silent=true).
### #Dev
- Plugin feasibility (FR): @gilles sketched a workflow for a **BoardGameGeek API-powered composer toolbar button** , and the thread weighed theme component vs plugin tradeoffs (API key exposure) in [Besoin d’avis pour essai de programmation de plugin](https://meta.discourse.org/t/-/397948/1?silent=true).
### #contribute:feature
- Automation design discussion: @sam revisited the idea of **splitting automations into trigger → filter → action pipelines** in [Feature Request - Split Automations into Triggers and Actions](https://meta.discourse.org/t/-/384262/2?silent=true).
- SSO privacy: a report noted **emails exposed in [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) provider redirect URLs** (base64 payload, not encrypted), and the proposed path forward was a backward-compatible site setting (#pr-welcome) in [Security/Privacy concern: Email exposed in DiscourseConnect Provider redirect URL](https://meta.discourse.org/t/-/397980/1?silent=true) with reference to [Use Discourse as an identity provider (SSO DiscourseConnect)](https://meta.discourse.org/t/-/32974/1?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @sam led on AI + automation improvements: rolling out provider **service tiers** in [Service tiers on Open AI providers](https://meta.discourse.org/t/-/397937/1?silent=true) (tied back to the [LLM settings page](https://meta.discourse.org/t/-/319903/1?silent=true)), and engaging on the **automation pipeline** proposal in [Split Automations into Triggers and Actions](https://meta.discourse.org/t/-/384262/2?silent=true). He also asked for deeper diagnostics on large-scale embedding backfills in [Enabling AI search crippled my server](https://meta.discourse.org/t/-/397869/3?silent=true).
- @HAWK helped untangle confusion around **FAQ vs Guidelines links** , steering a docs cleanup conversation in [Review and update topics related to FAQ & Guidelines links](https://meta.discourse.org/t/-/397938/1?silent=true) and looping in @Danielle for coordination ([read more](https://meta.discourse.org/t/-/397938/5?silent=true)).
- @Danielle confirmed the team will sync on the **FAQ/Guidelines documentation audit** and report back in [Review and update topics related to FAQ & Guidelines links](https://meta.discourse.org/t/-/397938/7?silent=true).
- @david clarified how “bundled plugin” rebuild hints can be misleading on older installs, and provided an actionable hook snippet to clean up plugin directories in [Bundling more popular plugins with Discourse core](https://meta.discourse.org/t/-/373574/166?silent=true) ([read more](https://meta.discourse.org/t/-/373574/168?silent=true)).
- @nat acknowledged dashboard chart UX feedback and hinted at incoming improvements in [Site Traffic graph rescaling](https://meta.discourse.org/t/-/397956/4?silent=true), and also confirmed a fix landed for a tags-related bug in [Slug generation `none` + new tag editor issue](https://meta.discourse.org/t/-/397789/10?silent=true).
- @tshenry closed the loop on a tags UX paper-cut (“missing tag group” error messaging) in [Missing tag group error message](https://meta.discourse.org/t/-/397853/4?silent=true).
- @awesomerobot responded on two fronts: troubleshooting tag visibility in [Restricted visibility tag groups visible on /tags](https://meta.discourse.org/t/-/397930/2?silent=true), and offering a practical policy+automation approach for “must read/accept guidelines + intro” gating in [Plugin or other option to require a post and a like?](https://meta.discourse.org/t/-/397978/2?silent=true), with pointers to [Discourse Policy](https://meta.discourse.org/t/-/88557/1?silent=true), [Discourse Automation](https://meta.discourse.org/t/-/195773/1?silent=true), and [Creating triggered custom badge queries](https://meta.discourse.org/t/-/19336/1?silent=true).
- @pmusaraj handled #discourse-id support: requesting diagnostic logs in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/2?silent=true), and offering to clear credentials as a temporary workaround in [Can’t set up Discourse ID: redirect URI already exists](https://meta.discourse.org/t/-/397991/2?silent=true) (similar guidance also appeared in the older solved thread [Can’t setup Discourse ID: redirect URI already exists](https://meta.discourse.org/t/-/396136/14?silent=true)).
- @Falco weighed in across SEO, SSO, ops, and privacy threads: clarifying canonical expectations in the solved topic [Translated pages (?tl=) not indexed…](https://meta.discourse.org/t/-/397925/2?silent=true), probing the threat model in the #pr-welcome SSO email discussion [Email exposed in DiscourseConnect Provider redirect URL](https://meta.discourse.org/t/-/397980/2?silent=true), asking for infra details on embeddings load in [Enabling AI search crippled my server](https://meta.discourse.org/t/-/397869/4?silent=true), and live-testing onebox image caching behavior in [Cache onebox images…](https://meta.discourse.org/t/-/325769/21?silent=true).
- @supermathie helped narrow down a mobile-browser-specific issue (Mi Browser) and suggested escalating to the browser vendor in [Mobile text-selection quote/copy buttons not working](https://meta.discourse.org/t/-/397943/4?silent=true).
> If yesterday taught us anything, it’s this: keep your **Guidelines** renamed, your **oneboxes** cached, and never let an outdated build steal your **cake day** frosting.
---
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **Total activity (last 24h):** **51** new posts across **7** new topics, including fresh threads on #chat, self-hosting, and plugins like a new points mall ([read more](https://meta.discourse.org/t/-/398080/1?silent=true)).
- **New topics opened (7):**
- **Top users by posts & likes (with recent highlights):**
| User | Posts | Likes | Recent highlight |
| --- | --- | --- | --- |
| **@Falco** | 3 | 9 | Shared a [Data Explorer](https://meta.discourse.org/t/32566?silent=true) SQL to inspect AI spam logs ([read more](https://meta.discourse.org/t/-/343541/33?silent=true)) |
| **@ToddZ** | 5 | 5 | Pointed self-hosters to the canonical path-prefix guide for WP sub-path deployments ([read more](https://meta.discourse.org/t/-/398033/2?silent=true)) |
| **@Huskijore** | 1 | 4 | Asked about a direct-to-chat shortcut for communities migrating from Discord ([read more](https://meta.discourse.org/t/-/398082/1?silent=true)) |
| **@jdc20181** | 1 | 3 | Confirmed restricted tag groups behaved after a rebuild (#tags) ([read more](https://meta.discourse.org/t/-/397930/4?silent=true)) |
| **@Lilly** | 2 | 3 | Clarified chat access rules for admins/mods and suggested checking upload concurrency settings ([read more](https://meta.discourse.org/t/-/398048/2?silent=true)) |
| **@Monikas** | 3 | 3 | Published an early WIP “Points Mall” plugin with check-ins, shop, and ledger ([read more](https://meta.discourse.org/t/-/398080/1?silent=true)) |
| **@Andrew_Rowe** | 2 | 2 | Recalled prior discussion around opening Chat directly and suggested searching meta for similar requests ([read more](https://meta.discourse.org/t/-/398082/2?silent=true)) |
| **@noahl** | 1 | 2 | Expanded on more flexible conditions/logic for Discourse Automation pipelines (#automation) ([read more](https://meta.discourse.org/t/-/384262/5?silent=true)) |
| **@lucy.sierracircuits** | 2 | 2 | Reported multi-image upload limits persisting despite settings adjustments ([read more](https://meta.discourse.org/t/-/398088/1?silent=true)) |
| **@asc** | 4 | 2 | Continued debugging sign-up failures and console 404s for source maps (#discourse-id) ([read more](https://meta.discourse.org/t/-/397895/7?silent=true)) |
## Interesting Topics
### #Support
- @eisammy asked how to **disable Chat for moderators** (keeping it admin-only), and @Lilly confirmed moderators can’t be excluded when chat is enabled—while @NateDhaliwal traced the behavior to core chat settings, likely requiring a plugin to override (#chat) ([read more](https://meta.discourse.org/t/-/398048/1?silent=true))
- @lucy.sierracircuits reported that members **can’t upload more than one image** per post; @Lilly suggested also checking the `simultaneous uploads` site setting as a likely culprit ([read more](https://meta.discourse.org/t/-/398088/2?silent=true))
- @pHneutre noticed the **Upcoming Events sidebar icon** showing as a generic link instead of a calendar; @Falco advised it’s fixed in current Discourse and recommended updating (#calendar-and-event) ([read more](https://meta.discourse.org/t/-/398052/2?silent=true))
- In a long-running moderation/admin thread, @Lydia2 hit a confusing state where a user appeared silenced **without an “unsilence” button** ; @Bas suggested clicking “silence” again to try resetting the state back to normal ([read more](https://meta.discourse.org/t/-/105988/11?silent=true))
- A wiki-editing problem got a quick resolution: @isaac pointed to a fix for an **error when editing a Wiki Topic** , then followed up as additional 500s were reported and the team started investigating further ([read more](https://meta.discourse.org/t/-/397964/2?silent=true))
### #Self-hosting
- @Huskijore (moving a community off Discord) asked whether Discourse can provide a **home-screen shortcut that lands directly in Chat** , or even a “latest-like” view that includes selected chats; @Andrew_Rowe recalled similar prior attempts but no clean solution yet (#chat) ([read more](https://meta.discourse.org/t/-/398082/1?silent=true))
- For SEO-minded WordPress operators, @hritik asked how to deploy Discourse on a **sub-path** rather than a subdomain; @ToddZ clarified the WP plugin is for integration and linked the canonical _path prefix/subfolder_ setup guide ([read more](https://meta.discourse.org/t/-/398033/2?silent=true), plus background: [read more](https://meta.discourse.org/t/-/30507/1?silent=true))
- In troubleshooting a broken onboarding flow, @asc and others continued digging into **new users failing to sign up** alongside console 404s (source map requests) and resource exhaustion errors, narrowing down what an anonymous user experiences (#discourse-id) ([read more](https://meta.discourse.org/t/-/397895/7?silent=true))
- A Cloudflare hardening thread got an update as @haydenjames shared real-world rulesets and planned to incorporate Discourse’s recommended WAF exclusions, especially around post creation and [Data Explorer](https://meta.discourse.org/t/32566?silent=true) admin queries (#cloudflare) ([read more](https://meta.discourse.org/t/-/293405/26?silent=true))
### #Site Management
- In the Discourse AI spam tooling thread, @LotusJeff asked for **lower-level reporting** behind the AI spam summary box; @Falco replied with a direct SQL query to pull records from `ai_spam_logs`, pointing to #DataExplorer as the practical path to “show me the details” (#ai #spam #moderation) ([read more](https://meta.discourse.org/t/-/343541/33?silent=true), [Data Explorer](https://meta.discourse.org/t/32566?silent=true) reference: [read more](https://meta.discourse.org/t/-/32566/1?silent=true))
### #contribute:feature
- Naming polish landed: in the “AI Persona → AI Agent” discussion, @Falco confirmed @sam shipped the rename work, linking the implementation PR and closing the loop on the terminology direction (#ai) ([read more](https://meta.discourse.org/t/-/368198/13?silent=true))
- In the automation redesign request (_split automations into triggers and actions_), participants pushed for more expressive workflows—especially **delays and richer conditional logic** —with @noahl exploring how conditions could be composed with AND/OR and values pulled from `trigger_context` (#automation) ([read more](https://meta.discourse.org/t/-/384262/5?silent=true))
### #customization:plugin
- @Monikas announced a new (very early) **Discourse Points Mall** plugin—daily check-ins, a shop, orders, makeup cards, and a points ledger—while explicitly flagging UI bugs and advising admins to wait before installing in production ([read more](https://meta.discourse.org/t/-/398080/1?silent=true))
### #ux
- A Foundation theme UI report (in Chinese) flagged a **search button wrapping** issue; @awesomerobot said the fix is to prevent text wrapping in buttons and noted it should be resolved after updating Discourse (#foundation-theme) ([read more](https://meta.discourse.org/t/-/398038/2?silent=true))
- On site chrome and default pages, the “FAQ/Guidelines and About pages” discussion continued: @ToddZ and @Andrew_Rowe outlined the practical value of the built-ins (default sidebar links, boilerplate, and discoverability/SEO concerns even if you “hide” them) ([read more](https://meta.discourse.org/t/-/397882/4?silent=true))
### #contribute:translations
- In a thread about **poor French translations** in automation UI, @gerhard talked through the dream of _in-context translations inside Discourse_, noting Crowdin’s constraints around single-project in-context mode and hinting at experimentation in coming months (#automation) ([read more](https://meta.discourse.org/t/-/397946/4?silent=true))
### #Developer Guides
- A theme-dev thread got modernized guidance: @MarkDoerr explained that legacy widget code is outdated due to the post stream changes, and suggested using a **Glimmer component** plus `api.renderAfterWrapperOutlet` to place user custom fields in the post header—linking back to the post-stream migration guidance ([read more](https://meta.discourse.org/t/-/106928/7?silent=true), migration context: [read more](https://meta.discourse.org/t/-/372063/1?silent=true))
### #Site feedback
- Meta’s “collaborative content gardening hub” experiment kept chugging along: @ToddZ proposed pruning obsolete “About page customization” topics now that the newer About-page docs and features exist, and linked several candidates for cleanup alongside the newer canonical references ([read more](https://meta.discourse.org/t/-/397606/48?silent=true), related hub: [read more](https://meta.discourse.org/t/-/397938/2?silent=true), About page announcement: [read more](https://meta.discourse.org/t/-/324212/1?silent=true), About page guide: [read more](https://meta.discourse.org/t/-/332161/1?silent=true), candidates: [read more](https://meta.discourse.org/t/-/283018/1?silent=true), [read more](https://meta.discourse.org/t/-/83818/1?silent=true), [read more](https://meta.discourse.org/t/-/58853/1?silent=true))
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@Falco** pushed forward both product clarity and admin pragmatics: confirmed the **AI Persona → AI Agent** rename landed ([read more](https://meta.discourse.org/t/-/368198/13?silent=true)), provided a **[Data Explorer](https://meta.discourse.org/t/32566?silent=true) SQL** to inspect AI spam log details ([read more](https://meta.discourse.org/t/-/343541/33?silent=true)), and noted an **Upcoming Events icon** issue is already fixed upstream (encouraging an update) ([read more](https://meta.discourse.org/t/-/398052/2?silent=true)).
- **@Bas** helped troubleshoot an odd moderation UI state by suggesting a “toggle it to reset it” approach for a missing unsilence control ([read more](https://meta.discourse.org/t/-/105988/11?silent=true)).
- **@isaac** linked a confirmed fix for a **wiki topic editing error** , then acknowledged follow-up 500 errors and indicated the team is investigating ([read more](https://meta.discourse.org/t/-/397964/2?silent=true), follow-up report: [read more](https://meta.discourse.org/t/-/397964/5?silent=true)).
- **@awesomerobot** acknowledged a #foundation-theme search UI bug and pointed to a fix that prevents button text wrapping after updating Discourse ([read more](https://meta.discourse.org/t/-/398038/2?silent=true)).
- **@gerhard** shared direction on improving translation workflows, including the idea of **in-context translations** inside Discourse and the constraints with Crowdin’s current project model ([read more](https://meta.discourse.org/t/-/397946/4?silent=true)).
- **@tgxworld** confirmed a fix is queued for **object-type theme settings** , linking the PR that will address it ([read more](https://meta.discourse.org/t/-/305009/33?silent=true)).
- **@MarkDoerr** provided updated theme-developer guidance for rendering custom fields near post headers using **Glimmer components** , referencing the broader post-stream migration work ([read more](https://meta.discourse.org/t/-/106928/7?silent=true), background: [read more](https://meta.discourse.org/t/-/372063/1?silent=true)).
> Between spam-log SQL, chat UX wishes, and Glimmer-powered theme fixes, meta spent the day proving that “it’s just one small tweak” is rarely just one small tweak ([read more](https://meta.discourse.org/t/-/343541/33?silent=true)).
---
# Today on [meta.discourse.org](http://meta.discourse.org)…
_Daily recap for the last 24 hours (2026-03-10 → 2026-03-11)._
* * *
## Key Stats
- **New posts:** 95
- **New topics:** 20
**Top users (posts / likes in the last 24h):**
| User | Posts | Likes |
| --- | --- | --- |
| **@ToddZ** | 7 | 7 |
| **@DavidO** | 1 | 7 |
| **@darkpixlz** | 5 | 5 |
| **@Canapin** | 3 | 5 |
| **@awesomerobot** _(team)_ | 2 | 5 |
| **@merefield** | 1 | 5 |
| **@Falco** _(team)_ | 6 | 4 |
| **@RGJ** | 2 | 4 |
| **@martin** _(team)_ | 1 | 4 |
| **@Lilly** | 5 | 3 |
* * *
## Interesting Topics
### #Support
- **Solved plugin confusion + post-merge “FAILED” when selecting a solution:** @Silas-Inservio-Pax hit an error after merging topics and then trying to mark a specific reply as the solution, with @Lilly and @darkpixlz guiding them toward browser console output and checking `/logs` (which required an admin). [read more](https://meta.discourse.org/t/-/398163/1?silent=true)
- **[Data Explorer](https://meta.discourse.org/t/32566?silent=true) API change: `limit=ALL` stopped working (by design):** @pfaffman tracked a breakage down to `limit=ALL`, with @Falco pointing to a change intended to remove the “no limit” path and recommending pagination (and clarifying the new cap). [read more](https://meta.discourse.org/t/-/398172/1?silent=true) (see also: the “reverse engineer” approach mentioned in-context [read more](https://meta.discourse.org/t/-/20576/1?silent=true))
- **After upgrading, “official” theme components fail… but the culprit is a plugin:** @Stephane_Roy reported multiple “official” components breaking post-upgrade; @awesomerobot found a console error pointing at the #broken Journal plugin and suggested confirming via [safe mode](https://meta.discourse.org/t/53504?silent=true) with plugins disabled. [read more](https://meta.discourse.org/t/-/398143/1?silent=true) (related: Journal plugin reference [read more](https://meta.discourse.org/t/-/317785/1?silent=true))
- **Adding intro text to `/g` (Groups page) via a tiny theme component:** @pHneutre wanted a paragraph above the group list; @ToddZ outlined a simple Theme Component using **After Header** + scoped CSS to only show on `.groups-page`. [read more](https://meta.discourse.org/t/-/398174/1?silent=true) (background threads: custom HTML on groups page [read more](https://meta.discourse.org/t/-/140787/1?silent=true), Versatile Banner [read more](https://meta.discourse.org/t/-/109133/1?silent=true))
- **Moderator permissions: can mods delete users, and how do you prevent it?** @Ethsim2 confirmed moderators can delete users by default, then documented a practical workaround using **category moderators** + `enable category group moderation` to avoid global powers. [read more](https://meta.discourse.org/t/-/398136/1?silent=true) (reference table: trust-level permissions [read more](https://meta.discourse.org/t/-/224824/1?silent=true); related staff logging notes [read more](https://meta.discourse.org/t/-/58022/1?silent=true))
- **User post deletion fails with `InvalidForeignKey` (reviewable notes):** @Canapin found deletion failing due to `reviewable_notes` referencing `reviewables`; @darkpixlz confirmed it looks like a bug and linked a current workaround: remove the related note/comment first. [read more](https://meta.discourse.org/t/-/398175/1?silent=true) (workaround context: [read more](https://meta.discourse.org/t/-/397700/3?silent=true))
- **Onebox/OpenGraph failures traced to server certificate chain:** @wlandgraf reported Onebox previews failing on their own instance despite working on Meta, then determined the Discourse server couldn’t validate the site’s newer cert chain. [read more](https://meta.discourse.org/t/-/398149/1?silent=true) (handy troubleshooting guide referenced: [read more](https://meta.discourse.org/t/-/239715/1?silent=true))
### #bug
- **Localized tags aren’t slugified (breaking body classes + tag display):** @RGJ demonstrated how localized tag names containing whitespace/quotes leak into CSS classes and UI, with @sam looping in @nat to investigate. [read more](https://meta.discourse.org/t/-/398105/1?silent=true) (related mention: slug behavior discussion [read more](https://meta.discourse.org/t/-/397789/10?silent=true))
- **Shared-edit wiki history “Edit post” opens the wrong editor and errors on save:** @hannahbit reported that editing from post history can open the normal editor (not the collaborative one), then saving triggers an error (including a 422 involving tags), temporarily blanking the post until refresh. [read more](https://meta.discourse.org/t/-/398145/1?silent=true)
- **Multiple form templates per category don’t persist after refresh:** @donaldsoncd showed that selecting two templates initially works, but after refresh only one remains as the default—raising questions about limitation vs bug in #form-templates. [read more](https://meta.discourse.org/t/-/398176/1?silent=true) (reference docs/threads: Introducing Form Templates [read more](https://meta.discourse.org/t/-/278631/1?silent=true), Creating form templates [read more](https://meta.discourse.org/t/-/397564/1?silent=true))
- **Admin UI glitch: changing target audience for “Enable form templates” creates a sidebar “Update Discourse” entry:** @Noble_Fish posted a reproducible UI oddity in v2026.3.0-latest where toggling audience seems to create an incorrect left-nav entry. [read more](https://meta.discourse.org/t/-/398151/1?silent=true)
### #ux
- **Login page logo won’t center when language/theme toggles appear:** @jack222 reported the top login logo shifts off-center if a language switcher or dark/light toggle appears on the right side. [read more](https://meta.discourse.org/t/-/398159/1?silent=true)
- **Profile/settings IA continues to bug people (navigation + grouping):** discussion continued around reorganizing profile/account/security/interface sections to reduce user confusion, with concrete suggestions quoted into the thread by @ToddZ. [read more](https://meta.discourse.org/t/-/330279/3?silent=true)
### #contribute:feature
- **Proposal: “User self engagement” report for CPD-style evidence:** @Paul_King suggested a user-run report that can summarize engagement over a date range (categories/tags/topics, reading vs posting) to help professionals document participation. [read more](https://meta.discourse.org/t/-/398148/1?silent=true)
### #blog
- **How Discourse built “Upcoming Changes” for gradual rollouts:** @martin posted the companion discussion for the blog explaining how Discourse can stage changes across different site configurations to prevent surprises for admins and members. [read more](https://meta.discourse.org/t/-/398118/1?silent=true)
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@awesomerobot** diagnosed a post-upgrade breakage of “official” theme components and traced it to a missing module import from the Journal plugin, recommending [safe mode](https://meta.discourse.org/t/53504?silent=true) to confirm plugin interference. [read more](https://meta.discourse.org/t/-/398143/2?silent=true)
Also pointed someone trying to jump directly into Chat toward a helpful theme component. [read more](https://meta.discourse.org/t/-/398082/3?silent=true) (component: [read more](https://meta.discourse.org/t/-/387112/1?silent=true))
- **@Falco** helped untangle the [Data Explorer](https://meta.discourse.org/t/32566?silent=true) API change that rejects `limit=ALL`, linked the underlying change, and shared pagination guidance plus the current max-row cap. [read more](https://meta.discourse.org/t/-/398172/2?silent=true)
They also clarified assignment-related API endpoints and parameters for group vs direct assignments. [read more](https://meta.discourse.org/t/-/398168/2?silent=true)
And confirmed delayed AI Agent responses aren’t supported yet, framing it as an #automation need and hinting at a future overhaul. [read more](https://meta.discourse.org/t/-/306099/30?silent=true)
- **@martin** kicked off discussion on Discourse’s gradual rollout machinery via the “Upcoming Changes” companion topic. [read more](https://meta.discourse.org/t/-/398118/1?silent=true)
- **@nat** acknowledged the localized-tag slugification bug report and jumped in to investigate. [read more](https://meta.discourse.org/t/-/398105/4?silent=true)
Separately, they confirmed a fix had been merged for a wiki-editing issue and linked the PR in-thread. [read more](https://meta.discourse.org/t/-/397964/10?silent=true)
- **@Bas** chimed in on an “unsilence” UX oddity with the memorable takeaway:
- **@sam** connected the localized-tags issue to earlier slug-related work and looped @nat in for review. [read more](https://meta.discourse.org/t/-/398105/2?silent=true) (referenced: [read more](https://meta.discourse.org/t/-/397789/10?silent=true))
- **@gerhard** clarified Crowdin behavior around “identical translation already saved,” and offered to review the specific language string in question. [read more](https://meta.discourse.org/t/-/14882/159?silent=true)
- **@pmusaraj** responded on a signup/console-error thread by suggesting a controlled test: try a fresh install on the same 1GB droplet size to isolate whether resource constraints are the root cause. [read more](https://meta.discourse.org/t/-/397895/13?silent=true)
* * *
_That’s a wrap—may all your localized tags be slugified, your `limit=ALL` requests be pleasantly paginated, and every “task failed successfully” moment end in a clean refresh._
---
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
**In the last 24 hours (2026-03-11 → 2026-03-12):**
- **New posts:** 67
- **New topics:** 7
**Top contributors (posts + likes received in the last 24h):**
| User | Posts | Likes |
| --- | --- | --- |
| @nat | 4 | 9 |
| @awesomerobot | 5 | 3 |
| @Canapin | 4 | 3 |
| @yingdong | 3 | 4 |
| @Danielle | 2 | 5 |
| @sam | 2 | 4 |
| @supermathie | 2 | 4 |
| @martin | 1 | 3 |
| @dax | 1 | 2 |
| @benword | 1 | 2 |
* * *
## Interesting Topics
### #Support
- @yingdong asked how to localize custom badges/groups on multilingual sites (#badges #groups #translation), and @nat explained why seeded badges are i18n’d but custom ones aren’t—plus a _console-only_ workaround using `TranslationOverride.upsert!` to create new locale keys ([read more](https://meta.discourse.org/t/-/398127/8?silent=true)).
- A tricky edge case popped up where a topic merge left a “solved” record behind, preventing the new merged topic from marking a solution; @martin fixed the database state and noted they’ll investigate a preventative fix ([read more](https://meta.discourse.org/t/-/398163/13?silent=true)).
- After a change, admins can’t turn topics from read-restricted categories into **global banners** anymore; @dax framed it as an access-control/security safeguard and suggested using **unlisted topics** in public categories plus **Discourse Automation** as a workflow workaround ([read more](https://meta.discourse.org/t/-/398306/2?silent=true), plus the referenced automation topic: [read more](https://meta.discourse.org/t/-/195773/1?silent=true)).
### #bug
- A report about mobile browser text-selection “action buttons” not working ended with @supermathie recommending supported browsers (and explaining why chasing obscure/non-store browsers isn’t viable) ([read more](https://meta.discourse.org/t/-/397943/6?silent=true), background: [read more](https://meta.discourse.org/t/-/210258/5?silent=true)).
- The **discourse-subscriptions** plugin started crashing boot on `v2026.3.0` with an `USERNAME_ROUTE_FORMAT` constant error; @sam confirmed a load-order/deprecation tangle and shipped a core PR to remove the deprecation path ([read more](https://meta.discourse.org/t/-/398212/3?silent=true)).
- “Multiple form templates per category” didn’t persist because the save button never appeared; @awesomerobot reproduced, provided a workaround (disable “simplified category creation”), and then merged a fix shortly after ([read more](https://meta.discourse.org/t/-/398176/4?silent=true)).
- Dashboard report UX: a discussion on whether traffic graphs should re-scale the Y-axis when series are toggled; @chapoi agreed the intention doesn’t fit this report well and suggested making the scaling smarter ([read more](https://meta.discourse.org/t/-/397956/9?silent=true)).
- A gnarly composer issue on iPad where “peek mode” could shove the editor off-screen appears fixed via a core change; @chapoi asked for confirmation after updating, and the reporter confirmed it worked ([read more](https://meta.discourse.org/t/-/396942/10?silent=true)).
- Localized tags weren’t being slugified correctly (#content-localization); @nat shared that a fix was merged to clean localized tag names returned from the LLM _and_ migrate existing “dirty” tag names ([read more](https://meta.discourse.org/t/-/398105/7?silent=true)).
- Two fresh admin/UI bugs landed: newly created groups not appearing everywhere until refresh ([read more](https://meta.discourse.org/t/-/398285/1?silent=true), related older thread: [read more](https://meta.discourse.org/t/-/77715/1?silent=true)) and a “topic timer” flow that could lead to a disastrous, unresponsive UI state after scheduling publishing with a missing destination category ([read more](https://meta.discourse.org/t/-/398284/1?silent=true), related: [read more](https://meta.discourse.org/t/-/64870/1?silent=true)).
### #announcements
- @Danielle announced a new webinar— **“Creating & Nurturing a Moderator Program”** —and confirmed that registering will also provide access to a recording afterward ([read more](https://meta.discourse.org/t/-/398295/3?silent=true)).
### #customization:plugin
- The official **Discourse Signatures** plugin got a solid set of improvements merged by @jamie.wilson: group-based restriction, category-based display, first-post-only mode, stricter URL validation, and size limits—all backward-compatible by default ([read more](https://meta.discourse.org/t/-/42263/213?silent=true)).
### #customization:extras
- The GitHub Action that creates Discourse topics for releases shipped `v1.1.0`, adding GitHub→Discourse username mapping so release announcements can post “as the author” instead of a fixed service account ([read more](https://meta.discourse.org/t/-/221114/3?silent=true)).
- The terminal client **termcourse** added real-time notifications via MessageBus so topic list updates can appear in a status bar (and sparked discussion about matching Discourse keyboard shortcuts) ([read more](https://meta.discourse.org/t/-/395285/18?silent=true)).
### #contribute:site-feedback
- Feedback continued on Meta’s category re-organization; @hellekin shared specific navigation pain points (subwiki “index” links, missing descriptions, and subcategory visibility), with suggestions about where “Data Reporting” should live ([read more](https://meta.discourse.org/t/-/396306/55?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @nat dug deep into multilingual badge mechanics—clarifying what’s i18n’d via Crowdin vs. stored as plain DB text, and why custom badge localization currently requires console access ([How can badges and groups be localized (multilingual)?](https://meta.discourse.org/t/-/398127/8?silent=true)). Also shared a merged fix for cleaning localized tag outputs + a migration to repair existing localized tags ([Localized tags are not slugified](https://meta.discourse.org/t/-/398105/7?silent=true)).
- @Danielle posted the upcoming moderator-program webinar announcement and confirmed a replay will be posted after the event ([Webinar: Creating & Nurturing a Moderator Program](https://meta.discourse.org/t/-/398295/3?silent=true)).
- @sam responded to a boot-crashing regression involving the **discourse-subscriptions** plugin and followed up with a core PR to eliminate the deprecation issue underlying the failure mode ([Discourse-subscriptions plugin crashes boot on v2026.3.0](https://meta.discourse.org/t/-/398212/3?silent=true)).
- @supermathie closed out a mobile-browser text-selection issue by recommending supported browsers and explaining why debugging non-store browsers isn’t practical ([The three buttons that pop up after selecting text on a mobile browser do not work](https://meta.discourse.org/t/-/397943/6?silent=true)).
- @martin investigated and fixed a “cannot mark reply as solution after merger” situation by correcting an existing solved-record conflict left behind from the old topic ([Cannot mark reply as “solution” after merger](https://meta.discourse.org/t/-/398163/13?silent=true)).
- @awesomerobot reproduced a bug where multiple category form templates couldn’t be saved and confirmed a fix was merged ([Multiple “Form templates” for a category doesn’t work](https://meta.discourse.org/t/-/398176/4?silent=true)). They also helped triage a potential “solved status locked” bug by asking for console errors and additional diagnostics ([How to understand the “Solved” locked status](https://meta.discourse.org/t/-/398266/4?silent=true)), and answered a GDPR/process question by clarifying AI compliance depends on the configured provider and deployment choices ([Introducing Discourse AI Sentiment Analysis](https://meta.discourse.org/t/-/355901/7?silent=true)).
- @dax explained why global banners are now gated (no more banners sourced from read-restricted categories), and suggested an interim workflow using _unlisted_ topics plus automation to keep banner templates out of public lists ([Can no longer create global banners from restricted categories](https://meta.discourse.org/t/-/398306/2?silent=true)).
- @jamie.wilson merged a major upgrade set into the official signatures plugin, including group restrictions and hardened URL validation ([Discourse Signatures](https://meta.discourse.org/t/-/42263/213?silent=true)).
- @chapoi weighed in on dashboard report scaling behavior and agreed the current approach doesn’t work well for the traffic graph use case ([Site Traffic graph: should reselection of included series re-scale the Y axis?](https://meta.discourse.org/t/-/397956/9?silent=true)). They also pointed to a core fix for an iPad composer peek-mode layout issue ([Ipad - Composer peek mode button causes editor to go off screen](https://meta.discourse.org/t/-/396942/10?silent=true)).
- @isaac clarified the security rationale behind disallowing banners sourced from read-restricted categories—banner content can become visible to everyone, and admins may not realize that implication when drafting in private areas ([Can no longer create global banners from restricted categories](https://meta.discourse.org/t/-/398306/6?silent=true)).
* * *
_That’s a wrap: yesterday we learned that badges can be multilingual (sometimes), banners can’t be private (anymore), and topic timers can be… adventurous—so keep your console handy and your drafts well-fed._
---
# Today on [meta.discourse.org](http://meta.discourse.org)…
_Daily recap for activity between 2026-03-12 and 2026-03-13 (last 24 hours). All highlights below are backed by the linked discussions._
* * *
## Key Stats
- **New posts:** **54**
- **New topics:** **11**
**Top users (posts + likes received in the last 24h)**
| User | Posts | Likes |
| --- | --- | --- |
| @LotusJeff | 5 | 17 |
| @Canapin | 4 | 4 |
| @chapoi | 3 | 5 |
| @NateDhaliwal | 3 | 4 |
| @pacharanero | 2 | 3 |
| @ばこん | 2 | 3 |
| @derak | 1 | 10 |
| @Falco | 1 | 4 |
| @elmuerte | 1 | 3 |
| @Lilly | 1 | 3 |
> Team movers worth noting: @chapoi, @Falco, @dax, @martin, and @sam all posted in the last day (details in the [@team](https://meta.discourse.org/groups/team?silent=true) section).
* * *
## Interesting Topics
### #Community Building
- @LotusJeff kicked off a nostalgia-and-migrations thread asking _“How old is your forum?”_ and started compiling an “elder forums” table, with stories ranging from mailing lists → Yahoo Groups → phpBB → Discourse ([read more](https://meta.discourse.org/t/-/398335/1?silent=true)).
Related: a long-running vBulletin-to-Discourse migration effort came up via @elmuerte’s import work ([read more](https://meta.discourse.org/t/-/54881/178?silent=true)) and community anniversary reflections were referenced ([read more](https://meta.discourse.org/t/-/326493/1?silent=true), [read more](https://meta.discourse.org/t/-/359593/1?silent=true)).
* * *
### #customization:plugin
- @derak announced **📞 diskuz Call** , a plugin that adds **peer-to-peer WebRTC voice/video calls inside Discourse** (site handles signaling, media goes P2P with optional TURN) ([read more](https://meta.discourse.org/t/-/398331/1?silent=true)).
If you’re evaluating new add-ons, the canonical plugin install guide remains the starting point ([read more](https://meta.discourse.org/t/-/19157/1?silent=true)).
- The **ActivityPub plugin** thread saw reports of failures when trying to follow `@announcements@meta.discourse.org`, including “Could not resolve actor” warnings and logs to investigate ([read more](https://meta.discourse.org/t/-/266794/477?silent=true)).
- A **security-focused heads-up** landed in the Sign-In with Ethereum plugin topic: @RGJ pointed people to a newer fork and urged an immediate switch due to vulnerabilities found in the older plugin version ([read more](https://meta.discourse.org/t/-/231897/53?silent=true)).
* * *
### #Announcements
- Discourse’s hosted LLM offering increased capacity substantially across plans; @Falco shared new limits (e.g. Starter → 200K, Pro → 500K, Business → 1M) plus improvements to model quality, max tokens, and responsiveness ([read more](https://meta.discourse.org/t/-/390985/12?silent=true)).
Background context continues in the broader #ai discussions around dev workflows and guardrails ([read more](https://meta.discourse.org/t/-/394773/12?silent=true)).
* * *
### #Marketplace
- A new request appeared from someone looking for help installing Discourse on a VPS (including database/SSH setup), with @NateDhaliwal pointing to the **one-line installer** and a practical “quick start” path ([read more](https://meta.discourse.org/t/-/398340/1?silent=true)).
* * *
### #bug
- A “sticky notification” report described Discourse showing a notification badge that didn’t correspond to anything unread, prompting troubleshooting (reload, cookies, logout/login) and broader commentary about async UI complexity ([read more](https://meta.discourse.org/t/-/398328/1?silent=true)).
- A Chinese-language report said that **after chat is disabled, chat-related preferences/settings disappear** , and visiting the preferences/chat URL redirects to `/latest` ([read more](https://meta.discourse.org/t/-/398401/1?silent=true)).
The reporter referenced an older recurring issue thread for historical comparison ([read more](https://meta.discourse.org/t/-/217271/1?silent=true)).
- A UI glitch was shared where opening a user card and then scrolling caused the card to appear **over the editor** in a “funny bug” screenshot ([read more](https://meta.discourse.org/t/-/398327/1?silent=true)).
* * *
### #Support
- Upload troubleshooting continued: @Lilly tested new-user upload limits and couldn’t reproduce the “only one image” issue under default settings, while others suggested verifying whether the real limiter was _embedded media_ settings or error messaging ([read more](https://meta.discourse.org/t/-/398088/8?silent=true)).
- Email-in reliability: a self-hoster reported Discourse **stopped polling POP3** with `Net::ReadTimeout`, despite interval changes, upgrades, and restarts—suggesting something intermittent or provider-related ([read more](https://meta.discourse.org/t/-/398324/1?silent=true)).
- A regression report on **2026.3.0-latest** : staging showed username + real name no longer displayed together (only username shown), asking for debugging pointers ([read more](https://meta.discourse.org/t/-/398407/1?silent=true)).
- Another urgent admin report: a community began **logging everyone out** and blocking logins with “you can’t log in from that IP address” unless retried several times ([read more](https://meta.discourse.org/t/-/398408/1?silent=true)).
- A practical limitation surfaced when merging topics: you currently **can’t mark a reply as “solution” after a merge** unless you clear the existing solution first—though a fix is in progress ([read more](https://meta.discourse.org/t/-/398163/16?silent=true)).
Related feature discussion on solved UX continues elsewhere ([read more](https://meta.discourse.org/t/-/335397/8?silent=true)).
- Banner workflows: users found it hard to create **global banners from restricted categories** because “Pin topic” disappears when unlisting; a workaround is to use Automation’s “Make Banner Topic” script referencing the unlisted topic ID ([read more](https://meta.discourse.org/t/-/398306/11?silent=true)).
(Automation plugin context: [read more](https://meta.discourse.org/t/-/195773/1?silent=true))
* * *
### #ux
- The DiscoTOC iPad portrait overlay problem has a clear direction: @chapoi pointed to a fix via a PR that should resolve TOC rendering over text without a proper background ([read more](https://meta.discourse.org/t/-/387532/5?silent=true)).
* * *
### #users
- A new step-by-step guide explained how to set up **Discourse MCP** in **OpenCode CLI** , emphasizing that ordinary-user access is enough and encouraging people to “use your LLM” to follow the instructions ([read more](https://meta.discourse.org/t/-/398378/1?silent=true)).
Companion guide for another client (Codex CLI) was also referenced ([read more](https://meta.discourse.org/t/-/397662/1?silent=true)).
* * *
### #customization:extras
- The **Clip To Discourse** Chrome extension shipped v0.19.5 with _text selection support_, selection-aware templates, and a right-click context menu—plus plans to implement the Discourse User API auth flow ([read more](https://meta.discourse.org/t/-/392335/7?silent=true)).
Relevant spec: Discourse User API keys specification ([read more](https://meta.discourse.org/t/-/48536/1?silent=true)).
- Terminal Discourse client **termcourse** got UX tweaks and localisation updates (including `es`, `fr`, `de`, `en`), with @merefield inviting PRs for more languages ([read more](https://meta.discourse.org/t/-/395285/21?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @chapoi weighed in on the “phantom notification” issue, explaining why these problems are _extremely hard to solve perfectly_ given the complexity of modern web stacks ([read more](https://meta.discourse.org/t/-/398328/5?silent=true)).
- @chapoi answered an #ai development-docs question by pointing out that Discourse dev docs are now included in the main repo (context: discussion in the Claude + Discourse dev thread) ([read more](https://meta.discourse.org/t/-/394773/13?silent=true)).
- @chapoi also linked the likely fix for the iPad DiscoTOC overlay issue ([read more](https://meta.discourse.org/t/-/387532/5?silent=true)).
- @Falco posted updated capacity limits and performance improvements for Discourse’s hosted LLM service, noting multiple capacity increases since launch ([read more](https://meta.discourse.org/t/-/390985/12?silent=true)).
- @dax provided a concrete workaround for creating banners from restricted/unlisted topics: use the Automation plugin’s **“Make Banner Topic”** script with the topic ID ([read more](https://meta.discourse.org/t/-/398306/11?silent=true)).
- @martin confirmed the current limitation around solution-marking after topic merges and noted a fix is being worked on ([read more](https://meta.discourse.org/t/-/398163/16?silent=true)).
- @sam responded to a dev question about replacing Markdown with Quarkdown: _not possible directly_—you’d need to extend `markdown.it` with the desired features ([read more](https://meta.discourse.org/t/-/398341/2?silent=true)).
* * *
_That’s a wrap—yesterday we time-traveled through 25-year-old forums, shipped bigger AI limits, and even squeezed in a Discourse-native WebRTC calling plugin… not bad for a single day on Meta._
---
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
In the last 24 hours, meta saw **46 new posts** across **11 new topics**. (Time window covered by this report: 2026-03-13 → 2026-03-14.)
**Top users (posts / likes received in the period):**
| User | Posts | Likes |
| --- | --- | --- |
| @Falco | 7 | 15 |
| @satonotdead | 3 | 4 |
| @Timelord | 3 | 1 |
| @Canapin | 2 | 5 |
| @supermathie | 2 | 4 |
| @itsbhanusharma | 1 | 3 |
| @nat | 1 | 3 |
| @darkpixlz | 1 | 2 |
| @merefield | 1 | 1 |
| @pfaffman | 1 | 1 |
* * *
## Interesting Topics
### #Support
- @Canapin suspected a blocked-IP misconfiguration in a “everyone is getting logged out” report, and @Falco quickly traced it to a **Cloudflare + IP ban** foot-gun (everyone appears from one IP), plus a reminder to use the Cloudflare template in `app.yml` ([read more](https://meta.discourse.org/t/-/398408/2?silent=true), [read more](https://meta.discourse.org/t/-/398408/3?silent=true)).
- Forum content “acquisition”: @Timelord asked how to bring content from another Discourse without a full backup/restore, and @itsbhanusharma pointed to guidance on **moving topics between instances** ([read more](https://meta.discourse.org/t/-/398452/1?silent=true), [read more](https://meta.discourse.org/t/-/398452/2?silent=true), plus the referenced how-to: [read more](https://meta.discourse.org/t/-/38930/1?silent=true)).
- A Chinese-language AI-translation edge case: enabling AI translation also localizes **tags** and makes them hard to edit; @nat suggested enabling the _Experimental tag settings page_ so tag localizations can be edited properly ([read more](https://meta.discourse.org/t/-/398440/1?silent=true), [read more](https://meta.discourse.org/t/-/398440/2?silent=true)).
- Long-form “fix-it” write-up: @satonotdead documented a recovery approach for **missing upload records** after migrating from S3 to local filesystem, including rebuilding `uploads` DB records and rebaking posts ([read more](https://meta.discourse.org/t/-/152978/9?silent=true)).
- Article/course-style publishing on Discourse: @Engineer_Abdallah explored using Discourse as a tutorials + course sequence platform (with restricted authorship), and @chapoi recommended using **Topic List Thumbnails** to get images into lists ([read more](https://meta.discourse.org/t/-/398435/1?silent=true), [read more](https://meta.discourse.org/t/-/398435/2?silent=true), and the component: [read more](https://meta.discourse.org/t/-/150602/1?silent=true)).
- Admin UI nuance: @Ethsim2 questioned how `about page hidden groups` should interact with `about page extra groups`—specifically whether “extra” viewers (like admins) should still see otherwise-hidden groups on `/about` ([read more](https://meta.discourse.org/t/-/398417/1?silent=true)).
- Theme behavior investigation: a Ghost theme user reported that categories _without_ subcategories weren’t showing view/reply counts; @chapoi challenged whether it’s truly theme-related and pointed at the Ghost preview showing counts on a “no subcategory” category ([read more](https://meta.discourse.org/t/-/398418/1?silent=true), [read more](https://meta.discourse.org/t/-/398418/2?silent=true), Ghost theme reference: [read more](https://meta.discourse.org/t/-/111806/47?silent=true)).
- Attachment link counters regression: a report that click counters no longer appear for uploaded files—whether or not `|attachment` is present—prompting questions about restoring the prior behavior ([read more](https://meta.discourse.org/t/-/398453/1?silent=true)).
- OIDC login troubleshooting: a LinkedIn OAuth redirect mismatch was resolved by ensuring the callback URL matches, e.g. `https://discourse.example.com/auth/linkedin_oidc/callback` ([read more](https://meta.discourse.org/t/-/375899/4?silent=true)).
- #ai sentiment backfill: @satonotdead hit `Don't run this task in production!` when trying `rake ai:sentiment:populate`, and @Falco clarified that **backfill for the last 60 days is automatic** once enabled ([read more](https://meta.discourse.org/t/-/309270/15?silent=true), [read more](https://meta.discourse.org/t/-/309270/16?silent=true)).
### #bug
- #search #tablet: a mobile/tablet report where the **floating search widget types characters reversed** (“thing” becomes “gniht”) in landscape on Edge/Android; @Falco couldn’t reproduce on a newer environment and suggested trying another keyboard ([read more](https://meta.discourse.org/t/-/398423/1?silent=true), [read more](https://meta.discourse.org/t/-/398423/3?silent=true)).
- #search #tablet (related): another Edge/Android landscape/portrait issue where the **floating search box can’t be closed** after rotating back to vertical, persisting across navigations until the device is horizontal again ([read more](https://meta.discourse.org/t/-/398427/1?silent=true)); the reporter also confirmed reproducibility in [Safe Mode](https://meta.discourse.org/t/53504?silent=true) ([read more](https://meta.discourse.org/t/-/53504/1?silent=true)).
- #solved: the new category settings UI appears to make it impossible to _disable_ “Allow topic owner and staff to mark a reply as the solution” after it’s enabled, with the “Solved” section disappearing from the original settings page ([read more](https://meta.discourse.org/t/-/398439/1?silent=true)).
- #chat: after disabling chat, chat settings reportedly **disappear from preferences** and don’t return; a second user confirmed they can reproduce it ([read more](https://meta.discourse.org/t/-/398401/2?silent=true)).
### #contribute:feature
- Reactions/likes UI: a user asked how to expand “and 6 more…” to see _everyone_ who reacted; @Falco said Discourse is working on a new UI component to support this cleanly ([read more](https://meta.discourse.org/t/-/389820/23?silent=true), [read more](https://meta.discourse.org/t/-/389820/24?silent=true)).
- Multisite clarity: @supermathie proposed improving the `/sidekiq` experience for admins on multisite “guest” sites—showing a **helpful explanation** instead of a confusing error when Sidekiq is only available on the host instance ([read more](https://meta.discourse.org/t/-/398415/1?silent=true), with prior context link: [read more](https://meta.discourse.org/t/-/398397/7?silent=true)).
- Calendar privacy ergonomics: for authenticated ICS feeds for private events, @Falco pointed to work already added via PR plus follow-up improvements to make User API Key flows friendlier for non-technical users ([read more](https://meta.discourse.org/t/-/393203/4?silent=true), PRs referenced: [read more](https://github.com/discourse/discourse/pull/38534), [read more](https://github.com/discourse/discourse/pull/38598)).
### #Integrations
- #ai #how-to: Discourse AI Google Programmable Search Engine setup hit a snag as Google now requires at least one configured domain; @Falco confirmed the “entire web” behavior is discontinued and said the team is researching alternatives (including leveraging LLM-native web search tools) ([read more](https://meta.discourse.org/t/-/307107/13?silent=true), [read more](https://meta.discourse.org/t/-/307107/15?silent=true), plus Google’s deprecation context links shared in-thread: [read more](https://developers.google.com/custom-search/v1/overview), [read more](https://cloud.google.com/use-cases/site-search)).
### #customization:theme component
- A new Bilibili inline player theme component was shared as a **no-rebuild** alternative to the server-side plugin approach, with setup notes and comparisons to the existing OneBox/plugin route ([read more](https://meta.discourse.org/t/-/398438/1?silent=true), related plugin topic: [read more](https://meta.discourse.org/t/-/389149/1?silent=true)).
### #customization:plugin
- Discourse OpenID Connect (#openid-connect) discussion continued with a request to sync Discourse groups from **OIDC groups** , referencing an older PR that implemented it but wasn’t taken further ([read more](https://meta.discourse.org/t/-/103632/320?silent=true), referenced PR: [read more](https://github.com/discourse/discourse/pull/34763/changes)).
### #community-building Building
- A community check-in thread asked “How old is your forum?”, drawing stories ranging from forums founded in 2024 to a week-old install currently stuck at _502 Bad Gateway_ ([read more](https://meta.discourse.org/t/-/398335/14?silent=true), [read more](https://meta.discourse.org/t/-/398335/15?silent=true)).
### #Marketplace
- A VPS install/help thread got a generous offer: @Timelord volunteered to help with installation _for free_ via DM ([read more](https://meta.discourse.org/t/-/398340/5?silent=true)).
### #Dev
- A Dev curiosity resurfaced: “Can Markdown be replaced with Quarkdown?”, with @merefield praising the linked repo ([read more](https://meta.discourse.org/t/-/398341/3?silent=true)).
### #Using Discourse
- Topic list filtering: a question about using `/filter` while keeping a left-side navigation (like a docs sidebar) referenced the official guide on filtering topic lists ([read more](https://meta.discourse.org/t/-/375558/19?silent=true), original reference: [read more](https://meta.discourse.org/t/-/375558/1?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Falco was busy across support, bugs, and roadmap signals: they diagnosed a Cloudflare/IP-ban cause for mass logouts ([read more](https://meta.discourse.org/t/-/398408/3?silent=true)), asked for keyboard variability to reproduce the reversed floating-search input bug ([read more](https://meta.discourse.org/t/-/398423/3?silent=true)), confirmed work underway for a better “view all reactions” UI ([read more](https://meta.discourse.org/t/-/389820/24?silent=true)), and clarified that Discourse AI Google search needs new providers now that Google’s prior capability is discontinued ([read more](https://meta.discourse.org/t/-/307107/15?silent=true)). They also noted that AI sentiment backfill is automatic for the last 60 days ([read more](https://meta.discourse.org/t/-/309270/16?silent=true)) and referenced improvements for authenticated ICS feeds in the calendar feature area ([read more](https://meta.discourse.org/t/-/393203/4?silent=true)).
- @supermathie posted an operational heads-up in an email-delivery thread, linking the breaking/fixing commits and apologizing for the disruption from a merged gem update ([read more](https://meta.discourse.org/t/-/393621/23?silent=true)). They also proposed a UX improvement so admins understand why `/sidekiq` is unavailable on multisite guests, aligning with the “principle of least surprise” ([read more](https://meta.discourse.org/t/-/398415/1?silent=true)).
- @nat delivered a quick solution to a tag-localization issue caused by AI translation: enable the _Experimental tag settings page_ so tag localizations can be edited ([read more](https://meta.discourse.org/t/-/398440/2?silent=true)).
- @chapoi helped guide two separate support threads: for “articles with images,” they recommended using Topic List Thumbnails ([read more](https://meta.discourse.org/t/-/398435/2?silent=true)); and for Ghost theme view/reply counts, they challenged the premise by checking the theme preview and asking for confirmation it’s actually theme-caused ([read more](https://meta.discourse.org/t/-/398418/2?silent=true)).
* * *
Yesterday’s vibes: if your search starts typing **backwards** , just remember—on meta, someone will inevitably suggest _palindromes_ while the team hunts the real fix.
---
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
In the last 24 hours, meta logged **42 new posts** across **4 new topics** —including fresh threads on composer UI overflow ([read more](https://meta.discourse.org/t/-/398473/1?silent=true)), intermittent theme upload failures ([read more](https://meta.discourse.org/t/-/398471/1?silent=true)), recovering missing hosted CDN assets ([read more](https://meta.discourse.org/t/-/398493/1?silent=true)), and embedding Bunny Stream videos ([read more](https://meta.discourse.org/t/-/398491/1?silent=true)).
**Top users (posts / likes, with a recent reference post):**
| User | Posts | Likes | Recent post |
| --- | --- | --- | --- |
| **@Canapin** | 3 | 5 | Horizontal-scroll hint + UX note ([read more](https://meta.discourse.org/t/-/398473/3?silent=true)) |
| **@awesomerobot** _(team)_ | 2 | 4 | Investigating missing scroll arrow ([read more](https://meta.discourse.org/t/-/398473/6?silent=true)) |
| **@NateDhaliwal** | 4 | 3 | Theme upload troubleshooting / pointers ([read more](https://meta.discourse.org/t/-/398471/3?silent=true)) |
| **@Timelord** | 3 | 2 | Offer to help with VPS install/backup plan ([read more](https://meta.discourse.org/t/-/398340/7?silent=true)) |
| **@pfaffman** | 1 | 2 | “Click-to-upgrade” dashboard mention ([read more](https://meta.discourse.org/t/-/398340/8?silent=true)) |
| **@Arkshine** | 2 | 2 | Banner Featured Links fixes + cleanup ([read more](https://meta.discourse.org/t/-/327497/27?silent=true)) |
| **@amotl** | 2 | 1 | Hosted CDN attachment recovery question ([read more](https://meta.discourse.org/t/-/398493/1?silent=true)) |
| **@RGJ** | 2 | 1 | Cloudflare + Geo blocking clarification ([read more](https://meta.discourse.org/t/-/227824/36?silent=true)) |
| **@renato** _(team)_ | 2 | 1 | Anchor-link bug no longer reproducible ([read more](https://meta.discourse.org/t/-/397748/7?silent=true)) |
| **@merefield** | 1 | 1 | Advising to remove noisy/deprecated plugin ([read more](https://meta.discourse.org/t/-/398471/9?silent=true)) |
* * *
## Interesting Topics
### #ux
- In a #composer usability thread, 祁同伟 reported that when the editor has “too many buttons,” the ones at the end become inaccessible; replies suggested the toolbar is horizontally scrollable, but the affordance is subtle (and the arrow disappears on touch devices), sparking discussion about better pointer/viewport logic ([read more](https://meta.discourse.org/t/-/398473/1?silent=true), [read more](https://meta.discourse.org/t/-/398473/6?silent=true)).
### #Support
- A hosted-support question asked how to restore **individual missing CDN uploads** (one image + two JSON attachments) after a hiccup, highlighting the gap between self-hosted “I know where to look” instincts and the hosted operational toolchain (#hosted-support) ([read more](https://meta.discourse.org/t/-/398493/1?silent=true), [read more](https://meta.discourse.org/t/-/398493/2?silent=true)).
- A theme-dev workflow issue: a site intermittently returns **HTTP 500** during `admin/themes/import.json` while uploading via CLI, and the ensuing debugging touched logs, deprecation noise, and isolating third-party plugins as a first step ([read more](https://meta.discourse.org/t/-/398471/1?silent=true), [read more](https://meta.discourse.org/t/-/398471/9?silent=true)). (Related reference threads that came up: Theme CLI install guide ([read more](https://meta.discourse.org/t/-/82950/1?silent=true)) and installing themes/components ([read more](https://meta.discourse.org/t/-/63682/1?silent=true)).)
- Tablet/search UX: someone observed that characters appear **in reverse order** while typing in the _floating search widget_, and narrowed it down to the OS “floating keyboard” feature (with follow-up testing planned across keyboards/IMEs) (#search #tablet) ([read more](https://meta.discourse.org/t/-/398423/5?silent=true), [read more](https://meta.discourse.org/t/-/398423/6?silent=true)).
- An older-but-active DiscourseAI support thread circled back to **debugging missing sentiment output** (“no sentiment in 60 days”) and pointed to the self-hosting setup guide for sentiment/emotion as the baseline checklist (#ai #ai-sentiment) ([read more](https://meta.discourse.org/t/-/309270/17?silent=true), [read more](https://meta.discourse.org/t/-/334451/1?silent=true)).
- A signup regression investigation continued: after toggling “enable local logins,” new users reportedly hit failures plus console errors, with logs mentioning missing MaxMind DB files and OAuth callback failures in the Discourse ID flow (#discourse-id) ([read more](https://meta.discourse.org/t/-/397895/14?silent=true), [read more](https://meta.discourse.org/t/-/397895/1?silent=true)).
- An attachments/UI detail got attention: the **link counter/URL formatting for attachments** seems to include a second “dimension-like” segment that makes sense for images but looks suspicious for non-images, raising questions about what the counter _should_ display ([read more](https://meta.discourse.org/t/-/398453/1?silent=true), [read more](https://meta.discourse.org/t/-/398453/2?silent=true)).
- A short, practical embed question: how to get Discourse to **inline-embed Bunny Stream (Bunny CDN) videos** instead of showing a plain link preview, using a `player.mediadelivery.net` URL as the example ([read more](https://meta.discourse.org/t/-/398491/1?silent=true), [read more](https://meta.discourse.org/t/-/398491/2?silent=true)).
- A solved support topic on **forum acquisition/migration planning** saw an update promising dev testing results “in the next week or so,” keeping the thread moving even after being marked solved ([read more](https://meta.discourse.org/t/-/398452/1?silent=true), [read more](https://meta.discourse.org/t/-/398452/5?silent=true)).
### #Marketplace
- In a “help me install Discourse on my VPS” conversation, the thread evolved from “I’m new to servers/SSH” into practical offers (install help + backup strategy) and alternatives like one-click upgrade tooling, plus a side discussion about legal requests and data access expectations ([read more](https://meta.discourse.org/t/-/398340/6?silent=true), [read more](https://meta.discourse.org/t/-/398340/8?silent=true)).
### #Theme\_component
- The **Banner Featured Links** component received a burst of maintenance: replacing deprecated `htmlSafe`, fixing mobile SCSS issues, improving settings descriptions, tightening HTML validity, and pinning to a newer core version; the update was shared along with an upstream PR for review ([read more](https://meta.discourse.org/t/-/327497/24?silent=true), [read more](https://meta.discourse.org/t/-/327497/27?silent=true)).
### #bug
- An “anchor links don’t work _inside_ Discourse” report appears resolved: the issue could no longer be reproduced after a core fix landed, and the topic is being scheduled to close unless anyone can still trigger it ([read more](https://meta.discourse.org/t/-/397748/7?silent=true), [read more](https://meta.discourse.org/t/-/397748/1?silent=true)).
### #customization:plugin
- The long-running #activitypub #experimental thread gained more diagnostics: a participant shared log excerpts showing repeated handle validation and actor lookups while confirming identical behavior to prior reports—useful breadcrumbs for anyone trying to reproduce ([read more](https://meta.discourse.org/t/-/266794/478?silent=true), [read more](https://meta.discourse.org/t/-/266794/1?silent=true)).
- The **Geo Blocking plugin** thread clarified Cloudflare specifics: it can work with Cloudflare when configured correctly, but `CF-IPCountry` is a _country code_ header (not an IP), and the plugin relies on Discourse’s MaxMind database rather than that header ([read more](https://meta.discourse.org/t/-/227824/35?silent=true), [read more](https://meta.discourse.org/t/-/227824/36?silent=true)). (Cloudflare best-practices doc referenced in-thread: [read more](https://meta.discourse.org/t/-/293405/1?silent=true).)
### #Site\_feedback
- In the “collaborative content gardening hub” discussion, @Canapin described using flags to request edits on older posts, but hit an odd UI limitation where only an “It’s illegal” flag option appeared—prompting a meta conversation about better processes (wiki conversion, mod contact norms) and cross-linking to “user uploaded files monitoring” and “topic gallery” ideas ([read more](https://meta.discourse.org/t/-/397606/50?silent=true), [read more](https://meta.discourse.org/t/-/358635/2?silent=true)). (Related plugin/topic mentioned: [read more](https://meta.discourse.org/t/-/394953/1?silent=true).)
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@awesomerobot** dug into the missing horizontal-scroll arrow in the composer toolbar overflow discussion, asking whether a theme might be interfering and confirming the current behavior: the arrow is intentionally hidden on touch devices—while questioning whether that assumption still holds for touch-enabled laptops ([read more](https://meta.discourse.org/t/-/398473/4?silent=true), [read more](https://meta.discourse.org/t/-/398473/6?silent=true)).
- **@renato** contributed two notable updates: a UX refinement idea for the scroll-arrow logic (consider “fine pointer” detection / narrower-screen heuristics) in the composer toolbar thread ([read more](https://meta.discourse.org/t/-/398473/7?silent=true)), and a maintenance closeout in the anchor-link bug report after it stopped reproducing post-fix ([read more](https://meta.discourse.org/t/-/397748/7?silent=true)).
- **@Falco** responded to DiscourseAI sentiment debugging by steering the investigation back to the documented self-hosting setup steps—effectively a “verify the pipeline end-to-end” checkpoint for anyone seeing missing sentiment output ([read more](https://meta.discourse.org/t/-/309270/18?silent=true), [read more](https://meta.discourse.org/t/-/334451/1?silent=true)).
* * *
If yesterday had a theme, it was _“everything scrolls sideways (including your debugging scope)”_—from hidden composer arrows to CDN hiccups and one more embed that refuses to inline.
---
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **48 new posts** across **3 new topics** in the last 24 hours, with fresh threads including a broken theme-component footer template ([read more](https://meta.discourse.org/t/-/398553/1?silent=true)), a sidebar-link URL-normalization bug report ([read more](https://meta.discourse.org/t/-/398537/1?silent=true)), and a question about proxying a forum via someone else’s URL ([read more](https://meta.discourse.org/t/-/398517/1?silent=true)).
- **Top users (posts / likes received)**
- **Recent activity highlights (source links)**
@das-g and @chapoi dug into a theme-component regression around deprecated connector patterns ([read more](https://meta.discourse.org/t/-/398553/7?silent=true)).
@merefield gave practical mitigation advice for unwanted proxy mirroring of a forum ([read more](https://meta.discourse.org/t/-/398517/4?silent=true)).
@dax noted that category-specific title placeholders are now available in core ([read more](https://meta.discourse.org/t/-/390841/19?silent=true)).
- **Other threads that saw notable replies (sampling of the day’s chatter)**:
ghost theme category metrics rendering ([read more](https://meta.discourse.org/t/-/398418/4?silent=true)), Cloudflare setup notes ([read more](https://meta.discourse.org/t/-/293405/28?silent=true)), ActivityPub actor lookup troubleshooting ([read more](https://meta.discourse.org/t/-/266794/479?silent=true)), Discourse AI tool timeout debugging ([read more](https://meta.discourse.org/t/-/398355/5?silent=true)), automation composer formatting quirks ([read more](https://meta.discourse.org/t/-/391347/10?silent=true)), login/sign-up errors with Discourse ID ([read more](https://meta.discourse.org/t/-/397895/17?silent=true)), AI sentiment backfill questions ([read more](https://meta.discourse.org/t/-/309270/20?silent=true)), and search/filtering with topic voting ([read more](https://meta.discourse.org/t/-/40121/317?silent=true)).
* * *
## Interesting Topics
### #Dev
- @das-g reported a theme “component” footer whose templating began rendering control directives literally, and @chapoi traced it to ongoing modernization work (notably deprecated `registerConnectorClass`) and recommended refactoring toward plugin outlets and modern theme patterns ([read more](https://meta.discourse.org/t/-/398553/1?silent=true), [read more](https://meta.discourse.org/t/-/398553/7?silent=true), [read more](https://meta.discourse.org/t/-/398553/9?silent=true), plus background: [read more](https://meta.discourse.org/t/-/32727/1?silent=true), [read more](https://meta.discourse.org/t/-/91966/1?silent=true), [read more](https://meta.discourse.org/t/-/93648/1?silent=true)).
### #Support
- In a #hosting-flavored security/privacy question, @ばこん asked how to prevent a “friend” from proxying their forum via another URL; the core guidance landed on _policy + enforcement_, up to making the forum private and banning obvious mirroring behavior ([read more](https://meta.discourse.org/t/-/398517/1?silent=true), [read more](https://meta.discourse.org/t/-/398517/4?silent=true)).
- A #ghost-theme issue showed category reply/view counts failing to render when viewing a category without subcategories; @chapoi pinpointed a missing outlet in that display context and later noted a structural change to make the custom elements consistently appear ([read more](https://meta.discourse.org/t/-/398418/3?silent=true), [read more](https://meta.discourse.org/t/-/398418/4?silent=true), [read more](https://meta.discourse.org/t/-/398418/7?silent=true)).
- A report in Chinese asked about Discourse AI tool-call timeouts (#ai); @Falco pushed for concrete details (which tool + what request) to move from symptoms to actionable debugging ([read more](https://meta.discourse.org/t/-/398355/3?silent=true), [read more](https://meta.discourse.org/t/-/398355/5?silent=true)).
- Automation formatting (#automation): @renato confirmed fixes related to escaping/formatting when pasting special markup (like `[wrap]`) into automation text fields, and discussed the tension between “rich editor expectations” and “automation wants raw-ish text” ([read more](https://meta.discourse.org/t/-/391347/10?silent=true)).
- A bug report described sidebar “custom link” normalization stripping the site hostname out of a query parameter for _external_ URLs—breaking redirect-style use cases—along with a workaround involving URL-encoding and DB edits ([read more](https://meta.discourse.org/t/-/398537/1?silent=true)).
- In ongoing Discourse ID troubleshooting (#discourse-id), @pmusaraj suggested regenerating credentials, then pivoted to investigating broader signup configuration after regeneration didn’t resolve 404s for new user creation ([read more](https://meta.discourse.org/t/-/397895/15?silent=true), [read more](https://meta.discourse.org/t/-/397895/17?silent=true)).
- Discourse AI Sentiment setup (#ai #ai-sentiment): a user confirmed dashboards were working but wanted deeper historical backfill; @Falco focused the conversation on what time range was actually backfilled so far (e.g., “last 60 days?”) before pushing further ([read more](https://meta.discourse.org/t/-/309270/19?silent=true), [read more](https://meta.discourse.org/t/-/309270/20?silent=true)).
- A regression report claimed “username + real name” display behavior changed in `2026.3.0-latest`; follow-up suggested checking [safe mode](https://meta.discourse.org/t/53504?silent=true) as a next diagnostic step ([read more](https://meta.discourse.org/t/-/398407/3?silent=true), [read more](https://meta.discourse.org/t/-/398407/4?silent=true)).
- A question on the floating search widget reported reversed character order when typing (#search #tablet) and asked why the topic was reclassified from “bug” to “support” ([read more](https://meta.discourse.org/t/-/398423/7?silent=true)).
### #ux
- Category creation UX (#categories): @dax highlighted that Discourse now supports **title placeholders per category** , and separately confirmed the capability is “now in core” for those looking to customize the topic-title prompt ([read more](https://meta.discourse.org/t/-/390841/19?silent=true), [read more](https://meta.discourse.org/t/-/205219/4?silent=true)).
- Another Chinese-language UX thread (#composer) showed that when the editor has “too many buttons,” later buttons can become inaccessible; testing in [safe mode](https://meta.discourse.org/t/53504?silent=true) affected whether the overflow/arrow UI appeared, suggesting theme/plugin interactions ([read more](https://meta.discourse.org/t/-/398473/8?silent=true)).
### #customization:plugin
- ActivityPub (#experimental #activitypub): @pmusaraj investigated an issue where an actor like `@announcements@meta.discourse.org` couldn’t be found, starting by narrowing down the Discourse version and confirming the actor resolved correctly elsewhere ([read more](https://meta.discourse.org/t/-/266794/479?silent=true)).
- Topic Voting: users asked for advanced search options tied to votes; the answer suggested using **filter parameters** (e.g., `order:votes`, `status:open`, `-tag:`) and even saving the filtered URL for others via the sidebar—also referencing a related closed thread for context ([read more](https://meta.discourse.org/t/-/40121/316?silent=true), [read more](https://meta.discourse.org/t/-/40121/317?silent=true), related: [read more](https://meta.discourse.org/t/-/272279/1?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@chapoi**
Investigated a theme-component regression where a footer template stopped rendering as expected, connecting it to deprecations and the Glimmer modernization path, and provided practical direction toward plugin outlets and theme docs ([read more](https://meta.discourse.org/t/-/398553/7?silent=true), [read more](https://meta.discourse.org/t/-/398553/9?silent=true)).
Also diagnosed a ghost theme edge case where reply/view widgets didn’t appear in certain category views, then followed up with an implementation change to make the elements render consistently ([read more](https://meta.discourse.org/t/-/398418/4?silent=true), [read more](https://meta.discourse.org/t/-/398418/7?silent=true)).
- **@dax**
Shared that Discourse now supports category-specific topic-title placeholders, including a pointer that the change has landed in core ([read more](https://meta.discourse.org/t/-/390841/19?silent=true), [read more](https://meta.discourse.org/t/-/205219/4?silent=true)).
- **@Falco**
Pressed for concrete reproduction details in a Discourse AI tools timeout report—focusing on _which tool_ and _what request_ to enable proper debugging ([read more](https://meta.discourse.org/t/-/398355/5?silent=true)).
Followed up on AI sentiment backfill expectations by clarifying what time window was actually populated (e.g., “last 60 days?”) before exploring extending history ([read more](https://meta.discourse.org/t/-/309270/20?silent=true)).
- **@pmusaraj**
Helped narrow down an ActivityPub actor discovery issue by asking about Discourse version and verifying expected behavior elsewhere ([read more](https://meta.discourse.org/t/-/266794/479?silent=true)).
Continued investigating Discourse ID signup failures by recommending regenerating credentials, then requesting a (sanitized) view of login-related site settings once that didn’t resolve the 404s ([read more](https://meta.discourse.org/t/-/397895/15?silent=true), [read more](https://meta.discourse.org/t/-/397895/17?silent=true)).
- **@renato**
Confirmed that automation-field escaping for special formatting (like `[wrap]`) should be improved after a merge, and explained how clipboard HTML payloads can cause the rich editor to “do the wrong thing” for automation-style inputs ([read more](https://meta.discourse.org/t/-/391347/10?silent=true)).
* * *
Yesterday’s vibe: if your footer suddenly starts printing template syntax and your votes need better filtering, at least Cloudflare and plugin outlets are there to keep the plot moving.
---
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
In the last 24 hours (2026-03-16 → 2026-03-17), Meta saw **97 new posts** across **14 new topics**. (See today’s new announcement on support category creation: [read more](https://meta.discourse.org/t/-/398338/1?silent=true))
**Top users (posts / likes, last 24h):**
- **@das-g** — **9 posts** , **8 likes** (theme dev + Glimmer troubleshooting: [read more](https://meta.discourse.org/t/-/398578/1?silent=true))
- **@Falco** — **6 posts** , **2 likes** (calendar + embeds fixes: [read more](https://meta.discourse.org/t/-/393203/5?silent=true))
- **@NateDhaliwal** — **6 posts** , **7 likes** (dev help + version guidance: [read more](https://meta.discourse.org/t/-/398578/2?silent=true))
- **@gingerbeardman** — **5 posts** , **4 likes** (mobile composer issue report: [read more](https://meta.discourse.org/t/-/398604/1?silent=true))
- **@chapoi** — **5 posts** , **4 likes** (support + dev guidance: [read more](https://meta.discourse.org/t/-/398648/2?silent=true))
- **@sam** — **4 posts** , **4 likes** (translation workflow + bug triage: [read more](https://meta.discourse.org/t/-/398585/2?silent=true))
- **@itsbhanusharma** — **4 posts** , **8 likes** (admin workflow clarification: [read more](https://meta.discourse.org/t/-/398627/2?silent=true))
- **@merefield** — **4 posts** , **5 likes** (self-hosting config pointers: [read more](https://meta.discourse.org/t/-/398601/3?silent=true))
- **@martin** — **3 posts** , **17 likes** (new feature + bugfix follow-up: [read more](https://meta.discourse.org/t/-/398338/1?silent=true))
- **@Moin** — **2 posts** , **4 likes** (review-queue strategy & dynamic groups: [read more](https://meta.discourse.org/t/-/398648/6?silent=true))
* * *
## Interesting Topics
### #Announcements
- **Support categories are now one-click configurable using Discourse Solved defaults.** @martin announced a streamlined “Support” category type that auto-enables solution-marking and sets sensible defaults, building on the longstanding #solved plugin foundation ([read more](https://meta.discourse.org/t/-/398338/1?silent=true); background on #solved: [read more](https://meta.discourse.org/t/-/30155/1?silent=true)).
- **Splash screen branding feedback continues (SVG sizing limits).** A follow-up in the splash branding announcement notes constraints around customizing SVG sizes for branded loading experiences ([read more](https://meta.discourse.org/t/-/395100/31?silent=true)).
### #Dev
- **Theme component naming conventions: “discourse-tc-\*” emerges as a community standard.** @das-g asked what’s recognizable on disk and in repos; @awesomerobot noted there’s no enforced convention, while others shared consistent prefixes like `discourse-theme-` vs `discourse-tc-` ([read more](https://meta.discourse.org/t/-/398572/1?silent=true)).
- **Glimmer theme component assets: using `assets/` + `settings.theme_uploads` to reference images.** @das-g worked through strict-mode template constraints, with @NateDhaliwal confirming assets in `assets/` are treated as uploads and can be referenced via theme upload settings ([read more](https://meta.discourse.org/t/-/398578/1?silent=true); the underlying “include assets” guide being discussed: [read more](https://meta.discourse.org/t/-/62459/1?silent=true)).
- **“Templating of my component broke” wrapped up with a documented working approach.** After iterative troubleshooting, @das-g posted a working resolution (and a repo commit) and discussed best practice around marking solutions with @chapoi ([read more](https://meta.discourse.org/t/-/398553/12?silent=true)).
- **A quick win: broken links in the Theme Developer Quick Reference were fixed.** A report that the theme/component directory links no longer worked led to a prompt correction ([read more](https://meta.discourse.org/t/-/110448/11?silent=true)).
### #Support
- **iOS / Hub composer sometimes becomes unresponsive while editing.** @gingerbeardman described an “unable to exit editing” state requiring an app force-quit; @chapoi and @awesomerobot compared notes and asked for version/repro details ([read more](https://meta.discourse.org/t/-/398604/1?silent=true)).
- **Per-user “force approval” isn’t built-in, but review-queue patterns (and dynamic groups) can approximate it.** @haydenjames wanted a per-user moderation switch; @chapoi confirmed no native toggle, and @Moin suggested a strategy using group-based approval plus #discourse-dynamic-groups ([read more](https://meta.discourse.org/t/-/398648/1?silent=true); the older plugin idea referenced: [read more](https://meta.discourse.org/t/-/58179/1?silent=true); the review-trigger overview: [read more](https://meta.discourse.org/t/-/328584/1?silent=true); dynamic groups: [read more](https://meta.discourse.org/t/-/365342/1?silent=true)).
- **Self-hosting uploads: nginx config changes inside the container don’t persist—use `app.yml` / supported overrides.** A 30MB PDF upload failed despite “512m” settings; the discussion moved toward durable config via supported mechanisms rather than editing container files directly ([read more](https://meta.discourse.org/t/-/398601/1?silent=true); the canonical “max upload size” instructions: [read more](https://meta.discourse.org/t/-/26435/1?silent=true)).
- **Replacing Discourse search with SearchUnify: feasibility questions raised.** A new thread asks whether the header search can be swapped or results can be delegated to an external enterprise search platform ([read more](https://meta.discourse.org/t/-/398650/1?silent=true)).
- **Onboarding for returning (inactive) users: can “Welcome back!” be paired with a calmer UI?** @emyoulation proposed a less overwhelming experience for dormant users, potentially via theming similar to approaches used to simplify UI for newcomers ([read more](https://meta.discourse.org/t/-/398584/1?silent=true); related “hide elements for new users” discussion: [read more](https://meta.discourse.org/t/-/254191/14?silent=true)).
- **Account compromise mitigation: admins want clearer UI for “nuke sessions / force reset” workflows.** A self-hosted admin described needing Rails console for email/password/session control; responses debated what’s already possible in the admin UI vs what should remain “power-user” territory ([read more](https://meta.discourse.org/t/-/398627/1?silent=true)).
- **Embedding Bunny Stream: allowlisting iframes solves it.** The solution centered on adding Bunny’s embed host to allowed iframe settings and embedding via `