ملخص يومي (الساعة 9 مساءً بتوقيت UTC)

الأخبار والأحداث ملخصات المنتديات
851

Today on meta.discourse.org…

Key Stats

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

Interesting Topics

#Theme component

  • darkpixlz shipped Modern User Card, reviving the older experimental user card UI—then immediately ran into follow-up work around the component-template-resolving deprecation warning, with Lilly jumping in to help investigate. read more (see also: the original experiment here and the deprecation thread being referenced here)

  • The Load More Button component continued to surface an underlying core limitation/bug (with DiscoveryTopics not passing canLoadMore), and discussion shifted toward practical workarounds (CSS hiding) versus “this needs core support.” read more

#Site feedback

  • A visual glitch report: ondrej spotted a weird/garbled Meta logo that normalizes when zooming in, but breaks again at default zoom—likely pointing to a rendering/scaling issue across browsers. read more

development

  • jericson posted a reflective case study on learning Discourse plugin development “as an amateur”, connecting the dots between a real client need (a contact form for anonymous visitors), the official plugin tutorial path, and the end result. read more (background links referenced in-thread include: the “not possible?” discussion here, the plugin dev tutorial here, and the resulting contact form plugin topic here)

#Self-hosting

  • A Russian-language support thread escalated from “file too large (even 2MB videos)” into rebuild troubleshooting: guidance centered on aligning container/nginx limits (app.yml) with site settings, and the need for SSH access to rebuild reliably. read more (the key doc being pointed to: Change the maximum attachment upload size)

Support

  • A solved how-to: forcing exact characters on a single line (with a live counter and customizable styling) wrapped up cleanly once the right approach landed. read more

  • The ongoing age requirement / youth accountability discussion kept branching into what platforms can enforce versus what’s realistic (and where responsibility should sit). read more

General

  • The “infinite scroll” debate got a terminology reset: participants emphasized that Discourse’s scroll is pagination replacement (finite content), not “infinite content feeds” like social media—plus some legal framing discussion on what counts as a “significant part of the services.” read more

  • In show-and-tell, kirupa shared an update on populating a mostly-dead forum with bots, including publishing the full source code so others can adapt the approach. read more

#Announcements

  • The Foundation theme modernization thread saw another small but telling UI detail: a gap/spacing issue under the “Related” button (especially with larger fonts). Lilly suggested a targeted padding/line-height patch and flagged it as a UX clash with an injected AI-related button. read more

bug

  • The new AI docked composer looks improved overall, but Lilly reported a sharp regression: file uploads appear to break after the first post, keeping the bug thread active. read more

#Plugin

  • In the official openid-connect thread, a practical ops question came up: will users be automatically removed from groups when they’re no longer members in the identity provider? read more

  • The official Discourse Calendar (and Event) plugin thread continued with feature-scope discussion: interest in a more complete, configurable event management system—and some candid notes on which AIs are being used for coding assistance. read more

  • The Telegram Notifications plugin thread saw UI/option confusion (screenshots + “no such option”), suggesting either documentation drift or a UI/settings mismatch between versions. read more

#Extras

  • SuperHref shipped an update: suggested products can now keep the original affiliate tag or swap in a custom one—useful for operators trying to preserve monetization while improving link hygiene. read more

Activity by the @team Group

  • Lilly collaborated with darkpixlz on next steps for the Modern User Card theme component, including diagnosing the component-template-resolving warning and setting expectations about refactoring needs. read more and read more

  • Lilly noted a potential workaround/fork for an edge case in Load More Button, while agreeing the approach is “hacky” and limited by core behavior. read more

  • Lilly provided a concrete CSS patch suggestion for a spacing/UX issue in Modernizing the Foundation theme, tying it to a mismatch between button classes and an injected AI-related UI element. read more

  • Lilly added a key regression report to New ai docked composer: uploads appear broken after the first post, even if the composer is otherwise “much less buggy.” read more

If yesterday proved anything, it’s that Discourse scroll isn’t truly infinite—but the community’s capacity to debug UI quirks and resurrect forums with bots might be.

Daily Summary Feedback