Today on meta.discourse.org…
Key Stats
- New posts (last 24h): 74
- New topics (last 24h): 16
Top users (posts / likes received in the last 24h)
(Links go to a recent post from each user as a reference.)
| User | Posts | Likes | Recent highlight |
|---|---|---|---|
| david | 5 | 23 | Deprecations: .js.es6 and fixes for plugins (read more) |
| Moin | 8 | 10 | Tracked an API key error down to a plugin (read more) |
| Falco | 4 | 15 | Shipped new calendar subscription URLs (read more) |
| LeoDavidson | 3 | 5 | Reported a plugin build issue and confirmed the fix (read more) |
| markvanlan | 1 | 5 | Improved clarity for deeply nested thread “context view” (read more) |
| gilles | 3 | 4 | Reported Android breakage tied to a theme component (read more) |
| Don | 1 | 3 | Merged a fix for the F-NAV Android issue (read more) |
| awesomerobot | 1 | 3 | Fixed awkward “Default LLM” duplication in AI UI errors (read more) |
| ganncamp | 1 | 2 | Shared assignment API endpoint gotchas + solution (read more) |
| satonotdead | 2 | 2 | Added to the nested replies testing chatter (read more) |
Interesting Topics
#Announcements
-
Discourse introduced calendar subscription URLs so people can subscribe to forum-based reminders/events in external apps (Google/Apple/Outlook) via a new Preferences → Calendar tab (read more). Related context: it builds on the calendar-and-event ecosystem, including the discourse-calendar plugin, and comes alongside ongoing ICS export refinements (read more) plus real-world event-creation gotchas (read more).
-
The March “Current Projects” thread continued with questions about how translations should be contributed (Crowdin vs PR workflow), with a promise of follow-up from the team (read more).
Dev
-
Discourse is formally deprecating
.js.es6in themes/plugins and plans to remove support after the next ESR—migration is simply renaming files to.js(read more). -
Discourse is also deprecating
.hbstemplates, encouraging migration to.gjsfor better tooling and future performance gains (read more). For folks upgrading existing code, the team pointed to automation guidance (read more). -
A real-world “it broke after updating” report landed quickly: a plugin hit a Rollup “Duplicate export” compile error after upgrading to
2026.3.0-latest, and a core fix was shipped and confirmed working (read more). This also tied back into the broader shift described in the new plugin build system announcement (read more). -
A dev asked (in French) how to make rich text “interpret” HTML instead of showing it, and the guidance was effectively: prefer Markdown, because only a small subset of HTML is accepted/safe (read more).
#Nested Replies Testing
-
Work continued on making deeply nested conversations feel “lovely”: after ~10 nesting levels Discourse switches into a dedicated “context view,” and new styling aims to make that state much more obvious (read more). The change was demonstrated against the ongoing nested replies mega-test thread (read more).
-
The main nested-replies test thread also raised usability questions like whether a user’s Top/New/Old sorting preference can persist across visits (read more).
#Feature
-
A feature request proposed a smoother “Translate” affordance (especially on mobile) and a cost-saving idea: store AI translations so the first translation can be reused instead of re-billing the API 100 times (read more). This was linked to earlier discussion about saving AI translations for localization workflows (read more).
-
For auth setups, a request asked for parity with OAuth2’s “email verified” toggle: admins want an option to disable email verification when using OIDC too (read more).
#Data & reporting
- A new thread asked for Discourse’s Data Processing Agreement (DPA) and details on how contact data is stored, retained, and shared—community replies pointed toward existing legal/privacy pages and prior Meta discussion (read more; older reference: read more).
Support
-
A self-hoster hit an API key creation page exception referencing
:dumbcourse_base_path; troubleshooting quickly fingered the “dumbcourse” plugin, and removing it resolved the issue (read more). The suspected plugin is discussed here (read more). -
On hosted (free) sites, admins debated what the dashboard label “last month” actually means: previous calendar month vs rolling last ~30 days. The thread includes evidence it behaves like a rolling window and suggestions that the label should reflect that more clearly (read more).
-
Patreon integration got attention from two angles: a long-running request to update the Patreon plugin to API v2 got an “I’ll take a stab next week” commitment (read more), while a hosted customer reported Patreon group membership not syncing reliably (including a manual sync button that appears to do nothing) (read more).
bug
-
A bug report showed that when an Update request fails, the Update button duplicates, quickly becoming “literally unusable” (read more).
-
A Chinese-language bug report described a confusing flow where attempting to permanently delete a post before the 5-minute window elapses can result in the post appearing to restore itself, forcing a second delete + wait (read more).
-
Another UX/bug papercut: when a user has a post pending approval, clicking “New Post” can trigger a discard confirmation modal, falsely implying the pending content will be lost. Others confirmed the confusion and suggested the UI needs refinement (read more).
Activity by the @team Group
-
Falco shipped the new external calendar subscription URLs experience (with one-click subscribe options) in #Announcements (read more), and also gave quick feedback that the nested “detached thread” styling looks clear (read more). On the integration front, Falco committed to taking a run at the Patreon API v2 update next week and asked for testing credentials/process (read more).
-
david posted two major dev-facing notices: deprecating
.js.es6in themes/plugins (read more) and deprecating.hbstemplates in favor of.gjs, including ESR timing expectations (read more). david also jumped on a breaking plugin build report and linked the fix that resolved the “duplicate export” error (read more), then cross-referenced that resolution back in the broader plugin build system thread (read more). -
markvanlan iterated on nested replies UX, adding stronger “you are in context view” styling to reduce confusion once threads get extremely deep (read more).
-
awesomerobot acknowledged an awkward AI-related UI error and linked the fix to remove redundant “Default LLM” wording (read more).
-
lindsey responded in the “Current Projects” roadmap thread about translation contribution paths and said they’re investigating the best approach and will follow up (read more).
If yesterday taught us anything, it’s that even when the daily summary bot misses its shift (read more; see also read more), Discourse still finds time to ship calendar feeds—and dive 10 levels deep into nested replies without getting lost.