# Ежедневная сводка (5:00 UTC) **URL:** https://meta.discourse.org/t/daily-summary-5am-utc/291851 **Category:** Forum summaries **Created:** [16.Январь.2024 21:58:09 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851 "2024-01-16T21:58:09Z") **Posts on this page:** 20 **Page:** 31
### 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 05:02:04 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/832 "2026-05-13T05:02:04Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 47 - **New topics (last 24h):** 11 ### Top users (posts + likes received) | User | New posts | Likes received | | --- | --- | --- | | @Lilly | 4 | 14 | | @markvanlan | 1 | 11 | | @putty | 2 | 5 | | @Falco | 2 | 4 | | @zogstrip | 3 | 3 | | @martin | 2 | 3 | | @Shauny | 1 | 3 | | @NateDhaliwal | 1 | 2 | | @merefield | 2 | 2 | | @RBoy | 2 | 2 | > Biggest headline: Discourse shared an early look at **fully #Announcements nested replies** —a major shift from the traditional flat timeline model. See the announcement: [read more](https://meta.discourse.org/t/-/402812/1?silent=true) * * * ## Interesting Topics ### #Announcements - **Nested replies are moving from experiment to core direction.** @markvanlan introduced the “fully nested reply view” and described how linked-post navigation can switch into a single-thread view for clarity ([read more](https://meta.discourse.org/t/-/402812/1?silent=true)); early excitement rolled in quickly (including practical “can’t-wait-to-try-it” deployment plans) ([read more](https://meta.discourse.org/t/-/402812/2?silent=true)) - **Permissions clarity: splitting the historical `@everyone` pseudogroup into `anonymous` and `logged_in_users`.** @martin detailed why `@everyone` has become ambiguous and how the upcoming change `granular_anonymous_and_logged_in_groups_permissions` aims to make site settings, category permissions, and tag groups less confusing ([read more](https://meta.discourse.org/t/-/402273/1?silent=true)) - **Reporting UI refinement landed: “Specific groups” is becoming clearer and more consistent.** In the ongoing Admin Reporting improvements thread, @martin noted a merged change that narrows the reporting access options down to clearer choices (No one / Staff / Specific groups), with an illustrative screenshot of the new UI ([read more](https://meta.discourse.org/t/-/395768/28?silent=true)); background context in the same feature line is in the main topic ([read more](https://meta.discourse.org/t/-/395768/1?silent=true)) ### #Self-hosting - **Renaming categories (and slugs) without breaking anything:** The thread confirms the _category ID_ is what matters for routing, not the slug. @putty explained how even “wrong” slugs redirect correctly as long as the ID matches ([read more](https://meta.discourse.org/t/-/402804/2?silent=true)), and @Lilly added that you _can_ safely change slugs too (topic links don’t depend on them) ([read more](https://meta.discourse.org/t/-/402804/6?silent=true)); original question and rollout concerns are here ([read more](https://meta.discourse.org/t/-/402804/1?silent=true)) - **Redirecting users away from missing pages (404s):** A self-hosting admin asked how to send visitors somewhere useful when they hit “page does not exist” errors ([read more](https://meta.discourse.org/t/-/402807/1?silent=true)), and @merefield pointed to a proven approach for redirecting all 404s to home (with a direct reference to an earlier how-to) ([read more](https://meta.discourse.org/t/-/402807/2?silent=true); plus the referenced how-to: [read more](https://meta.discourse.org/t/-/235187/15?silent=true)) - **Self-hosted Discourse AI sentiment setup hit a HuggingFace 404—workaround provided.** A self-hoster reported failing pulls for `cardiffnlp/twitter-roberta-base-sentiment-latest` during container startup ([read more](https://meta.discourse.org/t/-/334451/14?silent=true)); @Falco explained the upstream model change hadn’t merged and recommended pointing to a specific branch (including an updated command) ([read more](https://meta.discourse.org/t/-/334451/15?silent=true)), which resolved the issue for the reporter ([read more](https://meta.discourse.org/t/-/334451/16?silent=true)) ### #bug - **“找不到请求的 url 或资源” when jumping to a reply then editing/saving (Chinese report) gained traction.** The report outlines a reproducible path (expand replies → jump to post → edit → save) leading to a “URL/resource not found” error ([read more](https://meta.discourse.org/t/-/402747/1?silent=true)); @chapoi confirmed and shared console clues ([read more](https://meta.discourse.org/t/-/402747/2?silent=true)), and @zogstrip reported a fix in progress after reproducing locally ([read more](https://meta.discourse.org/t/-/402747/4?silent=true)). A near-identical duplicate report also appeared ([read more](https://meta.discourse.org/t/-/402737/1?silent=true)) - **Grid Lightbox browsing order is wrong (1,3,2,4) when arrowing through images.** @Shauny demonstrated that grid uploads don’t navigate in upload order when using keyboard arrows in the lightbox ([read more](https://meta.discourse.org/t/-/402817/1?silent=true)) - **Monthly recurring automations may be using weekday-based rules instead of calendar days.** In the Automation thread, @Lilly traced behavior to how recurrence rules are generated and suggested the logic may be injecting weekday alignment (e.g., `BYDAY`) where a fixed date (`BYMONTHDAY`) is expected ([read more](https://meta.discourse.org/t/-/402664/13?silent=true)); @zogstrip then pulled in an additional set of eyes for review ([read more](https://meta.discourse.org/t/-/402664/14?silent=true)) - **OpenID Connect group sync risk: users can be removed from “unsynced” groups.** @pmusaraj noted the fix is being backported and should land in minor releases, reducing rollout risk for sites relying on OIDC mapping behaviors ([read more](https://meta.discourse.org/t/-/402416/9?silent=true); original issue context: [read more](https://meta.discourse.org/t/-/402416/1?silent=true)) - **iOS PWA push subscriptions can silently fail when the Service Worker doesn’t control the app immediately.** In the PWA push-notification thread, the contributor updated their PR to ensure the Service Worker takes control right away, and invited early review/testing across deployment setups ([read more](https://meta.discourse.org/t/-/402645/5?silent=true); prior note on upcoming PR changes: [read more](https://meta.discourse.org/t/-/402645/4?silent=true)) ### #Support - **Admin API `/admin/users/list/active.json` intermittently 500s due to `main_user_record[:silenced_till]` nil access.** The report includes stack trace details and notes it started after upgrading to v3.5.2 ([read more](https://meta.discourse.org/t/-/402752/1?silent=true)); @zogstrip suggested the bug was already fixed upstream and pointed to updating to a newer version as likely resolution ([read more](https://meta.discourse.org/t/-/402752/3?silent=true)) - **Embedding Discourse inside Salesforce Experience Cloud via iframe: cookie and domain constraints.** @Falco outlined practical options—either align under the same base domain or adjust `same_site_cookies` (via hidden site settings) to enable the cross-site iframe scenario ([read more](https://meta.discourse.org/t/-/402712/4?silent=true); topic background: [read more](https://meta.discourse.org/t/-/402712/1?silent=true)) ### #ux - **AI settings UI nit: changing the default LLM doesn’t update agent labels until a reload.** @RBoy reported that agents using the “default LLM” don’t immediately reflect the new selection in the UI until the page is refreshed ([read more](https://meta.discourse.org/t/-/402792/1?silent=true)) ### #General - **Interest check: deeper gamification beyond trust levels (XP, streaks, coin economies, progression).** A builder proposed a Discourse integration for an external gamification/progression platform, asking community operators whether there’s demand beyond the built-in badge/trust-level ceiling ([read more](https://meta.discourse.org/t/-/402802/1?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@markvanlan** published the main announcement introducing Discourse’s evolving **nested replies** direction, including the rationale for when nested structures beat a flat timeline and how single-thread views work when linking directly to a post ([read more](https://meta.discourse.org/t/-/402812/1?silent=true)) - **@martin** shipped two notable updates: a new permissions model that distinguishes `anonymous` vs `logged_in_users` to replace confusing uses of `@everyone` ([read more](https://meta.discourse.org/t/-/402273/1?silent=true)), and a merged tweak making Admin Reporting access options clearer in the “Reporting & Analysis” improvements line ([read more](https://meta.discourse.org/t/-/395768/28?silent=true)) - **@Falco** unblocked a self-hosted Discourse AI sentiment deployment by recommending a working model branch after upstream HuggingFace assets returned 404s ([read more](https://meta.discourse.org/t/-/334451/15?silent=true)), and also provided concrete guidance for embedding Discourse into Salesforce Experience Cloud (domain alignment vs `same_site_cookies`) ([read more](https://meta.discourse.org/t/-/402712/4?silent=true)) - **@zogstrip** helped drive bug triage and next steps across multiple threads: confirming a repro and noting a fix in progress for the Chinese “URL/resource not found” editing flow ([read more](https://meta.discourse.org/t/-/402747/4?silent=true)), pointing out that a reported API 500 issue was fixed upstream in newer Discourse versions ([read more](https://meta.discourse.org/t/-/402752/3?silent=true)), and nudging review for a suspected bug in monthly recurring automations ([read more](https://meta.discourse.org/t/-/402664/14?silent=true)) - **@pmusaraj** reported that the **OpenID Connect group-sync regression** is actively being backported and should land in minor releases soon ([read more](https://meta.discourse.org/t/-/402416/9?silent=true)) - **@sam** followed up on an AI configuration bug report by checking whether the Gemini Pro “thinking budget” issue still reproduces for the reporter ([read more](https://meta.discourse.org/t/-/388485/5?silent=true)) - **@chapoi** confirmed the Chinese-language bug report and shared relevant console output as part of the investigation trail ([read more](https://meta.discourse.org/t/-/402747/2?silent=true)) * * * Nested replies are on the horizon—so today’s challenge is to keep your threads tidy _and_ your lightbox arrows in order. ---
### 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 05:02:04 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/833 "2026-05-14T05:02:04Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **103** new posts across **14** new topics. - **Top contributors (posts / likes received in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @Lilly | 9 | 21 | | @lindsey | 2 | 18 | | @awesomerobot | 5 | 12 | | @markvanlan | 4 | 10 | | @zogstrip | 2 | 8 | | @gilles | 6 | 6 | | @Richie | 3 | 4 | | @NateDhaliwal | 3 | 4 | | @nat | 2 | 4 | | @dax | 2 | 4 | > **Quick link rollup (other threads with fresh replies worth bookmarking):** > Community growth strategy continued in _Enterprise_ discussions on [breaking points](https://meta.discourse.org/t/-/402716/2?silent=true) and [scaling too late vs too early](https://meta.discourse.org/t/-/402717/2?silent=true). > A long-running theme thread flagged a pattern issue in **Graceful** ([read more](https://meta.discourse.org/t/-/93040/162?silent=true)) and **Air Theme** shipped fixes ([read more](https://meta.discourse.org/t/-/197703/604?silent=true)). > There were also ongoing bug/support follow-ups on mobile Assign issues ([read more](https://meta.discourse.org/t/-/400986/12?silent=true)), calendar behavior ([read more](https://meta.discourse.org/t/-/372658/5?silent=true)), custom-field sanitization ([read more](https://meta.discourse.org/t/-/402557/3?silent=true)), and an ESR/API compatibility question ([read more](https://meta.discourse.org/t/-/402752/6?silent=true)). > Prior announcements and guides referenced frequently included support-category setup with #solved ([read more](https://meta.discourse.org/t/-/398338/1?silent=true)), post voting UX comparisons ([read more](https://meta.discourse.org/t/-/227808/1?silent=true)), and the theme install guide ([read more](https://meta.discourse.org/t/-/63682/1?silent=true)). > Email troubleshooting also came up again, linking back to the classic checklist ([read more](https://meta.discourse.org/t/-/16326/1?silent=true)). * * * ## Interesting Topics ### #Announcements - @lindsey announced **#solved improvements** : a new **“Me too”** button for _unsolved_ topics in support categories so affected members can opt-in for a notification when a solution is marked, and communities can better gauge impact ([read more](https://meta.discourse.org/t/-/402498/1?silent=true)). - The ongoing rollout of **nested replies** drew practical admin questions (bulk toggling, reversibility, and UX clarity), with implementation details and testing guidance discussed as the feature lands ([read more](https://meta.discourse.org/t/-/402812/8?silent=true)). ### #bug - A regression meant regular users **couldn’t see who the group owners are** ; @awesomerobot confirmed it was unintentionally dropped during a prior table refactor and moved quickly with a fix path ([read more](https://meta.discourse.org/t/-/402886/2?silent=true)). - Lightbox + grid layouts were showing images in the **wrong order** , and @zogstrip traced and fixed the issue after a tricky debugging session ([read more](https://meta.discourse.org/t/-/402817/3?silent=true)). - A composer validation edge case surfaced where **uppercase letters in an AI agent username** can break the “reachable mention” warning logic; @zogstrip linked it to earlier mention-related changes and opened a fix ([read more](https://meta.discourse.org/t/-/401292/6?silent=true)). - Locale detection for Norwegian was misaligned (`no` vs `nb_NO`/`nb-NO`), causing unnecessary translation credit usage and subtle diffs; @nat acknowledged the report and suggested a prompt-level mitigation while a core adjustment is considered ([read more](https://meta.discourse.org/t/-/402859/2?silent=true)). ### #Support - Content localization users reported **titles translating while post bodies didn’t** ; @nat explained a translation length limit was likely at play and noted it resolved after adjusting/processing ([read more](https://meta.discourse.org/t/-/402858/2?silent=true)). - A fresh self-host install sent **test email successfully** but not the initial **activation email** ; debugging focused on verifying `EmailLog` records and isolating where delivery/sending diverged ([read more](https://meta.discourse.org/t/-/402893/2?silent=true)). - A signup UX question: Discourse can prefill `email=` in `/signup`, but can it also prefill `username=`? The thread confirms the gap and explores whether it needs a plugin-level solution ([read more](https://meta.discourse.org/t/-/402890/3?silent=true)). - API posting via a container + reverse proxy produced Redis mutex warnings (“held for too long”); analysis suggested it’s tied to post-creation work under a short-lived lock (often performance/plugin related) rather than proxying itself ([read more](https://meta.discourse.org/t/-/402855/2?silent=true)). ### #development - The new **`discourse-patch-triage` bot** workflow prompted questions about how to collaborate from forks; constraints were clarified (no bot commits to forks, but reviews/suggestions still work) and improvements to bot messaging were made ([read more](https://meta.discourse.org/t/-/402898/2?silent=true)). - A potential **plugin name clash** is brewing: a core PR using the name “Workflow” may collide with an existing plugin called _Discourse Workflow_, raising discoverability and admin confusion concerns ([read more](https://meta.discourse.org/t/-/402854/1?silent=true)). ### #Site Management - Admins digging into sidebar defaults learned the “backfill” behavior is **delta-based** (preserving user preference) rather than a hard reset; @fzngagan documented what gets added/removed and why ([read more](https://meta.discourse.org/t/-/402479/5?silent=true)). ### #contribute:feature - A moderation UX idea proposed **multi-select flagging** (select several posts, flag once, then handle as a grouped review item) to reduce repetitive flag actions in spammy threads ([read more](https://meta.discourse.org/t/-/402928/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@lindsey** introduced the new #solved support UX with a “Me too” opt-in flow and invited ideas for admin-facing reporting/visibility enhancements ([read more](https://meta.discourse.org/t/-/402498/1?silent=true), [read more](https://meta.discourse.org/t/-/402498/4?silent=true)). - **@dax** clarified rollout status (“not enabled on Meta”), enabled testing elsewhere, and provided on-the-ground troubleshooting updates during setup ([read more](https://meta.discourse.org/t/-/402498/6?silent=true), [read more](https://meta.discourse.org/t/-/402498/9?silent=true)). - **@awesomerobot** helped distinguish “Me too” from Boost (separate mechanisms and notification behavior) ([read more](https://meta.discourse.org/t/-/402498/11?silent=true)), confirmed a group-owner display regression and moved it toward a fix ([read more](https://meta.discourse.org/t/-/402886/2?silent=true)), and pushed UX polish around AI model defaults ([read more](https://meta.discourse.org/t/-/402792/2?silent=true)). - **@markvanlan** continued to unpack how nested replies behaves at scale (bulk toggling, historical-topic conversion risk, and reversibility), while steering testing toward dedicated spaces ([read more](https://meta.discourse.org/t/-/402812/8?silent=true), [read more](https://meta.discourse.org/t/-/402812/11?silent=true), [read more](https://meta.discourse.org/t/-/402812/16?silent=true)). - **@zogstrip** landed fixes and follow-ups for tricky regressions—lightbox ordering in grid layouts ([read more](https://meta.discourse.org/t/-/402817/3?silent=true)) and mention validation edge cases affecting AI-agent handles ([read more](https://meta.discourse.org/t/-/401292/6?silent=true)). - **@nat** acknowledged and guided mitigation for Norwegian locale detection mismatches impacting translation behavior ([read more](https://meta.discourse.org/t/-/402859/2?silent=true)) and explained why content localization may translate titles but skip long posts, with a path to resolution ([read more](https://meta.discourse.org/t/-/402858/2?silent=true)). - **@chapoi** delivered a quick, concrete solution for hiding user cards from anonymous visitors via a site setting pointer in a solved support thread ([read more](https://meta.discourse.org/t/-/402846/2?silent=true)). - **@isaac** clarified how to properly interact with `@patch-triage`, what it can/can’t do on forks, and noted internal follow-up on improving fork support ([read more](https://meta.discourse.org/t/-/402898/2?silent=true), [read more](https://meta.discourse.org/t/-/402898/5?silent=true)). - **@fzngagan** documented nuanced sidebar backfill semantics (why it’s incremental, and how to achieve uniformity without clobbering user preferences) ([read more](https://meta.discourse.org/t/-/402479/5?silent=true)). - **@HAWK** kept the _Enterprise_ thread on community-scale pain points moving, focusing discussion on moderation consistency, process design, and governance patterns ([read more](https://meta.discourse.org/t/-/402716/5?silent=true), [read more](https://meta.discourse.org/t/-/402716/9?silent=true)). * * * Power tip for today: keep the lights on—otherwise your rollout might go the way @dax’s neighborhood did mid “Me too” setup ([read more](https://meta.discourse.org/t/-/402498/9?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: [15.Май.2026 05:02:29 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/834 "2026-05-15T05:02:29Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **In the last 24 hours (2026-05-14 → 2026-05-15):** - **New posts:** 53 - **New topics:** 10 **Top users (posts / likes in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @EricGT | 8 | 8 | | @Moin | 6 | 8 | | @Lilly | 6 | 7 | | @ted | 4 | 4 | | @putty | 3 | 3 | | @RGJ | 2 | 6 | | @martin | 2 | 3 | | @gilles | 2 | 2 | | @ToddZ | 1 | 2 | | @noahl | 1 | 2 | **Most active [@team](https://meta.discourse.org/groups/team?silent=true) members (posts / likes in the last 24h):** - @martin (2 posts, 3 likes) - @awesomerobot (1 post, 1 like) - @HAWK (1 post, 1 like) - @nat (1 post, 1 like) - @lindsey (1 post, 0 likes) * * * ## Interesting Topics ### #customization:theme-component - @EricGT highlighted how nested replies can reintroduce “wrong reply button” confusion, arguing the plain **Reply** label isn’t specific enough and should better distinguish replying-to-topic vs replying-to-post ([read more](https://meta.discourse.org/t/-/402911/2?silent=true)). The discussion explicitly ties back to nested replies UX concerns raised in the nested replies announcement thread ([read more](https://meta.discourse.org/t/-/402812/13?silent=true), [read more](https://meta.discourse.org/t/-/402812/14?silent=true)), and @Lilly quickly shipped improvements—first enabling customization of _both_ reply button labels ([read more](https://meta.discourse.org/t/-/402911/9?silent=true)), then adding the floating topic reply button into nested topic views ([read more](https://meta.discourse.org/t/-/402911/11?silent=true)). - A new component aims to remove the “X votes left” line when #topic-voting is configured with effectively “unlimited” votes ([read more](https://meta.discourse.org/t/-/402966/1?silent=true)). @NateDhaliwal suggested conditional visibility when a user is close to running out ([read more](https://meta.discourse.org/t/-/402966/2?silent=true)), and @awesomerobot noted a newly-added site setting—`Topic voting enable vote limits`—that can eliminate the need for absurdly high vote caps in the first place ([read more](https://meta.discourse.org/t/-/402966/4?silent=true)). Related reference points in the ecosystem include the official #topic-voting documentation topic ([read more](https://meta.discourse.org/t/-/40121/1?silent=true)). * * * ### #announcements - The newly-improved “members can indicate they’re experiencing a reported issue” flow sparked a semantics-and-UX debate about whether the **“Me too”** counter should start at **1** (including the OP) or **0** (only “additional” reporters) ([read more](https://meta.discourse.org/t/-/402498/20?silent=true), [read more](https://meta.discourse.org/t/-/402498/23?silent=true)). @lindsey clarified the intent: the count represents “how many people are impacted,” hence starting at 1 to reflect the author’s impact ([read more](https://meta.discourse.org/t/-/402498/22?silent=true)), while @RGJ argued the label should change if the number includes the author ([read more](https://meta.discourse.org/t/-/402498/24?silent=true)). The discussion also referenced how this looks “in the wild,” pointing to an API-related support thread where the button appeared to imply someone else was affected, but was just the OP ([read more](https://meta.discourse.org/t/-/402855/1?silent=true)). - The Horizon theme now has **high context topic cards enabled by default** , expanding the information shown in topic lists and leaning into at-a-glance signals like #solved, #topic-voting, #assign, tags, and excerpts ([read more](https://meta.discourse.org/t/-/402843/1?silent=true)). This builds directly on the earlier “Horizon high context topic cards” introduction ([read more](https://meta.discourse.org/t/-/393470/1?silent=true)) and references core/official feature docs for Solved ([read more](https://meta.discourse.org/t/-/30155/1?silent=true)), Topic Voting ([read more](https://meta.discourse.org/t/-/40121/1?silent=true)), and Assign ([read more](https://meta.discourse.org/t/-/58044/1?silent=true)). - “Upcoming Changes” got a small but impactful UX report: when admins land on a filtered Upcoming Changes URL from a notification, the **Preview** link may be missing—despite being present when you browse the page normally ([read more](https://meta.discourse.org/t/-/392894/26?silent=true)). @martin explained that “Feedback…” and “Preview” are optional metadata per change item and offered to ping internally so more changes include them ([read more](https://meta.discourse.org/t/-/392894/27?silent=true)). * * * ### #contribute:feature - A request proposes suppressing the **“New features available!”** notification on freshly created forums, arguing that on a brand-new instance _everything_ is new and the alert adds noise rather than value ([read more](https://meta.discourse.org/t/-/402999/1?silent=true)). The suggestion echoes the broader principle of reducing early-admin cognitive load (and references prior precedent for suppressing some “upcoming changes” messaging on new sites, via the linked GitHub PR from within the topic: [read more](https://meta.discourse.org/t/-/402999/1?silent=true)). - Another branding/UX request asks for a separate `mobile_logo_dark` (or `login_mobile_logo_dark`) upload specifically for the **login/signup splash screen** , so admins can optimize the unauthenticated first impression without compromising the logged-in mobile header logo ([read more](https://meta.discourse.org/t/-/402949/1?silent=true)). * * * ### #bug - A composer interaction bug report shows that when the cursor sits just above a horizontal rule, pressing ↓ while the emoji picker is open can cause the horizontal rule to steal focus and close the picker ([read more](https://meta.discourse.org/t/-/403019/1?silent=true)). @ted also linked a proposed fix PR for Discourse core right from the report ([read more](https://meta.discourse.org/t/-/403019/2?silent=true)). - The locale detector for #ai content localization hit a mismatch: Norwegian is detected as `no`, but supported locales use `nb_NO`. @nat confirmed that adding explicit mappings to the system prompt is the right direction and shared an upcoming improvement—pulling in the “supported languages” setting so other communities avoid similar issues ([read more](https://meta.discourse.org/t/-/402859/6?silent=true)). * * * ### #ux - A small but visible UI polish issue: user profile bios can be **slightly clipped on the right edge** (especially noticeable with italicized text), suggesting padding/overflow adjustments may be needed ([read more](https://meta.discourse.org/t/-/403012/1?silent=true)). The report usefully references an older analysis of italics overflowing their container (quoted in the topic) to help narrow the likely CSS cause ([read more](https://meta.discourse.org/t/-/403012/1?silent=true)). - The edit bookmark dialog UI got scrutiny: @ted questioned whether a particular button is necessary at all, and noted that its icon and placement are misleading/confusing in its current form ([read more](https://meta.discourse.org/t/-/403018/1?silent=true)). - A proposal suggests showing **uneditable user fields** in profile preferences as **disabled inputs** instead of hiding them, to better match user expectations and reduce confusion—while acknowledging moderation “staff notes” style use-cases might require configurability ([read more](https://meta.discourse.org/t/-/403015/1?silent=true)). - Meta’s experimentation with “simple mode” for doc categories raised two UX questions: how to **get the TOC back** after clicking “timeline,” and why the **toggle translations** button is only visible while the timeline is open—especially when testing #doc-categories, #disco-toc, and #content-localization together ([read more](https://meta.discourse.org/t/-/403003/1?silent=true)). A related “how do I set the same sidebar categories for all users?” thread also saw continued troubleshooting around default vs user-customized sidebar state, relevant to admin predictability expectations ([read more](https://meta.discourse.org/t/-/402479/6?silent=true)). * * * ### #contribute:site-feedback - “Simple mode” appearing in Meta’s #Wiki doc categories sparked feedback about contributor recognition: @Moin argued that showing authorship matters more in the community wiki than in official documentation, and linked several historical threads about docs/wiki discoverability and contribution pathways ([read more](https://meta.discourse.org/t/-/403006/1?silent=true); related: [read more](https://meta.discourse.org/t/-/322620/6?silent=true), [read more](https://meta.discourse.org/t/-/326614/1?silent=true)). * * * ### #enterprise - A scaling story underscored that performance failures can come from **information architecture** rather than media volume—especially when category trees explode into “sub-sub-subcategories.” @jpishgar described a large community buckling under category depth, and @HAWK added a real-world customer migration anecdote where over-deep categorization became a dealbreaker (and reinforced “tags over endless nesting”) ([read more](https://meta.discourse.org/t/-/402717/4?silent=true)). * * * ### #customization:plugin - The official Discourse Subscriptions plugin (#subscriptions #payments) got a high-signal edge-case bug report: in certain flows, the plugin can create a Stripe PaymentIntent _without_ attaching a valid payment method (especially when an expired card exists), leading to silent subscription failures for end users ([read more](https://meta.discourse.org/t/-/140818/751?silent=true)). Related plugin areas also saw activity elsewhere on Meta, including Discourse Workflow’s new visual editor PR announcement ([read more](https://meta.discourse.org/t/-/347110/22?silent=true)) and an OpenID Connect corner case involving disallowed usernames ending with underscores ([read more](https://meta.discourse.org/t/-/103632/325?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @martin posted an announcement that **high context topic cards are now enabled by default in the Horizon theme** , pointing admins to the upcoming change toggle and recapping what the new cards surface ([read more](https://meta.discourse.org/t/-/402843/1?silent=true)). He also followed up in the “Upcoming Changes” system thread to clarify that “Feedback…” and “Preview” links are optional per change item—and offered to prompt internal improvements to metadata coverage ([read more](https://meta.discourse.org/t/-/392894/27?silent=true)). - @awesomerobot replied to the “Hide Votes Left” component thread with timely product news: a new #topic-voting site setting (`Topic voting enable vote limits`) can remove vote limits entirely without the “set it to 100,000” workaround—while noting the component might still be useful for mixed trust-level configurations ([read more](https://meta.discourse.org/t/-/402966/4?silent=true)). - @HAWK added an enterprise perspective to the scaling/IA discussion, describing a prospective customer with extreme geographic sub-categorization, Discourse’s preference for tags in such cases, and why the team declined to support an unsustainable structure ([read more](https://meta.discourse.org/t/-/402717/4?silent=true)). - @nat confirmed the fix direction for Norwegian locale handling in the locale detector, validating the “common language codes” mapping approach and committing to improve the generic system prompt by using the site’s supported languages setting ([read more](https://meta.discourse.org/t/-/402859/6?silent=true)). - @lindsey clarified the intent behind the new “Me too” counter behavior: it starts at **1** to represent the topic author as impacted, framing the counter as “people impacted” rather than “people who clicked” ([read more](https://meta.discourse.org/t/-/402498/22?silent=true)). * * * If today’s Meta was any indication, tomorrow’s Discourse admins will have clearer **Reply** buttons, fewer “100,000 votes left” humblebrags, and emoji pickers that (hopefully) won’t get bullied by horizontal rules. ---
### 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 05:02:02 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/835 "2026-05-16T05:02:02Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **In the last 24 hours (2026-05-15 → 2026-05-16):** - **51 new posts** and **11 new topics** were published across discussions like the bookmark modal UX tweak in [Superfluous button in edit bookmark dialog?](https://meta.discourse.org/t/-/403018/6?silent=true) and the security-oriented thread [Nginx CVE-2026-42945](https://meta.discourse.org/t/-/403121/5?silent=true). **Top contributors (posts / likes)** (Linked examples point to their recent participation.) | User | Posts | Likes | Recent activity | | --- | --- | --- | --- | | @Lilly | 5 | 11 | Reproduced a mobile-only Theme Creator export issue in [Theme Creator… white screen](https://meta.discourse.org/t/-/403108/2?silent=true), and shipped a mobile label option for a theme component in [Discourse Reply Button Labels](https://meta.discourse.org/t/-/402911/14?silent=true). | | @RGJ | 1 | 8 | Flagged risky UX in category editing: [Delete category button is more prominent than Save](https://meta.discourse.org/t/-/403037/1?silent=true). | | @chapoi | 5 | 7 | Removed the bookmark edit dialog toggle after discussion in [Superfluous button in edit bookmark dialog?](https://meta.discourse.org/t/-/403018/6?silent=true) and chimed in on composer UX in [Horizontal rule steals focus…](https://meta.discourse.org/t/-/403019/3?silent=true). | | @tobiaseigen | 1 | 6 | Suggested a visibility/marketing move for Discourse in [Nominate Discourse for the Digital Public Goods Alliance registry](https://meta.discourse.org/t/-/403061/1?silent=true). | | @martin | 1 | 6 | Announced streamlined setup for Events categories in [Easily create Events categories…](https://meta.discourse.org/t/-/401309/1?silent=true). | | @Falco | 1 | 4 | Confirmed an embed login-flow fix in [Tecnoblog’s Experience With Discourse Comments](https://meta.discourse.org/t/-/400721/55?silent=true). | | @NateDhaliwal | 4 | 4 | Added context on “new/unread” behavior in [Removing NEW status from topics - behaviour changed?](https://meta.discourse.org/t/-/403030/3?silent=true) and pointed to a new “me too” style improvement in [Option to hide ‘me too’ replies](https://meta.discourse.org/t/-/275751/2?silent=true). | | @sam | 1 | 3 | Clarified container posture + base image update plan in [Nginx CVE-2026-42945](https://meta.discourse.org/t/-/403121/5?silent=true). | | @nathank | 2 | 3 | Routed a report to the right category in [Silent subscription failures in Subscriptions plugin](https://meta.discourse.org/t/-/403082/2?silent=true) and discussed Custom Wizard capabilities in [Custom Wizard Plugin 🧙](https://meta.discourse.org/t/-/73345/950?silent=true). | | @markvanlan | 1 | 3 | Explained why nested replies didn’t build on Post Voting in [Introducing nested replies](https://meta.discourse.org/t/-/402812/27?silent=true). | **Quick link round-up (more active threads worth a skim):** - Theme/UX: [Discourse Combined Auth Button](https://meta.discourse.org/t/-/401215/5?silent=true), [Hide Votes Left](https://meta.discourse.org/t/-/402966/7?silent=true), [DiscoTOC - automatic table of contents](https://meta.discourse.org/t/-/111143/486?silent=true), [Add separate mobile\_logo\_dark…](https://meta.discourse.org/t/-/402949/2?silent=true) - Support/admin: [Community members can’t access the page](https://meta.discourse.org/t/-/403054/4?silent=true), [使用api发帖，出现错误警告](https://meta.discourse.org/t/-/402855/8?silent=true), [Googlebot 404 errors due to page numbers](https://meta.discourse.org/t/-/96337/15?silent=true), [Can I identify what caused this specific notification](https://meta.discourse.org/t/-/402276/9?silent=true) - Plugins: [No Bump First Post Plugin](https://meta.discourse.org/t/-/385290/6?silent=true), [Discourse Gamification](https://meta.discourse.org/t/-/225916/453?silent=true), [Bug calendar event on mobile](https://meta.discourse.org/t/-/372658/8?silent=true) - Features: [Replace the 🙂 emoji… “More…”](https://meta.discourse.org/t/-/403116/1?silent=true) * * * ## Interesting Topics ### #Announcements - **Events categories got a streamlined “type-based” setup flow.** @martin shared how the Events category type now auto-enables key settings (and ties into the ongoing “category setup initiative”) in [Easily create Events categories using the Events and Calendar plugin](https://meta.discourse.org/t/-/401309/1?silent=true) (#calendar-and-event #events #categories). Related background: [Discourse Calendar and Event](https://meta.discourse.org/t/-/97376/1?silent=true), plus the earlier category-type work for [support categories](https://meta.discourse.org/t/-/398338/1?silent=true) and [ideas categories](https://meta.discourse.org/t/-/399365/1?silent=true). - **Horizon theme now defaults to high-context topic cards.** The announcement in [High context topic cards are now enabled by default in the Horizon theme](https://meta.discourse.org/t/-/402843/1?silent=true) (#horizon-theme) sparked praise and screenshots from adopters. - **Nested replies discussion expanded into “could this replace Post Voting?” territory.** A user asked about combining/replacing Post Voting, and @markvanlan explained why nested replies took a different approach in [Introducing nested replies](https://meta.discourse.org/t/-/402812/27?silent=true). ### #ux - **Category editing UX: “Delete” felt dangerously prominent vs “Save.”** @RGJ nearly deleted a category due to button placement in [Delete category button is more prominent than Save](https://meta.discourse.org/t/-/403037/1?silent=true). - **Bookmark edit modal: a toggle button was doing too little (and got removed).** After clarifying mobile vs desktop behavior, @chapoi opted to remove the toggle discussed in [Superfluous button in edit bookmark dialog?](https://meta.discourse.org/t/-/403018/6?silent=true) (#bookmarks). - **Small admin UX request: link the deprecated setting text directly to Watched Words.** The suggestion is to make “Silence Watched Words” clickable from the deprecated setting description in [Add link from ‘Auto silence first post regex’ description to Watched words](https://meta.discourse.org/t/-/403058/1?silent=true) (#watched-words #site-settings). - **Topic tracking confusion: when does the blue “new” indicator disappear now?** A detailed behavioral question (and follow-up clarifications) landed in [Removing NEW status from topics - behaviour changed?](https://meta.discourse.org/t/-/403030/1?silent=true) (#ux). - **Profile preferences: should uneditable custom fields look “disabled” rather than editable?** The UX proposal (and a staff follow-up question) is in [Show uneditable user fields as disabled inputs in profile preferences](https://meta.discourse.org/t/-/403015/1?silent=true) (#user-custom-fields). ### #bug - **Theme Creator exports: mobile users hit a white screen after tapping Export.** @Lilly confirmed a mobile-only reproduction path in [In Theme Creator, exporting themes results in a white screen](https://meta.discourse.org/t/-/403108/2?silent=true) (#mobile #theme-creator). - **Composer oddity: inserting a horizontal rule could steal focus from the emoji picker.** The report and staff visibility ping are in [Horizontal rule steals focus from emoji picker in the composer](https://meta.discourse.org/t/-/403019/3?silent=true) (#composer #emoji). - **Flagging regression: require-message flags throw a TypeError and silently fail to submit.** A thorough repro + stack trace was posted in [TypeError when submitting a flag with custom content (require\_message flags)](https://meta.discourse.org/t/-/403133/1?silent=true). - **Subscriptions plugin: “silent failures” report was triaged into the bug queue.** The routing/triage update is captured in [Silent subscription failures in Subscriptions plugin](https://meta.discourse.org/t/-/403082/2?silent=true) (#subscriptions). ### #Support - **Security thread: Nginx CVE concern prompted a “base image update” response.** After a “is Discourse vulnerable?” question and some moderation pushback, @sam clarified status/next steps in [Nginx CVE-2026-42945](https://meta.discourse.org/t/-/403121/5?silent=true). ### #wordpress - **SEO headers drift in older WP-embedded comment topics: missing `noindex` + canonical.** @Thiago_Mobilon documented older embedded topics losing expected tags in [Old topics published via WordPress embed are missing x-robots: noindex and canonical tags](https://meta.discourse.org/t/-/403109/1?silent=true) (#wordpress). ### #Enterprise - **Community scaling “breaking points”: discussion shifted toward retaining positive power users.** @HAWK reinforced the value of superusers and linked further reading in [What are some common breaking points as communities grow?](https://meta.discourse.org/t/-/402716/14?silent=true) (#enterprise-ready). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @chapoi iterated quickly on a small-but-impactful UX detail by removing the bookmark modal toggle after feedback in [Superfluous button in edit bookmark dialog?](https://meta.discourse.org/t/-/403018/6?silent=true), and also called for visibility on a composer focus issue in [Horizontal rule steals focus from emoji picker in the composer](https://meta.discourse.org/t/-/403019/3?silent=true). - @awesomerobot suggested improving the placement/flow of the bookmark modal control in [Superfluous button in edit bookmark dialog?](https://meta.discourse.org/t/-/403018/5?silent=true). - @martin announced a simplified creation flow for Events categories (auto-enabling the right settings) in [Easily create Events categories using the Events and Calendar plugin](https://meta.discourse.org/t/-/401309/1?silent=true). - @Falco confirmed a fix for a major embed-mode login-friction complaint (and pointed to the updated flow) in [Tecnoblog’s Experience With Discourse Comments](https://meta.discourse.org/t/-/400721/55?silent=true). - @markvanlan explained the product reasoning behind nested replies (and why it didn’t become “Post Voting v2”) in [Introducing nested replies](https://meta.discourse.org/t/-/402812/27?silent=true). - @HAWK contributed guidance on scaling communities—specifically the benefits of nurturing power users and how to retain them—in [What are some common breaking points as communities grow?](https://meta.discourse.org/t/-/402716/14?silent=true). - @sam addressed container-security concerns and stated the plan to update Discourse’s base image while noting default rules aren’t vulnerable in [Nginx CVE-2026-42945](https://meta.discourse.org/t/-/403121/5?silent=true). * * * _That’s a wrap—may your categories be safe from rogue “Delete” clicks, your embeds log in smoothly, and your bookmarks stay blissfully toggle-free._ ---
### 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 05:01:45 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/836 "2026-05-17T05:01:45Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **In the last 24 hours (2026-05-16 → 2026-05-17):** - **New posts:** 87 - **New topics:** 11 (see the new threads list below) ### Top users (posts / likes) | User | Posts | Likes | | --- | --- | --- | | [@Lilly](https://meta.discourse.org/t/-/403155/1?silent=true) | 17 | 17 | | [@Crown1](https://meta.discourse.org/t/-/403167/1?silent=true) | 8 | 5 | | [@EricGT](https://meta.discourse.org/t/-/403160/1?silent=true) | 7 | 3 | | [@darkpixlz](https://meta.discourse.org/t/-/403167/2?silent=true) | 6 | 3 | | [@Moin](https://meta.discourse.org/t/-/403160/6?silent=true) | 3 | 5 | | [@Falco](https://meta.discourse.org/t/-/403151/4?silent=true) | 2 | 6 | | [@Arkshine](https://meta.discourse.org/t/-/350962/68?silent=true) | 1 | 7 | | [@Jagster](https://meta.discourse.org/t/-/402911/15?silent=true) | 1 | 2 | | [@ondrej](https://meta.discourse.org/t/-/403151/8?silent=true) | 1 | 1 | ### New topics opened (11) - #Support Starter upgrade option confusion on hosted Free plan ([read more](https://meta.discourse.org/t/-/403167/1?silent=true)) - #Bug: Recovering a deleted post hits errors (and may involve nested topics) ([read more](https://meta.discourse.org/t/-/403161/1?silent=true)) - #Support Users can’t delete topics/posts as expected ([read more](https://meta.discourse.org/t/-/403151/1?silent=true)) - #Support Discourse AI translation “not working” (ended up being a preference toggle) ([read more](https://meta.discourse.org/t/-/403160/1?silent=true)) - #Bug: Nested mode disables post admin wrench menu actions ([read more](https://meta.discourse.org/t/-/403155/1?silent=true)) - #Bug: Full-screen reactions on mobile are hard to exit ([read more](https://meta.discourse.org/t/-/403149/1?silent=true)) - #Support /about page “hidden groups” vs overlapping “visible groups” behavior ([read more](https://meta.discourse.org/t/-/403162/1?silent=true)) - #Support Reverse proxy + `X-Forwarded-For` / real IP header config questions ([read more](https://meta.discourse.org/t/-/403181/1?silent=true)) - #UX: Mobile admin UI layout issue on tag group page (Modernize Foundation theme) ([read more](https://meta.discourse.org/t/-/403180/1?silent=true)) - #Support Using tags on the hosted #free-plan (answer: not currently available) ([read more](https://meta.discourse.org/t/-/403137/1?silent=true)) - #Community Building Using Discourse for a small town government/community ([read more](https://meta.discourse.org/t/-/403146/1?silent=true)) ### Continuing conversations that also saw fresh activity - #customization:theme-component: Quote Callouts shipped improvements (history rendering, excerpt stripping, shortcut changes) ([read more](https://meta.discourse.org/t/-/350962/68?silent=true)) - #customization:theme-component: Reply button labeling + reply UI expectations discussion continued ([read more](https://meta.discourse.org/t/-/402911/15?silent=true)) - #Support Admin notice about outdated theme/plugin JS API (investigating which component triggers it) ([read more](https://meta.discourse.org/t/-/401924/8?silent=true)) - #customization:theme-component: Normalized Profile Links component drew console warnings/questions ([read more](https://meta.discourse.org/t/-/345494/7?silent=true)) - #Development: Dev bootstrap flow clarified; dev toolbar explained ([read more](https://meta.discourse.org/t/-/399187/6?silent=true)) - #UX: “NEW” status / read-state behavior change discussion continued ([read more](https://meta.discourse.org/t/-/403030/4?silent=true)) - #Community Building Growth tactics without a product—what changes actually moved the needle? ([read more](https://meta.discourse.org/t/-/399943/8?silent=true)) - #contribute:feature #ai: “Hide ‘me too’ replies” got pointed to newer #solved-related work ([read more](https://meta.discourse.org/t/-/275751/3?silent=true)) - #Support `default_composition_mode` mismatch was fixed (plugin-side) ([read more](https://meta.discourse.org/t/-/401379/10?silent=true)) - #Announcements #solved: “Me too” / solved-improvements feedback kept rolling in ([read more](https://meta.discourse.org/t/-/402498/26?silent=true)) - #Support #email: Registration emails not delivered even though test emails work ([read more](https://meta.discourse.org/t/-/402893/4?silent=true)) - #Plugin: Custom Wizard plugin support—submission deletion + messaging behavior ([read more](https://meta.discourse.org/t/-/73345/953?silent=true)) - #Announcements #chat: Quick replies for chat notifications got a compatibility question ([read more](https://meta.discourse.org/t/-/245358/10?silent=true)) - #WordPress: Embedded WordPress topics missing canonical/noindex—clarification questions ([read more](https://meta.discourse.org/t/-/403109/2?silent=true)) - #Plugin: “No Bump First Post Plugin” discussion continued with bumping workflow questions ([read more](https://meta.discourse.org/t/-/385290/7?silent=true)) * * * ## Interesting Topics ### #Support - @Crown1 reported a confusing hosted upgrade flow where **Starter didn’t appear as an upgrade option** from the Free plan, while only Pro showed up; @mcwumbly confirmed Starter should be available, asked _where the upgrade click originated_, and began investigating what may be influencing the UI (including plan-gated plugin prompts) ([read more](https://meta.discourse.org/t/-/403167/7?silent=true)). - @EricGT thought **Discourse AI translation wasn’t working** , but the thread concluded it was driven by a preference (“show in original language”) and the topic-level toggle that syncs back to user settings; @Moin explained how the toggle works and why it appeared inconsistent ([read more](https://meta.discourse.org/t/-/403160/6?silent=true)). - @Ethsim2 dug into **/about page group visibility edge-cases** : “about page hidden groups” hides the section, but doesn’t prevent a user from appearing via another visible group; discussion focused on whether this is intended and how to avoid accidental exposure (group member visibility settings) ([read more](https://meta.discourse.org/t/-/403162/1?silent=true)). - A hosted Free-plan user asked how to **enable tags** , and @darkpixlz clarified that tags aren’t currently available on the hosted #free-plan, pointing to the Free Plan Beta announcement for context ([read more](https://meta.discourse.org/t/-/403137/2?silent=true)). - @Eviepayne asked how to properly set up **real IP forwarding behind a reverse proxy** (needing `set_real_ip_from` + `real_ip_header X-Forwarded-For`) and whether there’s an env var or `app.yml` option to support this cleanly ([read more](https://meta.discourse.org/t/-/403181/1?silent=true)). ### #bug - @Prempavee couldn’t recover a deleted post and ran into **HTTP 500 errors** when trying to open the topic; @Falco flagged it as likely a bug involving **deleted nested topics** and offered to take a closer look ([read more](https://meta.discourse.org/t/-/403161/12?silent=true)). - @Lilly documented that **nested mode breaks post admin wrench menu actions** (menu opens, actions fail silently), forcing admins to switch back to flat mode to complete moderation tasks ([read more](https://meta.discourse.org/t/-/403155/1?silent=true)). - @Lilly reported a mobile UX/bug where **full-screen reactions are difficult to exit** on iPhone Chrome, sometimes leaving “close the browser window” as the only escape route ([read more](https://meta.discourse.org/t/-/403149/1?silent=true)). - In a related moderation flow, @Prempavee asked why they **can’t delete topics/posts** as a regular user; the thread surfaced core rules (age/no-replies constraints) and also the possibility that **nested mode affects delete controls** , with @ondrej noting delete worked in flat mode but not nested ([read more](https://meta.discourse.org/t/-/403151/8?silent=true)). ### #ux - A mobile browser report (Chinese-language) showed the **admin tag group page rendering incorrectly** when using the Modernize Foundation theme, raising questions about responsive layout regressions in admin screens ([read more](https://meta.discourse.org/t/-/403180/1?silent=true)). - The “NEW status” conversation continued: users observed that **topics appear to be marked read immediately upon entering** , rather than after reaching/reading the end—suggesting a behavioral change worth verifying ([read more](https://meta.discourse.org/t/-/403030/4?silent=true)). ### #development - A plugin naming thread heated up around a **potential “Workflow” plugin name clash** ; @j.jaffeux advised avoiding “Discourse X” naming for non-official plugins and suggested a clearer namespace approach ([read more](https://meta.discourse.org/t/-/402854/4?silent=true)). - Dev setup clarity improved: @Ethsim2 summarized the cleanest approach to **bootstrapping the first admin account in dev** (`d/boot_dev --init`, MailHog, and `bin/rails admin:create`), and @Moin pointed them to the Discourse **developer toolbar** capabilities ([read more](https://meta.discourse.org/t/-/399187/6?silent=true)). ### #customization:theme-component - Quote Callouts shipped a useful round of polish: @Arkshine updated behavior so **callouts render in history revisions** , onebox excerpts strip markers, and the keyboard shortcut moved to `Ctrl/⌘ + Alt + C` ([read more](https://meta.discourse.org/t/-/350962/68?silent=true)). ### #wordpress - A WordPress embed SEO thread progressed with @angus narrowing down a diagnostic checklist around **missing/changed canonical tags and x-robots headers** for older embedded topics—trying to confirm when and how canonical URLs switched to the Discourse URL ([read more](https://meta.discourse.org/t/-/403109/2?silent=true)). ### #Community Building - A practical adoption question: @Architect explored whether Discourse can work for **small town government outreach** (public + resident communications), and what hosting/admin approach makes sense when the “staff” are civic employees rather than a typical product team ([read more](https://meta.discourse.org/t/-/403146/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @mcwumbly engaged on hosted plan upgrades, confirming Starter was intentionally _deprioritized_ on pricing pages but should still be available for Free → Starter upgrades; they asked where the upgrade action originated and began investigating why only Pro was shown in @Crown1’s case ([read more](https://meta.discourse.org/t/-/403167/7?silent=true), [read more](https://meta.discourse.org/t/-/403167/12?silent=true), [read more](https://meta.discourse.org/t/-/403167/15?silent=true)). - @Falco appeared in two moderation/nesting-related support paths: they clarified the **rules for self-deleting topics** (no replies + \<24h) ([read more](https://meta.discourse.org/t/-/403151/4?silent=true)) and identified a likely **bug visiting deleted nested topics** while offering to investigate further ([read more](https://meta.discourse.org/t/-/403161/12?silent=true)). - @j.jaffeux weighed in on plugin ecosystem hygiene, recommending **stronger third-party naming/namespace practices** to reduce collisions with official or upcoming plugins ([read more](https://meta.discourse.org/t/-/402854/4?silent=true)). * * * _May today bring you visible Starter upgrades, working nested-mode wrenches, and reaction overlays with an obvious “close” button._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [18.Май.2026 05:01:26 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/837 "2026-05-18T05:01:26Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 42** (spread across active threads like the update crash report [read more](https://meta.discourse.org/t/-/403196/1?silent=true) and reverse-proxy configuration discussion [read more](https://meta.discourse.org/t/-/403181/1?silent=true)) - **New topics (last 24h): 4** (including a self-host lockout scenario [read more](https://meta.discourse.org/t/-/403202/1?silent=true), an AI plugin hyperlink bug report [read more](https://meta.discourse.org/t/-/403201/1?silent=true), and an update crash workaround [read more](https://meta.discourse.org/t/-/403196/1?silent=true)) **Top users by activity (posts) & appreciation (likes):** - @Falco — **4 posts** , **13 likes** ([example](https://meta.discourse.org/t/-/403196/3?silent=true), [follow-up](https://meta.discourse.org/t/-/403196/7?silent=true)) - @Lilly — **4 posts** , **11 likes** ([example](https://meta.discourse.org/t/-/403196/2?silent=true), [support reply](https://meta.discourse.org/t/-/403198/2?silent=true)) - @TroLLoBlogger — **4 posts** , **8 likes** ([topic starter](https://meta.discourse.org/t/-/403196/1?silent=true), [server details](https://meta.discourse.org/t/-/403196/4?silent=true)) - @Ethsim2 — **4 posts** , **3 likes** ([community building](https://meta.discourse.org/t/-/403146/2?silent=true), [about-page settings deep dive](https://meta.discourse.org/t/-/403162/3?silent=true)) - @NateDhaliwal — **3 posts** , **5 likes** ([1vCPU pain point](https://meta.discourse.org/t/-/403196/10?silent=true), [privacy note](https://meta.discourse.org/t/-/403146/3?silent=true)) - @greymont — **3 posts** , **4 likes** ([hosted signup issue](https://meta.discourse.org/t/-/403198/1?silent=true), [solution confirmation](https://meta.discourse.org/t/-/403198/4?silent=true)) - @david — **1 post** , **4 likes** ([plugin asset build analysis](https://meta.discourse.org/t/-/403196/8?silent=true)) - @merefield — **1 post** , **3 likes** ([swap/vCPU suggestion](https://meta.discourse.org/t/-/403196/5?silent=true)) - @Moin — **1 post** , **2 likes** ([bug fix pointer](https://meta.discourse.org/t/-/373048/23?silent=true)) - @Prempavee — **1 post** , **2 likes** ([delete-topics thread update](https://meta.discourse.org/t/-/403151/12?silent=true)) > Notable theme of the day: _resource constraints + rebuild/update flows_—with discussion around plugin asset compilation timeouts and whether very small single-vCPU servers should avoid web-based updates ([read more](https://meta.discourse.org/t/-/403196/7?silent=true), [read more](https://meta.discourse.org/t/-/403196/12?silent=true)). Additional threads that also saw fresh replies today: small-town government use cases ([read more](https://meta.discourse.org/t/-/403146/2?silent=true)), bulk tag tooling updates ([read more](https://meta.discourse.org/t/-/402693/4?silent=true)), and the Custom Wizard plugin’s missing “advanced” dropdown options ([read more](https://meta.discourse.org/t/-/73345/957?silent=true)). * * * ## Interesting Topics ### #bug - @TroLLoBlogger reported a **crash after attempting to update via the admin UI** , traced to a plugin asset compilation timeout; the workaround was rebuilding via `./launcher rebuild app`, with follow-up discussion about whether **single-vCPU servers** should be steered away from web updates and toward rebuilds ([read more](https://meta.discourse.org/t/-/403196/1?silent=true), [team follow-up](https://meta.discourse.org/t/-/403196/7?silent=true), [analysis](https://meta.discourse.org/t/-/403196/8?silent=true)). - In the long-running “Thanks for Contributing” popup thread, @Moin pointed to a fix landing via a PR, suggesting the issue is already addressed upstream ([read more](https://meta.discourse.org/t/-/373048/23?silent=true)). - The AI locale detector behavior was updated: **Norwegian/Greek locale handling** is now incorporated into the default agent configuration, aiming to reduce mismatches like `no` vs `nb_NO` in supported locales ([read more](https://meta.discourse.org/t/-/402859/7?silent=true)). - A **TypeError occurs when submitting certain flags** that require custom text (`require_message` flags). @sam acknowledged the report and invited a PR while the team investigates ([read more](https://meta.discourse.org/t/-/403133/2?silent=true)). - A new report (in Chinese) describes **hyperlinks inside the official AI plugin not responding** when clicked, with a screenshot showing the affected UI and behavior ([read more](https://meta.discourse.org/t/-/403201/1?silent=true)). ### #Support - A brand-new hosted customer hit an “ **Oops! That page doesn’t exist or is private** ” moment during email verification; the root cause turned out to be testing while still effectively authenticated as admin in another context—resolved by doing a truly clean/incognito verification flow ([read more](https://meta.discourse.org/t/-/403198/1?silent=true), [resolution](https://meta.discourse.org/t/-/403198/4?silent=true)). - Reverse-proxy operators discussed how to properly preserve client IPs with `X-Forwarded-For`: @Eviepayne needed `set_real_ip_from ...` for internal nginx to respect forwarded IPs (after 429s), and @Lilly outlined how to make the change **survive rebuilds** using `replace` in `app.yml`/`web_only.yml` ([read more](https://meta.discourse.org/t/-/403181/5?silent=true), [recommended approach](https://meta.discourse.org/t/-/403181/6?silent=true)). - A nuanced settings interaction question: how `/about` behaves when **“about page hidden groups”** overlaps with **“about page extra groups.”** @Ethsim2 proposed a clearer rule (or even a dedicated boolean setting) to prevent users hidden via one setting from reappearing via another ([read more](https://meta.discourse.org/t/-/403162/3?silent=true), [proposed setting](https://meta.discourse.org/t/-/403162/4?silent=true)). - A developer question explored whether Discourse can **pre-fill both email and username from URL parameters**. The conclusion: email is partially supported via a cookie-to-signup flow, but _username_ isn’t built-in; @ted mapped the relevant Rails/Ember flow for anyone considering a plugin/PR ([read more](https://meta.discourse.org/t/-/402890/5?silent=true)). - The “Missing PNG to JPEG settings” discussion clarified a subtle behavior: PNGs **only convert to JPEG when there’s no transparency** , making the setting more practical than it initially appeared for image-sharing workflows ([read more](https://meta.discourse.org/t/-/395964/7?silent=true)). ### #Self-hosting - A self-host admin locked themselves out by disabling Discourse ID before establishing a local admin login: the instance reported **“No login methods are configured”** , and `/u/admin-login` emails weren’t arriving—highlighting the sharp edges in auth-method transitions if recovery paths aren’t confirmed first ([read more](https://meta.discourse.org/t/-/403202/1?silent=true)). - In a migration/restore thread, @xlg256 suggested downgrading `aws-sdk-s3` to work around rebuild failures introduced by AWS SDK changes, linking to a related deep-dive discussion on the gem bump and integrity protections ([read more](https://meta.discourse.org/t/-/402623/11?silent=true), [related](https://meta.discourse.org/t/-/354217/49?silent=true)). - A question about the **`discourse/discourse` Docker image** asked whether it’s “production-ready” and how to upgrade when the image lags behind official releases—surfacing common confusion between community images and the standard Discourse Docker install path ([read more](https://meta.discourse.org/t/-/380646/28?silent=true)). - Command-line backup workflows got attention: @Jonathan5 double-checked whether CLI backups match the web UI output, then noted confusion about the download path versus where the tarball actually landed—useful caution for “I forgot to back up before rebuild” moments ([read more](https://meta.discourse.org/t/-/64364/37?silent=true), [path detail](https://meta.discourse.org/t/-/64364/38?silent=true)). ### #Announcements - Bulk tag operations: @nat popped into the “Better bulk tag management” announcement thread to say a temporarily-missing feature/behavior will be back “soon™,” keeping momentum on tag tooling improvements ([read more](https://meta.discourse.org/t/-/402693/4?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco drove the investigation on update-related downtime, zooming in on the **plugin build timeout** and asking for server specs—then explicitly questioned whether the combination of **non-core plugins + single vCPU** should trigger guidance to rebuild rather than update via the web UI ([read more](https://meta.discourse.org/t/-/403196/3?silent=true), [read more](https://meta.discourse.org/t/-/403196/7?silent=true), [follow-up](https://meta.discourse.org/t/-/403196/9?silent=true), [constraints note](https://meta.discourse.org/t/-/403196/12?silent=true)). - @david clarified how **pre-built assets** are distributed and why this case behaved differently: the failing `discourse-doc-categories` plugin isn’t core (so its assets aren’t prebuilt/distributed), but the reported **120s compile time** still seemed unusually high for such a simple plugin ([read more](https://meta.discourse.org/t/-/403196/8?silent=true)). - @nat posted an update that the AI locale detection guidance is now **baked into the default agent** , so installations using Norwegian/Greek should have better defaults going forward ([read more](https://meta.discourse.org/t/-/402859/7?silent=true)); and also checked in on the tag tooling announcement with a “back soon™” status update ([read more](https://meta.discourse.org/t/-/402693/4?silent=true)). - @sam acknowledged a newly reported **TypeError when submitting require-message flags** , confirming the team will investigate and welcoming an external PR in the meantime ([read more](https://meta.discourse.org/t/-/403133/2?silent=true)). * * * Yesterday’s vibe: if you needed a reminder to _rebuild first, test in incognito, and never underestimate one lonely vCPU_, meta delivered in full. ---
### 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: [19.Май.2026 05:01:59 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/838 "2026-05-19T05:01:59Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **75** new posts across **13** new topics - **Most active users (posts / likes):** - **@Lilly** — 9 posts / 16 likes - **@awesomerobot** — 4 posts / 14 likes - **@Falco** — 6 posts / 6 likes - **@nathank** — 5 posts / 4 likes - **@darkpixlz** — 4 posts / 3 likes - **@lindsey** — 2 posts / 7 likes - **@Richie** — 2 posts / 3 likes - **@Thomas_Rother** — 1 post / 7 likes - **@david** — 1 post / 5 likes - **@switschel** — 1 post / 4 likes > A lot of today’s conversation clustered around _events & calendaring polish_ (notably #calendar-and-event), plus continued real-world testing and fixes around #nested-replies (e.g. [read more](https://meta.discourse.org/t/-/403155/1?silent=true), [read more](https://meta.discourse.org/t/-/403277/1?silent=true)). * * * ## Interesting Topics ### #Announcements - Discourse shipped **more flexible RSVPs for recurring events** , letting people RSVP to _just the next occurrence_ or _all future occurrences_—a big usability win for organizers using #calendar-and-event ([read more](https://meta.discourse.org/t/-/402827/1?silent=true)). @Lilly immediately asked about notifying groups for upcoming events without spinning up a group PM ([read more](https://meta.discourse.org/t/-/402827/2?silent=true)) and @nathank highlighted how this pairs well with more advanced recurrence patterns (like “nth weekday”) ([read more](https://meta.discourse.org/t/-/402827/3?silent=true), related: [read more](https://meta.discourse.org/t/-/347943/1?silent=true)). - **May 19th 2026 intermediate releases** landed to deliver critical security fixes, with @david pointing admins at the changelogs for multiple supported trains under #release-notes ([read more](https://meta.discourse.org/t/-/403279/1?silent=true)). - Discourse AI got a small but impactful UX boost: you can now **star AI chats** so they stay pinned at the top of your conversation list—rollable via Upcoming Changes as `Enable AI bot starred conversations` (#ai) ([read more](https://meta.discourse.org/t/-/403285/1?silent=true)). ### #ux - A long-standing consistency paper-cut is being addressed: when `discourse_reactions_experimental_allow_any_emoji` is enabled, the “More…” control shouldn’t be represented by the `:-)` emoji. @awesomerobot confirmed a fix in progress (#reactions) ([read more](https://meta.discourse.org/t/-/403116/2?silent=true)). - A new **Form checkbox redesign** (via Upcoming Changes) modernizes FormKit checkboxes: the native checkbox remains functional but visually hidden, while a presentational checkmark span enables better styling and animation. The team asked for bug reports directly in the topic ([read more](https://meta.discourse.org/t/-/403284/1?silent=true)). ### #Support - “Do you ship a default abusive-word list?” came up again. The consensus: **no default list** , because community needs differ—but **Watched Words** is powerful (bulk import/export, block/flag/censor/require approval, wildcards, etc.). @HAWK linked the canonical guide and explained the supported actions (#watched-words) ([read more](https://meta.discourse.org/t/-/403261/1?silent=true), guide: [read more](https://meta.discourse.org/t/-/241735/1?silent=true)). - Nested Replies continues to surface workflow gotchas for admins: one user couldn’t **change topic ownership** (and hoped to transform a reply into a topic), but the immediate workaround was “switch to flat mode” until nested-mode wrench actions are fully restored ([read more](https://meta.discourse.org/t/-/403257/1?silent=true), workaround context: [read more](https://meta.discourse.org/t/-/403257/2?silent=true)). - A practical “power user” question: **is there a shortcut to link to a specific post number** (like “comment #123”) without quoting? The thread confirmed there’s no built-in composer syntax today; copying the post link (or creating a theme component) remains the option ([read more](https://meta.discourse.org/t/-/403237/1?silent=true)). - Custom Wizard users asked how to **remove test submissions** “via Rails,” noting that community/LLM guidance can be unreliable without exact commands. The same question was posted both as a standalone support topic and into the plugin megathread ([read more](https://meta.discourse.org/t/-/403230/1?silent=true), plugin thread: [read more](https://meta.discourse.org/t/-/73345/958?silent=true)). ### #bug - A mobile-only issue: visiting the bottom of a nested-replies testing topic (especially via an unread indicator) can produce a **404 at the bottom of the page**. @Falco flagged it as likely related to nested read-state changes and looped in engineering to investigate (#mobile #nested-replies) ([read more](https://meta.discourse.org/t/-/403277/1?silent=true), staff ping: [read more](https://meta.discourse.org/t/-/403277/2?silent=true)). - A regression (or resurfacing) report: with #topic-voting enabled, users can’t **view who voted on a closed topic** ; the UI shows nothing and the API returns an empty list. The report includes repro steps and screenshots ([read more](https://meta.discourse.org/t/-/403286/1?silent=true), historical reference: [read more](https://meta.discourse.org/t/-/77712/1?silent=true)). - Admin/moderation tooling hit an error path: a **TypeError when submitting a flag requiring a message** (custom flags or “Something Else”) was discussed, with @tgxworld requesting a safe-mode repro to rule out theme/plugin interference ([read more](https://meta.discourse.org/t/-/403133/1?silent=true), [safe mode](https://meta.discourse.org/t/53504?silent=true) guide: [read more](https://meta.discourse.org/t/-/53504/1?silent=true), staff reply: [read more](https://meta.discourse.org/t/-/403133/4?silent=true)). ### #contribute:feature - A thoughtful moderation housekeeping idea: automatically **purge silenced users with no posts after X days** (often pure spam accounts). The author later noted the existing “Clean up inactive users after days” setting may cover the use case, while @awesomerobot recommended “delete and block” for spam cleanly ([read more](https://meta.discourse.org/t/-/403208/1?silent=true), staff guidance: [read more](https://meta.discourse.org/t/-/403208/4?silent=true)). - Bulk operations friction: when **bulk converting Topics → Messages** , there’s no option to add a _Group_ recipient—making “convert a category into a group inbox” hard without manually adding participants. The request proposes matching the richer modal available in the reverse conversion direction ([read more](https://meta.discourse.org/t/-/403267/1?silent=true)). ### #customization:theme-component - A small but real UI polish bug in **Quote Callouts** : code-styled text in callout titles rendered too “short,” causing clipping/overlap in some languages and sizes. A fix was pushed to add missing core CSS for `` and tidy whitespace ([read more](https://meta.discourse.org/t/-/350962/69?silent=true), fix note: [read more](https://meta.discourse.org/t/-/350962/70?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@lindsey** shipped the headline Events improvement— **granular RSVPs for recurring events** —and documented the desktop/mobile interaction differences (#calendar-and-event) ([read more](https://meta.discourse.org/t/-/402827/1?silent=true)). She also followed up in a related support thread to point users at the new behavior ([read more](https://meta.discourse.org/t/-/335780/17?silent=true)). - **@david** published **May 19th 2026 intermediate releases** , pointing self-hosters and hosted customers at the relevant security-fix changelogs (#release-notes) ([read more](https://meta.discourse.org/t/-/403279/1?silent=true)). - **@awesomerobot** made several high-signal drive-bys: confirmed a tweak to how “Me too” counts are tallied in Solved improvements work ([read more](https://meta.discourse.org/t/-/402498/27?silent=true)) and confirmed the “Me too” label text is safe to customize ([read more](https://meta.discourse.org/t/-/402498/30?silent=true)); acknowledged and began addressing the `:-)` “More…” reactions inconsistency (#reactions) ([read more](https://meta.discourse.org/t/-/403116/2?silent=true)); and recommended best-practice spam cleanup (“delete and block”) in a moderation feature discussion ([read more](https://meta.discourse.org/t/-/403208/4?silent=true)). - **@Falco** stayed deep in the #nested-replies trenches: connected a mobile 404 report to read-state work and pinged engineering ([read more](https://meta.discourse.org/t/-/403277/2?silent=true)); clarified how category-level nested settings behave (“default at creation time only”) and reinforced bug-report hygiene (“one bug per topic in #Contribute > Bug”) ([read more](https://meta.discourse.org/t/-/403155/3?silent=true), [read more](https://meta.discourse.org/t/-/403155/4?silent=true)); and linked fixes-in-flight for missing wrench actions and deleted-post recovery problems ([read more](https://meta.discourse.org/t/-/403155/6?silent=true), [read more](https://meta.discourse.org/t/-/403161/17?silent=true)). - **@HAWK** provided the definitive answer on abusive-language moderation: no universal default list, but **Watched Words** offers block/flag/censor/require-approval and more—plus bulk CSV workflows—backed by the reference guide (#watched-words) ([read more](https://meta.discourse.org/t/-/403261/3?silent=true), guide: [read more](https://meta.discourse.org/t/-/241735/1?silent=true)). He also reassured enterprise readers that calendar/events is under active development and video conferencing is on the roadmap ([read more](https://meta.discourse.org/t/-/402716/16?silent=true)). - **@tgxworld** investigated a reported **flag submission TypeError** , asked for a safe-mode confirmation, and noted the bug wasn’t reproducible locally yet ([read more](https://meta.discourse.org/t/-/403133/4?silent=true)). - **@chapoi** announced the **Form checkbox redesign** upcoming change, including before/after captures and implementation detail (native input preserved; stylable presentational element added) ([read more](https://meta.discourse.org/t/-/403284/1?silent=true)). - **@martin** responded to feedback on the “Easily create Events categories” automation, asking for clarification on what a “sidebar equivalent” should mean (e.g., surfacing upcoming events in the sidebar vs. simplifying sidebar setup) ([read more](https://meta.discourse.org/t/-/401309/3?silent=true)). - **@featheredtoast** explained an **unintentional side effect** in discourse\_docker (from clearing stuck web upgrades) and pointed to an in-progress PR to resolve it ([read more](https://meta.discourse.org/t/-/380646/29?silent=true)). - **@sam** shipped the Discourse AI improvement to **star common AI conversations** , making frequently used chats easier to keep at hand (#ai) ([read more](https://meta.discourse.org/t/-/403285/1?silent=true)). * * * Yesterday’s moral: between recurring-event RSVPs, checkbox makeovers, and nested-replies edge cases, even the smallest UI choices can spark the biggest conversations. ---
### 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: [20.Май.2026 05:02:44 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/839 "2026-05-20T05:02:44Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **84** new posts across **16** new topics. - **Most-liked post:** @keegan’s announcement of a docked composer for #ai / #ai-bot conversations ([read more](https://meta.discourse.org/t/-/403327/1?silent=true)). ### Top users (posts + likes in the last 24h) | User | Posts | Likes | | --- | --- | --- | | @keegan | 1 | 12 | | @Falco | 2 | 11 | | @Lilly | 7 | 9 | | @Danielle | 1 | 7 | | @jake | 1 | 6 | | @cocococosti | 1 | 5 | | @awesomerobot | 2 | 4 | | @Ethsim2 | 8 | 4 | | @RGJ | 1 | 3 | | @mae | 1 | 3 | ### Other threads that also saw notable replies - Backup scheduling nuances on multi-container setups (and why S3 matters) ([read more](https://meta.discourse.org/t/-/14855/142?silent=true)) - A long-running Chat/IP exposure concern got bumped again ([read more](https://meta.discourse.org/t/-/375405/12?silent=true)) - A category banner display issue resurfaced (with prior reports linked) ([read more](https://meta.discourse.org/t/-/403363/1?silent=true)) - “DistributedMutex held for too long” warnings popping up in logs ([read more](https://meta.discourse.org/t/-/402855/9?silent=true)) - WordPress embeds: missing canonical/noindex on older embedded topics (diagnostics via Rails console) ([read more](https://meta.discourse.org/t/-/403109/4?silent=true)) - Multisite operators asked about adding new sites _without_ a rebuild ([read more](https://meta.discourse.org/t/-/403367/1?silent=true)) - A “move topics” confusion turned into a helpful subcategory vs tag realization ([read more](https://meta.discourse.org/t/-/403292/4?silent=true)) - WooCommerce + [WP Discourse](https://github.com/discourse/wp-discourse): whether Discourse usernames can safely diverge from WordPress `user_login` ([read more](https://meta.discourse.org/t/-/403297/1?silent=true)) - A blog companion thread argued for staying browser-first (and not forcing apps) ([read more](https://meta.discourse.org/t/-/403381/1?silent=true)) ## Interesting Topics ### #Announcements - @keegan introduced a **docked composer** experience for #ai-bot conversations—aimed at reducing “click Reply again” friction and keeping the input persistent, behind the upcoming change flag `ai_bot_enable_docked_composer` ([read more](https://meta.discourse.org/t/-/403327/1?silent=true)) - In the ongoing splash customization thread, @Falco shared more examples of branding the Discourse splash screen with custom #splash SVGs (and noted improved results using Gemini 3.5 Flash) ([read more](https://meta.discourse.org/t/-/395100/32?silent=true)) - Follow-up discussion on “Events category” creation explored possible integration with Right Sidebar Blocks—@martin is considering whether Discourse can detect the component and enable event-related sidebar blocks automatically (#calendar-and-event #events #categories) ([read more](https://meta.discourse.org/t/-/401309/5?silent=true)) ### #events - An Office Hours replay dives into **MCP + [Data Explorer](https://meta.discourse.org/t/32566?silent=true)** workflows—showing how AI assistants can generate queries and summarize community trends, with the recording linked for those who missed it (#webinar #office-hours) ([read more](https://meta.discourse.org/t/-/403330/1?silent=true)) ### #blog - A companion discussion to Discourse’s latest blog post makes the case that **Discourse “will never block you from the web,”** contrasting with platforms nudging users into apps ([read more](https://meta.discourse.org/t/-/403381/1?silent=true)) ### #support:migration - A phpBB importer performance thread dug into “why is my import slow when CPU is low?”—with Redis timeouts and likely I/O or DB-side bottlenecks (plus a hint that faster migration tooling is in the works) (#phpbb) ([read more](https://meta.discourse.org/t/-/403319/1?silent=true)) ### #Support - External Postgres upgrades bit a self-host: backups fail when the container’s `pg_dump` (v15) talks to a Postgres 18 server—highlighting client/server version mismatch considerations ([read more](https://meta.discourse.org/t/-/403289/1?silent=true)) - A new admin asked how to export **all site data** (not just personal exports), with pointers toward using full site backups ([read more](https://meta.discourse.org/t/-/403374/1?silent=true)) - A report of **Internal Server Error** when approving new users (with OAuth2 auth) focused troubleshooting around `/logs` and browser console output ([read more](https://meta.discourse.org/t/-/403296/1?silent=true)) - A release email appears to link to a **non-existent changelog URL** (missing the `v` prefix), causing a 404 for “See what’s new in the release notes” ([read more](https://meta.discourse.org/t/-/403389/1?silent=true)) ### #contribute:feature - A feature request proposed “delivered” vs “read” indicators for Chat DMs (#chat), with discussion about the social downsides of read receipts and whether it should be optional ([read more](https://meta.discourse.org/t/-/403370/1?silent=true)) ### #ux - The missing “tag info” button prompted clarification: it was removed after adding a dedicated tag settings page, and there’s now a PR to bring it back with a refreshed banner aligned to category banners ([read more](https://meta.discourse.org/t/-/402436/7?silent=true)) ### #customization:theme - Horizon Theme feedback focused on mobile/compact layouts: trouble reproducing a “suggested threads” display issue, plus broader UI density concerns around sticky navigation and footer buttons stacking (#official #horizon-theme) ([read more](https://meta.discourse.org/t/-/360486/81?silent=true)) ### #customization:theme component - Discourse Mermaid users asked about the **update cadence** for mermaid.js (notably for newer chart types like Wardley Mapping), and whether a PR would be welcomed (#official #mermaid) ([read more](https://meta.discourse.org/t/-/218242/53?silent=true)) ### #bug - A reproducible TypeError tied to `require_message: true` flag flows (and `already_did_flagging`) was narrowed down—especially around nested topics where multiple flag reasons remain available unexpectedly ([read more](https://meta.discourse.org/t/-/403133/6?silent=true)) ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @keegan announced the new **docked composer** for AI bot conversations and invited feedback on how it feels in longer back-and-forth chats ([read more](https://meta.discourse.org/t/-/403327/1?silent=true)). - @Falco posted additional splash-screen SVG examples (and commented on model output quality improvements) in the splash branding thread ([read more](https://meta.discourse.org/t/-/395100/32?silent=true)); and welcomed community PRs to update Mermaid support in the official component ([read more](https://meta.discourse.org/t/-/218242/54?silent=true)). - @Danielle published the Office Hours replay and walkthrough framing for MCP + [Data Explorer](https://meta.discourse.org/t/32566?silent=true) in action (including the recording link) ([read more](https://meta.discourse.org/t/-/403330/1?silent=true)). - @cocococosti weighed in on speeding up phpBB imports—suggesting DB-side work like indexes/views/settings tweaks, and teased faster migration tooling on the horizon ([read more](https://meta.discourse.org/t/-/403319/8?silent=true)). - @awesomerobot confirmed that brand-new forums will no longer get “new features” notifications for historical releases (only future ones) ([read more](https://meta.discourse.org/t/-/402999/2?silent=true)); and opened work to bring back/improve the tag info UI affordance ([read more](https://meta.discourse.org/t/-/402436/7?silent=true)). - @mae shared that Discourse had already been submitted to the Digital Public Goods Alliance registry (submission timing and attribution noted) ([read more](https://meta.discourse.org/t/-/403061/3?silent=true)). - @martin responded to feedback on Events-category setup automation and is considering enhancing setup when Right Sidebar Blocks are present ([read more](https://meta.discourse.org/t/-/401309/5?silent=true)). - @nat merged a translation-related PR after adding specs, closing the loop on the reported language-code behavior ([read more](https://meta.discourse.org/t/-/402544/6?silent=true)). - @isaac marked improvements to the @patch-triage bot—supporting fork workflows and expanded actions—then invited broader testing ([read more](https://meta.discourse.org/t/-/402898/8?silent=true)). - @featheredtoast cautioned about the operational risks of relying on the `discourse/discourse` Docker image in production and recommended avoiding mixed upgrade paths that increase exposure to unexpected changes ([read more](https://meta.discourse.org/t/-/380646/31?silent=true)). * * * With docked composers rolling out and migrations still sprinting (even when Redis complains), today’s meta vibe was: ship UX, measure everything, and keep the web open. ---
### 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: [21.Май.2026 05:01:39 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/840 "2026-05-21T05:01:39Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 62 - **New topics (last 24h):** 13 ### Top contributors (posts / likes in the last 24h) - **@NateDhaliwal** — 4 posts / 8 likes - **@Lilly** — 6 posts / 2 likes - **@nicolsdennis** — 3 posts / 4 likes - **@nathank** — 3 posts / 3 likes - **@RGJ** — 2 posts / 4 likes - **@Richie** — 2 posts / 3 likes - **@angus** — 2 posts / 3 likes - **@saquetim** — 1 post / 5 likes - **@davidb** — 1 post / 3 likes - **@eisammy** — 1 post / 3 likes > “_No one will ever be beholden to us._” — @HAWK on data portability while discussing the hosted **Free** plan’s evolving boundaries ([read more](https://meta.discourse.org/t/-/403393/3?silent=true)) * * * ## Interesting Topics #### #Announcements - **A new “simple mode” for Doc Categories (reading-first docs, replies behind a toggle).** @saquetim announced a documentation-focused experience for the Doc Categories plugin, including auto-expanding when linking directly to a reply and an “Updated” style topic list for doc categories ([read more](https://meta.discourse.org/t/-/403366/1?silent=true)). Related background: the Doc Categories plugin overview lives here ([read more](https://meta.discourse.org/t/-/322376/1?silent=true)). - **Reply count placement updated when using Reactions.** @davidb shared an opt-in “upcoming change” that moves the **reply count** to the right to keep reactions alignment consistent in-post for sites running #reactions ([read more](https://meta.discourse.org/t/-/403390/1?silent=true)). - **“Me too” + Solved interactions: requests for category-level configurability.** In the ongoing discussion about Solved improvements, @Noble_Fish argued that combining Topic Voting + Solved + “Me too” can be confusing in mixed-use categories, and asked for more granular controls ([read more](https://meta.discourse.org/t/-/402498/33?silent=true)). - **Events + Calendar UX wishlist: unify upcoming events and topic list in one view.** In the Events and Calendar plugin announcement thread, @nathank proposed a more obvious combined “upcoming events + topics” category view (especially for right-sidebar blocks and “what’s next” scanning) ([read more](https://meta.discourse.org/t/-/401309/6?silent=true)). #### #blog - **Discourse positioning: “Will never block you from the web.”** A new blog post sparked discussion (and a small meta-question about attribution/author display), with @NateDhaliwal asking if the author should be changed to @ducks ([read more](https://meta.discourse.org/t/-/403381/2?silent=true)). #### #ux - **Search UI consistency: casing and punctuation in dropdown labels.** @Richie asked for consistent casing across dropdown options on expanded search (`/search?expanded=true`) and suggested removing the trailing ellipsis from “Only return topics/posts…” ([read more](https://meta.discourse.org/t/-/403413/1?silent=true)). @NateDhaliwal pointed out the “Where topics are…” phrasing may be intentionally sentence-like, but agreed standardization is still valuable ([read more](https://meta.discourse.org/t/-/403413/2?silent=true)). - **Staff auditing gap: undeleting a post doesn’t create a log entry.** @RGJ reported that _deleting_ and _restoring topics_ are logged, but _restoring posts_ isn’t—making it hard to see who restored content without digging into system logs ([read more](https://meta.discourse.org/t/-/403423/1?silent=true)). #### #bug - **Horizon theme header breaks on mid-size (640–767px) viewports (foldables/small tablets).** @nathank reported missing header elements (search/avatar) at certain widths on #horizon-theme, and @Lilly shared a CSS workaround plus notes about a setting that can influence the behavior ([read more](https://meta.discourse.org/t/-/403484/1?silent=true)). - **Emoji autocomplete fails with special characters (e.g. “ü”), worse in Chat.** @Moin shared repro videos showing that selecting an emoji from “more” doesn’t properly replace typed text when special characters are involved—and Chat throws a console error and can fail selection entirely ([read more](https://meta.discourse.org/t/-/403420/1?silent=true)). Related footnote: @Moin noticed a tagging + grace-period edge case again while testing this, in an older bug thread about revisions ([read more](https://meta.discourse.org/t/-/396501/5?silent=true)). - **Tag Icons component inconsistencies (underscore vs dash slug behavior).** @AquaL1te reported missing tag icons in topics/tag pages despite working in the sidebar; @Lilly suspected tag slug normalization (underscores becoming dashes) tied to an upstream change in the component and suggested adjusting slugs in the theme settings accordingly ([read more](https://meta.discourse.org/t/-/403428/4?silent=true)). - **Chat UX bug: Back button forgets “Starred” context.** @Shauny described an everyday annoyance: even when navigating within Starred chats, “Back” returns users to Channels/DMs instead of Starred—adding friction that undermines the feature’s purpose ([read more](https://meta.discourse.org/t/-/403431/1?silent=true)). Related feature reference: starring channels was introduced here ([read more](https://meta.discourse.org/t/-/390713/1?silent=true)). - **Meta testing page shows a 404 at the bottom (nested replies test).** In a bug report about a recurring 404 on a Meta testing route, @markvanlan said they couldn’t reproduce at the moment but would keep an eye out ([read more](https://meta.discourse.org/t/-/403277/4?silent=true)). #### #Support - **Hosted pricing + Free plan boundaries: what changed, and what’s “essential email”?** @Alex_Dehnert flagged confusing shifts in the pricing page emphasis and noted “email in” became locked after working; @HAWK clarified the Free plan is a recent soft launch, that “email in” was disabled after an oversight, and reiterated export/self-host as the escape hatch if plans change ([read more](https://meta.discourse.org/t/-/403393/3?silent=true)). Extra context referenced in-thread: Free plan beta discussion ([read more](https://meta.discourse.org/t/-/395632/14?silent=true)) and “No starter upgrade option” history ([read more](https://meta.discourse.org/t/-/403167/8?silent=true)). - **Theme component upload error: `about.json` invalid/missing (zip structure issues).** @baseline-mobile hit an import error installing a theme component zip; @Moin suggested the zip’s folder structure (often impacted by OS zip behavior) may place `about.json` one directory too deep, and provided a repacked zip that installed successfully ([read more](https://meta.discourse.org/t/-/403447/1?silent=true)). - **Postgres 18 backups failing: how to align client tools and work around version mismatches.** In a support thread, @ted highlighted uncertainty about Discourse’s Postgres client upgrade policy and pointed to prior similar discussions; @pfaffman suggested installing matching client packages and then codifying the steps in `app.yml` ([read more](https://meta.discourse.org/t/-/403289/7?silent=true)). Related older reference: Postgres client upgrade discussions ([read more](https://meta.discourse.org/t/-/215063/1?silent=true)). - **Accessibility question: themes/components that work best with screen readers.** @happyhappy asked whether any themes or theme components are known to be especially navigable for visually impaired users, given most base accessibility work is now in core ([read more](https://meta.discourse.org/t/-/403464/1?silent=true)). #### #wordpress - **[WP Discourse](https://github.com/discourse/wp-discourse) + WooCommerce identity mapping: username sync not required.** @angus explained that [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) matches accounts using `external_id` (WordPress user id), so WordPress and Discourse usernames don’t need to stay aligned—reducing risk if Discourse users rename themselves ([read more](https://meta.discourse.org/t/-/403297/2?silent=true)). - **WordPress embed SEO edge case: missing `topic_embed` records break canonical/noindex behavior.** In a thread about embedded topics missing `x-robots` noindex and canonical tags, @angus noted the canonical-for-embeds feature requires a `topic_embed` record, and discussion continued around making “apply noindex to all topics in category” a more direct setting ([read more](https://meta.discourse.org/t/-/403109/6?silent=true)). #### #General - **A native Discourse client app for iOS + Android (show-and-tell).** @nicolsdennis demoed a native client and noted current plugin support is limited to official plugins (calendar integration is in progress) ([read more](https://meta.discourse.org/t/-/403429/1?silent=true)). Related mention: they also posted an update in an older “turn a forum into an app” thread, saying they’re replying using the client ([read more](https://meta.discourse.org/t/-/378700/19?silent=true)). #### #development - **Notification consolidation: UI-only grouping or database/API-level row reuse?** @nitinkg reported that reply/reaction notifications appear consolidated even with small counts, and asked whether Discourse updates existing notification rows (instead of append-only inserts) and whether consolidation can be disabled for a “one action = one record” model ([read more](https://meta.discourse.org/t/-/403440/1?silent=true)). Related (Chat adjacency): read/delivered semantics for DMs are being debated separately ([read more](https://meta.discourse.org/t/-/403370/5?silent=true)). #### #customization:plugin / #Theme\_component / #Self-Hosting (quick hits worth a peek) - **Plugin rename: “Discourse Workflow” rebranded to “Process Manager.”** @merefield announced a rename due to an upcoming naming conflict with core; tables/indexes were renamed and settings weren’t migrated, so admins should recheck plugin settings and any [Data Explorer](https://meta.discourse.org/t/32566?silent=true) queries ([read more](https://meta.discourse.org/t/-/347110/23?silent=true)). - **Theme component compatibility: Featured Topics vs pavilion dropdown header.** @TestingRico reported a collision where the pavilion dropdown header disappears in preview when testing Featured Topics, and asked about workarounds ([read more](https://meta.discourse.org/t/-/217580/61?silent=true)). Related pavilion ecosystem thread: Topic Ratings plugin discussions continue ([read more](https://meta.discourse.org/t/-/39578/450?silent=true)). - **Cloudflare R2 now working as S3-compatible storage (doc needs an update).** In the long-running S3-compatible uploads/how-to topic, @Lilly reported successful external backups and restores using Cloudflare R2, noting prior incompatibility text is outdated and should be revised ([read more](https://meta.discourse.org/t/-/148916/504?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@saquetim** published an announcement introducing **simple mode** for Doc Categories, emphasizing a _reading-first_ layout with replies behind a toggle and auto-expansion when linking directly to replies ([read more](https://meta.discourse.org/t/-/403366/1?silent=true)). - **@davidb** announced an opt-in layout change for sites using the Reactions plugin: the **reply count** moves to the right to keep alignment consistent throughout posts ([read more](https://meta.discourse.org/t/-/403390/1?silent=true)). - **@markvanlan** followed up on a reported 404 at the bottom of a Meta testing page, noting they couldn’t reproduce currently but would keep watch in case it’s intermittent ([read more](https://meta.discourse.org/t/-/403277/4?silent=true)). - **@HAWK** clarified what’s happening with the hosted **Free plan** (still in soft launch), explaining why “email in” was reverted/disabled, and reaffirming that communities can always export and self-host if priorities change ([read more](https://meta.discourse.org/t/-/403393/3?silent=true)). * * * _That’s a wrap: may your folding-phone headers stay aligned, your tag icons survive every slug rewrite, and your emoji picker learn to love “ü” by tomorrow._ ---
### 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: [22.Май.2026 05:02:47 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/841 "2026-05-22T05:02:47Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… _(Activity window: 2026-05-21 → 2026-05-22)_ * * * ## Key Stats - **New posts (last 24h): 67** - **New topics (last 24h): 8** ### Top contributors (posts + likes earned in the last 24h) | User | Posts | Likes | Recent highlight | | --- | --- | --- | --- | | @Lilly | 8 | 13 | Theme + community onboarding feedback in a new site launch thread — [read more](https://meta.discourse.org/t/-/403511/5?silent=true) | | @zogstrip | 6 | 7 | Rapid “fixed by PR” responses across multiple bug reports — [read more](https://meta.discourse.org/t/-/403520/2?silent=true) | | @NateDhaliwal | 3 | 7 | Clarifying questions + troubleshooting steps on support/bug reports — [read more](https://meta.discourse.org/t/-/403522/2?silent=true) | | @Tris20 | 1 | 5 | Detailed “growth breaks communities” field notes — [read more](https://meta.discourse.org/t/-/402716/17?silent=true) | | @pfaffman | 1 | 4 | Practical follow-up on Postgres tooling + automation — [read more](https://meta.discourse.org/t/-/403289/11?silent=true) | | @kairo162 | 3 | 4 | iOS PWA + nested replies UI regression report — [read more](https://meta.discourse.org/t/-/403532/1?silent=true) | | @Thomas_Rother | 1 | 3 | Solved a Postgres 18 backup failure with a simple fix — [read more](https://meta.discourse.org/t/-/403289/10?silent=true) | | @Discourse | 1 | 3 | New blog companion topic on “agent-ready” forums — [read more](https://meta.discourse.org/t/-/403594/1?silent=true) | | @david | 1 | 3 | Confirmed direction on mobile/desktop switching and the future of a legacy setting — [read more](https://meta.discourse.org/t/-/384280/11?silent=true) | | @nicolsdennis | 1 | 3 | Clarified scope/availability of a native Discourse client app concept — [read more](https://meta.discourse.org/t/-/403429/6?silent=true) | **Team highlights (by volume):** @zogstrip led team participation (6 posts) with quick links to fixes and PRs, including reactions, chat, flags, and SEO-crawler edge cases مثل [read more](https://meta.discourse.org/t/-/403431/4?silent=true). * * * ## Interesting Topics ### #blog - Discourse published a companion discussion on being **“Agent Ready”** —how AI agents consume forum knowledge and what that implies for communities and publishing strategy ([read more](https://meta.discourse.org/t/-/403594/1?silent=true)). A closely-related thread on provenance/fact mapping continues to orbit the same theme of _how content should be trusted and traced_ in an AI-shaped web ([read more](https://meta.discourse.org/t/-/392842/3?silent=true)). ### #Announcements - “Simple mode” for **Doc Categories** landed, aiming to reduce confusion around posting vs reading in docs-style spaces, after folks reported replying before realizing a doc topic already had a discussion/history ([read more](https://meta.discourse.org/t/-/403366/1?silent=true); example confusion noted here: [read more](https://meta.discourse.org/t/-/403366/2?silent=true); related docs-category context: [read more](https://meta.discourse.org/t/-/64364/37?silent=true)). - The **nested replies** rollout continues to surface UX + translation-adjacent customization needs: one participant suggested language-specific CSS selectors, while @Lilly pointed to a plugin-based approach with translations included ([read more](https://meta.discourse.org/t/-/402812/28?silent=true); CSS suggestion: [read more](https://meta.discourse.org/t/-/402812/28?silent=true); plugin alternative: [read more](https://meta.discourse.org/t/-/402812/29?silent=true); referenced solution thread: [read more](https://meta.discourse.org/t/-/402911/1?silent=true)). ### #development (#dev-news) - On improving automatic **mobile/desktop mode switching** , @Lilly connected a folding/mid-viewport Horizon theme regression to the _viewport-based mobile mode_ setting, and @david noted the setting is “long overdue” for removal because modern design assumes it’s enabled ([read more](https://meta.discourse.org/t/-/384280/10?silent=true); @david follow-up: [read more](https://meta.discourse.org/t/-/384280/11?silent=true); related Horizon viewport bug: [read more](https://meta.discourse.org/t/-/403484/1?silent=true)). ### #General (#show-and-tell) - A native **iOS+Android Discourse client app** preview drew interest; @nicolsdennis clarified it’s not store-published yet, depends on a companion plugin for full functionality on many sites, and shared the “Allowed user API auth redirects” setup needed for login previews ([read more](https://meta.discourse.org/t/-/403429/6?silent=true)). ### #bug - A **nested replies UI glitch on iOS PWA** showed a large gap between username and avatar; once confirmed as an iOS progressive web app, @markvanlan jumped in to investigate ([read more](https://meta.discourse.org/t/-/403532/1?silent=true); platform confirmation: [read more](https://meta.discourse.org/t/-/403532/3?silent=true); team response: [read more](https://meta.discourse.org/t/-/403532/4?silent=true)). - Chat navigation weirdness: the **back button in floating chat** can “forget” state (like starring) due to floating chat interacting with page history; @sam and @zogstrip discussed how this should improve once upstream work merges ([read more](https://meta.discourse.org/t/-/403431/2?silent=true); PR-referenced improvement note: [read more](https://meta.discourse.org/t/-/403431/4?silent=true)). - A “new version available” **email template contained a broken release-notes link** (missing the `v` in the URL); @Lilly prepared a fix proposal, and the reporter confirmed it’s helpful even for local patching ([read more](https://meta.discourse.org/t/-/403389/2?silent=true); reporter follow-up: [read more](https://meta.discourse.org/t/-/403389/3?silent=true)). - Emoji autocomplete struggled with **special characters like `ü`** , and @renato linked a PR expected to fix it ([read more](https://meta.discourse.org/t/-/403420/3?silent=true)). - Reactions UX had two sharp edges this cycle: (1) the **“+1” hover popover** could spin forever because `+` wasn’t URL-encoded, and (2) **mobile back-navigation** with the reactions list open could leave the modal open and jump scroll position. The hover issue was acknowledged as fixed by a PR, while the back-button behavior echoed earlier modal-related reports ([read more](https://meta.discourse.org/t/-/403520/1?silent=true); fix pointer: [read more](https://meta.discourse.org/t/-/403520/2?silent=true); back-button report: [read more](https://meta.discourse.org/t/-/403509/1?silent=true); earlier related modal discussion: [read more](https://meta.discourse.org/t/-/389820/78?silent=true); another related post: [read more](https://meta.discourse.org/t/-/389820/81?silent=true)). ### #Support - A self-hosted backup failing under **Postgres 18** was resolved when @Thomas_Rother installed Postgres packages inside the container/host context; @pfaffman recommended pinning the right client packages and automating in `app.yml` to avoid future surprises ([read more](https://meta.discourse.org/t/-/403289/10?silent=true); follow-up hardening advice: [read more](https://meta.discourse.org/t/-/403289/11?silent=true)). - A report that **one topic’s view counts weren’t incrementing** prompted basic triage questions and a suggestion to try [safe mode](https://meta.discourse.org/t/53504?silent=true) to rule out theme/component interference ([read more](https://meta.discourse.org/t/-/403522/1?silent=true); troubleshooting prompt: [read more](https://meta.discourse.org/t/-/403522/2?silent=true)). - Hosted-plan UX friction continued: questions about **pricing structure changes / free plan feature visibility** got a candid acknowledgement that experimentation is ongoing, plus a promise to raise feature-matrix clarity internally ([read more](https://meta.discourse.org/t/-/403393/5?silent=true)). In a separate upgrade-flow bug, the **Starter plan option appeared missing** due to a recommendation-system edge case around staff limits, with a fix planned ([read more](https://meta.discourse.org/t/-/403167/23?silent=true)). ### #Self-hosting - On whether the `discourse/discourse` Docker image is **production-ready** , @featheredtoast confirmed a patch restored expected builds and upgrades, and that the latest image became available again after the fix ([read more](https://meta.discourse.org/t/-/380646/32?silent=true)). ### #wordpress - WordPress embed users flagged that older embedded topics were missing **`x-robots: noindex` and canonical tags** ; @angus clarified canonical behavior depends on embed records and suggested republishing to recreate missing records, while the OP argued for a native “category-level noindex” control as a broader SEO need ([read more](https://meta.discourse.org/t/-/403109/8?silent=true); follow-up/feature request argument: [read more](https://meta.discourse.org/t/-/403109/9?silent=true)). ### #Enterprise (#enterprise-ready) - A thoughtful thread on **community breaking points as usage grows** continued: @Tris20 described how unmanaged growth can overwhelm specialists and moderation, and shared a tactic of gating new-topic creation behind “read this first” expectations—effective, but not universally loved ([read more](https://meta.discourse.org/t/-/402716/17?silent=true); @HAWK follow-up question: [read more](https://meta.discourse.org/t/-/402716/18?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@zogstrip** was the day’s “fast path to resolution” across multiple threads: pointing to fixes for chat history/state confusion ([read more](https://meta.discourse.org/t/-/403431/4?silent=true)), the reactions “+1” hover encoding bug ([read more](https://meta.discourse.org/t/-/403520/2?silent=true)), a flagged-post restore edge case ([read more](https://meta.discourse.org/t/-/401900/3?silent=true)), plus maintenance/UX improvements like adding missing setting-description links ([read more](https://meta.discourse.org/t/-/403058/2?silent=true)) and addressing crawler pagination issues ([read more](https://meta.discourse.org/t/-/96337/16?silent=true)). - **@david** confirmed product direction on viewport-based device mode switching—calling out that the legacy “disable viewport-based mobile mode” setting is overdue for removal because current design assumes it remains enabled ([read more](https://meta.discourse.org/t/-/384280/11?silent=true)). - **@HAWK** engaged on hosted-plan communications and expectation-setting: acknowledging continued experimentation around plan packaging and committing to bring feature-matrix clarity feedback to the team ([read more](https://meta.discourse.org/t/-/403393/5?silent=true)), and following up on enterprise community-growth process questions ([read more](https://meta.discourse.org/t/-/402716/18?silent=true)). - **@markvanlan** picked up investigation on an iOS PWA nested-replies layout gap report ([read more](https://meta.discourse.org/t/-/403532/4?silent=true)). - **@featheredtoast** confirmed Docker image build availability was restored after a patch, unblocking upgrades for image users ([read more](https://meta.discourse.org/t/-/380646/32?silent=true)). - **@sam** dug into why floating chat and browser history interaction creates confusing “back button” behavior, helping narrow scope (floating vs full-screen) and framing the underlying issue ([read more](https://meta.discourse.org/t/-/403431/2?silent=true)). - **@rishabh** acknowledged and explained why a hosted upgrade flow could incorrectly skip Starter (staff-limit logic), thanked the reporter, and committed to follow up after a fix ([read more](https://meta.discourse.org/t/-/403167/23?silent=true)). - **@renato** linked an in-flight fix for emoji autocomplete failures with non-ASCII characters ([read more](https://meta.discourse.org/t/-/403420/3?silent=true)). - **@supermathie** asked the key diagnostic question (“what was the reason given?”) in a Chinese-language support thread about approval/flag states that appeared confusing in the moderation queue ([read more](https://meta.discourse.org/t/-/403507/2?silent=true)). * * * Yesterday, Discourse got more _agent-ready_ while reactions tried to turn “+1” into “ 1” — at least the fixes landed fast ([read more](https://meta.discourse.org/t/-/403520/2?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: [23.Май.2026 05:02:15 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/842 "2026-05-23T05:02:15Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 91 - **New topics (last 24h):** 12 - Stats are compiled in the same spirit as Meta’s ongoing “daily summary” discussions (see: [Daily Summary Feedback](https://meta.discourse.org/t/-/291853/289?silent=true)). **Top users (posts / likes in the last 24h)** | User | Posts | Likes | Recent highlight | | --- | --- | --- | --- | | **@Moin** | 14 | 10 | Dug into approval/review edge-cases in [Approval button on user’s profile doesn’t work](https://meta.discourse.org/t/-/403620/1?silent=true) and follow-ups in [Notification claims X users for approval, but none are found](https://meta.discourse.org/t/-/262853/17?silent=true) | | **@Lilly** | 13 | 10 | Traced a font-size change to Modernized Foundation in [刚才rebuild更新后，首页字体变的很小](https://meta.discourse.org/t/-/403614/2?silent=true) | | **@awesomerobot** _(team)_ | 3 | 10 | Clarified expectations for the #free-plan inactivity emails in [What is the minimum required activity?](https://meta.discourse.org/t/-/403615/2?silent=true) | | **@supermathie** _(team)_ | 4 | 7 | Explained clipboard format differences for highlighted code in [Syntax highlighting… is not copied](https://meta.discourse.org/t/-/403639/7?silent=true) | | **@darkpixlz** | 4 | 6 | Raised a UX gap in nested replies moderation tooling in [Can’t add note to admin action in threaded view](https://meta.discourse.org/t/-/403660/1?silent=true) | | **@sniper756** | 7 | 3 | Reported the post-rebuild small-font regression in [刚才rebuild更新后，首页字体变的很小](https://meta.discourse.org/t/-/403614/1?silent=true) | | **@Ed_S** | 5 | 3 | Helped narrow down a “phantom approvals”/500s situation in [Notification claims X users…](https://meta.discourse.org/t/-/262853/19?silent=true) | | **@Orioni** | 3 | 4 | Added SEO/AI nuance around #llms-txt skepticism in [Discourse is Agent Ready](https://meta.discourse.org/t/-/403594/6?silent=true) | | **@Canapin** | 1 | 2 | Asked for citations/sourcing in [Discourse is Agent Ready](https://meta.discourse.org/t/-/403594/4?silent=true) | | **@Tris20** | 1 | 3 | Shared enterprise “pre-existing platform baggage” lessons in [What are some common breaking points as communities grow?](https://meta.discourse.org/t/-/402716/19?silent=true) | **More threads worth skimming (high signal / ongoing)** - AI, crawling, and opt-in/out realities: [Discourse is Agent Ready](https://meta.discourse.org/t/-/403594/5?silent=true) (and a practical counterpoint on “blocking isn’t foolproof” in [this reply](https://meta.discourse.org/t/-/403594/8?silent=true)) - Approval notifications + invisible users: [Notification claims X users for approval, but none are found](https://meta.discourse.org/t/-/262853/16?silent=true) plus the new repro report in [Approval button on user’s profile doesn’t work](https://meta.discourse.org/t/-/403620/1?silent=true) - “Solved reminders” + suggested-topics scoping: [Discourse Solved Reminders](https://meta.discourse.org/t/-/327291/23?silent=true) - Topic Voting UI changes (“big Vote button” → smaller control): [Discourse Topic Voting](https://meta.discourse.org/t/-/40121/319?silent=true) - Likes hidden by Voting categories and ways around it: [Discourse Topic Voting](https://meta.discourse.org/t/-/40121/311?silent=true) and the “show both” guide: [read more](https://meta.discourse.org/t/-/101252/2?silent=true) - A docs UX shift and where feedback ended up: [Introducing simple mode for Discourse Doc Categories](https://meta.discourse.org/t/-/403366/3?silent=true), plus the referenced feedback thread: [read more](https://meta.discourse.org/t/-/403003/1?silent=true) - Wiki attribution concerns tied to doc “simple mode”: [“Simple mode” for doc categories in wiki category](https://meta.discourse.org/t/-/403006/2?silent=true) - Release-note email link bug reportedly fixed after merge: [Email with update available has invalid link to release notes](https://meta.discourse.org/t/-/403389/4?silent=true) - Dev environment gotcha (UID 1000) when using `boot_dev`: [Install Discourse for development using Docker](https://meta.discourse.org/t/-/102009/326?silent=true) - A self-hostable helper for “pretty” support URLs: [Discourse Shortlink Router](https://meta.discourse.org/t/-/401542/9?silent=true) - Migration progress report (phpBB importer throughput): [PHPBB to Discourse Migration Speed Optimization](https://meta.discourse.org/t/-/403319/10?silent=true) - A theme-admin CSS fix after class changes: [Preview image for own themes](https://meta.discourse.org/t/-/389978/12?silent=true) - Tag UI nitpick continues: [Slightly enlarge the tag input field…](https://meta.discourse.org/t/-/399588/2?silent=true) - Duplicate report around spoilers inside details (still a known issue): [Duplicate report](https://meta.discourse.org/t/-/403626/1?silent=true) and the original: [read more](https://meta.discourse.org/t/-/194499/6?silent=true) * * * ## Interesting Topics ### #blog - @eisammy challenged the value proposition of “being crawled by AI” (bandwidth, incentives, and legal/privacy concerns), and @awesomerobot framed it as _context-dependent_—helpful for support/knowledge bases, harmful for social communities—in [Discourse is Agent Ready: Here’s How](https://meta.discourse.org/t/-/403594/5?silent=true). Related nuance around #llms-txt skepticism appears in [this reply](https://meta.discourse.org/t/-/403594/6?silent=true), and a “just block them” stance (plus examples) is in [this post](https://meta.discourse.org/t/-/403594/7?silent=true). ### #ux - A rebuild/theme update left category-list “featured topics” looking cramped with smaller text; @Lilly pinned it to Modernized Foundation and offered a CSS workaround in [刚才rebuild更新后，首页字体变的很小](https://meta.discourse.org/t/-/403614/2?silent=true) (#foundation-theme). Confirmations/notes followed in [this post](https://meta.discourse.org/t/-/403614/5?silent=true) and a “cache made it look broken” resolution came later in [this reply](https://meta.discourse.org/t/-/403614/8?silent=true). - Nested/threaded view is missing a control to add notes to admin actions (available in flat view), which @darkpixlz flagged as a workflow regression in [Can’t add note to admin action in threaded view](https://meta.discourse.org/t/-/403660/1?silent=true) (#nested-replies). ### #bug - Copy/paste expectations collided with clipboard reality: @supermathie showed that the Discourse codeblock **copy button** provides plain text, while selecting rendered HTML can preserve formatting—leading to a deeper “is it copy or paste?” investigation—in [Syntax highlighting… is not copied](https://meta.discourse.org/t/-/403639/7?silent=true). The thread ultimately pointed to browser behavior differences, with Firefox not inlining styles like Chromium in [this analysis](https://meta.discourse.org/t/-/403639/11?silent=true). - A serious moderation flow blocker emerged where **Approving a user** from their admin/profile page appears to do nothing / throw a 500; @Moin documented the state mismatch and investigation angle in [Approval button on user’s profile doesn’t work](https://meta.discourse.org/t/-/403620/1?silent=true). This also ties into long-running “phantom approval notifications” reports in [Notification claims X users for approval, but none are found](https://meta.discourse.org/t/-/262853/19?silent=true). - A mobile/PWA composer regression: when iOS text size is set smaller inside the PWA, the **Reply** button can disappear (while Safari works), as reported in [Reply button not visible when composing on iOS PWA](https://meta.discourse.org/t/-/403662/1?silent=true) (#composer #pwa #ios). The report also references a potentially-related older issue: [read more](https://meta.discourse.org/t/-/322220/1?silent=true). - A post-update navigation/admin sequence briefly produced an alarming error page, but loading in a fresh tab “fixed it”; @Falco suggested checking logs in [Bug? forum issues](https://meta.discourse.org/t/-/403672/2?silent=true). The initial report is here: [read more](https://meta.discourse.org/t/-/403672/1?silent=true). ### #Support - Discourse’s #free-plan hosting expectations were clarified: roughly “a couple users and a handful of topics” within ~3 weeks, with staged notices and eventual decommission timing explained by @awesomerobot in [What is the minimum required activity? Is this implementation correct?](https://meta.discourse.org/t/-/403615/2?silent=true). - A nuanced permissions question: should category moderators be able to review flags on _their own posts_, and is there a built-in way to prevent that conflict-of-interest? The discussion starts in [Can category moderators be prevented from reviewing flags on their own posts?](https://meta.discourse.org/t/-/403661/1?silent=true) (#moderation #category-moderators #review-queue), with a related “policy vs technical enforcement” note linked here: [read more](https://meta.discourse.org/t/-/358201/8?silent=true). - iOS Chrome “back” navigation on Meta itself was reported as inconsistent (sometimes returning to an unexpectedly older page), raising compatibility/history concerns in [Chrome浏览器返回键的bug](https://meta.discourse.org/t/-/403608/1?silent=true) (#mobile). A translation clarification came in later here: [read more](https://meta.discourse.org/t/-/403608/3?silent=true). - A “missing Like button” mystery turned out to be expected behavior: in Voting-enabled categories, Likes are suppressed; the diagnosis and pointers (including possible Reactions workaround) are in [请问一下点赞按钮如何显示](https://meta.discourse.org/t/-/403674/5?silent=true). The canonical plugin note is quoted from [Discourse Topic Voting](https://meta.discourse.org/t/-/40121/311?silent=true), and the “show both like & vote” guide is here: [read more](https://meta.discourse.org/t/-/101252/2?silent=true). ### #contribute:feature - A least-privilege request proposes splitting “delete all posts and topics allowed groups” into **own-content** vs **global-content** permissions, to avoid granting moderation-grade powers just to let trusted users better manage their own deletions/revisions: [Split “delete all posts and topics allowed groups”…](https://meta.discourse.org/t/-/403671/1?silent=true) (#moderation #groups #trust-levels #revisions). ### #Announcements - Doc categories “simple mode” continues to generate practical UX questions/feedback, including where to consolidate prior reports and how it affects discoverability of controls—see [Introducing simple mode for Discourse Doc Categories](https://meta.discourse.org/t/-/403366/3?silent=true) (#doc-categories) and the referenced follow-up thread: [read more](https://meta.discourse.org/t/-/403003/1?silent=true). Related site-feedback about attribution impact in #Wiki appears in [this post](https://meta.discourse.org/t/-/403006/2?silent=true). ### #Developer Guides - A dev setup footgun: `./d/boot_dev --init` can effectively assume your host user is UID 1000; @dubwoc shared a detailed failure mode and workaround in [Install Discourse for development using Docker](https://meta.discourse.org/t/-/102009/326?silent=true) (#docker #dev-install). ### #customization:plugin - Voting UI expectations surfaced again after an update: communities used to a large, explicit “Vote” button now see a subtle arrow control; the request to revert/adjust is in [Discourse Topic Voting](https://meta.discourse.org/t/-/40121/319?silent=true) (#topic-voting). This also intersects with “Likes hidden in voting categories” (see: [read more](https://meta.discourse.org/t/-/403674/5?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** engaged in the “AI crawler / incentives” debate, emphasizing that the right choice depends on whether your forum is primarily _support/knowledge_ or _social community_, in [Discourse is Agent Ready](https://meta.discourse.org/t/-/403594/5?silent=true), and added the pragmatic reality that many scrapers ignore robots/IP blocks in [this follow-up](https://meta.discourse.org/t/-/403594/8?silent=true). - **@awesomerobot** also documented the (currently evolving) operational thresholds for free hosted sites—timelines for inactivity notices and decommissioning—in [What is the minimum required activity?](https://meta.discourse.org/t/-/403615/2?silent=true). - **@supermathie** provided a concrete breakdown of _why_ syntax highlighting often won’t paste “with colors” (copy-button clipboard formats vs rendered HTML selection), plus debugging ideas/tools, in [Syntax highlighting… is not copied](https://meta.discourse.org/t/-/403639/7?silent=true) and [this continuation](https://meta.discourse.org/t/-/403639/9?silent=true). - **@supermathie** solved a missing-like-button report by identifying Voting-category suppression and pointing to known ways to re-enable/approximate likes (or use Reactions), in [请问一下点赞按钮如何显示](https://meta.discourse.org/t/-/403674/5?silent=true). - **@techAPJ** confirmed how the “help answer similar questions” PM uses standard suggested-topic logic and respects category-limiting settings, in [Discourse Solved Reminders - suggesting already solved topics](https://meta.discourse.org/t/-/327291/23?silent=true). - **@Falco** responded to a post-update “weird error page” report by directing the reporter to inspect instance logs, in [Bug? forum issues](https://meta.discourse.org/t/-/403672/2?silent=true). * * * Yesterday’s moral: may your fonts be readable, your approval queues non-phantom, and your “Reply” buttons remain stubbornly visible—especially on iOS PWAs. ---
### 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: [24.Май.2026 05:00:49 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/843 "2026-05-24T05:00:49Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 26** - **New topics (last 24h): 6** **Top users (posts / likes in the last 24h)** | User | Posts | Likes | Recent reference | | --- | --- | --- | --- | | @Ethsim2 | 8 | 3 | Reactions serializer error report: [read more](https://meta.discourse.org/t/-/403692/1?silent=true) · Settings wording proposal: [read more](https://meta.discourse.org/t/-/403690/1?silent=true) | | @jack222 | 2 | 1 | Reply-order discussion (CN): [read more](https://meta.discourse.org/t/-/403691/2?silent=true) · iOS/Chrome back issue thread: [read more](https://meta.discourse.org/t/-/403608/4?silent=true) | | @wenqin | 1 | 5 | Cross-cultural UX feedback on reply order: [read more](https://meta.discourse.org/t/-/403691/1?silent=true) | | @mcmcclur | 1 | 4 | KaTeX-rendered topic titles theme component: [read more](https://meta.discourse.org/t/-/403702/1?silent=true) | | @Ryan_Hyer | 1 | 2 | Infinite scroll error with user directory component: [read more](https://meta.discourse.org/t/-/403699/1?silent=true) | | @Lilly | 1 | 1 | Nested replies + post voting compatibility note: [read more](https://meta.discourse.org/t/-/403696/2?silent=true) | | @pfaffman | 1 | 1 | Rebuild advice after update issues: [read more](https://meta.discourse.org/t/-/403672/5?silent=true) | | @Falco _(team)_ | 1 | 1 | Reply-order UX + nested replies pointer: [read more](https://meta.discourse.org/t/-/403691/3?silent=true) | | @dax _(team)_ | 1 | 1 | Guidance on keeping Meta focused (trial sites/testing): [read more](https://meta.discourse.org/t/-/403511/8?silent=true) | | @darkpixlz | 1 | 1 | Translation/communication clarification in back-button thread: [read more](https://meta.discourse.org/t/-/403608/6?silent=true) | * * * ## Interesting Topics ### #contribute:feature - @wenqin shared cross-cultural + generational usability feedback and asked for an **admin-selectable default reply order** (oldest-first vs newest-first), noting discoverability issues around the timeline/progress UI for older users; @Falco replied that the timeline is a single click/tap and pointed to how **nested replies** changes the reading flow ([read more](https://meta.discourse.org/t/-/403691/1?silent=true), [read more](https://meta.discourse.org/t/-/403691/3?silent=true), plus nested replies context: [read more](https://meta.discourse.org/t/-/398759/117?silent=true)) - A parallel permissions discussion continued around splitting “delete all posts and topics allowed groups” into more precise capabilities (own-content vs global-content), with deep dives into `PostGuardian` checks and what should/shouldn’t become visible to non-staff ([read more](https://meta.discourse.org/t/-/403671/2?silent=true), [read more](https://meta.discourse.org/t/-/403671/3?silent=true), [read more](https://meta.discourse.org/t/-/403671/4?silent=true)) ### #ux - @Ethsim2 proposed clearer wording for the `delete_removed_posts_after` setting to better distinguish _author removal_ vs _later cleanup deletion_, and to clarify what staff vs regular users can see during the retention window ([read more](https://meta.discourse.org/t/-/403690/1?silent=true), background thread: [read more](https://meta.discourse.org/t/-/403671/2?silent=true)) ### #customization:theme component - @mcmcclur released a theme component to typeset **KaTeX in topic titles** , acknowledging Discourse’s general avoidance of rich formatting in titles while providing a practical option for math-heavy communities ([read more](https://meta.discourse.org/t/-/403702/1?silent=true); related prior request: [read more](https://meta.discourse.org/t/-/143762/1?silent=true), and staff stance quoted there: [read more](https://meta.discourse.org/t/-/143762/2?silent=true)) - The long-running “Indented Subcategories” theme component thread saw fresh activity (a post was removed by its author), a reminder that even mature components still get maintenance/cleanup moments ([read more](https://meta.discourse.org/t/-/393838/15?silent=true)) ### #Support - A debugging thread on an iOS **Chrome back-button bug** (tagged #mobile) homed in on language/translation factors: @NateDhaliwal asked whether it only occurs when the interface language isn’t English, and later replies suggested it may actually be **Chrome’s page translation** interacting with Discourse navigation/history state ([read more](https://meta.discourse.org/t/-/403608/5?silent=true), [read more](https://meta.discourse.org/t/-/403608/6?silent=true), [read more](https://meta.discourse.org/t/-/403608/7?silent=true)) ### #bug - A theme component conflict: enabling a user directory/user card component (tagged #user-card-directory) reportedly breaks infinite scroll with `this.model is undefined` / `loadMore` errors, preventing loading past the first page of users ([read more](https://meta.discourse.org/t/-/403699/1?silent=true)) - After an “update all,” one admin saw a mix of errors: apparent **stale-tab asset issues** (Propshaft missing chunk JS) plus a separate **reactions-related backend NameError** ; the thread suggested rebuilding from the command line and separating “old tab” fallout from real runtime regressions ([read more](https://meta.discourse.org/t/-/403672/4?silent=true), [read more](https://meta.discourse.org/t/-/403672/5?silent=true), and the linked reactions error report: [read more](https://meta.discourse.org/t/-/403692/1?silent=true)) - A new regression report: `NameError (uninitialized constant ReactionsSerializerHelpers)` when loading topic posts (tagged #reactions), with @Ethsim2 also linking a fix via PR and narrowing the failing load/constant initialization order ([read more](https://meta.discourse.org/t/-/403692/1?silent=true), [read more](https://meta.discourse.org/t/-/403692/2?silent=true)) - Compatibility edge case: enabling **nested replies** and **post voting** together (tags #nested-replies + #post-voting) and converting a post to nested view triggered a 500 error (`undefined method 'post_number' for nil`), with early suspicion that the features aren’t compatible _yet_ ([read more](https://meta.discourse.org/t/-/403696/1?silent=true), [read more](https://meta.discourse.org/t/-/403696/2?silent=true), plus the nested replies intro reference: [read more](https://meta.discourse.org/t/-/402812/27?silent=true)) - An “Approval button on user’s profile” bug investigation continued, including a striking scenario where an old deleted/spam account’s history appears to have influenced a new user who later received the same numeric ID, echoing an older Meta report about deleted user info leaking into approvals ([read more](https://meta.discourse.org/t/-/403620/6?silent=true), [read more](https://meta.discourse.org/t/-/403620/7?silent=true), older related report: [read more](https://meta.discourse.org/t/-/161720/1?silent=true)) ### #Nested Replies Testing - In ongoing nested replies experiments, participants asked about **disabling machine translation UI** (e.g., missing the “文A” button in nested mode) and how to “catch everyone’s attention” in threaded contexts when you need to redirect a conversation ([read more](https://meta.discourse.org/t/-/398759/117?silent=true), [read more](https://meta.discourse.org/t/-/398759/118?silent=true)) ### #community-building Building - In a “new community” thread, @dax clarified that Meta isn’t the right place to run functional tests or promote trial sites, recommended using the official demo environment, and asked users to avoid unsolicited PM outreach for testing workflows ([read more](https://meta.discourse.org/t/-/403511/8?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco responded to the reply-order/cultural UX feedback by pointing out the existing timeline/scroll affordances and highlighted that the **nested replies** feature is designed for alternative reading flows ([read more](https://meta.discourse.org/t/-/403691/3?silent=true); nested replies testing context: [read more](https://meta.discourse.org/t/-/398759/117?silent=true)). - @dax posted a moderation/community-process clarification reminding folks to keep Meta focused on support and discussion (not external testing/promotion), and directed experimentation to the official demo site ([read more](https://meta.discourse.org/t/-/403511/8?silent=true)). * * * If yesterday was any indication, tomorrow will involve at least one more deep scroll, one more tricky serializer constant, and at least one beautifully rendered KaTeX title. ---
### 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: [25.Май.2026 05:02:08 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/844 "2026-05-25T05:02:08Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 39** - **New topics (last 24h): 7** ### Top contributors (posts / likes) - **@Moin** — **8 posts** , **9 likes** (e.g. digging into education-banner logic: [read more](https://meta.discourse.org/t/-/403727/1?silent=true); plus user-approval “phantom counts” triage: [read more](https://meta.discourse.org/t/-/403731/2?silent=true)) - **@Lilly** — **4 posts** , **7 likes** (launched an admin QoL theme component: [read more](https://meta.discourse.org/t/-/403729/1?silent=true); reported a docs UI overlap: [read more](https://meta.discourse.org/t/-/403721/1?silent=true)) - **@RGJ** — **2 posts** , **6 likes** (pointed out nested-replies navigation gotchas in reply-order discussions: [read more](https://meta.discourse.org/t/-/403691/8?silent=true); resurfaced a long-standing approvals-notification issue: [read more](https://meta.discourse.org/t/-/262853/27?silent=true)) - **@Ed_S** — **2 posts** , **2 likes** (pushed on _discoverability_ vs “just do X”: [read more](https://meta.discourse.org/t/-/403691/6?silent=true)) - **@haydenjames** — **2 posts** , **2 likes** (flagged surprise settings changes after upgrades: [read more](https://meta.discourse.org/t/-/383691/20?silent=true)) - **@Falco** _(team)_ — **2 posts** , **2 likes** (nested replies + timeline iteration notes: [read more](https://meta.discourse.org/t/-/403691/9?silent=true)) - **@Eviepayne** — **1 post** , **3 likes** (suggested shipping Anubis CAPTCHA support alongside “agent ready”: [read more](https://meta.discourse.org/t/-/403594/10?silent=true)) - **@ted** — **1 post** , **3 likes** (copyright / regulation skepticism on LLM scraping: [read more](https://meta.discourse.org/t/-/403594/9?silent=true)) - **@fitzy** _(team)_ — **1 post** , **2 likes** (confirmed the NGINX CVE fix is completed: [read more](https://meta.discourse.org/t/-/403121/6?silent=true)) - **@nobrowser** — **1 post** , **2 likes** (keyboard/timeline “jump” perspective in reply-order UX: [read more](https://meta.discourse.org/t/-/403691/4?silent=true)) ### New topics opened (7) - Admin UI noise reducer: **“Dismiss Admin Noise!”** [read more](https://meta.discourse.org/t/-/403729/1?silent=true) - Wiki/docs banner overlap report: [read more](https://meta.discourse.org/t/-/403721/1?silent=true) - Invite notifications question: [read more](https://meta.discourse.org/t/-/403724/1?silent=true) - Education banner behavior after recent changes: [read more](https://meta.discourse.org/t/-/403727/1?silent=true) - Reverse proxy + separate host config help: [read more](https://meta.discourse.org/t/-/403720/1?silent=true) - “Phantom” outstanding approvals reminder: [read more](https://meta.discourse.org/t/-/403731/1?silent=true) - Local logins disabled (social-only auth) question: [read more](https://meta.discourse.org/t/-/403735/1?silent=true) * * * ## Interesting Topics ### #contribute:feature - Older-user usability and cross-cultural expectations sparked a debate about reply order, _discoverability_, and navigation affordances in **“Cross-cultural feedback on topic reply order and usability for older users”** ([read more](https://meta.discourse.org/t/-/403691/1?silent=true)). @Ed_S argued that “just do this” doesn’t solve the _discoverability_ problem ([read more](https://meta.discourse.org/t/-/403691/6?silent=true)), while @RGJ highlighted that nested replies complicate the usual timeline affordance ([read more](https://meta.discourse.org/t/-/403691/8?silent=true)). @Falco shared that a timeline for nested replies briefly shipped and was reverted while the team explores a better design ([read more](https://meta.discourse.org/t/-/403691/9?silent=true)). _Related:_ nested-replies testing thread: [read more](https://meta.discourse.org/t/-/398759/1?silent=true) ### #blog - The conversation around **“Discourse is Agent Ready: Here’s How”** expanded into AI-era risk management: @ted questioned whether regulation will meaningfully constrain LLM training on copyrighted content ([read more](https://meta.discourse.org/t/-/403594/9?silent=true)), while @Eviepayne proposed making **Anubis** a supported CAPTCHA option as part of the same push ([read more](https://meta.discourse.org/t/-/403594/10?silent=true)). _Related:_ “agent ready” discussion hub: [read more](https://meta.discourse.org/t/-/403594/1?silent=true) ### #Community\_Building (#automation) - In **“Sharing approaches to using automation to send messages to members”** ([read more](https://meta.discourse.org/t/-/383691/1?silent=true)), admins compared notes on using automation to reduce mod toil and steer behavior—especially as AI-generated posts change site tone. @haydenjames also raised frustration about settings being silently toggled by updates ([read more](https://meta.discourse.org/t/-/383691/20?silent=true)), and @Moin linked proposals to log update-driven setting changes ([read more](https://meta.discourse.org/t/-/383705/1?silent=true)) and to build notifications when system settings change ([read more](https://meta.discourse.org/t/-/208961/11?silent=true)). _Related:_ staff-action logging proposal: [read more](https://meta.discourse.org/t/-/383705/1?silent=true) ### #Theme\_component (#notifications) - **“Dismiss Admin Noise!”** shipped as a lightweight theme component to auto-dismiss selected admin notifications in the user menu ([read more](https://meta.discourse.org/t/-/403729/1?silent=true)), with install guidance pointing back to the standard theme install how-to ([read more](https://meta.discourse.org/t/-/63682/1?silent=true)). It also immediately became a practical answer for people annoyed by specific notification types (like invite acceptances) ([read more](https://meta.discourse.org/t/-/403724/3?silent=true)). - The long-running **“Unformatted Code Detector”** thread saw a brief troubleshooting detour when a user hit a “cannot clone repository” error ([read more](https://meta.discourse.org/t/-/112773/67?silent=true)). @Moin suggested checking the component’s source link and retrying updates ([read more](https://meta.discourse.org/t/-/112773/68?silent=true)), noting it may be transient GitHub rate limiting (with a pointer to a broader “error cloning” discussion) ([read more](https://meta.discourse.org/t/-/399003/6?silent=true)). ### #bug - A nine-year-old papercut returned to the spotlight in **“Notification claims X users for approval, but none are found”** ([read more](https://meta.discourse.org/t/-/262853/27?silent=true)), with @RGJ calling out that the cause appears well-understood yet unresolved. - In **“Approval button on user’s profile doesn’t work”** ([read more](https://meta.discourse.org/t/-/403620/1?silent=true)), @Moin shared database evidence suggesting the problematic `ReviewableUser` record was created _after_ the user account ([read more](https://meta.discourse.org/t/-/403620/8?silent=true)), and @Ed_S hypothesized mismatched targets / invalid reviewable state and listed multiple failure modes (exceptions, missing queue entries, silent migration issues) ([read more](https://meta.discourse.org/t/-/403620/9?silent=true)). ### #ux - **“Pending suggested edit notification overlaps the edit history and date”** reported a UI overlap on wiki/doc pages ([read more](https://meta.discourse.org/t/-/403721/1?silent=true)), with suspicion it may relate to doc-category “simple mode” styling changes ([read more](https://meta.discourse.org/t/-/403721/2?silent=true)). _Related:_ “Discourse suggested edits” tagging/meta thread: [read more](https://meta.discourse.org/t/-/398691/1?silent=true) and “Introducing simple mode for Discourse Doc Categories” overlap evidence: [read more](https://meta.discourse.org/t/-/403366/4?silent=true) ### #Support - **NGINX CVE-2026-42945** mitigation landed: @fitzy confirmed the base image and default image bumps are complete in **“Nginx CVE-2026-42945”** ([read more](https://meta.discourse.org/t/-/403121/6?silent=true)). - **“Turn off invite accepted notifications?”** reaffirmed there’s no built-in toggle yet ([read more](https://meta.discourse.org/t/-/403724/2?silent=true)); responders pointed to an older feature request ([read more](https://meta.discourse.org/t/-/150633/1?silent=true)) and suggested operational workarounds—then @Lilly cheekily offered **Dismiss Admin Noise** as a pragmatic mitigation ([read more](https://meta.discourse.org/t/-/403724/3?silent=true)). - **“How does `educate_until_posts` interact with the recent changes to `check_education_message`?”** dug into expectations vs actual banner behavior for new users ([read more](https://meta.discourse.org/t/-/403727/1?silent=true)), explicitly continuing from a “Thanks for Contributing” popup thread ([read more](https://meta.discourse.org/t/-/373048/24?silent=true)). - **“System permanently thinks there are user approvals outstanding”** described years-long “phantom approvals” reminders ([read more](https://meta.discourse.org/t/-/403731/1?silent=true)). @Moin pointed to the `pending users reminder delay minutes` setting for reminder frequency control and connected the symptoms to known approval-notification bugs ([read more](https://meta.discourse.org/t/-/403731/2?silent=true)), including older-user triggers ([read more](https://meta.discourse.org/t/-/240731/4?silent=true)). - **“If local logins are disabled”** asked for real-world experiences running social-login-only while SMTP is broken ([read more](https://meta.discourse.org/t/-/403735/1?silent=true)). ### #Self-hosting (#nginx) - In **“Config help when reverse proxy and discourse on seperate computers”** , a self-hoster asked how to translate the “unix socket” `proxy_pass` approach into an IP-based upstream and what ports/expose settings to use when the proxy and Discourse aren’t co-located ([read more](https://meta.discourse.org/t/-/403720/1?silent=true)). ### #Integrations (#embedding) - The evergreen **“Embed Discourse comments on another website via Javascript”** thread got a mobile-app angle: @benji asked whether embedding can be used to import “just the comments” experience into an app ([read more](https://meta.discourse.org/t/-/31963/486?silent=true)), and @Falco clarified that the basic embed is read-only and works well for a webview-based comments list, inviting more details on the use case ([read more](https://meta.discourse.org/t/-/31963/487?silent=true)). ### #Announcements (#nested-replies) - **“Introducing nested replies”** continued to draw product-level skepticism and curiosity: a commenter questioned whether nesting truly solves “too many replies to keep up,” and suggested it may increase cognitive load even as it adds choice ([read more](https://meta.discourse.org/t/-/402812/30?silent=true)). ### #support:migration (#phpbb) - A practical “oops” moment in **“PHPBB to Discourse Migration Speed Optimization”** : after completing a run, @Mattash realized passwords weren’t imported and planned a restart—this time pruning low-value content to speed things up ([read more](https://meta.discourse.org/t/-/403319/11?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@fitzy** wrapped up the operational side of the **NGINX CVE-2026-42945** work, confirming the upgraded images are shipped and pointing to the underlying Docker image updates ([read more](https://meta.discourse.org/t/-/403121/6?silent=true)). - **@Falco** contributed to two active product/implementation discussions: * * * _Yesterday was a day of phantom approvals, nested timelines, and admins begging for fewer pings—may today’s Meta be quieter, clearer, and one click closer to the right reply._ ---
### 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: [26.Май.2026 05:01:58 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/845 "2026-05-26T05:01:58Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours (2026-05-25 → 2026-05-26), Meta saw **47 new posts** across **8 new topics**. (Highlights include new discussions in [#Announcements](https://meta.discourse.org/t/-/403795/1?silent=true), [#contribute:bug](https://meta.discourse.org/t/-/403743/1?silent=true), [#contribute:ux](https://meta.discourse.org/t/-/403741/1?silent=true), and [#Site feedback](https://meta.discourse.org/t/-/403798/1?silent=true).) **Top contributors (posts / likes received):** | User | Posts | Likes | | --- | --- | --- | | @Moin | 6 | 12 | | @darkpixlz | 6 | 3 | | @Jagster | 3 | 3 | | @Falco | 2 | 4 | | @martin | 2 | 3 | | @haydenjames | 2 | 2 | | @ToddZ | 1 | 6 | | @dax | 1 | 5 | | @RGJ | 1 | 2 | | @manuel | 1 | 2 | > Several threads converged on “small UX papercuts that feel big,” from suggested-topic links that 404 to admin notification overload. See: [nested link issue](https://meta.discourse.org/t/-/403743/1?silent=true), [admin noise theme component](https://meta.discourse.org/t/-/403729/2?silent=true), and [featured component installs](https://meta.discourse.org/t/-/403741/1?silent=true). * * * ## Interesting Topics ### #Announcements - @martin announced an upcoming change to **enable Discourse Reactions by default** on new and existing sites, with admins still able to disable them if desired ([read more](https://meta.discourse.org/t/-/403795/1?silent=true)). The follow-up also touched on longer-term thinking around “likes vs reactions vs boosts” ([read more](https://meta.discourse.org/t/-/403795/3?silent=true)). - Ongoing discussion continued on **client-side image optimizations** , including questions about broader WebP usage for conversions and compression, and tradeoffs around exposing many new settings ([read more](https://meta.discourse.org/t/-/402705/2?silent=true), [Falco’s reply](https://meta.discourse.org/t/-/402705/3?silent=true)). ### #bug - @Moin reported that a **suggested topic link to a nested reply** can break navigation (including a header that stays wrong after returning home), with console output showing a failing nested route JSON request ([read more](https://meta.discourse.org/t/-/403743/1?silent=true), [console details](https://meta.discourse.org/t/-/403743/3?silent=true)). @Falco noted it looks like an issue in `nested.js` ([read more](https://meta.discourse.org/t/-/403743/5?silent=true)). - A self-hoster hit repeated `can't alloc thread` job exceptions after upgrading to **2026.4.1** , and @sam zeroed in on likely host resource / platform constraints and verifying Docker/OS/image currency ([read more](https://meta.discourse.org/t/-/403784/1?silent=true), [sam asks about RAM](https://meta.discourse.org/t/-/403784/2?silent=true), [upgrade follow-up](https://meta.discourse.org/t/-/403784/4?silent=true)). - Another self-hosting error report flagged `NameError: uninitialized constant ReactionsSerializerHelpers` while loading topic posts on **2026.5.0-latest.1** , with extra context about container timezone configuration ([read more](https://meta.discourse.org/t/-/403692/3?silent=true), referenced: [set timezone for docker container](https://meta.discourse.org/t/-/244190/2?silent=true)). ### #ux - A new thread asked why **Featured components** can suggest installing theme components you already have—sometimes inconsistently—and whether duplicates should be hidden or marked. @dax clarified duplicates can be intentional when testing or applying different configs across themes ([read more](https://meta.discourse.org/t/-/403741/1?silent=true), [dax explains rationale](https://meta.discourse.org/t/-/403741/3?silent=true), [consistency concern](https://meta.discourse.org/t/-/403741/4?silent=true)). - In a longer-running UX thread about group visibility, @copymonopoly pointed out that even if **trust level groups** are hidden from the groups list, TL membership is still effectively visible via badge grant histories ([read more](https://meta.discourse.org/t/-/389652/5?silent=true)). ### #Marketplace (#meta-theme-feedback #meta-redesign-2026) - Someone asked what it would cost to **copy Meta’s branded theme** ; community replies emphasized the design isn’t open source, estimated commissioning a comparable theme, and @manuel suggested recreating similar homepage blocks using available theming/block skills material ([read more](https://meta.discourse.org/t/-/403747/1?silent=true), [cost/exclusivity perspective](https://meta.discourse.org/t/-/403747/3?silent=true), [manuel’s pointer](https://meta.discourse.org/t/-/403747/4?silent=true), referenced: [Skills for authoring themes and blocks](https://meta.discourse.org/t/-/401629/1?silent=true)). ### #Site feedback - @darkpixlz reported that **wiki posts** appear to hide user info similarly to doc-simple-mode, which feels wrong for wiki contexts; the thread quickly connected it to “simple mode” behavior and spun off a userstyle workaround ([read more](https://meta.discourse.org/t/-/403798/1?silent=true), [simple mode pointer](https://meta.discourse.org/t/-/403798/2?silent=true), related: [“Simple mode” for doc categories in wiki category](https://meta.discourse.org/t/-/403006/3?silent=true)). - In the collaborative “content gardening hub” experiment, @Moin shared a recurring maintenance gotcha: edits to official plugin/theme topics can break **category mention blocks** due to Meta’s updated category structure, and the mentions often need refreshing after edits ([read more](https://meta.discourse.org/t/-/397606/99?silent=true)). ### #Support - A feature request asked for a **public (unauthenticated) ActivityPub handle list** for federated categories, since the current admin endpoint is restricted ([read more](https://meta.discourse.org/t/-/403769/1?silent=true)). - A self-hosting admin asked about running with **local logins disabled** , especially when SMTP is blocked (e.g. on DigitalOcean). Replies covered using social logins, Discourse ID, and the `enable local logins` site setting; troubleshooting snippets for Resend/Mailgun configuration were also shared ([read more](https://meta.discourse.org/t/-/403735/2?silent=true), [disable local logins setting](https://meta.discourse.org/t/-/403735/4?silent=true), [config examples](https://meta.discourse.org/t/-/403735/5?silent=true), referenced: [Configure Mailgun for email when using DigitalOcean for DNS](https://meta.discourse.org/t/-/40590/1?silent=true), [How Discourse ID works](https://meta.discourse.org/t/-/379565/1?silent=true)). - A “permanent user approvals outstanding” issue was resolved by exporting users and manually approving the few lingering `approved=false` accounts, closing out the phantom approval indicator ([read more](https://meta.discourse.org/t/-/403731/3?silent=true), referenced: [related approval-notification thread](https://meta.discourse.org/t/-/262853/21?silent=true)). ### #Self-hosting - A Chinese-language self-hosting thread noted that after recent rebuild updates, the Discourse container image size appeared to drop (e.g. ~7GB to ~5GB), inviting others to compare observations ([read more](https://meta.discourse.org/t/-/403758/1?silent=true)). ### #support:migration - During a phpBB migration optimization discussion, @cocococosti reminded folks that Discourse migrations **do not import passwords** (and recommended not attempting to), instead guiding users through password reset post-migration ([read more](https://meta.discourse.org/t/-/403319/12?silent=true)). ### #customization:theme component (#notifications) - Feedback on **“Dismiss Admin Noise!”** highlighted how certain admin notifications (like invite acceptances) can overwhelm the dropdown notification list; the thread also shared Rails-console snippets to generate specific notification types for testing component settings ([read more](https://meta.discourse.org/t/-/403729/2?silent=true), [testing via rails console](https://meta.discourse.org/t/-/403729/3?silent=true)). Related support context: [turn off invite accepted notifications?](https://meta.discourse.org/t/-/403724/4?silent=true). _(Extra background threads referenced in today’s discussions: [Discourse Reactions feature topic](https://meta.discourse.org/t/-/183261/1?silent=true), [testing nested replies on Meta](https://meta.discourse.org/t/-/398759/113?silent=true), [contributing translations to Discourse](https://meta.discourse.org/t/-/14882/1?silent=true), and the long-running [Discourse Calendar (and Event)](https://meta.discourse.org/t/-/97376/581?silent=true) translation note.)_ * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @dax chimed in on the UX report about duplicate installs in the Featured Components flow, clarifying that allowing duplicates was an **intentional design choice** to support multiple theme configs and testing workflows ([read more](https://meta.discourse.org/t/-/403741/3?silent=true)). - @Falco participated in two threads: they flagged a likely code location for the nested-replies suggested-topics breakage ([read more](https://meta.discourse.org/t/-/403743/5?silent=true)), and explained tradeoffs in the image optimization rollout—especially the cost of introducing many fine-grained compression settings—even while noting ideal future directions ([read more](https://meta.discourse.org/t/-/402705/3?silent=true)). - @martin announced the upcoming “ **Reactions enabled by default** ” rollout and answered follow-ups about future consolidation of likes/reactions/boosts (no timeline yet) ([read more](https://meta.discourse.org/t/-/403795/1?silent=true), [follow-up](https://meta.discourse.org/t/-/403795/3?silent=true)). - @manuel responded to the Marketplace request about copying Meta’s branded theme, reiterating brand-language constraints and pointing to practical building blocks for achieving similar components via official theming guidance ([read more](https://meta.discourse.org/t/-/403747/4?silent=true), referenced: [Skills for authoring themes and blocks](https://meta.discourse.org/t/-/401629/1?silent=true)). - @HAWK contributed to the enterprise discussion on community scaling “breaking points,” advising that growth strategies should explicitly support subgroup fragmentation and semi-autonomous operation ([read more](https://meta.discourse.org/t/-/402716/21?silent=true)). - @sam helped triage the self-hosting error `can't alloc thread` after an upgrade, focusing on host constraints and ensuring Docker/OS/image layers are fully up to date ([read more](https://meta.discourse.org/t/-/403784/2?silent=true), [follow-up](https://meta.discourse.org/t/-/403784/4?silent=true)). - @cocococosti advised in the phpBB migration optimization thread that password import is not supported (and shouldn’t be attempted), recommending the standard reset-password flow post-migration ([read more](https://meta.discourse.org/t/-/403319/12?silent=true)). Yesterday’s vibe: may your **suggested-topic links not 404** , your **theme components be intentionally duplicated** , and your **reactions roll out smoothly** —all at the same 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: [27.Май.2026 05:02:26 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/846 "2026-05-27T05:02:26Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **Last 24 hours (2026-05-26 → 2026-05-27)** - **New posts:** 91 - **New topics:** 7 **Top users (posts + likes received in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @Lilly | 8 | 11 | | @markvanlan | 4 | 9 | | @rishabh | 1 | 6 | | @zogstrip | 3 | 6 | | @HAWK | 2 | 5 | | @Falco | 3 | 5 | | @NateDhaliwal | 5 | 5 | | @awesomerobot | 1 | 4 | | @RGJ | 1 | 4 | | @david | 2 | 4 | * * * ## Interesting Topics ### #Announcements - The “live status” era arrived for GitHub PR oneboxes: @rishabh announced **inline PR status support** so you can see checks/state directly inside the onebox preview ([read more](https://meta.discourse.org/t/-/390900/21?silent=true)). - Discourse is preparing to **enable Reactions by default** for new _and existing_ sites, with @martin explaining how upcoming rollout mechanics make this safer and easier to opt out of ([read more](https://meta.discourse.org/t/-/403795/5?silent=true)). Related: the canonical Reactions feature thread is here ([read more](https://meta.discourse.org/t/-/183261/1?silent=true)). - The new “shared issue” / “me too” Solved improvement sparked UX and community-safety feedback: a report highlighted how **“me too” can feel loaded** in some communities, and discussion followed on customizing the label and whether it discourages detailed reports ([read more](https://meta.discourse.org/t/-/402498/34?silent=true)). ### #bug - #nested-replies + #post-voting collided: @markvanlan suggested making post voting explicitly incompatible with nested replies (at least for now), and linked work toward disabling post voting on nested topics to prevent further edge cases ([read more](https://meta.discourse.org/t/-/403696/4?silent=true)). - Another #nested-replies issue: **suggested-topic links** pointing at nested topics were broken, with a fix linked by @markvanlan ([read more](https://meta.discourse.org/t/-/403743/6?silent=true)). - Infinite scroll in the #user-card-directory experience was failing with a `loadMore` error; @awesomerobot confirmed a fix was applied and pointed to the patch ([read more](https://meta.discourse.org/t/-/403699/3?silent=true)). - Admin workflows hit friction: the **approval button on a user profile** wasn’t working in some cases, and @zogstrip shared a PR intended to catch more of the raised edge cases ([read more](https://meta.discourse.org/t/-/403620/10?silent=true)). Related historical context on approval notifications: ([read more](https://meta.discourse.org/t/-/262853/28?silent=true)) and a prior “must approve users” edge case reference ([read more](https://meta.discourse.org/t/-/240731/4?silent=true)). - A recurring production error report resurfaced: “ **Document tree depth limit exceeded** ” in crawler middleware, reported as still happening after multiple prior fixes ([read more](https://meta.discourse.org/t/-/403831/1?silent=true)). (Earlier related report thread referenced by the reporter: [read more](https://meta.discourse.org/t/-/402426/1?silent=true)). - AI localization snag: **markdown quotes (`>`) sometimes convert to `0`** in AI translations (examples provided for two model families), raising concerns for formatting fidelity in translated content ([read more](https://meta.discourse.org/t/-/403874/1?silent=true)). ### #Support - A self-hosting mail setup got derailed by real-world constraints: DigitalOcean SMTP port blocking, Sidekiq email failures, and a subtle-but-deadly config detail (curly quotes in YAML) all surfaced in a troubleshooting thread that also recommends running `rake emails:test` to reveal immediate errors ([read more](https://meta.discourse.org/t/-/403735/7?silent=true)). Related guide: troubleshooting email on new installs ([read more](https://meta.discourse.org/t/-/16326/1?silent=true)). - A user asked if they can **opt out of the leaderboard** , and the answer remains: not as an individual (admins can use workarounds), so the practical advice is to avoid the leaderboard page ([read more](https://meta.discourse.org/t/-/403888/4?silent=true)). - Browser support reality-check: a thread on UXP forks (e.g. Pale Moon) prompted troubleshooting suggestions—@david noted the dev console should show which JS/CSS feature detections fail ([read more](https://meta.discourse.org/t/-/403890/5?silent=true)). Prior related discussion: Discourse + Pale Moon incompatibility ([read more](https://meta.discourse.org/t/-/381077/1?silent=true)), plus an “old browser friendly UI” option via Dumbcourse ([read more](https://meta.discourse.org/t/-/395104/1?silent=true)). ### #contribute:feature - A proposal asked for **webhook/event support for Discourse AI artifact updates** (to avoid polling and enable automation pipelines like n8n). @Falco suggested revisiting after the upcoming Workflows work lands, while agreeing the server-side webhook idea is appealing ([read more](https://meta.discourse.org/t/-/403865/2?silent=true)). @sam also endorsed the idea—especially if it can scope by artifact id ([read more](https://meta.discourse.org/t/-/403865/4?silent=true)). ### #development - Mobile/desktop mode logic keeps evolving: @david confirmed **legacy mobile mode has been removed** , and downstream theme/component authors are now seeing deprecations warning against checking viewport mode during site initialization ([read more](https://meta.discourse.org/t/-/384280/12?silent=true)). Related: MD Topic List Mobile component testing and the deprecation note ([read more](https://meta.discourse.org/t/-/146341/69?silent=true)), plus the deprecation reference topic linked in the warning output ([read more](https://meta.discourse.org/t/-/367810/1?silent=true)). ### #community-building:praise - A detailed Discourse success story shared how a team moved from Trello sprawl to a **multi-site Discourse setup** , testing hardware limits and highlighting how Discourse scaled for a larger moderator group and workflows ([read more](https://meta.discourse.org/t/-/403869/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @rishabh shipped a polished product win by announcing **PR status support inside GitHub oneboxes** ([read more](https://meta.discourse.org/t/-/390900/21?silent=true)). - @martin clarified the rationale and safer rollout mechanics behind **enabling Reactions by default** across new/existing sites ([read more](https://meta.discourse.org/t/-/403795/5?silent=true)). - @markvanlan focused on #nested-replies compatibility, proposing defensive behavior for #post-voting when nesting is enabled and linking fixes/PRs ([read more](https://meta.discourse.org/t/-/403696/4?silent=true); [read more](https://meta.discourse.org/t/-/403743/6?silent=true)). - @Falco weighed in on future automation direction for AI artifacts (with Workflows as the likely “revisit point”) ([read more](https://meta.discourse.org/t/-/403865/2?silent=true)), and also guided embedding discussion toward the “full comment system” approach ([read more](https://meta.discourse.org/t/-/31963/489?silent=true)). - @sam endorsed server-side webhook support for AI artifacts—especially scoping events by artifact id—and flagged maintenance needs on a Zulip integration PR (rebase needed) ([read more](https://meta.discourse.org/t/-/403865/4?silent=true); [read more](https://meta.discourse.org/t/-/398789/2?silent=true)). - @zogstrip delivered multiple moderation/admin fixes: shoring up profile approval edge cases ([read more](https://meta.discourse.org/t/-/403620/10?silent=true)) and continuing the theme of tightening approval/notification behavior ([read more](https://meta.discourse.org/t/-/262853/28?silent=true)). - @awesomerobot confirmed a fix for the **user-card-directory infinite scroll** regression ([read more](https://meta.discourse.org/t/-/403699/3?silent=true)). - @david continued the platform cleanup by confirming **legacy mobile mode removal** ([read more](https://meta.discourse.org/t/-/384280/12?silent=true)) and provided a practical debugging pointer for unsupported browsers via feature-detection failures in devtools ([read more](https://meta.discourse.org/t/-/403890/5?silent=true)). - @Bas responded on billing/analytics wording confusion around “site traffic” reporting and pageview-model transitions, inviting follow-up to switch plans if desired ([read more](https://meta.discourse.org/t/-/402288/9?silent=true)). - @lindsey highlighted that the “shared issue” Solved button label is **customizable via Site Text** (`shared_issue`), which is especially relevant given community feedback about the default phrasing ([read more](https://meta.discourse.org/t/-/402498/36?silent=true)). - @HAWK addressed leaderboard concerns by confirming individuals can’t opt out directly (beyond admin workarounds), recommending simply avoiding that page ([read more](https://meta.discourse.org/t/-/403888/4?silent=true)). * * * Between the new _“PR status oneboxes”_ ([read more](https://meta.discourse.org/t/-/390900/21?silent=true)) and the spirited debate over the _“me too / shared issue”_ label in Solved UI ([read more](https://meta.discourse.org/t/-/402498/34?silent=true)), yesterday basically proved that even tiny buttons can generate big momentum. ---
### 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: [28.Май.2026 05:01:09 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/847 "2026-05-28T05:01:09Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **74** new posts, **8** new topics - **Top users by posts/likes (last 24h):** * * * ## Interesting Topics ### #contribute:feature - @jdc20181 proposed letting admins edit user emails even when “edit email after signup” is disabled, arguing the current toggle is _all-or-nothing_ and risky during the brief “enabled” window; @Lilly pushed back on security grounds, then warmed to a **sudo-style** confirmation (password/2FA + staff log) as a safer compromise — [read more](https://meta.discourse.org/t/-/403930/1?silent=true) and the security friction debate — [read more](https://meta.discourse.org/t/-/403930/2?silent=true) - A long-running request to **auto-delete topics at the category level** got a forward-looking hint: @sam noted it should be “solvable quite cleanly” via **Discourse Workflows** , implying a more flexible replacement for timer-only patterns (#topic-timers) — [read more](https://meta.discourse.org/t/-/138361/18?silent=true) - Limiting AI translation by category still works, but the control flipped to an “exclude list”: @pmusaraj explained a new `ai_translation_excluded_categories` site setting after a technical change, and said existing sites should have been migrated (#content-localization) — [read more](https://meta.discourse.org/t/-/392993/7?silent=true) - Translating content in **emails/activity summaries** remains on the roadmap: @pmusaraj asked for clarification/screenshots around “custom remarks,” while confirming there’s no timeline yet for translated-email delivery (#ai #activity-summary #dynaloc) — [read more](https://meta.discourse.org/t/-/383546/4?silent=true) and roadmap status — [read more](https://meta.discourse.org/t/-/383546/6?silent=true) * * * ### #bug - A French-language instance saw the composer replacing an apostrophe with `>` (e.g., `j'ai` → `j>ai`): @renato identified it as an overly eager **markdown typographer** behavior and suggested disabling `enable_markdown_typographer` or adjusting quotation mark defaults; the reporter confirmed disabling resolved it (#composer) — diagnosis — [read more](https://meta.discourse.org/t/-/403905/6?silent=true) and confirmation — [read more](https://meta.discourse.org/t/-/403905/8?silent=true) - Nested replies + post voting friction continues: @markvanlan said they’ll disable post voting for nested replies for now, and floated building a **native upvote/downvote** mechanism directly into nested replies as a better long-term fit (#nested-replies #post-voting) — [read more](https://meta.discourse.org/t/-/403696/8?silent=true) * * * ### #Self-hosting - A fresh install hit: **“Failed to automatically register with Discourse ID”**. The root cause turned out to be Discourse ID rejecting a non-HTTPS redirect URI; the workaround was creating an admin via `rake admin:create`, enabling `force_https`, and then enabling Discourse ID login (#advanced-setup) — initial error — [read more](https://meta.discourse.org/t/-/403951/1?silent=true), log clue — [read more](https://meta.discourse.org/t/-/403951/4?silent=true), and the fix path — [read more](https://meta.discourse.org/t/-/403951/7?silent=true) - “Vultr vs DO” turned into a broader reality check: SMTP deliverability/config pain isn’t magically solved by switching vendors. @Lilly recommended pairing a host (e.g., Hetzner) with a dedicated mail provider (e.g., Resend), and noted real-world migration gotchas like login waves and quota spikes — [read more](https://meta.discourse.org/t/-/403964/1?silent=true) and email-provider experience — [read more](https://meta.discourse.org/t/-/403964/8?silent=true) * * * ### #Support - A previously unseen **15-minute impersonation limit** was traced to a hidden setting `experimental_impersonation_time_limit_minutes`. Guidance: it’s not in the UI; you’ll need rails console access (or ask the site owner) to modify it — setting discovery — [read more](https://meta.discourse.org/t/-/403961/2?silent=true), hidden-setting context — [read more](https://meta.discourse.org/t/-/403961/4?silent=true), and rails console snippet — [read more](https://meta.discourse.org/t/-/403961/5?silent=true) - A “document tree depth exceeded” middleware issue got a practical path forward: @sam pointed to a guard already added and highlighted that affected sites will need specific commits (or a rebuild on the latest release / next monthly) — [read more](https://meta.discourse.org/t/-/403831/2?silent=true) - With `allow new registrations` disabled, inviting users into private groups can still throw “registrations not allowed,” especially in SSO flows—an open question seeking a configuration pattern that blocks mass signups while still enabling invite links for existing members — [read more](https://meta.discourse.org/t/-/403941/1?silent=true) - On the “If local logins are disabled” troubleshooting thread, @Lilly redirected a stuck admin to the canonical new-install email troubleshooting guide and reinforced that **YAML sharp edges** (quotes/spacing) can derail rebuilds — email troubleshooting pointer — [read more](https://meta.discourse.org/t/-/403735/22?silent=true) and “scared of yml” follow-up — [read more](https://meta.discourse.org/t/-/403735/25?silent=true) - Discourse’s browser support boundary came up again: a user on a UXP-based browser fork (e.g., Pale Moon) said they’d investigate further after feedback, continuing the “supported vs legacy” compatibility theme — [read more](https://meta.discourse.org/t/-/403890/6?silent=true) * * * ### #customization:plugin - Discourse Gamification’s “external systems” story resurfaced: after @jdc20181 asked about more native/manual/custom point events, @Falco pointed them to the official guide for redeeming/awarding points via integrations — request context — [read more](https://meta.discourse.org/t/-/225916/455?silent=true) and integration guide pointer — [read more](https://meta.discourse.org/t/-/225916/456?silent=true) - In the Discourse OpenID Connect plugin thread, an admin asked how to synchronize **admins via OIDC** , flagging ongoing needs around role/group mapping for enterprise auth (#openid-connect) — [read more](https://meta.discourse.org/t/-/103632/326?silent=true) * * * ### #Announcements / #ux / #blog / #users - “Simple mode” for Doc Categories: @Moin reported a confusing UX moment—posting the first reply in a doc category, then not seeing it—suggesting replies/comments should unhide automatically after publishing — [read more](https://meta.discourse.org/t/-/403366/6?silent=true) - Discourse Discover: May Roundup landed as a companion discussion topic, highlighting communities “building in public” (and turning hard parts into shared knowledge) — [read more](https://meta.discourse.org/t/-/403962/1?silent=true) - A new how-to on changing your title shipped with a screen recording; @Moin noted the video accidentally exposed the author’s email, a timely reminder to scrub recordings before posting — tutorial — [read more](https://meta.discourse.org/t/-/403967/1?silent=true) and privacy catch — [read more](https://meta.discourse.org/t/-/403967/2?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@renato** diagnosed the French composer “apostrophe becomes `>`” issue as a **typographer replacement** , pointing admins to relevant site settings and suggesting quick wins for core UX improvement — [read more](https://meta.discourse.org/t/-/403905/6?silent=true) - **@sam** (1) tied category-level auto-delete to upcoming **Discourse Workflows** capabilities — [read more](https://meta.discourse.org/t/-/138361/18?silent=true) — and (2) provided commit-level guidance for the middleware “document tree depth exceeded” problem, advising upgrade/rebuild paths — [read more](https://meta.discourse.org/t/-/403831/2?silent=true) - **@david** updated the developer guide on pinning plugin/theme versions to document the new `d-compat/*` strategy, referencing the newer versioning RFC — [read more](https://meta.discourse.org/t/-/272665/7?silent=true) - **@Danielle** posted that the webinar relay + recap is now available in the retention event topic — [read more](https://meta.discourse.org/t/-/401266/3?silent=true) - **@Falco** (1) confirmed that DiscourseAI sentiment self-hosting support for other LLMs was added recently and should roll out soon — [read more](https://meta.discourse.org/t/-/334451/18?silent=true) — and (2) linked gamification users to the official external integration walkthrough for awarding/redeeming points — [read more](https://meta.discourse.org/t/-/225916/456?silent=true) - **@pmusaraj** (1) clarified that category scoping for translations now uses `ai_translation_excluded_categories` after a technical change — [read more](https://meta.discourse.org/t/-/392993/7?silent=true) — and (2) confirmed translated-email support is still planned (no timeline yet), while requesting more detail to refine the spec — [read more](https://meta.discourse.org/t/-/383546/6?silent=true) - **@markvanlan** proposed a product direction for nested replies: disable post voting there for now, and consider building voting directly into nested replies as a better-aligned feature — [read more](https://meta.discourse.org/t/-/403696/8?silent=true) - **@chapoi** helped on two fronts: explaining how to anonymize/disconnect a WordPress-linked user via the admin UI — [read more](https://meta.discourse.org/t/-/396112/2?silent=true) — and suggesting extension/browser isolation steps to diagnose weird translation formatting on Debian Linux — [read more](https://meta.discourse.org/t/-/400723/2?silent=true) * * * Yesterday’s moral: whether it’s **YAML whitespace** , **HTTPS redirects** , or a typographer turning `j'ai` into `j>ai`, the smallest characters caused the biggest adventures. ---
### 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: [29.Май.2026 05:01:58 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/848 "2026-05-29T05:01:58Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours (as reflected by the activity across threads like the _phantom unread_ report in #bug [read more](https://meta.discourse.org/t/-/403986/1?silent=true) and the rollout note about _small post actions_ in #Announcements [read more](https://meta.discourse.org/t/-/404058/1?silent=true)), Meta saw: - **Total new posts:** **106** - **Total new topics:** **19** ### Top users (posts + likes) | User | Posts | Likes | Recent highlight | | --- | --- | --- | --- | | **@Lilly** | 15 | 25 | Shared a site-wide Rails snippet to clear “phantom” unread state in #bug [read more](https://meta.discourse.org/t/-/403986/5?silent=true) | | **@awesomerobot** | 1 | 13 | Announced the improved in-composer event editor for #calendar-and-events in #Announcements [read more](https://meta.discourse.org/t/-/404041/1?silent=true) | | **@merefield** | 7 | 12 | Helped debug SMTP/provider constraints in #Self-hosting discussions [read more](https://meta.discourse.org/t/-/403964/10?silent=true) | | **@chapoi** | 5 | 9 | Confirmed the team is tracking the “phantom unreads” bug in #bug [read more](https://meta.discourse.org/t/-/403986/3?silent=true) | | **@rishabh** | 1 | 8 | Posted the May edition of _Current Projects_ in #Announcements [read more](https://meta.discourse.org/t/-/403907/1?silent=true) | | **@haydenjames** | 2 | 8 | Praised bundled plugins and the “no rebuild” workflow in #community-building:praise [read more](https://meta.discourse.org/t/-/404014/1?silent=true) | | **@loic** | 1 | 6 | Published the **v2026.05** monthly release pointer in #Announcements [read more](https://meta.discourse.org/t/-/403981/1?silent=true) | | **@sam** | 2 | 6 | Announced small actions will no longer count as tracked/watched activity in #Announcements [read more](https://meta.discourse.org/t/-/404058/1?silent=true) | | **@ted** | 2 | 6 | Investigated (and proposed fixes for) group-creation validation/UX edge cases in #ux [read more](https://meta.discourse.org/t/-/404049/2?silent=true) | | **@matt_k_bcn** | 2 | 6 | Brought UX feedback about Horizon category badges being distracting (#customization:theme) [read more](https://meta.discourse.org/t/-/360486/90?silent=true) | > “We are aware of this bug and trying to resolve it. We are all annoyed by it” — @chapoi, on phantom unreads [read more](https://meta.discourse.org/t/-/403986/3?silent=true) ### A few other threads that stayed busy - Horizon theme visual feedback (#customization:theme) [read more](https://meta.discourse.org/t/-/360486/90?silent=true) - Announcement Bar theme component improvements (#customization:theme component) [read more](https://meta.discourse.org/t/-/286352/31?silent=true) - Mixed-case tag names breaking tag selection in form templates (#Support, #form-templates) [read more](https://meta.discourse.org/t/-/404021/1?silent=true) - Nested replies rollout feedback & stability concerns (#Announcements, #nested-replies) [read more](https://meta.discourse.org/t/-/402812/31?silent=true) - Dev Container workflow troubleshooting on macOS (#Developer Guides) [read more](https://meta.discourse.org/t/-/336366/11?silent=true) - “Live Pull Request Status on GitHub Oneboxes” got a Gitea question (#Announcements) [read more](https://meta.discourse.org/t/-/390900/22?silent=true) * * * ## Interesting Topics ### #bug - @Orioni reported a confusing “Unread (14)” counter while `/unread` was empty, and @chapoi confirmed the team is actively working on the “phantom unreads” issue; a temporary site-wide mitigation via Rails/SQL was shared for admins who need immediate relief [read more](https://meta.discourse.org/t/-/403986/1?silent=true). Related: the fix was noted as tied to the small-action tracking change shipping in [Small post actions no longer tracked or watched](https://meta.discourse.org/t/-/404058/1?silent=true). - @dennisjbr described an incoming-email handler crash around Gmail dot variants (`user.name@gmail.com` vs `username@gmail.com`) that also blocks adding dot-variant addresses as secondary emails, due to “Primary email has already been taken” validations [read more](https://meta.discourse.org/t/-/404042/1?silent=true). - @glob-canard.4x hit an upgrade blocker where `rake db:seed_fu` fails with “Name has already been taken” while creating new system groups (`anonymous`, `logged_in_users`), and documented a manual workaround (saving without validation) [read more](https://meta.discourse.org/t/-/404037/1?silent=true). - A fix was proposed for an infinite-loading/403 loop when clicking reaction counters on _hidden_ posts: backend permission checks block the request, but the frontend still renders the counter, creating a bad UX trap [read more](https://meta.discourse.org/t/-/404053/1?silent=true). ### #Announcements - Discourse shipped a smoother event creation flow: @awesomerobot introduced an interactive event editor directly inside the composer (plus clearer RSVP settings) for the #calendar-and-events plugin [read more](https://meta.discourse.org/t/-/404041/1?silent=true). Background: the core plugin thread is here [read more](https://meta.discourse.org/t/-/97376/1?silent=true), and related setup simplifications were previously announced here [read more](https://meta.discourse.org/t/-/401309/1?silent=true). - @sam announced a behavioral change: **small action posts** (close/open/assign/admin actions) will no longer advance _Tracked_/_Watched_ indicators, explicitly to reduce “administrivia notifications” (and it’s _not optional_) [read more](https://meta.discourse.org/t/-/404058/1?silent=true). ### #ux - @darkpixlz flagged that creating a request-only group **with no owner** yields an unhelpful generic “FAILED” message; @ted dug into how/where validation fires, noted additional edge cases (private group + request-only settings), and opened a PR to restore a missing translation-backed error message [read more](https://meta.discourse.org/t/-/404049/1?silent=true). ### #Support - @ARK-Helena needed to create chat channels via API at scale; @chapoi pointed to the (existing) endpoint `POST /chat/api/channels`, and the OP followed up with a working parameter example (noting `chatable_id` is the category id) [read more](https://meta.discourse.org/t/-/403979/1?silent=true). - @Ric wanted a “landing page” that lists only certain community groups (e.g., Communities of Practice), and was pointed at the Landing Pages plugin as a likely solution [read more](https://meta.discourse.org/t/-/403988/1?silent=true). Follow-on: someone else reported the Landing Pages plugin throwing a 500 after upgrading to `v2026.6.0-latest`, sharing a backtrace and error details for debugging [read more](https://meta.discourse.org/t/-/180967/161?silent=true). - @Parker1090 found a form-templates `tag-chooser` dropdown that _renders_ but won’t allow selection; @zogstrip tracked it down to **mixed-case tag names** , reproduced locally, and linked a PR fix [read more](https://meta.discourse.org/t/-/404021/1?silent=true). ### #contribute:feature - A long-running admin workflow question resurfaced: when `email_editable` is disabled (to prevent users changing addresses), admins also lose the ability to edit user emails through the admin UI—prompting discussion about security, admin tiering, and guardrails [read more](https://meta.discourse.org/t/-/403930/10?silent=true). - @dfabulich argued that “Sign Up” is too hard to find on mobile (especially when header space is tight), and the thread quickly connected to existing UI/component options and a PR to improve the situation [read more](https://meta.discourse.org/t/-/404022/1?silent=true). Related: the “combined auth button” component discussed as a workaround is here [read more](https://meta.discourse.org/t/-/401215/1?silent=true). ### #Self-hosting - A practical hosting thread compared Vultr vs DigitalOcean for running Discourse—quickly orbiting around **SMTP port blocking** and the pitfalls of “easy installs” like the DO marketplace image; the consensus leaned toward standard installs + using third-party email providers (or APIs) instead of raw SMTP when providers restrict ports [read more](https://meta.discourse.org/t/-/403964/10?silent=true). Cross-link: the original “local logins disabled” troubleshooting thread that got referenced is here [read more](https://meta.discourse.org/t/-/403735/27?silent=true). ### #community-building Building - @putty asked how to manage product announcement subscriptions when you have _many products_ and _many versions_: whether to drive subscriptions via tags, how to handle “applies to everyone” posts, and how to avoid overwhelming users as release cadence increases [read more](https://meta.discourse.org/t/-/404039/1?silent=true). ### #Announcements (again, because it kept bubbling up) - The ongoing nested replies discussion got fresh production feedback: pilot testers reported users disliking the UI, theme-component incompatibilities, and URL/endpoint changes causing link breakage—leading to a strong warning about enabling it in production right now [read more](https://meta.discourse.org/t/-/402812/31?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** published the new “create events” composer flow announcement for the Calendar and Events plugin (#calendar-and-events), including screenshots and a rundown of revised advanced settings [read more](https://meta.discourse.org/t/-/404041/1?silent=true). - **@chapoi** (1) confirmed active work on the “phantom unreads” bug and acknowledged community frustration [read more](https://meta.discourse.org/t/-/403986/3?silent=true); (2) pointed out the existing API endpoint for chat channel creation and got the Support thread to a solution [read more](https://meta.discourse.org/t/-/403979/2?silent=true); (3) handled Horizon theme feedback triage by folding a support-ish post into the main theme thread to keep feedback centralized [read more](https://meta.discourse.org/t/-/360486/92?silent=true). - **@rishabh** posted the May 2026 “Current Projects” newsletter, with pointers to recently finished plugin improvements (including Topic Voting and Calendar/Events workflow improvements) [read more](https://meta.discourse.org/t/-/403907/1?silent=true). Linked references from that post include: Topic Voting plugin [read more](https://meta.discourse.org/t/-/40121/1?silent=true), voting improvements writeup [read more](https://meta.discourse.org/t/-/401156/1?silent=true), and new voting badges announcement [read more](https://meta.discourse.org/t/-/401731/1?silent=true). - **@sam** announced the rollout that removes “small action” posts from Tracked/Watched counters—explicitly to reduce noisy notifications—while requesting feedback about downstream impact [read more](https://meta.discourse.org/t/-/404058/1?silent=true). @sam also reassured folks that phantom unreads should disappear as deployment completes [read more](https://meta.discourse.org/t/-/403986/7?silent=true). - **@loic** posted the pointer for the **May 2026 monthly release** (v2026.05), linking to the official changelog [read more](https://meta.discourse.org/t/-/403981/1?silent=true). - **@markvanlan** noted that an idea from the Nested Replies testing thread has been implemented, closing the loop on a piece of earlier feedback [read more](https://meta.discourse.org/t/-/398759/119?silent=true). - **@manuel** shipped updates to the Announcement Bar theme component (localized strings, localStorage dismiss logic, responsive layout, and BEM class cleanup) [read more](https://meta.discourse.org/t/-/286352/31?silent=true), and also followed up on feedback expectations in the Featured Topics component thread [read more](https://meta.discourse.org/t/-/217580/63?silent=true). - **@Danielle** replied in the moderator-program webinar thread to confirm the recap has been posted (after a delay) [read more](https://meta.discourse.org/t/-/398295/21?silent=true). - **@pmusaraj** acknowledged helpful examples about localized “something else” flag handling in the content-localization/email translation discussion [read more](https://meta.discourse.org/t/-/383546/8?silent=true). - **@zogstrip** reproduced and diagnosed the form-templates tag selector issue, traced it to mixed-case tag names, and linked a PR fix—getting the support request to “Solved” [read more](https://meta.discourse.org/t/-/404021/7?silent=true). * * * Phantom unreads are getting exorcised and small actions are being banished from your counters—so here’s hoping tomorrow’s Meta is just a little quieter (in all the right notification places). ---
### 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: [30.Май.2026 05:01:08 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/849 "2026-05-30T05:01:08Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **In the last 24 hours (2026-05-29 → 2026-05-30):** - **New posts:** 67 - **New topics:** 8 - This snapshot is based on activity across active discussions including the new core build system announcement ([read more](https://meta.discourse.org/t/-/403908/1?silent=true)) and multiple UX/support threads like keyboard shortcut alignment ([read more](https://meta.discourse.org/t/-/404060/1?silent=true)) and JAWS accessibility troubleshooting ([read more](https://meta.discourse.org/t/-/404095/1?silent=true)). **Top users (posts / likes in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @david | 1 | 26 | | @merefield | 6 | 10 | | @Lilly | 8 | 2 | | @Moin | 4 | 3 | | @chapoi | 3 | 6 | | @NateDhaliwal | 2 | 4 | | @satgo1546 | 1 | 3 | | @alehandrof | 1 | 2 | | @jrgong | 1 | 2 | | @mcdanlj | 1 | 2 | > Notable: the biggest “single post impact” came from @david’s #development update on a new JavaScript build system for core ([read more](https://meta.discourse.org/t/-/403908/1?silent=true)). * * * ## Interesting Topics ### #development - @david announced a **new JavaScript build system for Discourse core** , moving from `ember-cli`/`webpack` to _rolldown_ (aligned with Vite and modern ES Modules) with claims of **~80% faster dev builds** and a focus on backwards compatibility for production installs ([read more](https://meta.discourse.org/t/-/403908/1?silent=true)). ### #ux - A visual polish issue was reported where **keys appear misaligned in the keyboard shortcut modal** , likely due to legacy margins remaining after a redesign; @chapoi identified the likely cause and linked the fix PR ([read more](https://meta.discourse.org/t/-/404060/1?silent=true)). - A UX regression/rough edge was discussed: creating a **request-only group with no owner** yields an error that’s not descriptive enough; the thread references an older related warning message discussion ([read more](https://meta.discourse.org/t/-/404049/1?silent=true), and the older reference: [read more](https://meta.discourse.org/t/-/64760/1?silent=true)). ### #Announcements - In the ongoing rollout/testing of **#nested-replies** , folks explored how to test nested mode without forcing it on everyone; the thread also highlights that some themes/components may not yet be compatible with nested rendering ([read more](https://meta.discourse.org/t/-/402812/36?silent=true)). - Conversation continues around the **docked composer for AI bot conversations** (#ai / #ai-bot): feedback suggests chat-style input can be limiting for long-form prompts (code blocks, paragraphs), and there was also a report that image uploads were breaking after the first post when using the docked composer mode ([read more](https://meta.discourse.org/t/-/403327/3?silent=true)). - The “Easily create Support categories using the discourse-solved plugin” announcement thread picked up additional product feedback: the ask is to optionally make “support ticket” categories private (checkbox-style) to approximate a lightweight ticketing workflow ([read more](https://meta.discourse.org/t/-/398338/14?silent=true)). - The “Easily create Ideas categories using the Topic Voting plugin” thread saw a report that removing the “Ideas” type can also remove voting unexpectedly, prompting clarification on how category “type” and vote UI are meant to interact ([read more](https://meta.discourse.org/t/-/399365/3?silent=true)). ### #Support - A marketplace-style use case asked for **customizing post layout/structure** beyond what #form-templates can output (linear `h3`/`p` pairs): the practical answer is that truly custom “product card” layouts generally require a theme component (or hiring help), while topic-list components like official thumbnails/cards mostly address _lists_, not in-post structured rendering ([read more](https://meta.discourse.org/t/-/404068/1?silent=true)). - A self-hosting admin hit “running out of space” during rebuilds and investigated Docker/container storage consumption, asking if multi-GB usage under `/var/lib/containerd` and `/var/docker` is normal; cleanup commands were suggested ([read more](https://meta.discourse.org/t/-/404122/1?silent=true)). - A “browser unsupported” login blocker appeared on an Ubuntu Discourse instance despite the reporter being on a current Firefox build; debugging suggestions included checking the browser console and clearing cache/cookies, and it was cross-referenced with known UXP/fork browser support limitations ([read more](https://meta.discourse.org/t/-/404070/1?silent=true), plus related: [read more](https://meta.discourse.org/t/-/403890/5?silent=true)). - Category visibility questions resurfaced: excluding/hiding categories from `/latest` is still a recurring need, with admins comparing “mute” vs “suppressed” behavior and pointing to the official suppression plugin and older context on why the core setting disappeared ([read more](https://meta.discourse.org/t/-/402209/17?silent=true), background: [read more](https://meta.discourse.org/t/-/133894/101?silent=true), and plugin pointer: [read more](https://meta.discourse.org/t/-/357254/7?silent=true)). ### #bug - A bug report notes that **email notifications don’t reflect “full name” display settings** : even if the UI is configured to show full names in-app, email mention formatting still shows usernames, suggesting a mismatch between UX settings and email rendering (#email / #mentions) ([read more](https://meta.discourse.org/t/-/404075/1?silent=true)). - In #nested-replies bug-chasing, a broken **suggested-topics link to nested topics** was discussed: the nested link format changed, and redirect/404 handling plus unread indicators/dots were explored as follow-ups ([read more](https://meta.discourse.org/t/-/403743/8?silent=true)). - A theming bug was reported for **Topic List Thumbnails** : in “Blog Style” mode the reply count appears wrong/not counting, prompting investigation in the official #topic-list-thumbnails ecosystem ([read more](https://meta.discourse.org/t/-/404124/1?silent=true); related component thread: [read more](https://meta.discourse.org/t/-/150602/353?silent=true)). ### #Support (Accessibility) - JAWS screen reader usage raised two key issues: (1) JAWS shortcuts can override Discourse shortcuts unless virtual cursor mode is toggled, and (2) category/subcategory reading and selection can become unusable depending on where the category list is being navigated (#accessibility / #ux) ([read more](https://meta.discourse.org/t/-/404095/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@david** published a major #development update introducing a **new JS build system for core** using rolldown, native ES Modules, and large dev-speed improvements, while emphasizing production/backwards compatibility and continued use of precompiled assets for self-hosters ([read more](https://meta.discourse.org/t/-/403908/1?silent=true); related precompiled assets context: [read more](https://meta.discourse.org/t/-/376700/1?silent=true)). - **@chapoi** helped triage and fix UX issues, including identifying a likely legacy CSS margin as the cause of misaligned shortcut keys in the keyboard shortcuts modal and linking the implementation fix ([read more](https://meta.discourse.org/t/-/404060/3?silent=true)). @chapoi also advised on approaches to custom marketplace-style layouts, pointing to existing list-based options while clarifying when you’ve crossed into “needs a custom theme component” territory ([read more](https://meta.discourse.org/t/-/404068/2?silent=true), plus referenced components: [read more](https://meta.discourse.org/t/-/150602/1?silent=true) and [read more](https://meta.discourse.org/t/-/296048/1?silent=true)). - **@markvanlan** continued tightening up #nested-replies behavior, confirming that link updates landed but that redirects from flat-view links should be fixed to avoid 404s, and explaining why unread counts are not shown for nested topics (since “catching up” isn’t a simple scroll-to-bottom operation) ([read more](https://meta.discourse.org/t/-/403743/8?silent=true) and [read more](https://meta.discourse.org/t/-/403743/10?silent=true)). - **@tannerabread** delivered an update for #form-templates: copy/paste and drag/drop into a composer inside a form template is now available in `latest`, and they asked for verification from reporters once tested ([read more](https://meta.discourse.org/t/-/402250/13?silent=true)). - **@pmusaraj** merged a fix related to sending users **translated posts in emails when their user language is set** , linking the GitHub PR from the long-running feature thread (#ai / #activity-summary / #dynaloc / #content-localization) ([read more](https://meta.discourse.org/t/-/383546/9?silent=true)). - **@southpaw** clarified expectations around Discourse-hosting backups: infrastructure/cluster backups are for disaster recovery and not intended for routine customer-requested restores; site-level “full backups including uploads” can be arranged via support for hosted customers ([read more](https://meta.discourse.org/t/-/122710/69?silent=true)). - **@awesomerobot** provided practical #accessibility guidance for JAWS: screenreaders can capture keys (virtual cursor mode), preventing Discourse shortcuts; toggling that mode should allow Discourse shortcuts through, and they asked for specifics on where category/subcategory selection becomes inaccessible so it can be reproduced and improved ([read more](https://meta.discourse.org/t/-/404095/2?silent=true)). * * * _Fun sign-off:_ Yesterday’s Meta felt like a tuning sprint—between **rolldown-powered build speed gains** ([read more](https://meta.discourse.org/t/-/403908/1?silent=true)) and ongoing **nested replies** fit-and-finish work ([read more](https://meta.discourse.org/t/-/403743/8?silent=true)), the community basically spent the day shaving seconds off both developer workflows and reader clicks. ---
### 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: [31.Май.2026 05:01:25 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/850 "2026-05-31T05:01:25Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **Window covered:** 2026-05-30 → 2026-05-31 (last 24 hours) - **New posts:** **19** - **New topics:** **2** — a request to localize AI prompts ([read more](https://meta.discourse.org/t/-/404143/1?silent=true)) and a staff-category “endless spinner” bug report ([read more](https://meta.discourse.org/t/-/404136/1?silent=true)). **Top users (posts / likes in the last 24h):** - **@RGJ** — **3 posts** , **4 likes** (notably in the Snapblocks discussion: [read more](https://meta.discourse.org/t/-/310155/7?silent=true), [read more](https://meta.discourse.org/t/-/310155/10?silent=true), [read more](https://meta.discourse.org/t/-/310155/12?silent=true)) - **@chapoi** — **2 posts** , **3 likes** (nested replies UX/mental-model discussion: [read more](https://meta.discourse.org/t/-/402812/41?silent=true), [read more](https://meta.discourse.org/t/-/402812/43?silent=true)) - **@bksubhuti** — **2 posts** , **1 like** (questions about user-selectable nested replies: [read more](https://meta.discourse.org/t/-/402812/40?silent=true), [read more](https://meta.discourse.org/t/-/402812/42?silent=true)) - **@Luna_Mora** — **2 posts** , **0 likes** (plugin deprecation notice + policy-page UX: [read more](https://meta.discourse.org/t/-/70649/133?silent=true), [read more](https://meta.discourse.org/t/-/24083/25?silent=true)) - **@ego-lay_atman-bay** — **3 posts** , **0 likes** (Snapblocks implementation details + WYSIWYG concerns: [read more](https://meta.discourse.org/t/-/310155/9?silent=true), [read more](https://meta.discourse.org/t/-/310155/11?silent=true)) - **@Lilly** — **1 post** , **1 like** (CSS-only “Sign up” link idea for mobile anon users: [read more](https://meta.discourse.org/t/-/404022/14?silent=true)) - **@Bryanpwo** — **1 post** , **1 like** (browser compatibility troubleshooting question: [read more](https://meta.discourse.org/t/-/404070/4?silent=true)) - **@awesomerobot** — **1 post** , **1 like** (mobile signup UX patterns and tradeoffs: [read more](https://meta.discourse.org/t/-/404022/13?silent=true)) - **@Jose_C_Gomez** — **1 post** , **0 likes** (staff-only category spinner error report: [read more](https://meta.discourse.org/t/-/404136/1?silent=true)) - **@bird** — **1 post** , **0 likes** (Chinese localization request for AI plugin prompts: [read more](https://meta.discourse.org/t/-/404143/1?silent=true)) * * * ## Interesting Topics ### #Announcements - **Nested replies: should it be a per-user preference?** In the ongoing #nested-replies discussion, @bksubhuti asked why individuals can’t toggle it in their personal UI ([read more](https://meta.discourse.org/t/-/402812/40?silent=true)), and @chapoi argued that _shared content needs shared structure_ because divergent views break reference points like “the previous comment” and permalink expectations ([read more](https://meta.discourse.org/t/-/402812/41?silent=true)). - **Engagement vs communication (and what Discourse optimizes for).** The same thread also sharpened into a values debate: @bksubhuti suggested “engagement trumps a unified experience” ([read more](https://meta.discourse.org/t/-/402812/42?silent=true)), and @chapoi pushed back with “Does engagement trump good communication?” ([read more](https://meta.discourse.org/t/-/402812/43?silent=true)). ### #customization:plugin - **Snapblocks: plugin or theme component?** In the Snapblocks #bbcode discussion, @RGJ questioned whether the work should be a theme component rather than a plugin ([read more](https://meta.discourse.org/t/-/310155/7?silent=true)), while @ego-lay_atman-bay explained they’re hooking into parsing to prevent inner-tag parsing and want better composer/WYSIWYG support ([read more](https://meta.discourse.org/t/-/310155/9?silent=true)). @RGJ countered that plugin installs/rebuilds are _more_ cumbersome than theme component updates and don’t work on Discourse-hosted plans ([read more](https://meta.discourse.org/t/-/310155/10?silent=true); [read more](https://meta.discourse.org/t/-/310155/12?silent=true)). - **Geo Blocking plugin impacted by a recent Discourse update.** @LotusJeff reported that a new Discourse update appears to have broken the Geo Blocking plugin and pointed to a GitHub issue for tracking ([read more](https://meta.discourse.org/t/-/227824/48?silent=true)). - **Category Lockdown plugin: console deprecation warning for `.hbs` connector templates.** @Luna_Mora shared a deprecation notice indicating the plugin’s connector template should move from `.hbs` to `.gjs` ([read more](https://meta.discourse.org/t/-/70649/133?silent=true)), referencing the underlying deprecation documentation topic ([read more](https://meta.discourse.org/t/-/398896/1?silent=true)). ### #contribute:feature - **Make “Sign up” easier to find on mobile (UX patterns and tradeoffs).** @awesomerobot reviewed patterns across popular sites—often prioritizing login, sometimes using a combined email-first flow—and discussed the pros/cons of not differentiating until after email entry ([read more](https://meta.discourse.org/t/-/404022/13?silent=true)). - **A lightweight CSS workaround: show “Sign up” only to mobile anonymous users.** In the same thread, @Lilly proposed adding a sidebar link and hiding it for everyone except mobile anon visitors using simple CSS targeting ([read more](https://meta.discourse.org/t/-/404022/14?silent=true)). - **Request: allow AI plugin prompts to be configured/localized in Chinese.** A new #ai #localization feature request asked for Chinese prompt support for things like summarization and title generation, noting current behavior defaults to English ([read more](https://meta.discourse.org/t/-/404143/1?silent=true)); @sniper756 added that language output can be inconsistent depending on model and other factors ([read more](https://meta.discourse.org/t/-/404143/2?silent=true)). - **Add a custom page to the About/FAQ/ToS/Privacy section (UX consistency).** @Luna_Mora revived the long-running request to support at least one additional page in the “About” area, describing a workaround (“FAQ URL trick”) but noting it breaks the smooth navigation within the on-site policy page cluster ([read more](https://meta.discourse.org/t/-/24083/25?silent=true)). ### #Support - **“Unfortunately, your browser is unsupported” — narrowing down browser/compatibility.** In troubleshooting, @Bryanpwo asked which browser the reporter is using, noting Firefox works across Discourse installs (including their own) ([read more](https://meta.discourse.org/t/-/404070/4?silent=true)). - **New: Endless spinner when viewing posts—only in a Staff category.** @Jose_C_Gomez reported a “Could not view topic” TypeError (`name_key` undefined) that occurs only in their Staff category and pointed to a similar Meta thread for comparison ([read more](https://meta.discourse.org/t/-/404136/1?silent=true); related: [read more](https://meta.discourse.org/t/-/323031/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@chapoi** dug into the _social + technical_ implications of allowing per-user nested/linear views, arguing that divergent mental models undermine a shared conversation space (including how “reply-to” references and ordering are perceived) ([read more](https://meta.discourse.org/t/-/402812/41?silent=true)). They also framed the product stance bluntly—prioritizing communicative clarity over raw engagement mechanics ([read more](https://meta.discourse.org/t/-/402812/43?silent=true)). - **@awesomerobot** weighed in on mobile onboarding patterns and why Discourse isn’t necessarily out-of-step with common UI conventions, while still acknowledging alternative flows like “email-first then branch by account existence” ([read more](https://meta.discourse.org/t/-/404022/13?silent=true)). * * * _Yesterday’s vibe check:_ between nested-replies philosophy and mobile signup tweaks, Meta managed to debate the meaning of “good conversation” **and** ship a CSS snippet in the same day—classic Discourse energy. ---
### 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: [01.Июнь.2026 05:02:21 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/851 "2026-06-01T05:02:21Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 52** - **New topics (last 24h): 9** **Top contributors (posts / likes received in the last 24h):** - **@Lilly** — 9 posts / 6 likes - **@Ed_S** — 3 posts / 8 likes - **@sam** — 3 posts / 2 likes - **@NateDhaliwal** — 3 posts / 5 likes - **@martin** — 2 posts / 1 like - **@nwnuyhs** — 2 posts / 2 likes - **@RalfJung** — 2 posts / 2 likes - **@Jagster** — 1 post / 2 likes - **@Moin** — 1 post / 1 like - **@ego-lay_atman-bay** — 1 post / 1 like **Quick hits & follow-ups that also saw motion:** - A long-running moderation/review oddity resurfaced in [“Notification claims X users for approval, but none are found”](https://meta.discourse.org/t/-/262853/29?silent=true), with pointers to additional edge-case handling discussed elsewhere ([read more](https://meta.discourse.org/t/-/403620/10?silent=true)). - Chat capabilities & expectations came up again around bot formatting support in [“Full markdown support in Chat for bots”](https://meta.discourse.org/t/-/312003/21?silent=true), alongside broader “Chat vs Messages” considerations ([read more](https://meta.discourse.org/t/-/336765/14?silent=true)). - Plugin maintenance notes continued, including the #TAG **#bbcode** plugin thread [“Snapblocks”](https://meta.discourse.org/t/-/310155/13?silent=true) and the #customization:plugin report on **Geo Blocking** after a core change ([read more](https://meta.discourse.org/t/-/227824/49?silent=true)). - Math rendering/MathJax context also got cross-linked via prior upgrade work: [“Undefined control sequence \textcolor”](https://meta.discourse.org/t/-/372840/3?silent=true) referencing [“Upgrading Mathjax to version 4”](https://meta.discourse.org/t/-/392669/1?silent=true). * * * ## Interesting Topics ### #Support - @long_season investigated disk pressure from large container layers, and @Ed_S recommended cleanup + system journaling trimming (including a `journalctl --vacuum-size` idea) while @merefield clarified how base images accumulate during rebuilds in [“Running out of space - Docker image is large?”](https://meta.discourse.org/t/-/404122/4?silent=true) (see also the cleanup details and image discussion: [read more](https://meta.discourse.org/t/-/404122/5?silent=true), plus historical journaling context quoted by @Ed_S: [read more](https://meta.discourse.org/t/-/165438/25?silent=true)). - A branding mystery (“logo not showing”) turned out to be a site configuration mismatch—resolved by enabling **Force HTTPS** in [“Forum logo isn’t showing”](https://meta.discourse.org/t/-/404163/3?silent=true). - A screenshot sparked curiosity about a dismissible UI box; the answer was that it’s a private theme component used by the team, and the thread helpfully pointed to the public approach in [“Is this a plugin? or a built in feature.?”](https://meta.discourse.org/t/-/404166/2?silent=true) (related: [“Dismissible banner on Meta”](https://meta.discourse.org/t/-/233189/1?silent=true)). - A puzzling “unsupported browser” banner appeared only on certain page types, prompting troubleshooting steps (including MTU adjustments and VPN suggestions) in [“Unfortunately, your browser is unsupported”](https://meta.discourse.org/t/-/404070/5?silent=true) (workaround ideas here: [read more](https://meta.discourse.org/t/-/404070/6?silent=true)). - A lightbox UI regression/UX snag was reported after PhotoSwipe icon changes, where overlay icons visually collide with screenshot content in [“PhotoSwipe new icons visual collision”](https://meta.discourse.org/t/-/404167/1?silent=true) (#TAG **#lightbox** ). ### #Site feedback - The meta documentation ecosystem got a small but important papercut report: category links in the bug-reporting guide now 404 due to the #TAG **#meta-redesign-2026** category restructuring, with proposed fixes centered on using category-ID URLs in [“‘Creating bug reports for Discourse on Meta’ guide has dead links”](https://meta.discourse.org/t/-/404150/1?silent=true) (original guide referenced: [read more](https://meta.discourse.org/t/-/33070/1?silent=true)). ### #bug - Chat uploads + CDNs: @Lilly identified that **chat thumbnails** can bypass `s3_cdn_url` and leak/break by using raw bucket URLs when S3-compatible storage is configured, especially impacting secure setups like R2, in [“Chat thumbnails bypass s3\_cdn\_url & use raw S3 bucket URLs”](https://meta.discourse.org/t/-/404174/1?silent=true) (#TAG **#cdn** #TAG **#s3** #TAG **#chat** ). This connected back to earlier storage/CDN analysis ([read more](https://meta.discourse.org/t/-/358204/1?silent=true)). - The “Unread” experience issue continued: some unread topics don’t appear in the Unread list even when visible in Latest; it was marked duplicate of an existing tracking thread in [“‘Unread’ tab is not listing all thread with unread messages”](https://meta.discourse.org/t/-/404151/2?silent=true) (dupe target: [read more](https://meta.discourse.org/t/-/403986/1?silent=true)). - A permissions regression (or newly enforced rule) may be blocking a moderator workflow: setting a `publish_to_category` topic timer now returns **403** for a global moderator (while admins succeed) in [“403 when setting publish\_to\_category topic timer after update”](https://meta.discourse.org/t/-/404164/1?silent=true) (#TAG **#topic-timers** #TAG **#bug** ). - iOS PWA composer UI: a fix landed (or is at least available via rebuild) for a composer sizing problem that hid the Reply button while composing, in [“Reply button not visible when composing on iOS PWA”](https://meta.discourse.org/t/-/403662/6?silent=true) (#TAG **#composer** #TAG **#pwa** #TAG **#ios** ). - Upgrade/seed task failure: `db:seed_fu` can crash on auto-group creation when **user/group namespaces collide** , prompting investigation and a likely rename strategy in [“Db:seed\_fu fails on 002\_groups.rb during upgrade: Validation failed: Name has already been taken”](https://meta.discourse.org/t/-/404037/7?silent=true). - Another iOS + math rendering report landed: intermittent cropped delimiters in portrait (post-upgrade) were captured and described in [“Occasional cropped delimiters on iOS portrait after recent rebuild”](https://meta.discourse.org/t/-/404148/1?silent=true) (#TAG **#pwa** #TAG **#math** ), adding to the broader MathJax upgrade context ([read more](https://meta.discourse.org/t/-/392669/1?silent=true)) and prior symptom tracking ([read more](https://meta.discourse.org/t/-/372840/3?silent=true)). ### #customization:plugin - The #TAG **#experimental** “Suggested Edits” plugin hit an initialization ordering pitfall—attempting to modify `service:composer` after it had already been initialized—along with a proposed fix/approach in [“Discourse Suggested Edits”](https://meta.discourse.org/t/-/398691/6?silent=true) (related plugin API warning thread: [read more](https://meta.discourse.org/t/-/262064/1?silent=true)). ### #development - CI ergonomics: a plugin author described difficulty reproducing the “SKIP\_DB\_AND\_REDIS bootability” GitHub Action failure locally, and shared the real culprit (DB access during boot via a constant referencing AR schema) in [“Github actions failing ‘Check SKIP\_DB\_AND\_REDIS bootability’ step”](https://meta.discourse.org/t/-/404152/1?silent=true). ### #Nested Replies Testing - The nested replies experiment continued to attract “tree vs simplicity” feedback—suggestions leaned toward lighter UI (e.g., a pop-up reply panel) rather than a Reddit-like structure in [“Testing Nested Replies on Meta”](https://meta.discourse.org/t/-/398759/120?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @sam jumped into the chat CDN/S3 thumbnail bug report—after a side note about broken oneboxes likely tied to the site move—mentioning a rebake in [“Chat thumbnails bypass s3\_cdn\_url & use raw S3 bucket URLs”](https://meta.discourse.org/t/-/404174/2?silent=true). - @sam acknowledged the plugin initialization issue and flagged that a **pre-initializer** may be required in [“Discourse Suggested Edits”](https://meta.discourse.org/t/-/398691/7?silent=true). - @sam closed the Unread-list report as a duplicate (while signaling an impending fix) in [“‘Unread’ tab is not listing all thread with unread messages”](https://meta.discourse.org/t/-/404151/2?silent=true) and pointed back to the canonical tracking topic ([read more](https://meta.discourse.org/t/-/403986/1?silent=true)). - @martin investigated the seed/upgrade failure and moved toward a practical fix via renaming to reduce collisions in [“Db:seed\_fu fails on 002\_groups.rb during upgrade”](https://meta.discourse.org/t/-/404037/5?silent=true) (follow-up reasoning here: [read more](https://meta.discourse.org/t/-/404037/7?silent=true)). - @olivia advised admins to **rebuild the app container** to pick up the latest composer resizing fix for iOS PWA in [“Reply button not visible when composing on iOS PWA”](https://meta.discourse.org/t/-/403662/6?silent=true). * * * If yesterday taught us anything, it’s that a quick rebake, a careful cleanup, and a non-Reddit reply UI can save the day—while your chat thumbnails politely take the CDN instead of wandering off to raw bucket URLs. [Предыдущая страница](https://meta.discourse.org/t/daily-summary-5am-utc/291851.md?page=30) [Следующая страница](https://meta.discourse.org/t/daily-summary-5am-utc/291851.md?page=32)