# 일일 요약 (UTC 오전 5시) **URL:** https://meta.discourse.org/t/daily-summary-5am-utc/291851 **Category:** Forum summaries **Created:** [1월 16, 2024, 9:58오후 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851 "2024-01-16T21:58:09Z") **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: [4월 3, 2026, 5:01오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/792 "2026-04-03T05:01:19Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 65 - **New topics (last 24h):** 11 **Top users (posts / likes in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @Moin | 7 | 10 | | @lindsey | 1 | 4 | | @awesomerobot | 3 | 4 | | @Lilly | 1 | 3 | | @Falco | 2 | 3 | | @Tris20 | 1 | 3 | | @nat | 2 | 3 | | @supermathie | 2 | 3 | | @pfaffman | 3 | 2 | | @mcmcclur | 1 | 2 | * * * ## Interesting Topics ### #bug - @Moin noticed tag pages suddenly looked “empty” because **tags weren’t appearing in tag banners** ; @awesomerobot confirmed it was caused by a data-availability change and shipped a quick plugin-side fix—already restored on Meta. [read more](https://meta.discourse.org/t/-/399813/1?silent=true) - A **Category Experts plugin crash during CLI user merges** was traced to a validation failure; @zogstrip linked the PR that fixes the plugin so merges won’t require disabling it first. [read more](https://meta.discourse.org/t/-/399785/3?silent=true) - Self-hosters reported **Cloudflare R2 backups failing on multipart upload** with `aws-sdk-s3 1.182.0` (`undefined method 'downcase' for nil`); @pfaffman shared a proven pinning workaround, and the OP confirmed it solved the issue. [read more](https://meta.discourse.org/t/-/399768/2?silent=true) - An intermittent but nasty **iPad Safari composer jump-to-top** (breaking upload buttons and resizing) was reported; after a bit of testing, the issue stopped reproducing for the reporter—still a useful breadcrumb if others see similar behavior. [read more](https://meta.discourse.org/t/-/399794/1?silent=true) - A report flagged **German translations injecting “AI commentary” / thought-process-like text** into UI and even cross-language post viewing, raising concerns about translation quality and tone. [read more](https://meta.discourse.org/t/-/399805/1?silent=true) ### #ux - Enforcing #2fa can lock users onto security preferences without access to “how-to” guidance; @supermathie pointed to customizing the relevant site text, and @awesomerobot provided a theme-component approach to inject richer HTML/help content above the enforcement UI. [read more](https://meta.discourse.org/t/-/399836/3?silent=true) - A site with an all-numeric tag found **old-style `/tag/6309` URLs returning a 500** instead of a clean 404/redirect—bad for crawlers and user experience; discussion centered on falling back more gracefully (or detecting numeric tag names). [read more](https://meta.discourse.org/t/-/399784/1?silent=true) - The long-running question of **what the “homepage” should be for doc categories** got new traction: @nickrsan explored adding a redirect-to-index option, but found a larger plugin rework underway and suggested integrating the idea there. [read more](https://meta.discourse.org/t/-/398616/4?silent=true) - In the ongoing “let users control AI” thread, @paco argued for a **per-user `discourse_ai_enabled` equivalent** so people can opt out of AI features even when site-wide AI is enabled. [read more](https://meta.discourse.org/t/-/393818/12?silent=true) ### #Announcements - @lindsey announced a quality-of-life improvement for #solved workflows: **users Tracking/Watching topics in support categories now get notified when the topic is marked solved** , with a preference toggle for those who want it off. [read more](https://meta.discourse.org/t/-/399821/1?silent=true) - Feedback continued on embedding Discourse as a full comment system (#embedding): @Tris20 highlighted discoverability issues (the scrollbar and “reply” affordances), and @mcmcclur worried some UI elements may now be _too_ subtle (including missing timeline context). [read more](https://meta.discourse.org/t/-/399743/9?silent=true) - The #calendar-and-event subscription announcement thread surfaced a potential regression: an existing install no longer shows **events in posts** , suggesting a plugin-migration-related issue rather than the subscription URLs feature itself. [read more](https://meta.discourse.org/t/-/398902/18?silent=true) ### #contribute:feature - A long-requested i18n nicety landed: **emoji search now supports English _and_ localized aliases** , and in the process a bug fix trimmed the `emojis.json` payload by ~160KB. [read more](https://meta.discourse.org/t/-/86641/25?silent=true) - More #content-localization + tag UI polish: @Moin asked for **tag icons to appear correctly for translated tags in tag/category banners** , after noticing parity gaps between English and translated tag displays. [read more](https://meta.discourse.org/t/-/399840/1?silent=true) - Continuing the localization + tag UX theme, discussion on the tag icon component asked to **support translated tags more completely** , including in dropdown menus where some translated variants still don’t render as expected. [read more](https://meta.discourse.org/t/-/399594/4?silent=true) ### #Support / #Dev / #Theme\_component (worth a quick look) - A hosted-support question: **category-level moderation isn’t triggering the `post_needs_approval` email** , even though posts correctly land in the review queue—admins are looking for a per-category solution without enabling global moderation emails. [read more](https://meta.discourse.org/t/-/399775/1?silent=true) - Design/dev enablement: a user asked where to find **Discourse design resources** , and the accepted answer pointed them to enabling the built-in **styleguide** on their instance (plus a nudge toward #Documentation > Developer Guides). [read more](https://meta.discourse.org/t/-/399847/2?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot responded quickly to the missing-tag-banner regression, identified the upstream change that affected available data, and confirmed the fix was merged and visible again on Meta. [read more](https://meta.discourse.org/t/-/399813/2?silent=true) - @awesomerobot also provided a practical, copy/paste-ready solution for improving the locked-down #2fa enforcement experience via a theme component and `renderBeforeWrapperOutlet`, enabling admins to add links and richer guidance. [read more](https://meta.discourse.org/t/-/399836/3?silent=true) - @lindsey published the announcement that **Tracking/Watching users now receive solved notifications** in support categories using the #solved plugin, including the “Want to turn it off?” preference guidance. [read more](https://meta.discourse.org/t/-/399821/1?silent=true) - @supermathie helped unblock MFA-enforcement messaging by pointing admins to the exact site-text customization path to tweak the “required to enable” copy. [read more](https://meta.discourse.org/t/-/399836/2?silent=true) - @Falco closed the loop on localized emoji aliases, linking the implementation PRs and noting the performance win (smaller emoji payload) that came along for the ride. [read more](https://meta.discourse.org/t/-/86641/25?silent=true) - @Falco also chimed in on a self-hosting migration collision story with some levity (and confirmation they’d recently re-done a failing migration), keeping the solved thread moving. [read more](https://meta.discourse.org/t/-/399572/10?silent=true) - @nat followed up in the localization/tag-icons conversation, clarifying a translation shown was intentionally manual/wordplay on their own instance—useful context when evaluating translated-label behavior. [read more](https://meta.discourse.org/t/-/399594/6?silent=true) - @davidb pointed to the core change that resolves **group dropdowns not refreshing properly** after new groups are created, effectively closing the loop on that bug report. [read more](https://meta.discourse.org/t/-/398285/3?silent=true) - @zogstrip acknowledged the Category Experts merge crash report and linked the plugin PR that addresses it so admins won’t need to disable the plugin during merges. [read more](https://meta.discourse.org/t/-/399785/3?silent=true) * * * _Sign-off:_ Between tag banners vanishing and reappearing ([read more](https://meta.discourse.org/t/-/399813/1?silent=true)), emoji payloads going on a 160KB diet ([read more](https://meta.discourse.org/t/-/86641/25?silent=true)), and at least one migration “buddy” showing a surprising amount of personality ([read more](https://meta.discourse.org/t/-/399572/10?silent=true)), Meta had one of those delightfully chaotic-yet-productive days. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 4, 2026, 5:01오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/793 "2026-04-04T05:01:06Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **100** new posts, **9** new topics. _(Source window: 2026-04-03 → 2026-04-04; see discussion highlights like [read more](https://meta.discourse.org/t/-/399835/1?silent=true) and [read more](https://meta.discourse.org/t/-/399862/1?silent=true))._ - **Top posters & most-liked (last 24h):** | User | Posts | Likes | | --- | --- | --- | | @Canapin | 7 | 27 | | @RGJ | 9 | 21 | | @Moin | 8 | 18 | | @awesomerobot | 5 | 14 | | @NateDhaliwal | 10 | 12 | | @putty | 4 | 11 | | @Bas | 2 | 10 | | @lindsey | 1 | 10 | | @zogstrip | 3 | 9 | | @Lilly | 2 | 8 | * * * ## Interesting Topics ### #Announcements - **“Boosts” reactions-with-text experiment landed on Meta.** @lindsey introduced the new _boosts_ interaction layer ([read more](https://meta.discourse.org/t/-/399835/1?silent=true)), with follow-up discussion digging into naming confusion, moderation/flagging behavior, and whether boosts should merge into reactions long-term ([read more](https://meta.discourse.org/t/-/399835/19?silent=true)). Related: ActivityPub confusion got clarified ([read more](https://meta.discourse.org/t/-/399835/22?silent=true)) and “convert too-short replies into boosts” was debated ([read more](https://meta.discourse.org/t/-/399835/30?silent=true)). - **Embedding Discourse as a full comment system: practical UX questions keep rolling in.** People discussed how embedded pages map back into Discourse categories and reporting flows ([read more](https://meta.discourse.org/t/-/399743/11?silent=true)), plus feedback that infinite scroll can hide the reply affordance in constrained embed heights ([read more](https://meta.discourse.org/t/-/399743/12?silent=true)). Related: example reference to tag strategy from “It’s time we talked about tags” ([read more](https://meta.discourse.org/t/-/72467/1?silent=true)). * * * ### #Site feedback - **[ask.discourse.com](http://ask.discourse.com) outage report → confirmed + fixed.** A quick heads-up that Ask was unreachable led to a team acknowledgement and resolution ([read more](https://meta.discourse.org/t/-/399862/1?silent=true), then [read more](https://meta.discourse.org/t/-/399862/4?silent=true)). Related: UX polish request on Ask’s “Back to Forum” link placement ([read more](https://meta.discourse.org/t/-/399871/1?silent=true)). - **Meta “content gardening hub” thread: more process-oriented tooling ideas.** The ongoing experiment thread continued with suggestions for surfacing topics that likely need a #fixed tag (via a staff/PR-linked topic filter pattern) ([read more](https://meta.discourse.org/t/-/397606/71?silent=true)). Related: discussion that prompted the filter referenced #Contribute workflows in #bug/#contribute:ux contexts ([read more](https://meta.discourse.org/t/-/399805/4?silent=true)). * * * ### #General - **Looking for Discourse communities about public transit / urban design.** A member asked for a directory of transit-focused forums running Discourse, and got pointed to [discover.discourse.org](http://discover.discourse.org) and a couple known examples ([read more](https://meta.discourse.org/t/-/399902/1?silent=true)). Related: discovery as an ongoing need connects well with the broader “directory” idea mentioned in the same thread ([read more](https://meta.discourse.org/t/-/399902/2?silent=true)). * * * ### #contribute:feature (tags: #ai) - **Mistral embeddings compatibility issue: “dimensions” vs “output\_dimension”.** @RGJ reported that Mistral’s embeddings endpoint rejects the OpenAI-style `dimensions` parameter and that Discourse currently requires it for saving ([read more](https://meta.discourse.org/t/-/399854/1?silent=true)). Related: prior how-to context for Mistral embeddings configuration ([read more](https://meta.discourse.org/t/-/361095/1?silent=true)). * * * ### #ux (tags: #tags, #ask-discourse) - **Numeric-tag URLs throwing 500s at legacy paths (crawl/SEO impact).** A report highlighted 500 errors when old-style numeric tag URLs get crawled, with confirmation that a fix is planned while keeping `/tag/name` resolution stable ([read more](https://meta.discourse.org/t/-/399784/11?silent=true)). Related: broader tag discussions often come back to URL stability and discoverability ([read more](https://meta.discourse.org/t/-/72467/1?silent=true)). - **Ask UI: hide “Back to Forum” on the homepage.** A small but sensible UX tweak request noted that the “Back to Forum” link is redundant on Ask’s homepage and should only appear when actually “in” a conversation flow ([read more](https://meta.discourse.org/t/-/399871/1?silent=true)). Related: Ask’s availability incident from earlier the same day ([read more](https://meta.discourse.org/t/-/399862/1?silent=true)). * * * ### #bug (tags: #ai, #content-localization) - **AI-generated German translation pages had “Thinking/Translate”-style artifacts; cleanup + agent update deployed.** The issue was investigated, a formatting-tightening update shipped, and affected titles/posts were cleaned up ([read more](https://meta.discourse.org/t/-/399805/4?silent=true)). Related: the referenced prompt/feature change that may have contributed ([read more](https://meta.discourse.org/t/-/38965/1?silent=true)) and the deployed fix PR link cited in-thread ([read more](https://meta.discourse.org/t/-/399805/4?silent=true)). * * * ### #Support - **Hidden comments “reappearing” after user edits: clarification of intended moderation behavior.** A moderator reported that hidden posts re-entered the timeline after edits, expecting an approval gate; replies clarified that once posted, edits can reinstate visibility unless the post is deleted or “request revision” is used pre-approval ([read more](https://meta.discourse.org/t/-/399901/1?silent=true)). Related: moderation workflow differences between approval queue vs public timeline were central ([read more](https://meta.discourse.org/t/-/399901/4?silent=true)). - **Featured Topics via API: where to fetch them.** A question about a native endpoint for “featured topics” was answered with a pointer to `/categories.json` when category pages are configured to include featured topics ([read more](https://meta.discourse.org/t/-/399867/1?silent=true)). Related: this fits into broader REST API usage patterns for topic discovery ([read more](https://meta.discourse.org/t/-/399867/2?silent=true)). - **Mail receiver trouble with self-hosted email: SPF rejection example.** A “me too” update on a long-running mail receiver thread shared a bounce log showing SPF fail/rejection after migrating away from Gmail to self-hosted mail ([read more](https://meta.discourse.org/t/-/349243/7?silent=true)). Related: email deliverability pitfalls continue to be a common ops theme ([read more](https://meta.discourse.org/t/-/349243/7?silent=true)). - **Filtering topic lists: yes, you can include plain text search terms in the “topic filter” UI.** A question about filtering by arbitrary text (without jumping into full search UI) was answered: just type the words after other filters to constrain the topic list ([read more](https://meta.discourse.org/t/-/375558/20?silent=true)). Related: examples in the reference thread show mixed filter + text patterns ([read more](https://meta.discourse.org/t/-/375558/21?silent=true)). - **Bitnami + polls error (“NoMethodError”): install path matters.** A report in Chinese showed a stack trace hitting the poll serializer; replies quickly suspected Bitnami packaging (long unsupported/deprecated) as a root cause ([read more](https://meta.discourse.org/t/-/399856/1?silent=true)). Related: “Bitnami installations are unsupported” doc ([read more](https://meta.discourse.org/t/-/142538/1?silent=true)) and the Bitnami container deprecation notice ([read more](https://meta.discourse.org/t/-/374875/1?silent=true)). - **iOS home-screen push notifications for self-hosted: behavior, fragility, and security tradeoffs.** The push-notifications thread confirmed iOS 16.4+ “add to home screen” push can work, but uncovered a surprising “wipe keys on logout” line and the privacy rationale behind it ([read more](https://meta.discourse.org/t/-/394149/11?silent=true), plus [read more](https://meta.discourse.org/t/-/394149/15?silent=true)). Related: the code line discussion referenced in-thread ([read more](https://meta.discourse.org/t/-/394149/13?silent=true)). * * * ### #customization:plugin - **Discourse Daily Challenges: repo access weirdness (404 for some users) led to moving to GitLab.** In the daily challenges plugin thread, a GitHub “account flagged/held” scenario caused intermittent 404s for others, prompting a migration to GitLab and updated links ([read more](https://meta.discourse.org/t/-/398980/57?silent=true), then [read more](https://meta.discourse.org/t/-/398980/65?silent=true)). Related: another similar “repo disappeared” anecdote referenced QR shareables ([read more](https://meta.discourse.org/t/-/341948/26?silent=true)). - **Pushover plugin got modernized for current Discourse versions.** A long-running notifications plugin topic received an update: the plugin was updated/modernized to work again on recent releases ([read more](https://meta.discourse.org/t/-/119258/28?silent=true)). Related: notification ecosystem overlaps with other push-notification discussions ([read more](https://meta.discourse.org/t/-/394149/11?silent=true)). * * * ### #Integrations (tags: #sso, #how-to) - **New guide: auto-provision users when SSO is enabled (skip the signup interstitial).** A documentation topic explains how to enable `auth skip create confirm` to silently create accounts on first external login, plus optional overrides depending on identity provider behavior ([read more](https://meta.discourse.org/t/-/399917/1?silent=true)). Related: foundational SSO setup via [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) ([read more](https://meta.discourse.org/t/-/13045/1?silent=true)), plus common auth plugins like OIDC ([read more](https://meta.discourse.org/t/-/103632/1?silent=true)) and OAuth2 Basic ([read more](https://meta.discourse.org/t/-/33879/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@lindsey** introduced the **Boosts** experiment and invited feedback on positioning, notifications, and use-cases ([read more](https://meta.discourse.org/t/-/399835/1?silent=true)). - **@zogstrip** clarified boosts are _not_ meant to reorder posts (just “reaction-like” metadata) ([read more](https://meta.discourse.org/t/-/399835/8?silent=true)), joined the naming discussion ([read more](https://meta.discourse.org/t/-/399835/10?silent=true)), and flagged likely install-path issues in the Bitnami/polls error report ([read more](https://meta.discourse.org/t/-/399856/2?silent=true)). - **@j.jaffeux** explained the intended “interaction hierarchy” and hinted at a longer-term unification path for boosts/reactions/likes so communities can choose the right layer(s) ([read more](https://meta.discourse.org/t/-/399835/19?silent=true)). - **@awesomerobot** elaborated on the intent (“morale boost” style), confirmed boosts will be optional, and shared moderation notes (watched words apply; AI scanning is possible but not on yet) ([read more](https://meta.discourse.org/t/-/399835/22?silent=true), [read more](https://meta.discourse.org/t/-/399835/29?silent=true)). They also responded to a public-transit community directory question ([read more](https://meta.discourse.org/t/-/399902/2?silent=true)) and agreed to adjust Ask’s custom “Back to Forum” link behavior on the homepage ([read more](https://meta.discourse.org/t/-/399871/2?silent=true)). - **@Bas** acknowledged the Ask outage report and followed up with confirmation that service was restored ([read more](https://meta.discourse.org/t/-/399862/3?silent=true), [read more](https://meta.discourse.org/t/-/399862/4?silent=true)). - **@nat** confirmed the team had eyes on the numeric-tag URL 500 issue and reiterated the commitment to `/tag/name` compatibility ([read more](https://meta.discourse.org/t/-/399784/11?silent=true)). They also shipped/confirmed an AI agent formatting fix and cleanup for German localization artifacts ([read more](https://meta.discourse.org/t/-/399805/4?silent=true)). - **@Falco** confirmed iOS home-screen push support expectations and pointed to a problematic implementation detail that may be causing fragility (especially around admin impersonation/logouts) ([read more](https://meta.discourse.org/t/-/394149/11?silent=true), [read more](https://meta.discourse.org/t/-/394149/13?silent=true)). - **@featheredtoast** added important context on why “wipe push keys on logout” exists (preventing notification previews on logged-out devices), and proposed exploring better session/user binding for push subscriptions ([read more](https://meta.discourse.org/t/-/394149/15?silent=true)). They also modernized the Pushover plugin for current Discourse versions ([read more](https://meta.discourse.org/t/-/119258/28?silent=true)). * * * _Yesterday’s theme: Meta got a “boost” of its own—between rockets, restored Ask uptime, and revived notifications plumbing, the site spent the day leveling up how it pings and praises people._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 5, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/794 "2026-04-05T05:02:21Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 75** - **New topics (last 24h): 14** (covered below in _Interesting Topics_) ### Top users (posts + likes) | User | Posts | Likes | | --- | --- | --- | | @Ed_S | 7 | 16 | | @RGJ | 6 | 16 | | @Canapin | 3 | 10 | | @Anton_Akhmerov | 2 | 7 | | @Falco | 3 | 6 | | @Denis_Kovalenko | 8 | 6 | | @haydenjames | 1 | 5 | | @Lilly | 4 | 4 | | @eisammy | 3 | 4 | | @ProxyTracer | 3 | 4 | ### More threads with fresh replies (worth a quick catch-up) - Ongoing UX/design discussion around Boosts continued in **#Announcements** : [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/46?silent=true) [read more](https://meta.discourse.org/t/-/399835/56?silent=true) - Embedding feedback kept flowing in **#Announcements** : [Embed Discourse as a full comment system on your site](https://meta.discourse.org/t/-/399743/14?silent=true) - A solved-notification edge case was raised in **#Announcements** : [Notifying members when a Tracked or Watched topic is solved](https://meta.discourse.org/t/-/399821/2?silent=true) - Trust-level references got resurfaced in **#Using Discourse** : [Discourse Trust Levels: A Detailed Explanation](https://meta.discourse.org/t/-/396792/9?silent=true) (with pointer to [Trust level permissions reference](https://meta.discourse.org/t/-/224824/1?silent=true)) - Push notification implementation details came up again in **#Support** : [iOS/Android Push Notifications on Self-Hosted Discourse (Docker)](https://meta.discourse.org/t/-/394149/16?silent=true) - Approval/refusal workflow questions returned in **#Site Management** : [Configuring and managing the sign-up flow with user approval](https://meta.discourse.org/t/-/112128/33?silent=true) - Theme toggle troubleshooting continued in **#customization:theme component** : [Sidebar Theme Toggle](https://meta.discourse.org/t/-/242802/39?silent=true) - Cloudflare R2 backup troubleshooting had a small “it works now” update in **#bug** : [Backups to Cloudflare R2 fail during multipart upload…](https://meta.discourse.org/t/-/399768/4?silent=true) - PM inbox bump-date behavior was re-confirmed in **#bug** : [Automatic replies to something else flags don’t update the bump date in the inbox](https://meta.discourse.org/t/-/393447/2?silent=true) - Logged-out popup security expectations were discussed in **#contribute:feature** : [Security Suggestions For Discourse Logged Out Popups](https://meta.discourse.org/t/-/389991/3?silent=true) - A niche directory request wrapped up in **#General** : [Are there forums on public transit in discourse?](https://meta.discourse.org/t/-/399902/4?silent=true) * * * ## Interesting Topics **#Announcements** - @RGJ, @Ed_S, @ToddZ and @Canapin continued debating what “boost-worthy” content is—and how Boosts interact with character limits and reply-clarity—in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/46?silent=true) (including UI clarity concerns about “reply-to-the-post-above” behavior: [read more](https://meta.discourse.org/t/-/399835/50?silent=true)) **#General** - @Ed_S asked how many admins deliberately run a “minimal” Discourse (few categories, no chat, no reactions, no LLMs, etc.) in [How minimal is your forum?](https://meta.discourse.org/t/-/399941/1?silent=true), with @Canapin sharing a pragmatic “minimal-ish” setup and pointing to components/plugins like [Discourse Who’s Online](https://meta.discourse.org/t/-/52345/1?silent=true), [Discourse Yearly Review](https://meta.discourse.org/t/-/105713/1?silent=true), and third-party add-ons such as [Locations Plugin](https://meta.discourse.org/t/-/69742/1?silent=true), [🖼 Topic Gallery](https://meta.discourse.org/t/-/394953/1?silent=true), and [Search Thumbnails](https://meta.discourse.org/t/-/395082/1?silent=true) (plus UI extras like [Emoji Fluff](https://meta.discourse.org/t/-/339163/1?silent=true) and the [MD Topic List Mobile component](https://meta.discourse.org/t/-/146341/1?silent=true)) - @Monikas debuted a game-inspired UI concept theme and got a nudge toward proper sharing/packaging by @Lilly in [I made a Zenless Zone Zero Inter-Knot UItheme (੭ˊ͈꒳ˋ͈)੭ ✎](https://meta.discourse.org/t/-/399961/1?silent=true) **#customization:plugin** _(#groups #chat)_ - @Anton_Akhmerov shared an AI-assisted prototype plugin for multi-team “workspaces” (categories as workspaces, subcategories as channels + paired chat) and @mcwumbly asked about real-world usage in [Workspace groups](https://meta.discourse.org/t/-/399936/1?silent=true) (install reference: [How to install plugins in Discourse](https://meta.discourse.org/t/-/19157/1?silent=true)) - A new anti-abuse integration plugin landed, using an external API to detect/block VPN & proxy traffic at registration/login (with caching + fail-open options) in [ProxyTracer: VPN & Proxy Blocker](https://meta.discourse.org/t/-/399958/1?silent=true) **#community-building Building** _(#community-strategy)_ - @haydenjames asked for tactics to grow a community that _isn’t_ anchored to a product/service (so no built-in support-driven return visits), in [How to Grow a Discourse Forum without product or service behind it?](https://meta.discourse.org/t/-/399943/1?silent=true) **#bug** _(#ai #content-localization)_ - @Denis_Kovalenko reported that images disappeared only in translated views when switching from OpenAI to Mistral—then confirmed that upgrading from Mistral Small to Mistral Large resolved it—in [Images missing in translated posts when using Mistral as translation model](https://meta.discourse.org/t/-/399939/1?silent=true) (resolution details: [read more](https://meta.discourse.org/t/-/399939/5?silent=true)) **#bug** _(#calendar-and-event)_ - A Safari PWA user-facing throttling problem was reported (with video evidence) in [/upcoming-events rate limiting](https://meta.discourse.org/t/-/399931/1?silent=true) **#contribute:feature** - A request proposed codec inspection (or rejection/transcoding) for `.mp4` uploads that are VP9-in-MP4—fine on desktop/Android but silently fail on iOS Safari—in [Auto-detect or reject VP9 video uploads incompatible with iOS Safari](https://meta.discourse.org/t/-/399955/1?silent=true); @Falco pointed to [Discourse Video Stream 🎥](https://meta.discourse.org/t/-/388754/1?silent=true) and discussed safe default trade-offs for self-hosters ([read more](https://meta.discourse.org/t/-/399955/4?silent=true)) **#Site feedback** _(#content-localization)_ - @Denis_Kovalenko asked for Ukrainian/Russian in Meta’s language switcher, and @Falco confirmed it’ll be added soon in [Please add the Ukrainian or Russian languages](https://meta.discourse.org/t/-/399957/1?silent=true) (team follow-up: [read more](https://meta.discourse.org/t/-/399957/8?silent=true)) **#ux** _(#composer)_ - @RGJ flagged confusing wording when abandoning an _edit_ (button says “Discard”, modal asks “discard your post?” even with no changes), proposing “Cancel edit / discard edits” clarity in [“do you want to discard your post ?”](https://meta.discourse.org/t/-/399942/1?silent=true) **#Support** - A question about “turning off the composer panel” turned into guidance about rich-text vs Markdown mode and preview toggles in [Toggling off the composer panel](https://meta.discourse.org/t/-/399937/1?silent=true), with a pointer back to the rich-text/Markdown switch UX shown in [the composer toggle topic](https://meta.discourse.org/t/-/375476/1?silent=true) - A self-hosting moderation question asked whether AI triage automation actually scans DMs between regular users when “Include personal messages” is enabled, in [Does AI triage automation scan DMs between regular users?](https://meta.discourse.org/t/-/399952/1?silent=true) - A Chinese-language support thread dug into why all traffic appears as Cloudflare IPs when running a multi-proxy chain (`Cloudflare -> local nginx -> container`) in [如何解决所有流量显示为来自 Cloudflare 的服务器，而不是用户的浏览器 IP](https://meta.discourse.org/t/-/399954/1?silent=true), referencing [Using Discourse with Cloudflare (best practices)](https://meta.discourse.org/t/-/293405/1?silent=true) and discussing additional reverse-proxy layers ([read more](https://meta.discourse.org/t/-/399954/6?silent=true)) **#Self-hosting** - A blocked setup flow (Discourse ID registration/SSO error) plus a “what’s wrong with my NGINX config?” question came up in [Trying to setup discourse and cannot use it due to sso?](https://meta.discourse.org/t/-/399956/1?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco focused on practical platform-level guardrails: in [Auto-detect or reject VP9 video uploads incompatible with iOS Safari](https://meta.discourse.org/t/-/399955/2?silent=true), @Falco recommended looking at [Discourse Video Stream](https://meta.discourse.org/t/-/388754/1?silent=true) and highlighted why “safe by default” transcoding is tricky for small self-hosts, then floated exploring a plugin option with explicit admin trade-offs ([read more](https://meta.discourse.org/t/-/399955/4?silent=true)). - @Falco also confirmed a straightforward localization improvement for Meta itself: Ukrainian and Russian are planned to be added to Meta’s language switcher in [Please add the Ukrainian or Russian languages](https://meta.discourse.org/t/-/399957/8?silent=true). - @mcwumbly engaged with new plugin experimentation and asked the “is it used in production yet?” question on a multi-team workspace concept in [Workspace groups](https://meta.discourse.org/t/-/399936/2?silent=true). * * * If yesterday was any indication, today’s Meta vibe is: _keep it minimal… unless you’re adding Boosts, workspaces, and VP9 detection—then buckle up._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 6, 2026, 5:01오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/795 "2026-04-06T05:01:42Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours (2026-04-05 → 2026-04-06), Meta saw **37 new posts** across **6 new topics**. Source range: topics and replies in this report (e.g. [read more](https://meta.discourse.org/t/-/399973/1?silent=true)). ### Top users (posts / likes in the last 24h) | User | Posts | Likes | | --- | --- | --- | | @Moin | 4 | 10 | | @Ed_S | 4 | 5 | | @elmuerte | 3 | 5 | | @Canapin | 2 | 2 | | @satonotdead | 1 | 3 | | @RGJ | 1 | 3 | | @sam | 1 | 2 | | @bryce | 1 | 2 | | @merefield | 1 | 1 | | @patrickemin | 1 | 1 | (Per-post highlights include @Moin’s guidance on TL3 tuning in #Support ([read more](https://meta.discourse.org/t/-/399973/2?silent=true)) and @elmuerte’s new Ko‑fi plugin announcement in #customization:plugin ([read more](https://meta.discourse.org/t/-/399978/1?silent=true)).) * * * ## Interesting Topics ### #Support - @Ed_S asked how to _data-drive_ #trust-levels tuning so TL3 promotion matches the community’s size, and @Moin pointed to user-level requirement breakdowns plus [Data Explorer](https://meta.discourse.org/t/32566?silent=true) queries for identifying “almost TL3” users ([read more](https://meta.discourse.org/t/-/399973/1?silent=true), [read more](https://meta.discourse.org/t/-/399973/2?silent=true), plus the referenced query thread: [read more](https://meta.discourse.org/t/-/91495/1?silent=true)). - Meta’s own TL3 thresholds came up as a real-world example: @mcwumbly shared that Meta reduced TL3 _cap_ requirements (topics viewed cap and posts read cap) after analyzing query results, and discussed upcoming work to roll out future default-setting changes more transparently ([read more](https://meta.discourse.org/t/-/399973/3?silent=true), referenced analysis context: [read more](https://meta.discourse.org/t/-/91495/27?silent=true), and the quoted settings-change topic: [read more](https://meta.discourse.org/t/-/395960/1?silent=true)). - In an #automation / #ai support question, @RGJ confirmed that enabling “Include personal messages” means AI triage can scan DMs between regular users too—and asked how the reporter verified DMs weren’t being scanned ([read more](https://meta.discourse.org/t/-/399952/2?silent=true), original question: [read more](https://meta.discourse.org/t/-/399952/1?silent=true)). - A French-language #calendar-and-event support question asked for a “cancel event” workflow that notifies _all_ registrants without manually addressing each user in a message ([read more](https://meta.discourse.org/t/-/399981/1?silent=true)). - Following up on structured-data / SEO work, @Richie reported Google Search Console still flagging a missing `text` field under `mainEntity.suggestedAnswer` even after updating to the latest build, referencing prior investigation and fixes ([read more](https://meta.discourse.org/t/-/399974/1?silent=true), prior bug thread: [read more](https://meta.discourse.org/t/-/399525/1?silent=true)). - A Chinese-language thread continued troubleshooting why all traffic appears to come from Cloudflare instead of end-user IPs—discussion centered on constraints introduced by a control panel setup and whether simplifying the stack would help ([read more](https://meta.discourse.org/t/-/399954/7?silent=true), continuation: [read more](https://meta.discourse.org/t/-/399954/8?silent=true)). ### #customization:plugin - A new plugin drop: **Discourse Ko‑fi integration** by @elmuerte adds donation/subscription syncing via Ko‑fi webhooks, with rewards like badges and group membership; follow-ups covered currency limitations and anonymization behavior ([read more](https://meta.discourse.org/t/-/399978/1?silent=true), caveats: [read more](https://meta.discourse.org/t/-/399978/2?silent=true), maintenance/PR discussion: [read more](https://meta.discourse.org/t/-/399978/3?silent=true), maintainer response: [read more](https://meta.discourse.org/t/-/399978/4?silent=true)). - In the experimental **Discourse Suggested Edits** plugin topic, @sam confirmed a requested capability is “not implemented yet” but will be added; discussion immediately continued into category selection expectations ([read more](https://meta.discourse.org/t/-/398691/4?silent=true), follow-up question: [read more](https://meta.discourse.org/t/-/398691/5?silent=true)). - The long-running **Locations Plugin** support thread saw a report that category maps stopped rendering after updates; @merefield responded by inviting sponsorship and offering to investigate ([read more](https://meta.discourse.org/t/-/69742/1232?silent=true), response: [read more](https://meta.discourse.org/t/-/69742/1233?silent=true)). - In **ProxyTracer: VPN & Proxy Blocker** , @Moin cautioned that [Safe Mode](https://meta.discourse.org/t/53504?silent=true) won’t help with Ruby-only behavior and raised skepticism about plugin packaging choices; the plugin author updated docs with server-side disable steps and removed redundant theme metadata ([read more](https://meta.discourse.org/t/-/399958/6?silent=true), author follow-up: [read more](https://meta.discourse.org/t/-/399958/7?silent=true), [Safe Mode](https://meta.discourse.org/t/53504?silent=true) reference: [read more](https://meta.discourse.org/t/-/53504/1?silent=true), related admin recovery reference: [read more](https://meta.discourse.org/t/-/89605/1?silent=true)). ### #ux - A “mystery overlay” report turned out to be a rendering artifact: @wuyuan saw gray dots/lines in the bottom-left; after initial UI guesses, @bryce explained it’s likely the sidebar fade gradient and provided CSS to disable it via `--d-sidebar-footer-fade` ([read more](https://meta.discourse.org/t/-/399977/1?silent=true), clarification: [read more](https://meta.discourse.org/t/-/399977/4?silent=true), staff solution: [read more](https://meta.discourse.org/t/-/399977/5?silent=true), related component reference: [read more](https://meta.discourse.org/t/-/242802/1?silent=true)). - “Clearing advice doesn’t actually clear it”: @ted shared a PR concept to make specific dashboard problem-check notices ignorable (with an overview/undo surface), so admins can manage checks more deliberately ([read more](https://meta.discourse.org/t/-/398754/4?silent=true), original UX complaint context: [read more](https://meta.discourse.org/t/-/398754/1?silent=true)). ### #bug - A regression tied to the “simplified category creation” upcoming change: @Moin reported that re-parenting categories/subcategories can silently reset category security permissions (re-opening posting to `everyone`); @mcwumbly confirmed it looked familiar and that the team would dig in ([read more](https://meta.discourse.org/t/-/399976/1?silent=true), response: [read more](https://meta.discourse.org/t/-/399976/2?silent=true), referenced upcoming change: [read more](https://meta.discourse.org/t/-/394971/1?silent=true)). ### #Announcements - The ongoing “Testing Boosts on Meta” discussion continued with feedback about how boosts vs likes/reactions should communicate community value—@Canapin argued boosts may be more “guestbook” than “signal,” and suggested visibility differences for authors vs readers ([read more](https://meta.discourse.org/t/-/399835/57?silent=true), @Canapin’s perspective: [read more](https://meta.discourse.org/t/-/399835/58?silent=true), topic root: [read more](https://meta.discourse.org/t/-/399835/1?silent=true)). ### #Site feedback - In the “collaborative content gardening hub” experiment thread, @Moin noticed category descriptions and/or restrictions no longer matched reality for plugin/theme posting, and @mcwumbly connected it to category re-parenting permission loss—linking it directly to the new security-reset bug report ([read more](https://meta.discourse.org/t/-/397606/72?silent=true), staff reply linking bug: [read more](https://meta.discourse.org/t/-/397606/74?silent=true), cross-link to bug: [read more](https://meta.discourse.org/t/-/399976/1?silent=true)). - A localization request thread about adding Ukrainian or Russian languages continued, with @Denis_Kovalenko asking which translation model might be used as the request progressed ([read more](https://meta.discourse.org/t/-/399957/9?silent=true), thread root: [read more](https://meta.discourse.org/t/-/399957/1?silent=true)). ### #Self-hosting - In a solved “plugins not functioning due to CORS” thread, @TomoftheFog added a _new_ symptom: some users can’t see avatar images when the Preformatted Text markdown button tries to load highlight.js and hits a CORS failure—flagging it for others in case it’s related ([read more](https://meta.discourse.org/t/-/399466/18?silent=true), thread root: [read more](https://meta.discourse.org/t/-/399466/1?silent=true)). ### #General - In “How minimal is your forum?”, @Ed_S reflected on tag value (SEO vs maintenance burden) and how permissive tag creation at TL2 may contribute to tag sprawl—then spun that into a deeper TL3 threshold question ([read more](https://meta.discourse.org/t/-/399941/7?silent=true), follow-on TL3 tuning topic: [read more](https://meta.discourse.org/t/-/399973/1?silent=true)). - A previously opened support topic about “official components” breaking after an update was confirmed resolved by @Stephane_Roy, serving as a quick “good news” datapoint amid other upgrade-side effects ([read more](https://meta.discourse.org/t/-/398143/3?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @mcwumbly engaged in #Support to share Meta’s _real_ TL3 requirement adjustments (notably reduced cap values) and to discuss improving how Discourse communicates/rolls out default site-setting changes ([read more](https://meta.discourse.org/t/-/399973/3?silent=true)). He also acknowledged and connected reports of category permission loss after re-parenting, both directly in the bug report ([read more](https://meta.discourse.org/t/-/399976/2?silent=true)) and while replying in the content-gardening experiment thread ([read more](https://meta.discourse.org/t/-/397606/74?silent=true)). - @bryce jumped into #ux to diagnose the “bottom-left overlay” as a sidebar fade gradient artifact and provided a targeted CSS workaround using `--d-sidebar-footer-fade` ([read more](https://meta.discourse.org/t/-/399977/5?silent=true)). - @sam replied in the #customization:plugin area on the experimental suggested-edits effort, confirming a requested feature isn’t built yet but is planned (“will add”) ([read more](https://meta.discourse.org/t/-/398691/4?silent=true)). * * * If yesterday proved anything, it’s that Meta can debate _boosts vs likes_ while simultaneously chasing down _mysterious gradient dots_—peak Discourse multitasking. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 7, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/796 "2026-04-07T05:02:02Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 92 - **New topics (last 24h):** 12 **Top users (posts / likes in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @RGJ | 9 | 16 | | @Canapin | 6 | 13 | | @Falco | 5 | 9 | | @ars18 | 2 | 8 | | @chapoi | 2 | 7 | | @awesomerobot | 3 | 5 | | @manuel | 3 | 4 | | @R23D_Printing | 4 | 4 | | @sam | 4 | 3 | | @pmusaraj | 1 | 3 | **Also active (worth a quick scan):** boosts and “lightweight reactions” debate in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/63?silent=true), AI embeddings provider setup in [Use Mistral for embeddings](https://meta.discourse.org/t/-/399854/3?silent=true), a safety-minded update cadence discussion in [Auto updates via cronjob - is this safe?](https://meta.discourse.org/t/-/241232/9?silent=true), translations + dashboards in [Discourse Daily Challenges](https://meta.discourse.org/t/-/398980/77?silent=true), install quirks in [Discourse Doc Categories](https://meta.discourse.org/t/-/322376/159?silent=true), and new embedding-as-comments questions in [Embed Discourse as a full comment system on your site](https://meta.discourse.org/t/-/399743/15?silent=true). * * * ## Interesting Topics ### #Support - @Denis_Kovalenko tested whether AI triage automations scan user-to-user DMs and discovered they weren’t being reviewed until configuration was adjusted; @RGJ confirmed the audit logs didn’t include PMs and the fix was to **leave “Topic Type” empty** so PMs are included, prompting UI clarity suggestions from @awesomerobot in [Does AI triage automation scan DMs between regular users?](https://meta.discourse.org/t/-/399952/5?silent=true) (#automation #ai) - Translation users debugging missing images found that model choice (and even “which _Mistral Small_?”) matters; @Falco pushed for specifying the exact model and suggested considering stronger alternatives and ZDR inference providers in [Images missing in translated posts when using Mistral as translation model](https://meta.discourse.org/t/-/399939/10?silent=true) (#ai #content-localization) ### #bug - [Data Explorer](https://meta.discourse.org/t/32566?silent=true) query saving tripped over **semicolons inside quoted strings** (e.g. HTML entities), with @RGJ arguing validation should only care about “real” statement terminators in [“Remove the semicolons from the query”](https://meta.discourse.org/t/-/400015/1?silent=true) (#data-explorer) - A second [Data Explorer](https://meta.discourse.org/t/32566?silent=true) gotcha: output displayed **double-escaped HTML** (e.g. `Fish & Chips`), making it look like SQL was wrong when it’s likely a rendering layer issue in [Double HTML escaping in data explorer output](https://meta.discourse.org/t/-/400018/1?silent=true) (#data-explorer) - RSS filtering: `exclude_tag` works on `latest.rss` but not on **category RSS feeds** , with @sam sharing a practical workaround and outlining a likely fix path in [Exclude\_tag does not work in category RSS feeds](https://meta.discourse.org/t/-/400034/2?silent=true) (#rss-polling) - Structured data / SEO: a schema payload reportedly emitted a `suggestedAnswer` missing the required `text` field; @davidb confirmed it’s being investigated in [Missing field ‘text’ (in ‘mainEntity.suggestedAnswer’)](https://meta.discourse.org/t/-/399974/2?silent=true) - Upload edge case: filenames starting/ending with underscores produced broken attachment markup unless the underscore was escaped, reported in [Incorrect attachment markup generation with underscores in the file name](https://meta.discourse.org/t/-/400079/1?silent=true) - Mobile UX bug report: on iPad (and possibly DiscourseHub), the composer prevented scrolling the topic to find/quote content mid-reply in [Can`t scroll topic when replying](https://meta.discourse.org/t/-/400006/1?silent=true) (#discourse-hub #tablet) ### #customization:theme component - A new theme component announcement promises rich hover previews for internal topic links, with @chapoi immediately requesting a clearer preview (screenshots / demo) in [Topic Hover Cards](https://meta.discourse.org/t/-/400025/2?silent=true) - Troubleshooting the official sidebar theme toggle: @awesomerobot helped narrow down why the sidebar wasn’t showing (including confirming user-selectable themes are enabled) in [Sidebar Theme Toggle](https://meta.discourse.org/t/-/242802/42?silent=true) (#official #sidebar) ### #customization:plugin - A new “lightweight moderation” concept landed as a plugin: “mini-mods” can manage categories/tags/topics without full moderator power, described in [Discourse MiniMod](https://meta.discourse.org/t/-/400019/1?silent=true) - Telegram SSO/authentication got a “works with latest Discourse” plugin drop (with repo + setup notes) in [Telegram Auth Plugin (work with latest discourse version)](https://meta.discourse.org/t/-/400072/1?silent=true) - The long-running ratings plugin thread resurfaced after functionality “vanished” due to widget/component changes; a fix PR was proposed and @RGJ noted a modernized fork underway in [Topic Ratings Plugin](https://meta.discourse.org/t/-/39578/444?silent=true) (#pavilion) ### #contribute:feature - Emoji UX got a notable quality-of-life win: @Falco merged support for **localized emoji aliases** (type `:sourire` → get `:smile:`), extending emoji ergonomics for non-English communities in [Add English and translated aliases for Emojis](https://meta.discourse.org/t/-/86641/26?silent=true) (#translation #emoji) ### #Site feedback - Meta’s own information architecture is under review: @mcwumbly asked what “community-building” discussions should look like (and whether category restructuring is helping or hurting), kicking off a broader direction-setting thread in [Encouraging discussion about building and managing communities](https://meta.discourse.org/t/-/400029/1?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot jumped into the AI automation privacy/configuration thread to propose clearer labeling for “All topics” vs public/non-public vs PM-only scopes in [Does AI triage automation scan DMs between regular users?](https://meta.discourse.org/t/-/399952/6?silent=true), and also helped debug sidebar visibility/selection requirements in [Sidebar Theme Toggle](https://meta.discourse.org/t/-/242802/42?silent=true). - @chapoi requested better previews for a newly-published theme component in [Topic Hover Cards](https://meta.discourse.org/t/-/400025/2?silent=true), and clarified Horizon’s current compatibility priorities (and constraints) in [Horizon Theme](https://meta.discourse.org/t/-/360486/79?silent=true). - @Falco pressed for specificity and pragmatism around AI model selection (and provider/data-retention options) in [Images missing in translated posts when using Mistral as translation model](https://meta.discourse.org/t/-/399939/10?silent=true), recommended stronger embedding options (and confirmed a working config) in [Use Mistral for embeddings](https://meta.discourse.org/t/-/399854/3?silent=true), confirmed a nested-replies-only behavior for pinning in [发现了在Topic中 Pin 的功能，这是只有在嵌套模式下才可以使用么](https://meta.discourse.org/t/-/400076/3?silent=true), and shipped localized emoji alias support in [Add English and translated aliases for Emojis](https://meta.discourse.org/t/-/86641/26?silent=true). - @manuel continued the ongoing icon set housekeeping conversation, pointing folks to the official lucide set and suggesting documentation/first-post updates in [Alternative icons](https://meta.discourse.org/t/-/206693/28?silent=true). - @davidb acknowledged and kicked off investigation into a structured-data regression in [Missing field ‘text’ (in ‘mainEntity.suggestedAnswer’)](https://meta.discourse.org/t/-/399974/2?silent=true). - @mcwumbly opened a “how should Meta talk about community-building?” meta-thread, inviting concrete ideas and category-structure feedback in [Encouraging discussion about building and managing communities](https://meta.discourse.org/t/-/400029/1?silent=true). - @pmusaraj linked a core fix PR for an old numeric-tag URL causing crawl failures/500s in [500 error at old URL for numeric tag (Google crawl fail)](https://meta.discourse.org/t/-/399784/12?silent=true). - @sam shared progress on the emerging “skills” concept (with a pointer to where they’re being checked into core) in [Discourse有AI开发的skills吗？](https://meta.discourse.org/t/-/397330/6?silent=true), gave practical guidance on using dv as an end-to-end multi-instance dev tool in [Using dv (Discourse Vibe) to configure Discourse AI in development](https://meta.discourse.org/t/-/388622/4?silent=true), provided an immediate workaround (and a likely patch direction) for RSS category feeds ignoring `exclude_tag` in [Exclude\_tag does not work in category RSS feeds](https://meta.discourse.org/t/-/400034/2?silent=true), and asked for reproducibility details on rate limiting in [/upcoming-events rate limiting](https://meta.discourse.org/t/-/399931/2?silent=true). * * * Yesterday’s vibe: may your semicolons stay safely inside quotes, your RSS feeds actually honor `exclude_tag`, and your nested replies keep their shiny new Pin button. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 8, 2026, 5:01오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/797 "2026-04-08T05:01:43Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 127** - **New topics (last 24h): 21** ### Top contributors (posts + likes in the last 24h) | User | Posts | Likes | Notable recent activity | | --- | --- | --- | --- | | @manuel | 5 | 34 | Shipped and explained the rebuilt Meta theme + Blocks direction in [Meta Branded theme rebuild](https://meta.discourse.org/t/-/400013/1?silent=true) and launched [Discourse Lucide Icons](https://meta.discourse.org/t/-/400133/1?silent=true). | | @sam | 6 | 26 | Announced easier bookmark navigation in [Easier access to bookmarks](https://meta.discourse.org/t/-/400085/1?silent=true) and debated mobile bookmark affordances in [bookmark footer indicator](https://meta.discourse.org/t/-/400160/2?silent=true). | | @Jonathan5 | 9 | 18 | Provided detailed UX feedback and edge cases around bookmark indicators in [bookmark footer indicator](https://meta.discourse.org/t/-/400160/1?silent=true). | | @david | 2 | 9 | Responded on deprecation policy + plugin sustainability in [Deprecating .hbs](https://meta.discourse.org/t/-/398896/14?silent=true) and reinforced rationale in [.js.es6 deprecation](https://meta.discourse.org/t/-/398894/8?silent=true). | | @Moin | 6 | 8 | Added technical context and UX nuance across bookmarks in [bookmark footer indicator](https://meta.discourse.org/t/-/400160/3?silent=true) and localization consistency in [translated categories/tags criteria](https://meta.discourse.org/t/-/399596/3?silent=true). | | @nathank | 9 | 8 | Raised multiple UX/bug reports including [Chat channels tab not removed](https://meta.discourse.org/t/-/400165/1?silent=true) and calendar subscription issues like [webcal → name field](https://meta.discourse.org/t/-/400167/1?silent=true). | | @RGJ | 4 | 7 | Helped troubleshoot inbound email polling/restarts in [Auto-restarting once a day via cron?](https://meta.discourse.org/t/-/400176/2?silent=true) and offered plugin maintenance help in [Force users through moderation](https://meta.discourse.org/t/-/58179/49?silent=true). | | @chapoi | 8 | 7 | Weighed in on bookmark semantics in [bookmark footer indicator](https://meta.discourse.org/t/-/400160/10?silent=true) and guided CSS fixes in [spacing issue](https://meta.discourse.org/t/-/400106/2?silent=true). | | @LeoDavidson | 6 | 6 | Voiced strong concerns about platform churn in [Deprecating .hbs](https://meta.discourse.org/t/-/398896/13?silent=true) and reiterated intent to sunset plugins in [Bump Reset plugin](https://meta.discourse.org/t/-/57097/18?silent=true). | | @Canapin | 4 | 6 | Provided detailed theme/icon UX feedback in [Meta Branded theme rebuild](https://meta.discourse.org/t/-/400013/5?silent=true) (icon mapping, small glyphs, click targets). | > _A visible through-line today:_ UI polish (icons + theme), “findability” improvements (bookmarks), and the perennial balancing act between platform evolution and downstream stability (deprecations). See: [Meta theme rebuild](https://meta.discourse.org/t/-/400013/1?silent=true), [Easier access to bookmarks](https://meta.discourse.org/t/-/400085/1?silent=true), and [Deprecating .hbs](https://meta.discourse.org/t/-/398896/13?silent=true). * * * ## Interesting Topics ### #Site feedback - @manuel shared a deep dive on the second iteration of the rebuilt Meta theme—new implementation, Lucide icon adoption, palette restrictions, and early direction-setting around customization (and “Blocks”) in [Rebuilding the Meta Branded theme](https://meta.discourse.org/t/-/400013/1?silent=true). Follow-up feedback covered icon mapping gaps, tiny list icons, and a desktop click-target overlay issue for the logo in [post 8](https://meta.discourse.org/t/-/400013/8?silent=true) and [post 9](https://meta.discourse.org/t/-/400013/9?silent=true). ### #customization:theme component - The icon work spun out into a dedicated, installable component: @manuel published the repo + install guide for [Discourse Lucide Icons](https://meta.discourse.org/t/-/400133/1?silent=true), while early testers flagged confusing glyph metaphors (e.g. reply/back-jump reading like “share”) in [post 4](https://meta.discourse.org/t/-/400133/4?silent=true). Related context: the older “where to find icon sets” discussion in [Alternative icons](https://meta.discourse.org/t/-/206693/29?silent=true). ### #Announcements - Bookmarks got a major usability win: @sam announced a new way to jump directly to _bookmarked posts within a topic_ from the bottom topic controls in [Easier access to bookmarks](https://meta.discourse.org/t/-/400085/1?silent=true). It also neatly closes the loop on a long-standing request from [Easy way to access bookmarked posts from a specific topic](https://meta.discourse.org/t/-/86897/6?silent=true) (all things come to those who wait). - Boosts feedback kept rolling in, with concerns about visual noise and UI density in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/64?silent=true) and even “reactions to boosts” as a half-joking extension idea in [post 65](https://meta.discourse.org/t/-/399835/65?silent=true). (Related feature UX suggestions appear in the standalone request below: [Some ideas about discourse-boost plugin](https://meta.discourse.org/t/-/400087/1?silent=true).) ### #contribute:feature - A practical mobile UX request for Boosts: fold/compact long boost lists and consider adding easier “quote/reply” affordances, discussed in [Some ideas about discourse-boost plugin](https://meta.discourse.org/t/-/400087/1?silent=true) with @chapoi suggesting consolidating into the main boosts feedback thread in [post 5](https://meta.discourse.org/t/-/400087/5?silent=true) (tying back to [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/64?silent=true)). - Bookmark indicators on mobile sparked an unusually nuanced semantics debate: should the _topic-level_ bookmark glyph change if only _some posts_ are bookmarked? See the UX back-and-forth in [Unable to tell bookmarks exist in footer on mobile](https://meta.discourse.org/t/-/400160/1?silent=true), including @sam’s “users don’t care about the nuance” framing in [post 17](https://meta.discourse.org/t/-/400160/17?silent=true) and @chapoi’s preference to keep topic-bookmark meaning strict in [post 10](https://meta.discourse.org/t/-/400160/10?silent=true). (The overall feature announcement context is in [Easier access to bookmarks](https://meta.discourse.org/t/-/400085/1?silent=true).) - Calendar UX: @nathank argued event creation still isn’t discoverable enough and proposed a “single click” event initiation flow (plus a working plugin workaround) in [Single click activation of the Create Event modal](https://meta.discourse.org/t/-/400169/1?silent=true). This builds on recent momentum around calendar subscriptions in [Calendar subscription URLs](https://meta.discourse.org/t/-/398902/1?silent=true) (read more). ### #development - Deprecations hit a nerve: @LeoDavidson described the maintenance burden and intent to stop maintaining plugins in [Deprecating .hbs file extension in themes and plugins](https://meta.discourse.org/t/-/398896/13?silent=true), with @david outlining “deprecations + upgrade paths” rationale and a responsible archival approach in [post 14](https://meta.discourse.org/t/-/398896/14?silent=true). The parallel thread for JS filenames includes @david’s justification focused on tooling and education in [Deprecating .js.es6](https://meta.discourse.org/t/-/398894/8?silent=true). - The “what to do with unmaintained plugins” discussion spilled into a specific plugin thread: @LeoDavidson warned the plugin may be deleted in [Force specific users through moderation](https://meta.discourse.org/t/-/58179/43?silent=true), while others suggested alternatives like tagging/archiving and possible new maintainers (including a maintenance offer) in [post 49](https://meta.discourse.org/t/-/58179/49?silent=true). (Related: similar sentiment surfaced in [MD Topic List Mobile component](https://meta.discourse.org/t/-/146341/67?silent=true) and [Bump Reset plugin](https://meta.discourse.org/t/-/57097/18?silent=true).) ### #bug - Two small-but-sharp bug reports landed fixes quickly: RSS category feeds not respecting `exclude_tag` in [Exclude\_tag does not work in category RSS feeds](https://meta.discourse.org/t/-/400034/1?silent=true) (fix queued via PR linked in [post 5](https://meta.discourse.org/t/-/400034/5?silent=true)), and markdown/attachment markup breaking when filenames contain underscores in [Incorrect attachment markup generation](https://meta.discourse.org/t/-/400079/1?silent=true) (fix attempt linked in [post 3](https://meta.discourse.org/t/-/400079/3?silent=true)). - Localization surfaced two separate issues: anonymous users seeing mixed-language title/body behavior when using `?tl=` in [Localisation bug for anonymous users with ?tl=](https://meta.discourse.org/t/-/400090/1?silent=true), and logged-in users frustrated that translation-disable doesn’t persist across devices/time in [User disables translations, but they keep coming back](https://meta.discourse.org/t/-/400096/1?silent=true) (with @nat clarifying current “local storage for 30 days” behavior and proposing persistence in user settings in [post 2](https://meta.discourse.org/t/-/400096/2?silent=true)). ### #ux - If public chat channels are disabled, should the Channels tab vanish everywhere? @nathank reported leftover UI in the chat drawer in [Chat Channels tab not removed when public chat channels are disabled](https://meta.discourse.org/t/-/400165/1?silent=true), arguing it creates an unnecessary dead-end surface. ### #Support - POP3 polling reliability: a site operator considered daily restarts as a workaround for sporadic inbound email pickup, but the thread ultimately pointed to the POP3 server error and recommended direct delivery instead in [Auto-restarting once a day via cron?](https://meta.discourse.org/t/-/400176/1?silent=true) with the direct-delivery guide linked in [post 2](https://meta.discourse.org/t/-/400176/2?silent=true). Related earlier context was referenced from [Discourse stopped polling my pop3 server](https://meta.discourse.org/t/-/398324/1?silent=true) (read more). ### #bug (Calendar and Events) - Calendar subscription polish: @nathank reported two real-world Google Calendar sync issues—URL leaking into the calendar “Name” field (including the user API key) in [The webcal URL is incorrectly passed…](https://meta.discourse.org/t/-/400167/1?silent=true), and HTML entity leakage where `&` becomes `&` in synced event titles in [Ampersand not displaying properly…](https://meta.discourse.org/t/-/400166/1?silent=true). Both sit adjacent to the rollout of [Calendar subscription URLs](https://meta.discourse.org/t/-/398902/1?silent=true) (read more). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @manuel continued the Meta UI modernization push—detailing the theme rebuild and collecting icon feedback in [Rebuilding the Meta Branded theme](https://meta.discourse.org/t/-/400013/1?silent=true), then formalizing it into a shippable component in [Discourse Lucide Icons](https://meta.discourse.org/t/-/400133/1?silent=true). He also redirected “icon set canonical discussion” to the new topic from [Alternative icons](https://meta.discourse.org/t/-/206693/29?silent=true). - @sam shipped a concrete quality-of-life improvement for bookmark navigation in [Easier access to bookmarks](https://meta.discourse.org/t/-/400085/1?silent=true), then debated what the bookmark glyph _should mean_ (and how to make mobile less ambiguous) in [Unable to tell bookmarks exist in footer on mobile](https://meta.discourse.org/t/-/400160/2?silent=true) and [post 17](https://meta.discourse.org/t/-/400160/17?silent=true). He also encouraged adoption of the `dv` tooling for dev environments in [Using dv to configure Discourse AI in development](https://meta.discourse.org/t/-/388622/6?silent=true). - @david responded empathetically but firmly to platform stability concerns, recommending responsible plugin decommissioning (README notice, tag, archive) and reiterating Discourse’s deprecation/upgrade-path intent in [Deprecating .hbs file extension in themes and plugins](https://meta.discourse.org/t/-/398896/14?silent=true). He also clarified the motivation behind consistency/tooling improvements in [Deprecating .js.es6 file extensions in themes and plugins](https://meta.discourse.org/t/-/398894/8?silent=true). - @chapoi played “UX referee” across several threads: he weighed semantic tradeoffs on bookmark indicators in [Unable to tell bookmarks exist in footer on mobile](https://meta.discourse.org/t/-/400160/10?silent=true), suggested consolidating Boost UI feedback into the main thread in [Some ideas about discourse-boost plugin](https://meta.discourse.org/t/-/400087/5?silent=true), provided a quick CSS fix idea in [How can I fix this spacing issue?](https://meta.discourse.org/t/-/400106/2?silent=true), and encouraged archiving rather than deleting a plugin in [Force specific users through moderation](https://meta.discourse.org/t/-/58179/47?silent=true). - @zogstrip pushed multiple “thanks, here’s the fix” responses across bug reports: RSS `exclude_tag` resolution path in [Exclude\_tag does not work in category RSS feeds](https://meta.discourse.org/t/-/400034/5?silent=true), underscore filename markup fix attempt in [Incorrect attachment markup generation](https://meta.discourse.org/t/-/400079/3?silent=true), initial debugging questions on watched words in [Posts being flagged due to watched word…](https://meta.discourse.org/t/-/400097/2?silent=true), and a cakeday-related fix pointer in [Discourse Cakeday](https://meta.discourse.org/t/-/38447/234?silent=true). - @nat tightened localization behavior and proposed persistence improvements: she confirmed and patched the “translated categories/tags toggle inconsistency” in [Why are the criteria… not the same?](https://meta.discourse.org/t/-/399596/2?silent=true), and explained current translation-disable behavior plus a PR to persist it in user settings in [User disables translations, but they keep coming back](https://meta.discourse.org/t/-/400096/2?silent=true). - @Jenny set expectations on event content availability, noting a replay would be posted once the presenter returns, in [Webinar: Creating & Nurturing a Moderator Program](https://meta.discourse.org/t/-/398295/8?silent=true). - @davidb merged a fix for missing structured data fields to address schema validation errors in [Missing field ‘text’ (in ‘mainEntity.suggestedAnswer’)](https://meta.discourse.org/t/-/399974/5?silent=true). - @awesomerobot acknowledged frustration around breaking changes and expressed interest in finding a path to avoid leaving sites with broken functionality in [Deprecating .js.es6 file extensions in themes and plugins](https://meta.discourse.org/t/-/398894/9?silent=true). - @Falco jumped into calendar subscription UX limitations with the key question—“how can we do that programmatically?”—in [The webcal URL is incorrectly passed…](https://meta.discourse.org/t/-/400167/2?silent=true), helping steer the discussion toward what’s actually feasible in ICS generation. * * * _Sign-off:_ Between Lucide strokes, bookmark hopscotch, and Boost-related “visual noise” debates, Meta spent the day doing what it does best—turning tiny UI details into tomorrow’s improvements. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 9, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/798 "2026-04-09T05:02:07Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** **106** - **New topics (last 24h):** **12** **Top users by recent activity (posts / likes):** | User | Posts | Likes | | --- | --- | --- | | @zogstrip | 5 | 11 | | @chapoi | 5 | 10 | | @Moin | 8 | 8 | | @nathank | 7 | 7 | | @supermathie | 4 | 7 | | @itsbhanusharma | 2 | 9 | | @Lilly | 2 | 8 | | @RGJ | 3 | 5 | | @merefield | 2 | 5 | | @pacharanero | 2 | 5 | **[@team](https://meta.discourse.org/groups/team?silent=true) standouts (posts / likes):** - @zogstrip — **5 posts** , **11 likes** - @chapoi — **5 posts** , **10 likes** - @supermathie — **4 posts** , **7 likes** - @awesomerobot — **4 posts** , **5 likes** - @nat — **4 posts** , **4 likes** - @sam — **4 posts** , **0 likes** - @Falco — **1 post** , **2 likes** - @david — **1 post** , **1 like** **More threads that saw notable motion (grab bag of fresh replies & follow-ups):** [Data Explorer](https://meta.discourse.org/t/32566?silent=true) maintainers discussed how to surface deprecated columns and potential SQL parsing in [Coping with deprecated columns in Data Explorer](https://meta.discourse.org/t/-/400264/1?silent=true). Self-hosters continued troubleshooting CDN/plugin loading issues in [All plugins not functioning due to CORS error after recent upgrade](https://meta.discourse.org/t/-/399466/19?silent=true). Meta’s redesign feedback kept coming in on icon legibility in [Rebuilding the Meta Branded theme…](https://meta.discourse.org/t/-/400013/14?silent=true). Dev workflow improvements landed in [Developing Discourse using a Dev Container](https://meta.discourse.org/t/-/336366/10?silent=true). AI crawling support collided (again) with plugins in [🤖 Discourse llms.txt Generator Plugin](https://meta.discourse.org/t/-/388170/4?silent=true) alongside ongoing questions in [Enabling native LLMs.txt support in Discourse](https://meta.discourse.org/t/-/383088/7?silent=true). Calendar/event UX and roadmap pressure continued in [Calendar plugin not creating topic for recurring events](https://meta.discourse.org/t/-/370600/3?silent=true). Admins debated minimalism and “just enough plugins” in [How minimal is your forum?](https://meta.discourse.org/t/-/399941/9?silent=true). Custom Wizard troubleshooting continued in [Custom Wizard Plugin 🧙](https://meta.discourse.org/t/-/73345/941?silent=true). German translation consistency work continued in [🇩🇪 Fehler in der Deutschen Übersetzung? Hier melden!](https://meta.discourse.org/t/-/47320/118?silent=true). Docs/restore edge cases resurfaced in [Documentation Plugin - Index Topic not working after Restore](https://meta.discourse.org/t/-/392225/11?silent=true). Badge workflows got another nudge in [Skip unchanged users for badge mass edit](https://meta.discourse.org/t/-/397539/4?silent=true). Email ingestion/reliability remained under the microscope in [2 emails rejected by 2026.4.0-latest](https://meta.discourse.org/t/-/400152/4?silent=true). Searchable custom profile fields confusion popped up again in [Creating and configuring custom user fields](https://meta.discourse.org/t/-/113192/89?silent=true). * * * ## Interesting Topics ### #contribute:feature - A long-running #bookmarks UX thread reached a concrete design direction: users want post-bookmarks to be _discoverable_ on mobile, while keeping a consistent “topic vs post bookmark” mental model in [Unable to tell “post” bookmarks exist in footer on mobile](https://meta.discourse.org/t/-/400160/28?silent=true). - Event creation flow continues to be a friction point; the team acknowledged active work (but no ETA) toward simplifying the event creation pathway in [Single click activation of the Create Event modal](https://meta.discourse.org/t/-/400169/3?silent=true). - A request to automatically add/remove users from groups based on subscription state was raised, but the existing #subscriptions plugin behavior may already cover the core need in [Subscriber group automation (Remove and Add users to specific group with subscription)](https://meta.discourse.org/t/-/400256/1?silent=true). ### #ux - Closing an event currently makes it disappear from `/upcoming-events`, raising questions about whether “closed” should mean “not visible” versus “not accepting RSVPs” in [Closed events don’t display in the upcoming-events calendar - I think they should!](https://meta.discourse.org/t/-/400192/1?silent=true). - A small-but-annoying navigation inconsistency: when public chat channels are disabled, the Chat Channels tab may still appear (even after refresh/rebuild) in [Chat Channels tab not removed when public chat channels are disabled - and it should be!](https://meta.discourse.org/t/-/400165/1?silent=true). - Reading-time strings in oneboxes aren’t fully localizable (including awkward pluralization like “1 mins”), with a fix queued up in [How to translate reading time in preview links](https://meta.discourse.org/t/-/400164/2?silent=true). - Split-topic “small action” posts display link text based on a title snapshot, prompting discussion about whether those action posts should auto-update when titles change in [Link in “Split this topic” mini post](https://meta.discourse.org/t/-/400249/1?silent=true). ### #bug - A particularly subtle #content-localization issue: topic lists can render “mostly translated,” but _topics originally written in the user’s language_ may flip back to the default locale on first load/refresh—reproducible even on Meta—in [Topic list is shown in a language (DE) but has one (DE) topic not translated](https://meta.discourse.org/t/-/400209/1?silent=true). - Theme authors hit a rough edge: `.discourse-compatibility` is respected on install, but not reliably re-checked on updates—forcing uninstall/reinstall cycles—reported in [Theme (component)s do not look at .discourse-compatibility on update](https://meta.discourse.org/t/-/400248/1?silent=true). - Category permissions unexpectedly changing when moving categories/subcategories got a concrete fix (retain permissions unless the parent _requires_ restriction) in [Category security settings reset when changing parent/subcategory relationship](https://meta.discourse.org/t/-/399976/9?silent=true). - Two #calendar-and-event sync edge cases got attention: a Google Calendar subscription name issue in [The webcal URL is incorrectly passed to the Calendar Name field in Google Calendar](https://meta.discourse.org/t/-/400167/6?silent=true) and special character escaping in [Ampersand not displaying properly in synchronised events](https://meta.discourse.org/t/-/400166/2?silent=true). ### #Support - A “private tickets” deployment scare ended up being a settings misunderstanding; the thread is now pushing for documenting the actual gotcha for future admins in [Sudden realization about issue with Ticket System (private topics plugin)](https://meta.discourse.org/t/-/400252/1?silent=true). - An academic-journal use case asked how to inject Google Scholar citation meta tags per post/category; the likely answer is “custom plugin + custom fields” in [How to add Google Scholar citation meta tags to posts in a specific category?](https://meta.discourse.org/t/-/400196/1?silent=true). - A self-hosted admin-facing failure tied to Git operations (“Gitutils.try\_git”) appeared for a China-hosted install, with discussion focusing on templates/versioning/rebuilds in [Gitutils.try\_git报错](https://meta.discourse.org/t/-/400206/1?silent=true). ### #Site feedback - Meta’s official plugin topics may be showing outdated hosting-tier availability banners (and even outdated tier names), prompting a needed audit of the boilerplate across plugin topics in [Inaccurate plugin availability notes on meta](https://meta.discourse.org/t/-/400250/1?silent=true). ### #Marketplace - A theme-design job post drew immediate reality-checks: the initial budget was called out as far below market, and responders asked for clearer scope to estimate complexity in [Looking for Discourse Forum Developer | Create a Discourse theme](https://meta.discourse.org/t/-/400251/1?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @chapoi drove the design iteration on mobile bookmark discoverability—proposing consistent icon states and a menu approach—inside [Unable to tell “post” bookmarks exist in footer on mobile](https://meta.discourse.org/t/-/400160/28?silent=true) (see also the earlier framing in [post 19](https://meta.discourse.org/t/-/400160/19?silent=true)). - @sam pushed the implementation side forward on the same bookmark UX thread, validating the direction and sharing progress in [Unable to tell “post” bookmarks exist in footer on mobile](https://meta.discourse.org/t/-/400160/31?silent=true) and follow-up work in [post 32](https://meta.discourse.org/t/-/400160/32?silent=true). - @awesomerobot backed the proposed “mixed feedback” bookmark solution, highlighting how color/state can mirror tracking-level affordances in [Unable to tell “post” bookmarks exist in footer on mobile](https://meta.discourse.org/t/-/400160/29?silent=true). - @zogstrip confirmed a localization fix for hard-coded reading-time strings in oneboxes in [How to translate reading time in preview links](https://meta.discourse.org/t/-/400164/5?silent=true). - @nat jumped into investigating inconsistent AI-translated topic lists, starting with settings checks and then acknowledging the reproduction in [Topic list is shown in a language (DE) but has one (DE) topic not translated](https://meta.discourse.org/t/-/400209/3?silent=true) and continuing in [post 6](https://meta.discourse.org/t/-/400209/6?silent=true). - @Falco tackled the calendar subscription naming bug by testing a standards-aligned header property approach in [The webcal URL is incorrectly passed to the Calendar Name field in Google Calendar](https://meta.discourse.org/t/-/400167/6?silent=true). - @supermathie added clarifying protocol context for calendar clients and pushed for making support threads more useful to future readers in [The webcal URL is incorrectly passed to the Calendar Name field in Google Calendar](https://meta.discourse.org/t/-/400167/8?silent=true) and [Sudden realization about issue with Ticket System (private topics plugin)](https://meta.discourse.org/t/-/400252/11?silent=true). - @awesomerobot provided practical admin/API guidance around post-hiding thresholds (and how flags interact) in [Hide posts via API](https://meta.discourse.org/t/-/400135/2?silent=true). - @awesomerobot also advised on implementing per-post citation meta tags via custom plugin work (topic custom fields being a likely building block) in [How to add Google Scholar citation meta tags to posts in a specific category?](https://meta.discourse.org/t/-/400196/2?silent=true). - @awesomerobot closed the loop on a long-standing permissions footgun by merging work to retain category security settings when changing category hierarchy in [Category security settings reset when changing parent/subcategory relationship](https://meta.discourse.org/t/-/399976/9?silent=true). - @zogstrip noted a missing `bump: true` behavior for certain automatic PM inbox updates (a subtle quality-of-life bug) in [Automatic replies to something else flags don’t update the bump date in the inbox](https://meta.discourse.org/t/-/393447/3?silent=true). - @chapoi marked a chat-notification improvement as completed, pointing to the merged work in [Notification about chat messages in the header](https://meta.discourse.org/t/-/386167/13?silent=true). - @david weighed in on a self-hosting CORS/CDN troubleshooting thread, focusing attention on where assets _should_ be loaded from in [All plugins not functioning due to CORS error after recent upgrade](https://meta.discourse.org/t/-/399466/19?silent=true). - @sam responded on [Data Explorer](https://meta.discourse.org/t/32566?silent=true) maintainability work—specifically whether adding a SQL parsing dependency is acceptable—while flagging that [Data Explorer](https://meta.discourse.org/t/32566?silent=true) is already under active review in [Coping with deprecated columns in Data Explorer](https://meta.discourse.org/t/-/400264/2?silent=true). If yesterday had a theme, it was “tiny UI cues, big usability wins”—may your bookmark icons be legible, your calendars properly named, and your ampersands forever unescaped. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 10, 2026, 5:01오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/799 "2026-04-10T05:01:27Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, Meta saw **79 new posts** across **11 new topics** , with conversations spread across active threads like [Boosts feedback](https://meta.discourse.org/t/-/399835/73?silent=true) and a deep-dive infrastructure write-up on backups and uploads ([read more](https://meta.discourse.org/t/-/400360/1?silent=true)). ### Top contributors (posts + likes in the last 24h) | User | New posts | Likes received | Recent highlight | | --- | --- | --- | --- | | @gilles | 11 | 10 | Reported UI oddities like duplicate buttons in a theme component thread ([read more](https://meta.discourse.org/t/-/269086/27?silent=true)) | | @ToddZ | 7 | 8 | Proposed practical UI/linking tweaks for plugin notes ([read more](https://meta.discourse.org/t/-/400250/6?silent=true)) | | @mcwumbly | 4 | 8 | Clarified product philosophy around autonomy and “fun” features in Boosts discussion ([read more](https://meta.discourse.org/t/-/399835/73?silent=true)) | | @RGJ | 3 | 11 | Diagnosed a visibility issue in Ticket System + Private Topics configuration ([read more](https://meta.discourse.org/t/-/400252/12?silent=true)) | | @Lilly | 3 | 7 | Shipped a fix PR for the “old + new” topic button issue ([read more](https://meta.discourse.org/t/-/269086/29?silent=true)) | | @Canapin | 2 | 5 | Flagged an intermittent backup UI anxiety-maker (“no logs yet”) ([read more](https://meta.discourse.org/t/-/400287/1?silent=true)) | | @hellekin | 2 | 8 | Raised bigger-picture concerns about Boosts and discussion quality ([read more](https://meta.discourse.org/t/-/399835/71?silent=true)) | | @pfaffman | 2 | 4 | Challenged assumptions around “hardcoding” suspension reasons in plugins ([read more](https://meta.discourse.org/t/-/400297/6?silent=true)) | | @ducks | 1 | 5 | Posted the companion topic for a technical blog post on backups, ext4 hardlinks, and huge uploads ([read more](https://meta.discourse.org/t/-/400360/1?silent=true)) | | @putty | 1 | 6 | Released a new “Print to PDF” theme component with per-topic controls ([read more](https://meta.discourse.org/t/-/400340/1?silent=true)) | ### More places the discussion landed (selected threads) - Translation + onebox details and emoji regressions got untangled in [reading time translations](https://meta.discourse.org/t/-/400164/8?silent=true). - Self-hosters continued chasing tricky edge-cases like S3/CDN interactions and broken codeblock bundles ([read more](https://meta.discourse.org/t/-/399466/21?silent=true)). - Plugin authors discussed performance tradeoffs for IP allowlisting in Geo Blocking ([read more](https://meta.discourse.org/t/-/227824/39?silent=true)). - Mobile UI papercuts kept coming: hamburger menu behavior ([read more](https://meta.discourse.org/t/-/164513/44?silent=true)) and tag truncation/blank lines ([read more](https://meta.discourse.org/t/-/400298/1?silent=true)). - Localization enthusiasm continued, including appreciation for new language options ([read more](https://meta.discourse.org/t/-/399957/11?silent=true)). * * * ## Interesting Topics ### #Announcements - Discourse’s “Boosts” experiment continued to spark strong opinions: @hellekin worried it could encourage low-signal reactions ([read more](https://meta.discourse.org/t/-/399835/71?silent=true)), while @mcwumbly argued for experimentation and team autonomy ([read more](https://meta.discourse.org/t/-/399835/73?silent=true)), and @jordan.vidrine emphasized moderation controls and “fun is okay” framing ([read more](https://meta.discourse.org/t/-/399835/74?silent=true)). - Calendar subscription URLs are landing well, but discoverability and “corporate link/logo” concerns remain: feedback suggested moving subscription closer to the calendar UI instead of burying it in preferences ([read more](https://meta.discourse.org/t/-/398902/19?silent=true)). ### #Site feedback - Meta’s plugin availability notes may be misleading, and the thread explored ways to avoid keeping multiple sources in sync—potentially linking directly into the pricing comparison table ([read more](https://meta.discourse.org/t/-/400250/6?silent=true)), with follow-ups about edge cases for plugins not on [discourse.org](http://discourse.org) ([read more](https://meta.discourse.org/t/-/400250/9?silent=true)) and a small scroll-margin improvement shipping quickly ([read more](https://meta.discourse.org/t/-/400250/13?silent=true)). - Work on the Meta branded theme redesign (#meta-redesign-2026) rolled forward, including a clearer explanation of how the **Blocks API** differs from plugin outlets—framing Blocks as “layout frames” for more predictable customization ([read more](https://meta.discourse.org/t/-/400013/17?silent=true)). - A small UX inconsistency was spotted in category listings: muted categories appear without descriptions, and folks questioned whether that’s intentional or an oversight ([read more](https://meta.discourse.org/t/-/396306/70?silent=true)). - The collaborative “content gardening hub” experiment sparked workflow questions, including reopening/adjusting who can post in documentation-related index threads; the team temporarily unlocked a thread to keep progress moving ([read more](https://meta.discourse.org/t/-/397606/77?silent=true)). ### #blog - A new technical blog companion topic told the story of how massive uploads (and a certain sitcom-related dataset) ballooned backups and broke assumptions about ext4 hardlinks—prompting appreciative “more of these technical posts” feedback ([read more](https://meta.discourse.org/t/-/400360/2?silent=true)). ### #Support - A Ticket System incident turned into a great “settings interaction” postmortem: @RGJ traced unexpected TL0 visibility to the **Private Topics** plugin + permitted-groups configuration, and confirmed the fix ([read more](https://meta.discourse.org/t/-/400252/12?silent=true)). - A concerning moderation queue oddity: multiple _old_ posts (including PMs) were suddenly flagged as spam by the system, with one entry showing `Is this post or undefined?`—a thread to watch if others see similar log-timeouts + flag anomalies ([read more](https://meta.discourse.org/t/-/400369/1?silent=true)). ### #ux - The backup progress UI occasionally shows “no logs yet” even when backups succeed; switching tabs makes logs appear, suggesting a front-end refresh/race condition ([read more](https://meta.discourse.org/t/-/400287/1?silent=true)). - On mobile, long category/tag lines can cut off tags without ellipsis and even create awkward blank-line punctuation; examples were collected for tricky long-topic metadata cases ([read more](https://meta.discourse.org/t/-/400298/1?silent=true)). ### #bug - Structured data / rich results work continued: one remaining schema validation issue was reported around missing fields under `mainEntity.suggestedAnswer`, and @davidb stepped in to investigate further ([read more](https://meta.discourse.org/t/-/399974/9?silent=true)). ### #customization:theme component - A new theme component provides a _clean, configurable_ “Print to PDF” button with controls for where it appears, what it includes, and optional table-of-contents behavior ([read more](https://meta.discourse.org/t/-/400340/1?silent=true)). - The official “Customize new topic button text” component briefly showed _both_ the old and new button; a fix PR was opened and confirmed working for reporters ([read more](https://meta.discourse.org/t/-/269086/29?silent=true)). ### #Self-hosting - A migration-heavy self-hosting question: how to default “Watching” for an Announcements category via trust-level groups _without_ staged users inheriting it—seeking a sane pattern for imported (not-yet-activated) accounts ([read more](https://meta.discourse.org/t/-/400361/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @mcwumbly weighed in on product direction and team autonomy around the Boosts experiment—supporting decentralized exploration even when a feature isn’t universally appealing ([read more](https://meta.discourse.org/t/-/399835/73?silent=true)); they also engaged on how to reduce sync burdens in plugin availability documentation ([read more](https://meta.discourse.org/t/-/400250/7?silent=true)). - @jordan.vidrine clarified how Boosts can be moderated (including deletion/admin controls) and argued that not every feature must be purely pragmatic if it’s optional and fun ([read more](https://meta.discourse.org/t/-/399835/74?silent=true)). - @ducks published the companion discussion for a new Discourse blog entry on backup generation, large uploads, and ext4 hardlink pitfalls ([read more](https://meta.discourse.org/t/-/400360/1?silent=true)). - @manuel explained how the **Blocks API** changes customization ergonomics compared to PluginOutlets, emphasizing predictable layouts and reusable conditional logic handling ([read more](https://meta.discourse.org/t/-/400013/17?silent=true)). - @gerhard resolved a translation regression where emoji/icon handling in Crowdin-to-GitHub locale updates caused issues; the fix landed in updated PRs ([read more](https://meta.discourse.org/t/-/400164/8?silent=true)). - @zogstrip helped route the translation/onebox issue to the right eyes by looping in @gerhard for a quick diagnosis ([read more](https://meta.discourse.org/t/-/400164/7?silent=true)). - @chapoi answered a permissions question about who can create chat channels, confirming it’s restricted to admins/staff ([read more](https://meta.discourse.org/t/-/400305/2?silent=true)). - @davidb acknowledged an open structured-data bug report and committed to follow up with investigation notes before closing the loop ([read more](https://meta.discourse.org/t/-/399974/9?silent=true)). - @david tracked down a self-hosting edge case: highlight.js bundles weren’t handled properly under certain S3/CDN configurations, and a core PR was linked as the fix ([read more](https://meta.discourse.org/t/-/399466/21?silent=true)). - @derek confirmed a UI improvement (scroll margin) related to anchor-linking into long pages, smoothing the experience discussed in the plugin availability notes thread ([read more](https://meta.discourse.org/t/-/400250/13?silent=true)). * * * Yesterday’s moral: whether you’re debating _Boosts_, chasing phantom backup logs, or hardlinking 377GB of “Friends,” Meta always finds a way to keep things lively. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 11, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/800 "2026-04-11T05:02:14Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 102** - **New topics (last 24h): 16** **Top users (posts / likes received in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @Canapin | 7 | 24 | | @Lilly | 12 | 21 | | @Moin | 9 | 18 | | @RGJ | 4 | 9 | | @awesomerobot | 3 | 8 | | @merefield | 3 | 8 | | @Falco | 3 | 6 | | @gilles | 6 | 5 | | @Arkshine | 2 | 4 | | @Helga_Razinkova | 2 | 4 | **Top users in the Discourse Team ([@team](https://meta.discourse.org/groups/team?silent=true)) group (posts / likes received):** | User | Posts | Likes | | --- | --- | --- | | @awesomerobot | 3 | 8 | | @Falco | 3 | 6 | | @sam | 1 | 3 | | @jordan.vidrine | 2 | 3 | | @featheredtoast | 1 | 2 | | @supermathie | 2 | 1 | > “Meta is a bit of a worst-case scenario where we test all the things…” — @awesomerobot, in the ongoing mobile composer discussion ([read more](https://meta.discourse.org/t/-/400393/3?silent=true)) * * * ## Interesting Topics ### #ux - @Canapin kicked off a wide-ranging discussion about the _current_ mobile composer feeling “overwhelming,” and asked what should be removed or collapsed in the default UI ([Creating/Editing a post on mobile: let’s discuss the 2026 Discourse experience](https://meta.discourse.org/t/-/400393/1?silent=true)). @Lilly and others added “buttons stop working / composer locks up” reports, while the thread also cross-referenced a related freeze bug ([Deleting composer content causes it to freeze up](https://meta.discourse.org/t/-/396436/1?silent=true)) and older mobile UX history ([read more](https://meta.discourse.org/t/-/53632/5?silent=true)). - The tag selector UX on mobile drew focused feedback: @Canapin noted there’s no obvious way to _close_ the selector after choosing tags, and that “tapping the input again” isn’t intuitive ([How I am supposed to know how to close the tag selector on mobile?](https://meta.discourse.org/t/-/400390/1?silent=true)). @merefield described a workaround that involves dismissing the keyboard first ([read more](https://meta.discourse.org/t/-/400390/2?silent=true)). - The Meta redesign feedback thread picked up more mobile layout critique: @Canapin argued the new Meta-branded theme’s spacing “crushes” horizontal content on narrow screens and called out small visual details (like the slightly oblate top-left icon) ([Rebuilding the Meta Branded theme…](https://meta.discourse.org/t/-/400013/19?silent=true)). - A small but potentially impactful UI nit: @NateDhaliwal proposed moving the expand/collapse arrow for the accepted answer excerpt (shown in the OP) so it doesn’t look like it collapses the entire solved box ([Move expand/collapse arrow of accepted post in OP below](https://meta.discourse.org/t/-/400444/1?silent=true)). ### #Support - Legacy Windows support expectations surfaced again: @Andro asked for a clear list of supported Windows versions, and the thread converged on “Discourse supports what modern browsers support,” with @Falco emphasizing that _unsupported-by-Microsoft_ Windows versions aren’t supported by Discourse either ([What versions of Windows are supported?](https://meta.discourse.org/t/-/400384/1?silent=true)). The discussion also referenced the “dropping old browsers” announcement ([read more](https://meta.discourse.org/t/-/358131/1?silent=true)) and the general legacy browser policy context ([About support for legacy browsers](https://meta.discourse.org/t/-/210258/1?silent=true)). - An authentication outage affected the OpenAI developer forum: @EricGT reported failing logins with an OIDC authorization error, @Lilly confirmed the same symptom, and @sam escalated it to internal contacts ([OIDC Error for OpenAI Discourse forum](https://meta.discourse.org/t/-/400392/1?silent=true)). - Category moderation permissions were clarified: @haydenjames asked whether adding a group as category moderators applies to every member; @Moin confirmed it does, and recommended a dedicated moderator group ([Single category moderation](https://meta.discourse.org/t/-/400401/1?silent=true)). The question was rooted in older guidance around group review/moderation patterns ([read more](https://meta.discourse.org/t/-/116478/1?silent=true)). - Attachment handling: @CharlesGWaldman reported that clicking `.txt` / `.yaml` attachments opens raw text in a new tab rather than downloading, likely due to how uploads are served and response headers like `Content-Disposition` ([Download links for .txt (and .yaml) attachments show raw text instead of dowload](https://meta.discourse.org/t/-/400405/1?silent=true)). Related past S3 upload behavior and filename handling came up as useful background ([Cannot download non-image media files… uploaded to S3](https://meta.discourse.org/t/-/152797/1?silent=true)). ### #customization:theme-component - The **Quote Callouts** component had a locale-specific JS error: @nesges reported an issue that only occurred under German translation, and @Arkshine shipped a quick fix via a PR and follow-up guidance ([Quote Callouts](https://meta.discourse.org/t/-/350962/55?silent=true)). The thread also included a neat “zero-width space” workaround to create icon-only/no-title callouts ([read more](https://meta.discourse.org/t/-/350962/59?silent=true)). - **Versatile Banner** ran into a real-world dependency problem: @pacharanero warned that the component’s default background image is hosted on Imgur, which is now inaccessible in the UK, making first-time installs look broken and prompting a suggestion to switch defaults to a non-blocked host ([Versatile Banner](https://meta.discourse.org/t/-/109133/373?silent=true)). - Maintenance realities for older theme components showed up again: in the **Left side hamburger menu on mobile** thread, @Lilly shared a CSS approach (noting the deprecation of `/mobile` theme paths), and @featheredtoast acknowledged the component’s assumptions were impacted by the move away from mobile/desktop view separation ([read more](https://meta.discourse.org/t/-/164513/47?silent=true)). That change itself was recently celebrated elsewhere as a big win ([Improving automatic switching of mobile/desktop modes](https://meta.discourse.org/t/-/384280/1?silent=true)). - A new “micro” component from @Moin restores the composer fullscreen toggle on larger touch devices (like tablets) where it’s hidden by default ([Unhide composer fullscreen toggle for tablets](https://meta.discourse.org/t/-/400433/1?silent=true)). ### #Announcements - The **Modernizing the Foundation theme** project got a status update: after questions from @Lilly and @Canapin about timelines and selector scoping, @jordan.vidrine explained the plan to merge smaller items into core while keeping bigger changes (buttons/header/font rendering) behind a feature flag for now ([read more](https://meta.discourse.org/t/-/395331/65?silent=true)). ### #contribute:site-feedback - Release communication/traceability came up: @jrgong requested that feature/bugfix announcement topics include a version number (especially helpful for managed hosting with slower update cadences), and @RGJ pushed back on the “just run tests-passed” expectation for plugin/theme-heavy sites ([Feature/Bugfix announcement topics should include version number](https://meta.discourse.org/t/-/400394/1?silent=true)). The request used a recent chat pinning announcement as an example ([read more](https://meta.discourse.org/t/-/397571/1?silent=true)). ### #contribute:feature - Topic merges and user expectations: @ganncamp asked what notification a user receives when their topic is merged into another, and how to avoid disorienting people (or cluttering incident threads). @Moin confirmed there _is_ a “post moved” notification and suggested an official notice to explain context ([What merge topic notification does the user get?](https://meta.discourse.org/t/-/400412/1?silent=true)). This ties into a broader request for merge “breadcrumbs” in the target topic ([Request: add breadcrumb to merge target topic](https://meta.discourse.org/t/-/299848/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot engaged directly on mobile composer complexity, asking the community for concrete, actionable proposals to simplify the default UI (toolbar toggle, close vs delete affordances, tag input collapsing) in the main thread ([read more](https://meta.discourse.org/t/-/400393/3?silent=true)). They also acknowledged and followed up on a theme-related draft issue report in the “reddit-ish” theme thread ([A reddit-ish theme for Discourse](https://meta.discourse.org/t/-/269466/125?silent=true)), and confirmed a translation string issue in Solved would be fixed via PR ([Noch ein nicht übersetzbarer Text: “Solved”](https://meta.discourse.org/t/-/400436/2?silent=true)). - @Falco clarified the practical stance on old Windows support (and tested alternative browser forks that still work) in the Windows support topic ([read more](https://meta.discourse.org/t/-/400384/7?silent=true)). They also flagged a self-host performance/upgrade situation as rooted in a deprecated plugin that should be removed ([Forum lagging after reboot + upgrade…](https://meta.discourse.org/t/-/400446/2?silent=true)), and answered calendar/event feature context earlier in the month (referenced again in discussion) ([Add to Calendar .ics request](https://meta.discourse.org/t/-/399329/1?silent=true)). - @sam escalated the OpenAI developer forum login/OIDC error to internal contacts, signaling active investigation on the hosted-support side ([read more](https://meta.discourse.org/t/-/400392/5?silent=true)). The thread itself includes corroboration that the issue affected multiple users ([read more](https://meta.discourse.org/t/-/400392/4?silent=true)). - @jordan.vidrine contributed both product/process guidance (how to frame actionable UX feedback) in the mobile composer discussion ([read more](https://meta.discourse.org/t/-/400393/6?silent=true)) and provided a concrete project status update for the Foundation modernization effort, including what will remain feature-flagged ([read more](https://meta.discourse.org/t/-/395331/65?silent=true)). - @featheredtoast acknowledged that the **Left side hamburger menu on mobile** theme component is behind on updates and that the move away from `/mobile`/`/desktop` assumptions broke parts of it, while pointing toward a CSS grid approach for reordering items ([read more](https://meta.discourse.org/t/-/164513/48?silent=true)). - @supermathie dug into why Windows 7 users might fail to load Discourse even with “supported-ish” browsers, suggesting it could be down to modern TLS defaults and recommending an SSL Labs client test for diagnosis ([read more](https://meta.discourse.org/t/-/400384/12?silent=true)). * * * Yesterday’s vibe: if your mobile tag selector won’t close, your composer keeps freezing, and your Windows 7 users are emailing “it doesn’t work,” at least you’re having the same day as everyone else on Meta. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 12, 2026, 5:01오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/801 "2026-04-12T05:01:38Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** **40** - **New topics (last 24h):** **5** ### Top posters (posts / likes) | User | Posts | Likes | | --- | --- | --- | | @NateDhaliwal | 5 | 2 | | @hellekin | 5 | 1 | | @Moin | 4 | 5 | | @pmusaraj | 2 | 4 | | @rasanderson | 2 | 2 | | @Lilly | 1 | 4 | | @LarisaHaster | 1 | 3 | | @EricGT | 1 | 3 | | @jrgong | 1 | 2 | | @Canapin | 1 | 2 | ### Quick clicks from across Meta (more active threads) - OIDC login issues got resolved for the OpenAI community forum: [read more](https://meta.discourse.org/t/-/400392/9?silent=true) - New site signups briefly hung on “Almost there…” before a fix landed: [read more](https://meta.discourse.org/t/-/400466/4?silent=true) - A reproducible caching oddity was reported for `/favicon/proxied`: [read more](https://meta.discourse.org/t/-/400464/1?silent=true) - Ongoing discussion about “Boosts” and broader impact/values continued: [read more](https://meta.discourse.org/t/-/399835/76?silent=true) - Horizon theme compatibility reassurance for the Kanban component: [read more](https://meta.discourse.org/t/-/118164/298?silent=true) - A request to better connect release notes + versioning to announcement topics: [read more](https://meta.discourse.org/t/-/400394/6?silent=true) - WordPress plugin feature exploration around excluding certain comments/posts: [read more](https://meta.discourse.org/t/-/400422/2?silent=true) * * * ## Interesting Topics ### #Support - @LarisaHaster reported the OpenAI forum OIDC login issue now appears resolved, with @Lilly and @EricGT confirming they can log in again in **“OIDC Error for OpenAI Discourse forum”** (#openid-connect #hosted-support #fixed) — [read more](https://meta.discourse.org/t/-/400392/7?silent=true), [confirmation](https://meta.discourse.org/t/-/400392/8?silent=true) - A new-site creation flow hung at “Almost there…”, with @NateDhaliwal reproducing and @pmusaraj later confirming a fix in **“Stuck on creating new account”** (#free-plan). The original reporter referenced a similar past thread while troubleshooting — [read more](https://meta.discourse.org/t/-/400466/1?silent=true), [status update](https://meta.discourse.org/t/-/400466/4?silent=true), [related](https://meta.discourse.org/t/-/398993/1?silent=true) - @bondero highlighted a tricky notifications problem: staged users can’t easily unsubscribe, raising the question of whether staged users _should_ receive “Watching” emails in **“Exclude staged users from Watching?”** (#staged-users) — [read more](https://meta.discourse.org/t/-/400361/3?silent=true) - Banner workflow friction after upgrades continued: @hellekin described losing a banner topic and difficulties keeping staff-only discussion alongside public banners, tying it to restricted-category banners; @Moin suggested mitigations like splitting posts or hiding revisions and pointed to scheduling as an alternative — [read more](https://meta.discourse.org/t/-/398976/3?silent=true), [restricted banners context](https://meta.discourse.org/t/-/398306/19?silent=true), [scheduling reference](https://meta.discourse.org/t/-/60731/1?silent=true) - @rogerreed offered practical guidance for incoming email on cPanel—_filter by “To” address_, use a dedicated address like `replies@…`, then forward appropriately—in **“How to configure c panel email server to work with incoming emails”** (#email #hosting) — [read more](https://meta.discourse.org/t/-/388143/7?silent=true) * * * ### #bug - @NateDhaliwal reported Meta intermittently loading older topics first (then showing a “new/unread topics” prompt), plus “New replies” counts that linger and later vanish, in **“Opening forum goes to topics 1 day ago, not recent topics”** — [read more](https://meta.discourse.org/t/-/400459/1?silent=true) - A potential cache-key mixup was documented where `/favicon/proxied` appears to return the _same_ image for different URLs, with concrete reproduction URLs provided in **“Bug: `/favicon/proxied` returns the same image for different URLs (cache key issue?)”** — [read more](https://meta.discourse.org/t/-/400464/1?silent=true) - In a French-language report on category settings, @NateDhaliwal suggested tagging to clarify whether it’s actually a calendar/events-related problem in **“Problème dans les paramètres avancés des categories”** (#calendar-and-event #categories) — [read more](https://meta.discourse.org/t/-/400288/12?silent=true) * * * ### #ux - A styling/placement nit: @Moin questioned whether the expand/collapse control for the accepted-answer block belongs below the content rather than in the header (and compared it to quote controls) in **“Move expand/collapse arrow of accepted post in OP below”** (#solved) — [read more](https://meta.discourse.org/t/-/400444/2?silent=true) - @Canapin spotted what looks like inverted tooltip logic for the translation toggle (original vs machine-translated states), and @Moin noted it’s a known bug that can sometimes be “fixed” by refreshing in **“Logic flip in post translation button tooltips?”** (#content-localization) — [read more](https://meta.discourse.org/t/-/400481/1?silent=true), [workaround note](https://meta.discourse.org/t/-/400481/2?silent=true) - Localization detail: @Moin flagged that “Key” and “Value” strings inside the Wrap modal aren’t translatable, and included direct code pointers in **“‘Key’ und ‘Value’ aus dem Wrap Modal sind nicht übersetzbar”** — [read more](https://meta.discourse.org/t/-/400478/1?silent=true) * * * ### #Site feedback - Release communications consistency came up again: @jrgong argued that announcement topics (features/bugfixes) should more explicitly include version numbers, and suggested better linkage between the releases page and announcement topics in **“Feature/Bugfix announcement topics should include version number”** — [read more](https://meta.discourse.org/t/-/400394/6?silent=true) * * * ### #contribute:feature - In **“Allow category moderators to create subcategories”** (#category-moderators), @alanr asked whether this exists, whether it can be sponsored, and what options are available; @NateDhaliwal pointed to Marketplace hiring or (for Enterprise hosting customers) paid Discourse build services, and @ars18 suggested an existing related tool — [read more](https://meta.discourse.org/t/-/280203/12?silent=true), [options](https://meta.discourse.org/t/-/280203/13?silent=true), [related tool](https://meta.discourse.org/t/-/400019/1?silent=true) * * * ### #customization:theme component - Horizon migration planning: @Lew_Grothe asked whether the Kanban theme component will work with Horizon (or whether forking is needed), and @mcwumbly replied it should work “pretty well” in **“Kanban Board”** (#pr-welcome #official #kanban-board) — [read more](https://meta.discourse.org/t/-/118164/297?silent=true), [compatibility reply](https://meta.discourse.org/t/-/118164/298?silent=true) * * * ### #customization:plugin - Plugin/core behavior boundaries were discussed in **“Discourse llms.txt Generator Plugin”** (#ai): @kaktak said they’ll ship an update so core doesn’t override the plugin’s intended behavior, reinforcing the “plugins should be able to override” philosophy — [read more](https://meta.discourse.org/t/-/388170/6?silent=true) * * * ### #wordpress - A filtering feature request for [WP Discourse](https://github.com/discourse/wp-discourse): @angus asked clarifying questions about whether there’s a post-level signal that matches “exclude comments with a specific tag,” contrasting it with the existing inclusive “Only Import Moderator-Liked” setting in **“Wp-discourse feature request - do not show comments with specific tag?”** (#wp-discourse) — [read more](https://meta.discourse.org/t/-/400422/2?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @pmusaraj responded quickly to a signup outage, acknowledging technical issues and later confirming resolution in **“Stuck on creating new account”** — [initial response](https://meta.discourse.org/t/-/400466/3?silent=true), [fix confirmed](https://meta.discourse.org/t/-/400466/4?silent=true) - @mcwumbly chimed in on theme component compatibility, noting the Kanban component should work well with Horizon in **“Kanban Board”** — [read more](https://meta.discourse.org/t/-/118164/298?silent=true) * * * If yesterday was any indication, today’s going to be smoother: fewer “Almost there…” signups, and more logins that just work. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 13, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/802 "2026-04-13T05:02:01Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **61 new posts** across **6 new topics** in the last 24 hours, with lots of hands-on troubleshooting and polish discussions (e.g. new theme components like [Highlight to Search](https://meta.discourse.org/t/-/400492/1?silent=true) and UX tweaks like the [share modal copy button](https://meta.discourse.org/t/-/400502/1?silent=true)). - **Top users (posts / likes)** - **Notable [@team](https://meta.discourse.org/groups/team?silent=true) participation (posts / likes)** * * * ## Interesting Topics ### #customization:theme-component - @NateDhaliwal published **“Highlight to Search”** , a theme component that lets users highlight text inside a post and instantly search for it (either via Discourse search or an external engine) — a neat “micro-productivity” win for readers and moderators alike [read more](https://meta.discourse.org/t/-/400492/1?silent=true). For setup references, see [theme/component install instructions](https://meta.discourse.org/t/-/63682/1?silent=true) and the [themes beginner guide](https://meta.discourse.org/t/-/91966/1?silent=true). - @nathank released **“Upcoming Events Extra Buttons”** , adding configurable **Subscribe** and (optionally) **Create event** buttons to `/upcoming-events`, aimed at reducing friction for event-heavy communities [read more](https://meta.discourse.org/t/-/400503/1?silent=true). Related background: discussion around event UX expectations continues in calendar threads like [closed events visibility](https://meta.discourse.org/t/-/400192/2?silent=true) and broader event workflow ideas [read more](https://meta.discourse.org/t/-/400169/9?silent=true). - The long-running **Kanban Board** component got another round of “is it broken on Horizon?” testing: @Lew_Grothe reported it not working, @Arkshine suggested basic checks (component attachment + console errors), and @nathank shared CSS to widen the Kanban layout under Horizon’s tighter center column [read more](https://meta.discourse.org/t/-/118164/299?silent=true). - In **Discourse Lucide Icons** , @cuo_wu hit an issue where the `calendar-heart` icon wouldn’t render even after adding it to custom SVGs, and @nathank clarified that the “extra icons” mechanism is **Font Awesome 6** -oriented—Lucide additions should follow the custom SVG replacement approach [read more](https://meta.discourse.org/t/-/400133/5?silent=true), with the canonical how-to here: [Replace default SVG icons in a theme](https://meta.discourse.org/t/-/115736/1?silent=true). - **User Field Prompt** got a documentation/UI mismatch callout: @Moin noted the first-post screenshot is now misleading because the field title/description display differs from what admins see in preferences, suggesting an update for less surprise [read more](https://meta.discourse.org/t/-/185214/25?silent=true). - **Banner Featured Links** support continued in French: @gilles wanted the buttons shown beyond the homepage, and @Arkshine pointed to selecting the right plugin outlet (and checking “URL must contain”), recommending the **Developer Toolbar** to discover outlet placement [read more](https://meta.discourse.org/t/-/327497/31?silent=true). The referenced helper tool: [Introducing Discourse Developer Toolbar](https://meta.discourse.org/t/-/346215/1?silent=true). ### #bug - A fresh RTL regression report: **topic title input stays LTR on RTL sites**. @Nima1 described how `dir="auto"` causes empty inputs to render LTR (cursor/selection/placeholder feel wrong), and @sam confirmed it’s not solvable with CSS alone—proposing a markup behavior change (default RTL until typing begins, then switch to auto) with a linked PR [read more](https://meta.discourse.org/t/-/400490/1?silent=true). Cross-reference: @sam noted this also covers older reports like **“Titles placeholder in New topic is not RTL”** [read more](https://meta.discourse.org/t/-/385232/3?silent=true). - The **composer cursor “jumping around”** thread resurfaced with a video showing the editor snapping position during longer edits; @renato suspected it was actually the Markdown split-preview composer (not ProseMirror) and asked for cross-instance reproduction steps to narrow it down [read more](https://meta.discourse.org/t/-/263017/21?silent=true). - **Cooked error after translate** : @cuo_wu reported that translating content (with SC language enabled) seemed to trigger cooked/format issues; @Moin traced at least one culprit to malformed table pipes—tweaking the English source fixed the German translation output too, suggesting translation pipelines can be less forgiving than the main renderer [read more](https://meta.discourse.org/t/-/400509/1?silent=true). ### #ux - On mobile, @Canapin suggested the **share modal** should place the **Copy** button on the same line as the URL input (better thumb reach, less wasted vertical space) [read more](https://meta.discourse.org/t/-/400502/1?silent=true). This fits neatly alongside other Meta-mobile layout nits being tracked in the ongoing theme work (e.g. leaderboard overflow on mobile) [read more](https://meta.discourse.org/t/-/400013/20?silent=true). - **Closed events don’t display in the upcoming-events calendar** : @Ethsim2 argued that “Close event” has become a practical way to hide items without BBCode hacks, and asked that closed events remain visible—or alternatively that Discourse add a separate “Delete event” (or rebrand “Close” to “Hide”) to clarify intent [read more](https://meta.discourse.org/t/-/400192/2?silent=true). Adjacent calendar discussions keep circling back to workflow and visibility: recurring-event topic creation expectations [read more](https://meta.discourse.org/t/-/370600/5?silent=true) and “Add to calendar” integration requests [read more](https://meta.discourse.org/t/-/399329/7?silent=true). - **Notification count persistence** : @sixty4bit described the current behavior (count clears after opening the avatar menu) as actively harmful for low-volume-but-critical PM workflows (e.g. support inboxes), arguing it causes missed follow-ups and extra clicks [read more](https://meta.discourse.org/t/-/299882/14?silent=true). ### #Support - A new **Discourse ID login** problem report (Chinese): users saw a _“redirect uri is malformed or doesn’t match client redirect URI”_ error; @NateDhaliwal pointed to regenerating credentials and the known domain-change fix path, then continued troubleshooting when only admins could log in [read more](https://meta.discourse.org/t/-/400487/1?silent=true). Related reference topic: [Changing domain names prevents Discourse ID from working](https://meta.discourse.org/t/-/386102/1?silent=true). ### #customization:plugin - **Topic Ratings Plugin** got a practical compatibility win: @Arkshine explained a merged PR that removes legacy widget references so the plugin works again, and confirmed updating the plugin should resolve the errors for affected sites [read more](https://meta.discourse.org/t/-/39578/446?silent=true). - In **Telegram Notifications Plugin** , @scavin asked the key maintenance question—whether the plugin is still actively supported—flagging an evergreen concern for production admins weighing long-lived integrations [read more](https://meta.discourse.org/t/-/60483/203?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@sam** focused on fixing RTL title-field directionality by explaining why HTML `dir="auto"` yields LTR when the input is empty, proposing a behavior change (default RTL until the first character, then switch to auto), and linking an implementation PR for review [read more](https://meta.discourse.org/t/-/400490/2?silent=true). @sam also connected the fix to prior RTL UX reports so it lands as a comprehensive improvement rather than a one-off patch [read more](https://meta.discourse.org/t/-/385232/3?silent=true). - **@renato** investigated a renewed report of the composer/editor “jumping” issue, noting the captured behavior appeared to be in the Markdown split-preview composer (not ProseMirror) and requesting reproduction confirmation across multiple Discourse instances to isolate scope and cause [read more](https://meta.discourse.org/t/-/263017/22?silent=true). * * * If today’s Meta had a theme, it’d be: _highlight it, copy it, and make sure it doesn’t accidentally turn LTR while you weren’t looking._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 14, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/803 "2026-04-14T05:02:07Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, Meta saw **67 new posts** and **5 new topics** (for examples of brand-new threads, see [read more](https://meta.discourse.org/t/-/400575/1?silent=true), [read more](https://meta.discourse.org/t/-/400558/1?silent=true), [read more](https://meta.discourse.org/t/-/400557/1?silent=true), [read more](https://meta.discourse.org/t/-/400570/1?silent=true), [read more](https://meta.discourse.org/t/-/400576/1?silent=true)). **Top posters & likers (last 24h)** _(counts reflect activity within the window; each name includes a link to a recent post)_ - **@Moin** — **6 posts** , **7 likes** ([hashtag autocomplete console error report](https://meta.discourse.org/t/-/400570/1?silent=true)) - **@NateDhaliwal** — **7 posts** , **4 likes** ([recent-topics “jumping back in time” discussion](https://meta.discourse.org/t/-/400459/2?silent=true)) - **@putty** — **4 posts** , **7 likes** ([new theme component: Shared Draft default New Topic](https://meta.discourse.org/t/-/400557/1?silent=true)) - **@awesomerobot** — **3 posts** , **6 likes** ([tooltip fix PR opened](https://meta.discourse.org/t/-/400575/2?silent=true)) - **@nathank** — **3 posts** , **3 likes** ([Calendar/Event wizard interpolation explanation](https://meta.discourse.org/t/-/400169/11?silent=true)) - **@manuel** — **1 post** , **6 likes** ([deprecation model + migration window perspective](https://meta.discourse.org/t/-/398896/19?silent=true)) - **@Lilly** — **1 post** , **4 likes** ([admin post menu hover-tip bug report](https://meta.discourse.org/t/-/400575/1?silent=true)) - **@Falco** — **1 post** , **3 likes** ([self-hosting upgrade fix: remove broken plugin](https://meta.discourse.org/t/-/400558/3?silent=true)) - **@david** — **1 post** , **2 likes** ([Telegram plugin deprecation resolved](https://meta.discourse.org/t/-/60483/206?silent=true)) - **@jordan.vidrine** — **1 post** , **2 likes** ([Boosts thread: refocusing on constructive product discussion](https://meta.discourse.org/t/-/399835/79?silent=true)) * * * ## Interesting Topics ### #ux - @Lilly flagged that **admin post menu hover-tooltips are missing/mismatched** (including incorrect labels like “unhide” showing up for unrelated actions), with a core fix quickly spun up by @awesomerobot [read more](https://meta.discourse.org/t/-/400575/1?silent=true). - A mobile/UX refinement request asked for the **share-link modal “copy” button to sit on the same line as the URL input** , and @awesomerobot followed up with a PR that also addresses adjacent layout issues [read more](https://meta.discourse.org/t/-/400502/2?silent=true). - In a localization UX snag, the **“Key” and “Value” strings in the Wrap modal** were reported as not translatable; @awesomerobot confirmed it as an oversight and linked a core fix PR [read more](https://meta.discourse.org/t/-/400478/2?silent=true). - Calendar UX expectations came up again: a user argued that **closed events should still display in the upcoming-events calendar** , and the thread continues to tease apart whether “Close” should behave more like “Hide” (and how much retrospective visibility matters) [read more](https://meta.discourse.org/t/-/400192/4?silent=true). ### #development (#dev-news) - The ongoing transition away from legacy theme/plugin templates got more nuance: @manuel weighed in on **deprecating the `.hbs` extension** , arguing that Discourse is closer to an evolving platform ecosystem than a “stable OS API” model—so _versioning + clear deprecation windows_ matters most [read more](https://meta.discourse.org/t/-/398896/19?silent=true). ### #Self-hosting - A post-upgrade outage (“ **Failed to initialize site default** ”) ended up being caused by a known landmine: a **broken `discourse-multilingual` plugin**. The fix was to remove it and rebuild, with a direct pointer to the plugin topic [read more](https://meta.discourse.org/t/-/400558/3?silent=true) (related plugin thread: [read more](https://meta.discourse.org/t/-/142740/1?silent=true)). ### #customization:theme component - A new component proposes a workflow tweak: **make “Shared Draft” the default New Topic action** , replacing the button text and preloading the composer for staff collaboration workflows (#shared-drafts) [read more](https://meta.discourse.org/t/-/400557/1?silent=true). - In “Highlight to Search” (#search), support questions turned into a mini guide: **external search can be switched by changing the configured search URL** (e.g., to Bing), and the thread also surfaced other search-related components people may want to combine [read more](https://meta.discourse.org/t/-/400492/8?silent=true) (see also [Baidu search](https://meta.discourse.org/t/-/170283/1?silent=true) and [DuckDuckGo search suggestions](https://meta.discourse.org/t/-/83902/1?silent=true)). - The “Discourse Lucide Icons” component thread had a meta problem of its own: **it’s hard to “respond to a Boost,”** and the discussion also highlighted gaps in how changes/features are documented/discoverable via search [read more](https://meta.discourse.org/t/-/400133/9?silent=true). - A long-standing, currently #broken theme component (“Video Upload to YouTube and Vimeo”) got a pulse check: work has restarted and Vimeo is reportedly already functioning again—next steps are to get the full pipeline back into shape [read more](https://meta.discourse.org/t/-/170079/58?silent=true). ### #bug - A puzzling navigation issue: some users report that **opening the forum shows topics from 1–3 days ago instead of recent** , with unread counts that don’t align with what they’ve actually read—possibly related to state restoration when tabs go inactive [read more](https://meta.discourse.org/t/-/400459/2?silent=true) (potentially related: [read more](https://meta.discourse.org/t/-/303928/1?silent=true)). - Another composer-adjacent bug report: **hashtag autocomplete triggers browser console errors** in [safe mode](https://meta.discourse.org/t/53504?silent=true) (“generateIconHTML” undefined) and behaves differently when plugins are enabled (“dataSource is not a function”), suggesting a core JS edge case or an integration mismatch (#hashtag-autocomplete) [read more](https://meta.discourse.org/t/-/400570/1?silent=true). - A smaller follow-up confirmed resolution of a translation/rendering issue: **a “cooked” error after translate** was reported and then marked fixed by the reporter (#ai, #dynaloc) [read more](https://meta.discourse.org/t/-/400509/3?silent=true). ### #Support - Incoming-email topic creation hit a common snag: **HTML emails being trimmed/treated as quoted content** , resulting in only the first lines appearing in the created topic. The thread is moving toward debugging with a full raw email + post source to see what Discourse is detecting [read more](https://meta.discourse.org/t/-/400576/4?silent=true). - A Discourse ID login support thread (in Chinese) wrapped up after troubleshooting: the poster ultimately **reinstalled and confirmed the issue resolved** , after configuration checks around login settings (#discourse-id) [read more](https://meta.discourse.org/t/-/400487/9?silent=true). - Multilingual admin customization got a pragmatic solution: a user shared a **small plugin approach to localize badges and groups** by adding strings under `config/locales` and naming badges using translation keys (#badges, #groups, #translation) [read more](https://meta.discourse.org/t/-/398127/9?silent=true). - For sites that create lots of staged users, one admin outlined how they stopped staged users turning the site into a “spamming machine”: **force staged users to TL0, set new users to TL1, and use TL1+ category watching** (#staged-users) [read more](https://meta.discourse.org/t/-/400361/4?silent=true). ### #Announcements - The “Testing Boosts on Meta” thread continued, with a reminder to keep feature discussion focused: **product feedback can stay fun without drifting into unrelated heavy topics** , and there’s interest in giving communities more expressive options over time [read more](https://meta.discourse.org/t/-/399835/79?silent=true). - “Upcoming Changes” clarity improved: **auto-grids for image uploads** are now “Stable” for most sites, but staff emphasized that _Stable doesn’t always mean “setting will be removed”_—opt-out remains and “Permanent” status won’t be applied in this case [read more](https://meta.discourse.org/t/-/394784/10?silent=true) (background on the system: [read more](https://meta.discourse.org/t/-/392894/1?silent=true)). ### #customization:plugin - The Telegram notifications plugin had a quick maintenance win: a `.hbs` deprecation warning was addressed, with a maintainer confirming the deprecation should now be resolved (ties back to the broader `.hbs` deprecation announcement) [read more](https://meta.discourse.org/t/-/60483/206?silent=true) and [read more](https://meta.discourse.org/t/-/398896/19?silent=true). - The Landing Pages plugin (#pavilion) received a compatibility update for current stable (2026.1), with follow-up review comments already landing in the thread [read more](https://meta.discourse.org/t/-/180967/158?silent=true). - A plugin vendor/support thread noted an integration issue: **ProxyTracer + Cloudflare WARP returning “unknown error” instead of a blocked message** , suggesting either detection gaps or error handling needing refinement [read more](https://meta.discourse.org/t/-/399958/8?silent=true). ### #contribute:feature - AI agent behavior design remains a hot spot: one request asked for **AI personas/agents to respond only to @mentions** , not to replies to their posts (#ai, #ai-bot), and discussion pointed to workaround tactics [read more](https://meta.discourse.org/t/-/399221/4?silent=true) (related workaround thread: [read more](https://meta.discourse.org/t/-/398209/4?silent=true)). - In “New AI Persona Editor for Discourse,” there’s renewed interest in configuring a persona to act like a **“standard chat AI”** (i.e., not searching Discourse content or being aware it’s embedded in a forum context) [read more](https://meta.discourse.org/t/-/286271/35?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** moved several UX fixes forward: they opened a fix for the **admin post-menu hover-tip mismatches** [read more](https://meta.discourse.org/t/-/400575/2?silent=true), confirmed and patched the **Wrap modal translation gap** [read more](https://meta.discourse.org/t/-/400478/2?silent=true), and posted a PR-driven fix for the **share modal copy-button layout** [read more](https://meta.discourse.org/t/-/400502/2?silent=true). - **@manuel** added strategic context to the `.hbs` deprecation conversation, emphasizing **clear versioning + deprecation notices + migration windows** as the sustainable model for a live ecosystem [read more](https://meta.discourse.org/t/-/398896/19?silent=true). - **@Falco** unblocked a broken self-hosting upgrade by identifying the culprit as a **broken customization plugin** and recommending removal + rebuild, which resolved the boot issue [read more](https://meta.discourse.org/t/-/400558/3?silent=true). - **@david** confirmed a maintenance fix in the Telegram notifications plugin ecosystem, noting the `.hbs` deprecation warning should now be **resolved** [read more](https://meta.discourse.org/t/-/60483/206?silent=true). - **@jordan.vidrine** helped steer the “Boosts” discussion back toward productive product feedback, discouraging unrelated real-world digressions so the feature conversation stays **useful for communities** [read more](https://meta.discourse.org/t/-/399835/79?silent=true). - **@martin** clarified how “Upcoming Changes” statuses work in practice, noting that **Stable ≠ forced permanent** , and that “enable auto grid images” is expected to remain **opt-out** [read more](https://meta.discourse.org/t/-/394784/10?silent=true). - **@supermathie** jumped into email-in support, explaining that missing content is often due to Discourse detecting parts of the email as **quoted/previous-email content** , and requested a raw email + post source for accurate diagnosis [read more](https://meta.discourse.org/t/-/400576/4?silent=true). * * * _That’s a wrap—may your tooltips stay accurate, your boosts stay on-topic, and your hashtag autocomplete stop yelling at your browser console._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 15, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/804 "2026-04-15T05:02:10Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 78 - **New topics (last 24h):** 10 - **Top posters / liked contributors (last 24h):** - **What drove the day (threads with lots of “gravity”):** mobile composing pain points (see [read more](https://meta.discourse.org/t/-/400393/18?silent=true)), review queue / moderation workflow questions (see [read more](https://meta.discourse.org/t/-/400602/3?silent=true)), and a cluster of reviewable/insights bugs (see [read more](https://meta.discourse.org/t/-/391230/3?silent=true)). * * * ## Interesting Topics ### #ux - @Ed_S highlighted how cramped mobile composing can get (down to _one visible line_), and the discussion expanded into discoverability and defaults for the toolbar—now being actively reviewed by staff in the ongoing thread about the “2026 Discourse experience” (#composer #mobile) [read more](https://meta.discourse.org/t/-/400393/18?silent=true). - A small-but-daily-friction point: the sharing modal UI and how the copy button aligns alongside the URL (especially when sharing _posts_ vs _topics_), with clarification about what changed and what didn’t (#mobile) [read more](https://meta.discourse.org/t/-/400502/4?silent=true). ### #contribute:feature - The long-running request to show **all** likes/reactions (instead of a truncated panel) resurfaced strongly; staff noted the UX change was partly about shared components/consistency, but also that the community signal here is loud and it’s getting more priority (#Contribute > Feature) [read more](https://meta.discourse.org/t/-/389820/36?silent=true). - A previously-requested improvement appears to have quietly landed: the composer toolbar is now behaving more like mobile (horizontal overflow/scroll), and people are noticing it “just works” in practice (#composer #ux) [read more](https://meta.discourse.org/t/-/380864/2?silent=true). ### #Support - A French-language support thread dug into “search within only _two specific categories_ by default,” balancing user simplicity vs powerful filters; the accepted direction pointed toward tuning **category search priority** (and possibly a theme component for a more guided UX) (#search) [read more](https://meta.discourse.org/t/-/400385/18?silent=true). - Email-in workflows struck another edge case: an incoming-email-created topic was missing most content because the HTML got split at a `
` boundary. The most maintainable workaround suggested moving away from “HTML email parsing” to a **markdown template + API post creation** approach (#email) [read more](https://meta.discourse.org/t/-/400576/6?silent=true). ### #bug - Several “reviewable/insights” issues continue to be sharp edges: IP info not refreshing correctly when switching reviewables, alongside reports of incorrect join date + post count in insights. The cluster suggests a broader “stale/incorrect insights panel state” problem (#review-queue) — see [read more](https://meta.discourse.org/t/-/391230/3?silent=true) and [read more](https://meta.discourse.org/t/-/391232/6?silent=true). - A composer console error around hashtag autocomplete (`generateIconHTML` undefined) got a clear pointer to the fix, while a second autocomplete error remains harder to reproduce (#hashtag-autocomplete) [read more](https://meta.discourse.org/t/-/400570/3?silent=true). - Embedded comments are still showing **English-formatted dates** even when the embed UI is otherwise localized; the report includes expected Finnish locale behavior and highlights that the “classic” embed approach is preferred for the site in question (#embedding) [read more](https://meta.discourse.org/t/-/400582/1?silent=true). - AI translation: Portuguese (`pt`) is being skipped even when many other locales translate automatically; the report includes environment details (Discourse/AI plugin versions and model selection) and clear repro steps (#ai #dynaloc) [read more](https://meta.discourse.org/t/-/400612/1?silent=true). - Creating a topic from a tag page can prefill a **disallowed tag** into the composer (server-side still blocks submission, but the UI flow is confusing); this looks like a “composer prefill bypasses tag-group restriction rules” footgun (#composer #tags #tag-groups) [read more](https://meta.discourse.org/t/-/400616/1?silent=true). ### #Sysadmins - Two closely-related “make everything go to `www`” how-tos (apex → `www`, and wildcard/random subdomains → `www`) also sparked a practical ops aside: when `sudo` is (and isn’t) necessary depending on how you run your server and whether root logins are allowed (#www) — see [read more](https://meta.discourse.org/t/-/400583/1?silent=true) and [read more](https://meta.discourse.org/t/-/400584/1?silent=true). ### #Announcements - The “upcoming changes”/impact-labeling conversation continues to evolve: discussion clarified how **defaults** and **warnings** should behave going forward (especially on Stable), prompted by a previously-announced default around image grids. Context: the original announcement [read more](https://meta.discourse.org/t/-/394784/15?silent=true) plus the broader “Upcoming Changes” feature thread [read more](https://meta.discourse.org/t/-/395390/1?silent=true). - The “full comment system embed” announcement thread got additional confirmation of UX improvements like floating controls (reply access and timeline invocation), addressing early feedback about long iframe scroll experiences (#embedding) [read more](https://meta.discourse.org/t/-/399743/16?silent=true). ### #customization:theme component - A new official theme component, **Whisper Warning** , adds an explicit composer toggle/indicator so staff don’t accidentally post publicly when they meant to whisper (#official #whispers). It was also pointed to as a practical answer for “where did whisper go?” confusion in the broader UX discussion [read more](https://meta.discourse.org/t/-/400629/1?silent=true) (related context: [read more](https://meta.discourse.org/t/-/379639/4?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** covered multiple “why did this change?” questions: - **@Falco** focused on clarifying current behavior and pointing to fixes/ship-ready changes: - **@renato** acknowledged and acted on mobile composer feedback: confirmed the toolbar default change isn’t the whole story for the cramped 375px case, merged duplicate discussion into the main thread, and noted improvements are actively being discussed internally [read more](https://meta.discourse.org/t/-/400393/18?silent=true). - **@zogstrip** stayed close to bug triage and plugin constraints: - **@supermathie** advised on replacing fragile email-parsing pipelines with a more reliable “template to markdown + API post” integration for consistent formatting [read more](https://meta.discourse.org/t/-/400576/6?silent=true). - **@martin** clarified how “upcoming changes” impact types should behave going forward, especially for migrated/legacy default-setting changes and what should (not) show warnings on Stable [read more](https://meta.discourse.org/t/-/394784/15?silent=true). * * * If yesterday had a theme, it was: _may your composer show more than one line, your flags be less mysterious, and every rogue subdomain politely redirect to `www`_ (see [read more](https://meta.discourse.org/t/-/400393/18?silent=true) and [read more](https://meta.discourse.org/t/-/400583/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: [4월 16, 2026, 5:01오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/805 "2026-04-16T05:01:30Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 81** - **New topics (last 24h): 14** **New topics opened (with references):** - #contribute:feature / #embedding — _Tecnoblog’s Experience With Discourse Comments_ ([read more](https://meta.discourse.org/t/-/400721/1?silent=true)) - #Support / #post-notices — _Where did the you are replying to an old topic warning go?_ ([read more](https://meta.discourse.org/t/-/400688/1?silent=true)) - #contribute:feature / #review-queue — _Custom review queue help links_ ([read more](https://meta.discourse.org/t/-/400700/1?silent=true)) - #bug / #composer / #tags — _Inconsistent permission to use the same tag in the same category_ ([read more](https://meta.discourse.org/t/-/400696/1?silent=true)) - #Support — _URLs with encoding are altered when using Discourse link function_ ([read more](https://meta.discourse.org/t/-/400694/1?silent=true)) - #bug / #calendar-and-event — _Chat link missing in post event widget after to Rollup_ ([read more](https://meta.discourse.org/t/-/400691/1?silent=true)) - #bug — _Unable to save category settings made by plugins_ ([read more](https://meta.discourse.org/t/-/400699/1?silent=true)) - #Support / #tags / #free-plan — _Does Free forums not support the use of tags?_ ([read more](https://meta.discourse.org/t/-/400738/1?silent=true)) - #Support — _Remote images are always downloaded_ ([read more](https://meta.discourse.org/t/-/400697/1?silent=true)) - #Support / #ai / #content-localization — _Post not being detected as German_ ([read more](https://meta.discourse.org/t/-/400708/1?silent=true)) - #ux / #free-plan — _Misleading free plan shutdown timeline_ ([read more](https://meta.discourse.org/t/-/400747/1?silent=true)) - #bug — _New posts/replies do not appear in real-time; manual refresh required_ ([read more](https://meta.discourse.org/t/-/400710/1?silent=true)) - #bug / #backups / #ux — _Backups page_ ([read more](https://meta.discourse.org/t/-/400730/1?silent=true)) - #ux / #translation — _Translated text on Linux Debian has weird formatting_ ([read more](https://meta.discourse.org/t/-/400723/1?silent=true)) **Top users (posts / likes in the last 24h):** - **@Falco** — **12 posts** , **39 likes** (notably responding in [Discourse Comments embed feedback](https://meta.discourse.org/t/-/400721/3?silent=true) and [AI translation language detection](https://meta.discourse.org/t/-/400708/2?silent=true)) - **@Thiago_Mobilon** — **3 posts** , **11 likes** (shared detailed embed findings in [this report](https://meta.discourse.org/t/-/400721/1?silent=true)) - **@Moin** — **7 posts** , **8 likes** (tag permissions in [this bug report](https://meta.discourse.org/t/-/400696/1?silent=true) and troubleshooting in [encoded-URL support](https://meta.discourse.org/t/-/400694/4?silent=true)) - **@nat** — **7 posts** , **6 likes** (helped unblock chat access in [Discourse Livestream](https://meta.discourse.org/t/-/341335/48?silent=true) and tracked localization issues in [this UX thread](https://meta.discourse.org/t/-/400481/3?silent=true)) - **@haydenjames** — **3 posts** , **7 likes** (raised concerns about removed “old topic” notice in [this support topic](https://meta.discourse.org/t/-/400688/1?silent=true)) * * * ## Interesting Topics ### #contribute:feature - @Thiago_Mobilon shared real-world, high-traffic feedback on the new full-app embedding experience—covering **10x request spikes** , caching headers, analytics duplication, and dynamic height needs—prompting @Falco to point to fixes and ongoing work in the same thread ([read more](https://meta.discourse.org/t/-/400721/1?silent=true)) - @Lilly suggested improving staff UX in the review queue by letting admins **truly replace** the built-in moderation help link (instead of just adding another link on top), to avoid staff confusion and reduce reliance on outdated Meta docs ([read more](https://meta.discourse.org/t/-/400700/1?silent=true)) - A long-running request to keep push subscriptions on logoff was marked implemented, with @Falco linking the completion back to the original request thread ([read more](https://meta.discourse.org/t/-/134038/7?silent=true)) ### #Support - The disappearance of the “you’re replying to an old topic” warning led to a values discussion: @simonk referenced the rationale that Discourse prefers _revivals over duplicates_, while @haydenjames argued for keeping the notice but with better, configurable messaging ([read more](https://meta.discourse.org/t/-/400688/1?silent=true)) - A report that Discourse “double-encodes” already-encoded URLs when inserted via the composer link tool couldn’t be reproduced; the thread quickly turned into upgrade guidance (moving from 3.5.3 toward current releases) and validating behavior on try.discourse ([read more](https://meta.discourse.org/t/-/400694/1?silent=true)) - A hosted customer reported remote images suddenly being **downloaded and locally re-hosted** despite attempting to disable it and add domain exceptions; @Moin noted the exception setting works on their hosted site and encouraged checking recent changes and staff logs ([read more](https://meta.discourse.org/t/-/400697/1?silent=true)) - A German post wasn’t being translated because language detection was confused by mixed-language context; @Falco confirmed the manual language selector _forces_ the post language, and follow-ups pointed to possible issues around translation editing/title handling ([read more](https://meta.discourse.org/t/-/400708/1?silent=true)) ### #bug - A new composer/tagging hint system appears inconsistent: the same tag sometimes shows as allowed vs disallowed depending on the search term; @zogstrip confirmed the feature needed to be smarter around tag limits and linked a fix ([read more](https://meta.discourse.org/t/-/400696/1?silent=true)) - The `discourse-calendar` event widget lost its 💬 chat-channel link after the Rollup build changes; @klappradla identified the regression window and provided a PR, with @david encouraging the contribution ([read more](https://meta.discourse.org/t/-/400691/1?silent=true)) - Plugin-defined category settings stopped saving after 2026.4.0: admins can change plugin fields but never get the “unsaved changes” save prompt; @awesomerobot explained this is tied to **FormKit** + `enable_simplified_category_creation`, and plugins must migrate to the new form structure ([read more](https://meta.discourse.org/t/-/400699/1?silent=true)) - A self-hosted site reported MessageBus-style live updates no longer delivering new replies in an open topic (manual refresh required); the first troubleshooting question from @sam was whether a proxy (e.g., Cloudflare) is involved ([read more](https://meta.discourse.org/t/-/400710/1?silent=true)) - A small but telling UI regression: on the admin backups screen, an arrow/tab indicator intermittently fails to render until navigating away and back, and the reporter suspects it’s part of a broader “log/output only updates after navigation” class of issues ([read more](https://meta.discourse.org/t/-/400730/1?silent=true)) ### #ux - A free-plan site shutdown email appeared to promise time to “create activity,” but the site was already placed in read-only mode shortly after—raising concerns that the timeline messaging is misleading ([read more](https://meta.discourse.org/t/-/400747/1?silent=true)) - A translation UI rendering issue on Debian/Firefox shows translated text overflowing into the right column before wrapping, suggesting a platform/font/layout edge case in the translated-post presentation ([read more](https://meta.discourse.org/t/-/400723/1?silent=true)) ### #customization:plugin - In the official livestream workflow, users who RSVP “going” still couldn’t access chat; @nat adjusted a setting to Trust Level 0 and noted the “everyone” group edge case isn’t a real group for the plugin’s checks ([read more](https://meta.discourse.org/t/-/341335/47?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@Falco** drove several embed-related follow-ups: diagnosing caching headers (double `cache-control`) and performance implications in _Tecnoblog’s embed report_ ([read more](https://meta.discourse.org/t/-/400721/3?silent=true)), discussing analytics-in-iframe concerns ([read more](https://meta.discourse.org/t/-/400721/4?silent=true)), and confirming dynamic embed height work landed ([read more](https://meta.discourse.org/t/-/400721/6?silent=true)). He also clarified manual language selection behavior in the AI translation thread ([read more](https://meta.discourse.org/t/-/400708/2?silent=true)) and closed the loop on push subscriptions on logoff ([read more](https://meta.discourse.org/t/-/134038/7?silent=true)). - **@nat** handled multiple product-support touchpoints: unblocking chat permissions for the livestream plugin by changing access to TL0 ([read more](https://meta.discourse.org/t/-/341335/48?silent=true)), progressing a docs reindexing fix with a linked PR in the restore issue ([read more](https://meta.discourse.org/t/-/392225/15?silent=true)), and acknowledging/triaging localization bugs (including the translation tooltip logic) ([read more](https://meta.discourse.org/t/-/400481/3?silent=true)) plus the `?tl=` anonymous localization thread ([read more](https://meta.discourse.org/t/-/400090/4?silent=true)). He also challenged a suspected cause in the German-translation debugging thread and asked about model deprecations ([read more](https://meta.discourse.org/t/-/400708/9?silent=true)). - **@pmusaraj** linked an upcoming fix for Google One Tap behavior inside embedded Discourse (iframe refresh/login flow) in the embed feedback thread ([read more](https://meta.discourse.org/t/-/400721/2?silent=true)), and requested clearer problem details in the WeChat mini program integration discussion ([read more](https://meta.discourse.org/t/-/312085/5?silent=true)). - **@zogstrip** confirmed the new tag permission messaging needed smarter logic around tag limits, pointing to a fix in the bug thread ([read more](https://meta.discourse.org/t/-/400696/4?silent=true)). - **@awesomerobot** explained why plugin category settings stopped saving under the simplified category creation experience, and outlined the FormKit migration path (with an example branch pattern) ([read more](https://meta.discourse.org/t/-/400699/2?silent=true)). - **@david** encouraged a community PR to fix the missing chat link in the calendar event widget, giving a quick green light to proceed ([read more](https://meta.discourse.org/t/-/400691/2?silent=true)). - **@featheredtoast** followed up on the long-running mobile left hamburger menu theme component, noting @Lilly’s cleanup work and that the changes were merged ([read more](https://meta.discourse.org/t/-/164513/49?silent=true)). - **@tgxworld** documented that category moderation trust-level behavior and “approvals tied to groups” effectively landed (linking the implementation) and closed out the older feature request accordingly ([read more](https://meta.discourse.org/t/-/258867/3?silent=true)) and ([read more](https://meta.discourse.org/t/-/148540/4?silent=true)). - **@sam** kicked off troubleshooting for missing real-time topic updates by asking whether a proxy like Cloudflare is in the mix ([read more](https://meta.discourse.org/t/-/400710/2?silent=true)). * * * Yesterday’s vibe: cache headers got a stern talking-to, old-topic warnings sparked philosophy, and even the backups page tried to play hide-and-seek—may your embeds be lazy-loaded and your UI arrows always show up on the first try. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 17, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/806 "2026-04-17T05:02:12Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 118** - **New topics (last 24h): 20** ### Top users (posts + likes in the last 24h) | User | Posts | Likes | Seen in… | | --- | --- | --- | --- | | **@Lilly** | 9 | 23 | Released a new theme component: [read more](https://meta.discourse.org/t/-/400765/1?silent=true) | | **@pmusaraj** | 8 | 12 | Investigated translation + locale issues: [read more](https://meta.discourse.org/t/-/400612/6?silent=true) | | **@Falco** | 3 | 11 | Shipped rapid improvements to Discourse Comments embedding behavior: [read more](https://meta.discourse.org/t/-/400721/17?silent=true) | | **@Canapin** | 9 | 10 | Flagged UI regressions around voting + theme states: [read more](https://meta.discourse.org/t/-/400800/1?silent=true) | | **@putty** | 5 | 9 | Helped diagnose content-localization behavior & UX preferences: [read more](https://meta.discourse.org/t/-/400708/10?silent=true) | | **@awesomerobot** | 4 | 9 | Responded with fixes + workarounds to multiple admin-facing issues: [read more](https://meta.discourse.org/t/-/400699/4?silent=true) | | **@RGJ** | 2 | 7 | Reported breakage and offered concrete code-level pointers: [read more](https://meta.discourse.org/t/-/400775/1?silent=true) | | **@lindsey** | 2 | 6 | Announced a smoother “Ideas” category setup powered by Topic Voting: [read more](https://meta.discourse.org/t/-/399365/1?silent=true) | | **@Thiago_Mobilon** | 3 | 5 | Tested embed sizing changes and reported edge cases with very tall iframes: [read more](https://meta.discourse.org/t/-/400721/19?silent=true) | | **@sam** | 1 | 5 | Published a direct reassurance on Discourse staying open source: [read more](https://meta.discourse.org/t/-/400863/1?silent=true) | ### Quick hits that also drew attention - A Chrome-only “preview theme doesn’t exist” locale-switch trap was traced to a stale URL parameter: [read more](https://meta.discourse.org/t/-/400784/5?silent=true) - Staff shared practical guidance on remote image downloads and orphan cleanup timing: [read more](https://meta.discourse.org/t/-/400697/6?silent=true) - A self-hosting deep dive connected staff-only 502s to partial git clones and repeated `merge-base` checks: [read more](https://meta.discourse.org/t/-/394612/4?silent=true) - A new “Mobile Latest Homepage” component was posted as a replacement for a long-marked-broken one: [read more](https://meta.discourse.org/t/-/95705/33?silent=true) - A request for better review-queue ergonomics argued for grouping items per user to avoid accidental moderation actions: [read more](https://meta.discourse.org/t/-/400783/1?silent=true) ## Interesting Topics ### #blog - @sam addressed ecosystem concerns head-on, reiterating Discourse’s commitment to open source in the wake of other SaaS projects closing their codebases: [read more](https://meta.discourse.org/t/-/400863/1?silent=true) ### #Announcements - @lindsey announced a streamlined way to create “Ideas” categories using the Topic Voting plugin (#topic-voting), baking common settings into category creation so admins don’t have to wire everything manually: [read more](https://meta.discourse.org/t/-/399365/1?silent=true) ### #contribute:feature - In a detailed embed-field report from a high-traffic site, @Thiago_Mobilon and @Falco iterated quickly on Discourse Comments (#embedding) — fixing dynamic height and discussing sane limits to avoid “infinite-scroll-meets-giant-iframe” UX traps: [read more](https://meta.discourse.org/t/-/400721/20?silent=true) ### #customization:plugin - @pmusaraj shared an experimental Buffer sharing plugin (#experimental) that lets staff queue a topic to Buffer from the share modal or wrench menu, including a server-generated preview of title/excerpt/image before posting: [read more](https://meta.discourse.org/t/-/400819/1?silent=true) ### #bug - A breaking change to category settings UI impacted multiple plugins; staff clarified the rollout and pointed admins to disabling `enabled_simplified_category_creation` in **Upcoming Changes** while fixes landed: [read more](https://meta.discourse.org/t/-/400699/4?silent=true) - AI translation (#ai, #dynaloc) appeared to skip Portuguese when many locales were enabled; narrowing enabled languages made PT translations start working again, suggesting a scaling/limits issue worth further logging: [read more](https://meta.discourse.org/t/-/400612/6?silent=true) - A real-time sync gap was reported: moving a post between topics didn’t update already-open clients viewing the destination topic, raising questions about the pathway for move events vs. standard “new post” updates: [read more](https://meta.discourse.org/t/-/400811/1?silent=true) - Invite detail tabs were invisible to non-staff due to a client-side route/controller mismatch; a one-line fix was proposed and quickly accepted: [read more](https://meta.discourse.org/t/-/400775/2?silent=true) ### #ux - A moderation workflow pain point: @noahl suggested the review queue (#review-queue) should visually group items by user (or at least warn about related queue items) to reduce “delete first, discover legitimate content later” outcomes: [read more](https://meta.discourse.org/t/-/400783/1?silent=true) - Theme work surfaced UI polish issues: vote display sizing in the new Foundation theme (#topic-voting) and additional dark-theme state contrast problems were raised in the broader modernization thread: [read more](https://meta.discourse.org/t/-/400800/1?silent=true) and [read more](https://meta.discourse.org/t/-/395331/73?silent=true) ### #Theme\_component - @Lilly published **Discourse Dynamic Sidebar Icon** (#sidebar), a lightweight component that swaps the sidebar toggle icon based on open/closed state, with optional mobile behavior for icon consistency: [read more](https://meta.discourse.org/t/-/400765/2?silent=true) - Whisper UX got attention from both angles: the **Whisper Warning** component’s settings interactions were clarified, while core UI work-in-progress was hinted to make whisper toggling more obvious in the composer flow (#whispers): [read more](https://meta.discourse.org/t/-/400629/5?silent=true) and [read more](https://meta.discourse.org/t/-/379639/13?silent=true) - The long-standing “Force Mobile Homepage” component (#broken) got a practical successor: a new **Mobile Latest Homepage** component avoids deprecated APIs and uses viewport detection + router redirects, with session memory of “Latest vs Categories”: [read more](https://meta.discourse.org/t/-/95705/33?silent=true) and [read more](https://meta.discourse.org/t/-/400836/1?silent=true) ### #Support - A locale-switching error that only affected admins in Chrome was resolved by removing a stale `?preview_theme_id=` parameter that “stuck” in the URL, triggering a misleading theme-preview error across topics: [read more](https://meta.discourse.org/t/-/400784/5?silent=true) - A usability question turned into a product/setting discussion: can admins change the **default landing tab for Groups** (Members vs Activity vs Messages), ideally per-group, to emphasize what’s happening instead of who’s listed: [read more](https://meta.discourse.org/t/-/400825/1?silent=true) ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@sam** published a clear public stance that Discourse is **not** going closed source, framing the post as a response to broader industry anxiety and AI-era risks: [read more](https://meta.discourse.org/t/-/400863/1?silent=true) - **@Falco** pushed multiple embed improvements based on real-world testing, including adopting native lazy-loading via `loading="lazy"` and iterating on dynamic height behavior for Discourse Comments (#embedding): [read more](https://meta.discourse.org/t/-/400721/17?silent=true) and [read more](https://meta.discourse.org/t/-/400721/18?silent=true) - **@david** contributed to the embed conversation by suggesting the browser-native lazy iframe approach (reducing the need for custom JS/observers), helping drive the quick follow-up changes: [read more](https://meta.discourse.org/t/-/400721/16?silent=true) - **@pmusaraj** debugged multiple support/bug reports, including identifying that an admin-only locale-switch error was actually caused by a stale `preview_theme_id` parameter: [read more](https://meta.discourse.org/t/-/400784/4?silent=true) - **@pmusaraj** also investigated a tricky AI translation edge case where Portuguese translations were skipped when many locales were enabled, then looped in teammates and suggested using verbose logs for diagnosis (#ai, #dynaloc): [read more](https://meta.discourse.org/t/-/400612/6?silent=true) - **@nat** weighed in on the “Portuguese skipped” translation mystery and pointed to `/logs` plus a hidden verbose logging setting `ai_translation_verbose_logs` for deeper investigation: [read more](https://meta.discourse.org/t/-/400612/7?silent=true) - **@awesomerobot** acknowledged and provided immediate mitigation for plugin breakage caused by simplified category creation, including pointing admins at toggling the upcoming change setting while fixes rolled out: [read more](https://meta.discourse.org/t/-/400699/4?silent=true) - **@martin** clarified the notification/rollout expectations around the simplified category setup change, then followed up with confirmation that fixes were merged (with extra spec coverage) for affected official plugins: [read more](https://meta.discourse.org/t/-/400699/8?silent=true) and [read more](https://meta.discourse.org/t/-/400699/10?silent=true) - **@awesomerobot** quickly accepted a code-level bug report about invite detail visibility and linked the fix PR back to the report thread (#invites): [read more](https://meta.discourse.org/t/-/400775/2?silent=true) - **@lindsey** announced improvements to create “Ideas” categories powered by Topic Voting, and cross-referenced it from the ongoing “Current Projects” roundup to keep the roadmap thread tidy: [read more](https://meta.discourse.org/t/-/399365/1?silent=true) and [read more](https://meta.discourse.org/t/-/398565/13?silent=true) - **@supermathie** explained a scary-looking 429 after split/move operations as non-critical (a timings update request), giving admins confidence that the move itself succeeded and the error can be ignored: [read more](https://meta.discourse.org/t/-/400785/2?silent=true) - **@manuel** resurfaced interest in a Discourse static archive generator and shared a community prototype that outputs browsable categories/tags/users with working search, as a reference point for future tooling: [read more](https://meta.discourse.org/t/-/373808/10?silent=true) May your sidebar icons stay perfectly in sync, and may none of your embeds decide they need 9,000 pixels of breathing room overnight. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 18, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/807 "2026-04-18T05:02:23Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **83** new posts, **10** new topics - **Most active users (posts / likes):** - @NateDhaliwal — **7 posts** , **15 likes** (e.g. shipping a new theme component in [Wikipedia Lookup](https://meta.discourse.org/t/-/400884/1?silent=true) and reporting a Free Plan issue in [Cannot disable read-only mode on Free Plan](https://meta.discourse.org/t/-/400870/1?silent=true)) - @chapoi — **2 posts** , **14 likes** (notably reacting to the open-source stance in [Discourse is Not Going Closed Source](https://meta.discourse.org/t/-/400863/6?silent=true)) - @jomaxro — **5 posts** , **13 likes** (supporting Discourse ID troubleshooting in [Discourse ID and 2FA](https://meta.discourse.org/t/-/400910/2?silent=true) and clarifying trials/free plan in [Sample Forum to See Admin Features?](https://meta.discourse.org/t/-/392680/12?silent=true)) - @Moin — **4 posts** , **8 likes** (login UX + text customization guidance in [Disable initial page that re-directs to /login](https://meta.discourse.org/t/-/400773/3?silent=true) and [How do i change “Welcome Back” on /login](https://meta.discourse.org/t/-/400930/3?silent=true)) - @manuel — **1 post** , **8 likes** (highlighting improvements in [Discourse is Not Going Closed Source](https://meta.discourse.org/t/-/400863/8?silent=true)) - @elmuerte — **1 post** , **8 likes** (community perspective on trust/open source in [Discourse is Not Going Closed Source](https://meta.discourse.org/t/-/400863/4?silent=true)) - @Lilly — **4 posts** , **7 likes** (confirming trial behavior in [Sample Forum to See Admin Features?](https://meta.discourse.org/t/-/392680/8?silent=true) and filing a new sidebar bug in [Cannot search for icon by name…](https://meta.discourse.org/t/-/400945/1?silent=true)) - @zhanfeng — **1 post** , **7 likes** (supportive response in [Discourse is Not Going Closed Source](https://meta.discourse.org/t/-/400863/7?silent=true)) - @Canapin — **3 posts** , **7 likes** (product feedback in [Support `` in the rich editor](https://meta.discourse.org/t/-/400885/1?silent=true) and UI details in [Modernizing the Foundation theme](https://meta.discourse.org/t/-/395331/75?silent=true)) - @awesomerobot — **3 posts** , **6 likes** (helping on login/welcome banner questions like [What’s the background image size…](https://meta.discourse.org/t/-/400767/2?silent=true) and tidying old info in [Sample Forum to See Admin Features?](https://meta.discourse.org/t/-/392680/10?silent=true)) > One memorable technical gem: @zogstrip explained why diffs sometimes fail with a “budget” cutoff so the server doesn’t melt down — [read more](https://meta.discourse.org/t/-/400810/2?silent=true). * * * ## Interesting Topics ### #blog - **Discourse reaffirmed its long-term commitment to open source** , sparking discussion about trust, security, and community reciprocity in [Discourse is Not Going Closed Source](https://meta.discourse.org/t/-/400863/1?silent=true) (with pointed reactions like @elmuerte’s take on security-by-obscurity and community trust — [read more](https://meta.discourse.org/t/-/400863/4?silent=true)). - **Questions about Discourse MCP transport options** came up again, and @Falco clarified that HTTP transport is already supported in [Discourse MCP is here!](https://meta.discourse.org/t/-/386983/34?silent=true). ### #bug - **A Free Plan site got “stuck” in read-only mode** , where the “Disable read-only” button wouldn’t persist; @rishabh identified a system-side flag incorrectly forcing read-only in [Cannot disable read-only mode on Free Plan](https://meta.discourse.org/t/-/400870/4?silent=true) (original report: [read more](https://meta.discourse.org/t/-/400870/1?silent=true)). - **Custom sidebar icon picker search is broken** : @Lilly reported the icon selector search field can’t be typed into (reproducible even in [safe mode](https://meta.discourse.org/t/53504?silent=true)) in [Cannot search for icon by name in custom sidebar section configuration modal](https://meta.discourse.org/t/-/400945/1?silent=true). - **Admin category settings + plugins collision** : plugin-provided settings weren’t saving cleanly, and the discussion continued around the admin UI changes and what could have better protected plugin authors in [Unable to save category settings made by plugins](https://meta.discourse.org/t/-/400699/11?silent=true) (related context: [Simplified category setup](https://meta.discourse.org/t/-/394971/1?silent=true)). - **Structured data validation remains spotty for some pages** : Google checks still failing for certain topic/post types (including posts with YouTube embeds) in [Missing field ‘text’ (in ‘mainEntity.suggestedAnswer’)](https://meta.discourse.org/t/-/399974/13?silent=true). ### #Support - **Discourse ID, OAuth2, and 2FA expectations got untangled** : @jomaxro clarified that when using external logins, 2FA enforcement must live at the identity provider (and local enforcement isn’t supported without local logins) in [Discourse ID and 2FA](https://meta.discourse.org/t/-/400910/14?silent=true) (solution post: [read more](https://meta.discourse.org/t/-/400910/2?silent=true)). - **Free Plan signup blocked by “email not permitted”** : a Discourse ID site-creation attempt failed until the user switched to a different email domain in [I am unable to register for a free Discourse site](https://meta.discourse.org/t/-/400900/1?silent=true) (solution details: [read more](https://meta.discourse.org/t/-/400900/2?silent=true)). - **Welcome banner image sizing guidance** : @awesomerobot provided minimum dimensions for both the theme component and the built-in feature in [What’s the background image size for the Welcome Banner?](https://meta.discourse.org/t/-/400767/2?silent=true) (related: [Welcome Link Banner](https://meta.discourse.org/t/-/218743/1?silent=true)). - **“Diff is too complex to display” explained** : @zogstrip broke down the diff “comparison budget” and the hard ceiling that prevents runaway compute in [Diff is too complex to display](https://meta.discourse.org/t/-/400810/2?silent=true). - **Redis `FLUSHALL` as a troubleshooting tool (with warnings)**: a host shared that flushing Redis cleared a stuck “Updating” admin state in [Redis Flushall](https://meta.discourse.org/t/-/400936/1?silent=true), and @RGJ cautioned it logs users out and wipes Sidekiq jobs in [their follow-up](https://meta.discourse.org/t/-/400936/2?silent=true). ### #ux / #development - **Login-required sites and the “landing page” before `/login`** : discussion revisited why the homepage may show a screen with a Login button first, with @pmusaraj explaining the rationale and the narrow skip-case setting in [Disable initial page that re-directs to /login](https://meta.discourse.org/t/-/400773/5?silent=true) (and @zogstrip noting the homepage edge-case — [read more](https://meta.discourse.org/t/-/400773/4?silent=true)). - **Customizing the `/login` page wording (two related threads)**: admins wanted to change “Welcome back” and add disclaimer-like text near the login button; guidance pointed to translation keys such as `js.login.header_title` in [How do i change “Welcome Back” on /login](https://meta.discourse.org/t/-/400930/3?silent=true), plus parallel exploration of “login disclaimer” equivalents in [Add text for /login (like js.create\_account.disclaimer for /signup)](https://meta.discourse.org/t/-/400886/1?silent=true) (related technique: [Find a translation key with verbose localization](https://meta.discourse.org/t/-/134651/1?silent=true)). - **Free Plan shutdown timeline confusion continues** : users reported unexpectedly fast takedowns after warning emails in [Misleading free plan shutdown timeline](https://meta.discourse.org/t/-/400747/5?silent=true) (broader Free Plan context: [You’re invited to try the Discourse Free Plan (Beta)](https://meta.discourse.org/t/-/395632/1?silent=true)). ### #customization:theme component - **New “Wikipedia Lookup” theme component shipped** : @NateDhaliwal released a tooltip-based lookup tool with install instructions in [Wikipedia Lookup](https://meta.discourse.org/t/-/400884/1?silent=true), then quickly added configuration for non-English base URLs in [a follow-up](https://meta.discourse.org/t/-/400884/5?silent=true) (docs referenced: [How to install a theme or theme component](https://meta.discourse.org/t/-/63682/1?silent=true), [Beginner’s guide to using Discourse Themes](https://meta.discourse.org/t/-/91966/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @chapoi joined the conversation celebrating Discourse’s open-source stance in [Discourse is Not Going Closed Source](https://meta.discourse.org/t/-/400863/6?silent=true) and flagged the read-only issue for deeper investigation in [Cannot disable read-only mode on Free Plan](https://meta.discourse.org/t/-/400870/2?silent=true). - @jomaxro clarified current policy around trials (no credit card by default, with anti-abuse exceptions) in [Sample Forum to See Admin Features?](https://meta.discourse.org/t/-/392680/12?silent=true), and handled Discourse ID / 2FA expectations in [Discourse ID and 2FA](https://meta.discourse.org/t/-/400910/14?silent=true) (including the earlier solution post — [read more](https://meta.discourse.org/t/-/400910/2?silent=true)). - @manuel spotlighted improvements to the Discourse releases site while replying to the open-source blog post in [Discourse is Not Going Closed Source](https://meta.discourse.org/t/-/400863/8?silent=true). - @awesomerobot cleaned up outdated guidance by archiving an old topic reference in [Sample Forum to See Admin Features?](https://meta.discourse.org/t/-/392680/10?silent=true), provided exact welcome banner sizing recommendations in [What’s the background image size for the Welcome Banner?](https://meta.discourse.org/t/-/400767/2?silent=true), and helped locate the correct site text key for login wording in [How do i change “Welcome Back” on /login](https://meta.discourse.org/t/-/400930/2?silent=true). - @zogstrip explained why Discourse intentionally stops “too expensive” diffs in [Diff is too complex to display](https://meta.discourse.org/t/-/400810/2?silent=true), and dug into the login landing-page edge-case while discussing possible settings changes in [Disable initial page that re-directs to /login](https://meta.discourse.org/t/-/400773/4?silent=true). - @Falco confirmed that HTTP transport is already available for MCP usage in [Discourse MCP is here!](https://meta.discourse.org/t/-/386983/34?silent=true). - @pmusaraj provided product rationale for keeping a login landing screen (community context, signup/login affordances) and pointed out the “single external login method” exception in [Disable initial page that re-directs to /login](https://meta.discourse.org/t/-/400773/5?silent=true). - @rishabh resolved a Free Plan read-only misfire and linked it to timing-related work already being tracked, in [Cannot disable read-only mode on Free Plan](https://meta.discourse.org/t/-/400870/4?silent=true) (with extra context pointing back to [Misleading free plan shutdown timeline](https://meta.discourse.org/t/-/400747/5?silent=true)). - @tgxworld weighed in on how to reliably detect deprecated DB columns for [Data Explorer](https://meta.discourse.org/t/32566?silent=true) (suggesting readonly as a stronger signal) in [Coping with deprecated columns in Data Explorer](https://meta.discourse.org/t/-/400264/3?silent=true). - @jordan.vidrine checked scope/availability of changes being discussed in [Modernizing the Foundation theme](https://meta.discourse.org/t/-/395331/74?silent=true). * * * Yesterday’s moral: keep your sites _out_ of read-only, your login copy _customizable_, and your diffs _under budget_ — and you’ll have a surprisingly peaceful day on Meta. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 19, 2026, 5:01오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/808 "2026-04-19T05:01:32Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, **[meta.discourse.org](http://meta.discourse.org)** saw **52 new posts** across **8 new topics**. **Top contributors (posts + likes in the last 24h):** | User | New posts | Likes received | | --- | --- | --- | | @Moin | 4 | 12 | | @merefield | 3 | 10 | | @RGJ | 4 | 8 | | @Lilly | 5 | 5 | | @gilles | 5 | 3 | | @Ed_S | 3 | 3 | | @elmuerte | 1 | 4 | | @mcwumbly | 1 | 3 | | @NateDhaliwal | 1 | 3 | | @nat | 1 | 2 | **Team presence:** Discourse Team members active today included **@mcwumbly** and **@nat** (see details in [Activity by the @team Group](#activity-by-the-team-group)). * * * ## Interesting Topics ### #blog - @elmuerte and @RGJ pushed back strongly on the idea that open source is “dead,” arguing that Discourse (and its dependencies) benefit from open ecosystems, and that _security by obscurity doesn’t work_ in practice—especially given that vulnerabilities in upstream components are still publicly disclosed ([read more](https://meta.discourse.org/t/-/400863/11?silent=true), [read more](https://meta.discourse.org/t/-/400863/14?silent=true)). Related: a side discussion touched on automated update workflows and why “just turn on auto-updates” can be risky for self-hosting ([read more](https://meta.discourse.org/t/-/400863/13?silent=true), [read more](https://meta.discourse.org/t/-/241232/1?silent=true)). ### #General - A Chinese-language thread asked why there isn’t a widely-used open source Android app for Discourse; replies noted that Discourse’s PWA support (including notifications on iOS/Android) has reduced the need for a native wrapper, and pointed to earlier discussions about app conversion and Play Store presence ([read more](https://meta.discourse.org/t/-/400947/5?silent=true), [read more](https://meta.discourse.org/t/-/378700/10?silent=true), [read more](https://meta.discourse.org/t/-/135040/1?silent=true)). ### #Site feedback - Confusion surfaced around why **some topics have Post Voting enabled and others don’t** ; @NateDhaliwal spotted inconsistent behavior between two topics, @Moin suggested it might have been manually selected during topic creation, and @mcwumbly confirmed the team will investigate ([read more](https://meta.discourse.org/t/-/400961/1?silent=true), [read more](https://meta.discourse.org/t/-/400961/3?silent=true)) #post-voting. - In ongoing work on the Meta theme redesign, @cuo_wu asked how Meta resolved the “filled heart icon on like” behavior and wanted to replicate it on their own site—another small but telling example of how design details affect perceived polish ([read more](https://meta.discourse.org/t/-/400013/21?silent=true)) #meta-theme-feedback #meta-redesign-2026. ### #bug - A deep dive into **AI Translation intermittently skipping locales** continued: @Denis_Kovalenko reported “randomly skipped” languages (not only Portuguese), plus inconsistent title/body translation; @nat suggested checking LLM context window limits and cautioned against “GPT mini” translation quality, while @RGJ surfaced backend 503 errors and questioned retry behavior on translation jobs ([read more](https://meta.discourse.org/t/-/400612/8?silent=true), [read more](https://meta.discourse.org/t/-/400612/12?silent=true), [read more](https://meta.discourse.org/t/-/400612/13?silent=true)) #ai #dynaloc. Related: enabling hidden verbose logs required knowing about hidden site settings ([read more](https://meta.discourse.org/t/-/400612/10?silent=true), [read more](https://meta.discourse.org/t/-/308773/1?silent=true)). - A mobile UI regression/quirk was reported where the “add user” dropdown modal can jump _above the visible viewport_, making it hard to complete actions like adding users to groups or inviting users to PMs—especially frustrating because swiping tends to dismiss the modal instead of bringing it back into view ([read more](https://meta.discourse.org/t/-/400974/1?silent=true)) #mobile. ### #Support - A thread on **Redis `FLUSHALL`** turned into a practical discussion about troubleshooting “stuck updates” and the difference between Redis restart vs destructive flush; @Ed_S clarified Redis persistence, @RGJ corrected the “in-memory only” misconception, and @Lilly noted that UI-based updating has been improving (even from a phone), though CLI remains more reliable for many admins ([read more](https://meta.discourse.org/t/-/400936/4?silent=true), [read more](https://meta.discourse.org/t/-/400936/8?silent=true), [read more](https://meta.discourse.org/t/-/400936/9?silent=true)). - A Chinese-language question asked for a “better global Chinese plugin” because some admin setting names remain English; @Moin explained why keeping _setting keys consistent across languages_ helps support/debugging, and linked ongoing ideas to add translated subtitles rather than fully translating setting names ([read more](https://meta.discourse.org/t/-/400973/2?silent=true), [read more](https://meta.discourse.org/t/-/205100/8?silent=true), [read more](https://meta.discourse.org/t/-/396962/1?silent=true), [read more](https://meta.discourse.org/t/-/344861/14?silent=true)). - A new support question asked whether Discourse supports a “variable” or macro to avoid repeating the same large image markup thousands of times in wiki tables—highlighting real-world post length/maintenance constraints when content gets very large ([read more](https://meta.discourse.org/t/-/400979/1?silent=true)). - Another support thread (Chinese) reported a plugin replacement that “didn’t succeed,” shared with a screenshot—early signal of a potentially common deployment/configuration pitfall to be diagnosed next ([read more](https://meta.discourse.org/t/-/400980/1?silent=true)). - Email configuration came up again: someone needing to move from SMTP basic auth to OAuth learned that some providers (like MailEnable) don’t support OAuth for SMTP in the same way as Google/Microsoft, implying a switch to a compatible relay/provider may be required ([read more](https://meta.discourse.org/t/-/367023/12?silent=true)). ### #contribute:feature - Chat feature feedback: @gilles requested the ability to create **polls in chat channels** , plus better defaults and permissions; @Lilly asked to split the default-channel-configuration request into its own topic for clearer tracking and prioritization ([read more](https://meta.discourse.org/t/-/400955/1?silent=true), [read more](https://meta.discourse.org/t/-/400955/2?silent=true)) #polls #chat. - Following up, @gilles posted a dedicated request for **default settings when creating new chat channels** (pre-configuring threads, etc.) and questioned why channel creation is restricted to mods/admins; replies suggested the restriction may help prevent channel spam ([read more](https://meta.discourse.org/t/-/400956/1?silent=true), [read more](https://meta.discourse.org/t/-/400956/2?silent=true)) #chat. ### #customization:theme component - A long-running theme component thread on **forcing a mobile homepage** got fresh commentary: @merefield argued the problem is increasingly _layout-based rather than route-based_, and described experimenting with a sidebar “Categories column” that naturally disappears on mobile—same URL, adaptive layout ([read more](https://meta.discourse.org/t/-/95705/34?silent=true)). - The **Wikipedia Lookup** theme component got a useful configuration tip: setting the `wikipedia base url` can point not only to language-specific Wikipedia subdomains, but even to alternative wiki hosts (e.g., a Miraheze wiki), making the component more flexible than it first appears ([read more](https://meta.discourse.org/t/-/400884/7?silent=true)). - A customization gotcha: changing the “New Topic” button label via a component also changed the “Reply” label, suggesting shared i18n keys or unintended coupling in the component’s implementation ([read more](https://meta.discourse.org/t/-/269086/31?silent=true)). ### #wordpress - [WP Discourse](https://github.com/discourse/wp-discourse) publishing edge case: an Italian-language report described a WordPress post containing _only a large gallery_ failing to mirror correctly into Discourse, instead pulling GDPR/footer text—suggesting the excerpting/parsing logic may be grabbing the wrong content when there’s no traditional body text ([read more](https://meta.discourse.org/t/-/400954/1?silent=true)). Related: another [WP Discourse](https://github.com/discourse/wp-discourse) feature thread continued about filtering which comments sync back, and the limitations of post-level tagging signals today ([read more](https://meta.discourse.org/t/-/400422/3?silent=true)). ### #customization:plugin - “Discourse Category Lockdown” saw renewed interest in allowing _teaser visibility_ (e.g., show first posts in locked categories to motivate subscriptions), a recurring monetization/course-delivery use case ([read more](https://meta.discourse.org/t/-/70649/132?silent=true)) #pavilion. ### #Announcements - Boosts feedback kept rolling in: @Andrew_Rowe shared that boosts turned out to be surprisingly useful as a lightweight “this matters” signal when a like feels too small but a reply feels too noisy, while others suggested better ways to locate and manage _your own_ boosts in long lists ([read more](https://meta.discourse.org/t/-/399835/81?silent=true), [read more](https://meta.discourse.org/t/-/399835/80?silent=true)). ### #Site Management - A practical admin note landed in the evergreen moderation guide thread: @Lilly reminded admins that the moderation guide link is included in the automated “welcome staff” message, and that sites with custom guides should update `system_messages.welcome_staff.text_body_template` to point moderators to the right place ([read more](https://meta.discourse.org/t/-/63116/101?silent=true)) #moderation #explanation. ### #ux - Mobile composer ergonomics remain a pain point: a self-hosting admin shared that editing on a phone can feel cramped, comparing Discourse’s composer space to their phone’s native notes UI as inspiration for better mobile composition patterns ([read more](https://meta.discourse.org/t/-/400393/21?silent=true)) #composer #mobile. * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @mcwumbly acknowledged confusing behavior around Post Voting being enabled inconsistently across topics and confirmed the team is investigating what’s going on ([read more](https://meta.discourse.org/t/-/400961/3?silent=true)). - @nat weighed in on the AI Translation locale-skipping investigation, proposing checks around context window constraints and noting that some smaller/cheaper models perform poorly for translation workloads—useful guidance for anyone tuning #discourse-ai translation quality ([read more](https://meta.discourse.org/t/-/400612/12?silent=true)). * * * _That’s a wrap—yesterday’s Meta was basically a three-course meal of boosts, bots, and Redis buttons daring admins to press them._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 20, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/809 "2026-04-20T05:02:09Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 63** - **New topics (last 24h): 6** **Top users (posts + likes received in the last 24h)** | User | Posts | Likes | Recent highlight | | --- | --- | --- | --- | | @ted | 2 | 17 | Markdown trick for reusable upload labels in [“Some sort of variable to eliminate duplicate text?”](https://meta.discourse.org/t/-/400979/3?silent=true) and open-source reassurance in [“Discourse is Not Going Closed Source”](https://meta.discourse.org/t/-/400863/15?silent=true) | | @Lilly | 8 | 10 | Practical guidance on private custom-field workflows in [“New user filter by custom field and contact”](https://meta.discourse.org/t/-/400989/2?silent=true) and Rails-console steps for hidden ad settings in [“Help enabling a hidden site setting”](https://meta.discourse.org/t/-/401011/2?silent=true) | | @Moin | 5 | 10 | Clarifying plugin limitations and translation scope in [“Globally replace translations”](https://meta.discourse.org/t/-/315695/19?silent=true) plus debugging questions in [the assignee modal thread](https://meta.discourse.org/t/-/400986/6?silent=true) | | @angus | 7 | 3 | Deep dive into Readability/embedding constraints for image-heavy WP posts in [“Pubblicazione post con galleria WordPress su Discourse”](https://meta.discourse.org/t/-/400954/12?silent=true) | | @nathank | 1 | 2 | UX-friendly suggestion for group/message navigation in [“Change default landing page for Groups”](https://meta.discourse.org/t/-/400825/2?silent=true) | | @Lxk520 | 3 | 2 | Screenshots and clarification around what’s actually translatable in [“Globally replace translations”](https://meta.discourse.org/t/-/315695/20?silent=true) | | @Rhod | 1 | 2 | Confirmed success using the theme component in [“Reader Mode”](https://meta.discourse.org/t/-/307916/17?silent=true) | | @stromfeldt | 1 | 1 | Reported integration/UX issues while trying the new embed comments setup in [“Embed Discourse as a full comment system on your site”](https://meta.discourse.org/t/-/399743/18?silent=true) | | @supermathie | 1 | 1 | Raised an MFA-assertion question in [“Discourse ID and 2FA”](https://meta.discourse.org/t/-/400910/18?silent=true) | | @Dmitry_Krasnoperov | 1 | 1 | Requested feature direction and moderation controls in [“Discourse User Feedback”](https://meta.discourse.org/t/-/219002/56?silent=true) | * * * ## Interesting Topics ### #Support - @ted shared a lightweight Markdown approach to _reduce duplicated upload URLs_ using reference-style labels in [“Some sort of variable to eliminate duplicate text?”](https://meta.discourse.org/t/-/400979/3?silent=true) — helpful when you’re repeating the same upload in multiple places. [read more](https://meta.discourse.org/t/-/400979/1?silent=true) - A hosted-Pro admin asked how to _segment new users by private custom fields and contact them in bulk_, with @Lilly outlining options/limitations (Automation/[Data Explorer](https://meta.discourse.org/t/32566?silent=true) vs. plan constraints) in [“New user filter by custom field and contact”](https://meta.discourse.org/t/-/400989/2?silent=true), referencing how to configure fields in [“Creating and configuring custom user fields”](https://meta.discourse.org/t/-/113192/1?silent=true) and potential automation strategies via [“Discourse Automation”](https://meta.discourse.org/t/-/195773/1?silent=true); API privacy tradeoffs also came up via [“Adding non-visible user custom fields to the API”](https://meta.discourse.org/t/-/276618/1?silent=true). [read more](https://meta.discourse.org/t/-/400989/1?silent=true) - Verifying a `*.discourse.group` subdomain in Google Search Console surfaced practical DNS limitations; @Moin pointed to the standard verification guide in [“How to verify a subdomain (mysite.discourse.group) in Google Search Console?”](https://meta.discourse.org/t/-/401003/2?silent=true) via [“Perform Google Search Console verification with Discourse”](https://meta.discourse.org/t/-/107229/1?silent=true). [read more](https://meta.discourse.org/t/-/401003/1?silent=true) - Group UX navigation came up again: a request to change the _default landing tab_ for group pages drew pointers to a sidebar/messages approach in [“Change default landing page for Groups (Members → Activity/Messages?)”](https://meta.discourse.org/t/-/400825/2?silent=true), plus related customization ideas in [“Messages section for sidebar”](https://meta.discourse.org/t/-/389664/1?silent=true) and [“Custom homepage for groups”](https://meta.discourse.org/t/-/199623/1?silent=true). [read more](https://meta.discourse.org/t/-/400825/1?silent=true) - Hidden settings and ad configuration: @Lilly explained that `ad_platform_through_trust_level` is a hidden Discourse AdPlugin setting and showed how to change it via Rails console in [“Help enabling a hidden site setting”](https://meta.discourse.org/t/-/401011/2?silent=true), citing the broader how-to in [“How to Edit Hidden Site Settings”](https://meta.discourse.org/t/-/308773/1?silent=true). [read more](https://meta.discourse.org/t/-/401011/1?silent=true) ### #bug - A report that the _assignee picker can’t be searched/typed into_ when Discourse is used as an iOS homescreen app/PWA is being investigated in [“Why we can’t type the assignee in the search of a post to assign - home screen app”](https://meta.discourse.org/t/-/400986/1?silent=true); responders compared it to broader mobile modal/viewport issues discussed in [“Add user to list modal often appears above the mobile viewport screen”](https://meta.discourse.org/t/-/400974/1?silent=true) and asked for environment details/screenshots in follow-ups like [this question](https://meta.discourse.org/t/-/400986/4?silent=true). [read more](https://meta.discourse.org/t/-/400986/1?silent=true) - Structured data cleanup is still chasing edge cases: after partial improvements, @Richie reported remaining failures around QAPage JSON-LD fields, and @davidb requested example URLs to reproduce in [“Missing field ‘text’ (in ‘mainEntity.suggestedAnswer’)”](https://meta.discourse.org/t/-/399974/15?silent=true) following the latest status update in [the same thread](https://meta.discourse.org/t/-/399974/14?silent=true). [read more](https://meta.discourse.org/t/-/399974/1?silent=true) ### #wordpress - [WP Discourse](https://github.com/discourse/wp-discourse) “Publish” + image galleries ran into a core limitation: @angus explained that the embed pipeline relies on Mozilla’s Readability-style extraction and is _optimized for text_, so image-heavy “gallery-only” posts can scrape poorly in [“Pubblicazione post con galleria WordPress su Discourse”](https://meta.discourse.org/t/-/400954/12?silent=true); the discussion also touched on selector settings in [this follow-up](https://meta.discourse.org/t/-/400954/14?silent=true) and the reality that true 1:1 gallery syncing may require custom plugins in [the latest reply](https://meta.discourse.org/t/-/400954/18?silent=true). [read more](https://meta.discourse.org/t/-/400954/1?silent=true) ### #blog - Community reaction continued on the open-source stance: @ted pushed back on “security by obscurity” narratives and voiced support in [“Discourse is Not Going Closed Source”](https://meta.discourse.org/t/-/400863/15?silent=true). [read more](https://meta.discourse.org/t/-/400863/1?silent=true) ### #customization:plugin - Translation/customization limits were clarified: @Moin explained that the “Globally replace translations” plugin affects frontend locale strings, not arbitrary/untranslatable setting labels, in [“Globally replace translations”](https://meta.discourse.org/t/-/315695/19?silent=true), with adjacent guidance pointing toward editing translatable text via [“Customize text in Discourse”](https://meta.discourse.org/t/-/36092/1?silent=true) and a related explanation referenced in [this linked post](https://meta.discourse.org/t/-/315695/21?silent=true). [read more](https://meta.discourse.org/t/-/315695/1?silent=true) ### #Announcements - Real-world adoption notes (and friction) surfaced for the new embedding approach: @stromfeldt described trying to combine Ghost + membership syncing and still seeing incomplete comment UI/flows in [“Embed Discourse as a full comment system on your site”](https://meta.discourse.org/t/-/399743/18?silent=true), in the context of the Ghost bridge announced in [“Introducing Discourse on Ghost”](https://meta.discourse.org/t/-/257108/1?silent=true). [read more](https://meta.discourse.org/t/-/399743/1?silent=true) ### #development - A Python “no API key” Discourse wrapper sparked a ToS/automation caution: a new library was shared in [“Interact with discourse from Python?”](https://meta.discourse.org/t/-/87543/26?silent=true), and @Moin noted potential ToS conflicts with automated access in [this reply](https://meta.discourse.org/t/-/87543/27?silent=true). [read more](https://meta.discourse.org/t/-/87543/1?silent=true) ### #Support (#free-plan) - Federated login and MFA assurance: @supermathie asked whether an IdP can pass along _proof/attestation of MFA completion_ to the service provider (and what to do if not) in [“Discourse ID and 2FA”](https://meta.discourse.org/t/-/400910/18?silent=true). [read more](https://meta.discourse.org/t/-/400910/1?silent=true) ### #contribute:feature (#login) - A feature request asked for a setting to _disable local signups while still allowing OpenID Connect registrations_, including notes about UI workarounds and approval flows in [“Site setting to disable local sign ups”](https://meta.discourse.org/t/-/401005/1?silent=true) and its follow-up suggesting policy/scoping ideas in [the second post](https://meta.discourse.org/t/-/401005/2?silent=true), with context pointing back to [“Disable initial page that re-directs to /login”](https://meta.discourse.org/t/-/400773/1?silent=true). [read more](https://meta.discourse.org/t/-/401005/1?silent=true) ### #contribute:feature - A workflow/UX enhancement proposal suggested a category-specific “one-touch” control to split/move posts into existing topics in [“Category-toggled one-touch move post”](https://meta.discourse.org/t/-/400983/1?silent=true). [read more](https://meta.discourse.org/t/-/400983/1?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @davidb followed up on remaining Google Search Console structured-data errors, asking for concrete examples to investigate potential edge cases in [“Missing field ‘text’ (in ‘mainEntity.suggestedAnswer’)”](https://meta.discourse.org/t/-/399974/15?silent=true) after @Richie reported unresolved items in [the prior update](https://meta.discourse.org/t/-/399974/14?silent=true). - @supermathie dug into identity-provider MFA semantics—specifically whether IdPs can pass along an “MFA performed” signal/attestation to relying parties—in [“Discourse ID and 2FA”](https://meta.discourse.org/t/-/400910/18?silent=true). * * * Yesterday’s theme: if Readability can’t find your gallery and Rails won’t let you `exit`, at least meta will still help you untangle it all by morning. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 21, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/810 "2026-04-21T05:02:14Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** **142** - **New topics (last 24h):** **14** **Top users (posts / likes in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @Lilly | 15 | 30 | | @chapoi | 7 | 21 | | @Canapin | 13 | 18 | | @Falco | 8 | 14 | | @zogstrip | 5 | 14 | | @Moin | 11 | 14 | | @RGJ | 3 | 12 | | @darkpixlz | 10 | 10 | | @supermathie | 3 | 9 | | @merefield | 2 | 7 | A big share of the conversation clustered around the refreshed reactions/likes experience and its UX follow-ups in [read more](https://meta.discourse.org/t/-/389820/51?silent=true). * * * ## Interesting Topics ### #contribute:feature - The reactions UI got a major usability boost with “show _all_ likes/reactions” returning in a new panel; @chapoi shared progress and final tweaks, while feedback covered blank space on low-reaction posts and mobile scrolling fixes in [read more](https://meta.discourse.org/t/-/389820/51?silent=true). (Related: keeping reactions anchored consistently was bundled into the same work in [read more](https://meta.discourse.org/t/-/315144/4?silent=true).) - A thoughtful proposal asked whether Discourse could support “future self” post-approval (or trusted friends) to help users during episodic unwellness—essentially a voluntary delay/approval workflow—starting in [read more](https://meta.discourse.org/t/-/401050/1?silent=true). - A combined feature request suggested **grouping Personal Messages** (flags, warnings, group messages, etc.) and also collaborative post drafting; responders pointed to Shared Drafts as an existing solution for staff collaboration in [read more](https://meta.discourse.org/t/-/401088/1?silent=true) (see also Shared Drafts [read more](https://meta.discourse.org/t/-/83493/1?silent=true)). ### #customization:plugin - Communiteq published **Communiteq Power Tools** , a “single plugin” bundle of practical admin enhancements (including exposing otherwise hidden site settings) and invited suggestions for what to fold in next in [read more](https://meta.discourse.org/t/-/401064/1?silent=true). (Install guidance reference: [read more](https://meta.discourse.org/t/-/19157/1?silent=true).) - The **Discourse Private Replies** plugin hit friction with the newer category settings UI; @RGJ noted multiple plugins were caught off-guard and suggested temporarily disabling `enabled_simplified_category_creation` until updates land in [read more](https://meta.discourse.org/t/-/146712/100?silent=true) (background on the setting: [read more](https://meta.discourse.org/t/-/400699/4?silent=true)). ### #development - A revived thread on interacting with Discourse from Python debated _automation vs. exploration_, ToS responsibility, and rate limits; @david and @supermathie clarified that tooling can be fine, but bulk automation/scraping is where problems start in [read more](https://meta.discourse.org/t/-/87543/31?silent=true). ### #Support - A “no email notifications” report turned into a hosting/support-boundaries discussion: community members suggested checking email logs, and @supermathie explained Meta can help with standard Discourse behavior but can’t troubleshoot third-party host configurations in [read more](https://meta.discourse.org/t/-/401077/13?silent=true) ([standard install](https://meta.discourse.org/t/142537?silent=true) reference: [read more](https://meta.discourse.org/t/-/142537/1?silent=true)). - A formatting question asked how to **force horizontal scrolling for tables** when they’re in a “too wide to fit, not wide enough to scroll” middle ground; a practical workaround using non‑breaking spaces (` `) was shared in [read more](https://meta.discourse.org/t/-/401103/4?silent=true). - Discourse ID + MFA expectations were explored: @pmusaraj explained why an MFA flag ideally needs OIDC (Discourse ID is currently OAuth2) and outlined the implementation complications in [read more](https://meta.discourse.org/t/-/400910/19?silent=true). ### #bug - A UX-breaking email issue was raised: when “Private email” is enabled, outgoing emails can omit a usable topic link—making notifications confusing for recipients—in [read more](https://meta.discourse.org/t/-/401078/1?silent=true). - A mobile UX bug where “Add user to list” modals appear _above_ the viewport got a proposed fix from @awesomerobot (and a call for modal/menu review) in [read more](https://meta.discourse.org/t/-/400974/2?silent=true). - Redis `FLUSHALL` fallout that could persist across rebuilds prompted core + Docker Manager fixes being linked by @Falco in [read more](https://meta.discourse.org/t/-/400936/13?silent=true). - SSO configuration edge case: a provider URL containing `#` was flagged as a protocol violation (fragments are client-side only) in [read more](https://meta.discourse.org/t/-/400782/2?silent=true). ### #ux - A set of concrete mobile **review queue** alignment/spacing issues (headers, margins, overly-wide textarea, topic title layout) was reported—and quickly followed by a cleanup PR—in [read more](https://meta.discourse.org/t/-/401041/2?silent=true). - Mobile post revision history controls were reported as **uniformly truncated** , proposing two-line buttons and better modal sizing in [read more](https://meta.discourse.org/t/-/401038/1?silent=true) (and a tag discussion spun up alongside in [read more](https://meta.discourse.org/t/-/401040/1?silent=true)). ### #Site feedback - Meta’s tag hygiene discussion continued: users noted “restricted”/internal tags showing up in the public tag picker; the thread dug into permission expectations and whether tag visibility should respect category security better in [read more](https://meta.discourse.org/t/-/364105/14?silent=true). (Side-effect note: tagging edits interacting with `#fixed` and reopening behavior surfaced in [read more](https://meta.discourse.org/t/-/397606/91?silent=true), with an example bug reference [read more](https://meta.discourse.org/t/-/292414/1?silent=true).) - A performance suspicion: #disco-toc may contribute to slow rendering on posts with many headings; safe-mode comparisons and videos were shared to help isolate the issue in [read more](https://meta.discourse.org/t/-/401085/1?silent=true) (example post referenced: [read more](https://meta.discourse.org/t/-/326439/4?silent=true)). ### #contribute:feature (Embedding) - Embedded comments got more polish: Tecnoblog reported mobile overflow + overlay issues in the redesigned comment form; fixes were shipped quickly, and Safari-specific behavior and auto-dark-mode synchronization came up in follow-ups in [read more](https://meta.discourse.org/t/-/400721/26?silent=true). (Related: full embed announcement thread context in [read more](https://meta.discourse.org/t/-/399743/20?silent=true); dark mode switching reference in [read more](https://meta.discourse.org/t/-/161593/1?silent=true); older embedded dark-mode discussion [read more](https://meta.discourse.org/t/-/184347/1?silent=true).) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @chapoi pushed the updated reactions viewer toward the finish line—sharing a “live on Meta” preview and iterating on spacing/UX details in [read more](https://meta.discourse.org/t/-/389820/51?silent=true), and later confirming the “new normal” alignment behavior in [read more](https://meta.discourse.org/t/-/389820/62?silent=true). @chapoi also confirmed the reactions placement request was effectively bundled into the same work in [read more](https://meta.discourse.org/t/-/315144/4?silent=true). - @zogstrip landed (and linked) a mobile scroll fix for the reactions panel in [read more](https://meta.discourse.org/t/-/389820/55?silent=true), then jumped into Meta’s tag-visibility UX debate—acknowledging the balance and agreeing to investigate whether tags are shown when they shouldn’t be in [read more](https://meta.discourse.org/t/-/364105/17?silent=true). Separately, @zogstrip worked on breadcrumb/race-condition behavior on the backups page in [read more](https://meta.discourse.org/t/-/400730/3?silent=true), and confirmed a regression fix for icon search in sidebar section configuration in [read more](https://meta.discourse.org/t/-/400945/3?silent=true). - @Falco handled multiple embed-related improvements and confirmations—crediting the mobile-first comment form work, fixing `embedMinHeight`, and confirming mobile width fixes in [read more](https://meta.discourse.org/t/-/400721/23?silent=true) and [read more](https://meta.discourse.org/t/-/400721/26?silent=true). @Falco also clarified Safari-only “Allow access” behavior and “not logged in” embed mode semantics in [read more](https://meta.discourse.org/t/-/399743/20?silent=true). On infra, @Falco linked fixes to prevent Redis flush issues persisting across rebuilds in [read more](https://meta.discourse.org/t/-/400936/13?silent=true). And on nested replies testing, @Falco reiterated why non-linear discussion is inherently trickier and noted a missing “Parent post” link in [read more](https://meta.discourse.org/t/-/398759/88?silent=true) (background argument: [read more](https://meta.discourse.org/t/-/63172/2?silent=true)). - @supermathie clarified Discourse’s stance on “tools vs. automation” in the Python access discussion—encouraging learning and API exploration while discouraging bulk scraping/undue load—in [read more](https://meta.discourse.org/t/-/87543/33?silent=true). @supermathie also reported a sharp email UX regression where private-email mode removes the helpful topic link from outgoing mail in [read more](https://meta.discourse.org/t/-/401078/1?silent=true), and helped set expectations about what Meta can/can’t troubleshoot for third-party hosted instances in [read more](https://meta.discourse.org/t/-/401077/13?silent=true). - @awesomerobot continued a run of mobile UI fixes: a pass on mobile reviewables (alignment, margins, textarea width, layout) was posted in [read more](https://meta.discourse.org/t/-/401041/2?silent=true); a fix attempt for list modals appearing above the viewport landed in [read more](https://meta.discourse.org/t/-/400974/2?silent=true); and a topic-list tag cut-off / blank-line issue received a “should fix it” PR link in [read more](https://meta.discourse.org/t/-/400298/2?silent=true). - @pmusaraj helped triage the missing-email-notifications report by pointing to likely email configuration/hosting factors in [read more](https://meta.discourse.org/t/-/401077/3?silent=true), and provided a detailed breakdown of what it would take for Discourse ID to convey/require MFA status via OIDC in [read more](https://meta.discourse.org/t/-/400910/19?silent=true). - @david weighed in on public API access tooling, noting official tooling supports unauthenticated access too and emphasizing rate limits + ToS responsibility in [read more](https://meta.discourse.org/t/-/87543/31?silent=true). - @manuel continued Meta theme work, including Lucide icon component guidance and design polish banter (“just think about it, and it is fixed”) in [read more](https://meta.discourse.org/t/-/400013/22?silent=true) and [read more](https://meta.discourse.org/t/-/400013/27?silent=true). - @markvanlan clarified that the “view as flat” option in nested replies testing is now behind a group site setting (staff-only by default) to avoid pushing end-users into thinking about modes in [read more](https://meta.discourse.org/t/-/398759/84?silent=true). - @sam confirmed that `#` in an SSO provider URL is a protocol violation (client-side fragments) in [read more](https://meta.discourse.org/t/-/400782/2?silent=true). * * * Yesterday’s vibe: if your reactions panel doesn’t scroll, your tags leak into the picker, and your embed toolbar overflows on mobile—just think about it really hard and the fixes will ship. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [4월 22, 2026, 5:02오전 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/811 "2026-04-22T05:02:06Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **In the last 24 hours:** **167 new posts** across **23 new topics**. ### Top contributors (posts + likes) | User | Posts | Likes | Recent reference | | --- | --- | --- | --- | | @Moin | 15 | 30 | Spotted a homepage regression in the new Meta theme ([read more](https://meta.discourse.org/t/-/401100/21?silent=true)) | | @awesomerobot | 8 | 29 | Explained the broader goal of the new Meta homepage content mix ([read more](https://meta.discourse.org/t/-/401100/8?silent=true)) | | @derek | 5 | 27 | Shipped + hotfixed the updated Meta Branded homepage ([read more](https://meta.discourse.org/t/-/401100/23?silent=true)) | | @lindsey | 3 | 27 | Announced moderation and workflow improvements ([read more](https://meta.discourse.org/t/-/401132/1?silent=true)) | | @Canapin | 13 | 25 | Filed several crisp mobile/UX reports ([read more](https://meta.discourse.org/t/-/401114/1?silent=true)) | | @nat | 5 | 19 | Rolled out [Data Explorer](https://meta.discourse.org/t/32566?silent=true) charting upgrades ([read more](https://meta.discourse.org/t/-/401130/1?silent=true)) | | @Ed_S | 7 | 16 | Helped debug self-host update UX and CLI expectations ([read more](https://meta.discourse.org/t/-/401160/14?silent=true)) | | @Lilly | 12 | 15 | Guided self-host troubleshooting + shipped a theme-component fix ([read more](https://meta.discourse.org/t/-/394049/14?silent=true)) | | @merefield | 5 | 15 | Gave practical design guidance to modernize a community’s UI ([read more](https://meta.discourse.org/t/-/401141/5?silent=true)) | | @NateDhaliwal | 7 | 12 | Solved how to add custom category icons in the sidebar ([read more](https://meta.discourse.org/t/-/401106/3?silent=true)) | ### New topics started (23) [Updates to the Meta Branded theme homepage](https://meta.discourse.org/t/-/401100/1?silent=true), [Que penses vos utilisateurs sur votre interface discourse?](https://meta.discourse.org/t/-/401141/1?silent=true), [Truncated very long button label on user deletion modal](https://meta.discourse.org/t/-/401116/1?silent=true), [Getting notified that out of date but not able to update](https://meta.discourse.org/t/-/401160/1?silent=true), [Event’s date next to the title lacks styling on mobile](https://meta.discourse.org/t/-/401114/1?silent=true), [More flexible category-level topic and reply approvals](https://meta.discourse.org/t/-/401132/1?silent=true), [How can I add custom category icons to the sidebar?](https://meta.discourse.org/t/-/401106/1?silent=true), [Pin or un-pin topics in bulk](https://meta.discourse.org/t/-/401138/1?silent=true), [Improvements to Topic Voting: Voting access, notification prompts, and Hot sorting](https://meta.discourse.org/t/-/401156/1?silent=true), [Looking for a technical community consultant (Discourse setup & product integration)](https://meta.discourse.org/t/-/401131/1?silent=true), [Tag topics using AI](https://meta.discourse.org/t/-/401178/1?silent=true), [我想请教下这个文件/var/www/discourse/vendor/data/RT\_sRGB.icm是用来干什么的？](https://meta.discourse.org/t/-/401148/1?silent=true), [More charting options for Data Explorer](https://meta.discourse.org/t/-/401130/1?silent=true), [接口报错500](https://meta.discourse.org/t/-/401118/1?silent=true), [Empty space below unanswered topics](https://meta.discourse.org/t/-/401115/1?silent=true), [Idea: on mobile, show anons signup and login buttons on hamburger menu](https://meta.discourse.org/t/-/401173/1?silent=true), [标题过长，超出边界](https://meta.discourse.org/t/-/401152/1?silent=true), [ESR Usage Help](https://meta.discourse.org/t/-/401203/1?silent=true), [Mobile Rendering issues (mostly PWA)](https://meta.discourse.org/t/-/401109/1?silent=true), [Discourse to Markdown Plugin](https://meta.discourse.org/t/-/401199/1?silent=true), [解决错误日志中MaxMindDB警告](https://meta.discourse.org/t/-/401193/1?silent=true), [Discourse logs sent to wrong S3](https://meta.discourse.org/t/-/401176/1?silent=true), [Save the website for offline viewing](https://meta.discourse.org/t/-/401122/1?silent=true) * * * ## Interesting Topics ### #contribute:site-feedback - @derek rolled out **a redesigned Meta Branded homepage** with “hot topics”, events, and contributor highlights; follow-up discussion covered video placement, logged-in vs anon parity, and a quick theme fix after a core change ([read more](https://meta.discourse.org/t/-/401100/1?silent=true)). Related: the underlying layout work leans on the early **Blocks API** preview mentioned in context ([read more](https://meta.discourse.org/t/-/401100/18?silent=true)) and its broader write-up ([read more](https://meta.discourse.org/t/-/400013/1?silent=true)). - Category structure feedback continued: @Canapin argued the new hierarchy can be harder to navigate/link (especially on mobile), while others noted search and discoverability tradeoffs ([read more](https://meta.discourse.org/t/-/396306/71?silent=true)). This tied directly into the UX request about lengthy inline subcategory mentions ([read more](https://meta.discourse.org/t/-/397217/1?silent=true)). - The Meta Branded theme refresh thread picked up another UI polish report: hover styling in preferences selectors can become hard to read compared to Horizon ([read more](https://meta.discourse.org/t/-/397246/54?silent=true)). - Tag translation expectations got clarified: @nat explained AI translations currently apply broadly (topics/posts/categories/tags), and recommended editing tag translations directly (or adjusting the agent prompt) to “set-and-forget” ([read more](https://meta.discourse.org/t/-/399570/14?silent=true)). * * * ### #announcements - [Data Explorer](https://meta.discourse.org/t/32566?silent=true) gained **more charting options** and smarter defaults based on result “shape”, making queries easier to interpret at a glance ([read more](https://meta.discourse.org/t/-/401130/1?silent=true)). Background: the plugin itself remains the familiar [Data Explorer](https://meta.discourse.org/t/32566?silent=true) toolset ([read more](https://meta.discourse.org/t/-/32566/1?silent=true)). - Category moderation controls are now **more flexible** : approvals can be required for _everyone except_ certain groups, or _no one except_ certain groups, all organized under a new Moderation tab in category settings ([read more](https://meta.discourse.org/t/-/401132/1?silent=true)). - Bulk actions now support **pinning/unpinning multiple topics at once** , helping admins manage “must read” content without repetitive clicks ([read more](https://meta.discourse.org/t/-/401138/1?silent=true)). - Topic Voting shipped a cluster of UX upgrades: a persistent vote button while scrolling, post-vote notification prompts, and Hot sorting improvements for idea backlogs ([read more](https://meta.discourse.org/t/-/401156/1?silent=true)). Related: the Topic Voting plugin overview ([read more](https://meta.discourse.org/t/-/40121/1?silent=true)) and the “ideas category” creation flow it builds on ([read more](https://meta.discourse.org/t/-/399365/1?silent=true)). - A new how-to guide showed how to **auto-tag topics using AI triage + Discourse Automation** , including prerequisites, agent prompt guidance, and setup details ([read more](https://meta.discourse.org/t/-/401178/1?silent=true)). Related building blocks: Discourse AI ([read more](https://meta.discourse.org/t/-/259214/1?silent=true)), Discourse Automation ([read more](https://meta.discourse.org/t/-/195773/1?silent=true)), and LLM settings documentation ([read more](https://meta.discourse.org/t/-/319903/1?silent=true)). * * * ### #ux (#mobile) - A mobile UI issue in the user deletion flow: an extremely long confirmation label overflows and feels awkward; @awesomerobot proposed a cleaner dropdown-first confirmation design, and linked a core PR ([read more](https://meta.discourse.org/t/-/401116/2?silent=true)). @jordan.vidrine suggested shortening the scary button copy to something like “I understand” ([read more](https://meta.discourse.org/t/-/401116/4?silent=true)). - Event topics on mobile showed the **date concatenated into the title** without consistent styling; the discussion pointed to an existing plugin thread mention and a targeted fix PR ([read more](https://meta.discourse.org/t/-/401114/1?silent=true)). - A subtle layout concern: unanswered topics show awkward empty space around the topic progress / reply-presence area, prompting a deeper look at reserved layout height vs consistent placement ([read more](https://meta.discourse.org/t/-/401115/1?silent=true)). - A signup UX proposal: on narrow mobile widths, anon users may miss the _Sign Up_ entry point, so the suggestion is to surface login/signup actions in the hamburger menu as well ([read more](https://meta.discourse.org/t/-/401173/1?silent=true)). Historical context for the same issue was linked too ([read more](https://meta.discourse.org/t/-/45411/1?silent=true)). - Another mobile report flagged **overlong titles overflowing boundaries** ; the topic collected examples and cross-linked related filesystem/MaxMind discussion where the issue was encountered ([read more](https://meta.discourse.org/t/-/401152/1?silent=true)). * * * ### #Community Building - A French-language discussion asked whether Discourse “feels dated” vs Discord; replies emphasized the _asynchronous, durable_ nature of topics and suggested reducing conflicting custom styling for a more cohesive, modern feel ([read more](https://meta.discourse.org/t/-/401141/1?silent=true)). * * * ### #bug - AI Translation reliability concerns continued: a report described silent skips on transient LLM 503 errors and asked for clearer admin visibility; responses covered token-cost tradeoffs and noted background backfill retries do occur ([read more](https://meta.discourse.org/t/-/400612/16?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @derek shipped the **Meta Branded homepage update** and followed up quickly on a breakage caused by a recent core change, confirming the theme was updated and resolved ([read more](https://meta.discourse.org/t/-/401100/23?silent=true)). - @awesomerobot clarified the strategic intent behind the homepage’s broader content mix (appealing beyond developers) in the same rollout thread ([read more](https://meta.discourse.org/t/-/401100/8?silent=true)), proposed a redesigned flow for the deletion modal UX issue ([read more](https://meta.discourse.org/t/-/401116/2?silent=true)), and confirmed a mobile events styling fix was reasonable ([read more](https://meta.discourse.org/t/-/401114/3?silent=true)). - @lindsey delivered multiple admin-facing workflow improvements: flexible category approvals ([read more](https://meta.discourse.org/t/-/401132/1?silent=true)), bulk pin/unpin actions ([read more](https://meta.discourse.org/t/-/401138/1?silent=true)), and a set of upgrades to the Topic Voting experience ([read more](https://meta.discourse.org/t/-/401156/1?silent=true)). - @nat announced **expanded [Data Explorer](https://meta.discourse.org/t/32566?silent=true) charting** ([read more](https://meta.discourse.org/t/-/401130/1?silent=true)), and helped clarify expectations and mechanics around AI translation retries/backfill behavior during intermittent provider errors ([read more](https://meta.discourse.org/t/-/400612/22?silent=true)). - @markvanlan continued working through nested reply UX/notification edge-cases—especially how consolidated “N new replies” notifications can hide earlier replies, and what URL/query-param approaches might help ([read more](https://meta.discourse.org/t/-/398759/91?silent=true)). - @Falco added perspective on “parent context” navigation expectations vs Reddit/HN and aligned on the intended “branch-focused” reading model for nested view ([read more](https://meta.discourse.org/t/-/398759/103?silent=true)). - @supermathie merged a fix for a Discourse MCP permission issue and advised rebuild timing once it reaches tests-passed ([read more](https://meta.discourse.org/t/-/398792/9?silent=true)); also solved a self-hosting filesystem question by recommending symlinking GeoIP files rather than mounting the whole directory ([read more](https://meta.discourse.org/t/-/401148/3?silent=true)), and reminded admins that logs are the right starting point for diagnosing AI endpoint 500s ([read more](https://meta.discourse.org/t/-/401118/3?silent=true)). - @jordan.vidrine suggested simplifying overly long “permanent delete” confirmation button copy to improve clarity (and avoid truncation) ([read more](https://meta.discourse.org/t/-/401116/4?silent=true)). - @pmusaraj discussed AI translation retry/cost tradeoffs and set expectations about conservative retry behavior ([read more](https://meta.discourse.org/t/-/400612/17?silent=true)), and walked through the exact combination of login settings to disable local logins while keeping external auth and a branded splash screen ([read more](https://meta.discourse.org/t/-/401005/7?silent=true)). - @manuel clarified how the new “Home” sidebar link interacts with personal homepage preferences—helping avoid surprises while encouraging discovery of the new homepage layout ([read more](https://meta.discourse.org/t/-/401100/20?silent=true)). * * * With Blocks landing on the homepage and pins going bulk-mode, Meta spent the day getting both more _modular_ and more _manageable_—like tidying your forum with a power drill and a label maker. [Previous page](https://meta.discourse.org/t/daily-summary-5am-utc/291851.md?page=28) [Next page](https://meta.discourse.org/t/daily-summary-5am-utc/291851.md?page=30)