# Daily Summary (9pm UTC) **URL:** https://meta.discourse.org/t/daily-summary-9pm-utc/291850 **Category:** Forum summaries **Created:** [January 16, 2024, 9:56pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850 "2024-01-16T21:56:19Z") **Posts on this page:** 20 **Page:** 29
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [March 29, 2026, 9:02pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/818 "2026-03-29T21:02:36Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 48** (spread across threads like [Plugin Cleaner](https://meta.discourse.org/t/-/399505/1?silent=true), [AI translation & PMs](https://meta.discourse.org/t/-/399524/1?silent=true), and [releases.discourse.org feedback](https://meta.discourse.org/t/-/399414/10?silent=true)) - **New topics (last 24h): 7** (including [Plugin Cleaner](https://meta.discourse.org/t/-/399505/1?silent=true), [AI not translating PMs](https://meta.discourse.org/t/-/399524/1?silent=true), and [root-level links](https://meta.discourse.org/t/-/399520/1?silent=true)) **Top users by recent activity (posts / likes)** - @merefield — **1 post / 7 likes** on plugin safety concerns in [Plugin Cleaner](https://meta.discourse.org/t/-/399505/2?silent=true) - @Lilly — **4 posts / 5 likes** helping with theming questions in [Theme customize - sidebar content](https://meta.discourse.org/t/-/399504/3?silent=true) - @pfaffman — **3 posts / 5 likes** weighing risks in [Plugin Cleaner](https://meta.discourse.org/t/-/399505/3?silent=true) and debugging hosting issues in [CORS error after upgrade](https://meta.discourse.org/t/-/399466/4?silent=true) - @ferdnyc — **2 posts / 5 likes** doing accessibility contrast analysis in [releases.discourse.org feedback](https://meta.discourse.org/t/-/399414/10?silent=true) - @Falco — **1 post / 3 likes** proposing a settings improvement in [AI translation & PMs](https://meta.discourse.org/t/-/399524/4?silent=true) - @stephtara — **1 post / 3 likes** reporting readability issues in the [Meta Branded redesign](https://meta.discourse.org/t/-/397246/47?silent=true) - @elmuerte — **1 post / 2 likes** noting foreign-key edge cases in [Plugin Cleaner](https://meta.discourse.org/t/-/399505/4?silent=true) - @bartv — **1 post / 2 likes** flagging broken links in [OpenClaw integration](https://meta.discourse.org/t/-/397239/9?silent=true) - @supermathie — **1 post / 2 likes** suggesting an error-message improvement in [MCP/about.json](https://meta.discourse.org/t/-/398792/4?silent=true) - @Moin — **1 post / 2 likes** clarifying translation scope in [AI translation & PMs](https://meta.discourse.org/t/-/399524/2?silent=true) * * * ## Interesting Topics ### #customization:plugin - @canbekcan introduced **Discourse Plugin Cleaner** , a tool to audit/remove orphaned plugin residue; @merefield raised concerns about safely detecting plugin-owned tables and avoiding accidental deletion of core custom fields, with follow-up caution from @pfaffman about the non-zero chance of breaking a database state ([read more](https://meta.discourse.org/t/-/399505/1?silent=true)). Related install guide: [How to install plugins](https://meta.discourse.org/t/-/19157/1?silent=true) - **Discourse Daily Challenges** shipped v1.4.0 with “ChallengeBot” for DM confirmations, reminders, and mention-driven stats; follow-up questions explored whether mentions can respond in-topic vs DM-only ([read more](https://meta.discourse.org/t/-/398980/39?silent=true)) - The **Landing Pages** plugin surfaced an admin warning (`discourse.resolver-resolutions`) indicating it “contains code which needs updating”, suggesting maintainers may need to bump compatibility for recent core changes ([read more](https://meta.discourse.org/t/-/180967/157?silent=true)) ### #contribute:feature (#ai #content-localization) - A configuration gotcha: **AI translation is not translating 1:1 PMs** (even when the UI implies translation progress is complete). @Moin clarified current behavior and @Falco floated changing the boolean setting into a more explicit _targets_ menu (public topics vs all topics vs group PMs vs all PMs) ([read more](https://meta.discourse.org/t/-/399524/1?silent=true)) ### #Support - A “how do I build this sidebar?” theming question turned into a quick identification: the screenshot matches the **Discourse Doc Categories** experience, pointing admins toward the plugin rather than custom CSS/theme work ([read more](https://meta.discourse.org/t/-/399504/1?silent=true)). Reference: [Discourse Doc Categories](https://meta.discourse.org/t/-/322376/1?silent=true) - @paco dug into how **root-level routes** like `/faq`, `/privacy`, and `/about` behave (including when `must-be-logged-in` is enabled), and whether admins can create similar first-class paths; one suggestion was to publish additional static pages via a topic-to-page workflow ([read more](https://meta.discourse.org/t/-/399520/1?silent=true)). Reference: [Page Publishing](https://meta.discourse.org/t/-/151971/1?silent=true) - A possible regression/expectation mismatch: **`use_name_for_username_suggestions` appears to have no effect on the regular signup form** (even if it may apply to SSO/OAuth flows). Others confirmed the behavior, and the thread connects back to earlier username-suggestion discussions ([read more](https://meta.discourse.org/t/-/399499/1?silent=true)). Related: [Customize registration form / hide or normalize username field](https://meta.discourse.org/t/-/399497/7?silent=true), [Offering blank username suggestions](https://meta.discourse.org/t/-/391542/1?silent=true), and [“use email for username and name suggestions”](https://meta.discourse.org/t/-/318791/1?silent=true) - After updating to a recent build, @RBoy saw **Google Search Console “acceptedAnswer” warnings** appear on an older FAQ-like page, and asked what changed to trigger it now; the report references prior guidance that unsolved topics set `answerCount` to 0 ([read more](https://meta.discourse.org/t/-/399525/1?silent=true)). Background: [acceptedAnswer / suggestedAnswer discussion](https://meta.discourse.org/t/-/111809/3?silent=true) - In the #mcp-tagged MCP/API thread, a **granular-access API user couldn’t read `about.json`** , yielding an “invalid username/key” error; @supermathie questioned whether the error text is misleading and worth improving ([read more](https://meta.discourse.org/t/-/398792/4?silent=true)) - A long-running “print/export” need resurfaced: exporting **a single post** (e.g., wiki meeting notes) as PDF for sharing into other tools; the discussion points back toward a theme-component approach as a practical solution ([read more](https://meta.discourse.org/t/-/258689/12?silent=true)) - A UX/CSS papercut: **tiny category images** were fixed with custom CSS, but @CharlesGWaldman argued the underlying change (an `aspect-image` behavior shift) caused unnecessary breakage and should be reconsidered upstream ([read more](https://meta.discourse.org/t/-/380837/6?silent=true)) ### #Self-hosting (#cdn #backups) - Multiple admins reported **plugins breaking due to CORS errors after a recent upgrade** , especially when using BunnyCDN; one workaround attempt involved tweaking Bunny’s CORS handling for JS assets, but the “why did this start now?” question remains front-and-center ([read more](https://meta.discourse.org/t/-/399466/4?silent=true)). Related: [Code highlighting failed because bunny.net CDN](https://meta.discourse.org/t/-/296333/1?silent=true) - A governance/security question: **can Discourse admins be restricted from backups/exports via the UI?** Replies emphasized the “admins have absolute control” model, while noting env-defined settings may override/hide UI toggles and pointing to standard automated backup guidance ([read more](https://meta.discourse.org/t/-/399510/1?silent=true)). Reference: [Configure automatic backups for Discourse](https://meta.discourse.org/t/-/14855/1?silent=true) ### #General - The new releases site got a detailed **accessibility/contrast review** , with @ferdnyc measuring WCAG contrast ratios and listing several failing combinations (e.g., white text over `--color-feature`), calling for urgent fixes and a broader accessibility audit ([read more](https://meta.discourse.org/t/-/399414/10?silent=true)) ### #Site feedback - In the **Meta Branded redesign** feedback thread, @stephtara reported that linked text on the dark theme is “just below readable,” comparing against other themes (Fondation/Horizon) that remain legible ([read more](https://meta.discourse.org/t/-/397246/47?silent=true)) ### #bug - A recurring restriction prompted a workaround: **unable to download `.js` attachments** (for legitimate non-browser uses). One admin reported success by moving uploads to S3-compatible storage and enabling CDN URLs to bypass the short-url controller path ([read more](https://meta.discourse.org/t/-/180671/13?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco engaged in the #ai #content-localization discussion about PM translation limits, proposing a clearer setting model (switching from a boolean to an option menu to explicitly include/exclude group PMs and 1:1 PMs) in [AI is not translating PMs](https://meta.discourse.org/t/-/399524/4?silent=true). - @supermathie reviewed an MCP-related API failure mode and suggested improving potentially misleading authentication/scoping errors in [API user with granular access cannot read about.json](https://meta.discourse.org/t/-/398792/4?silent=true). - @sam jumped into a broken-link report with “Yikes, will have a look,” cc’ing the relevant maintainer in [OpenClaw plugin for Discourse integration](https://meta.discourse.org/t/-/397239/11?silent=true). * * * Yesterday’s vibe: half the community was sweeping up plugin leftovers while the other half debated whether your PMs deserve to be multilingual too. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [March 30, 2026, 9:02pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/819 "2026-03-30T21:02:28Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 109 - **New topics (last 24h):** 14 - **Top users (posts / likes):** * * * ## Interesting Topics ### #contribute:site-feedback - @Moin shared a hilarious-but-painful list of **AI tag translation misses** (e.g. _#tablet → “pill”_) and flagged a serious problem: different tags collapsing into the same translation, breaking discovery in localized UIs ([read more](https://meta.discourse.org/t/-/399570/1?silent=true)). The follow-up explored improving prompts and grounding translations via context and existing localization decisions ([read more](https://meta.discourse.org/t/-/399570/9?silent=true)), alongside the wider rollout note that **translated tags are now live** ([read more](https://meta.discourse.org/t/-/383057/3?silent=true)) and the broader localization feature set ([read more](https://meta.discourse.org/t/-/370000/1?silent=true)). - The **Meta branded redesign theme refresh** continued: @manuel acknowledged color/usability concerns and pointed to a cleaner path forward now that themes can constrain available color schemes ([read more](https://meta.discourse.org/t/-/397246/48?silent=true)). A side-thread ended up being a great reminder that “theme weirdness” can come from _outside_ Discourse—one report was traced to an unrelated browser theme leaking CSS into Meta ([read more](https://meta.discourse.org/t/-/397246/53?silent=true)). ### #contribute:feature - In #ai #content-localization, troubleshooting why **AI translation isn’t translating PMs** turned into a preview of upcoming controls—shifting from “public-only backfill” toward explicit toggles like _Translate PMs_ plus “translate these categories” targeting ([read more](https://meta.discourse.org/t/-/399524/5?silent=true)). The related feature request for category-scoped translation was referenced as “coming soon” ([read more](https://meta.discourse.org/t/-/392993/1?silent=true)). - A localization workflow gap was spotted: when a category name changes (e.g. “Installation” → “Self-hosting”), the **translated category name may not update automatically** , leaving localized UIs stale ([read more](https://meta.discourse.org/t/-/399585/1?silent=true)). This tied neatly into the active push to make #dynaloc behave more predictably across the product ([read more](https://meta.discourse.org/t/-/399570/1?silent=true)). - Another #dynaloc request: when the **translated “About this category” topic** gets updated, the **category banner description** in that language may still show deprecated text—suggesting the banner’s source field isn’t being refreshed on translation updates ([read more](https://meta.discourse.org/t/-/399587/1?silent=true)). - The #tag-icons ecosystem hit a localization snag: **tag icons don’t reliably work with translated tag slugs** , so the icon meaning can vanish just when localized tags are most needed (notably for #ai clarity) ([read more](https://meta.discourse.org/t/-/399594/1?silent=true)). This complements broader “translated tag behavior” questions and bug reports ([read more](https://meta.discourse.org/t/-/399591/1?silent=true)). ### #bug - A settings expectation mismatch got clarified (and reclassified): **“Use name for username suggestions”** doesn’t affect the _local signup form_—it only applies to SSO/OAuth flows—so the setting text was updated to reduce confusion ([read more](https://meta.discourse.org/t/-/399499/4?silent=true)). The discussion also spun off into “should local signup be able to prioritize name→username?” ([read more](https://meta.discourse.org/t/-/399499/6?silent=true)) and echoed related “hide/normalize username field” constraints on hosted plans ([read more](https://meta.discourse.org/t/-/399497/10?silent=true)). - Google Search Console reports surfaced a structured data issue: **`acceptedAnswer` errors** appear to be linked to recent work that inadvertently exposed a bug; a fix is already queued ([read more](https://meta.discourse.org/t/-/399525/2?silent=true)). - Translated tag UX got thorny fast: when localized autocomplete suggests translated tags, inserting them can result in **non-linking hashtags and missing tags** , making it unclear what “translated tags” are supposed to do in composer/search/tagging flows ([read more](https://meta.discourse.org/t/-/399591/1?silent=true)). This overlaps with earlier reports of localized autocomplete behaving inconsistently depending on context (topic list vs composer vs hashtag autocomplete) ([read more](https://meta.discourse.org/t/-/374737/7?silent=true)). - A puzzling image zoom issue (“ **Image could not be loaded** ” only when clicking directly, but not when navigating via arrows) looked account/session-specific—incognito worked—so troubleshooting focused on [safe mode](https://meta.discourse.org/t/53504?silent=true), cache, and “try an alt account” isolation ([read more](https://meta.discourse.org/t/-/399548/1?silent=true)). ### #self-hosting - A bootstrap failure during `db:migrate` ( **`relation "ai_agent_mcp_servers" does not exist`** ) turned out to be an edge case caused by a **migration ID collision** —notably linked to AI-assisted migration generation producing date-stamped collisions across repos ([read more](https://meta.discourse.org/t/-/399572/5?silent=true)). The resolution included guidance to avoid “suspiciously round” timestamps and a concrete workaround using a new migration version ([read more](https://meta.discourse.org/t/-/399572/7?silent=true)). - A self-hosting upgrade procedure check-in covered “rebuild vs rebuild-in-place” and how to think about **release vs latest vs ESR** choices—especially the practical reminder that _downgrades aren’t supported_ ([read more](https://meta.discourse.org/t/-/399550/4?silent=true)). The recommended background reading was the release channel explainer ([read more](https://meta.discourse.org/t/-/264400/1?silent=true)) plus how to configure tracking branches ([read more](https://meta.discourse.org/t/-/17014/1?silent=true)). - A post-upgrade “all plugins broken” incident was traced to **CORS + `script type="module"` requirements** in the newer plugin system; once CDN headers were corrected, everything returned to normal ([read more](https://meta.discourse.org/t/-/399466/6?silent=true)). ### #Dev - Rails ecosystem maintenance: a PR adding **Sidekiq 8 support to `mini_scheduler`** was merged and released quickly, unblocking dependency upgrades for downstream apps ([read more](https://meta.discourse.org/t/-/399560/2?silent=true)). ### #ux - A Horizon theme UX issue— **category creation floating box blocking lower settings** —was acknowledged with a forthcoming fix (and a linked core change) ([read more](https://meta.discourse.org/t/-/399481/4?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@nat** dug into localization quality issues around AI-driven tag translations and next steps for improving prompts/context ([read more](https://meta.discourse.org/t/-/399570/3?silent=true)), proposed predictable ways to inject more context into translation calls ([read more](https://meta.discourse.org/t/-/399570/5?silent=true)), and outlined upcoming configuration improvements for category-scoped translation controls while troubleshooting PM translation behavior ([read more](https://meta.discourse.org/t/-/399524/5?silent=true)). @nat also posted the progress update that **translated tags are now available** ([read more](https://meta.discourse.org/t/-/383057/3?silent=true)). - **@Falco** proposed a “give the agent tools to fetch context” approach to improve tag/category translations ([read more](https://meta.discourse.org/t/-/399570/4?silent=true)), endorsed combining multiple grounding strategies ([read more](https://meta.discourse.org/t/-/399570/7?silent=true)), and expanded on why using existing translations and limited code search can materially improve outcomes for enumerable strings ([read more](https://meta.discourse.org/t/-/399570/9?silent=true))—while still arguing against disabling machine translation for key areas on Meta ([read more](https://meta.discourse.org/t/-/399570/11?silent=true)). - **@david** helped debug a self-hosting bootstrap failure by checking migration ordering and asking for evidence the table-creating migration ran ([read more](https://meta.discourse.org/t/-/399572/4?silent=true)), then identified the underlying AI-related migration collision dynamic and asked how to ensure real timestamps going forward ([read more](https://meta.discourse.org/t/-/399572/6?silent=true)). @david also clarified why plugin CORS issues appeared “suddenly” due to the gradual move to `type="module"` ([read more](https://meta.discourse.org/t/-/399466/6?silent=true)), confirmed successful resolution of tag/branch deployment confusion in the older-versions deployment thread ([read more](https://meta.discourse.org/t/-/399409/25?silent=true)), and merged/released Sidekiq 8 support in `mini_scheduler` ([read more](https://meta.discourse.org/t/-/399560/2?silent=true)). - **@zogstrip** connected an ecosystem bug (404s on `/llms.txt`-style root routes) to an in-flight core fix ([read more](https://meta.discourse.org/t/-/397239/16?silent=true)), clarified the constraints behind the “use name for username suggestions” setting and updated its description to match actual behavior ([read more](https://meta.discourse.org/t/-/399499/4?silent=true)), shipped a fix for the “can’t unfollow banned users” edge case via the official follow plugin ([read more](https://meta.discourse.org/t/-/304256/3?silent=true)), flagged intended vs actual behavior in recurring event attendance semantics and linked a fix for attendee management permissions ([read more](https://meta.discourse.org/t/-/335780/13?silent=true)), and confirmed a fix path for Google Search Console’s `acceptedAnswer` errors ([read more](https://meta.discourse.org/t/-/399525/2?silent=true)). - **@sam** confirmed a missing Ember route causing root-level links to misbehave in-app (similar to safe-mode quirks) and suggested tracking it properly ([read more](https://meta.discourse.org/t/-/397239/13?silent=true)), then reinforced why fixing `/llms.txt` routing matters as it becomes more widely linked ([read more](https://meta.discourse.org/t/-/397239/15?silent=true)). - **@manuel** continued iterating on Meta’s redesign theme, acknowledging color issues and describing how a new theme modifier removes the need for a hard-coded color-scheme hack ([read more](https://meta.discourse.org/t/-/397246/48?silent=true)), and followed up on a suspected link highlighting bug by requesting inspection details (ultimately traced to external CSS) ([read more](https://meta.discourse.org/t/-/397246/52?silent=true)). - **@martin** pointed to a prior removal/cleanup relevant to FAQ & Guidelines link behavior ([read more](https://meta.discourse.org/t/-/397938/15?silent=true)) and provided guidance on enabling “solved-style support category creation” via category settings, noting future UX improvements are planned ([read more](https://meta.discourse.org/t/-/398338/13?silent=true)). - **@schleifer** clarified that a reported Discourse CDN domain with an invalid SSL cert had been retired years ago, and directed the reporter toward support escalation if a hosted site was still referencing it ([read more](https://meta.discourse.org/t/-/399543/3?silent=true)). - **@awesomerobot** acknowledged a Horizon theme layout blocker during category creation and linked an upcoming fix via core changes ([read more](https://meta.discourse.org/t/-/399481/4?silent=true)). - **@HAWK** moved a confusing signup behavior report into #bug and documented reproduction details on [try.discourse.org](http://try.discourse.org) ([read more](https://meta.discourse.org/t/-/399499/3?silent=true)), clarified hosted-plan limitations around CSS-based registration form customization ([read more](https://meta.discourse.org/t/-/399497/8?silent=true)), and pointed to known behavior where scheduled-post publishing doesn’t trigger mention notifications as expected ([read more](https://meta.discourse.org/t/-/399539/3?silent=true)). * * * If today taught us anything, it’s this: may your migration IDs be unique, your CORS headers correct, and your German #tablet never again translate into medication. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [March 31, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/820 "2026-03-31T21:01:44Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **Window covered:** 2026-03-30 → 2026-03-31 (last 24 hours) - **New posts:** **84** - **New topics:** **11** - **Posts from the [@team](https://meta.discourse.org/groups/team?silent=true) group (top posters):** **19** (from @david, @Falco, @nat, @awesomerobot, @Danielle, @renato, @sam, @j.jaffeux — see participation highlights below) **Top users (posts / likes received in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @david | 7 | 9 | | @Moin | 6 | 3 | | @RGJ | 3 | 5 | | @Falco | 3 | 4 | | @NateDhaliwal | 3 | 3 | | @merefield | 2 | 5 | | @denvergeeks | 2 | 4 | | @nat | 2 | 4 | | @awesomerobot | 2 | 3 | | @Ed_S | 1 | 3 | * * * ## Interesting Topics ### #Announcements - **Discourse 2026.3 shipped:** @david posted the **March 2026 monthly release** announcement with links to the full changelog and patch releases, and @Ed_S confirmed smooth upgrades and RSS/email visibility on their side — [read more](https://meta.discourse.org/t/-/399630/1?silent=true). - **Calendar subscription sync expectations:** folks using subscription URLs noticed edits/deletions don’t appear instantly; @Falco clarified Google Calendar typically refreshes _about twice per day_, so changes can take hours — [read more](https://meta.discourse.org/t/-/398902/12?silent=true). ### #Dev - **Theme/plugin template deprecations sparked strong feelings:** the ongoing move away from `.hbs` prompted pushback, while others pointed to auto-conversion tooling and past deprecation runways — [read more](https://meta.discourse.org/t/-/398896/8?silent=true). (Related: the “auto-update to .gjs” guide was referenced as a path forward — [read more](https://meta.discourse.org/t/-/368051/1?silent=true), plus earlier compatibility discussions like the FA6 upgrade thread — [read more](https://meta.discourse.org/t/-/325349/43?silent=true).) - **`.js.es6` filename deprecation (again):** discussion reiterated that most cases are simply renaming files to `.js`, and @awesomerobot offered to help update open-source plugins via PRs — [read more](https://meta.discourse.org/t/-/398894/5?silent=true). - **API regression report:** a script using the REST API began returning **400** errors with the `all-users` scope, breaking previously-working automation (user creation + liking) — [read more](https://meta.discourse.org/t/-/399597/1?silent=true). ### #contribute:feature - **Review Queue UX: “helpful flags” should be clickable:** admins spotted that “helpful flags” lacked a link/filter path; @awesomerobot opened and merged a fix so it’ll land in upcoming updates — [read more](https://meta.discourse.org/t/-/341613/8?silent=true). (The same report was also raised in #ux form — [read more](https://meta.discourse.org/t/-/399600/1?silent=true).) - **Limit AI translation to specific categories:** @nat linked a PR implementing category targeting for translations, aiming to reduce “translate everything” blast radius — [read more](https://meta.discourse.org/t/-/392993/5?silent=true). (This ties into broader localization workflows and documentation — [read more](https://meta.discourse.org/t/-/370969/1?silent=true).) - **Email-in for automatic groups:** a request argued that blocking incoming email for _automatic_ groups is confusing (UI hides the setting), forcing awkward “shadow group” workarounds — [read more](https://meta.discourse.org/t/-/399611/1?silent=true). (Prior art includes staff-group email-in expectations — [read more](https://meta.discourse.org/t/-/62724/1?silent=true) and a Rails-console workaround thread — [read more](https://meta.discourse.org/t/-/212147/3?silent=true).) ### #Community\_Building - **Real-world multilingual community operations:** a private community considering Spanish/French/Portuguese support asked for rollout strategies and realistic expectations about machine translation quality — [read more](https://meta.discourse.org/t/-/399606/1?silent=true). (Team examples pointed to live multilingual usage, including a French chat discussion — [read more](https://meta.discourse.org/t/-/399495/1?silent=true) and a Chinese-language topic example — [read more](https://meta.discourse.org/t/-/391136/1?silent=true).) ### #Support - **“Ongoing translation” experience (original + translated side-by-side):** a detailed request described an AU-scale multilingual need (Anglophone/Francophone/Lusophone/Arabic) and asked for automatic dual-display and paragraph-level translation; @Falco noted native content localization covers most needs, but _chat translation_ isn’t there yet — [read more](https://meta.discourse.org/t/-/399610/2?silent=true). - **Chinese-language “Oops” after switching to ESR:** a self-host rebuilt started throwing generic errors after setting `version: esr`; @david identified this as a **downgrade** scenario (unsupported) where the DB schema no longer matches older code, requiring backup restore or returning to `latest` — [read more](https://meta.discourse.org/t/-/399614/9?silent=true). (Related upgrade/process discussions continue elsewhere — [read more](https://meta.discourse.org/t/-/399550/8?silent=true).) ### #bug - **Chat plugin build failure with rollup:** a report about `_assert is not a function` remained unresolved; @david asked whether any local patching/customization might explain why it’s not widely reproduced — [read more](https://meta.discourse.org/t/-/399321/5?silent=true). - **Topic Voting plugin: missing vote tallies + broken voting after upgrades:** a site on `2026.4.0-latest` reported vote history disappearing and users struggling to vote; logs mention tag param deprecations and multiple bundled plugins (Reactions, User Notes, Calendar, Solved) were suspected — [read more](https://meta.discourse.org/t/-/399649/1?silent=true). (Troubleshooting also referenced a “everything broke” pattern like CORS issues affecting all plugins — [read more](https://meta.discourse.org/t/-/399466/1?silent=true), and Meta’s own voting UI changes were noticed — [read more](https://meta.discourse.org/t/-/308402/42?silent=true).) ### #ux - **Translated categories vs translated tags behave differently:** @Moin noticed category names switch to the interface language immediately, but tag translation seems tied to a separate toggle (topic/post translation), creating inconsistent mental models — [read more](https://meta.discourse.org/t/-/399596/1?silent=true). ### #events - **Events revamp: clearer “Webinars” vs “Office Hours”:** @Danielle outlined a new structure for announcements, replays, and where to find everything in the #events category going forward — [read more](https://meta.discourse.org/t/-/399640/1?silent=true). (A related events thread also had quick fixes to confusing displayed times — [read more](https://meta.discourse.org/t/-/398295/6?silent=true).) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@david** shipped the **2026.3 release announcement** and linked patch trains — [read more](https://meta.discourse.org/t/-/399630/1?silent=true); helped debug a **chat build/compiler error** by probing for local customization — [read more](https://meta.discourse.org/t/-/399321/5?silent=true); and resolved a self-host “Oops” incident by explaining why **downgrading to ESR is unsupported** due to schema drift — [read more](https://meta.discourse.org/t/-/399614/9?silent=true). - **@Falco** set expectations on **calendar subscription refresh cadence** (Google Calendar updates ~2x/day) — [read more](https://meta.discourse.org/t/-/398902/12?silent=true); shared real-world multilingual implementations while discussing how to run a **multilingual community** — [read more](https://meta.discourse.org/t/-/399606/4?silent=true); and clarified that **content localization covers most translation needs** except chat (for now) — [read more](https://meta.discourse.org/t/-/399610/2?silent=true). - **@nat** connected multiple translation-related threads to the same implementation work, posting a PR for **category-scoped translations** — [read more](https://meta.discourse.org/t/-/392993/5?silent=true) and explaining how translation settings will **migrate** for PM/public content behavior — [read more](https://meta.discourse.org/t/-/399524/8?silent=true). - **@awesomerobot** unblocked a Review Queue UX gap by opening (and merging) a PR to make “helpful flags” link properly to the “Flagged by” filter — [read more](https://meta.discourse.org/t/-/341613/8?silent=true); and offered hands-on help updating plugins impacted by **deprecations** (especially extension renames) — [read more](https://meta.discourse.org/t/-/398894/5?silent=true). - **@Danielle** clarified how Discourse will organize **Events, webinars, office hours, and replays** — [read more](https://meta.discourse.org/t/-/399640/1?silent=true); and quickly fixed a confusing **event time display** after it was reported — [read more](https://meta.discourse.org/t/-/398295/6?silent=true). - **@renato** noted a recent editor change: the rich editor now consistently serializes closed `[details]` blocks regardless of current open/closed state, and asked for further reports if issues persist — [read more](https://meta.discourse.org/t/-/377645/23?silent=true). - **@sam** weighed in on an AI/migration workflow issue, suggesting that a lint-like guardrail might prevent recurring migration filename/id mistakes — [read more](https://meta.discourse.org/t/-/399572/8?silent=true). - **@j.jaffeux** revisited a recurring-events edge case (“going” attendance not resetting), pointing out limitations stemming from not having per-date event entries — [read more](https://meta.discourse.org/t/-/335780/14?silent=true). * * * _Yesterday’s vibe check:_ Meta managed to ship a fresh release, chase down translation ambitions across continents, and still find time to remind everyone that **downgrades bite** —a pretty classic day in Discourse-land.\* ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 1, 2026, 9:02pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/821 "2026-04-01T21:02:31Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **In the last 24 hours:** **118 new posts** across **12 new topics** (plus plenty of ongoing threads getting fresh replies, fixes, and follow-ups). **Top contributors (posts / likes received in the last 24h):** | User | Posts | Likes | Seen in | | --- | --- | --- | --- | | @Lilly | 9 | 21 | Reported a mobile viewport regression in [Some Meta topic pages borked on mobile viewport](https://meta.discourse.org/t/-/399691/1?silent=true) and followed up across several support threads ([read more](https://meta.discourse.org/t/-/399678/4?silent=true)) | | @Falco | 8 | 19 | Shipped a major embedding upgrade in [Embed Discourse as a full comment system on your site](https://meta.discourse.org/t/-/399743/1?silent=true) | | @Moin | 15 | 17 | Helped debug reactions + archived topics in [Only posts with no likes or reactions can be “liked” in an archived topic](https://meta.discourse.org/t/-/399681/2?silent=true) and provided bookmark organization workarounds ([read more](https://meta.discourse.org/t/-/19591/14?silent=true)) | | @sam | 3 | 16 | Announced MCP connectivity for AI agents in [Bring your own MCP!](https://meta.discourse.org/t/-/399668/1?silent=true) | | @nat | 2 | 12 | Published the multilingual retrospective in [Building for Every Language](https://meta.discourse.org/t/-/399661/1?silent=true) | | @RGJ | 1 | 10 | Released an April 1st-ready theme component in [Full Screen Cover Image](https://meta.discourse.org/t/-/399690/1?silent=true) | | @WorldIsMine | 3 | 7 | Shared “live-in-production” prank outcomes in [Full Screen Cover Image](https://meta.discourse.org/t/-/399690/3?silent=true) | | @davidb | 1 | 7 | Found the likely root cause and initiated a revert for the mobile breakage ([read more](https://meta.discourse.org/t/-/399691/5?silent=true)) | | @zogstrip | 6 | 6 | Pushed fixes for archived reactions logic in [Only posts with no likes or reactions can be “liked” in an archived topic](https://meta.discourse.org/t/-/399681/5?silent=true) | | @ToddZ | 5 | 6 | Improved discoverability and docs hygiene around gardening/index maintenance ([read more](https://meta.discourse.org/t/-/397606/64?silent=true)) | **Notable “still-moving” threads worth a quick skim (and likely to keep evolving):** - Bookmark organization and the long-running “tag bookmarks” request in [Ability to tag a bookmarks](https://meta.discourse.org/t/-/19591/13?silent=true) (#bookmarks) - Sorting and workflow ideas for the change-management UI in [Introducing Upcoming Changes…](https://meta.discourse.org/t/-/392894/19?silent=true) (#upcoming-changes) - Ongoing UX feedback and structure discussions in [Testing Nested Replies on Meta](https://meta.discourse.org/t/-/398759/76?silent=true) - Moderator ergonomics around whispers discoverability in [Whispers only temporarily bump topics](https://meta.discourse.org/t/-/397588/10?silent=true) - Docs landing-page behavior debate in [What should the homepage be for doc categories?](https://meta.discourse.org/t/-/398616/3?silent=true) - Meta gardening/index cleanup workflow in [Experiment: Collaborative content gardening hub for meta](https://meta.discourse.org/t/-/397606/67?silent=true) * * * ## Interesting Topics ### #customization:theme-component - A new splash/screen takeover component landed: @RGJ shared **Full Screen Cover Image** , a theme component that can display a full-page cover image on load (perfect for maintenance notices—or April 1st mischief) in [Full Screen Cover Image](https://meta.discourse.org/t/-/399690/1?silent=true). The thread includes install pointers to [How do I install a theme or theme component?](https://meta.discourse.org/t/-/63682/1?silent=true) and [Beginner’s guide to using Discourse Themes](https://meta.discourse.org/t/-/91966/1?silent=true), plus field reports of how startling it can be when deployed “for real” ([read more](https://meta.discourse.org/t/-/399690/3?silent=true)). ### #announcements - Embedding got a major power-up: Discourse embeds can now run in **full app mode** so visitors can reply/like/quote _inside the iframe_, announced by @Falco in [Embed Discourse as a full comment system on your site](https://meta.discourse.org/t/-/399743/1?silent=true) (#embedding). This builds on the older JS embedding approach in [Embedding Discourse comments via Javascript](https://meta.discourse.org/t/-/31963/1?silent=true), and it effectively answers multiple long-standing “can I embed full threads?” questions raised in [Embedding full threads - possible?](https://meta.discourse.org/t/-/360386/1?silent=true), [Embed single discourse Topics to articles on news website](https://meta.discourse.org/t/-/81473/1?silent=true), and even “topic as widget” use cases ([read more](https://meta.discourse.org/t/-/49811/1?silent=true)). - Discourse AI agents can now connect outward to the broader tool ecosystem: @sam announced **MCP client support** for Discourse AI in [Bring your own MCP!](https://meta.discourse.org/t/-/399668/1?silent=true) (#ai), paired with the admin-facing how-to in [AI Bot – Bring Your Own MCP Server](https://meta.discourse.org/t/-/399667/1?silent=true) (#ai-bot). It’s framed explicitly as the complement to Discourse acting as a server in [Discourse MCP is here](https://meta.discourse.org/t/-/386983/1?silent=true), and contrasts with in-Discourse scripting approaches in [AI Bot: Custom Tools](https://meta.discourse.org/t/-/314103/1?silent=true). - Real-world calendar subscription testing brought feature-completeness questions to the surface: permissions-aware expectations and “show until revoked” ergonomics were discussed in [Calendar subscription URLs for external calendar apps](https://meta.discourse.org/t/-/398902/15?silent=true) (#calendar-and-event). Follow-up troubleshooting noted a key dependency on `Discourse post event enabled` ([read more](https://meta.discourse.org/t/-/398902/17?silent=true)). - Project-status coordination got a quick pulse check: @lindsey noted progress (pending a teammate returning) on translation support for blog styling components in [Current Projects - March 2026](https://meta.discourse.org/t/-/398565/10?silent=true) (#current-projects). ### #blog - A behind-the-scenes multilingual retrospective dropped: @nat posted **Building for Every Language** , covering how Discourse’s multilingual support evolved over 13 years in [Building for Every Language](https://meta.discourse.org/t/-/399661/1?silent=true). It dovetailed nicely with today’s separate translation logistics discussion in plugin-land ([read more](https://meta.discourse.org/t/-/398980/44?silent=true)). ### #bug - Meta itself hit a mobile regression: @Lilly reported topic pages showing only header/title (links dead) on iOS browsers in [Some Meta topic pages borked on mobile viewport](https://meta.discourse.org/t/-/399691/1?silent=true). @dax confirmed quickly ([read more](https://meta.discourse.org/t/-/399691/2?silent=true)), and @davidb traced it to a recent change in the tag icons component with a temporary revert while investigating ([read more](https://meta.discourse.org/t/-/399691/5?silent=true)). Related work on tag icons localization support is also progressing in [Add support for translated tags to the tag icon component](https://meta.discourse.org/t/-/399594/3?silent=true). - Archived topics + reactions had inconsistent logic: a report showed you could sometimes click “like” on archived posts (then get a confusing “too long ago” error), especially where reactions were involved, in [Only posts with no likes or reactions can be “liked” in an archived topic](https://meta.discourse.org/t/-/399681/1?silent=true) (#reactions). @zogstrip confirmed and linked a fix PR adjusting archived-topic handling ([read more](https://meta.discourse.org/t/-/399681/5?silent=true)). - Group invite behavior didn’t respect intent: adding emails in bulk could still send invitation emails even when “Notify users” was unchecked, reported in [Bulk adding email addresses to group sends invitation emails even when “Notify users” is unchecked (latest branch)](https://meta.discourse.org/t/-/397334/1?silent=true). @zogstrip pointed to a fix that ensures the checkbox is actually respected ([read more](https://meta.discourse.org/t/-/397334/2?silent=true)). ### #self-hosting - The “plugins suddenly broke” cluster got clearer: CORS/ES-module loading changes caused **plugin JS to fail behind certain CDN/S3 setups** , with investigation and mitigation steps collected in [All plugins not functioning due to CORS error after recent upgrade](https://meta.discourse.org/t/-/399466/12?silent=true). This also intersected with “missing votes / plugin failures” symptoms discussed in [Topic Voting Plugin - Tally of past votes is missing, users having trouble voting](https://meta.discourse.org/t/-/399649/1?silent=true), where @zogstrip suggested the fix may be covered by the same core change ([read more](https://meta.discourse.org/t/-/399649/16?silent=true)). ### #Support - A spooky “presence” glitch was resolved with a simple toggle: admins seeing an infinite “is replying…” indicator were advised to flip `Presence enabled` off/on; the workaround was confirmed successful in [Infinite ‘is replying…’ bug? / Presence plugin](https://meta.discourse.org/t/-/399655/2?silent=true) (confirmation: [read more](https://meta.discourse.org/t/-/399655/4?silent=true)). - AI bots throwing `{ "error": "Not found" }` turned into a practical configuration walkthrough: a likely deprecated Gemini model ID/URL was flagged, and updated model URL examples were provided in [Issue with AI bots forum bots](https://meta.discourse.org/t/-/399660/1?silent=true) (#ai, #ai-bot), including recommended alternatives for text vs image generation ([read more](https://meta.discourse.org/t/-/399660/6?silent=true)). - A “banner that won’t unpin” mystery ended up being theme-related: after [safe mode](https://meta.discourse.org/t/53504?silent=true) removed the banner, the thread concluded it was coming from a theme/component rather than a pinned-topic banner, and the admin found the right setting in [How to Unpin this Topic from Banner Area](https://meta.discourse.org/t/-/399702/1?silent=true) (solution path: [read more](https://meta.discourse.org/t/-/399702/5?silent=true)). - Pulling live stats/graphs onto an external website prompted guidance toward the API + [Data Explorer](https://meta.discourse.org/t/32566?silent=true): embedding admin dashboard-style reports isn’t a one-click feature, but exporting data is feasible; see [How can I post links to live reports or embed site activity?](https://meta.discourse.org/t/-/399678/1?silent=true) alongside [Run Data Explorer queries with the Discourse API](https://meta.discourse.org/t/-/120063/1?silent=true) and [How to reverse engineer the Discourse API](https://meta.discourse.org/t/-/20576/1?silent=true). - Requests for integrated “/rules” and “/apply” pages (without `/pub`) surfaced again: page publishing didn’t match the desired “native tabbed layout” feel in [Creating custom pages like “About” and “FAQ”](https://meta.discourse.org/t/-/399679/1?silent=true). A practical alternative suggested the official landing pages approach in [Landing Pages Plugin](https://meta.discourse.org/t/-/180967/1?silent=true), while the original request referenced [Page Publishing](https://meta.discourse.org/t/-/151971/1?silent=true). - Search quality concerns appeared in a new report: exact title-word searches failing in a multilingual site (plus a 500 when semantic search embeddings are enabled) was raised in [Search not finding topics by exact title words](https://meta.discourse.org/t/-/399693/1?silent=true) (#search). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco shipped the headline feature of the day—interactive **full-app embeds** —in [Embed Discourse as a full comment system on your site](https://meta.discourse.org/t/-/399743/1?silent=true), and then pointed multiple older “can I embed X?” threads to the new capability in [Topic as widget](https://meta.discourse.org/t/-/49811/10?silent=true), [Embedding full threads - possible?](https://meta.discourse.org/t/-/360386/5?silent=true), and [Embed single discourse Topics to articles on news website](https://meta.discourse.org/t/-/81473/9?silent=true). He also clarified a key prerequisite setting for calendar subscription URLs in [Calendar subscription URLs for external calendar apps](https://meta.discourse.org/t/-/398902/17?silent=true) and discussed future leaderboard flexibility in [Discourse Gamification](https://meta.discourse.org/t/-/225916/452?silent=true). - @sam expanded Discourse AI’s ecosystem reach by announcing MCP connectivity in [Bring your own MCP!](https://meta.discourse.org/t/-/399668/1?silent=true) and documenting setup details in [AI Bot – Bring Your Own MCP Server](https://meta.discourse.org/t/-/399667/1?silent=true). He also performed some doc housekeeping by moving an outdated GetSatisfaction migration topic out of official documentation status in [Migrate from GetSatisfaction to Discourse](https://meta.discourse.org/t/-/56197/9?silent=true). - @nat published the companion discussion for the Discourse blog post on multilingual evolution in [Building for Every Language](https://meta.discourse.org/t/-/399661/1?silent=true), and confirmed imminent progress on translated tags support for tag icons via a linked PR in [Add support for translated tags to the tag icon component](https://meta.discourse.org/t/-/399594/3?silent=true). - @dax quickly confirmed the iOS/mobile rendering regression affecting some Meta pages in [Some Meta topic pages borked on mobile viewport](https://meta.discourse.org/t/-/399691/2?silent=true), helping validate it as more than a single-device anomaly. - @davidb identified the likely culprit for the mobile regression as a recent change in `discourse-tag-icons` and noted a temporary revert while the root cause is investigated in [Some Meta topic pages borked on mobile viewport](https://meta.discourse.org/t/-/399691/5?silent=true). - @david pulled together the “why” and “what to do next” for CDN-related CORS/ES module issues after the plugin loading changes, including the need for a full rebuild for NGINX config changes, in [All plugins not functioning due to CORS error after recent upgrade](https://meta.discourse.org/t/-/399466/12?silent=true) and followed up with additional guidance added to the canonical explanation ([read more](https://meta.discourse.org/t/-/399466/13?silent=true)). - @zogstrip drove several fixes forward: he confirmed and linked a PR correcting archived-topic reactions logic in [Only posts with no likes or reactions can be “liked” in an archived topic](https://meta.discourse.org/t/-/399681/5?silent=true), suggested the relevant core change for plugin vote/tally breakage symptoms in [Topic Voting Plugin - Tally of past votes is missing, users having trouble voting](https://meta.discourse.org/t/-/399649/16?silent=true), noted new support for hiding vote limits in [Topic Voting enabled for our #contribute:feature category!](https://meta.discourse.org/t/-/308402/44?silent=true), and pointed to fixes for group invite notification behavior in [Bulk adding email addresses to group sends invitation emails even when “Notify users” is unchecked (latest branch)](https://meta.discourse.org/t/-/397334/2?silent=true) and RTL external-link icon alignment in [External link icon not RTL](https://meta.discourse.org/t/-/397432/2?silent=true). - @awesomerobot helped triage and improve admin UX across multiple areas: he asked key diagnostic questions on the presence indicator issue in [Infinite ‘is replying…’ bug? / Presence plugin](https://meta.discourse.org/t/-/399655/3?silent=true), opened a PR to avoid misleading “reply to this message” text when no contact user/group is configured in [“reply to this message” goes nowhere?](https://meta.discourse.org/t/-/399477/2?silent=true), and explained why the Horizon sticky layout limitation isn’t trivially solvable via CSS alone in [Horizon theme bug: Category heading container sticky in topic lists](https://meta.discourse.org/t/-/387267/11?silent=true). - @featheredtoast continued clarifying the realities of production usage for the `discourse/discourse` Docker image, especially around plugin builds and why “compile on boot” isn’t viable, in [Is Docker image discourse/discourse considered safe and production-ready?](https://meta.discourse.org/t/-/380646/25?silent=true), including a concrete example referencing [resenha: add Discord-style voice rooms](https://meta.discourse.org/t/-/389056/1?silent=true). - @HAWK weighed in on external reporting/metric display expectations and plan limitations in [How can I post links to live reports or embed site activity?](https://meta.discourse.org/t/-/399678/2?silent=true). * * * Yesterday’s highlight: between fullscreen “site seizure” splash screens and brand-new full-app embeds, Meta managed to both _startle_ and _ship_—may tomorrow’s deployments cause fewer heart palpitations than [Full Screen Cover Image](https://meta.discourse.org/t/-/399690/1?silent=true). ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 2, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/822 "2026-04-02T21:01:35Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 71** - **New topics (last 24h): 11** **Top users (posts / likes in the last 24h):** - @Falco — **4 posts** / **11 likes** - @Moin — **6 posts** / **6 likes** - @mcwumbly — **2 posts** / **5 likes** - @awesomerobot — **4 posts** / **5 likes** - @RGJ — **2 posts** / **4 likes** - @lindsey — **1 post** / **3 likes** - @sam — **2 posts** / **3 likes** - @Tris20 — **1 post** / **3 likes** - @Ed_S — **2 posts** / **2 likes** - @pfaffman — **2 posts** / **2 likes** * * * ## Interesting Topics ### #bug - @Moin noticed **tag banners were suddenly missing their tags** (very empty vibes), and @awesomerobot confirmed it was caused by a core data change and quickly shipped a fix for the #tag-banners component (#fixed) — [read more](https://meta.discourse.org/t/-/399813/1?silent=true) (and the “back to normal” confirmation: [read more](https://meta.discourse.org/t/-/399813/3?silent=true)). - @RGJ reported that the **Category Experts plugin can crash user merges** due to validations while merging via CLI; @zogstrip linked a fix in progress for #category-experts — [read more](https://meta.discourse.org/t/-/399785/1?silent=true). - @hel_Sinki flagged a **high-severity backup failure to Cloudflare R2** during multipart upload (`undefined method 'downcase' for nil`) affecting S3-compatible backup storage; @pfaffman shared a pragmatic gem-pinning workaround and confirmed it’s a recurring “S3-compatible” edge case — [read more](https://meta.discourse.org/t/-/399768/1?silent=true) (workaround link drop: [read more](https://meta.discourse.org/t/-/399768/2?silent=true)). - @putty shared screenshots of **German translations leaking “AI commentary” (thought process text)** into the output, including cases where German posts look odd when viewed in English — [read more](https://meta.discourse.org/t/-/399805/1?silent=true). - A theme-component gotcha: **Topic List Previews (TLP) broke sites on 2026.1.3 ESR** due to a missing compatibility pin; @RGJ provided a PR and mitigation steps, and @merefield merged quickly — [read more](https://meta.discourse.org/t/-/209973/730?silent=true). - @davidb noted a fix landing for **group dropdowns not refreshing correctly after new groups are created** , pointing to the resolving commit (#fixed) — [read more](https://meta.discourse.org/t/-/398285/3?silent=true). - @Jesse_Starks reported a weird **iPad Safari composer jumping to the top** (breaking buttons and resizing) that later became hard to reproduce; early suspicion pointed at theme interactions (Horizon/Foundation) — [read more](https://meta.discourse.org/t/-/399794/1?silent=true). ### #ux - @Ed_S found that hitting an **old numeric tag URL (`/tag/6309`) throws a 500 instead of a 404/redirect**, triggering Google crawl errors; @supermathie included the stack trace and suggested better fallback/handling — [read more](https://meta.discourse.org/t/-/399784/1?silent=true). - @Eviepayne highlighted an MFA rollout pain point: **enforcing MFA can “lock” logged-in but unenrolled users onto security prefs** , preventing them from reading the very guidance topic they need; they requested richer admin messaging (and noted “passkeys are MFA”) — [read more](https://meta.discourse.org/t/-/399836/1?silent=true). - On docs navigation, @nickrsan explored what the **“homepage” should be for doc categories** , discovering a larger rework in progress for doc-categories and asking how an “index topic as home” option might fit with upcoming “Simple Mode” work — [read more](https://meta.discourse.org/t/-/398616/4?silent=true). ### #contribute:feature - A long-running gamification request got fresh momentum: @Falco is investigating **per-leaderboard scoring values** and shared a first draft PR direction for #gamification — [read more](https://meta.discourse.org/t/-/264619/9?silent=true). - @sam and @Falco discussed whether AI personas/agents should **respond only to explicit `@mentions`** (rather than replies), with a lean toward avoiding “option paralysis” and instead leaning on upcoming workflows — [read more](https://meta.discourse.org/t/-/399221/2?silent=true) (Falco’s workflow angle: [read more](https://meta.discourse.org/t/-/399221/3?silent=true)). - @Moin proposed improving localization polish: **tag icons don’t appear for translated tags inside tag banners** , especially in combined category+tag headers (new request tying together #tag-banners + #tag-icons + #content-localization) — [read more](https://meta.discourse.org/t/-/399840/1?silent=true). ### #Announcements - @lindsey announced a quality-of-life improvement for support: people who are **Tracking/Watching topics in a Solved-enabled support category now get a notification when a topic is marked solved** (with a user preference to disable) — [read more](https://meta.discourse.org/t/-/399821/1?silent=true). _(Related background: Solved plugin [read more](https://meta.discourse.org/t/-/30155/1?silent=true) and “support categories” guidance [read more](https://meta.discourse.org/t/-/398338/1?silent=true))._ - The new embedding work drew UI feedback: in the “full comment system” embed, @Tris20 suggested making **scrollbars and “Reply to Topic” affordances more obvious** to prevent accidental replies/notifications; @mcmcclur echoed concerns that some UI elements may be too subtle — [read more](https://meta.discourse.org/t/-/399743/9?silent=true). ### #blog - In multilingual land, @mcwumbly praised the storytelling (and years-long payoff) behind **Building for Every Language** , calling out how discussions mature over time and tying it back to the “magical multilingual features” — [read more](https://meta.discourse.org/t/-/399661/2?silent=true). - On the AI tooling front, @Falco added an **“edit existing posts” tool to Discourse MCP** , responding to requests for wiki/post updates via LLMs (and hinting at broader “remote web MCP” thinking) — [read more](https://meta.discourse.org/t/-/386983/31?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** - **@Falco** - **@mcwumbly** - **@lindsey** - **@sam** - **@supermathie** - **@martin** - **@zogstrip** - **@davidb** * * * > Bonus threads that also saw fresh replies (for extra context): numeric tag handling (#tags) [read more](https://meta.discourse.org/t/-/399784/1?silent=true), plugin/theme troubleshooting patterns via [Safe Mode](https://meta.discourse.org/t/53504?silent=true) docs [read more](https://meta.discourse.org/t/-/53504/1?silent=true), and more self-hosting “S3-compatible isn’t always S3” reality checks [read more](https://meta.discourse.org/t/-/399768/2?silent=true). Sign-off: Yesterday’s vibe was “everything is fine”… right up until tag banners went blank and Falco’s migration “buddy” demanded emotional support—classic Meta day. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 3, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/823 "2026-04-03T21:01:39Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **Last 24 hours (2026-04-02 → 2026-04-03)** saw **99 new posts** across **10 new topics** , with a big chunk of the conversation orbiting the new **“Boosts”** experiment in #Announcements ([read more](https://meta.discourse.org/t/-/399835/1?silent=true)) and a quick turnaround on an Ask Discourse outage in #Site feedback #ask-discourse ([read more](https://meta.discourse.org/t/-/399862/1?silent=true)). ### Totals - **New posts:** 99 - **New topics:** 10 ### Top users (posts + likes in the last 24h) | User | Posts | Likes | | --- | --- | --- | | **@Moin** | 10 | 17 | | **@NateDhaliwal** | 9 | 11 | | **@RGJ** | 7 | 13 | | **@Canapin** | 6 | 14 | | **@awesomerobot** | 5 | 14 | | **@putty** | 4 | 11 | | **@nat** | 4 | 9 | | **@Lilly** | 3 | 11 | | **@Bas** | 2 | 10 | | **@lindsey** | 1 | 10 | > “Boosts fill a gap in the interaction hierarchy…” — @j.jaffeux in the Boosts trial thread ([read more](https://meta.discourse.org/t/-/399835/19?silent=true)) * * * ## Interesting Topics ### #Announcements - @lindsey kicked off a Meta-only experiment for **Boosts** —a “reaction with a tiny message” intended to reduce low-effort replies while still acknowledging posts, sparking debate about naming, discoverability, moderation/flagging, and whether boosts should eventually unify with likes/reactions ([read more](https://meta.discourse.org/t/-/399835/1?silent=true)). Related: ActivityPub/Mastodon-style “boost” confusion came up too ([read more](https://meta.discourse.org/t/-/399835/15?silent=true)), alongside a request for better “quote boost” support ([read more](https://meta.discourse.org/t/-/397569/1?silent=true)) and concerns about AI/toxicity scanning + watched-words coverage ([read more](https://meta.discourse.org/t/-/399835/29?silent=true)). - The new **“Embed Discourse as a full comment system”** announcement continued to draw practical UX feedback—especially around infinite scroll hiding key actions and questions about how embedded replies/likes show up in reporting and categories ([read more](https://meta.discourse.org/t/-/399743/11?silent=true)). One user pointed to tag organization context as a way to reason about where embedded content lands ([read more](https://meta.discourse.org/t/-/72467/1?silent=true)). ### #Site feedback - Ask Discourse briefly went down, with multiple confirmations and a fast fix: @Bas acknowledged and resolved the issue within the thread, closing the loop cleanly for #ask-discourse watchers ([read more](https://meta.discourse.org/t/-/399862/1?silent=true)). - A separate Ask Discourse UX nit: the **“Back to Forum”** link appears on the homepage where it’s redundant. @awesomerobot noted Ask is a special customization case and the team will hide it there ([read more](https://meta.discourse.org/t/-/399871/2?silent=true)). ### #General - A community member asked whether there are any Discourse forums focused on **public transit / urban design** ; @awesomerobot suggested checking the official directory plus a known Queensland example, and @RGJ added a London-related forum link ([read more](https://meta.discourse.org/t/-/399902/1?silent=true)). ### #ux - A self-host admin hit a **2FA enforcement lock-in** problem and wanted to embed help content in the enforcement message. The solution: customize site text (simple) or inject a richer HTML help panel via a theme component + outlet rendering (flexible) ([read more](https://meta.discourse.org/t/-/399836/3?silent=true)). - A **500 error on old numeric tag URLs** (hurting Google crawl) got staff eyes quickly; @nat confirmed compatibility of `/tag/name` resolution is intentional and a fix is forthcoming for numeric edge cases ([read more](https://meta.discourse.org/t/-/399784/11?silent=true)). ### #bug - An AI-related localization glitch: **German translations accidentally included “Thinking/Translate” artifacts** in public output. @nat traced it to a recent prompt/feature update and shipped a formatting-tightening fix, plus cleaned up affected posts/titles ([read more](https://meta.discourse.org/t/-/399805/4?silent=true)). (There’s also ongoing broader language/translation work being discussed elsewhere, e.g. blog follow-ups ([read more](https://meta.discourse.org/t/-/399661/1?silent=true)).) ### #Support - A moderation workflow surprise: **hidden posts can reappear after the author edits**. The thread clarifies this is intended behavior for “hidden” (vs deleted) content—if you want it to stay out of the timeline, request revision pre-publication or delete after posting ([read more](https://meta.discourse.org/t/-/399901/2?silent=true)). - Self-hosters revisited **iOS push notifications via “Add to Home Screen”** : @Falco confirmed PWA push should work on iOS 16.4+ and dug into why admin impersonation can break notification setup, pointing at a specific initializer line as the culprit ([read more](https://meta.discourse.org/t/-/394149/13?silent=true)). A related upload/draft-loss thread also saw renewed attention ([read more](https://meta.discourse.org/t/-/399453/3?silent=true)). - A new #rest-api question asked how to **GET “Featured Topics”**. The answer: if featured topics are used in category list layouts, they can be pulled from `/categories.json` under each category’s `topics` array ([read more](https://meta.discourse.org/t/-/399867/2?silent=true)). - A Chinese-language report showed a **Poll plugin “NoMethodError”** in an #unsupported-install Bitnami environment; replies pointed out Bitnami installs are deprecated/unsupported and may behave differently from the [standard install](https://meta.discourse.org/t/142537?silent=true) docs ([read more](https://meta.discourse.org/t/-/399856/2?silent=true)). Supporting context: the canonical “[standard install](https://meta.discourse.org/t/142537?silent=true)” guide ([read more](https://meta.discourse.org/t/-/142537/1?silent=true)) and the explicit “Bitnami installations are unsupported” note ([read more](https://meta.discourse.org/t/-/142538/1?silent=true)), plus the “container image is deprecated” discussion ([read more](https://meta.discourse.org/t/-/374875/1?silent=true)). - Mail-receiver troubleshooting resurfaced: a user migrating away from Gmail found their self-hosted mail server was rejected due to **SPF failures** , with logs showing `550 5.7.23` rejections and prompting deeper email-auth alignment checks ([read more](https://meta.discourse.org/t/-/349243/7?silent=true)). ### #contribute:feature - AI embeddings integration got a sharp edge-case: **Mistral embeddings aren’t fully OpenAI-compatible** because the API expects `output_dimension` while Discourse requires `dimensions`, making “Run Test” work but blocking saves without `dimensions` ([read more](https://meta.discourse.org/t/-/399854/1?silent=true)). Background reference: earlier “how to implement Mistral with embeddings” guidance ([read more](https://meta.discourse.org/t/-/361095/1?silent=true)). - Localization + tag visuals: two parallel requests aimed to make **tag icons work with translated tags** —both in tag banners and the tag icon component. The core issue: translated tag labels don’t currently pick up icons like the default-language tag does ([read more](https://meta.discourse.org/t/-/399840/1?silent=true)) and related component support is being requested too ([read more](https://meta.discourse.org/t/-/399594/1?silent=true)). - Emoji search got more multilingual: **localized emoji aliases** (English + translations) were implemented via PRs, and in the process the `emojis.json` payload shrank by ~160KB ([read more](https://meta.discourse.org/t/-/86641/25?silent=true)). ### #Migrating to Discourse - A migration deep-dive: importing Google Groups via **mbox** worked, but messages tied to already-existing Discourse users appeared authored by `system`. The thread asks how to map existing users to imported messages (without rolling back via backup each time) ([read more](https://meta.discourse.org/t/-/79773/252?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @lindsey launched the **Boosts** experiment on Meta, outlining how boosts work, notification behavior, and asking for feedback on usefulness and naming ([read more](https://meta.discourse.org/t/-/399835/1?silent=true)). - @zogstrip clarified that boosts aren’t intended to reorder posts (i.e., not an algorithmic “boost”), and later joined troubleshooting on a Poll/Bitnami error report ([read more](https://meta.discourse.org/t/-/399835/8?silent=true), [read more](https://meta.discourse.org/t/-/399856/2?silent=true)). - @j.jaffeux framed boosts as a missing rung in the engagement ladder and hinted at a longer-term direction: **unifying boosts/reactions/likes** so communities can choose the interaction model that fits ([read more](https://meta.discourse.org/t/-/399835/19?silent=true)). - @awesomerobot provided the clearest positioning on Boosts: optional, inspired by Basecamp-style morale boosts, and potentially useful for communities that otherwise generate lots of short “cool!” replies; also confirmed boosts aren’t scanned by AI today (but could be) while watched words apply ([read more](https://meta.discourse.org/t/-/399835/22?silent=true), [read more](https://meta.discourse.org/t/-/399835/29?silent=true)). They also acknowledged an Ask Discourse homepage UX edge case and suggested a directory approach for finding transit-related Discourse communities ([read more](https://meta.discourse.org/t/-/399871/2?silent=true), [read more](https://meta.discourse.org/t/-/399902/2?silent=true)). - @Bas responded quickly to an Ask Discourse outage report and confirmed the fix after investigation, keeping the status visible to reporters ([read more](https://meta.discourse.org/t/-/399862/3?silent=true), [read more](https://meta.discourse.org/t/-/399862/4?silent=true)). - @nat confirmed an incoming fix for the **numeric tag old-URL 500 error** while reinforcing that `/tag/name` compatibility is a deliberate product decision ([read more](https://meta.discourse.org/t/-/399784/11?silent=true)). They also shipped a fix for AI-generated translation formatting issues in German and cleaned up affected content ([read more](https://meta.discourse.org/t/-/399805/4?silent=true)), plus shared the next entry in the language/localization blog series ([read more](https://meta.discourse.org/t/-/397784/8?silent=true), [read more](https://meta.discourse.org/t/-/399661/1?silent=true)) and clarified a tag translation example as intentional wordplay ([read more](https://meta.discourse.org/t/-/399594/6?silent=true)). - @Falco confirmed iOS PWA push notification support for Discourse instances added to the home screen and pointed to a specific code path that makes notifications fragile after admin impersonation ([read more](https://meta.discourse.org/t/-/394149/11?silent=true), [read more](https://meta.discourse.org/t/-/394149/13?silent=true)). They also noted the implementation of localized emoji aliases and a payload reduction win ([read more](https://meta.discourse.org/t/-/86641/25?silent=true)). - @supermathie answered a 2FA enforcement UX question by pointing admins to customize the enforcement copy via **site text overrides** , enabling clearer instructions for locked-out users ([read more](https://meta.discourse.org/t/-/399836/2?silent=true)). * * * Boost rockets launched, Ask Discourse recovered, and a handful of translation/notification gremlins got chased off—pretty solid day for both _uplifts_ and _fixes_. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 4, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/824 "2026-04-04T21:01:41Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 71 - **New topics (last 24h):** 14 **Top users (posts • likes)** | User | Posts | Likes | Recent highlights | | --- | --- | --- | --- | | @RGJ | 8 | 18 | Boosts/reactions UX debate in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/49?silent=true) and a UX wording nit in [“do you want to discard your post ?”](https://meta.discourse.org/t/-/399942/1?silent=true) | | @Ed_S | 7 | 15 | Minimalism discussion kickoff in [How minimal is your forum?](https://meta.discourse.org/t/-/399941/1?silent=true) and more nuance on “boosts” as language/UX in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/48?silent=true) | | @Canapin | 4 | 13 | Concern about “boosts” being a single-emoji workaround in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/41?silent=true) plus sharing a fairly minimal setup in [How minimal is your forum?](https://meta.discourse.org/t/-/399941/5?silent=true) | | @ToddZ | 3 | 5 | “Boosts” comparisons (Basecamp/Mastodon) and settings pointers in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/43?silent=true) | | @Moin | 4 | 3 | Version/context help in the translation thread [Images missing… when using Mistral](https://meta.discourse.org/t/-/399939/2?silent=true) and composer-mode guidance in [Toggling off the composer panel](https://meta.discourse.org/t/-/399937/2?silent=true) | > Sample of where the day’s energy went: UX iteration on boosts ([read more](https://meta.discourse.org/t/-/399835/45?silent=true)), composing/editing ergonomics ([read more](https://meta.discourse.org/t/-/399942/1?silent=true)), and a flurry of plugin/self-hosting problem-solving ([read more](https://meta.discourse.org/t/-/399936/1?silent=true), [read more](https://meta.discourse.org/t/-/399956/1?silent=true)). * * * ## Interesting Topics ### #Announcements - @Canapin and @nickrsan dug into the _UX cost_ of “boosts” (visual noise, emoji semantics, and whether boosts should merge with reactions/likes), while @ToddZ and others compared the term to Basecamp/Mastodon patterns in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/45?silent=true). - Embedding Discourse as a full comment system kept getting real-world scrutiny: @traek called out the “scroll an iframe forever” problem and asked for a top-level comment entry affordance in [Embed Discourse as a full comment system on your site](https://meta.discourse.org/t/-/399743/14?silent=true). ### #General - Feature restraint became the theme: @Ed_S shared a deliberately small configuration (few categories, no chat/reactions/LLMs) and prompted others to compare “minimal by choice” setups in [How minimal is your forum?](https://meta.discourse.org/t/-/399941/1?silent=true). - A lighter thread still surfaced an operational question: finding Discourse communities about transit—follow-ups narrowed interest away from UK examples in [Are there forums on public transit in discourse?](https://meta.discourse.org/t/-/399902/4?silent=true). ### #customization:plugin - @Anton_Akhmerov proposed a “multi-team Discourse” concept: turning top-level categories into _workspaces_ and subcategories into _channels_ (with paired chat channels), and @mcwumbly asked about real-world use and scaling in [Workspace groups](https://meta.discourse.org/t/-/399936/2?silent=true) (#groups #chat). - A new anti-abuse tool dropped: ProxyTracer’s plugin offers VPN/proxy detection at registration/login/global, with caching and fail-open options to avoid mass lockouts in [ProxyTracer: VPN & Proxy Blocker](https://meta.discourse.org/t/-/399958/1?silent=true). - A practical maintenance update: the repo move (GitHub → GitLab) for challenges tooling continued, including a note about account flagging fallout in [Discourse Daily Challenges](https://meta.discourse.org/t/-/398980/69?silent=true). - Push notifications via Pushover got a modernization pass: @featheredtoast shipped updates so the plugin works with recent Discourse versions in [Pushover notifications](https://meta.discourse.org/t/-/119258/28?silent=true) (#notifications). ### #bug - Translation + uploads hit a sharp edge: switching from OpenAI to Mistral caused **images to disappear in translated versions** (upload links not preserved). The workaround was effectively “use a stronger model”: Mistral Large resolved it, while Small didn’t reliably follow instructions in [Images missing in translated posts when using Mistral as translation model](https://meta.discourse.org/t/-/399939/5?silent=true) (#ai #content-localization). - Safari PWA users ran into rate limiting on the events endpoint, with a screen recording shared for diagnosis in [/upcoming-events rate limiting](https://meta.discourse.org/t/-/399931/1?silent=true) (#calendar-and-event). - Cloudflare R2 backups: an aws-sdk-s3 multipart upload failure workaround was confirmed—but only after placing the snippet in its own hooks block in [Backups to Cloudflare R2 fail during multipart upload…](https://meta.discourse.org/t/-/399768/4?silent=true). ### #ux - A deceptively small wording issue kept tripping people up: when abandoning an _edit_, the UI says “Discard your post?” (even if there are no changes). The request: make it “Cancel edit” / “Discard edits” and avoid prompting when nothing changed in [“do you want to discard your post ?”](https://meta.discourse.org/t/-/399942/1?silent=true). ### #contribute:feature - Media compatibility surfaced as a silent failure mode: VP9-in-MP4 uploads can look fine on desktop/Android but fail on iOS Safari; the proposal is to detect codec on upload and reject or transcode. Related pointers included the official streaming/transcoding direction in [Auto-detect or reject VP9 video uploads incompatible with iOS Safari](https://meta.discourse.org/t/-/399955/1?silent=true) (see also [Discourse Video Stream 🎥](https://meta.discourse.org/t/-/388754/1?silent=true)). ### #community-building Building - Growth without a product “gravity well”: @haydenjames described the challenge of sustaining engagement in a niche community where the admin remains the main activity engine, and asked what actually moves the needle beyond “babysitting” in [How to Grow a Discourse Forum without product or service behind it?](https://meta.discourse.org/t/-/399943/1?silent=true) (#community-strategy). ### #Support - A serious moderation/design boundary question: AI triage automation worked for public posts but did **not** appear to scan DMs between regular users even with “Include personal messages” enabled, raising concerns about abuse moving to private channels in [Does AI triage automation scan DMs between regular users?](https://meta.discourse.org/t/-/399952/1?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot weighed in on when “boosts” are _not_ appropriate (“don’t boost anything you need to rely on later”), helping define the line between lightweight acknowledgement and durable content in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/44?silent=true). - @mcwumbly encouraged the direction of category-as-workspace thinking and asked about “in the wild” adoption / real operational experience for the prototype in [Workspace groups](https://meta.discourse.org/t/-/399936/2?silent=true). - @featheredtoast unpacked a push-notification privacy/safety edge case (logged-out devices still receiving sensitive previews), and floated ideas like binding subscriptions to sessions in [iOS/Android Push Notifications on Self-Hosted Discourse (Docker)](https://meta.discourse.org/t/-/394149/15?silent=true); they also shipped an update to modernize the integration in [Pushover notifications](https://meta.discourse.org/t/-/119258/28?silent=true). - @Falco responded to the VP9/iOS upload problem with a practical “this exists, but shipping safely is hard” pointer to the official streaming approach in [Auto-detect or reject VP9 video uploads incompatible with iOS Safari](https://meta.discourse.org/t/-/399955/2?silent=true). * * * If yesterday was any indication, today’s mission is clear: keep your forums _minimal_, your boosts _uncluttered_, and your “Discard” dialogs _only discarding what you actually changed_. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 5, 2026, 9:02pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/825 "2026-04-05T21:02:55Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 50** - **New topics (last 24h): 7** **Top users (posts / likes received in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @Moin | 4 | 10 | | @Lilly | 4 | 6 | | @Ed_S | 4 | 5 | | @Denis_Kovalenko | 4 | 3 | | @Falco | 2 | 5 | | @elmuerte | 3 | 4 | | @mcwumbly | 3 | 1 | | @NateDhaliwal | 2 | 3 | | @Monikas | 1 | 3 | | @satonotdead | 1 | 3 | | @Canapin | 1 | 1 | > Notable quick wins: @Falco committed to adding languages to Meta’s translator “early next week” in [this thread](https://meta.discourse.org/t/-/399957/8?silent=true), and @mcwumbly linked real-world TL3 tuning changes Meta just made in [this support discussion](https://meta.discourse.org/t/-/399973/3?silent=true). * * * ## Interesting Topics ### #contribute:site-feedback - @Denis_Kovalenko asked for Ukrainian/Russian to be added to Meta’s language switcher, and @Falco confirmed it’s a good idea and will be added soon ([read more](https://meta.discourse.org/t/-/399957/8?silent=true)). - In the ongoing “content gardening hub” experiment, @Moin noticed category descriptions/config no longer match the intended “only certain groups can post” rules, which helped connect the dots to a new permissions-reset bug ([read more](https://meta.discourse.org/t/-/397606/72?silent=true)). (Related: the bug report itself in #bug: [read more](https://meta.discourse.org/t/-/399976/1?silent=true).) ### #Support - @Ed_S wanted _data-driven_ advice for tuning TL3 promotion/demotion thresholds; @Moin pointed to per-user TL3 requirements and [Data Explorer](https://meta.discourse.org/t/32566?silent=true) queries ([read more](https://meta.discourse.org/t/-/399973/2?silent=true)), and @mcwumbly shared Meta’s own recent cap reductions (500→250 topics viewed, 20k→2k posts read) based on query results ([read more](https://meta.discourse.org/t/-/399973/3?silent=true)). (Deep link: the referenced query thread at [read more](https://meta.discourse.org/t/-/91495/27?silent=true).) - A Chinese-language support thread dug into why all traffic appears as Cloudflare IPs when there’s a _second_ reverse proxy layer; replies focused on updating nginx config and questioning whether the extra proxy layer (e.g. 1Panel) is necessary ([read more](https://meta.discourse.org/t/-/399954/4?silent=true)). - @wuyuan reported a mysterious bottom-left overlay showing “gadgets” across forums; @Ed_S identified it as a UI gadget box (theme toggle, light/dark, shortcut help) and pointed to an existing component discussion ([read more](https://meta.discourse.org/t/-/399977/2?silent=true); related: [read more](https://meta.discourse.org/t/-/242802/1?silent=true)). - A French admin asked how to notify all event registrants about cancellations without manually @-mentioning dozens of users—raising a potential gap in #calendar-and-event workflows ([read more](https://meta.discourse.org/t/-/399981/1?silent=true)). - In AI triage automation, @Denis_Kovalenko questioned whether “Include personal messages” scans DMs between two regular (non-staff) users; @RGJ clarified that it does—then asked how the behavior was verified ([read more](https://meta.discourse.org/t/-/399952/2?silent=true)). - @Richie reported Google Search Console still complaining about a missing `text` field in `mainEntity.suggestedAnswer` despite updating to 2026.4.0-latest, referencing last week’s earlier report and fix attempt ([read more](https://meta.discourse.org/t/-/399974/1?silent=true); background: [read more](https://meta.discourse.org/t/-/399525/1?silent=true)). - In a long-running sign-up approval workflow doc, @stephtara asked what “refusal” looks like in practice—can staff provide reasons, “park” requests, or message applicants to clarify missing info? ([read more](https://meta.discourse.org/t/-/112128/33?silent=true)) - A previously active support topic saw a confirm-that-it’s-fixed follow-up: after updating, “official components” started working again for @Stephane_Roy ([read more](https://meta.discourse.org/t/-/398143/3?silent=true)). ### #customization:plugin - @elmuerte released a **Ko-fi integration plugin** that can reward donations with badges/group membership (including tier-based monthly memberships), with notes about currency limitations and anonymization support ([read more](https://meta.discourse.org/t/-/399978/1?silent=true)). Follow-up discussion covered long-term maintenance and potential enhancements like a public progress bar/widget support ([read more](https://meta.discourse.org/t/-/399978/4?silent=true)). - The **ProxyTracer: VPN & Proxy Blocker** thread debated whether [Safe Mode](https://meta.discourse.org/t/53504?silent=true) undermines a security plugin; @Moin argued [safe mode](https://meta.discourse.org/t/53504?silent=true) won’t help much for a Ruby-only plugin and raised caution flags, and the author updated docs (and removed a redundant `about.json`) in response ([read more](https://meta.discourse.org/t/-/399958/6?silent=true); author update: [read more](https://meta.discourse.org/t/-/399958/7?silent=true)). - The long-running **Locations Plugin** thread received a report that category maps stopped generating after an update; @merefield suggested sponsorship and offered to investigate ([read more](https://meta.discourse.org/t/-/69742/1232?silent=true)). - In the experimental **Discourse Suggested Edits** plugin thread, @NateDhaliwal asked whether OPs are notified when someone suggests an edit—after not spotting notification logic in the code ([read more](https://meta.discourse.org/t/-/398691/3?silent=true)). ### #contribute:feature - A feature request proposed auto-detecting or rejecting VP9 video uploads that won’t play on iOS Safari; discussion explored async/background transcoding trade-offs vs. simply flagging VP9 on upload. @Falco highlighted CPU-abuse risks (especially 1vCPU self-hosts) but considered exploring a plugin option ([read more](https://meta.discourse.org/t/-/399955/4?silent=true)). ### #bug - @Moin reported a serious issue where category security permissions can reset when changing parent/subcategory relationships under the “simplified category creation” upcoming change—potentially re-enabling `everyone` reply/create without warning ([read more](https://meta.discourse.org/t/-/399976/1?silent=true)). @mcwumbly confirmed it sounded familiar and said the team would dig in ([read more](https://meta.discourse.org/t/-/399976/2?silent=true)). (Related upcoming change: [read more](https://meta.discourse.org/t/-/394971/1?silent=true).) ### #announcements - Feedback continued on “Testing Boosts on Meta,” with @satonotdead endorsing a UI concept that “fuses” elements from multiple approaches because the current state feels confusing ([read more](https://meta.discourse.org/t/-/399835/57?silent=true)). (Referenced earlier mock/concept: [read more](https://meta.discourse.org/t/-/399835/27?silent=true).) - In the “notify when a watched/tracked topic is solved” announcement, @marteng69 flagged that disabling this new notification also disables alerts when _your own_ post is marked as the solution—asking whether that’s intended or a bug ([read more](https://meta.discourse.org/t/-/399821/2?silent=true)). ### #General - @Monikas shared a slick Zenless Zone Zero “Inter-Knot UI” inspired Discourse theme concept; @Lilly encouraged reposting it properly under #Customization > Theme with a GitHub repo link so others can try it ([read more](https://meta.discourse.org/t/-/399961/2?silent=true)). - In “How minimal is your forum?”, the discussion swung back to category vs tag sprawl: @NateDhaliwal teased the “huge bunch of tags,” and @Ed_S reflected on whether low-usage tags help users vs SEO—then spun that into a deeper TL2/TL3 capability question ([read more](https://meta.discourse.org/t/-/399941/7?silent=true)). - A small but handy docs pointer: in the trust-level explainer thread, @stephtara asked for the “permissions per trust level” reference, and @ToddZ linked the canonical permissions matrix topic ([read more](https://meta.discourse.org/t/-/396792/10?silent=true); reference: [read more](https://meta.discourse.org/t/-/224824/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco confirmed Meta will add Ukrainian/Russian to the translator language switcher soon, responding directly to the request in #contribute:site-feedback ([read more](https://meta.discourse.org/t/-/399957/8?silent=true)). - @Falco continued the VP9-on-iOS discussion, explaining why server-side video handling is trickier than images (CPU abuse vectors on small instances), but floated making an optional plugin path for admins willing to accept trade-offs ([read more](https://meta.discourse.org/t/-/399955/4?silent=true)). - @mcwumbly shared operational insight into TL3 tuning on Meta—specifically, reduced “cap” defaults informed by real usage data—while also discussing how Discourse may roll out future default changes more transparently ([read more](https://meta.discourse.org/t/-/399973/3?silent=true)). - @mcwumbly acknowledged a high-impact permissions regression report and confirmed the team would investigate the category-security reset behavior ([read more](https://meta.discourse.org/t/-/399976/2?silent=true)). - @mcwumbly tied the “lost posting restrictions” mystery back to the same re-parenting bug class, and said he’d prioritize sorting the restrictions later that day ([read more](https://meta.discourse.org/t/-/397606/74?silent=true)). * * * Signing off: Yesterday was a classic Meta combo—_new languages incoming_ while category permissions played a little game of “now you see me, now you don’t.” ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 6, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/826 "2026-04-06T21:01:56Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **81** new posts across **9** new topics _(Sample of where the conversation happened: [AI DM triage](https://meta.discourse.org/t/-/399952/4?silent=true), [Data Explorer semicolons](https://meta.discourse.org/t/-/400015/1?silent=true), [Topic Hover Cards](https://meta.discourse.org/t/-/400025/1?silent=true))_ - **Top users (posts / likes)** | User | Posts | Likes | Notable threads they were active in | | --- | --- | --- | --- | | @RGJ | 8 | 15 | Confirmed how DM scanning is included/excluded in automations ([read more](https://meta.discourse.org/t/-/399952/4?silent=true)); reported [Data Explorer](https://meta.discourse.org/t/32566?silent=true) edge cases ([read more](https://meta.discourse.org/t/-/400015/1?silent=true), [read more](https://meta.discourse.org/t/-/400018/1?silent=true)) | | @Canapin | 7 | 16 | Continued the boosts experiment discussion ([read more](https://meta.discourse.org/t/-/399835/58?silent=true)); weighed update-risk tradeoffs for self-hosters ([read more](https://meta.discourse.org/t/-/241232/9?silent=true)) | | @Falco | 4 | 4 | Landed progress on localized emoji aliases ([read more](https://meta.discourse.org/t/-/86641/26?silent=true)); discussed model choices & GDPR expectations for AI translation/embeddings ([read more](https://meta.discourse.org/t/-/399939/8?silent=true), [read more](https://meta.discourse.org/t/-/399854/3?silent=true)) | | @awesomerobot | 3 | 5 | Suggested clearer UI wording for automation “topic type” options ([read more](https://meta.discourse.org/t/-/399952/6?silent=true)); debugged a theme-component behavior question ([read more](https://meta.discourse.org/t/-/242802/40?silent=true)) | | @manuel | 3 | 4 | Pointed folks to the official Lucide icon set and noted docs updates needed ([read more](https://meta.discourse.org/t/-/206693/24?silent=true), [read more](https://meta.discourse.org/t/-/206693/28?silent=true)) | | @ばこん | 3 | 3 | Worked through a “sidebar not appearing” mystery with the theme-toggle component ([read more](https://meta.discourse.org/t/-/242802/41?silent=true)) | | @ars18 | 2 | 8 | Released a “MiniMod” plugin concept for delegated category/tag management ([read more](https://meta.discourse.org/t/-/400019/1?silent=true)) | | @chapoi | 2 | 7 | Asked for better previews/screenshots on a new theme component announcement ([read more](https://meta.discourse.org/t/-/400025/2?silent=true)); clarified Horizon theme compatibility expectations ([read more](https://meta.discourse.org/t/-/360486/79?silent=true)) | | @bryce | 1 | 4 | Explained the “mysterious dots/lines” overlay as a sidebar fade gradient + CSS override ([read more](https://meta.discourse.org/t/-/399977/5?silent=true)) | | @pmusaraj | 1 | 3 | Shared a core fix in flight for numeric-tag legacy URL 500s ([read more](https://meta.discourse.org/t/-/399784/12?silent=true)) | * * * ## Interesting Topics ### #Support - @Denis_Kovalenko discovered AI triage automation _wasn’t_ scanning DMs between regular users until “Topic Type” was left blank; @RGJ confirmed the audit logs omission and the fix path, and @awesomerobot suggested UI copy changes to reduce confusion ([read more](https://meta.discourse.org/t/-/399952/4?silent=true)). - A translation workflow issue surfaced where images went missing in translated posts when using a Mistral model; discussion shifted toward _which_ “Mistral Small” is meant, and what better-supported alternatives exist for both quality and GDPR constraints ([read more](https://meta.discourse.org/t/-/399939/8?silent=true)). ### #Announcements - The “Boosts on Meta” trial continued with @Canapin arguing boosts may be more “guestbook-like” for authors than useful for readers, and a side debate emerged about whether boosts could introduce negativity that clashes with Discourse’s no-downvote philosophy ([read more](https://meta.discourse.org/t/-/399835/58?silent=true)). ### #customization:theme component - A new component, **Topic Hover Cards** , was announced to show rich previews when hovering internal topic links; @chapoi requested screenshots/preview links to make evaluation easier before install ([read more](https://meta.discourse.org/t/-/400025/1?silent=true)). - In the official **Sidebar Theme Toggle** component thread, a “sidebar not appearing” report ended up being a configuration/selection hiccup that resolved during troubleshooting, after @awesomerobot checked theme selectability settings ([read more](https://meta.discourse.org/t/-/242802/40?silent=true)). ### #customization:plugin - **Discourse MiniMod** debuted as a plugin that extends category group moderation so trusted users can manage categories/tags/topics without full mod/admin powers—positioned as “organizers” who can rearrange shelves, not “kick people out” ([read more](https://meta.discourse.org/t/-/400019/1?silent=true)). - The long-running **Topic Ratings** plugin thread saw a regression report (ratings UI vanished), followed by a fix PR for leftover widget references—and a note that the plugin has been modernized further in a separate fork pending more testing ([read more](https://meta.discourse.org/t/-/39578/440?silent=true)). ### #bug - [Data Explorer](https://meta.discourse.org/t/32566?silent=true) authors hit a guardrail: queries containing HTML entities like `"` couldn’t be saved because semicolons were being flagged even inside quoted strings; the request is for smarter detection (end-of-query/outside quotes) ([read more](https://meta.discourse.org/t/-/400015/1?silent=true)). - A second [Data Explorer](https://meta.discourse.org/t/32566?silent=true) issue: output appears _double HTML-escaped_ (`Fish & Chips` instead of `Fish & Chips`), suggesting the “bug” lives in rendering rather than SQL ([read more](https://meta.discourse.org/t/-/400018/1?silent=true)). - RSS edge case: `exclude_tag` works on the main RSS feed but appears ignored on **category** RSS feeds; a reproducible `diff` test was provided ([read more](https://meta.discourse.org/t/-/400034/1?silent=true)). - A structured-data/SEO issue was reported: schema output missing the `'text'` field in `mainEntity.suggestedAnswer`; staff confirmed investigation underway ([read more](https://meta.discourse.org/t/-/399974/2?silent=true)). ### #ux - A “strange overlay” of gray dots/lines in the bottom-left turned out to be a sidebar fade gradient artifact; @bryce shared a CSS variable override to disable the effect entirely ([read more](https://meta.discourse.org/t/-/399977/5?silent=true)). - Numeric-tag legacy URLs: a report about **500 errors** on old URLs (impacting crawlers like Googlebot) got a core PR reference indicating the issue should resolve once merged ([read more](https://meta.discourse.org/t/-/399784/12?silent=true)). ### #Site feedback - Meta’s category reshuffle sparked reflection: @mcwumbly asked what kinds of “community building/management” discussion should be encouraged, and whether structure or norms should shift to keep the space focused and useful ([read more](https://meta.discourse.org/t/-/400029/1?silent=true)). ### #contribute:feature - A long-requested i18n nicety landed: **localized emoji aliases** now work for some languages (e.g., typing a French alias can map to the canonical emoji), improving usability on non-English instances ([read more](https://meta.discourse.org/t/-/86641/26?silent=true)). - AI embeddings: a configuration for using Mistral embeddings was shared, but the discussion also emphasized that other higher-scoring models (and multiple zero-retention providers / self-hosting) may be more practical depending on goals ([read more](https://meta.discourse.org/t/-/399854/3?silent=true)). ### #Self-hosting - A new self-hosting question asked how to think about port forwarding when using Cloudflare Tunnels—specifically whether to target `localhost:80`, a LAN IP, or something else ([read more](https://meta.discourse.org/t/-/400059/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot proposed clearer automation scope labels (distinguishing public topics vs all categories vs DMs) after a user confusion report about “All topics” not including PMs by default ([read more](https://meta.discourse.org/t/-/399952/6?silent=true)); and followed up on troubleshooting in the official sidebar toggle component thread ([read more](https://meta.discourse.org/t/-/242802/40?silent=true)). - @chapoi requested better preview media for the newly released “Topic Hover Cards” component so admins can evaluate quickly before installation ([read more](https://meta.discourse.org/t/-/400025/2?silent=true)); and set expectations on Horizon theme compatibility work, noting requests drive prioritization ([read more](https://meta.discourse.org/t/-/360486/79?silent=true)). - @manuel highlighted the official Lucide icon set in the “Alternative icons” guide and noted the topic itself should be updated to reflect newer/official options ([read more](https://meta.discourse.org/t/-/206693/24?silent=true), [read more](https://meta.discourse.org/t/-/206693/28?silent=true)). - @bryce explained the “unexpected overlay” effect as a gradient fade used for sidebar overflow, and provided a CSS variable override to disable it ([read more](https://meta.discourse.org/t/-/399977/5?silent=true)). - @pmusaraj linked to a core PR that addresses numeric-tag legacy URL failures causing crawler-visible 500s, suggesting relief once the fix merges ([read more](https://meta.discourse.org/t/-/399784/12?silent=true)). - @sam confirmed an experimental feature gap in the Suggested Edits plugin (“not implemented yet”) and indicated it would be added ([read more](https://meta.discourse.org/t/-/398691/4?silent=true)). - @davidb acknowledged and escalated the structured-data issue involving `mainEntity.suggestedAnswer` missing a required field, noting an update should follow soon ([read more](https://meta.discourse.org/t/-/399974/2?silent=true)). - @mcwumbly kicked off a meta-level discussion on how to better support _community-building_ conversations after category changes, asking for input on structure and norms ([read more](https://meta.discourse.org/t/-/400029/1?silent=true)). - @Falco merged progress on localized emoji aliases (bringing non-English shortcode parity closer to reality) ([read more](https://meta.discourse.org/t/-/86641/26?silent=true)); and pushed back on ambiguous “Mistral Small” reports while recommending higher-performing translation models and zero-retention inference options ([read more](https://meta.discourse.org/t/-/399939/8?silent=true), [read more](https://meta.discourse.org/t/-/399939/10?silent=true)). * * * Yesterday’s highlight reel: Meta managed to debate _boosts etiquette_, fix _DM scanning scope_, and teach emojis to speak French—all before anyone even finished hovering over the new hover cards. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 7, 2026, 9:02pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/827 "2026-04-07T21:02:05Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **120** new posts across **16** new topics - **Top contributors (posts | likes received):** - @manuel — **5** posts | **30** likes (see: [Meta Branded theme rebuild](https://meta.discourse.org/t/-/400013/1?silent=true), [Lucide Icons component](https://meta.discourse.org/t/-/400133/1?silent=true)) - @sam — **8** posts | **29** likes (see: [Easier access to bookmarks](https://meta.discourse.org/t/-/400085/1?silent=true), [RSS exclude\_tag workaround](https://meta.discourse.org/t/-/400034/2?silent=true)) - @Jonathan5 — **9** posts | **14** likes (see: [bookmark UI follow-ups](https://meta.discourse.org/t/-/400085/5?silent=true)) - @david — **2** posts | **9** likes (see: [deprecation rationale](https://meta.discourse.org/t/-/398894/8?silent=true), [compatibility response](https://meta.discourse.org/t/-/398896/14?silent=true)) - @Moin — **6** posts | **8** likes (see: [bookmark icon behavior discussion](https://meta.discourse.org/t/-/400085/4?silent=true), [translated titles/tags consistency](https://meta.discourse.org/t/-/399596/3?silent=true)) - @Canapin — **4** posts | **6** likes (see: [Meta Branded theme feedback](https://meta.discourse.org/t/-/400013/5?silent=true)) - @RGJ — **3** posts | **5** likes (see: [ESR + staging workflow advice](https://meta.discourse.org/t/-/398896/17?silent=true)) - @chapoi — **8** posts | **5** likes (see: [bookmark UI stance](https://meta.discourse.org/t/-/400085/11?silent=true), [boost feedback routing](https://meta.discourse.org/t/-/400087/5?silent=true)) - @LeoDavidson — **6** posts | **5** likes (see: [plugin maintenance frustration](https://meta.discourse.org/t/-/398896/13?silent=true), [MD Topic List Mobile comment](https://meta.discourse.org/t/-/146341/67?silent=true)) - @soeren-1 — **1** post | **5** likes (see: [Boosts “visual noise” feedback](https://meta.discourse.org/t/-/399835/64?silent=true)) * * * ## Interesting Topics ### #Announcements - @sam shipped **easier access to bookmarked posts within a topic** , adding “jump-to” links from the bottom bookmark control—then the thread quickly turned into a nuanced discussion of _how the topic-level bookmark icon should signal “post(s) bookmarked” on mobile_ ([read more](https://meta.discourse.org/t/-/400085/1?silent=true)). Related: an old feature request finally got its “told-you-so” moment ([read more](https://meta.discourse.org/t/-/86897/6?silent=true)). - The **Boosts experiment** continued to draw “signal vs noise” feedback, including concerns about visual clutter and ideas like reactions-to-boosts—plus a new request suggested collapsing long boost lists on mobile ([read more](https://meta.discourse.org/t/-/399835/64?silent=true); [read more](https://meta.discourse.org/t/-/400087/1?silent=true)). - Image uploads with **automatic grids** got fresh pushback from @Moin, who argued that default grid formatting can _hide information_ and adds extra work for Markdown writers ([read more](https://meta.discourse.org/t/-/394784/5?silent=true)). Related: broader UI polish discussions continue in the theme space ([read more](https://meta.discourse.org/t/-/395331/62?silent=true)). ### #Site feedback - @manuel shared a substantial update: **the Meta Branded theme has been rebuilt from scratch** , showcasing Lucide icons, a theme modifier to restrict color palettes, and a “where customization is heading” narrative—while the replies zeroed in on icon legibility, “replied” glyph choices, small list icons, and layout quirks like an unclickable logo ([read more](https://meta.discourse.org/t/-/400013/1?silent=true)). - A quieter meta-thread asked for more **community-building and migration stories** (especially Facebook → Discourse), pointing to the educational value of real-world moves and what worked ([read more](https://meta.discourse.org/t/-/400029/2?silent=true)). ### #customization:theme component - @manuel published **Discourse Lucide Icons** as a dedicated theme component (with repo + install docs), inviting focused feedback as the icon mapping gets refined over time ([read more](https://meta.discourse.org/t/-/400133/1?silent=true)). Related: this was also cross-referenced from icon guidance discussions ([read more](https://meta.discourse.org/t/-/206693/29?silent=true)). ### #development - Deprecations continued to be a flashpoint: @david explained why dropping legacy `.es6` extensions is about **reducing real-world developer confusion** (tooling, highlighting, linting, codemods), not mere technical constraints ([read more](https://meta.discourse.org/t/-/398894/8?silent=true)). - The companion thread on deprecations escalated into a broader debate about **plugin/theme compatibility expectations** , with @LeoDavidson describing burnout and arguing for a more stable API surface, and others advocating ESR + staging workflows ([read more](https://meta.discourse.org/t/-/398896/13?silent=true)). Related: the same “I may delete/abandon plugins” theme spilled into older plugin topics ([read more](https://meta.discourse.org/t/-/58179/43?silent=true); [read more](https://meta.discourse.org/t/-/57097/18?silent=true); [read more](https://meta.discourse.org/t/-/146341/67?silent=true)). - In a Chinese-language dev thread, @sam pointed to early work on **checking in AI “skills” into core** under `.skills`, framing it as “early days” with more to come ([read more](https://meta.discourse.org/t/-/397330/6?silent=true)). Related: local dev workflows for Discourse AI are still being clarified ([read more](https://meta.discourse.org/t/-/388622/4?silent=true)). ### #bug - A bug report found that **`exclude_tag` doesn’t work in category RSS feeds** , and @sam offered a practical workaround (`/latest.rss?category=...&exclude_tag=...`) while @zogstrip linked a core fix PR ([read more](https://meta.discourse.org/t/-/400034/2?silent=true)). - Upload markup generation can break when filenames begin/end with underscores (e.g. `_test_file_.txt`), producing malformed attachment links; @zogstrip posted an “attempt at fixing this once and for good” ([read more](https://meta.discourse.org/t/-/400079/1?silent=true)). - A self-hosted instance using `mail-receiver` reported **intermittent inbound email processing failures** where messages appear under both received and rejected, alongside observed `ActiveRecord::Deadlocked` logs ([read more](https://meta.discourse.org/t/-/400152/1?silent=true)). ### #ux - A localization UX inconsistency was acknowledged: the **translated categories/tags toggle** wasn’t behaving consistently; @nat shipped an adjustment so the toggle only affects the title and post, aiming for predictable behavior ([read more](https://meta.discourse.org/t/-/399596/2?silent=true)). - Horizon theme users revisited a mobile layout concern: **sticky category heading containers** can dominate small screens; discussion explored whether this should be a theme-level change or left to site CSS tweaks ([read more](https://meta.discourse.org/t/-/387267/12?silent=true)). ### #Support - A report noted that users who **disable translations** sometimes see them re-enabled after weeks; @nat clarified the current approach (local storage for 30 days) and proposed persisting the preference in _user settings_ for cross-device consistency ([read more](https://meta.discourse.org/t/-/400096/2?silent=true)). - Another localization issue described a **`?tl=` anonymous browsing bug** : titles appear in the requested locale at first, but revert inconsistently while scrolling and inside topics—despite the UI showing the chosen language ([read more](https://meta.discourse.org/t/-/400090/1?silent=true)). - Moderation workflow questions came up again: a new topic asked whether there’s an API to **hide a post (not delete it)** so flagged content can be removed from view without resolving the flag ([read more](https://meta.discourse.org/t/-/400135/1?silent=true)). Related: concerns about **auto-resolving flags on deleted posts** leaving sensitive content visible without staff action ([read more](https://meta.discourse.org/t/-/392236/3?silent=true)). - A watched-words support case reported **flags triggered without a highlighted watched word** , possibly tied to email-based replies; staff asked for configuration details (regex vs plain) to narrow it down ([read more](https://meta.discourse.org/t/-/400097/1?silent=true)). ### #community-building Building - A Japanese-language question asked why a forum **doesn’t appear in Discourse Discover** , noting seemingly less-active sites that do show up; replies pointed to “appear in discourse discover” and referenced known criteria discussions ([read more](https://meta.discourse.org/t/-/400115/1?silent=true)). Related: Discover inclusion context ([read more](https://meta.discourse.org/t/-/314909/3?silent=true)). ### #Self-hosting - Cloudflare Tunnel troubleshooting continued: one user solved port-forwarding uncertainty by following the Tunnel guide, while another reported `ERR_CONNECTION_TIMED_OUT` after following the same approach, looking for next diagnostic steps ([read more](https://meta.discourse.org/t/-/400059/2?silent=true); [read more](https://meta.discourse.org/t/-/400126/1?silent=true)). Related: the referenced Tunnel walkthrough ([read more](https://meta.discourse.org/t/-/211297/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @sam - @manuel - @david - @chapoi - @nat - @Jenny - @zogstrip - @awesomerobot - @Falco - @davidb * * * _That’s a wrap: may your bookmarks be one tap away, your RSS feeds properly filtered, and your Lucide hearts eventually find their filled-in “liked” state._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 8, 2026, 9:02pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/828 "2026-04-08T21:02:23Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **Last 24 hours (2026-04-07 → 2026-04-08)** - **New posts:** **113** - **New topics:** **18** **Top users (posts / likes received)** - **@nathank** — 14 posts / 18 likes - **@zogstrip** — 5 posts / 10 likes - **@chapoi** — 5 posts / 9 likes - **@Lilly** — 3 posts / 9 likes - **@itsbhanusharma** — 2 posts / 8 likes - **@RGJ** — 4 posts / 7 likes - **@Moin** — 7 posts / 6 likes - **@pacharanero** — 2 posts / 5 likes - **@merefield** — 2 posts / 5 likes - **@Canapin** — 1 post / 4 likes **Conversation hotspots (by sheer “people care about this” energy):** - Mobile bookmark discoverability and “topic vs post” mental models: [read more](https://meta.discourse.org/t/-/400160/21?silent=true) - Calendar subscriptions polishing (naming, escaping, UX): [read more](https://meta.discourse.org/t/-/400167/7?silent=true), [read more](https://meta.discourse.org/t/-/400166/3?silent=true) - Content localization oddities on first load / refresh: [read more](https://meta.discourse.org/t/-/400209/4?silent=true) - Theme/admin ergonomics (compatibility + sidebar sections): [read more](https://meta.discourse.org/t/-/400248/1?silent=true), [read more](https://meta.discourse.org/t/-/394049/13?silent=true) **More threads with fresh replies (quick links):** - Auto-grids for images (and the desire for an off-switch): [read more](https://meta.discourse.org/t/-/394784/8?silent=true) - Plugin vs core `llms.txt` collisions: [read more](https://meta.discourse.org/t/-/388170/4?silent=true) and native support debate: [read more](https://meta.discourse.org/t/-/383088/7?silent=true) - Lucide icon feedback (and “reply” icon confusion): [read more](https://meta.discourse.org/t/-/400133/4?silent=true) - Meta theme redesign icons legibility: [read more](https://meta.discourse.org/t/-/400013/14?silent=true) - “How minimal is your forum?” configuration inventories: [read more](https://meta.discourse.org/t/-/399941/9?silent=true) - Badge bulk-award workflow UX: [read more](https://meta.discourse.org/t/-/397539/4?silent=true) - Custom Wizard location/map quirk: [read more](https://meta.discourse.org/t/-/73345/941?silent=true) - Incoming email processing edge cases / diagnostics: [read more](https://meta.discourse.org/t/-/400152/4?silent=true) - Translation consistency (“Timer” vs “Zeitschaltuhr”): [read more](https://meta.discourse.org/t/-/47320/118?silent=true) - Discourse MiniMod new settings for TL4 permissions: [read more](https://meta.discourse.org/t/-/400019/3?silent=true) * * * ## Interesting Topics ### #Marketplace - @Mistery went shopping for a theme redesign with a $50 budget, and @itsbhanusharma + @Canapin pushed back that the request is too vague (and the budget unrealistic) unless scope is clarified ([read more](https://meta.discourse.org/t/-/400251/1?silent=true), [read more](https://meta.discourse.org/t/-/400251/5?silent=true)) ### #contribute:feature (#bookmarks) - The “Unable to tell post bookmarks exist in the footer on mobile” thread dug into whether the footer bookmark icon should communicate _post_ bookmarks, _topic_ bookmarks, or both—plus how to keep a consistent action model without hiding useful “jump to bookmark” affordances ([read more](https://meta.discourse.org/t/-/400160/21?silent=true), [read more](https://meta.discourse.org/t/-/400160/28?silent=true)) ### #contribute:feature (#calendar-and-event) - Event creation UX remains a stumbling block: @nathank argued for a _single-click_ entry point to the Create Event flow (and less “markdown cleanup”), with acknowledgement that improvements are underway but without ETA ([read more](https://meta.discourse.org/t/-/400169/1?silent=true), [read more](https://meta.discourse.org/t/-/400169/3?silent=true)) ### #ux (#chat) - Disabling public chat channels currently still leaves a “Channels” tab visible in the chat drawer; the thread explores whether it’s a caching/refresh issue or a genuine UI state mismatch ([read more](https://meta.discourse.org/t/-/400165/1?silent=true), [read more](https://meta.discourse.org/t/-/400165/2?silent=true)) ### #ux (#translation, #onebox) - @discojan spotted that preview link reading-time uses a hard-coded `"mins"` string that can’t be translated (and can even produce awkward plurals), prompting a fix to localize it properly ([read more](https://meta.discourse.org/t/-/400164/1?silent=true), [read more](https://meta.discourse.org/t/-/400164/5?silent=true)) ### #bug (#calendar-and-event, #fixed) - Calendar subscription syncing HTML-escaped ampersands (`&`) into Google Calendar event titles was reported and quickly patched, with confirmation that it’s now resolved ([read more](https://meta.discourse.org/t/-/400166/1?silent=true), [read more](https://meta.discourse.org/t/-/400166/3?silent=true)) ### #bug (#calendar-and-event, #fixed) - Another calendar-subscription papercut: Google Calendar was using the _webcal URL_ as the calendar name (leaking an API key into the visible name field). The thread landed on adding `X-WR-CALNAME` to the ICS output, and it’s confirmed working ([read more](https://meta.discourse.org/t/-/400167/1?silent=true), [read more](https://meta.discourse.org/t/-/400167/7?silent=true)) ### #bug (#content-localization) - A puzzling localization edge case: on initial page load, topic lists can appear mostly translated _except_ for topics originally written in the visitor’s language (e.g., German topics showing in English), and it reproduces even on Meta itself ([read more](https://meta.discourse.org/t/-/400209/1?silent=true), [read more](https://meta.discourse.org/t/-/400209/4?silent=true)) ### #bug - Theme components respect `.discourse-compatibility` at install time, but not when compatibility targets change later—meaning admins may need a remove/reinstall dance to recover, instead of updates rolling back automatically ([read more](https://meta.discourse.org/t/-/400248/1?silent=true)) ### #Support (#email-in) - “Should I cron-restart Discourse daily?” came up in the context of POP3 polling gaps; replies pointed to the POP server error and suggested moving to direct-delivery incoming email and/or splitting mail onto a subdomain ([read more](https://meta.discourse.org/t/-/400176/1?silent=true), [read more](https://meta.discourse.org/t/-/400176/2?silent=true)) ### #Support - A ticket-system setup hit a scary privacy snag: TL0 users could see content in a support workflow that was expected to be private; the discussion immediately pointed at the Private Topics approach and troubleshooting why it might not be behaving as expected ([read more](https://meta.discourse.org/t/-/400252/1?silent=true), [read more](https://meta.discourse.org/t/-/400252/3?silent=true)) ### #Site feedback - Meta’s official plugin topics may have outdated “available on all hosting tiers” callouts now that tiers changed (including the free tier), and there’s also cleanup needed for old category-mention text like `#contribute:bug` that no longer resolves ([read more](https://meta.discourse.org/t/-/400250/1?silent=true), [read more](https://meta.discourse.org/t/-/400250/2?silent=true)) ### #Support - Using Discourse as an academic journal: adding Google Scholar `citation_*` meta tags per “article post” likely needs a custom plugin (not a setting/theme tweak), with pointers toward registering custom field types ([read more](https://meta.discourse.org/t/-/400196/1?silent=true), [read more](https://meta.discourse.org/t/-/400196/2?silent=true)) ### #customization:theme component (#sidebar) - Sidebar Menu Reorder troubleshooting: the component couldn’t find a section, and @Lilly shared a practical Rails-console approach to inspect `SidebarSection` records and restore the default “Community” section title ([read more](https://meta.discourse.org/t/-/394049/12?silent=true), [read more](https://meta.discourse.org/t/-/394049/13?silent=true)) ### #bug - IME users (e.g., Chinese input) can get their composition interrupted by word limits in the Boost composer; a proposed fix delays cutting until after composition ends, with a PR linked for review ([read more](https://meta.discourse.org/t/-/400178/1?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@zogstrip** shipped a string-localization fix path for onebox reading time (“mins”), tying the report to an upstream PR ([read more](https://meta.discourse.org/t/-/400164/5?silent=true)); confirmed a calendar-sync escaping bug would be fixed via PR ([read more](https://meta.discourse.org/t/-/400166/2?silent=true)); and continued tightening PM/flag inbox behavior with a “missing `bump: true`” patch ([read more](https://meta.discourse.org/t/-/393447/3?silent=true)). - **@chapoi** drove the bookmark footer design discussion forward with a consistency-first UI proposal (including distinct icon states and menu behavior) ([read more](https://meta.discourse.org/t/-/400160/28?silent=true)); and confirmed ongoing work to simplify event creation UX (no ETA yet) ([read more](https://meta.discourse.org/t/-/400169/3?silent=true)). - **@sam** argued for an end-user-focused interpretation of bookmarks (topic vs post) and pushed back against making UX harder in the name of nuance ([read more](https://meta.discourse.org/t/-/400160/17?silent=true)); and clarified the intended audience for `dv` tooling as developer/designer oriented rather than hobbyist-friendly ([read more](https://meta.discourse.org/t/-/388622/6?silent=true)). - **@nat** jumped on the content-localization “wrong-language-on-refresh” report by validating relevant settings and investigating the reproduction on Meta ([read more](https://meta.discourse.org/t/-/400209/3?silent=true), [read more](https://meta.discourse.org/t/-/400209/6?silent=true)); and acknowledged [Data Explorer](https://meta.discourse.org/t/32566?silent=true) issues amid planned updates ([read more](https://meta.discourse.org/t/-/400015/3?silent=true), [read more](https://meta.discourse.org/t/-/400018/3?silent=true)). - **@awesomerobot** endorsed the bookmark icon/menu compromise as a good synthesis of feedback ([read more](https://meta.discourse.org/t/-/400160/29?silent=true)); advised that Google Scholar citation meta tags likely require a custom plugin approach ([read more](https://meta.discourse.org/t/-/400196/2?silent=true)); and noted a merged fix to retain category permissions when changing category hierarchy (unless parent restrictions require tightening) ([read more](https://meta.discourse.org/t/-/399976/9?silent=true)). - **@Falco** took the “webcal URL becomes Calendar Name” report from “how would we do that?” to “let’s try it” by adding `X-WR-CALNAME` support and linking the fix PR ([read more](https://meta.discourse.org/t/-/400167/6?silent=true)). - **@david** helped diagnose a self-hosting CORS/CDN problem by narrowing where HighlightJS _should_ be loaded from and asking clarifying questions about S3 vs app CDN setup ([read more](https://meta.discourse.org/t/-/399466/19?silent=true)). * * * Yesterday proved once again that on Meta, the smallest UI details—bookmark glyphs, calendar names, and even a humble ampersand—can trigger the biggest (and most productive) deep-dives. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 10, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/829 "2026-04-10T21:01:37Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 104 - **New topics (last 24h):** 15 **Top users (posts / likes in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @Canapin | 7 | 21 | | @Moin | 8 | 12 | | @Lilly | 10 | 11 | | @RGJ | 5 | 10 | | @merefield | 3 | 8 | | @ducks | 1 | 7 | | @gilles | 8 | 6 | | @Falco | 2 | 5 | | @jordan.vidrine | 2 | 5 | | @awesomerobot | 2 | 4 | A lot of the energy clustered around mobile composer UX and day-to-day admin practicality: the mobile composer overhaul discussion in #ux ([read more](https://meta.discourse.org/t/-/400393/1?silent=true)) cross-pollinated with the “how do I close the tag selector?” question ([read more](https://meta.discourse.org/t/-/400390/1?silent=true)), while “what’s supported?” conversations popped up on legacy Windows access ([read more](https://meta.discourse.org/t/-/400384/1?silent=true)) and Discourse-hosted SSO/OIDC trouble reports ([read more](https://meta.discourse.org/t/-/400392/1?silent=true)). ## Interesting Topics ### #ux - @Canapin kicked off a wide-ranging reality check on **creating/editing posts on mobile in 2026** , arguing the composer is visually and functionally overwhelming on small screens and asking what should be removed from the default experience ([read more](https://meta.discourse.org/t/-/400393/1?silent=true)); the thread also connected to reports of composer freezing ([read more](https://meta.discourse.org/t/-/396436/1?silent=true)) and older mobile UX context ([read more](https://meta.discourse.org/t/-/53632/5?silent=true)). - The “ **close the tag selector on mobile** ” UX papercut got its own focused thread: the selector stays open with no obvious dismissal pattern, and users described awkward workarounds like dismissing the keyboard first ([read more](https://meta.discourse.org/t/-/400390/1?silent=true)). ### #Site feedback - A request to make **feature/bugfix announcement topics include a version number** highlighted the gap between `tests-passed` expectations and the reality of managed hosting + large plugin/theme stacks, where “just update daily” isn’t workable ([read more](https://meta.discourse.org/t/-/400394/1?silent=true)); the discussion referenced a chat pinning announcement as an example ([read more](https://meta.discourse.org/t/-/397571/1?silent=true)). - Ongoing feedback on the **Meta branded theme rebuild** continued, with mobile spacing called out as “too much padding” that reduces usable width on narrow screens ([read more](https://meta.discourse.org/t/-/400013/19?silent=true)); related meta “plugin availability notes” confusion also saw a small improvement (scroll margin) land ([read more](https://meta.discourse.org/t/-/400250/13?silent=true)). ### #Support - “ **What versions of Windows are supported?** ” turned into a practical clarification: Discourse support tracks _supported browsers_ and, as staff emphasized, **no support for OS versions Microsoft no longer supports** —with real-world notes about modern TLS + browser feature requirements and workable Chromium/Firefox forks for stragglers ([read more](https://meta.discourse.org/t/-/400384/1?silent=true)); background context included legacy browser policy ([read more](https://meta.discourse.org/t/-/358131/1?silent=true)) and legacy browser guidance ([read more](https://meta.discourse.org/t/-/210258/5?silent=true)). - A Discourse-hosted (customer) incident: users reported **OIDC login failures on the OpenAI Discourse forum** , with multiple confirmations that “Sorry, there was an error… with oidc” is reproducible ([read more](https://meta.discourse.org/t/-/400392/1?silent=true)). - A nuanced uploads question: **.txt and .yaml attachment “download links” open raw text instead of downloading** , prompting discussion of storage/CDN/S3 headers like `content-disposition` and whether “secure uploads” is the right lever ([read more](https://meta.discourse.org/t/-/400405/1?silent=true)); a potentially related S3 filename/download behavior thread was cited ([read more](https://meta.discourse.org/t/-/152797/1?silent=true)). - A migration/admin-defaults edge case: **staged users inherited “watching” via TL0 group settings** , and the thread explored whether “default categories watching” behaves as admins expect (especially pre-activation) ([read more](https://meta.discourse.org/t/-/400361/1?silent=true)); the setup referenced a Google Groups migration path ([read more](https://meta.discourse.org/t/-/79773/252?silent=true)). - A moderation anomaly: admins saw **the system flag multiple _old_ posts (including PMs) as spam** with confusing review-queue messages (including “Is this post or undefined?”) alongside a worker timeout/backtrace in logs ([read more](https://meta.discourse.org/t/-/400369/1?silent=true)). ### #customization:theme component - A tiny-but-handy new component restores the **composer fullscreen toggle on tablets / larger touch devices** , where it’s normally hidden—aimed at improving #composer ergonomics for bigger screens ([read more](https://meta.discourse.org/t/-/400433/1?silent=true)). - The official **Versatile Banner** component hit an unexpected external dependency snag: its default background image is hosted on Imgur, which is now inaccessible in the UK—making the _out-of-box_ banner appear broken for new installs there ([read more](https://meta.discourse.org/t/-/109133/373?silent=true)). - In **Quote Callouts** , a locale-specific bug appeared _only_ with German translation enabled; a quick fix was proposed and confirmed, and follow-up UX requests asked for icon-only/no-title callouts ([read more](https://meta.discourse.org/t/-/350962/55?silent=true)). ### #Announcements - The ongoing experiment with **Boosts** kept drawing thoughtful community “culture-fit” feedback: admins want strong control (disable/hide low-content UI affordances), and reassurance that disabling doesn’t cause breakage ([read more](https://meta.discourse.org/t/-/399835/75?silent=true)). ### #blog - A delightfully deep infra post explained how “ **Jennifer Aniston and Friends** ” led to **377GB of bloat and ext4 hardlink issues** during backup generation—prompting both laughs and appreciation for more technical postmortems ([read more](https://meta.discourse.org/t/-/400360/1?silent=true)). ### #wordpress - A #wp-discourse feature idea proposed **hiding specific Discourse replies from being pulled into WordPress comments** by applying a Discourse tag (similar in spirit to existing trust-level based filtering) ([read more](https://meta.discourse.org/t/-/400422/1?silent=true)). ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @ducks published the companion discussion for the infra write-up on backup generation, ext4 hardlinks, and how real-world media load can explode disk usage ([read more](https://meta.discourse.org/t/-/400360/1?silent=true)). - @awesomerobot engaged in the mobile composer reality-check thread, acknowledging “Meta is a worst-case scenario” and asking for actionable guidance on what to remove/simplify from the default mobile composer UI ([read more](https://meta.discourse.org/t/-/400393/3?silent=true)); they also followed up on a theme-related composer/draft warning report in a reddit-like theme thread ([read more](https://meta.discourse.org/t/-/269466/125?silent=true)). - @jordan.vidrine weighed in on the mobile composer discussion with both product perspective and feedback-quality guidance—encouraging specifics that can translate into fixes ([read more](https://meta.discourse.org/t/-/400393/6?silent=true))—and continued clarifying intent/controls around Boosts moderation and “fun features” in the experiment thread ([read more](https://meta.discourse.org/t/-/399835/74?silent=true)). - @Falco clarified the practical policy stance on legacy platforms (Discourse support aligning with vendor-supported OSes) while also sharing tested alternatives for older Windows users via modern browser forks ([read more](https://meta.discourse.org/t/-/400384/7?silent=true)) and follow-up testing results ([read more](https://meta.discourse.org/t/-/400384/14?silent=true)). - @supermathie helped troubleshoot the legacy Windows accessibility complaints by hypothesizing TLS negotiation / modern cipher support issues and suggesting concrete diagnostics via SSL Labs’ client test flow ([read more](https://meta.discourse.org/t/-/400384/12?silent=true)). - @derek shipped a small but meaningful usability tweak (scroll margin) in the ongoing “plugin availability notes” discussion, improving how anchored headings land on the page ([read more](https://meta.discourse.org/t/-/400250/13?silent=true)). If yesterday taught us anything, it’s this: keep your hardlinks healthy, your mobile composer buttons tappable, and maybe don’t let Jennifer Aniston anywhere near your backup volume. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 11, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/830 "2026-04-11T21:01:06Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours (2026-04-10 → 2026-04-11), Meta saw **47 new posts** across **8 new topics** (source window reflected in ongoing discussions like the #Support signup outage: [read more](https://meta.discourse.org/t/-/400466/1?silent=true)). **Top posters & most-liked (last 24h):** - @Lilly — **3 posts** , **8 likes** (e.g., mobile UX discussion: [read more](https://meta.discourse.org/t/-/400393/13?silent=true)) - @Moin — **4 posts** , **6 likes** (e.g., solved-label i18n report: [read more](https://meta.discourse.org/t/-/400436/1?silent=true)) - @sam — **1 post** , **5 likes** (OIDC escalation: [read more](https://meta.discourse.org/t/-/400392/5?silent=true)) - @awesomerobot — **1 post** , **4 likes** (confirmed fix path for translation issue: [read more](https://meta.discourse.org/t/-/400436/2?silent=true)) - @pmusaraj — **2 posts** , **3 likes** (signup issue acknowledged + resolved: [read more](https://meta.discourse.org/t/-/400466/3?silent=true), [read more](https://meta.discourse.org/t/-/400466/4?silent=true)) - @NateDhaliwal — **6 posts** , **2 likes** (e.g., “stuck on signup” repro: [read more](https://meta.discourse.org/t/-/400466/2?silent=true)) - @EricGT — **1 post** , **2 likes** (confirmed OIDC working: [read more](https://meta.discourse.org/t/-/400392/9?silent=true)) - @jrgong — **1 post** , **2 likes** (release notes versioning idea: [read more](https://meta.discourse.org/t/-/400394/6?silent=true)) - @featheredtoast — **1 post** , **2 likes** (theme component note on mobile/desktop view changes: [read more](https://meta.discourse.org/t/-/164513/48?silent=true)) - @rasanderson — **2 posts** , **2 likes** (reported + confirmed resolution of new-site signup hang: [read more](https://meta.discourse.org/t/-/400466/1?silent=true), [read more](https://meta.discourse.org/t/-/400466/5?silent=true)) * * * ## Interesting Topics ### #Support - @EricGT reported an OpenAI forum login failure tied to #openid-connect, and @sam escalated it; by the end, multiple folks confirmed it was working again and the topic was marked solved (#fixed) ([read more](https://meta.discourse.org/t/-/400392/1?silent=true), escalation note: [read more](https://meta.discourse.org/t/-/400392/5?silent=true), confirmation: [read more](https://meta.discourse.org/t/-/400392/9?silent=true)). - New-site signups on the Free plan were hanging at “Almost there…”, with @NateDhaliwal reproducing and @pmusaraj confirming a backend issue before reporting it resolved (#free-plan) ([read more](https://meta.discourse.org/t/-/400466/1?silent=true), repro: [read more](https://meta.discourse.org/t/-/400466/2?silent=true), fix update: [read more](https://meta.discourse.org/t/-/400466/4?silent=true)). - A request to **exclude staged users from “Watching” email behavior** raised concerns that staged accounts can’t unsubscribe—prompting discussion of intended staged-user notification semantics (#staged-users) ([read more](https://meta.discourse.org/t/-/400361/1?silent=true), latest concern: [read more](https://meta.discourse.org/t/-/400361/3?silent=true)). - A self-hosted instance hit sluggishness and rebuild trouble after an upgrade, with logs pointing at a deprecated plugin; @Falco advised removing `discourse-question-answer` (#unsupported-install) ([read more](https://meta.discourse.org/t/-/400446/1?silent=true), team guidance: [read more](https://meta.discourse.org/t/-/400446/2?silent=true)). ### #ux - A broader “2026 mobile composing/editing experience” thread continued, with @Lilly highlighting how removing legacy `/mobile` and `/desktop` view paths improved real-world theme/dev workflows (#composer #mobile) ([read more](https://meta.discourse.org/t/-/400393/1?silent=true), @Lilly’s note: [read more](https://meta.discourse.org/t/-/400393/13?silent=true), related reference: [read more](https://meta.discourse.org/t/-/384280/1?silent=true)). - @NateDhaliwal suggested the expand/collapse arrow for the accepted-answer excerpt in the OP could be misleading, and @Moin compared its placement to quote controls—raising a “do we move it or keep consistency?” UI question (#solved) ([read more](https://meta.discourse.org/t/-/400444/1?silent=true), quote UI comparison: [read more](https://meta.discourse.org/t/-/400444/2?silent=true)). - A German i18n report flagged “Solved” as non-translatable in the solved UI; @awesomerobot acknowledged and pointed toward a fix (#solved #fixed) ([read more](https://meta.discourse.org/t/-/400436/1?silent=true), response: [read more](https://meta.discourse.org/t/-/400436/2?silent=true)). - Another i18n snag: the Wrap modal shows “Key” and “Value” strings that appear not to be translated, with code pointers supplied for investigation ([read more](https://meta.discourse.org/t/-/400478/1?silent=true)). ### #bug - @NateDhaliwal reported Meta sometimes opening on topics from 1–2 days ago and only later revealing a “new/unread topics” bar—suggesting a potential “stale landing” or caching/state issue ([read more](https://meta.discourse.org/t/-/400459/1?silent=true)). - A suspected cache-key issue: `/favicon/proxied` appears to return the same image for different target URLs, with clear reproduction steps provided ([read more](https://meta.discourse.org/t/-/400464/1?silent=true)). - Pasting HTML tables into the rich editor: when a table has no ``, the top row’s first `TD` may be converted into a `TH`, indicating a clipboard-to-Markdown/HTML normalization edge case ([read more](https://meta.discourse.org/t/-/400440/1?silent=true)). - A French-language bug thread about category advanced settings continued, with a suggestion to better tag it if it’s really a #calendar-and-event issue (#categories) ([read more](https://meta.discourse.org/t/-/400288/1?silent=true), tagging suggestion: [read more](https://meta.discourse.org/t/-/400288/12?silent=true)). ### #Site feedback - A request that feature/bugfix announcement topics include a version number evolved into a workflow idea: link each release-note item back to its Meta announcement so versioning context is easier to apply ([read more](https://meta.discourse.org/t/-/400394/1?silent=true), expansion: [read more](https://meta.discourse.org/t/-/400394/6?silent=true)). - A meta-level conversation about encouraging healthier community-building and moving away from toxic environments continued, referencing “institutional arrangements” and community governance as essential complements to tooling ([read more](https://meta.discourse.org/t/-/400029/1?silent=true), latest reflection: [read more](https://meta.discourse.org/t/-/400029/3?silent=true)). ### #Announcements - The “Modernizing the Foundation theme” effort got a status update from @jordan.vidrine: smaller pieces may merge into core first, while larger UI aspects stay feature-flagged temporarily—followed by concrete pain points like button styling mismatches across old/new foundations ([read more](https://meta.discourse.org/t/-/395331/1?silent=true), update: [read more](https://meta.discourse.org/t/-/395331/65?silent=true), follow-up: [read more](https://meta.discourse.org/t/-/395331/66?silent=true)). - Calendar subscription URLs discussion continued, with guidance that a Theme Component button is the robust path (Wizard optional/fragile), and interest building for a proper TC topic (#calendar-and-event #bookmarks) ([read more](https://meta.discourse.org/t/-/398902/1?silent=true), guidance: [read more](https://meta.discourse.org/t/-/398902/22?silent=true)). ### #wordpress - A [WP Discourse](https://github.com/discourse/wp-discourse) feature request explored filtering out comments by some signal akin to tags, but noted tags are topic-level; the conversation circled around needing a post-level exclusion signal analogous to “Only Import Moderator-Liked” (#wp-discourse) ([read more](https://meta.discourse.org/t/-/400422/1?silent=true), response: [read more](https://meta.discourse.org/t/-/400422/2?silent=true)). ### #customization:plugin - The #ai llms.txt generator plugin thread discussed an upcoming plugin update to prevent core from overriding plugin behavior—very much in the spirit of plugins “fine-tuning” baseline behavior ([read more](https://meta.discourse.org/t/-/388170/1?silent=true), update: [read more](https://meta.discourse.org/t/-/388170/6?silent=true)). - The long-running **Discourse Solved** plugin topic got a small but practical request: refresh the OP screenshots because they’re now outdated (#official #solved #included-in-core) ([read more](https://meta.discourse.org/t/-/30155/1?silent=true), screenshot request: [read more](https://meta.discourse.org/t/-/30155/400?silent=true)). ### #customization:theme component - The “left-side hamburger menu on mobile” component discussion resurfaced: the move away from separate mobile/desktop views broke assumptions, and a CSS positioning/grid approach was suggested as a pragmatic path forward (#mobile) ([read more](https://meta.discourse.org/t/-/164513/1?silent=true), maintainer note: [read more](https://meta.discourse.org/t/-/164513/48?silent=true)). ### #contribute:feature - A “category moderators can create subcategories” request got a fresh ping asking whether it shipped and whether sponsoring features is possible (#category-moderators) ([read more](https://meta.discourse.org/t/-/280203/1?silent=true), latest query: [read more](https://meta.discourse.org/t/-/280203/12?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @sam stepped in on the OpenAI OIDC login outage, explicitly escalating to relevant contacts and helping unblock users once the issue cleared (#Support, #openid-connect) ([read more](https://meta.discourse.org/t/-/400392/5?silent=true), resolution confirmed later: [read more](https://meta.discourse.org/t/-/400392/9?silent=true)). - @awesomerobot acknowledged the untranslated “Solved” string report and pointed to an imminent fix (#ux, #solved) ([read more](https://meta.discourse.org/t/-/400436/2?silent=true)). - @pmusaraj responded quickly to the Free-plan new-site signup hang: first confirming technical issues, then posting that signups were resolved (#Support, #free-plan) ([read more](https://meta.discourse.org/t/-/400466/3?silent=true), resolution post: [read more](https://meta.discourse.org/t/-/400466/4?silent=true)). - @featheredtoast provided context on why a mobile theme component broke after the mobile/desktop view refactor and suggested pragmatic CSS adjustments (#customization:theme component, #mobile) ([read more](https://meta.discourse.org/t/-/164513/48?silent=true)). - @Falco diagnosed a self-host upgrade/rebuild pain point as stemming from a deprecated plugin and advised removing it (#Support, #unsupported-install) ([read more](https://meta.discourse.org/t/-/400446/2?silent=true)). - @jordan.vidrine posted a progress update on the Foundation modernization plan, explaining what may land in core first and what remains behind a feature flag temporarily (#Announcements) ([read more](https://meta.discourse.org/t/-/395331/65?silent=true)). * * * _That’s a wrap for today—may your signups never get stuck on “Almost there…”, your OIDC logins stay green, and every last “Solved” label be perfectly translated._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 12, 2026, 9:03pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/831 "2026-04-12T21:03:21Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 43** - **New topics (last 24h): 4** — including: - “Highlight to Search” in **#customization:theme component** (#search) — [read more](https://meta.discourse.org/t/-/400492/1?silent=true) - “Logic flip in post translation button tooltips?” in **#ux** (#content-localization) — [read more](https://meta.discourse.org/t/-/400481/1?silent=true) - “New topic title input (#reply-title) remains LTR in RTL sites — fix still not effective (2026)” in **#bug** (#composer #rtl #content-localization) — [read more](https://meta.discourse.org/t/-/400490/1?silent=true) - “无法登录什么原因” in **#Support** (#discourse-id) — [read more](https://meta.discourse.org/t/-/400487/1?silent=true) **Top users (posts / likes in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @Arkshine | 5 | 10 | | @NateDhaliwal | 3 | 9 | | @Moin | 4 | 3 | | @Canapin | 2 | 3 | | @gilles | 5 | 2 | | @RGJ | 1 | 2 | | @ars18 | 1 | 2 | | @merefield | 1 | 1 | | @haydenjames | 1 | 1 | | @renato | 1 | 1 | **Team check-in (posts / likes in the last 24h)** - @renato — 1 post / 1 like ([composer investigation](https://meta.discourse.org/t/-/263017/22?silent=true)) - @mcwumbly — 1 post / 0 likes ([Horizon + Kanban guidance](https://meta.discourse.org/t/-/118164/298?silent=true)) * * * ## Interesting Topics ### #customization:theme component - @NateDhaliwal published **“Highlight to Search”** (#search), a component that lets users highlight text inside posts and kick off a search (site search or external like Google); @Lilly suggested polishing the repo docs, and @Moin shared the practical pain of not knowing the final Meta topic URL until approval. [read more](https://meta.discourse.org/t/-/400492/1?silent=true) (see also the install how-to: [read more](https://meta.discourse.org/t/-/63682/1?silent=true), and the themes beginner guide: [read more](https://meta.discourse.org/t/-/91966/1?silent=true)) - In **“Banner Featured Links”** , @gilles asked how to show the banner buttons beyond the homepage (e.g., on category pages), and @Arkshine walked through using the right _plugin outlet_ (notably `above-main-container`) and checking settings like URL matching. [read more](https://meta.discourse.org/t/-/327497/31?silent=true) (plus the outlet-discovery tip via Developer Toolbar: [read more](https://meta.discourse.org/t/-/346215/1?silent=true)) - The long-running **“Kanban Board”** component thread got a Horizon-compatibility ping: @mcwumbly expected it to work well with Horizon, while @Lew_Grothe reported it not rendering on their dev instance; @Arkshine suggested confirming theme attachment and checking browser console errors. [read more](https://meta.discourse.org/t/-/118164/298?silent=true) (follow-up troubleshooting: [read more](https://meta.discourse.org/t/-/118164/300?silent=true)) - In **“User Field Prompt”** , @Moin proposed updating the screenshots/docs because the UI now displays the field title/description _below_ the input, which can surprise admins expecting the older preferences layout. [read more](https://meta.discourse.org/t/-/185214/25?silent=true) - Over in **“Discourse Lucide Icons”** , @cuo_wu reported that `calendar-heart` wouldn’t render even after adding it to the custom SVG sprite set, and shared screenshots of the missing icon behavior. [read more](https://meta.discourse.org/t/-/400133/5?silent=true) * * * ### #customization:theme - In **“FKB Pro - Social theme”** , @RGJ found a CSS selector that unintentionally affects **private messages** when tags are involved (and the sidebar is hidden), collapsing the available width; they suggested adding a missing `:not(.archetype-private_message)` to avoid PM layouts being caught by topic-list styles. [read more](https://meta.discourse.org/t/-/234323/488?silent=true) * * * ### #customization:plugin - The **“Topic Ratings Plugin”** thread saw a practical fix explanation: @n1bff confirmed things working again, and @Arkshine explained their merged PR removes lingering widget references so the plugin works with modern Discourse. [read more](https://meta.discourse.org/t/-/39578/446?silent=true) * * * ### #ux - In **“Logic flip in post translation button tooltips?”** (#content-localization), @Canapin pointed out the tooltip strings appear reversed (original vs translated state), while @Moin noted it’s a known bug tied to the newer preference option—sometimes fixed by a refresh, sometimes the toggle fails until refresh. [read more](https://meta.discourse.org/t/-/400481/1?silent=true) - In **“Closed events don’t display in the upcoming-events calendar - I think they should!”** (#calendar-and-event), @Ethsim2 argued that “Close event” shouldn’t effectively hide it from `/upcoming-events`, noting they previously had to “break bbcode” to remove events and asking for either restored visibility or a separate “Delete event” option. [read more](https://meta.discourse.org/t/-/400192/2?silent=true) - The **notification UX** debate continued in **“Make notification count persist after opening avatar menu”** (#notifications): @sixty4bit described how clearing the unread count on menu-open causes missed PM follow-ups in customer-service workflows (and adds extra clicks vs. scanning the header count). [read more](https://meta.discourse.org/t/-/299882/14?silent=true) - In **“How can I enter special formatting like [wrap], in the text field of automations?”** (#automation), @Moin confirmed a workable approach: sticking to markdown mode for wraps (and avoiding copy/paste quirks), even showing a helper component workflow to generate wrap snippets reliably. [read more](https://meta.discourse.org/t/-/391347/11?silent=true) * * * ### #contribute:feature - The feature request **“Allow category moderators to create subcategories”** resurfaced with a pragmatic path: @NateDhaliwal suggested Marketplace hiring or Discourse enterprise services, while @ars18 pointed to **Discourse MiniMod** as a possible stepping stone; @alanr plans to start there but still wants true subcategory creation rights for category mods. [read more](https://meta.discourse.org/t/-/280203/13?silent=true) (MiniMod reference: [read more](https://meta.discourse.org/t/-/400019/1?silent=true)) - In **“Returning bumping after editing last post”** , @haydenjames pushed back on the change where editing no longer bumps topics, arguing it undermines moderation advice (“edit instead of double-posting”) and makes it harder to resurface improved solutions later. [read more](https://meta.discourse.org/t/-/390033/12?silent=true) * * * ### #bug - The composer thread **“Cursor jumping around in composer / editor text box”** got renewed scrutiny: @Thomas_Rother shared a screencast of “jumping effects,” while @renato noted the video appears to show the markdown composer (rendered preview mode) rather than ProseMirror, and asked for reproduction confirmation across instances like Meta or [try.discourse.org](http://try.discourse.org). [read more](https://meta.discourse.org/t/-/263017/21?silent=true) (team reply: [read more](https://meta.discourse.org/t/-/263017/22?silent=true)) - RTL pain point: @Nima1 reported **the new topic title input stays LTR on RTL sites** , even with RTL settings and mixed-direction support enabled; they detailed steps and CSS attempts, noting cursor/selection feel wrong until RTL characters are typed (and even then inconsistently). [read more](https://meta.discourse.org/t/-/400490/1?silent=true) * * * ### #Support - In the Chinese-language support topic **“无法登录什么原因”** (#discourse-id), @Lxk520 hit a “redirect uri malformed” Discourse ID login error; @NateDhaliwal linked prior troubleshooting (regenerate credentials, and the known domain-change fix), and the OP confirmed progress but reported a new login prompt afterward. [read more](https://meta.discourse.org/t/-/400487/2?silent=true) (related: domain-change fix thread [read more](https://meta.discourse.org/t/-/386102/1?silent=true), and the earlier troubleshooting thread referenced [read more](https://meta.discourse.org/t/-/394238/1?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @mcwumbly weighed in on Horizon compatibility for the **Kanban Board** theme component, suggesting it _should_ work well with Horizon—useful context as others test and debug their setups. [read more](https://meta.discourse.org/t/-/118164/298?silent=true) - @renato helped triage the **composer cursor-jumping** report by spotting that the screencast appeared to show the markdown editor (with preview) rather than ProseMirror, and asked for broader reproduction across instances to narrow down root cause. [read more](https://meta.discourse.org/t/-/263017/22?silent=true) * * * Yesterday, Meta had everything: text you can _highlight-to-search_, topics you can’t bump by editing, and a cursor determined to go on its own little adventure—never a dull scroll. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 13, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/832 "2026-04-13T21:01:29Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, Meta kept busy with **78 new posts** across **6 new topics** , with discussion spread across ongoing threads like [Boosts testing](https://meta.discourse.org/t/-/399835/78?silent=true), [RTL composer behavior](https://meta.discourse.org/t/-/400490/2?silent=true), and a fresh round of theme-component releases for events and drafts ([read more](https://meta.discourse.org/t/-/400503/1?silent=true), [read more](https://meta.discourse.org/t/-/400557/1?silent=true)). **Top users (posts / likes in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @nathank | 13 | 18 | | @NateDhaliwal | 10 | 8 | | @Moin | 7 | 8 | | @manuel | 1 | 6 | | @putty | 4 | 6 | | @sam | 2 | 3 | | @Canapin | 2 | 2 | | @david | 1 | 2 | | @awesomerobot | 1 | 2 | | @Falco | 1 | 2 | A few threads drove a lot of the “what’s new / what’s broken / what’s next” energy—especially UX nits like the share modal layout ([read more](https://meta.discourse.org/t/-/400502/1?silent=true)) and deeper technical concerns like deprecated theme template extensions and upgrade fallout ([read more](https://meta.discourse.org/t/-/398896/19?silent=true), [read more](https://meta.discourse.org/t/-/400558/3?silent=true)). * * * ## Interesting Topics ### #customization:theme-component - @putty shipped a new component to make **Shared Draft** the default “New Topic” action—relabeling the button and preloading the composer with a shared-draft workflow ([read more](https://meta.discourse.org/t/-/400557/1?silent=true)). - @nathank published **Upcoming Events Extra Buttons** , adding configurable “Subscribe” and optional “Create event” buttons to `/upcoming-events` for communities using events heavily (tagged #calendar-and-event) ([read more](https://meta.discourse.org/t/-/400503/1?silent=true)). - “Highlight to Search” support continued, with @NateDhaliwal clarifying how to swap the external search engine by adjusting the `search_url` (e.g., Bing) and untangling confusion about what Discourse core vs the component controls ([read more](https://meta.discourse.org/t/-/400492/8?silent=true)). Related components and approaches were also pointed out for alternate engines like Baidu and DuckDuckGo ([read more](https://meta.discourse.org/t/-/170283/1?silent=true), [read more](https://meta.discourse.org/t/-/83902/1?silent=true)). - The **Kanban Board** component got real-world “works with Horizon” confirmation, plus practical CSS tweaks to widen the board and adjust column width for tighter layouts ([read more](https://meta.discourse.org/t/-/118164/301?silent=true)). - Lucide icon usage came up again: @nathank noted gaps vs Font Awesome tooling, and @Moin linked a core commit that helps explain the current icon baseline and expectations for support/documentation ([read more](https://meta.discourse.org/t/-/400133/8?silent=true)). - The long-running **Video Upload to YouTube and Vimeo** component got a gentle ping from @putty, and @Arkshine replied with progress—Vimeo already working locally, and an intent to get the full stack working soon (tagged #broken) ([read more](https://meta.discourse.org/t/-/170079/58?silent=true)). - The official **Mermaid** theme component saw a quick “what version is supported?” question, with the repository’s `about.json` cited as the source of truth ([read more](https://meta.discourse.org/t/-/218242/52?silent=true)). ### #bug - A subtle but important issue: after using translation features, a post’s “cooked” output broke in one locale due to malformed table pipes. @Moin explained the underlying Markdown table formatting sensitivity and confirmed the fix restored translations cleanly (tags #ai and #dynaloc) ([read more](https://meta.discourse.org/t/-/400509/2?silent=true)). - A navigation/session oddity: the “opening forum” view sometimes jumped back to **days-old topics** instead of the most recent, with hypotheses ranging from tab staleness to login state caching and unread banner behavior (and a possible connection to the unread-topics banner not updating) ([read more](https://meta.discourse.org/t/-/400459/2?silent=true), [read more](https://meta.discourse.org/t/-/303928/1?silent=true)). - RTL usability continues to get careful attention: @sam explained why the composer title field direction problem isn’t solvable with CSS alone and proposed a markup-level strategy (default RTL when empty, then switch to `auto` once typing begins) via a core PR (tags #rtl and #composer) ([read more](https://meta.discourse.org/t/-/400490/2?silent=true)). ### #ux - On mobile, @Canapin suggested a small but high-impact change: put the **Copy** button on the same line as the URL input in the share modal to improve reachability and reduce awkward tapping (tagged #mobile) ([read more](https://meta.discourse.org/t/-/400502/1?silent=true)). - German UI translation friction: “Key” and “Value” in the wrap modal weren’t translatable, and @awesomerobot flagged it as an oversight with a fix already queued in core via PR ([read more](https://meta.discourse.org/t/-/400478/2?silent=true)). ### #Self-hosting - A painful upgrade failure (“bouncing dots” / stuck boot) was diagnosed quickly: @Falco identified the broken `discourse-multilingual` plugin as the culprit and advised removing it before rebuilding; the OP confirmed the instance recovered immediately ([read more](https://meta.discourse.org/t/-/400558/3?silent=true)). For background context, the plugin’s status has been tracked for a while ([read more](https://meta.discourse.org/t/-/142740/1?silent=true)). ### #development - Deprecation pressure remains real: the ongoing move away from `.hbs` in themes/plugins sparked discussion of what a healthy deprecation and migration policy looks like in a fast-moving frontend ecosystem. @manuel argued for “mature API platform” style expectations—clear versioning, notices, and migration windows—rather than comparing to a fully vertically-integrated stack ([read more](https://meta.discourse.org/t/-/398896/19?silent=true)). ### #Support - A new console-error report landed: hashtag autocomplete triggered `generateIconHTML`/datasource errors under different safe-mode configurations, and @Moin asked for help narrowing down whether this is core behavior, a plugin interaction, or an autocomplete edge case (tag #hashtag-autocomplete) ([read more](https://meta.discourse.org/t/-/400570/1?silent=true)). - Discourse ID login trouble (topic in Chinese) continued: admins could log into the backend, but other users could not; @NateDhaliwal walked through checking relevant auth settings like `enable discourse id` and local email logins, while also probing whether SSO was in play ([read more](https://meta.discourse.org/t/-/400487/6?silent=true)). ### #Announcements - The “Testing Boosts on Meta” experiment stayed lively: @nathank described “boosts” as potentially adding friction compared to reactions—both in posting and reading—while acknowledging there _may_ be a niche if implemented extremely slickly (e.g., extending a reaction or replacing ultra-short replies) ([read more](https://meta.discourse.org/t/-/399835/78?silent=true)). The thread also got a moderation-tone nudge from @jordan.vidrine urging the discussion to stay constructive and on-topic ([read more](https://meta.discourse.org/t/-/399835/79?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @manuel weighed in on the `.hbs` deprecation conversation, emphasizing that Discourse lives in a shifting ecosystem (especially frontend dependencies) and that the right model is _explicit versioning + deprecation windows_, not “never break anything” expectations ([read more](https://meta.discourse.org/t/-/398896/19?silent=true)). - @sam pushed RTL composer improvements forward, explaining the `dir`/`auto` behavior and proposing a markup change to make empty title inputs behave correctly for RTL sites—plus coordinating review/merge on the fix ([read more](https://meta.discourse.org/t/-/400490/2?silent=true)). - @awesomerobot confirmed an i18n gap (“Key”/“Value” in wrap modal) and linked the core PR that will make these strings translatable ([read more](https://meta.discourse.org/t/-/400478/2?silent=true)). - @Falco solved a self-hosting post-upgrade outage by pointing to the broken multilingual plugin and advising removal + rebuild; the OP reported immediate recovery ([read more](https://meta.discourse.org/t/-/400558/3?silent=true)). - @david responded to plugin-maintenance concerns for Telegram notifications by shipping a commit that resolves the `.hbs` deprecation warning—turning a “is this maintained?” question into forward motion ([read more](https://meta.discourse.org/t/-/60483/206?silent=true)). - @jordan.vidrine helped steer the Boosts experiment thread back toward productive software discussion, while expressing optimism about offering communities more expressive options over time ([read more](https://meta.discourse.org/t/-/399835/79?silent=true)). * * * _Sign-off:_ If the day ever feels a little chaotic, just remember: between Boost debates, RTL fixes, and event-button upgrades, Meta managed to keep the “bouncing dots” mostly on the loading screen where they belong ([read more](https://meta.discourse.org/t/-/400558/3?silent=true)). ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 15, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/833 "2026-04-15T21:01:43Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **81** new posts, **13** new topics (see today’s threads like [Discourse Comments embed feedback](https://meta.discourse.org/t/-/400721/1?silent=true) and [Backups page UI glitch](https://meta.discourse.org/t/-/400730/1?silent=true)) - **Top posters & likability (last 24h):** | User | Posts | Likes | | --- | --- | --- | | @Falco | 12 | 21 | | @Moin | 9 | 7 | | @nat | 6 | 6 | | @haydenjames | 3 | 7 | | @Thiago_Mobilon | 3 | 7 | | @pmusaraj | 2 | 4 | | @Lilly | 1 | 6 | | @simonk | 1 | 5 | | @awesomerobot | 1 | 3 | | @RGJ | 1 | 3 | * * * ## Interesting Topics ### #contribute:feature - **Discourse Comments embed: real-world scaling notes from a high-traffic site (#embedding)** — @Thiago_Mobilon shared performance, analytics, and UX hurdles seen after embedding the “full app”, including server load spikes and tracking duplication; @Falco dug into caching headers and outlined upcoming improvements (lazy-load, dynamic height, and embed-specific optimizations) in the same thread [read more](https://meta.discourse.org/t/-/400721/1?silent=true). - **Make review queue help links truly customizable (#review-queue)** — @Lilly requested that setting a “Moderator guide topic” link should _replace_ the built-in help link list (instead of stacking another link on top), to avoid staff confusion and dependency on possibly outdated Meta docs [read more](https://meta.discourse.org/t/-/400700/1?silent=true). - **Push notifications: keep other device subscriptions when logging off (#push-notifications)** — a long-running request to avoid wiping _all_ push subscriptions on logout got marked done by @Falco, pointing to an implementation in core [read more](https://meta.discourse.org/t/-/134038/7?silent=true). - **Moderation controls: approvals tied to group membership (and related category moderation work)** — @tgxworld posted an update that tying approvals requirements to groups has landed, and also cross-referenced the related category-moderation work that shipped in the same change set ([approvals thread](https://meta.discourse.org/t/-/148540/4?silent=true), related: [category moderation & trust levels](https://meta.discourse.org/t/-/258867/3?silent=true)). * * * ### #Support - **“Replying to an old topic” warning removed—admins want the UX back (or at least customizable messaging)** — @haydenjames noticed the classic “old topic” notice is no longer appearing and argued that _guidance_ beats discouragement; @simonk linked to the rationale in the broader necroposting discussion (and values shift away from discouraging revivals) ([current report](https://meta.discourse.org/t/-/400688/1?silent=true), background: [warn users about old posts](https://meta.discourse.org/t/-/126798/1?silent=true), rationale: [necroposting safeguard discussion](https://meta.discourse.org/t/-/389992/14?silent=true), related gripe: [bumping after editing](https://meta.discourse.org/t/-/390033/12?silent=true)). - **Composer link tool double-encoding? (SOLVED by “update first”)** — a report that encoded URLs were being altered when inserted via the link tool ended with inability to reproduce on newer versions and a strong nudge to upgrade off 3.5.x; the OP later confirmed tests on try.discourse were fine ([issue report](https://meta.discourse.org/t/-/400694/1?silent=true), solution context: [version/support guidance](https://meta.discourse.org/t/-/400694/7?silent=true)). - **Remote images suddenly being downloaded even with exceptions configured** — @AlexVoss reported that hosted instances started rewriting remote image URLs to locally-downloaded copies “as of today,” and shared their `disabled image download domains` configuration for troubleshooting [read more](https://meta.discourse.org/t/-/400697/1?silent=true). - **Core translations: odd line-wrapping/overflow on Debian/Firefox** — a moderator on Debian (Firefox ESR) saw translated text layout overflow into the right column before wrapping; the report includes a screenshot and environment details for repro [read more](https://meta.discourse.org/t/-/400723/1?silent=true). - **AI translation/language detection: German posts not recognized, manual title/content translation quirks** — @putty reported a German post not translating; @Falco explained why mixed-language titles can skew detection and confirmed manual language selection forces language, while later replies suggest a regression affecting manual edits ([problem statement](https://meta.discourse.org/t/-/400708/1?silent=true), @Falco’s explanation]([Post not being detected as German - #2 by Falco](https://meta.discourse.org/t/-/400708/2?silent=true)), related localization tracking: [tooltips logic flip](https://meta.discourse.org/t/-/400481/3?silent=true), and linked bug context: [anonymous `?tl=` localization issue](https://meta.discourse.org/t/-/400090/4?silent=true)). - **Docs plugin restore edge case: indexing breaks when calendar is enabled (with fix in-flight)** — @nat acknowledged the restore/index issue and later linked a fix after identifying a calendar side-effect that prevented reindexing ([ack](https://meta.discourse.org/t/-/392225/13?silent=true), diagnosis question]([Documentation Plugin - Index Topic not working after Restore - #14 by nat](https://meta.discourse.org/t/-/392225/14?silent=true)), fix reference]([Documentation Plugin - Index Topic not working after Restore - #15 by nat](https://meta.discourse.org/t/-/392225/15?silent=true))). - **Official livestream plugin: “Going” to an event but chat still inaccessible** — @nat adjusted a setting to allow Trust Level 0 and noted the “everyone” group edge case that likely tripped permissions in the plugin flow [read more](https://meta.discourse.org/t/-/341335/48?silent=true). * * * ### #bug - **Tag permission hints are inconsistent in the composer (#composer #tags)** — @Moin demonstrated cases where autocomplete alternately claims a tag is allowed vs not allowed in the same category; @zogstrip replied that the feature needed to be “smarter” about limits and pointed to a fix [read more](https://meta.discourse.org/t/-/400696/1?silent=true) (fix note: [follow-up](https://meta.discourse.org/t/-/400696/4?silent=true)). - **Calendar/event plugin: chat link vanished from the post event widget after Rollup** — @klappradla traced a regression to build-system changes and offered a PR; @david encouraged posting the PR link and confirmed direction [read more](https://meta.discourse.org/t/-/400691/1?silent=true) (team response: [@david](https://meta.discourse.org/t/-/400691/2?silent=true)). - **Category settings saved by _non-official_ plugins fail to persist (no “unsaved changes” prompt)** — @RGJ reported that after 2026.4.0-latest, multiple plugins can’t save category-level settings; the report references breakage seen in the Custom Wizard thread as well ([bug report](https://meta.discourse.org/t/-/400699/1?silent=true), related plugin thread: [Custom Wizard Plugin](https://meta.discourse.org/t/-/73345/942?silent=true)). - **Real-time topic updates broken: new replies don’t appear without refresh** — @Ethsim2 reported what looks like a regression in live updates (MessageBus/WebSocket/polling), with clear repro steps across sessions and no customizations installed [read more](https://meta.discourse.org/t/-/400710/1?silent=true). (Possibly related “UI only updates after navigating away/back” symptom: [Backups page arrow glitch](https://meta.discourse.org/t/-/400730/1?silent=true)). * * * > “…our reasoning was that the goal of preventing necro-posting didn’t align with our values…” — linked from the old-topic warning discussion ([context](https://meta.discourse.org/t/-/389992/14?silent=true), surfaced via [this support thread](https://meta.discourse.org/t/-/400688/2?silent=true)) Extra threads that also saw movement (for deeper browsing): [IP info not updating in reviewables](https://meta.discourse.org/t/-/391230/3?silent=true), [Wrong join date/post count in reviewable insights](https://meta.discourse.org/t/-/391232/6?silent=true), [Hashtag autocomplete console error](https://meta.discourse.org/t/-/400570/4?silent=true), [ProxyTracer plugin support](https://meta.discourse.org/t/-/399958/9?silent=true), [Serve from a subfolder logging oddity](https://meta.discourse.org/t/-/30507/129?silent=true), [Show latest reply hint performance discussion](https://meta.discourse.org/t/-/273018/5?silent=true), [WeChat mini-program integration follow-up](https://meta.discourse.org/t/-/312085/5?silent=true), and [Nested replies testing continues](https://meta.discourse.org/t/-/398759/81?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@Falco** stayed deep in the Discourse Comments embed feedback loop—responding on caching headers, analytics-in-iframe concerns, polling behavior, and shipping a series of improvements discussed in-thread ([embed feedback main post](https://meta.discourse.org/t/-/400721/1?silent=true), team replies: [cache headers](https://meta.discourse.org/t/-/400721/3?silent=true), [analytics question](https://meta.discourse.org/t/-/400721/4?silent=true), [embed requests/AI credit checks](https://meta.discourse.org/t/-/400721/5?silent=true), [dynamic height note](https://meta.discourse.org/t/-/400721/6?silent=true), [native lazy-load support](https://meta.discourse.org/t/-/400721/10?silent=true), plus language detection guidance in [German detection thread](https://meta.discourse.org/t/-/400708/2?silent=true), and push-subscription behavior in [push subscriptions topic](https://meta.discourse.org/t/-/134038/7?silent=true)). - **@nat** unblocked chat access for livestream events by adjusting permissions and documenting the “everyone group” gotcha ([livestream fix](https://meta.discourse.org/t/-/341335/48?silent=true)); also investigated and shipped a fix path for a Docs plugin restore/indexing issue linked to calendar behavior ([ack](https://meta.discourse.org/t/-/392225/13?silent=true), [follow-up](https://meta.discourse.org/t/-/392225/15?silent=true)), and confirmed localization bugs are being tracked across threads ([translation tooltip bug note](https://meta.discourse.org/t/-/400481/3?silent=true), [anonymous `?tl=` issue follow-up](https://meta.discourse.org/t/-/400090/4?silent=true)). - **@pmusaraj** confirmed a Google One Tap embed-related issue has a targeted fix in progress and requested clearer problem statements on the WeChat mini-program integration thread ([embed/One Tap reply](https://meta.discourse.org/t/-/400721/2?silent=true), [WeChat thread follow-up](https://meta.discourse.org/t/-/312085/5?silent=true)). - **@awesomerobot** followed up on reviewable UX/data refresh behavior and linked a fix to ensure state resets correctly when navigating between flags ([reviewable IP info thread](https://meta.discourse.org/t/-/391230/3?silent=true)). - **@tgxworld** posted closure/updates that _group-based approvals requirements_ and related moderation controls have landed in core ([approvals tied to group membership](https://meta.discourse.org/t/-/148540/4?silent=true), [category moderation & trust levels](https://meta.discourse.org/t/-/258867/3?silent=true)). - **@zogstrip** acknowledged the tag-autocomplete permission messaging bug and pointed to a fix making limits handling “smarter” ([tag permissions bug](https://meta.discourse.org/t/-/400696/4?silent=true)). - **@martin** clarified how “upcoming changes for site setting defaults” messaging should behave on Stable vs experimental/legacy settings, in the ongoing discussion about automatic grids for images ([announcements thread](https://meta.discourse.org/t/-/394784/15?silent=true)). - **@david** green-lit the proposed direction for the calendar/event widget regression and invited a PR link for the missing chat icon after Rollup changes ([calendar widget bug](https://meta.discourse.org/t/-/400691/2?silent=true)). * * * If yesterday taught us anything, it’s that **cache-control headers, chat links, and “old topic” nudges** can all vanish at the worst moment—so today’s lucky charm is a well-timed refresh and an even better PR. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [April 16, 2026, 9:01pm UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/834 "2026-04-16T21:01:57Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **109** new posts, **20** new topics. - **Top contributors (posts / likes in the last 24h, with a recent reference):** | User | Posts | Likes | Recent reference | | --- | --- | --- | --- | | @Lilly | 8 | 15 | Published a new theme component: [read more](https://meta.discourse.org/t/-/400765/1?silent=true) | | @Falco | 3 | 11 | Drove embed improvements (dynamic height + lazy loading tweaks): [read more](https://meta.discourse.org/t/-/400721/17?silent=true) | | @pmusaraj | 6 | 10 | Shipped an experimental Buffer sharing plugin: [read more](https://meta.discourse.org/t/-/400819/1?silent=true) | | @putty | 5 | 9 | Confirmed/closed an AI-translation “German detection” investigation: [read more](https://meta.discourse.org/t/-/400708/10?silent=true) | | @awesomerobot | 4 | 8 | Landed a fix for invite details visibility: [read more](https://meta.discourse.org/t/-/400775/2?silent=true) | | @RGJ | 2 | 7 | Reported plugin-setting breakage tied to simplified category creation: [read more](https://meta.discourse.org/t/-/400699/3?silent=true) | | @Canapin | 6 | 6 | Raised UI issues with Topic Voting display on Foundation: [read more](https://meta.discourse.org/t/-/400800/1?silent=true) | | @lindsey | 2 | 5 | Announced “Ideas” category creation improvements: [read more](https://meta.discourse.org/t/-/399365/1?silent=true) | | @nat | 4 | 5 | Investigated translation edge cases + suggested verbose logging: [read more](https://meta.discourse.org/t/-/400612/7?silent=true) | | @darkpixlz | 1 | 5 | Flagged confusing “free plan shutdown” messaging vs reality: [read more](https://meta.discourse.org/t/-/400747/1?silent=true) | * * * ## Interesting Topics ### #Announcements - **“Ideas” categories got a smoother on-ramp** : @lindsey introduced a new “Ideas” category type that auto-configures Topic Voting and related settings during category creation [read more](https://meta.discourse.org/t/-/399365/1?silent=true). (Related background: Topic Voting plugin overview [read more](https://meta.discourse.org/t/-/40121/1?silent=true).) - **Meta housekeeping + multilingual edge cases surfaced again** : In the ongoing “content gardening hub” experiment, @nat called out the tricky case of _topic title language != first-post language_ and adjusted a title manually while noting composer UX limitations [read more](https://meta.discourse.org/t/-/397606/87?silent=true). ### #contribute:feature - **Embedding (Discourse Comments) kept leveling up**: the Tecnoblog thread continued as @Falco iterated on fixes for dynamic height and native lazy-loading via `