# Resumen diario (5am UTC) **URL:** \ **Category:** Forum summaries\ **Created:** [16 Enero, 2024 21:58 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851 "2024-01-16T21:58:09Z")\ **Posts on this page:** 1\ **Showing post:** 823
**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:** [4 Mayo, 2026 05:01 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/823 "2026-05-04T05:01:26Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 47 - **New topics (last 24h):** 2 — [“Case study of an amateur plugin author”](https://meta.discourse.org/t/-/402084/1?silent=true), [“Этот файл слишком большой”](https://meta.discourse.org/t/-/402101/1?silent=true) ### 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](https://meta.discourse.org/t/-/401984/30?silent=true)). A related legal nuance was raised around whether infinite scroll is a “significant part of the services” in the context of regulation ([read more](https://meta.discourse.org/t/-/401984/31?silent=true)). * * * ### #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](https://meta.discourse.org/t/-/402101/1?silent=true)). @Canapin pointed to the canonical guide for adjusting upload limits ([read more](https://meta.discourse.org/t/-/402101/4?silent=true)), while @merefield emphasized that you often must update `app.yml` **and** have SSH/terminal access to complete the rebuild properly ([read more](https://meta.discourse.org/t/-/402101/6?silent=true)). - 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](https://meta.discourse.org/t/-/402101/14?silent=true), [read more](https://meta.discourse.org/t/-/402101/28?silent=true)). The thread ultimately surfaced a common pitfall: stopping `./launcher rebuild app` partway through (visible via `^C`) and then wondering why the site won’t boot ([read more](https://meta.discourse.org/t/-/402101/22?silent=true), [read more](https://meta.discourse.org/t/-/402101/29?silent=true)). - Several replies reinforced the practical “next step” of pasting full terminal output in code blocks to diagnose failures ([read more](https://meta.discourse.org/t/-/402101/20?silent=true), [read more](https://meta.discourse.org/t/-/402101/21?silent=true)). For anyone following along later, the underlying reference docs were again the “change maximum attachment upload size” guide ([read more](https://meta.discourse.org/t/-/26435/1?silent=true)). - 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](https://meta.discourse.org/t/-/402101/24?silent=true), [read more](https://meta.discourse.org/t/-/402101/25?silent=true)). * * * ### #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-passed` rather than an ESR channel ([read more](https://meta.discourse.org/t/-/402084/1?silent=true)). @Moin suggested the breakage might be tied to an Ember deprecation-handler crash rather than immediate plugin code rot ([read more](https://meta.discourse.org/t/-/402084/2?silent=true)), linking the known issue: [“Ember this fallback deprecations crash in the deprecation handler”](https://meta.discourse.org/t/-/401927/1?silent=true). - 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](https://meta.discourse.org/t/-/402084/3?silent=true)). The discussion also nodded to Discourse’s evolving release strategy (referenced via the versioning RFC) ([read more](https://meta.discourse.org/t/-/383536/1?silent=true)). * * * ### #customization: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 `DiscoveryTopics` doesn’t pass the `canLoadMore` model property through to the `LoadMore` component—making the issue _not fully solvable_ in a theme component alone ([read more](https://meta.discourse.org/t/-/402049/9?silent=true)). - 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](https://meta.discourse.org/t/-/402049/10?silent=true), [read more](https://meta.discourse.org/t/-/402049/11?silent=true)). * * * ### #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](https://meta.discourse.org/t/-/402100/1?silent=true)). * * * ### #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](https://meta.discourse.org/t/-/401961/7?silent=true)). 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](https://meta.discourse.org/t/-/401961/8?silent=true)). * * * ### #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](https://meta.discourse.org/t/-/401602/38?silent=true)). 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](https://meta.discourse.org/t/-/401602/36?silent=true), [read more](https://meta.discourse.org/t/-/401602/37?silent=true)). - 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](https://meta.discourse.org/t/-/401602/38?silent=true), [read more](https://meta.discourse.org/t/-/401602/39?silent=true)). * * * ### #customization: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](https://meta.discourse.org/t/-/103632/321?silent=true)). - 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](https://meta.discourse.org/t/-/97376/576?silent=true)). @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](https://meta.discourse.org/t/-/97376/577?silent=true)). * * * ### #customization: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](https://meta.discourse.org/t/-/401889/18?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **No posts were attributed to the [@team](https://meta.discourse.org/groups/team?silent=true) (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](https://meta.discourse.org/t/-/401984/30?silent=true)) and the self-hosting recovery journey after interrupted rebuilds ([read more](https://meta.discourse.org/t/-/402101/29?silent=true)). - If a staff response does land later, likely candidates for resolution/triage include the Meta logo rendering anomaly report ([read more](https://meta.discourse.org/t/-/402100/1?silent=true)) and the remaining regressions/UX questions in the AI docked composer (#composer #ai) ([read more](https://meta.discourse.org/t/-/401961/8?silent=true)). * * * _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._ --- _[View the full topic](https://meta.discourse.org/t/daily-summary-5am-utc/291851)._