What drove the chatter: reactions UX polish and regressions dominated the day (read more), alongside tag visibility/cleanup discussions (read more) and the ongoing push to make Discourse embedding feel like a first-class comment system (read more).
Interesting Topics
#Feature
brendantheclayboy and others pushed back on the reactions UX change, while chapoi shared an improved “all reactions” panel that supports scrolling/loading more—with remaining layout tweaks in flight (read more).
A thoughtful feature idea asked whether Discourse could support delayed/self-approval posting (or approval by trusted friends) for users dealing with episodic unwellness, to prevent “write on a bad day, regret on a good day” moments (read more).
Feedback from a real-world deployment praised the redesigned embedded comment composer (especially on mobile), while flagging a couple UI bugs and suggesting testing an “always-open” composer to increase engagement (read more).
#Announcements
Site owners experimenting with the “full comment system” embed reported confusing “half-logged-in” behavior and Safari-specific prompts; Falco clarified the logged-out mode and pointed to custom integration issues (notably with Ghost + DoG setups) (read more).
A serious performance report suggested chat replies can silently create thread tracking that bloats over time, leading to Pitchfork timeouts and chat load failures on long-history sites; the report includes query traces and suspected hotspots (read more).
Mobile moderation UX got a detailed teardown: misaligned header elements, cramped spacing, and oversized inputs on reviewables—prompting a cleanup pass and PR from core (read more).
On mobile, the post revision/history modal shows every button label truncated; the suggestion: allow two-line labels and reclaim unused top padding for a more usable layout (read more).
#Site feedback
Meta’s tag taxonomy came under the microscope again: several “restricted” or staff-ish tags appear in the public tag picker, raising questions about what “restricted” should mean in the UX and whether tag visibility should follow category permissions more strictly (read more).
Meta’s ongoing redesign/theme rebuild continues: icon work is being folded into the Lucide Icons component, and small spacing/polish oddities (like upvote container proportions) were spotted and discussed as the new UI settles (read more).
A micro-meta improvement request proposed introducing a dedicated tag for revision/history discussions; the community quickly converged on a concrete tag choice to help future searchability (now using revisions) (read more).
#Plugin
Communiteq published Communiteq Power Tools, bundling a grab-bag of admin enhancements into a single maintained plugin (including exposing “hidden” settings to reduce Rails console dependency), with screenshots and an open invitation for suggestions (read more).
The Discourse Private Replies plugin hit friction with the newer category settings UI; maintainers noted multiple plugins were “caught off guard” and shared a temporary workaround involving disabling a specific upcoming change setting (read more).
#Theme component
The Social Share theme component got a PR to allow configuring popup dimensions (or switching behavior), addressing the hard-coded default being too small for many share widgets (read more).
Composer Button Bonanza sparked a useful “docs vs behavior” moment: keyboard shortcuts weren’t firing due to a documentation mistake about the shortcut format (use shift+k, not shift-k) (read more).
A recurring question about automating Discourse access via Python resurfaced: discussion centered on public endpoints vs API keys, ToS responsibility, and the practical difference between “exploration/dev tooling” and “automation/scraping”—with core folks reiterating rate limits and intent matter (read more).
A user trying to enable an AdSense trust-level control discovered it’s a hidden site setting; guidance covered how to set it via Rails console and what “normal” console exit behavior looks like (read more).
chapoi shepherded the reactions UX fix forward, sharing a “live on Meta” preview and confirming the new placement standard (“all displays on the left”) in the reactions rework thread (read more), and also confirmed the “keep reactions in one place” request is now bundled with that same work (read more).
zogstrip landed or referenced multiple fixes: a mobile scrolling issue in the reactions panel was already resolved with a linked commit (read more), continued investigating tag visibility edge-cases on Meta (read more), and tackled UI regressions like the backups breadcrumb separator race condition (read more) and sidebar icon search regression (read more).
supermathie weighed in on the “Python tooling vs automation” debate to clarify intent and acceptable experimentation boundaries (read more), raised an important identity/MFA propagation question for Discourse ID and federated login flows (read more), and filed a sharp bug report arguing outgoing emails should still link to topics even with “private email” enabled (read more).
david provided practical guidance on API tooling: public reads are supported (even without an API key), but bot requests face stricter rate limits and protections; the core message was to prefer keys where possible and keep usage respectful (read more).
Falco responded to embedded-comments feedback, highlighting mobile-first design intent and noting follow-ups still in progress (toolbar width, send-on-enter), and also linked a fix for an embed sizing bug via a core PR (read more). He also clarified “logged-out embed mode” behavior and pointed out Safari-specific consent prompts in a separate embedding support thread (read more).
manuel continued polishing the Meta-branded theme rebuild, noting icon work has been merged into the Lucide Icons component and playfully acknowledging “synchronous magic” when UI quirks seemed to resolve mid-report (read more).
pmusaraj explained that the standards-based path for passing MFA context is OIDC, while Discourse ID is currently OAuth2-only—laying out complications around IdP-provided MFA signals and the possibility of needing 2FA at the ID layer (read more). They also jumped into email-delivery troubleshooting, suggesting misconfiguration and asking about hosting context (read more).
sam gave the definitive protocol answer on OAuth/SSO URLs: a # fragment in a provider URL is a violation (fragments are client-side only), helping close out a puzzling configuration issue (read more).
awesomerobot shipped fixes for mobile moderation workflows after a detailed report, linking the PR that improves alignment/spacing and other reviewables issues (read more), and separately shared an “attempt at a fix” for modals opening above the viewport on mobile (read more).
“Our most exclusive support plan: just think about it, and it is fixed.” — manuel (read more)
And that’s a wrap—may your reactions menus scroll smoothly and your bugs fix themselves the moment you think about them.
Where the conversation clustered: the Meta homepage/layout refresh and early Blocks API rollout drove a lot of feedback (read more), while nested replies testing continued to surface UX/navigation edge cases (read more). Several admin/product updates also landed in #Announcements, including Data Explorer charts (read more) and more flexible approvals (read more).
“This was built using our new Blocks API… still an early preview.” — derek (source)
Interesting Topics
#Site feedback
The Meta Branded theme homepage got a dashboard-style refresh (events, hot topics, contributors, “watch & listen”), and feedback quickly honed in on who the new homepage is for and whether video content should be as prominent (read more).
Ongoing debate about Meta’s reorganized category structure continued: discoverability, long category paths in composer/autocomplete, and frustration linking #bug now that it lives under a parent category (read more).
A potential performance/UX snag was raised around disco-toc on very long, heading-heavy posts—safe mode appeared to render faster, suggesting a theme/component interaction worth digging into (read more).
In the “support categories” process discussion, Lilly argued that “mark as solution” often ends up incorrect or unhelpful in practice, with follow-on discussion about OPs marking their own posts and how to improve outcomes (read more).
#Announcements
The Data Explorer plugin gained more charting options and smarter auto-selection of chart types based on result “shape,” improving quick visualization of query outputs (read more).
Category moderation got a boost: topic/reply approvals can now be targeted (“everyone except group X” / “no one except group Y”) and settings were consolidated into a new Moderation tab in category settings (read more).
Bulk moderation got a practical upgrade: admins can now pin/unpin topics in bulk, choosing global vs category pin + timeframe in the bulk actions flow (read more).
Topic Voting improvements shipped: better vote button access while scrolling, opt-in notification prompts after voting, and “Hot” sorting refinements for ideas categories (read more).
A mobile UX papercut: a very long button label in the user deletion modal gets truncated; awesomerobot proposed a cleaner “select deletion type, then confirm” interaction pattern (read more).
Calendar/event display on mobile: an event’s date next to the title lacked styling and was confusing at a glance; a consistency fix was queued (read more).
“Empty space below unanswered topics” highlighted how reserved UI space (e.g., “person is replying”) can create layout inconsistencies between 0-reply and replied-to topics, prompting discussion of outlet placement and bounce prevention (read more).
A new UX suggestion: on narrow mobile viewports for anonymous users, make Sign up easier to find by placing login/sign-up actions in the hamburger/sidebar menu (linked to the long-running older request) (read more).
AI translation reliability concerns resurfaced: skipped locales (e.g., Portuguese) and how to handle transient LLM 503 errors without runaway token costs; staff clarified current retry/backfill behavior and expectations (read more).
Nested Replies testing kept revealing “find the unread replies” challenges and navigation expectations (e.g., a stronger “parent context” traversal), plus discussion of how nested reading shifts attention to branches, not “read all” (read more).
A neat formatting workaround: to “force” table columns to stop compressing (and become scrollable in practice), using (non‑breaking spaces) can prevent undesirable wraps in table headers/cells (read more).
derek introduced the updated Meta Branded theme homepage and engaged with feedback about content placement and logged-in vs logged-out behavior (homepage update; Blocks API note here).
awesomerobot emphasized that the homepage/layout changes aim to make Meta more welcoming beyond developers—particularly for admins and community managers (context)—and proposed a redesigned user deletion flow to avoid unwieldy button copy (mockups + approach).
lindsey shipped two admin workflow improvements: more flexible category-level approvals (details) and bulk pin/unpin for topics (how-to). She also announced a batch of Topic Voting UX improvements (read more).
nat posted the Data Explorer charting improvements announcement (read more), confirmed a localization fix for “one un-translated topic in an otherwise translated list” (fix deployed), and clarified AI tag translation scope/limitations (tags aren’t independently disable-able from other translation targets) (read more).
Falco continued to pressure-test nested replies UX, pointing back to the historic rationale for flat discussions while acknowledging gaps like better parent traversal in non-linear threads (nested replies thread; related context link here). He also followed up in the full comment system embedding area, noting Safari constraints and reiterating how Discourse’s automatic dark mode helps keep embeds in sync (embed follow-up; dark mode feature reference here).
markvanlan clarified that the flat/nested toggle is now behind a group site setting (staff-only by default) and discussed notification-linking challenges when multiple replies are consolidated (toggle note; notification issue analysis here).
supermathie updated several support threads: confirming a fix/merge for a Discourse MCP permission issue affecting about.json (status), recommending a safer GeoIP file management approach using symlinks rather than mounting the entire vendor data directory (suggestion), and advising that diagnosing a 500 error on an AI embeddings endpoint needs logs (Rails + /logs) rather than guesswork (read more).
pmusaraj responded on AI translation retry expectations and token-cost tradeoffs, noting Discourse avoids aggressive retries but does backfill/retry over time (read more; follow-up here). He also explained how to disable local logins while keeping OIDC signups workable (and how auth immediately affects the splash vs immediate redirect) (walkthrough).
sam jumped into a performance-heavy chat bug report with an optimization that produced a large improvement in testing, emphasizing the need to shed load safely even if counts become slightly approximate (read more).
jordan.vidrine suggested tightening confirmation UX copy: if the modal body already explains irreversible deletion, the button label can be shorter (e.g., “I understand”) (read more).
Yesterday’s Meta felt like a choose-your-own-adventure: new homepage blocks up top, nested reply branches down below—just try not to get lost in the thread forest.
Admins can now manage “permanently delete” without console support: lindsey shared an update that exposes can permanently delete to admins with extra safeguards, including explicit confirmation modals and a 5‑minute delay between soft delete and permanent delete actions (read more).
More charting options land for Data Explorer (and hosted rollout clarifications): follow-up discussion covered testing expectations and timing for hosted deployments, with staff confirming it should appear after the next deploy (read more).
#site-management
Auto-tagging topics using Discourse AI + Automation: a new guide explains how to configure AI triage to apply tags automatically, including prerequisites like enabling plugins and setting up an Agent persona (read more). Related docs include Discourse AI, Discourse Automation, the LLM settings page guide, and AI bot personas.
#plugin
Serve Discourse content as Markdown for LLM-friendly ingestion: benword released a plugin that returns “cooked” content as Markdown when clients request Accept: text/markdown or append .md to URLs, aiming to reduce token costs and simplify downstream processing (read more). pmusaraj highlighted the value of leveraging Discourse’s cooking pipeline for richer Markdown output (read more).
#theme-component
Theme component: “Show hidden categories” (with a nod to existing solutions): pfaffman shared a component that adds a “fake category” entry that links to a group page (to request access/join), and the thread quickly compared it to Category Previews and discussed possible differentiators (like category boxes support) (read more). Installation references: How to install a theme/component and the Beginner’s guide to using Discourse Themes.
Theme component: combined mobile “Sign Up / Log In” UX: Lilly introduced a component to replace the mobile login button with a combined flow, then followed up with an update that opens a modal with links to signup/login, crediting an idea from Moin (read more). This also connected back to the UX request around anon auth affordances on mobile (read more).
Google Photos album oneboxes look like single images: Ed_S reported that Google Photos album links onebox as a lone cover image with no clear indication it’s clickable or contains multiple photos; pmusaraj tagged it pr-welcome for contributors to improve (read more). The thread also referenced prior behavior/regressions in “Onebox support for new Google Photos”.
Content Localization SEO: ?tl= translations should be self-canonical: a report argued translated crawler pages are effectively “killed by canonical” because they canonicalize to the base language URL; nat agreed that each language variant should be self-canonical and said the team will investigate (read more).
“Each language variant should be self-canonical.” — nat (source)
Editing posts can explode raw size due to underscore alt-text escaping: a detailed report shows repeated edits double-escape underscores in image alt text, causing exponential growth in backslashes and eventually making posts uneditable due to length limits; zogstrip noted it’s likely a regression and started investigating (read more).
API DX feedback (headless frontends) + draft deletion auth inconsistency: one new thread proposed clearer pagination / post-stream separation for Next.js-style headless builds (read more), while another uncovered DELETE /drafts/{key}.json returning not_found via API-key auth unless ?username= is provided—prompting a consistency fix proposal (read more).
Reachable-mention warnings fail when usernames contain uppercase: thoka found that mentioning @SomeUser can bypass composer “not reachable” checks because the mentions endpoint returns lowercase usernames without user_reasons, so warnings never appear (read more). This investigation grew out of behavior observed in the long-running Private Topics Plugin thread.
AI translation + locale detection: Portuguese skipped and controls clarified: a deep dive described three overlapping issues (locale mis-detection, API failures, and category-targeting edge cases), and pmusaraj pointed out how to override locale via the composer controls and acknowledged category support gaps worth improving (read more).
#site-feedback
Meta homepage breakage fixed after a core change: Moin reported the homepage looking broken, and derek explained a recent core update changed how the custom homepage model is handled; the theme was updated and the issue resolved (read more).
#extras
Termcourse adds hi-res image expansion support (terminal-friendly upgrades): the terminal client gained better image expansion support (chafa/sixel/magick) for terminals that can display it, with implementation details linked via its PR (read more).
Webinar announced: “Community Retention: How to Define and Drive Return Behavior”: Danielle shared registration details and outlined a retention framework focused on return behavior (not just “more activity”), plus practical levers like onboarding moments and recognition (read more).
Sign-off: Yesterday’s highlights had everything—canonicals, oneboxes, and backslashes multiplying in the dark—just another day on Meta where the edge cases come out to play.
A second Domniq-adjacent showcase landed: a configurable premium landing page plugin for logged-out visitors (hero variants, community stats, trending topics, FAQs) in Domniq - A Premium Landing Page for Discourse Preview.
A small-but-impactful fix landed: “clearing advice” didn’t actually clear until a PR was merged; the merge confirmation is in Clearing advice doesn’t actually clear it.
#Feature
Incident responders asked for a notification level beyond Watching: a proposed “Obnoxious” level that could force desktop notifications on specific threads only (rather than enabling site-wide push) in New notification level: Obnoxious.
A request to make a useful moderation/power-user tool more shareable: the “view posts by @user” filtered-topic view should be linkable/shareable without insider knowledge in Make the “view posts by @user” filtered topic view shareable / linkable (with the current ?username_filters= behavior cited in-reply at post #2).
CI pain point: the minio_runner install script reportedly fails to follow a redirect, breaking shared GitHub Action workflows and leaving Rails system tests red in Minio installer breaks CI.
Helpdesk workflow scaling: a community running a busy support mailbox asked whether volunteers can “archive/hide” requests only for themselves (without archiving for everyone) in Support Mailbox archiving for some and not others.
#Theme
Theme breakage after core changes: the long-running “FKB Pro” theme thread reported a fatal frontend crash tied to the removed ember-this-fallback/js-component shim in FKB Pro - Social theme.
#Feature (Embedding / Analytics)
Embedding analytics surfaced sharp edges: a publisher reported double-firing analytics (page_view duplication, GTM scripts injected twice) when Discourse is embedded, with charts and detailed impact notes in Tecnoblog’s Experience With Discourse Comments.
In the last 24 hours, meta saw 69 new posts across 8 new topics. (Highlights include a new home for show-and-tell ideas and multiple product/UX updates: read more, read more, read more)
mcwumbly proposed a lightweight “post it in General and tag it show-and-tell” pattern for people sharing cool Discourse-related work—sparking immediate examples like a topic-embedding cluster map idea from piffy and a quick event countdown component from Lilly (read more, example post, example post).
#Announcements
Discourse is simplifying default email subject lines to feel less technical and reduce redundancy; early feedback included concerns about losing category context in group-based setups and when [PM] is helpful as an explicit indicator (read more, discussion, related: subcategory display options in email templates).
Emoji picker search now supports keywords in 48 languages, resolving a long-standing multilingual pain point and closing the loop with older requests about translated emoji aliases (read more, earlier request: translated emoji aliases, older support Q: other languages in emoji search).
A proposal to start a community-written “Meta Monthly Newsletter” drew pragmatic pushback: concerns about “user/staff of the month” turning into a popularity contest, and questions about what value it adds beyond official posts, AI summaries, and leaderboards (read more, critique](MNN Meta Monthly News - #4 by Canapin)).
A solved composer regression report (“composer ignores default_composition_mode”) turned into a plugin-hunt; safe mode was recommended to narrow down conflicts, with suspicion landing on third-party components (and a reminder that safe mode doesn’t require downtime) (safe mode guidance).
Embed users reported a serious “can’t type into the first comment” issue (plus iOS/Safari scroll quirks); follow-ups stressed impact on real readers and highlighted ongoing embed-related improvements being tracked by the team (read more, follow-up](Tecnoblog's Experience With Discourse Comments - #36 by Falco)).
When switching translation LLM settings mid-stream, a key question emerged: does Discourse redo translations? The answer: existing translations remain, and the new model handles only what hasn’t been translated yet (read more, answer](What happens to translations when LLM changes? - #3 by Falco)).
SEO + localization: confirmation that translated pages using ?tl= won’t rank as separate pages because canonicalization points search engines back to the original content (confirmation).
Admins changing a user’s email still hits awkward friction: verification links can fail with “Access Denied” while logged in as admin, prompting calls for a more seamless workflow (with workarounds via impersonation or console-based updates) (read more, console workaround reference](Change staff email address from console)).
#Feature
A thoughtful request explored “future self” / trusted-friends post approval for users with episodic unwellness; the conversation widened into ideas like “undo send,” scheduled posting, and even opt-in AI-based “are you sure?” drafting feedback (read more, undo-send tie-in](The awkward mishap of premature posting - #14 by NateDhaliwal)).
A bump request for emailing .ics calendar invites into group inboxes tied into ongoing Calendar/Events plugin improvements, connecting feature needs to broader project planning (read more, roadmap reference](Current Projects - April 2026)).
A user flagged a perceived problematic symbol in the Graceful theme’s background pattern; replies suggested it’s likely a stretch, and reminded that admins can swap the background if desired (read more).
Dev/install docs upkeep: a nudge that improvements to “Install Discourse on macOS for development” should likely be incorporated into the first post for discoverability (read more).
Self-hosting storage layout: clarification about disk usage split between /var/discourse/shared/standalone (forum data) and /var/lib/docker (images/overlay), as part of a question about putting them on separate volumes (read more).
lindsey announced upcoming default email subject line cleanups intended to reduce technical clutter and improve approachability, then invited feedback on edge cases like category/group context and PM labeling (announcement, community concerns](Simpler email subject lines - #2 by alehandrof)).
sam helped troubleshoot a “composer ignores default_composition_mode” report by encouraging safe-mode testing and isolating third-party plugin interference, leading to a likely culprit identified during debugging (diagnosis).
nat confirmed an important SEO implication for localized content: translated pages using ?tl= won’t rank independently due to canonical behavior (confirmation).
Falco weighed in across multiple fronts: explaining leaderboard anomalies can arise via private activity or external point-awarding systems (leaderboard context), reassuring that switching translation LLMs won’t trigger a full re-translation backlog (LLM translations), and shipping multilingual emoji search—then closing the loop by pointing older support threads to the new announcement (emoji announcement, back-reference](How to support other language in emoji search? - #2 by Falco)). They also followed up on embed/comment UX breakage reports in a high-impact publisher use case (embed follow-up).
That’s a wrap: yesterday’s meta felt like equal parts polish and play—tidying inboxes, teaching emoji search new languages, and still finding time to show-and-tell the fun stuff people are building.
kirupa showcased a show-and-tell experiment: a Discourse forum “revived” with AI bots that each have personalities and posting behaviors, sparking debate about what community means and whether bots can be a legitimate “daily briefing” tool (read more; discussion pushback: read more; team reaction: read more)
fuse wondered if Discourse should notify contributors when a topic is deleted or becomes inaccessible, after a thread seemingly vanished due to a privacy mishap—prompting a clarification and apology from staff (read more; staff follow-up: read more)
A quick shout-out landed for recent improvements to releases.discourse.org readability, with mcdanlj noting the site is “a lot easier to read now” (read more)
#Announcements
The emoji picker gained language-aware search, and follow-up questions immediately popped up: custom emoji naming/translatability and whether announcement tagging should include localization (read more; custom emoji question: read more; tagging suggestion: read more)
“Wiki rollback” turned out to be a permissions edge case: category moderators can’t use the “Revert Edit Revisions” button—even if they feel like “a moderator”—and the solution pointed straight at the permissions matrix (read more; solution: read more; permissions reference: read more; related wiki guide thread: read more)
AI translations troubleshooting: one admin reported huge daily token usage with zero translation progress, and Falco suggested enabling verbose logs and inspecting AI API audit-log entries to verify what’s actually happening (read more; staff guidance: read more; related ai plugin overview: read more)
An automation + ai “triage agent” kept flagging every post because the model appeared to treat “Examples” as part of the content under review; Falco recommended using Triage with AI Agent + the flag tool rather than forcing string-only responses (read more; staff workaround: read more)
A self-host install attempt on HestiaCP ran into port/proxy confusion plus a GitHub-related snag, with the OP sharing Nginx template details and asking which reverse-proxy approach is “right” (read more)
“Logs sent to wrong S3” got a pragmatic debugging angle: check for anything outside Discourse (bind mounts, cron, rclone, aws s3 sync) that might still be syncing to the old bucket even after config changes (read more)
Monetizing instructional videos: a new admin asked about selling paid access to videos inside Discourse; replies leaned toward hosting video offsite (e.g., members-only YouTube) or using a points/paywall-like plugin approach (read more; offsite hosting suggestion: read more; points-plugin idea: read more)
#Self-hosting
Disk layout flexibility: clarification that /var/discourse and Docker storage don’t need to live on the same volume—Discourse “doesn’t know or care”—as long as your ops story remains sane for future maintainers (read more)
#Community Building
A practical mini-guide showed how to connect DBeaver/TablePlus to Discourse Postgres by mapping a port, locking it down with firewall/Tailscale, and adjusting auth—aimed at safer “real GUI” DB access than the built-in Data Explorer (read more)
#Plugin
Locations plugin sponsors got an update: early-access invites went out, sponsor lists are reviewed daily, and a staged migration plan to public repo was reiterated (read more)
Trading Buttons plugin users reported a recent Discourse update seemingly disabled the plugin and removed category-level enablement options, raising compatibility and regression questions (read more)
#Theme
The #Theme thread for FKB Pro logged a post-upgrade break: after updating to v2026.4.0-latest / Ember v6.10.1, an error about missing ember-this-fallback/this-fallback-helper reportedly made the forum unusable—requesting a fix path (read more)
chapoi joined the bot-forum discussion, praising the styling and framing the bots less as “community” and more as an interesting way to stay updated on niche interests (read more)
mcwumbly responded to the “deleted/private topic” surprise, apologized for crossed wires, and indicated the team is untangling the situation so the missing content can be appreciated again (read more)
Falco handled two AI-adjacent support threads: advising verbose logging + auditing API log entries for AI translations that burn tokens without progress (read more), and recommending a more robust automation pattern (tool-calling via flag) for AI triage agents that were misusing “Examples” (read more)
Yesterday’s moral: whether you’re herding bots, reverting wikis, or chasing runaway translation tokens—meta was in full “debug the future” mode.
itsbhanusharma — 1 post / 1 like (noting parts of passwordless flow are already possible: read more)
merefield — 1 post / 1 like (showing off a “snazzy 3D view option” update: read more)
Falco — 1 post / 1 like (explaining why AI triage examples were mis-specified: read more)
@team standouts:mcwumbly (4 posts / 4 likes) and Falco (1 post / 1 like), per their activity in support + UX + community threads (read more, read more).
Interesting Topics
#Site feedback
nathank shared excitement about the direction of the Meta-branded theme rebuild—especially how the custom homepage work and emerging Blocks API tooling could help smaller orgs simplify their overall web stack (read more, read more).
#Feature
The “post approval by your future self / trusted friends” idea continued to evolve, with RGJ pushing back on framing this as simply “accountability training,” while ted broadened the use-cases (e.g., rage-bait, drunk-posting) but emphasized the need to work closely with the impacted user to validate what should be productized (read more, read more, read more).
Discourse ID forums got a practical update: mcwumbly confirmed users should now be able to change their username/name directly in user settings even if the account was created with discourse-id (read more, read more).
A new login feature request asked to decouple passwordless “email magic link” login/signup from enabling local password authentication, aiming for “local accounts + email verification + no local passwords” as a first-class configuration (read more). The replies ranged from “this is already possible” (read more) to the blunt suggestion that users should just use password managers (read more).
A related auth configuration question asked whether allowed email domains is validated against the email returned by OIDC at account creation time (openid-connect, login) (read more).
Discourse AI triage debugging: markschmucker reported examples causing “flags every post” behavior, and Falco explained the key nuance—examples are sent as prior turns, so they must mimic the expected LLM response (including tool calls), and for simple cases examples may be unnecessary if the prompt clearly describes when to call the tool (automationai) (read more, read more, read more).
On monetizing community video content, ted highlighted that once creators are paid, complexity increases beyond technical implementation into legal/operational considerations (read more, read more).
#Extras
A new tool, Discourse Shortlink Router, proposed a support-friendly way to swap long admin URLs for a short domain that redirects to the same path—followed by an intense privacy/trust back-and-forth about logging, cookies, and what the service operator can see (read more, read more, read more).
The ICS → Discourse Importer thread added a subtle but meaningful behavior note: the --time-only-dedupe option isn’t purely time-based because it still considers “close enough” locations—helping treat room changes as a “new topic surfaced in Latest” signal while reducing feed noise (calendar-and-eventrest-api) (read more, read more).
Jagster flagged that public edit history visibility doesn’t appear to cover changing the author/owner of a topic/first post—creating potential confusion for admins who post on behalf of users and then transfer ownership; mcwumbly suggested it looks like a bug or missing feature and moved it for UX discussion (read more, read more).
A mobile UI report about overlong titles not wrapping properly looks like it may already be fixed: mcwumbly tested across several themes (Horizon, Foundation, Meta Branded) and couldn’t reproduce, suggesting affected sites may just need an update (mobile) (read more, read more).
#Community Building
Planning for change management: a new thread asked how to reconfigure an existing community around a new product launch, with follow-up questions probing whether it’s a shift from single→multi product and what the motivator is—plus a suggested “audience venn diagram” approach (customer-success) (read more, read more, read more).
#Self-hosting / #Self-Hosting
An migrations-tooling thread reported IPBv4 migration pain points: avatar import inconsistencies, handling an already-existing admin user (and posts not migrating as expected), link rewriting gaps, reaction conversion inconsistencies, and even dropped text inside <a href> tags (read more, read more).
In the ongoing Cloudflare best-practices topic (how-tocloudflare), sandra.mccollum described two issues (a blank login screen on first access and embedded PDFs not rendering) that persist even when pausing Cloudflare—prompting a call for debugging strategies (read more, read more).
#Plugin
The long-running “Community Network Visualisation” plugin thread got a fresh highlight: merefield noted it’s received more love and now includes a 3D view option, complete with screenshots (read more, read more).
mcwumbly confirmed a recent improvement for discourse-id sites: users can now change username/name directly in settings even when created via Discourse ID (read more).
They also handled a UX-triage moment by flagging author-change visibility as likely a bug/missing feature and moving it for discussion (read more, read more).
On the community side, mcwumbly asked clarifying questions to better understand the context of a reconfiguration request for a new product launch (read more).
Finally, they suggested a likely resolution path for a mobile title-wrap report by noting it wasn’t reproducible on current themes and may already be fixed upstream (read more).
Falco diagnosed why Discourse AI triage “examples” were backfiring: because examples are sent as previous turns, they must match the expected LLM response format (including tool calls when relevant), and simpler prompts may work better without examples at all (read more, read more).
That’s a wrap—may today’s support links be shorter, your magic-link logins smoother, and your mobile titles finally wrap the way they should.
A legal/terms clarification thread asked whether Discourse “requires” users to be 13+, and whether self-hosted communities can choose otherwise; replies cited Meta’s ToS language and pointed out the difference between self-hosting versus CDCK-hosted obligations in Age requirement for Discourse.
A support question noted that custom badge images appear to be missing alt text (as flagged by accessibility scanners), asking whether this needs a core fix or a site-side workaround in Custom Badges are not applying Alt Text.
A “Kali forums” UI oddity turned out to be reproducible only with site customizations enabled; it was ultimately treated as off-product and closed with guidance to check themes/components and safe mode in Kali Forums Bug (see also Safe mode).
A UX/permissions friction point: admins can copy a query URL that works for them, but non-privileged users get a 403; the thread proposed a “shareable/view URL” or button to generate group-report links in Sharing a Data Explorer Query.
A Chinese-language UX report noted inconsistent “delete/discard” icons between the composer and post-edit UI, possibly tied to earlier discard-confirmation UI changes in 编辑器删除图标不一致 (related: Do you want to discard your post?).
A cookie audit question asked what cookies the WP Discourse plugin sets; the answer clarified it does not set its own cookies and relies on standard WordPress auth cookies for DiscourseConnect in Cookie information request.
chapoi closed an off-product support request after confirming it was specific to a third-party site’s customizations, in Kali Forums Bug.
Sign-off: After a day of debating age gates, wrestling scrollable Data Explorer tables, and trying to get event notifications to behave, at least we can all unwind by polishing a fresh set of theme blocks in Verso-inspired calm.
The biggest “news” moment: the April 2026 release notes landed in #Announcements — read more
Interesting Topics
#Announcements
lindsey shipped new Topic Voting badges (Daydreamer → Visionary) to celebrate idea topics that earn votes, and enabled them on Meta too (topic-voting) — read more (plus the earlier plugin improvements context: read more)
The April 2026 monthly release post went up, pointing everyone to the full 2026.4 changelog (release-notes) — read more
After upgrading to 2026.4, a “Document tree depth limit exceeded” error surfaced in crawler middleware logs; Falco requested a reproducible URL and later shared upstream fixes to apply — read more (follow-ups: read more, read more)
A data-explorer report bug where results were stuck at 5 rows was confirmed and then quickly resolved by nat — read more (fix confirmation: read more)
Scheduling a topic via the automation plugin appeared to break image uploads (works in normal topics, fails in “planned threads”), with workarounds discussed — read more (related alternative: Topic Timers for scheduling — read more)
A recurring governance question: age requirements & verification on hosted Discourse, with legal constraints explained and privacy-preserving verification approaches linked — read more (team clarification: read more)
Moderators asked for a way to force users to edit low-quality/AI-generated topics; suggestions included custom flags + staff-only UI approaches, plus category approval tooling references — read more (custom flag + hide workflow: read more, approvals reference: read more)
A post-update styling regression made category badge font colors change while scrolling; safe-mode debugging and a quick CSS fix restored consistency — read more (CSS fix: read more, investigation note: read more)
A Chinese-language support thread asked where to enable allow_user_api_key; it turned into a pointer to the canonical spec and hidden-setting documentation — read more (spec reference: read more, hidden settings explainer: read more)
A self-host evaluation hit confusion around GitHub issue comment sync using the Code Review plugin; discussion clarified expectations vs. configuration (and plugin choice constraints) — read more (plugin reference: read more)
Theme authors asked for clearer guidance on Blocks + “skills” documentation; manuel pointed to the compact SKILL.md and explained the shift from PluginOutlets to layout frames and block registration patterns — read more (documentation pointers inside: read more)
The Discourse AI for Enterprise Office Hours replay was shared publicly, highlighting semantic/conversational search and “human-in-the-loop” automated moderation — read more (background on webinar structure: read more)
#Feature
A long-running gamification request for per-leaderboard scoring values was celebrated as merged, unlocking much more granular scoring configuration — read more (screenshots + excitement: read more)
A new paid request sought help “productizing” a Discourse community (theme QA, member portal/profile work, conditional links, possible auth questions), with the thread quickly converging on scope clarity + maintainable theming — read more (scope clarification: read more, maintainability concerns: read more)
#Plugin
The Discourse to Markdown plugin discussion explored how Discourse MCP could use Accept: text/markdown content negotiation (falling back to JSON when unsupported) — read more (MCP cross-link: read more, integration idea: read more)
lindsey introduced and enabled the new topic-voting badge set on Meta — read more (enabled confirmation: read more); also tied related vote recognition back to older feature requests — read more. On the calendar-and-event front, she closed the loop on multiple “completed” items: event details now populate .ics exports — read more — and “All day event” support in the modal was reiterated across related topics — read more, read more. She also formally closed the “default calendar view” request thread — read more.
david posted the official April 2026 monthly release announcement (release-notes) and pointed to the complete 2026.4 changelog — read more.
Falco investigated the 2026.4 crawler middleware error (“document tree depth limit exceeded”), asked for a triggering page, and later linked fixes (cc’ing nat) — read more, read more. He also advanced debugging on embedded comments’ mobile horizontal scroll behavior — read more — and noted a gamification enhancement had merged — read more.
pmusaraj helped narrow down an embedded-comments horizontal scrollbar issue as likely “admin-only,” then linked the core PR expected to resolve it — read more, read more.
awesomerobot clarified that hosted customers must comply with applicable regional regulations (including age-verification requirements where relevant) — read more.
supermathie cited Discourse hosting terms around “Special Data Regulations” (incl. COPPA), explaining why hosted customers can’t simply opt out — read more.
Danielle shared the AI for Enterprise Office Hours replay, summarizing AI Search and automated moderation capabilities for enterprise communities — read more.
chapoi guided safe-mode debugging and theme/component isolation for the category badge color regression, and noted the team would investigate the root cause — read more, read more.
fzngagan suggested a practical moderation workflow (“Something else” flag → hide post → prompt edit) while acknowledging limits around custom messaging — read more.
Yesterday’s vibe: we handed out shiny new voting badges while chasing an elusive admin-only iOS scrollbar—a classic Meta combo of celebration and sleuthing.
Most-referenced threads that saw fresh replies (quick index):
Announcements: TL3 defaults read more, Topic Voting badges read more, email subject lines read more
UX: hidden profile invite tab read more, invite button behavior read more
Bugs: MediaWiki oneboxes read more, YJIT enablement confusion read more, schema “suggestedAnswer” field follow-up read more
Dev/Plugins: OIDC group sync read more, Minio CI break note read more, Workspace groups progress read more, Discourse→Markdown plugin/MCP discussion read more, OIDC plugin docs (referenced) read more
Themes/TCs: YouTube/Vimeo upload TC permissions read more, FKB Pro theme Ember import failure + PR read more
Admin/How-to: group owners visibility question read more, trust level reference edit noted read more, Trust Level permissions reference (linked) read more
Community/AI: support-bot tooling discussion ping read more, Doc Categories plugin (used in LMS setup) read more
Interesting Topics
#Announcements
martin announced an upcoming change to make Trust Level 3 easier to attain on very active forums by adjusting caps and promotion duration (via an opt-in upcoming change), with follow-up questions about whether prior customized defaults could be reset read more and read more. trust-levels
The new Topic Voting celebration badges sparked questions about backfills and notifications; lindsey clarified that backfills will happen, but notifications are limited to the last two weeks and only the “highest” qualifying badge will notify to avoid spam read more. badgestopic-voting
The “simpler email subject lines” discussion continued with a focus on whether email should clearly distinguish PMs from public replies, especially for people who reply directly from their email client read more. email
A UX inconsistency was reported where an Invite button appears on other people’s profiles and still creates invites “as you,” prompting debate about whether the feature should exist at all, or be redesigned to truly support “invite on someone’s behalf” read more and Lilly’s breakdown of why it feels misleading in practice read more.
Closely related: hidden profiles can still display an Invite tab, which feels contradictory to “this user’s public profile is hidden,” and links directly into the confusing invite-creation flow read more (with the cross-reference back to the invite-button report read more).
Oneboxing certain MediaWiki image HTML pages can break depending on URL structure; a proposed mitigation was to check the response Content-Type before treating a URL as an image read more. onebox
A self-hosted admin reported that enabling YJIT via the Docker template sets RUBY_YJIT_ENABLE=1 but appeared disabled in a Rails runner check; Falco suggested the check was misleading and recommended inspecting the running Pitchfork process environment via /proc/<pid>/environ instead read more and read more.
Group membership syncing via authentication got a concrete update: OIDC group sync is now available, with pointers to settings like openid_connect_groups_claim and “Associated Groups” mapping behavior read more.
CI/build tooling chatter: the Minio installer issue was noted as fixed upstream, with a GitHub PR referenced as the resolution path read more. developmentbug
#Theme component
The “Video Upload to YouTube and Vimeo” theme component discussion moved from “please test first” to permission hardening: nathank argued uploads should be group-restricted to reduce abuse risk read more, and Arkshine shipped an allowed_groups setting in the latest update for validation read more. broken
#Theme
The FKB Pro theme thread continues tracking an Ember-era break (ember-this-fallback/this-fallback-helper missing); a working fork/PR was pointed out as a likely fix path while users asked for status read more and read more.
The “Age requirement for Discourse” thread stayed nuanced: beyond parental responsibility debates, HAWK highlighted that operators must meet regulatory compliance in jurisdictions users may access from, then corrected wording to focus specifically on the UK OSA scope (and noted EU DSA requirements too) read more and read more.
A restore failure report showed PG::DuplicateTable during migrations (relation ... already exists), likely plugin/migration-state related; pfaffman outlined a pragmatic approach (stop before migrations, drop the table, etc.) and suggested escalation paths if urgent read more and read more. backups
#Self-hosting
A self-hosting “gotcha” was documented: to disable Let’s Encrypt/SSL templates in a Docker-based fresh install, comment out the web.ssl / web.letsencrypt.ssl templates in containers/app.ymlread more.
#Community Building
Discourse-as-LMS got a practical blueprint: zsviczian shared a lightweight “category = course, topic = lesson” approach and tackled “notification decay” limitations with a small plugin + theme component, leveraging Doc Categories patterns for a syllabus/index experience read more (and the Doc Categories plugin it builds upon read more).
martin shipped a high-impact defaults proposal to smooth TL3 progression on busy communities, with an opt-in upcoming-change flag and clear notes on how customized settings remain unaffected read more.
HAWK clarified legal/compliance expectations around age restrictions and risk assessments, including a correction from “EU” to “UK OSA” scope and a reminder about DSA obligations for EU contexts read more and read more.
david confirmed that OIDC now supports group sync, pointing admins to configuration details and the broader reference material for the OpenID Connect plugin’s group claim workflow read more and read more.
lindsey explained how Topic Voting badge backfills will work without creating notification spam, including a two-week notification window and “highest badge only” notification behavior read more.
Falco diagnosed the YJIT “not enabled” report as a measurement issue (checking a new Ruby process rather than the running server), recommending /proc/<pid>/environ inspection to confirm the live environment for Pitchfork workers read more.
Yesterday’s theme was “things hiding in plain sight”: invite buttons showing up where they shouldn’t, and YJIT quietly doing its thing until someone went spelunking in /proc.
RGJ’s age requirement thread broadened into a practical/ethical discussion about verification services, privacy risk, and what sites can reasonably enforce in policies; awesomerobot highlighted the threat model of third-party data storage and the appeal of zero-knowledge approaches: read more (related theme component: read more)
A newly migrated community asked how to avoid infinite scroll on the homepage topic list to keep a footer accessible; chapoi confirmed “pagination isn’t on the roadmap” and suggested custom landing pages instead, while others proposed changing the homepage mode and discussed whether infinite scroll is inherently harmful: read more (footer component mentioned: read more)
A Windows 7 support follow-up explored what users see on unsupported browsers and whether admins can customize that message; the thread narrowed into the subtlety that strings under js.* may not load when JS is intentionally blocked, limiting customization: read more (background/related: read more, text customization guide: read more)
An [Admin Notice] about id:discourse.user.userOptions led to a hunt for which theme/component/plugin triggered it; the OP correlated it with notification oddities and started isolating customizations and grepping plugin codepaths: read more (broader plugin bundling context: read more)
AI translation behavior and cost controls came up again: a site hit token/day rate limits while translations kept retrying, and the OP asked whether “thinking/vision/reasoning effort” affects translation outcomes in Discourse AI: read more
#Self-hosting
A “YJIT enablement doesn’t work” report turned into a precise debugging lesson: environment variables can be scrubbed by sudo (unless -E is used), which made YJIT appear disabled; the thread ended with a confirmed fix and the solution marked: read more
A backup restore failed with a Sidekiq renice permission error and a Postgres type collision (ai_moderation_setting_type already exists), prompting advice to ensure the target DB is truly clean and to adjust the restore workflow: read more (referenced prior incident: read more)
A chat mention bug produced duplicate “pings” pointing to the same message; staff confirmed reproduction and shipped a fix shortly after: read more
Deprecation handling broke builds for some customizations: missing ember-this-fallback/* modules caused runtime errors and made it harder to locate the real offending code; the issue was investigated, fixed, and queued for backport: read more (example fallout in a theme thread: read more)
A new AI docked composer experience was reported as visually polished but functionally unstable: editing controls blocked, markdown/preview UX oddities, quoting breaking sidebars, and mobile scrolling/lockups—reproduced even in safe-mode with only official plugins: read more
The long-running “Proofread breaks quotes” issue got reaffirmed as fixed, with a pointer to the upstream change and follow-up testing around models/prompts—particularly important for communities where quotes must remain verbatim: read more
#Announcements
Trust system mechanics were clarified around the “upcoming change” for trust level 3 defaults: overrides remain preserved, but using Reset reveals the new defaults, and disabling the upcoming change restores older defaults (until the transition is finalized): read more
Discourse’s full-site embedding as a comment system was explicitly framed as a Disqus replacement (with data/control benefits), including a callout to member-only communities that want public blog engagement without anonymous posting: read more
#Extras
A product idea pitched dead Amazon/eBay link detection and replacement with related products; staff pushed for real-world Discourse testing results before it can be evaluated as broadly useful: read more
The companion discussion thread for Discourse Discover: Hobbyist Edition landed, showcasing niche communities (unicycling, tiny houses, flight sim) and the kind of “specific expertise” that Discourse instances tend to accumulate: read more
awesomerobot weighed in on the risks of third-party age verification (especially services that store sensitive identity data) and why zero-knowledge verification could reduce exposure—while still acknowledging transfer risk: read more
chapoi answered a roadmap question bluntly (“no pagination plan” for topic lists), suggested workarounds like custom landing pages, and later pushed back on equating Discourse’s infinite scroll with addictive algorithmic feeds: read more, read more
lindsey confirmed the duplicate mention/ping bug affected staff too and kicked off investigation: read more
Falco closed the loop on the ping issue with a shipped fix, clarified YJIT toggling behavior (and what the env var does/doesn’t do), explained why “unsupported browser” messaging can’t rely on JS-loaded strings, reaffirmed the fix for AI-proofread quote preservation, and positioned embedded comments as a Disqus alternative:
david investigated the ember build/deprecation regression, confirmed expectations (“deprecated but still supposed to work”), and delivered a fix with a backport plan: read more, read more
martin clarified how Discourse’s site-setting override system interacts with the new TL3 defaults (especially what Reset does and how “upcoming changes” affect which default set you see): read more
Bas challenged an Extras pitch constructively by asking for real Discourse instance testing and results before further evaluation: read more
If yesterday proved anything, it’s that Meta can debate bottomlessness while still shipping fixes—may all your pings be single, your YJIT be truly enabled, and your scroll be responsibly unaddictive.
awesomerobot prompted for stronger sourcing, kicking off a deeper discussion of whether Discourse-style scrolling is “infinite” in the addictive-feed sense (and whether laws might still sweep it in) in Time to reconsider infinite scroll?
#Self-hosting
gallery3540 tried to tune composer image resizing for a photography-heavy community, and the thread clarified which settings control trigger vs target, plus how to verify changes in the console in Composer image resize threshold
codixer explored whether the hard cap on max_favorite_badges can be exceeded (and what the UX/perf tradeoffs are), with suggestions ranging from alternative presentation approaches to custom work in Bypass the 6 badge fav limit
Building a partner/participant directory inside Discourse led back to the built-in /u directory and optional “cards” UI, with pointers to user fields and layout options in Member directory (read more)
The new AI docked composer UI continued getting real-world testing notes, with a status update that keegan is working through the feedback in New ai docked composer (composerai)
AI Helper troubleshooting continued: Falco asked whether the proofreader agent’s shipped “examples” were being used, since they help the model preserve quoting behavior in Proofread breaks quotes (aiai-helper)
Accessibility/contrast feedback on the refreshed UI continued, focusing on button borders when using the WCAG palette in Modernizing the Foundation theme
Falco helped untangle which composer setting controls when resizing triggers vs what width the image targets in Composer image resize threshold, and added practical console-check guidance in follow-ups (read more, read more). Falco also continued investigating quote-preservation behavior in AI proofreading in Proofread breaks quotes.
sam acknowledged feedback and confirmed active work-in-progress on the AI docked composer, pointing to an update from keegan in New ai docked composer.
HAWK added perspective on identity verification vs bot pressure (and the tradeoffs communities may face) in the ongoing policy/practice discussion in Age requirement for Discourse.
southpaw asked for key hosting context (self-hosted vs Discourse-hosted + plan) before advising on disabling read-only mode, in Read Only Modes in Discourse.
Yesterday’s meta energy was peak Discourse: debating “infinite” scrolling and shipping a theme concept literally named “Newspaper from Hell”—all in a day’s work.
A lot of today’s energy clustered around UX friction vs. usability: infinite scroll controls, mobile typography, reaction discoverability, and composer behavior.
Interesting Topics
#Theme component
RGJ published a new theme component that adds a manual “Load More” button to interrupt infinite scrolling, positioning it as a compliance-friendly “manual input” step: Load More Button (discussion tie-in, read more).
Mobile ergonomics feedback came quickly: Canapin noted the button is hard to reach with a right thumb and suggested centering; Lilly shipped a centering SCSS snippet + PR that was merged: feedback and CSS fix (merge confirmation).
mcmcclur reported the button appearing even when there’s nothing to load (small/hidden-content site), and RGJ traced it to a core canLoadMore propagation issue rather than the component itself: bug report and core explanation.
The broader “is Discourse infinite scroll social media-ish?” debate continued, with RGJ’s practical counterpoint being “ship a workaround” (the new component), while others dug into scalability and UX patterns like “catch your breath” prompts after N scroll units: theme component drop-in context and scroll implications question (read more).
A concrete pointer surfaced: for “pause” nudges, there’s already a community option, though time-based (not scroll-based): Take a break theme component (referenced from this comment).
A new support question asked whether admins can force exact characters on a single line (to keep a “clean” first paragraph look). The thread explored enforcement limits, user workarounds (multi-line), and the UX downsides of “exact length” constraints: question and cautionary take.
A new UX report claimed some hosted instances’ mobile font sizes got smaller (navbar + Suggested/Related), with Lilly suspecting the “modernized foundation” rollout being the differentiator: report and foundation theme hypothesis.
That complaint cross-linked into the main announcement thread, where Lilly argued the new foundation styles are “sleeker” and offered CSS snippets for users/admins who prefer larger text: cross-link post and CSS suggestions.
The long-running draft-save UX discussion continued: Moin highlighted inconsistent draft auto-saving (especially around thresholds/quotes), arguing the removed “save draft for later” affordance used to help users avoid silent loss: Nate’s clarification and Moin’s reproducible concern.
In the “show all likes/reactions” thread, Moin asked for better visibility into all reaction types (especially on communities with many emojis). NateDhaliwal noted you can horizontally scroll the tooltip—but the UI gives little indication that it’s possible: question and sidescroll explanation.
The AI docked composer fixes progressed: keegan referenced earlier fixes and queued improvements addressing editability and mobile quoting/sidebar issues, while clarifying the markdown/preview behavior as an intentional design choice due to space constraints: status + PR links and follow-up.
#Self-hosting
The “bypass the 6 badge fav limit” discussion leaned toward “possible, but not wise.” pfaffman outlined that it’s easy via plugin or even app.yml replace stanzas, then suggested an alternative: use group flair badges (via a theme component) instead of pushing badge limits: plugin/app.yml note and theme-based alternative.
#Theme component (icons + sorting)
Iconography polish request: Moin flagged confusing mirrored “previous/next” icons in edit history within the Lucide icons component, suggesting more intuitive paired designs: confusing icon pair.
A small enhancement request landed on “Created Topic Sort”: davidkingham asked whether the sorting option can persist when browsing a tag view, since the menu disappears there: tag-view question.
#Plugin
The long-standing Calendar/Event thread got a big jolt: oshyan criticized the current settings/terminology sprawl and shared an early “event-focused” plugin prototype video after a few days of rapid iteration: prototype reveal.
In the .gjs migration thread, jericson noted older plugin skeletons may also need the modern ESLint config file, pointing devs at the updated skeleton reference: eslint.config.mjs note.
keegan shipped updates on the AI docked composer bug thread, pointing to fixes already in-flight and a follow-up PR, and clarified why the docked composer favors RTE with markdown available but without preview: details + PR references (read more).
derek investigated a category badge text color regression caused by Foundation modernization styles overriding expectations, then provided a fix via PR to the badge styles component: root cause + PR (confirmation reply).
Yesterday’s vibe check: Meta collectively tried to click “Load More” less, while simultaneously asking for bigger fonts, clearer icons, and more visible reactions—a very on-brand day of UI debates.
darkpixlz shipped Modern User Card, reviving the older experimental user card UI—then immediately ran into follow-up work around the component-template-resolving deprecation warning, with Lilly jumping in to help investigate. read more (see also: the original experiment here and the deprecation thread being referenced here)
The Load More Button component continued to surface an underlying core limitation/bug (with DiscoveryTopics not passing canLoadMore), and discussion shifted toward practical workarounds (CSS hiding) versus “this needs core support.” read more
#Site feedback
A visual glitch report: ondrej spotted a weird/garbled Meta logo that normalizes when zooming in, but breaks again at default zoom—likely pointing to a rendering/scaling issue across browsers. read more
jericson posted a reflective case study on learning Discourse plugin development “as an amateur”, connecting the dots between a real client need (a contact form for anonymous visitors), the official plugin tutorial path, and the end result. read more (background links referenced in-thread include: the “not possible?” discussion here, the plugin dev tutorial here, and the resulting contact form plugin topic here)
#Self-hosting
A Russian-language support thread escalated from “file too large (even 2MB videos)” into rebuild troubleshooting: guidance centered on aligning container/nginx limits (app.yml) with site settings, and the need for SSH access to rebuild reliably. read more (the key doc being pointed to: Change the maximum attachment upload size)
A solved how-to: forcing exact characters on a single line (with a live counter and customizable styling) wrapped up cleanly once the right approach landed. read more
The ongoing age requirement / youth accountability discussion kept branching into what platforms can enforce versus what’s realistic (and where responsibility should sit). read more
The “infinite scroll” debate got a terminology reset: participants emphasized that Discourse’s scroll is pagination replacement (finite content), not “infinite content feeds” like social media—plus some legal framing discussion on what counts as a “significant part of the services.” read more
In show-and-tell, kirupa shared an update on populating a mostly-dead forum with bots, including publishing the full source code so others can adapt the approach. read more
#Announcements
The Foundation theme modernization thread saw another small but telling UI detail: a gap/spacing issue under the “Related” button (especially with larger fonts). Lilly suggested a targeted padding/line-height patch and flagged it as a UX clash with an injected AI-related button. read more
The new AI docked composer looks improved overall, but Lilly reported a sharp regression: file uploads appear to break after the first post, keeping the bug thread active. read more
#Plugin
In the official openid-connect thread, a practical ops question came up: will users be automatically removed from groups when they’re no longer members in the identity provider? read more
The official Discourse Calendar (and Event) plugin thread continued with feature-scope discussion: interest in a more complete, configurable event management system—and some candid notes on which AIs are being used for coding assistance. read more
The Telegram Notifications plugin thread saw UI/option confusion (screenshots + “no such option”), suggesting either documentation drift or a UI/settings mismatch between versions. read more
#Extras
SuperHref shipped an update: suggested products can now keep the original affiliate tag or swap in a custom one—useful for operators trying to preserve monetization while improving link hygiene. read more
Lilly collaborated with darkpixlz on next steps for the Modern User Card theme component, including diagnosing the component-template-resolving warning and setting expectations about refactoring needs. read more and read more
Lilly noted a potential workaround/fork for an edge case in Load More Button, while agreeing the approach is “hacky” and limited by core behavior. read more
Lilly provided a concrete CSS patch suggestion for a spacing/UX issue in Modernizing the Foundation theme, tying it to a mismatch between button classes and an injected AI-related UI element. read more
Lilly added a key regression report to New ai docked composer: uploads appear broken after the first post, even if the composer is otherwise “much less buggy.” read more
If yesterday proved anything, it’s that Discourse scroll isn’t truly infinite—but the community’s capacity to debug UI quirks and resurrect forums with bots might be.
Vsekraski’s “file too large” troubleshooting turned into a full incident narrative: interrupted rebuilds (^C) and upload failures ultimately pointed to a host-side firewall blocking payloads, not a Discourse build failure (read more). Related guidance included “don’t cancel rebuilds,” paste logs instead of screenshots, and patience for long rebuilds on low-RAM servers (read more).
Mike73 shared the fix for OpenID Connect accounts not mapping to existing users: ensure the incoming email claim is treated as verified via the provider setting “set to always verified” (read more).
Another Russian-language setup issue (“component install errors”) was quickly resolved—Lilly confirmed the install was successful and noted URL/domain translation can break the “link method” approach (read more).
A reflective “plugin author” post sparked a deeper discussion about Discourse’s pace of change, deprecations, and the reality that documentation often lags behind engineering priorities—plus a constructive outcome: a docs PR for the plugin outlet tutorial (read more). The thread also referenced the Ember deprecation-handler crash bug that likely caused the reported breakage (read more) and the broader release/versioning strategy debate (read more).
A regression in bin/lint workflows for non-bundled plugins was reported, reproduced, fixed via PR, iterated (verbosity/progress output + --fix behavior), and merged with confirmation from the reporter (read more).
Self-hosters running OpenShift reported huge RAM spikes (20GB+) during asset precompile/build since the newer “pre-compiled assets” approach; david requested plugin lists and asked whether memory drops immediately after the build completes (read more). Background context included the shift to precompiled JS assets (read more) and the newer plugin build system (read more).
Invite links producing “wrong” social previews: the image often falls back to the site’s large icon/favicon, while the background tile is controlled by the preview client (e.g. WhatsApp), so transparent icons can disappear on white (read more).
A fresh report noted a moderator not appearing on /about despite having moderator status—likely an about-page listing/config nuance to be debugged next (read more).
#Community Building
“Welcoming new users” explored ways to notify regular members about new signups (especially via Chat). Constraints from managed/free hosting (no cron/SQL) forced a rethink toward creative in-app approaches like linking to trust-level group member lists (TL0/TL1) and surfacing them via sidebar controls (read more). A related UI/tooling idea referenced conditional sidebar visibility patterns (read more).
Testing continued on the new AI docked composer: earlier quoting issues appear fixed after rebuild, and keegan shipped a fix for “uploads fail after first post” plus gated the feature behind an upcoming change while polishing continues (read more).
#Site Management
Form templates: users can paste images into the main composer easily, but composer fields inside form templates don’t behave the same—workarounds included switching to WYSIWYG (but it doesn’t behave like a real upload) or adding an explicit upload field type (read more).
#Plugin
ActivityPub plugin: a report noted that following Mastodon actors works, but following other Discourse actors fails; pmusaraj acknowledged and queued investigation (read more).
“Trading Buttons” plugin support surfaced a possible interaction with an upcoming change that simplified category creation and altered how plugin category settings are saved (read more); the underlying change was tracked in a separate “unable to save category settings made by plugins” topic (read more).
OpenID Connect plugin thread: a quick confirmation post clarified expected behavior (“Yes they will”)—but follow-up testing suggested nuance remains (read more).
#Announcements
Clarification: the tests-passed branch name is still a functional alias for latest, and there’s no admin warning yet for configs still referencing it (read more).
david spent a big chunk of the day in developer-support mode: he shipped and merged the fix for bin/lint regressions affecting non-bundled plugins, iterating quickly based on reporter feedback (read more). He also provided broader context on Discourse’s stability vs progress tradeoffs and clarified the .hbs deprecation timeline in the ongoing plugin-author discussion (read more), asked for plugin lists + memory behavior details in the OpenShift asset-build RAM spike report (read more), confirmed tests-passed remains an alias for latest (read more), and replied in the OIDC plugin thread where testing results appear mixed (read more).
chapoi helped untangle what can/can’t be controlled in invite link previews, explaining why external preview renderers often force a white tile behind transparent icons (read more). He also responded candidly in the plugin-author discussion about resource constraints and why docs inevitably lag sometimes (read more).
keegan continued polishing the AI docked composer: he temporarily gated the feature behind an upcoming change while it’s refined, and posted a fix commit for the “uploads after first post” bug (read more).
pmusaraj acknowledged a fresh ActivityPub regression report (Discourse-to-Discourse follows failing) and indicated the team would investigate shortly (read more).
derek confirmed a UX fix (category badge font color) is now merged and invited further reports if any issues persist (read more).
If yesterday taught us anything, it’s this: let your rebuilds finish cooking—no more mid-rebuild CTRL+C “taste tests.”
New posts (last 24h): 79 — spanning support threads like cross-domain embedding in #Support, self-hosting troubleshooting in #Self-hosting, and UI/UX fixes in #UX.
New topics (last 24h): 8 — including new asks about UI tweaks (read more), moderation/docs gotchas (read more), and composer behavior (read more).
nat shared a visual tour of what Discourse looks like in non-English locales, sparking follow-ups about theme strings and plugin UI that don’t yet flow through AI translation in What It’s Actually Like to Use Discourse in Another Language. Related: missing theme string was confirmed and patched (read more).
Site owners looking to exclude a noisy category from /latest got pointed to the discourse-categories-suppressed plugin (read more) and also compared it to the built-in default_categories_muted behavior (read more) in Exclude category from latest. (Background context: older “where did that setting go?” thread: read more).
A theming question about adding a “Latest Topics” header turned into a useful pointer: use the discovery-navigation-bar-above plugin outlet in Adding “latest topics” header in the main interface, with the canonical outlet guide here: read more.
Cross-domain Full App Embed behavior came up again: login/reply inside an iframe can fail due to cookie policy, and one suggested workaround was adjusting SameSite cookies in Rails (read more) in Is using the full app embed on another domain possible?. (Related embed expectations discussion referenced here: read more).
Asset compilation and RAM pressure remained a hot self-hosting pain-point: the thread dug into OOM evidence, swap/overcommit advice (read more), and suspected loops in plugin JS build tooling in Excessive consumption of memory due to precompiling assets. Extra background referenced by the reporter: precompiled assets rollout (read more) and the new plugin build system (read more).
A calendar issue resurfaced where holiday status appeared incorrectly applied (showing unrelated members) despite the relevant site setting, in Holiday status being incorrectly applied.
A long-running request for better email notification control granularity got a new angle: “can this be changed at a group level?” in Email notification granularity.
Accessibility polish: custom badge images were missing/incorrect alt behavior, and the planned fix was to treat the image as decorative (empty alt) with work tracked from Custom Badges are not applying Alt Text (badgesaccessibility).
Profile privacy: a UX bug where the Invite tab appeared on hidden profiles is getting patched, with the fix queued from Invite tab shows on hidden profile.
Invites UX follow-up: the “weird invite button” case got a concrete “hide the button” fix in motion, plus a note that “inviting on behalf of others” is a separate feature request, in Weird invite button behavior (invites).
If you spent yesterday toggling sidebars, wrangling SameSite cookies, and reading Meta in Russian “just to check,” you’re in excellent company—see what tomorrow’s thread pile-up brings.
eisammy shared real-world data on how localized content changes traffic sources over time (with country-by-country stats and observations about discovery), and nat chimed in on how this can guide language support decisions — read more
Bryony asked about implementing safeguarding-focused reporting (custom report flows, emergency protocol prompts, tailored moderator notifications, and auto-hiding behavior), with replies clarifying what can be done via custom flags vs what would require plugin work — read more (see also the pointer to flag tooling in Moderation flags, plus discussion of flag notification UX concerns in Turn off notifications of flagged post removed, and a possible stopgap via Report content to group)
A self-hosted admin couldn’t access theme customization routes even in safe mode; troubleshooting led to the core fix: rebuild + upgrade from an older beta (with the exact rebuild command provided) — read more
Following on the “legacy vs new metrics” thread, a second report noted crawler counts appearing in Legacy Consolidated Pageviews but not in Site Traffic, raising the practical question of which dataset to trust going forward — read more
Upload limits: a classic “Discourse setting vs edge proxy” problem. After increasing limits in app.yml, the real blocker was upstream (Cloudflare’s default limit), and changing Cloudflare settings resolved uploads >100MB — read more
Discourse AI token-limit issues: RBoy reported requests exceeding configured thresholds “randomly,” while Falco pointed out the likely confusion between request tokens vs response tokens (and that 413 indicates the request itself is too large) — read more
Impersonation UX got attention: after a hidden time limit ends impersonation, the UI doesn’t clearly reflect it. martin outlined improvements like MessageBus-driven UI updates, a visible timer, better “Stop impersonating” behavior, and possibly bumping the limit — read more (continuation context: New Bug With Experimental Impersonation Interface)
Editing someone else’s survey after transferring topic ownership triggered errors; sam flagged it for review and techAPJ confirmed a fix shipped via a plugin commit — read more
Mobile reactions UX: long-pressing the reactions counter could unintentionally open the picker (and even throw a console error). A fix + PR was posted to stop the wrong element from triggering the picker — read more (related: Ability to display all the likes/reactions on a post)
Form templates: missing paste support in composer fields was acknowledged, with tannerabread actively working on the fix — read more
#Feature
A request proposed a team-shared invite status page (akin to /my/invited/pending, but accessible to multiple admins) to avoid “vacation bottlenecks” and reduce the need for account sharing — read more
Navigation for “publishing / comment-driven” communities: Thiago_Mobilon described a pain point where muting high-volume subcategories makes parent categories look empty, and looked for ways to aggregate those muted streams. The practical workaround surfaced quickly: use configurable top navigation links — read more and the solution follow-up in Custom Navigation Filters in top menu (docs: Custom top navigation links)
Chat discoverability: “promoting chats to first-class content” continued drawing feedback about how mixed lists of categories/topics/chat channels should feel in practice — read more
#Announcements
Embedding Discourse comments: renewed interest in whether embedded comments auto-create topics on first visit. The answer: yes, if configured properly, the topic is created in the background — read more (canonical doc: Embed Discourse comments on another website via JavaScript)
martin jumped into impersonation UX improvements, proposing UI updates when the hidden time limit expires and a smoother “Stop impersonating” flow — read more (related background thread: read more)
sam acknowledged the survey editing bug report and handed it off for investigation — read more
techAPJ delivered the fix for the survey issue and linked the resolving commit — read more
tannerabread confirmed missing paste functionality for form-template composer fields and started work on a fix — read more
Falco clarified embedded comments behavior (auto-creating a topic on first visit) — read more — and also shared progress on improving the embedded-login UX loop in the Tecnoblog embedding discussion — read more
Falco provided troubleshooting guidance for ai token errors, noting that HTTP 413 indicates request too large and warning about overly-small context limits — read more
Falco helped debug AI proofreader quote issues by pointing to agent examples in the admin UI — read more
nat reacted to shared multilingual traffic data (and the inevitable idiom-translation experiment) in the language-usage blog thread — read more
chapoi worked through a confusing notifications investigation with Moin, probing whether certain “other notifications” lack traceability in the unread list — read more
Alteras shipped an update to the Created Topic Sort theme component, adding new settings for tag display — read more
Yesterday’s vibe: between auto-expiring impersonations, mysteriously “legacy” pageview dashboards, and translators trying to prove the pudding is in the proof, Meta stayed delightfully chaotic—in the best debugging way.
A lot of today’s momentum clustered around “small UX papercuts with big impact”, from link parsing edge-cases (read more) to login/profile field expectations (read more) and admin-facing reporting clarity (read more, read more).
Other active (updated) discussions worth noting:
Reaction/likes visibility UX continues to matter for “likes-only” communities (read more).
Traffic analytics reports vs crawler metrics got clarified again (read more).
Hosted vs self-hosted backup expectations surfaced in docs (read more).
A long-running trust-level / onboarding control question kept evolving (and translation strings got scrutinized) (read more, read more).
A self-hosting reverse-proxy “May 2026 update” got added for NPM Plus users (read more).
The “shortlink router” experiment is winding down due to low usage (read more).
Doc Categories plugin users reported anchor scrolling turning into full reloads (read more).
Theme Creator workflows hit confusion around color schemes/palettes (read more).
A Docker image thread saw more practical ops tweaks (upload size) and build questions (ESR vs newer) (read more).
Interesting Topics
#Announcements
gabriel introduced Discover Hot Topics for Discourse Discover (discourse-discover), surfacing the most active discussions across communities by subject in DiscourseHub (iOS) with Android/web coming soon — plus some iOS TestFlight/build-track chatter and UI styling thoughts (read more; background: read more).
The “simpler email subject lines” rollout continues to get real-world feedback, with dfabulich specifically lobbying to bring back a minimal [PM] prefix for clarity (email) (read more).
HAWK’s companion discussion to “The Digg Lesson: Why Moderation Infrastructure Matters” sparked reflections on spam waves, brigading/sockpuppetry, approval queues, and the long-term “arms race” nature of moderation tooling (read more).
Jonathan5 reported a deceptively annoying formatting edge-case: when a URL ends a bracketed sentence, trailing characters like .] can get pulled into the link. The thread converged on why it happens (linkifier behavior) and practical workarounds (angle brackets or just drop the trailing period) (read more).
In an identity/SSO planning scenario, watsonbriant asked whether enabling the DiscourseConnect “provider” mode breaks native login. The answer: enabling the provider doesn’t disrupt the site’s normal login flow (sso) (read more; related background: read more).
A “Mailcow login page shows instead of my forum” incident turned into a solid troubleshooting case study: caching/DNS changes first, then a deeper root cause—reverse proxy config not listening on IPv6, which mobile networks may prefer (read more).
Vsekraski asked how to change the title/description on a tag page, and got pointed to the in-UI wrench that opens tag editing (tags) (read more).
A hosted-plan admin hit confusion with the Full name requirement when signups flow through Discourse ID (discourse-id): even with “full name required” set, the Discourse ID flow didn’t behave as expected; pmusaraj reproduced and flagged it for fixing (read more).
A high-impact report suggested OpenID Connect group sync can remove users from all unsynced groups when one OIDC group is lost/changed—effectively over-removing membership and risking access loss (openid-connect, sso) (read more).
The crawler middleware error “Document tree depth limit exceeded” appears to be persisting for at least one site, with the report explicitly tying back to an earlier thread and stack trace context (read more; earlier reference: read more).
Moin proposed improving the logged-in experience when switching themes: instead of showing a blank /custom page for regular users (when their chosen theme lacks a custom homepage), show a “Take me home” style button to recover gracefully (read more).
#Feature
Moin suggested that translated posts should preserve (or clearly re-present) the valuable “quote context” UI—topic/post metadata and the extra context dropdown—so translations don’t silently remove information the author expects readers to see (content-localization) (read more).
The “promote chat to first-class content” idea kept moving: a unified activity view across topics/subcategories/chat channels aims to improve discoverability and navigation, with discussion around hierarchy, configurability, and defaults (chat) (read more).
#Theme component
A troubleshooting thread on Discourse Age Check focused on why the signup validation wasn’t firing—leading to the usual suspects: console errors, correct parent theme assignment, and ensuring the site is up to date (read more).
#Developer Guides
Theme Creator + Theme CLI users hit confusion around color schemes defined in about.json: schemes appear in one place but can’t be selected/applied as expected in preferences, prompting investigation into preview environment behavior (read more).
gabriel shipped the day’s splashiest announcement by unveiling Discover Hot Topics and how it’s rolling out across clients, with pointers back to the broader Discover initiative (read more, read more).
pmusaraj jumped into multiple threads: clarified the current DiscourseHub/TestFlight situation and iOS UI constraints (read more), reproduced and escalated the full-name requirement vs Discourse ID behavior into a bug workflow (read more), and encouraged continued iteration on “chat as first-class content” experiments (read more).
HAWK published the companion discussion for Discourse’s Digg moderation piece, prompting broader moderator-tooling reflections (read more), and also contributed community-growth resources and motivation frameworks in an ongoing strategy thread (read more).
sam pointed admins to the upcoming-changes toggle that enables improved reaction/like viewer behavior—answering a long-running UX request in the “show all likes” thread (read more).
david provided the practical markdown fix for link boundary control—using angle brackets to avoid punctuation being absorbed into URLs (read more).
awesomerobot clarified why some Site Traffic report dates show zeros (report rollout baseline), and linked the underlying rationale/commit history for accurate comparisons (read more). They also noted a fix is inbound for long tags being cut off on mobile (read more).
Falco helped nail down the “URL punctuation” issue as linkify-it default behavior (read more), flagged a likely-related composer/iframe editing bug in an embedding feedback topic (read more), and explained why “thinking models” can break locale detection and stall automatic translations (ai) (read more).
supermathie answered a key SSO architecture question: enabling the DiscourseConnect provider won’t disrupt native login (read more), and followed up on the OIDC group-sync report to confirm assumptions and isolate the incorrect removal behavior (read more).
martin continued the UX/product discussion around impersonation session timeouts, weighing “inactivity-based” timeouts vs fixed timers and the original intent behind the safeguard (read more).
chapoi asked the right first troubleshooting question on the Age Check component (“anything in the console?”) and verified when/where the validation should trigger during signup (read more).
If yesterday taught us anything, it’s: keep your periods out of your URLs, your group syncs on a short leash, and your tab bars only as glassy as you’re prepared to maintain.
merefield noticed Bootstrap mode removal and asked what replaced it; pmusaraj explained it had been effectively sidelined and is now replaced by an onboarding panel, then circled back after Moin highlighted the old auto-enable job and some “niceties” worth keeping (like better early user directory refresh). Main thread: Bootstrap mode is legacy? (see the replacement explanation here and the correction/next steps here). Background: Bootstrap mode effects, older context on what it used to do here, and a referenced system note here.
Ed_S reported that the “Nice Share” badge notification linked to a post that wasn’t theirs; Moin clarified the badge is about tracked share links (with ?u=) being clicked, not necessarily the post containing 25-click links. Details: ‘Nice Share’ notification links to wrong post (solution explanation here).
A request to remove the blue-dots preloader resurfaced: GaurangBlaze asked how to disable it after an upgrade, and awesomerobot confirmed the “disable Splash” setting was removed (partly due to potential Core Web Vitals impact), offering a workaround: an animated SVG can fully replace the dots (including a blank/transparent animated SVG). Thread: How to disable “preloader-image” on Discourse instance? (core explanation + workaround pack here). Background announcement: Introducing Discourse Splash.
A new self-hosting planning thread asked about AWS Lightsail + Ubuntu upgrade approaches (in-place upgrade vs snapshot-and-restore onto a fresh instance), especially with newer Ubuntu LTS releases appearing. Thread starter: Self Hosted, AWS Lightsail and Ubuntu.
A structured data issue around Solved/QAPage schema narrowed down to a key edge case: OPs containing no text content can trigger validation problems. davidb suggested either skipping or substituting placeholder text (like the topic title) to satisfy schema expectations. Investigation: Missing field ‘text’ (in ‘mainEntity.suggestedAnswer’) (analysis from davidbhere).
AI translation failures showed up as Raw can't be blank, Cooked can't be blank; Falco walked through debugging via /p/ID and ai_api_audit_logs, then identified the underlying issue: reasoning tokens consuming the completion budget, reinforcing why translations avoid reasoning mode. Thread: AI translations errors (debug guidance here and root cause callout here). Related historical context: Discourse AI failing to translate large number of posts and topics.
The “tag info” affordance appears to have moved: Moin asked where the tag description/info button went for regular users, and Lilly pointed to a commit suggesting a UI relocation. Thread: Where did the tag info button go? (commit hint here). Background references: awesomerobot’s earlier guidance cited in this post and a related tag-banner discussion mentioned in this post.
The “split this topic” small-action post still seems to preserve stale topic titles: follow-up discussion noted there’s no UI-based rebuild for these small-action posts, and that rebaking is more of a CLI/web-request operation (with limited benefit if the title is stored as literal text). Thread: Link in “Split this topic” mini post (title-staleness analysis here and the UI limitation here).
A UX issue report proposed that when a custom page is blank for regular users, Discourse should show a clearer escape hatch (like a “Take me home” button) rather than leaving people stranded; derek acknowledged and said the team would investigate. Thread: Show “Take me home” button instead of blank custom page for regular users.
#Plugin
In the long-running official translator discussion, nat advised avoiding dual translation experiences and recommended standardizing on the newer automatic translation direction as the older experience is deprecating. Thread: Discourse Translator (team guidance here).
pmusaraj clarified the rationale for removing Bootstrap mode and pointed admins to the new onboarding panel in Bootstrap mode is legacy?, then followed up after Moin’s investigation to acknowledge how Bootstrap mode was actually enabled and flagged “keep-worthy” behaviors like early directory refresh and initial role setup (follow-up, hourly directory improvement note here). Also delivered a fix pointer for an SSO-related group-sync bug in OpenID Connect group can kick users out of all unsynced groups.
If today’s Meta felt extra lively, blame it on the blue dots Splash screen—apparently even our discussions needed a preloader before they fully rendered.
