# סיכום יומי (בשעה 13:00 UTC) **URL:** https://meta.discourse.org/t/daily-summary-1pm-utc/291852 **Category:** Forum summaries **Created:** [16 בינואר,‏ 2024,‏ 10:00pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852 "2024-01-16T22:00:28Z") **Posts on this page:** 20 **Page:** 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: [3 באפריל,‏ 2026,‏ 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/788 "2026-04-03T13:02:05Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **82** new posts across **13** new topics. - **Top users (posts / likes):** | User | Posts | Likes | | --- | --- | --- | | @lindsey | 2 | 13 | | @Moin | 9 | 11 | | @NateDhaliwal | 12 | 10 | | @Bas | 2 | 6 | | @awesomerobot | 3 | 6 | | @zogstrip | 6 | 6 | | @nat | 4 | 6 | | @supermathie | 2 | 5 | | @Falco | 2 | 4 | | @Lilly | 1 | 4 | - **Biggest “news” posts:** a Meta-only experiment with **Boosts** ([read more](https://meta.discourse.org/t/-/399835/1?silent=true)) and an update to **Solved** notifications for watchers/trackers in support categories ([read more](https://meta.discourse.org/t/-/399821/1?silent=true)). - **Also seeing fresh replies in ongoing threads:** numeric-tag URL errors ([read more](https://meta.discourse.org/t/-/399784/2?silent=true)), localized emoji search aliases landing ([read more](https://meta.discourse.org/t/-/86641/25?silent=true)), Bitnami installs being _unsupported_ resurfacing ([read more](https://meta.discourse.org/t/-/142538/1?silent=true)), and “how do I filter topic lists?” tips ([read more](https://meta.discourse.org/t/-/375558/20?silent=true)). * * * ## Interesting Topics ### #Announcements - @lindsey introduced a live experiment: **“Boosts”** —a short, one-per-post micro-reaction that’s meant to sit between a standard reaction and a full reply ([read more](https://meta.discourse.org/t/-/399835/1?silent=true)). Early feedback covered visibility glitches, naming confusion, translation gaps, and UX nits like accidental flag clicks near the boost UI ([read more](https://meta.discourse.org/t/-/399835/11?silent=true)). - Discourse improved the **#solved** experience: if you’re **Tracking** or **Watching** a topic in a support category, you’ll now get a notification when it’s marked solved ([read more](https://meta.discourse.org/t/-/399821/1?silent=true)). The announcement also links back to guidance on setting up support categories ([read more](https://meta.discourse.org/t/-/398338/1?silent=true)) and the main Solved plugin doc ([read more](https://meta.discourse.org/t/-/30155/1?silent=true)). ### #Site feedback - **[ask.discourse.com](http://ask.discourse.com) went down** for some users, was confirmed by @NateDhaliwal, and @Bas reported back once it was fixed ([read more](https://meta.discourse.org/t/-/399862/4?silent=true)). - The long-running “content gardening hub” experiment got a practical boost: @Moin pointed out two near-duplicate feature requests about merging posts ([read more](https://meta.discourse.org/t/-/397606/70?silent=true)), linking to “merge replies with OP” ([read more](https://meta.discourse.org/t/-/240628/1?silent=true)) and “cannot merge first & second post” ([read more](https://meta.discourse.org/t/-/49444/1?silent=true)). @NateDhaliwal also shared a staff-focused topic-filter query to help find #bug/#contribute:ux topics that probably need a **#fixed** tag when a PR is already linked ([read more](https://meta.discourse.org/t/-/397606/71?silent=true)). ### #ux - Enforcing **#2fa** can strand logged-in users on the security screen, so the thread focused on how to _embed_ better guidance into the enforcement experience. @supermathie pointed to customizing site text strings ([read more](https://meta.discourse.org/t/-/399836/2?silent=true)), while @awesomerobot suggested a theme-component approach to insert richer HTML content above the wrapper outlet ([read more](https://meta.discourse.org/t/-/399836/3?silent=true)). - A **500 error** on an _old numeric-tag URL_ (bad for crawlers) was diagnosed with logs and a likely backend name/ID resolution mismatch; @nat confirmed the team has eyes on it and a fix is coming ([read more](https://meta.discourse.org/t/-/399784/11?silent=true)). - On [ask.discourse.com](http://ask.discourse.com), a UI nit: the **“Back to Forum”** link appears even on the homepage where it’s redundant; @NateDhaliwal proposed hiding it there ([read more](https://meta.discourse.org/t/-/399871/1?silent=true)). ### #bug - **Tag banners looked “empty”** because tags weren’t rendering; @awesomerobot traced it to upstream data changes, shipped a fix in the tag-banners plugin, and confirmed they were back on Meta ([read more](https://meta.discourse.org/t/-/399813/3?silent=true)). - A hosted AI translation mishap produced “AI commentary” / “thinking” text leaking into German output; @nat said the agent formatting was tightened, linked the deployed fix, and cleaned up affected titles/posts ([read more](https://meta.discourse.org/t/-/399805/4?silent=true)). - Cloudflare R2 backups: users reported multipart upload failures tied to **aws-sdk-s3 1.182.0** (`undefined method 'downcase' for nil`). @pfaffman shared a prior workaround thread ([read more](https://meta.discourse.org/t/-/399768/2?silent=true)) referencing the earlier aws-sdk bump discussion ([read more](https://meta.discourse.org/t/-/354217/49?silent=true)), and the OP confirmed pinning gems restored successful uploads ([read more](https://meta.discourse.org/t/-/399768/3?silent=true)). (Related: ongoing CDN/CORS troubleshooting patterns also showed up in the recent self-hosting CORS thread ([read more](https://meta.discourse.org/t/-/399466/17?silent=true)).) - iPad Safari briefly showed the composer **jumping to the top** and losing button functionality; after a few checks (including theme suspicion), the issue became non-reproducible—filed as “the joys of computing” for now ([read more](https://meta.discourse.org/t/-/399794/3?silent=true)). - The **Category Experts** plugin crashed during user merges; @zogstrip acknowledged the report and pointed to the PR that resolves it ([read more](https://meta.discourse.org/t/-/399785/3?silent=true)). ### #contribute:feature - A localization edge case: in combined **tag + category banners** , tag icons render for English tags but not for **translated tags** ; a feature request was opened to make translated tag banners consistent ([read more](https://meta.discourse.org/t/-/399840/1?silent=true))—building on recent momentum around translated tag/icon support ([read more](https://meta.discourse.org/t/-/399594/4?silent=true)). - AI feature request: **Mistral embeddings** integration hits an OpenAI-compat mismatch (`dimensions` vs `output_dimension`), where leaving out dimensions makes tests pass but blocks saving because the UI requires it ([read more](https://meta.discourse.org/t/-/399854/1?silent=true)). The report references earlier setup guidance for Mistral embeddings ([read more](https://meta.discourse.org/t/-/361095/1?silent=true)). ### #Dev - “Where are the design resources?”: for UI designers, the recommended path was enabling the built-in **styleguide** ; the topic was marked solved ([read more](https://meta.discourse.org/t/-/399847/2?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @lindsey kicked off two high-signal announcements: **testing Boosts** on Meta ([read more](https://meta.discourse.org/t/-/399835/1?silent=true)) and **Solved notifications for Tracking/Watching** users in support categories ([read more](https://meta.discourse.org/t/-/399821/1?silent=true)). - @Bas handled an incident response loop for [ask.discourse.com](http://ask.discourse.com)—acknowledged the outage ([read more](https://meta.discourse.org/t/-/399862/3?silent=true)) and then confirmed it was fixed ([read more](https://meta.discourse.org/t/-/399862/4?silent=true)). - @nat confirmed a fix is forthcoming for the numeric-tag URL 500 regression ([read more](https://meta.discourse.org/t/-/399784/11?silent=true)), posted an update on the AI-translation “thinking text” leak (including cleanup) ([read more](https://meta.discourse.org/t/-/399805/4?silent=true)), and continued the multilingual push by linking “Building for every language” as the next blog entry ([read more](https://meta.discourse.org/t/-/397784/8?silent=true)). - @zogstrip helped debug early Boosts rollout quirks (visibility/refresh) and clarified it’s _not_ intended to reorder/bump posts ([read more](https://meta.discourse.org/t/-/399835/8?silent=true)). They also pointed reporters toward a fix for a Category Experts merge crash ([read more](https://meta.discourse.org/t/-/399785/3?silent=true)) and flagged Bitnami as a likely factor in a polls-related stack trace report ([read more](https://meta.discourse.org/t/-/399856/2?silent=true))—with relevant context that Bitnami installs are unsupported ([read more](https://meta.discourse.org/t/-/142538/1?silent=true)) and the container image has been deprecated ([read more](https://meta.discourse.org/t/-/374875/1?silent=true)). - @awesomerobot shipped fast turnaround on a tag-banner regression: diagnosis + fix + confirmation on Meta ([read more](https://meta.discourse.org/t/-/399813/3?silent=true)), and provided a concrete theme-component recipe to inject richer guidance into the enforced 2FA screen ([read more](https://meta.discourse.org/t/-/399836/3?silent=true)). - @supermathie shared the simplest admin-friendly option for 2FA enforcement messaging—customizing the relevant site text string in `/admin/customize/site_texts` ([read more](https://meta.discourse.org/t/-/399836/2?silent=true))—and earlier helped surface the severity of the numeric-tag URL 500s with logs ([read more](https://meta.discourse.org/t/-/399784/2?silent=true)). - @Falco closed the loop on a long-running emoji request: **English + translated emoji aliases** are now implemented, along with a payload size reduction ([read more](https://meta.discourse.org/t/-/86641/25?silent=true)). They also chimed in on a self-hosting migration-collision oddity with a bit of gallows humor ([read more](https://meta.discourse.org/t/-/399572/10?silent=true)). - @davidb pointed to the upstream commit that should resolve **group dropdowns not refreshing** when new groups are created ([read more](https://meta.discourse.org/t/-/398285/3?silent=true)). * * * > “There are only two hard things in Computer Science: cache invalidation and naming things.” — resurfaced again while everyone tried out _Boosts_ ([read more](https://meta.discourse.org/t/-/399835/10?silent=true)). Until tomorrow: may your tags resolve to names (not IDs), your backups finish multipart uploads, and your rockets boost morale more than they boost confusion. ---
### 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 באפריל,‏ 2026,‏ 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/789 "2026-04-04T13:01:35Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 91** - **New topics (last 24h): 7** **Top users by activity (posts) and appreciation (likes) in the last 24 hours** | User | Posts | Likes | | --- | --- | --- | | @RGJ | 12 | 25 | | @R23D_Printing | 8 | 6 | | @Canapin | 7 | 27 | | @Moin | 6 | 12 | | @Ed_S | 6 | 12 | | @awesomerobot | 5 | 14 | | @putty | 4 | 11 | | @Lilly | 2 | 9 | | @Shauny | 1 | 8 | | @j.jaffeux | 1 | 6 | A big chunk of today’s conversation clustered around how “Boosts” fit into Discourse’s interaction model—especially around naming, moderation, and UI complexity ([read more](https://meta.discourse.org/t/-/399835/22?silent=true), [read more](https://meta.discourse.org/t/-/399835/29?silent=true)). * * * ## Interesting Topics ### #Announcements - @Lilly, @putty, @Shauny, @Canapin and others dug into what **Boosts** are _for_ (vs reactions/likes), whether they’re optional, and how moderation/flagging should work—plus a lively naming debate (“Boost” vs something less algorithmic-sounding) ([read more](https://meta.discourse.org/t/-/399835/19?silent=true), [read more](https://meta.discourse.org/t/-/399835/22?silent=true), [read more](https://meta.discourse.org/t/-/399835/21?silent=true), [read more](https://meta.discourse.org/t/-/399835/45?silent=true)). - The new embedding approach prompted feedback about UX tradeoffs: infinite-scroll discoverability, iframe drawbacks, and “how do I add a top-level comment without scrolling to the end?” ([read more](https://meta.discourse.org/t/-/399743/12?silent=true), [read more](https://meta.discourse.org/t/-/399743/14?silent=true), [read more](https://meta.discourse.org/t/-/399743/11?silent=true)). ### #General - A member asked where to find Discourse communities about **public transit / urban design** , with pointers to [discover.discourse.org](http://discover.discourse.org) plus a couple of real-world examples shared by @awesomerobot and @RGJ ([read more](https://meta.discourse.org/t/-/399902/1?silent=true), [read more](https://meta.discourse.org/t/-/399902/2?silent=true), [read more](https://meta.discourse.org/t/-/399902/3?silent=true)). ### #Integrations - A new official how-to covered **auto-provisioning accounts** when external auth ([DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) / OIDC / OAuth2 / SAML, etc.) is enabled—aimed at skipping the extra signup confirmation step via site settings ([read more](https://meta.discourse.org/t/-/399917/1?silent=true)). ### #ux (#ask-discourse) - On Ask Discourse specifically, the “Back to Forum” link was called out as confusing on the homepage; @awesomerobot noted [ask.discourse.com](http://ask.discourse.com) is a special customization case and would be adjusted ([read more](https://meta.discourse.org/t/-/399871/2?silent=true)). ### #Support (#notifications #push-notifications #ios) - Self-hosters revisited iOS “Add to Home Screen” **push notifications** : @Falco confirmed it should work on iOS 16.4+, then the thread dug into why certain admin flows (e.g. impersonation) can break it and why Discourse currently wipes keys on logout ([read more](https://meta.discourse.org/t/-/394149/11?silent=true), [read more](https://meta.discourse.org/t/-/394149/13?silent=true), [read more](https://meta.discourse.org/t/-/394149/15?silent=true), [read more](https://meta.discourse.org/t/-/394149/16?silent=true)). - A moderation workflow surprise: a hidden post can **reappear after the author edits it** , which prompted discussion about “intended behavior” vs “needs approval before reinstating,” and when “request revision” is the safer tool ([read more](https://meta.discourse.org/t/-/399901/1?silent=true), [read more](https://meta.discourse.org/t/-/399901/2?silent=true), [read more](https://meta.discourse.org/t/-/399901/4?silent=true)). - A user asked how to stop the **composer panel** from appearing when editing; the conversation quickly narrowed to toggling between rich-text and Markdown modes ([read more](https://meta.discourse.org/t/-/399937/1?silent=true), [read more](https://meta.discourse.org/t/-/399937/2?silent=true)). ### #customization:plugin - A prototype “workspaces” plugin proposed turning top-level categories into **Slack/Mattermost-like team spaces** , pairing channels with chat channels, and adding join/leave + guest access flows; @mcwumbly asked about real-world usage and rollout plans ([read more](https://meta.discourse.org/t/-/399936/1?silent=true), [read more](https://meta.discourse.org/t/-/399936/2?silent=true), [read more](https://meta.discourse.org/t/-/399936/3?silent=true)). - The “Discourse Daily Challenges” plugin thread had a practical hiccup: GitHub access started returning 404 for some users, leading to a **move to GitLab** and updated links (and a side-note about GitHub account flags) ([read more](https://meta.discourse.org/t/-/398980/57?silent=true), [read more](https://meta.discourse.org/t/-/398980/65?silent=true), [read more](https://meta.discourse.org/t/-/398980/69?silent=true)). - The long-running Pushover plugin got a fresh burst of life: @featheredtoast posted that it’s been **updated/modernized** for current Discourse versions ([read more](https://meta.discourse.org/t/-/119258/28?silent=true)). ### #bug (#ai #content-localization) - A new report flagged that when using **Mistral for translations** , translated posts lose embedded images (text-only rendering), whereas OpenAI translations didn’t—complete with repro steps and an external example link ([read more](https://meta.discourse.org/t/-/399939/1?silent=true)). ### #bug (#calendar-and-event) - A Safari PWA issue report: `/upcoming-events` appears to trigger **user-facing rate limiting** in production, backed by a screen recording and version details ([read more](https://meta.discourse.org/t/-/399931/1?silent=true)). ### #bug - Cloudflare R2 backups: someone confirmed a workaround for **multipart upload failures** (aws-sdk-s3 1.182.0 / `downcase` nil) and noted the fix required placing the change in its own `hooks:` block ([read more](https://meta.discourse.org/t/-/399768/4?silent=true)). ### #contribute:feature - A thread on “logged out” popups continued with a security/auditability angle: clarifying that admins can force-log-out users, and debating whether the UI should indicate _who_ initiated the logout without exposing sensitive info like IPs ([read more](https://meta.discourse.org/t/-/389991/2?silent=true), [read more](https://meta.discourse.org/t/-/389991/3?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot spent time clarifying the intent and safety boundaries of **Boosts** —including that the feature will be optional, how it compares to Basecamp’s version, and current moderation coverage (watched words yes; AI scan not yet) ([read more](https://meta.discourse.org/t/-/399835/22?silent=true), [read more](https://meta.discourse.org/t/-/399835/29?silent=true), [read more](https://meta.discourse.org/t/-/399835/44?silent=true)). They also pointed someone to [discover.discourse.org](http://discover.discourse.org) when asked about transit/urbanism communities ([read more](https://meta.discourse.org/t/-/399902/2?silent=true)), and noted Ask Discourse’s homepage needs a small customization tweak for the “Back to Forum” link ([read more](https://meta.discourse.org/t/-/399871/2?silent=true)). - @j.jaffeux outlined the longer-term interaction hierarchy thinking—where boosts sit today and how Discourse might eventually **unify boosts/reactions/likes** so communities can pick what fits their culture/scale ([read more](https://meta.discourse.org/t/-/399835/19?silent=true)). - @Falco confirmed that iOS home-screen installs on **iOS 16.4+ should receive push notifications** , and then pinpointed a specific code path that causes fragile behavior when admins impersonate users ([read more](https://meta.discourse.org/t/-/394149/11?silent=true), [read more](https://meta.discourse.org/t/-/394149/13?silent=true)). - @featheredtoast explained the security rationale behind wiping push keys on logout (preventing sensitive previews from going to logged-out devices), and floated a more nuanced approach (session-bound subscriptions) as a future improvement ([read more](https://meta.discourse.org/t/-/394149/15?silent=true)). They also revived the Pushover plugin by modernizing it for current Discourse versions ([read more](https://meta.discourse.org/t/-/119258/28?silent=true)). - @mcwumbly jumped into the new “workspace groups” prototype to validate the direction and ask the most important question: “is this in the wild yet?”—helping frame it as an RFC before production migration ([read more](https://meta.discourse.org/t/-/399936/2?silent=true)). Yesterday’s vibe in one sentence: if your notifications didn’t _push_, at least your comments could still get a morale **Boost** —just maybe not three new buttons’ worth of it ([read more](https://meta.discourse.org/t/-/394149/15?silent=true), [read more](https://meta.discourse.org/t/-/399835/45?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: [5 באפריל,‏ 2026,‏ 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/790 "2026-04-05T13:02:02Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **69** new posts across **13** new topics (plus ongoing discussions), including threads like _minimalist feature setups_ ([read more](https://meta.discourse.org/t/-/399941/1?silent=true)), _translation/language requests_ ([read more](https://meta.discourse.org/t/-/399957/1?silent=true)), and _category security regressions_ ([read more](https://meta.discourse.org/t/-/399976/1?silent=true)). - **Top users (posts / likes in the last 24h):** * * * ## Interesting Topics ### #General - **How minimal is your forum?** — @Ed_S compared a deliberately “small surface area” Discourse setup (few categories, no chat/reactions/LLMs) and asked how others resist feature creep, prompting replies that ranged from _super minimal_ to _purposefully extended_ stacks ([read more](https://meta.discourse.org/t/-/399941/1?silent=true)). The thread also spun out practical plugin/component references 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), [Locations Plugin](https://meta.discourse.org/t/-/69742/1?silent=true), [Topic Gallery](https://meta.discourse.org/t/-/394953/1?silent=true), [Search Thumbnails](https://meta.discourse.org/t/-/395082/1?silent=true), [Emoji Fluff](https://meta.discourse.org/t/-/339163/1?silent=true), and [MD Topic List Mobile component](https://meta.discourse.org/t/-/146341/1?silent=true). - **A Zenless Zone Zero “Inter-Knot” inspired UI theme** — @Monikas showed off a striking custom theme concept, with @Lilly suggesting it be reposted to the proper theme category once a repo is ready ([read more](https://meta.discourse.org/t/-/399961/1?silent=true)). ### #Community\_Building - **How to grow a Discourse forum without a product/service behind it?** — @haydenjames described the classic “founder-as-primary-engine” problem (4 years in, still driving a large share of activity) and asked what actually moves the needle for pure-interest communities; responses stressed consistency, SEO, and accepting the 99-9-1 dynamic ([read more](https://meta.discourse.org/t/-/399943/1?silent=true)). ### #ux - **Composer wording confusion: “Discard your post?” when you only meant cancel editing** — @RGJ highlighted a long-running papercut where the UI asks “Do you want to discard your post?” even when you’re merely exiting edit mode (and sometimes even with zero changes), proposing clearer “Cancel edit” / “Discard edits” language ([read more](https://meta.discourse.org/t/-/399942/1?silent=true)). ### #contribute:feature - **Auto-detect or reject VP9-in-MP4 uploads (iOS Safari playback failure)** — @shortmort37 reported “silent” iOS failures when users upload MP4 files that are actually VP9, and suggested rejecting, warning, or transcoding. @Falco pointed to [Discourse Video Stream](https://meta.discourse.org/t/-/388754/1?silent=true) and discussed the tricky security/performance trade-offs of safe local transcoding, possibly as an opt-in plugin ([read more](https://meta.discourse.org/t/-/399955/1?silent=true)). ### #bug - **Images missing in translated posts when using Mistral (#ai #content-localization)** — a translation regression was narrowed down to model behavior: `upload://` image links were not consistently preserved by _Mistral Small_, while switching to _Mistral Large_ resolved the issue, reinforcing that prompt-following fidelity can vary significantly by model tier ([read more](https://meta.discourse.org/t/-/399939/5?silent=true)). - **Category security permissions reset when re-parenting categories (with simplified category creation enabled)** — @Moin provided a detailed repro where changing parent/subcategory relationships wipes carefully set security rules and re-enables `everyone` posting. The report explicitly ties to the setting/topic “Enable simplified category creation” ([read more](https://meta.discourse.org/t/-/399976/1?silent=true)) and references [Enable simplified category creation](https://meta.discourse.org/t/-/394971/1?silent=true) as a key toggle. ### #Site\_feedback - **Please add Ukrainian or Russian languages to Meta’s language switcher (#content-localization)** — @Denis_Kovalenko asked for Ukrainian/Russian on [meta.discourse.org](http://meta.discourse.org) itself; @Falco confirmed it’s planned for early next week and expects the current translation model to handle it ([read more](https://meta.discourse.org/t/-/399957/8?silent=true)). - **Meta category posting restrictions may have been unintentionally loosened** — in the collaborative “content gardening hub” experiment thread, @Moin noticed category descriptions and/or configs no longer match expected “only group members can post” rules for plugins/themes/announcements. @mcwumbly connected it to the same class of “re-parenting resets permissions” issues and linked it directly to the new repro report ([read more](https://meta.discourse.org/t/-/397606/74?silent=true)). ### #Announcements - **Testing Boosts on Meta: reactions/likes/boosts convergence and UI clutter** — the “Boosts” experiment continued with users arguing that boosts and reactions feel redundant _today_, while pointing to longer-term plans to unify these feedback affordances; several UI decluttering concepts were shared ([read more](https://meta.discourse.org/t/-/399835/56?silent=true)). ### #customization:plugin - **ProxyTracer: VPN & Proxy Blocker plugin release** — @ProxyTracer announced a new plugin integrating the ProxyTracer API to detect/block VPN/proxy traffic with caching and fail-open options, plus configuration details and CIDR whitelisting ([read more](https://meta.discourse.org/t/-/399958/1?silent=true)). The thread also touched [Safe Mode](https://meta.discourse.org/t/53504?silent=true) concerns, with pointers to settings and recovery flows like [log back in as admin after lockout](https://meta.discourse.org/t/-/89605/1?silent=true), and general plugin installation docs ([read more](https://meta.discourse.org/t/-/19157/1?silent=true)). ### #Support - **How to tune TL3 thresholds (and find what’s blocking promotions)** — @Ed_S asked how to choose _which_ trust-level requirements to adjust to reach a desired TL3 population; @Moin marked a solution: inspect per-user TL3 requirements and use [Data Explorer](https://meta.discourse.org/t/32566?silent=true) queries like “find users likely to become TL3” ([read more](https://meta.discourse.org/t/-/399973/2?silent=true)) via [this query thread](https://meta.discourse.org/t/-/91495/1?silent=true). - **Cloudflare + reverse proxy setup causing all traffic to appear as Cloudflare IPs (#unsupported-install #cloudflare)** — a Chinese-language support thread dug into a multi-proxy setup (`User → Cloudflare → 1Panel Nginx → Discourse`) and why adding the Cloudflare template may not be sufficient when an intermediate proxy rewrites headers. The canonical reference remains the Cloudflare best practices guide ([read more](https://meta.discourse.org/t/-/399954/2?silent=true)) and its template instructions ([read more](https://meta.discourse.org/t/-/293405/1?silent=true)). - **Structured data: “Missing field ‘text’ (mainEntity.suggestedAnswer)” after updates** — @Richie reported Google Search Console still failing schema validation even after updating to a build that was expected to resolve “AcceptedAnswer” issues, referencing the earlier bug topic ([read more](https://meta.discourse.org/t/-/399974/1?silent=true)) and prior context ([read more](https://meta.discourse.org/t/-/399525/1?silent=true)). - **Does “AI triage automation” scan DMs between regular users?** — @Denis_Kovalenko questioned whether “Include personal messages” truly covers user-to-user DMs, citing real moderation-risk scenarios and asking if this is a limitation or intentional behavior ([read more](https://meta.discourse.org/t/-/399952/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@Falco** confirmed Meta will add Ukrainian/Russian to the language switcher soon, responding positively to the localization request in #Site\_feedback ([read more](https://meta.discourse.org/t/-/399957/8?silent=true)). - **@Falco** weighed in on safe handling of incompatible VP9 uploads in #contribute:feature, pointing admins at [Discourse Video Stream](https://meta.discourse.org/t/-/388754/1?silent=true) while noting that _local_ transcoding has security/CPU abuse risks and may be best offered as an opt-in plugin ([read more](https://meta.discourse.org/t/-/399955/4?silent=true)). - **@mcwumbly** acknowledged and triaged a regression where category security settings reset during re-parenting, thanking @Moin for the detailed steps and confirming it will be investigated ([read more](https://meta.discourse.org/t/-/399976/2?silent=true)). - **@mcwumbly** connected broader Meta configuration drift (lost posting restrictions in certain categories) to the same class of category re-parenting issues, linking back to the new bug report and committing to fix the underlying problem ([read more](https://meta.discourse.org/t/-/397606/74?silent=true)). _May your edits be clearly “canceled” (not “discarded”), your boosts stay uncluttered, and your translations keep every last `upload://` image link intact._ ---
### 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: [6 באפריל,‏ 2026,‏ 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/791 "2026-04-06T13:02:10Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 48** - **New topics (last 24h): 7** — including: - Ko-fi donations plugin: [read more](https://meta.discourse.org/t/-/399978/1?silent=true) - Strange bottom-left overlay / sidebar fade artifact: [read more](https://meta.discourse.org/t/-/399977/1?silent=true) - “Mini-mod” permissions plugin: [read more](https://meta.discourse.org/t/-/400019/1?silent=true) - [Data Explorer](https://meta.discourse.org/t/32566?silent=true) output double-escaping HTML: [read more](https://meta.discourse.org/t/-/400018/1?silent=true) - [Data Explorer](https://meta.discourse.org/t/32566?silent=true) query rejected due to semicolons inside strings: [read more](https://meta.discourse.org/t/-/400015/1?silent=true) - Event cancellation notifications (Calendar/Event): [read more](https://meta.discourse.org/t/-/399981/1?silent=true) - iPad/DiscourseHub scroll issue while replying: [read more](https://meta.discourse.org/t/-/400006/1?silent=true) **Top contributors (posts / likes in the last 24h):** | User | Posts | Likes | Recent reference | | --- | --- | --- | --- | | @Canapin | 6 | 8 | Boost visibility thoughts: [read more](https://meta.discourse.org/t/-/399835/58?silent=true) | | @RGJ | 5 | 8 | [Data Explorer](https://meta.discourse.org/t/32566?silent=true) escaping bug: [read more](https://meta.discourse.org/t/-/400018/1?silent=true) | | @elmuerte | 3 | 5 | Ko-fi plugin announcement: [read more](https://meta.discourse.org/t/-/399978/1?silent=true) | | @manuel | 2 | 3 | Lucide/alt icon set notes: [read more](https://meta.discourse.org/t/-/206693/24?silent=true) | | @bryce | 1 | 3 | Sidebar fade gradient CSS fix: [read more](https://meta.discourse.org/t/-/399977/5?silent=true) | | @sam | 1 | 2 | Suggested edits follow-up: [read more](https://meta.discourse.org/t/-/398691/4?silent=true) | | @gilles | 2 | 2 | Event cancellation question: [read more](https://meta.discourse.org/t/-/399981/1?silent=true) | | @ars18 | 2 | 2 | MiniMod plugin intro: [read more](https://meta.discourse.org/t/-/400019/1?silent=true) | | @Ed_S | 2 | 1 | “Box of gadgets” explanation attempt: [read more](https://meta.discourse.org/t/-/399977/2?silent=true) | | @mcwumbly | 1 | 1 | TL3 caps update + rollout notes: [read more](https://meta.discourse.org/t/-/399973/3?silent=true) | * * * ## Interesting Topics ### #customization:plugin - @elmuerte published a new **Ko-fi integration plugin** that can reward donations with badges and group memberships via webhooks, plus notes about currency handling and anonymization hooks ([read more](https://meta.discourse.org/t/-/399978/1?silent=true); install guide reference: [read more](https://meta.discourse.org/t/-/19157/1?silent=true)). - @ars18 introduced **Discourse MiniMod** , a plugin for “organizer-like” powers (managing categories/tags/topics) without granting full moderator access, building on category group moderation ([read more](https://meta.discourse.org/t/-/400019/1?silent=true)). - The **ProxyTracer VPN/Proxy blocker** thread continued with operational guidance: [safe mode](https://meta.discourse.org/t/53504?silent=true) isn’t helpful for diagnosing it, so the author added steps for disabling via Rails console and clarified how [safe mode](https://meta.discourse.org/t/53504?silent=true) access changes when “Enabled for All Visitors” is on ([read more](https://meta.discourse.org/t/-/399958/7?silent=true)). - In **Discourse Suggested Edits** (#experimental), @sam confirmed a requested piece isn’t implemented yet and will be added, while others asked for category-selection ergonomics (top-level vs subcategories) ([read more](https://meta.discourse.org/t/-/398691/4?silent=true)). ### #bug - Two **[Data Explorer](https://meta.discourse.org/t/32566?silent=true)** (#data-explorer) papercuts landed back-to-back: one report shows the UI refusing queries that contain semicolons even when they’re inside quoted strings ([read more](https://meta.discourse.org/t/-/400015/1?silent=true)), and a second report shows **double HTML escaping** in output (“Fish & Chips” instead of “Fish & Chips”) indicating a display-layer issue rather than SQL ([read more](https://meta.discourse.org/t/-/400018/1?silent=true)). - A structured data issue was flagged as **Missing field `text` in `mainEntity.suggestedAnswer`** , and @davidb replied that the team is investigating and will update soon ([read more](https://meta.discourse.org/t/-/399974/2?silent=true)). - Mobile/editor UX remains under scrutiny: one topic was moved into bugs because users reported being **unable to exit editing a post** (at least on the mobile web) ([read more](https://meta.discourse.org/t/-/398604/8?silent=true)). - Tablet workflow trouble: an iPad user reported they **can’t scroll the topic while the reply composer is open** in DiscourseHub, making quoting mid-reply awkward ([read more](https://meta.discourse.org/t/-/400006/1?silent=true)). ### #ux - A user reported a puzzling **bottom-left overlay** with “dots and lines”; after some misdirection about sidebar gadgets, @bryce explained it’s likely a sidebar footer fade gradient artifact and provided a CSS variable override to disable the fade ([read more](https://meta.discourse.org/t/-/399977/5?silent=true); related: Sidebar Theme Toggle discussion [read more](https://meta.discourse.org/t/-/242802/1?silent=true)). - The **Testing Boosts on Meta** conversation kept digging into what boosts are _for_: @Canapin argued likes/reactions help the community discover valuable posts, while boosts may be more author-centric, proposing different default visibility for authors vs everyone else ([read more](https://meta.discourse.org/t/-/399835/58?silent=true)). - “Clearing advice doesn’t actually clear it” gained traction when a contributor opened a PR to let admins ignore select problem checks properly, plus a dashboard tab to review/undo ignores ([read more](https://meta.discourse.org/t/-/398754/4?silent=true)). ### #Support - An admin asked whether **AI triage automation** (#automation #ai) can scan _regular-user DMs_ when “Include personal messages” is enabled; @RGJ stated that it does (and asked how the reporter determined it wasn’t scanning) ([read more](https://meta.discourse.org/t/-/399952/2?silent=true)). - In a solved thread on **tuning TL3 thresholds** (#trust-levels), @mcwumbly shared that meta reduced TL3 caps (topics viewed cap and posts read cap), based on learnings from a “who is likely to become TL3” query, and noted work is underway to roll out site-setting defaults more methodically ([read more](https://meta.discourse.org/t/-/399973/3?silent=true); referenced query topic: [read more](https://meta.discourse.org/t/-/91495/27?silent=true)). - A French-language support question asked for a better way to **notify all “Going” participants when an event is cancelled** (#calendar-and-event), pointing out manual PM tagging doesn’t scale; discussion centered on possible UI improvements and what “Close event” actually changes in notification behavior ([read more](https://meta.discourse.org/t/-/399981/1?silent=true); docs context: [read more](https://meta.discourse.org/t/-/97376/1?silent=true) and [read more](https://meta.discourse.org/t/-/149964/1?silent=true)). ### #Developer-Guides / #customization:theme / #Dev - In **Alternative icons** (#reference #theme-guides), @manuel pointed to Discourse’s lucide-based icon set repo and discussed brand icon mappings, prompting @Canapin to suggest the official set should be highlighted more clearly in the original guide ([read more](https://meta.discourse.org/t/-/206693/24?silent=true)). - The **Horizon Theme** (#official #horizon-theme) thread got an update from @chapoi: no new compatibility work is currently planned, and they highlighted a likely conflict around the welcome banner outlet—suggesting configuration changes that _might_ make it work ([read more](https://meta.discourse.org/t/-/360486/79?silent=true)). - In “Claude & Discourse-related development,” new reflections landed on whether AI-generated work changes the migration/build landscape, with some skepticism about overly AI-polished writeups and a preference for more human-looking experience reports ([read more](https://meta.discourse.org/t/-/394773/14?silent=true)). - The “Using dv (Discourse Vibe) to configure Discourse AI in development” topic saw follow-up questions about running multiple dev instances and mirroring a live site in dev behind a reverse proxy ([read more](https://meta.discourse.org/t/-/388622/3?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @manuel helped clarify the “official” direction for icon packs by pointing to Discourse’s lucide icon set and asking what improvements might still be needed ([read more](https://meta.discourse.org/t/-/206693/24?silent=true)). - @bryce diagnosed the reported bottom-left “artifact overlay” as a sidebar fade/gradient effect and provided a practical CSS override via `--d-sidebar-footer-fade` ([read more](https://meta.discourse.org/t/-/399977/5?silent=true)). - @sam responded in the Suggested Edits plugin thread, confirming a missing piece “isn’t implemented yet” and will be added ([read more](https://meta.discourse.org/t/-/398691/4?silent=true)). - @mcwumbly shared internal context about TL3 “cap” reductions on meta and described ongoing work to roll out future default site-setting changes in a more transparent, controllable way for admins ([read more](https://meta.discourse.org/t/-/399973/3?silent=true)). - @davidb acknowledged the structured data report about `mainEntity.suggestedAnswer` missing `text`, stating the team is investigating and will follow up ([read more](https://meta.discourse.org/t/-/399974/2?silent=true)). - @chapoi provided a status update on Horizon Theme compatibility priorities, noting roadmap decisions depend on demand and outlining a likely welcome-banner outlet conflict ([read more](https://meta.discourse.org/t/-/360486/79?silent=true)). * * * _That’s a wrap—may your sidebar gradients stay smooth, your boosts stay meaningful, and your [Data Explorer](https://meta.discourse.org/t/32566?silent=true) finally serve “Fish & Chips” without the extra `&`._ ---
### 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: [7 באפריל,‏ 2026,‏ 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/792 "2026-04-07T13:01:49Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 119** - **New topics (last 24h): 15** ### Top contributors (posts + likes in the last 24h) | User | Posts | Likes | | --- | --- | --- | | @sam | 8 | 21 | | @manuel | 3 | 14 | | @Falco | 5 | 9 | | @chapoi | 4 | 9 | | @Canapin | 6 | 8 | | @RGJ | 5 | 7 | | @R23D_Printing | 4 | 6 | | @Jonathan5 | 7 | 6 | | @david | 2 | 5 | | @awesomerobot | 3 | 5 | _Traffic drivers today included a UI win for #bookmarks in_ [Easier access to bookmarks](https://meta.discourse.org/t/-/400085/1?silent=true) _and a substantial update on the Meta theme rebuild in_ [Rebuilding the Meta Branded theme](https://meta.discourse.org/t/-/400013/1?silent=true)_._ * * * ## Interesting Topics ### #Announcements - @sam shipped a small-but-mighty UX improvement: topic-level bookmark controls now surface **all post bookmarks** from the bottom-of-topic action, making it far easier to find what you saved in long threads—see [Easier access to bookmarks](https://meta.discourse.org/t/-/400085/1?silent=true). ### #Site feedback - The Meta Branded theme rebuild continues, with a deep dive into **Lucide icons** , color scheme restrictions, and early direction for the **Blocks API** —plus some early buglets like a non-clickable logo caused by overlaying UI—details in [Rebuilding the Meta Branded theme: New icons, a custom homepage, and a first look at the Blocks API](https://meta.discourse.org/t/-/400013/1?silent=true). ### #customization:theme component - A new theme component proposal introduces hover tooltips for **internal topic links** (topic preview “cards” on hover), with early feedback requesting screenshots and preview clarity in [Topic Hover Cards](https://meta.discourse.org/t/-/400025/1?silent=true). ### #contribute:feature - Feedback rolled in on the new **Boosts** concept: concerns about “visual flooding” on mobile at higher boost counts, plus suggestions like collapsible display and quoting UX, in [Some ideas about discourse-boost plugin](https://meta.discourse.org/t/-/400087/1?silent=true). ### #Support - A watched-words moderation oddity: posts are being flagged, but reviewers can’t see _which_ watched word triggered it—possibly related to replying-by-email formatting—tracked in [Posts being flagged due to watched word, however no watched word is flagged](https://meta.discourse.org/t/-/400097/1?silent=true). - A CSS/layout troubleshooting thread: a navigation bar wraps awkwardly, and @chapoi suggested `white-space: nowrap;` (and possibly overflow handling) in [How can I fix this spacing issue?](https://meta.discourse.org/t/-/400106/1?silent=true). - Users disabling translations report that the setting “comes back” after a while; today’s key detail is that it currently persists **in local storage for 30 days** , and a change is in flight to persist per-user across devices—see [User disables translations, but they keep coming back](https://meta.discourse.org/t/-/400096/1?silent=true). ### #bug - RSS consumers found that `exclude_tag` works on `/latest.rss` but not on _category_ feeds, with a confirmed workaround and a core fix queued—full repro steps in [Exclude\_tag does not work in category RSS feeds](https://meta.discourse.org/t/-/400034/1?silent=true). - Upload/markdown edge case: attachments named with leading/trailing underscores (e.g. `_test_file_.txt`) generate markup that fails to escape underscores correctly, documented in [Incorrect attachment markup generation with underscores in the file name](https://meta.discourse.org/t/-/400079/1?silent=true). - A localisation regression report: anonymous users visiting with `?tl=[lang]` see inconsistent language across topic lists and inside topics, despite the UI showing the selected locale—recorded with a screencast in [Localisation bug for anonymous users with ?tl=[lang]](https://meta.discourse.org/t/-/400090/1?silent=true). ### #customization:plugin - A fresh authentication plugin drop: **Telegram login** for current Discourse versions, including repo link, configuration notes, and a demo forum in [Telegram Auth Plugin (work with latest discourse version)](https://meta.discourse.org/t/-/400072/1?silent=true). - A long-running plugin thread hit a breaking change: **Topic Ratings** UI vanished due to widget leftovers after a modernization effort; the thread includes analysis and a proposed fix path in [Topic Ratings Plugin](https://meta.discourse.org/t/-/39578/440?silent=true). ### #Self-hosting - A (very) large VPS sizing question sparked discussion about whether huge NVMe allocations are necessary, and whether the question is Discourse-related; the context includes running Discourse plus other services—see [请问有使用netcup root server的么？](https://meta.discourse.org/t/-/400031/1?silent=true). ### #Nested Replies Testing - Nested replies UX exploration continued: a user discovered “Pin” behavior differs between nested vs flat mode, and the answer is that pinning is currently **nested-mode-only** —see [发现了在Topic中 Pin 的功能，这是只有在嵌套模式下才可以使用么](https://meta.discourse.org/t/-/400076/1?silent=true). ### #development - Plugin/theme author fatigue surfaced in the ongoing template deprecation conversation: a plugin maintainer asked how to responsibly sunset plugins without breaking downstream users, and @david outlined safer paths (marking broken/unmaintained, archiving, enabling forks)—see [Deprecating .hbs file extension in themes and plugins](https://meta.discourse.org/t/-/398896/13?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @sam shipped a bookmarks UX improvement and then immediately dug into mobile edge cases around indicating “post bookmarked vs topic bookmarked” in [Easier access to bookmarks](https://meta.discourse.org/t/-/400085/1?silent=true). - @sam confirmed and provided a practical workaround for tag-exclusion in RSS category feeds (and sketched a likely fix direction) in [Exclude\_tag does not work in category RSS feeds](https://meta.discourse.org/t/-/400034/2?silent=true). - @manuel posted a substantial “under-the-hood” write-up on the rebuilt Meta theme (including Lucide mapping decisions and icon tradeoffs) in [Rebuilding the Meta Branded theme: New icons, a custom homepage, and a first look at the Blocks API](https://meta.discourse.org/t/-/400013/1?silent=true), and also noted documentation follow-ups around icon set guidance in [Alternative icons](https://meta.discourse.org/t/-/206693/28?silent=true). - @chapoi requested better preview material for a new component announcement in [Topic Hover Cards](https://meta.discourse.org/t/-/400025/2?silent=true), and offered pragmatic CSS guidance for a layout issue in [How can I fix this spacing issue?](https://meta.discourse.org/t/-/400106/2?silent=true). - @Falco advised on AI model selection and constraints (including provider considerations) for translation/image-handling scenarios in [Images missing in translated posts when using Mistral as translation model](https://meta.discourse.org/t/-/399939/8?silent=true), and shared configuration notes plus broader recommendations in [Use Mistral for embeddings](https://meta.discourse.org/t/-/399854/3?silent=true). - @Falco also merged a long-requested i18n improvement: **localized emoji aliases** (e.g. typing localized equivalents mapping to canonical emojis) in [Add English and translated aliases for Emojis](https://meta.discourse.org/t/-/86641/26?silent=true), and clarified nested-only behavior for pinning in [发现了在Topic中 Pin 的功能，这是只有在嵌套模式下才可以使用么](https://meta.discourse.org/t/-/400076/3?silent=true). - @david explained the real-world developer-experience motivation behind extension deprecations (education/support/tooling consistency) in [Deprecating .js.es6 file extensions in themes and plugins](https://meta.discourse.org/t/-/398894/8?silent=true), and responded constructively to maintainer burnout concerns in [Deprecating .hbs file extension in themes and plugins](https://meta.discourse.org/t/-/398896/14?silent=true). - @awesomerobot proposed clearer UI wording for automation “topic type” semantics after confusion about whether DMs are included in “all topics” in [Does AI triage automation scan DMs between regular users?](https://meta.discourse.org/t/-/399952/6?silent=true), and helped diagnose a theme-component “not appearing” report in [Sidebar Theme Toggle](https://meta.discourse.org/t/-/242802/40?silent=true). - @pmusaraj linked a fix for a Google crawl failure triggered by legacy numeric-tag URLs in [500 error at old URL for numeric tag (Google crawl fail)](https://meta.discourse.org/t/-/399784/12?silent=true). - @mcwumbly kicked off a strategic discussion about what community-building conversations Meta should encourage—plus how category structure impacts that—in [Encouraging discussion about building and managing communities](https://meta.discourse.org/t/-/400029/1?silent=true). - @zogstrip asked for diagnostic detail on watched-words false/opaque triggers in [Posts being flagged due to watched word, however no watched word is flagged](https://meta.discourse.org/t/-/400097/2?silent=true), confirmed a fix is coming for Cakeday persistence edge cases in [Discourse Cakeday](https://meta.discourse.org/t/-/38447/234?silent=true), and linked the core fix for RSS tag exclusion in [Exclude\_tag does not work in category RSS feeds](https://meta.discourse.org/t/-/400034/5?silent=true). - @nat clarified current translation-preference persistence (30-day local storage) and linked an improvement to persist the preference as a user setting across devices in [User disables translations, but they keep coming back](https://meta.discourse.org/t/-/400096/2?silent=true). * * * Yesterday, Meta got easier to navigate (hello, bookmark shortcuts), learned to _smile_ in more languages (localized emoji aliases), and kept sharpening the theme toolkit—one Lucide stroke at a time. ---
### 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: [9 באפריל,‏ 2026,‏ 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/793 "2026-04-09T13:01:54Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **In the last 24 hours (2026-04-08 → 2026-04-09), Meta saw:** - **86 new posts** - **11 new topics** - Lots of hands-on troubleshooting and UX iteration, from private ticketing setups to mobile bookmark affordances (e.g. [read more](https://meta.discourse.org/t/-/400252/1?silent=true), [read more](https://meta.discourse.org/t/-/400160/1?silent=true)). ### Top users (posts + likes in the last 24h) | User | Posts | Likes | | --- | --- | --- | | @RGJ | 5 | 13 | | @itsbhanusharma | 2 | 11 | | @supermathie | 4 | 8 | | @Moin | 6 | 6 | | @awesomerobot | 4 | 6 | | @Canapin | 2 | 6 | | @chapoi | 1 | 6 | | @pacharanero | 2 | 5 | | @zogstrip | 2 | 4 | | @nathank | 7 | 4 | **Quick sampling of where the top voices showed up:** - @RGJ helped diagnose a “private tickets” visibility scare and pinpointed the key plugin setting involved in the [final solution](https://meta.discourse.org/t/-/400252/12?silent=true). - @itsbhanusharma pushed back on a very-low Marketplace budget and suggested a practical DIY route in [this hiring request](https://meta.discourse.org/t/-/400251/2?silent=true). - @supermathie asked clarifying questions about what “private topics” meant in practice, and later requested better postmortem details for future readers in [the same thread](https://meta.discourse.org/t/-/400252/11?silent=true). - @Moin flagged inconsistent plugin availability notes and also called out outdated plan naming in official plugin banners in a [site feedback report](https://meta.discourse.org/t/-/400250/2?silent=true). - @awesomerobot shared current API limitations around hiding posts (and a workable mitigation) in [Hide posts via API](https://meta.discourse.org/t/-/400135/2?silent=true). * * * ## Interesting Topics ### #Support - @tknospdr hit a scary “ticket visibility” surprise using the #private-topics workflow; the root cause ended up being a misunderstanding of “Private topics permitted groups”, and @RGJ explained exactly why **TL0 users could see everything** in the [accepted solution](https://meta.discourse.org/t/-/400252/12?silent=true) (also see the related plugin thread: [read more](https://meta.discourse.org/t/-/268646/1?silent=true)). - API users asked about hiding a post via the API without resolving flags; @awesomerobot confirmed the limitation and suggested tuning `hide_post_sensitivity` as a practical workaround in [Hide posts via API](https://meta.discourse.org/t/-/400135/2?silent=true). - A Cloudflare proxy setup caused all traffic to appear as Cloudflare IPs in admin views; the thread moved toward “restore real visitor IP” guidance (Apache example shared) in [this support topic](https://meta.discourse.org/t/-/399954/11?silent=true). - Email operations discussion: separating mail subdomains and moving from POP3 to the newer mail-receiver model came up in [Auto-restarting once a day via cron?](https://meta.discourse.org/t/-/400176/5?silent=true). * * * ### #contribute:feature - [Data Explorer](https://meta.discourse.org/t/32566?silent=true) maintainers discussed how to reduce “query breakage surprises” when columns get dropped/renamed; @ted proposed deprecation marking (and possibly SQL parsing) in [Coping with deprecated columns in Data Explorer](https://meta.discourse.org/t/-/400264/1?silent=true) (context link: [Data Explorer](https://meta.discourse.org/t/-/32566/1?silent=true)). - Subscriber automation: @hipp0 asked for automatic add/remove of users to groups when subscriptions start/end; @Moin pointed out the #subscriptions plugin already does this group lifecycle management in [Subscriber group automation](https://meta.discourse.org/t/-/400256/2?silent=true) (plugin reference: [read more](https://meta.discourse.org/t/-/140818/1?silent=true)). * * * ### #ux - Mobile bookmarks UI got a serious iteration: @chapoi proposed reusing the sidebar’s nested dropdown patterns to make bookmarked-post navigation clearer, and @sam prototyped it (including multi-level menu concerns) in [Unable to tell “post” bookmarks exist in footer on mobile](https://meta.discourse.org/t/-/400160/28?silent=true). - Topic split “small action posts”: a request suggested the _display text_ should survive topic renames more predictably (or rebuild like oneboxes do), explored in [Link in “Split this topic” mini post](https://meta.discourse.org/t/-/400249/1?silent=true). - Mobile titlebar layout: long category/tag lines can cut off tags without ellipsis and even introduce odd punctuation wrapping; examples and reproduction details are in [If topic info is too long, tags are cut off and create a blank line](https://meta.discourse.org/t/-/400298/1?silent=true) (examples referenced: [read more](https://meta.discourse.org/t/-/113192/1?silent=true), [read more](https://meta.discourse.org/t/-/370969/1?silent=true)). - Backups UI anxiety: admins sometimes see “no logs yet” even when the backup succeeds, raising concerns about failure-state observability in [Backup process page keeps saying “no logs yet”](https://meta.discourse.org/t/-/400287/1?silent=true). * * * ### #bug - Calendar integration fix (#calendar-and-event): Google Calendar was using the webcal URL as the “Calendar Name”; @Falco shipped a core fix using `X-WR-CALNAME` in [this bug report](https://meta.discourse.org/t/-/400167/6?silent=true). - Category permissions regression: changing parent/subcategory relationships could reset security settings; @awesomerobot noted a fix that preserves permissions unless parent restrictions require changes, in [Category security settings reset when changing parent/subcategory relationship](https://meta.discourse.org/t/-/399976/9?silent=true). - Theme component update behavior: `.discourse-compatibility` is honored on install, but not reliably re-checked on subsequent updates; @RGJ described a painful uninstall/reinstall workaround and requested rollback-aware updates in [Theme (component)s do not look at .discourse-compatibility on update](https://meta.discourse.org/t/-/400248/1?silent=true). * * * ### #customization:plugin - Geo-blocking enhancement: a contributor proposed an IP allowlist feature, and @RGJ welcomed it _with a performance constraint_ (avoid extra DB calls per request; use lazy-loaded cache) in [Geo Blocking plugin](https://meta.discourse.org/t/-/227824/39?silent=true). * * * ### #Site feedback - Official plugin topic banners appear to have outdated/inaccurate “available on all hosting tiers” notes after pricing/tier changes; examples were collected (including plan name drift like “Standard” vs “Pro”) in [Inaccurate plugin availability notes on meta](https://meta.discourse.org/t/-/400250/1?silent=true) with related plugin topics cited: [Math](https://meta.discourse.org/t/-/65770/1?silent=true), [Cakeday](https://meta.discourse.org/t/-/38447/1?silent=true), [Solved](https://meta.discourse.org/t/-/30155/1?silent=true), [Yearly Review](https://meta.discourse.org/t/-/105713/1?silent=true), plus an older banner example in [Advertising](https://meta.discourse.org/t/-/33734/1?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@chapoi** proposed a cleaner, more consistent mobile bookmark affordance (including icon states and nested menu behavior) in [Unable to tell “post” bookmarks exist in footer on mobile](https://meta.discourse.org/t/-/400160/28?silent=true). - **@awesomerobot** : - **@supermathie** : - **@zogstrip** : - **@sam** : - **@Falco** shipped a calendar subscription improvement via `X-WR-CALNAME` to fix Google Calendar naming behavior in [The webcal URL is incorrectly passed to the Calendar Name field in Google Calendar](https://meta.discourse.org/t/-/400167/6?silent=true). - **@david** investigated a self-hosting CORS/plugin break report and identified a highlightjs bundle edge case when S3 CDN variables are set (without `DISCOURSE_CDN_URL`), providing a core fix link in [All plugins not functioning due to CORS error after recent upgrade](https://meta.discourse.org/t/-/399466/21?silent=true). * * * Yesterday’s vibe: half the forum was polishing UX edges while the other half was doing “PRs on our brains” to fix configuration mix-ups—may your bookmarks be discoverable and your private topics stay private. ---
### 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: [10 באפריל,‏ 2026,‏ 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/794 "2026-04-10T13:01:51Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 82 - **New topics (last 24h):** 13 **Top contributors (posts / likes in the last 24h):** - @gilles — **11 posts** , **10 likes** - @mcwumbly — **4 posts** , **10 likes** - @hellekin — **2 posts** , **8 likes** - @Canapin — **4 posts** , **8 likes** - @ToddZ — **6 posts** , **7 likes** - @putty — **1 post** , **7 likes** - @Lilly — **1 post** , **6 likes** - @ducks — **1 post** , **5 likes** - @merefield — **2 posts** , **4 likes** - @Moin — **4 posts** , **3 likes** **A couple of “where the discussion energy went” quick links (busiest/most-referenced threads):** Boosts feedback continued in [read more](https://meta.discourse.org/t/-/399835/73?silent=true), Meta’s redesign/Blocks API discussion kept evolving in [read more](https://meta.discourse.org/t/-/400013/17?silent=true), and plugin/docs clarity came up again in [read more](https://meta.discourse.org/t/-/400250/7?silent=true). * * * ## Interesting Topics ### #Announcements - @mcwumbly and @jordan.vidrine jumped into the ongoing debate around _Boosts_—with concerns about “low-signal” reactions, moderation implications, and whether “fun” belongs in serious communities—while emphasizing feature autonomy and admin control [read more](https://meta.discourse.org/t/-/399835/73?silent=true) (plus moderation notes [read more](https://meta.discourse.org/t/-/399835/74?silent=true)). - Calendar subscription URLs got a strong +1, but also feedback on _discoverability_ (put the subscribe entry point closer to the calendar UI) and concerns about “corporate links/logos” for communities focused on digital sovereignty [read more](https://meta.discourse.org/t/-/398902/19?silent=true). _(Related: event creation flow was referenced as context [read more](https://meta.discourse.org/t/-/400169/1?silent=true))._ ### #Site feedback - Confusion around plugin availability/docs sparked a practical suggestion: link “availability” callouts directly to the canonical plugin comparison table (and handle anchors/scroll offsets). @derek confirmed scroll margin improvements landed [read more](https://meta.discourse.org/t/-/400250/13?silent=true). _(Related context: Staff Alias plugin availability edge cases were raised [read more](https://meta.discourse.org/t/-/156202/1?silent=true))._ - The Meta branded theme + redesign thread continued: @manuel clarified how the **Blocks API** differs from Plugin Outlets (frames vs insertion points, more predictable layouts, centralized conditional logic) [read more](https://meta.discourse.org/t/-/400013/17?silent=true), while others highlighted spacing/density concerns and shared CSS experiments [read more](https://meta.discourse.org/t/-/400013/18?silent=true). - Category organization tweaks revealed a UX oddity: muted categories may display without their descriptions, raising the question of whether it’s intentional or an oversight [read more](https://meta.discourse.org/t/-/396306/70?silent=true). ### #blog - A new technical deep-dive unpacked how upload-heavy backups led to **377GB** of unexpected disk usage and _ext4 hardlink_ headaches—earning appreciation for “less marketing, more engineering story time” [read more](https://meta.discourse.org/t/-/400360/1?silent=true). ### #customization:theme component - A brand-new theme component shipped: **Customizable Print to PDF Button** , aiming to provide a cleaner per-topic print/PDF experience (with installation and theme-learning docs linked right in the OP) [read more](https://meta.discourse.org/t/-/400340/1?silent=true). _(Related: stock printing discussion for comparison [read more](https://meta.discourse.org/t/-/160061/1?silent=true); install guide [read more](https://meta.discourse.org/t/-/63682/1?silent=true); beginner themes guide [read more](https://meta.discourse.org/t/-/91966/1?silent=true))._ - Versatile Banner hit a real-world snag: its default background image is hosted on Imgur, which is now inaccessible in the UK—suggesting a move to GitHub-hosted defaults to avoid “broken out-of-the-box” installs for some regions [read more](https://meta.discourse.org/t/-/109133/373?silent=true). - Quote Callouts saw a locale-specific runtime error (German translation), and a quick PR fixed it—plus follow-up questions about icon-only / titleless callouts [read more](https://meta.discourse.org/t/-/350962/56?silent=true). ### #ux - A long-standing papercut: on mobile, the **tag selector** can feel “stuck open” with no obvious close affordance; users described dismissal workarounds and asked for more intuitive exit patterns [read more](https://meta.discourse.org/t/-/400390/1?silent=true). - A broader “mobile-first reality check” opened: the 2026 mobile composer is powerful, but can read as visually overwhelming compared to older, simpler layouts—prompting a discussion about prioritization and interaction design for mobile composing/editing [read more](https://meta.discourse.org/t/-/400393/1?silent=true). _(Related historical reference was cited in-thread [read more](https://meta.discourse.org/t/-/53632/5?silent=true).)_ - Translating reading time text in Onebox/preview links surfaced a Crowdin → GitHub workflow detail: emoji/icon handling in locale files briefly broke and was corrected [read more](https://meta.discourse.org/t/-/400164/8?silent=true). ### #bug - Structured data/SEO debugging continued: validation improved, but a remaining schema complaint focused on missing fields (like `text` / `datePublished`) in `mainEntity.suggestedAnswer`, and the request was to keep the topic open while the last issues are chased down [read more](https://meta.discourse.org/t/-/399974/7?silent=true). - A French bug report dug into browser console accessibility/autofill warnings inside category advanced settings—still reproducible even in [safe mode](https://meta.discourse.org/t/53504?silent=true)—making it hard to tell what’s harmless vs what breaks real settings (like event sorting) [read more](https://meta.discourse.org/t/-/400288/11?silent=true). ### #Support - “System flagged old posts as spam?” described a worrying burst: multiple historic posts (even PMs) suddenly queued with inconsistent system messages (including a puzzling `Is this post or undefined?`) alongside a Pitchfork timeout log snippet [read more](https://meta.discourse.org/t/-/400369/1?silent=true). - Staged users + default category watching preferences: a self-host admin wanted imported staged users _not_ to watch Announcements until activation, and testing suggested subtle differences between group defaults vs the `Default categories watching` setting (and when defaults apply) [read more](https://meta.discourse.org/t/-/400361/2?silent=true). _(Related migration background: Google Groups import thread [read more](https://meta.discourse.org/t/-/79773/252?silent=true).)_ * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @mcwumbly helped reframe the “Boosts” concern as a question of community fit and personal/team autonomy, supporting experimentation even when it’s not everyone’s top priority [read more](https://meta.discourse.org/t/-/399835/73?silent=true). They also engaged on improving plugin availability notes, exploring ways to reduce duplicated “two sources of truth” documentation [read more](https://meta.discourse.org/t/-/400250/3?silent=true) and agreeing a direct link/anchor approach could help [read more](https://meta.discourse.org/t/-/400250/7?silent=true). - @jordan.vidrine emphasized that Boosts are optional, _moderate-able_, and that “fun” can be a valid product goal—plus noted admin tools to delete problematic boosts/users if needed [read more](https://meta.discourse.org/t/-/399835/74?silent=true). - @ducks published a companion discussion for a technical blog post explaining how a backup process met ext4 hardlink realities (and how _Friends_ became an accidental infrastructure stress test) [read more](https://meta.discourse.org/t/-/400360/1?silent=true). - @gerhard resolved a translation pipeline snag where emojis/icons didn’t survive the Crowdin → GitHub transition cleanly, confirming a fix and updated PRs [read more](https://meta.discourse.org/t/-/400164/8?silent=true). - @davidb acknowledged the remaining structured-data “suggestedAnswer” schema issues and committed to investigating further (with a promise of another update) [read more](https://meta.discourse.org/t/-/399974/9?silent=true). - @chapoi answered a support question in French: who can create chat channels (admins/staff), which then prompted discussion about event-driven channel creation workflows [read more](https://meta.discourse.org/t/-/400305/2?silent=true). - @manuel clarified the rationale and mechanics behind the **Blocks API** in the Meta redesign effort (frames, stability, and centralized conditional rendering) [read more](https://meta.discourse.org/t/-/400013/17?silent=true). - @derek confirmed a UX polish improvement landed: scroll margin was added so anchored links don’t hide headings under fixed headers [read more](https://meta.discourse.org/t/-/400250/13?silent=true). - @zogstrip looped in the right folks on the reading-time translation issue, helping get it in front of the localization maintainers quickly [read more](https://meta.discourse.org/t/-/400164/7?silent=true). * * * Yesterday’s lesson: **if Jennifer Aniston can accidentally eat 377GB, your backups deserve a snack plan too.** ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [11 באפריל,‏ 2026,‏ 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/795 "2026-04-11T13:01:52Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 86** - **New topics (last 24h): 13** **Top users (posts / likes in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @Lilly | 12 | 21 | | @Moin | 8 | 20 | | @RGJ | 4 | 10 | | @Canapin | 4 | 8 | | @awesomerobot | 3 | 8 | | @Falco | 3 | 7 | | @sam | 1 | 4 | | @Arkshine | 1 | 3 | | @jordan.vidrine | 2 | 3 | | @Lee_Ars | 2 | 3 | **Team pulse:** The most active folks from the [@team](https://meta.discourse.org/groups/team?silent=true) group were @awesomerobot, @Falco, @jordan.vidrine, @sam, @supermathie, and @featheredtoast, spread across mobile UX, support triage, and theme-component maintenance (details below). * * * ## Interesting Topics **#ux** - @Lilly kicked off a big reality-check on the _2026 mobile composer experience_, calling out intermittent iOS reliability issues (uploads, quoting, dropdowns, freezes) and asking what should be simplified or removed in defaults—prompting @awesomerobot to steer the discussion toward actionable “what should we remove?” changes like toolbar behavior, draft/close controls, and tag UI ([read more](https://meta.discourse.org/t/-/400393/2?silent=true)). Related: the “how do I close tag selector?” confusion ([read more](https://meta.discourse.org/t/-/400390/1?silent=true)), a likely-related freeze report when deleting composer content ([read more](https://meta.discourse.org/t/-/396436/1?silent=true)), and praise for the `/mobile` + `/desktop` path deprecation and improved auto-switching ([read more](https://meta.discourse.org/t/-/384280/1?silent=true)). - A localization snag was spotted where **“Solved”** wasn’t translating in a UI string; @Moin pinpointed the code location and @awesomerobot linked an in-flight fix via PR ([read more](https://meta.discourse.org/t/-/400436/2?silent=true)). This also dovetails with broader “Solved” UI polish conversations in the main plugin topic ([read more](https://meta.discourse.org/t/-/30155/400?silent=true)). - The new “Solved in OP” styling got a small-but-important UX critique: the expand/collapse arrow placement _looks like it might close the entire box_, and @Moin compared it to quote controls as a precedent for header-positioned actions ([read more](https://meta.discourse.org/t/-/400444/1?silent=true)). - In Foundation modernization progress, theme/component developers pushed for clarity on timelines and scoping. @jordan.vidrine shared a plan to merge smaller items into core while keeping bigger pieces behind a feature flag, and asked for concrete examples of the “two foundations” pain (buttons were a notable offender) ([read more](https://meta.discourse.org/t/-/395331/65?silent=true)). * * * **#Support** - “Which Windows versions are supported?” turned into a practical boundary-setting discussion: _Discourse follows Microsoft’s support lifecycle_, and while Windows XP-era access can sometimes be coaxed via browser forks, Windows 7 users are increasingly hitting hard stops. Falco and others traded real-world options and diagnostics (including TLS suspicion) ([read more](https://meta.discourse.org/t/-/400384/7?silent=true)). Background context: the old-browser support policy shift and minimum Firefox feature requirements ([read more](https://meta.discourse.org/t/-/358131/1?silent=true)). - An **OIDC login error affecting the OpenAI developer forum (Discourse-hosted)** was confirmed by multiple users; @sam escalated the issue, and follow-up indicated it was resolved ([read more](https://meta.discourse.org/t/-/400392/5?silent=true)). - Category-level moderation permissions were clarified: if a group is added as category moderators, **every member** of that group gets those moderation powers—so create a dedicated group for moderators rather than reusing a broad group ([read more](https://meta.discourse.org/t/-/400401/2?silent=true)). (Original “how-to” reference that caused confusion: [read more](https://meta.discourse.org/t/-/116478/1?silent=true)). - A file-handling support question surfaced: on some instances, clicking `.txt`/`.yaml` attachments opens raw text in a new tab instead of downloading. Discussion focused on storage/CDN behavior and `content-disposition` headers, with a pointer to prior S3 filename/download behavior threads ([read more](https://meta.discourse.org/t/-/400405/1?silent=true); [read more](https://meta.discourse.org/t/-/152797/1?silent=true)). - After a failed upgrade/rebuild and recovery, an admin reported _admin-panel-only sluggishness_; @Falco pointed out the immediate culprit: `discourse-question-answer` is deprecated and should be removed ([read more](https://meta.discourse.org/t/-/400446/2?silent=true)). - A new customer reported being stuck at **“Almost there… shouldn’t take much longer now”** while creating a new hosted site, noting that the commonly-linked workaround “try another browser” didn’t help (and forced multiple account names) ([read more](https://meta.discourse.org/t/-/400466/1?silent=true)). Prior related thread (now closed) referenced by the reporter: [read more](https://meta.discourse.org/t/-/398993/1?silent=true). * * * **#Site\_feedback** - A request was raised to include **version numbers** in feature/bugfix announcement topics to help admins on managed hosting (or anyone not tracking `tests-passed`) understand when changes will land. @RGJ highlighted how heavy plugin/theme stacks make rapid updates unrealistic, suggesting announcements could better connect to release tracking ([read more](https://meta.discourse.org/t/-/400394/1?silent=true)). * * * **#Theme\_component** - @Moin published a tiny but practical component that **restores the fullscreen composer toggle on larger touch devices (tablets)** where it’s hidden by default ([read more](https://meta.discourse.org/t/-/400433/1?silent=true)). Install/help references: theme install guide ([read more](https://meta.discourse.org/t/-/63682/1?silent=true)) and theming beginner guide ([read more](https://meta.discourse.org/t/-/91966/1?silent=true)). - Maintenance notes landed on the long-running “left side hamburger menu on mobile” component: the migration away from separate mobile/desktop view folders broke some assumptions, and @featheredtoast acknowledged it needs updating; @Lilly shared a “hacky but works” CSS approach as a stopgap ([read more](https://meta.discourse.org/t/-/164513/48?silent=true)). * * * **#wordpress** - A wp-discourse feature request asked for a way to **exclude specific Discourse replies from being shown as WordPress comments** —ideally via tagging—so divisive/off-topic replies can remain on Discourse without being amplified on the WP front-end. Discussion quickly identified that tags are topic-level, and explored whether a post-level signal (analogous to “Only Import Moderator-Liked”) would work better ([read more](https://meta.discourse.org/t/-/400422/1?silent=true)). * * * **#bug** - A caching/keying issue was reported: `/favicon/proxied` appears to return the **same image for different input URLs** , reproducible on meta itself, suggesting a cache key problem ([read more](https://meta.discourse.org/t/-/400464/1?silent=true)). - Another meta-specific bug report: opening meta sometimes shows **topics from 1–2 days ago** first, followed by a “new/unread topics” banner that reveals the real latest list; clearing cookies helped briefly but the issue returned ([read more](https://meta.discourse.org/t/-/400459/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** engaged on mobile composer simplification—framing the discussion around removing/streamlining default UI affordances while noting Meta is a “worst case” because it tests many features ([read more](https://meta.discourse.org/t/-/400393/3?silent=true)). They also acknowledged and linked the fix for the untranslatable “Solved” string ([read more](https://meta.discourse.org/t/-/400436/2?silent=true)), and continued troubleshooting theme-related composer/draft issues in a “reddit-ish” theme thread ([read more](https://meta.discourse.org/t/-/269466/125?silent=true)). - **@Falco** provided clear guidance on Windows support boundaries (tying Discourse support to Microsoft support) and tested real-world workarounds via alternative browser forks for older systems ([read more](https://meta.discourse.org/t/-/400384/7?silent=true); [read more](https://meta.discourse.org/t/-/400384/14?silent=true)). Falco also helped triage a post-upgrade performance issue by identifying a deprecated plugin that should be removed ([read more](https://meta.discourse.org/t/-/400446/2?silent=true)). - **@sam** escalated the OpenAI forum OIDC login issue through internal contacts, and later follow-up indicated resolution ([read more](https://meta.discourse.org/t/-/400392/5?silent=true)). - **@jordan.vidrine** joined the mobile composer thread with design-feedback coaching and empathy for the complexity of the current mobile UI surface area ([read more](https://meta.discourse.org/t/-/400393/6?silent=true)). They also posted a status update on modernizing Foundation—what can be merged, what stays behind flags, and asked for concrete theme/component breakage examples ([read more](https://meta.discourse.org/t/-/395331/65?silent=true)). - **@featheredtoast** acknowledged that the move away from separate mobile/desktop views broke assumptions in the left-hamburger theme component, and confirmed it needs updating while discussing a more robust layout approach ([read more](https://meta.discourse.org/t/-/164513/48?silent=true)). - **@supermathie** dug into the “Windows support” thread from a protocol angle, asking whether failures might be due to TLS negotiation and suggesting a concrete diagnostic workflow using SSL Labs’ client test ([read more](https://meta.discourse.org/t/-/400384/10?silent=true); [read more](https://meta.discourse.org/t/-/400384/12?silent=true)). * * * Yesterday’s moral: may your composer stop freezing, your “Solved” strings translate on the first try, and your Windows 7 holdouts discover a browser fork before your support inbox does. ---
### 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: [12 באפריל,‏ 2026,‏ 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/796 "2026-04-12T13:01:43Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 34 - **New topics (last 24h):** 4 > Snapshot based on active threads from the last day, including sign-in/sign-up incidents, UX polish reports, and theme/component support discussions (e.g. [read more](https://meta.discourse.org/t/-/400466/4?silent=true), [read more](https://meta.discourse.org/t/-/400392/9?silent=true), [read more](https://meta.discourse.org/t/-/400481/1?silent=true), [read more](https://meta.discourse.org/t/-/118164/298?silent=true)). **Top users (posts / likes in the last 24h):** - **@hellekin:** 5 posts / 3 likes (active across product/meta discussions like [read more](https://meta.discourse.org/t/-/399835/76?silent=true) and banner workflow threads [read more](https://meta.discourse.org/t/-/398306/19?silent=true)) - **@NateDhaliwal:** 4 posts / 2 likes (hands-on support + guidance, e.g. signups [read more](https://meta.discourse.org/t/-/400466/2?silent=true) and Discourse ID debugging pointers [read more](https://meta.discourse.org/t/-/400487/2?silent=true)) - **@Moin:** 4 posts / 2 likes (localization/editor workflow threads like [read more](https://meta.discourse.org/t/-/400481/2?silent=true) and automations formatting [read more](https://meta.discourse.org/t/-/391347/11?silent=true)) - **@pmusaraj:** 2 posts / 4 likes (incident response + resolution update [read more](https://meta.discourse.org/t/-/400466/4?silent=true)) - **@Lilly:** 1 post / 4 likes (confirmation that OIDC login is back [read more](https://meta.discourse.org/t/-/400392/8?silent=true)) - **@EricGT:** 1 post / 3 likes (solution-marking + request for root-cause details [read more](https://meta.discourse.org/t/-/400392/9?silent=true)) - **@Canapin:** 1 post / 3 likes (sharp UX bug report on translation tooltip logic [read more](https://meta.discourse.org/t/-/400481/1?silent=true)) - **@ars18:** 1 post / 2 likes (pointed to a possible workaround tool (#Feature-adjacent via minimod) [read more](https://meta.discourse.org/t/-/280203/14?silent=true)) - **@Ethsim2:** 1 post / 1 like (calendar/event behavior feedback [read more](https://meta.discourse.org/t/-/400192/2?silent=true)) - **@alanr:** 3 posts / 1 like (feature follow-up + procurement path discussion [read more](https://meta.discourse.org/t/-/280203/12?silent=true)) * * * ## Interesting Topics ### #Support - @Lilly and @EricGT confirmed an **OIDC login failure affecting the OpenAI community forum** is now fixed, with a request to document the root cause/workaround for future outages (#openid-connect #hosted-support #fixed) — [read more](https://meta.discourse.org/t/-/400392/8?silent=true) / [read more](https://meta.discourse.org/t/-/400392/9?silent=true) - A **new-site creation/sign-up flow** on the free plan briefly got stuck with no DevTools errors; @pmusaraj reported a technical issue and later confirmed it was resolved (#free-plan) — [read more](https://meta.discourse.org/t/-/400466/2?silent=true) / [read more](https://meta.discourse.org/t/-/400466/4?silent=true) / [read more](https://meta.discourse.org/t/-/400466/5?silent=true) - A Chinese-language report showed **“redirect uri is malformed or doesn’t match client redirect URI”** when logging in with Discourse ID; @NateDhaliwal pointed to regenerating Discourse ID credentials and (if needed) a rails-console reset path — [read more](https://meta.discourse.org/t/-/400487/1?silent=true) / [read more](https://meta.discourse.org/t/-/400487/2?silent=true) / [read more](https://meta.discourse.org/t/-/394238/2?silent=true) / [read more](https://meta.discourse.org/t/-/386102/3?silent=true) - Staged users and notifications: a report noted **staged users can’t unsubscribe from “Watching” emails** , raising the question of whether staged users should receive notification emails at all (#staged-users) — [read more](https://meta.discourse.org/t/-/400361/3?silent=true) ### #ux - A potential logic inversion: the **post translation toggle tooltip text appears swapped** (original vs translated states), and may also require refreshes to behave correctly (#content-localization) — [read more](https://meta.discourse.org/t/-/400481/1?silent=true) / [read more](https://meta.discourse.org/t/-/400481/2?silent=true) - Localization polish request: the Wrap modal labels **“Key” and “Value” appear not to be translatable** , with code pointers into core — [read more](https://meta.discourse.org/t/-/400478/1?silent=true) - Event UX expectations: a suggestion that **closed events should still appear in `/upcoming-events`** (or alternatively provide a separate “Delete event” action), to avoid hacks like deliberately breaking BBCode (#calendar-and-event) — [read more](https://meta.discourse.org/t/-/400192/2?silent=true) - The accepted-answer UI: discussion on whether to **move the expand/collapse arrow for an accepted post in the OP** (and whether it’s best left as-is) (#solved) — [read more](https://meta.discourse.org/t/-/400444/3?silent=true) - Automations editor workflow: progress toward making it easier to **enter special formatting like `[wrap]`** and keep Markdown mode behavior predictable (#automation) — [read more](https://meta.discourse.org/t/-/391347/11?silent=true) ### #bug - RTL regression report: on RTL sites, the **new-topic title input (`#reply-title`) stays LTR** despite RTL settings and aggressive CSS attempts (#composer #rtl #content-localization) — [read more](https://meta.discourse.org/t/-/400490/1?silent=true) ### #contribute:feature - Category tooling: an older request resurfaced asking to **let category moderators create subcategories** , plus guidance on commissioning work (and a pointer to mini-mod tooling as a partial workaround) (#category-moderators) — [read more](https://meta.discourse.org/t/-/280203/12?silent=true) / [read more](https://meta.discourse.org/t/-/280203/13?silent=true) / [read more](https://meta.discourse.org/t/-/280203/14?silent=true) / [read more](https://meta.discourse.org/t/-/400019/1?silent=true) - Calendar UX iteration: someone offered to **test a JSON-based Create Event form** idea as part of “single click activation” experimentation (#calendar-and-event) — [read more](https://meta.discourse.org/t/-/400169/8?silent=true) ### #Announcements - The “Boosts on Meta” experiment continued to generate broader reflection—@hellekin argued that **continuing to raise concerns matters** , even for “fun” features, to steer future choices in more sustainable directions — [read more](https://meta.discourse.org/t/-/399835/76?silent=true) ### #customization:theme - In the _FKB Pro – Social theme_, a CSS selector appears to **incorrectly constrain private message width when tags are involved** , with a suspected `:not(.archetype-private_message)` fix — [read more](https://meta.discourse.org/t/-/234323/488?silent=true) ### #customization:theme component - Compatibility check: questions about whether the **Kanban Board theme component works with the Horizon theme** , and whether forking is necessary; early feedback suggested it should work fine (#official #kanban-board) — [read more](https://meta.discourse.org/t/-/118164/297?silent=true) / [read more](https://meta.discourse.org/t/-/118164/298?silent=true) - Banner Featured Links: a quick request asked whether **the buttons can also be shown inside categories** — [read more](https://meta.discourse.org/t/-/327497/28?silent=true) ### #Support (banner workflow follow-ups) - Banner workflow got tricky post-upgrade: a user who “lost” a banner topic realized it was a workflow mistake, but the thread also captured practical cleanup options like splitting/rewriting history and scheduling topics (#pinned-topics) — [read more](https://meta.discourse.org/t/-/398976/3?silent=true) / [read more](https://meta.discourse.org/t/-/398976/4?silent=true) / [read more](https://meta.discourse.org/t/-/60731/1?silent=true) - Related concern: creating global banners from restricted categories remains contentious because **staff-only discussion workflows can be disrupted** , with continued reliance on a known workaround (#pinned-topics) — [read more](https://meta.discourse.org/t/-/398306/19?silent=true) / [read more](https://meta.discourse.org/t/-/398306/11?silent=true) ### #customization:extras - DisHub (native mobile app): the developer posted an update—after delays due to other projects, they’re **refocusing on improvements** and considering open source options — [read more](https://meta.discourse.org/t/-/377296/23?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@pmusaraj** responded to a live onboarding incident, acknowledging **technical issues with new site signups** and then confirming the fix was deployed (“new site signups should work now”) — [read more](https://meta.discourse.org/t/-/400466/3?silent=true) / [read more](https://meta.discourse.org/t/-/400466/4?silent=true) - **@mcwumbly** weighed in on theme compatibility, noting the **Kanban Board theme component should work pretty well with Horizon** — [read more](https://meta.discourse.org/t/-/118164/298?silent=true) * * * Sign-off: With signups un-stuck and OIDC logins behaving again, may tomorrow’s biggest drama be nothing more than a tooltip that finally points the right way. ---
### 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: [13 באפריל,‏ 2026,‏ 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/797 "2026-04-13T13:01:34Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 76** - **New topics (last 24h): 4** — including: - **Highlight to Search** (#customization:theme-component, #search): a new component for highlight→search workflows — [read more](https://meta.discourse.org/t/-/400492/1?silent=true) - **Copy button on the same line as the url input on sharing link modal?** (#ux, #mobile): a small mobile usability tweak request — [read more](https://meta.discourse.org/t/-/400502/1?silent=true) - **Upcoming Events Extra Buttons** (#customization:theme-component, #calendar-and-event): adds “Subscribe” + optional “New event” buttons to `/upcoming-events` — [read more](https://meta.discourse.org/t/-/400503/1?silent=true) - **Cooked error after translate** (#bug, #ai, #dynaloc): a translation/cooking edge case when tables are malformed — [read more](https://meta.discourse.org/t/-/400509/1?silent=true) **Top users by activity (posts) & appreciation (likes)** | User | Posts | Likes | | --- | --- | --- | | @NateDhaliwal | 9 | 16 | | @nathank | 13 | 11 | | @Moin | 7 | 11 | | @Arkshine | 5 | 11 | | @Canapin | 3 | 2 | | @sam | 2 | 2 | | @Lilly | 1 | 4 | | @david | 1 | 2 | | @haydenjames | 1 | 2 | | @renato | 1 | 2 | | @haydenjames | 1 | 2 | > A lot of the “gravity” today clustered around _theme components and UX polish_, especially for search, events, and mobile ergonomics (e.g. [Highlight to Search](https://meta.discourse.org/t/-/400492/1?silent=true), [Upcoming Events Extra Buttons](https://meta.discourse.org/t/-/400503/1?silent=true), and the [share modal copy button layout](https://meta.discourse.org/t/-/400502/1?silent=true)). * * * ## Interesting Topics ### #customization:theme-component - @NateDhaliwal published **Highlight to Search** , a theme component that lets users highlight text in a post and immediately search it (either via Discourse search or an external engine), with install docs referencing the standard guides ([How to install a theme/component](https://meta.discourse.org/t/-/63682/1?silent=true), [Beginner’s guide to themes](https://meta.discourse.org/t/-/91966/1?silent=true)) — [read more](https://meta.discourse.org/t/-/400492/1?silent=true) - In **Banner Featured Links** , @Arkshine helped debug why featured links appeared only on the homepage, pointing to correct _plugin outlet_ usage and suggesting the **Developer Toolbar** to locate outlets more easily — [read more](https://meta.discourse.org/t/-/327497/31?silent=true) (related: [Developer Toolbar component](https://meta.discourse.org/t/-/346215/1?silent=true)) - **Kanban Board** compatibility checks continued: @Lew_Grothe reported Kanban not working on Horizon, @Arkshine suggested confirming attachment + console errors, and @nathank shared CSS tweaks for a wider Horizon layout — [read more](https://meta.discourse.org/t/-/118164/301?silent=true) - **Discourse Lucide Icons** saw troubleshooting around missing Lucide icons; @nathank noted the “extra icons” approach is Font Awesome–specific, and pointed to the canonical “replace default SVG icons” guide for adding more Lucide glyphs — [read more](https://meta.discourse.org/t/-/400133/6?silent=true) (related: [Replace default SVG icons in a theme](https://meta.discourse.org/t/-/115736/1?silent=true)) - **User Field Prompt** feedback focused on UI consistency: @Moin suggested updating the component’s screenshots because the rendered layout now differs from expectations, and @nathank advocated aligning preference display vs prompt display — [read more](https://meta.discourse.org/t/-/185214/25?silent=true) - @nathank released **Upcoming Events Extra Buttons** , adding configurable navigation buttons for `/upcoming-events` (including a direct path to calendar subscription preferences and an optional “Create event” entrypoint) — [read more](https://meta.discourse.org/t/-/400503/1?silent=true) (related: install docs [here](https://meta.discourse.org/t/-/63682/1?silent=true)) ### #bug - In **Opening forum goes to topics 1 day ago, not recent topics** , @NateDhaliwal described Meta “jumping back” to older topic lists (days old) despite showing many “new or updated topics,” while @Canapin connected it to a potentially related banner/update state bug — [read more](https://meta.discourse.org/t/-/400459/2?silent=true) (related: [topic info not updated when using banner](https://meta.discourse.org/t/-/303928/1?silent=true)) - **Cooked error after translate** : @cuo_wu reported a post “cooking” / rendering failure after translation; @Moin identified malformed Markdown tables as the trigger (missing leading/trailing pipes), and fixing the English table resolved the downstream translations — [read more](https://meta.discourse.org/t/-/400509/2?silent=true) (related context surfaced via a linked plugin topic: [Discourse FontAwesome Pro](https://meta.discourse.org/t/-/150871/1?silent=true)) - **New topic title input remains LTR in RTL sites** : @sam explained why CSS can’t solve the empty-field LTR direction behavior, outlined a markup-based approach (defaulting to rtl until content exists), and linked a PR for review — [read more](https://meta.discourse.org/t/-/400490/2?silent=true) (related: earlier report [Titles placeholder in New topic is not RTL](https://meta.discourse.org/t/-/385232/3?silent=true)) - **Cursor jumping around in composer/editor** resurfaced: @Thomas_Rother shared a screencast of the cursor/viewport jumping; @renato noted the report was actually in Markdown mode (not ProseMirror) and requested reproduction on other instances like try.discourse — [read more](https://meta.discourse.org/t/-/263017/22?silent=true) ### #customization:plugin - **Telegram Notifications Plugin** maintenance questions turned into action: after @scavin reported a `.hbs` deprecation warning, @david confirmed the issue is resolved via an upstream change and thanked them for the heads-up — [read more](https://meta.discourse.org/t/-/60483/206?silent=true) (related: the deprecation reference topic mentioned in the warning: [deprecation id discourse.hbs-extension](https://meta.discourse.org/t/-/398896/1?silent=true)) - **Topic Ratings Plugin** got a pragmatic status update: @Arkshine confirmed a PR removing widget references has been merged, restoring compatibility and advising an update — [read more](https://meta.discourse.org/t/-/39578/446?silent=true) ### #Announcements - The **Testing Boosts on Meta** experiment continued to prompt nuanced UX debate: @volas described a “screenshot megathread” use case where boosts could help keep replies clean (after trying Q&A-style structuring), while @nathank argued boosts risk adding friction vs reactions unless implemented _very_ slickly — [read more](https://meta.discourse.org/t/-/399835/78?silent=true) (related: [Question Answer plugin](https://meta.discourse.org/t/-/56032/1?silent=true)) ### #ux - **Copy button on the same line as the url input on sharing link modal?** : @Canapin proposed moving the copy button onto the same row as the share URL on mobile to improve reachability and reduce awkward tapping — [read more](https://meta.discourse.org/t/-/400502/1?silent=true) - **Rebuilding the Meta Branded theme** : @Canapin reported a leaderboard _date range_ picker overflowing horizontally on mobile, raising the question of whether it’s theme-specific or a component layout constraint — [read more](https://meta.discourse.org/t/-/400013/20?silent=true) - Several event-related UX threads stayed active, including the semantics of hiding/closing events and recurring event behavior (e.g. “close vs hide” framing) — [read more](https://meta.discourse.org/t/-/400192/3?silent=true) (related: recurring topic creation discussion [here](https://meta.discourse.org/t/-/370600/5?silent=true), and “Add to Calendar” email/ICS workflow [here](https://meta.discourse.org/t/-/399329/7?silent=true), plus external calendar subscriptions [here](https://meta.discourse.org/t/-/398902/1?silent=true)) ### #Developer-Guides - In **Objects type for theme setting** , constraints for `type: objects` came up again: @singi2016cn shared an approach for extending settings to support a `max` limit on the objects array, including an example schema and initializer-level implementation — [read more](https://meta.discourse.org/t/-/305009/37?silent=true) ### #Support - A Chinese-language login support topic ( **无法登录什么原因** ) continued: @NateDhaliwal suggested checking whether Discourse ID or local email logins were enabled, and whether SSO might be interfering, after the admin could log in but other users could not — [read more](https://meta.discourse.org/t/-/400487/6?silent=true) - **New AI Persona Editor for Discourse** drew configuration questions: @Alon1 asked how to configure a persona to behave like a “standard” chat AI (similar to claude.ai), specifically _without_ searching Discourse content or being aware of site context — [read more](https://meta.discourse.org/t/-/286271/35?silent=true) - A couple of older “solved” support threads saw new housekeeping concerns around visibility/language and indexing — [read more](https://meta.discourse.org/t/-/370407/9?silent=true) and [read more](https://meta.discourse.org/t/-/374615/28?silent=true) (related banner-topic handling guidance: [lost banner topic after upgrade](https://meta.discourse.org/t/-/398976/5?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @sam pushed forward an RTL composer fix, explaining why empty fields default to LTR due to markup semantics and proposing a behavior change (default RTL until input) — [read more](https://meta.discourse.org/t/-/400490/2?silent=true). They also connected the fix back to the earlier RTL placeholder report — [read more](https://meta.discourse.org/t/-/385232/3?silent=true) - @david responded quickly to a real-world deprecation warning in **discourse-telegram-notifications** , confirming the `.hbs` extension deprecation was resolved upstream after a user report — [read more](https://meta.discourse.org/t/-/60483/206?silent=true) (context: the referenced deprecation tracking topic is [here](https://meta.discourse.org/t/-/398896/1?silent=true)) - @renato helped triage a renewed report of “cursor jumping” in the composer, clarifying the reporter was in Markdown mode (not ProseMirror) and requesting broader reproduction testing across instances — [read more](https://meta.discourse.org/t/-/263017/22?silent=true) * * * If yesterday proved anything, it’s that Meta can debate _Boosts_, chase down _RTL edge cases_, and still find time to ship a “highlight-to-search” power tool—all before the coffee gets cold. ---
### 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: [14 באפריל,‏ 2026,‏ 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/798 "2026-04-14T13:02:51Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **Last 24 hours (2026-04-13 → 2026-04-14)** - **New posts:** 58 - **New topics:** 9 **Top users (posts / likes in the last 24h)** | User | Posts | Likes | Recent reference | | --- | --- | --- | --- | | @awesomerobot | 3 | 9 | Fixed tooltip mixups via a PR after a report in [Hover tips on admin post menu are incorrect or missing](https://meta.discourse.org/t/-/400575/2?silent=true) | | @putty | 4 | 7 | Published a new theme component in [Shared Draft as default New Topic](https://meta.discourse.org/t/-/400557/1?silent=true) | | @manuel | 1 | 6 | Added nuance to deprecation expectations in [Deprecating .hbs file extension in themes and plugins](https://meta.discourse.org/t/-/398896/19?silent=true) | | @Lilly | 2 | 5 | Reported UI tooltip issues in [Hover tips on admin post menu are incorrect or missing](https://meta.discourse.org/t/-/400575/1?silent=true) | | @Falco | 2 | 3 | Solved an upgrade break by identifying a broken plugin in [Exception: Failed to initialize site default after upgrade](https://meta.discourse.org/t/-/400558/3?silent=true) | | @darkpixlz | 2 | 3 | Nudged towards better mod-notification etiquette in [Email receive issue](https://meta.discourse.org/t/-/374615/33?silent=true) | | @martin | 1 | 3 | Clarified “Stable vs Permanent” for Upcoming Changes in [Automatically apply grids to image uploads](https://meta.discourse.org/t/-/394784/10?silent=true) | | @Moin | 3 | 3 | Reported console errors with composer autocomplete in [Error in browser console when using hashtag autocomplete…](https://meta.discourse.org/t/-/400570/1?silent=true) | | @jordan.vidrine | 1 | 2 | Steered feature discussion back on-topic in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/79?silent=true) | | @jlc | 3 | 2 | Documented a post-upgrade failure mode in [Exception: Failed to initialize site default after upgrade](https://meta.discourse.org/t/-/400558/1?silent=true) | * * * ## Interesting Topics ### #ux - @Lilly spotted mislabeled or missing hover tooltips in the admin post wrench menu (including copy/paste-looking mismatches), and @awesomerobot responded with a fix PR in [Hover tips on admin post menu are incorrect or missing](https://meta.discourse.org/t/-/400575/2?silent=true) ([report](https://meta.discourse.org/t/-/400575/1?silent=true)). ### #development (#dev-news) - The ongoing deprecation conversation around theme/plugin `.hbs` templates continued, with @manuel arguing that Discourse’s ecosystem needs clear versioning + migration windows rather than “OS-style” stability expectations in [Deprecating .hbs file extension in themes and plugins](https://meta.discourse.org/t/-/398896/19?silent=true) [read more](https://meta.discourse.org/t/-/398896/1?silent=true). ### #Self-hosting - A self-host upgrade failure (“Failed to initialize site default”) turned out to be caused by a broken customization: @Falco identified `discourse-multilingual` and advised removing it, resolving the issue in [Exception: Failed to initialize site default after upgrade](https://meta.discourse.org/t/-/400558/3?silent=true). The thread also referenced the common “restart Docker” troubleshooting path from [Troubleshoot Docker installation issues](https://meta.discourse.org/t/-/13657/4?silent=true) and pointed directly at the broken plugin topic [Multilingual plugin](https://meta.discourse.org/t/-/142740/1?silent=true). ### #customization:theme component (#shared-drafts) - @putty released a theme component that effectively makes “Shared Draft” the default workflow by relabeling the _New Topic_ button and preloading the composer action in [Shared Draft as default New Topic](https://meta.discourse.org/t/-/400557/1?silent=true). It builds on the core feature described in [Shared Drafts: allow staff to collaborate on posts before publishing](https://meta.discourse.org/t/-/83493/1?silent=true), with setup pointers to [How do I install a theme or theme component?](https://meta.discourse.org/t/-/63682/1?silent=true) and [Beginner’s guide to using Discourse Themes](https://meta.discourse.org/t/-/91966/1?silent=true). ### #Support - A tricky “incoming email creates a topic, but only includes the first lines” report narrowed down to HTML parsing quirks (splitting at ``), and @supermathie asked for raw email + generated post source to diagnose what Discourse is treating as quoted/trimmed content in [Topic created by incoming email, doesn’t include most of the content](https://meta.discourse.org/t/-/400576/4?silent=true) ([original report](https://meta.discourse.org/t/-/400576/1?silent=true)). - @Moin reported two distinct console errors triggered by composer hashtag autocomplete (including `generateIconHTML` undefined in [safe mode](https://meta.discourse.org/t/53504?silent=true)), seeking root-cause guidance in [Error in browser console when using hashtag autocomplete in the composer: undefined generateIconHTML](https://meta.discourse.org/t/-/400570/1?silent=true). - A French-language thread dug into “search within two categories at once while staying on the forum page,” with concrete examples using Discourse’s filter-style query syntax shared in [Fonction recherche dans certaines catégories](https://meta.discourse.org/t/-/400385/11?silent=true). Related context included the “external search redirect” theme discussion in [Highlight to Search](https://meta.discourse.org/t/-/400492/8?silent=true) and examples of alternative search components like [Baidu Search](https://meta.discourse.org/t/-/170283/1?silent=true) and [DuckDuckGo Search Suggestions](https://meta.discourse.org/t/-/83902/1?silent=true). ### #bug (#embedding) - Embedded comments are localized _except_ for date strings: @MarkoK reported English month/date formatting persisting in classic embeds (even when UI text is localized) in [Embedded comments dates are still not localized](https://meta.discourse.org/t/-/400582/1?silent=true). The report explicitly ties back to the older baseline issue [Embed: dates are not localized](https://meta.discourse.org/t/-/27997/1?silent=true) and the canonical embed setup guide [Embed Discourse comments on another website via Javascript](https://meta.discourse.org/t/-/31963/1?silent=true). ### #Announcements - “Upcoming Changes” messaging caused confusion around whether Stable implies a future removal of opt-outs; @martin clarified that for auto-grids, **Stable** means “enabled by default for most sites,” not “setting will be removed,” in [Automatically apply grids to image uploads](https://meta.discourse.org/t/-/394784/10?silent=true). That clarification references the broader framework in [Introducing Upcoming Changes, a system to manage new features…](https://meta.discourse.org/t/-/392894/1?silent=true). - The Boosts experiment thread drifted into heavy real-world topics, and @jordan.vidrine asked participants to keep the conversation constructive and relevant to the software feature in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/79?silent=true). ### #contribute:feature (#calendar-and-event) - A deep dive on event-creation UX and wizard-generated markdown explained why wizard interpolation uses a `w` prefix for step IDs, plus noted that Locations integration with Calendar & Events still isn’t in a good state, in [Single click activation of the Create Event modal](https://meta.discourse.org/t/-/400169/11?silent=true). Related “paper-cut” consistency feedback on event participants remains active in [Use user names in participants list](https://meta.discourse.org/t/-/390176/26?silent=true). ### #Support (#calendar-and-event) - On repeating events, the “going” state not resetting automatically was framed as “planned but non-trivial” (needs storing per-date instances, not just recurrence formulas), with a candid status update in [Repeating Event " going" gets not deleted anymore](https://meta.discourse.org/t/-/335780/16?silent=true). (See also the broader Calendar & Event UX feedback in [Use user names in participants list](https://meta.discourse.org/t/-/390176/1?silent=true).) ### #Sysadmins - A concise how-to showed configuring canonical host vs aliases to redirect apex domains to `www` using `DISCOURSE_HOSTNAME` + `DISCOURSE_HOSTNAME_ALIASES` in [@顶级域名重定向到www](https://meta.discourse.org/t/-/400583/1?silent=true). - A second sysadmin guide described redirecting arbitrary subdomains and obtaining wildcard certs with `acme.sh` + DNS validation (with a reminder-worthy implication: **don’t post real credentials** ), in [任何随机子域名重定向到www](https://meta.discourse.org/t/-/400584/1?silent=true). ### #Marketplace - A Mandarin job post sought a full-time Rails + Ember Discourse plugin developer (with explicit expectations around AI tooling usage), in [寻找论坛全职开发](https://meta.discourse.org/t/-/400595/1?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot jumped on multiple UI papercuts: they opened a fix PR after @Lilly’s report in [Hover tips on admin post menu are incorrect or missing](https://meta.discourse.org/t/-/400575/2?silent=true), posted a “this should fix it” update (plus extra improvements) for [Copy button on the same line as the url input on sharing link modal?](https://meta.discourse.org/t/-/400502/2?silent=true), and flagged an i18n oversight with a fix PR in [“Key” und “Value” aus dem Wrap Modal sind nicht übersetzbar](https://meta.discourse.org/t/-/400478/2?silent=true). - @manuel added ecosystem context and expectations-setting around frontend breaking changes and deprecation policy in [Deprecating .hbs file extension in themes and plugins](https://meta.discourse.org/t/-/398896/19?silent=true). - @Falco quickly diagnosed a post-upgrade outage as a broken plugin customization and provided the fix in [Exception: Failed to initialize site default after upgrade](https://meta.discourse.org/t/-/400558/3?silent=true), then later reinforced how full-page search makes filtered queries approachable for everyday users in [Fonction recherche dans certaines catégories](https://meta.discourse.org/t/-/400385/13?silent=true). - @martin clarified how “Upcoming Changes” states should be interpreted (and that “Stable” doesn’t necessarily imply forced permanence) in [Automatically apply grids to image uploads](https://meta.discourse.org/t/-/394784/10?silent=true). - @jordan.vidrine stepped in to keep feature feedback productive and on-topic in [Testing Boosts on Meta](https://meta.discourse.org/t/-/399835/79?silent=true). - @supermathie requested the key diagnostic artifacts (raw email + post source) to properly understand Discourse’s email parsing decisions in [Topic created by incoming email, doesn’t include most of the content](https://meta.discourse.org/t/-/400576/4?silent=true). - @zogstrip provided a transparent status update on the technical constraints behind auto-resetting RSVP/“going” state for recurring events in [Repeating Event " going" gets not deleted anymore](https://meta.discourse.org/t/-/335780/16?silent=true). * * * _That’s it for today—may your hover tooltips be accurate, your auto-grids stay optional, and your Boosts discussions stay blissfully software-shaped._ ---
### 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: [15 באפריל,‏ 2026,‏ 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/799 "2026-04-15T13:01:50Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 78** - **New topics (last 24h): 7** — including: - Missing flag scoring UI: [read more](https://meta.discourse.org/t/-/400602/1?silent=true) - Tag restrictions bypassed when composing from tag pages: [read more](https://meta.discourse.org/t/-/400616/1?silent=true) - MiniScheduler + Sidekiq 8 regression fix proposal: [read more](https://meta.discourse.org/t/-/400645/1?silent=true) - New _Whisper Warning_ theme component: [read more](https://meta.discourse.org/t/-/400629/1?silent=true) - AI translation skipping Portuguese locale: [read more](https://meta.discourse.org/t/-/400612/1?silent=true) - Sysadmin redirect question (apex → www): [read more](https://meta.discourse.org/t/-/400583/1?silent=true) - “Old topic reply warning” seemingly gone: [read more](https://meta.discourse.org/t/-/400688/1?silent=true) **Top users (posts / likes in the last 24h)** - @Moin — **15 posts / 14 likes** - @awesomerobot — **6 posts / 13 likes** - @nat — **6 posts / 4 likes** - @Falco — **3 posts / 6 likes** - @Ed_S — **3 posts / 5 likes** - @darkpixlz — **3 posts / 3 likes** - @Lilly — **2 posts / 5 likes** - @merefield — **2 posts / 3 likes** - @1101010 — **2 posts / 3 likes** - @renato — **1 post / 4 likes** * * * ## Interesting Topics ### #ux - Mobile composing continued to draw heat: @Ed_S shared an iPhone screenshot showing a near-unusable one-line editor, and @Moin pointed out the _hidden_ “collapse toolbar” control—prompting the classic “I never would have guessed” response and renewed focus on #mobile #composer usability ([read more](https://meta.discourse.org/t/-/400393/14?silent=true), [read more](https://meta.discourse.org/t/-/400393/15?silent=true), [read more](https://meta.discourse.org/t/-/400393/18?silent=true)). - The “show everyone who liked/reacted” request is back in focus: @1101010 questioned why a previously full list became truncated, and @awesomerobot explained it as component reuse/consistency—while also confirming it’s now being prioritized as the most voted #Contribute > Feature ([read more](https://meta.discourse.org/t/-/389820/33?silent=true), [read more](https://meta.discourse.org/t/-/389820/34?silent=true)). - Alongside the likes UX discussion, @awesomerobot pointed admins toward better “what’s changing” visibility via _Upcoming Changes_ notices—positioning Meta as the closest thing to a public roadmap, and linking the newer change-warning workflow to a dedicated tracking topic ([read more](https://meta.discourse.org/t/-/389820/36?silent=true), [read more](https://meta.discourse.org/t/-/395390/1?silent=true)). - Sharing modal ergonomics got a small but meaningful mobile polish: the discussion about the copy button placement clarified that the _date_ element isn’t being removed—just reorganized for better readability in post-sharing scenarios (#mobile, #fixed) ([read more](https://meta.discourse.org/t/-/400502/4?silent=true)). ### #bug - Review Queue data quality issues remain an ongoing thread: IP details not updating when switching reviewables is now tracked with a fix in flight, but the broader “reviewable insights correctness” theme continues (including odd stale/stuck fields) ([read more](https://meta.discourse.org/t/-/391230/3?silent=true), [read more](https://meta.discourse.org/t/-/391232/6?silent=true)). - Composer tag enforcement hit a papercut: creating a new topic _from a tag page_ can prefill a tag that’s disallowed by tag-group rules—server-side validation rejects it on submit, but the UI still sets users up to fail (#composer #tags #tag-groups) ([read more](https://meta.discourse.org/t/-/400616/1?silent=true)). - Hashtag autocomplete threw console errors in [safe mode](https://meta.discourse.org/t/53504?silent=true) testing: @zogstrip tied one error to a core fix, while @Moin noted a second error that may relate to translated tags—keeping this one in “hard to reproduce” territory (#hashtag-autocomplete) ([read more](https://meta.discourse.org/t/-/400570/3?silent=true), [read more](https://meta.discourse.org/t/-/53504/1?silent=true)). - Localization edge-cases are still being chased: anonymous `?tl=` behavior and mixed-language topic lists appear related, and @nat indicated a likely fix path while cross-linking the reports (#content-localization) ([read more](https://meta.discourse.org/t/-/400090/4?silent=true), [read more](https://meta.discourse.org/t/-/400209/1?silent=true)). - AI translation may be skipping Portuguese entirely: a report shows auto-generated translations for many locales, but not `pt`—despite being enabled—raising questions about locale handling in the AI translation pipeline (#ai #dynaloc) ([read more](https://meta.discourse.org/t/-/400612/1?silent=true)). ### #Support - Moderators noticed the _flag scoring_ UI is gone: @Lilly couldn’t find the scoring “?” in Review Queue, and @awesomerobot confirmed it was removed due to confusion—while the conversation also highlighted that the official moderation docs may now be misleading where they still reference the old UI ([read more](https://meta.discourse.org/t/-/400602/1?silent=true), [read more](https://meta.discourse.org/t/-/400602/3?silent=true), [read more](https://meta.discourse.org/t/-/63116/100?silent=true)). - Email-in topic creation reliability came up again: @supermathie suggested bypassing brittle HTML→email parsing by generating Markdown from the source system and posting directly via the API, as a more maintainable ingestion pipeline ([read more](https://meta.discourse.org/t/-/400576/6?silent=true)). - Self-hosted mobile push notifications got a “remove the confusing line” moment: @Falco linked a change intended to address the documentation/UX friction around #push-notifications in Docker setups ([read more](https://meta.discourse.org/t/-/394149/18?silent=true)). - A docs restore/reindex problem appears to be triggered by an interaction with discourse-calendar: @nat posted a fix and asked for confirmation, explaining the side-effect that prevented Docs Categories from reindexing after restore (#doc-categories) ([read more](https://meta.discourse.org/t/-/392225/13?silent=true), [read more](https://meta.discourse.org/t/-/392225/15?silent=true)). - Admins reported the “replying to an old topic” warning seemingly disappearing (and customized text vanishing with it), rekindling concerns about silent changes to admin-configured behaviors—plus cross-references to the long-standing “warn on old post” setting discussion and adjacent behavior changes ([read more](https://meta.discourse.org/t/-/400688/1?silent=true), [read more](https://meta.discourse.org/t/-/126798/1?silent=true), [read more](https://meta.discourse.org/t/-/390033/12?silent=true)). ### #customization:theme component - Discourse shipped an official safety toggle for whispers: the new **Whisper Warning** theme component adds a prominent composer control to prevent accidental public replies when staff intended a whisper (#official #whispers), complementing prior UX discussion about where whisper controls should live ([read more](https://meta.discourse.org/t/-/400629/1?silent=true), [read more](https://meta.discourse.org/t/-/379639/4?silent=true)). - A quick fix landed for Quote Callouts: @Arkshine patched a color regression involving “Hide details” so callout styling survives editing/saving as expected ([read more](https://meta.discourse.org/t/-/350962/61?silent=true), [read more](https://meta.discourse.org/t/-/350962/62?silent=true)). ### #Sysadmins - Two closely-related redirect threads (apex → www, and “any random subdomain” → www) surfaced the perennial security/usability tension: guidance touched on _root vs sudo_ expectations in “standard” installs and how instruction wording can confuse admins on hardened hosts ([read more](https://meta.discourse.org/t/-/400583/2?silent=true), [read more](https://meta.discourse.org/t/-/400583/4?silent=true), [read more](https://meta.discourse.org/t/-/400584/3?silent=true)). ### #development - MiniScheduler maintainers flagged a regression introduced by a previous PR: `MiniScheduler::Web` broke due to Sidekiq Web extension API changes, and a corrective PR was proposed to restore compatibility (and add missing test coverage assumptions) ([read more](https://meta.discourse.org/t/-/400645/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** clarified the rationale behind the likes/reactions UI change and confirmed renewed priority on showing the full list ([read more](https://meta.discourse.org/t/-/389820/34?silent=true)); explained why flag scoring was removed from the review queue and invited concrete feedback on what admins used it for ([read more](https://meta.discourse.org/t/-/400602/3?silent=true)); posted a fix direction for stale IP info when navigating reviewables and reduced redundant refetching in insights ([read more](https://meta.discourse.org/t/-/391230/3?silent=true)); and addressed iPad scrolling behavior while the iOS keyboard is up by proposing an exception for tablets ([read more](https://meta.discourse.org/t/-/400006/3?silent=true)). - **@Falco** surfaced a core change relevant to self-hosted push notifications and the “maybe remove that line” docs/UX pain point ([read more](https://meta.discourse.org/t/-/394149/18?silent=true)); helped untangle a translation nuance in a French-language search support thread (what “simultaneous category search” really meant) ([read more](https://meta.discourse.org/t/-/400385/15?silent=true)); and confirmed embed improvements like a floating reply button and a timeline affordance inside embedded comment experiences ([read more](https://meta.discourse.org/t/-/399743/16?silent=true)). - **@renato** acknowledged the mobile composer constraints and confirmed active internal discussion—after merging overlapping reports into the main “2026 mobile composing” thread for better continuity (#composer #mobile) ([read more](https://meta.discourse.org/t/-/400393/18?silent=true)). - **@nat** investigated and shipped a fix for Docs Categories indexing after restore, potentially caused by discourse-calendar side-effects ([read more](https://meta.discourse.org/t/-/392225/15?silent=true)); noted an upcoming fix for a translation-tooltip logic bug, linking it to a related topic-list language issue ([read more](https://meta.discourse.org/t/-/400481/3?silent=true), [read more](https://meta.discourse.org/t/-/400209/1?silent=true)); connected an anonymous `?tl=` localization report to the same underlying issue family and promised follow-up ([read more](https://meta.discourse.org/t/-/400090/4?silent=true)); and resolved a Discourse Livestream access issue by adjusting chat permissions to Trust Level 0, while identifying the “everyone group” edge-case as the likely culprit ([read more](https://meta.discourse.org/t/-/341335/48?silent=true)). - **@zogstrip** confirmed a fix for the `generateIconHTML` console error in hashtag autocomplete and reported difficulty reproducing the second autocomplete error mentioned by @Moin (#hashtag-autocomplete) ([read more](https://meta.discourse.org/t/-/400570/3?silent=true)). - **@supermathie** advised moving from HTML emails toward a direct API posting workflow to improve reliability and maintainability for inbound content pipelines ([read more](https://meta.discourse.org/t/-/400576/6?silent=true)). - **@martin** clarified how “Upcoming Changes” warnings should (and should not) apply to legacy experimental site settings—specifically noting that Stable should avoid certain warning/problem-check behaviors going forward ([read more](https://meta.discourse.org/t/-/394784/15?silent=true)). - **@tgxworld** closed the loop on long-requested moderation workflow features by pointing to the commit that implemented approvals requirements tied to group membership, updating multiple feature request threads accordingly ([read more](https://meta.discourse.org/t/-/148540/4?silent=true), [read more](https://meta.discourse.org/t/-/258867/3?silent=true)). * * * Yesterday’s vibe: _between invisible toolbar toggles, missing flag scores, and a brand-new whisper safety switch, Meta spent the day making sure the right words go to the right place—on the right screen._ ---
### 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: [16 באפריל,‏ 2026,‏ 1:01pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/800 "2026-04-16T13:01:49Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 92** - **New topics (last 24h): 22** **Top contributors (posts • likes)** | User | Posts | Likes | Where they were active | | --- | --- | --- | --- | | @Falco | 12 | 39 | Deep-dive on embedded comments performance + fixes in progress ([read more](https://meta.discourse.org/t/-/400721/3?silent=true)) | | @Moin | 6 | 7 | Helped debug tagging + linking edge-cases ([read more](https://meta.discourse.org/t/-/400694/7?silent=true)) | | @Lilly | 4 | 16 | Shipped a new sidebar-related theme component + several UX/Support threads ([read more](https://meta.discourse.org/t/-/400765/1?silent=true)) | | @Thiago_Mobilon | 3 | 11 | Field report from a high-traffic embed deployment ([read more](https://meta.discourse.org/t/-/400721/1?silent=true)) | | @RGJ | 3 | 8 | Reported multiple regressions affecting plugins and invites ([read more](https://meta.discourse.org/t/-/400699/1?silent=true)) | | @darkpixlz | 2 | 4 | Raised UX concerns about free-plan messaging ([read more](https://meta.discourse.org/t/-/400747/1?silent=true)) | | @haydenjames | 2 | 3 | Advocated for better “old topic” guidance vs discouraging revival ([read more](https://meta.discourse.org/t/-/400688/4?silent=true)) | **Quick link roundup (more active threads you may have missed)** - Plugin/category form regressions tied to simplified category creation surfaced in both a new bug report ([read more](https://meta.discourse.org/t/-/400699/1?silent=true)) and ongoing plugin discussion ([read more](https://meta.discourse.org/t/-/73345/942?silent=true)). - A calendar + chat integration regression after Rollup ended with a PR and merge ([read more](https://meta.discourse.org/t/-/400691/3?silent=true)). - Review queue UX proposals focused on grouping items by user ([read more](https://meta.discourse.org/t/-/400783/1?silent=true)). - A new bug report suggests users can’t see invite details tabs due to a likely route/model typo ([read more](https://meta.discourse.org/t/-/400775/1?silent=true)). - Translation/AI localization continued to generate edge-cases, including mixed-language detection ([read more](https://meta.discourse.org/t/-/400708/1?silent=true)) and Portuguese being skipped in dynaloc translations ([read more](https://meta.discourse.org/t/-/400612/2?silent=true)). - Self-hosters compared notes on real-time updates not appearing without refresh ([read more](https://meta.discourse.org/t/-/400710/1?silent=true)) and a UI oddity on the Backups page ([read more](https://meta.discourse.org/t/-/400730/1?silent=true)). - Theme/component maintenance and modernizations continued, including a left-menu mobile component update ([read more](https://meta.discourse.org/t/-/164513/49?silent=true)) and ongoing work modernizing a video upload component ([read more](https://meta.discourse.org/t/-/170079/59?silent=true)). - One long-running self-hosting investigation traced staff-only 502s after login to git partial-clone behavior during “unseen features” checks ([read more](https://meta.discourse.org/t/-/394612/4?silent=true)). * * * ## Interesting Topics ### #contribute:feature - @Thiago_Mobilon shared a detailed, real-world report on **running Discourse Comments as a “full app” embed** on a high-traffic site—covering server load spikes, caching headers, analytics double-counting, iframe login refresh behavior, polling frequency, and the need for dynamic height; @Falco responded with specific diagnoses and multiple fixes queued up ([read more](https://meta.discourse.org/t/-/400721/1?silent=true)). - A long-running request to **stop wiping all push subscriptions on logoff** got a concrete “done” update from @Falco ([read more](https://meta.discourse.org/t/-/134038/7?silent=true)). ### #bug - A regression affecting **saving category settings for multiple plugins** (including official ones) was traced to FormKit + `enable_simplified_category_creation`, with @awesomerobot pointing plugin authors to a migration approach and example core PR ([read more](https://meta.discourse.org/t/-/400699/2?silent=true)). - The **calendar post event widget** lost its chat-channel link after the Rollup build change; a fix was proposed and quickly merged by @david ([read more](https://meta.discourse.org/t/-/400691/4?silent=true)). - Tag restrictions messaging in the composer appeared inconsistent (“allowed” vs “not allowed” depending on the search term); @zogstrip acknowledged the limits logic needed to be smarter and linked a fix PR ([read more](https://meta.discourse.org/t/-/400696/4?silent=true)). - A self-hosted report that **new replies don’t appear in real-time** (manual refresh required) raised concerns about MessageBus / polling behavior; initial triage focused on whether a proxy/CDN might be involved ([read more](https://meta.discourse.org/t/-/400710/1?silent=true)). - Users seemingly cannot view **invite details tabs** (while staff can), and the report suggests a likely `controllerFor` vs `modelFor` mismatch in the route logic ([read more](https://meta.discourse.org/t/-/400775/1?silent=true)). ### #Support - Community members noticed the **“you are replying to an old topic” warning** is gone; discussion re-centered on Discourse’s preference for durable conversations, with references back to the broader necroposting values discussion ([read more](https://meta.discourse.org/t/-/400688/2?silent=true), and related context: [read more](https://meta.discourse.org/t/-/389992/14?silent=true)). - A hosted customer reported that **remote images started being downloaded and rewritten** by `system` “as of today,” despite exceptions/settings—prompting checks of `disabled image download domains` behavior and staff logs ([read more](https://meta.discourse.org/t/-/400697/1?silent=true)). - A question about **tags on the free hosted plan** was resolved quickly: tags aren’t available on free, even if some settings appear in the UI ([read more](https://meta.discourse.org/t/-/400738/2?silent=true)). - A report claimed **URL encoding gets altered** when using the editor’s link tool, causing 404s; the thread ultimately pointed to reproducibility/version context and ended with the reporter planning an upgrade after testing on try.discourse ([read more](https://meta.discourse.org/t/-/400694/7?silent=true)). ### #ux - A moderation story highlighted a sharp edge in the review queue: **items for the same user can be scattered** , leading to accidental over-enforcement; the suggestion was to group queue items by user or at least surface “this user has other items in queue” more prominently ([read more](https://meta.discourse.org/t/-/400783/1?silent=true)). - Free-plan site owners flagged **confusing shutdown/read-only messaging** when an email suggests you can keep a site alive with activity, but the site appears locked shortly after; @rishabh confirmed the team is investigating and will clarify ([read more](https://meta.discourse.org/t/-/400747/4?silent=true)). ### #customization:theme component - @Lilly released **Discourse Dynamic Sidebar Icon** , a lightweight component that changes the sidebar toggle icon depending on open/closed state and allows admin customization via theme settings ([read more](https://meta.discourse.org/t/-/400765/1?silent=true)). ### #development - A self-hosted admin shared a theme/plugin-side workaround to **force anonymous users to `/login`** (except a safelist of routes), asking for a better way to avoid a “slow redirect” UX on the initial landing experience ([read more](https://meta.discourse.org/t/-/400773/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@Falco** drove follow-ups and actionable fixes around embedded Discourse Comments—covering caching headers, analytics-in-iframe concerns, and performance improvements like native lazy-load support ([read more](https://meta.discourse.org/t/-/400721/3?silent=true), [read more](https://meta.discourse.org/t/-/400721/10?silent=true)). He also clarified how manual language selection affects translation detection for mixed-language posts ([read more](https://meta.discourse.org/t/-/400708/2?silent=true)) and closed the loop on push subscription cleanup behavior ([read more](https://meta.discourse.org/t/-/134038/7?silent=true)). - **@pmusaraj** confirmed a fix path for the Google One Tap iframe refresh issue affecting embeds ([read more](https://meta.discourse.org/t/-/400721/2?silent=true)) and requested clearer reproduction details for an older WeChat mini-program integration thread ([read more](https://meta.discourse.org/t/-/312085/5?silent=true)). - **@awesomerobot** explained why plugin category settings stopped saving under simplified category creation, pointing directly to FormKit migration patterns and an example implementation strategy ([read more](https://meta.discourse.org/t/-/400699/2?silent=true)). - **@zogstrip** acknowledged the tag-limit UX bug and linked the “smarter limits” fix work ([read more](https://meta.discourse.org/t/-/400696/4?silent=true)). - **@david** encouraged and merged the fix for the calendar plugin’s missing chat link regression after Rollup ([read more](https://meta.discourse.org/t/-/400691/2?silent=true), [read more](https://meta.discourse.org/t/-/400691/4?silent=true)). - **@chapoi** weighed in on review queue UX by pointing to existing “insights” data as a starting point for improvement ([read more](https://meta.discourse.org/t/-/400783/3?silent=true)). - **@rishabh** responded to concerns about free-plan shutdown messaging and confirmed the team is checking for clarity and correctness ([read more](https://meta.discourse.org/t/-/400747/4?silent=true)). - **@nat** handled a multilingual edge-case in a site feedback experiment (topic title language mismatch) and flagged the UX constraint for internal discussion ([read more](https://meta.discourse.org/t/-/397606/87?silent=true)); she also continued triage on translation/LLM issues by asking which model was in use and pointing to model deprecations as a potential factor ([read more](https://meta.discourse.org/t/-/400708/9?silent=true)). - **@featheredtoast** merged and confirmed updates to the “left-side hamburger menu on mobile” theme component after cleanup work ([read more](https://meta.discourse.org/t/-/164513/49?silent=true)). - **@Osama** confirmed a fix was merged for RTL title input direction issues (new topic title input staying LTR) ([read more](https://meta.discourse.org/t/-/400490/3?silent=true)). * * * If yesterday taught us anything, it’s that the fastest way to get something fixed on Meta is to ship a PR, toggle the sidebar, and then embed the whole app inside a blog post to see what breaks first. ---
### 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: [17 באפריל,‏ 2026,‏ 1:02pm UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/801 "2026-04-17T13:02:03Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 114 - **New topics (last 24h):** 15 **Top users (posts + likes in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @sam | 1 | 25 | | @Lilly | 8 | 17 | | @Canapin | 11 | 17 | | @pmusaraj | 8 | 13 | | @Falco | 3 | 11 | | @darkpixlz | 1 | 10 | | @chapoi | 3 | 10 | | @awesomerobot | 4 | 10 | | @putty | 5 | 9 | | @lindsey | 2 | 7 | A few threads did the heavy lifting for discussion volume today, including the open-source statement in [read more](https://meta.discourse.org/t/-/400863/1?silent=true), ongoing embedding improvements in [read more](https://meta.discourse.org/t/-/400721/15?silent=true), and plugin/admin workflow friction around category settings in [read more](https://meta.discourse.org/t/-/400699/4?silent=true). * * * ## Interesting Topics ### #blog - **Discourse publicly reaffirmed it’s staying open source** : @sam addressed industry anxiety after another SaaS vendor announced closing their codebase, and framed Discourse’s position as choosing “courage over hiding behind a locked door” in the companion discussion: [read more](https://meta.discourse.org/t/-/400863/1?silent=true). > “Transparency is now becoming exposure.” — context that sparked a nuanced debate about the real security tradeoffs of open source in the AI era ([read more](https://meta.discourse.org/t/-/400863/1?silent=true)). > Related: a shout-out that **[releases.discourse.org](http://releases.discourse.org)** “works and looks amazing now” also surfaced in-thread ([read more](https://meta.discourse.org/t/-/400863/8?silent=true)). ### #bug - **Plugins couldn’t save category settings after the “simplified category setup” flow** : staff acknowledged the rollout needed better warning/mitigation and provided a quick workaround via `/admin/config/upcoming-changes` (disable `enabled_simplified_category_creation`) while fixes landed ([read more](https://meta.discourse.org/t/-/400699/4?silent=true)). Related context/expectations were debated in [Simplified category setup](https://meta.discourse.org/t/-/394971/1?silent=true) and follow-ups about what counts as adequate notification and migration time ([read more](https://meta.discourse.org/t/-/400699/8?silent=true)). - **AI translations intermittently skipped Portuguese when many locales were enabled** : investigation suggests that with ~14 target languages, Portuguese may be skipped due to rate limits/timeouts (but not necessarily due to simultaneous requests), and verbose logging was suggested for diagnosis ([read more](https://meta.discourse.org/t/-/400612/6?silent=true)). Related: language detection/translation confusion was also recently untangled in a separate thread that ended up being configuration-related ([read more](https://meta.discourse.org/t/-/400708/10?silent=true)). - **Free-hosted sites: read-only mode couldn’t be disabled** : a report described the UI toggling read-only “off” but reverting on reload; staff identified the system incorrectly forcing read-only due to an internal timeline assumption and asked the OP to retry while they dig deeper ([read more](https://meta.discourse.org/t/-/400870/4?silent=true)). Related: a timing/timeline concern was cross-referenced here ([read more](https://meta.discourse.org/t/-/400747/4?silent=true)). ### #Announcements - **New “Ideas” category type makes Topic Voting setup far easier** : @lindsey announced a streamlined category-creation path that pre-configures voting-related settings for feature-request style categories ([read more](https://meta.discourse.org/t/-/399365/1?silent=true)). Related: this builds on the long-running [Discourse Topic Voting](https://meta.discourse.org/t/-/40121/1?silent=true) plugin and also connects to requests like “auto self-vote” from topic creators ([read more](https://meta.discourse.org/t/-/394770/1?silent=true)). ### #customization:plugin - **New #experimental Buffer integration plugin to streamline social sharing** : @pmusaraj released an experimental plugin that adds “Share to Buffer” from the share dialog/admin wrench, generating a preview and queuing to Buffer channels ([read more](https://meta.discourse.org/t/-/400819/1?silent=true)). Related: installation guidance references the standard plugin install doc ([read more](https://meta.discourse.org/t/-/19157/1?silent=true)). ### #contribute:feature - **Embedding: lazy-loading + dynamic height improvements surfaced real-world “too-tall composer” edge cases** : in Tecnoblog’s embed experience thread (#embedding), work progressed from “native lazy loading via `