Moin noticed tag pages suddenly looked “empty” because tags weren’t appearing in tag banners; awesomerobot confirmed it was caused by a data-availability change and shipped a quick plugin-side fix—already restored on Meta. read more
A Category Experts plugin crash during CLI user merges was traced to a validation failure; zogstrip linked the PR that fixes the plugin so merges won’t require disabling it first. read more
Self-hosters reported Cloudflare R2 backups failing on multipart upload with aws-sdk-s3 1.182.0 (undefined method 'downcase' for nil); pfaffman shared a proven pinning workaround, and the OP confirmed it solved the issue. read more
An intermittent but nasty iPad Safari composer jump-to-top (breaking upload buttons and resizing) was reported; after a bit of testing, the issue stopped reproducing for the reporter—still a useful breadcrumb if others see similar behavior. read more
A report flagged German translations injecting “AI commentary” / thought-process-like text into UI and even cross-language post viewing, raising concerns about translation quality and tone. read more
Enforcing 2fa can lock users onto security preferences without access to “how-to” guidance; supermathie pointed to customizing the relevant site text, and awesomerobot provided a theme-component approach to inject richer HTML/help content above the enforcement UI. read more
A site with an all-numeric tag found old-style /tag/6309 URLs returning a 500 instead of a clean 404/redirect—bad for crawlers and user experience; discussion centered on falling back more gracefully (or detecting numeric tag names). read more
The long-running question of what the “homepage” should be for doc categories got new traction: nickrsan explored adding a redirect-to-index option, but found a larger plugin rework underway and suggested integrating the idea there. read more
In the ongoing “let users control AI” thread, paco argued for a per-user discourse_ai_enabled equivalent so people can opt out of AI features even when site-wide AI is enabled. read more
#Announcements
lindsey announced a quality-of-life improvement for solved workflows: users Tracking/Watching topics in support categories now get notified when the topic is marked solved, with a preference toggle for those who want it off. read more
Feedback continued on embedding Discourse as a full comment system (embedding): Tris20 highlighted discoverability issues (the scrollbar and “reply” affordances), and mcmcclur worried some UI elements may now be too subtle (including missing timeline context). read more
The calendar-and-event subscription announcement thread surfaced a potential regression: an existing install no longer shows events in posts, suggesting a plugin-migration-related issue rather than the subscription URLs feature itself. read more
#Feature
A long-requested i18n nicety landed: emoji search now supports English and localized aliases, and in the process a bug fix trimmed the emojis.json payload by ~160KB. read more
More content-localization + tag UI polish: Moin asked for tag icons to appear correctly for translated tags in tag/category banners, after noticing parity gaps between English and translated tag displays. read more
Continuing the localization + tag UX theme, discussion on the tag icon component asked to support translated tags more completely, including in dropdown menus where some translated variants still don’t render as expected. read more
Support / Dev / #Theme_component (worth a quick look)
A hosted-support question: category-level moderation isn’t triggering the post_needs_approval email, even though posts correctly land in the review queue—admins are looking for a per-category solution without enabling global moderation emails. read more
Design/dev enablement: a user asked where to find Discourse design resources, and the accepted answer pointed them to enabling the built-in styleguide on their instance (plus a nudge toward Documentation > Developer Guides). read more
awesomerobot responded quickly to the missing-tag-banner regression, identified the upstream change that affected available data, and confirmed the fix was merged and visible again on Meta. read more
awesomerobot also provided a practical, copy/paste-ready solution for improving the locked-down 2fa enforcement experience via a theme component and renderBeforeWrapperOutlet, enabling admins to add links and richer guidance. read more
lindsey published the announcement that Tracking/Watching users now receive solved notifications in support categories using the solved plugin, including the “Want to turn it off?” preference guidance. read more
supermathie helped unblock MFA-enforcement messaging by pointing admins to the exact site-text customization path to tweak the “required to enable” copy. read more
Falco closed the loop on localized emoji aliases, linking the implementation PRs and noting the performance win (smaller emoji payload) that came along for the ride. read more
Falco also chimed in on a self-hosting migration collision story with some levity (and confirmation they’d recently re-done a failing migration), keeping the solved thread moving. read more
nat followed up in the localization/tag-icons conversation, clarifying a translation shown was intentionally manual/wordplay on their own instance—useful context when evaluating translated-label behavior. read more
davidb pointed to the core change that resolves group dropdowns not refreshing properly after new groups are created, effectively closing the loop on that bug report. read more
zogstrip acknowledged the Category Experts merge crash report and linked the plugin PR that addresses it so admins won’t need to disable the plugin during merges. read more
Sign-off: Between tag banners vanishing and reappearing (read more), emoji payloads going on a 160KB diet (read more), and at least one migration “buddy” showing a surprising amount of personality (read more), Meta had one of those delightfully chaotic-yet-productive days.
“Boosts” reactions-with-text experiment landed on Meta.lindsey introduced the new boosts interaction layer (read more), with follow-up discussion digging into naming confusion, moderation/flagging behavior, and whether boosts should merge into reactions long-term (read more).
Related: ActivityPub confusion got clarified (read more) and “convert too-short replies into boosts” was debated (read more).
Embedding Discourse as a full comment system: practical UX questions keep rolling in. People discussed how embedded pages map back into Discourse categories and reporting flows (read more), plus feedback that infinite scroll can hide the reply affordance in constrained embed heights (read more).
Related: example reference to tag strategy from “It’s time we talked about tags” (read more).
#Site feedback
ask.discourse.com outage report → confirmed + fixed. A quick heads-up that Ask was unreachable led to a team acknowledgement and resolution (read more, then read more).
Related: UX polish request on Ask’s “Back to Forum” link placement (read more).
Meta “content gardening hub” thread: more process-oriented tooling ideas. The ongoing experiment thread continued with suggestions for surfacing topics that likely need a fixed tag (via a staff/PR-linked topic filter pattern) (read more).
Related: discussion that prompted the filter referenced Contribute workflows in bug/#UX contexts (read more).
Looking for Discourse communities about public transit / urban design. A member asked for a directory of transit-focused forums running Discourse, and got pointed to discover.discourse.org and a couple known examples (read more).
Related: discovery as an ongoing need connects well with the broader “directory” idea mentioned in the same thread (read more).
Mistral embeddings compatibility issue: “dimensions” vs “output_dimension”.RGJ reported that Mistral’s embeddings endpoint rejects the OpenAI-style dimensions parameter and that Discourse currently requires it for saving (read more).
Related: prior how-to context for Mistral embeddings configuration (read more).
Numeric-tag URLs throwing 500s at legacy paths (crawl/SEO impact). A report highlighted 500 errors when old-style numeric tag URLs get crawled, with confirmation that a fix is planned while keeping /tag/name resolution stable (read more).
Related: broader tag discussions often come back to URL stability and discoverability (read more).
Ask UI: hide “Back to Forum” on the homepage. A small but sensible UX tweak request noted that the “Back to Forum” link is redundant on Ask’s homepage and should only appear when actually “in” a conversation flow (read more).
Related: Ask’s availability incident from earlier the same day (read more).
AI-generated German translation pages had “Thinking/Translate”-style artifacts; cleanup + agent update deployed. The issue was investigated, a formatting-tightening update shipped, and affected titles/posts were cleaned up (read more).
Related: the referenced prompt/feature change that may have contributed (read more) and the deployed fix PR link cited in-thread (read more).
Hidden comments “reappearing” after user edits: clarification of intended moderation behavior. A moderator reported that hidden posts re-entered the timeline after edits, expecting an approval gate; replies clarified that once posted, edits can reinstate visibility unless the post is deleted or “request revision” is used pre-approval (read more).
Related: moderation workflow differences between approval queue vs public timeline were central (read more).
Featured Topics via API: where to fetch them. A question about a native endpoint for “featured topics” was answered with a pointer to /categories.json when category pages are configured to include featured topics (read more).
Related: this fits into broader REST API usage patterns for topic discovery (read more).
Mail receiver trouble with self-hosted email: SPF rejection example. A “me too” update on a long-running mail receiver thread shared a bounce log showing SPF fail/rejection after migrating away from Gmail to self-hosted mail (read more).
Related: email deliverability pitfalls continue to be a common ops theme (read more).
Filtering topic lists: yes, you can include plain text search terms in the “topic filter” UI. A question about filtering by arbitrary text (without jumping into full search UI) was answered: just type the words after other filters to constrain the topic list (read more).
Related: examples in the reference thread show mixed filter + text patterns (read more).
Bitnami + polls error (“NoMethodError”): install path matters. A report in Chinese showed a stack trace hitting the poll serializer; replies quickly suspected Bitnami packaging (long unsupported/deprecated) as a root cause (read more).
Related: “Bitnami installations are unsupported” doc (read more) and the Bitnami container deprecation notice (read more).
iOS home-screen push notifications for self-hosted: behavior, fragility, and security tradeoffs. The push-notifications thread confirmed iOS 16.4+ “add to home screen” push can work, but uncovered a surprising “wipe keys on logout” line and the privacy rationale behind it (read more, plus read more).
Related: the code line discussion referenced in-thread (read more).
#Plugin
Discourse Daily Challenges: repo access weirdness (404 for some users) led to moving to GitLab. In the daily challenges plugin thread, a GitHub “account flagged/held” scenario caused intermittent 404s for others, prompting a migration to GitLab and updated links (read more, then read more).
Related: another similar “repo disappeared” anecdote referenced QR shareables (read more).
Pushover plugin got modernized for current Discourse versions. A long-running notifications plugin topic received an update: the plugin was updated/modernized to work again on recent releases (read more).
Related: notification ecosystem overlaps with other push-notification discussions (read more).
New guide: auto-provision users when SSO is enabled (skip the signup interstitial). A documentation topic explains how to enable auth skip create confirm to silently create accounts on first external login, plus optional overrides depending on identity provider behavior (read more).
Related: foundational SSO setup via DiscourseConnect (read more), plus common auth plugins like OIDC (read more) and OAuth2 Basic (read more).
lindsey introduced the Boosts experiment and invited feedback on positioning, notifications, and use-cases (read more).
zogstrip clarified boosts are not meant to reorder posts (just “reaction-like” metadata) (read more), joined the naming discussion (read more), and flagged likely install-path issues in the Bitnami/polls error report (read more).
j.jaffeux explained the intended “interaction hierarchy” and hinted at a longer-term unification path for boosts/reactions/likes so communities can choose the right layer(s) (read more).
awesomerobot elaborated on the intent (“morale boost” style), confirmed boosts will be optional, and shared moderation notes (watched words apply; AI scanning is possible but not on yet) (read more, read more). They also responded to a public-transit community directory question (read more) and agreed to adjust Ask’s custom “Back to Forum” link behavior on the homepage (read more).
Bas acknowledged the Ask outage report and followed up with confirmation that service was restored (read more, read more).
nat confirmed the team had eyes on the numeric-tag URL 500 issue and reiterated the commitment to /tag/name compatibility (read more). They also shipped/confirmed an AI agent formatting fix and cleanup for German localization artifacts (read more).
Falco confirmed iOS home-screen push support expectations and pointed to a problematic implementation detail that may be causing fragility (especially around admin impersonation/logouts) (read more, read more).
featheredtoast added important context on why “wipe push keys on logout” exists (preventing notification previews on logged-out devices), and proposed exploring better session/user binding for push subscriptions (read more). They also modernized the Pushover plugin for current Discourse versions (read more).
Yesterday’s theme: Meta got a “boost” of its own—between rockets, restored Ask uptime, and revived notifications plumbing, the site spent the day leveling up how it pings and praises people.
RGJ, Ed_S, ToddZ and Canapin continued debating what “boost-worthy” content is—and how Boosts interact with character limits and reply-clarity—in Testing Boosts on Meta (including UI clarity concerns about “reply-to-the-post-above” behavior: read more)
A new anti-abuse integration plugin landed, using an external API to detect/block VPN & proxy traffic at registration/login (with caching + fail-open options) in ProxyTracer: VPN & Proxy Blocker
RGJ flagged confusing wording when abandoning an edit (button says “Discard”, modal asks “discard your post?” even with no changes), proposing “Cancel edit / discard edits” clarity in “do you want to discard your post ?”
A question about “turning off the composer panel” turned into guidance about rich-text vs Markdown mode and preview toggles in Toggling off the composer panel, with a pointer back to the rich-text/Markdown switch UX shown in the composer toggle topic
Falco also confirmed a straightforward localization improvement for Meta itself: Ukrainian and Russian are planned to be added to Meta’s language switcher in Please add the Ukrainian or Russian languages.
mcwumbly engaged with new plugin experimentation and asked the “is it used in production yet?” question on a multi-team workspace concept in Workspace groups.
If yesterday was any indication, today’s Meta vibe is: keep it minimal… unless you’re adding Boosts, workspaces, and VP9 detection—then buckle up.
In the last 24 hours (2026-04-05 → 2026-04-06), Meta saw 37 new posts across 6 new topics. Source range: topics and replies in this report (e.g. read more).
(Per-post highlights include Moin’s guidance on TL3 tuning in Support (read more) and elmuerte’s new Ko‑fi plugin announcement in #Plugin (read more).)
Ed_S asked how to data-drivetrust-levels tuning so TL3 promotion matches the community’s size, and Moin pointed to user-level requirement breakdowns plus Data Explorer queries for identifying “almost TL3” users (read more, read more, plus the referenced query thread: read more).
Meta’s own TL3 thresholds came up as a real-world example: mcwumbly shared that Meta reduced TL3 cap requirements (topics viewed cap and posts read cap) after analyzing query results, and discussed upcoming work to roll out future default-setting changes more transparently (read more, referenced analysis context: read more, and the quoted settings-change topic: read more).
In an automation / ai support question, RGJ confirmed that enabling “Include personal messages” means AI triage can scan DMs between regular users too—and asked how the reporter verified DMs weren’t being scanned (read more, original question: read more).
A French-language calendar-and-event support question asked for a “cancel event” workflow that notifies all registrants without manually addressing each user in a message (read more).
Following up on structured-data / SEO work, Richie reported Google Search Console still flagging a missing text field under mainEntity.suggestedAnswer even after updating to the latest build, referencing prior investigation and fixes (read more, prior bug thread: read more).
A Chinese-language thread continued troubleshooting why all traffic appears to come from Cloudflare instead of end-user IPs—discussion centered on constraints introduced by a control panel setup and whether simplifying the stack would help (read more, continuation: read more).
#Plugin
A new plugin drop: Discourse Ko‑fi integration by elmuerte adds donation/subscription syncing via Ko‑fi webhooks, with rewards like badges and group membership; follow-ups covered currency limitations and anonymization behavior (read more, caveats: read more, maintenance/PR discussion: read more, maintainer response: read more).
In the experimental Discourse Suggested Edits plugin topic, sam confirmed a requested capability is “not implemented yet” but will be added; discussion immediately continued into category selection expectations (read more, follow-up question: read more).
The long-running Locations Plugin support thread saw a report that category maps stopped rendering after updates; merefield responded by inviting sponsorship and offering to investigate (read more, response: read more).
In ProxyTracer: VPN & Proxy Blocker, Moin cautioned that Safe Mode won’t help with Ruby-only behavior and raised skepticism about plugin packaging choices; the plugin author updated docs with server-side disable steps and removed redundant theme metadata (read more, author follow-up: read more, Safe Mode reference: read more, related admin recovery reference: read more).
A “mystery overlay” report turned out to be a rendering artifact: wuyuan saw gray dots/lines in the bottom-left; after initial UI guesses, bryce explained it’s likely the sidebar fade gradient and provided CSS to disable it via --d-sidebar-footer-fade (read more, clarification: read more, staff solution: read more, related component reference: read more).
“Clearing advice doesn’t actually clear it”: ted shared a PR concept to make specific dashboard problem-check notices ignorable (with an overview/undo surface), so admins can manage checks more deliberately (read more, original UX complaint context: read more).
A regression tied to the “simplified category creation” upcoming change: Moin reported that re-parenting categories/subcategories can silently reset category security permissions (re-opening posting to everyone); mcwumbly confirmed it looked familiar and that the team would dig in (read more, response: read more, referenced upcoming change: read more).
#Announcements
The ongoing “Testing Boosts on Meta” discussion continued with feedback about how boosts vs likes/reactions should communicate community value—Canapin argued boosts may be more “guestbook” than “signal,” and suggested visibility differences for authors vs readers (read more, Canapin’s perspective: read more, topic root: read more).
#Site feedback
In the “collaborative content gardening hub” experiment thread, Moin noticed category descriptions and/or restrictions no longer matched reality for plugin/theme posting, and mcwumbly connected it to category re-parenting permission loss—linking it directly to the new security-reset bug report (read more, staff reply linking bug: read more, cross-link to bug: read more).
A localization request thread about adding Ukrainian or Russian languages continued, with Denis_Kovalenko asking which translation model might be used as the request progressed (read more, thread root: read more).
#Self-hosting
In a solved “plugins not functioning due to CORS” thread, TomoftheFog added a new symptom: some users can’t see avatar images when the Preformatted Text markdown button tries to load highlight.js and hits a CORS failure—flagging it for others in case it’s related (read more, thread root: read more).
In “How minimal is your forum?”, Ed_S reflected on tag value (SEO vs maintenance burden) and how permissive tag creation at TL2 may contribute to tag sprawl—then spun that into a deeper TL3 threshold question (read more, follow-on TL3 tuning topic: read more).
A previously opened support topic about “official components” breaking after an update was confirmed resolved by Stephane_Roy, serving as a quick “good news” datapoint amid other upgrade-side effects (read more).
mcwumbly engaged in Support to share Meta’s real TL3 requirement adjustments (notably reduced cap values) and to discuss improving how Discourse communicates/rolls out default site-setting changes (read more). He also acknowledged and connected reports of category permission loss after re-parenting, both directly in the bug report (read more) and while replying in the content-gardening experiment thread (read more).
bryce jumped into ux to diagnose the “bottom-left overlay” as a sidebar fade gradient artifact and provided a targeted CSS workaround using --d-sidebar-footer-fade (read more).
sam replied in the #Plugin area on the experimental suggested-edits effort, confirming a requested feature isn’t built yet but is planned (“will add”) (read more).
If yesterday proved anything, it’s that Meta can debate boosts vs likes while simultaneously chasing down mysterious gradient dots—peak Discourse multitasking.
A new theme component announcement promises rich hover previews for internal topic links, with chapoi immediately requesting a clearer preview (screenshots / demo) in Topic Hover Cards
Troubleshooting the official sidebar theme toggle: awesomerobot helped narrow down why the sidebar wasn’t showing (including confirming user-selectable themes are enabled) in Sidebar Theme Toggle (officialsidebar)
#Plugin
A new “lightweight moderation” concept landed as a plugin: “mini-mods” can manage categories/tags/topics without full moderator power, described in Discourse MiniMod
The long-running ratings plugin thread resurfaced after functionality “vanished” due to widget/component changes; a fix PR was proposed and RGJ noted a modernized fork underway in Topic Ratings Plugin (pavilion)
Meta’s own information architecture is under review: mcwumbly asked what “community-building” discussions should look like (and whether category restructuring is helping or hurting), kicking off a broader direction-setting thread in Encouraging discussion about building and managing communities
chapoi requested better previews for a newly-published theme component in Topic Hover Cards, and clarified Horizon’s current compatibility priorities (and constraints) in Horizon Theme.
manuel continued the ongoing icon set housekeeping conversation, pointing folks to the official lucide set and suggesting documentation/first-post updates in Alternative icons.
Yesterday’s vibe: may your semicolons stay safely inside quotes, your RSS feeds actually honor exclude_tag, and your nested replies keep their shiny new Pin button.
Provided detailed theme/icon UX feedback in Meta Branded theme rebuild (icon mapping, small glyphs, click targets).
A visible through-line today: UI polish (icons + theme), “findability” improvements (bookmarks), and the perennial balancing act between platform evolution and downstream stability (deprecations). See: Meta theme rebuild, Easier access to bookmarks, and Deprecating .hbs.
Interesting Topics
#Site feedback
manuel shared a deep dive on the second iteration of the rebuilt Meta theme—new implementation, Lucide icon adoption, palette restrictions, and early direction-setting around customization (and “Blocks”) in Rebuilding the Meta Branded theme. Follow-up feedback covered icon mapping gaps, tiny list icons, and a desktop click-target overlay issue for the logo in post 8 and post 9.
#Theme component
The icon work spun out into a dedicated, installable component: manuel published the repo + install guide for Discourse Lucide Icons, while early testers flagged confusing glyph metaphors (e.g. reply/back-jump reading like “share”) in post 4. Related context: the older “where to find icon sets” discussion in Alternative icons.
Boosts feedback kept rolling in, with concerns about visual noise and UI density in Testing Boosts on Meta and even “reactions to boosts” as a half-joking extension idea in post 65. (Related feature UX suggestions appear in the standalone request below: Some ideas about discourse-boost plugin.)
#Feature
A practical mobile UX request for Boosts: fold/compact long boost lists and consider adding easier “quote/reply” affordances, discussed in Some ideas about discourse-boost plugin with chapoi suggesting consolidating into the main boosts feedback thread in post 5 (tying back to Testing Boosts on Meta).
Bookmark indicators on mobile sparked an unusually nuanced semantics debate: should the topic-level bookmark glyph change if only some posts are bookmarked? See the UX back-and-forth in Unable to tell bookmarks exist in footer on mobile, including sam’s “users don’t care about the nuance” framing in post 17 and chapoi’s preference to keep topic-bookmark meaning strict in post 10. (The overall feature announcement context is in Easier access to bookmarks.)
Deprecations hit a nerve: LeoDavidson described the maintenance burden and intent to stop maintaining plugins in Deprecating .hbs file extension in themes and plugins, with david outlining “deprecations + upgrade paths” rationale and a responsible archival approach in post 14. The parallel thread for JS filenames includes david’s justification focused on tooling and education in Deprecating .js.es6.
Localization surfaced two separate issues: anonymous users seeing mixed-language title/body behavior when using ?tl= in Localisation bug for anonymous users with ?tl=, and logged-in users frustrated that translation-disable doesn’t persist across devices/time in User disables translations, but they keep coming back (with nat clarifying current “local storage for 30 days” behavior and proposing persistence in user settings in post 2).
POP3 polling reliability: a site operator considered daily restarts as a workaround for sporadic inbound email pickup, but the thread ultimately pointed to the POP3 server error and recommended direct delivery instead in Auto-restarting once a day via cron? with the direct-delivery guide linked in post 2. Related earlier context was referenced from Discourse stopped polling my pop3 server (read more).
Falco jumped into calendar subscription UX limitations with the key question—“how can we do that programmatically?”—in The webcal URL is incorrectly passed…, helping steer the discussion toward what’s actually feasible in ICS generation.
Sign-off: Between Lucide strokes, bookmark hopscotch, and Boost-related “visual noise” debates, Meta spent the day doing what it does best—turning tiny UI details into tomorrow’s improvements.
Event creation flow continues to be a friction point; the team acknowledged active work (but no ETA) toward simplifying the event creation pathway in Single click activation of the Create Event modal.
Split-topic “small action” posts display link text based on a title snapshot, prompting discussion about whether those action posts should auto-update when titles change in Link in “Split this topic” mini post.
A self-hosted admin-facing failure tied to Git operations (“Gitutils.try_git”) appeared for a China-hosted install, with discussion focusing on templates/versioning/rebuilds in Gitutils.try_git报错.
#Site feedback
Meta’s official plugin topics may be showing outdated hosting-tier availability banners (and even outdated tier names), prompting a needed audit of the boilerplate across plugin topics in Inaccurate plugin availability notes on meta.
If yesterday had a theme, it was “tiny UI cues, big usability wins”—may your bookmark icons be legible, your calendars properly named, and your ampersands forever unescaped.
In the last 24 hours, Meta saw 79 new posts across 11 new topics, with conversations spread across active threads like Boosts feedback and a deep-dive infrastructure write-up on backups and uploads (read more).
Self-hosters continued chasing tricky edge-cases like S3/CDN interactions and broken codeblock bundles (read more).
Plugin authors discussed performance tradeoffs for IP allowlisting in Geo Blocking (read more).
Mobile UI papercuts kept coming: hamburger menu behavior (read more) and tag truncation/blank lines (read more).
Localization enthusiasm continued, including appreciation for new language options (read more).
Interesting Topics
#Announcements
Discourse’s “Boosts” experiment continued to spark strong opinions: hellekin worried it could encourage low-signal reactions (read more), while mcwumbly argued for experimentation and team autonomy (read more), and jordan.vidrine emphasized moderation controls and “fun is okay” framing (read more).
Calendar subscription URLs are landing well, but discoverability and “corporate link/logo” concerns remain: feedback suggested moving subscription closer to the calendar UI instead of burying it in preferences (read more).
#Site feedback
Meta’s plugin availability notes may be misleading, and the thread explored ways to avoid keeping multiple sources in sync—potentially linking directly into the pricing comparison table (read more), with follow-ups about edge cases for plugins not on discourse.org (read more) and a small scroll-margin improvement shipping quickly (read more).
Work on the Meta branded theme redesign (meta-redesign-2026) rolled forward, including a clearer explanation of how the Blocks API differs from plugin outlets—framing Blocks as “layout frames” for more predictable customization (read more).
A small UX inconsistency was spotted in category listings: muted categories appear without descriptions, and folks questioned whether that’s intentional or an oversight (read more).
The collaborative “content gardening hub” experiment sparked workflow questions, including reopening/adjusting who can post in documentation-related index threads; the team temporarily unlocked a thread to keep progress moving (read more).
A new technical blog companion topic told the story of how massive uploads (and a certain sitcom-related dataset) ballooned backups and broke assumptions about ext4 hardlinks—prompting appreciative “more of these technical posts” feedback (read more).
A Ticket System incident turned into a great “settings interaction” postmortem: RGJ traced unexpected TL0 visibility to the Private Topics plugin + permitted-groups configuration, and confirmed the fix (read more).
A concerning moderation queue oddity: multiple old posts (including PMs) were suddenly flagged as spam by the system, with one entry showing Is this post or undefined?—a thread to watch if others see similar log-timeouts + flag anomalies (read more).
The backup progress UI occasionally shows “no logs yet” even when backups succeed; switching tabs makes logs appear, suggesting a front-end refresh/race condition (read more).
On mobile, long category/tag lines can cut off tags without ellipsis and even create awkward blank-line punctuation; examples were collected for tricky long-topic metadata cases (read more).
Structured data / rich results work continued: one remaining schema validation issue was reported around missing fields under mainEntity.suggestedAnswer, and davidb stepped in to investigate further (read more).
#Theme component
A new theme component provides a clean, configurable “Print to PDF” button with controls for where it appears, what it includes, and optional table-of-contents behavior (read more).
The official “Customize new topic button text” component briefly showed both the old and new button; a fix PR was opened and confirmed working for reporters (read more).
#Self-hosting
A migration-heavy self-hosting question: how to default “Watching” for an Announcements category via trust-level groups without staged users inheriting it—seeking a sane pattern for imported (not-yet-activated) accounts (read more).
mcwumbly weighed in on product direction and team autonomy around the Boosts experiment—supporting decentralized exploration even when a feature isn’t universally appealing (read more); they also engaged on how to reduce sync burdens in plugin availability documentation (read more).
jordan.vidrine clarified how Boosts can be moderated (including deletion/admin controls) and argued that not every feature must be purely pragmatic if it’s optional and fun (read more).
ducks published the companion discussion for a new Discourse blog entry on backup generation, large uploads, and ext4 hardlink pitfalls (read more).
manuel explained how the Blocks API changes customization ergonomics compared to PluginOutlets, emphasizing predictable layouts and reusable conditional logic handling (read more).
gerhard resolved a translation regression where emoji/icon handling in Crowdin-to-GitHub locale updates caused issues; the fix landed in updated PRs (read more).
zogstrip helped route the translation/onebox issue to the right eyes by looping in gerhard for a quick diagnosis (read more).
chapoi answered a permissions question about who can create chat channels, confirming it’s restricted to admins/staff (read more).
davidb acknowledged an open structured-data bug report and committed to follow up with investigation notes before closing the loop (read more).
david tracked down a self-hosting edge case: highlight.js bundles weren’t handled properly under certain S3/CDN configurations, and a core PR was linked as the fix (read more).
derek confirmed a UI improvement (scroll margin) related to anchor-linking into long pages, smoothing the experience discussed in the plugin availability notes thread (read more).
Yesterday’s moral: whether you’re debating Boosts, chasing phantom backup logs, or hardlinking 377GB of “Friends,” Meta always finds a way to keep things lively.
Topic Gallery
Discourse llms.txt Generator Plugin
Fehler in der Deutschen Übersetzung? Hier melden!