Riassunto Settimanale

[Discourse]

This week on meta.discourse.org…

Key Stats

Reporting window: 2026-03-08 → 2026-03-15, as reflected across active threads like the FAQ/Guidelines housekeeping discussion (read more) and late-week UX/browser reports (read more).

• Total new posts: 426
• Total new topics: 72

Top users (posts + likes in the last 7 days)

User	Posts	Likes	Recent reference
Falco	24	50	Cloudflare IP bans explanation (read more)
ToddZ	23	37	Theme-component solution for /groups intro text (read more)
Canapin	16	30	“How old is your forum?” community thread (read more)
LotusJeff	9	29	“How old is your forum?” opener + history (read more)
nat	9	20	Badge i18n deep dive + console workaround (read more)
sam	7	19	OpenAI/Azure “service tiers” announcement (ai, #Announcements) (read more)
awesomerobot	12	17	Form templates multi-template bug + fix guidance (read more)
NateDhaliwal	19	16	“Quick start” self-host install guidance (read more)
merefield	9	15	Dashboard traffic-graph scaling feedback (read more)
Danielle	3	14	Webinar announcement: moderator programs (read more)

---

Interesting Topics

#Announcements

• Discourse AI got OpenAI/Azure “service tier” selection, letting admins trade off cost vs latency vs reliability in provider settings (ai, #Announcements) — read more

• A new webinar was announced: “Creating & Nurturing a Moderator Program” (with a promised replay for registrants) (webinar, #Announcements) — read more

• Hosted AI capacity limits were increased significantly (plus model + throughput improvements), with updated quotas reflected on the pricing page (ai, #Announcements) — read more

blog

• The Discourse team published a detailed write-up on the Upcoming Changes system and how it supports gradual rollouts across varied site configurations (blog) — read more

#Community Building

• A fun and insightful thread asked: “How old is your forum?”—prompting migration histories from Yahoo Groups, phpBB, Ning, vBulletin, and more (#Community Building) — read more

• Cross-platform community ops came up again in a “WhatsApp challenges” follow-up: one practical pattern was capturing key takeaways from chat groups into a shared Discourse category (#Community Building) — read more

• Meta’s evergreen “Discourse is great” energy continued, with community members sharing milestones and encouragement (#Praise) — read more

Support

• A tricky edge case: after merging topics, one post could no longer be marked as the Solved answer—eventually traced to an existing solved record in the original topic and manually repaired, with a fix planned (solved, Support) — read more

• Multilingual admins asked how to localize custom badges and groups; the key takeaway: seeded badges are i18n’d, but custom badges need translation overrides (currently console-dependent) (translation, badges, Support) — read more

• A “forum acquisition” question explored how to bring topics from one Discourse into another without full restore, pointing back to established migration workflows (Support) — read more

• A clean, low-code customization request: adding explanatory text above /g (groups index) was solved with a tiny theme component using After Header + CSS gating (groups, Support) — read more

• Moderator capability boundaries surfaced: moderators can delete users, so the recommended approach for tighter control was Category Moderators + per-category moderator groups (Support) — read more

• A self-hosting anxiety post (“install on my VPS”) turned into a practical mini-guide: one-line installer, backup mindset, and hosted-vs-self-host tradeoffs (#Self-hosting, Support) — read more

• A Onebox/OpenGraph failure that worked on Meta but not on the user’s site ended up being a certificate chain / server-side fetch trust issue, reinforcing that Onebox generation is server-side and sensitive to TLS setup (onebox, Support) — read more

• Admins trying to “require TOS acceptance” used a clever workaround: a required custom user field checkbox to gate saving profile/preferences (Support) — read more

bug

• A dashboard UX/data issue: the Site Traffic graph becomes unhelpful when crawlers dominate, prompting a request for smarter scaling or a “rescale” control (dashboard-reports, bug) — read more

• A content-localization bug: localized tag names weren’t being cleaned/slugified, breaking body classes and tag display; a fix plus migration shipped (content-localization, bug) — read more

• Form Templates: selecting multiple templates per category didn’t persist after refresh due to missing save behavior in a simplified category-creation flow; workaround + merged fix provided (form-templates, bug) — read more

• Discourse v2026.3.0 upgrade pain: discourse-subscriptions failed boot due to a route constant load-order/deprecation edge case; a core PR removed the deprecation point (subscriptions, bug) — read more

• A scary report: using topic timers + schedule publishing in a draft with a missing destination category could spiral into a heavy, “catastrophic” UI state (topic-timers, bug) — read more

ux

• Mobile composer toolbar: when too many buttons exist (often from theme components), later buttons can look “missing”; discussion turned to whether scroll affordances (like arrows) should appear on touch devices (composer, ux) — read more

• On some tablets/browsers, the floating search widget produced bizarre input behavior (reversed character order), eventually linked to a floating keyboard feature (search, Support) — read more

• A login-page polish issue: top logo alignment shifts when language switcher or theme toggle is present (login, ux) — read more

#Plugin / #Theme component

• A notable new plugin: diskuz Call brings peer-to-peer voice/video calls into Discourse using WebRTC (signaling on server, media P2P/TURN) (#Plugin) — read more

• Another plugin showcase: a Discourse Points Mall prototype (check-in, shop, orders, ledger) with candid notes about current bugs and readiness (#Plugin) — read more

• A theme-component tooling thread: Tag Style Tool shipped updates quickly after reports of disappearing UI and Font Awesome SVG subset quirks (tags, #Theme component) — read more

• A no-rebuild alternative to server plugins: Bilibili inline player as a theme component, compared against an existing rebuild-required plugin approach (onebox, #Theme component) — read more

• “Banner Featured Links” got an update to address htmlSafe deprecation and other cleanup, pinned to 2026.3.0-latest (#Theme component) — read more

• The terminal-based Discourse client “termcourse” added MessageBus-powered realtime notifications and began aligning shortcut conventions (experimental, #Extras) — read more

---

Activity by the @team Group

• Falco focused on practical admin fixes and roadmap notes: explained Cloudflare “everyone got banned” IP behavior and the need for the Cloudflare template (read more), confirmed work on a new UI to display full “and N more…” reactions lists (read more), clarified Data Explorer API behavior changes and limits/pagination guidance (read more), expanded hosted LLM capacity limits and model capabilities (read more), and outlined replacements for Google’s discontinued Custom Search integration plus future “native web search tools” support (read more).

• nat delivered several “deep internals” clarifications and fixes: corrected the realities of i18n for custom badges and provided the console-based TranslationOverride approach (read more), investigated localized tag output and shipped a cleanup fix + migration (read more), responded to dashboard traffic-graph scaling feedback with “changes coming” context (read more), and pointed users to the experimental tag settings page for managing translated tags after AI translation (read more).

• sam shipped and discussed multiple AI/automation developer-facing improvements: announced OpenAI/Azure provider service tiers and how to configure them in LLM settings (read more), advanced the “automation pipelines” idea (trigger → filters → actions, observability, extensibility) (read more), responded to upgrade issues around USERNAME_ROUTE_FORMAT with a core PR to remove the deprecation pressure point (read more), and continued triage on AI Search resource usage expectations vs unexpected CPU pressure (read more).

• awesomerobot handled a broad spread of admin UX + bug triage: reproduced and confirmed the multi-form-template persistence bug, suggested a workaround, and followed with a merged fix (read more); investigated toolbar overflow behavior and the “hidden arrow on touch devices” tradeoff (read more); identified a third-party plugin causing “official” components to fail after update and offered safe-mode isolation steps (read more); and suggested structured approaches for gating access via guidelines acceptance using Policy + Automation patterns (read more).

• Danielle coordinated community-facing updates: announced the moderator-program webinar and confirmed recordings will be shared after the session (read more), and helped steer a process for reviewing/updating older FAQ/Guidelines documentation references (read more).

• supermathie provided crisp diagnostics and user-expectation improvements: tested problematic mobile browsers for text-selection UI issues and concluded the most viable path is recommending supported browsers (read more), documented a temporary email regression caused by a gem update (with break/fix commits) for anyone impacted that day (read more), and proposed a UX hint for multisite “guest” admins who can’t access /sidekiq to reduce confusion (read more).

• chapoi engaged on UX polish and dashboard/report behavior: clarified the intent behind the site-traffic Y-axis behavior and agreed it should be smarter in crawler-heavy scenarios (read more), pointed developers to Discourse docs being included directly in the core repo (read more), and confirmed a tablet TOC overlay bug should be fixed by an upstream DiscoTOC PR (read more).

• martin worked on both production troubleshooting and product communication: diagnosed why “mark as solution” can fail after merges (a prior solved record in the old topic) and applied a fix while investigating a preventative change (read more), and published the companion discussion topic for the “Upcoming Changes system” blog post (read more).

• HAWK kicked off a cleanup thread about FAQ/Guidelines link confusion, which quickly evolved into a documentation and process review effort (read more).

• pmusaraj supported Discourse ID troubleshooting: requested backtraces for “can’t alloc thread” signup failures and helped narrow suspicion toward memory constraints / reproducibility via fresh installs (read more), and offered direct cleanup of duplicate redirect-URI credentials as a temporary fix while workflow improvements are in progress (read more).

---

Thanks for reading, and I’ll see you again next week!

[Discourse]

This week on meta.discourse.org…

A busy week on Meta (2026-03-15 → 2026-03-22), with lots of energy around experimental UX (nested replies), developer-facing changes (plugin build tooling + deprecations), and a steady stream of admin/support troubleshooting across hosting, auth, and calendars (see the mega test thread: read more).

---

Key Stats

• New posts: 644
• New topics: 82

Most active / most appreciated users (posts + likes received this week):

User	Posts	Likes
Moin	62	108
Falco	30	111
chapoi	21	33
NateDhaliwal	27	21
darkpixlz	16	29
Lilly	14	44
david	13	60
merefield	13	24
martin	6	27
Canapin	10	44

Conversation drivers worth noting (with sources):

• The nested/threaded replies experiment generated a lot of testing, delight, confusion, and UX ideas in Testing Nested Replies on Meta (and a follow-up UX clarity improvement in UX improvements for deeply nested thread view).
• Plugin authors got a major tooling update with a new plugin JS build system in Introducing a new build system for plugins, followed quickly by a real-world edge case in Plugin “Duplicate export” error after Discourse update.
• A notable end-user feature landed: calendar subscription URLs for external calendar apps in Calendar subscription URLs for external calendar apps.

---

Interesting Topics

#Announcements

• A new Support category type now makes it much easier to set up Q&A flows using Solved defaults (including solution-marking) in Easily create Support categories using the discourse-solved plugin — with follow-up tweaks to defaults and copy discussed in-thread (read more).

• Discourse added Calendar subscription URLs (ICS feeds) directly in user preferences, including bookmarks-with-reminders and optional event feeds when the calendar plugin is enabled: Calendar subscription URLs for external calendar apps.

• March’s “what we’re building” roundup shipped, including AI limit increases and a roadmap-style digest in Current Projects - March 2026.

• A new experimental plugin brings a “Wikipedia-style” workflow for post improvements without granting broad edit rights: Discourse Suggested Edits.

---

Dev

• Plugin authors got a big modernization with caching, ES modules, and precompile opportunities in Introducing a new build system for plugins, and the compiler was soon enabled by default in latest (read more).

• A concrete breakage surfaced quickly — a “duplicate export” error — and got patched fast in Plugin “Duplicate export” error after Discourse update (with fix confirmation in read more).

• Theme/plugin authors got a clear deadline: .js.es6 is now formally on the chopping block in Deprecating .js.es6 file extensions in themes and plugins.

• Handlebars templates are also being phased out in favor of modern .gjs (and tooling exists to automate the transition): Deprecating .hbs file extension in themes and plugins (automation guide referenced here: read more).

• A development-environment edge case with plugin bundling/compilation spurred investigation and mitigation discussion in FIX: Compile missing rollup plugin bundles on demand in development.

• A practical “how do I name these repos?” thread revisited conventions for themes vs theme components vs plugins in Is there a naming convention for theme component projects?.

---

ux

• The review-queue prompt “Is this post something else or spam?” triggered a nuanced UX/wording discussion about binary prompts, dropdown semantics, and grammar ambiguity in “Is this post something else or spam?”.

• A “dismiss” button that isn’t truly dismissing (because the underlying condition persists) raised the broader question of snoozing vs clearing admin notices in Clearing advice doesn’t actually clear it.

• A Discourse ID onboarding concern: the referring site’s identity can feel visually “secondary” compared to Discourse ID itself, especially when local logins are disabled — with suggestions for stronger co-branding in Featuring the referring site’s logo and name more prominently in Discourse ID.

• Meta’s own “Guidelines / FAQ” discoverability prompted discussion about static pages vs topics, restricted categories, and search expectations in Guidelines/FAQ not appearing in search results?.

• Translation/UI layout friction popped up again: German upload placeholder text overflowing its container was reported in German upload text is wider than the image placeholder.

• A small but sharp UI alignment nit: tags and votes sitting too low in the “similar topics” composer popup in Tags are too low in similar topic pop up.

---

#Site feedback

• People couldn’t find the releases site, and the community pushed for better IA/link placement — resulting in quick fixes discussed in Where is the link to the releases? (with changes implemented shortly after: read more).

• Meta’s internal “gardening” continued: closing out fixed bugs more reliably, and even adding automation to close topics after tagging fixed, discussed in Experiment: Collaborative content gardening hub for meta.

• A Try Discourse debate: whether try.discourse.org should ever allow admin-level testing (and why that’s risky) played out in Improving Try.discourse.org and a positive note.

• Meta’s ongoing category reorg kept surfacing edge cases around index topics, click targets, and pin/unpin behavior in Updating how categories are organized on Meta.

---

Support (and #Self-hosting)

• Admins discussed incident response for compromised accounts, including email/password/session management and what should (or shouldn’t) require console access in Dealing with a hacked user account should not require the console (with related admin-email control needs linked here: read more).

• Discourse ID signups failing (with console errors) turned into a plugin-isolation investigation in New users can’t sign up, 404 errors in console.

• Upload-size configuration confusion (nginx config vs container regen vs app.yml) came up again in Maxmum upload size, with the canonical config path referenced in Change the maximum attachment upload size.

• Cloudflare ops folks shared updated real-world WAF/rules guidance and plan limitations (e.g., regex operator availability) in the evergreen guide thread Using Discourse with Cloudflare: Best Practices.

• Free-plan provisioning got stuck for multiple users (“Almost there…”) in Got stuck when creating site.

• Form Templates validation gaps: required: true not being enforced for upload fields was reported in Required: true not enforced for upload field in form templates.

---

#Nested Replies Testing

• Discourse shipped a very experimental nested/threaded topic view plugin for testing, explicitly framed as feedback-on-feel rather than bug reporting: Testing Nested Replies on Meta.

• To reduce “where did the other posts go?” confusion once deep nesting triggers a detached “context view,” a UI clarity pass was proposed and demoed in UX improvements for deeply nested thread view.

---

#Plugins / #Theme component / #Extras

• A new gamification-style plugin for recurring check-ins, leaderboards, and badges dropped in Discourse Daily Challenges.

• A community translation component idea got feedback about packaging/installation expectations (theme skeleton, about.json) in G-Translate - Fast and easy translate you entire Discourse Forum for free.

• Quote Callouts received a significant modernization: Glimmer conversion + rich-text editor support in Quote Callouts.

• Android breakage reports for a mobile nav component were rapidly fixed upstream in F NAV - Mobile Navigation Tabs.

• A new “are folks interested?” thread explored the appetite for an open-source Discourse mobile app template in Releasing a Open Source Forum App for Discourse.

---

#Feature

• People want per-post translation UX that’s less fiddly than highlight→Ask AI→Translate, plus a way to cache/save translations to avoid repeated API spend: Translate post with AI and save translation (building on earlier localization ideas: read more).

• A self-hosting reliability proposal asked Discourse to gracefully handle low disk space during upgrades (pre-clean before pulling images, reduce downtime) in Proposal to gracefully handle low disk space during a Discourse upgrade.

---

bug

• A latest regression report described theme/component update checks failing with “Error cloning git repository” while manual “check for updates” succeeded in All themes reporting a “Error cloning git repository, access is denied or repository is not found” error.

• Upload failures for small GIFs were acknowledged and resolved quickly in I cannot upload a GIF, for a non-descript error appears.

---

Activity by the @team Group

• Falco drove and shaped two of the week’s biggest UX stories: the nested replies testbed in Testing Nested Replies on Meta (later opened to all trust levels in read more) and the new calendar feeds feature in Calendar subscription URLs for external calendar apps (including follow-up on filtering expectations: read more). He also engaged with AI translation workflow tradeoffs in Translate post with AI and save translation and committed to tackling a Patreon API v2 update soon in Upgrade Patreon Discourse Plugin to API v2.

• david shipped core developer-facing changes: the rollout and default enabling of the new plugin build pipeline in Introducing a new build system for plugins (enabled by default here: read more), plus clear “time to migrate” notices in Deprecating .js.es6 file extensions in themes and plugins and Deprecating .hbs file extension in themes and plugins. When a regression hit plugin authors, he delivered a fix quickly in Plugin “Duplicate export” error after Discourse update, and also dug into dev-environment compilation timeouts in FIX: Compile missing rollup plugin bundles on demand in development.

• chapoi focused on “make things smoother” improvements across product and support: he implemented better discoverability for the releases site in Where is the link to the releases?, advised on theme/component modernization patterns in Templating of my “component” broke. How do I fix it?, and added automation to reduce “fixed but still open” backlog in Experiment: Collaborative content gardening hub for meta. He also shipped/confirmed fixes for UI/components in Subcategories and Categories with no subcategories don’t show views/reply counts and table-builder tablet layout issues in Huge gap below tables on tablets.

• martin continued the “simplify admin setup” push with the Support-category defaults announcement in Easily create Support categories using the discourse-solved plugin and follow-up clarifications/UX tweaks in read more. He also addressed a regression around toggling Solved per-category in Unable to disable the solved feature for categories after it has been enabled (merged update noted here: read more).

• markvanlan iterated rapidly on the nested replies prototype, contributing hands-on UX analysis inside the main testing hub Testing Nested Replies on Meta and then proposing clearer “detached thread” affordances in UX improvements for deeply nested thread view.

• awesomerobot weighed in on UX wording and moderation review semantics in “Is this post something else or spam?”, clarified team norms around naming conventions in Is there a naming convention for theme component projects?, and reinforced guardrails around agent-like automation acting as users in Discourse官方会出个官方的openclaw skill么？. He also patched a small but confusing AI-related string issue in Why is ‘Default LLM’ repeated in the error message about enabling chat for an agent?.

• pmusaraj helped troubleshoot Discourse ID onboarding and configuration issues in New users can’t sign up, 404 errors in console, culminating in pragmatic advice about plugin isolation even when “disabled” in read more. She also engaged UI/branding improvement requests for Discourse ID in Featuring the referring site’s logo and name more prominently in Discourse ID and clarified Free-plan constraints around privacy/categories in You’re invited to try the Discourse Free plan beta!.

• mcwumbly acted as a product “edge-case magnet” (in the best way), surfacing usability gaps in the new docs/category experience in What should the homepage be for doc categories? and pinpointing click-target issues in Meta’s category reorg thread Updating how categories are organized on Meta. He also provided early feedback and testing notes inside the nested replies sandbox in Testing Nested Replies on Meta.

• sam introduced a new experimental collaboration workflow plugin in Discourse Suggested Edits, clarified localization expectations for PR authors in If a PR needs localization what do we do?, and supported investigation into moderation tooling issues in Bug when trying to split as well as chat-related bug reports in 聊天功能被禁用后，其设置消失。.

• lindsey published the team’s monthly roadmap-style update in Current Projects - March 2026 and followed up on translation workflow questions raised in-thread (read more).

---

Thanks for reading, and I’ll see you again next week!