More threads that saw fresh replies (worth a quick skim):
Nested replies SEO behavior was examined in depth (read more), embedded comments access-control got a thoughtful question (read more), and splash screen branding continued to evolve with dark-mode asset considerations (read more). Self-hosting and ops folks also chimed in across “Discourse Meetup” planning (read more), Slack integration automation ideas (read more), Fedora dev environment docs cleanup (read more), theme/markdown extensibility questions (read more), free-plan expectations discussion (read more), and disk/log footprint troubleshooting (read more).
One recurring theme: small UX changes and “invisible” system behaviors (unreads, composer flows, theme modernization) can have outsized impact on day-to-day community operations.
Interesting Topics
#Announcements
jordan.vidrine introduced an alpha composer redesign: a unified “Post Type” actions dropdown behind enable_new_composer_actions, bringing mode switching and toggles (whisper/no-bump/unlist) into one consistent menu (read more).
Follow-up clarification landed that “small post actions” changes apply broadly—including unlisting/listing—which matters for how sites track/watch topic activity (read more).
#topic-cards:RGJ found that a linting update broke liking from topic cards, and david quickly merged the fix—great example of tight plugin maintenance loops (issue report, merge confirmation).
The long-running “phantom/unreliable unreads” situation got sharper diagnosis: sam tied missing items on /unread to the half-finished implementation of suppressing “small actions,” with a fix underway (analysis, status update). For context, a related report had been closed as a duplicate (read more).
A subtle but important permission UX question: the New Topic button remains visible even in categories where the user can’t create topics. chapoi explained why the behavior is intentional (don’t block composer opening), while others suggested CSS/theme-component workarounds to reduce confusion (problem statement, team position, CSS approach, alt component).
Spam defense strategy on constrained hosting came up again: a request for a signup “questionnaire” was met with practical guidance around bot behavior, hCaptcha, AI spam detection, and admin-side mitigations like approvals (topic, hCaptcha pointer, AI suggestion + resources, approval workflow idea). Related reading: hCaptcha plugin thread (read more), incident playbook (read more), and prevention tips (read more).
A site noticed shrunken homepage topic-link fonts without theme changes; the likely culprit was the “Modernize Foundation theme” upcoming change. Disabling it resolved the issue, and there’s discussion of improving sizing semantics (e.g., REM vs EM) (report, how to disable, follow-up on sizing). Background threads referenced: rebuild chatter (read more) and the modernization initiative itself (read more).
A Discourse Hub / iOS login snag: Meta appeared inside the app unexpectedly, and an SSO user reported being prompted for a “Discourse login” despite using Google successfully in-browser (read more).
An older-but-still-active question resurfaced: alphabetizing within a category—and whether any workarounds exist when similar requests have been closed elsewhere (read more).
#Feature
A small quality-of-life request: allow pasting input during installation (typing long secrets blindly is rough). The thread clarified this is about the installer flow, not signup UX (request, clarification).
#Self-hosting
Self-hosting troubleshooting: a site redirecting to Discourse ID unexpectedly led to suggestions like using /u/admin-login and toggling enable_discourse_id via console (symptom, suggested fix).
A Russian-language request asked how to add a homepage banner (notably with horizon-theme), and got pointed to the versatile banner solution (question, suggested component, plus the referenced banner topic: read more).
#Plugin
official#calendar-and-events: clicking a calendar date to create an event triggered an immediate “discard post?” prompt; the “New Event” button worked fine. The behavior was reproduced and confirmed as a bug, alongside practical UI customization ideas (bug report, confirmation, custom UI tip).
#Enterprise
fsasaki published the first iteration of an Enterprise Discourse AI Getting Started Guide, inviting feedback on feature toggles, defaults, and operational considerations (read more).
Questions about the Sentiment dashboard dug into how sentiment is assigned, why only some posts are classified, and what knobs exist (backfill age, agent configuration, settings filter) (question, configuration pointers). Related docs: Sentiment feature overview and backfill details (read more).
jordan.vidrine shipped an early look at a composer actions redesign (new dropdown + integrated toggles) behind an alpha flag, giving admins an opt-in path via upcoming changes (read more).
sam confirmed the “small actions” change affects all small actions (including listing/unlisting) (read more), and also connected unread-list inconsistencies to the in-progress suppression work—then reassured folks a fix is being worked on (read more, status update).
david merged the fix for broken likes in topic-cards after a linting-related regression was reported (read more).
chapoi weighed in on two UX/support threads: why New Topic remains clickable even where posting isn’t allowed (read more), and diagnosing unexpected font-size changes as likely tied to the “Modernize Foundation theme” upcoming change—plus a note that sizing may be improved (REM vs EM) (read more, read more).
martin resolved a db seeding upgrade failure by merging a fix for group name conflicts, also noting knock-on improvements for upcoming-change logic tied to granular permissions (fix context, merge update, related permissions thread: read more).
fsasaki posted an Enterprise-focused Discourse AI onboarding guide and asked for iterative feedback to improve it (read more).
HAWK advised using tags (with tag groups)—not ever-more-granular categories—to manage multi-product/multi-version announcements, enabling users to watch product/version tags cleanly (read more).
May your topic cards be likeable, your unreads be real, and your composer toggles always live exactly where you expect them.
Moin raised renewed accessibility concerns with the ongoing Foundation theme modernization, including reduced visual affordances under WCAG palettes; chapoi clarified there’s no longer an opt-out on Meta and jordan.vidrine apologized and committed to prioritizing fixes, following up with multiple specific UI fixes. (read more)
In the nested replies rollout (nested-replies), curi asked for a “flat default with nested as an optional view”; markvanlan shared that the internal “view as flat” toggle was removed, while jordan.vidrine explained perceived width changes due to timeline removal. (read more)
Discourse’s embedded comment system got a clarification on permissions: featheredtoast confirmed that standard forum permission rules apply—users must still be members to comment in the embedded window, and the embedded topic must be public to display for visitors. (read more)
A UX wrinkle surfaced in Events category creation (calendar-and-events): Lou reported that “Events Calendar Categories” now tend to default to creating events when composing, which is awkward for mixed-use categories; awesomerobot confirmed the change was intentional but suggested a future setting may be needed. (read more)
The new “Post Type” composer actions dropdown had an early rendering bug where “topic link” displayed HTML along with the title; jordan.vidrine flagged it and linked a fix PR. (read more)
A common admin IA request came up: nesting sidebar links (sidebar) under a collapsible “Groups” parent. While that’s not currently supported as a built-in nested structure, haydenjames ultimately solved their use-case by using Discourse’s built-in custom section configuration. (read more)
A Russian-language self-hosting question asked how to add a banner on the homepage with the horizon-theme; discussion pointed to compatibility constraints in Horizon (read more) and the caveat-heavy compatibility of Versatile Banner (read more), plus the official guide to Discourse’s core banner feature. (read more)
A question on small banner ads placement led to the pragmatic answer: core placements are limited, and the Discourse Advertising Plugin is the closest match (notably “Topic List Top” positions). (read more)
Accessibility support continued with JAWS screen reader + shortcuts (accessibilityux): awesomerobot explained current assumptions (screen reader users typically don’t use Discourse shortcuts), outlined why announcements aren’t being read during shortcut navigation, and discussed table-navigation behavior for category lists. (read more)
A visual UI snag in PhotoSwipe (lightbox) was resolved via CSS to avoid icon collisions (with a note that it’s niche and potentially fragile against future changes). (read more)
A passkey regression (passkey) was reported: “The security key is not owned by the user” when attempting passkey login. pmusaraj confirmed they could reproduce on Meta (even outside Microsoft ecosystems), suggesting a Discourse-side regression worth investigation. (read more)
The Unread counter mismatch bug (“Unread (14)” but /unread is empty) got a concrete status update: sam pointed to a regression fix commit and noted deployment timing. (read more)
A French keyboard/input issue was raised: in the rich-text editor on AZERTY keyboards, typing an apostrophe can incorrectly produce l>eau. The workaround/reference was linked to an earlier related report. (read more)
In the topic-cards component (topic-cards), RGJ diagnosed invalid HTML caused by a stray <td> after glimmerization and opened a PR introducing a table structure plus connectors/CSS adjustments to keep output valid and accessible. (read more)
Upgrade tooling friction: Db:seed_fu fails on 002_groups.rb during upgrade due to “Name has already been taken”—and there was an explicit request to backport the fix to release/2026.5. (read more)
A subtle UI inconsistency was spotted: the Reply post-action button shows a background transition effect that doesn’t appear consistently across other buttons; HAWK asked which theme is in use, noting that Meta Branded and Horizon do apply effects broadly. (read more)
Ongoing Meta redesign feedback (meta-redesign-2026): icons in topic lists (including bookmark/title-adjacent icons) were reported as too small, with screenshots and comparisons posted for review. (read more)
#Plugin
The long-running Migrated password hashes support thread saw a significant security-related improvement: RGJ explained how legacy hashes persist via import_pass fields, then pushed an update to clear that field on every successful login to prevent old hashes from remaining usable after password resets or alternative auth. (read more)
Quick plugin health notes: Discourse Video Stream users reported an initial audio issue that resolved after re-upload, suggesting edge-case handling during first ingestion. (read more)
Related threads that were referenced and/or active in the same 24h window (for extra context): Foundation sizing regressions (read more), homepage font shrink follow-up (read more), private-site embedding limits and HTTP 419 debugging (read more), marketplace-adjacent “build it yourself” sidebar nesting discussion via Indented Subcategories (read more), and the canonical banner documentation (read more).
jordan.vidrine owned the accountability loop on Foundation theme modernization, apologizing for delayed follow-up and committing to prioritize fixes, then listing multiple resolved WCAG/icon issues with a linked PR. (read more, read more)
jordan.vidrine also debugged UI behavior in nested replies, explaining that the layout feels wider because the timeline is removed in nested mode. (read more)
jordan.vidrine reported and fixed a formatting issue in the new “Post Type” composer actions dropdown, where topic links were rendering with stray HTML. (read more, read more)
chapoi clarified that Foundation changes are no longer opt-out on Meta and engaged on accessibility feedback, including linking related sizing work elsewhere. (read more, read more)
chapoi advised on sidebar link nesting limitations (and reacted once the OP found a built-in workaround). (read more, read more)
chapoi also supported a horizon-theme banner question by pointing to Horizon’s compatibility list and the Versatile Banner caveat regarding below-site-header. (read more)
markvanlan explained a product/testing decision in Introducing nested replies: the “view as flat” option was removed after internal evaluation. (read more)
featheredtoast clarified how permissions work for embedding Discourse as a full comment system, emphasizing that membership and topic visibility still gate interaction. (read more)
awesomerobot confirmed that the Events category flow now defaults to event creation by design, while floating the idea of a setting for mixed-use categories. (read more)
awesomerobot also responded on JAWS + shortcuts behavior, explaining current expectations and why better screen-reader announcements during shortcut navigation aren’t trivial. (read more)
pmusaraj reproduced the passkey login regression and flagged it for investigation (including looping in falco). (read more)
HAWK weighed in on the European Discourse meetup thread, framing event support in terms of cost/ROI under current budget constraints. (read more)
HAWK also triaged a UI detail question about the Reply button hover/transition effect, asking which theme was in use and noting Meta Branded/Horizon apply effects broadly. (read more)
sam posted the status of the fix for the Unread count mismatch regression, linking the commit and deployment timing. (read more)
Sign-off: May your passkeys authenticate, your sidebar stay delightfully uncluttered, and your unread badge finally agree with /unread again.
In the last 24 hours:54 new posts and 11 new topics (activity window covered by threads like the spam-signup discussion read more and several fresh bug reports read more).
Top users (posts / likes in the last 24h) (each name links to one of their latest posts for quick context)
one1 described a coordinated wave of spam signups (not posts yet) with telltale patterns in usernames, domains, and random custom-field content; replies compared notes, suggested approval/workflow tweaks, and debated IP blocking tradeoffs (spam attack thread, plus the Data Explorer approach shared in-thread read more).
alehandrof asked how to approximate Meta’s design (sidebar hidden by default, “featured” category blocks, simplified nav, custom sidebar, category descriptions), and got pointed toward the newer custom homepage + Blocks API direction and existing theme components (design request, custom homepage feature read more, Meta branded theme/Blocks API discussion read more, and a “hide sidebar by default” component reference read more).
A “fresh install” troubleshooting thread popped up where uploads/avatars fail after Docker deployment; supermathie immediately narrowed it down by asking which upload storage mode is configured (failed uploads).
nitinkg asked how to prevent extra emails when promoting someone to admin/moderator—while still sending only the admin confirmation message—highlighting complexity around notification/email pipelines in API-managed/hidden communities (email suppression question).
A long-running settings deep-dive continued: how educate_until_posts now behaves after recent changes to check_education_message; chapoi argued the setting copy is now misleading, and Roman agreed the change may have gone too far and promised to revisit the behavior (setting behavior discussion).
#TAGai: thgl reported that AI Helper tag suggestions can recommend tags that are not allowed in the selected category (and even lets you pick them—then blocks submission). zogstrip replied with a fix already in motion via a core PR (bug report).
A new #TAGnested-replies rendering/navigation issue: after hopping through “suggested/related topics” without a page reload, replies from the previous topic can remain rendered inside the next topic until a hard refresh—intermittent, but reproducible after multiple hops (state bug report).
#TAGtopic-timers: a report of 403 errors when setting a publish_to_category topic timer after an update resurfaced, with davidkingham adding that they’re the only admin and category permissions haven’t changed (403 timer issue).
#TAGmobile / pwa / ios: kairo162 posted a screenshot showing “glitchy” date rendering on iOS/PWA, asking for confirmation and a fix (date glitch report).
An earlier issue where the UI showed “Unread (14)” but /unread was empty appears to have cleared up for LarisaHaster (“fixed on my end”), suggesting a transient state/sync problem (unread mismatch thread).
Review Queue ergonomics: sableraph flagged that “Yes/No” meanings vary between items (“Is this spam?” vs “Approve this topic?”), increasing the risk of muscle-memory mistakes. awesomerobot floated reframing prompts so Yes consistently means ‘something is wrong’ (UX feedback).
A smaller UI behavior question: why the Reply post-action button has a background transition effect in some themes; investigation pointed to theme-specific styling differences (Foundation vs Horizon vs Meta Branded) (button transition thread).
Another permissions/UX edge case continued: “New Topic” being visible even when users can’t actually post; the thread received follow-up thanks after options were provided (permissions UX thread).
#Extras
haydenjames shared discourse-health-check, a one-shot bash script for quickly checking Docker + Discourse services, backups, TLS, and basic security checks—prompting quick corrections from staff (“Discourse doesn’t run Puma”; “Pitchfork nowadays!!”) (health check tool).
#Community Building
A practical “feedback board” question: Bryce_Oishi asked how to set up a product/customer feedback channel (intake form, list view, upvoting, search). Replies pointed to Topic Voting and Form Templates as core building blocks (feedback channel thread, Topic Voting plugin read more, Form Templates announcement read more).
#Theme component
Right Sidebar Blocks: a quick configuration win—haydenjames asked how to increase “Top Contributors” from 5 to 10; chapoi suggested the count parameter, which resolved it (Right Sidebar Blocks).
Topic List Previews (TLP) saw multiple community PRs highlighted (tile avatar wrapping, timestamp wrapping, and making blank tile areas clickable) with notes about past Ember duplicate-event pitfalls and how it now behaves (TLP update post).
Discourse Mermaid: after staff encouragement, a community PR landed to improve the theme component (Mermaid thread).
#Integrations
Authentication business reality-check: pHneutre asked whether enabling Microsoft and Meta/Facebook authentication requires payment or subscriptions now, noting outdated docs and dead links in older guides (and also posted an update-needed note on the Facebook how-to) (auth cost question, Microsoft auth reference read more, Facebook login guide needing updates read more).
#Plugin
Calendar and Events: a UX question in French about preventing accidental event creation when users click near an event in the calendar grid (opening the “new event” modal unintentionally) (Calendar plugin thread).
Member Application plugin thread continued (in French) with an idea to validate signups by comparing a user-entered field against a CSV dataset—effectively a lightweight eligibility check at registration time (member application discussion).
awesomerobot engaged on moderation UX, proposing a consistent “problem confirmation” framing for the unified review queue prompts (review queue UX); they also weighed in on spam defenses and noted Meta’s long-running use of blocking tactics without obvious signup collapse (spam signups).
zogstrip acknowledged and rapidly moved a fix forward for AI Helper suggesting disallowed tags, linking to the PR that should resolve it once deployed (AI Helper tag bug and follow-up with PR link read more).
chapoi helped explain how Meta’s look is achieved—pointing to the custom homepage feature and the Blocks API path—and also confirmed a simple parameter-based solution in the Right Sidebar Blocks component thread (Meta-style homepage guidance, plus Right Sidebar Blocks help read more).
Falco provided a quick technical correction on a shared server script: Discourse doesn’t run Puma (helping keep diagnostics accurate) (health-check thread).
pmusaraj clarified that Meta isn’t force-added in the DiscourseHub iOS app, and explained the “stale session → log in again” prompt behavior (and how it relates to the site’s enabled login methods) (DiscourseHub iOS login explanation).
Roman responded to concerns that educate_until_posts may no longer match its wording/intent after recent logic changes, and committed to re-evaluating for a better middle ground (educate_until_posts follow-up).
HAWK chimed in on a subtle UI animation question (reply-button background transition), helping confirm what’s being observed visually across themes (reply button transition).
supermathie started triage on a “failed avatar/photos upload” report by narrowing scope to upload storage configuration—an important first fork in diagnosing local vs external storage issues (uploads failing).
Yesterday’s Meta was a mix of bots getting tangled in custom fields and humans shipping fixes at warp speed—may your review queue buttons always mean what your muscle memory thinks they mean.
A lot of the day’s momentum clustered around UX papercuts and operational debugging—from Sidekiq latency checks for webhooks (read more) to nested navigation state leaking between topics in Horizon (read more).
Also active / worth skimming from the same window:
A practical server auditing script got an improvement suggestion around backup “offsite-ness” detection in #Extras (read more).
Ongoing discussion about #Community Building tagging strategies for multi-version announcements (read more).
Self-hosters compared provider performance (Vultr HF vs DO) (read more) and SEO/H1 needs for category pages (read more).
A request for “Meta-like” homepage category featuring continued in Support (read more).
Tealk reported confusion where profiles appeared “silenced” publicly but not in the admin panel; awesomerobot clarified the UI shows historical silences, and that automatic silences can be lifted when a flag is rejected (read more, and the resolution at read more).
A webhook that used to fire instantly started arriving ~24 minutes late; chapoi pointed to Sidekiq queue latency (especially low) as the first place to investigate when many webhooks / emails are in play (read more).
Spam/abuse mitigation continued to be debated, including the tradeoffs of cracking down on VPNs; the thread also pointed to Cloudflare WAF/log explorer workflows as a pragmatic path (read more, plus Cloudflare rule tips at read more).
A “POP3 authentication error” warning surfaced despite mail seeming to work; the report references an earlier canonical thread and highlights a slightly unusual forwarding setup (support@ → Gmail polling) that may complicate diagnosis (read more, background: read more).
In nested-replies, Andry_Osminin described a Horizon-only bug where posts from the previously viewed topic remain rendered after in-app navigation; the investigation focused on “instant navigation” not resetting state, and markvanlan indicated a fix was incoming via a broader mobile nested-view PR (read more, fix note: read more).
Passkey login reports (“security key is not owned by the user”) saw follow-up testing: pmusaraj couldn’t reproduce reliably and suspects inconsistent client/platform behavior (possibly Windows passkey implementation changes) rather than a stable Discourse-side repro (read more).
A bug report on Gmail “dot variant” addresses causing incoming email handler failures (“Primary email has already been taken”) got a staff reply acknowledging it likely is a bug; the thread also mentions the normalize_emails setting tradeoffs while awaiting a deeper code look (read more).
Theme import/update UX tripped up admins: the “branch: main” field is a placeholder, so leaving it blank sets nil (often selecting d-compat/...) rather than main; the thread suggests clearer copy and/or different defaults depending on intended behavior (read more, staff triage prompt: read more).
Long personal message titles can overflow and be covered by composer buttons on mobile; chapoi noted the issue may be obsoleted by the newer composer actions UI and still considered a quickfix in the interim (read more, related change: read more).
A “dates glitching” regression on mobile/PWA/iOS was acknowledged as recent and under active investigation, with an expectation of a near-term fix (read more).
Review queue actions were called out as semantically inconsistent (“Approved/Rejected” meaning flips depending on item type), with users advocating for clearer confirmation flows and more consistent “Yes/No” semantics (read more).
#Translations
Translators couldn’t find the Arabic string for the “All” reactions filter; zogstrip identified the key as discourse_reactions.users_popup.all, helping narrow where to look in Crowdin (read more).
#Feature
A request for the AI title generator asked for separate toggles for title vs tags vs category (to encourage user-written titles while still enabling AI categorization); the report also notes a workaround that triggers a 500 when “titling agent” is set to None (read more).
“Accept paste input during installation” continued: the latest reply reiterates that workarounds exist but a first-class solution would still be preferable (read more).
#Plugin
In the long-running Discourse Topic Voting thread (officialtopic-votingincluded-in-core), martin asked for concrete examples after a report that removing the “Ideas” category type unexpectedly removed voting where it was previously enabled, and suggested using Category.can_vote?(cat.id) to validate behavior (read more).
chapoi spent time triaging multiple UX/support threads:
Confirmed the PM composer overflow issue and tied it to the new composer actions rollout (read more, related: read more).
Gave a concrete debugging path for delayed webhooks by pointing admins to Sidekiq queue latency and what to inspect (low queue, Busy tab) (read more).
Acknowledged a dates display regression and indicated a fix was in progress (read more).
Helped clarify the intended semantics around theme-import branch selection and looped in engineering for admin-side triage (read more).
Investigated a Horizon nested-navigation rendering bug and coordinated with engineering for visibility (read more).
markvanlan followed up on the Horizon nested-topic navigation bug and indicated a fix would land via an upcoming PR that significantly adjusts the mobile nested view (read more).
awesomerobot helped resolve the “silenced” profile confusion by explaining it reflects historical silences, and that auto-silences can be lifted when review outcomes reverse the triggering flag (read more, solution: read more). They also contributed admin-email troubleshooting advice about disable_emails behavior and bypassed system mail types (read more), and weighed in on abuse mitigation tradeoffs around VPN traffic (read more).
zogstrip supported translators by identifying the correct reactions string key to search for in Crowdin (read more), and debugged missing user-card actions by recommending safe mode and narrowing the issue to theme/plugin customization (read more).
pmusaraj investigated a passkey login error report, shared difficulty reproducing reliably, and suggested the root may be platform-level changes (notably Windows) rather than a consistent Discourse regression (read more).
martin engaged in plugin support for Topic Voting, asking clarifying questions about category-type changes affecting vote eligibility and offering a rails-console check to validate expected behavior (read more).
That’s it for today—may your nested replies stay in their own topic, your webhooks sprint out of Sidekiq, and your “silenced” banners remain purely historical!
Spam defense talk continued as Lee_Ars recommended the official Discourse hCaptcha plugin, while also pointing to the ongoing desire for Turnstile support (read more) and the plugin itself (read more).
one1 asked how to trigger “After user update” automations from one required field while optionally including other profile/custom fields; awesomerobot suggested mustache-style conditional blocks to only render filled fields (read more). Background reading included Using the new user update automation and a related limitation discussion (read more).
In ai / ai-helper support, Frully wanted better control over AI tag/category suggestions, and Falco clarified that tag/category suggestions don’t use LLMs—they’re based on embeddings against existing topics (read more).
A self-host install hit a confusing setup error: “Port 443… does not appear to be accessible” even after earlier checks passed. darkpixlz suggested bypassing the script’s connection test using --skip-connection-test, which unblocked the install (read more), and linked to a prior report of the same behavior (read more).
A question came up about when the improved Foundation theme changes will roll out broadly; a workaround was shared: admins can enable the “Modernize foundation theme” upcoming change manually (read more). (See also the Foundation theme thread for more background: read more.)
Maxine reported that after a restore/migration, uploads and avatars had URLs rewritten away from S3—raising concerns about how to prevent this in production migrations (read more).
awesomerobot walked through the reality of Microsoft and Facebook authentication setup: it may require free accounts, app registration, and (for some paths) credit cards or business verification steps—but not necessarily payment (read more).
#Feature
A feature request asked for an AI title generator toggle to selectively enable/disable title/tag/category suggestions; NateDhaliwal proposed a pragmatic CSS workaround to hide the UI button where needed (read more).
The long-running request to group groups on the /groups page resurfaced; awesomerobot noted there’s still room for discussion, but it’s not currently prioritized (read more).
#Self-hosting
Willy asked why plugins copied into /var/discourse/plugins don’t install in production the way they expect; guidance leaned toward using a dev environment or app.yml, plus how to work with private repos safely (read more). Helpful reference: Install plugins on a self-hosted site and backup/restore guidance for local testing (read more).
A site owner asked for a browser/OS support reference for the upcoming Discourse 2026.6.0 line; NateDhaliwal pointed to official support guidance and suggested the older-browser-friendly “Dumbcourse” UI as an option (read more) and (read more).
A mobile UX suggestion proposed letting users close the reactions list by dragging down from within the list, rather than requiring a reach to the empty area above (read more).
A UX papercut around theme import “branch” input was closed out; chapoi confirmed the fix landed and linked the completion (read more).
#Theme component
In a sidebar customization thread, tobiaseigen documented that sidebar section names are slug-sensitive (including tricky trailing spaces), and Lilly updated the component guidance to make the slug requirement more obvious (read more). Related component mentioned: Discourse Group Sidebar Menus.
pmusaraj shipped a new theme announcement, sharing preview, repo, and setup pointers for Accent Theme (read more).
awesomerobot helped shape a practical pattern for Discourse Automation templating—using conditional blocks to include optional profile/custom fields only when present (read more, and the follow-up explanation read more). They also reported real-world friction points in third-party auth setup while confirming it doesn’t necessarily require payment (read more), and clarified feature-priority status on hierarchical grouping of groups (read more).
Falco clarified that tag/category suggestions in the AI helper flow are not LLM-driven, but embedding-based against existing site content—important context for anyone trying to “prompt” those outputs (read more).
chapoi gave direct self-hosting guidance on plugin installation realities (local-folder installs “just don’t work” the way people expect in production), recommending dev/local restore workflows instead (read more) and pointing to official plugin-install docs for private repos (read more). They also confirmed a UX improvement was completed for theme import branch handling (read more).
nat briefly noted that improvements are coming soon for a onebox localization issue, signaling active work on the problem (read more).
Yesterday’s vibe: may your ports stay open, your sidebar slugs never include trailing spaces, and your accents remain tasteful—whether they’re theme colors or the way you say “automation.”
typed-sigterm — 1 post / 2 likes (contextualized WeChat “mini program” expectations and browser realities: read more)
Andro — 1 post / 2 likes (raised a serious regression report around experimental nested replies: read more)
RGJ — 1 post / 2 likes (defended the long-running migrated password hash approach: read more)
Arkshine — 1 post / 2 likes (posted a major modernization PR for the image comparison slider TC: read more)
Idoru_Toei — 1 post / 1 like (confirmed a self-hosting “port 443” resolution + shared a runbook: read more)
Interesting Topics
#Site feedback
stephtara noticed a strange combo where a reply was flagged as originally written in French (despite being English) and where edits seemed “missing” unless viewing the correct (non-translation) version; Moin explained AI locale detection can be tripped by keywords and that viewing the “English translation” can make edits look outdated until translation refreshes (issue report, analysis + workaround).
In an ongoing Cloudflare R2 migration thread, David_Ghost reported older uploads still resolve to the bucket endpoint URL (and thumbnails break unless a theme component is enabled), while Lilly recommended running migration + rebake tasks and ensuring DISCOURSE_S3_CDN_URL (or the “S3 CDN URL” setting) is set before migrating—and also suggested discourse remap for string replacement when needed (problem details, steps + ordering guidance).
A separate composer complaint (in French) resurfaced around “smart punctuation” behavior: apostrophe replacement is especially painful for French writing, prompting people to disable the setting even if they’ll miss emdash replacement (latest report, related locale/translation confusion elsewhere).
Admin-side topic editing started failing for stephtara; early troubleshooting focused on checking the browser console and site logs, and narrowing down by disabling problematic plugins (notably “Discourse Custom Wizard”) to see if edits succeed again (initial error report, first debugging steps).
A mobile Safari regression on iOS 26.5 was reported where the new topic composer editor becomes too small/crushed, while replies still appear usable; the report notes it reproduces on try.discourse.org and includes UA/device context for debugging (screenshots + environment, reference capture).
Experimental nested replies was described as a “can’t-revert” disaster: enabling it allegedly led to confusing UI for users, “disappearing” posts, then error pages when attempting to disable—leaving the site in a broken state and prompting requests for rollback/debug steps (problem statement, read more).
In Discourse Automation, one1 successfully templated one profile field via {{languages}} but found other custom/required fields didn’t resolve—raising the question of how field names map to automation variables and whether a code fix is needed to avoid renaming fields (working vs failing variables, read more).
A solved self-hosting setup thread turned into a practical “runbook” for Virtualmin/Webmin users: pfaffman emphasized not installing Postgres manually and suspected port exposure conflicts, while Idoru_Toei ultimately got things running (using --skip-connection-test) and documented cleanup + install steps for subdomain setups (diagnosis, solution + runbook).
“New Topic” button visibility continues to be a pain point in read-only / restricted categories; Moin pointed to a merged core change introducing a hidden setting hide_disabled_create_topic_button to restore older behavior by hiding the button when the user lacks create permissions (context + pointer, read more).
#Self-hosting
A Russian-language SEO question about adding an H1 on the homepage prompted pfaffman to remind that crawlers see a different (server-rendered) view than users do in the JS app, and that Discourse already handles SEO well—encouraging clarity on the actual SEO goal before changing templates (SEO caution, read more).
#Site Management
Auto-bump tuning got a feature suggestion: instead of bumping based purely on category selection, patrickemin proposed incorporating “interest” signals (views/votes) and topic age thresholds—while also referencing a related desire to avoid repetitive auto-bump alert noise (feature suggestion, related alert-noise discussion).
#Theme component
The image comparison slider theme component saw a big modernization update proposal: Arkshine shared a PR adding zoom/pan, fullscreen, lightbox originals, better handles/labels, keyboard accessibility, group-based insertion controls, and RTE editing—while keeping backward compatibility via a new [wrap] format (and noting 2026.6.0-latest is required) (feature rundown, read more).
#Theme
On the long-running FKB Pro – Social theme thread, xlg256 reported inconsistent “clickable areas” on mobile topic cards causing confusing hit-or-miss taps and accidental navigations; they proposed restricting click targets to core content and shared a CSS pointer-events “whitelist” approach as an interim fix (UX problem + suggestion, read more).
A WeChat mini program integration discussion revisited whether embedding Discourse inside an app-like container is worth it; participants highlighted WeChat constraints (openid/token needs, audits/content review), the friction of requiring email, and the cultural reality that many users expect “mini programs” over standalone browsers—especially given outdated Chromium forks common on devices (integration discussion, China browser context).
The thread also pointed back to earlier WeChat-login/plugin caveats, especially around WeChat not exposing email (related topic, read more).
#Migration
A PHPBB migration optimization thread briefly detoured into password handling: pfaffman recommended the long-established “migrated password hashes” approach for self-hosters, and RGJ pushed back on blanket security concerns—arguing the plugin has a long track record when insecure password allowances are disabled (plugin mention, security clarification).
No posts from the @team group were recorded in the last 24 hours within the captured threads for this digest. For reference, the newest/most-active topics during the window included:
bug Cloudflare R2 old upload URL/thumbnail issues: read more
If yesterday taught us anything, it’s this: may your port 443 stay reachable, your thumbnails rebake on the first try, and your AI stop insisting everything is written in French.
ばこん wondered how Discourse can sustainably offer a free hosted tier, with merefield framing it as a conversion funnel and HAWK clarifying it’s a freemium acquisition tier that often functions like an “indefinite free trial” (read more).
ice.d asked what the practical point of setting a user’s primary group is; itsbhanusharma highlighted flair precedence, while HAWK listed key behaviors like default titles, styling, and avatar flair (read more).
Tobias1 reported the AI Tools “test runner” appearing to negotiate SSL even when targeting an internal http:// endpoint, producing an SSL_connect ... wrong version number error despite “Allowed internal hosts” being set (read more).
In a continuing spam-defense discussion, mcdanlj argued for an option to block email without blocking IP when deleting spam accounts—calling IP blocking a “hidden cost”—and Ed_S agreed while comparing moderation workflows like approving new users and checking StopForumSpam (read more).
haydenjames followed up on switching to the Foundation theme—echoing that it’s “much easier on the eyes”—in the solved thread about rollout timing (read more).
A Right Sidebar Blocks regression: xlg256 reported the “Tags” right-sidebar block consuming tag data on initial load, leaving the native top-header tag dropdown blank until the block is removed (read more).
Andry_Osminin described an in-app navigation issue where posts from a previously viewed topic remain rendered when navigating into the next topic, and referenced a draft fix (“nested post registration teardown”) while offering to test (read more).
On the experimental nested replies front, markvanlan asked for screenshots to diagnose a severe “can’t revert” scenario after disabling the feature, with HAWK noting weekend timing might slow responses (read more).
Lilly connected a Cloudflare R2 image URL display problem to an in-flight fix, pointing people at a related discussion/PR trail for chat thumbnail URL handling (read more) and the referenced thread on chat thumbnails/CDN bypass (read more).
#feature
Tyson_Jacobs requested that /raw/... output include reply-relationship notation (which post a post is replying to), and NateDhaliwal suggested using JSON where reply_to_post_number is available (read more).
#self-hosting
stephtara asked how to give Claude Code read-only access to a self-hosted instance (SSH + DB) while preventing access to sensitive/security data, and whether SQL dumps contain sensitive material (read more).
#plugin
In the official Calendar/Event plugin thread, Lou asked for location lookup + clickable map behavior (Google Calendar / Facebook-style), and nathank pointed to the Locations plugin as an existing solution—though currently integrated with the alternative Events plugin, not the official one (read more; also see read more and read more).
Hasimir reported a breaking change causing discourse-custom-wizard to crash during boot with undefined method 'admin_stylesheets' for class DiscoursePluginRegistry, noting even /safe-mode fails because initialization middleware registration crashes early (read more).
#theme
In the Air Theme thread, stephtara flagged a Safari-only issue that breaks editing after adding a tag, and linked it to a deeper troubleshooting write-up—suggesting the failure disappears in safe mode or with a different theme (read more; debugging details: read more).
#announcements
Boosts on Meta were disabled for now: martin acknowledged feedback and said the team will figure out next steps before re-enabling (read more).
A small UX delight moment: haydenjames noticed the forum UI “feels MUCH better” with subtle font/layout changes while following the “Modernizing the Foundation theme” effort (read more).
In the “Granular group-based permissions” announcement, Moin dug into how theme components should treat pseudo-groups (and referenced their own component for context), asking whether separate checks are still required for “everyone”-style groups (read more; also referenced: read more).
Bonus cross-link: Primary groups were also cited as a way to tailor experiences (e.g., customized homepages) via the Discourse Category Home plugin (read more), referenced from the primary-group discussion (read more).
HAWK clarified Discourse’s freemium positioning—that the free plan is an acquisition tier often acting like an indefinite trial—adding business context to the community question in “Why are you able to offer a free plan?”.
HAWK answered what primary groups do in practice (styling hooks, default titles, avatar flair, and identifying affiliation) in “What is the point in primary’s”, reinforcing the original question from the opener.
HAWK acknowledged weekend timing in the experimental nested replies support thread, helping set expectations while the issue is investigated in “Nested replies experimental feature buggy”.
martin confirmed Boosts were turned off on Meta temporarily while the team evaluates next steps in “Testing Boosts on Meta”.
With Boosts taking a breather and nested replies keeping folks on their toes, here’s hoping tomorrow’s Meta brings fewer “wrong version number” surprises and more smooth scrolling.
Boosts aren’t gone forever (just not “seamless” yet): after community feedback on the Boosts experiment, martin confirmed they’ll return eventually, but the team can’t give the combined “boosts/likes/reactions” experience the attention it deserves right now (read more).
Related: the ongoing discussion around the experiment lives in Testing Boosts on Meta.
Unified “New” view is heading toward being the default: a new announcement lays out how /new will become a unified view with Topics / Replies / All subtabs—intended to make “new vs unread” easier to explain to newcomers (read more).
Context: it builds on earlier rollout notes in the new new has been enabled on meta and ties into admin controls via Upcoming changes.
“Me too / experiencing this issue” got more configurable:lindsey shared improvements to the solved-issue UX, including a category-specific setting and a configurable label directly in category settings (read more).
Right sidebar Tags block conflicts with other tag dropdowns: a repro was confirmed and a fix PR was linked by martin, targeting the conflicting dropdown behavior in the right-sidebar blocks component (read more).
Original report thread: Tags block is conflicting with other tag dropdowns.
Directory search regression for user custom fields:pfaffman reported that /u directory search appears to ignore user custom fields, even though global search finds them—suggesting a regression in directory filtering behavior (read more).
Survey plugin min/max wasn’t enforced:awesomerobot confirmed the issue and opened a PR to make survey min/max work and validate submissions (read more).
Topic navigation rendering glitch (nested replies carry-over): a fix was merged as part of a larger mobile refactor, but the reporter noted the carry-over still reproduces after updating—so investigation continues (read more).
Automation “3 errors recently” link points to the wrong log search: a bug report notes the dashboard link used search=discourse-automation even when the underlying error didn’t contain that string, resulting in a blank logs view (read more).
Tag info button appears but does nothing in a plugin context:Moin found a “circle-info” icon that looked like tag info but didn’t function; awesomerobot linked a PR to hide the button when required tag data isn’t available (read more).
Language UI mismatch edge case (interface vs translated content):Moin documented a reproducible mismatch where the header language and UI stayed English, but topic titles/tags/excerpts partially switched to German after changing language in a separate tab (read more).
Theme import “branch” field was misleading:david opened a PR to show the actually installed branch and resolved update target branch in the theme UI—reducing “why did it pull d-compat?” confusion (read more).
iOS Safari composer is too small (iOS 26.5):awesomerobot suggested hiding the toolbar for breathing room, and the discussion explored options like collapsing fields or moving icons; there’s also renewed interest in a mobile fullscreen composer approach (read more).
Deep background + component trail: Such a tiny window to edit here on a cell phone.
S3 restores rewriting image URLs / missing bucket links: after a restore, uploads didn’t have the expected bucket URLs; the thread dug into where S3 config must live (env/app.yml vs site settings), plus a workaround using SQL-only backups (read more).
Reference guide: Configure an S3-compatible object storage provider for uploads.
AI Tools “Test Runner” forces SSL for http URLs on non-80 ports:Falco clarified the current behavior—only HTTP on port 80 is supported; other ports default to HTTPS (marked solved) (read more).
Using an LLM to refactor a Flarum importer (and then a bootstrap failure):AkarinLiu shared a refactored script via Gist, then followed up with a Discourse install/bootstrap error (bundle install ... exit 15) while deploying (read more).
#Feature
Event location map support request: a proposal to add Google/FB-calendar-like location lookup so event locations can be picked more easily and clicked to open in map apps—especially useful for migrations from Facebook groups (read more).
Related context in the ecosystem: Discourse Calendar and Events, plus references to the older Locations plugin and the alternative Events plugin.
#Enterprise
Where should “Community” sit in an enterprise org chart?:HAWK opened a discussion about reporting lines (Support vs Marketing vs Product vs autonomous community org), aiming to compare models and outcomes across larger orgs (read more).
Reassured folks that Boosts will likely return once there’s time to integrate the concept properly into a unified boost/like/reaction experience (Testing Boosts on Meta).
Investigated iOS Safari composer constraints and suggested immediate mitigation (hide toolbar) while considering a better guaranteed typing area (New Topic Editor Too Small iOS 26.5 Safari Web).
Clarified why automation templates break with special characters in custom field names and suggested Discourse should strip them for automation-safe variables (After user update automation…).
Opened a UI improvement PR so admins can see the installed theme branch and the resolved update branch (helping avoid “why did it pull from d-compat?” surprises) (Misleading “branch” input in theme import).
Reported progress and merged work toward a mobile UX refactor, while the reporter confirmed the core rendering carry-over still happens post-update (so more follow-up is needed) (Posts from the topic I just left stay rendered…).
Suggested tuning nested replies behavior via site settings (Nested replies max depth + capping depth) to achieve a “collapsed” style thread presentation (Introducing nested replies).
Engaged with a contribution around migrating from Flarum and asked for more details about the importer use case (利用 AI LLM 重构 Flarum 导入脚本以迁移至 Discourse).
That’s a wrap: between nostalgia for Boosts, a brand-new unified “New” tab, and more deep dives into nested replies, Meta spent the day organizing conversations—both socially and literally into threads.
lindsey shared an early look at a highly experimental admin dashboard redesign, aiming to make community “health and value” more legible at a glance; commenters immediately asked for more modular KPIs and customizable group breakdowns in the new “Highlights/Engagement” areas — read more
The new unified “New” view sparked a mini therapy session about New vs Unread vs Unseen; chapoi teased that you “don’t need to [understand it] anymore,” while awesomerobot clarified the default semantics and why the combined UI should reduce cognitive overhead — read more
Ongoing nested replies polish: CedricS reported that moderated replies lose the helpful “greyed” appearance for staff, and also flagged a composer formatting-bar visibility issue when replying; markvanlan followed up with a fix PR for the moderated styling — read more
A deep dive into why /u?exclude_groups=admins behaves differently when logged out: haydenjames wanted admins excluded from “top contributors,” while david explained the intentional privacy model (preventing group-membership inference) unless group/member visibility allows it; the thread ends with a CSS-based workaround and a clarified “solution” — read more
Event UX question: MeganBowers asked whether event reminders can be emailed (vs. only in-app notifications), and nathank noted this likely depends on user notification/email settings—highlighting an opportunity for clearer “full notification” behavior for events — read more
Embeds in practice: AkarinLiu tried to whitelist player.bilibili.com for iframe embeds, but ultimately found that simply pasting the link (vs iframe code) was the path to success; the thread points to the Bilibili Onebox plugin as a pragmatic option — read more
Boot failures with a geographic twist: in a “Discourse does not start up” support thread, singi2016cn suggested China-based rebuild failures may be network-related (gem downloads) and potentially worsened by temporary filtering, recommending waiting or using a proxy — read more
Badge rendering bug (SVG): AkarinLiu reported SVG badge images not displaying, and awesomerobot identified a root cause (Font Awesome SVGs lacking explicit dimensions, causing width: 100% to compute as 0); a core fix was queued to avoid the “0-width” trap — read more
Search regression / inconsistency: in a “Trouble searching user custom fields” report, zogstrip couldn’t find the original regression point but shipped a fix to make both code paths consistent (via PR) — read more
Composer focus hiccup: a long-running issue where inserting a horizontal rule steals focus from the emoji picker got a resolution update, with renato confirming the fix was merged and thanking the reporter/contributor — read more
Plugin bug with big sites: enabling Discourse Gamification led to /leaderboard returning 404 with MissingAttributeError (missing attribute 'admin' for User); glob-canard.4x traced it to an overly narrow SELECT list and demonstrated that including users.admin/users.moderator resolves the crash — read more
PDF previews regression: nathank reported that clicking a PDF link (when PDF preview is active) now triggers a download instead of opening a new tab—despite earlier centralised “inline vs download” logic meant to standardize this behavior — read more
CI debugging in the weeds: elmuerte continued investigating why GitHub Actions fails the “Check SKIP_DB_AND_REDIS bootability” step, and david proposed targeted runner invocations (dev/test mode) to reproduce plugin-loading behavior and isolate what’s actually getting loaded locally vs CI — read more
Theme regression report: in Horizon, the sidebar button text in an events category reverts to “New Topic” instead of “New Event” when the sidebar is open (functionality still creates an event, so it’s cosmetic but confusing) — read more
lindsey drove discussion on the experimental admin dashboard redesign, inviting feedback on which KPIs/admin datapoints would be most valuable in the modular layout — read more and follow-up question — read more
nat kept the admin-dashboard thread light while still confirming “custom KPIs” are on the horizon (eventually), replying in classic GIF shorthand — read more and later — read more
chapoi helped shape the narrative around the unified new view (“New vs Unread vs …”) and guided a user toward verifying they were on the latest version — read more and read more
awesomerobot clarified default definitions for New/Unread/Unseen to reduce confusion with the new UI — read more — and separately identified the root cause + fix path for SVG badge icons not rendering — read more
david weighed in on the privacy/security model behind exclude_groups behavior in the user directory, then pivoted to debugging by confirming which group visibility settings are required for exclusion to work — read more and read more
HAWK engaged in the #Enterprise conversation on community ownership models, focusing on conflict-of-interest boundaries when community sits inside Marketing and how to handle cross-department stakeholder pressure — read more
markvanlan continued the steady march of nested replies polish, linking a PR to restore the greyed styling for moderated replies for staff — read more — and also iterated on a fix for “posts from the previous topic stay rendered after in-app navigation” — read more
zogstrip shipped a fix for searching user custom fields, aiming for consistent behavior across code paths — read more
renato confirmed a fix was merged for the composer issue where a horizontal rule could steal focus from the emoji picker — read more
jordan.vidrine pointed to a fix PR for a reported “homepage font got very small after rebuild” issue — read more
That’s a wrap: today’s Meta energy was equal parts dashboard dreams, list-view clarity, and the timeless belief that most product debates can be settled with the right animated GIF.