每日摘要（UTC早上5点）

新闻和活动 论坛摘要
820

Today on meta.discourse.org…

Key Stats

  • New posts (last 24h): 72
  • New topics (last 24h): 8

Top users (posts / likes received in the last 24h):

User Posts Likes
chapoi 4 17
Falco 5 14
Jonathan5 1 8
Moin 7 7
david 2 4
codixer 2 3
cedric_chin 2 3
bksubhuti 6 2
Lilly 5 2
nathank 4 2

A few themes popped repeatedly: infinite scroll vs. “bottomlessness” (read more, read more), post-upgrade admin warnings and odd notification behavior (read more), and AI-related UX/bug reports (read more, read more, read more).

Interesting Topics

General

  • mcmcclur challenged Discourse’s topic-list infinite scroll as potentially enabling addictive use, while chapoi argued the real harms come from algorithmic engagement mechanics rather than “scroll” itself (read more). Related: the practical “footer is unreachable” admin problem in Support (read more).

Support

  • A large migration hit an ergonomics snag: infinite scrolling makes the homepage footer inaccessible; chapoi confirmed pagination isn’t on the roadmap and suggested a custom landing page, while others discussed alternatives like category-based homepages and the limits of footers on /latest (read more). For theme-based footer approaches, see the Easy Responsive Footer component (read more) and the “old-forum UI” experiment Dumbcourse (read more).

  • A puzzling [Admin Notice] “code needs updating (id: discourse.user.userOptions)” appeared alongside strange category-notification behavior; Moin recommended isolating which customization triggers the warning (console/errors, plugins/components list), while the OP dug into app.yml and plugin references (read more). Related context: plugin bundling guidance mentioned by Lilly (read more).

  • Admins trying to customize the unsupported browser banner discovered an edge case: if the string lives under js.*, old browsers that don’t run JS won’t load customized strings—so the default message persists (read more). Customizing site text generally is covered here (read more).

  • The “Enabling YJIT via template doesn’t work” thread concluded with a clean root-cause: sudo -u discourse was scrubbing environment variables, and using sudo -E preserved RUBY_YJIT_ENABLE so YJIT correctly reported as enabled (read more).

  • A Chinese-language support question asked why permanent deletion reports “0 posts need to be permanently deleted before the topic itself can be permanently deleted”—highlighting the sometimes confusing multi-step nature of permanent deletion workflows (read more). Related: documentation clarity feedback on the “enable permanent delete” safeguards (read more).

bug

  • Chat pings issue: a reported ping problem got quick staff confirmation and a fix shipped via a core PR (read more).

  • Plugin/theme authors hit failures after toolchain changes: ember-this-fallback deprecation modules were missing and injected references made debugging harder; david confirmed hbs should still work and merged a fix (with backport planned) (read more). One concrete example surfaced in a theme thread: FKB Pro Social Theme error reference (read more).

  • The new AI docked composer was reported as blocking edits, behaving oddly with quoting, and becoming scroll-locky on mobile; sam noted work in progress and pointed to an imminent update from keegan (read more).

  • Moderation edge case: a flagged first post was hard to restore after the author was pushed to trust level 0—restoration failed until the user was restored to a level allowed to create topics, prompting a request for better admin feedback (read more).

  • AI Helper “proofread” behavior: users flagged that “proofread” must not alter quoted text; staff pointed to a fix already landed, with guidance to try a better model if issues persist (read more).

#Site-Management

  • A new how-to shows how to auto-categorize topics using AI triage by combining the Discourse AI plugin with Discourse Automation, including agent/system-prompt suggestions and setup prerequisites (read more). Background links: Discourse AI overview (read more), Automation plugin (read more), LLM settings guide (read more), and AI personas/agents (read more).

  • Form templates UX: a request asked whether copy/paste can be enabled inside form-template text inputs, to match the normal composer experience; staff asked for clarification on the exact limitation and desired behavior (read more).

  • “Read only mode” UI confusion: a user reported the Backups UI no longer shows the disable option, while staff said the enable/disable buttons appear normally and asked for a screenshot to diagnose (read more).

#Announcements

  • Discourse’s embedded comments capability prompted questions about whether it competes with Disqus; Falco confirmed it’s intended for that space (including use on the free plan) and highlighted private-community + public-blog use cases (read more).

  • Calendar subscription UX: real-world usage showed people copy the first subscription URL (often “Bookmarks”) and then complain events don’t appear, prompting a request to reorder options; a workaround was implemented in a related theme component snippet (read more, read more).

Activity by the @team Group

  • chapoi focused on “infinite scroll” concerns—separating mechanism vs. harm and emphasizing Discourse’s non-algorithmic, chronological lists (read more); and also gave a clear roadmap answer (“no”) plus workaround suggestions for the footer/pagination request (read more). chapoi also contributed to the age/identity discussion with nuance around anonymity, accountability, and real-world safety risks for minors (read more).

  • Falco delivered multiple “here’s the fix” moments: confirming a ping bug was fixed in core (read more), resolving a YJIT environment-variable misconception with Ruby-level documentation pointers (read more), clarifying why customized js.* strings don’t apply in truly old browsers where JS is disabled (read more), pointing to the “proofread breaks quotes” fix (read more), and answering questions about embedded comments competing with Disqus (read more).

  • david investigated and shipped a fix for the ember-this-fallback deprecation handler crash, confirming expected compatibility and linking to the merged PR/backport plan (read more, read more).

  • lindsey acknowledged the ping issue report and confirmed it was reproducible for staff, teeing up the subsequent fix (read more).

  • HAWK added perspective to the age/verification debate, arguing that communities avoiding identity checks may become increasingly bot-prone—and explicitly endorsed chapoi’s framing of the underlying safety problem (read more).

  • awesomerobot pressed for sources in the infinite-scroll addictiveness discussion, prompting research links and tightening the thread’s evidentiary basis (read more).

  • sam acknowledged the AI docked composer bug report and noted active work underway, with an upcoming update from keegan (read more).

Yesterday’s meta was a perfect blend of doomscroll discourse and YJIT detective work—may your footers stay visible and your env vars never get scrubbed.