Today on meta.discourse.org…
Key Stats
- New posts (last 24h): 47
- New topics (last 24h): 2 — “Case study of an amateur plugin author”, “Этот файл слишком большой”
Top users (posts & likes in the last 24h)
| User | Posts | Likes |
|---|---|---|
| merefield | 6 | 3 |
| Heliosurge | 5 | 3 |
| Lilly | 4 | 3 |
| darkpixlz | 2 | 1 |
| bloomexperiment | 1 | 8 |
| Jonathan5 | 1 | 4 |
| Moin | 1 | 3 |
| ondrej | 1 | 2 |
| piffy | 1 | 2 |
| NateDhaliwal | 1 | 1 |
Interesting Topics
General
-
bloomexperiment argued that Discourse’s “infinite scroll” is being conflated with “infinite content”—highlighting that Discourse and email clients can scroll without end only within a finite set of chosen content, unlike algorithmic feeds (read more). A related legal nuance was raised around whether infinite scroll is a “significant part of the services” in the context of regulation (read more).
“The scroll in Discourse replaces pagination. Just like pagination, it is not infinite.” (source)
#Self-hosting
-
A new admin troubleshooting thread (in Russian) tackled why even tiny video uploads were failing with “This file is too large” (read more). Canapin pointed to the canonical guide for adjusting upload limits (read more), while merefield emphasized that you often must update
app.ymland have SSH/terminal access to complete the rebuild properly (read more). -
As the rebuild progressed, the discussion shifted from “how do I increase upload limits?” to “how do I recover a broken instance?”—with repeated reminders not to interrupt rebuilds mid-flight and to share actual logs instead of screenshots (read more, read more). The thread ultimately surfaced a common pitfall: stopping
./launcher rebuild apppartway through (visible via^C) and then wondering why the site won’t boot (read more, read more). -
Several replies reinforced the practical “next step” of pasting full terminal output in code blocks to diagnose failures (read more, read more). For anyone following along later, the underlying reference docs were again the “change maximum attachment upload size” guide (read more).
-
The “can someone log into my server and fix it?” moment also appeared; community members cautioned that hands-on recovery is typically paid work and pointed toward professional options (read more, read more).
development
-
A reflective post on plugin maintenance described a plugin failing to load (missing module import) and the author’s surprise at being hit early due to tracking
tests-passedrather than an ESR channel (read more). Moin suggested the breakage might be tied to an Ember deprecation-handler crash rather than immediate plugin code rot (read more), linking the known issue: “Ember this fallback deprecations crash in the deprecation handler”. -
The thread then turned into a broader “maintenance in 2026” conversation: piffy explained that agentic coding dramatically reduced the pain of modernizing older plugins—turning multi-week updates into minutes—and described how that changed their willingness to keep sites updated (read more). The discussion also nodded to Discourse’s evolving release strategy (referenced via the versioning RFC) (read more).
#Theme component
-
The “Load More Button” theme component thread exposed a subtle UX discrepancy: the “Load more” UI can appear when it shouldn’t, because core’s
DiscoveryTopicsdoesn’t pass thecanLoadMoremodel property through to theLoadMorecomponent—making the issue not fully solvable in a theme component alone (read more). -
The community explored pragmatic workarounds, like conditional CSS hiding for specific contexts (e.g., logged-out landing pages), and Lilly mentioned a fork that handles the edge case (even if the approach is “hacky”) (read more, read more).
#Site feedback
- A small but intriguing UI report: ondrej saw a “weird logo” rendering across browsers at normal zoom, which corrected itself when zooming in—suggesting a scaling/rendering artifact rather than a broken asset (read more).
bug ( composer ai )
- Feedback continued on the new AI docked composer, with Lilly reporting that it’s “much less buggy” overall, but still appears to break file uploads after the first post (read more). Later, they summarized remaining issues (quoting doing nothing; uploads failing after first post) and called out a UX inconsistency: needing Shift+Enter for a newline compared to the regular composer (read more).
Support
-
The “Age requirement for Discourse” thread kept evolving into a broader policy-and-parenting discussion. Heliosurge challenged whether ID checks are even the right lever, leaning instead toward accountability models and parental responsibility (read more). The conversation also detoured into a comparison of legal enforcement vs cultural norms (with a bicycle helmet law example contrasting Canada and the Netherlands) (read more, read more).
-
The “what actually works” angle came through in practical examples: device-level controls, restricted OS accounts, and the human reality that kids often defeat weak passwords unless parents adopt better operational habits (read more, read more).
#Plugin
-
In the long-running official OpenID Connect plugin thread (official openid-connect auth-plugins included-in-core), Steradiant asked a concrete operational question: whether users will be automatically removed from Discourse groups once they’re no longer members of the corresponding IdP group (read more).
-
In the Discourse Calendar (and Event) plugin topic (official calendar-and-event included-in-core), feature direction came up again: a desire for more complete event management with toggles for optional modules—reducing the need to stack multiple plugins for common “events” requirements (read more). oshyan replied with implementation intent (configurable functions via settings) and shared tooling preferences for building: using both OpenAI Codex and Anthropic Claude directly (plus “MCPs and skills”) rather than wrappers like Cursor (read more).
#Extras
- The SuperHref project announced a monetization/UX improvement: suggested products can now keep the original affiliate tag or replace it with a custom one—useful for sites that want link-replacement benefits without losing attribution control (read more).
Activity by the @team Group
-
No posts were attributed to the @team (Discourse Team) group in this 24-hour snapshot. The most active threads were nonetheless worth tracking for follow-ups and potential staff input—particularly the policy/UX debate around “infinite scroll” (read more) and the self-hosting recovery journey after interrupted rebuilds (read more).
-
If a staff response does land later, likely candidates for resolution/triage include the Meta logo rendering anomaly report (read more) and the remaining regressions/UX questions in the AI docked composer (composer ai) (read more).
That’s all for today—may tomorrow’s scroll be finite, your logos crisp, and your ./launcher rebuild app run to completion without a single Ctrl+C.