In the last 24 hours (2026-03-07 → 2026-03-08), Meta saw 36 new posts across 5 new topics, with discussion spread across support troubleshooting, theming experiments, and self-host/dev setup snags (e.g. read more, read more, read more).
Explaining why Ruby 3.4.0.dev can fail Gemfile constraints read more
Also bubbling up on the sidelines: a multilingual blog thread got fresh replies read more, and the long-running events plugin topic flagged a broken external support link read more.
Interesting Topics
#Theme-component
jdc20181’s Tag Style Tool thread continued evolving into a mini “style builder” discussion, including Font Awesome icon support, UX requests for linking resources in settings, and experiments toward a color-picker UI read more (plus a progress demo read more).
A “why can’t I see the mobile UI on desktop browsers?” investigation explored the fading legacy of ?mobile_view=1read more, with pointers that it’s deprecated/legacy behavior read more and may have been removed recently read more; the deeper direction is viewport/capability-based styling read more.
A self-host admin reported Discourse ID signups silently failing (button does nothing) and noted anonymous-only console 404s like vendor.map/start-discourse.map, seeking configuration/debug guidance read more (discourse-id).
A new SEO/localization report suggested translated ?tl= pages aren’t being indexed because the canonical tag points to the non-translated URL (Google treating localized pages as “alternate with proper canonical”) read more (content-localization).
A self-hoster described AI Search resource impact and others asked for “hardware profile” details before enabling it themselves read more (aiai-search).
A theming question asked how to create a transparent “Discord-like” look, ideally per-user or for a small group—highlighting the common constraint that theme components typically apply instance-wide read more.
An iPadOS Safari oddity where the composer “flies off screen” when focusing different fields was reported—and then (mysteriously) stopped reproducing the next day, leading the OP to mark it resolved/withdrawn read more (resolution update read more) (composertablet).
In a solved onebox thread, NateDhaliwal suggested a composer button that inserts an iframe (theme-component feasible), and the discussion moved toward per-user personalization via custom user fields and access patterns read more (and follow-up on user-specific values read more).
A “non-admin users can’t load pages” support thread got a familiar first-line check: “does it work in safe mode?”, plus a reminder that the advanced search banner component is deprecated and its functionality moved into core/banner patterns read more (safe mode reference read more, deprecation notice read more, and the current banner guide read more).
#Self-hosting
The Windows 11 dev environment guide saw a fresh round of Ruby version mismatch troubleshooting (3.4.0.dev vs Gemfile ~> 3.4), with links to common “build fails / update fails” cousins and a confirmed fix by installing Ruby 3.4.8read more (related: build mismatch thread read more, crash-during-update read more, and the “big scary red button” update thread read more) (dev-install).
#Site-feedback
In the ongoing “improving support categories” conversation, sam pointed out Discourse AI already supports sophisticated agents and asked how to make advanced workflows easier to configure, tying into a parallel “split automations into triggers/actions” feature direction read more (feature request context read more).
#Theme
Pyx’s Modern Theme shipped an update aimed at compatibility with the upcoming default theme, including restoring a cursor-active behavior (under a new name) and tweaking button borders with an option to disable if it has side effects read more.
#Site-Management
A question on auto-bumping configuration asked whether “1” is effectively the minimum daily bump, after .25 (every 4 days) didn’t persist—raising practical concerns about overwhelming the feed in “resources” categories read more.
#Sysadmins
In the NodeBB → Discourse migration guide, a contributor shared a tweak to mongo.rb to ensure posts within a topic sort chronologically via sort(score: 1), improving import ordering read more (how-to).
#Feature
A “Math should be quotable” proposal suggested a theme-component approach to improve quoting of MathJax/KaTeX-heavy posts by replacing math wrappers with original TeX source before quote-to-Markdown conversion read more (pr-welcome).
Falco jumped into the Tag Style Tool discussion to note there’s a native HTML color picker input (<input type="color">) and that Discourse wraps it for easier usage—useful for turning a “maybe-plugin” idea into a realistic theme-component enhancement read more.
sam weighed in on improving support workflows, pointing out that Discourse AI already supports “extremely sophisticated agents,” and raised the key product question: how to expose these capabilities so admins can configure advanced workflows without heavy bespoke work read more.
If yesterday was any indication, today’s Meta motto is: may your mobile views be viewport-driven and your color pickers be delightfully native (read more, read more).
sam announced service tiers for OpenAI/Azure providers (including guidance on the responses endpoint for caching/costs) in Service tiers on Open AI providers, with a pointer back to the LLM settings page for configuration.
“Can Discourse force a one-way TOS acceptance?” was answered with a custom user field pattern that blocks saving until checked (marked solved) in Require TOS acceptance.
A big ops/perf report: enabling aiai-search caused heavy load while backfilling embeddings for a large site (millions of posts) in Enabling AI search crippled my server, after earlier requests for server/DB/provider specifics (read more).
A tricky error log around editing wiki posts for some users (with create_errors_json called with unrecognized type) landed in Error when editing a Wiki Topic.
Privacy/GDPR concerns surfaced again around oneboxes: max.l questioned whether onebox preview images/favicons are fetched remotely (tracking risk) in Cache onebox images and/or serve them from the main domain, and Falco walked through live testing and clarified behavior differences between composer preview and baked posts (read more).
A fast-moving iterative debug session continued for the Tag Style Tool, including a disappearing builder button and icon rendering quirks, in Tag Style Tool.
Plugin feasibility (FR): gilles sketched a workflow for a BoardGameGeek API-powered composer toolbar button, and the thread weighed theme component vs plugin tradeoffs (API key exposure) in Besoin d’avis pour essai de programmation de plugin.
If yesterday taught us anything, it’s this: keep your Guidelines renamed, your oneboxes cached, and never let an outdated build steal your cake day frosting.
Total activity (last 24h):51 new posts across 7 new topics, including fresh threads on chat, self-hosting, and plugins like a new points mall (read more).
New topics opened (7):
Chat UX request: open straight into Chat / show Chat on landing page (read more)
Permissions: disable chat for moderators (chat) (read more)
eisammy asked how to disable Chat for moderators (keeping it admin-only), and Lilly confirmed moderators can’t be excluded when chat is enabled—while NateDhaliwal traced the behavior to core chat settings, likely requiring a plugin to override (chat) (read more)
lucy.sierracircuits reported that members can’t upload more than one image per post; Lilly suggested also checking the simultaneous uploads site setting as a likely culprit (read more)
pHneutre noticed the Upcoming Events sidebar icon showing as a generic link instead of a calendar; Falco advised it’s fixed in current Discourse and recommended updating (calendar-and-event) (read more)
In a long-running moderation/admin thread, Lydia2 hit a confusing state where a user appeared silenced without an “unsilence” button; Bas suggested clicking “silence” again to try resetting the state back to normal (read more)
A wiki-editing problem got a quick resolution: isaac pointed to a fix for an error when editing a Wiki Topic, then followed up as additional 500s were reported and the team started investigating further (read more)
#Self-hosting
Huskijore (moving a community off Discord) asked whether Discourse can provide a home-screen shortcut that lands directly in Chat, or even a “latest-like” view that includes selected chats; Andrew_Rowe recalled similar prior attempts but no clean solution yet (chat) (read more)
For SEO-minded WordPress operators, hritik asked how to deploy Discourse on a sub-path rather than a subdomain; ToddZ clarified the WP plugin is for integration and linked the canonical path prefix/subfolder setup guide (read more, plus background: read more)
In troubleshooting a broken onboarding flow, asc and others continued digging into new users failing to sign up alongside console 404s (source map requests) and resource exhaustion errors, narrowing down what an anonymous user experiences (discourse-id) (read more)
A Cloudflare hardening thread got an update as haydenjames shared real-world rulesets and planned to incorporate Discourse’s recommended WAF exclusions, especially around post creation and Data Explorer admin queries (cloudflare) (read more)
#Site Management
In the Discourse AI spam tooling thread, LotusJeff asked for lower-level reporting behind the AI spam summary box; Falco replied with a direct SQL query to pull records from ai_spam_logs, pointing to #DataExplorer as the practical path to “show me the details” (aispammoderation) (read more, Data Explorer reference: read more)
#Feature
Naming polish landed: in the “AI Persona → AI Agent” discussion, Falco confirmed sam shipped the rename work, linking the implementation PR and closing the loop on the terminology direction (ai) (read more)
In the automation redesign request (split automations into triggers and actions), participants pushed for more expressive workflows—especially delays and richer conditional logic—with noahl exploring how conditions could be composed with AND/OR and values pulled from trigger_context (automation) (read more)
#Plugin
Monikas announced a new (very early) Discourse Points Mall plugin—daily check-ins, a shop, orders, makeup cards, and a points ledger—while explicitly flagging UI bugs and advising admins to wait before installing in production (read more)
A Foundation theme UI report (in Chinese) flagged a search button wrapping issue; awesomerobot said the fix is to prevent text wrapping in buttons and noted it should be resolved after updating Discourse (foundation-theme) (read more)
On site chrome and default pages, the “FAQ/Guidelines and About pages” discussion continued: ToddZ and Andrew_Rowe outlined the practical value of the built-ins (default sidebar links, boilerplate, and discoverability/SEO concerns even if you “hide” them) (read more)
#Translations
In a thread about poor French translations in automation UI, gerhard talked through the dream of in-context translations inside Discourse, noting Crowdin’s constraints around single-project in-context mode and hinting at experimentation in coming months (automation) (read more)
#Developer Guides
A theme-dev thread got modernized guidance: MarkDoerr explained that legacy widget code is outdated due to the post stream changes, and suggested using a Glimmer component plus api.renderAfterWrapperOutlet to place user custom fields in the post header—linking back to the post-stream migration guidance (read more, migration context: read more)
#Site feedback
Meta’s “collaborative content gardening hub” experiment kept chugging along: ToddZ proposed pruning obsolete “About page customization” topics now that the newer About-page docs and features exist, and linked several candidates for cleanup alongside the newer canonical references (read more, related hub: read more, About page announcement: read more, About page guide: read more, candidates: read more, read more, read more)
Falco pushed forward both product clarity and admin pragmatics: confirmed the AI Persona → AI Agent rename landed (read more), provided a Data Explorer SQL to inspect AI spam log details (read more), and noted an Upcoming Events icon issue is already fixed upstream (encouraging an update) (read more).
Bas helped troubleshoot an odd moderation UI state by suggesting a “toggle it to reset it” approach for a missing unsilence control (read more).
isaac linked a confirmed fix for a wiki topic editing error, then acknowledged follow-up 500 errors and indicated the team is investigating (read more, follow-up report: read more).
awesomerobot acknowledged a foundation-theme search UI bug and pointed to a fix that prevents button text wrapping after updating Discourse (read more).
gerhard shared direction on improving translation workflows, including the idea of in-context translations inside Discourse and the constraints with Crowdin’s current project model (read more).
tgxworld confirmed a fix is queued for object-type theme settings, linking the PR that will address it (read more).
MarkDoerr provided updated theme-developer guidance for rendering custom fields near post headers using Glimmer components, referencing the broader post-stream migration work (read more, background: read more).
Between spam-log SQL, chat UX wishes, and Glimmer-powered theme fixes, meta spent the day proving that “it’s just one small tweak” is rarely just one small tweak (read more).
Solved plugin confusion + post-merge “FAILED” when selecting a solution:Silas-Inservio-Pax hit an error after merging topics and then trying to mark a specific reply as the solution, with Lilly and darkpixlz guiding them toward browser console output and checking /logs (which required an admin). read more
Data Explorer API change: limit=ALL stopped working (by design):pfaffman tracked a breakage down to limit=ALL, with Falco pointing to a change intended to remove the “no limit” path and recommending pagination (and clarifying the new cap). read more (see also: the “reverse engineer” approach mentioned in-context read more)
After upgrading, “official” theme components fail… but the culprit is a plugin:Stephane_Roy reported multiple “official” components breaking post-upgrade; awesomerobot found a console error pointing at the broken Journal plugin and suggested confirming via safe mode with plugins disabled. read more (related: Journal plugin reference read more)
Adding intro text to /g (Groups page) via a tiny theme component:pHneutre wanted a paragraph above the group list; ToddZ outlined a simple Theme Component using After Header + scoped CSS to only show on .groups-page. read more (background threads: custom HTML on groups page read more, Versatile Banner read more)
Moderator permissions: can mods delete users, and how do you prevent it?Ethsim2 confirmed moderators can delete users by default, then documented a practical workaround using category moderators + enable category group moderation to avoid global powers. read more (reference table: trust-level permissions read more; related staff logging notes read more)
User post deletion fails with InvalidForeignKey (reviewable notes):Canapin found deletion failing due to reviewable_notes referencing reviewables; darkpixlz confirmed it looks like a bug and linked a current workaround: remove the related note/comment first. read more (workaround context: read more)
Onebox/OpenGraph failures traced to server certificate chain:wlandgraf reported Onebox previews failing on their own instance despite working on Meta, then determined the Discourse server couldn’t validate the site’s newer cert chain. read more (handy troubleshooting guide referenced: read more)
Localized tags aren’t slugified (breaking body classes + tag display):RGJ demonstrated how localized tag names containing whitespace/quotes leak into CSS classes and UI, with sam looping in nat to investigate. read more (related mention: slug behavior discussion read more)
Shared-edit wiki history “Edit post” opens the wrong editor and errors on save:hannahbit reported that editing from post history can open the normal editor (not the collaborative one), then saving triggers an error (including a 422 involving tags), temporarily blanking the post until refresh. read more
Multiple form templates per category don’t persist after refresh:donaldsoncd showed that selecting two templates initially works, but after refresh only one remains as the default—raising questions about limitation vs bug in form-templates. read more (reference docs/threads: Introducing Form Templates read more, Creating form templates read more)
Admin UI glitch: changing target audience for “Enable form templates” creates a sidebar “Update Discourse” entry:Noble_Fish posted a reproducible UI oddity in v2026.3.0-latest where toggling audience seems to create an incorrect left-nav entry. read more
Login page logo won’t center when language/theme toggles appear:jack222 reported the top login logo shifts off-center if a language switcher or dark/light toggle appears on the right side. read more
Profile/settings IA continues to bug people (navigation + grouping): discussion continued around reorganizing profile/account/security/interface sections to reduce user confusion, with concrete suggestions quoted into the thread by ToddZ. read more
#Feature
Proposal: “User self engagement” report for CPD-style evidence:Paul_King suggested a user-run report that can summarize engagement over a date range (categories/tags/topics, reading vs posting) to help professionals document participation. read more
How Discourse built “Upcoming Changes” for gradual rollouts:martin posted the companion discussion for the blog explaining how Discourse can stage changes across different site configurations to prevent surprises for admins and members. read more
awesomerobot diagnosed a post-upgrade breakage of “official” theme components and traced it to a missing module import from the Journal plugin, recommending safe mode to confirm plugin interference. read more
Also pointed someone trying to jump directly into Chat toward a helpful theme component. read more (component: read more)
Falco helped untangle the Data Explorer API change that rejects limit=ALL, linked the underlying change, and shared pagination guidance plus the current max-row cap. read more
They also clarified assignment-related API endpoints and parameters for group vs direct assignments. read more
And confirmed delayed AI Agent responses aren’t supported yet, framing it as an automation need and hinting at a future overhaul. read more
martin kicked off discussion on Discourse’s gradual rollout machinery via the “Upcoming Changes” companion topic. read more
nat acknowledged the localized-tag slugification bug report and jumped in to investigate. read more
Separately, they confirmed a fix had been merged for a wiki-editing issue and linked the PR in-thread. read more
Bas chimed in on an “unsilence” UX oddity with the memorable takeaway:
“Task failed successfully”
and asked for more reports if it happens repeatedly. read more
sam connected the localized-tags issue to earlier slug-related work and looped nat in for review. read more (referenced: read more)
gerhard clarified Crowdin behavior around “identical translation already saved,” and offered to review the specific language string in question. read more
pmusaraj responded on a signup/console-error thread by suggesting a controlled test: try a fresh install on the same 1GB droplet size to isolate whether resource constraints are the root cause. read more
That’s a wrap—may all your localized tags be slugified, your limit=ALL requests be pleasantly paginated, and every “task failed successfully” moment end in a clean refresh.
yingdong asked how to localize custom badges/groups on multilingual sites (badgesgroupstranslation), and nat explained why seeded badges are i18n’d but custom ones aren’t—plus a console-only workaround using TranslationOverride.upsert! to create new locale keys (read more).
A tricky edge case popped up where a topic merge left a “solved” record behind, preventing the new merged topic from marking a solution; martin fixed the database state and noted they’ll investigate a preventative fix (read more).
After a change, admins can’t turn topics from read-restricted categories into global banners anymore; dax framed it as an access-control/security safeguard and suggested using unlisted topics in public categories plus Discourse Automation as a workflow workaround (read more, plus the referenced automation topic: read more).
A report about mobile browser text-selection “action buttons” not working ended with supermathie recommending supported browsers (and explaining why chasing obscure/non-store browsers isn’t viable) (read more, background: read more).
The discourse-subscriptions plugin started crashing boot on v2026.3.0 with an USERNAME_ROUTE_FORMAT constant error; sam confirmed a load-order/deprecation tangle and shipped a core PR to remove the deprecation path (read more).
“Multiple form templates per category” didn’t persist because the save button never appeared; awesomerobot reproduced, provided a workaround (disable “simplified category creation”), and then merged a fix shortly after (read more).
Dashboard report UX: a discussion on whether traffic graphs should re-scale the Y-axis when series are toggled; chapoi agreed the intention doesn’t fit this report well and suggested making the scaling smarter (read more).
A gnarly composer issue on iPad where “peek mode” could shove the editor off-screen appears fixed via a core change; chapoi asked for confirmation after updating, and the reporter confirmed it worked (read more).
Localized tags weren’t being slugified correctly (content-localization); nat shared that a fix was merged to clean localized tag names returned from the LLM and migrate existing “dirty” tag names (read more).
Two fresh admin/UI bugs landed: newly created groups not appearing everywhere until refresh (read more, related older thread: read more) and a “topic timer” flow that could lead to a disastrous, unresponsive UI state after scheduling publishing with a missing destination category (read more, related: read more).
#announcements
Danielle announced a new webinar—“Creating & Nurturing a Moderator Program”—and confirmed that registering will also provide access to a recording afterward (read more).
#plugin
The official Discourse Signatures plugin got a solid set of improvements merged by jamie.wilson: group-based restriction, category-based display, first-post-only mode, stricter URL validation, and size limits—all backward-compatible by default (read more).
#extras
The GitHub Action that creates Discourse topics for releases shipped v1.1.0, adding GitHub→Discourse username mapping so release announcements can post “as the author” instead of a fixed service account (read more).
The terminal client termcourse added real-time notifications via MessageBus so topic list updates can appear in a status bar (and sparked discussion about matching Discourse keyboard shortcuts) (read more).
#site-feedback
Feedback continued on Meta’s category re-organization; hellekin shared specific navigation pain points (subwiki “index” links, missing descriptions, and subcategory visibility), with suggestions about where “Data Reporting” should live (read more).
nat dug deep into multilingual badge mechanics—clarifying what’s i18n’d via Crowdin vs. stored as plain DB text, and why custom badge localization currently requires console access (How can badges and groups be localized (multilingual)?). Also shared a merged fix for cleaning localized tag outputs + a migration to repair existing localized tags (Localized tags are not slugified).
sam responded to a boot-crashing regression involving the discourse-subscriptions plugin and followed up with a core PR to eliminate the deprecation issue underlying the failure mode (Discourse-subscriptions plugin crashes boot on v2026.3.0).
martin investigated and fixed a “cannot mark reply as solution after merger” situation by correcting an existing solved-record conflict left behind from the old topic (Cannot mark reply as “solution” after merger).
dax explained why global banners are now gated (no more banners sourced from read-restricted categories), and suggested an interim workflow using unlisted topics plus automation to keep banner templates out of public lists (Can no longer create global banners from restricted categories).
jamie.wilson merged a major upgrade set into the official signatures plugin, including group restrictions and hardened URL validation (Discourse Signatures).
isaac clarified the security rationale behind disallowing banners sourced from read-restricted categories—banner content can become visible to everyone, and admins may not realize that implication when drafting in private areas (Can no longer create global banners from restricted categories).
That’s a wrap: yesterday we learned that badges can be multilingual (sometimes), banners can’t be private (anymore), and topic timers can be… adventurous—so keep your console handy and your drafts well-fed.
LotusJeff kicked off a nostalgia-and-migrations thread asking “How old is your forum?” and started compiling an “elder forums” table, with stories ranging from mailing lists → Yahoo Groups → phpBB → Discourse (read more).
Related: a long-running vBulletin-to-Discourse migration effort came up via elmuerte’s import work (read more) and community anniversary reflections were referenced (read more, read more).
#Plugin
derak announced diskuz Call, a plugin that adds peer-to-peer WebRTC voice/video calls inside Discourse (site handles signaling, media goes P2P with optional TURN) (read more).
If you’re evaluating new add-ons, the canonical plugin install guide remains the starting point (read more).
The ActivityPub plugin thread saw reports of failures when trying to follow @announcements@meta.discourse.org, including “Could not resolve actor” warnings and logs to investigate (read more).
A security-focused heads-up landed in the Sign-In with Ethereum plugin topic: RGJ pointed people to a newer fork and urged an immediate switch due to vulnerabilities found in the older plugin version (read more).
#Announcements
Discourse’s hosted LLM offering increased capacity substantially across plans; Falco shared new limits (e.g. Starter → 200K, Pro → 500K, Business → 1M) plus improvements to model quality, max tokens, and responsiveness (read more).
Background context continues in the broader ai discussions around dev workflows and guardrails (read more).
A new request appeared from someone looking for help installing Discourse on a VPS (including database/SSH setup), with NateDhaliwal pointing to the one-line installer and a practical “quick start” path (read more).
A “sticky notification” report described Discourse showing a notification badge that didn’t correspond to anything unread, prompting troubleshooting (reload, cookies, logout/login) and broader commentary about async UI complexity (read more).
A Chinese-language report said that after chat is disabled, chat-related preferences/settings disappear, and visiting the preferences/chat URL redirects to /latest (read more).
The reporter referenced an older recurring issue thread for historical comparison (read more).
A UI glitch was shared where opening a user card and then scrolling caused the card to appear over the editor in a “funny bug” screenshot (read more).
Upload troubleshooting continued: Lilly tested new-user upload limits and couldn’t reproduce the “only one image” issue under default settings, while others suggested verifying whether the real limiter was embedded media settings or error messaging (read more).
Email-in reliability: a self-hoster reported Discourse stopped polling POP3 with Net::ReadTimeout, despite interval changes, upgrades, and restarts—suggesting something intermittent or provider-related (read more).
A regression report on 2026.3.0-latest: staging showed username + real name no longer displayed together (only username shown), asking for debugging pointers (read more).
Another urgent admin report: a community began logging everyone out and blocking logins with “you can’t log in from that IP address” unless retried several times (read more).
A practical limitation surfaced when merging topics: you currently can’t mark a reply as “solution” after a merge unless you clear the existing solution first—though a fix is in progress (read more).
Related feature discussion on solved UX continues elsewhere (read more).
Banner workflows: users found it hard to create global banners from restricted categories because “Pin topic” disappears when unlisting; a workaround is to use Automation’s “Make Banner Topic” script referencing the unlisted topic ID (read more).
(Automation plugin context: read more)
The DiscoTOC iPad portrait overlay problem has a clear direction: chapoi pointed to a fix via a PR that should resolve TOC rendering over text without a proper background (read more).
A new step-by-step guide explained how to set up Discourse MCP in OpenCode CLI, emphasizing that ordinary-user access is enough and encouraging people to “use your LLM” to follow the instructions (read more).
Companion guide for another client (Codex CLI) was also referenced (read more).
#Extras
The Clip To Discourse Chrome extension shipped v0.19.5 with text selection support, selection-aware templates, and a right-click context menu—plus plans to implement the Discourse User API auth flow (read more).
Relevant spec: Discourse User API keys specification (read more).
Terminal Discourse client termcourse got UX tweaks and localisation updates (including es, fr, de, en), with merefield inviting PRs for more languages (read more).
chapoi weighed in on the “phantom notification” issue, explaining why these problems are extremely hard to solve perfectly given the complexity of modern web stacks (read more).
chapoi answered an ai development-docs question by pointing out that Discourse dev docs are now included in the main repo (context: discussion in the Claude + Discourse dev thread) (read more).
chapoi also linked the likely fix for the iPad DiscoTOC overlay issue (read more).
Falco posted updated capacity limits and performance improvements for Discourse’s hosted LLM service, noting multiple capacity increases since launch (read more).
dax provided a concrete workaround for creating banners from restricted/unlisted topics: use the Automation plugin’s “Make Banner Topic” script with the topic ID (read more).
martin confirmed the current limitation around solution-marking after topic merges and noted a fix is being worked on (read more).
sam responded to a dev question about replacing Markdown with Quarkdown: not possible directly—you’d need to extend markdown.it with the desired features (read more).
That’s a wrap—yesterday we time-traveled through 25-year-old forums, shipped bigger AI limits, and even squeezed in a Discourse-native WebRTC calling plugin… not bad for a single day on Meta.
Canapin suspected a blocked-IP misconfiguration in a “everyone is getting logged out” report, and Falco quickly traced it to a Cloudflare + IP ban foot-gun (everyone appears from one IP), plus a reminder to use the Cloudflare template in app.yml (read more, read more).
Forum content “acquisition”: Timelord asked how to bring content from another Discourse without a full backup/restore, and itsbhanusharma pointed to guidance on moving topics between instances (read more, read more, plus the referenced how-to: read more).
A Chinese-language AI-translation edge case: enabling AI translation also localizes tags and makes them hard to edit; nat suggested enabling the Experimental tag settings page so tag localizations can be edited properly (read more, read more).
Long-form “fix-it” write-up: satonotdead documented a recovery approach for missing upload records after migrating from S3 to local filesystem, including rebuilding uploads DB records and rebaking posts (read more).
Article/course-style publishing on Discourse: Engineer_Abdallah explored using Discourse as a tutorials + course sequence platform (with restricted authorship), and chapoi recommended using Topic List Thumbnails to get images into lists (read more, read more, and the component: read more).
Admin UI nuance: Ethsim2 questioned how about page hidden groups should interact with about page extra groups—specifically whether “extra” viewers (like admins) should still see otherwise-hidden groups on /about (read more).
Theme behavior investigation: a Ghost theme user reported that categories without subcategories weren’t showing view/reply counts; chapoi challenged whether it’s truly theme-related and pointed at the Ghost preview showing counts on a “no subcategory” category (read more, read more, Ghost theme reference: read more).
Attachment link counters regression: a report that click counters no longer appear for uploaded files—whether or not |attachment is present—prompting questions about restoring the prior behavior (read more).
OIDC login troubleshooting: a LinkedIn OAuth redirect mismatch was resolved by ensuring the callback URL matches, e.g. https://discourse.example.com/auth/linkedin_oidc/callback (read more).
ai sentiment backfill: satonotdead hit Don't run this task in production! when trying rake ai:sentiment:populate, and Falco clarified that backfill for the last 60 days is automatic once enabled (read more, read more).
search#tablet: a mobile/tablet report where the floating search widget types characters reversed (“thing” becomes “gniht”) in landscape on Edge/Android; Falco couldn’t reproduce on a newer environment and suggested trying another keyboard (read more, read more).
searchtablet (related): another Edge/Android landscape/portrait issue where the floating search box can’t be closed after rotating back to vertical, persisting across navigations until the device is horizontal again (read more); the reporter also confirmed reproducibility in Safe Mode (read more).
#solved: the new category settings UI appears to make it impossible to disable “Allow topic owner and staff to mark a reply as the solution” after it’s enabled, with the “Solved” section disappearing from the original settings page (read more).
#chat: after disabling chat, chat settings reportedly disappear from preferences and don’t return; a second user confirmed they can reproduce it (read more).
#Feature
Reactions/likes UI: a user asked how to expand “and 6 more…” to see everyone who reacted; Falco said Discourse is working on a new UI component to support this cleanly (read more, read more).
Multisite clarity: supermathie proposed improving the /sidekiq experience for admins on multisite “guest” sites—showing a helpful explanation instead of a confusing error when Sidekiq is only available on the host instance (read more, with prior context link: read more).
Calendar privacy ergonomics: for authenticated ICS feeds for private events, Falco pointed to work already added via PR plus follow-up improvements to make User API Key flows friendlier for non-technical users (read more, PRs referenced: read more, read more).
#Integrations
ai#how-to: Discourse AI Google Programmable Search Engine setup hit a snag as Google now requires at least one configured domain; Falco confirmed the “entire web” behavior is discontinued and said the team is researching alternatives (including leveraging LLM-native web search tools) (read more, read more, plus Google’s deprecation context links shared in-thread: read more, read more).
#Theme component
A new Bilibili inline player theme component was shared as a no-rebuild alternative to the server-side plugin approach, with setup notes and comparisons to the existing OneBox/plugin route (read more, related plugin topic: read more).
#Plugin
Discourse OpenID Connect (openid-connect) discussion continued with a request to sync Discourse groups from OIDC groups, referencing an older PR that implemented it but wasn’t taken further (read more, referenced PR: read more).
#Community Building
A community check-in thread asked “How old is your forum?”, drawing stories ranging from forums founded in 2024 to a week-old install currently stuck at 502 Bad Gateway (read more, read more).
A Dev curiosity resurfaced: “Can Markdown be replaced with Quarkdown?”, with merefield praising the linked repo (read more).
#Using Discourse
Topic list filtering: a question about using /filter while keeping a left-side navigation (like a docs sidebar) referenced the official guide on filtering topic lists (read more, original reference: read more).
Falco was busy across support, bugs, and roadmap signals: they diagnosed a Cloudflare/IP-ban cause for mass logouts (read more), asked for keyboard variability to reproduce the reversed floating-search input bug (read more), confirmed work underway for a better “view all reactions” UI (read more), and clarified that Discourse AI Google search needs new providers now that Google’s prior capability is discontinued (read more). They also noted that AI sentiment backfill is automatic for the last 60 days (read more) and referenced improvements for authenticated ICS feeds in the calendar feature area (read more).
supermathie posted an operational heads-up in an email-delivery thread, linking the breaking/fixing commits and apologizing for the disruption from a merged gem update (read more). They also proposed a UX improvement so admins understand why /sidekiq is unavailable on multisite guests, aligning with the “principle of least surprise” (read more).
nat delivered a quick solution to a tag-localization issue caused by AI translation: enable the Experimental tag settings page so tag localizations can be edited (read more).
chapoi helped guide two separate support threads: for “articles with images,” they recommended using Topic List Thumbnails (read more); and for Ghost theme view/reply counts, they challenged the premise by checking the theme preview and asking for confirmation it’s actually theme-caused (read more).
Yesterday’s vibes: if your search starts typing backwards, just remember—on meta, someone will inevitably suggest palindromes while the team hunts the real fix.
In the last 24 hours, meta logged 42 new posts across 4 new topics—including fresh threads on composer UI overflow (read more), intermittent theme upload failures (read more), recovering missing hosted CDN assets (read more), and embedding Bunny Stream videos (read more).
Top users (posts / likes, with a recent reference post):
In a composer usability thread, 祁同伟 reported that when the editor has “too many buttons,” the ones at the end become inaccessible; replies suggested the toolbar is horizontally scrollable, but the affordance is subtle (and the arrow disappears on touch devices), sparking discussion about better pointer/viewport logic (read more, read more).
A hosted-support question asked how to restore individual missing CDN uploads (one image + two JSON attachments) after a hiccup, highlighting the gap between self-hosted “I know where to look” instincts and the hosted operational toolchain (hosted-support) (read more, read more).
A theme-dev workflow issue: a site intermittently returns HTTP 500 during admin/themes/import.json while uploading via CLI, and the ensuing debugging touched logs, deprecation noise, and isolating third-party plugins as a first step (read more, read more). (Related reference threads that came up: Theme CLI install guide (read more) and installing themes/components (read more).)
Tablet/search UX: someone observed that characters appear in reverse order while typing in the floating search widget, and narrowed it down to the OS “floating keyboard” feature (with follow-up testing planned across keyboards/IMEs) (searchtablet) (read more, read more).
An older-but-active DiscourseAI support thread circled back to debugging missing sentiment output (“no sentiment in 60 days”) and pointed to the self-hosting setup guide for sentiment/emotion as the baseline checklist (aiai-sentiment) (read more, read more).
A signup regression investigation continued: after toggling “enable local logins,” new users reportedly hit failures plus console errors, with logs mentioning missing MaxMind DB files and OAuth callback failures in the Discourse ID flow (discourse-id) (read more, read more).
An attachments/UI detail got attention: the link counter/URL formatting for attachments seems to include a second “dimension-like” segment that makes sense for images but looks suspicious for non-images, raising questions about what the counter should display (read more, read more).
A short, practical embed question: how to get Discourse to inline-embed Bunny Stream (Bunny CDN) videos instead of showing a plain link preview, using a player.mediadelivery.net URL as the example (read more, read more).
A solved support topic on forum acquisition/migration planning saw an update promising dev testing results “in the next week or so,” keeping the thread moving even after being marked solved (read more, read more).
In a “help me install Discourse on my VPS” conversation, the thread evolved from “I’m new to servers/SSH” into practical offers (install help + backup strategy) and alternatives like one-click upgrade tooling, plus a side discussion about legal requests and data access expectations (read more, read more).
#Theme_component
The Banner Featured Links component received a burst of maintenance: replacing deprecated htmlSafe, fixing mobile SCSS issues, improving settings descriptions, tightening HTML validity, and pinning to a newer core version; the update was shared along with an upstream PR for review (read more, read more).
An “anchor links don’t work inside Discourse” report appears resolved: the issue could no longer be reproduced after a core fix landed, and the topic is being scheduled to close unless anyone can still trigger it (read more, read more).
#Plugin
The long-running activitypubexperimental thread gained more diagnostics: a participant shared log excerpts showing repeated handle validation and actor lookups while confirming identical behavior to prior reports—useful breadcrumbs for anyone trying to reproduce (read more, read more).
The Geo Blocking plugin thread clarified Cloudflare specifics: it can work with Cloudflare when configured correctly, but CF-IPCountry is a country code header (not an IP), and the plugin relies on Discourse’s MaxMind database rather than that header (read more, read more). (Cloudflare best-practices doc referenced in-thread: read more.)
#Site_feedback
In the “collaborative content gardening hub” discussion, Canapin described using flags to request edits on older posts, but hit an odd UI limitation where only an “It’s illegal” flag option appeared—prompting a meta conversation about better processes (wiki conversion, mod contact norms) and cross-linking to “user uploaded files monitoring” and “topic gallery” ideas (read more, read more). (Related plugin/topic mentioned: read more.)
awesomerobot dug into the missing horizontal-scroll arrow in the composer toolbar overflow discussion, asking whether a theme might be interfering and confirming the current behavior: the arrow is intentionally hidden on touch devices—while questioning whether that assumption still holds for touch-enabled laptops (read more, read more).
renato contributed two notable updates: a UX refinement idea for the scroll-arrow logic (consider “fine pointer” detection / narrower-screen heuristics) in the composer toolbar thread (read more), and a maintenance closeout in the anchor-link bug report after it stopped reproducing post-fix (read more).
Falco responded to DiscourseAI sentiment debugging by steering the investigation back to the documented self-hosting setup steps—effectively a “verify the pipeline end-to-end” checkpoint for anyone seeing missing sentiment output (read more, read more).
If yesterday had a theme, it was “everything scrolls sideways (including your debugging scope)”—from hidden composer arrows to CDN hiccups and one more embed that refuses to inline.
48 new posts across 3 new topics in the last 24 hours, with fresh threads including a broken theme-component footer template (read more), a sidebar-link URL-normalization bug report (read more), and a question about proxying a forum via someone else’s URL (read more).
Recent activity highlights (source links) das-g and chapoi dug into a theme-component regression around deprecated connector patterns (read more). merefield gave practical mitigation advice for unwanted proxy mirroring of a forum (read more). dax noted that category-specific title placeholders are now available in core (read more).
Other threads that saw notable replies (sampling of the day’s chatter):
ghost theme category metrics rendering (read more), Cloudflare setup notes (read more), ActivityPub actor lookup troubleshooting (read more), Discourse AI tool timeout debugging (read more), automation composer formatting quirks (read more), login/sign-up errors with Discourse ID (read more), AI sentiment backfill questions (read more), and search/filtering with topic voting (read more).
das-g reported a theme “component” footer whose templating began rendering control directives literally, and chapoi traced it to ongoing modernization work (notably deprecated registerConnectorClass) and recommended refactoring toward plugin outlets and modern theme patterns (read more, read more, read more, plus background: read more, read more, read more).
In a #hosting-flavored security/privacy question, ばこん asked how to prevent a “friend” from proxying their forum via another URL; the core guidance landed on policy + enforcement, up to making the forum private and banning obvious mirroring behavior (read more, read more).
A ghost-theme issue showed category reply/view counts failing to render when viewing a category without subcategories; chapoi pinpointed a missing outlet in that display context and later noted a structural change to make the custom elements consistently appear (read more, read more, read more).
A report in Chinese asked about Discourse AI tool-call timeouts (ai); Falco pushed for concrete details (which tool + what request) to move from symptoms to actionable debugging (read more, read more).
Automation formatting (automation): renato confirmed fixes related to escaping/formatting when pasting special markup (like [wrap]) into automation text fields, and discussed the tension between “rich editor expectations” and “automation wants raw-ish text” (read more).
A bug report described sidebar “custom link” normalization stripping the site hostname out of a query parameter for external URLs—breaking redirect-style use cases—along with a workaround involving URL-encoding and DB edits (read more).
In ongoing Discourse ID troubleshooting (discourse-id), pmusaraj suggested regenerating credentials, then pivoted to investigating broader signup configuration after regeneration didn’t resolve 404s for new user creation (read more, read more).
Discourse AI Sentiment setup (aiai-sentiment): a user confirmed dashboards were working but wanted deeper historical backfill; Falco focused the conversation on what time range was actually backfilled so far (e.g., “last 60 days?”) before pushing further (read more, read more).
A regression report claimed “username + real name” display behavior changed in 2026.3.0-latest; follow-up suggested checking safe mode as a next diagnostic step (read more, read more).
A question on the floating search widget reported reversed character order when typing (searchtablet) and asked why the topic was reclassified from “bug” to “support” (read more).
Category creation UX (categories): dax highlighted that Discourse now supports title placeholders per category, and separately confirmed the capability is “now in core” for those looking to customize the topic-title prompt (read more, read more).
Another Chinese-language UX thread (composer) showed that when the editor has “too many buttons,” later buttons can become inaccessible; testing in safe mode affected whether the overflow/arrow UI appeared, suggesting theme/plugin interactions (read more).
#Plugin
ActivityPub (experimentalactivitypub): pmusaraj investigated an issue where an actor like @announcements@meta.discourse.org couldn’t be found, starting by narrowing down the Discourse version and confirming the actor resolved correctly elsewhere (read more).
Topic Voting: users asked for advanced search options tied to votes; the answer suggested using filter parameters (e.g., order:votes, status:open, -tag:) and even saving the filtered URL for others via the sidebar—also referencing a related closed thread for context (read more, read more, related: read more).
chapoi
Investigated a theme-component regression where a footer template stopped rendering as expected, connecting it to deprecations and the Glimmer modernization path, and provided practical direction toward plugin outlets and theme docs (read more, read more).
Also diagnosed a ghost theme edge case where reply/view widgets didn’t appear in certain category views, then followed up with an implementation change to make the elements render consistently (read more, read more).
dax
Shared that Discourse now supports category-specific topic-title placeholders, including a pointer that the change has landed in core (read more, read more).
Falco
Pressed for concrete reproduction details in a Discourse AI tools timeout report—focusing on which tool and what request to enable proper debugging (read more).
Followed up on AI sentiment backfill expectations by clarifying what time window was actually populated (e.g., “last 60 days?”) before exploring extending history (read more).
pmusaraj
Helped narrow down an ActivityPub actor discovery issue by asking about Discourse version and verifying expected behavior elsewhere (read more).
Continued investigating Discourse ID signup failures by recommending regenerating credentials, then requesting a (sanitized) view of login-related site settings once that didn’t resolve the 404s (read more, read more).
renato
Confirmed that automation-field escaping for special formatting (like [wrap]) should be improved after a merge, and explained how clipboard HTML payloads can cause the rich editor to “do the wrong thing” for automation-style inputs (read more).
Yesterday’s vibe: if your footer suddenly starts printing template syntax and your votes need better filtering, at least Cloudflare and plugin outlets are there to keep the plot moving.
diskuz Call, a plugin that adds peer-to-peer WebRTC voice/video calls inside Discourse (site handles signaling, media goes P2P with optional TURN) (