Biggest headline: Discourse shared an early look at fully #Announcements nested replies—a major shift from the traditional flat timeline model. See the announcement: read more
Interesting Topics
#Announcements
Nested replies are moving from experiment to core direction.markvanlan introduced the “fully nested reply view” and described how linked-post navigation can switch into a single-thread view for clarity (read more); early excitement rolled in quickly (including practical “can’t-wait-to-try-it” deployment plans) (read more)
Permissions clarity: splitting the historical @everyone pseudogroup into anonymous and logged_in_users.martin detailed why @everyone has become ambiguous and how the upcoming change granular_anonymous_and_logged_in_groups_permissions aims to make site settings, category permissions, and tag groups less confusing (read more)
Reporting UI refinement landed: “Specific groups” is becoming clearer and more consistent. In the ongoing Admin Reporting improvements thread, martin noted a merged change that narrows the reporting access options down to clearer choices (No one / Staff / Specific groups), with an illustrative screenshot of the new UI (read more); background context in the same feature line is in the main topic (read more)
#Self-hosting
Renaming categories (and slugs) without breaking anything: The thread confirms the category ID is what matters for routing, not the slug. putty explained how even “wrong” slugs redirect correctly as long as the ID matches (read more), and Lilly added that you can safely change slugs too (topic links don’t depend on them) (read more); original question and rollout concerns are here (read more)
Redirecting users away from missing pages (404s): A self-hosting admin asked how to send visitors somewhere useful when they hit “page does not exist” errors (read more), and merefield pointed to a proven approach for redirecting all 404s to home (with a direct reference to an earlier how-to) (read more; plus the referenced how-to: read more)
Self-hosted Discourse AI sentiment setup hit a HuggingFace 404—workaround provided. A self-hoster reported failing pulls for cardiffnlp/twitter-roberta-base-sentiment-latest during container startup (read more); Falco explained the upstream model change hadn’t merged and recommended pointing to a specific branch (including an updated command) (read more), which resolved the issue for the reporter (read more)
“找不到请求的 url 或资源” when jumping to a reply then editing/saving (Chinese report) gained traction. The report outlines a reproducible path (expand replies → jump to post → edit → save) leading to a “URL/resource not found” error (read more); chapoi confirmed and shared console clues (read more), and zogstrip reported a fix in progress after reproducing locally (read more). A near-identical duplicate report also appeared (read more)
Grid Lightbox browsing order is wrong (1,3,2,4) when arrowing through images.Shauny demonstrated that grid uploads don’t navigate in upload order when using keyboard arrows in the lightbox (read more)
Monthly recurring automations may be using weekday-based rules instead of calendar days. In the Automation thread, Lilly traced behavior to how recurrence rules are generated and suggested the logic may be injecting weekday alignment (e.g., BYDAY) where a fixed date (BYMONTHDAY) is expected (read more); zogstrip then pulled in an additional set of eyes for review (read more)
OpenID Connect group sync risk: users can be removed from “unsynced” groups.pmusaraj noted the fix is being backported and should land in minor releases, reducing rollout risk for sites relying on OIDC mapping behaviors (read more; original issue context: read more)
iOS PWA push subscriptions can silently fail when the Service Worker doesn’t control the app immediately. In the PWA push-notification thread, the contributor updated their PR to ensure the Service Worker takes control right away, and invited early review/testing across deployment setups (read more; prior note on upcoming PR changes: read more)
Admin API /admin/users/list/active.json intermittently 500s due to main_user_record[:silenced_till] nil access. The report includes stack trace details and notes it started after upgrading to v3.5.2 (read more); zogstrip suggested the bug was already fixed upstream and pointed to updating to a newer version as likely resolution (read more)
Embedding Discourse inside Salesforce Experience Cloud via iframe: cookie and domain constraints.Falco outlined practical options—either align under the same base domain or adjust same_site_cookies (via hidden site settings) to enable the cross-site iframe scenario (read more; topic background: read more)
AI settings UI nit: changing the default LLM doesn’t update agent labels until a reload.RBoy reported that agents using the “default LLM” don’t immediately reflect the new selection in the UI until the page is refreshed (read more)
markvanlan published the main announcement introducing Discourse’s evolving nested replies direction, including the rationale for when nested structures beat a flat timeline and how single-thread views work when linking directly to a post (read more)
martin shipped two notable updates: a new permissions model that distinguishes anonymous vs logged_in_users to replace confusing uses of @everyone (read more), and a merged tweak making Admin Reporting access options clearer in the “Reporting & Analysis” improvements line (read more)
Falco unblocked a self-hosted Discourse AI sentiment deployment by recommending a working model branch after upstream HuggingFace assets returned 404s (read more), and also provided concrete guidance for embedding Discourse into Salesforce Experience Cloud (domain alignment vs same_site_cookies) (read more)
zogstrip helped drive bug triage and next steps across multiple threads: confirming a repro and noting a fix in progress for the Chinese “URL/resource not found” editing flow (read more), pointing out that a reported API 500 issue was fixed upstream in newer Discourse versions (read more), and nudging review for a suspected bug in monthly recurring automations (read more)
pmusaraj reported that the OpenID Connect group-sync regression is actively being backported and should land in minor releases soon (read more)
sam followed up on an AI configuration bug report by checking whether the Gemini Pro “thinking budget” issue still reproduces for the reporter (read more)
chapoi confirmed the Chinese-language bug report and shared relevant console output as part of the investigation trail (read more)
Nested replies are on the horizon—so today’s challenge is to keep your threads tidy and your lightbox arrows in order.
Quick link rollup (other threads with fresh replies worth bookmarking):
Community growth strategy continued in Enterprise discussions on breaking points and scaling too late vs too early.
A long-running theme thread flagged a pattern issue in Graceful (read more) and Air Theme shipped fixes (read more).
There were also ongoing bug/support follow-ups on mobile Assign issues (read more), calendar behavior (read more), custom-field sanitization (read more), and an ESR/API compatibility question (read more).
Prior announcements and guides referenced frequently included support-category setup with solved (read more), post voting UX comparisons (read more), and the theme install guide (read more).
Email troubleshooting also came up again, linking back to the classic checklist (read more).
Interesting Topics
#Announcements
lindsey announced solved improvements: a new “Me too” button for unsolved topics in support categories so affected members can opt-in for a notification when a solution is marked, and communities can better gauge impact (read more).
The ongoing rollout of nested replies drew practical admin questions (bulk toggling, reversibility, and UX clarity), with implementation details and testing guidance discussed as the feature lands (read more).
A regression meant regular users couldn’t see who the group owners are; awesomerobot confirmed it was unintentionally dropped during a prior table refactor and moved quickly with a fix path (read more).
Lightbox + grid layouts were showing images in the wrong order, and zogstrip traced and fixed the issue after a tricky debugging session (read more).
A composer validation edge case surfaced where uppercase letters in an AI agent username can break the “reachable mention” warning logic; zogstrip linked it to earlier mention-related changes and opened a fix (read more).
Locale detection for Norwegian was misaligned (no vs nb_NO/nb-NO), causing unnecessary translation credit usage and subtle diffs; nat acknowledged the report and suggested a prompt-level mitigation while a core adjustment is considered (read more).
Content localization users reported titles translating while post bodies didn’t; nat explained a translation length limit was likely at play and noted it resolved after adjusting/processing (read more).
A fresh self-host install sent test email successfully but not the initial activation email; debugging focused on verifying EmailLog records and isolating where delivery/sending diverged (read more).
A signup UX question: Discourse can prefill email= in /signup, but can it also prefill username=? The thread confirms the gap and explores whether it needs a plugin-level solution (read more).
API posting via a container + reverse proxy produced Redis mutex warnings (“held for too long”); analysis suggested it’s tied to post-creation work under a short-lived lock (often performance/plugin related) rather than proxying itself (read more).
The new discourse-patch-triage bot workflow prompted questions about how to collaborate from forks; constraints were clarified (no bot commits to forks, but reviews/suggestions still work) and improvements to bot messaging were made (read more).
A potential plugin name clash is brewing: a core PR using the name “Workflow” may collide with an existing plugin called Discourse Workflow, raising discoverability and admin confusion concerns (read more).
#Site Management
Admins digging into sidebar defaults learned the “backfill” behavior is delta-based (preserving user preference) rather than a hard reset; fzngagan documented what gets added/removed and why (read more).
#Feature
A moderation UX idea proposed multi-select flagging (select several posts, flag once, then handle as a grouped review item) to reduce repetitive flag actions in spammy threads (read more).
lindsey introduced the new solved support UX with a “Me too” opt-in flow and invited ideas for admin-facing reporting/visibility enhancements (read more, read more).
dax clarified rollout status (“not enabled on Meta”), enabled testing elsewhere, and provided on-the-ground troubleshooting updates during setup (read more, read more).
awesomerobot helped distinguish “Me too” from Boost (separate mechanisms and notification behavior) (read more), confirmed a group-owner display regression and moved it toward a fix (read more), and pushed UX polish around AI model defaults (read more).
markvanlan continued to unpack how nested replies behaves at scale (bulk toggling, historical-topic conversion risk, and reversibility), while steering testing toward dedicated spaces (read more, read more, read more).
zogstrip landed fixes and follow-ups for tricky regressions—lightbox ordering in grid layouts (read more) and mention validation edge cases affecting AI-agent handles (read more).
nat acknowledged and guided mitigation for Norwegian locale detection mismatches impacting translation behavior (read more) and explained why content localization may translate titles but skip long posts, with a path to resolution (read more).
chapoi delivered a quick, concrete solution for hiding user cards from anonymous visitors via a site setting pointer in a solved support thread (read more).
isaac clarified how to properly interact with @patch-triage, what it can/can’t do on forks, and noted internal follow-up on improving fork support (read more, read more).
fzngagan documented nuanced sidebar backfill semantics (why it’s incremental, and how to achieve uniformity without clobbering user preferences) (read more).
HAWK kept the Enterprise thread on community-scale pain points moving, focusing discussion on moderation consistency, process design, and governance patterns (read more, read more).
Power tip for today: keep the lights on—otherwise your rollout might go the way dax’s neighborhood did mid “Me too” setup (read more).
EricGT highlighted how nested replies can reintroduce “wrong reply button” confusion, arguing the plain Reply label isn’t specific enough and should better distinguish replying-to-topic vs replying-to-post (read more). The discussion explicitly ties back to nested replies UX concerns raised in the nested replies announcement thread (read more, read more), and Lilly quickly shipped improvements—first enabling customization of both reply button labels (read more), then adding the floating topic reply button into nested topic views (read more).
A new component aims to remove the “X votes left” line when topic-voting is configured with effectively “unlimited” votes (read more). NateDhaliwal suggested conditional visibility when a user is close to running out (read more), and awesomerobot noted a newly-added site setting—Topic voting enable vote limits—that can eliminate the need for absurdly high vote caps in the first place (read more). Related reference points in the ecosystem include the official topic-voting documentation topic (read more).
#announcements
The newly-improved “members can indicate they’re experiencing a reported issue” flow sparked a semantics-and-UX debate about whether the “Me too” counter should start at 1 (including the OP) or 0 (only “additional” reporters) (read more, read more). lindsey clarified the intent: the count represents “how many people are impacted,” hence starting at 1 to reflect the author’s impact (read more), while RGJ argued the label should change if the number includes the author (read more). The discussion also referenced how this looks “in the wild,” pointing to an API-related support thread where the button appeared to imply someone else was affected, but was just the OP (read more).
The Horizon theme now has high context topic cards enabled by default, expanding the information shown in topic lists and leaning into at-a-glance signals like solved, topic-voting, assign, tags, and excerpts (read more). This builds directly on the earlier “Horizon high context topic cards” introduction (read more) and references core/official feature docs for Solved (read more), Topic Voting (read more), and Assign (read more).
“Upcoming Changes” got a small but impactful UX report: when admins land on a filtered Upcoming Changes URL from a notification, the Preview link may be missing—despite being present when you browse the page normally (read more). martin explained that “Feedback…” and “Preview” are optional metadata per change item and offered to ping internally so more changes include them (read more).
#feature
A request proposes suppressing the “New features available!” notification on freshly created forums, arguing that on a brand-new instance everything is new and the alert adds noise rather than value (read more). The suggestion echoes the broader principle of reducing early-admin cognitive load (and references prior precedent for suppressing some “upcoming changes” messaging on new sites, via the linked GitHub PR from within the topic: read more).
Another branding/UX request asks for a separate mobile_logo_dark (or login_mobile_logo_dark) upload specifically for the login/signup splash screen, so admins can optimize the unauthenticated first impression without compromising the logged-in mobile header logo (read more).
A composer interaction bug report shows that when the cursor sits just above a horizontal rule, pressing ↓ while the emoji picker is open can cause the horizontal rule to steal focus and close the picker (read more). ted also linked a proposed fix PR for Discourse core right from the report (read more).
The locale detector for ai content localization hit a mismatch: Norwegian is detected as no, but supported locales use nb_NO. nat confirmed that adding explicit mappings to the system prompt is the right direction and shared an upcoming improvement—pulling in the “supported languages” setting so other communities avoid similar issues (read more).
A small but visible UI polish issue: user profile bios can be slightly clipped on the right edge (especially noticeable with italicized text), suggesting padding/overflow adjustments may be needed (read more). The report usefully references an older analysis of italics overflowing their container (quoted in the topic) to help narrow the likely CSS cause (read more).
The edit bookmark dialog UI got scrutiny: ted questioned whether a particular button is necessary at all, and noted that its icon and placement are misleading/confusing in its current form (read more).
A proposal suggests showing uneditable user fields in profile preferences as disabled inputs instead of hiding them, to better match user expectations and reduce confusion—while acknowledging moderation “staff notes” style use-cases might require configurability (read more).
Meta’s experimentation with “simple mode” for doc categories raised two UX questions: how to get the TOC back after clicking “timeline,” and why the toggle translations button is only visible while the timeline is open—especially when testing doc-categories, disco-toc, and content-localization together (read more). A related “how do I set the same sidebar categories for all users?” thread also saw continued troubleshooting around default vs user-customized sidebar state, relevant to admin predictability expectations (read more).
#site-feedback
“Simple mode” appearing in Meta’s Wiki doc categories sparked feedback about contributor recognition: Moin argued that showing authorship matters more in the community wiki than in official documentation, and linked several historical threads about docs/wiki discoverability and contribution pathways (read more; related: read more, read more).
#enterprise
A scaling story underscored that performance failures can come from information architecture rather than media volume—especially when category trees explode into “sub-sub-subcategories.” jpishgar described a large community buckling under category depth, and HAWK added a real-world customer migration anecdote where over-deep categorization became a dealbreaker (and reinforced “tags over endless nesting”) (read more).
#plugin
The official Discourse Subscriptions plugin (subscriptionspayments) got a high-signal edge-case bug report: in certain flows, the plugin can create a Stripe PaymentIntent without attaching a valid payment method (especially when an expired card exists), leading to silent subscription failures for end users (read more). Related plugin areas also saw activity elsewhere on Meta, including Discourse Workflow’s new visual editor PR announcement (read more) and an OpenID Connect corner case involving disallowed usernames ending with underscores (read more).
martin posted an announcement that high context topic cards are now enabled by default in the Horizon theme, pointing admins to the upcoming change toggle and recapping what the new cards surface (read more). He also followed up in the “Upcoming Changes” system thread to clarify that “Feedback…” and “Preview” links are optional per change item—and offered to prompt internal improvements to metadata coverage (read more).
awesomerobot replied to the “Hide Votes Left” component thread with timely product news: a new topic-voting site setting (Topic voting enable vote limits) can remove vote limits entirely without the “set it to 100,000” workaround—while noting the component might still be useful for mixed trust-level configurations (read more).
HAWK added an enterprise perspective to the scaling/IA discussion, describing a prospective customer with extreme geographic sub-categorization, Discourse’s preference for tags in such cases, and why the team declined to support an unsustainable structure (read more).
nat confirmed the fix direction for Norwegian locale handling in the locale detector, validating the “common language codes” mapping approach and committing to improve the generic system prompt by using the site’s supported languages setting (read more).
lindsey clarified the intent behind the new “Me too” counter behavior: it starts at 1 to represent the topic author as impacted, framing the counter as “people impacted” rather than “people who clicked” (read more).
If today’s Meta was any indication, tomorrow’s Discourse admins will have clearer Reply buttons, fewer “100,000 votes left” humblebrags, and emoji pickers that (hopefully) won’t get bullied by horizontal rules.
Nested replies discussion expanded into “could this replace Post Voting?” territory. A user asked about combining/replacing Post Voting, and markvanlan explained why nested replies took a different approach in Introducing nested replies.
Security thread: Nginx CVE concern prompted a “base image update” response. After a “is Discourse vulnerable?” question and some moderation pushback, sam clarified status/next steps in Nginx CVE-2026-42945.
sam addressed container-security concerns and stated the plan to update Discourse’s base image while noting default rules aren’t vulnerable in Nginx CVE-2026-42945.
That’s a wrap—may your categories be safe from rogue “Delete” clicks, your embeds log in smoothly, and your bookmarks stay blissfully toggle-free.
Crown1 reported a confusing hosted upgrade flow where Starter didn’t appear as an upgrade option from the Free plan, while only Pro showed up; mcwumbly confirmed Starter should be available, asked where the upgrade click originated, and began investigating what may be influencing the UI (including plan-gated plugin prompts) (read more).
EricGT thought Discourse AI translation wasn’t working, but the thread concluded it was driven by a preference (“show in original language”) and the topic-level toggle that syncs back to user settings; Moin explained how the toggle works and why it appeared inconsistent (read more).
Ethsim2 dug into /about page group visibility edge-cases: “about page hidden groups” hides the section, but doesn’t prevent a user from appearing via another visible group; discussion focused on whether this is intended and how to avoid accidental exposure (group member visibility settings) (read more).
A hosted Free-plan user asked how to enable tags, and darkpixlz clarified that tags aren’t currently available on the hosted free-plan, pointing to the Free Plan Beta announcement for context (read more).
Eviepayne asked how to properly set up real IP forwarding behind a reverse proxy (needing set_real_ip_from + real_ip_header X-Forwarded-For) and whether there’s an env var or app.yml option to support this cleanly (read more).
Prempavee couldn’t recover a deleted post and ran into HTTP 500 errors when trying to open the topic; Falco flagged it as likely a bug involving deleted nested topics and offered to take a closer look (read more).
Lilly documented that nested mode breaks post admin wrench menu actions (menu opens, actions fail silently), forcing admins to switch back to flat mode to complete moderation tasks (read more).
Lilly reported a mobile UX/bug where full-screen reactions are difficult to exit on iPhone Chrome, sometimes leaving “close the browser window” as the only escape route (read more).
In a related moderation flow, Prempavee asked why they can’t delete topics/posts as a regular user; the thread surfaced core rules (age/no-replies constraints) and also the possibility that nested mode affects delete controls, with ondrej noting delete worked in flat mode but not nested (read more).
A mobile browser report (Chinese-language) showed the admin tag group page rendering incorrectly when using the Modernize Foundation theme, raising questions about responsive layout regressions in admin screens (read more).
The “NEW status” conversation continued: users observed that topics appear to be marked read immediately upon entering, rather than after reaching/reading the end—suggesting a behavioral change worth verifying (read more).
A plugin naming thread heated up around a potential “Workflow” plugin name clash; j.jaffeux advised avoiding “Discourse X” naming for non-official plugins and suggested a clearer namespace approach (read more).
Dev setup clarity improved: Ethsim2 summarized the cleanest approach to bootstrapping the first admin account in dev (d/boot_dev --init, MailHog, and bin/rails admin:create), and Moin pointed them to the Discourse developer toolbar capabilities (read more).
#Theme-component
Quote Callouts shipped a useful round of polish: Arkshine updated behavior so callouts render in history revisions, onebox excerpts strip markers, and the keyboard shortcut moved to Ctrl/⌘ + Alt + C (read more).
A WordPress embed SEO thread progressed with angus narrowing down a diagnostic checklist around missing/changed canonical tags and x-robots headers for older embedded topics—trying to confirm when and how canonical URLs switched to the Discourse URL (read more).
A practical adoption question: Architect explored whether Discourse can work for small town government outreach (public + resident communications), and what hosting/admin approach makes sense when the “staff” are civic employees rather than a typical product team (read more).
mcwumbly engaged on hosted plan upgrades, confirming Starter was intentionally deprioritized on pricing pages but should still be available for Free → Starter upgrades; they asked where the upgrade action originated and began investigating why only Pro was shown in Crown1’s case (read more, read more, read more).
Falco appeared in two moderation/nesting-related support paths: they clarified the rules for self-deleting topics (no replies + <24h) (read more) and identified a likely bug visiting deleted nested topics while offering to investigate further (read more).
j.jaffeux weighed in on plugin ecosystem hygiene, recommending stronger third-party naming/namespace practices to reduce collisions with official or upcoming plugins (read more).
May today bring you visible Starter upgrades, working nested-mode wrenches, and reaction overlays with an obvious “close” button.
New posts (last 24h): 42 (spread across active threads like the update crash report read more and reverse-proxy configuration discussion read more)
New topics (last 24h): 4 (including a self-host lockout scenario read more, an AI plugin hyperlink bug report read more, and an update crash workaround read more)
Top users by activity (posts) & appreciation (likes):
Notable theme of the day: resource constraints + rebuild/update flows—with discussion around plugin asset compilation timeouts and whether very small single-vCPU servers should avoid web-based updates (read more, read more).
Additional threads that also saw fresh replies today: small-town government use cases (read more), bulk tag tooling updates (read more), and the Custom Wizard plugin’s missing “advanced” dropdown options (read more).
TroLLoBlogger reported a crash after attempting to update via the admin UI, traced to a plugin asset compilation timeout; the workaround was rebuilding via ./launcher rebuild app, with follow-up discussion about whether single-vCPU servers should be steered away from web updates and toward rebuilds (read more, team follow-up, analysis).
In the long-running “Thanks for Contributing” popup thread, Moin pointed to a fix landing via a PR, suggesting the issue is already addressed upstream (read more).
The AI locale detector behavior was updated: Norwegian/Greek locale handling is now incorporated into the default agent configuration, aiming to reduce mismatches like no vs nb_NO in supported locales (read more).
A TypeError occurs when submitting certain flags that require custom text (require_message flags). sam acknowledged the report and invited a PR while the team investigates (read more).
A new report (in Chinese) describes hyperlinks inside the official AI plugin not responding when clicked, with a screenshot showing the affected UI and behavior (read more).
A brand-new hosted customer hit an “Oops! That page doesn’t exist or is private” moment during email verification; the root cause turned out to be testing while still effectively authenticated as admin in another context—resolved by doing a truly clean/incognito verification flow (read more, resolution).
Reverse-proxy operators discussed how to properly preserve client IPs with X-Forwarded-For: Eviepayne needed set_real_ip_from ... for internal nginx to respect forwarded IPs (after 429s), and Lilly outlined how to make the change survive rebuilds using replace in app.yml/web_only.yml (read more, recommended approach).
A nuanced settings interaction question: how /about behaves when “about page hidden groups” overlaps with “about page extra groups.”Ethsim2 proposed a clearer rule (or even a dedicated boolean setting) to prevent users hidden via one setting from reappearing via another (read more, proposed setting).
A developer question explored whether Discourse can pre-fill both email and username from URL parameters. The conclusion: email is partially supported via a cookie-to-signup flow, but username isn’t built-in; ted mapped the relevant Rails/Ember flow for anyone considering a plugin/PR (read more).
The “Missing PNG to JPEG settings” discussion clarified a subtle behavior: PNGs only convert to JPEG when there’s no transparency, making the setting more practical than it initially appeared for image-sharing workflows (read more).
#Self-hosting
A self-host admin locked themselves out by disabling Discourse ID before establishing a local admin login: the instance reported “No login methods are configured”, and /u/admin-login emails weren’t arriving—highlighting the sharp edges in auth-method transitions if recovery paths aren’t confirmed first (read more).
In a migration/restore thread, xlg256 suggested downgrading aws-sdk-s3 to work around rebuild failures introduced by AWS SDK changes, linking to a related deep-dive discussion on the gem bump and integrity protections (read more, related).
A question about the discourse/discourse Docker image asked whether it’s “production-ready” and how to upgrade when the image lags behind official releases—surfacing common confusion between community images and the standard Discourse Docker install path (read more).
Command-line backup workflows got attention: Jonathan5 double-checked whether CLI backups match the web UI output, then noted confusion about the download path versus where the tarball actually landed—useful caution for “I forgot to back up before rebuild” moments (read more, path detail).
#Announcements
Bulk tag operations: nat popped into the “Better bulk tag management” announcement thread to say a temporarily-missing feature/behavior will be back “soon™,” keeping momentum on tag tooling improvements (read more).
Falco drove the investigation on update-related downtime, zooming in on the plugin build timeout and asking for server specs—then explicitly questioned whether the combination of non-core plugins + single vCPU should trigger guidance to rebuild rather than update via the web UI (read more, read more, follow-up, constraints note).
david clarified how pre-built assets are distributed and why this case behaved differently: the failing discourse-doc-categories plugin isn’t core (so its assets aren’t prebuilt/distributed), but the reported 120s compile time still seemed unusually high for such a simple plugin (read more).
nat posted an update that the AI locale detection guidance is now baked into the default agent, so installations using Norwegian/Greek should have better defaults going forward (read more); and also checked in on the tag tooling announcement with a “back soon™” status update (read more).
sam acknowledged a newly reported TypeError when submitting require-message flags, confirming the team will investigate and welcoming an external PR in the meantime (read more).
Yesterday’s vibe: if you needed a reminder to rebuild first, test in incognito, and never underestimate one lonely vCPU, meta delivered in full.
Discourse shipped more flexible RSVPs for recurring events, letting people RSVP to just the next occurrence or all future occurrences—a big usability win for organizers using calendar-and-event (read more). Lilly immediately asked about notifying groups for upcoming events without spinning up a group PM (read more) and nathank highlighted how this pairs well with more advanced recurrence patterns (like “nth weekday”) (read more, related: read more).
May 19th 2026 intermediate releases landed to deliver critical security fixes, with david pointing admins at the changelogs for multiple supported trains under release-notes (read more).
Discourse AI got a small but impactful UX boost: you can now star AI chats so they stay pinned at the top of your conversation list—rollable via Upcoming Changes as Enable AI bot starred conversations (ai) (read more).
A long-standing consistency paper-cut is being addressed: when discourse_reactions_experimental_allow_any_emoji is enabled, the “More…” control shouldn’t be represented by the :-) emoji. awesomerobot confirmed a fix in progress (reactions) (read more).
A new Form checkbox redesign (via Upcoming Changes) modernizes FormKit checkboxes: the native checkbox remains functional but visually hidden, while a presentational checkmark span enables better styling and animation. The team asked for bug reports directly in the topic (read more).
“Do you ship a default abusive-word list?” came up again. The consensus: no default list, because community needs differ—but Watched Words is powerful (bulk import/export, block/flag/censor/require approval, wildcards, etc.). HAWK linked the canonical guide and explained the supported actions (watched-words) (read more, guide: read more).
Nested Replies continues to surface workflow gotchas for admins: one user couldn’t change topic ownership (and hoped to transform a reply into a topic), but the immediate workaround was “switch to flat mode” until nested-mode wrench actions are fully restored (read more, workaround context: read more).
A practical “power user” question: is there a shortcut to link to a specific post number (like “comment #123”) without quoting? The thread confirmed there’s no built-in composer syntax today; copying the post link (or creating a theme component) remains the option (read more).
Custom Wizard users asked how to remove test submissions “via Rails,” noting that community/LLM guidance can be unreliable without exact commands. The same question was posted both as a standalone support topic and into the plugin megathread (read more, plugin thread: read more).
A mobile-only issue: visiting the bottom of a nested-replies testing topic (especially via an unread indicator) can produce a 404 at the bottom of the page. Falco flagged it as likely related to nested read-state changes and looped in engineering to investigate (mobilenested-replies) (read more, staff ping: read more).
A regression (or resurfacing) report: with topic-voting enabled, users can’t view who voted on a closed topic; the UI shows nothing and the API returns an empty list. The report includes repro steps and screenshots (read more, historical reference: read more).
Admin/moderation tooling hit an error path: a TypeError when submitting a flag requiring a message (custom flags or “Something Else”) was discussed, with tgxworld requesting a safe-mode repro to rule out theme/plugin interference (read more, safe mode guide: read more, staff reply: read more).
#Feature
A thoughtful moderation housekeeping idea: automatically purge silenced users with no posts after X days (often pure spam accounts). The author later noted the existing “Clean up inactive users after days” setting may cover the use case, while awesomerobot recommended “delete and block” for spam cleanly (read more, staff guidance: read more).
Bulk operations friction: when bulk converting Topics → Messages, there’s no option to add a Group recipient—making “convert a category into a group inbox” hard without manually adding participants. The request proposes matching the richer modal available in the reverse conversion direction (read more).
#Theme-Component
A small but real UI polish bug in Quote Callouts: code-styled text in callout titles rendered too “short,” causing clipping/overlap in some languages and sizes. A fix was pushed to add missing core CSS for <code> and tidy whitespace (read more, fix note: read more).
lindsey shipped the headline Events improvement—granular RSVPs for recurring events—and documented the desktop/mobile interaction differences (calendar-and-event) (read more). She also followed up in a related support thread to point users at the new behavior (read more).
david published May 19th 2026 intermediate releases, pointing self-hosters and hosted customers at the relevant security-fix changelogs (release-notes) (read more).
awesomerobot made several high-signal drive-bys: confirmed a tweak to how “Me too” counts are tallied in Solved improvements work (read more) and confirmed the “Me too” label text is safe to customize (read more); acknowledged and began addressing the :-) “More…” reactions inconsistency (reactions) (read more); and recommended best-practice spam cleanup (“delete and block”) in a moderation feature discussion (read more).
Falco stayed deep in the nested-replies trenches: connected a mobile 404 report to read-state work and pinged engineering (read more); clarified how category-level nested settings behave (“default at creation time only”) and reinforced bug-report hygiene (“one bug per topic in Contribute > Bug”) (read more, read more); and linked fixes-in-flight for missing wrench actions and deleted-post recovery problems (read more, read more).
HAWK provided the definitive answer on abusive-language moderation: no universal default list, but Watched Words offers block/flag/censor/require-approval and more—plus bulk CSV workflows—backed by the reference guide (watched-words) (read more, guide: read more). He also reassured enterprise readers that calendar/events is under active development and video conferencing is on the roadmap (read more).
tgxworld investigated a reported flag submission TypeError, asked for a safe-mode confirmation, and noted the bug wasn’t reproducible locally yet (read more).
chapoi announced the Form checkbox redesign upcoming change, including before/after captures and implementation detail (native input preserved; stylable presentational element added) (read more).
martin responded to feedback on the “Easily create Events categories” automation, asking for clarification on what a “sidebar equivalent” should mean (e.g., surfacing upcoming events in the sidebar vs. simplifying sidebar setup) (read more).
featheredtoast explained an unintentional side effect in discourse_docker (from clearing stuck web upgrades) and pointed to an in-progress PR to resolve it (read more).
sam shipped the Discourse AI improvement to star common AI conversations, making frequently used chats easier to keep at hand (ai) (read more).
Yesterday’s moral: between recurring-event RSVPs, checkbox makeovers, and nested-replies edge cases, even the smallest UI choices can spark the biggest conversations.
“DistributedMutex held for too long” warnings popping up in logs (read more)
WordPress embeds: missing canonical/noindex on older embedded topics (diagnostics via Rails console) (read more)
Multisite operators asked about adding new sites without a rebuild (read more)
A “move topics” confusion turned into a helpful subcategory vs tag realization (read more)
WooCommerce + WP Discourse: whether Discourse usernames can safely diverge from WordPress user_login (read more)
A blog companion thread argued for staying browser-first (and not forcing apps) (read more)
Interesting Topics
#Announcements
keegan introduced a docked composer experience for ai-bot conversations—aimed at reducing “click Reply again” friction and keeping the input persistent, behind the upcoming change flag ai_bot_enable_docked_composer (read more)
In the ongoing splash customization thread, Falco shared more examples of branding the Discourse splash screen with custom splash SVGs (and noted improved results using Gemini 3.5 Flash) (read more)
Follow-up discussion on “Events category” creation explored possible integration with Right Sidebar Blocks—martin is considering whether Discourse can detect the component and enable event-related sidebar blocks automatically (calendar-and-eventeventscategories) (read more)
An Office Hours replay dives into MCP + Data Explorer workflows—showing how AI assistants can generate queries and summarize community trends, with the recording linked for those who missed it (webinaroffice-hours) (read more)
A companion discussion to Discourse’s latest blog post makes the case that Discourse “will never block you from the web,” contrasting with platforms nudging users into apps (read more)
#Migration
A phpBB importer performance thread dug into “why is my import slow when CPU is low?”—with Redis timeouts and likely I/O or DB-side bottlenecks (plus a hint that faster migration tooling is in the works) (phpbb) (read more)
External Postgres upgrades bit a self-host: backups fail when the container’s pg_dump (v15) talks to a Postgres 18 server—highlighting client/server version mismatch considerations (read more)
A new admin asked how to export all site data (not just personal exports), with pointers toward using full site backups (read more)
A report of Internal Server Error when approving new users (with OAuth2 auth) focused troubleshooting around /logs and browser console output (read more)
A release email appears to link to a non-existent changelog URL (missing the v prefix), causing a 404 for “See what’s new in the release notes” (read more)
#Feature
A feature request proposed “delivered” vs “read” indicators for Chat DMs (chat), with discussion about the social downsides of read receipts and whether it should be optional (read more)
The missing “tag info” button prompted clarification: it was removed after adding a dedicated tag settings page, and there’s now a PR to bring it back with a refreshed banner aligned to category banners (read more)
#Theme
Horizon Theme feedback focused on mobile/compact layouts: trouble reproducing a “suggested threads” display issue, plus broader UI density concerns around sticky navigation and footer buttons stacking (officialhorizon-theme) (read more)
#Theme component
Discourse Mermaid users asked about the update cadence for mermaid.js (notably for newer chart types like Wardley Mapping), and whether a PR would be welcomed (officialmermaid) (read more)
A reproducible TypeError tied to require_message: true flag flows (and already_did_flagging) was narrowed down—especially around nested topics where multiple flag reasons remain available unexpectedly (read more)
keegan announced the new docked composer for AI bot conversations and invited feedback on how it feels in longer back-and-forth chats (read more).
Falco posted additional splash-screen SVG examples (and commented on model output quality improvements) in the splash branding thread (read more); and welcomed community PRs to update Mermaid support in the official component (read more).
Danielle published the Office Hours replay and walkthrough framing for MCP + Data Explorer in action (including the recording link) (read more).
cocococosti weighed in on speeding up phpBB imports—suggesting DB-side work like indexes/views/settings tweaks, and teased faster migration tooling on the horizon (read more).
awesomerobot confirmed that brand-new forums will no longer get “new features” notifications for historical releases (only future ones) (read more); and opened work to bring back/improve the tag info UI affordance (read more).
mae shared that Discourse had already been submitted to the Digital Public Goods Alliance registry (submission timing and attribution noted) (read more).
martin responded to feedback on Events-category setup automation and is considering enhancing setup when Right Sidebar Blocks are present (read more).
nat merged a translation-related PR after adding specs, closing the loop on the reported language-code behavior (read more).
isaac marked improvements to the @patch-triage bot—supporting fork workflows and expanded actions—then invited broader testing (read more).
featheredtoast cautioned about the operational risks of relying on the discourse/discourse Docker image in production and recommended avoiding mixed upgrade paths that increase exposure to unexpected changes (read more).
With docked composers rolling out and migrations still sprinting (even when Redis complains), today’s meta vibe was: ship UX, measure everything, and keep the web open.
“No one will ever be beholden to us.” — HAWK on data portability while discussing the hosted Free plan’s evolving boundaries (read more)
Interesting Topics
#Announcements
A new “simple mode” for Doc Categories (reading-first docs, replies behind a toggle).saquetim announced a documentation-focused experience for the Doc Categories plugin, including auto-expanding when linking directly to a reply and an “Updated” style topic list for doc categories (read more). Related background: the Doc Categories plugin overview lives here (read more).
Reply count placement updated when using Reactions.davidb shared an opt-in “upcoming change” that moves the reply count to the right to keep reactions alignment consistent in-post for sites running reactions (read more).
“Me too” + Solved interactions: requests for category-level configurability. In the ongoing discussion about Solved improvements, Noble_Fish argued that combining Topic Voting + Solved + “Me too” can be confusing in mixed-use categories, and asked for more granular controls (read more).
Events + Calendar UX wishlist: unify upcoming events and topic list in one view. In the Events and Calendar plugin announcement thread, nathank proposed a more obvious combined “upcoming events + topics” category view (especially for right-sidebar blocks and “what’s next” scanning) (read more).
Discourse positioning: “Will never block you from the web.” A new blog post sparked discussion (and a small meta-question about attribution/author display), with NateDhaliwal asking if the author should be changed to ducks (read more).
Search UI consistency: casing and punctuation in dropdown labels.Richie asked for consistent casing across dropdown options on expanded search (/search?expanded=true) and suggested removing the trailing ellipsis from “Only return topics/posts…” (read more). NateDhaliwal pointed out the “Where topics are…” phrasing may be intentionally sentence-like, but agreed standardization is still valuable (read more).
Staff auditing gap: undeleting a post doesn’t create a log entry.RGJ reported that deleting and restoring topics are logged, but restoring posts isn’t—making it hard to see who restored content without digging into system logs (read more).
Horizon theme header breaks on mid-size (640–767px) viewports (foldables/small tablets).nathank reported missing header elements (search/avatar) at certain widths on horizon-theme, and Lilly shared a CSS workaround plus notes about a setting that can influence the behavior (read more).
Emoji autocomplete fails with special characters (e.g. “ü”), worse in Chat.Moin shared repro videos showing that selecting an emoji from “more” doesn’t properly replace typed text when special characters are involved—and Chat throws a console error and can fail selection entirely (read more). Related footnote: Moin noticed a tagging + grace-period edge case again while testing this, in an older bug thread about revisions (read more).
Tag Icons component inconsistencies (underscore vs dash slug behavior).AquaL1te reported missing tag icons in topics/tag pages despite working in the sidebar; Lilly suspected tag slug normalization (underscores becoming dashes) tied to an upstream change in the component and suggested adjusting slugs in the theme settings accordingly (read more).
Chat UX bug: Back button forgets “Starred” context.Shauny described an everyday annoyance: even when navigating within Starred chats, “Back” returns users to Channels/DMs instead of Starred—adding friction that undermines the feature’s purpose (read more). Related feature reference: starring channels was introduced here (read more).
Meta testing page shows a 404 at the bottom (nested replies test). In a bug report about a recurring 404 on a Meta testing route, markvanlan said they couldn’t reproduce at the moment but would keep an eye out (read more).
Hosted pricing + Free plan boundaries: what changed, and what’s “essential email”?Alex_Dehnert flagged confusing shifts in the pricing page emphasis and noted “email in” became locked after working; HAWK clarified the Free plan is a recent soft launch, that “email in” was disabled after an oversight, and reiterated export/self-host as the escape hatch if plans change (read more). Extra context referenced in-thread: Free plan beta discussion (read more) and “No starter upgrade option” history (read more).
Theme component upload error: about.json invalid/missing (zip structure issues).baseline-mobile hit an import error installing a theme component zip; Moin suggested the zip’s folder structure (often impacted by OS zip behavior) may place about.json one directory too deep, and provided a repacked zip that installed successfully (read more).
Postgres 18 backups failing: how to align client tools and work around version mismatches. In a support thread, ted highlighted uncertainty about Discourse’s Postgres client upgrade policy and pointed to prior similar discussions; pfaffman suggested installing matching client packages and then codifying the steps in app.yml (read more). Related older reference: Postgres client upgrade discussions (read more).
Accessibility question: themes/components that work best with screen readers.happyhappy asked whether any themes or theme components are known to be especially navigable for visually impaired users, given most base accessibility work is now in core (read more).
WP Discourse + WooCommerce identity mapping: username sync not required.angus explained that DiscourseConnect matches accounts using external_id (WordPress user id), so WordPress and Discourse usernames don’t need to stay aligned—reducing risk if Discourse users rename themselves (read more).
WordPress embed SEO edge case: missing topic_embed records break canonical/noindex behavior. In a thread about embedded topics missing x-robots noindex and canonical tags, angus noted the canonical-for-embeds feature requires a topic_embed record, and discussion continued around making “apply noindex to all topics in category” a more direct setting (read more).
A native Discourse client app for iOS + Android (show-and-tell).nicolsdennis demoed a native client and noted current plugin support is limited to official plugins (calendar integration is in progress) (read more). Related mention: they also posted an update in an older “turn a forum into an app” thread, saying they’re replying using the client (read more).
Notification consolidation: UI-only grouping or database/API-level row reuse?nitinkg reported that reply/reaction notifications appear consolidated even with small counts, and asked whether Discourse updates existing notification rows (instead of append-only inserts) and whether consolidation can be disabled for a “one action = one record” model (read more). Related (Chat adjacency): read/delivered semantics for DMs are being debated separately (read more).
#Plugin / #Theme_component / #Self-Hosting (quick hits worth a peek)
Plugin rename: “Discourse Workflow” rebranded to “Process Manager.”merefield announced a rename due to an upcoming naming conflict with core; tables/indexes were renamed and settings weren’t migrated, so admins should recheck plugin settings and any Data Explorer queries (read more).
Theme component compatibility: Featured Topics vs pavilion dropdown header.TestingRico reported a collision where the pavilion dropdown header disappears in preview when testing Featured Topics, and asked about workarounds (read more). Related pavilion ecosystem thread: Topic Ratings plugin discussions continue (read more).
Cloudflare R2 now working as S3-compatible storage (doc needs an update). In the long-running S3-compatible uploads/how-to topic, Lilly reported successful external backups and restores using Cloudflare R2, noting prior incompatibility text is outdated and should be revised (read more).
saquetim published an announcement introducing simple mode for Doc Categories, emphasizing a reading-first layout with replies behind a toggle and auto-expansion when linking directly to replies (read more).
davidb announced an opt-in layout change for sites using the Reactions plugin: the reply count moves to the right to keep alignment consistent throughout posts (read more).
markvanlan followed up on a reported 404 at the bottom of a Meta testing page, noting they couldn’t reproduce currently but would keep watch in case it’s intermittent (read more).
HAWK clarified what’s happening with the hosted Free plan (still in soft launch), explaining why “email in” was reverted/disabled, and reaffirming that communities can always export and self-host if priorities change (read more).
That’s a wrap: may your folding-phone headers stay aligned, your tag icons survive every slug rewrite, and your emoji picker learn to love “ü” by tomorrow.
Clarified scope/availability of a native Discourse client app concept — read more
Team highlights (by volume):zogstrip led team participation (6 posts) with quick links to fixes and PRs, including reactions, chat, flags, and SEO-crawler edge cases مثل read more.
Discourse published a companion discussion on being “Agent Ready”—how AI agents consume forum knowledge and what that implies for communities and publishing strategy (read more). A closely-related thread on provenance/fact mapping continues to orbit the same theme of how content should be trusted and traced in an AI-shaped web (read more).
#Announcements
“Simple mode” for Doc Categories landed, aiming to reduce confusion around posting vs reading in docs-style spaces, after folks reported replying before realizing a doc topic already had a discussion/history (read more; example confusion noted here: read more; related docs-category context: read more).
The nested replies rollout continues to surface UX + translation-adjacent customization needs: one participant suggested language-specific CSS selectors, while Lilly pointed to a plugin-based approach with translations included (read more; CSS suggestion: read more; plugin alternative: read more; referenced solution thread: read more).
On improving automatic mobile/desktop mode switching, Lilly connected a folding/mid-viewport Horizon theme regression to the viewport-based mobile mode setting, and david noted the setting is “long overdue” for removal because modern design assumes it’s enabled (read more; david follow-up: read more; related Horizon viewport bug: read more).
A native iOS+Android Discourse client app preview drew interest; nicolsdennis clarified it’s not store-published yet, depends on a companion plugin for full functionality on many sites, and shared the “Allowed user API auth redirects” setup needed for login previews (read more).
A nested replies UI glitch on iOS PWA showed a large gap between username and avatar; once confirmed as an iOS progressive web app, markvanlan jumped in to investigate (read more; platform confirmation: read more; team response: read more).
Chat navigation weirdness: the back button in floating chat can “forget” state (like starring) due to floating chat interacting with page history; sam and zogstrip discussed how this should improve once upstream work merges (read more; PR-referenced improvement note: read more).
A “new version available” email template contained a broken release-notes link (missing the v in the URL); Lilly prepared a fix proposal, and the reporter confirmed it’s helpful even for local patching (read more; reporter follow-up: read more).
Emoji autocomplete struggled with special characters like ü, and renato linked a PR expected to fix it (read more).
Reactions UX had two sharp edges this cycle: (1) the “+1” hover popover could spin forever because + wasn’t URL-encoded, and (2) mobile back-navigation with the reactions list open could leave the modal open and jump scroll position. The hover issue was acknowledged as fixed by a PR, while the back-button behavior echoed earlier modal-related reports (read more; fix pointer: read more; back-button report: read more; earlier related modal discussion: read more; another related post: read more).
A self-hosted backup failing under Postgres 18 was resolved when Thomas_Rother installed Postgres packages inside the container/host context; pfaffman recommended pinning the right client packages and automating in app.yml to avoid future surprises (read more; follow-up hardening advice: read more).
A report that one topic’s view counts weren’t incrementing prompted basic triage questions and a suggestion to try safe mode to rule out theme/component interference (read more; troubleshooting prompt: read more).
Hosted-plan UX friction continued: questions about pricing structure changes / free plan feature visibility got a candid acknowledgement that experimentation is ongoing, plus a promise to raise feature-matrix clarity internally (read more). In a separate upgrade-flow bug, the Starter plan option appeared missing due to a recommendation-system edge case around staff limits, with a fix planned (read more).
#Self-hosting
On whether the discourse/discourse Docker image is production-ready, featheredtoast confirmed a patch restored expected builds and upgrades, and that the latest image became available again after the fix (read more).
WordPress embed users flagged that older embedded topics were missing x-robots: noindex and canonical tags; angus clarified canonical behavior depends on embed records and suggested republishing to recreate missing records, while the OP argued for a native “category-level noindex” control as a broader SEO need (read more; follow-up/feature request argument: read more).
A thoughtful thread on community breaking points as usage grows continued: Tris20 described how unmanaged growth can overwhelm specialists and moderation, and shared a tactic of gating new-topic creation behind “read this first” expectations—effective, but not universally loved (read more; HAWK follow-up question: read more).
zogstrip was the day’s “fast path to resolution” across multiple threads: pointing to fixes for chat history/state confusion (read more), the reactions “+1” hover encoding bug (read more), a flagged-post restore edge case (read more), plus maintenance/UX improvements like adding missing setting-description links (read more) and addressing crawler pagination issues (read more).
david confirmed product direction on viewport-based device mode switching—calling out that the legacy “disable viewport-based mobile mode” setting is overdue for removal because current design assumes it remains enabled (read more).
HAWK engaged on hosted-plan communications and expectation-setting: acknowledging continued experimentation around plan packaging and committing to bring feature-matrix clarity feedback to the team (read more), and following up on enterprise community-growth process questions (read more).
markvanlan picked up investigation on an iOS PWA nested-replies layout gap report (read more).
featheredtoast confirmed Docker image build availability was restored after a patch, unblocking upgrades for image users (read more).
sam dug into why floating chat and browser history interaction creates confusing “back button” behavior, helping narrow scope (floating vs full-screen) and framing the underlying issue (read more).
rishabh acknowledged and explained why a hosted upgrade flow could incorrectly skip Starter (staff-limit logic), thanked the reporter, and committed to follow up after a fix (read more).
renato linked an in-flight fix for emoji autocomplete failures with non-ASCII characters (read more).
supermathie asked the key diagnostic question (“what was the reason given?”) in a Chinese-language support thread about approval/flag states that appeared confusing in the moderation queue (read more).
Yesterday, Discourse got more agent-ready while reactions tried to turn “+1” into “ 1” — at least the fixes landed fast (read more).
eisammy challenged the value proposition of “being crawled by AI” (bandwidth, incentives, and legal/privacy concerns), and awesomerobot framed it as context-dependent—helpful for support/knowledge bases, harmful for social communities—in Discourse is Agent Ready: Here’s How. Related nuance around #llms-txt skepticism appears in this reply, and a “just block them” stance (plus examples) is in this post.
A rebuild/theme update left category-list “featured topics” looking cramped with smaller text; Lilly pinned it to Modernized Foundation and offered a CSS workaround in 刚才rebuild更新后，首页字体变的很小 (foundation-theme). Confirmations/notes followed in this post and a “cache made it look broken” resolution came later in this reply.
Copy/paste expectations collided with clipboard reality: supermathie showed that the Discourse codeblock copy button provides plain text, while selecting rendered HTML can preserve formatting—leading to a deeper “is it copy or paste?” investigation—in Syntax highlighting… is not copied. The thread ultimately pointed to browser behavior differences, with Firefox not inlining styles like Chromium in this analysis.
A mobile/PWA composer regression: when iOS text size is set smaller inside the PWA, the Reply button can disappear (while Safari works), as reported in Reply button not visible when composing on iOS PWA (composerpwaios). The report also references a potentially-related older issue: read more.
A post-update navigation/admin sequence briefly produced an alarming error page, but loading in a fresh tab “fixed it”; Falco suggested checking logs in Bug? forum issues. The initial report is here: read more.
iOS Chrome “back” navigation on Meta itself was reported as inconsistent (sometimes returning to an unexpectedly older page), raising compatibility/history concerns in Chrome浏览器返回键的bug (mobile). A translation clarification came in later here: read more.
A “missing Like button” mystery turned out to be expected behavior: in Voting-enabled categories, Likes are suppressed; the diagnosis and pointers (including possible Reactions workaround) are in 请问一下点赞按钮如何显示. The canonical plugin note is quoted from Discourse Topic Voting, and the “show both like & vote” guide is here: read more.
Doc categories “simple mode” continues to generate practical UX questions/feedback, including where to consolidate prior reports and how it affects discoverability of controls—see Introducing simple mode for Discourse Doc Categories (doc-categories) and the referenced follow-up thread: read more. Related site-feedback about attribution impact in Wiki appears in this post.
Voting UI expectations surfaced again after an update: communities used to a large, explicit “Vote” button now see a subtle arrow control; the request to revert/adjust is in Discourse Topic Voting (topic-voting). This also intersects with “Likes hidden in voting categories” (see: read more).
awesomerobot engaged in the “AI crawler / incentives” debate, emphasizing that the right choice depends on whether your forum is primarily support/knowledge or social community, in Discourse is Agent Ready, and added the pragmatic reality that many scrapers ignore robots/IP blocks in this follow-up.
supermathie provided a concrete breakdown of why syntax highlighting often won’t paste “with colors” (copy-button clipboard formats vs rendered HTML selection), plus debugging ideas/tools, in Syntax highlighting… is not copied and this continuation.
supermathie solved a missing-like-button report by identifying Voting-category suppression and pointing to known ways to re-enable/approximate likes (or use Reactions), in 请问一下点赞按钮如何显示.
Falco responded to a post-update “weird error page” report by directing the reporter to inspect instance logs, in Bug? forum issues.
Yesterday’s moral: may your fonts be readable, your approval queues non-phantom, and your “Reply” buttons remain stubbornly visible—especially on iOS PWAs.
Translation/communication clarification in back-button thread: read more
Interesting Topics
#Feature
wenqin shared cross-cultural + generational usability feedback and asked for an admin-selectable default reply order (oldest-first vs newest-first), noting discoverability issues around the timeline/progress UI for older users; Falco replied that the timeline is a single click/tap and pointed to how nested replies changes the reading flow (read more, read more, plus nested replies context: read more)
A parallel permissions discussion continued around splitting “delete all posts and topics allowed groups” into more precise capabilities (own-content vs global-content), with deep dives into PostGuardian checks and what should/shouldn’t become visible to non-staff (read more, read more, read more)
Ethsim2 proposed clearer wording for the delete_removed_posts_after setting to better distinguish author removal vs later cleanup deletion, and to clarify what staff vs regular users can see during the retention window (read more, background thread: read more)
#Theme component
mcmcclur released a theme component to typeset KaTeX in topic titles, acknowledging Discourse’s general avoidance of rich formatting in titles while providing a practical option for math-heavy communities (read more; related prior request: read more, and staff stance quoted there: read more)
The long-running “Indented Subcategories” theme component thread saw fresh activity (a post was removed by its author), a reminder that even mature components still get maintenance/cleanup moments (read more)
A debugging thread on an iOS Chrome back-button bug (tagged mobile) homed in on language/translation factors: NateDhaliwal asked whether it only occurs when the interface language isn’t English, and later replies suggested it may actually be Chrome’s page translation interacting with Discourse navigation/history state (read more, read more, read more)
A theme component conflict: enabling a user directory/user card component (tagged user-card-directory) reportedly breaks infinite scroll with this.model is undefined / loadMore errors, preventing loading past the first page of users (read more)
After an “update all,” one admin saw a mix of errors: apparent stale-tab asset issues (Propshaft missing chunk JS) plus a separate reactions-related backend NameError; the thread suggested rebuilding from the command line and separating “old tab” fallout from real runtime regressions (read more, read more, and the linked reactions error report: read more)
A new regression report: NameError (uninitialized constant ReactionsSerializerHelpers) when loading topic posts (tagged reactions), with Ethsim2 also linking a fix via PR and narrowing the failing load/constant initialization order (read more, read more)
Compatibility edge case: enabling nested replies and post voting together (tags nested-replies + post-voting) and converting a post to nested view triggered a 500 error (undefined method 'post_number' for nil), with early suspicion that the features aren’t compatible yet (read more, read more, plus the nested replies intro reference: read more)
An “Approval button on user’s profile” bug investigation continued, including a striking scenario where an old deleted/spam account’s history appears to have influenced a new user who later received the same numeric ID, echoing an older Meta report about deleted user info leaking into approvals (read more, read more, older related report: read more)
#Nested Replies Testing
In ongoing nested replies experiments, participants asked about disabling machine translation UI (e.g., missing the “文A” button in nested mode) and how to “catch everyone’s attention” in threaded contexts when you need to redirect a conversation (read more, read more)
#Community Building
In a “new community” thread, dax clarified that Meta isn’t the right place to run functional tests or promote trial sites, recommended using the official demo environment, and asked users to avoid unsolicited PM outreach for testing workflows (read more)
Falco responded to the reply-order/cultural UX feedback by pointing out the existing timeline/scroll affordances and highlighted that the nested replies feature is designed for alternative reading flows (read more; nested replies testing context: read more).
dax posted a moderation/community-process clarification reminding folks to keep Meta focused on support and discussion (not external testing/promotion), and directed experimentation to the official demo site (read more).
If yesterday was any indication, tomorrow will involve at least one more deep scroll, one more tricky serializer constant, and at least one beautifully rendered KaTeX title.
emoji… “More…”