每日摘要（UTC早上5点）

新闻和活动 论坛摘要
832

Today on 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

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); early excitement rolled in quickly (including practical “can’t-wait-to-try-it” deployment plans) (read more)

  • 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)

  • 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); background context in the same feature line is in the main topic (read more)

#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), and Lilly added that you can safely change slugs too (topic links don’t depend on them) (read more); original question and rollout concerns are here (read more)

  • 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), and merefield pointed to a proven approach for redirecting all 404s to home (with a direct reference to an earlier how-to) (read more; plus the referenced how-to: read more)

  • 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); Falco explained the upstream model change hadn’t merged and recommended pointing to a specific branch (including an updated command) (read more), which resolved the issue for the reporter (read more)

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); chapoi confirmed and shared console clues (read more), and zogstrip reported a fix in progress after reproducing locally (read more). A near-identical duplicate report also appeared (read more)

  • 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)

  • 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); zogstrip then pulled in an additional set of eyes for review (read more)

  • 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; original issue context: read more)

  • 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; prior note on upcoming PR changes: read more)

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); zogstrip suggested the bug was already fixed upstream and pointed to updating to a newer version as likely resolution (read more)

  • 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; topic background: read more)

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)

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)

Activity by the @team 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)

  • martin shipped two notable updates: a new permissions model that distinguishes anonymous vs logged_in_users to replace confusing uses of @everyone (read more), and a merged tweak making Admin Reporting access options clearer in the “Reporting & Analysis” improvements line (read more)

  • Falco unblocked a self-hosted Discourse AI sentiment deployment by recommending a working model branch after upstream HuggingFace assets returned 404s (read more), and also provided concrete guidance for embedding Discourse into Salesforce Experience Cloud (domain alignment vs same_site_cookies) (read more)

  • 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), pointing out that a reported API 500 issue was fixed upstream in newer Discourse versions (read more), and nudging review for a suspected bug in monthly recurring automations (read more)

  • pmusaraj reported that the OpenID Connect group-sync regression is actively being backported and should land in minor releases soon (read more)

  • 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)

  • chapoi confirmed the Chinese-language bug report and shared relevant console output as part of the investigation trail (read more)

Nested replies are on the horizon—so today’s challenge is to keep your threads tidy and your lightbox arrows in order.