merefield rolled out Kanban support for Discourse Workflow with drag-and-drop lanes, keyboard moves, and overdue indicators in his huge update and detailed the GitHub PR.
Supportkgreed wondered how to hide public details about who liked their post, and Canapin along with Moin explained the “Hide my public profile” preference and site settings like default hide profile and hide user profiles from public. read more
Supportstephtara reported that updating an existing link in the composer replaces custom link text with the topic title, prompting ToddZ to suggest using Markdown or a custom component to preserve link labels when changing destinations. read more
Supportlong was puzzled why a calendar shortcode didn’t surface event creation options, and nat and nathank guided them to use the “Create event” action in the OP composer rather than the per-reply [@calendar] syntax. read more
UXSteradiant requested quick toggles between the public badge pages and their admin configuration, and stephtara linked this to broader quality-of-life improvements around Trust Levels and group privileges. read more
UXnewbit1337 noticed that re-sent invite emails dropped the “arrive at topic” subject and body details, and JammyDodger confirmed the UX discrepancy before moving the discussion to UX for a fix. read more
UXstephtara flagged that the term large_icon in the Logo & Icons admin UI is unclear, leading nathank and Moin to locate the relevant datetime_formats and month_names strings in Crowdin and propose translations updates. read more
FeatureNoble_Fish proposed a unified interface for customizable keyboard shortcuts, aiming to resolve conflicts like Ctrl+F vs site search and accidental Ctrl+Enter, sparking debate over per-site defaults and user exports/imports. read more
Featuremarkersocial asked for an API endpoint to delete uploads, observing that only “create” is available in the scope settings and suggesting a custom automation as a potential workaround. read more
Featurenathank outlined a case for allowing admins to edit and activate changed email addresses directly in /admin/users to avoid Rails console workarounds, echoing a common self-hosting pain point. read more
#Translationsstephtara discovered that published page dates appear as “month/day” in French instead of “day month,” and Moin mapped out the site text and Crowdin files (datetime_formats, month_names) for correction. read more
#Translationsstephtara questioned why the English menu reads “Page Publishing” instead of an active “Publish Page,” and ToddZ and Moin compared it to German “als Seite veröffentlichen.” read more
#Self-hosting supportRicardo_Viteri explored how to archive a decade-old Discourse forum into a static site to cut hosting costs, and Canapin pointed to archival tools that may require community maintenance. read more
Pluginelmuerte introduced Discourse Indisposable Email to block disposable addresses via multiple external validators, warning about false negatives and recommending redundant service configurations. read more
Plugin in a longstanding thread, Heliosurge praised the experimental Resenha voice rooms plugin while Falco noted missing UI elements and suggested tagging it experimental. read more
How to publish my theme component publicly: ClickandPledge wanted to share a Theme component in Theme component but found it read-only; chapoi explained that you must join the theme_authors group to publish and linked the docs. read more
Changing the default homepage to a specific category: Jesse_Starks asked how to redirect logged-in users to a chosen category instead of the latest feed; Moin showed how to reorder the top menu setting or use a custom homepage component. read more
How do I disable the hot feature?: Jesse_Starks didn’t want “hot” post labels on a small community; darkpixlz and Jesse_Starks removed the hot category and top-nav link in the Horizon theme. read more
Registration for non-Facebook Users: shortmort37 needs must_approve_users globally but allow auto-approval for Facebook signups; the community discussed plugin options. read more
Request to Verify Admin Rights for Discourse API Key: Apoorva_Johari asked why their API key can’t fetch group permissions; NateDhaliwal pointed to scoped-key docs and pfaffman recommended the Data Explorer for reports. read more
Calendar on top of category shows events, but embedded calendar doesn’t: Lou was puzzled why [calendar] in a post behaves differently than the category header calendar; HAWK confirmed topic calendars and category calendars are distinct. read more
Admin user export does not work in subfolder setup: RGJ reported the short-url export link 404s under a subfolder; zogstrip merged a fix in PR 37996. read more
Group filter includes deleted posts: Moin noticed deleted topics still appear in group: filters; zogstrip addressed this in PR 38000. read more
Open Channel action on Archived Channel triggers Close Channel modal: lindsey flagged that archived chats still show “Open Channel,” which opens the wrong modal; sam suggested hiding the button. read more
Links not opening in a new tab: long set the external-link target to _blank but links kept replacing the current tab; HAWK asked about personal preference overrides. read more
Minor edit on first post creates revision despite grace period when tagging is enabled: sam confirmed this is a regression after the tag refactor; isaac fixed it in PR 37989. read more
#Self-hosting support
Is it safe to upgrade pgvector to 0.8.0 before running migration?: Andrés_Tarrío asked if Discourse 3.4.5 is compatible with pgvector 0.8.0; Falco confirmed it’s safe for hosted PostgreSQL services. read more
All IPv6 IP addresses show up as 172.17.0.1: pfaffman found Docker’s default proxy caused evicted IPv6 addresses in logs; setting "userland-proxy": false in daemon.json resolved it. read more
GIF always shows the first frame when paused: Noble_Fish asked for consistent pause behavior; sam said precise pause requires manual rendering via Canvas and recommended using MP4 for perfect frame control. read more
Show create tag form to all users who may create tags: Sunilkumar wants TL3+ users to see the tag-creation form; chapoi questioned the use case and default admin assignment. read more
After 105 new posts and 16 fresh topics—plus a slew of bugs squashed and features refined—it’s safe to say meta.discourse.org never sleeps (and neither do our bookmarks).
Announcements Admin Reporting & Analysis: Incremental Changes — chapoi introduced the first step in reworking the admin dashboard, grouping reports into Engagement, Traffic, Members, Content & Health, Moderation, and Security, while also cleaning up unused charts read more and see the Admin Dashboard Report Reference Guide.
UX Why are “Required” and “Enum” hardcoded in AI tool parameter configuration? — Moin spotted non-translatable labels in the AI Tools UI, and zogstrip promptly merged a fix to make those strings translatable topic.
UX Long-press l to react with an emoji instead of a regular like? — Canapin proposed a long-press on l to open the emoji selector, igniting discussion on keyboard shortcut conventions read more.
Bug [Resolved] Search “in this topic” checkbox seems to be lost after the last update — small-lovely-cat reported missing in-topic search on mobile, and Canapin confirmed its presence with screenshots in the mobile view update.
Support Links not opening in a new tab — long and NateDhaliwal investigated external link behavior, and long shared a theme component snippet that forces target="_blank" and rel="noopener noreferrer" on outside links details.
#Self-hosting support Error on login page about SMTP server not being configured — R23D_Printing saw a banner stating email was disabled despite successful tests, and community members guided them through the Google Workspace SMTP relay setup.
#Self-hosting support Problem during ./launcher rebuild, Redis not starting the second time — Wanderer shared a rebuild failure due to a lingering Redis process; a community-supplied pkill redis-server hook in app.yml ensures reliable rebuilds read more.
Support Send New Users to Topic After Confirming Registration — long wanted to redirect newcomers post-confirmation; Moin examined the default flow and SSO implications, sparking deeper discussion about the wizard UI and possible site-setting solutions topic.
UX Field alignment issues in LLM cost configuration in German — Moin observed that longer German labels misalign input fields in the AI cost settings interface, highlighting the need for improved multi-language UI support discussion.
blog Elfsight: How a Wishlist Category Shaped 700 Feature Releases — The system post showcased Elfsight’s no-code widget roadmap and how community-driven wishlist discussions powered hundreds of releases read more.
UX Error popup when suggesting tags in topic already having tags — NateDhaliwal and Canapin debugged an unexpected popup during tag suggestions on already-tagged topics and weighed whether it qualifies as a bug conversation.
Support iPad – Composer peek mode button causes editor to go off screen — Jesse_Starks reported a UI glitch in peek mode on iPad, prompting multi-browser tests but no fix yet issue.
Volunteer Moderators introduced Danielle introduced the Volunteer Moderators program, outlining their stewardship role in keeping Meta organized without staff-level permissions.
Discourse Age Check RGJ released the Discourse Age Check theme component to verify user age on signup, sparking GDPR compliance discussions with awesomerobot’s insights.
#Announcements
Discourse Free plan beta rishabh invited community members to trial the Discourse Free plan beta, igniting conversations around feature limitations and self-hosting options.
Foundation theme modernization
Discussions on streamlining the #Foundation theme continued as manuel reviewed theme updates in Canvas Theme Template ahead of the modernized defaults.
Docs sidebar behavior stephtara raised UX concerns about disappearing admin links in Discourse Doc Categories, leading ToddZ to suggest CSS tweaks for a distinct crawler layout.
#Feature
Upload deletion via API markersocial explored automated workflows for removing uploads through endpoints outlined in Upload Deletion via API, with RGJ pointing to the Legal Compliance plugin.
Automated feed integration JeroenR introduced a Paid feed integration service for RSS, XML, and YouTube feeds, highlighting custom templates and high-frequency polling options.
With volunteer mods on patrol and themes being tweaked, it’s been a pupperiffic day—here’s hoping your notifications are as well-behaved as those new volunteer moderators!
Meta’s category re-org continues to iterate (meta-redesign-2026): mcwumbly explored whether “category groups” might work better than parent categories, and shipped tweaks like restricting posting in container categories and improving subcategory discovery (including “boxes”)—with ongoing debate about above-the-fold topic visibility on tablets. See the latest checkpoint update read more, plus the “category groups” direction via the existing theme component idea read more and prior context on admin UX friction like multi-tag setup read more.
Volunteer moderators program: messaging visibility + “how do I join?” Meta’s new volunteer initiative moved forward as Danielle confirmed the @VolunteerMods group is now visible and messageable, and clarified that expansion will come later once the pilot stabilizes read more.
New tagging request: track accessibility palette-specific issues: Moin proposed adding a dedicated wcag-palettes tag so palette-specific bugs (especially contrast/visibility) can be triaged more easily read more. (The tag was subsequently created and applied to example topics read more.)
Should unlisted topics appear in “Related”? A discussion popped up around whether unlisted topics should be excluded from the “Related” panel the way they are from search results, to reduce noise during research workflows read more.
Heading hierarchy in the composer (H1 vs H2 vs H3) meets accessibility reality: A thread on proper heading levels dug into SEO myths and screen-reader structure (including the surprising hidden heading structure per-post), with suggestions to hide H1/H2 buttons and standardize on deeper headings for content read more. Related historical context: “disable headers in replies” read more and the evergreen formatting reference guide read more.
Migration sizing question: 800k topics and 12k DAU: A large-scale migration inquiry asked whether Discourse needs special architecture at that size, and what “enough server” looks like beyond RAM numbers (pageviews were the next key question) read more.
Gate a marketplace category until someone “likes” the rules topic (automation): A self-hosted admin explored how to require a “rules acknowledgement” (via like → badge → group → permission) before granting posting rights in a Buy/Sell/Trade category read more, with a possible alternative approach using Discourse Policy workflows mentioned for comparison read more.
Free-plan polish: hide digest UI that’s not available (free-plan, activity-summary): A UX paper-cut where the digest controls were visible on the Free plan (even though the feature isn’t) was addressed, adding upgrade messaging and removing confusion read more.
User cards opened from the like list jump to the top-left (user-card): A repro GIF shows user cards snapping to the page corner after opening from the like-list avatar, suggesting a positioning/hover edge case read more.
Subcategory navigation friction: finding subcats in the topic-list dropdown (meta-redesign-2026): Continued feedback on how people discover and drill into subcategories during browsing, especially when hierarchy grows and “direct access” matters read more.
Make inline links to subcategories less… gigantic? (meta-redesign-2026): Following on from the category re-org, a new UX thread proposes improving how subcategory links render inline so they read more naturally in sentences read more.
Content localization toggle has no visible “on/off” state under WCAG palettes (content-localization, wcag-palettes): A report shows the translation toggle’s state is effectively invisible when high-contrast palettes are enabled—an issue that becomes clearer once you compare prior UI behavior and palette constraints read more. Background: WCAG palette feature reference read more and related palette-visibility reports like quoted mentions read more and icon visibility in menus read more.
RTE quoting attribution shows full name instead of username (composer): A bug fix landed after root-cause work, resolving quote attribution behavior in the rich-text editor read more.
Upcoming Changes UI: “staff enabled” state not reflected after reload (translation, upcoming-changes): A repro indicates the saved value can be "staff" while the UI select expects a literal group name (e.g. “Team”), causing the dropdown to fall back and display “no one” after refresh read more.
#Self-hosting
SMTP not configured warning appearing on login (regression found + fix queued) (email): A self-hosting report was traced to a regression, with a fix identified and linked for upgrade/rebuild guidance read more.
Dashboard confusion: “Latest” version equals “Installed”: A version-check endpoint issue was corrected after a semver formatting hiccup (“leading zeros”), and the discussion hints at future UX improvements for versioning clarity read more. Related self-hosting troubleshooting threads that stayed active: external proxy SSL detection gotchas read more and reverse-proxy setup notes for Caddy read more.
mcwumbly continued hands-on iteration on Meta’s category structure experiment—balancing container categories vs. “postable” parents, and improving discovery mechanics (like showing subcategories) read more. They also created the requested wcag-palettes tag for better triage read more, and spun off follow-up UX discussion about subcategory link formatting read more.
Danielle advanced the Volunteer Moderators rollout by enabling visibility/messaging for the group, and clarified the “pilot first, expand later” path read more.
rishabh clarified why Discourse ID must remain enabled on the Free plan (it’s the only login method there) and noted an update preventing admins from toggling it off read more.
tgxworld identified the regression behind the SMTP warning-on-login problem and linked the upstream fix PR for affected self-hosters read more.
zogstrip credited good root-cause analysis and shipped a fix for the RTE quote attribution bug (full name vs username) read more.
keegan addressed Free plan UX by hiding digest controls where they aren’t usable and adding an upgrade indicator read more.
Falco confirmed the renamed anonymous-search rate limit setting (rate_limit_search_anon_global_per_minute), helping unblock admins tuning defenses against automated search spam read more.
chapoi completed dashboard/reporting polish (alphabetical sorting that respects UI language) and dug into feedback about report deprecations and why certain “anti-gaming” reports matter read more and read more.
awesomerobot advised using admin permalinks to preserve SEO equity when merging topics (301 redirect via /admin/config/permalinks) read more.
david fixed the “latest version” display confusion caused by a semver edge case, and noted that the dashboard currently shows released versions only (with planned UX improvements) read more.
If yesterday taught us anything, it’s that Meta can debate category boxes above the fold with the same intensity it reserves for whether your post headings should start at H2… or H3.
“Part of good design is also daring to prune away things.” — chapoi (read more)
Interesting Topics
#Site feedback
NateDhaliwal noticed the Meta Branded theme shifting (notably purple accents, rounded controls, and a new font), and manuel confirmed this is part of aligning Meta with updated brand guidelines (including the important caveat that these brand choices aren’t intended to be user-adjustable) read more. Related: the broader rollout plan in Updating Meta’s theme and structure (meta-redesign-2026) read more, and the “themes restricting color schemes” gap (including discussion of #TargetableColorSchemes) read more and the “override selected palette” confirmation read more.
#Extras
A new OpenClaw integration plugin was announced, enabling agents to read/search/filter and optionally create/reply to topics, with Bas urging strong defaults and clear labeling whenever AI writes content read more. (It builds around “find unanswered questions” workflows) read more.
#Self-hosting
A “404 Not Found” during console install turned out to be a subtle URL typo (discourse-docker vs discourse_docker), and the thread also clarified why the documented wget -qO- ... | sudo bash matters for expected behavior read more.
Folks hunting for “Form Templates” learned the feature is no longer just a hidden experimental setting; it’s now managed via Admin → Upcoming Changes, as renato explained (and this also prompted a call to update older announcement/docs) read more. Related references: the original announcement topic (form-templates) read more and the central Upcoming changes page read more.
A deep dive into “Request Revision” highlighted a confusing moderation flow where a rejected first post + user silencing can leave the author unable to respond or iterate, prompting comparisons to UX ideas in Allow the ability to Edit post on rejection (review-queue) read more and the linked UX brainstorm read more.
A new bug report shows the Styleguide page can crash for anonymous users when “Styleguide allowed groups” is set to everyone, due to a missing admin component import (discourse/admin/components/highlighted-code) read more.
A small-but-annoying UX issue: the sidebar wrapper blocks clicking the logo (home navigation) on Foundation/Meta Branded themes, with screenshots showing the click target being covered read more.
#Translations
Missing translated strings cropped up again post-release; gerhard traced it to Crowdin not returning all translated strings and said he’s investigating to restore them ASAP read more.
On whether Discourse should “nudge” large third‑party instances with serious UX problems, chapoi noted outreach is rare unless things are truly dramatic—and community members pointed out safe mode as a practical workaround to bypass problematic customizations read more.
#Migration
A migration planning thread for 800k topics / 12k DAU continued: guidance emphasized that default search usually holds up at scale, while Falco flagged disk IOPS and DB caching as likely bottlenecks to watch (especially in the first month) read more.
#Community Building
A side conversation from an “age check” component spun into a focused GDPR thread on storing date of birth: the discussion centered on lawful basis, transparency, retention, and the idea that GDPR is about control, not a blanket prohibition read more. (The split was noted from the original theme-component discussion) read more.
#Site Management
A Discourse AI spam-detection troubleshooting post asked why a locally-created “spam” topic didn’t enter the review queue despite matching stated thresholds, and responders pointed to the built-in testing tool in /admin/plugins/discourse-ai/ai-spam for validating rule behavior read more.
#Feature
A small but meaningful GDPR-related request: exported data should include the Discourse post ID—awesomerobot said a PR is already open to implement it read more.
Clarification on hide_user_profiles_from_public: even if the UI redirects anonymous users away from /u, aggregated stats can still be visible via API; j.jaffeux framed it as “not airtight protection” and explained the tradeoffs read more.
WP‑Discourse “Path to your Login Page” confusion was resolved: the behavior was correct, but a third-party membership plugin (Memberium) was interfering—fixed temporarily via a custom WP plugin patch while awaiting upstream fixes read more.
manuel engaged heavily in the Meta brand refresh thread—confirming the brand alignment is intentional, acknowledging accessibility/comfort concerns, and explaining why Meta Branded currently conflicts with user color schemes (and why “restrict color schemes per theme” would be the cleaner long-term fix) read more and read more.
Falco added team perspective on the refreshed look (preferring it over the prior Meta Branded iteration) read more, and gave practical scaling guidance on migration hardware—especially around disk performance and early monitoring read more. Falco also chimed in on AI-assisted plugin development, stressing good local context and pointing to the in-repo AI agent guidance read more.
Bas responded to the OpenClaw plugin announcement with a clear moderation-minded plea: don’t let agents post unlabeled AI content, while endorsing “civilized defaults” like agent signatures read more.
renato solved confusion around Form Templates by pointing admins to Upcoming Changes, noting older announcement material needs updating to match the new reality read more (and reiterating the same in the original announcement topic) read more.
chapoi confirmed an iPad composer issue (peek mode pushing the editor off-screen) and said a fix is being investigated read more. chapoi also explained the rationale behind pruning admin reports in the reporting refresh—preferring observable feedback over indefinitely maintaining “extra” UI sections read more.
gerhard acknowledged the translation regression reports and indicated active investigation into Crowdin’s incomplete string returns read more.
j.jaffeux clarified the nuance behind hide_user_profiles_from_public, emphasizing it doesn’t fully block aggregated stats exposure through the API read more.
awesomerobot provided a crisp explanation for why the new Meta Branded theme appears to override chosen palettes (“theme overrides any selected color palette”) read more, and separately kicked off implementation work for adding post IDs to data exports read more.
Purple took center stage yesterday—may your buttons be rounded, your palettes intentional, and your feedback threads delightfully on-topic.
RGJ flagged that category mentions can trigger the “repeated link” warning (even when you’re just referencing something like bug), and argued category/tag mentions should be excluded from that prompt; discussion branched into category/tag name collisions and whether internal duplicates are ever helpful (read more).
Related: mcwumbly pointed at a “make subcategory links more concise” parallel thread (read more).
Moin noticed inconsistent opacity cues for hidden revisions (opacity applied to the “previous version” and also the right-side heading, but not the content) and asked whether the UI is behaving intentionally or accidentally (read more).
Luna_Mora reported a chat image viewer regression: after uploading an image, clicking it won’t open full-screen on first view until chat is toggled (mini/full) or the page is refreshed; reproduces across Chromium/mobile (read more).
Related older report that was believed fixed: read more.
The long-running iOS upload UX snag resurfaced: iPad landscape mode still makes file uploads painful in the iOS app, while Safari remains a workaround (read more).
Ethsim2 found that bulk-adding email addresses to a group may still send invitation emails even when “Notify users” is unchecked, raising the question of whether the invite flow for non-existing/staged users overrides that checkbox (and whether the UI is ambiguous or there’s a regression) (read more).
Related docs/discussion on invites: read more.
Jesse_Starks asked if there’s a querystring parameter to sort group members by last_seen_at descending (the view loads ascending by default); NateDhaliwal noted an asc filter in code but couldn’t get it working via URL (read more).
In a Chinese-language support thread, AkarinLiu shared a practical deliverability workaround: switching from Aliyun mail push to Brevo after Outlook delivery problems / IP rejection (read more).
#Migration
A large-scale migration thread (800k topics / 12k DAU) continued: jack222 confirmed they’re moving off a privately developed PHP forum system and reiterated why Discourse feels like a better long-term fit, sparking community encouragement around support quality and forward momentum (read more).
A Chinese-language Dev discussion on “AI dev skills” drew concrete field notes from Canapin: Claude can help build plugins, but minimal coding skill is still important, especially to catch security flaws; they linked both an AI-dev experience thread and a mostly-AI-written plugin they audited heavily before publishing (read more).
Related: AI dev experience thread (read more) and the “Topic Gallery” plugin showcase (read more).
Theme creation “best practices” got a +1 watcher: stephtara echoed they expect to hit similar issues and are tracking the thread for guidance (read more).
#Developer Guides
In the referencetheme-guides “Alternative icons” guide, Canapin asked how to find the complete set of icons used by core (noting missing mappings like palette), and Moin pointed to svg_sprite.rb plus suggested repo searching for registered icons—especially across plugins and included-in-core extensions (read more).
#Theme component
“Custom Header Links” support: a theme-component update error turned out to mirror an older Matrix URL issue; Moin suggested the permalink workaround and it solved raghukamath’s problem (read more).
Related prior report: read more.
#Plugin
In “Private Topics Plugin”, RGJ shipped a fix (noting the prior warning was harmless) after a report came in—quick maintenance on an established plugin thread (read more).
#Feature
OpenGraph improvements got a positive field report: shortmort37 said adding og:image:width, og:image:height, and og:image:type now integrates “quite nicely” with Facebook on the latest update (read more).
k4rtik requested a way to activate/confirm a changed email address from the Admin UI, specifically for staged users who only interact via email and where Rails console access isn’t available (read more).
Related personalization discussion: using first names (and even vocatives) in greetings instead of usernames (read more).
#Site feedback
Meta’s redesign feedback continued: NateDhaliwal reported a visual bug where wrapping tags onto a second line can clip the rounded corners due to the tag field’s rounding/overflow interaction (read more).
#Site Management
In the “Discourse AI - AI bot” how-to (aiai-bot), sam encouraged folks to open a dedicated topic with specific questions—confirming the feature is widely implemented, but troubleshooting is best handled case-by-case (read more).
Related AI ops thread: spam detection inconsistencies and testing conditions (e.g., mod vs new-user behavior) (read more).
awesomerobot weighed in on the “repeated link” warning + category/tag mention confusion, noting that a bug tag can still be useful in private subcategories, but also floated that it may be worth cleaning up since it’s not used much (read more).
mcwumbly supported cleaning up the overlapping bug tag, and cross-linked a related UX thread about making inline links to subcategories more concise (read more; related: read more).
sam replied in the Discourse AI bot how-to thread, confirming many sites are using it and steering follow-ups toward opening a dedicated topic with specifics for better support (read more).
Yesterday’s vibe: if you didn’t get a “repeated link” warning while debating the fate of bug and admiring shiny new icon sets, were you even on Meta?
Most active @team members: sam (12 posts, 4 likes) and martin (1 post) (see details in the @team section below).
Also getting attention (more threads to skim)
A few other conversations that picked up replies today: heading anchor behavior in Support (read more), reply-button CSS effects in Dev (read more), strengthening age-check workflows in #Theme-component (read more), category calendars vs embedded calendars in Support with calendar-and-event (read more), the “Dumbcourse” pagination discussion in #Plugin (read more), missing icons in “Alternative icons” in #Developer-Guides (read more), category icon styling help request in Support (read more), defaulting filters for Topic Status Filter in #Theme-component (read more), moderating plugin-collected feedback in #Plugin (read more), and a return to the perennial markup debate in #Feature (read more).
Interesting Topics
#Announcements
Discourse AI credentials go centralized.sam announced a refactor that moves all Discourse AI credentials (LLMs, embeddings, tools) into a central store—aiming to make tool distribution with secrets, credential rotation, and adding models significantly easier (read more; companion guide: read more).
#Site-Management
A deep-dive guide: “Managing AI credentials” (ai, how-to). The new documentation explains how credentials are created once and referenced everywhere (LLMs/embeddings/tools), including lifecycle protections and API management (read more).
Using Discourse AI to auto-move topics by timestamps (and whether AI is needed). In a rest-api + ai management workflow discussion, jdc20181 described moving “temporary ban” log topics after an expiration date, and sam suggested using topic timers (or core logging + Data Explorer access) instead of reaching for AI automation (read more; sam’s suggestion: read more).
Chat uploads: first image click not opening fullscreen (chat).sam asked for a re-test on latest after submitting a patch, implying the issue should now be addressed in current builds (read more).
Anonymous (and non-staff) styleguide crash.sam noted the issue impacts more than anonymous users and linked an upstream fix in core via a PR (read more).
“Upcoming changes” enablement error (translation, upcoming-changes).martin posted a fix link for the problem (via a core PR), unblocking admins experimenting with the upcoming-changes flow (read more).
Tag suggestion popup error when a topic already has tags (tags, ai).sam linked the core fix PR and reclassified it as a “bug” due to an obvious code flaw (read more).
Select-kit dropdown contrast problems (accessibility). In an accessibility discussion, BrettH traced “invisible text/icons on selection” to an older custom palette missing newer selected/hover colors, and suggested explicitly defining those colors (plus a thought: could future fallbacks consider text contrast?) (read more).
German UI alignment issues in LLM cost configuration (ai).sam flagged that 4 columns may be too cramped (even in English) and suggested restructuring the inputs into 3 rows for better spacing and layout resilience across locales (read more).
Will Discourse ever get pagination? (infinite scroll vs page numbers). The recurring pagination request resurfaced, with agemo asking for an admin/user option (read more), merefield pointing to the “Dumbcourse” plugin as an option today (read more; plugin: read more), and mcmcclur arguing pagination may become necessary—citing broader concerns about infinite scroll and addictive design patterns (read more).
NodeBB (MongoDB) → Discourse importer error: post is nil. While migrating from NodeBB 4.9.x, Twissell hit a crash in NodeBB::Mongo#post during post import (read more; output context: read more). pfaffman diagnosed the immediate cause—post is nil—and suggested the importer isn’t reading post data correctly (likely around key lookup / retrieval), while setting expectations that importer support is limited and may require deeper hands-on debugging (read more).
Error 500 when enabling plugins: “asset not found” + possible mounted-volume gotcha (hosting, unsupported-install).sistason reported consistent 500s on plugin activation with a Propshaft asset resolution error referencing plugins/discourse-translator.js (read more). RGJ noted those plugins work on 2026.1.1 for their clients and suggested the mounted docker volume to /var/www/discourse/plugins might be the culprit (read more). (Related translator reference: read more).
Sorting group members by “last seen” via querystring.Moin linked a prior thread for admins trying to force descending last-seen ordering when viewing group members—highlighting this as a repeat pain point (read more).
#Feature
Collapsible category calendar (calendar-and-event).Lou proposed making the category-top Events calendar optionally collapsed by default to reduce vertical space, ideally remembering user preference per category (read more). nathank echoed the usability issue and pointed to a related request around toggling calendars when browsing event lists (read more). (Context from the support side: read more).
When an AI model hits limits, fade it out + offer upgrade path (subscriptions, ai).sam responded with a broader product direction: reduce decision paralysis by moving toward a “just talk to the robot” experience where the system selects the best model automatically—while also questioning what “upgrade subscription” means in practice (instance plan vs admin configuration changes, etc.) (read more).
sam shipped/announced a major Discourse AI improvement: centralized credentials. The announcement frames this as solving long-standing tool distribution + secret management issues, and points to the new admin guide (read more; documentation: read more).
sam nudged an automation use case back toward core tools (timers/logs) rather than AI. In the “move topics by timestamp” thread, sam recommended using topic timers to auto-move topics after time passes, and suggested leveraging existing ban/log history via Data Explorer instead of custom AI flows (read more).
sam coordinated multiple fixes and follow-ups across bugs/UX:
Chat fullscreen upload fix: asked reporters to retry after a patch (read more).
Tag-suggestion popup bug: linked the core PR and called it a real bug (read more).
Styleguide crash affecting non-staff: confirmed scope and linked the fix PR (read more).
German LLM cost UI: proposed changing the layout to avoid cramped columns (read more).
sam set expectations (and offered a UX idea) on delayed NSFW scanning. While noting the feature isn’t supported yet, he warned about potential LLM costs from “upload-button playing,” and floated an “Awaiting content scanning” placeholder approach as a possible design direction (read more).
sam reinforced Meta’s bot policy in two related OpenClaw integration threads. He cited llms.txt and requested confirmation that the “skill” respects the rule that AI systems must not create accounts or post content (read more; Chinese-language counterpart: read more).
sam weighed in on “model limits UI” with a long-term direction: hide complexity for most users. Rather than surfacing upgrade prompts directly on model selection, he suggested moving toward a system that routes requests to the best model automatically, and asked clarifying questions about what “upgrade subscription” should mean (read more).
sam added practical guidance on tokenizers for AI models. He noted many coding agents simply estimate tokens, and that cl100k is “plenty fine” for most LLM use cases even with slightly different tokenizers (read more).
That’s a wrap: yesterday Meta managed to wrangle secret keys, tame a few bugs, and still found time to rekindle the eternal “pagination vs infinite scroll” debate.
In the last 24 hours:82 new posts across 14 new topics.
Much of the conversation clustered around responsive UX changes, AI/admin polish, and self-hosting ops questions—see discussions like AI credentials, responsive layouts, and hiding AI reports when disabled.
Lilly celebrated easier key rotation and model management after AI credentials shipped, and also flagged a mobile layout hiccup; derek followed up with a mobile stacking fix in the same announcement thread (read more).
A key shift toward width-based responsiveness was confirmed in No more switchable mobile/desktop layouts?—featheredtoast outlined why the explicit toggle is going away (read more), while awesomerobot shared capability-aware template patterns to replace initializer-time device logic (read more).
The underline indicator below “Suggested” and “Related” tabs was reported as vertically misaligned; awesomerobot noted upcoming tab changes should address it (read more).
Admin setting UX got a spotlight: Site settings with “Search or create…” that don’t search argues the hint text is misleading when entries require exact manual keys (great companion to dashboard docs discussion in Admin dashboard report reference guide) (read more).
RTL polish request: External link icon not RTL flags a directionality issue when using featured links in titles (read more).
A subtle styling inconsistency in moderation history UI was diagnosed: Understanding opacity in hidden revisions appears to be caused by fragile CSS selectors, with a fix moving toward explicit class targeting (read more).
Don’t show AI reports if AI is not enabled: emotion/admin AI reports still appear even with AI disabled; sam confirmed it’s a bug and agreed they should be hidden when AI is off (read more).
No indicator whether content translation is enabled or not: missing/unclear UI affordance was acknowledged, with an update queued to improve it (read more).
Chat image not opening full screen appears resolved—Luna_Mora reported the latest patch fixed the issue in testing (read more).
#Feature
Saving translations by AI-helper as content localization proposes letting moderators save an AI-helper translation directly into localization (mirroring the AI-helper “explain” workflow that can add footnotes) (read more).
Custom User Field Required for All, but only Editable ONCE highlights a tricky onboarding gap for OAuth/SSO signups and proposes “editable-until-filled” logic so “required for all” fields can be locked after first completion (read more).
Calendar UX feedback continued: Collapse category calendar asks for an on/off or collapse control because the current always-on display affects both visuals and usability (read more).
Size restrictions on videos? asks what levers admins really have for self-hosted screencast uploads beyond extension allowlists and max upload size settings (read more).
Recommended fail2ban configuration? surfaces a common “is apt install fail2ban enough?” question—useful for admins spotting the mention in official install docs (read more).
#Self-Hosting
Docker compose addition: featheredtoast clarified there’s still no officially supported compose template, but shared a maintained personal template for those who want to experiment (read more).
Falco published a companion discussion for Three Ways to Deploy AI in Community Platforms (and Why Choice Matters), arguing communities need flexible AI integration approaches rather than a single hardcoded provider path (read more).
chapoi continued tightening admin reporting UX by adding clearer units/labels to charts in Units for reports, and pointed feedback back toward the ongoing umbrella thread referenced there (read more).
Yesterday’s theme: make it responsive, make it clearer, and make sure the AI bits behave themselves—now if only every underline indicator could stay perfectly aligned while your folding phone unfolds.
