LotusJeff’s “elder forums” roll-call turned into a mini case study on why some communities survive platform shifts (phpBB/vBulletin → Discourse, Facebook leakage, and the “Discourse bump”), with migration notes from elmuerte and graphs from Canapin. How Old is Your Forum?
Discourse AI hosted LLM capacity got a major bump across plans, plus model and performance improvements (token limits and speed). Falco posted the new limits table and pointed folks to updated pricing. Unlock All Discourse AI Features with Our Hosted LLM
A “randomly logging everyone out” mystery ended up being a classic Cloudflare-origin IP pitfall: ban one IP and you’ve effectively banned everyone. Falco asked if the Cloudflare template is enabled in app.yml. Our Forum Seems To Be Logging Everyone Out
A staging upgrade to 2026.3.0-latest appeared to stop showing username + real name together; a likely culprit is the “same username/name” suppression behavior + the setting to force both to display. Username + real name not working in 2026.3.0-latest
A subtle permissions/UI question: should about-page hidden groups stay hidden even for members of about page extra groups (e.g. admins)? The current behavior seemed surprising enough to warrant clarification. About page hidden groups and about page extra groups
A Chinese-language ai support question reported tool-calling timeouts (Operation timed out - FinalDestination::HTTP); Falco asked which specific tool was timing out to narrow next steps. Discourse ai 的工具调用超时如何解决？
A practical “recovery cookbook” got added for people migrating uploads from S3 to local disk and ending up with transparent.png: recreate missing uploads records from orphaned files, then rebake. Re-adding missing uploads to the database
Chat settings confusion resurfaced: disabling chat made the chat preferences section disappear (and /preferences/chat redirects away). A prior related report was referenced for comparison. 聊天功能被禁用后，其设置消失。 (see also Once chat is disabled it cannot be enabled any more)
Notifications edge-case: chapoi noted that some “phantom notification” issues can be effectively impossible to solve perfectly due to complexity—while still acknowledging the frustration and discouraging rants. Discourse states i have a notification
Private calendar ergonomics continued to improve: authenticated ICS feed access is already in progress, but the follow-up is making User API Key generation non-technical-user friendly. Authenticated ICS feeds for private calendar events
Discourse dev + LLM workflows: a thread about Claude and Discourse-related development emphasized that models need guardrails and up-to-date docs; chapoi pointed out the dev docs are now back in the core repo. Claude & Discourse-related development. How good is it?
Markdown alternatives: replacing Markdown with Quarkdown was deemed not feasible without effectively extending markdown-it to replicate needed features. Can Markdown be replaced with Quarkdown
Set expectations on markup extensibility: “not possible” to swap out Markdown wholesale; you’d need to extend markdown-it for desired features in Can Markdown be replaced with Quarkdown.
May your Cloudflare bans be un-banned, your uploads rebaked, and your tablet search boxes stop typing in reverse—see you tomorrow, Meta adventurers.
Timelord asked how to merge content from another Discourse without a full backup/restore in “Forum Aquisition”, and itsbhanusharma pointed to the canonical “move topics between instances” approach (read more; reference: read more).
In a Chinese-language support thread about AI translation, nat explained that enabling the “Experimental tag settings page” lets admins edit tag localizations when AI translation also translates tag text (read more).
Engineer_Abdallah explored using Discourse as an articles + courses platform (with images/video/code/files), and chapoi suggested the Topic List Thumbnails theme component to get more visual “front page” presentation (read more; suggested TC: read more).
Eviepayne reported that attachment click counters no longer appear (even when using |attachment), and asked if the previous counter behavior can be restored (read more).
In a long-running “install on a VPS” help thread, the discussion ranged from DIY installs to safer maintenance workflows (including pfaffman’s one-click upgrade dashboard mention) and what to expect from hosted support (read more; hosting/legal process note: read more).
A LinkedIn OAuth setup got unstuck when alanr reminded folks the redirect URL must exactly match what LinkedIn expects (example callback path included) (read more).
A tricky sign-up failure investigation continued: asc linked reproduction to toggling local login, along with errors mentioning missing MaxMind DB files and Discourse ID auth failures (read more).
A fresh regression report claims the new category settings UI can leave “Solved” stuck on: once enabled, it can’t be deselected because the controls move/disappear between settings screens (read more).
Another bug report described the floating search widget reversing character order on certain setups; Falco couldn’t reproduce on Edge/Android/Gboard and suggested testing other keyboards (read more).
#Feature
In the reactions/likes UI discussion, soraiden asked how to expand the “and X more…” list of reactors, and Falco confirmed the team is working on a new UI component to support this cleanly (read more; question context: read more).
The Google Programmable Search Engine / Custom Search API situation appears to have shifted again: Falco noted the relevant Google capability was discontinued and said Discourse is researching alternative providers (and thinking about supporting “native search tools” bundled with major LLM providers) (read more; more context: read more).
#Theme component
A new theme component: “Bilibili Inline Player” was shared as a no-rebuild alternative to the server-side plugin approach, with setup steps and a comparison to the existing OneBox/plugin solution (read more; related plugin thread: read more).
The Banner Featured Links component got a practical compatibility refresh: eisammy swapped deprecated htmlSafe usage for trustHTML, and Arkshine shipped an update/cleanup with a detailed changelog and tests (read more; update notes: read more).
#Plugin
In the official Discourse OpenID Connect (OIDC) plugin thread, Steradiant asked about syncing Discourse groups from OIDC group claims, pointing to an older PR that implemented it and asking whether it could be included (read more).
The Geo Blocking plugin thread clarified Cloudflare specifics: RGJ confirmed it works with Cloudflare (with proper setup) and corrected a misunderstanding about what CF-IPCountry contains, while noting the plugin uses Discourse’s internal MaxMind DB (read more; question: read more; referenced Cloudflare guide: read more).
#Using Discourse
In a reference thread on filtering topic lists, cmdntd asked whether /filter can be used within a category context to keep the left-side navigation (cat menu / sidebar) in place (read more).
On AI Sentiment backfilling, satonotdead asked about populating sentiment further back than the default window, and Falco clarified that the last 60 days backfill is automatic once enabled (and the thread continues with debugging questions) (read more; original question: read more).
Confirmed the team is building a better UI to show the full list of reactions beyond “and X more…” (read more).
Investigated the reversed-character input in the floating search widget and asked for keyboard-specific reproduction details (read more).
Explained that Google discontinued a key Programmable Search behavior and shared that Discourse is researching alternatives (including possible LLM-native web search tooling support) (read more).
Clarified AI Sentiment behavior: enabling it automatically backfills the last 60 days (read more).
nat provided the solution for AI translation translating tags: enable the Experimental tag settings page and edit localizations there (read more).
chapoi helped connect “Discourse as articles/courses” needs to existing UI building blocks by recommending Topic List Thumbnails (read more), and also questioned whether a “missing counts” report was truly theme-caused by checking the Ghost theme preview behavior (read more).
If today’s search box starts typing backwards, remember Canapin’s wisdom: stick to palindromes and you’ll still get the right query (read more).
祁同伟 reported that when the composer has too many buttons, the later buttons become inaccessible; the thread explored horizontal scrolling affordances, gradient hints, and whether the scroll arrow should appear on touch devices (or only “narrow screens / coarse pointers”) in 编辑器按钮较多时，靠后的按钮不可见 — including the “arrow hidden on touch” detail at read more and the safe-mode observation at read more.
The same conversation pointed to a process note: staff-attention DMs often stay open and can be used to continue a moderation request without starting a new public thread, referencing A post in “A way to monitor user uploaded files” requires staff attention as an example of where that workflow surfaced.
ActivityPub implementers compared logs and confirmed repeatable behavior around handle validation / lookup flows (notably /webfinger/handle/validate followed by actor lookup), adding real-world diagnostics to the long-running ActivityPub Plugin thread.
DiscourseAI users troubleshooting Sentiment found a classic self-hosting pitfall: missing internal IPs in allowed internal hosts. The thread then moved into whether a deeper historical backfill is feasible and safe in Problems setting up Sentiment, with staff pointing back to the canonical setup guide Self-Hosting Sentiment and Emotion for DiscourseAI and clarifying questions at read more.
In that same upload issue, logs suggested plugin/theme interactions, and merefield advised removing a noisy third-party plugin to stabilize the build in Getting error while uploading theme (after the error-log excerpt surfaced at read more).
A request came in to embed videos from Bunny Stream, but Discourse only rendered a generic link preview; the thread asks what’s required for onebox/embed support in Allow Embedded Video from Bunny CDN stream service.
A lively AI-admin anecdote: using Claude Code + SSH to revive and migrate a “dead” vBulletin forum sparked discussion about how coding agents are changing admin workflows in Claude Code - Resurected Dead vBulletin from 2016.
The OpenAI Codex CLI + MCP setup thread saw a follow-up post deleted by its author, leaving the main configuration discussion as the primary reference point in Discourse MCP Setup in OpenAI Codex CLI.
awesomerobot dug into mobile/touch behavior around horizontally scrollable composer toolbars, first suspecting theme CSS interference and recommending safe mode checks in 编辑器按钮较多时，靠后的按钮不可见, then explaining that Discourse intentionally hides the scroll arrow on touch devices (and questioning whether that should change) at read more.
renato added a nuanced UX refinement: instead of “touch device detection,” the arrow-display logic might be better keyed off screen width or the presence of a “fine pointer,” since touch-enabled laptops complicate the current heuristic in 编辑器按钮较多时，靠后的按钮不可见. renato also confirmed an anchor-link issue appears fixed after a merged core PR and scheduled the report to close in Anchor links not working within Discourse - but work from outside the topic.
If yesterday taught meta anything, it’s that between resurrecting ancient vBulletin installs and chasing missing UI arrows, the real “scroll” was the troubleshooting we did along the way.
das-g’s footer sponsor component started rendering template directives literally after updates; chapoi traced it to modernization work and deprecated patterns like registerConnectorClass, pointing toward plugin outlets (e.g. above-footer) and newer theme structures (read more). Background pointers referenced in-thread include modern outlet patterns (read more) and theme docs (read more, read more).
Continuing that migration thread, das-g asked how to correctly reference theme assets (images/fonts) from Glimmer/strict-mode templates without hitting scope errors (e.g. helper resolution failures), with a nudge toward settings.theme_uploads... usage (read more). The discussion explicitly ties back to the broken footer work (read more) and the long-running assets guide it builds on (read more).
Naming conventions for Discourse theme component repos got some practical proposals: while nothing is enforced, patterns like discourse- prefixes and community conventions like discourse-tc- surfaced as a way to quickly distinguish components vs themes vs plugins (read more).
A small but impactful docs fix: das-g flagged broken links in the longstanding “Theme Developer Quick Reference Guide,” and tshenry patched them promptly (read more).
Localization workflow clarity: when a PR needs translations, the guidance was that contributors handle English and automation/community translation processes take care of the rest (read more).
Discourse made it much easier to create Q&A-style Support categories by turning on sensible defaults for the solved experience during category creation (notably “Allow topic owner and staff to mark a reply as the solution”) (read more). In related bug news, there’s also an acknowledged issue where some admins are unable to disable solved once enabled in a category—martin indicated a fix is in progress (read more). (For baseline context, the Solved plugin reference is here: read more.)
Category composition got another quality-of-life enhancement: you can now set title placeholders per category, and it’s been confirmed as “in core” (with commit references in-thread) (read more). This dovetails with prior asks about category-specific title prompts (read more).
A creative (and uncomfortable) scenario: a site owner reported their forum being accessible via someone else’s URL/proxy, and the pragmatic takeaway was that you can’t fully prevent public mirroring without making the site private—focus on account monitoring and privacy controls when needed (read more).
Cloudflare operational notes got two angles today: real-world configuration updates were added to the Cloudflare best-practices guide (including reminders like ensuring the Cloudflare template is in app.yml) (read more), and a separate “everyone is getting logged out” report tied the symptoms to Cloudflare/IP visibility and moderation actions (e.g. banning what looks like a shared IP) (read more).
A “core bug” turned out to be a theme interaction: a report that “Username + real name” display wasn’t working on 2026.3.0-latest was resolved by using safe mode to identify a theme setting (“Remove name suppression on posts”) as the culprit (read more).
Sidebar link normalization appears to be breaking certain external URLs: if an external URL contains the site’s own hostname inside a query parameter, the hostname may be stripped, breaking redirect-style flows (with a workaround involving URL-encoding / direct DB write) (read more).
Embedding video from Bunny Stream was solved with the straightforward approach: allow the provider’s iframe host via the allowed iframes setting, using Bunny’s embed URL format (read more).
#Plugin
The activitypub plugin thread continued diagnosing an actor-discovery mismatch: pmusaraj could find @announcements@meta.discourse.org elsewhere, while the reporter on 2026.3.0-latest could not—prompting version/config comparisons (read more).
#Site feedback
Meta’s own category re-organization work surfaced a UX gotcha: “index” links may be visually present but effectively unclickable because the whole box captures the click, preventing link interaction—mcwumbly confirmed the behavior and outlined why it happens (read more).
Discourse published a reflection on internal culture and craft: writing as a core practice for clearer thinking, stronger collaboration, and better decision-making—now mirrored on Meta as a companion discussion topic (read more).
pmusaraj continued troubleshooting in the experimental activitypub plugin thread by asking for version details and comparing actor discovery behavior across instances (ActivityPub Plugin); and also pushed forward diagnosis on Discourse ID signup failures by asking for credential regeneration and a review of auth-related settings (New users can’t sign up, 404 errors in console).
In the last 24 hours, Meta saw 97 new posts across 13 new topics, spanning everything from account-security workflows to docs navigation experiments (e.g. read more, read more, read more).
“How do you move changes from dev to prod?” (and what not to do): A practical thread on deployment mindset for Docker installs, with Falco pointing folks back to plugin/theme workflows and merefield emphasizing backups aren’t a dev→prod transport in What’s yall’s work-flow like?.
Admin UI breakage after upgrading to v3.5.3: A report (in Chinese) showing missing admin modules + safe-mode observations, with a reminder that v3.5.3 is out of support in 升级至v3.5.3之后管理员页面出现异常.
Per-user “always approve posts” moderation:haydenjames asked for a built-in way to force approval for specific users; Moin suggested a dynamic-groups approach as a workaround strategy in Force post approval for specific users only? (with pointers to review triggers here and dynamic group logic here).
Upload limits: nginx config resets + Docker best practice:Andro hit confusing “512m maximum allowed” failures even for a 30MB PDF, then realized container edits revert; merefield pointed to updating app.yml correctly in Maxmum upload size.
Replacing Discourse search with SearchUnify: A short “is this possible?” integration question in SearchUnify Search bar.
Moderation queue wording confusion (“Is this post something else or spam?”):peternlewis flagged an awkward yes/no prompt and asked for clearer action labeling, with follow-up examples of other queue weirdness in “Is this post something else or spam?”.
What should the homepage be for doc categories (index vs latest vs overview)?mcwumbly proposed routing doc-category clicks to an index/overview, while manuel raised deeper scanning/navigation issues with the current sidebar layout in What should the homepage be for doc categories?.
#Site feedback
Meta category organization + docs index duplication:manuel noted that index topics can appear in multiple places (sidebar generation, pinned topic list, description links) and suggested simplifying, while mcwumbly compared pin behavior and called it a docs-plugin usability gap in Updating how categories are organized on Meta.
#Plugin
Experimental plugin: “Suggested Edits” (Wikipedia-style contributions with reviewer control):sam announced Discourse Suggested Edits as an experimental plugin designed for granular review/acceptance of changes without granting full edit rights in Discourse Suggested Edits.
#Feature
Authenticated ICS feeds for private calendar events (merged) + client compatibility debugging:Falco merged authenticated feeds and then investigated why Google Calendar/Outlook might show no events despite valid VEVENTs, including mention of a fix for old recurring events in Authenticated ICS feeds for private calendar events.
New user signup failures + “can’t alloc thread” Sidekiq errors: A debugging thread where safe-mode behavior, plugin/theme elimination, and resource constraints (1GB droplet + swap considerations) came up in New users can’t sign up, 404 errors in console.
supermathie helped triage the same signup thread by verifying Discourse ID signups worked on their end and pointing out that “can’t alloc thread” suggests system-level constraints in New users can’t sign up, 404 errors in console.
Sign-off: After a day of suggested edits, hacked-account hardening, and calendar-feed detective work, Meta’s vibe is clear: ship the fix, refine the UX, and keep the puppies safe.
david announced a new, mostly backwards-compatible build system for plugin JavaScript, aligning plugins with the modern theme build pipeline and enabling faster rebuilds, better caching, and native ES modules (read more). This also ties into efforts to ship more precompiled assets for self-hosters (read more).
A moderation-review wording/flow issue: the prompt “Is this post something else or spam?” confused people because “X or Y” is logically always “yes”; awesomerobot suggested switching to more generic copy when multiple flag types are combined (read more). Related: visual oddities in moderator actions were cross-referenced to an older report (read more) and to a long-running lowercase-conversion translation problem (read more).
“Dismiss” that doesn’t dismiss: darkpixlz reported that the HTTPS / reverse-proxy advice banner reappears even after dismissal, prompting discussion of whether “dismiss” is intended as a permanent hide vs. a “fix underlying issue” nudge (read more). Moin linked the broader explanation of current notice behavior and the idea of adding “snooze” in the future (read more).
RTL polish: a new report notes the reply icon variant isn’t switching properly in the profile menu for RTL languages like Arabic/Persian, despite other UI areas using an RTL-correct icon (read more).
Locale-aware title cleanup: a quick question about whether title_remove_extraneous_space should be disabled by default concluded with Moin pointing out it’s already locale-overridden (enabled for English, disabled for non-English defaults) (read more). Background: the original behavior discussion lives here (read more) and the setting details were referenced here (read more).
A long-running UI glitch where the page “jumps” after opening a user card got more data: Arkshine reproduced it and suggested the chat plugin’s CSS might be contributing (read more). The thread also re-covered troubleshooting via safe mode to isolate customizations (read more).
Mobile/tablet rendering: the large gap below tables on tablets got a fix queued—chapoi pointed to a change for permanent visibility (read more) and later confirmed a targeted fix landed (read more).
Chat admin/settings reliability: in a Chinese-language report, chat settings disappear after chat is disabled; j.jaffeux indicated a fix would ship shortly and asked for confirmation if still broken (read more).
Another chat UX fix proposal: a patch thread continues work on iOS/iPadOS scrolling issues and member-list layout overflow, with j.jaffeux planning to test and chapoi leaving implementation feedback (read more, read more).
#Self-hosting
Upgrade woes after moving to 2026.1.1: a self-hosted admin reported admin pages breaking after upgrading, but the deployment details revealed a Kubernetes + “web_only” approach; replies clarified what’s supported and suggested typical rebuild steps, while noting the k8s approach is outside standard support paths (read more, read more).
#Announcements
Free plan beta clarification: mattdm asked whether the Free tier allows “public site + some private categories,” and pmusaraj clarified Free sites can be entirely public or entirely private, but can’t mix with additional private categories (beyond the seeded Staff category) (read more).
“Where can I try Chat?”: a new user asked for examples of Discourse Chat “in the wild”; Moin recommended trying it on the sandbox and explained options to experiment via hosted trials/free plan (read more) referencing the Free plan beta topic (read more).
#Feature
Email templates refinement: a feature request proposes an option so notification emails can display just the subcategory name (when present) instead of always showing “Category/Subcategory” (read more).
Likes/reactions visibility: a new request argues that when a post has many likes, it’s no longer possible to see the full list of users; the suggestion is to allow another click to fully expand the list (read more). This was also merged into the broader, older feature conversation about exposing all reactions/likes (read more).
AI + automation ideas continue: a new ai request asks whether Discourse would ship an official OpenClaw “skill” to let an authenticated user instruct an agent to perform forum actions (including reposting authorized content into categories with tags) (read more). For context, there’s already an “OpenClaw plugin for Discourse integration” thread exploring adjacent workflows (read more).
david introduced a new plugin JS build system with caching, ES module output, and a path toward bundling precompiled code for popular plugins (read more), explicitly tying into the precompiled-assets direction for self-hosters (read more).
awesomerobot jumped into the review-queue UX confusion around “Is this post something else or spam?”, identified a “standalone yes button” as a bug, and proposed more generic phrasing when multiple flag types are combined (read more, read more).
chapoi had a busy day across UI and bugfixes: they investigated the tablet table-builder gap and linked/landed fixes (read more, read more), reviewed a proposed iOS/iPadOS chat scrolling fix with some follow-up comments (read more), and helped debug a 500 error when splitting/merging topics by asking for browser-console clues and edge cases like solutions in the posts (read more).
pmusaraj clarified Discourse’s Free plan beta limitations around private categories on otherwise public sites (read more) and wrapped up a support thread by advising that “disabled” plugins may still run code—suggesting complete removal from app.yml while isolating login issues (read more).
davidb confirmed a bug fix for marking a reply as the solution after a merge, linking to the commit and noting it was already deployed to the affected site (read more).
j.jaffeux addressed multiple Chat-related items: they gave an imminent-fix ETA for chat settings disappearing when chat is disabled (read more), acknowledged a patch thread and planned testing for iOS/iPadOS scrolling/member-list overflow fixes (read more), and clarified that pinned chat messages are not destroyed (read more).
martin noted progress on a bug where admins were unable to disable “solved” after enabling it for categories (read more) and responded to feedback on the “support category” creation flow—agreeing to adjust confusing wording and avoid forced-lowercase strings that break translations (read more).
sam helped triage a report of 500 errors when splitting topics, requesting logs and clarifying whether the instance was hosted or self-hosted to guide next steps (read more, read more).
mcwumbly did some housekeeping by closing a feature request as a duplicate and pointing to the canonical thread on visibility of who has access to restricted categories (read more, read more).
If today’s threads taught anything, it’s that Meta users are as persistent as that “dismissed” reverse-proxy warning that keeps coming back (read more).
lindsey published Current Projects – March 2026, highlighting shipped work like the now-official Blog Post Styling component and hosted Discourse AI credit limit increases (plus continued work on AI Agents) — with a translation workflow question raised by Moin about whether the component should land in Crowdin or via PRs read more. (Related: Blog Post Stylingread more)
The “Easily create Support categories using the discourse-solved plugin” announcement thread continued with UI/text formatting and i18n nuance, as Moin suggested using existing lowercase translation keys to avoid breaking style guidance read more. (Related formatting guidance: read more)
In the dev-news thread on the new plugin build system, david confirmed the new compiler is now enabled by default on latest, marking a meaningful shift for plugin developers and build pipelines read more.
A self-hosting-oriented question popped up in the long-running RFC on Discourse versioning strategy, asking what the actualapp.yml configuration should look like when pinning an ESR/release branch read more.
A spate of upload failures (422 with a generic “upload failed” error) was reported when trying to upload a GIF; nat acknowledged the issue and then confirmed it was fixed shortly after read more. (Anecdotal “took several attempts” corroboration: read more)
A report on ActivityPub + Mastodon OAuth failing with The requested scope is invalid, unknown, or malformed suggests a compatibility/config mismatch in the authorization step, with a video reproduction included read more.
iPad/iOS Chat UI stability continued improving: a patch thread reported further fixes for Chat settings/member list scrolling and overflow issues, with additional iPadOS testing noted read more.
A German locale UI issue was flagged where “Click to upload…” text overflows the placeholder; zogstrip pointed to a PR that will introduce a more robust layout (likely via wrapping/line breaks) read more.
Discourse ID’s referring-site branding visibility was called out as too subtle at the moment users are deciding whether they’re in the right place; pmusaraj requested mockups to explore clearer hierarchy between Discourse ID and the originating site read more. (Related “flow friction” follow-up: read more)
Another RTL polish item: the reply icon under profile for RTL languages was acknowledged and queued for fix via PR, continuing the steady RTL UI refinement stream read more.
A microcopy oddity was spotted in Discourse AI Agent messaging: “Default llm” appearing redundantly before “Default LLM” in an error string, raising questions about string composition or translation keys read more.
A broader moderation-workflow UX debate continued around the flagging prompt “Is this post something else or spam?” with feedback that yes/no patterns and “Approve” labeling can be confusing when the moderator intent is “spam → delete/block” read more.
#Site_feedback
A request to expand try.discourse.org so people can test admin/mod tooling (and concerns about the instance not “clean resetting”) drew pushback: community members emphasized why public admin access is unsafe, and suggested alternatives like spinning up free/trial instances instead read more. (Prior art: “try.discourse.org as moderator/admin” read more; free plan beta invite read more)
Meta category organization discussion briefly reignited the long-running confusion around pinned/unpin site settings, with calls to improve descriptions and/or consolidate options so the user-default vs global settings are clearer read more. (Related: pinned settings usability thread read more; “official groups posts” reference point read more)
A searchability gap was reported: the Guidelines/FAQ don’t appear in search, even for unique phrases, prompting discussion about /guidelines being a static page and/or category restrictions preventing indexing read more.
A discoverability complaint: where to find “Releases” now that releases have a dedicated site, with suggestions to add links in more obvious places (footer, tag descriptions, or “New to Discourse” onboarding) read more. (Pointers: January 2026 releases read more; introducing releases.discourse.orgread more; “New to Discourse” hub read more)
A least-privilege API snag: the Discourse MCP server fails validation with scoped “granular access” API keys because it can’t read about.json, raising a question of what endpoints should be required/allowed for MCP integrations read more.
A new install enabling discourse-subscriptions hit “Error loading route” immediately; troubleshooting began by requesting logs/console output, while reminding that Stripe + webhooks + plugin settings need to be completed first read more. (Related canonical setup guide: read more; ongoing payment-method error concerns: read more)
lindsey kicked off the March roadmap update in #Announcements, outlining what shipped and what’s in progress (including AI changes and feature naming updates) in Current Projects – March 2026.
mcwumbly added practical context to the pinned-topic mystery (possibly due to historical “read → auto-unpin” behavior), helping validate the most plausible explanation in Updating how categories are organized on Meta.
Yesterday’s Meta mood: chasing down a vanishing GIF upload bug while also squeezing long German strings into tighter UI boxes—classic “polish the edges” day (upload fix, German layout tweak).