# Riepilogo Quotidiano (13:00 UTC)
**URL:** https://meta.discourse.org/t/daily-summary-1pm-utc/291852
**Category:** Forum summaries
**Created:** [16 Gennaio 2024, 10:00pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852 "2024-01-16T22:00:28Z")
**Posts on this page:** 20
**Page:** 30
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [24 Aprile 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/808 "2026-04-24T13:01:20Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 54**
- **New topics (last 24h): 7**
**Top contributors (by posts/likes in the last 24h)**
| User | Posts | Likes |
| --- | --- | --- |
| @nicolsdennis | 4 | 17 |
| @Eviepayne | 5 | 4 |
| @Ed_S | 4 | 4 |
| @sam | 3 | 2 |
| @Lilly | 2 | 11 |
| @nat | 2 | 7 |
| @mcwumbly | 2 | 4 |
| @lindsey | 2 | 3 |
| @bmind | 1 | 4 |
| @piffy | 1 | 3 |
**Top contributors from the Discourse Team ([@team](https://meta.discourse.org/groups/team?silent=true))**: @nat (2 posts / 7 likes), @mcwumbly (2 / 4), @lindsey (2 / 3), @sam (3 / 2).
* * *
## Interesting Topics
### #Support
- @bmind reported that localized/translated pages were being hurt in search due to canonical handling, and @nat confirmed a core fix has shipped and will be included after updating ([read more](https://meta.discourse.org/t/-/401275/5?silent=true)). (Confirmation follow-up: [read more](https://meta.discourse.org/t/-/401275/7?silent=true))
- @Eviepayne flagged that the composer was ignoring `default_composition_mode`, and @sam walked through repro checks + [safe mode](https://meta.discourse.org/t/53504?silent=true) testing—ultimately pointing to a third-party plugin interaction as the likely cause ([read more](https://meta.discourse.org/t/-/401379/6?silent=true)). (Original report: [read more](https://meta.discourse.org/t/-/401379/1?silent=true))
- A busy community asked for “per-volunteer” archiving in the Support Mailbox so helpers can clear items from _their_ view without hiding it from everyone else—surfacing a workflow gap for shared inbox triage ([read more](https://meta.discourse.org/t/-/401361/1?silent=true)).
### #Announcements
- Discourse announced **simpler email subject lines** to reduce technical-looking clutter in inboxes, aiming to make communities feel less intimidating to non-technical members ([read more](https://meta.discourse.org/t/-/395927/1?silent=true)). A related concern: some communities rely on category cues in the subject; see also the request around template display options ([read more](https://meta.discourse.org/t/-/398772/1?silent=true)).
- In **Current Projects** , @lindsey noted that blog post styling components are now available for translation via Crowdin, unblocking localization work for those assets ([read more](https://meta.discourse.org/t/-/398565/14?silent=true)). (For broader roadmap context, the April projects thread was also referenced elsewhere: [read more](https://meta.discourse.org/t/-/401259/1?silent=true)).
- The **calendar subscription URL** work continues to mature: after positive feedback, there was agreement that key UI affordances “should be in the plugin itself,” with a pointer to interim solutions in an “extra buttons” companion topic ([read more](https://meta.discourse.org/t/-/398902/24?silent=true); [read more](https://meta.discourse.org/t/-/400503/1?silent=true)).
### #General
- A member proposed an **MMN (Meta Monthly Newsletter)** run by the community, but feedback questioned the value vs existing summaries and cautioned that “user/staff of the month” voting can become a popularity contest ([read more](https://meta.discourse.org/t/-/401408/1?silent=true); critique: [read more](https://meta.discourse.org/t/-/401408/4?silent=true)).
- @nicolsdennis shared a preview of **Domniq** , a Discourse-native Android+iOS app concept, including design explorations like app-wide custom color modes and chat UI styling ([read more](https://meta.discourse.org/t/-/401349/3?silent=true)). Related inspirations referenced: a chat bubble component ([read more](https://meta.discourse.org/t/-/286735/1?silent=true)) and the Horizon theme ([read more](https://meta.discourse.org/t/-/360486/1?silent=true)).
- In a second “Domniq” showcase, @nicolsdennis previewed a **premium landing page plugin** for unauthenticated visitors—hero layouts, live stats, FAQs, and configurable sections aimed at turning “front page” traffic into engaged members ([read more](https://meta.discourse.org/t/-/401394/1?silent=true)). (Companion app thread: [read more](https://meta.discourse.org/t/-/401349/1?silent=true))
### #Site feedback
- @mcwumbly proposed a clearer home for lighter “I made a thing” posts: use #General with the #show-and-tell tag for now, and revisit structure once patterns emerge ([read more](https://meta.discourse.org/t/-/401414/1?silent=true)). @piffy immediately sanity-checked the direction by sharing an embeddings-based topic clustering map experiment ([read more](https://meta.discourse.org/t/-/401414/2?silent=true)).
### #contribute:feature
- A feature request floated a new notification level called **“Obnoxious”** , but the discussion quickly narrowed to a practical ask: _thread-specific_ desktop notifications (not global browser push) so people can opt-in only where it matters ([read more](https://meta.discourse.org/t/-/401355/3?silent=true)).
- A thoughtful feature ideation explored protecting users during episodic unwellness (e.g., manic episodes): @mcwumbly suggested “draft it to a trusted friend” patterns and even the possibility of opt-in, just-in-time AI feedback (“you sure you want to post this?”) ([read more](https://meta.discourse.org/t/-/401050/4?silent=true)). @Ed_S added adjacent concepts like scheduled send / undo-send time windows ([read more](https://meta.discourse.org/t/-/401050/5?silent=true)).
- Self-serve login control came up again: a request asked whether it’s possible to disable local sign-ups (hide Sign Up without CSS) while avoiding tricky authentication combinations—pointing to prior reports about `invite only` + `auth skip create confirm` interactions and differences across auth providers ([read more](https://meta.discourse.org/t/-/401005/14?silent=true); related: [read more](https://meta.discourse.org/t/-/380885/1?silent=true); auth context: [read more](https://meta.discourse.org/t/-/304280/3?silent=true)).
### #development
- CI pipelines hit friction when the `minio_runner` install script failed to follow a redirect, breaking shared GitHub Actions workflows and preventing Rails system tests from even starting in some plugin repos ([read more](https://meta.discourse.org/t/-/401370/1?silent=true)).
### #Self-hosting
- Storage layout questions resurfaced: one admin asked whether `/var/discourse` and `/var/lib/docker` can live on different volumes, and follow-up clarified what’s actually consuming disk (notably the `shared/standalone` data vs Docker overlay/image layers) ([read more](https://meta.discourse.org/t/-/401332/3?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @nat confirmed a production-ready fix for translated pages + canonical SEO behavior and told the reporter the patch is available in the newest build ([read more](https://meta.discourse.org/t/-/401275/5?silent=true); update confirmation: [read more](https://meta.discourse.org/t/-/401275/7?silent=true)).
- @mcwumbly established lightweight guidance for “show and tell” posts—routing them to #General with #show-and-tell while Meta watches for patterns worth formalizing ([read more](https://meta.discourse.org/t/-/401414/1?silent=true)). They also contributed to the “future self / trusted friends” posting-safety brainstorm, suggesting DM drafts and even opt-in AI nudges ([read more](https://meta.discourse.org/t/-/401050/4?silent=true)).
- @lindsey published an announcement detailing how Discourse is simplifying default email subject lines and how communities can adopt the changes ([read more](https://meta.discourse.org/t/-/395927/1?silent=true)). They also shared a projects update: blog post styling components are now ready for translation in Crowdin ([read more](https://meta.discourse.org/t/-/398565/14?silent=true)).
- @sam helped debug a “composer ignores `default_composition_mode`” report, recommending [safe mode](https://meta.discourse.org/t/53504?silent=true) and identifying third-party plugin interference as the likely culprit ([read more](https://meta.discourse.org/t/-/401379/6?silent=true)).
* * *
If you survived the push for _“Obnoxious”_ notifications, at least your inbox gets a calmer ride with those newly simplified email subject lines. ([read more](https://meta.discourse.org/t/-/401355/3?silent=true); [read more](https://meta.discourse.org/t/-/395927/1?silent=true))
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [25 Aprile 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/809 "2026-04-25T13:01:47Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 68**
- **New topics (last 24h): 10**
**Top users (posts / likes in the last 24h)**
| User | Posts | Likes | Recently seen in |
| --- | --- | --- | --- |
| @Falco | 6 | 26 | Emoji search localization announcement ([read more](https://meta.discourse.org/t/-/401482/1?silent=true)) |
| @Canapin | 3 | 19 | Sharing forum customizations (#show-and-tell) ([read more](https://meta.discourse.org/t/-/401472/1?silent=true)) |
| @eisammy | 7 | 12 | Discussion on bot-populated communities ([read more](https://meta.discourse.org/t/-/401493/5?silent=true)) |
| @Lilly | 5 | 12 | Admin email-change UX quirks ([read more](https://meta.discourse.org/t/-/401441/2?silent=true)) |
| @kirupa | 4 | 10 | “Mostly-dead” forum revived with bots ([read more](https://meta.discourse.org/t/-/401493/1?silent=true)) |
| @fuse | 3 | 9 | Topic deletion / visibility “random thought” ([read more](https://meta.discourse.org/t/-/401491/1?silent=true)) |
| @merefield | 4 | 9 | Locations plugin prototype + sponsor access ([read more](https://meta.discourse.org/t/-/69742/1235?silent=true)) |
| @mcwumbly | 7 | 6 | Follow-up on deleted/private topic confusion ([read more](https://meta.discourse.org/t/-/401491/6?silent=true)) |
| @mcdanlj | 1 | 3 | [releases.discourse.org](http://releases.discourse.org) readability feedback ([read more](https://meta.discourse.org/t/-/399414/12?silent=true)) |
| @tobiaseigen | 2 | 2 | “Access denied” on email verification link ([read more](https://meta.discourse.org/t/-/401441/1?silent=true)) |
* * *
## Interesting Topics
### #Announcements
- **Emoji picker search now works in your language** — @Falco shipped multilingual emoji keyword search (48 languages), unblocking long-standing localization pain where emoji search was effectively English-only ([read more](https://meta.discourse.org/t/-/401482/1?silent=true)). Related context: the earlier request for translated aliases ([read more](https://meta.discourse.org/t/-/86641/1?silent=true)) and the older “how do I support other languages?” support thread now answered via the new feature ([read more](https://meta.discourse.org/t/-/197428/2?silent=true)).
- **Simpler email subject lines** — the email UX discussion continued around making subjects clearer by default (and what to keep, like the usefulness of `[PM]`) ([read more](https://meta.discourse.org/t/-/395927/3?silent=true)).
### #General
- **“I populated my (mostly-dead) Discourse forum with bots!”** — @kirupa shared a #show-and-tell experiment using AI bots with distinct personalities to generate topics and replies, sparking debate about _community vs. “Dead Internet” vibes_ and the practical value of a personalized “daily briefing” forum ([read more](https://meta.discourse.org/t/-/401493/1?silent=true)).
- **Random thought: notify contributors when a topic disappears** — @fuse wondered whether Discourse should PM or otherwise preserve contributors’ writing when a topic is deleted or becomes inaccessible (especially when you’ve written something substantial) ([read more](https://meta.discourse.org/t/-/401491/1?silent=true)).
- **Modifications/features I made on my forums (and why)** — @Canapin consolidated a set of pragmatic improvements they’ve built (including community-funding mechanics) and why each change helped, as a concrete “here’s what worked” #show-and-tell reference for other admins ([read more](https://meta.discourse.org/t/-/401472/1?silent=true)). Related: the donation progress bar component referenced in the write-up ([read more](https://meta.discourse.org/t/-/394184/1?silent=true)) and the broader “where should people share?” meta discussion about #show-and-tell culture/site structure ([read more](https://meta.discourse.org/t/-/401414/1?silent=true)).
- **[Releases.discourse.org](http://Releases.discourse.org) feedback & suggestions** — a quick but meaningful nod that recent changes made [releases.discourse.org](http://releases.discourse.org) “a lot easier to read,” reinforcing that polish work on ancillary Discourse properties gets noticed ([read more](https://meta.discourse.org/t/-/399414/12?silent=true)).
### #Support
- **Can a leaderboard top contributor have no topic or posts in their activity?** — a neat edge case: yes, if the leaderboard is counting private-category participation (or even reading), it can look like a user has “no activity” while still ranking highly ([read more](https://meta.discourse.org/t/-/401479/1?silent=true)). Related: @Falco pointed to external point-award integrations as another factor ([read more](https://meta.discourse.org/t/-/262968/1?silent=true)).
- **What happens to translations when an LLM changes?** — after a model deprecation and switching LLM parameters, the key clarification was that existing translations remain and only missing items should be translated—helpful for admins watching token usage and progress bars ([read more](https://meta.discourse.org/t/-/401478/1?silent=true)).
- **Videos and monetizing my Discourse community** — a “what’s possible?” thread about selling access to instructional racing videos via a Discourse community, with early guidance leaning toward offloading video hosting/storage complexity elsewhere ([read more](https://meta.discourse.org/t/-/401492/1?silent=true)).
- **AI triage examples not sent properly?** — an important Discourse AI / automation report: examples appeared to be interpreted as part of the content being evaluated, causing every post to get flagged (and the model citing the _example wiring details_ as if they were real) ([read more](https://meta.discourse.org/t/-/401508/1?silent=true)).
### #ux
- **Admin changing email address of a member is still quirky** — @tobiaseigen documented a confusing flow where email verification links fail with “Access Denied” while logged in as admin; workarounds include impersonation or alternative methods, but the UX mismatch versus admin expectations sparked discussion ([read more](https://meta.discourse.org/t/-/401441/1?silent=true)). Related: the console-based approach for certain cases ([read more](https://meta.discourse.org/t/-/42062/1?silent=true)).
### #contribute:feature
- **Tecnoblog’s Experience With Discourse Comments (Embedding)** — ongoing embed feedback included a serious “can’t type in the text field” issue (notably for the _first comment_ on mobile), Safari/iOS scroll quirks, and broader embed instrumentation concerns ([read more](https://meta.discourse.org/t/-/400721/34?silent=true)).
### #customization:plugin
- **Locations Plugin prototype + early access for sponsors** — @merefield shared a prototype preview and outlined a sponsorship-based early access path (with invites rolling out and a “fixes first” promise for backers) ([read more](https://meta.discourse.org/t/-/69742/1235?silent=true)).
- **Trading Buttons plugin appears broken after an update** — a report that a recent Discourse update removed category-setting options needed for the plugin UI to function, despite the plugin being enabled ([read more](https://meta.discourse.org/t/-/71308/130?silent=true)).
### #Community Building
- **Accessing Discourse DB with DBeaver** — a practical guide to safely exposing Postgres from a Dockerized Discourse for use with GUI clients (port mapping, firewalling, and switching auth to `scram-sha-256`, with an emphasis on private networking like Tailscale) ([read more](https://meta.discourse.org/t/-/401507/1?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@Falco**
- **@mcwumbly**
- **@chapoi**
* * *
_That’s a wrap—may tomorrow bring multilingual emoji searches, fewer disappearing topics, and bots that know when to stop posting._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [26 Aprile 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/810 "2026-04-26T13:01:18Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
Over the last 24 hours (2026-04-25 → 2026-04-26):
- **New posts:** 43
- **New topics:** 5
**Top contributors (posts • likes)**
(Links go to a representative recent post from each user.)
- **@Ginger_Marcus** — 3 posts • 5 likes — reflections on tightening edit windows to reduce “impulsive posting” in a sensitive moderation/UX discussion ([read more](https://meta.discourse.org/t/-/401050/7?silent=true))
- **@Falco** _(team)_ — 3 posts • 2 likes — guidance on #automation triage agents and how “examples” are actually injected into the prompt history ([read more](https://meta.discourse.org/t/-/401508/4?silent=true))
- **@darkpixlz** — 3 posts • 2 likes — launched a “shortlink router” utility and followed up on privacy/logging concerns ([read more](https://meta.discourse.org/t/-/401542/3?silent=true))
- **@kirupa** — 2 posts • 5 likes — shared implementation details for populating a forum with bots and content sources ([read more](https://meta.discourse.org/t/-/401493/14?silent=true))
- **@ted** — 2 posts • 5 likes — weighed in on guardrails for regrettable posting and later on monetization/legal implications ([read more](https://meta.discourse.org/t/-/401050/11?silent=true))
- **@nathank** — 1 post • 5 likes — excitement about the Meta theme rebuild and “Blocks API” direction ([read more](https://meta.discourse.org/t/-/400013/28?silent=true))
- **@Moin** — 1 post • 4 likes — pointed to the _revert_ control in wiki edit history (and who can actually use it) ([read more](https://meta.discourse.org/t/-/401524/2?silent=true))
- **@ondrej** — 1 post • 3 likes — clarified permissions: category mods/TL4 can’t revert revisions ([read more](https://meta.discourse.org/t/-/401524/4?silent=true))
- **@pfaffman** — 1 post • 3 likes — pragmatic self-hosting guidance on separating Docker/Discourse volumes ([read more](https://meta.discourse.org/t/-/401332/4?silent=true))
- **@RGJ** — 1 post • 2 likes — cautioned against framing episodic unwellness as “accountability training” ([read more](https://meta.discourse.org/t/-/401050/9?silent=true))
* * *
## Interesting Topics
### #contribute:feature
- @Ginger_Marcus shared a real-world moderation experiment: _shortening the edit window_ to make conversations more coherent (and reduce context drift after OP edits), while @RGJ pushed back on “accountability” framing for episodic unwellness; @ted noted adjacent use-cases like rage-bait or drunk posting ([read more](https://meta.discourse.org/t/-/401050/7?silent=true))
### #Support
- A quick “how do I roll back a wiki page?” turned into a permissions gotcha: @Moin described the revert UI, but @ondrej clarified **category moderators/TL4 don’t have revert rights** per the permissions reference ([read more](https://meta.discourse.org/t/-/401524/4?silent=true))
- Monetizing via gated video/content raised bigger questions than plugins: @ted highlighted that _paying creators_ can introduce **legal and operational complexity** , not just technical setup ([read more](https://meta.discourse.org/t/-/401492/4?silent=true))
- In #automation + #ai triage, @Falco recommended using a **“Triage with AI Agent”** and the `flag` tool instead of string-return prompts—then dug into why example messages were causing unintended “flag everything” behavior ([read more](https://meta.discourse.org/t/-/401508/2?silent=true))
- Translation workloads + LLM switching: @Falco suggested enabling **verbose logs** and checking the **AI API audit logs table** to reconcile high token usage with “no progress” stats ([read more](https://meta.discourse.org/t/-/401478/5?silent=true))
- OpenID Connect login nuance: a new thread asked whether `allowed email domains` is validated against the email returned by OIDC _at account creation time_ ([read more](https://meta.discourse.org/t/-/401552/1?silent=true))
- Discourse ID accounts: @mcwumbly confirmed that **recent changes now allow users to change username/name in user settings** , even when the account was created via Discourse ID ([read more](https://meta.discourse.org/t/-/395729/11?silent=true))
### #Self-hosting
- “Can `/var/discourse` and `/var/lib/docker` live on different volumes?” got a pragmatic answer: Discourse doesn’t care where Docker stores its data—optimize for maintainability and clarity first ([read more](https://meta.discourse.org/t/-/401332/4?silent=true))
- A HestiaCP install run hit multiple snags: port conflicts with 80/443 templates and a puzzling GitHub/network failure that the OP later traced to DNS resolver behavior (Cloudflare/Google DNS vs internal DNS) ([read more](https://meta.discourse.org/t/-/401528/2?silent=true))
### #customization:extras
- A new utility, **Discourse Shortlink Router** , proposes a “swap hostname, keep path” approach to sharing admin/support URLs—prompting immediate questions about trust, logs, and what data might be exposed ([read more](https://meta.discourse.org/t/-/401542/1?silent=true))
- The ICS → Discourse importer thread documented a subtle behavior: `--time-only-dedupe` isn’t strictly time-only because it still applies “close enough” location checks—leading to a helpful “signal vs noise” outcome for room changes vs feed churn ([read more](https://meta.discourse.org/t/-/381646/20?silent=true))
### #ux
- A brand-new UX concern: “Edit history visible to public” _doesn’t appear to cover author/owner changes_ on the first post/topic—raising questions about transparency, moderation workflows, and whether this is a bug vs missing feature ([read more](https://meta.discourse.org/t/-/401545/1?silent=true))
### #Site feedback
- Meta’s theme rebuild continues to generate excitement: @nathank called out how the new tooling could help Discourse move from “a website component” to “the full website,” especially for small orgs seeking a simpler stack ([read more](https://meta.discourse.org/t/-/400013/28?silent=true))
### #General
- A lively #show-and-tell: @kirupa described bootstrapping a “mostly-dead” forum with bots, curated sources, and plans to resurrect old topics with modern responses—plus discussion about translation using Discourse AI ([read more](https://meta.discourse.org/t/-/401493/14?silent=true))
### #customization:theme
- After upgrading to `v2026.4.0-latest` (Ember v6.10.1), a report in the **FKB Pro** theme thread shows a client-side failure: missing `ember-this-fallback/this-fallback-helper`, effectively breaking the forum UI until resolved ([read more](https://meta.discourse.org/t/-/234323/492?silent=true))
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@Falco** helped troubleshoot why AI triage “examples” were backfiring: they explained that examples are sent as _previous turns_, so they must mimic the **exact** expected model response (including what a tool call should look like) and asked which LLM was in use ([read more](https://meta.discourse.org/t/-/401508/4?silent=true)). They also suggested a cleaner architecture using `Triage with AI Agent` plus the `flag` tool ([read more](https://meta.discourse.org/t/-/401508/2?silent=true)). In a separate AI-translations thread, they advised turning on verbose logging and checking AI audit logs to verify translation progress vs token burn ([read more](https://meta.discourse.org/t/-/401478/5?silent=true)).
- **@mcwumbly** responded to concerns that public edit history doesn’t reflect author/owner changes, flagging it as likely a **bug or missing feature** and moved it to UX for discussion ([read more](https://meta.discourse.org/t/-/401545/2?silent=true)). They also confirmed a Discourse ID improvement: users can now change their username/name directly in settings after recent changes ([read more](https://meta.discourse.org/t/-/395729/11?silent=true)).
* * *
Yesterday, Meta proved two things: bots can revive sleepy communities, and a 60-second edit window can keep the mustard-fueled hot takes delightfully accountable.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [27 Aprile 2026, 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/811 "2026-04-27T13:02:21Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
**In the last 24 hours:** **50** new posts and **10** new topics (including [Kali Forums Bug](https://meta.discourse.org/t/-/401577/1?silent=true), [Decouple passwordless email login/signup…](https://meta.discourse.org/t/-/401556/1?silent=true), and [IPBv4 migration script issues](https://meta.discourse.org/t/-/401561/1?silent=true)).
### Top contributors (posts + likes in the last 24h)
| User | Posts | Likes | Recent reference |
| --- | --- | --- | --- |
| @Moin | 3 | 7 | Helped isolate a theme/customization issue via [Safe Mode](https://meta.discourse.org/t/53504?silent=true) in [Kali Forums Bug](https://meta.discourse.org/t/-/401577/2?silent=true) |
| @merefield | 1 | 3 | Shared a new 3D view update in [Community Network Visualisation](https://meta.discourse.org/t/-/184189/50?silent=true) |
| @Ethsim2 | 2 | 3 | Proposed “true local passwordless” auth config in [Decouple passwordless…](https://meta.discourse.org/t/-/401556/1?silent=true) |
| @Revan_Manaflı | 2 | 2 | Reported a “blue nameless button” UI glitch in [Kali Forums Bug](https://meta.discourse.org/t/-/401577/1?silent=true) |
| @NateDhaliwal | 2 | 2 | Flagged a mobile tag truncation issue in [Long tags are cut off at screen edge](https://meta.discourse.org/t/-/401585/1?silent=true) |
| @angus | 1 | 2 | Clarified [WP Discourse](https://github.com/discourse/wp-discourse) cookies behavior in [Cookie information request](https://meta.discourse.org/t/-/401592/2?silent=true) |
| @Lilly | 3 | 2 | Added compliance context (COPPA/GDPR) in [Age requirement for Discourse](https://meta.discourse.org/t/-/401602/3?silent=true) |
| @Canapin | 3 | 2 | Asked for clarity on gallery open behavior in [🖼 Topic Gallery](https://meta.discourse.org/t/-/394953/13?silent=true) |
| @RGJ | 2 | 2 | Explained core behavior around “automatic groups” in [Discourse Dynamic Groups](https://meta.discourse.org/t/-/365342/20?silent=true) |
| @tobiaseigen | 1 | 1 | Revived an older integration thread in [How to deploy a SSO bridge…](https://meta.discourse.org/t/-/110003/8?silent=true) |
_Team activity snapshot:_ @mcwumbly contributed in [new product launch community reconfig](https://meta.discourse.org/t/-/401562/2?silent=true) and a mobile UI report follow-up on [long titles](https://meta.discourse.org/t/-/401152/4?silent=true); @chapoi stepped in to close an off-scope support request in [Kali Forums Bug](https://meta.discourse.org/t/-/401577/5?silent=true).
* * *
## Interesting Topics
### #Support
- @Revan_Manaflı reported a strange profile/UI behavior (“blue, nameless button”) affecting a single Discourse instance; @Moin suggested confirming whether it reproduces elsewhere and using [Safe Mode](https://meta.discourse.org/t/53504?silent=true) to rule out customizations in [Kali Forums Bug](https://meta.discourse.org/t/-/401577/1?silent=true). The reporter confirmed it disappeared in [Safe Mode](https://meta.discourse.org/t/53504?silent=true), pointing to a theme/component issue rather than core ([safe mode reference](https://meta.discourse.org/t/-/53504/1?silent=true)).
- @ice.d asked whether Discourse _requires_ users to be 13+ and whether hosted vs self-hosted changes that requirement; @Lilly highlighted Meta’s ToS language and child-safety compliance considerations in [Age requirement for Discourse](https://meta.discourse.org/t/-/401602/1?silent=true). For policy context, the “volunteer moderators” section change was also noted recently in [What Changed in the META ToS (July 18, 2024)](https://meta.discourse.org/t/-/317201/9?silent=true) (and prior comparison thread: [read more](https://meta.discourse.org/t/-/303258/1?silent=true)).
- Incoming email workflows regressed for private categories: @hellekin described cases where email-to-category fails with `Email::Receiver::InsufficientTrustLevelError`, even when unknown-address email is allowed, in [Incoming email stopped working for private categories](https://meta.discourse.org/t/-/401590/1?silent=true).
- Search and AI tooling parity came up: @jrgong requested a native search filter to find posts by members of a group (and raised interest in aligning “researcher persona” search with core search) in [Search filter: Find posts by users of a group](https://meta.discourse.org/t/-/401605/1?silent=true). Background threads referenced include [Advanced search filters: posts by group](https://meta.discourse.org/t/-/250027/1?silent=true) and the AI persona/search discussion in [read more](https://meta.discourse.org/t/-/368942/1?silent=true).
- Debugging AI translation behavior: @RBoy enabled verbose translation logs and observed repeated retries that consumed daily token quotas, suggesting a potential loop or repeated job retries in [What happens to translations when LLM changes?](https://meta.discourse.org/t/-/401478/6?silent=true) (#ai).
### #contribute:feature
- A request to support **local, email-only passwordless auth** (magic-link login + signup) _without_ enabling local password authentication: @Ethsim2 outlined the desired configuration split in [Decouple passwordless email login/signup from enable local logins](https://meta.discourse.org/t/-/401556/1?silent=true) (#login). Discussion touched both UX (removing/clarifying password fields) and user education (password managers). For adjacent identity/auth threads, see [How to deploy a SSO bridge alongside a discourse\_docker deployment?](https://meta.discourse.org/t/-/110003/8?silent=true) and OAuth troubleshooting in [Oauth2 with GitHub howto](https://meta.discourse.org/t/-/358125/2?silent=true) (#oauth2 #github).
### #ux
- @sniper756 pointed out inconsistent “delete/discard” iconography between the composer vs editing an existing post in [编辑器删除图标不一致](https://meta.discourse.org/t/-/401571/1?silent=true); @NateDhaliwal suggested it may relate to an earlier discard-confirmation change in [Do you want to discard your post?](https://meta.discourse.org/t/-/399942/1?silent=true).
- Mobile tag display got attention: @NateDhaliwal reported that long/many tags can be clipped with no ellipsis, potentially connected to earlier tag layout changes, in [Long tags are cut off at screen edge](https://meta.discourse.org/t/-/401585/1?silent=true) (#mobile #tags). The suspected related thread is [If topic info is too long: tags are cut off and create a blank line](https://meta.discourse.org/t/-/400298/1?silent=true).
### #customization:plugin
- Group visibility/admin UX edge cases: @nathank noted that marking groups “automatic” removes the Membership tab entirely (making some admin edits awkward), and @RGJ clarified the behavior is core—then flagged potential plugin maintenance follow-up—in [Discourse Dynamic Groups](https://meta.discourse.org/t/-/365342/19?silent=true).
- Gallery navigation ergonomics: @Canapin asked whether the gallery icon should open from the _current/unread_ post rather than always from the start, especially on mobile, in [🖼 Topic Gallery](https://meta.discourse.org/t/-/394953/13?silent=true).
- API/content pipeline improvements: a follow-up on resolved image URLs and possible integration with MCP was raised in [Discourse to Markdown Plugin](https://meta.discourse.org/t/-/401199/5?silent=true) (#markdown #ai), with an explicit callout to MCP compatibility via [Discourse MCP is here](https://meta.discourse.org/t/-/386983/1?silent=true).
- Visualization niceties: the long-running visualization thread got an update with a “snazzy” **3D view option** shared by @merefield in [Community Network Visualisation](https://meta.discourse.org/t/-/184189/50?silent=true).
### #wordpress
- Cookie inventories and compliance: @miednr asked for a detailed cookie list attributable to the [WP Discourse](https://github.com/discourse/wp-discourse) plugin; @angus replied that the plugin doesn’t set its own cookies (noting WordPress auth cookies as standard behavior) in [Cookie information request](https://meta.discourse.org/t/-/401592/1?silent=true).
### #Self-hosting
- Migration gotchas from IPBv4: @Anonymous_Moose reported issues with avatar import completeness, user collisions preventing post migration, link rewriting, and partial reaction conversion in [IPBv4 migration script issues](https://meta.discourse.org/t/-/401561/1?silent=true) (#migrations-tooling).
### #community-building Building
- Community IA during a multi-product transition: @Bryce_Oishi asked how to reconfigure an existing community to support a new product launch; @mcwumbly started by clarifying whether this is a shift from one product to multiple, in [How do you reconfigure a community for a new product launch?](https://meta.discourse.org/t/-/401562/1?silent=true) (#customer-success).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @chapoi closed an off-scope support thread (site-specific theme/customization issue) after @Moin helped narrow it down using [Safe Mode](https://meta.discourse.org/t/53504?silent=true), in [Kali Forums Bug](https://meta.discourse.org/t/-/401577/5?silent=true).
- @mcwumbly asked clarifying product/organization questions to shape advice for a community information architecture change in [How do you reconfigure a community for a new product launch?](https://meta.discourse.org/t/-/401562/2?silent=true).
- @mcwumbly followed up on a mobile-title wrapping report, noting it appears fixed on current Meta themes and suggesting affected sites may need updates, in [标题过长，超出边界](https://meta.discourse.org/t/-/401152/4?silent=true) (#mobile).
* * *
Yesterday proved that [Safe Mode](https://meta.discourse.org/t/53504?silent=true) is still the quickest way to turn “mystery blue buttons” into actionable theme fixes—right as everyone else was busy debating magic-link logins and chasing down cookie lists.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [28 Aprile 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/812 "2026-04-28T13:01:46Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
**In the last 24 hours** , Meta saw **94 new posts** across **15 new topics** (compiled from activity in the threads linked below, e.g. [read more](https://meta.discourse.org/t/-/401602/1?silent=true), [read more](https://meta.discourse.org/t/-/401611/1?silent=true), [read more](https://meta.discourse.org/t/-/401629/1?silent=true)).
- **New posts:** 94
- **New topics:** 15 — quick index: [Support: age requirements](https://meta.discourse.org/t/-/401602/1?silent=true), [Bug: Explorer rows](https://meta.discourse.org/t/-/401611/1?silent=true), [Dev: theme + blocks skills](https://meta.discourse.org/t/-/401629/1?silent=true), [Marketplace: paid v2 build](https://meta.discourse.org/t/-/401688/1?silent=true), [Theme: Verso](https://meta.discourse.org/t/-/401635/1?silent=true), [Feature: share Data Explorer query](https://meta.discourse.org/t/-/401612/1?silent=true), [Support: category badge font color](https://meta.discourse.org/t/-/401679/1?silent=true), [Support (FR): notify events to a group](https://meta.discourse.org/t/-/401634/1?silent=true), [Bug: crawler middleware depth](https://meta.discourse.org/t/-/401658/1?silent=true), [Bug: automation + scheduled uploads](https://meta.discourse.org/t/-/401683/1?silent=true), [Support: code review plugin webhooks](https://meta.discourse.org/t/-/401673/1?silent=true), [Support: “force user to edit” workflow](https://meta.discourse.org/t/-/401681/1?silent=true), [Support (ZH): allow\_user\_api\_key?](https://meta.discourse.org/t/-/401671/1?silent=true), [Community Building: missing allow\_user\_api\_key](https://meta.discourse.org/t/-/401706/1?silent=true), [Self-hosting: docker without Let’s Encrypt](https://meta.discourse.org/t/-/401632/1?silent=true).
### Top users (posts + likes in the last 24h)
| User | Posts | Likes |
| --- | --- | --- |
| **@Lilly** | 13 | 19 |
| **@manuel** | 4 | 17 |
| **@ganncamp** | 4 | 12 |
| **@Falco** | 3 | 12 |
| **@pmusaraj** | 1 | 10 |
| **@pfaffman** | 4 | 6 |
| **@awesomerobot** | 1 | 5 |
| **@supermathie** | 1 | 4 |
| **@RGJ** | 2 | 4 |
| **@nat** | 2 | 4 |
_(Notable team presence: @manuel, @Falco, @pmusaraj, @awesomerobot, @supermathie, @nat, @chapoi across the topics cited above — e.g. [read more](https://meta.discourse.org/t/-/401629/1?silent=true), [read more](https://meta.discourse.org/t/-/401611/6?silent=true), [read more](https://meta.discourse.org/t/-/401679/2?silent=true))._
* * *
## Interesting Topics
#### #Support
- @ice.d asked how **age requirements / age verification** interact with self-hosted vs CDCK-hosted sites, and @supermathie pointed to hosting terms and “Special Data Regulations” constraints in the discussion on [age requirement for Discourse](https://meta.discourse.org/t/-/401602/8?silent=true).
(Also: @awesomerobot clarified where “talk to your government” fits when regulations apply to hosting regions [read more](https://meta.discourse.org/t/-/401602/11?silent=true).)
- A theme/component interaction after updating to 2026.4.0 caused **category badge text color** to change while scrolling; @chapoi suggested [safe mode](https://meta.discourse.org/t/53504?silent=true) and inspection steps, and @Lilly shared a quick CSS fix in [issue with font colour in category badges](https://meta.discourse.org/t/-/401679/5?silent=true).
Follow-up: @chapoi said the team would investigate root cause [read more](https://meta.discourse.org/t/-/401679/7?silent=true).
- A new admin asked for a **“send it back to the author to rewrite it”** flow for incomplete/low-quality/AI-ish topics in [how to force a topic to be edited by the user](https://meta.discourse.org/t/-/401681/1?silent=true).
This one is likely to evolve into a moderation-workflow conversation (flags, staff messages, slow mode, approval queues, etc.) as the thread develops [read more](https://meta.discourse.org/t/-/401681/1?silent=true).
- A GitHub → Discourse integration attempt hit a snag: issue creation posts fine, but **issue comment webhooks don’t appear in Discourse** in [Discourse Code Review Questions](https://meta.discourse.org/t/-/401673/1?silent=true).
Context-wise, the asker is comparing the Code Review plugin to the older GitHub integration plugin docs/threads [read more](https://meta.discourse.org/t/-/401673/1?silent=true).
- Accessibility scanning surfaced that **custom badge images may be missing alt text** , prompting a question about whether this needs core changes or admin-side work in [Custom Badges are not applying Alt Text](https://meta.discourse.org/t/-/401648/1?silent=true).
This is a classic “is the HTML attribute missing in render, or can the badge UI supply it?” investigation [read more](https://meta.discourse.org/t/-/401648/1?silent=true).
- Two parallel threads (Chinese + English) asked where the master switch for **User API Key auth** went: [Allow\_user\_api\_key这个设置在哪开启](https://meta.discourse.org/t/-/401671/2?silent=true) and [How to enable allow\_user\_api\_key site setting which is missing…](https://meta.discourse.org/t/-/401706/1?silent=true).
@NateDhaliwal pointed to nearby setting names and _hidden site settings_ mechanics [read more](https://meta.discourse.org/t/-/401671/2?silent=true), which ties into the docs on hidden settings [read more](https://meta.discourse.org/t/-/308773/1?silent=true).
#### #bug
- [Data Explorer](https://meta.discourse.org/t/32566?silent=true) users reported that **query results appear capped to a tiny scrollable viewport** (effectively “5 rows”) regardless of result size in [Explorer reports limited to 5 rows…](https://meta.discourse.org/t/-/401611/1?silent=true).
After @Lilly offered a CSS workaround and a pointer to the SCSS in the plugin [read more](https://meta.discourse.org/t/-/401611/5?silent=true), @nat confirmed a fix was in progress [read more](https://meta.discourse.org/t/-/401611/6?silent=true) and later posted that it was **fixed and deployed** [read more](https://meta.discourse.org/t/-/401611/8?silent=true).
- A crawler-related error appeared post-upgrade: **`ArgumentError (Document tree depth limit exceeded)`** in middleware logs, likely triggered by bots requesting uploaded assets, in [Middleware - document tree depth exceeded](https://meta.discourse.org/t/-/401658/1?silent=true).
@Falco asked for a reproducible page/request to debug the culprit [read more](https://meta.discourse.org/t/-/401658/2?silent=true).
- Scheduling via the Automation plugin seems to break **image uploads in planned topics** (upload succeeds in composer briefly, then flips to “Upload failed”) in [Picture uploads broken, when planning to create a Thread](https://meta.discourse.org/t/-/401683/1?silent=true).
The thread also compares workarounds like core topic timers ([scheduling topics for future publication](https://meta.discourse.org/t/-/60731/1?silent=true)) versus Automation and how this interacts with homepage featured-topic flows ([Homepage feature](https://meta.discourse.org/t/-/144264/1?silent=true)).
#### #development
- @manuel published a repo of **Claude Code “skills” for theme authoring and the Blocks API** , including reference material and an example theme, in [Skills for authoring themes and blocks](https://meta.discourse.org/t/-/401629/1?silent=true).
In follow-up, @manuel explained how Blocks shift theme customizations toward “layout frames” per outlet and showed where initializer-driven layouts live [read more](https://meta.discourse.org/t/-/401629/5?silent=true).
- CI friction popped up again around dev tooling, with a report that a **Minio installer breaks CI** affecting workflows in [Minio installer breaks CI](https://meta.discourse.org/t/-/401370/2?silent=true).
This kind of thread is a bellwether for “dev environment parity” work [read more](https://meta.discourse.org/t/-/401370/1?silent=true).
#### #customization:theme
- A new lightweight editorial theme dropped: **Verso Theme** , emphasizing soft colors and minimal CSS-only changes, shared by @pmusaraj in [Verso Theme](https://meta.discourse.org/t/-/401635/1?silent=true).
The release post also links back to foundational theme docs like [How to install a theme or theme component](https://meta.discourse.org/t/-/63682/1?silent=true) and the [Beginner’s guide to using Discourse Themes](https://meta.discourse.org/t/-/91966/1?silent=true).
#### #contribute:feature
- Admin ergonomics for reporting got attention: @ganncamp proposed a better way to **share [Data Explorer](https://meta.discourse.org/t/32566?silent=true) queries** without forcing admins to manually hunt down group report URLs, in [Sharing a Data Explorer Query](https://meta.discourse.org/t/-/401612/1?silent=true).
@Lilly suggested a deterministic `/g/.../reports/...` pattern and hinted at a possible PR (plus a UX need to show which groups a query is shared with) [read more](https://meta.discourse.org/t/-/401612/2?silent=true).
- Embedding/Comments users confirmed a fix landed, but continued discussing a lingering **horizontal scroll on mobile** in [Tecnoblog’s Experience With Discourse Comments](https://meta.discourse.org/t/-/400721/38?silent=true).
@Falco couldn’t reproduce on-device and shared screenshots while investigating [read more](https://meta.discourse.org/t/-/400721/38?silent=true).
#### #Marketplace
- A “paid build” request sparked healthy scope/budget reality checks: a community platform owner requested help for a v2 launch (theme QA + custom member portal/profile work) in [[Paid] Discoure Community Platform - development for v2](https://meta.discourse.org/t/-/401688/1?silent=true).
The thread quickly focused on clarifying milestones, fragility of nav injection, and realistic pricing expectations [read more](https://meta.discourse.org/t/-/401688/6?silent=true).
#### #Self-hosting
- A self-hoster asked how to run Discourse behind an external reverse proxy and **disable Let’s Encrypt in the docker setup** in [Fresh install without lets-encrypt on docker](https://meta.discourse.org/t/-/401632/1?silent=true).
The canonical reference thread often cited for this area is “Allow SSL/HTTPS for your Discourse Docker setup” [read more](https://meta.discourse.org/t/-/13847/1?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@nat** jumped into the [Data Explorer](https://meta.discourse.org/t/32566?silent=true) UI regression report, acknowledged the issue and then confirmed it was **fixed and deployed** in [Explorer reports limited to 5 rows…](https://meta.discourse.org/t/-/401611/8?silent=true) (initial response: [read more](https://meta.discourse.org/t/-/401611/6?silent=true)).
- **@manuel** launched the new theme/block authoring “skills” resource and followed up with implementation guidance around BlockOutlets, layout frames, and initializer structure in [Skills for authoring themes and blocks](https://meta.discourse.org/t/-/401629/1?silent=true) and [follow-up details](https://meta.discourse.org/t/-/401629/5?silent=true).
He also cross-linked this work into Meta’s ongoing redesign conversations: [Rebuilding the Meta Branded theme…](https://meta.discourse.org/t/-/400013/29?silent=true) and [Updates to the Meta Branded theme homepage](https://meta.discourse.org/t/-/401100/28?silent=true).
- **@Falco** handled both policy/clarification and bug triage: he clarified hosting constraints and self-hosting freedom in [Age requirement for Discourse](https://meta.discourse.org/t/-/401602/6?silent=true), requested repro details for a crawler middleware error in [Middleware - document tree depth exceeded](https://meta.discourse.org/t/-/401658/2?silent=true), and continued troubleshooting embed/mobile overflow reports in [Tecnoblog’s Experience With Discourse Comments](https://meta.discourse.org/t/-/400721/38?silent=true).
- **@supermathie** provided the key legal/terms pointer for hosted customers around “Special Data Regulations” (including COPPA) in [Age requirement for Discourse](https://meta.discourse.org/t/-/401602/8?silent=true), grounding the discussion in the actual contractual clause.
- **@awesomerobot** added an operational note on compliance realities for hosted services—where regulation applies, CDCK must comply, and feedback is best directed at lawmakers—in [Age requirement for Discourse](https://meta.discourse.org/t/-/401602/11?silent=true).
- **@pmusaraj** shipped and showcased a new official-ish theme entry with install + getting-started references in [Verso Theme](https://meta.discourse.org/t/-/401635/1?silent=true), expanding the “lightweight theme” ecosystem and giving admins another clean baseline option.
- **@chapoi** led the first-line debugging workflow ([safe mode](https://meta.discourse.org/t/53504?silent=true), theme identification, inspector screenshots) and committed to investigating root cause in [Issue with font colour in category badges](https://meta.discourse.org/t/-/401679/2?silent=true) and [follow-up](https://meta.discourse.org/t/-/401679/7?silent=true).
* * *
_That’s a wrap—may your [Data Explorer](https://meta.discourse.org/t/32566?silent=true) tables grow taller than five rows, your category badge text stay readable while scrolling, and your Blocks layouts snap neatly into place._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [29 Aprile 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/813 "2026-04-29T13:01:44Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 72**
- **New topics (last 24h): 5**
- Topic Voting improvements: new badges (#Announcements, #badges #topic-voting): [read more](https://meta.discourse.org/t/-/401731/1?silent=true)
- April 2026 monthly release (#Announcements, #release-notes): [read more](https://meta.discourse.org/t/-/401718/1?silent=true)
- Default changes for trust level 3 requirements (#Announcements, #trust-levels): [read more](https://meta.discourse.org/t/-/397098/1?silent=true)
- Links to Mediawiki image pages break in oneboxes (#bug, #onebox): [read more](https://meta.discourse.org/t/-/401771/1?silent=true)
- AI for Enterprise – Office Hours Replay (#events, #webinar #office-hours): [read more](https://meta.discourse.org/t/-/401737/1?silent=true)
**Top contributors (posts + likes received on recent posts)**
| User | Posts | Likes | Where they were active |
| --- | --- | --- | --- |
| @lindsey | 8 | 29 | Announced new Topic Voting badges and enabled them on Meta: [read more](https://meta.discourse.org/t/-/401731/1?silent=true) |
| @putty | 6 | 6 | Shared moderation/workflow ideas for “request edit” via flags: [read more](https://meta.discourse.org/t/-/401681/4?silent=true) |
| @pfaffman | 4 | 4 | Gave maintainability guidance on theme/dev conventions in a Marketplace request: [read more](https://meta.discourse.org/t/-/401688/11?silent=true) |
| @Lilly | 3 | 7 | Provided CSS approach to limit a custom flag option to staff UI: [read more](https://meta.discourse.org/t/-/401681/10?silent=true) |
| @Thiago_Mobilon | 3 | 6 | Reported iOS horizontal scroll behavior in embedded comments: [read more](https://meta.discourse.org/t/-/400721/41?silent=true) |
| @pmusaraj | 3 | 5 | Narrowed a repro case + linked an upstream fix for the scroll issue: [read more](https://meta.discourse.org/t/-/400721/45?silent=true) |
| @david | 2 | 14 | Published the April 2026 release notes pointer: [read more](https://meta.discourse.org/t/-/401718/1?silent=true) |
| @HAWK | 2 | 5 | Clarified UK OSA/DSA compliance scope for Discourse sites: [read more](https://meta.discourse.org/t/-/401602/17?silent=true) |
| @darkpixlz | 2 | 5 | Asked about enabling new badges + noted backfill behavior: [read more](https://meta.discourse.org/t/-/401731/2?silent=true) |
| @martin | 1 | 6 | Proposed new defaults for TL3 requirements behind an upcoming change: [read more](https://meta.discourse.org/t/-/397098/1?silent=true) |
* * *
## Interesting Topics
### #Announcements
- @lindsey introduced **four new Topic Voting badges** (Daydreamer/Brainstormer/Innovator/Visionary) to celebrate ideas that attract votes, then flipped them on for Meta; follow-up clarified **backfill + notification rules** (only notify if earned in last 2 weeks, and only the highest badge if multiple thresholds are met). [read more](https://meta.discourse.org/t/-/401731/1?silent=true)
Related context: earlier Topic Voting improvements: [read more](https://meta.discourse.org/t/-/401156/1?silent=true) and long-running “Vote Notifications” discussion: [read more](https://meta.discourse.org/t/-/118712/1?silent=true)
- The **April 2026 monthly release** dropped, with @david pointing admins to the full 2026.4 changelog for details on what shipped. [read more](https://meta.discourse.org/t/-/401718/1?silent=true)
- @martin announced an **upcoming change** to make TL3 achievable on very active forums by reducing viewed/read caps and increasing minimum promotion duration (defaults only; manual overrides remain untouched). [read more](https://meta.discourse.org/t/-/397098/1?silent=true)
### #contribute:feature
- In an embedded-comments rollout, @Thiago_Mobilon shared screenshots of **horizontal scrolling on iOS** that seemed to affect admin sessions; @pmusaraj confirmed the “admin-only” angle and pointed to a core fix via PR. [read more](https://meta.discourse.org/t/-/400721/41?silent=true)
- A long-running gamification request got a quick victory lap: @Falco noted **per-leaderboard scoring values** were merged, and @Lilly highlighted the new granular scoring configuration options. [read more](https://meta.discourse.org/t/-/264619/10?silent=true)
### #Support
- A moderation workflow pain point: requesting that a user **must edit** a topic before it can proceed. Suggestions ranged from approvals to converting to PMs, but the most practical path discussed was using **custom flags** , plus UI-limiting them to staff via CSS. [read more](https://meta.discourse.org/t/-/401681/6?silent=true)
Supporting links: category-level approvals flexibility: [read more](https://meta.discourse.org/t/-/401132/1?silent=true) and the “staff-only custom flag” CSS approach: [read more](https://meta.discourse.org/t/-/401681/10?silent=true)
- “Age requirement for Discourse” turned into a compliance reality-check: @HAWK clarified **UK Online Safety Act scope** for U2U platforms (and noted DSA requirements in the EU), emphasizing that jurisdictional exposure matters even for self-hosters. [read more](https://meta.discourse.org/t/-/401602/17?silent=true)
- A Chinese-language support thread asked where to enable `allow_user_api_key`; the resolution was simply pointing to the **User API Keys specification** doc topic. [read more](https://meta.discourse.org/t/-/401671/9?silent=true)
Reference: the spec itself: [read more](https://meta.discourse.org/t/-/48536/1?silent=true)
- Event notifications in French (“Notifier un évènement à un groupe”) surfaced confusion around **bulk invitations/notifications** where only the first user seemed to receive the invite, prompting a call to rethink group notification flows. [read more](https://meta.discourse.org/t/-/401634/14?silent=true)
### #events
- Discourse shared an **Office Hours replay** focused on _Discourse AI for Enterprise_, covering semantic/conversational search and automation patterns for moderation and ops work. [read more](https://meta.discourse.org/t/-/401737/1?silent=true)
Related: the webinar/office-hours program context: [read more](https://meta.discourse.org/t/-/399640/1?silent=true)
### #ux
- The calendar/events UX thread about “all day events” effectively got closed out by a now-shipped **All day event checkbox** in the create-event modal, removing the “00:00 confusion” problem. [read more](https://meta.discourse.org/t/-/393495/4?silent=true)
Related feature request that’s now completed: [read more](https://meta.discourse.org/t/-/272052/1?silent=true)
- Another calendar UX improvement also landed: event exports now include **event descriptions in the `.ics` file** , improving the “save to calendar” experience. [read more](https://meta.discourse.org/t/-/384713/5?silent=true)
- A completed calendar request was formally closed, with an offer to split follow-ups into a new feature topic if needed (good housekeeping that keeps feature scopes clean). [read more](https://meta.discourse.org/t/-/387389/12?silent=true)
### #bug
- Oneboxing edge case: MediaWiki-style image _HTML pages_ sometimes break oneboxes (especially on certain MediaWiki hosts), and the suggestion was to detect `Content-Type: text/html` to avoid treating it as an image. [read more](https://meta.discourse.org/t/-/401771/1?silent=true)
- A “document tree depth exceeded” middleware issue got **a couple fixes** linked directly to PRs, with @Falco flagging it for review/visibility. [read more](https://meta.discourse.org/t/-/401658/5?silent=true)
### #customization:theme component
- The “Video Upload to YouTube and Vimeo” theme component thread progressed toward **permission scoping** : multiple folks emphasized restricting upload access by group to prevent abuse, and @Arkshine discussed Vimeo OAuth work so uploads can go to a _user’s_ Vimeo space. [read more](https://meta.discourse.org/t/-/170079/63?silent=true)
### #customization:plugin
- The “Discourse to Markdown” plugin discussion explored a clean integration path with **Discourse MCP** : try `Accept: text/markdown` first, then fall back to JSON API with `include_raw=true`. [read more](https://meta.discourse.org/t/-/401199/6?silent=true)
Related: Discourse MCP announcement thread: [read more](https://meta.discourse.org/t/-/386983/1?silent=true)
### #community-building Building
- A fresh, practical write-up shared a lightweight pattern for using Discourse as an **LMS/course tracker** built around categories/topics + Docs, with a small plugin + theme component to compensate for “notification decay” in lesson progress. [read more](https://meta.discourse.org/t/-/52633/26?silent=true)
Dependency referenced: Doc Categories plugin: [read more](https://meta.discourse.org/t/-/322376/1?silent=true)
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @lindsey shipped and enabled the new **Topic Voting badges** , then clarified how the **badge backfill + notification throttling** works to avoid retroactive notification spam. [read more](https://meta.discourse.org/t/-/401731/1?silent=true) and notification behavior detail: [read more](https://meta.discourse.org/t/-/401731/6?silent=true)
Also closed the loop on calendar UX improvements by pointing to shipped solutions for **all-day events** : [read more](https://meta.discourse.org/t/-/393495/4?silent=true) and `.ics` **event descriptions** : [read more](https://meta.discourse.org/t/-/384713/5?silent=true), and wrapped up a completed calendar-default-view request: [read more](https://meta.discourse.org/t/-/387389/12?silent=true)
- @david published the pointer for the **2026.4 (April 2026) release notes**. [read more](https://meta.discourse.org/t/-/401718/1?silent=true)
He also added an important implementation note elsewhere: **group sync is now available for OIDC** , pointing admins to the plugin topic and changelog. [read more](https://meta.discourse.org/t/-/175950/34?silent=true) (referencing the OIDC plugin’s “group sync” documentation: [read more](https://meta.discourse.org/t/-/103632/1?silent=true))
- @martin proposed an “upcoming change” to adjust **TL3 default requirements** , reducing caps for topics viewed/posts read while increasing minimum duration—aimed at very active communities where TL3 becomes unreachable. [read more](https://meta.discourse.org/t/-/397098/1?silent=true)
- @HAWK provided jurisdiction-specific clarification on **UK OSA** applicability (and noted DSA considerations), emphasizing that sites “may have users from” regulated regions and should plan compliance accordingly. [read more](https://meta.discourse.org/t/-/401602/17?silent=true)
- @pmusaraj helped narrow down an embedded-comments **horizontal scroll** issue to an admin-context repro and linked the upstream fix PR that should resolve it. [read more](https://meta.discourse.org/t/-/400721/45?silent=true)
- @Danielle shared the **AI for Enterprise Office Hours replay** , outlining how AI search and automated moderation aim to remove repetitive work while keeping humans in the loop. [read more](https://meta.discourse.org/t/-/401737/1?silent=true)
- @Falco flagged multiple “this is now fixed/shipped” updates across the day:
- @fzngagan outlined a practical moderation workaround for “force user edits” using the flag system’s **Hide Post** flow (while noting limitations around custom messaging), and pointed back to approvals as the more proactive approach. [read more](https://meta.discourse.org/t/-/401681/5?silent=true)
* * *
If yesterday’s Meta had a theme, it was “ship the badges, fix the scroll, and let calendars finally have all-day events without doing midnight math.”
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [30 Aprile 2026, 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/814 "2026-04-30T13:02:35Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 61**
- **New topics (last 24h): 10**
**Top contributors (posts / likes)**
(Each name includes a recent in-window reference post.)
| User | Posts | Likes | Recently seen in |
| --- | --- | --- | --- |
| @RGJ | 5 | 8 | Invite UX edge cases: [read more](https://meta.discourse.org/t/-/401819/1?silent=true) |
| @Moin | 5 | 7 | Infinite scroll + homepage options: [read more](https://meta.discourse.org/t/-/401894/3?silent=true) |
| @Lilly | 4 | 6 | Invite button UX mismatch: [read more](https://meta.discourse.org/t/-/401819/3?silent=true) |
| @pfaffman | 3 | 6 | Theme fix + PR pointer: [read more](https://meta.discourse.org/t/-/234323/495?silent=true) |
| @martin | 2 | 3 | TL3 default behavior clarified: [read more](https://meta.discourse.org/t/-/397098/8?silent=true) |
| @Richie | 2 | 2 | Email subject line nuance: [read more](https://meta.discourse.org/t/-/395927/4?silent=true) |
| @nathank | 2 | 4 | “This has always irked me” re: invites: [read more](https://meta.discourse.org/t/-/401819/4?silent=true) |
| @josir | 1 | 3 | Docker SSL/LE workaround documented: [read more](https://meta.discourse.org/t/-/401632/2?silent=true) |
| @awesomerobot | 1 | 3 | Privacy risks of age verification: [read more](https://meta.discourse.org/t/-/401602/27?silent=true) |
| @system | 1 | 3 | New Discover post discussion: [read more](https://meta.discourse.org/t/-/401884/1?silent=true) |
* * *
## Interesting Topics
### #Support
- @RGJ and others debated what an “age requirement” _should_ mean in practice—ranging from parental responsibility to privacy-preserving verification—while @awesomerobot highlighted the risk profile of third-party identity services and why zero-knowledge approaches may reduce retained data exposure ([read more](https://meta.discourse.org/t/-/401602/27?silent=true)).
Related: existing “enter your age” UI approaches like [Discourse age check](https://meta.discourse.org/t/-/397002/1?silent=true) also resurfaced as a lower-stakes alternative.
- A newly-migrated (52k-topic) community asked for alternatives to **infinite scroll** so their footer stays reachable; @chapoi stated pagination isn’t on the roadmap, while others suggested shifting the homepage to categories or rethinking footer importance ([read more](https://meta.discourse.org/t/-/401894/2?silent=true)).
Related: footer workarounds and components were referenced (e.g. [Easy Responsive Footer](https://meta.discourse.org/t/-/95818/1?silent=true)).
- A Windows 7 compatibility detour turned into a practical question: can admins customize the “unsupported browser” messaging to point users at viable alternatives? @Moin explained it’s a static HTML view plus an editable text string (`js.browser_update`) and suggested testing via old browsers/BrowserStack ([read more](https://meta.discourse.org/t/-/400384/18?silent=true)).
Related: what users see on old browsers was demoed here: [read more](https://meta.discourse.org/t/-/381666/3?silent=true), and the broader text customization guide is here: [read more](https://meta.discourse.org/t/-/36092/1?silent=true).
* * *
### #ux
- A UX paper-cut: **invite creation controls appear on other users’ profiles** , but the invite is still created/sent as the clicking user—making the placement misleading and “irk-y” to multiple admins ([read more](https://meta.discourse.org/t/-/401819/1?silent=true)).
The core mismatch (“looks like it’s on their behalf, but isn’t”) was spelled out clearly by @Lilly ([read more](https://meta.discourse.org/t/-/401819/3?silent=true)).
- A closely-related UX issue: even when a user’s public profile is hidden, an **Invite tab** can still show (even though it doesn’t leak hidden info), creating confusing navigation and expectations ([read more](https://meta.discourse.org/t/-/401818/1?silent=true)).
Cross-reference to the underlying behavior thread: [read more](https://meta.discourse.org/t/-/401819/1?silent=true).
* * *
### #Announcements
- The announcement about **default changes for Trust Level 3 requirements** prompted clarification on how admin overrides behave; @martin confirmed existing admin-set values are preserved, and “Reset” will reveal the new defaults when the upcoming change is enabled ([read more](https://meta.discourse.org/t/-/397098/8?silent=true)).
- On **simpler email subject lines** , discussion centered on whether PM-vs-public context _needs_ to be present in email subjects; participants argued that email clients can obscure the distinction even if the web UI makes it clear ([read more](https://meta.discourse.org/t/-/395927/5?silent=true)).
* * *
### #bug
- A self-hosting performance tweak became a debugging thread: adding the `enable-ruby-yjit.yml` template set `RUBY_YJIT_ENABLE=1`, but the reporter still observed YJIT disabled in runtime checks; the back-and-forth focused on whether the test method was checking the “right Ruby process” and what might be overriding startup behavior ([read more](https://meta.discourse.org/t/-/401815/1?silent=true)).
- A moderation edge case: a **flagged post** (that originally created a topic) became hard to restore after the author was pushed to TL0 and locked; restoring failed until the author was unlocked and moved back to TL1. The request: give admins clearer UI guidance instead of a generic error ([read more](https://meta.discourse.org/t/-/401900/1?silent=true)).
- A #chat notifications anomaly: a user reported being “pinged” multiple times (8) by what should have been a single mention, with all notifications pointing to the same message ([read more](https://meta.discourse.org/t/-/401869/1?silent=true)).
- AI Helper editing concerns resurfaced: “Proofread” reportedly **breaks or alters quotes** , which can be especially problematic in contexts where quoted material must remain exact (e.g., religious texts) ([read more](https://meta.discourse.org/t/-/365102/10?silent=true)).
Related structured-data/formatting thread seeing continued attention: [read more](https://meta.discourse.org/t/-/399974/19?silent=true).
* * *
### #Self-hosting
- Two different restore failures highlighted a common theme: **database object collisions during restore/migrate**. One restore hit a `PG::DuplicateTable` error involving a plugin table ([read more](https://meta.discourse.org/t/-/401845/1?silent=true)); another showed “type already exists” errors alongside Sidekiq/permissions noise, with suggestions pointing toward restoring into a clean DB and avoiding collisions ([read more](https://meta.discourse.org/t/-/401852/2?silent=true)).
Related: a “belt and suspenders” approach to deletion safeguards was also discussed recently in the context of permanent deletes: [read more](https://meta.discourse.org/t/-/206678/21?silent=true).
- A small but useful docker note was documented: how to disable Let’s Encrypt / SSL templates in a container setup by commenting out the relevant template includes ([read more](https://meta.discourse.org/t/-/401632/2?silent=true)).
* * *
### #customization:theme
- The popular **FKB Pro** theme thread continued to absorb fallout from newer Ember versions: admins reported “forum unusable” errors (`Could not find module ember-this-fallback/this-fallback-helper`), and @pfaffman pointed to a working repo and a PR to address it ([read more](https://meta.discourse.org/t/-/234323/495?silent=true)).
Related “oh no my theme broke” admin panic is also mentioned in the restore-debugging story: [read more](https://meta.discourse.org/t/-/401845/1?silent=true).
* * *
### #customization:plugin
- The **Contact Form** plugin received a maintenance update after failures on recent Discourse versions, with the author noting they’d updated the plugin to restore compatibility ([read more](https://meta.discourse.org/t/-/305462/13?silent=true)).
Related auth/integration topic still active in the background: OIDC account association troubles continue here: [read more](https://meta.discourse.org/t/-/383894/4?silent=true).
* * *
### #blog
- A new “Discourse Discover” installment highlighted niche hobbyist communities and the _specific expertise_ that makes forums work; the companion topic is live for discussion and link-sharing to the featured communities ([read more](https://meta.discourse.org/t/-/401884/1?silent=true)).
Related community enablement content: the moderator program webinar recording also got a fresh link drop: [read more](https://meta.discourse.org/t/-/398295/16?silent=true).
* * *
### #customization:extras
- A tool pitch: **SuperHref** proposes detecting dead Amazon/eBay links and swapping in related products; @Bas asked the practical question—has it been tested on a Discourse instance, and what were the results? ([read more](https://meta.discourse.org/t/-/401889/4?silent=true)).
Related “Discourse + chat/workspaces” experimentation also continues elsewhere: [read more](https://meta.discourse.org/t/-/399936/4?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @awesomerobot weighed in on privacy and security tradeoffs in age verification, pointing to real-world breach risk and why minimizing retained personal data matters ([read more](https://meta.discourse.org/t/-/401602/27?silent=true)).
- @chapoi firmly set expectations on infinite scroll: no roadmap plans to add pagination to topic lists, and suggested alternative approaches like custom landing pages/homepage configuration ([read more](https://meta.discourse.org/t/-/401894/2?silent=true)).
@chapoi also pushed back on framing age-gating solely as “kids misbehaving,” raising the accountability/anon tension in the same discussion ([read more](https://meta.discourse.org/t/-/401602/33?silent=true)).
- @martin clarified how the site setting default override system interacts with the updated TL3 defaults—especially what “Reset” will show when upcoming changes are enabled/disabled ([read more](https://meta.discourse.org/t/-/397098/8?silent=true)).
- @Falco challenged the YJIT troubleshooting approach, arguing the check was inspecting a newly spawned Ruby process rather than the web server’s running process environment, and suggested inspecting the Pitchfork process environ instead ([read more](https://meta.discourse.org/t/-/401815/2?silent=true)).
- @Bas pressed for real-world validation on the SuperHref idea, asking whether it’s been tried on Discourse and what the findings were ([read more](https://meta.discourse.org/t/-/401889/4?silent=true)).
* * *
Yesterday’s vibe: invite buttons tried to show up on the wrong profiles while infinite scroll refused to stop—at least the team kept the conversation grounded (and the footers… aspirational).
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [1 Maggio 2026, 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/815 "2026-05-01T13:02:28Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
> **Last 24h snapshot (2026-04-30 → 2026-05-01):** **78 new posts** and **8 new topics** , with much of the discussion concentrated around infinite scroll policy, front-end regressions, and admin/email customization questions (e.g. [read more](https://meta.discourse.org/t/-/401984/1?silent=true), [read more](https://meta.discourse.org/t/-/401927/1?silent=true), [read more](https://meta.discourse.org/t/-/401924/1?silent=true)).
- **New posts:** **78**
- **New topics:** **8** — notably:
- **Top users (posts / likes in the last 24h):**
## Interesting Topics
### #General
- @mcmcclur asked the team to reconsider Discourse’s stance on _pagination vs. infinite scroll_ in light of “addictive design” concerns and potential legal exposure; @chapoi pushed back that the harm is mostly about algorithmic feeds/variable rewards rather than Discourse’s chronological lists [read more](https://meta.discourse.org/t/-/401984/2?silent=true).
Related threads and context: a recent pagination request in French [read more](https://meta.discourse.org/t/-/401894/1?silent=true), plus a “small screens / old browser friendly” UI workaround mentioned as an alternative [read more](https://meta.discourse.org/t/-/395104/11?silent=true).
### #bug
- A **pings/mentions regression** got acknowledged by @lindsey (“this happened to me as well”) and then quickly patched by @Falco, linking the fix PR for confirmation [read more](https://meta.discourse.org/t/-/401869/4?silent=true).
If you’ve seen inconsistent pings lately, this is the thread to watch [read more](https://meta.discourse.org/t/-/401869/2?silent=true).
- @RGJ reported that missing `ember-this-fallback/*` modules were getting injected into compiled JS, making it harder to identify the _real_ deprecation source; @david confirmed `.hbs` should still work and shipped a core fix with a backport planned [read more](https://meta.discourse.org/t/-/401927/3?silent=true).
The report includes examples of the failing module imports and plugin/theme impact [read more](https://meta.discourse.org/t/-/401927/1?silent=true).
- The **AI docked composer** (tags #composer + #ai) was flagged as “nice but buggy,” with reports of editing/quoting/sidebar glitches on desktop and lockups on mobile; @sam replied that @keegan is already working on it and will update the thread [read more](https://meta.discourse.org/t/-/401961/2?silent=true).
Adjacent AI tooling discussion also popped up in the proofreader helper thread (quotes being affected, model choice, grounding examples) [read more](https://meta.discourse.org/t/-/365102/15?silent=true).
### #Support
- A deep-dive into **YJIT enablement detection** : @Falco clarified how `DISCOURSE_YJIT_ENABLED` and Ruby’s ENV toggles actually behave, and the OP ultimately discovered their confusion came from `sudo` scrubbing environment variables (resolved) [read more](https://meta.discourse.org/t/-/401815/4?silent=true).
The “aha” moment (and the exact command fix using `sudo -E`) is documented by the OP for future admins [read more](https://meta.discourse.org/t/-/401815/6?silent=true).
- An admin hit an **“[Admin Notice] One of your themes or plugins contains code which needs updating (id:discourse.user.userOptions)”** warning alongside confusing notification behavior; troubleshooting focused on identifying which customization triggered the notice and reviewing `app.yml` plugin lists [read more](https://meta.discourse.org/t/-/401924/1?silent=true).
The thread also cross-references the “bundling more popular plugins with core” change as possible background context [read more](https://meta.discourse.org/t/-/373574/1?silent=true).
- The **age requirement / identity verification** conversation continued with @HAWK arguing that purely non-verified communities risk becoming bot magnets, and emphasizing the difficulty of treating the underlying problem as “just parenting” [read more](https://meta.discourse.org/t/-/401602/34?silent=true).
The thread also calls out the regulatory/fine landscape (e.g., COPPA concerns) as a practical driver for some communities [read more](https://meta.discourse.org/t/-/401602/35?silent=true).
- A subtle gotcha in **unsupported browser messaging** : @paco found that customizing `js.browser_update` didn’t change the message on very old Firefox, and @Falco explained why—JS (and thus JS translations) is intentionally not running in those blocked browsers [read more](https://meta.discourse.org/t/-/400384/20?silent=true).
Follow-up investigation dug into what “very old” means and how the block logic is applied [read more](https://meta.discourse.org/t/-/400384/21?silent=true).
- A small UX/theming tweak solved: hiding **category descriptions inside the category chooser** can be done with a simple CSS rule; @Lilly provided the snippet and the OP confirmed it worked [read more](https://meta.discourse.org/t/-/401987/2?silent=true).
This is a handy pattern for sites that want a cleaner composer UI [read more](https://meta.discourse.org/t/-/401987/1?silent=true).
- “Can I change the default subject of digest/summary emails?”—@NateDhaliwal pointed to `user_notifications.digest.subject_template` as the relevant site text to explore for self-hosts [read more](https://meta.discourse.org/t/-/401993/4?silent=true).
The initial misunderstanding (asking about Meta’s own emails vs. a self-host) is captured in-thread for clarity [read more](https://meta.discourse.org/t/-/401993/3?silent=true).
- A Chinese-language support question: admins saw **“0 posts that need to be permanently deleted”** when trying to permanently delete a topic, and asked what to do next [read more](https://meta.discourse.org/t/-/401981/1?silent=true).
If you’ve run into edge cases around the deletion queue, this thread is the starting point [read more](https://meta.discourse.org/t/-/401981/1?silent=true).
### #Announcements
- Discourse’s **embedded comment system** positioning got clarified: @JimCanto asked whether it’s meant to compete with Disqus, and @Falco confirmed “yes,” highlighting the “bring readers in via blog comments without giving up data/control” use case (including on the free plan) [read more](https://meta.discourse.org/t/-/399743/25?silent=true).
This is particularly relevant for SSO/private communities that still want public-facing touchpoints [read more](https://meta.discourse.org/t/-/399743/24?silent=true).
- Email UX continues to be refined: the “simpler email subject lines” discussion added another admin perspective—when reply-by-email is disabled, ambiguity around “replying by email” isn’t top-of-mind, but clarity still matters [read more](https://meta.discourse.org/t/-/395927/6?silent=true).
If you’re tuning email deliverability and comprehension, the thread is worth a skim [read more](https://meta.discourse.org/t/-/395927/6?silent=true).
### #development
- Theme/block authoring got a jolt of inspiration: @manuel shared experiments using AI design tooling to prototype _wild_ homepage concepts (including the memorably titled “Newspaper from Hell”), showing how fast iteration can surface novel block layouts [read more](https://meta.discourse.org/t/-/401629/6?silent=true).
Related theme-component chatter about “Blog Post Styling” continues too (still seeing update issues) [read more](https://meta.discourse.org/t/-/110841/182?silent=true).
### #Site\_Management
- A new official guide explains how to **auto-categorize topics using AI triage** by combining the #ai Discourse AI plugin with Discourse Automation, including prerequisite setup and example agent prompts [read more](https://meta.discourse.org/t/-/401827/1?silent=true).
This sits nicely alongside other ongoing “AI in operations” discussions (e.g., proofreader behavior and quotes) [read more](https://meta.discourse.org/t/-/365102/11?silent=true).
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@chapoi** weighed in on the _infinite scroll vs. addictiveness_ framing, arguing Discourse lacks the algorithmic “variable reward” mechanisms typically implicated by research, and suggested de-escalating the thread unless practical workarounds emerge [read more](https://meta.discourse.org/t/-/401984/2?silent=true).
They also answered an email-customization question—clarifying that _per-user customization of subjects_ isn’t a thing in the way the OP initially asked it (before the self-host clarification) [read more](https://meta.discourse.org/t/-/401993/2?silent=true).
- **@Falco** closed the loop on multiple threads: they posted the fix reference for the pings regression [read more](https://meta.discourse.org/t/-/401869/4?silent=true), provided the authoritative explanation/solution on YJIT enablement detection and toggles [read more](https://meta.discourse.org/t/-/401815/4?silent=true), and confirmed the practical limitation of customizing `js.browser_update` when JS is blocked in old browsers [read more](https://meta.discourse.org/t/-/400384/20?silent=true).
They also pointed people back to the already-landed fix for AI proofreader/quotes and asked about adding examples to ground custom proofreader agents [read more](https://meta.discourse.org/t/-/365102/11?silent=true).
- **@david** acknowledged and investigated the `ember-this-fallback` deprecation crash report, then shipped/linked a core PR and noted it would be backported to **2026.4** [read more](https://meta.discourse.org/t/-/401927/3?silent=true).
- **@HAWK** added a key perspective to the age/verification debate—warning that non-verified communities may increasingly be the only ones bots can join, and reinforcing that the underlying safety/regulatory problem can’t be hand-waved away [read more](https://meta.discourse.org/t/-/401602/34?silent=true).
- **@lindsey** confirmed the pings bug was reproducible on their end and signaled it was being investigated before the fix landed [read more](https://meta.discourse.org/t/-/401869/2?silent=true).
- **@manuel** shared tangible theme/block prototypes created via AI-aided exploration (brutalist editorial layout, dense Japanese-style portal), illustrating a faster path from “idea” to “block concept” for theme authors [read more](https://meta.discourse.org/t/-/401629/6?silent=true).
- **@sam** acknowledged the AI docked composer bug report and pointed to ongoing work (with an upcoming update from @keegan) [read more](https://meta.discourse.org/t/-/401961/2?silent=true).
- **@awesomerobot** asked for sources in the infinite scroll/addictiveness discussion, prompting participants to bring research citations into the thread [read more](https://meta.discourse.org/t/-/401984/7?silent=true).
* * *
Yesterday’s vibe check: between doomscroll-law hypotheticals and a theme prototype literally dubbed **“Newspaper from Hell,”** Meta managed to be both conscientious _and_ wonderfully dramatic.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [2 Maggio 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/816 "2026-05-02T13:01:24Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 93**
- **New topics (last 24h): 7**
**Top users (posts / likes in the last 24h):**
- **@RGJ** — 4 posts / 24 likes
- **@Lilly** — 12 posts / 23 likes
- **@Moin** — 13 posts / 15 likes
- **@Falco** — 4 posts / 12 likes
- **@Canapin** — 2 posts / 7 likes
- **@eisammy** — 3 posts / 6 likes
- **@merefield** — 1 post / 5 likes
- **@gallery3540** — 8 posts / 5 likes
- **@mcmcclur** — 1 post / 4 likes
- **@NateDhaliwal** — 5 posts / 4 likes
* * *
## Interesting Topics
### #customization:theme component
- @RGJ shipped a new theme component that replaces auto infinite-loading with a manual **“Load More”** interaction, with discussion around mobile ergonomics and a discovered core limitation (where `DiscoveryTopics` doesn’t pass `canLoadMore`) in the follow-up thread: [Load More Button](https://meta.discourse.org/t/-/402049/1?silent=true). Related context: the broader debate that motivated it lives in [Time to reconsider infinite scroll?](https://meta.discourse.org/t/-/401984/18?silent=true), plus install docs like [How to install a theme or theme component](https://meta.discourse.org/t/-/63682/1?silent=true) and the [Beginner’s guide to using Discourse Themes](https://meta.discourse.org/t/-/91966/1?silent=true).
- Icon usability feedback popped up again—this time about mirrored “back/forward” affordances in edit history—via a specific UI example in [Discourse Lucide Icons](https://meta.discourse.org/t/-/400133/10?silent=true) (_request: make the icon pairings less ambiguous_).
- A long-running theme enhancement got a new question: whether **Created Topic Sort** can also appear while browsing a **tag** page (where the option currently disappears): [Created Topic Sort](https://meta.discourse.org/t/-/321521/20?silent=true) [read more](https://meta.discourse.org/t/-/321521/20?silent=true).
- A compatibility/migration concern resurfaced for a popular official component—whether the update depends on a particular Discourse core PR and how compatibility branches behave—discussed in [Blog Post Styling](https://meta.discourse.org/t/-/110841/183?silent=true).
* * *
### #Self-hosting
- A self-hosted admin asked how to change the composer’s image resize threshold/target for high-quality photography uploads; the solution clarified the difference between _trigger threshold_ and the _actual width target_, plus the gotcha that checking must use `SiteSetting.`: [Composer image resize threshold](https://meta.discourse.org/t/-/402018/1?silent=true). Useful related references: [Client side image optimization enabled by default](https://meta.discourse.org/t/-/197617/1?silent=true) and the [Hidden site settings reference guide](https://meta.discourse.org/t/-/308774/1?silent=true).
- Badge-heavy communities ran into the hard upper bound for `max_favorite_badges` (0–6). The thread explored alternatives (profiles vs usercards, plugins/components, and feasibility of changing limits via plugin or `app.yml` replace stanza): [Bypass the 6 badge fav limit](https://meta.discourse.org/t/-/402015/1?silent=true). Suggested adjacent tooling included the “post badges” ecosystem: [Post badges plugin discussion](https://meta.discourse.org/t/-/114722/121?silent=true) [read more](https://meta.discourse.org/t/-/114722/121?silent=true).
* * *
### #Support
- A request to **force a single line** (or otherwise constrain “first line” width/characters) turned into a broader conversation about _enforcement vs UX frustration_, with pointers to existing approaches like character requirements, form templates, and built-in composer counting: [Is there a way to force people to write exact characters for a single line?](https://meta.discourse.org/t/-/402056/1?silent=true). References shared included [discourse-characters-required](https://meta.discourse.org/t/-/77195/1?silent=true), [Creating form templates](https://meta.discourse.org/t/-/397564/1?silent=true), and [Composer character count](https://meta.discourse.org/t/-/358733/1?silent=true).
- A community hub trying to build a **partner directory** asked what Discourse can do natively (directory, custom user fields, admin views, [Data Explorer](https://meta.discourse.org/t/32566?silent=true)), and got pointed to both the built-in user list and a card-based UI option: [Member directory](https://meta.discourse.org/t/-/402030/1?silent=true). Helpful expansions: the [User Card Directory theme component](https://meta.discourse.org/t/-/144479/1?silent=true) and the directory enhancements from [New leaderboard/user directory features](https://meta.discourse.org/t/-/195263/1?silent=true).
- A solved, Chinese-language walkthrough detailed how to restore **real client IP visibility** when running Discourse behind Cloudflare + a reverse proxy (OpenResty) in a containerized 1Panel setup: [解决1Panel部署的Discourse，所有用户ip显示为来自 Cloudflare，而不是用户的浏览器真实IP的问题](https://meta.discourse.org/t/-/402038/1?silent=true). This also connected back to the earlier solved report: [如何解决所有流量显示为来自 Cloudflare 的服务器，而不是用户的浏览器 IP](https://meta.discourse.org/t/-/399954/16?silent=true).
* * *
### #General
- A user reported that font sizes (navbar + suggested/related areas) looked **smaller on mobile** across multiple hosted forums; the likely culprit was enabling the modernized Foundation theme, with reproduction steps and a cross-link into the main announcement thread: [Theme font size gets smaller due to hosted instance updates?](https://meta.discourse.org/t/-/402055/1?silent=true), referencing [Modernizing the Foundation theme](https://meta.discourse.org/t/-/395331/77?silent=true).
- The ongoing “infinite scroll vs ‘stop at last visit’” discussion continued, including distinctions between _infinite scroll_ and _algorithmic addictive feeds_, and whether legal definitions might apply: [Time to reconsider infinite scroll?](https://meta.discourse.org/t/-/401984/19?silent=true). The practical outcome (a manual-load TC) was later summarized and linked from within the same conversation: [Load More Button mention](https://meta.discourse.org/t/-/401984/23?silent=true).
* * *
### #ux
- Draft reliability concerns resurfaced: users want a way to **verify drafts will save** before closing, especially when content is mostly quotes/short text and doesn’t always trigger the save behavior they expect: [How do I ensure my draft will be saved…?](https://meta.discourse.org/t/-/385291/23?silent=true).
- A “completed” feature still had a usability gap: users can’t easily view **all reactions** in the post reaction tooltip without knowing horizontal scrolling is supported (and some devices/mice make that difficult): [Ability to display all the likes/reactions on a post](https://meta.discourse.org/t/-/389820/84?silent=true).
* * *
### #bug
- The new AI docked composer saw rapid iteration: fixes landed and more were queued to address edit issues and mobile quirks, with explicit design notes about RTE-first UX and why markdown preview isn’t shown in docked mode: [New ai docked composer](https://meta.discourse.org/t/-/401961/5?silent=true).
* * *
### #Announcements
- Continued feedback on the modernized Foundation theme focused on **WCAG palette button borders** , perceived affordance (buttons “floating”), and other subtle contrast/styling regressions, plus cross-linking to the mobile font-size report: [Modernizing the Foundation theme](https://meta.discourse.org/t/-/395331/76?silent=true).
* * *
### #ux (theme/component ecosystem)
- A styling regression was traced to Foundation modernization overriding expected text colors in a category badge component, and a fix PR was shared for the component repository: [Issue with font colour in category badges](https://meta.discourse.org/t/-/401679/8?silent=true) [read more](https://meta.discourse.org/t/-/401679/8?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Falco helped untangle hidden/advanced image optimization settings by clarifying which composer setting controls **triggering** vs the **width target** , and corrected how to verify values in Rails console: [Composer image resize threshold](https://meta.discourse.org/t/-/402018/9?silent=true), plus follow-ups on checking the setting correctly at [post 11](https://meta.discourse.org/t/-/402018/11?silent=true) and a longer-term UX tradeoff discussion at [post 13](https://meta.discourse.org/t/-/402018/13?silent=true).
- @keegan provided an implementation/status update on fixes and improvements for the docked AI composer, referencing active PR work and explaining the “no markdown preview” decision in docked mode: [New ai docked composer](https://meta.discourse.org/t/-/401961/5?silent=true).
- @derek identified Foundation modernization styles as the source of a category badge color regression, and linked a patch PR for the affected component: [Issue with font colour in category badges](https://meta.discourse.org/t/-/401679/8?silent=true).
- @southpaw requested key hosting/self-hosting context to diagnose why a site couldn’t be taken out of read-only mode (noting hosted-plan constraints): [Read Only Modes in Discourse](https://meta.discourse.org/t/-/296976/13?silent=true).
* * *
_Yesterday’s vibe check: we debated whether infinite scroll is “addictive,” then promptly built a button to make the law (and your thumb) happy._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [3 Maggio 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/817 "2026-05-03T13:01:58Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 27**
- **New topics (last 24h): 2**
- **Most active users (posts / likes):**
- **@Lilly** — **5 posts** , **7 likes**
- **@darkpixlz** — **4 posts** , **6 likes**
- **@kirupa** — **1 post** , **6 likes**
- **@bloomexperiment** — **1 post** , **4 likes**
- **@jericson** — **2 posts** , **2 likes**
- **@oshyan** — **1 post** , **3 likes**
- **@pfaffman** — **1 post** , **3 likes**
- **@merefield** — **1 post** , **3 likes**
- **@Moin** — **1 post** , **3 likes**
- **@elmuerte** — **1 post** , **1 like**
A lot of the visible momentum clustered around theme/UI polish and “is Discourse infinite scroll actually infinite?” philosophy—see the new theme component drop ([read more](https://meta.discourse.org/t/-/402081/1?silent=true)), the Foundation theme UX gap investigation ([read more](https://meta.discourse.org/t/-/395331/82?silent=true)), and the ongoing infinite-scroll framing debate ([read more](https://meta.discourse.org/t/-/401984/30?silent=true)).
* * *
## Interesting Topics
### #customization:theme component
- @darkpixlz published **“Modern User Card | Fixed Experimental Usercard”** , aiming to restore the older experimental user card on modern Discourse, with install pointers and a theme-creator preview ([read more](https://meta.discourse.org/t/-/402081/1?silent=true)). Follow-up posts dug into refactor realities and what “fixed” means in practice ([read more](https://meta.discourse.org/t/-/402081/9?silent=true)), plus compatibility concerns around the `discourse.component-template-resolving` deprecation warning ([read more](https://meta.discourse.org/t/-/402081/6?silent=true)) and how it relates to the broader deprecation guidance ([read more](https://meta.discourse.org/t/-/370019/2?silent=true)).
### #Announcements
- In **“Modernizing the Foundation theme”** , a small but annoying visual gap under the _Related_ / _Suggested_ buttons was reported—especially obvious with larger fonts ([read more](https://meta.discourse.org/t/-/395331/79?silent=true)). @Lilly traced it to a UX mismatch between button classes (including the injected AI-related button) and provided a targeted padding/line-height patch ([read more](https://meta.discourse.org/t/-/395331/82?silent=true)), with additional diagnostic back-and-forth on viewport assumptions ([read more](https://meta.discourse.org/t/-/395331/80?silent=true)).
### #General
- The long-running **“Time to reconsider infinite scroll?”** thread kept pushing on definitions: @elmuerte asked about technical implications at scale (e.g., “1,000,000 topics”) and suggested a “catch your breath after N units” UX concept ([read more](https://meta.discourse.org/t/-/401984/27?silent=true)). Replies pointed to existing “take a break” patterns ([read more](https://meta.discourse.org/t/-/401984/28?silent=true)) and reframed the debate as _infinite scroll vs infinite content_, emphasizing Discourse’s finite endpoints ([read more](https://meta.discourse.org/t/-/401984/30?silent=true)), plus legal/definition nuance about whether it’s a “significant part of the services” ([read more](https://meta.discourse.org/t/-/401984/31?silent=true)). (Related component link surfaced: [read more](https://meta.discourse.org/t/-/140248/1?silent=true).)
- In the #show-and-tell thread **“I populated my (mostly-dead) Discourse forum with bots!”**, @kirupa posted a substantial update: the full source code was published for others to adapt, plus a walkthrough video for implementation details ([read more](https://meta.discourse.org/t/-/401493/18?silent=true)).
### #Support
- **“Is there a way to force people to write exact characters for a single line?”** (marked _solved_) got a practical confirmation: @hipp0 reported the solution worked well and noted the counter color could be customized too ([read more](https://meta.discourse.org/t/-/402056/10?silent=true)).
### #customization:plugin
- In the official **Discourse Calendar (and Event)** thread (#official #calendar-and-event #included-in-core), @oshyan argued the current event/calendar configuration is a confusing “mish-mash” across settings layers and shared a prototype of a more event-focused plugin—after only a few days of “vibe coding”—including a demo video and feature outline ([read more](https://meta.discourse.org/t/-/97376/575?silent=true)).
- The **Telegram Notifications Plugin (discourse-telegram-notifications)** support thread saw UI/option confusion reported (including screenshots and “missing option” context) ([read more](https://meta.discourse.org/t/-/60483/207?silent=true)) with an additional follow-up screenshot clarifying what the reporter sees in the newer interface ([read more](https://meta.discourse.org/t/-/60483/208?silent=true)).
### #Self-hosting
- **“Bypass the 6 badge fav limit”** continued with alternative approaches: @pfaffman suggested skipping badges entirely and using theme components to add multiple flair-badges based on group membership (targeting user card/profile UX rather than badge limits) ([read more](https://meta.discourse.org/t/-/402015/21?silent=true)).
### #development
- @jericson posted **“Case study of an amateur plugin author”** , walking through the real-world path from “this isn’t possible” to building a contact-form plugin—despite not being a frontend specialist—linking out to earlier constraints and the plugin tutorial trail that made it doable ([read more](https://meta.discourse.org/t/-/402084/1?silent=true)). The post connects back to the earlier “contact form without third-party services” discussion ([read more](https://meta.discourse.org/t/-/233273/1?silent=true)), the official plugin-outlet tutorial ([read more](https://meta.discourse.org/t/-/31001/1?silent=true)), and the finished contact form plugin thread ([read more](https://meta.discourse.org/t/-/305462/1?silent=true)).
- In **“Automatically updating themes and plugins to .gjs file format”** (#dev-news), @jericson added a concrete gotcha for older plugins: depending on skeleton age, you may also need to pull in the updated ESLint config file ([read more](https://meta.discourse.org/t/-/368051/11?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Lilly partnered with @darkpixlz on the new user-card theme component thread—responding to reports of broken behavior and helping set expectations that it likely needs a deeper refactor to align with current core/theming patterns ([read more](https://meta.discourse.org/t/-/402081/4?silent=true); [read more](https://meta.discourse.org/t/-/402081/9?silent=true)). @Lilly also helped contextualize the deprecation warning discussion and how to treat it in the short term ([read more](https://meta.discourse.org/t/-/402081/6?silent=true); [read more](https://meta.discourse.org/t/-/370019/2?silent=true)).
- @Lilly investigated a UI gap/regression in the Foundation theme’s “Related/Suggested” area, identified class/structure mismatches, and offered a CSS patch to improve spacing across desktop and mobile ([read more](https://meta.discourse.org/t/-/395331/82?silent=true)), following up on the original report and reproductions ([read more](https://meta.discourse.org/t/-/395331/79?silent=true); [read more](https://meta.discourse.org/t/-/395331/80?silent=true)).
- @hipp0 confirmed the accepted approach in a Support thread worked as intended and highlighted an extra customization win (counter color flexibility) ([read more](https://meta.discourse.org/t/-/402056/10?silent=true)).
* * *
Yesterday’s meta energy: _finite_ scrolling that feels “infinite,” revived communities powered by bots, and yet another reminder that one tiny CSS gap can launch a whole UX investigation—see you tomorrow.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [4 Maggio 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/818 "2026-05-04T13:01:43Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (24h): 75** across active threads like the Self-hosting upload-limit troubleshooting saga ([read more](https://meta.discourse.org/t/-/402101/1?silent=true)), a deep dive into plugin maintenance/documentation gaps ([read more](https://meta.discourse.org/t/-/402084/1?silent=true)), and a fast-moving `bin/lint` regression report + fix cycle ([read more](https://meta.discourse.org/t/-/402126/1?silent=true)).
- **New topics (24h): 3**, including a new #Self-hosting support request about upload limits ([read more](https://meta.discourse.org/t/-/402101/1?silent=true)) and a #Site feedback report about Meta’s logo rendering oddly at certain zoom levels ([read more](https://meta.discourse.org/t/-/402100/1?silent=true)).
**Top users (posts / likes in the last 24h)**
- @Lilly — **7 posts / 11 likes** (notably diagnosing the root cause of a “broken rebuild” as an upstream firewall/VPS issue: [read more](https://meta.discourse.org/t/-/402101/32?silent=true))
- @merefield — **6 posts / 8 likes** (kept the rebuild troubleshooting grounded in logs + SSH basics: [read more](https://meta.discourse.org/t/-/402101/6?silent=true))
- @david — **7 posts / 5 likes** (shipped a quick fix for plugin linting workflow regression: [read more](https://meta.discourse.org/t/-/402126/2?silent=true))
- @Moin — **2 posts / 4 likes** (connected a plugin author’s breakage to a specific deprecation-handler bug: [read more](https://meta.discourse.org/t/-/402084/2?silent=true))
- @piffy — **1 post / 4 likes** (shared how “agentic coding” changed their plugin maintenance reality: [read more](https://meta.discourse.org/t/-/402084/3?silent=true))
- @chapoi — **1 post / 4 likes** (offered candid context on why docs lag behind product work: [read more](https://meta.discourse.org/t/-/402084/5?silent=true))
- @Bathinda — **2 posts / 3 likes** (reacted to the “not going closed source” announcement with appreciation: [read more](https://meta.discourse.org/t/-/400863/19?silent=true))
- @ondrej — **1 post / 3 likes** (reported the “weird logo” display issue: [read more](https://meta.discourse.org/t/-/402100/1?silent=true))
- @Heliosurge — **5 posts / 3 likes** (continued the practical policy/implementation discussion on age requirements: [read more](https://meta.discourse.org/t/-/401602/38?silent=true))
- @Canapin — **1 post / 2 likes** (linked the canonical “increase upload size” guide during troubleshooting: [read more](https://meta.discourse.org/t/-/402101/4?silent=true))
> “ **this is not a build issue** … it is a VPSmanager issue… enabled a firewall that is blocking sign up payloads as well as file uploads.” — @Lilly ([read more](https://meta.discourse.org/t/-/402101/32?silent=true))
* * *
## Interesting Topics
### #Self-hosting
- @Vsekraski hit “This file is too large” even for tiny uploads, then the thread escalated into instance recovery drama when rebuilds were interrupted—ultimately landing on a _provider firewall_ blocking payloads rather than an Nginx/app.yml misconfiguration ([read more](https://meta.discourse.org/t/-/402101/1?silent=true), [read more](https://meta.discourse.org/t/-/402101/14?silent=true), [read more](https://meta.discourse.org/t/-/402101/32?silent=true)).
- A German-language OIDC integration post documented why users weren’t matching existing accounts: the IdP email claim wasn’t being marked verified, and setting email verification handling fixed association in testing ([read more](https://meta.discourse.org/t/-/383894/5?silent=true)).
### #development
- A regression report explained how a change to `bin/lint` broke linting for non-bundled plugins when running `bin/lint --fix plugins/my-custom-plugin`; @david responded with a fix branch/PR, then iterated on visibility, file targeting, and `--fix` behavior ([read more](https://meta.discourse.org/t/-/402126/1?silent=true), [read more](https://meta.discourse.org/t/-/402126/2?silent=true), [read more](https://meta.discourse.org/t/-/402126/8?silent=true)).
- “Case study of an amateur plugin author” turned into a broader conversation about versioning strategy, a `.hbs`-related deprecation-handler crash, and the long-term cost of outdated tutorials—especially the still-referenced plugin guide teaching older patterns ([read more](https://meta.discourse.org/t/-/402084/2?silent=true), [read more](https://meta.discourse.org/t/-/402084/4?silent=true), [read more](https://meta.discourse.org/t/-/402084/6?silent=true)).
_(Related threads mentioned in the discussion: the deprecation crash bug report ([read more](https://meta.discourse.org/t/-/401927/1?silent=true)), the versioning strategy RFC ([read more](https://meta.discourse.org/t/-/383536/1?silent=true)), and the plugin tutorial that’s still widely linked ([read more](https://meta.discourse.org/t/-/31001/1?silent=true)).)_
### #Announcements
- The long-running “ **`tests-passed` is now `latest`** ” announcement got a fresh check-in: @jericson asked whether an admin warning exists yet, and @david confirmed it hasn’t been added—while noting `tests-passed` remains a working alias ([read more](https://meta.discourse.org/t/-/384272/4?silent=true), [read more](https://meta.discourse.org/t/-/384272/5?silent=true)).
### #bug
- In the #composer #ai experiment thread, @Lilly reported the “AI docked composer” is _much less buggy_ but still has issues: quoting initially failed (later fixed after a rebuild) and uploads after the first post continued to fail—plus ongoing muscle-memory friction around _Shift+Enter_ for newlines ([read more](https://meta.discourse.org/t/-/401961/7?silent=true), [read more](https://meta.discourse.org/t/-/401961/8?silent=true), [read more](https://meta.discourse.org/t/-/401961/9?silent=true)).
### #Site feedback
- A quick but intriguing bug report: Meta’s logo appears “weird” (pixelated/aliased) at normal zoom in multiple desktop browsers, but looks correct when zoomed in—suggesting a rendering/scaling edge case ([read more](https://meta.discourse.org/t/-/402100/1?silent=true)).
- The ongoing “Daily Summary Feedback” thread continued surfacing how automated summaries read in practice, including a system-generated recap that quoted and linked live troubleshooting threads ([read more](https://meta.discourse.org/t/-/291853/287?silent=true)).
_(The referenced auto-summary excerpt pointed back into the Self-hosting upload-limit thread: [read more](https://meta.discourse.org/t/-/402101/14?silent=true).)_
### #customization:theme component
- The “Load More Button” theme-component discussion highlighted a core issue: `DiscoveryTopics` doesn’t pass the `canLoadMore` model property through, so a “Load more” button may appear when it shouldn’t; commenters floated CSS hiding as a partial workaround and noted a fork exists for an edge case ([read more](https://meta.discourse.org/t/-/402049/9?silent=true), [read more](https://meta.discourse.org/t/-/402049/10?silent=true)).
### #customization:plugin
- In the official #openid-connect plugin topic, a key behavioral question came up: whether users are automatically removed from Discourse groups when they lose upstream membership; @david said “yes,” but follow-up testing suggested a mismatch worth re-checking ([read more](https://meta.discourse.org/t/-/103632/321?silent=true), [read more](https://meta.discourse.org/t/-/103632/322?silent=true), [read more](https://meta.discourse.org/t/-/103632/323?silent=true)).
- An old “Trading Buttons” plugin thread resurfaced with a very current-sounding hypothesis: plugin-per-category settings might fail to save due to the “simplified category creation” changes, pointing directly at a related bug/announcement about plugin category settings persistence ([read more](https://meta.discourse.org/t/-/71308/131?silent=true), [read more](https://meta.discourse.org/t/-/400699/1?silent=true)).
- The official #calendar-and-event plugin topic continued with a product-shaping idea: rather than stacking multiple plugins, build a more complete event management system with toggles—plus a side discussion on which AI coding tools people use in practice ([read more](https://meta.discourse.org/t/-/97376/576?silent=true), [read more](https://meta.discourse.org/t/-/97376/577?silent=true)).
### #Site Management
- A form-templates UX gap: users can easily paste images/GIFs into normal posts, but copying/pasting into _form template composer fields_ didn’t work in the Markdown editor; a workaround was to toggle WYSIWYG (with caveats), and an alternative was to add explicit `upload` fields to templates ([read more](https://meta.discourse.org/t/-/397564/9?silent=true), [read more](https://meta.discourse.org/t/-/397564/10?silent=true), [read more](https://meta.discourse.org/t/-/397564/11?silent=true)).
### #Support
- The “Age requirement for Discourse” thread kept rolling with practical/legal comparisons (e.g., helmet laws) and a strong focus on _accountability and parental guidance_—including a detailed anecdote about locking down kids’ OS accounts and the human factor of password leaks ([read more](https://meta.discourse.org/t/-/401602/36?silent=true), [read more](https://meta.discourse.org/t/-/401602/38?silent=true)).
### #customization:extras
- SuperHref shipped a monetization flexibility update: suggested products can now preserve the _original_ affiliate tag or swap in _your own_, depending on the site owner’s preference ([read more](https://meta.discourse.org/t/-/401889/18?silent=true)).
### #blog
- The “Discourse is Not Going Closed Source” blog topic picked up fresh appreciation and reflection from readers discovering the post later, underscoring how much the community values the open-source commitment and transparency ([read more](https://meta.discourse.org/t/-/400863/19?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @david jumped into a tooling regression report and quickly provided a concrete fix path for plugin authors impacted by `bin/lint` changes, then continued troubleshooting follow-up behavior like missing progress output and `--fix` doing nothing ([read more](https://meta.discourse.org/t/-/402126/2?silent=true), [read more](https://meta.discourse.org/t/-/402126/4?silent=true), [read more](https://meta.discourse.org/t/-/402126/8?silent=true)). He also clarified that `tests-passed` remains a functional alias for `latest` (no admin warning added yet) ([read more](https://meta.discourse.org/t/-/384272/5?silent=true)), and answered OIDC expectations about automatic group membership removal ([read more](https://meta.discourse.org/t/-/103632/322?silent=true)).
- @chapoi responded in the plugin-author “case study” thread with frank context about tradeoffs: a small team maintaining a large codebase, balancing customer commitments and community support, and why documentation (like plugin tutorials) often trails behind product evolution ([read more](https://meta.discourse.org/t/-/402084/5?silent=true)).
* * *
If yesterday taught anything, it’s this: let rebuilds finish, keep your hands off **Ctrl+C** , and maybe don’t trust a “weird logo” until you’ve tried zooming.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [5 Maggio 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/819 "2026-05-05T13:01:53Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 78** (spread across today’s active threads like the asset build memory report in [Support](https://meta.discourse.org/t/-/402139/1?silent=true) and plugin/docs discussions in [Development](https://meta.discourse.org/t/-/402084/10?silent=true)).
- **New topics (last 24h): 12** — here they are for quick scanning:
- **Top users (posts / likes in the last 24h)**
(Each user linked to a representative post from this period.)
* * *
## Interesting Topics
### #development
- @jericson’s “amateur plugin author” case study turned into a broader conversation about _documentation currency, migration pain, and how much “agency” plugin authors should have_—with pushback on wiki-style docs vs GitHub review flow ([read more](https://meta.discourse.org/t/-/402084/8?silent=true), and @david’s deprecation timeline clarification: [read more](https://meta.discourse.org/t/-/402084/10?silent=true)).
- A regression in plugin linting for non-bundled plugins was resolved, with @david confirming the fix and merging the PR after user verification ([read more](https://meta.discourse.org/t/-/402126/10?silent=true)).
### #Support
- Self-hosters running OpenShift reported **asset precompilation memory usage exploding past 20GB** after the newer precompiled assets + plugin build approach; debugging focused on plugin inventory and whether memory drops after `assets:build` completes ([read more](https://meta.discourse.org/t/-/402139/1?silent=true), plugin list follow-up: [read more](https://meta.discourse.org/t/-/402139/8?silent=true)).
- A “full app embed” used for cross-domain commenting ran into login/session issues that look like third-party cookie behavior; the thread quickly converged on `SameSite` settings and the security tradeoffs of cross-domain embedding ([read more](https://meta.discourse.org/t/-/402180/1?silent=true), suggested setting: [read more](https://meta.discourse.org/t/-/402180/3?silent=true)).
- A Russian-language “component install error” got resolved quickly; @Lilly noted the **“link method” can break when translation/characters interfere** , and confirmed the component was installed successfully ([read more](https://meta.discourse.org/t/-/402168/2?silent=true)).
- Invite links shared into apps like WhatsApp produced a preview tile where a white-on-transparent logo disappears; the conclusion was that preview clients often render thumbnails onto a light tile, so the fix is to bake contrast into the icon rather than expecting external renderers to respect transparency/background choices ([read more](https://meta.discourse.org/t/-/402159/6?silent=true)).
- A “Latest topics” header request revealed that Meta’s UI here is customized; the actionable answer was to add it via the `discovery-navigation-bar-above` outlet (and to review how outlets work in themes/plugins) ([read more](https://meta.discourse.org/t/-/402188/4?silent=true)).
- A Discourse AI Agent PM follow-up couldn’t accept an image upload on one instance, but was pointed to a fix already landed (and a specific commit to pick up), tying back to the docked composer/AI UX work ([read more](https://meta.discourse.org/t/-/402201/2?silent=true), related fix context: [read more](https://meta.discourse.org/t/-/401961/10?silent=true)).
### #Community Building
- “Welcoming new users” explored ways to **notify non-admin community members of new signups** , especially when hosted plans restrict SQL/cron; one practical idea was linking trusted users to a TL group membership view (e.g., TL0/TL1) via the sidebar for logged-in users ([read more](https://meta.discourse.org/t/-/402151/6?silent=true)).
- In a longer-running “new product launch” community reconfiguration thread, a simple tactic surfaced: switching the homepage from `/latest` to `/categories` to make a new structure immediately legible to members ([read more](https://meta.discourse.org/t/-/401562/10?silent=true)).
### #blog
- A new companion topic showcased what Discourse _actually feels like_ in a browser set to Japanese—spotlighting translation quality and the UI experience for non-English communities ([read more](https://meta.discourse.org/t/-/402177/1?silent=true)).
### #ux
- A revived discussion argued the three-bar “hamburger” used to toggle Discourse’s sidebar violates a common convention (users expect a temporary menu), and highlighted the tension between “customize it” solutions and out-of-the-box clarity ([read more](https://meta.discourse.org/t/-/304437/11?silent=true), plus a pointer to dynamic icon customization: [read more](https://meta.discourse.org/t/-/304437/12?silent=true)).
- Documentation nitpicks in the “closed/private community” guide: a screenshot example appears misleading about who can see a category (“everyone” vs TL0), and the guide may need updates for newer category visibility + the “advanced settings” requirement to even see the Security tab ([read more](https://meta.discourse.org/t/-/27014/5?silent=true)).
### #contribute:feature
- A concept proposal to treat **Chat channels and Topics as “first-class” activity in one unified recency-sorted view** (including category/subcategory lines + previews) generated discussion about what Discourse navigation could become as chat/forum boundaries blur ([read more](https://meta.discourse.org/t/-/402173/1?silent=true), demo video follow-up: [read more](https://meta.discourse.org/t/-/402173/2?silent=true)).
- ActivityPub integration continues to mature: a report noted that following Mastodon actors works, but following other Discourse actors may not, prompting the plugin maintainer to investigate ([read more](https://meta.discourse.org/t/-/266794/482?silent=true), maintainer response: [read more](https://meta.discourse.org/t/-/266794/484?silent=true)).
### #bug
- A rich text ↔ Markdown switch appears to introduce **incorrect whitespace insertion** (GIF + repro snippet provided), raising another composer edge case for parity between editors ([read more](https://meta.discourse.org/t/-/402184/1?silent=true)).
- A [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) privacy/security concern progressed with a linked PR intended to prevent leaking email addresses in redirect URLs ([read more](https://meta.discourse.org/t/-/397980/6?silent=true)).
### #Self-hosting
- A French self-hosting thread documented the pain of installing behind a non-_full-stack_ residential IP + unusual port forwarding constraints; suggestions ranged from Cloudflare Tunnel to “use a VPS,” and also highlighted that the installer’s connection test can be skipped when appropriate ([read more](https://meta.discourse.org/t/-/402198/1?silent=true), skip flag suggestion: [read more](https://meta.discourse.org/t/-/402198/5?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @david clarified that the `.hbs` deprecation runway is **not** an immediate “support drop,” pegging earliest removal after the next ESR (end of July), while acknowledging docs should have been updated sooner ([read more](https://meta.discourse.org/t/-/402084/10?silent=true)). He also investigated self-hoster reports of runaway memory during asset builds by requesting plugin lists and probing whether memory subsides after build completion ([read more](https://meta.discourse.org/t/-/402139/2?silent=true), follow-up question: [read more](https://meta.discourse.org/t/-/402139/7?silent=true)). Finally, he confirmed a linting workflow fix and merged the PR once validated ([read more](https://meta.discourse.org/t/-/402126/10?silent=true)).
- @nat published the companion discussion for the Discourse blog post on multilingual UX, anchoring observations around what Meta looks like in Japanese locale settings ([read more](https://meta.discourse.org/t/-/402177/1?silent=true)).
- @chapoi helped theme builders by pointing to the `discovery-navigation-bar-above` outlet for injecting a “Latest topics” header, and linked to the canonical outlet usage guide ([read more](https://meta.discourse.org/t/-/402188/4?silent=true)). He also unpacked why invite-link previews are largely controlled by external preview renderers—and why baking contrast into the uploaded icon is often the only reliable approach ([read more](https://meta.discourse.org/t/-/402159/6?silent=true)).
- @HAWK suggested a pragmatic community reconfiguration win for product launches: switch the homepage from `/latest` to `/categories` to immediately signal a new information architecture ([read more](https://meta.discourse.org/t/-/401562/10?silent=true)).
- @Falco advised how to get cross-domain “full app embed” sessions working by setting `SiteSetting.same_site_cookies = "None"` (via rails console), directly addressing modern browser cookie restrictions in iframes ([read more](https://meta.discourse.org/t/-/402180/3?silent=true)).
- @derek confirmed a UX styling fix (category badge font color) has been merged and invited further reports if anything remains off ([read more](https://meta.discourse.org/t/-/401679/10?silent=true)).
- @pmusaraj acknowledged an ActivityPub issue report (following Mastodon works, Discourse actors don’t) and said the team will investigate shortly ([read more](https://meta.discourse.org/t/-/266794/484?silent=true)).
- @keegan gated the new AI docked composer behind an “upcoming changes” switch while polish continues, and shipped an uploads fix tied to user testing feedback ([read more](https://meta.discourse.org/t/-/401961/10?silent=true)).
* * *
_That’s a wrap—may your embeds keep their cookies, your sidebars use the “right” icon, and your asset builds stay comfortably under 20GB._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [6 Maggio 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/820 "2026-05-06T13:01:47Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New activity (last 24h):** **92 new posts** across **8 new topics** (plus ongoing discussions).
- **Most active / appreciated users:**
| User | Posts | Likes |
| --- | --- | --- |
| **@Lilly** | 10 | 17 |
| **@awesomerobot** | 4 | 13 |
| **@Moin** | 10 | 11 |
| **@nat** | 2 | 7 |
| **@eisammy** | 2 | 5 |
| **@Iury_Batista_Araujo** | 7 | 5 |
| **@NateDhaliwal** | 4 | 4 |
| **@derek** | 1 | 4 |
| **@Alteras** | 1 | 3 |
| **@itsbhanusharma** | 3 | 3 |
A lot of the day’s momentum centered around practical admin workflow questions (like suppressing categories in Latest) and quality-of-life fixes in UX/accessibility—see discussions like language + translation gaps in [What It’s Actually Like to Use Discourse in Another Language](https://meta.discourse.org/t/-/402177/3?silent=true) and category suppression in [Exclude category from latest](https://meta.discourse.org/t/-/402209/2?silent=true).
* * *
## Interesting Topics
### #blog
- @Lilly and @nat dug into what _actually_ gets translated (and what doesn’t) when running Discourse in other languages; plugin/theme strings were a big pain point, and @derek confirmed a missing theme translation string is now fixed in [What It’s Actually Like to Use Discourse in Another Language](https://meta.discourse.org/t/-/402177/8?silent=true) — with extra context on plugin translation gaps in [read more](https://meta.discourse.org/t/-/402177/3?silent=true).
### #Support
- @Andrew_Rowe wanted to stop a “daily noise” category from cluttering _Latest_ for everyone; the solution was the **discourse-categories-suppressed** plugin and related site settings discussed in [Exclude category from latest](https://meta.discourse.org/t/-/402209/2?silent=true) (and contrasted with `default_categories_muted` behavior in [read more](https://meta.discourse.org/t/-/402209/11?silent=true)).
- A self-hosted admin couldn’t access theme customization routes despite being admin; troubleshooting quickly converged on “you’re not actually on latest,” and @NateDhaliwal provided the canonical rebuild steps (`./launcher rebuild app`) in [Não consigo acessar a rota de customização de temas mesmo sendo admin](https://meta.discourse.org/t/-/402243/11?silent=true).
- Uploading \>100MB files looked like a Discourse limit at first, but the real culprit was upstream: Cloudflare’s 100MB cap on the free plan; the fix was to adjust Cloudflare settings, as confirmed in [Issue with Upload File Size Limit](https://meta.discourse.org/t/-/402272/6?silent=true).
- @ganncamp couldn’t find the newer “Site traffic” report and kept getting redirected to “Legacy Consolidated Pageviews”; the thread points to a hidden `use_legacy_pageviews` setting as a likely cause in [‘Site traffic report’?](https://meta.discourse.org/t/-/402288/3?silent=true), with background links to [Better pageview metrics with the new site traffic report](https://meta.discourse.org/t/-/324068/1?silent=true) and [Understanding pageviews and the site traffic report](https://meta.discourse.org/t/-/324062/1?silent=true).
- @Moin investigated an “Other notifications” bubble that didn’t show in the unread notifications list, sparking debugging questions around notification traceability in [Can I identify what caused this specific notification](https://meta.discourse.org/t/-/402276/1?silent=true) (and some initial guesswork / clarification from @chapoi in [read more](https://meta.discourse.org/t/-/402276/4?silent=true)).
- A self-hoster reported high memory use and looping behavior during asset precompile at runtime, including repeated `pnpm` activity; the root-cause exploration is captured in [Excessive consumption of memory due to precompiling assets](https://meta.discourse.org/t/-/402139/12?silent=true), with relevant background in [Introducing pre-compiled JS assets for self hosters](https://meta.discourse.org/t/-/376700/1?silent=true) and [Introducing a new build system for plugins](https://meta.discourse.org/t/-/398713/1?silent=true).
### #Self-hosting (tag: #hosting)
- A French thread walked through installing Discourse “behind” a non-publicly-routable IP for local testing; the conversation emphasized HTTPS requirements and suggested alternatives like Cloudflare Tunnel or a #dev-install workflow in [Installation auto-hébergée derrière une IP non-routée publiquement](https://meta.discourse.org/t/-/402198/7?silent=true), with supporting references to [Install Discourse on a residential internet with Cloudflare Tunnel](https://meta.discourse.org/t/-/211297/1?silent=true), [Allow SSL / HTTPS for your Discourse Docker setup](https://meta.discourse.org/t/-/13847/1?silent=true), and [Set up HTTPS support with Let’s Encrypt](https://meta.discourse.org/t/-/40709/1?silent=true).
### #ux (tags: #impersonate, #badges, #accessibility, #invites)
- Impersonation auto-terminates after a hidden 15-minute limit, but the UI doesn’t reflect it well; @martin outlined improvements like a MessageBus UI update and possibly bumping the limit in [Experience when impersonation is terminated automatically after some time](https://meta.discourse.org/t/-/402252/2?silent=true) (continuing the earlier thread in [New Bug With Experimental Impersonation Interface](https://meta.discourse.org/t/-/395621/10?silent=true)).
- Custom badge images were missing appropriate alt-text behavior; @awesomerobot confirmed the images are decorative and should use an empty alt attribute to avoid redundant screen reader output in [Custom Badges are not applying Alt Text](https://meta.discourse.org/t/-/401648/2?silent=true).
- Invite UX got polish: the “Invite” tab and related button behavior on profiles needed tightening, and @awesomerobot noted fixes are on the way in both [Invite tab shows on hidden profile](https://meta.discourse.org/t/-/401818/2?silent=true) and [Weird invite button behavior](https://meta.discourse.org/t/-/401819/5?silent=true).
- Review-queue workflows continued to be debated: the “request revision” pattern (especially when silencing is involved) remained a sticking point in [How to Understand the Request Revision Feature](https://meta.discourse.org/t/-/397258/7?silent=true), with the broader UX/feature direction discussed in [Allow the ability to Edit post on rejection](https://meta.discourse.org/t/-/373992/23?silent=true).
### #bug (tags: #surveys, #reactions, #ai, #ai-helper)
- Editing a survey after transferring topic ownership threw an error; the issue was acknowledged and fixed via a plugin commit, as tracked in [Unable to edit a survey](https://meta.discourse.org/t/-/402237/4?silent=true).
- A mobile interaction bug: long-pressing the reactions counter could incorrectly open the picker (and throw a `getBoundingClientRect` error); a PR was opened in [FIX: long pressing reactions-counter shouldn’t open ReactionsPicker](https://meta.discourse.org/t/-/402269/1?silent=true), with a related pointer to [Ability to display all the likes/reactions on a post](https://meta.discourse.org/t/-/389820/77?silent=true).
- AI Proofread/Proofreader behavior and quoting issues continued to be debugged, with @Falco pointing to local agent examples for troubleshooting in [Proofread breaks quotes](https://meta.discourse.org/t/-/365102/19?silent=true).
### #customization:theme-component
- The “Created Topic Sort” component shipped updates adding new settings for tag-based display behavior, announced in [Created Topic Sort](https://meta.discourse.org/t/-/321521/21?silent=true).
### #customization:plugin (tags: #paid-support, #openid-connect, #auth-plugins)
- The Locations plugin discussion flagged missing MaxMind environment variable hints in the newer slimmed `app.yml`, plus a sidebar link UX question; see [Locations Plugin](https://meta.discourse.org/t/-/69742/1237?silent=true) and the referenced setup guide [Configure MaxMind for reverse IP lookups](https://meta.discourse.org/t/-/173941/1?silent=true).
- OpenID Connect implementers discussed passing custom `/authorize` parameters reliably, asking what’s “officially supported” and what patterns are recommended in [Discourse OpenID Connect (OIDC)](https://meta.discourse.org/t/-/103632/324?silent=true).
### #Announcements (tag: #embedding)
- Questions came in about embedding Discourse as a comment system—specifically whether topics are auto-created on first use or must be created manually—in [Embed Discourse as a full comment system on your site](https://meta.discourse.org/t/-/399743/26?silent=true).
### #contribute:feature
- Admins revisited whether email notification settings can be adjusted at a **group** level (especially for onboarding cohorts), continuing the older request thread in [Email notification granularity](https://meta.discourse.org/t/-/164371/6?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @nat responded to translation edge-cases (notably plugins like calendar/events) and praised real-world multilingual traffic results shared by @eisammy in [What It’s Actually Like to Use Discourse in Another Language](https://meta.discourse.org/t/-/402177/13?silent=true) ([read more](https://meta.discourse.org/t/-/402177/3?silent=true)).
- @derek confirmed and shipped a fix for a missing **theme translation string** surfaced in the same multilingual UX discussion: [What It’s Actually Like to Use Discourse in Another Language](https://meta.discourse.org/t/-/402177/8?silent=true).
- @awesomerobot pushed multiple UX/accessibility fixes forward: decorative badge images should get empty alt text in [Custom Badges are not applying Alt Text](https://meta.discourse.org/t/-/401648/2?silent=true), plus invite/profile UX fixes in [Invite tab shows on hidden profile](https://meta.discourse.org/t/-/401818/2?silent=true) and [Weird invite button behavior](https://meta.discourse.org/t/-/401819/5?silent=true), and a forthcoming fix for request-revision confusion in [How to Understand the Request Revision Feature](https://meta.discourse.org/t/-/397258/6?silent=true).
- @sam acknowledged a surveys bug report and routed it for investigation in [Unable to edit a survey](https://meta.discourse.org/t/-/402237/2?silent=true).
- @techAPJ followed up with the fix commit for that surveys ownership/editing issue in [Unable to edit a survey](https://meta.discourse.org/t/-/402237/4?silent=true).
- @supermathie clarified free-tier constraints around theme customization access in [Não consigo acessar a rota de customização de temas mesmo sendo admin](https://meta.discourse.org/t/-/402243/3?silent=true), referencing the hosted offering discussed in [You’re invited to try the Discourse free plan beta](https://meta.discourse.org/t/-/395632/1?silent=true).
- @martin outlined concrete UX improvements for impersonation timeouts (and possibly increasing the default limit) in [Experience when impersonation is terminated automatically after some time](https://meta.discourse.org/t/-/402252/2?silent=true).
- @chapoi engaged in diagnosing a “mystery” notification bubble and what actions/links should reveal its source in [Can I identify what caused this specific notification](https://meta.discourse.org/t/-/402276/4?silent=true).
- @Alteras published updates to the Created Topic Sort theme component, adding new settings requested by users in [Created Topic Sort](https://meta.discourse.org/t/-/321521/21?silent=true).
- @Falco provided targeted troubleshooting guidance for AI proofread/quote breakage by pointing admins to local agent examples in [Proofread breaks quotes](https://meta.discourse.org/t/-/365102/19?silent=true).
* * *
Yesterday’s meta lesson: sometimes the _proof really is in the pudding_—especially when you’re testing translations, chasing phantom notification bubbles, and discovering Cloudflare was the “100MB limit” all along.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [7 Maggio 2026, 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/821 "2026-05-07T13:02:10Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
**Last 24 hours (2026-05-06 → 2026-05-07)**
- **New posts:** 72
- **New topics:** 12
**Top contributors (posts / likes received)**
| User | Posts | Likes |
| --- | --- | --- |
| @Lilly | 6 | 14 |
| @Thiago_Mobilon | 5 | 5 |
| @Falco | 3 | 7 |
| @Moin | 2 | 6 |
| @HAWK | 2 | 5 |
| @ted | 2 | 3 |
| @merefield | 1 | 5 |
| @tannerabread | 1 | 4 |
| @Heliosurge | 1 | 3 |
| @sam | 1 | 3 |
* * *
## Interesting Topics
### #Marketplace
- @Bryony asked for help building _safeguarding-first_ reporting UX (custom “report” buttons, different outcomes per option, emergency messaging, and notifications), and the thread quickly clarified this is **plugin** territory rather than theme work: [read more](https://meta.discourse.org/t/-/402296/1?silent=true). Related pointers included using Discourse’s custom flags as a starting point ([read more](https://meta.discourse.org/t/-/325589/1?silent=true)), concerns about automated flag PM wording ([read more](https://meta.discourse.org/t/-/329142/1?silent=true)), and a “report content to group” theme component as a partial workaround ([read more](https://meta.discourse.org/t/-/249323/1?silent=true)).
### #Support
- Custom “Top Menu” navigation filters came up again as a way to surface topics from specific (even muted) subcategories; the request was resolved by pointing to a theme component for custom top navigation links: [read more](https://meta.discourse.org/t/-/402317/1?silent=true) and the referenced solution ([read more](https://meta.discourse.org/t/-/87225/1?silent=true)). Follow-up discussion dug into a **mobile-only gap** when hiding the default nav menu ([read more](https://meta.discourse.org/t/-/402317/4?silent=true)), with broader context from the “muted subcategories in parent category” use case ([read more](https://meta.discourse.org/t/-/402315/1?silent=true)).
- The “Site traffic report” thread resurfaced confusion around why a promoted admin report can effectively disappear behind a hidden setting; the key detail was `SiteSetting.use_legacy_pageviews` and how it impacts what admins see: [read more](https://meta.discourse.org/t/-/402288/1?silent=true). For background, hidden site settings were cited as requiring Rails console access for self-hosters ([read more](https://meta.discourse.org/t/-/308773/1?silent=true)) and hosted customers needing to contact support for changes ([read more](https://meta.discourse.org/t/-/310574/1?silent=true)).
- A follow-on question compared “Legacy Consolidated Pageviews” vs “Site Traffic” crawler numbers (showing crawlers in one place and zeros in the other); the explanation was essentially **date-range / rollout alignment** and that the legacy report can be ignored going forward: [read more](https://meta.discourse.org/t/-/402347/1?silent=true). (This was explicitly framed as piggybacking on the original traffic-report discussion: [read more](https://meta.discourse.org/t/-/402288/1?silent=true)).
- A Discourse AI operator reported requests “randomly” exceeding LLM token thresholds; discussion focused on distinguishing **request size vs response size** (and what a 413 implies), plus the practical need to tune the configured context window: [read more](https://meta.discourse.org/t/-/402334/1?silent=true) and the key clarification reply ([read more](https://meta.discourse.org/t/-/402334/2?silent=true)).
- A mobile sign-up UX question asked how to place external login buttons (institutional SSO) _above_ the local “Simple Sign Up” form, to reduce student mis-signups when arriving via QR/invite; theme/CSS reordering was proposed: [read more](https://meta.discourse.org/t/-/402339/1?silent=true).
- An SSO/identity architecture question asked if enabling **[DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) provider** breaks native login; the answer was “no”—provider mode can be enabled without changing the forum’s own login experience: [read more](https://meta.discourse.org/t/-/402359/1?silent=true). The question referenced the broader [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) setup guidance thread ([read more](https://meta.discourse.org/t/-/32974/1?silent=true)).
- A small-but-real linking edge case: punctuation after a URL (like a trailing period) can cause auto-linking to capture the dot and break the link, especially with routes like `.rss` in play: [read more](https://meta.discourse.org/t/-/402371/1?silent=true).
- A support thread investigated a situation where a forum appeared to show “mailcow” instead of Discourse after a config change; replies strongly suggested a DNS/server/caching mismatch and recommended restarting/clearing cache: [read more](https://meta.discourse.org/t/-/402380/1?silent=true). (Related self-hosting “it works for me now” reverse-proxy operational notes also appeared elsewhere: [read more](https://meta.discourse.org/t/-/300191/9?silent=true)).
### #contribute:feature
- #embedding received two complementary updates: a real-world “Discourse Comments” conversion/UX note that native login still leaves iframe embeds looking logged out until refresh ([read more](https://meta.discourse.org/t/-/400721/47?silent=true)), plus a pointer to ongoing work improving the login flow ([read more](https://meta.discourse.org/t/-/400721/48?silent=true)). In parallel, the canonical embed announcement thread reiterated that embedded comments can **auto-create topics on first visit** ([read more](https://meta.discourse.org/t/-/399743/27?silent=true)) and linked back to the long-running embed how-to documentation ([read more](https://meta.discourse.org/t/-/31963/1?silent=true)).
- A long-running request about showing **all likes/reactions** in the post “liked by” modal got a practical pointer: enabling an upcoming change in admin can make the list load more users rather than truncating early: [read more](https://meta.discourse.org/t/-/389820/90?silent=true).
### #bug
- A bug report noted missing **paste** functionality in form-template composer fields; a fix is actively in progress: [read more](https://meta.discourse.org/t/-/402250/12?silent=true).
- Schema/SEO monitoring continued for “Missing field `text` in `mainEntity.suggestedAnswer`”; guidance suggested using Google’s “test live URL” to rule out cached validation artifacts, with follow-up reports of new affected URLs: [read more](https://meta.discourse.org/t/-/399974/20?silent=true) and the fresh example report ([read more](https://meta.discourse.org/t/-/399974/21?silent=true)).
### #ux
- Impersonation timeout UX: discussion considered whether the auto-termination timer should be “15 minutes of inactivity” vs a fixed countdown, and concluded that clearer messaging might be the safer improvement (given configurable duration and unclear original intent): [read more](https://meta.discourse.org/t/-/402252/4?silent=true) and the follow-up reasoning ([read more](https://meta.discourse.org/t/-/402252/6?silent=true)).
### #blog
- A new companion discussion thread for the Discourse blog post “The Digg Lesson: Why Moderation Infrastructure Matters” kicked off broader reflection on moderation tooling, brigading, and the “arms race” nature of community safety: [read more](https://meta.discourse.org/t/-/402362/1?silent=true).
### #community-building Building
- A Russian-language question asked how many subcategories display within a parent category (and where to configure that), for a “cities as subcategories” structure: [read more](https://meta.discourse.org/t/-/402386/1?silent=true).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Falco weighed in on improving the embedded-comments login experience and shared that work is underway to make the flow better: [read more](https://meta.discourse.org/t/-/400721/48?silent=true). @Falco also responded to the Discourse AI token-limit report, clarifying that a 413 indicates **request too large** (not response tokens) and pointing at context window configuration: [read more](https://meta.discourse.org/t/-/402334/2?silent=true).
- @HAWK published the companion discussion topic for the Discourse blog article on Digg and moderation infrastructure: [read more](https://meta.discourse.org/t/-/402362/1?silent=true).
- @tannerabread confirmed a real missing capability (paste in form-template composer fields) and stated a fix is in progress: [read more](https://meta.discourse.org/t/-/402250/12?silent=true).
- @sam pointed admins to the **/admin/config/upcoming-changes** toggle that enables a “load more” style for the likes popup list: [read more](https://meta.discourse.org/t/-/389820/90?silent=true).
- @supermathie answered an SSO/identity-provider question: enabling **[DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) provider** should not disrupt native login on the Discourse site: [read more](https://meta.discourse.org/t/-/402359/2?silent=true).
- @awesomerobot explained why crawlers can show as zero in the “Site Traffic” report for older dates (rollout alignment and hidden/filtered pre-rollout data), helping reconcile the discrepancy with legacy pageview reports: [read more](https://meta.discourse.org/t/-/402347/2?silent=true).
- @pmusaraj reviewed a proposal to unify public activity across chats/topics/categories in a single view, questioning whether categories belong alongside “content items” like topics and chat channels: [read more](https://meta.discourse.org/t/-/402173/3?silent=true).
- @martin continued the internal UX discussion around impersonation timeouts, weighing the intent and security implications of redefining “inactivity” vs fixed timers: [read more](https://meta.discourse.org/t/-/402252/5?silent=true).
- @chapoi helped troubleshoot a theme-component issue (“Discourse Age Check”) by asking for console errors and confirming reproduction steps: [read more](https://meta.discourse.org/t/-/397002/19?silent=true).
- @davidb suggested using Google Search Console’s “test live URL” to distinguish cached schema errors from current behavior and noted trending improvements after merged fixes: [read more](https://meta.discourse.org/t/-/399974/20?silent=true).
Yesterday’s moral: keep your moderation tools sharp and your login flows smooth—nobody wants a “Digg redesign moment” for their community.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [8 Maggio 2026, 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/822 "2026-05-08T13:02:24Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h):** 118
- **New topics (last 24h):** 14
- **Biggest “where did that go / why did that change?” energy:** tag UI + bootstrap mode + custom homepages (see [read more](https://meta.discourse.org/t/-/402436/1?silent=true), [read more](https://meta.discourse.org/t/-/402468/1?silent=true), [read more](https://meta.discourse.org/t/-/402425/1?silent=true))
**Most active touchpoints (sample of what drove discussion):**
- Discourse Discover’s new “hot topics” surfacing ([read more](https://meta.discourse.org/t/-/401974/1?silent=true))
- Markdown link edge-cases + the angle-bracket workaround ([read more](https://meta.discourse.org/t/-/402371/8?silent=true))
- Discourse ID + “full name required” signup flow oddities ([read more](https://meta.discourse.org/t/-/402392/12?silent=true))
- AI translation workflows getting stuck on “thinking” models ([read more](https://meta.discourse.org/t/-/401478/12?silent=true))
- OIDC group sync unexpectedly removing unrelated group memberships ([read more](https://meta.discourse.org/t/-/402416/1?silent=true))
### Top users (posts + likes in the last 24h)
| User | Posts | Likes | Recent highlight |
| --- | --- | --- | --- |
| @Moin | 14 | 26 | Proposed a better UX when a theme-specific homepage goes missing after login ([read more](https://meta.discourse.org/t/-/402425/1?silent=true)) |
| @Lilly | 18 | 17 | Helped diagnose markdown/linkify behavior and user setup flows ([read more](https://meta.discourse.org/t/-/402371/6?silent=true)) |
| @gabriel | 1 | 9 | Announced “Discover Hot Topics” for #discourse-discover ([read more](https://meta.discourse.org/t/-/401974/1?silent=true)) |
| @pmusaraj | 5 | 6 | Confirmed signup/full-name behavior needs a fix; moved it into #bug ([read more](https://meta.discourse.org/t/-/402392/12?silent=true)) |
| @david | 1 | 5 | Shared the practical “use angle brackets” solution for URLs at sentence ends ([read more](https://meta.discourse.org/t/-/402371/8?silent=true)) |
| @hammerdunner | 4 | 5 | Reported Discourse ID signup ignoring “full name required” expectations ([read more](https://meta.discourse.org/t/-/402392/1?silent=true)) |
| @NateDhaliwal | 5 | 4 | Pointed folks to landing pages + page publishing options ([read more](https://meta.discourse.org/t/-/402465/2?silent=true)) |
| @Falco | 3 | 4 | Identified link parsing source + helped debug AI translation stalls ([read more](https://meta.discourse.org/t/-/402371/7?silent=true)) |
| @Ed_S | 3 | 4 | Flagged confusion around “Nice Share” badge attribution ([read more](https://meta.discourse.org/t/-/402438/1?silent=true)) |
| @darkpixlz | 4 | 4 | Chatted DiscourseHub/TestFlight reality + splash screen customization limits ([read more](https://meta.discourse.org/t/-/402456/2?silent=true)) |
* * *
## Interesting Topics
### #announcements
- @gabriel introduced **Discover “Hot Topics”** —a new way to surface the most active discussions across Discourse communities, grouped by subject, inside Discourse Discover (#discourse-discover) ([read more](https://meta.discourse.org/t/-/401974/1?silent=true)); background context also lives in the earlier Discourse Discover overview ([read more](https://meta.discourse.org/t/-/295223/1?silent=true)).
### #Support
- A markdown/linkify edge-case: **punctuation and brackets can become part of a detected URL** , and the practical fix is to wrap the URL in angle brackets—though quoting can complicate that presentation ([read more](https://meta.discourse.org/t/-/402371/8?silent=true)); @Falco traced it to `markdown-it/linkify-it` behavior ([read more](https://meta.discourse.org/t/-/402371/7?silent=true)).
- A “Nice Share” badge confusion was cleared up: it’s tied to **referral-style links with `?u=` getting clicked** , not necessarily the badge recipient owning the linked post ([read more](https://meta.discourse.org/t/-/402438/2?silent=true)).
- “Bootstrap mode is legacy?” sparked a useful archaeology thread on _what bootstrap mode used to do_ and what remains configurable via site settings today ([read more](https://meta.discourse.org/t/-/402468/1?silent=true)); related background on bootstrap effects and its removal came up via older references ([read more](https://meta.discourse.org/t/-/58462/2?silent=true), [read more](https://meta.discourse.org/t/-/322876/1?silent=true)).
- Tag UI basics: how to **change the title/description shown on a tag page** (hint: the wrench/controls on the tag-filtered topic list) ([read more](https://meta.discourse.org/t/-/402430/2?silent=true)).
- “How do I make a static page?” got pointed toward the modern toolbox: the **Landing Pages plugin** and **Page Publishing** (and a note that an older static pages plugin is broken) ([read more](https://meta.discourse.org/t/-/402465/2?silent=true), plus [read more](https://meta.discourse.org/t/-/180967/1?silent=true) and [read more](https://meta.discourse.org/t/-/151971/1?silent=true); historical footnote: [read more](https://meta.discourse.org/t/-/69698/1?silent=true)).
- A newly-upgraded site asked if the **blue “Discourse Splash” preloader dots** can be disabled; the answer leaned toward “no, but you can customize what appears” ([read more](https://meta.discourse.org/t/-/402456/1?silent=true)); original splash introduction for context ([read more](https://meta.discourse.org/t/-/232003/1?silent=true)).
- A Russian-language admin question explored how many **subcategories can/should be displayed under a parent category** (including the practical reality of trying ~30 “city” subcats) ([read more](https://meta.discourse.org/t/-/402386/1?silent=true)).
### #bug
- A hosted signup flow issue: when using **Discourse ID** , “full name required” didn’t behave as expected—testing suggested Discourse ID autofill + signup flow needs adjustment, and the report was moved to #bug for follow-up ([read more](https://meta.discourse.org/t/-/402392/12?silent=true)).
- **OpenID Connect group sync** may remove users from _all_ non-synced groups when a single OIDC group disappears from the claim; @supermathie proposed a crisp repro summary to validate the behavior ([read more](https://meta.discourse.org/t/-/402416/3?silent=true), original report: [read more](https://meta.discourse.org/t/-/402416/1?silent=true)).
- Structured data / schema debugging continued: missing `mainEntity.suggestedAnswer.text` appears linked to topics whose OP has **no text content** , prompting investigation into skipping/placeholder behavior ([read more](https://meta.discourse.org/t/-/399974/26?silent=true), more detail from the field: [read more](https://meta.discourse.org/t/-/399974/25?silent=true)).
### #ux
- A theme-switching gotcha: if your default theme has a `/custom` homepage but your user-selected theme doesn’t, users can land on a **blank custom page after login** —suggestion: show a friendly “Take me home” affordance instead ([read more](https://meta.discourse.org/t/-/402425/1?silent=true)).
- The **“Permanent” filter on Upcoming Changes** appeared empty and raised questions about what should be listed there (especially after changes become permanent) ([read more](https://meta.discourse.org/t/-/402433/1?silent=true)).
- “Where did the tag info button go?” tracked a UI affordance regression/relocation: non-admin users can’t easily find **tag descriptions/usage help** that used to be surfaced via an info icon ([read more](https://meta.discourse.org/t/-/402436/1?silent=true)); older references cited in the discussion include prior guidance screenshots ([read more](https://meta.discourse.org/t/-/125187/23?silent=true), [read more](https://meta.discourse.org/t/-/307762/6?silent=true)).
### #customization:plugin
- The long-running #official Discourse Translator discussion clarified strategy: **pick one translation UX** , and the newer automatic translation path is preferred as the older experience deprecates ([read more](https://meta.discourse.org/t/-/32630/453?silent=true)).
### #contribute:feature
- A thoughtful localization UX request: translated posts currently lose useful quote metadata (topic linkage + the “more context” affordance), making **translated quotes less informative than originals** ([read more](https://meta.discourse.org/t/-/402420/1?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @gabriel shipped the day’s headline: **Discover Hot Topics** for #discourse-discover, expanding cross-community discovery in DiscourseHub and beyond ([read more](https://meta.discourse.org/t/-/401974/1?silent=true); earlier Discover overview: [read more](https://meta.discourse.org/t/-/295223/1?silent=true)).
- @pmusaraj jumped into both product and troubleshooting threads—answering DiscourseHub/TestFlight questions ([read more](https://meta.discourse.org/t/-/401974/5?silent=true)) and confirming the **Discourse ID + full-name requirement** flow likely needs a fix, moving it into #bug ([read more](https://meta.discourse.org/t/-/402392/12?silent=true)); they also continued engaging on chat-as-content experiments ([read more](https://meta.discourse.org/t/-/402173/5?silent=true)).
- @david provided the concrete solution for link parsing ambiguity: **use angle brackets to explicitly bound URLs** when punctuation/brackets are involved ([read more](https://meta.discourse.org/t/-/402371/8?silent=true)).
- @Falco traced the bracket/URL behavior to the underlying library defaults ([read more](https://meta.discourse.org/t/-/402371/7?silent=true)) and helped diagnose why AI translations can stall when locale detection meets “thinking” model output formats ([read more](https://meta.discourse.org/t/-/401478/12?silent=true)); they also engaged on an embedded-comments UI bug report in the Tecnoblog case study thread ([read more](https://meta.discourse.org/t/-/400721/50?silent=true)).
- @nat clarified the direction for Discourse Translator: avoid running _both_ translation experiences, and prefer the newer automatic translations since the older path is deprecating ([read more](https://meta.discourse.org/t/-/32630/453?silent=true)).
- @davidb investigated schema validation errors and suspected a key trigger: **OPs with no text** can break QAPage schema expectations, suggesting either skipping or filling placeholders ([read more](https://meta.discourse.org/t/-/399974/26?silent=true)).
- @supermathie worked on pinning down the OpenID Connect group sync issue by proposing a precise reproduction summary (critical when group membership changes could remove access) ([read more](https://meta.discourse.org/t/-/402416/3?silent=true)).
- @awesomerobot acknowledged a fix is inbound for **mobile tag display truncation** (“long tags are cut off at screen edge”) ([read more](https://meta.discourse.org/t/-/401585/2?silent=true)).
* * *
Yesterday’s lesson: may your URLs be neatly wrapped in angle brackets, your tag info buttons stay discoverable, and your blue splash dots blink only _briefly_.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [9 Maggio 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/823 "2026-05-09T13:01:34Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 50**
- **New topics (last 24h): 6**
- **Where the conversation clustered:** lots of hands-on admin troubleshooting in **#Support** (e.g. [bootstrap mode changes](https://meta.discourse.org/t/-/402468/4?silent=true), and [splash screen behavior](https://meta.discourse.org/t/-/402456/6?silent=true)) plus implementation-level debugging in **#bug** (e.g. [OpenID Connect group sync](https://meta.discourse.org/t/-/402416/6?silent=true), and [AI translation failures](https://meta.discourse.org/t/-/402477/1?silent=true)).
**Top users by recent activity (posts) & appreciation (likes):**
- **@pmusaraj** — **6 posts** , **16 likes** (notably clarifying what replaced bootstrap mode and what should be kept: [read more](https://meta.discourse.org/t/-/402468/4?silent=true))
- **@Falco** — **6 posts** , **2 likes** (hands-on debugging advice for translation logs: [read more](https://meta.discourse.org/t/-/402477/2?silent=true))
- **@markvanlan** — **4 posts** , **2 likes** (testing notification behavior in nested replies: [read more](https://meta.discourse.org/t/-/398759/108?silent=true))
- **@Moin** — **3 posts** , **9 likes** (pushing for accuracy on how bootstrap mode was actually enabled: [read more](https://meta.discourse.org/t/-/402468/5?silent=true))
- **@Lilly** — **3 posts** , **4 likes** (practical mobile CSS guidance for category styling: [read more](https://meta.discourse.org/t/-/402473/2?silent=true))
- **@RGJ** — **3 posts** , **2 likes** (reviewing plugin behavior & PR expectations: [read more](https://meta.discourse.org/t/-/227824/42?silent=true))
- **@rokejulianlockhart** — **1 post** , **2 likes** (looping back to the perennial “threaded vs. linear” debate: [read more](https://meta.discourse.org/t/-/63172/85?silent=true))
- **@Canapin** — **1 post** , **6 likes** (a memorable rule of thumb for “healthy updates”: [read more](https://meta.discourse.org/t/-/402456/8?silent=true))
- **@keegan** — **1 post** , **2 likes** (confirming an embed-related fix landed: [read more](https://meta.discourse.org/t/-/400721/52?silent=true))
- **@darkpixlz** — **1 post** , **2 likes** (asking about user directory refresh timing: [read more](https://meta.discourse.org/t/-/402468/11?silent=true))
> **Notable quotable:** @Canapin’s maintenance heuristic—“updated when the dashboard emoji becomes red”—became the day’s most-liked one-liner ([source](https://meta.discourse.org/t/-/402456/8?silent=true)).
* * *
## Interesting Topics
### #Support
- **Bootstrap mode appears “legacy” — what changed, and what should remain?** @pmusaraj explained bootstrap mode had effectively faded away and that **the admin onboarding panel** is the new “nudge” mechanism ([read more](https://meta.discourse.org/t/-/402468/4?silent=true)); @Moin challenged the timeline and pointed to prior discussion that implied bootstrap mode was still active ([read more](https://meta.discourse.org/t/-/402468/5?silent=true)), referencing the older deep-dive on behavior details ([read more](https://meta.discourse.org/t/-/320673/4?silent=true)).
- **Disabling the “preloader-image” / splash screen is no longer a toggle (and why)**: @awesomerobot confirmed the setting to disable the splash screen was removed, citing stability and potential **Core Web Vitals** impact, and offered a clever workaround via a transparent animated SVG ([read more](https://meta.discourse.org/t/-/402456/6?silent=true)); the thread also featured some lighthearted ops advice ([read more](https://meta.discourse.org/t/-/402456/8?silent=true)).
- **Mobile-only category background styling (Horizon theme)**: @Lilly shared a clean SCSS approach using viewport mixins and category targeting, plus optional dark/light variable handling ([read more](https://meta.discourse.org/t/-/402473/2?silent=true); follow-up snippet: [read more](https://meta.discourse.org/t/-/402473/3?silent=true)).
- **Custom dropdown user field “unselectable value” showing up (possible bot signal?)**: A report that spambots appear to submit values not present in the dropdown options—raising both _honeypot_ implications and potential validation gaps ([read more](https://meta.discourse.org/t/-/402557/1?silent=true)).
### #bug
- **OpenID Connect group sync can remove users from unrelated groups** : A bug report highlighted that OIDC group syncing could kick users out of groups that aren’t being synced; @pmusaraj linked a fix PR intended to resolve it ([read more](https://meta.discourse.org/t/-/402416/6?silent=true)).
- **AI translations failing with “Raw can’t be blank / Cooked can’t be blank”** : @Falco guided debugging via `/p/ID` and `ai_api_audit_logs` queries ([read more](https://meta.discourse.org/t/-/402477/2?silent=true); query correction: [read more](https://meta.discourse.org/t/-/402477/4?silent=true)), and later identified token starvation from _reasoning_ output as a likely root cause ([read more](https://meta.discourse.org/t/-/402477/8?silent=true)), tying it to prior translation-scale troubleshooting ([read more](https://meta.discourse.org/t/-/385414/12?silent=true)).
- **“Middleware document tree depth exceeded” still biting (patch referenced)**: A fix was pointed to via a linked PR, continuing the effort to stamp out this recurring error ([read more](https://meta.discourse.org/t/-/402426/2?silent=true)).
- **Selecting “no tag” then switching categories causes an error page** : A Chinese-language report shows a reproducible UI flow ending in “page doesn’t exist or isn’t public,” with an animated repro GIF ([read more](https://meta.discourse.org/t/-/402545/1?silent=true)).
### #ux
- **Custom homepage goes blank for regular users — suggest a “Take me home” button** : A UX proposal to avoid dead-end custom pages for non-staff drew acknowledgement from @derek, who said the team would investigate and report back ([read more](https://meta.discourse.org/t/-/402425/3?silent=true)).
- **“Split this topic” mini-post link behavior still confusing** : Follow-up discussion notes those system posts lack a post menu and don’t auto-update the link the way users expect ([read more](https://meta.discourse.org/t/-/400249/12?silent=true)).
### #Self-hosting
- **AWS Lightsail + Ubuntu LTS upgrades: in-place vs. snapshot-and-restore strategy** : A self-host admin asked for real-world experiences planning the jump from Ubuntu 20.04 to newer LTS on Lightsail and whether rebuild-from-snapshot remains the safest pattern ([read more](https://meta.discourse.org/t/-/402512/1?silent=true)).
### #Nested Replies Testing
- **Nested replies notification behavior: does consolidation “feel right”?** @markvanlan ran a quick series of notification tests in the experimental nested replies area ([read more](https://meta.discourse.org/t/-/398759/108?silent=true); continuation: [read more](https://meta.discourse.org/t/-/398759/111?silent=true)), while others compared it to journaling-style workflows ([read more](https://meta.discourse.org/t/-/398759/112?silent=true); related: [read more](https://meta.discourse.org/t/-/317785/1?silent=true)) and broader skepticism about threading complexity over time ([read more](https://meta.discourse.org/t/-/63172/85?silent=true)).
### #contribute:feature
- **Discourse Comments embed: editing inside iframe layout glitch** : In the ongoing field report from Tecnoblog’s Discourse Comments usage, @keegan confirmed a fix landed for an iframe edit-mode blank-space/layout shift bug ([read more](https://meta.discourse.org/t/-/400721/52?silent=true)).
### #customization:plugin
- **Geo Blocking plugin: request for an “allowlist-first” mode (and PR review expectations)**: A user requested a configuration where only certain countries can access (deny-by-default), with precedence rules for allowlist vs blocklist ([read more](https://meta.discourse.org/t/-/227824/41?silent=true)); @RGJ suggested a backwards-compatible approach and asked for smaller, focused PRs ([read more](https://meta.discourse.org/t/-/227824/42?silent=true); review feedback: [read more](https://meta.discourse.org/t/-/227824/44?silent=true)).
- **Trading Buttons plugin: is the per-category enable/disable actually working?** @RGJ asked whether the category-level setting functions as intended, alongside ongoing maintenance concerns ([read more](https://meta.discourse.org/t/-/71308/133?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- **@pmusaraj** clarified that bootstrap mode has effectively been superseded by a lighter-touch onboarding panel, then revisited the history after @Moin challenged the details—ultimately agreeing bootstrap mode did have some “niceties” worth preserving ([bootstrap discussion](https://meta.discourse.org/t/-/402468/4?silent=true), correction/research follow-up: [read more](https://meta.discourse.org/t/-/402468/7?silent=true), and the idea to refresh directory views more frequently for very small sites: [read more](https://meta.discourse.org/t/-/402468/10?silent=true)). @pmusaraj also linked a fix for an OpenID Connect group-sync edge case ([read more](https://meta.discourse.org/t/-/402416/6?silent=true)).
- **@awesomerobot** confirmed the removal of the “disable splash screen” setting, explained the SEO/perf rationale, and provided a workaround path using a custom (even transparent) animated SVG ([read more](https://meta.discourse.org/t/-/402456/6?silent=true)).
- **@Falco** contributed to troubleshooting across multiple threads: chiming in on the splash-screen topic ([read more](https://meta.discourse.org/t/-/402456/7?silent=true)), pointing to a fix PR for the “document tree depth” issue ([read more](https://meta.discourse.org/t/-/402426/2?silent=true)), and walking through debugging steps for AI translation errors—ultimately attributing failures to reasoning tokens exhausting the completion budget ([read more](https://meta.discourse.org/t/-/402477/2?silent=true), follow-up guidance: [read more](https://meta.discourse.org/t/-/402477/6?silent=true), conclusion: [read more](https://meta.discourse.org/t/-/402477/8?silent=true)).
- **@markvanlan** ran a compact set of “how do these notifications feel?” experiments inside the nested replies testbed ([read more](https://meta.discourse.org/t/-/398759/108?silent=true); also: [read more](https://meta.discourse.org/t/-/398759/110?silent=true)).
- **@keegan** confirmed a Discourse Comments embed bugfix shipped for iframe edit-mode layout issues reported by a production user ([read more](https://meta.discourse.org/t/-/400721/52?silent=true)).
- **@derek** acknowledged a UX report about regular users hitting blank custom pages and said the team would investigate and update ([read more](https://meta.discourse.org/t/-/402425/3?silent=true)).
* * *
If your dashboard emoji is starting to look _a little too red_, it might be time to ship that fix—and maybe swap your splash screen for a stylish animated SVG while you’re at it ([read more](https://meta.discourse.org/t/-/402456/8?silent=true)).
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [10 Maggio 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/824 "2026-05-10T13:01:16Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 37**
- **New topics (last 24h): 9**
**Top contributors (posts / likes, last 24h):**
- **@Lilly** — **6 posts** , **13 likes**
- **@Noble_Fish** — **4 posts** , **5 likes**
- **@Moin** — **2 posts** , **7 likes**
- **@merefield** — **2 posts** , **4 likes**
- **@Falco** — **2 posts** , **4 likes**
- **@Sukenik** — **2 posts** , **0 likes**
- **@nathank** — **1 post** , **3 likes**
- **@jack222** — **1 post** , **2 likes**
- **@gilles** — **1 post** , **1 like**
- **@cuo_wu** — **1 post** , **0 likes**
> If you only have time for a quick scan, today leaned heavily into _migration/ops_, _localization quirks_, and _UX papercuts_—plus some lively plugin/theme component iteration.
* * *
## Interesting Topics
### #Self-hosting (#install)
- @merefield asked about realistic migration/upgrade timing, and @Falco recommended the “spin up new server → read-only old site → backup/restore → DNS cutover” approach (plus lowering DNS TTL in advance), with @Lilly confirming the same method worked well during a long-distance Docker move ([read more](https://meta.discourse.org/t/-/402512/3?silent=true), [read more](https://meta.discourse.org/t/-/402512/4?silent=true))
### #Support
- A “why does it say _regular_ under my username?” question turned into a helpful explainer: @Lilly pointed to trust levels, while @Moin clarified it’s a selectable _Title_ once earned via badges ([read more](https://meta.discourse.org/t/-/402579/2?silent=true), [read more](https://meta.discourse.org/t/-/402579/3?silent=true), plus the trust-level reference: [read more](https://meta.discourse.org/t/-/396792/1?silent=true))
- A guest-access concern in Chinese: @jack222 reported that logged-out visitors can’t view **/activity/reactions** and asked for either a setting to allow it or a clearer error message indicating login is required ([read more](https://meta.discourse.org/t/-/402588/1?silent=true))
- @Noble_Fish proposed that **“New topic approval”** and **“New reply approval”** need _global default_ counterparts for workflows where only certain users later become “must-approve” without needing category-by-category configuration ([read more](https://meta.discourse.org/t/-/402590/1?silent=true))
- A forensic/logging question: @Sukenik asked how one might establish (years later) whether suspensions carried over during a Discourse → custom-forum migration; @Andrew_Rowe noted hosting details matter and that long-term log retention is often limited, with follow-up context about a large platform running parallel migrations ([read more](https://meta.discourse.org/t/-/402581/1?silent=true), [read more](https://meta.discourse.org/t/-/402581/2?silent=true), [read more](https://meta.discourse.org/t/-/402581/3?silent=true))
### #ux (#dark-theme, #meta-redesign-2026)
- Dark-theme readability feedback: @Noble_Fish flagged low-contrast text (including Titles) and a “dark yellow” highlight row in the user list that makes scanning harder in the current redesign context ([read more](https://meta.discourse.org/t/-/402573/1?silent=true))
### #bug (#translation, #content-localization)
- @Moin investigated an “unexpected language code” problem and suggested the invalid `hreflang` may originate in core when locales include underscores—proposing conversion to hyphens (e.g., `tr('_', '-')`) to avoid malformed values ([read more](https://meta.discourse.org/t/-/402544/3?silent=true))
### #Support (#translation, #user-custom-fields, #content-localization)
- @cuo_wu asked how to make **custom user fields** display in multiple languages; @Lilly indicated it’s likely a feature request and linked the existing request to make custom user field names/descriptions translatable ([read more](https://meta.discourse.org/t/-/402568/2?silent=true), related: [read more](https://meta.discourse.org/t/-/221479/1?silent=true))
### #bug (#user-custom-fields)
- A dropdown custom user field ended up storing “unselectable” values; @Lilly suggested bots may bypass front-end validation via API signup, recommended tightening anti-spam (including hCaptcha), and shared a [Data Explorer](https://meta.discourse.org/t/32566?silent=true) query to find offending rows ([read more](https://meta.discourse.org/t/-/402557/2?silent=true), hCaptcha reference: [read more](https://meta.discourse.org/t/-/291383/1?silent=true))
### #bug (#composer)
- Rich-text composer behavior: @Noble_Fish reported that dragging an **unselected** image triggers a re-upload instead of moving it in-place, and asked whether that’s intentional or a design/UX bug ([read more](https://meta.discourse.org/t/-/402566/1?silent=true))
### #customization:theme component
- The **Quote Callouts** component discussion continued: @Noble_Fish noted callouts still render citation-style in revision history, @nathank pointed out similar oddities in excerpts/oneboxes, and @scavin raised a macOS shortcut hazard (“Ctrl+Q” muscle memory colliding with “⌘+Q” quit); @Arkshine discussed edge cases and floated safer shortcut alternatives ([read more](https://meta.discourse.org/t/-/350962/64?silent=true), [read more](https://meta.discourse.org/t/-/350962/65?silent=true), [read more](https://meta.discourse.org/t/-/350962/66?silent=true), [read more](https://meta.discourse.org/t/-/350962/67?silent=true))
### #Announcements (#upcoming-changes)
- In the “Upcoming Changes” system thread, @Lilly asked whether the UI notifications can be disabled _without_ CSS hacks (sharing a CSS snippet that hides the alerts), and @NateDhaliwal noted the notification count/indicator may still remain ([read more](https://meta.discourse.org/t/-/392894/23?silent=true), [read more](https://meta.discourse.org/t/-/392894/24?silent=true))
### #customization:plugin (#paid-support)
- **Locations Plugin** status update: @merefield said a fix is now deployed (plus compatibility work) and explained a widened gap between Early Access vs public versions—highlighting sponsor-only features like a 3D users-map globe and IP-based location lookup; @gilles replied with thanks ([read more](https://meta.discourse.org/t/-/69742/1240?silent=true), [read more](https://meta.discourse.org/t/-/69742/1241?silent=true))
### #customization:plugin
- **Trading Buttons** saw modernization work: @Janno_Liivak updated the plugin to reduce browser console warnings and align better with FormKit, asking the community to report any issues ([read more](https://meta.discourse.org/t/-/71308/135?silent=true))
### #Site Management (#how-to, #ai)
- On the Discourse AI LLM settings page, @danhanghai reported trouble getting `gemini-3.1-flash-lite` working with the Google provider endpoint, sharing their configuration details while seeking guidance ([read more](https://meta.discourse.org/t/-/319903/22?silent=true))
### #bug (#ai)
- AI translations troubleshooting continued: after switching models, @RBoy hit a `json_schema`/structured outputs limitation error, and @Falco advised using a model that supports structured outputs (common among recent state-of-the-art models) ([read more](https://meta.discourse.org/t/-/402477/10?silent=true), [read more](https://meta.discourse.org/t/-/402477/11?silent=true))
### #bug
- A Chinese-language repro note: @NateDhaliwal confirmed an issue can be reproduced on Meta where choosing “no tag” in one category then switching categories triggers a “page doesn’t exist / not public” style error ([read more](https://meta.discourse.org/t/-/402545/2?silent=true))
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Falco weighed in on best-practice self-host migration strategy— **restore to a fresh server and flip DNS with a lowered TTL** , rather than attempting risky in-place release upgrades ([read more](https://meta.discourse.org/t/-/402512/3?silent=true))
- @Falco also helped unblock an AI translations thread by pointing out the reported error indicates a **structured outputs** requirement, and that the fix is to choose a model that supports it ([read more](https://meta.discourse.org/t/-/402477/11?silent=true))
* * *
Migration plans got sharper, callouts got safer, and someone out there is definitely lowering their DNS TTL to 5 minutes _right now_—see you tomorrow for another round of Meta detective work.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [11 Maggio 2026, 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/825 "2026-05-11T13:02:20Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 71**
- **New topics (last 24h): 5**
**Top users (posts / likes):**
| User | Posts | Likes |
| --- | --- | --- |
| @Lilly | 9 | 11 |
| @Moin | 5 | 8 |
| @denvergeeks | 5 | 3 |
| @Noble_Fish | 6 | 2 |
| @chapoi | 7 | 2 |
| @fzngagan | 1 | 4 |
| @janbolmeson | 1 | 3 |
| @nat | 1 | 3 |
| @klappradla | 2 | 2 |
| @Janno_Liivak | 1 | 1 |
**Also seeing activity / bumps worth a look:** discussions around scheduling and automation ([read more](https://meta.discourse.org/t/-/192093/6?silent=true), [read more](https://meta.discourse.org/t/-/60731/1?silent=true), [read more](https://meta.discourse.org/t/-/195773/1?silent=true)), plugin support ([read more](https://meta.discourse.org/t/-/71308/136?silent=true)), structured data/SEO reports ([read more](https://meta.discourse.org/t/-/399974/29?silent=true)), and language/locale edge cases ([read more](https://meta.discourse.org/t/-/402544/5?silent=true)).
## Interesting Topics
### #Support
- A self-host reported **Badges failing to load** and missing admin settings; troubleshooting quickly converged on “too many / unofficial plugins” (including _theme creator installed as a plugin_) and possible environment pitfalls like missing SMTP port and storage choices in [Badges Error launching](https://meta.discourse.org/t/-/402594/16?silent=true) (#badges). Related/duplicate context: [Discourse badges error](https://meta.discourse.org/t/-/377124/5?silent=true).
- A question about allowing **anonymous access to** `/activity/reactions` got redirected to an existing UX request in [游客对于 /activity/reactions 页面的查看权限修改](https://meta.discourse.org/t/-/402588/2?silent=true) (#reactions), with the canonical discussion at [Allow /activity/reactions to be visible by anon](https://meta.discourse.org/t/-/366430/1?silent=true).
- A newcomer asked “what are **cheers**?” and got pointed to prior explanations and the broader gamification context in [Does anybody know what cheers are?](https://meta.discourse.org/t/-/402615/2?silent=true), including references to [What is a cheer?](https://meta.discourse.org/t/-/235686/1?silent=true), [What are Discourse cheers supposed to be?](https://meta.discourse.org/t/-/223867/1?silent=true), [What’s a cheer and how do you enable it?](https://meta.discourse.org/t/-/295988/1?silent=true), and [Discourse Gamification](https://meta.discourse.org/t/-/225916/1?silent=true).
- A mobile theming question turned into a mini reminder that **Horizon is intentionally “out-of-the-box”** and customization is best started from Foundation, in [How can I change the category background in the mobile version?](https://meta.discourse.org/t/-/402473/4?silent=true) (#mobile #horizon-theme). Background links: [Horizon theme announcement](https://meta.discourse.org/t/-/360486/1?silent=true) and related feedback in [Horizon theme bug: category heading container sticky…](https://meta.discourse.org/t/-/387267/13?silent=true).
- A site owner seeing errors in Google’s URL inspection was told it may simply be a **brand-new domain + empty sitemap/content** situation in [Error encountered while inspecting Live URL](https://meta.discourse.org/t/-/402595/2?silent=true) (#seo).
### #Site-Management
- A concise how-to explained how admins can **force a consistent sidebar category set for all users** (via clearing and re-applying `default navigation menu categories` _historically_) in [How to set the same sidebar categories for all the users](https://meta.discourse.org/t/-/402479/1?silent=true) (#sidebar), followed by nuance/questions about whether the “two-step + wait” is required in [the follow-up discussion](https://meta.discourse.org/t/-/402479/2?silent=true).
### #Self-hosting
- A migration restore failed with `You can only specify one non-default checksum at a time.` and the thread narrowed toward **Cloudflare R2 S3-compatibility** concerns and checksum handling, in [迁移Discourse恢复数据失败](https://meta.discourse.org/t/-/402623/1?silent=true). Suggestions included attempting checksum env-var overrides ([read more](https://meta.discourse.org/t/-/402623/7?silent=true)) and confirming the object store + environment details ([read more](https://meta.discourse.org/t/-/402623/4?silent=true)).
### #bug
- `@discourse/mcp` users reported that on **subfolder installs** (e.g. `/forum`) MCP calls drop the subpath and hit the wrong endpoints in [MCP bug when subfolder-install in](https://meta.discourse.org/t/-/402609/1?silent=true) (#mcp); a fix was linked shortly after in [the response](https://meta.discourse.org/t/-/402609/2?silent=true).
- A tricky composer/RTE edge case described **dragging an unselected image repeatedly re-uploading it** , with reproduction attempts focusing on Edge, click-vs-drag behavior, and “borderline but stable for certain assets” in [When dragging an unselected image in a rich text editor, it is uploaded repeatedly](https://meta.discourse.org/t/-/402566/1?silent=true) (#composer).
- A detailed iOS PWA report suggested the UI claims push is enabled even though the server never receives a subscription because the **service worker isn’t controlling the app yet** in [Push notification subscription in iOS PWA silently failing…](https://meta.discourse.org/t/-/402645/1?silent=true) (#push-notifications).
- A locale/SEO concern: an unexpected language code and `hreflang` compliance fix was proposed via PR in [Unerwarteter Sprachcode](https://meta.discourse.org/t/-/402544/5?silent=true) (#translation #content-localization).
- Structured data markup continues to be iterated: one admin reported Google Search Console issues resolved after upgrading, while another still sees problems, in [Missing field ‘text’ (in ‘mainEntity.suggestedAnswer’)](https://meta.discourse.org/t/-/399974/29?silent=true).
### #contribute:feature
- A feature discussion highlighted that **translated quotes can lose important context** (like the topic title), and that German translation behavior may warrant separate evaluation, in [Improving the information provided on translated quotes](https://meta.discourse.org/t/-/402420/3?silent=true) (#content-localization).
- A long-running request about **publishing automatically at a set time** resurfaced with pointers to scheduled-topic publication and admin automation capabilities in [Publishing a post automatically at a set time](https://meta.discourse.org/t/-/192093/6?silent=true), plus related links to [Scheduling topics for future publication](https://meta.discourse.org/t/-/60731/1?silent=true) and API-based approaches discussed in [the referenced thread](https://meta.discourse.org/t/-/267938/2?silent=true), and a nod to [Discourse Automation](https://meta.discourse.org/t/-/195773/1?silent=true).
### #development
- Theme developers discussed long-term maintenance expectations and the intended stability goals of Blocks, with guidance that forks are owned by the forker and the “skills” docs should be treated as the living reference in [Skills for authoring themes and blocks](https://meta.discourse.org/t/-/401629/10?silent=true) (#theme-guides #blocks #skills).
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @fzngagan posted a step-by-step admin recipe for standardizing sidebar categories for all users in [How to set the same sidebar categories for all the users](https://meta.discourse.org/t/-/402479/1?silent=true).
- @nat weighed in on quote translation behavior and noted German is disproportionately affected (prompting more targeted evaluation) in [Improving the information provided on translated quotes](https://meta.discourse.org/t/-/402420/3?silent=true).
- @chapoi was active across multiple support/bug threads: advising plugin reduction and safe-mode isolation in [Badges Error launching](https://meta.discourse.org/t/-/402594/20?silent=true), attempting reproduction and gathering browser details in the composer issue [When dragging an unselected image…](https://meta.discourse.org/t/-/402566/2?silent=true), and clarifying Horizon’s customization intent in [How can I change the category background in the mobile version?](https://meta.discourse.org/t/-/402473/4?silent=true).
- @manuel replied with practical guidance on forking themes, expectations for upstream updates, and how the Blocks API aims for resilience in [Skills for authoring themes and blocks](https://meta.discourse.org/t/-/401629/10?silent=true).
- @sam responded to the MCP subfolder-install breakage with a pointer to a fix PR in [MCP bug when subfolder-install in](https://meta.discourse.org/t/-/402609/2?silent=true).
- @HAWK reviewed an SEO/URL Inspection report and suggested the failure is likely due to “new domain + empty sitemap/public content” in [Error encountered while inspecting Live URL](https://meta.discourse.org/t/-/402595/2?silent=true).
- @supermathie jumped into the restore/migration failure to request environment/object-store specifics in [迁移Discourse恢复数据失败](https://meta.discourse.org/t/-/402623/4?silent=true).
- @gerhard suggested a potential workaround for Cloudflare R2 checksum incompatibility by setting AWS checksum environment variables, in [迁移Discourse恢复数据失败](https://meta.discourse.org/t/-/402623/7?silent=true).
_That’s a wrap: may your badges load, your service workers take control on the first try, and your cat images drag without triggering an accidental re-upload spree._
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [12 Maggio 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/826 "2026-05-12T13:01:24Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
**In the last 24 hours (2026-05-11 → 2026-05-12):**
- **New posts:** 72
- **New topics:** 18
**Top contributors (posts / likes received):**
| User | Posts | Likes |
| --- | --- | --- |
| @Falco | 3 | 17 |
| @Lilly | 11 | 15 |
| @Moin | 6 | 9 |
| @lindsey | 1 | 6 |
| @RGJ | 2 | 5 |
| @chapoi | 5 | 5 |
| @zogstrip | 3 | 5 |
| @awesomerobot | 2 | 3 |
| @sniper756 | 1 | 3 |
| @gassim | 4 | 2 |
> A lot of today’s momentum clustered around **#mobile UX** , **automation scheduling** , and a big step forward in **image optimization**.
* * *
## Interesting Topics
### #Announcements
- **Bulk tag actions got a cleanup:** @lindsey introduced **Better bulk tag management** with a unified “Manage Tags” modal, while @Lilly and @Moin raised follow-ups about bringing back tag UI affordances and improving how bulk tag edits appear in revision history ([read more](https://meta.discourse.org/t/-/402693/1?silent=true), related: [tag info button](https://meta.discourse.org/t/-/402436/1?silent=true), [prior feature request](https://meta.discourse.org/t/-/276709/1?silent=true)).
- **Chat notification quick replies are back (and better):** @Falco revived quick replies for Chat notifications and noted improved robustness, emoji-only replies becoming reactions, and support for chat threads ([read more](https://meta.discourse.org/t/-/245358/8?silent=true), related: [Chat threads](https://meta.discourse.org/t/-/270613/1?silent=true)).
- **Less “admin noise” for Upcoming Changes:** @Lilly shared a way to dismiss notifications tied to Upcoming Changes (and new features) within the ongoing rollout discussion ([read more](https://meta.discourse.org/t/-/392894/25?silent=true), related: [Introducing Upcoming Changes](https://meta.discourse.org/t/-/392894/1?silent=true)).
- **Clarifying “Everyone” on Admin UI upcoming changes:** In the Admin Reporting & Analysis thread, @martin explained that “Everyone” is a misleading label for admin-only surfaces (since only staff can access the admin UI anyway), and suggested future options like _Staff only_ / _No one_ to reduce confusion ([read more](https://meta.discourse.org/t/-/395768/27?silent=true)).
### #contribute:feature
- **Client-side image optimization gets a major upgrade:** @Falco announced new client-side optimizations, including **GIF → Animated WebP conversion** (roughly halving file sizes) and tying the rollout into the Upcoming Changes framework ([read more](https://meta.discourse.org/t/-/402705/1?silent=true), background: [client-side image optimization origins](https://meta.discourse.org/t/-/196998/1?silent=true), older discussions: [GIF conversion idea](https://meta.discourse.org/t/-/16739/1?silent=true), [WebP plugin idea](https://meta.discourse.org/t/-/36470/2?silent=true)).
- **Smoother self-hosted builds when downloads fail:** A feature request proposed making fragile build-time downloads (like fetching `acme.sh`) more resilient, including adding an override such as `DISCOURSE_ACME_DOWNLOAD_URL` ([read more](https://meta.discourse.org/t/-/402657/1?silent=true), related guidance: [acme.sh rebuild stuck thread](https://meta.discourse.org/t/-/387131/1?silent=true)).
- **Embedded views stats vs. “full app embed” reality check:** In the Tecnoblog embedding experience thread, @Thiago_Mobilon questioned whether embedded view tracking is undercounting after switching to full app embed—because traffic increased dramatically but “Embedded Views” did not ([read more](https://meta.discourse.org/t/-/400721/54?silent=true)).
### #bug
- **Klipy + limited infinite search results = error edge cases:** @RGJ reported that Klipy categories aren’t paginated but still wire up a `loadMore`, which breaks when `limit_infinite_search_results` is enabled (and also noted a backspace crash scenario) ([read more](https://meta.discourse.org/t/-/402679/1?silent=true)).
- **iOS PWA push subscriptions silently failing (service worker control):** @Falco asked whether adding `skipWaiting()` / `clients.claim()` to the main service worker would resolve the issue, and the reporter iterated on a PR to ensure immediate SW control for the PWA ([read more](https://meta.discourse.org/t/-/402645/3?silent=true)).
- **Admin API `/active.json` intermittently 500s (nil `main_user_record`):** A report highlighted failures in `/admin/users/list/active.json` pages due to `main_user_record[:silenced_till]` being nil, including a traced regression window and stack output ([read more](https://meta.discourse.org/t/-/402752/1?silent=true)).
- **“Jump to post” + edit reply + save ⇒ missing resource error:** A reproducible flow in the reply expansion UI can lead to “URL/resource not found” after saving an edit with no changes; @chapoi confirmed and shared console clues ([read more](https://meta.discourse.org/t/-/402747/1?silent=true)).
- **Why monthly timed automations don’t run (and why month length matters):** The automation scheduling debugging thread dug into why “monthly” recurrence behaves inconsistently; @Lilly traced the logic to recurring trigger code and suspected a mismatch between calendar day intent and BYDAY-based RRULE behavior ([read more](https://meta.discourse.org/t/-/402664/1?silent=true)).
### #ux
- **Mobile Edge “Permanent delete” dialog is too narrow:** A long-lived UI path wasn’t updated to the newer modal component; @chapoi confirmed, and @zogstrip linked a fix PR ([read more](https://meta.discourse.org/t/-/402663/1?silent=true)).
- **Automation list on mobile: “last run” column overlaps edit controls:** @Lilly reported the portrait viewport collision, and @awesomerobot pointed to an upcoming fix ([read more](https://meta.discourse.org/t/-/402695/1?silent=true)).
### #Support
- **Salesforce Experience Cloud embedding: iframe shows only login / limited mode:** A Business Trial user described an LWC-based embed setup (including [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) and trusted URLs) but still seeing only the login view rather than a full forum experience ([read more](https://meta.discourse.org/t/-/402712/1?silent=true)).
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @Falco shipped news and follow-ups across performance + platform edges: announcing **new client-side image optimizations** (including GIF→WebP) ([read more](https://meta.discourse.org/t/-/402705/1?silent=true)), restoring **Chat notification quick replies** with better handling + thread support ([read more](https://meta.discourse.org/t/-/245358/8?silent=true)), and pushing on an iOS PWA fix by suggesting service worker control changes ([read more](https://meta.discourse.org/t/-/402645/3?silent=true)).
- @lindsey introduced the consolidated **Manage Tags** modal for bulk actions and invited feedback on the workflow ([read more](https://meta.discourse.org/t/-/402693/1?silent=true)).
- @zogstrip confirmed and routed multiple fixes: a narrow mobile Edge “permanent delete” modal got a concrete fix path ([read more](https://meta.discourse.org/t/-/402663/4?silent=true)), a category/tag “no tag” switching bug received a PR-based resolution ([read more](https://meta.discourse.org/t/-/402545/4?silent=true)), and the monthly automation investigation got escalated for a deeper look ([read more](https://meta.discourse.org/t/-/402664/14?silent=true)).
- @chapoi did a lot of sharp-edge triage: confirming the outdated modal implementation behind the Edge report ([read more](https://meta.discourse.org/t/-/402663/2?silent=true)), confirming the “missing URL/resource” reproduction and sharing console hints ([read more](https://meta.discourse.org/t/-/402747/2?silent=true)), and pushing back on “reading time scripts” as unethical trust-level gaming ([read more](https://meta.discourse.org/t/-/402738/4?silent=true)). They also noted a merged fix for reaction-picker behavior on long press ([read more](https://meta.discourse.org/t/-/402269/3?silent=true)).
- @awesomerobot acknowledged two UX paper-cuts and linked fixes/next steps: the confusing “Permanent” filter wording in Upcoming Changes ([read more](https://meta.discourse.org/t/-/402433/2?silent=true)) and a fix for the automation mobile overlap issue ([read more](https://meta.discourse.org/t/-/402695/2?silent=true)).
- @supermathie supported a self-host migration recovery case by pointing to the official migration guide and requesting the relevant (redacted) ENV block for troubleshooting ([read more](https://meta.discourse.org/t/-/402623/9?silent=true), guide: [step-by-step migration](https://meta.discourse.org/t/-/382491/1?silent=true)).
- @martin clarified how **admin-only upcoming changes** behave despite “Everyone” being shown, and outlined why adding _Staff / No one_ options would reduce confusion ([read more](https://meta.discourse.org/t/-/395768/27?silent=true)).
- @sam checked in on an AI integration bug report regarding Gemini Pro “thinking budget” edge values (0 / -1), asking whether it’s still reproducible ([read more](https://meta.discourse.org/t/-/388485/5?silent=true)).
* * *
Yesterday, Meta managed to _shrink GIFs, untangle tags, and un-squish mobile modals_—may all your automations trigger on the exact calendar day you meant.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [13 Maggio 2026, 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/827 "2026-05-13T13:01:42Z")
# Today on [meta.discourse.org](http://meta.discourse.org)…
## Key Stats
- **New posts (last 24h): 68**
- **New topics (last 24h): 14**
**Top users (posts / likes in the last 24h)**
| User | Posts | Likes |
| --- | --- | --- |
| @Lilly | 4 | 20 |
| @markvanlan | 1 | 19 |
| @gilles | 6 | 4 |
| @merefield | 4 | 4 |
| @zogstrip | 3 | 4 |
| @Falco | 2 | 4 |
| @NateDhaliwal | 1 | 4 |
| @martin | 3 | 5 |
| @putty | 2 | 5 |
| @Shauny | 1 | 3 |
A big chunk of today’s momentum came from two major announcements: **nested replies** ([read more](https://meta.discourse.org/t/-/402812/1?silent=true)) and **clearer group semantics for “everyone”** ([read more](https://meta.discourse.org/t/-/402273/1?silent=true)).
**More threads with fresh activity (quick links)**
(Extra browsing fuel from across Meta—each link is a specific post.)
- DiscourseAI translation UI edge case: default LLM text not updating live ([read more](https://meta.discourse.org/t/-/402792/1?silent=true))
- Gemini “thinking budget” quirk discussion continued ([read more](https://meta.discourse.org/t/-/388485/6?silent=true))
- Boosts feedback kept rolling in ([read more](https://meta.discourse.org/t/-/399835/84?silent=true))
- Calendar/mobile work continued via a PR proposal ([read more](https://meta.discourse.org/t/-/372658/5?silent=true))
- Topic List Previews docs typo got corrected collaboratively ([read more](https://meta.discourse.org/t/-/209973/732?silent=true))
- Email subject line simplification feedback continued ([read more](https://meta.discourse.org/t/-/395927/9?silent=true))
- “Workflow” naming collision concern raised for core vs plugin ([read more](https://meta.discourse.org/t/-/402854/1?silent=true))
- Discourse Workflow plugin shipped compatibility updates ([read more](https://meta.discourse.org/t/-/347110/21?silent=true))
- Sidekiq 8 MiniScheduler integration PR got merged & released ([read more](https://meta.discourse.org/t/-/400645/3?silent=true))
- OpenID Connect group sync bug: backporting underway ([read more](https://meta.discourse.org/t/-/402416/9?silent=true))
- API failures around `silenced_till` + ESR timing discussion ([read more](https://meta.discourse.org/t/-/402752/3?silent=true))
- “Disable Markdown / default rich text” thread asked for a reliable repro in #Contribute > Bug ([read more](https://meta.discourse.org/t/-/370335/21?silent=true))
- Assign on mobile: modal search field blows up with JS error ([read more](https://meta.discourse.org/t/-/400986/12?silent=true))
- Data restore/migration troubleshooting continued (S3 uploads rake task) ([read more](https://meta.discourse.org/t/-/402623/10?silent=true))
* * *
## Interesting Topics
### #Announcements
- **Nested replies are here (early days, big potential):** @markvanlan introduced an officially-supported, fully **nested topic view** —including a single-thread view when deep-linking to a reply, plus new site settings and a roadmap to watch. [read more](https://meta.discourse.org/t/-/402812/1?silent=true)
- **Clearer permissions via new pseudogroups:** @martin announced “granular” pseudogroups—`anonymous` and `logged_in_users`—to replace confusing `@everyone` behavior in _group-list_ settings, while explicitly keeping category/tag permission semantics stable. [read more](https://meta.discourse.org/t/-/402273/1?silent=true)
- **Reporting UI clarity improvements shipped:** In the ongoing admin reporting thread, @martin noted a merged change that makes upcoming “reporting improvements” options more explicit (No one / Staff / Specific groups). [read more](https://meta.discourse.org/t/-/395768/28?silent=true)
### #General
- **Interest check: deeper gamification beyond trust levels:** A proposal to integrate a richer XP/streaks/economy-style gamification system with Discourse sparked discussion about where core ends and plugin ecosystems begin (#gamification). [read more](https://meta.discourse.org/t/-/402802/1?silent=true)
### #Self-hosting
- **Renaming categories (and slugs) without breaking links:** @bayardo.rivas asked what changes are “safe” in production; replies clarified how category IDs drive routing and how “wrong” slugs still redirect—plus practical examples and reassurance about renaming slugs. [read more](https://meta.discourse.org/t/-/402804/1?silent=true)
- **Redirecting users away from non-existent pages:** A self-hosting question on handling 404s quickly pointed to established approaches and highlighted using **#permalinks** for redirecting specific paths. [read more](https://meta.discourse.org/t/-/402807/1?silent=true)
- **Self-hosted DiscourseAI sentiment model fix:** A setup broke due to upstream model files returning 404; @Falco shared a workaround by pointing Docker at the correct branch until the model-side change lands. [read more](https://meta.discourse.org/t/-/334451/15?silent=true)
### #bug
- **Grid lightbox navigation order is wrong:** @Shauny reported grid-uploaded images advancing in an unexpected order (1,3,2,4), and @zogstrip confirmed it was debugged and fixed via a PR. (#lightbox) [read more](https://meta.discourse.org/t/-/402817/1?silent=true)
- **Chinese error: “cannot find requested URL/resource” fix in progress:** In a Chinese-language bug thread, @zogstrip reported reproducing the issue and working on a fix (linked PR) before landing the final solution. (#fixed) [read more](https://meta.discourse.org/t/-/402747/4?silent=true)
- **Upcoming Events: clicking a link opens a user card (maybe Safari PWA?):** @Ethsim2 traced the click path through FullCalendar’s `eventClick` and a popover menu, then suspected conditions like Safari PWA + network jitter after the issue stopped reproducing reliably. (#calendar-and-event #ux) [read more](https://meta.discourse.org/t/-/402845/1?silent=true)
- **Norwegian locale mismatch wastes translation credits:** A DiscourseAI locale detector labeling Norwegian as `no` while target locales use `nb_NO` caused “translations” that barely change content—prompt tweaks were suggested as a fast mitigation. (#ai) [read more](https://meta.discourse.org/t/-/402859/1?silent=true)
- **Assign/re-assign on mobile: can’t type in the user search field:** A long-running mobile/assign issue resurfaced with a concrete console trace; attempts to guard `targetElement` removed the exception but didn’t restore typing behavior. (#mobile #assign) [read more](https://meta.discourse.org/t/-/400986/12?silent=true)
### #Support
- **Hide user cards from anonymous users:** A straightforward configuration question got a quick pointer to the relevant setting to prevent anon visitors from seeing user cards. [read more](https://meta.discourse.org/t/-/402846/1?silent=true)
- **Translation translates only the topic title (not the post body):** A report showed the title translating while the post content did not; @nat identified a post-length limit and adjusted/bumped so the content translated properly afterwards. [read more](https://meta.discourse.org/t/-/402858/1?silent=true)
* * *
## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group
- @markvanlan unveiled Discourse’s new **nested replies** experience, including enablement settings and early roadmap notes in [Introducing nested replies](https://meta.discourse.org/t/-/402812/1?silent=true).
- @martin clarified the long-standing `@everyone` ambiguity by announcing new `anonymous` + `logged_in_users` pseudogroups in [Granular group-based permissions for anonymous and logged in users](https://meta.discourse.org/t/-/402273/1?silent=true), and followed up to confirm category/tag permissions won’t unexpectedly become login-gated ([read more](https://meta.discourse.org/t/-/402273/4?silent=true)). He also shipped UI clarity improvements for reporting options in [Admin Reporting & Analysis: Incremental Changes](https://meta.discourse.org/t/-/395768/28?silent=true).
- @zogstrip acknowledged and fixed the lightbox ordering bug reported in [Grid Lightbox images show in wrong order](https://meta.discourse.org/t/-/402817/3?silent=true), continued progress on the Chinese-language error thread in [出错了：找不到请求的 url 或资源](https://meta.discourse.org/t/-/402747/4?silent=true), and helped diagnose an API issue by pointing to a prior fix/commit in [API calls fail due issue with main\_user\_record silenced\_till](https://meta.discourse.org/t/-/402752/3?silent=true).
- @Falco unblocked self-hosted sentiment analysis by providing a working model reference/branch in [Self-Hosting Sentiment and Emotion for DiscourseAI](https://meta.discourse.org/t/-/334451/15?silent=true), and advised on cross-site iframe/Salesforce embedding approaches (domain alignment vs `same_site_cookies`) in [Is it possible to embed Discourse into a Salesforce Community…?](https://meta.discourse.org/t/-/402712/4?silent=true).
- @nat jumped into translation issues twice: first by noting and effectively resolving a “title translates but post doesn’t” case in [Translation does not translate topic but title is translated](https://meta.discourse.org/t/-/402858/2?silent=true), and then by suggesting prompt-level mitigations for Norwegian locale normalization in [Norwegian is identified as `no` by locale detector agent…](https://meta.discourse.org/t/-/402859/2?silent=true).
- @chapoi provided the relevant admin setting to disable user cards for anonymous visitors in [Anonyme carte utilisateur](https://meta.discourse.org/t/-/402846/2?silent=true).
- @david confirmed a Dev PR was “Merged and released” in [PR: Fix MiniScheduler::Web integration with Sidekiq 8](https://meta.discourse.org/t/-/400645/3?silent=true).
- @pmusaraj shared that backporting is underway for an SSO/OpenID group sync issue in [OpenID Connect group can kick users out of all unsynced groups](https://meta.discourse.org/t/-/402416/9?silent=true).
* * *
Yesterday’s vibe in one line: may your replies be neatly _nested_, your permissions _less mysterious_, and your lightbox arrows finally go **1-2-3-4**.
[Pagina precedente](https://meta.discourse.org/t/daily-summary-1pm-utc/291852.md?page=29)
[Pagina seguente](https://meta.discourse.org/t/daily-summary-1pm-utc/291852.md?page=31)