Should nested replies be a per-user preference? In the ongoing #Announcements discussion on nested-replies, bksubhuti asked why individuals can’t choose this in their personal interface settings (read more). chapoi argued that letting different users view the same shared conversation with divergent structures breaks shared reference points, permalinks, and “conversation as shared space” expectations (read more, read more).
French translation nuance for “Support” category type.patrickemin flagged that translating “support” as “soutenir” is incorrect in this UI context, and suggested it should remain untranslated for clarity (read more).
“Ideas” category type affecting voting behavior.patrickemin reported that removing the “Ideas” type from categories appears to remove the vote button as well, which seems unintended for sites that want voting outside “Ideas” categories (read more).
Self-hosting disk pressure: “Running out of space — Docker image is large?” A self-host admin on a 25GB VM found large usage under /var/lib/containerd and /var/docker and asked if that’s normal and what can be done before upgrading (read more). NateDhaliwal suggested trying ./launcher cleanup as a first step (read more).
“Unfortunately, your browser is unsupported” troubleshooting. In a support thread, Rubi recommended checking the browser console, clearing cache/cookies, and hard refresh to resolve an “unsupported browser” message (read more). Bryanpwo followed up by asking which browser was being used, noting Firefox works across Discourse instances (read more).
Endless spinner in one category (Staff) with a name_key error.Jose_C_Gomez reported an “endless spinner” affecting only their Staff category and included a stack trace pointing at post.js / post-stream hydration logic, asking why it would be scoped to a single category (read more). (They referenced a similar prior incident for comparison in the same report: read more).
Reply count not updating in “Blog Style” mode for Topic List Thumbnails.xlg256 reported that when using the Topic List Thumbnails theme component with the “Blog Style” layout, the reply count appears broken, and provided screenshots for diagnosis (read more). (Related component context: read more).
#Feature
Making “Sign Up” easier to find on mobile (sidebar/account UX).awesomerobot discussed common UX patterns across popular sites and favored approaches that don’t explicitly separate login vs signup until after an email step—while acknowledging tradeoffs (read more). Lilly questioned the value if it can’t be removed, and shared a CSS-based alternative to show a “Sign up” link only for mobile anonymous users (read more).
#Plugin
Snapblocks: plugin vs theme component tradeoffs. In the #Plugin topic tagged bbcode, RGJ suggested Snapblocks’ current behavior might be better implemented as a theme component rather than server-side plugin logic (read more). ego-lay_atman-bay explained they’re hooking into the message parser to prevent parsing inside tags and want WYSIWYG composer support, plus “enable once globally” behavior (read more). RGJ countered that plugins are more cumbersome (rebuilds, updates, hosted plan limitations) and theme components can cover the current JS-side functionality with click-to-update convenience (read more, read more).
Voting button behavior tied to category type (possible glitch). In the long-running #Plugin thread for topic-voting (tagged official and included-in-core), patrickemin shared findings that categories not marked as “ideas” can’t show the vote button—potentially contradicting expected behavior for mixed discussion + voting setups (read more).
chapoi focused on shared conversational coherence in the nested replies debate, cautioning that allowing per-user display modes creates divergent mental models and undermines stable references like post ordering and meaning across participants (read more). They also pushed back on the idea that engagement should outrank communication quality in Discourse’s design philosophy (read more).
awesomerobot weighed in on mobile account UX, noting that many sites prioritize login entry points (or unify login/signup flows) and outlining pros/cons of email-first “branching” patterns (read more).
If yesterday was any indication, today’s Discourse recipe is: a dash of nested-replies philosophy, a sprinkle of mobile signup UX debate, and just enough Docker cleanup to keep your VM from bursting at the seams.
long_season dug into disk pressure from self-hosting and large container layers in “Running out of space - Docker image is large?”; Ed_S suggested a cleanup workflow and shared real output from ./launcher cleanup and image sizes (read more, read more).
A quick “is this built-in or a plugin?” question landed as Solved: haydenjames asked about a dismissible UI box, and Lilly confirmed it’s a private theme component used by the team (read more, read more). The thread also points to the related banner discussion (read more).
In “Unfortunately, your browser is unsupported”, guy_rouillier narrowed symptoms down to a site-wide landing-page issue (but topic pages loading fine), including a console error reference, while others suggested connectivity/MTU workarounds and testing steps (read more, read more). Lilly later reported testing on Firefox/Ubuntu successfully and suspected identity/caching quirks in the login flow (read more, read more).
“Forum logo isn’t showing” was resolved after configuration review: Lilly couldn’t reproduce and asked for branding settings; nwnuyhs confirmed enabling “force https” in Admin settings fixed it (read more, read more, read more).
“PhotoSwipe new icons visual collision” flagged a UI regression/UX snag: haydenjames noted the lightbox overlay controls shifting from text to icons and colliding with screenshot content, asking if it’s been reported and whether any toggles exist (read more).
#Site feedback
The “Creating bug reports for Discourse on Meta” guide was reported with dead category links after the recent restructure: RalfJung noticed /c/bug no longer resolves, NateDhaliwal suggested editing to use category-ID-based links, and Moin argued for durable permalinks when categories move or become subcategories (read more, read more, read more, read more).
In “‘Unread’ tab is not listing all thread with unread messages”, RalfJung provided side-by-side screenshots showing unread items visible in Latest but missing from Unread, describing the risk of silently missing required replies across hosted instances (read more).
pwamath users may have hit a rendering regression: Ethsim2 reported “Occasional cropped delimiters on iOS portrait after recent rebuild” (with a reproduction video and rebuild details) and noted it didn’t reproduce later in subsequent PWA sessions (read more).
A permissions edge-case cropped up after an update: “403 when setting publish_to_category topic timer after update” describes a formerly-working workflow where a global moderator can no longer schedule publish to category from a private staging area, receiving a 403; Lilly asked clarifying questions about whether the affected user truly has create/post access in the staging category (read more, read more).
Plugin authors hit a CI stumbling block: “Github actions failing ‘Check SKIP_DB_AND_REDIS bootability’ step” explains a failure that was hard to reproduce locally, and elmuerte tracked it to Rails boot-time DB access caused by an ActiveRecord call inside a controller constant (Reward.attribute_names...) (read more).
#Plugin
The “Discourse Suggested Edits” plugin saw a boot-order/race warning: Lilly identified an initializer ordering issue (“Attempted to modify service:composer, but it was already initialized”) and proposed reordering api.modifyClass before api.customizeComposerText, including a specific code pointer and opening a PR (read more, read more).
The “Geo Blocking plugin” was impacted by a core change: LotusJeff linked an upstream GitHub issue, and RGJ replied that the problem was resolved and attributed it to a specific Discourse core change (read more, read more).
A deprecation warning surfaced for “Discourse Category Lockdown”: Luna_Mora reported console output noting .hbs connector templates are deprecated and should be refactored to .gjs (with a deprecation reference) (read more, read more).
#Feature
A localization request came in for #ai: in “希望ai插件可以设置提示词为中文” (ailocalization), bird asked for the AI plugin to support Chinese prompt text for things like summaries/titles/DM summaries, noting these currently default to English (read more, read more).
Mobile UX continues to be debated: in “Make it easier to find ‘Sign Up’ on mobile”, Jagster argued the sidebar/hamburger interaction is the core discoverability hurdle, and Lilly shared that—even if not her preferred option—some approaches are being discussed because they accomplish similar goals (read more, read more).
Lilly helped close the loop on a “feature or plugin?” support request by confirming a dismissible UI element is a private team theme component in “Is this a plugin? or a built in feature.?” (read more).
Lilly assisted troubleshooting a logo rendering issue by checking reproducibility and requesting branding settings in “Forum logo isn’t showing” (read more).
Lilly joined investigation of a permissions regression in “403 when setting publish_to_category topic timer after update”, focusing on whether the affected moderator has the necessary create/post access in the staging category (read more).
Lilly added field-testing and a possible caching/identity-provider angle to “Unfortunately, your browser is unsupported”, after verifying Firefox/Ubuntu behavior and describing a confusing password-reset loop that later resolved (read more, read more).
Lilly flagged and diagnosed a plugin initializer ordering issue (and opened a fix PR) in “Discourse Suggested Edits” (read more).
Lilly weighed in on mobile sign-up discoverability tradeoffs in “Make it easier to find ‘Sign Up’ on mobile” (read more).
Vacuumed your Docker images, chased a vanishing bug category link, and dodged a couple of 403s—just another day of spring-cleaning on Meta.
Total new topics (last 24h): 9 A slice of the activity came from threads like the composer redesign announcement (read more) and multiple bug reports around likes, unread, and uploads/CDNs (read more, read more, read more).
Top users by recent activity (posts) & appreciation (likes):
(Examples of where the conversation clustered: UX around category posting permissions (read more), troubleshooting “phantom/missing unread” behavior (read more), and a fresh alpha composer change behind a flag (read more).)
RGJ reported that topic card likes stopped working after a linting update in the #TAGtopic-cards component, and linked a fix PR; david merged it quickly (read more, read more).
Lilly found chat thumbnails bypass s3_cdn_url and leak raw bucket URLs, breaking thumbnails for some secure S3-compatible setups (e.g., Cloudflare R2) in #TAGchat + #TAGcdn + #TAGs3; sam noted a rebake after site move issues (read more, read more, plus related R2 investigation context read more).
In an upgrade edge case, db:seed_fu failed due to a user/group name namespace collision; martin investigated why an existing migration didn’t prevent the clash and moved toward a PR to reduce conflicts (and improve related permission logic) (read more, read more, read more, and the permissions feature referenced read more).
The long-running Unread count vs /unread missing topics thread gained sharper diagnosis: sam connected missing items to “small actions” suppression being only half-implemented, while RalfJung argued they were missing real posts, not just small-action closures (read more, read more); a related report was closed as a duplicate earlier (read more).
A #TAGcomposer + #TAGpwa + #TAGios regression where the Reply button wasn’t visible while composing on iOS PWA got a practical next step from olivia: rebuild the app container to pick up the resize fix (read more).
A moderator workflow started failing with 403 errors when setting publish_to_category topic timers after an update; the thread continues to focus on permissions/config changes between rebuild and reproduction (read more, read more).
putty flagged a confusing UX where the “New Topic” button still appears in read-only categories, opening the composer without the category selected; chapoi explained why the team prefers not blocking composer entry (users may want to post elsewhere while referencing what they’re viewing), and moved the thread into ux (read more, read more).
#Announcements
jordan.vidrine introduced an alpha composer redesign behind enable_new_composer_actions, replacing the legacy SelectKit actions with a unified dropdown and embedding whisper/no-bump/unlist toggles directly in that menu (read more).
The “small actions” tracking change continued to ripple outward: sam confirmed the suppression applies broadly to small actions including unlisting/listing, tying back to the ongoing unread/page behavior discussions (read more, and the implementation context read more).
Discussion continued on branding the Discourse splash screen with SVGs, with Ethsim2 exploring an “escape hatch” for a truly different dark-mode asset instead of purely variable-based recoloring (read more).
Heather_Phillips noticed homepage topic link fonts shrinking unexpectedly; chapoi pointed to the upcoming change “Modernize Foundation theme” as the likely driver and suggested disabling it; later, chapoi considered switching sizing units (REM vs EM) to avoid overly small text (read more, read more, read more, with background threads referenced read more and read more).
A self-hosted admin got stuck where new users were redirected to id.discourse.com; NateDhaliwal suggested /u/admin-login and shared the console setting to disable Discourse ID if needed (read more, read more).
An admin reported an endless spinner when staff view posts in a specific Staff category, while a subcategory worked—suggesting a category-specific setting or data edge case worth isolating (read more).
#Feature
JustinZ requested the Discourse installer accept pasted input (notably for long secrets), to avoid error-prone manual typing during setup; the thread clarified it’s about installation prompts, not signup forms (read more, read more).
#Enterprise
fsasaki shared a first iteration of an Enterprise Discourse AI Getting Started Guide, inviting feedback on feature toggles, data processed, and visibility of AI outputs (read more).
#Developer Guides
A quick documentation nit: NateDhaliwal questioned whether the Fedora dev setup guide should still say “not an official guide,” implying it may need an update/clarification (read more).
NateDhaliwal asked whether Markdown extensions described in the dev guide can be used via a Theme Component or if they remain plugin-only—useful for folks trying to keep customization lightweight (read more).
#Integrations
A Slack integration question resurfaced: can the discourse-chat-integration plugin tag specific people in Slack based on keywords coming from Discourse notifications? (read more)
jordan.vidrine announced an alpha composer actions redesign (unified dropdown + embedded toggles) behind enable_new_composer_actions (read more).
sam connected the Unread list not matching unread counts to the ongoing “small actions suppression” implementation, and clarified it’s the same underlying issue users are observing (read more, read more).
sam also closed a duplicate unread-report thread, pointing folks back to the canonical discussion so fixes land in one place (read more, read more).
sam handled site maintenance fallout by rebaking (noting likely site-move related onebox oddities) in the chat thumbnail/CDN investigation thread (read more).
david merged the fix for broken likes on topic cards after RGJ identified the removed getter calls and posted a PR (read more).
martin investigated a db:seed_fu upgrade failure involving auto-groups and name collisions, then moved toward a PR-level fix and noted implications for the anonymous/logged-in permissions work (read more, read more, and the referenced permissions feature thread read more).
chapoi guided a UX discussion about why the composer can still open in read-only categories (and recategorized the topic to ux), emphasizing that users may want to start writing and then choose an allowed category (read more).
chapoi also helped diagnose shrunk homepage topic fonts as likely fallout from the “Modernize Foundation theme” upcoming change, suggested disabling it, and later considered improvements to sizing units (REM vs EM) to avoid surprises (read more, read more, read more, with background read more).
olivia advised a practical remediation for iOS PWA composer layout: rebuild the app container to pick up the latest resizing fixes (read more).
fsasaki published an initial Enterprise Discourse AI Getting Started Guide and explicitly asked for feedback to refine it (read more).
That’s a wrap—may tomorrow’s “unreads” be less phantom, and your topic-card likes stay eminently clickable.
Foundation theme modernization hit an accessibility flashpoint.Moin reported low-contrast and sizing issues with the WCAG palette, chapoi clarified Meta can’t opt-out anymore, and jordan.vidrine apologized for delayed follow-up and committed to addressing earlier feedback—then shared multiple fixes landing via PR work (read more, read more). Related: the font-size regression discussion in Why did our home page topic links font shrink? and the ongoing ux thread in Chinese about small homepage fonts (read more).
Nested replies: admins want choice (flat vs nested), but the “view as flat” switch is gone. A request for a global flat default with per-topic nested toggling came up, and markvanlan confirmed the flat toggle was removed after internal testing; jordan.vidrine explained the “wider” layout is due to the timeline being removed (read more, read more).
Embedding comments: confirmed you can show public comments while restricting who can post to private-community members.JimCanto asked about “visible to all, comment only for members,” and featheredtoast confirmed standard permission rules still apply as long as the topic is public (read more).
Events category creation flow: “calendar category” now defaults to “create event,” and that may be too opinionated.Lou reported friction when a category needs a calendar header but mostly normal topics; awesomerobot said the default was intentional but suggested a setting might be needed for mixed-use categories (read more). Related: mobile UX feedback in It’s easier than ever to create events in Discourse! and ongoing breakage reports in the long-running Events Plugin thread.
Composer “Post Type” dropdown: topic-link rendering looks like it’s leaking HTML.jordan.vidrine flagged that the “topic link” option appears to render with HTML code mixed into the title, suggesting a formatting/escaping bug in the new composer actions UI (read more).
Spam signup mitigation on hosted/free plans: what’s realistic without custom plugins? A site owner asked for a signup “questionnaire” challenge; replies covered limits of UX-only challenges, using #DiscourseAI spam detection to hide spam posts, and admin workflows like must_approve_users (read more). Related reading: Discourse hCaptcha, Immediate actions you can take during a spam attack, and Tips for preventing spam.
Ad placements: “small banner ads” in specific UI spots may require plugin constraints and accepted locations. A support thread explored the feasibility and pointed back to standard plugin approaches like the official advertising plugin and its placement options (read more; see also Discourse Advertising Plugin).
PhotoSwipe icon collision fixed with CSS (but flagged as potentially fragile). A solved thread documented a CSS workaround after icon positioning collided with OS window controls, with a caution that UI changes may break the tweak later (read more).
Passkeys regression: “security key is not owned by the user” appears reproducible on Meta.pmusaraj confirmed reproduction (not Microsoft-specific) and flagged it as likely a Discourse regression worth immediate investigation (read more).
Unread count shows “Unread (14)” but the unread list is empty.sam noted a fix is in progress and asked affected users to hold tight while the patch lands (read more).
Invalid HTML in #topic-cards: stray <td> after glimmerization. A regression analysis explained how cells hard-coded <td> and introduced invalid markup; a PR was opened to reintroduce valid structure and keep a11y behavior aligned with core (read more).
Rich-text editor on AZERTY: apostrophes turning into l>eau-style sequences. A report in French was quickly routed to an existing related thread for troubleshooting and context (read more; related: compositeur remplace les caractères spéciaux).
UI polish: why does the “Reply” action have a background transition while text color doesn’t? A UX thread calls out inconsistent hover/transition behavior in post actions and asks whether it’s intentional or an overlooked styling detail (read more).
Meta redesign feedback continues: tiny icons on topic lists (and more). Follow-ups in the Meta branded theme rebuild thread highlighted icon sizing issues (topic list + inline icons), reinforcing that small visual changes can cascade into usability complaints (read more).
Embedding comments on a private forum + separate domains: a reported HTTP 419 “Page Expired” and what it implies. An integrations thread explored private embedding constraints and domain alignment, echoing the documented limitation that fully private forums won’t embed across unrelated domains (read more).
jordan.vidrine jumped into multiple design-forward threads: apologized and committed to prioritizing accessibility fixes in the Foundation theme modernization (read more), posted a detailed “fixed / fixed / fixed” follow-up referencing shipped corrections (read more), explained the wider nested-replies layout as a timeline-removal side effect (read more), and flagged an apparent HTML rendering issue in the new composer “Post Type” dropdown (read more). Also continued investigating font-size reports in the Foundation-related UX thread (read more).
chapoi handled a broad sweep of product/support edge cases: clarified the Foundation opt-out group is obsolete and responded to accessibility priority concerns (read more, read more), answered sidebar nesting feasibility (and later acknowledged the misunderstanding once the OP solved it) (read more, read more), and guided Horizon banner compatibility details in the Russian self-hosting thread (read more).
markvanlan confirmed a key product decision: the “view as flat” nested-replies toggle was removed after internal testing, as it wasn’t providing sufficient value to keep (read more).
featheredtoast clarified embedding permissions: visitors can see embedded comments on a public topic, but only members with permission can post—membership restrictions remain up to the community admin (read more).
sam provided a status update on the unread-state bug, noting a fix is underway and setting expectations for follow-up debugging if needed (read more).
HAWK advised on event/meetup feasibility under tighter budget scrutiny and suggested gathering data first (e.g., interest + agenda) before pushing for in-person investment (read more).
martin merged a PR to resolve upgrade failures caused by seed group-name conflicts, unblocking affected installs and prompting a backport request (read more).
pmusaraj reproduced and acknowledged the passkey login regression, flagging it for investigation and looping in another engineer for regression context (read more).
awesomerobot explained the rationale behind the new “Events category” default-to-event behavior and floated the idea of adding a setting for mixed event/topic categories (read more). Also continued accessibility/support investigation around screen readers and shortcuts behavior (read more).
If yesterday taught us anything, it’s that nested replies change the shape of everything—sometimes even the timeline—and the smallest icon can start the biggest discussion.
A quick configuration win: haydenjames asked to increase “Top Contributors” from 5→10 in the right sidebar block, and chapoi pointed out the existing count parameter in Right Sidebar Blocks (read more)
Topic tiles got more clickable and more robust: multiple community PRs landed for TLP (avatar wrapping, timestamp wrapping, blank tile click behavior), in Topic List Previews (TLP)
Mermaid diagram support saw forward motion with a community PR submission following Falco’s encouragement, in Discourse Mermaid
Facebook login documentation drift was flagged again (“/apps link is dead”), reinforcing that auth how-tos need upkeep in Configure Facebook login for Discourse
#Self-hosting
Hosting provider experiences continued: warnings about Vultr policies and a reminder that SMTP deliverability is often best handled by a specialist provider (and not necessarily your VM host) in Vultr vs DO for discourse (read more)
awesomerobot engaged on anti-spam tactics, endorsing signup custom fields/Data Explorer approaches and reassuring that proactive IP blocking hasn’t harmed Meta’s signup flow in odd spam user attack, and also explored copy/flow options to make “Yes/No” review queue actions more consistent in review queue UX.
chapoi helped reverse-engineer Meta’s layout: pointing admins at the custom homepage + Blocks API building blocks in Approximate Meta’s design, then followed up with theme-component config guidance in Right Sidebar Blocks. chapoi also dug into setting semantics and proposed updating copy/behavior around educate_until_posts in composer education message discussion, and suggested webhook-based automation for flagged-post workflows (plus a hint of “something cool” coming) in auto-reply after flag approval.
sam flagged a regression fix and deploy timing for unread state issues, crediting zogstrip’s fix in Unread is empty.
Roman acknowledged that recent changes may have overcorrected by making educate_until_posts effectively irrelevant (if the message only shows once), and committed to revisiting the implementation in educate_until_posts.
Falco reviewed a community-shared server health script and corrected a key runtime detail (“no Puma”) in Discourse-health-check, and also encouraged a contribution that turned into a PR for Mermaid support in Discourse Mermaid.
HAWK helped troubleshoot a subtle UI animation by comparing theme behavior and probing whether the transition is just more noticeable on the reply button in reply button transition effect (read more).
Yesterday’s vibe check: between bots inventing genders at signup and the review queue making “Yes” mean two different things, it’s been a wonderfully chaotic day of humans vs. edge cases.
New activity (last 24h):53 new posts, 12 new topics.
Source: see the day’s new threads like the Horizon nested-replies navigation bug report (read more) and the theme-import branch UX discussion (read more).
Top users (posts / likes received):
chapoi — 7 posts / 10 likes (e.g. Sidekiq troubleshooting advice in a webhook delay report: read more)
Andry_Osminin reported a #TAGnested-replies state bug where replies from a previously viewed topic can remain rendered when navigating via “suggested/related topics” in-app—apparently Horizon-specific, likely tied to “instant” navigation not tearing down the prior topic state (read more; Horizon vs Foundation observations: read more; markvanlan hints at an incoming fix: read more).
Passkey login troubleshooting continued for the #TAGpasskey error “The security key is not owned by the user”, with pmusaraj noting difficulty reproducing and suspecting earlier test inconsistency—while inviting more Windows/passkey implementation feedback (read more; latest investigation: read more).
A long-running report about getting 403 errors when setting the publish_to_category topic timer after an update resurfaced, with the OP reaffirming permissions hadn’t changed and they were the only admin able to change category settings (read more; latest detail: read more).
Theme import got a sharp UX audit: the “branch: main” field behaves like a placeholder, so leaving it blank sets branch=nil (not main)—leading to confusion when a theme pulls a d-compat/... branch instead of what admins think they selected (read more; chapoi escalates for triage: read more; clarification on intended d-compat behavior: read more).
A mobile #TAGpwaios regression made date labels appear “glitchy”; chapoi confirmed it as a recent regression and said a fix is being worked on (read more; status update: read more).
Composer layout edge-case: long personal-message titles overflow and get covered by buttons on Android Edge, reportedly reproducible even in safe mode on the affected site (but not on Meta) (read more; chapoi notes a recent composer UI change may make it obsolete and looks for a quick fix: read more; related composer change: read more).
Review queue consistency concerns continued: users want clearer confirmation flows because “Approved/Rejected” can mean different outcomes depending on whether you’re confirming a flag vs rejecting a queued post, and “Yes/No” actions can feel inverted depending on context (read more; continued analysis from moderators: read more).
A “silenced” confusion turned out to be historical UI: the public profile header can show a count like “silenced once” even if the admin panel shows the user is not currently silenced—clicking reveals when it occurred in logs (read more; awesomerobot explains the historical counter: read more).
Webhook troubleshooting: a user_added_to_group webhook began triggering ~24 minutes late; chapoi pointed to Sidekiq queue latency (especially the low queue) as a likely cause and recommended using /sidekiq to inspect queues and busy jobs (read more; Sidekiq pointers: read more).
Anti-abuse discussion continued around unusual spam user attacks and IP blocking tradeoffs—balancing VPN-abuse realities vs potentially excluding legitimate users in regions with pooled IP ranges (read more; Ed_S cautions about pooled IP collateral damage: read more; awesomerobot discusses VPNs as an abuse vector and the desire for reputation-based approaches: read more).
POP3 polling issues (revisited): despite Gmail forwarding and app-specific passwords “working,” an admin wanted to clear a persistent dashboard POP3 authentication warning, noting the setup involves an address forwarding into Gmail which Discourse polls for inbound email topic creation (read more; earlier related thread referenced: read more).
#Extras
A new utility tool, discourse-health-check, kept improving: community feedback suggested verifying whether backups have been read since being written (as a proxy for offsite copying), and the author added an atime-vs-mtime check with noatime awareness and credits (read more; backup check suggestion: read more; implemented in v1.0.2: read more; and yes, “Pitchfork nowadays!!” (read more)).
#Community Building
Building a customer/product feedback channel: the community recommended combining #TAG topic voting with structured intake using form templates—pointing to the Topic Voting plugin and Form Templates as building blocks for upvotes + submission forms (read more; plugin + forms pointers: read more; Topic Voting plugin: read more; Form Templates: read more).
#Translations
Translation sleuthing: a missing Arabic string for reactions’ “All” label was identified as discourse_reactions.users_popup.all, helping locate it in Crowdin (read more; key name provided by zogstrip: read more).
#Self-hosting
SEO and headings: a Russian-language thread asked how to control H1/title/description on the homepage and /categories for SEO; replies suggested some of this is already handled by Discourse document titles and that the title site setting controls the suffix/branding portion (read more; follow-up clarifying what can be changed: read more).
chapoi handled a wide spread of triage and support: asking for theme-scope repro details on the Horizon nested replies rendering bug (read more), escalating the theme-import branch placeholder confusion for engineering triage (read more) and aligning on the right fix direction (read more), confirming an iOS/PWA date regression is being fixed (read more), acknowledging the PM composer overflow and tying it to the newer composer actions UI (read more), and providing the accepted Sidekiq-based explanation for webhook delays (read more).
markvanlan jumped into the Horizon nested replies bug thread and indicated a fix is in progress, expected in an upcoming PR impacting mobile nested topic view (read more).
awesomerobot clarified a key “silenced” misunderstanding—distinguishing historical silences from current status on profiles (read more)—and continued the moderation/abuse discussion on VPN/IP blocking tradeoffs and the need for something like IP reputation rather than all-or-nothing blocks (read more).
zogstrip helped unblock translators by naming the exact i18n key for reactions’ “All” label (read more), and assisted in debugging missing user-card buttons by isolating the issue to themes/plugins via safe mode and advising to identify the offending customization (read more; confirmation it’s customization-related: read more).
pmusaraj investigated the passkey login error report and shared reproduction results, suggesting early tests may have been unreliable and noting potential Windows implementation changes as a factor worth watching (read more).
If yesterday taught us anything, it’s this: keep an eye on Sidekiq, don’t trust placeholder text, and always make sure your backups have actually been read—Pitchfork-approved.
pmusaraj released “Accent Theme”, a clean, card-based light theme with accent-driven styling and both light/dark schemes—plus support for common UI areas like chat and PMs (read more). Related references: theme install guide (read more) and the themes beginner’s guide (read more).
#Theme component
In “Discourse Sidebar Menu Reorder”, tobiaseigen documented a sharp edge: sidebar section names must match exactly (spaces become dashes), and even a trailing space can generate a slug that breaks matching—prompting Lilly to improve the component’s guidance (read more, and Lilly’s update at read more). Related component: “Discourse group sidebar menus” (read more).
In “After user update automation…”, one1 explored how to trigger an automation from a required profile/custom field while optionally including other fields, and awesomerobot suggested using conditional blocks like {{#foo}}...{{/foo}} so empty fields don’t render (read more, plus the deeper explanation at read more). The thread also surfaced a potential snag: custom-field names containing symbols may need normalization for templates to work smoothly (read more). Background: “Using the new user update automation” (read more) and “Allow ‘after user update’ automation trigger to fire without custom field” (read more).
In “How to customize AI tag and category suggestions” (aiai-helper), Falco clarified a key implementation detail: tag/category suggestions aren’t using LLMs—they rely on embeddings comparing the current draft to existing topics, which explains why “prompting” doesn’t affect tag/category output the way it might for title generation (read more).
“User Shows as ‘Silenced’ Publicly but Not in Admin Dashboard” was resolved after Tealk noticed silences were being reversed quickly; awesomerobot explained that if the underlying flag is rejected in the review queue, the system silence can be automatically lifted (read more).
In “Is anyone experiencing an odd spam user attack? Any way to block?”, mitigations ranged from Cloudflare WAF rules and log exploration (read more with Cloudflare best practices at read more) to Discourse’s official hCaptcha plugin as a signup/bot defense (read more and plugin details at read more). There was also renewed interest in Cloudflare Turnstile support as a lower-friction alternative (read more).
In “Feature request for ai title generator: toggle title/tag/category”, Frully asked for per-feature toggles (title vs tag vs category suggestions), and NateDhaliwal offered a practical workaround: hide only the title-suggestion button using CSS (button.suggest-titles-button { display: none; }) (read more).
“Group groups for groups page?” resurfaced, with satonotdead advocating for clearer hierarchy (and separating “subscriptions/team/staff” groups from trust-level concepts); awesomerobot confirmed there’s still room to discuss, though it’s not currently prioritized (read more, and team reply at read more).
#Self-hosting
In “Why can’t I install plugins locally?”, Willy dug into why copying plugin folders into /var/discourse/plugins in a production container doesn’t “just work.” chapoi summed it up: it’s not blocked, it simply won’t work as expected in that setup—use app.yml or test locally in a dev environment; they also covered using private Git repos safely via tokens (read more and private repo guidance at read more). Helpful references shared: backing up/restoring to move data into a local test instance (read more) and the plugin install guide (including private repos) (read more).
In “Discourse version 2026.6.0 and old browser resp OS”, Alfi asked for a browser/OS compatibility reference before upgrading a community with many older users; NateDhaliwal pointed to official “supported browsers” info and suggested checking “Dumbcourse” for an older-browser-friendly UI approach (read more and Dumbcourse at read more).
“Could we close the user reactions list by draging the list element down…” proposed a small-but-impactful mobile improvement: allow dismissing the reactions list by dragging within the list itself, rather than requiring a reach to the empty area above (read more).
In “Misleading ‘branch’ input in theme import” (fixed), chapoi confirmed the UX confusion is addressed via a core fix (linked PR), closing the loop on misleading UI expectations in theme imports (read more).
“Validation failed: Primary email has already been taken…” highlighted issues handling Gmail dot-variants in inbound email and secondary email workflows; ted agreed it appears to be a bug and suggested normalize_emails as a possible (but risky) mitigation while investigating (read more).
In “Oneboxed text localization issue” (oneboxcontent-localization), nat noted improvements are planned “soon™,” signaling upcoming work on localized onebox text rendering (read more).
“Old topics published via WordPress embed are missing x-robots: noindex and canonical tags” got a practical contribution: Thiago_Mobilon shared a plugin that adds X-Robots-Tag: noindex headers for topics in selected categories to help manage indexing/SEO for embedded content (read more).
pmusaraj shipped a brand-new theme announcement for Accent Theme, including preview + repo links and positioning it as “accent-color driven” with easy branding adjustments (read more).
awesomerobot was active across support + feature discussions:
Helped unblock an automation workflow by recommending conditional mustache blocks and explaining how {{#field}}...{{/field}} prevents empty-label rendering (read more, read more).
Flagged a likely edge case: custom fields with symbol-heavy names may break automation templating, suggesting simplified/normalized field keys for now (read more).
Explained why a “silenced” state can appear transient if the relevant flag is rejected and the silence is automatically lifted (read more).
Replied on group-hierarchy UX, confirming the “groups for groups page” concept isn’t currently prioritized but is still discussable (read more).
Falco provided a decisive clarification on AI behavior: category/tag suggestions rely on embeddings, not an LLM, which changes what kinds of customization are possible today (read more).
chapoi closed the loop on multiple admin/operator pain points:
Confirmed the theme-import “branch” UX issue is fixed, linking to the core PR for verification (read more).
Clarified self-hosting plugin expectations: local plugin folders in production aren’t a workable path; use app.yml or a local dev environment, and private repos remain private even when cloned with a token (read more, plus private repo guidance at read more).
martin dug into a Topic Voting configuration report, asking for concrete examples and suggesting a rails-console check (Category.can_vote?(cat.id)) to diagnose category-level voting behavior (read more).
nat briefly previewed upcoming improvements to address localized onebox text issues, signalling maintenance work in the onebox + localization area (read more).
May all your sidebar slugs be space-free, and all your automation fields render only when they’re actually filled in.
Denis_Advert noticed big UI/typography improvements in the Foundation theme and asked when they’ll roll out everywhere; darkpixlz pointed out you can enable it via the “Modernize foundation theme” upcoming change toggle (no global timeline yet). read more (solution context)
A self-host install hit the dreaded “Port 443… does not appear to be accessible” despite earlier checks passing; darkpixlz suggested bypassing the connectivity test with --skip-connection-test and linked prior learnings, while pfaffman clarified that you should not install Postgres manually (Docker includes what’s needed) and that port ownership/exposure is the real culprit. read more (skip-test workaround, follow-up clarifications, related thread)
Experimental nested-replies got called out as “a disaster” after users reported missing posts and the admin couldn’t revert cleanly—raising concerns about how reversible upcoming changes are when something goes sideways. read more
After restoring a test site, Maxine reported that all upload URLs (including avatars) rewrote back to the forum domain instead of the S3 bucket URL, and asked both how to fix and how to prevent it in production (s3hosting). read more
A reproducible mobile-web issue: the new-topic composer appears crushed/too small on “iOS 26.5 Safari Web”, while replies still work—reported with screenshots from try.discourse.org and user agent details (ios-26). read more
Admin topic editing errors: stephtara hit failures editing multiple topics and asked where to troubleshoot; Moin recommended checking the browser console and /logs, and the follow-up mentioned JS errors like “Failed to load discourse-custom-wizard”. read more (first troubleshooting step)
OAuth reality check: awesomerobot walked through Microsoft login and found it requires a free Azure/Entra setup (including a credit card during registration) but not necessarily payment; they also tested Facebook login and noted the “verify as a business” friction that can block completion (auth-plugins365-oauthsocial-auth). read more (topic start)
Composer auto-replacement pain: a French-writing workflow got wrecked by special-character substitution (especially apostrophes), prompting stephtara to disable the setting—even while mourning the loss of emdash replacement (composer). read more
Cloudflare R2 migrations: David_Ghost reported that older uploads still render with the R2 endpoint URL (and only show correctly with a particular theme component), while Lilly suggested running uploads:migrate_to_s3, rebaking posts, and ensuring DISCOURSE_S3_CDN_URL is set—plus a possible discourse remap fallback. read more (rake + rebake guidance, CDN URL ordering)
#Site feedback
AI language detection & stale translations: stephtara saw an English post labeled as French (apparently triggered by the word “French”), then edits “not showing” until it became clear they were viewing an outdated translation; Moin explained the locale button and how translations can lag edits (aidynaloccontent-localization). read more (diagnosis, follow-up)
The “New Topic” button appearing even when users can’t post got an update: Moin surfaced that a hidden site setting (hide_disabled_create_topic_button) can restore the older behavior—hiding the button in read-only contexts once you’re on a version that includes the merged change. read more
#Theme component
The Image Comparison Slider theme component got a substantial modernization proposal: Arkshine shared a PR adding zoom/pan, fullscreen, lightbox originals, keyboard accessibility, RTE editing support, group restrictions, and a new [wrap]-based format—while keeping backward compatibility. read more
WeChat Mini Program integration: the thread explored whether embedding Discourse inside a Mini Program is worth it, the challenges around WeChat identity/email, and broader China-specific browser/app ecosystem constraints; typed-sigterm added on-the-ground context for why “just open it in a browser” often isn’t realistic. read more (ecosystem context, related WeChat login thread)
#Migration
PHPBB migration security tradeoffs: pfaffman recommended the long-standing migrated password hashes approach for self-hosters, while RGJ pushed back on blanket “don’t migrate passwords” advice, noting the plugin’s track record and emphasizing keeping insecure-password allowances disabled. read more (plugin reference, security discussion)
#Site Management
Auto-bump refinement request: patrickemin suggested making auto-bump selection smarter by factoring in interest signals (views/votes) and age thresholds, and referenced a related pain point about keeping only the last auto-bump alert message. read more (related suggestion thread)
awesomerobot investigated real-world friction in third-party auth setups—confirming Microsoft login can be configured with a free Azure/Entra account (credit card required during setup, but not necessarily paid) and documenting where Facebook login flow can dead-end without business verification. read more
awesomerobot also chimed in on responsive behavior nuances for the Custom Header Links theme component—reminding everyone that tablet layout behavior depends on device size and orientation. read more
Yesterday’s vibe: between AI confidently “detecting” French from the word French and admins learning the magic of --skip-connection-test, it was a day of polite chaos and practical workarounds on Meta.
ばこん — 1 post, 1 like (free plan economics question: read more)
Hasimir — 1 post, 0 likes (Custom Wizard crash report with stack trace: read more)
Interesting Topics
#site-feedback
ばこん asked how Discourse can sustainably offer a free plan, with merefield framing it as a sensible conversion funnel business model and ice.d pointing to paid-plan economics (read more, read more).
Ongoing investigation into Cloudflare R2 image URL / thumbnail display issues: David_Ghost reported old thumbnails still broken even after remapping, while Lilly shared a fix-in-progress and linked a related chat-thumbnail thread (read more, read more, plus related: read more).
A fresh report that the nested-replies experimental feature may be buggy (or at least under-documented in the community so far): Moin noted it’s new, it’s the weekend, and suggested alternate routes for quicker attention (read more, read more).
Spam defenses and tradeoffs: in an “odd spam user attack” thread, mcdanlj advocated suspending forever to harvest patterns and argued for an option to block email without blocking IP, with Ed_S agreeing and comparing moderation workflows (read more, read more).
Group management clarity: ice.d asked what setting a “primary group” is actually for, and itsbhanusharma highlighted a practical win—flair precedence when multiple group flairs exist (read more, read more).
A Safari-only editor failure was narrowed down: stephtara tracked an error when editing a topic to the presence of tags, observed it disappears in safe mode / with other themes, and suspected the air-theme path specifically (read more, plus the cross-reference in the Air Theme thread: read more).
Discourse Automation field templating: one1 confirmed {{languages}} works but struggled with profile/custom fields whose names contain punctuation/parentheses, raising the possibility of either naming constraints or a needed code-level tweak (read more).
#self-hosting
stephtara explored the idea of giving Claude Code read-only access to a self-hosted Discourse (SSH + DB), seeking ways to lock down sensitive paths and permissions while still enabling efficient troubleshooting (read more).
#announcements
In the granular group-based permissions announcement thread, Moin dug into theme-component implications and “pseudo-group” behavior, referencing prior art and edge-cases around group-ID comparisons (read more, and mentioned component context: read more).
#plugin
Calendar UX request: Lou asked whether event locations could support typeahead/lookup (like Google Calendar/Facebook) and become clickable to open map apps (read more).
Potential breaking change: Hasimir reported that a recent core update appears to crash the discourse-custom-wizard plugin during boot (even blocking safe mode), sharing an admin_stylesheets registry error and confirming disabling the plugin restores startup (read more).
#theme
More signals that Air Theme may have a Safari-specific interaction issue, with stephtara providing a reproducible path tied to editing a tagged topic (read more and supporting investigation notes in read more).
On FKB Pro, xlg256 praised the card UI but reported confusing mobile “hit-or-miss” tap targets, proposing a CSS pointer-events whitelist approach so only key content areas are clickable (read more).
The long-running WeChat Mini Program integration thread saw activity (a post by merefield was later deleted by the author), indicating continued interest/maintenance attention in that integration space (read more).
Lilly followed up on the Cloudflare R2/chat thumbnail display investigation, noting that prior steps didn’t resolve it for the reporter and pointing to a PR/fix thread for chat thumbnails (read more, related fix thread: read more).
Yesterday’s vibe: we chased Safari tagging gremlins, debated the economics of “free,” and tightened the anti-spam toolkit—all before the weekend even cooled down (read more, read more, read more).
HAWK clarified that Discourse’s free tier is effectively a freemium acquisition layer (often behaving like an “indefinite free trial”), while others dug into what “power usage” really means in terms of typical server sizing and cost — read more.
Related context on the “minimum vs recommended” hosting footprint was also shared from install guidance — read more
#Announcements
Meta’s live experiment with Boosts was disabled for now after feedback, with commenters asking Discourse not to abandon the idea and suggesting it could complement likes/reactions rather than replace them — read more.
Several folks argued for making Boosts an optional mode alongside classic reactions — read more
#Announcements
The “Solved improvements” feature (letting users indicate they’re also experiencing an issue) got follow-up tweaks: it’s now a category-specific setting, and the button label can be customized right in category settings — read more.
This should make it easier to enable for true support areas while keeping noise out of categories where it doesn’t fit — read more
On iOS Safari (iOS 26.5), the new topic editor/composer can become unusably small; awesomerobot suggested hiding the toolbar via the ☰ button as a temporary workaround while considering UI improvements to preserve at least one line for typing — read more.
The discussion also resurfaced a mobile fullscreen composer theme component thread, now updated to work on newer Discourse versions — read more
A navigation bug where posts from the previous topic remain rendered after in-app navigation received an update: markvanlan noted the fix landed as part of a larger mobile UX refactor and was merged, with a request for testers to confirm after updating — read more.
The same area also references ongoing quirks like the formatting of the views label — read more
The experimental nested-replies feature caused a nasty failure mode when toggled: disabling it could lead to missing-message errors, and markvanlan asked for screenshots + suggested URL swapping (/n/ ↔ /t/) as a diagnostic — read more.
The thread highlights how hard “safe rollback” can be for experimental UX features if URLs/routes behave differently — read more
#Feature
A request came in to include reply-to notation in /raw/<topic>/<post> output, so raw text can preserve reply relationships; responders pointed out the JSON already includes reply_to_post_number, and asked for more context to clarify the need — read more.
If you’re building tooling, this is also a good moment to confirm whether JSON endpoints can replace raw text for your workflow — read more
The Right Sidebar “Tags” block appears to “consume” tag data on load, leaving the native header tag dropdown empty; chapoi confirmed reproducibility and called for triage — read more.
The report includes clear reproduction steps and a simple workaround (remove the block) while awaiting a fix — read more
On tag pages, the tag info (circle-info) button can appear clickable but do nothing (notably on localized tag paths like /ap/about); awesomerobot filed a PR to hide the button when the reused component lacks the data it expects — read more.
This is a nice example of a “component reuse” edge case that only shows up in less common navigation flows — read more
An edge case in content localization was documented where the UI language stays English while topic list elements (titles/tags/excerpts) partially flip to German after changing the header language in a separate tab — read more.
The repro steps are concrete and should help narrow down caching/state leakage across tabs — read more
Theme import UX got a practical polish: the “branch” input can be misleading, so david opened a PR to show the actually installed branch and the resolved target branch used for updates — read more.
This comes from real-world confusion where instances pulled from a compat branch instead of main — read more
Foundation-theme-related font sizing is still a hot topic: users noticed subtle UI improvements, while others reported the homepage font becoming too small after rebuild updates; jordan.vidrine confirmed it’s on the fix list — read more.
Related chatter continues in the broader “Modernizing the Foundation theme” announcement thread — read more
A developer workflow issue: GitHub Actions failing a “Check SKIP_DB_AND_REDIS bootability” step led david to suggest toggling schema_cache_dump to reproduce locally, and floated the idea of adding an ENV to control it more cleanly — read more.
The report calls out a specific ActiveRecord attribute edge case that likely wasn’t considered previously — read more
A Chinese-language dev post shared an AI/LLM-assisted refactor of a Flarum import script (tested and posted as a gist), and cocococosti asked for more detail about the migration needs to better understand the use case — read more.
If this grows legs, it could become a handy community-maintained bridge for Flarum → Discourse migrations — read more
#Self-hosting
A security-minded question on giving Claude Code read-only access to a self-hosted install got a candid answer: you can create a read-only SSH user, but it can still read highly sensitive data (PMs, hashes, IPs, API keys), so a sanitized duplicate environment is often safer — read more.
This aligns with Discourse Team’s own policy of not allowing LLM access to production databases — read more
Yesterday’s vibe check: Boosts may be paused, but the community still found plenty of ways to boost ideas—especially by making composers bigger, tags less confusing, and branches more honest.
Suggested likely network/Gem download issues during rebuild in China — read more
A few more threads that also saw fresh momentum: nested replies feedback and fixes — read more — plus right-sidebar tag dropdown conflicts — read more — and user-directory filtering edge cases — read more.
Interesting Topics
#Announcements
A highly experimental redesign of the admin dashboard was previewed by lindsey, focusing on a more modular hub for KPIs, pinned reports (including Data Explorer queries), traffic, and engagement—follow-up discussion quickly zeroed in on customizable KPIs and better-fit stats for non-public/internal communities (dashboard) — read more (see also the KPI customization ask: read more, and the follow-up question from lindsey: read more).
Discourse introduced the unified “New” view as the upcoming default topic-list experience, consolidating the old /new and /unread split into clearer subtabs (Topics / Replies / All), with guidance to manage it via “Upcoming changes” — read more (background: read more, and the “Upcoming changes” system: read more).
“Testing Boosts on Meta” got an update from martin noting that rolling boosts/likes/reactions may return, but the combined concept isn’t getting full attention right now — read more.
The nested replies announcement thread continues to collect real-world UX feedback (including alternative collapse patterns and moderation visibility concerns), with settings-based suggestions and PR follow-ups (nested-replies) — read more (and the recent fix pointer: read more).
The Horizon theme’s High Context Topic Cards got a positive field report after someone “gave it a spin” and shared screenshots (horizon-theme) — read more.
A likely regression was reported where the user directory (/u) search fails to match user custom fields even though global search does; zogstrip replied with a fix PR to align the code paths (user-directory) — read more (fix note: read more).
A new report showed SVG badge icons importing but not rendering, with awesomerobot diagnosing missing dimensions (common with some Font Awesome SVGs) and preparing a core fix (badgesbug) — read more (diagnosis + PR link: read more).
The right sidebar tags block was conflicting with other tag dropdowns; martin acknowledged and linked a fix PR (right-sidebar-blocks) — read more.
A self-host reported Discourse Gamification’s /leaderboard returning 404 due to a MissingAttributeError caused by a narrow SELECT list omitting users.admin/users.moderator, with a suggested patch (bug) — read more.
A particularly gnarly nested-replies-related bug persists where posts from the previous topic remain rendered after in-app navigation; markvanlan shipped “another go” at a fix PR and asked for retesting (nested-replies) — read more (latest fix attempt: read more).
The upgrade issue where db:seed_fu fails on 002_groups.rb due to “Name has already been taken” saw martin pointing to a PR resolution — read more.
A new self-host deployment thread covered Discourse failing to bootstrap (bundle install exit code 15); responders asked for earlier log lines, while another user suggested the likely culprit was network/Gem access issues in China during a sensitive period — read more (request for more logs: read more, network hypothesis: read more).
A report found /u?exclude_groups=admins behaves differently when logged out, potentially exposing admin accounts despite group pages being inaccessible; discussion explored group visibility/privacy semantics and info-leak implications (groupsuser-directory) — read more (follow-up confusion/analysis: read more).
A restore/migration thread revisited why images can lose correct S3 bucket URLs after restore, including advice that restore tooling needs S3 config available during restore and a note about discourse backup --sql_only to avoid URL rewrite (s3hosting) — read more (ongoing details: read more).
An AI Tools Test Runner edge case was confirmed: HTTP only works to port 80; other ports default to HTTPS, and the topic was marked solved (rest-apiai) — read more.
lindsey kicked off the day with a detailed preview of the redesigned admin dashboard and then explicitly asked the community which KPIs/datapoints they’d want to see modularized (dashboard) — read more, read more, read more.
martin announced unified new (making the combined New experience the default) and later helped keep the “Boosts” expectations grounded while still optimistic about its return — read more, read more. He also linked fixes for two separate issues: right-sidebar tags conflicts — read more — and a seed_fu/groups validation failure — read more.
nat responded to early dashboard feedback with a “soon” nod on KPI customization, and separately acknowledged a UX edge case around language mismatch between UI language and translated content (content-localization) — read more, read more.
HAWK started a thoughtful #Enterprise thread on community ownership models (where community teams “sit” org-wise), and teased upcoming Workflows as “superpowered automations” in an automation thread (automation) — read more, read more.
chapoi helped reduce confusion around New vs Unread in the unified-new thread and encouraged version-checking for admins who couldn’t see the toggle — read more, read more. They also shipped a small UX win for the Discourse GIFs component: the GIF button now appears in the regular mobile toolbar like desktop (officialgifs) — read more.
Falco provided the accepted solution for the AI Tools Test Runner behavior: HTTP-to-non-80 ports defaulting to HTTPS (ai) — read more.
markvanlan continued shepherding #nested-replies: offering a configuration-based approach to limit depth and shipping PRs for nested-reply-related glitches, including a fix for moderation visibility and another attempt at the “carry-over rendered posts” bug — read more, read more, read more.
awesomerobot clarified terminology for New vs Unread vs Unseen (and why unified new aims to be more intuitive), and diagnosed/fixed the SVG badge-dimension rendering issue (badges) — read more, read more.
gerhard advised on an S3 restore situation, emphasizing that restores need S3 to be configured in the right place and suggesting discourse backup --sql_only to avoid upload URL rewriting (s3hosting) — read more.
david jumped into a Development thread with concrete reproduction commands to test SKIP_DB_AND_REDIS bootability behavior across modes — read more.
A composer polish fix got merged (HR stealing focus from emoji picker): read more
Nested replies rollout continued to shake out edge cases (topic “leaking” fix confirmed + styling follow-ups): read more
Discourse hosting/pricing questions popped up again: read more
AI / sentiment resources were re-linked for folks exploring customization limits: read more
Interesting Topics
#Announcements
GIFs are moving into core (via Klipy), with migrations and gotchas for existing setups.davidb announced the core move and outlined migration paths for hosted vs. self-hosted installs, including a rake task for self-hosters: read more. Related context: the “Upcoming changes” system that can surface this in-admin: read more, and the long-running GIF component/thread where the UI placement came up: read more.
Admin dashboard redesign continues to evolve, with community metrics talk surfacing alongside screenshots. The redesigned dashboard preview thread picked up fresh discussion about what’s useful to measure and how teams pull stats via custom queries: read more.
The unified topic list view is iterating on empty-state UX and “how much guidance is too much.”martin shared updated copy/layout that avoids overly verbose empty states for long-time accounts while still helping new users: read more.
Nested replies remains a “center of gravity” feature—people are now joking that even announcements should be nested. The nested replies announcement thread is still attracting meta-discussion and adoption momentum: read more. For an older “can Discourse do this?” reference that now has a clear answer: read more.
Boosts brainstorming continued, with a “Medium claps” style finite-currency angle. The Boosts experiment thread got a thoughtful comparison to Medium’s multi-clap mechanic and what it might imply for long-form/community incentives: read more.
Hiding admins from rankings/user directory: a practical CSS workaround emerged (and a deeper privacy model discussion). The thread explored why /u?exclude_groups=admins behaves differently depending on group visibility, and ended with a “just hide the row” CSS solution for anonymous views and top-contributor blocks: read more. Related sidebar component context: read more.
SQL-triggered badges: how to attach grants to a specific topic/post.chapoi suggested adding a post_id subquery (and the need to target posts) so awarded badges can point at a canonical topic: read more.
Content Localization language switcher confusion: UI toggle visible, but locale not changing as expected.Moin reported that selecting a language didn’t actually switch the interface language; the discussion quickly pointed to a required cookie-based locale setting mentioned in the AI localization guide: read more, with the referenced manual here: read more.
Event reminders: can they email instead of being “easy to miss” in-app notifications? The request/experiment is underway, including whether commenting on an event might trigger emails for RSVP’d users: read more.
Bilibili embeds: iframe whitelisting vs. simply posting a link (and when a plugin helps). A support thread in Chinese walked through why an iframe approach didn’t render as expected, and pointed to the bilibili onebox/plugin route; the OP ultimately found that posting a link could “just work”: read more. Related plugin reference: read more.
Ad placements + nested replies: too tall/annoying layouts and occasional sizing glitches.Moin documented how ads feel especially intrusive in nested replies topics and also noted edge cases where ads don’t reserve enough space (quotes/polls): read more.
PDF previews regression: clicking the PDF link downloads instead of opening in a new tab. The report notes this is especially painful when users want a full-window PDF view, and flags inconsistent behavior between local uploads vs. S3; a fix was linked via PR: read more. Historical reference for intended behavior: read more.
ActivityPub federation: [event] (and other markdown-like artifacts) leaking into fed posts. A fresh reply reiterated that event syntax (and other formatting) showing up on Mastodon can be embarrassing, especially when edits also federate: read more.
Horizon + Events: “New Topic” label regressed in the sidebar even though it creates an event. The issue is cosmetic but confusing; chapoi linked a fix PR after the report, and the thread references ongoing Events improvements: read more. Related plugin context: read more.
Upcoming Changes notifications: should Discourse notify you about changes that are hidden because the theme/plugin is disabled?Moin reported a notification that led to an empty/hidden state, suggesting the notification itself might need suppression when the change is not actionable: read more. Background on the Upcoming Changes system: read more.
Extending Discourse Chat “message blocks”: request for a plugin API/extension point. A developer asked whether chat’s structured blocks JSON could become extensible (e.g. registerChatBlockType) to support richer cards for GitHub/GitLab-style activity feeds without patching core internals: read more.
davidb drove the core GIFs announcement and migration details, including guiding self-hosters who couldn’t see the new setting yet and discussing migration edge cases (e.g., domain allow/deny lists and translation overrides): read more, read more, read more.
nat helped clarify rollout timing for the GIFs-to-core build and also showcased the new GIF flow in the admin dashboard preview conversation: read more, read more.
david engaged deeply on group visibility/privacy implications in “exclude admins from directory” behavior, including why group membership inference matters and what configurations change behavior: read more, read more, read more.
Falco acknowledged an unfinished fix around ad layout in nested replies topics and pointed to documentation when troubleshooting the content localization language switcher: read more, read more.
chapoi responded across multiple threads: clarifying the GIF button’s new location, proposing SQL to associate badge grants with a topic’s first post, and acknowledging/fixing the Horizon “New Event” sidebar label regression: read more, read more, read more.
HAWK pushed the enterprise/community conversation forward by probing how community teams handle cross-department mandates and member-first boundaries inside marketing-led org structures: read more.
zogstrip chimed in with a concrete fix path for the PDF-preview regression (noting S3 vs. local inconsistencies), and confirmed that Discourse does indeed offer a free plan (pointing to pricing): read more, read more.
awesomerobot corrected a bot hallucination about “censored usernames,” clarifying that watched/blocked/censored words don’t apply to usernames and that reserved usernames is the current tool (with admin exemptions): read more.
renato confirmed a UX polish fix was merged for the composer (horizontal rule stealing focus from the emoji picker), thanking the reporter/contributor: read more.
martin shared updated thinking and visuals for the unified topic list view’s empty-state guidance, aiming for a better balance between help and noise: read more.
Sign-off: If yesterday proved anything, it’s that Discourse can now power serious admin dashboards and the occasional GIF-only philosophical debate—just try not to let the ads nest themselves too.
Sara_Carmona_y_Lladó dug into AI Translation behavior changes—specifically why “Translatable categories” disappeared and how cost/scope is now determined—and Moin confirmed there was a migration to excluded categories, including how the values were converted and where to audit changes (staff action logs), plus a handy Data Explorer query to inspect translation volume (read more, migration details, SQL idea, referenced migration note, aidynaloc).
JDParker couldn’t add a secondary email because the UI button was missing; the culprit ended up being the email_editable site setting (and related settings that can hide email edit controls) (question, diagnosis, solution).
A mobile layout oddity with custom-header-links (a “Blog” link dropping to the bottom-left) was traced to wrapping/padding behavior, and a fix was merged to prevent the bad wrap on mobile (report, fix).
Livestream has been officially folded into the Events plugin, consolidating virtual/in-person events and livestream scheduling under one roof, with notes about migration behavior and hosted plan availability (announcement, calendar-and-eventsdiscourse-livestream).
#Feature
The long-running “Matrix protocol for chat” thread got a fresh jolt: pmusaraj shared a proof-of-concept Discourse ↔ Matrix chat bridge, including a test instance and follow-up debugging around federation and room visibility (PoC drop, follow-up fix, community context, chat).
A new embedding feature request asked for embeds to optionally include the first post (or even a “create topic” flow) so external sites can show context + multiple related threads; the proposal builds on existing embed capabilities and prior discussions (feature request, topic list embeds, classic comments embed, prior first-post approach, embedding).
Recurring events localization: an Every [missing %{weekday} value] rendering bug (notably on en-UK) turned out to already be fixed upstream, but required pulling newer commits; a rebuild/update resolved it for the reporter (bug report, fix status, confirmed resolved, calendar-and-events).
Nested replies met advertising layout: topic list ads were consuming too much vertical space in topics using nested replies, and fixes landed in the component (not the main Ads plugin), plus a candid “wrong plugin” detour that will feel familiar to anyone who’s debugged ad stacks (fixes + context, Ads plugin reference, nested-replies).
A chat + CDN issue remained in the review queue: chat thumbnails were reported to bypass s3_cdn_url and instead use raw S3 bucket URLs; the PR was described as waiting on human review after automated help got tests green (status update, question, cdns3chat).
Composer behavior change: auto-conversion of certain characters was removed while typing in the rich editor (though conversions may still happen during cooking under some conditions), which ties into ongoing reports of “apostrophe becomes quote-like characters” on some installs/locales (team explanation, related report, older similar issue, composer).
Admin navigation feedback: RGJ argued that Tags and Tag Groups are still too “hidden” in the new admin IA, suggesting they deserve first-class placement under Content rather than being discovered indirectly via settings links (proposal, tagstag-groupsadmin-sidebar).
A micro-interaction deep dive: the “Reply” post action’s background transition effect was questioned as inconsistent with other controls; awesomerobot traced it to older UI behavior and pushed a PR to remove an unnecessary transition while discussing whether the subtle hover differentiation still earns its keep (PR context, behavior rationale).
#Theme component
DiscoTOC + translations: Honeyxilia reported that enabling DiscoTOC’s side panel can make the topic translation swap button effectively disappear, and asked for a way to keep the default Discourse control accessible even with the TOC panel present (report, officialdisco-toc).
#Site feedback
Tag translation quality got an on-meta improvement: nat confirmed that several problematic AI-generated tag translations should now be handled properly on Meta, while noting that passing richer context to the tag translator is still not high priority (update, tagsaidynaloc).
lindsey announced that livestream is now part of the Events plugin and outlined enablement + migration details (read more); she also acknowledged a report about recurring RSVP “going” state not resetting and flagged it for investigation (read more).
pmusaraj revived the Matrix chat discussion with a Discourse ↔ Matrix bridge proof-of-concept and iterated live based on early tester feedback (room visibility/federation) (read more, follow-up, implementation notes).
awesomerobot confirmed the recurring events localization bug was already fixed and advised updating to pick it up (read more); merged a mobile layout fix for custom-header-links (read more); and dug into the “Reply” button hover transition behavior, including rationale and cleanup (read more, PR context).
Falco posted the concrete fixes for excessive ad spacing with nested replies—after discovering it lived in a separate topic list ads component rather than the main Ads plugin (read more).
renato clarified that the rich editor no longer auto-converts characters while typing (though cooking-time conversion may still happen), pointing to the relevant change (read more).
zogstrip quickly sanity-checked whether the recurring events localization issue was running on a version that included the very recent fix (read more).
martin pointed folks tracking Foundation rollout to the canonical modernization thread (read more) and confirmed a UX bug where some upcoming-change notifications are hidden, promising a fix (read more).
nat confirmed fixes/cleanup for AI tag translations on Meta (read more) and acknowledged a bug report about translated-language post links for further investigation (read more).
chapoi followed up on recent Data Explorer changes and suggested updating to rule out a newly-fixed UI issue (read more); helped debug an external email recipient rejection by focusing on group-alias recipient limits and relevant site settings (read more, settings check); and clarified limitations in the GitHub integration architecture (commit/PR oriented, not issue comments), pointing toward the right feature request path (read more, related feature request).
saquetim explained that Doc Categories doesn’t support a card view yet (theme customization likely required) and pointed to the plugin’s compatibility pinning approach for ESR/self-hosters (read more).
Yesterday’s vibe: merge a plugin, bridge a chat network, and then rebuild anyway because “latest” is sometimes just a state of mind.