每日总结（UTC下午1点）

新闻和活动 论坛摘要
780

Today on meta.discourse.org…

Key Stats

  • New posts (last 24h): 82 — conversation clustered around release visibility, UX details, and plugin/dev workflows (e.g. read more, read more, read more).
  • New topics (last 24h): 7 — including new support questions like hiding staff from /about (read more) and making an “Announcements” category effectively read-only on the free plan (read more).

Top users (posts/likes in the last 24h, with an example jump-in):

User Posts Likes Reference
Falco 3 29 Pointed to context on the “33 security fixes” discussion (read more)
Moin 11 18 Suggested “require approval” as a free-plan workaround for read-only categories (read more)
david 3 13 Explained the release comms change + raised the feedback internally (read more)
merefield 2 12 Reacted to the release thread and noted the “AI getting some credit” angle (read more)
zogstrip 5 11 Dropped PR links for bug fixes (example: whispers bumping) (read more)
Ed_S 4 10 Raised concern about “stealth” security releases & missing Announcement pointers (read more)
nathank 10 10 Walked through /about group-hiding mechanics and alternatives (read more)
asc 3 5 Proposed weekly/interval-based check-ins for Daily Challenges plugin (read more)
NateDhaliwal 4 4 Asked clarifying questions re: hiding users vs hiding groups on /about (read more)
R23D_Printing 3 4 Confirmed feature interpretation and explored mod-level creation for challenges (read more)

More threads with fresh replies worth a glance:

  • Translation tooling background jobs temporarily impacted string context features (read more)
  • Watched-words auto-tagging fix reminder: “update when you are able” (read more)
  • Reporting permissions still evolving (“Staff only” / “No one” options planned) (read more)
  • Marketplace: paid request for Kajabi ↔ Discourse integration + migration (read more)
  • Anonymous mode visibility mockups for composer + banner UI (read more)
  • ActivityPub plugin version check-in from a running install (read more)
  • Theme component maintenance chatter (“Classic About Statistics”) (read more)
  • Theme component fix notes for prefilled composer link generator (read more)
  • Plugin warning after update: discourse-formatting-toolbar needs code updates (read more)
  • Horizon/UX: sticky category header tradeoffs discussed in the older thread too (read more)
  • A “Modern Theme” March update landed with DM support and various UI fixes (read more)
  • A longstanding “mail-receiver” how-to gained a Cloudflare/TLS deep dive + caveats (read more)

Interesting Topics

Support

  • Ed_S raised alarm that v2026.3.0-latest.1 shipped with “33 security fixes” yet felt “stealthy” due to fewer Announcement pointers; Falco linked background, and david acknowledged the pain around visibility + said the feedback was raised internally (read more, read more, read more). Follow-up context included the newly posted/backdated release pointers (read more, read more) and references to older “dashboard advice” confusion (read more) and version-notification oddities (read more).

  • A site owner asked for a built-in way to remove the default @moderators section from /about (without CSS/theme work). The thread dug into what about_page_hidden_groups actually hides, and how to keep staff access without listing everyone publicly (about-page) (read more, read more). A notable possible extension was using dynamic group membership to hide “trainee mods” as a set (read more).

  • On the free hosted plan, Naoshi wanted an “Announcements” category where only staff can create topics, but everyone can reply. Moin suggested a pragmatic workaround: enable approval for new topics in that category and simply don’t approve non-staff topics (free-plan categories) (read more, read more).

#Self-Hosting

  • The long-running mail-receiver guide got a very practical Cloudflare-focused addendum: why Cloudflare proxying blocks SMTP, the need for a separate inbound-mail hostname, and how to do Let’s Encrypt via DNS challenge for TLS. The discussion also surfaced risks around exposing origin IPs when adding a DNS-only record (read more, read more, read more).

#Plugin

  • “Discourse Daily Challenges” drew feature requests for non-daily intervals (e.g. weekly check-ins) and letting mods/category mods create challenges instead of requiring admins. The back-and-forth clarified expectations like “1 entry per week across a month” and even referenced Calendar’s configurable week start (gamification, tangentially) (read more, read more, read more).

  • The diskuz Call plugin (P2P voice/video inside Discourse) got a strong +1, plus a request to consider group calls / meetings as a next step (#experimental-ish in spirit, even if not tagged that way) (read more).

Dev

  • A long-awaited improvement landed: an “icon type” SiteSetting exists now. The thread quickly turned into “this will make updating theme components easier”, and it also connected to real-world fallout like FontAwesome icon availability and free/regular fallbacks (with the Reactions plugin cited as benefiting) (read more, read more, read more).

  • Work continued on a new build system for plugins, with david announcing a public talk at Ember Europe for those who want the architectural overview and rationale (dev-news) (read more).

bug

  • “Impossible to prevent x.com oneboxes (and they’re broken)” got a clear “will be fixed by PR” response, continuing the ongoing efforts to keep oneboxing reliable and configurable (onebox) (read more).

  • A new report: Chat plugin fails to compile when the rollup plugin compiler is enabled by default, with a concrete error trace pointing at _assert is not a function (chat) (read more).

  • “Whispers only temporarily bump topics” progressed toward a fix, while still surfacing a philosophical split: some want any staff-visible activity to bump, others want no bump because “nothing happened” publicly (whispers) (read more, read more).

ux

  • The Horizon theme’s sticky category heading became a mobile pain point: what’s “lovely on desktop” can crowd the topic list on small screens. chapoi noted it’s an unintended side-effect of keeping navigation visible, and invited others to investigate a cleaner solution (horizon-theme mobile pr-welcome) (read more, read more).

Community Building

  • In the long-running “comment platform viability” conversation, Falco announced Discourse’s own blog comments were swapped over to a new embedded-topic commenting system, with early feedback already noting theme/padding/light-vs-dark mismatches and the plan to iterate via a theme component first (read more, read more, read more).

Nested Replies Testing

  • More hands-on feedback landed in the “Testing Nested Replies on Meta” sandbox: users called out how notifications/flat view can make it hard to know which “nested chunk” a reply belongs to, and suggested adding “parent comment” affordances (LiveJournal-style) to improve orientation (read more, read more).

Marketplace

  • A new paid request asked for a developer to integrate Discourse with a Kajabi membership site, including migration, tiered access automation, branding, and replacing Disqus-style comments—explicitly aiming for Facebook-like simplicity on the front-end while keeping Discourse power behind the scenes (read more).

Activity by the @team Group

  • Falco helped contextualize the sudden “33 security fixes” concern and engaged on release visibility expectations (read more), and also announced that Discourse’s blog comments are now running on a new embedded Topic-based system and invited feedback (read more).

  • david responded directly to the release-visibility feedback, apologized for the long-unnoticed email issue, and said the team is discussing adding Meta pointers back into Announcements; he also linked the newly posted/backdated release announcement topics (read more, read more, read more, read more). He additionally shared a public talk slot about the plugin build system (read more).

  • zogstrip continued the “here’s the PR” style of bug-triage updates across multiple threads—whispers bumping behavior (read more), x.com onebox breakage/config limitations (read more), topic timer instability (read more), and the discard-confirmation modal annoyance when approvals are involved (read more).

  • gerhard explained why translation context lookup could be temporarily degraded: a background job was running to backfill AI-generated context, expected to settle within about a day (read more).

  • nat posted a quick status update that the watched-words auto-tagging issue had already been fixed and encouraged updating when possible (read more).

  • martin noted an upcoming refinement to reporting/share options—adding clearer “Staff only” / “No one” choices since “Everyone” doesn’t map well to certain report behaviors (read more).

  • chapoi weighed in on the Horizon theme sticky heading issue, framing it as an unintended side effect of keeping navigation visible and inviting community PRs if someone can disentangle the containers cleanly (read more).

Yesterday’s Meta energy was peak “blink and you’ll miss it”: stealthy security-fix releases on one side, and shiny new embedded blog comments on the other—keep one eye on your dashboard and the other on the comment box.