Meta got a nostalgia-meets-migration roll call: LotusJeff asked how long communities have been running and what platforms they migrated from in How Old is Your Forum?, sparking stories of decades-old forums and long migration journeys (read more).
The official signatures plugin picked up several long-requested admin controls (group restrictions, category display, “first post only”, stricter URL validation, etc.) after jamie.wilson merged a PR into Discourse Signatures (read more).
Admin workflows around banners changed: staff can no longer make global banner topics from read-restricted categories, and dax suggested an interim “unlisted topic + Automation script” workflow in Can no longer create global banners from restricted categories. isaac emphasized the underlying issue is inadvertent exposure of restricted content via banners (read more).
Localization limitations for custom objects came up again: nat corrected earlier guidance and shared the console-based approach for translating custom badge strings in How can badges and groups be localized (multilingual)? (and why /admin/customize/site_texts won’t find keys that don’t exist yet).
“Phantom notification” behavior popped up: ice.d reported a notification badge that wouldn’t clear in Discourse states i have a notification, and chapoi explained why these async edge cases can be “impossible-to-solve-properly” in the general case (read more).
The “Clip To Discourse” extension shipped text selection clipping (plus context-menu support and template customization) in ‘Clip To Discourse’ Chrome Extension, with plans to adopt the Discourse User API authorization flow (read more).
dax explained the reasoning behind restricting banners sourced from private categories and proposed an interim workflow using an unlisted topic plus Automation scripting in Can no longer create global banners from restricted categories, then reiterated why Automation is needed when pin controls vanish on unlisted topics (read more).
Yesterday’s energy had everything: communities reminiscing about 20+ year timelines while the rest of us debated banners, browsers, and bugs—classic Meta, vintage edition.
Reported a regression in showing username + real name after upgrading in Support
Other threads that also saw fresh movement: chat settings disappearing after disabling chat (Bug), the tablet floating-search oddities (reversed typing in Bug and the uncloseable popover in Bug), and a Bilibili inline player theme component announcement in Theme component.
Interesting Topics
#Announcements
Falco announced major capacity increases for Discourse’s hosted LLM service (bigger plan limits, updated open-weights model, higher max tokens, faster generation), with the new caps already live and reflected on customer dashboards (details).
#Community Building
A long-running-community “roll call” turned into a mini playbook: LotusJeff shared how a niche forum avoids “social media leaks” via deep archival know-how and a strong core, while Canapin reflected on migrations from newsgroups/phpBB and the “multiple migration phenomenon” (discussion, plus context on migrations here and the referenced older thread read more).
A new guide walks through installing Discourse MCP into OpenCode CLI—framing the three-piece architecture (remote forum, local MCP server, and the client) and encouraging people to let an LLM help with the steps (guide); it also cross-links to a companion setup for another client (Codex CLI).
A “why are we being logged out / IP blocked?” incident got a classic diagnosis: with Cloudflare in front, everyone can appear to come from the same IP, so banning one bad actor can effectively ban everyone—plus a reminder to use the Cloudflare template in app.yml (problem report, Falco’s explanation read more).
A hands-on recovery recipe landed for admins who migrated uploads (S3 → local filesystem) and ended up with transparent.png due to missing DB records: satonotdead documented an approach to recreate uploads rows from on-disk files and then rebake posts (walkthrough).
A staging upgrade to 2026.3.0-latest surfaced a display-name mismatch: “username + real name” wasn’t appearing as expected, and pfaffman pointed out the “same value” suppression behavior (and that there’s a setting to force both) (report, reply read more).
A subtle permissions/visibility question explored how about page hidden groups interacts with about page extra groups, especially whether “hidden” should be absolute or conditionally visible to privileged viewers (e.g., admins) (question).
A known email regression reappeared “in the wild”: supermathie tied it to a merged gem update (with a specific breaking commit and a later fix) to help anyone who hit outbound mail failures after updating (post-mortem + pointers).
#Feature
A UX improvement request argued that admins on a multisite guest who hit /sidekiq should get an explanatory hint rather than a confusing error—continuing a thread from an earlier discussion and leaning on the “law of least surprise” principle (feature request, prior context link read more).
Private calendar ergonomics improved: Falco noted authenticated ICS access work already in progress, then followed up with efforts to make user API key generation friendlier for non-technical users—bringing Discourse closer to “private RSS feed”-style usability for calendars (update).
Two tightly-related tablet/search issues were reported on try.discourse.org: one where characters appear reversed in the floating search widget in landscape mode (bug report) and another where the floating search popover persists and can’t be closed after rotating back to portrait (bug report). Both were reproducible even in Safe Mode (Safe Mode reference), and Canapin proposed an interim workaround: only search for palindromes (quip).
A report in Chinese flagged that enabling AI translation can also translate tags into the user’s language and then make the localized tag content uneditable; nat suggested enabling the “Experimental tag settings page” to edit those localizations (report, solution path read more).
Disabling Chat appears to remove Chat preferences permanently (redirecting /preferences/chat back to /latest), and a responder confirmed reproducibility—referencing an older “once chat is disabled…” regression report (new report, reproduction note read more, earlier related topic read more).
#Theme component
A new Bilibili inline player theme component was shared as a “no rebuild” alternative to a server-side plugin approach, with a setup guide via the Themes UI and notes on fallback behavior for edge cases (announcement, comparison plugin link read more).
Falco delivered a substantial upgrade announcement for hosted ai LLM capacity/limits and model performance, including a clear plan-by-plan table of the new caps (post).
He also quickly identified a likely Cloudflare/IP-ban cause behind widespread forced logouts and suggested checking the Cloudflare template in app.yml (support reply).
On the calendar front, he shared progress on authenticated ICS feeds and improving User API Key ergonomics to make “private calendar feeds” feel as seamless as private RSS (feature update).
He additionally asked for clarification to narrow down an AI tool timeout question (support follow-up).
supermathie traced an outbound-email regression to a gem update (and pointed to the fixing commit), effectively serving as a same-day heads-up for anyone upgrading and suddenly losing mail delivery (support update).
He also proposed a UX improvement: when a multisite guest admin hits /sidekiq, Discourse should explain why it’s unavailable instead of simply erroring, referencing earlier discussion context (feature request, earlier thread link read more).
nat responded to a bug report about AI translation affecting tag localizations, pointing admins to enable the experimental tag settings page so localized tag strings can be edited (reply).
If today’s floating search box starts typing gniht instead of thing, it might be time to lean into yesterday’s wisdom and search for palindromes until the bug is squashed.
Timelord asked how to merge/import content from another Discourse site without a full restore, and itsbhanusharma pointed to the long-running “move topics between instances” guidance as a practical path forward (read more, plus the referenced how-to: read more).
A regression (or at least a surprising behavior change) popped up around attachment click counters—uploaded files using the |attachment syntax weren’t showing counters, and now counters appear missing even when that part is removed (read more, follow-up discussion: read more).
“How do I show images on the article front page?” got a very “use the right building block” answer: chapoi suggested the Topic List Thumbnails theme component as the likely solution (read more, component: read more).
A tricky auth/config edge case continued: disabling local logins could prevent new-user signup and surface console/log errors (including missing MaxMindDB files and OAuth access_denied)—with reproduction notes on a fresh install (read more).
“Problems setting up Sentiment” resurfaced with questions about backfilling older sentiment data on self-hosted sites (aiai-sentiment). Falco clarified that the last 60 days backfill automatically after enabling, but the thread continues with debugging questions for cases where that doesn’t appear to run (read more, staff answer: read more, continued troubleshooting: read more).
Theme development tooling hit turbulence: an intermittent 500 error while uploading a theme via CLI led to requests for logs, clarification about which tooling was being used, and eventual suspicion about a problematic plugin in the build (#themes). The thread includes log excerpts and advice to clean up/remove a noisy plugin while investigating (read more, request for logs: read more, log excerpt: read more, plugin caution: read more). (Related references: theme CLI topic read more and theme install guide read more).
On tablets, the floating search widget reportedly reversed typed character order (searchtablet). Falco couldn’t reproduce with a specific environment and suggested trying different keyboards, and the reporter later narrowed it to the “floating keyboard” feature and a particular IME configuration (read more, staff debugging question: read more, additional findings: read more).
A UX gotcha: when the composer toolbar has many buttons, later buttons become effectively invisible—responders noted it’s horizontally scrollable, but the gradient hint may be too subtle (composer). The thread also points out similar affordance issues elsewhere in the UI (read more, suggestion to scroll: read more, gradient hint critique: read more).
#Feature
Users asked to display all likes/reactions on a post, specifically how to expand “and N more…”. Falco confirmed work is underway on a new UI component that would support this more cleanly (read more, staff update: read more).
The long-running discussion about SEO settings for tags (seotags) picked up again, with additional feedback proposing parallel fields for categories and major landing pages (Latest/Top/New): UI title/description and meta title/description (read more, recent “happens on fresh install” report: read more).
#Integrations
Discourse AI’s “Google Programmable Search / Custom Search API” guidance needs revisiting: Google discontinued a key feature, Vertex AI Search is too limited for broad replacement, and the team is researching new providers and potentially native web-search tools from major LLM platforms (aihow-to).
“Google discontinued this feature… Vertex is limited to a handful of domains, it is not a suitable alternative.” (read more)
A practical “should I self-host?” thread continued with advice ranging from “I can install it for free” to “use a dashboard to run one-click upgrades,” plus reminders that managed Discourse hosting/services can reduce operational risk (read more, dashboard mention: read more, hosting/provider angle: read more, follow-up question on provider choice: read more).
#Theme_component
Banner Featured Links got a compatibility refresh: swapping deprecated htmlSafe usage, updating for a new banner class, and a broader cleanup + tests. The maintainer shipped an update and pinned the TC to a newer core version (read more, maintainer update & changelog: read more).
#Plugin
In Discourse OpenID Connect (OIDC) (openid-connect), a request resurfaced to sync Discourse groups with OIDC-provided groups/claims, citing an earlier PR that wasn’t pursued and asking whether it could be integrated (read more).
The Geo Blocking plugin thread revisited Cloudflare considerations: LotusJeff asked about Cloudflare headers, and RGJ clarified what CF-IPCountry actually provides and noted the plugin relies on Discourse’s internal MaxMind database (plus pointing to Cloudflare best practices) (read more, clarification: read more, related guide: read more).
#Using_Disourse
A question came up about the /filter feature: whether filters can be used “in category” while still keeping a left-side navigation experience like category menus / doc-style sidebars (searchtopic-filter) (read more).
Falco focused on product direction + debugging across several threads:
Confirmed active work on a UI that can reveal the full list of post reactions/likes (read more).
Investigated the “reversed typing” report in the floating search widget and requested keyboard/environment checks (read more).
Clarified how AI Sentiment backfill works (automatic for the last 60 days) and set expectations for self-hosters trying to backfill older content (read more).
Flagged that Google discontinued a search feature used in Discourse AI documentation, and outlined plans to ship new search tooling with alternative providers and possibly native LLM web-search integrations (read more).
chapoi helped with practical “what component/setting do I need?” guidance:
Recommended Topic List Thumbnails for showing images on an article’s front page, connecting a support question to a proven theme component approach (read more, component reference: read more).
Challenged an assumption that missing view/reply counts were caused by a theme by checking a theme preview and reporting what they observed (read more).
That’s a wrap—may tomorrow’s imports be smooth, your toolbars scroll sideways on the first try, and your search widgets type in the correct direction.
New topics (last 24h): 3 — including discussions like the composer toolbar visibility on touch devices (read more), a privacy question about proxy access (read more), and embedding Bunny Stream videos (read more).
The composer toolbar overflow affordance came under scrutiny: awesomerobot noted Discourse hides the scroll arrow on touch devices and wondered if that assumption should change (read more), while renato suggested switching the logic to “show if a fine pointer is available” to avoid issues on touch-enabled laptops (read more).
The same thread also turned into a debugging checklist: safe mode showed the missing arrow for the OP, hinting at a theme/style interaction rather than core behavior (read more) and confirming that reproduction depends on environment/device quirks (read more).
A privacy/security concern: a user reported their forum could be accessed via “someone else’s URL” (proxy-style exposure) and asked how to prevent mirroring (read more). The accepted guidance was pragmatic: go fully private if needed and ban accounts showing obvious “visit everything” scraping behavior (read more).
A Ghost-theme-specific display issue: reply/view/activity counts disappeared inside a category topic list when the category had no subcategories, due to the chosen rendering outlet not appearing in that context (read more). The report included screenshots and narrowed the problem to an outlet selection tradeoff (read more).
Hosted customers asked how to recover individual missing CDN uploads (one image + two JSON attachments) after a hiccup, particularly when they’re comfortable self-hosting but unsure what options exist on hosted (read more; read more).
Embedding video from Bunny CDN Stream: attempts to paste a Bunny “player.mediadelivery.net” URL resulted in a plain link rather than an inline embed, prompting questions about allowed/whitelisted oneboxes and embedding rules (read more).
Discourse AI tool calls timing out: a user shared screenshots showing tool execution timing out during script testing and asked whether Discourse’s timeout can be adjusted (read more; read more).
Automation composer formatting: users trying to paste special markup like [wrap] into automation text fields found that rich-text pasting escapes content; renato pointed out a fix that landed, while acknowledging the broader “rich editor vs plain markdown” expectation mismatch (read more).
Sentiment setup and historical backfill: Falco pointed users back to the self-hosting guide for Sentiment/Emotion (read more)—and the follow-up clarified that the dashboard works, but the community wants more than 60 days of backfill and needs to know how far back is feasible (read more). For reference, the guide being cited is here: read more.
#Site feedback
Meta experimentation around “content gardening” doubled as a process question: Canapin explained they often flag their own old posts to request edits, but after a previous staff edit the flag UI only offered “It’s illegal,” so they asked for a better path (read more). darkpixlz solved the immediate need by turning the post into a wiki so the author can update it directly (read more).
That same exchange tied together several “knowledge curation” threads: Canapin wanted to update their earlier post about monitoring uploads (read more) to point at a relevant plugin and topic gallery tooling (read more), and darkpixlz noted staff-attention DMs can be replied to later since they tend not to close (read more).
#Plugin
ActivityPub troubleshooting continued with confirmatory logs showing repeated /webfinger/handle/validate requests and a follow-up find-by-handle lookup, suggesting a consistent reproduction pattern across installs (read more).
Topic Voting feature request: someone asked whether advanced search can be limited to “votable” areas and/or sorted by votes, referencing an older closed related question (read more; read more).
#Self-Hosting
Cloudflare best practices got fresh field notes from a long-term proxy-mode setup: key takeaways included ensuring the Cloudflare template is in app.yml, bypassing cache for /session/*, and skipping WAF on post creation/edits—plus a nuanced WordPress-comment caching strategy to handle bursty traffic (read more).
#Theme component
Topic List Previews (TLP) theme component: a user reported that visiting /u/user/messages/tags/abc was being auto-switched into a “tiles topic lists” display mode and asked how to keep messages on the default display instead (read more).
Anchor links inside Discourse topics: renato reported they can no longer reproduce the issue after a fix merged, and moved toward closing the report unless someone still experiences it (read more).
A “coding agents + SSH” anecdote: a community member described being emboldened as a Discourse admin by using coding agents to resurrect a long-dead vBulletin install—an interesting signal of how admin workflows are changing (read more).
Discourse MCP setup in OpenAI Codex CLI saw a brief update: a follow-up post was deleted by the author, leaving the thread without that additional context (read more).
awesomerobot investigated why the composer toolbar overflow arrow wasn’t visible and asked whether safe mode showed it—strongly suggesting a theme/CSS interaction (read more). They also clarified current intent: the arrow is intentionally hidden on touch devices because horizontal scrolling is “easier,” while openly questioning whether the UI should change to show it anyway (read more).
chapoi diagnosed the Ghost theme issue where views/replies/activity disappear inside certain category lists, pointing to the topic-list-after-category outlet not being available when there’s no category context, and noted they’d check whether an easy outlet switch exists (read more).
Falco supported a Sentiment/Emotion deployment by confirming whether the self-hosting setup guide was followed (read more) and then pushed for clarification on what data range was actually backfilled so troubleshooting could proceed with clear expectations (read more).
renato weighed in on the composer toolbar affordance logic, proposing a refinement: show/hide the arrow based on screen width or fine pointer availability, rather than the broad “touch device” rule (read more). They also noted an anchor-link bug appears fixed and queued the topic for closure unless further reports come in (read more), and confirmed an automation formatting/paste issue should be addressed by recent changes while acknowledging remaining UX tension (read more).
Sign-off: Yesterday’s meta moral: if your toolbar controls vanish, don’t panic—sometimes the missing arrow is just playing hide-and-seek until you flip into safe mode.
Much of today’s momentum centered around theme/component modernization, support category UX, and documentation category navigation — with concrete fixes and “what’s the right default?” discussions across Dev, UX, and Announcements.
das-g tracked down why a legacy footer component started rendering template directives literally, and chapoi tied it to ongoing modernization (including deprecations like registerConnectorClass) and advised refactoring around plugin outlets (e.g. above-footer) in Templating of my “component” broke. How do I fix it? (see the deprecation nudge in-context at post 7, and related guidance referenced via Plugin outlet modernization topic and the theme guides here and here).
A practical naming discussion emerged for making repos instantly recognizable as Discourse theme components (e.g. discourse-tc-*), with community conventions captured in Is there a naming convention for theme component projects? (including awesomerobot’s “not enforced, but often discourse-” in post 2 and a tidy three-way split from RGJ in post 5).
Theme devs revisited how to reference images shipped inside a theme component, clarifying that items in assets/ count as uploads addressable via settings.theme_uploads.* in How do I use images from assets in HTML of a Glimmer-based theme component? (with helpful cross-linking back to the older assets documentation topic here).
A quick-and-clear workflow note landed on localization expectations for PRs: “handle English; robots/community translations get collated later,” in If a PR needs localization what do we do? — plus a broader point from sam about preferring dedicated Meta topics over doc comments for triage in post 4.
A small docs breakage got spotted and fixed: the Theme Directory / Component Directory links in the long-running quick reference stopped working, then were repaired after the report in Theme Developer Quick Reference Guide.
Discourse’s internal culture of writing (as a tool for thinking, alignment, and “ideas that survive pushback”) sparked reflection in the companion thread How Discourse Is Becoming a Community of Writers.
Meta’s documentation IA continues to evolve: a focused question asked whether clicking a documentation category should land on an index topic (vs. latest list), prompting thoughts about scan-friendly navigation patterns and sidebar layouts in What should the homepage be for doc categories?.
Related: category box click behavior and “index link discoverability” remain under debate in Updating how categories are organized on Meta, including whether index links are a workaround for gaps in the new docs experience and whether pinned index behavior differs per user in post 59 and post 60.
A self-host admin hit upload size confusion after editing discourse.conf inside the container (changes reverted on reboot), then discovered the “right place” is persistent config via app.yml; the thread includes the canonical pointer for correct configuration in Maxmum upload size (with the practical fix link shared in post 3 to Change the maximum attachment upload size).
Discourse Hub app users reported getting “stuck” in post-edit mode (save/close controls unresponsive) and needing to force quit; chapoi started narrowing variables around iOS versions and cross-site reproducibility in Unable to exit editing post.
pmusaraj stayed in the weeds on federation and auth troubleshooting: asking for version details to debug ActivityPub actor discovery in ActivityPub Plugin, and continuing to diagnose Discourse ID signup issues (credentials regeneration and configuration review) in New users can’t sign up, 404 errors in console.
Sign-off: With support categories getting friendlier and theme components getting more Glimmer-modern, may today’s plugin outlets be clickable and your “solved” toggles stay solvable.
A Chinese-language upgrade report described admin UI breakage after updating to 3.5.3, then further trouble jumping forward; responders encouraged upgrading properly and checking /logs in 升级至v3.5.3之后管理员页面出现异常 (read more).
A tricky sign-up failure investigation: after disabling plugins/components and testing safe-mode, asc still saw 404s for sourcemaps and Sidekiq “can’t alloc thread” errors; supermathie suggested this looked system-level (RAM/limits/swap) in New users can’t sign up, 404 errors in console (read more).
A new question asked how to connect Discourse AI to a self-hosted knowledge base / RAG pipeline in Discourse ai 如何引入自建知识库RAG？ (ai).
A configuration confusion report: a user expected skip_review_media_groups to trigger review for image posts but observed no approval queue entry, raising questions about expectations vs. actual review rules in Skip_review_media_groups 这个配置不生效.
A new official-but-experimental plugin proposal would let members suggest edits with reviewer-controlled diffs—aiming for a “Wikipedia-style” workflow without granting full edit permissions—in Discourse Suggested Edits (experimental).
“Plugin is experimental and subject to lots of change at the moment, not for production usage yet.” (source)
A small wording/UI clarity issue: the review flow asks “Is this post something else or spam?” with Yes/No buttons, which peternlewis notes isn’t a sensible yes/no question; darkpixlz added more review-queue UI weirdness in “Is this post something else or spam?”.
Yesterday’s vibe: if you weren’t chasing a 500 error, you were probably refining the review queue—or polishing an ICS feed until Google Calendar finally agrees there are events.
Moin and manuel dug into why pinned topics may not “stick” and whether Discourse should distinguish between “Automatically unpin topics” and “Default topics automatic unpin”, with follow-up on improving the wording and admin UX (read more). Related: the deeper settings/wording discussion continues in read more and older context around “automatically unpin” behavior was referenced here (read more).
In the collaborative gardening hub experiment, Moin and NateDhaliwal asked for help closing out issues that are already tagged fixed, as part of ongoing “tidy-up Meta” efforts (read more). The “please close” list pointed at several threads, including read more, read more, read more, read more, and read more.
#Announcements
The Discourse Free plan beta got a clarification: you can make the whole site public or private, but you can’t run a public site with some private categories on Free (aside from the seeded Staff area) (read more).
The “create Support categories using solved” flow prompted translation + UX feedback: Moin highlighted issues with forced lowercase (bad for German nouns) and ambiguous “auto close” wording, with martin confirming fixes are planned (including restoring “after the last reply” clarity) (read more). Background references included the formatting guidance (read more), earlier lowercase side-effects on flag reasons (read more), and related translation/admin-UI friction around settings discoverability (read more).
Moderation review-queue wording came under scrutiny: “Is this post something else or spam?” reads like it’s always “Yes”, and the thread converged on using more generic, action-oriented phrasing when multiple flag types are combined (read more). The discussion also connected to an older visual glitch report (read more) and the lowercase-translation edge case mentioned above (read more).
A self-hosting UX papercut: dismissing a persistent “advice” banner doesn’t really dismiss it if the underlying condition remains—so it keeps returning after reload/new browser sessions (read more). The “known behavior” explanation cited prior notes about planned “snooze” semantics (read more).
RTL polish request: the “reply” icon under the user-profile menu isn’t using the RTL variant consistently, and a fix is already queued via a core PR (read more).
Another translation/layout UX issue: German “Click to upload or drag & drop file” text overflows the placeholder area on some admin upload screens, prompting a request for line-breaking or smarter wrapping (read more).
RTL positioning bug: when reactions are hearts only, the “who reacted” popup appears in the wrong place/direction compared to LTR behavior; other reaction mixes appear OK (read more).
A desktop UI glitch appears when clicking a user profile and then scrolling; Arkshine suspects a CSS interaction (possibly in the chat plugin stylesheet) and provided reproduction evidence (read more).
Chat on iOS/iPadOS continues getting attention: a fix PR for scrolling/member-list overflow got peer review, with follow-up testing and small adjustments reported (read more).
Chat settings disappearing after disabling chat (reported in Chinese) was flagged as time-sensitive; j.jaffeux indicated it should be fixed shortly and asked for confirmation if it persisted (read more).
A long-running “can’t disable solved after enabling it for categories” bug reached the finish line: martin noted the fix has now been merged (read more).
Discourse MCP + granular API keys hit a sharp edge: the MCP server fails validation because it can’t read about.json with scoped credentials, forcing users onto non-scoped “global” keys as a workaround (read more).
#Feature
A Zulip integration improvement PR landed on Meta: terminology updates (“stream” → “channel”, “subject” → “topic”) plus per-thread topic mapping so each Discourse thread can map cleanly to a Zulip topic when left blank (read more).
pmusaraj clarified Free-plan privacy constraints (site-wide public/private, but no private categories on public Free sites) in the Free plan beta thread (read more), and also advised that “disabled” plugins may still run code—recommending fully removing suspect plugins from app.yml when debugging login issues (read more).
awesomerobot unpacked why the new review-queue “Yes/No” UX can be confusing when multiple flags are merged, and suggested switching to a more generic “Is there something wrong with this post?” copy for multi-flag situations (read more).
zogstrip confirmed fixes are coming for two UX issues: the missing RTL reply icon variant in the user menu (read more) and German upload-helper text overflowing its placeholder in admin settings (read more).
chapoi reviewed and commented on an iOS/iPadOS chat scrolling/member-list overflow fix, noting it looked good and calling out a few additions they felt weren’t needed (read more). They also pointed to a core fix for “huge gap below tables on tablets” (read more) and merged a new “can’t see who liked a post anymore” request into the existing “display all likes/reactions” feature thread (read more).
j.jaffeux acknowledged and planned testing for the iOS/iPadOS chat scrolling fix (read more), provided an imminent “should be fixed shortly” update for chat-settings disappearing after disabling chat (read more), and clarified that pinned chat messages are not destroyed (read more).
manuel explained the two different unpin-related site settings and questioned whether Discourse should keep them distinct or improve the descriptions for clarity (read more); they also cross-linked the broader usability conversation about pinned-topic settings (read more).
martin confirmed a bugfix has been merged for disabling the solved feature after enabling it for categories (read more), and responded to feedback on the “Support categories with solved” feature by agreeing to fix forced lowercase (to avoid broken translations) and to restore clearer “auto close after last reply” wording (read more).
mcwumbly closed a feature request as a duplicate and pointed to the canonical topic for restricted-category visibility of who has access (read more); they also weighed in on the pinned-topic mystery, noting it was plausibly due to past manual actions or having read topics while auto-unpin was enabled (read more).
sam jumped into a “bug when trying to split” report to establish whether the affected site is hosted by Discourse or self-hosted—key triage info for next steps (read more).
May your pinned topics stay pinned, your warnings learn how to snooze, and your moderation buttons never again answer “Yes” to a question that wasn’t asked.
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).
Discourse is formally deprecating .js.es6 in themes/plugins and plans to remove support after the next ESR—migration is simply renaming files to .js (read more).
Discourse is also deprecating .hbs templates, encouraging migration to .gjs for 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).
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).
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).
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.es6 in themes/plugins (read more) and deprecating .hbs templates 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.
Rich Text Editor compatibility friction continues: renato asked what functionality was actually required, and explained when Discourse prefers calling ProseMirror commands directly rather than parity via legacy APIs, in Composer Button Bonanza (with follow-up about how missing fidelity affects the component: read more).
A breaking change workaround was confirmed for Custom Wizard: after an update, /admin/wizards stopped loading, and setting ROLLUP_PLUGIN_COMPILER=0 restored access in Custom Wizard Plugin , with the new build system context linked from Introducing a new build system for plugins and the fix confirmed by the reporter (read more).
“You have less than 10 GB of free disk space. Would you like to clean up old containers before upgrading?” (read more)
AI translation UX trade-offs resurfaced: Falco argued that the existing topic-level automatic translation toggle is meant to avoid per-post “translation invocation” friction and duplicated API costs, while the OP wanted intentional friction for a multilingual event in Translate post with AI and save translation (continued: read more).
Provisioning hiccups: multiple users reported id.discourse.com/create-site stuck at “Almost there…” and then hitting “provisioned too many sites,” with one workaround suggestion being try another browser in Got stuck when creating site (read more).
A small but sharp UI nit: Moin found that tags (and votes) are visually “too low” in the composer’s similar topics popup due to CSS margins, in Tags are too low in similar topic pop up.
j.jaffeux weighed in on a confusing Chat report, challenging the premise (“this is not an issue you can have on your site…”) in the ongoing thread 聊天功能被禁用后，其设置消失。, as troubleshooting continued around safe mode and plugin enablement (read more).
renato clarified Discourse’s stance on rich editor APIs and when parity with old textarea-based abstractions is not guaranteed, recommending direct ProseMirror command usage for complex operations in Composer Button Bonanza.
Yesterday’s vibe: if your upgrade disk is full, your calendar feed is picky, and your translations are intentionally frictiony… at least your CSS can still start a lively debate.
In the last 24 hours (2026-03-22 → 2026-03-23), Meta saw 63 new posts across 8 new topics, with most of the discussion clustering around update/ops reliability, UX polish, and plugin/theme edge cases (e.g. theme update checks in this Support thread and self-hosting email/version-job debugging in this report).
Total new posts:63
Total new topics:8
Top users (posts / likes received in the last 24h):
Richie reported that all themes/components started showing “Error cloning git repository” after upgrading to 2026.3.0-latest.1, even though manual checks succeeded; suggestions ranged from rebuild attempts to GitHub rate limits/outages (with GitHub-status context noted by david). read more
Richie asked why “Associated Accounts” controls aren’t visible for staff accounts, and the thread concluded it’s likely hidden when staff have 2FA enabled, with a pointer to the existing guidance. read more
In the long-running Custom Wizard thread, users narrowed down an env var naming gotcha (ROLLUP_PLUGIN_COMPILER vs prefixed variants), while david linked an upstream PR and warned the fallback won’t be around forever. read more
#Self-hosting
A privacy/security-focused self-hoster argued Discourse can reveal the origin server IP when fetching remote resources for previews/embeds; discussion explored proxy/plugin angles, but initial plugin settings didn’t prevent direct fetches in the reporter’s testing. read more
A self-hosted admin reported “new version” notification emails stopped (despite settings enabled), and follow-up debugging suggested a failing CallDiscourseHub job with a Redis argument-type exception. read more
Group inbox migration logistics came up again: one approach floated was converting PMs to topics, moving, then converting back, acknowledging potential workflow limitations. read more
#Site-feedback
A small-but-annoying UI edge case: with topic-voting enabled and 0 votes, the vote indicator disappears and a dangling comma appears after the last tag; investigation pointed at a customization that hid “0 votes,” and disabling themes restored expected layout. read more
#Feature
A request proposed an “expand-table” wide-screen viewer for regular users (read-only), mirroring the author-only table-builder full-width editor view—aimed at making markdown tables usable on laptops. read more
On mobile, ondrej suggested adding the same grip bar affordance seen in topic admin actions to post admin actions as well, to make the sheet more obviously draggable. read more
A long-running calendar-and-event “Uncaught (in promise)” report moved toward closure: sam asked for clarity on what’s still broken, and the reporter replied with testing evidence suggesting FullCalendar is functioning across setups. read more
ActivityPub troubleshooting continued: sam flagged a Mastodon connection issue and suspected OAuth now requires an explicit scope in the payload, looping in the likely maintainers for ideas. read more
The post-approval flow got another UX papercut: a discard confirmation modal appears when clicking “New Post” if a post is pending approval, and sam emphasized the broader end-user experience can feel hostile without clearer queue visibility and expectations. read more
A small process note: theme/plugin skeleton compatibility pinning happened again, and david confirmed the team is moving to a branch-based versioning strategy and won’t run the old automated .discourse-compatibility process going forward. read more
A versioning-strategy RFC thread gained more field feedback: a user reported they could install a specific branch, but the UI update page didn’t detect newer updates, complicating upgrade validation. read more
#Announcements
Follow-up in the “Support categories + discourse-solved” announcement: martin dropped a link to the PR that fixes the reported issues. read more
Calendar subscription URLs for external apps: feedback noted that regenerating URLs after first reveal makes multi-device setup awkward, and there was discussion about wanting community-specific feeds rather than combined output. read more
A large migration request landed: phpBB → Discourse with ~870k posts, Hebrew RTL, strict SEO/301 redirect requirements, and minimal downtime expectations. read more
david weighed in on the theme git-access errors, backing the theory that GitHub rate limiting/outages are likely culprits and pointing to GitHub’s recent incident history (read more). He also advanced the Custom Wizard troubleshooting by linking an upstream fix PR and recommending migrating off the legacy compiler flag once patched (read more). Additionally, he confirmed the team’s future approach on skeleton compatibility/versioning strategy changes (read more).
sam responded to the hard-to-reproduce theme update error reports with “try removing and re-adding” and called out the likelihood of environment-specific behavior or GitHub rate limiting (read more). He also followed up on a calendar-and-event console error report to verify whether anything is still broken (read more), flagged a likely OAuth scope requirement in an ActivityPub/Mastodon connection issue (read more), and pushed for a more humane, end-to-end UX for “post approval required” flows after a confusing discard modal report (read more).
martin posted a direct pointer to the fix PR for issues raised in the “Easily create Support categories using the discourse-solved plugin” announcement thread (read more).
Sign-off: Between GitHub hiccups, compiler flags, and a surprise “favorite TV series” detour into LG OLED evo territory (read more), Meta stayed delightfully unpredictable—here’s hoping tomorrow’s rebuilds take only one try.
Investigated activitypub verification failures (meta actor vs. other actors) — read more
“I’ve heard this feedback from a few different places now, so I’ve added a little messaging around it to clarify…” — awesomerobot on search behavior changes (source)
Also active (more threads worth a click):
Topic Voting UI punctuation fix when votes = 0 and tags are present — read more
Similar-topics popup tag positioning (ux) — read more
Discotoc floating Contents/Timeline buttons issue (disco-toc) — read more
Admin webhooks page layout + localization concerns — read more
Bug report (ZH): permanent-delete flow unexpectedly “restores” state — read more
Support (FR): admin warning about discourse.resolver-resolutions in a third-party plugin — read more
Marketplace: bulk-create + approve ~1,500 users via API (Marketplace) — read more
Interesting Topics
#Theme component
Noble_Fish spotted confusing duplicate callout entries when aliases share a Title, and Arkshine quickly shipped a fix to filter the type list properly — read more
Ivan_Rapekas released “AI Summary In Topic Header”, a theme component that surfaces the Discourse AI summarize action in the topic’s right sidebar (desktop) and title area (mobile/narrow) (aiai-summarize) — read more
In “Restrict uploads”, Moin shared a PR switching restrictions from trust levels to groups, making “subscriber-group-only uploads” much easier to model — read more
#Extras
Eilgnaw introduced Dexo, a native iOS Discourse client (UIKit/Swift) featuring multi-forum management, HTML rendering, secure User API Key auth, and light/dark/system themes — read more
#Plugin
The “ImgLink” plugin announcement drew scrutiny: Moin questioned “random/spammy tags” and broken links, and darkpixlz removed tags and suggested starting from the official plugin skeleton — read more
A long-running “Custom Wizard Plugin” thread got a notable update: david said the fix was merged and asked maintainers to re-enable the rollup plugin compiler for verification — read more
“No new version emails” appears to have broken after a redis gem update (dating back to March 2025); david linked the core PR addressing it — read more
ActivityPub integration hit a Mastodon compatibility snag: Mastodon seemingly renamed scope to scopes; pmusaraj proposed a fix and later confirmed meta-side resolution (activitypub) — read more
A report about failing to connect Discourse ActivityPub actors suggests something specific to the meta actor (other actors worked in testing); pmusaraj is still investigating and comparing cross-instance behavior (activitypub) — read more
kirupa asked how to add custom links beneath the welcome banner; responses pointed to the “Banner Featured Links” component and potential plugin-outlet configuration mismatches after banner migrations — read more
joshhabka asked about MediaWiki-style [[wikilinks]] autocomplete in posts; discussion covered alternatives like standard markdown linking and Watched Words for auto-linking common phrases — read more
#Feature
A request proposed updating only themes/components (without full core upgrades) to reduce admin friction and avoid rate limits when updating many components — read more
A detailed calendar-and-event request argues for multiple [event] blocks per topic so tentative times can all appear on the calendar during scheduling, rather than fragmenting discussions into one-event-per-topic — read more
Discourse published a new Discover roundup highlighting communities “where builders learn together,” with a companion discussion topic on meta — read more
awesomerobot focused on UX polish and clearer messaging: they added explicit UI copy distinguishing “exact” vs semantic/AI-ish matches in search results feedback (search thread), and confirmed a fix for a Topic Voting tag-list comma glitch (topic-voting + tags). They also pointed to a fix for tags appearing too low in the “similar topics” popup (UX report).
zogstrip pushed multiple fixes forward by tying reports directly to core PRs: a “permanently delete” state bug report in Chinese (bug report), “required: true” not being enforced for upload fields in form templates (form-templates bug), and missing post URLs in ICS exports (calendar feature).
david handled a mix of diagnosis, guidance, and maintenance follow-through: they traced “no new version emails” to a redis gem change and linked the fix (bug thread), advised that .gjs format updates should be done in a local dev environment (dev-news thread), clarified a French admin-warning banner was caused by a third-party plugin and suggested uninstall/report-to-author (support thread), and confirmed a Custom Wizard fix was merged plus requested retesting with rollup enabled (custom wizard).
pmusaraj spent time deep in activitypub troubleshooting: they identified Mastodon parameter drift (scope → scopes) and proposed a plugin-side fix (mastodon issue) before confirming it was resolved on meta (follow-up). In a separate report, they noted failures seemed tied to the meta actor and compared behavior across instances/domains (Discourse AP connection issue).
sam performed doc gardening on “Searching for content effectively”: they removed stale discussion after cross-referencing current code (doc update note), then restored previously deleted wiki content to unblock improvements and encouraged suggested edits to the OP (restoration).
If yesterday taught us anything, it’s this: may your callout aliases stay tidy, your summarize buttons stay visible, and your ActivityPub “scopes” always be spelled correctly.
In the last 24 hours (2026-03-24 → 2026-03-25), Meta kept busy across support, dev-news, and feature discussions—ranging from dev-container bootstrapping tips to UX polish and plugin releases (see activity in threads like read more and read more).
New posts:91
New topics:9
Top users (posts / likes received):
Moin — 12 posts / 17 likes (e.g. dev workflow guidance in read more, plus CSS theming pointers in read more)
R23D_Printing announced Discourse Member Application (#discourse-member-application), a plugin to run a pre-invite application workflow at /apply, with admin review and automated invite links: read more.
Related install/how-to references: read more
In Discourse Suggested Edits (experimental), Moin reported missing notifications for suggesters/affected users, suggesting the notification flow may not match expectations: read more.
This ties into broader composer/draft expectations raised elsewhere: read more
A Subscriptions (subscriptions) renewal/update error (“PaymentIntent does not have a payment method…”) was reported with Stripe + legacy supporter history, prompting discussion of cleanup/handling older billing states: read more.
Prior related incident referenced for comparison: read more
A dev-container workflow snag—email confirmation blocks first login without SMTP—was resolved by pointing to bin/rails admin:create, improving the “first admin” bootstrap story for new contributors: read more. awesomerobot also suggested using MailHog to “receive” dev mail without real SMTP config: read more and the Docker dev guide was referenced in-thread: read more
The ongoing .hbs deprecation (dev-news) conversation continued as RGJ flagged docs needing updates, and david clarified timelines and added notes (including pointing people to ask.discourse.com for help): read more.
The “modernizing inline script tags” companion announcement was also updated to note the removal has now landed: read more
A hosted/free provisioning block (“You have provisioned too many sites in the past hour”) turned out to be domain-related; staff asked for the domain value and the user confirmed switching domains resolved it: read more.
A new Free plan site owner couldn’t find where to configure auth/login and learned that Discourse ID handles social login on the free tier; they then reported an inability to enable it, triggering follow-up investigation: read more.
The Free plan beta announcement was referenced as the baseline expectation: read more
A thoughtful UX request proposed making Anonymous Mode (anonymous-mode) more discoverable (e.g., from the composer) and adding clearer “you’re anonymous” affordances for switching back: read more.
Moin reported that Klipy (gifs) search results appear to repeat while scrolling (unlike Giphy’s finite scroll), asking whether Klipy can adopt similar “end-of-results” behavior: read more.
A theming question about moving a banner/image to the very top ended with a practical CSS target (.d-header .wrap) and a pointer to the canonical “custom CSS changes” doc for step-by-step guidance: read more.
Referenced resources: Brand Header component read more and the custom CSS guide read more
#Announcements
Admin Reporting improvements (dashboard-reportsreporting) prompted confusion about why “Staff only” wasn’t available; clarification: it’s intentionally a simple Everyone/No one toggle because the reporting UI applies globally: read more.
The broader “Upcoming changes” mechanism was referenced as context: read more
#Site feedback
In the “collaborative content gardening” experiment, adding fixed unexpectedly re-opened an old closed topic as a side-effect of automation—confirmed as unintended and slated for adjustment: read more.
The reopened example topic was linked directly: read more
awesomerobot helped smooth dev workflows by recommending MailHog for local email capture during development (read more) and updated banner documentation to reflect that dismissible banners need public-category placement (read more; referenced doc: read more).
zogstrip drove multiple fixes/triage updates: acknowledging a bug report and proposing/confirming a fix for a sidebar “Update Discourse” oddity (read more), noting an ignored-users/digest issue is covered by a PR (read more), and clarifying that “Reporting improvements” is a global on/off (Everyone/No one) toggle (read more).
chapoi confirmed the #fixed-tag reopening behavior is unintended and should be adjusted (read more), and answered a Carousel Mode question: height is fixed by design; customization requires CSS (read more).
pedro followed up on a hosted provisioning limit report by asking for the exact domain value entered, helping isolate the trigger (read more).
HAWK acknowledged the same provisioning report and escalated it internally for review (read more).
lindsey documented a serious approval-queue UX issue where a discard modal can block posting broadly when a post is pending approval, plus shared investigation notes around where pending content appears (read more).
gerhard confirmed a translations/context issue should now be fixed, after reports that a “removed” label looked wrong (read more).
david updated dev documentation threads: adding guidance/notes around the .hbs deprecation and highlighting that ask.discourse.com can help with smaller migrations (read more), and announced that support for legacy inline script tags has been removed in the latest Discourse version (read more).
martin confirmed a fix for the “Enable form templates” targeting/sidebar issue has been merged (read more).
sam kept docs tidy by updating the Composer Popup Messages guide and removing outdated items (read more).
If your day included a carousel that won’t resize, a dev inbox living at localhost:8025, and a mysteriously re-opened topic just because someone added fixed… congratulations: you’ve basically experienced the full Meta variety pack.
New posts (last 24h): 82 — conversation clustered around release visibility, UX details, and plugin/dev workflows (e.g. read more, read more, read more).
New topics (last 24h): 7 — including new support questions like hiding staff from /about (read more) and making an “Announcements” category effectively read-only on the free plan (read more).
Top users (posts/likes in the last 24h, with an example jump-in):
Ed_S raised alarm that v2026.3.0-latest.1 shipped with “33 security fixes” yet felt “stealthy” due to fewer Announcement pointers; Falco linked background, and david acknowledged the pain around visibility + said the feedback was raised internally (read more, read more, read more). Follow-up context included the newly posted/backdated release pointers (read more, read more) and references to older “dashboard advice” confusion (read more) and version-notification oddities (read more).
A site owner asked for a built-in way to remove the default @moderators section from /about (without CSS/theme work). The thread dug into what about_page_hidden_groupsactually hides, and how to keep staff access without listing everyone publicly (about-page) (read more, read more). A notable possible extension was using dynamic group membership to hide “trainee mods” as a set (read more).
On the free hosted plan, Naoshi wanted an “Announcements” category where only staff can create topics, but everyone can reply. Moin suggested a pragmatic workaround: enable approval for new topics in that category and simply don’t approve non-staff topics (free-plancategories) (read more, read more).
#Self-Hosting
The long-running mail-receiver guide got a very practical Cloudflare-focused addendum: why Cloudflare proxying blocks SMTP, the need for a separate inbound-mail hostname, and how to do Let’s Encrypt via DNS challenge for TLS. The discussion also surfaced risks around exposing origin IPs when adding a DNS-only record (read more, read more, read more).
#Plugin
“Discourse Daily Challenges” drew feature requests for non-daily intervals (e.g. weekly check-ins) and letting mods/category mods create challenges instead of requiring admins. The back-and-forth clarified expectations like “1 entry per week across a month” and even referenced Calendar’s configurable week start (gamification, tangentially) (read more, read more, read more).
The diskuz Call plugin (P2P voice/video inside Discourse) got a strong +1, plus a request to consider group calls / meetings as a next step (#experimental-ish in spirit, even if not tagged that way) (read more).
A long-awaited improvement landed: an “icon type” SiteSetting exists now. The thread quickly turned into “this will make updating theme components easier”, and it also connected to real-world fallout like FontAwesome icon availability and free/regular fallbacks (with the Reactions plugin cited as benefiting) (read more, read more, read more).
Work continued on a new build system for plugins, with david announcing a public talk at Ember Europe for those who want the architectural overview and rationale (dev-news) (read more).
“Impossible to prevent x.com oneboxes (and they’re broken)” got a clear “will be fixed by PR” response, continuing the ongoing efforts to keep oneboxing reliable and configurable (onebox) (read more).
A new report: Chat plugin fails to compile when the rollup plugin compiler is enabled by default, with a concrete error trace pointing at _assert is not a function (chat) (read more).
“Whispers only temporarily bump topics” progressed toward a fix, while still surfacing a philosophical split: some want any staff-visible activity to bump, others want no bump because “nothing happened” publicly (whispers) (read more, read more).
The Horizon theme’s sticky category heading became a mobile pain point: what’s “lovely on desktop” can crowd the topic list on small screens. chapoi noted it’s an unintended side-effect of keeping navigation visible, and invited others to investigate a cleaner solution (horizon-thememobilepr-welcome) (read more, read more).
In the long-running “comment platform viability” conversation, Falco announced Discourse’s own blog comments were swapped over to a new embedded-topic commenting system, with early feedback already noting theme/padding/light-vs-dark mismatches and the plan to iterate via a theme component first (read more, read more, read more).
More hands-on feedback landed in the “Testing Nested Replies on Meta” sandbox: users called out how notifications/flat view can make it hard to know which “nested chunk” a reply belongs to, and suggested adding “parent comment” affordances (LiveJournal-style) to improve orientation (read more, read more).
A new paid request asked for a developer to integrate Discourse with a Kajabi membership site, including migration, tiered access automation, branding, and replacing Disqus-style comments—explicitly aiming for Facebook-like simplicity on the front-end while keeping Discourse power behind the scenes (read more).
Falco helped contextualize the sudden “33 security fixes” concern and engaged on release visibility expectations (read more), and also announced that Discourse’s blog comments are now running on a new embedded Topic-based system and invited feedback (read more).
david responded directly to the release-visibility feedback, apologized for the long-unnoticed email issue, and said the team is discussing adding Meta pointers back into Announcements; he also linked the newly posted/backdated release announcement topics (read more, read more, read more, read more). He additionally shared a public talk slot about the plugin build system (read more).
zogstrip continued the “here’s the PR” style of bug-triage updates across multiple threads—whispers bumping behavior (read more), x.com onebox breakage/config limitations (read more), topic timer instability (read more), and the discard-confirmation modal annoyance when approvals are involved (read more).
gerhard explained why translation context lookup could be temporarily degraded: a background job was running to backfill AI-generated context, expected to settle within about a day (read more).
nat posted a quick status update that the watched-words auto-tagging issue had already been fixed and encouraged updating when possible (read more).
martin noted an upcoming refinement to reporting/share options—adding clearer “Staff only” / “No one” choices since “Everyone” doesn’t map well to certain report behaviors (read more).
chapoi weighed in on the Horizon theme sticky heading issue, framing it as an unintended side effect of keeping navigation visible and inviting community PRs if someone can disentangle the containers cleanly (read more).
Yesterday’s Meta energy was peak “blink and you’ll miss it”: stealthy security-fix releases on one side, and shiny new embedded blog comments on the other—keep one eye on your dashboard and the other on the comment box.
Activity snapshot is reflected across active threads like Discourse ID + HTTPS configuration discussions in #Self-hosting (read more) and releases/distribution workflow feedback in General (read more).
Interesting Topics
#Self-hosting
darkpixlz hit a blocker enabling Discourse ID when force_https is disabled; supermathie and Falco reiterated the fix is getting the reverse proxy + HTTPS signaling correct so Discourse can generate valid redirect URIs (read more). Related: an earlier Discourse ID redirect-URI edge case was also recently addressed (read more).
A continuing discussion on deploying older / pinned Discourse versions turned into a practical guide (update discourse_docker, set version, rebuild), with david clarifying that version: esrshould work and that changes belong in containers/app.yml, not web.template.yml (read more). Background references: tracking branches overview (read more) and beta-branch/tag history (read more).
Self-hosted inbound email ops got an update: LotusJeff revised Cloudflare guidance and discussed running mail-receiver separately to avoid exposing origin IPs (read more).
A long-running hosting/security nuance resurfaced: someone troubleshooting why the Security UI shows Cloudflare IPs got a reminder to verify DNS/proxying and sometimes “remove/re-add domain” to re-trigger provisioning flows (read more).
Feedback landed on the shift toward releases.discourse.org as the canonical changelog source: concerns about discoverability and readability turned into quick iteration—RSS was added and styling improvements are in-flight, with david welcoming actionable UX feedback (read more). Supporting refs shared in-thread include RSS discovery tips (read more) and release notification options (read more).
A tiny-but-real papercut: the “champagne” emoji shortcode doesn’t resolve even though the tooltip says “Champagne”; Falco traced it to a mapping issue in discourse-emojis and suggested removing the conflicting alias entry (read more).
On Meta specifically, 2FA inputs were left-aligned (visually off compared to the rest of the login layout). awesomerobot narrowed it down to the “login via email” path and linked the fix PR (read more).
Clarification on permanent deletion and attachments: uploads tied to a permanently deleted post will be removed after clean_orphan_uploads_grace_period_hours, with caveats if anything else still references the file (avatars, emojis, site settings, etc.) (read more). Deep dives referenced: permanent delete introduction (read more), upload cleanup guidance (read more), and historical quirks around auto-purging uploads (read more).
A user asked why Meta “doesn’t notify” them anymore; manuel pointed them to per-topic notification levels and global tracking preferences (e.g., set topics to Watching if you want every reply) (read more).
A likely UX bug/validation mismatch: setting Welcome Banner text color via the picker saved without a leading #, then failed validation; workaround was to manually enter #RRGGBB, and it was suggested this might warrant a UX report (read more).
New report: Android app keyboard not appearing when composing posts. NateDhaliwal asked for version details and whether it reproduces in safe mode, while noting they couldn’t reproduce in Discourse Hub / Chrome (read more).
Someone exploring the experimental /filter topic list syntax asked for boolean “OR” between category/tag constraints; replies confirmed it’s not supported today and suggested filing a feature request (read more). Related docs: the original filter feature thread (read more), search tips (read more), and filter operator examples (read more).
A theme/CSS rendering oddity: tables without <thead> are getting a header divider as if a <thead> existed (seen on Horizon + Meta). The report includes minimal HTML reproduction and explains why Markdown/CommonMark expectations differ (read more).
Search UX friction continues: autocomplete can override intended #category input when mixing category+tag or tag+tag, and recent category organization changes may have made “simple category entry” harder on Meta (read more).
#Plugin
The Discourse Challenges plugin shipped updates, then quickly hit a “create challenge = 500” report. The maintainer diagnosed a badge-name regression and requested logs while preparing fixes and clarifying required fields like existing Topic ID and tag entry format (read more).
Long-running ecosystem note: the Formatting toolbar plugin maintainer expressed concern about ongoing compatibility and the sustainability of maintaining plugins/components as core evolves (read more).
Theme/component dev question: adding avatar decorations/overlays from custom user fields. The recommended approach was to reference examples of accessing custom user fields in theme components; prior art discussions around frames/overlays were also pointed out (read more). References: accessing fields via a theme component example (read more) and earlier avatar frame discussion (read more).
supermathie helped diagnose why Discourse ID requires HTTPS redirect URIs, emphasizing that force_https is about assumption of scheme (not “serve on 443”), and the proxy must forward the right headers (read more).
Falco reinforced the pragmatic fix for Discourse ID enablement—fix the reverse proxy/HTTPS setup first—in the same thread (read more); also flagged the emoji alias issue for :champagne and pointed to the exact constants mapping that likely needs removal (read more).
Falco weighed in on calendar/event workflows, pointing people to calendar subscription URLs as a near-term solution for staying synced across instances (read more).
awesomerobot investigated the misaligned 2FA UI, identified it as specific to the email-login flow, and linked the upstream fix PR (read more).
pmusaraj documented that Discourse now handles the “redirect URI already exists” Discourse ID setup issue by generating new keys when re-registering with the same redirect URI (read more); and followed up on a Discourse ID alternate-email report requesting reproducible details/screenshots (read more).
david responded to changelog/release UX feedback: clarified that Highlights are curated (similar intent to old release notes), invited further actionable feedback, shipped an RSS feed for the releases site, and outlined ongoing styling work (read more).
david also clarified correct version-pinning mechanics for self-hosters: use containers/app.yml, not templates, and confirmed tags like esr are designed to work via git checkout $version (read more).
manuel helped a user regain expected notifications by pointing them to per-topic notification levels and the Preferences → Tracking page for global defaults (read more).
Yesterday’s Meta managed to ship an RSS feed, debug a few login/layout mysteries, and still found time to debate why :champagne isn’t actually champagne—classic Discourse energy.
eisammy marked two years of community-building and learning-by-doing (including theme components and open-source experiments) in Celebrating 2 years of my Instance , with a warm wave of congratulations following in the replies.
A “big red banner” mystery turned into a theme component health check: darkpixlz explained the banner indicates a broken component and pointed to Chat Sidebar, while david strongly cautioned against hiding the warning with CSS in Getting rid of the big red banner, how? (the component was then fixed, per the thread’s conclusion in post 4).
A chat UX limitation (GIF + text in the same message) was clarified as long-standing behavior of the GIF component: Falco confirmed history and reclassified accordingly in Gif + texte dans le même message dans chat.
Reviewable workflows raised a subtle but important question: the system DM text says “reply to this message,” but replies appear to go nowhere—prompting suggestions like notifying moderators or changing the copy in “reply to this message” goes nowhere?.
A site where “everything plugin-related stopped working” turned into likely CDN/CORS diagnosis: darkpixlz suggested investigating CDN script errors (and testing with CORS tools) in All plugins not functioning, with the original symptoms described in post 1.
Version pinning expectations were reinforced: david helped troubleshoot YAML/parameter placement and clarified that downgrades aren’t supported (and ESR requires waiting for the next ESR release if you’ve advanced) in Help deploying older versions of Discourse.
A forum design “show and tell” for a Resonite community drew praise plus actionable UI feedback (notably on mobile header links) in Opinions on the forum I’ve built (see the mobile CSS note in post 6).
The #plugin thread for challenges hit a migration snag and recovered: R23D_Printing walked through missing DB columns and a path to resolution (including rebuild guidance and an update push) in Discourse Daily Challenges through the “it works” confirmation in post 34.
Yesterday, meta featured everything from dancing “challenge solved” celebrations to big red banners getting defused the right way—may your migrations be smooth and your components forever unbroken (or at least loudly warning you when they are).
awesomerobot agreed it’s reasonable that granular API access should be able to read about.json, and noted a PR was opened for review in “API user with granular access cannot read about.json” (mcp) — read more. The thread also dug into whether the current error messaging is misleading, with supermathie specifically calling that out (read more) and the original poster confirming the confusion (read more).
A “how do I customize the sidebar like this?” question led to identifying the likely feature as the Docs Categories plugin in Theme customize - sidebar content; Lilly pointed to the relevant component as a starting place (read more), referencing Discourse Doc Categories.
A potential regression (or expectation mismatch) surfaced: “Use name for username suggestions” appears to have no effect on the standard signup form, confirmed by another admin in “Use name for username suggestions”: no effect on signup form? (signup) — read more, plus confirmation in-reply (read more). This was spun out of the now-solved registration UX discussion in Customize registration form / hide or normalize username field, where ToddZ suggested using site text + settings (and even CSS) to guide “real-name-like” usernames (read more), and later noted the suspected issue and opened the follow-up topic (read more).
Export/printing needs resurfaced in Is there a way to print a single post in a topic?: Thomas_Rother described a workflow need for sharing a single Discourse post (e.g., a wiki meeting protocol) into other channels, ideally as PDF — read more.
#Self-Hosting
In Help deploying older versions of Discourse, troubleshooting focused on YAML structure: Ed_S suggested the version line was likely mis-indented because it belongs under params (read more), after RBoy shared a screenshot showing the config layout (read more).
How to set up fine-grained admin permissions or limit export capability? (backups) revisited a common constraint: admins effectively have full control. NateDhaliwal asked for the underlying goal and pointed to the standard automation approach (read more) while referencing the guide on automatic backups. Another reply suggested environment-defined settings may take precedence over UI configuration (read more).
A frustrating composer failure report in Lost paragraphs / huge post due to HEIC upload moved toward reproducibility: awesomerobot asked for the exact error and whether the issue could be reproduced with similar text + the same images, emphasizing repeatable steps as the quickest path to root cause (read more).
#Site-Feedback
Accessibility/readability feedback continued on the Meta Branded redesign: theme refresh thread (meta-theme-feedback, meta-redesign-2026). stephtara reported that linked text in the dark palette was “just below readable,” especially the purple-on-dark contrast, after comparing against other themes (read more).
Releases.discourse.org feedback & suggestions sharpened into a concrete accessibility checklist: ferdnyc identified contrast failures (including a failing WCAG ratio for white-on---color-feature) and argued the site needs an accessibility review (read more), then enumerated additional contrast problem areas flagged by tooling (read more).
The contrast ratio cited for one key pairing was 3.46:1, below the WCAG AA 4.5:1 minimum (details).
#Plugin
A brand-new admin-oriented utility, Plugin Cleaner, was introduced as a way to scan/audit orphaned data left behind after uninstalling plugins (read more). merefield offered a detailed critique, warning about edge cases like plugin-owned tables and the risk of deleting fields that may later become core (read more).
Tag Intersection Navigator got both maintenance and a practical UX improvement: merefield shared PRs for upkeep and a feature allowing “normal banner notifications” while staying on the tag-intersections view, making it more viable as a homepage (read more).
Discourse Daily Challenges shipped v1.4.0, adding an optional ChallengeBot for DM-based confirmations, reminders, and mention-driven commands (like status / leaderboard)—with rate limiting and a new site setting for bot username (read more). A user also asked about displaying the challenge info elsewhere (e.g., on user cards) earlier in the thread (read more).
In Eu tenho um fórum, mas não sei se ele está bem organizado o suficiente, NateDhaliwal discussed information architecture tradeoffs (e.g., why tags don’t always map cleanly to subcategories) and suggested improving “Report a Bug / Give Suggestion” flows by linking directly to a pre-filled composer (read more), pointing to the how-to: Creating a link to start a new topic with pre-filled information.
#Feature
A chat UX gap was reported in Pouvoir changer de canaux et de fermer en grande fenêtre chat (chat): when the chat window is expanded, the controls to switch channels or close the window appear to be missing, forcing users to shrink the panel to regain navigation (read more).
#Extras
OpenClaw plugin for Discourse integration hit a snag when a referenced page began returning 404 (read more); a follow-up pointed back to context in the related OpenClaw skill discussion (read more), with a direct reply and link-drop in the OpenClaw integration topic (read more).
awesomerobot engaged on API permissions + developer ergonomics in API user with granular access cannot read about.json | Discourse MCP (mcp), saying it’s reasonable to include about.json access and noting a PR had been opened (read more).
awesomerobot also worked the debugging angle in Lost paragraphs / huge post due to HEIC upload, asking for the error details and encouraging reproduction steps to isolate the cause (read more).
supermathie followed up in the same MCP/API thread by questioning whether the current “invalid API username/key” message is misleading in granular-access cases, hinting at an opportunity to improve the error text (read more).
May your plugin residue be minimal, your contrast ratios pass audits, and your ChallengeBot DMs arrive right on schedule.
diskuz Call – Voice and video calls inside Discourse (P2P, no external apps) (installation background: How to install plugins in Discourse).
