bmind reported that localized/translated pages were being hurt in search due to canonical handling, and nat confirmed a core fix has shipped and will be included after updating (read more). (Confirmation follow-up: read more)
Eviepayne flagged that the composer was ignoring default_composition_mode, and sam walked through repro checks + safe mode testing—ultimately pointing to a third-party plugin interaction as the likely cause (read more). (Original report: read more)
A busy community asked for “per-volunteer” archiving in the Support Mailbox so helpers can clear items from their view without hiding it from everyone else—surfacing a workflow gap for shared inbox triage (read more).
#Announcements
Discourse announced simpler email subject lines to reduce technical-looking clutter in inboxes, aiming to make communities feel less intimidating to non-technical members (read more). A related concern: some communities rely on category cues in the subject; see also the request around template display options (read more).
In Current Projects, lindsey noted that blog post styling components are now available for translation via Crowdin, unblocking localization work for those assets (read more). (For broader roadmap context, the April projects thread was also referenced elsewhere: read more).
The calendar subscription URL work continues to mature: after positive feedback, there was agreement that key UI affordances “should be in the plugin itself,” with a pointer to interim solutions in an “extra buttons” companion topic (read more; read more).
A member proposed an MMN (Meta Monthly Newsletter) run by the community, but feedback questioned the value vs existing summaries and cautioned that “user/staff of the month” voting can become a popularity contest (read more; critique: read more).
nicolsdennis shared a preview of Domniq, a Discourse-native Android+iOS app concept, including design explorations like app-wide custom color modes and chat UI styling (read more). Related inspirations referenced: a chat bubble component (read more) and the Horizon theme (read more).
In a second “Domniq” showcase, nicolsdennis previewed a premium landing page plugin for unauthenticated visitors—hero layouts, live stats, FAQs, and configurable sections aimed at turning “front page” traffic into engaged members (read more). (Companion app thread: read more)
#Site feedback
mcwumbly proposed a clearer home for lighter “I made a thing” posts: use General with the show-and-tell tag for now, and revisit structure once patterns emerge (read more). piffy immediately sanity-checked the direction by sharing an embeddings-based topic clustering map experiment (read more).
#Feature
A feature request floated a new notification level called “Obnoxious”, but the discussion quickly narrowed to a practical ask: thread-specific desktop notifications (not global browser push) so people can opt-in only where it matters (read more).
A thoughtful feature ideation explored protecting users during episodic unwellness (e.g., manic episodes): mcwumbly suggested “draft it to a trusted friend” patterns and even the possibility of opt-in, just-in-time AI feedback (“you sure you want to post this?”) (read more). Ed_S added adjacent concepts like scheduled send / undo-send time windows (read more).
Self-serve login control came up again: a request asked whether it’s possible to disable local sign-ups (hide Sign Up without CSS) while avoiding tricky authentication combinations—pointing to prior reports about invite only + auth skip create confirm interactions and differences across auth providers (read more; related: read more; auth context: read more).
CI pipelines hit friction when the minio_runner install script failed to follow a redirect, breaking shared GitHub Actions workflows and preventing Rails system tests from even starting in some plugin repos (read more).
#Self-hosting
Storage layout questions resurfaced: one admin asked whether /var/discourse and /var/lib/docker can live on different volumes, and follow-up clarified what’s actually consuming disk (notably the shared/standalone data vs Docker overlay/image layers) (read more).
nat confirmed a production-ready fix for translated pages + canonical SEO behavior and told the reporter the patch is available in the newest build (read more; update confirmation: read more).
mcwumbly established lightweight guidance for “show and tell” posts—routing them to General with show-and-tell while Meta watches for patterns worth formalizing (read more). They also contributed to the “future self / trusted friends” posting-safety brainstorm, suggesting DM drafts and even opt-in AI nudges (read more).
lindsey published an announcement detailing how Discourse is simplifying default email subject lines and how communities can adopt the changes (read more). They also shared a projects update: blog post styling components are now ready for translation in Crowdin (read more).
sam helped debug a “composer ignores default_composition_mode” report, recommending safe mode and identifying third-party plugin interference as the likely culprit (read more).
If you survived the push for “Obnoxious” notifications, at least your inbox gets a calmer ride with those newly simplified email subject lines. (read more; read more)
“Access denied” on email verification link (read more)
Interesting Topics
#Announcements
Emoji picker search now works in your language — Falco shipped multilingual emoji keyword search (48 languages), unblocking long-standing localization pain where emoji search was effectively English-only (read more). Related context: the earlier request for translated aliases (read more) and the older “how do I support other languages?” support thread now answered via the new feature (read more).
Simpler email subject lines — the email UX discussion continued around making subjects clearer by default (and what to keep, like the usefulness of [PM]) (read more).
“I populated my (mostly-dead) Discourse forum with bots!” — kirupa shared a show-and-tell experiment using AI bots with distinct personalities to generate topics and replies, sparking debate about community vs. “Dead Internet” vibes and the practical value of a personalized “daily briefing” forum (read more).
Random thought: notify contributors when a topic disappears — fuse wondered whether Discourse should PM or otherwise preserve contributors’ writing when a topic is deleted or becomes inaccessible (especially when you’ve written something substantial) (read more).
Modifications/features I made on my forums (and why) — Canapin consolidated a set of pragmatic improvements they’ve built (including community-funding mechanics) and why each change helped, as a concrete “here’s what worked” show-and-tell reference for other admins (read more). Related: the donation progress bar component referenced in the write-up (read more) and the broader “where should people share?” meta discussion about show-and-tell culture/site structure (read more).
Releases.discourse.org feedback & suggestions — a quick but meaningful nod that recent changes made releases.discourse.org “a lot easier to read,” reinforcing that polish work on ancillary Discourse properties gets noticed (read more).
Can a leaderboard top contributor have no topic or posts in their activity? — a neat edge case: yes, if the leaderboard is counting private-category participation (or even reading), it can look like a user has “no activity” while still ranking highly (read more). Related: Falco pointed to external point-award integrations as another factor (read more).
What happens to translations when an LLM changes? — after a model deprecation and switching LLM parameters, the key clarification was that existing translations remain and only missing items should be translated—helpful for admins watching token usage and progress bars (read more).
Videos and monetizing my Discourse community — a “what’s possible?” thread about selling access to instructional racing videos via a Discourse community, with early guidance leaning toward offloading video hosting/storage complexity elsewhere (read more).
AI triage examples not sent properly? — an important Discourse AI / automation report: examples appeared to be interpreted as part of the content being evaluated, causing every post to get flagged (and the model citing the example wiring details as if they were real) (read more).
Admin changing email address of a member is still quirky — tobiaseigen documented a confusing flow where email verification links fail with “Access Denied” while logged in as admin; workarounds include impersonation or alternative methods, but the UX mismatch versus admin expectations sparked discussion (read more). Related: the console-based approach for certain cases (read more).
#Feature
Tecnoblog’s Experience With Discourse Comments (Embedding) — ongoing embed feedback included a serious “can’t type in the text field” issue (notably for the first comment on mobile), Safari/iOS scroll quirks, and broader embed instrumentation concerns (read more).
#Plugin
Locations Plugin prototype + early access for sponsors — merefield shared a prototype preview and outlined a sponsorship-based early access path (with invites rolling out and a “fixes first” promise for backers) (read more).
Trading Buttons plugin appears broken after an update — a report that a recent Discourse update removed category-setting options needed for the plugin UI to function, despite the plugin being enabled (read more).
Accessing Discourse DB with DBeaver — a practical guide to safely exposing Postgres from a Dockerized Discourse for use with GUI clients (port mapping, firewalling, and switching auth to scram-sha-256, with an emphasis on private networking like Tailscale) (read more).
Announced the multilingual emoji search upgrade (48 locales), including examples of non-English keywords now matching correctly (read more).
Clarified translation behavior when switching LLM parameters: old translations are retained and only missing items should be processed going forward (read more).
Helped explain “invisible” leaderboard activity and pointed to external gamification integration possibilities (read more).
Stayed engaged in embed-related troubleshooting and follow-ups in Tecnoblog’s embedding thread (read more).
Closed the loop on an older “emoji search in other languages” question by linking to the new announcement (read more).
Responded to confusion caused by a topic becoming inaccessible, acknowledged the internal mishap, and signaled the content should reappear once things are untangled (read more).
Nudged show-and-tell sharing toward clearer expectations (inspiration/feedback vs. reusable components) and explored how meta should structure those conversations (read more).
Added thoughts to a sensitive feature discussion around safer posting flows (e.g., “undo send” style ideas) for users dealing with episodic unwellness (read more).
Shared a “quote-to-draft” reading workflow hack in the long-running “chapters for long topics” thread (read more).
Chimed in on the bot-populated forum #show-and-tell: appreciated the styling, questioned “community” framing, and highlighted the “stay up to date on interests” angle (read more).
That’s a wrap—may tomorrow bring multilingual emoji searches, fewer disappearing topics, and bots that know when to stop posting.
Top contributors (posts • likes)
(Links go to a representative recent post from each user.)
Ginger_Marcus — 3 posts • 5 likes — reflections on tightening edit windows to reduce “impulsive posting” in a sensitive moderation/UX discussion (read more)
Falco(team) — 3 posts • 2 likes — guidance on automation triage agents and how “examples” are actually injected into the prompt history (read more)
darkpixlz — 3 posts • 2 likes — launched a “shortlink router” utility and followed up on privacy/logging concerns (read more)
kirupa — 2 posts • 5 likes — shared implementation details for populating a forum with bots and content sources (read more)
ted — 2 posts • 5 likes — weighed in on guardrails for regrettable posting and later on monetization/legal implications (read more)
nathank — 1 post • 5 likes — excitement about the Meta theme rebuild and “Blocks API” direction (read more)
Moin — 1 post • 4 likes — pointed to the revert control in wiki edit history (and who can actually use it) (read more)
ondrej — 1 post • 3 likes — clarified permissions: category mods/TL4 can’t revert revisions (read more)
pfaffman — 1 post • 3 likes — pragmatic self-hosting guidance on separating Docker/Discourse volumes (read more)
RGJ — 1 post • 2 likes — cautioned against framing episodic unwellness as “accountability training” (read more)
Interesting Topics
#Feature
Ginger_Marcus shared a real-world moderation experiment: shortening the edit window to make conversations more coherent (and reduce context drift after OP edits), while RGJ pushed back on “accountability” framing for episodic unwellness; ted noted adjacent use-cases like rage-bait or drunk posting (read more)
A quick “how do I roll back a wiki page?” turned into a permissions gotcha: Moin described the revert UI, but ondrej clarified category moderators/TL4 don’t have revert rights per the permissions reference (read more)
Monetizing via gated video/content raised bigger questions than plugins: ted highlighted that paying creators can introduce legal and operational complexity, not just technical setup (read more)
In automation + ai triage, Falco recommended using a “Triage with AI Agent” and the flag tool instead of string-return prompts—then dug into why example messages were causing unintended “flag everything” behavior (read more)
Translation workloads + LLM switching: Falco suggested enabling verbose logs and checking the AI API audit logs table to reconcile high token usage with “no progress” stats (read more)
OpenID Connect login nuance: a new thread asked whether allowed email domains is validated against the email returned by OIDC at account creation time (read more)
Discourse ID accounts: mcwumbly confirmed that recent changes now allow users to change username/name in user settings, even when the account was created via Discourse ID (read more)
#Self-hosting
“Can /var/discourse and /var/lib/docker live on different volumes?” got a pragmatic answer: Discourse doesn’t care where Docker stores its data—optimize for maintainability and clarity first (read more)
A HestiaCP install run hit multiple snags: port conflicts with 80/443 templates and a puzzling GitHub/network failure that the OP later traced to DNS resolver behavior (Cloudflare/Google DNS vs internal DNS) (read more)
#Extras
A new utility, Discourse Shortlink Router, proposes a “swap hostname, keep path” approach to sharing admin/support URLs—prompting immediate questions about trust, logs, and what data might be exposed (read more)
The ICS → Discourse importer thread documented a subtle behavior: --time-only-dedupe isn’t strictly time-only because it still applies “close enough” location checks—leading to a helpful “signal vs noise” outcome for room changes vs feed churn (read more)
A brand-new UX concern: “Edit history visible to public” doesn’t appear to cover author/owner changes on the first post/topic—raising questions about transparency, moderation workflows, and whether this is a bug vs missing feature (read more)
#Site feedback
Meta’s theme rebuild continues to generate excitement: nathank called out how the new tooling could help Discourse move from “a website component” to “the full website,” especially for small orgs seeking a simpler stack (read more)
A lively #show-and-tell:kirupa described bootstrapping a “mostly-dead” forum with bots, curated sources, and plans to resurrect old topics with modern responses—plus discussion about translation using Discourse AI (read more)
#Theme
After upgrading to v2026.4.0-latest (Ember v6.10.1), a report in the FKB Pro theme thread shows a client-side failure: missing ember-this-fallback/this-fallback-helper, effectively breaking the forum UI until resolved (read more)
Falco helped troubleshoot why AI triage “examples” were backfiring: they explained that examples are sent as previous turns, so they must mimic the exact expected model response (including what a tool call should look like) and asked which LLM was in use (read more). They also suggested a cleaner architecture using Triage with AI Agent plus the flag tool (read more). In a separate AI-translations thread, they advised turning on verbose logging and checking AI audit logs to verify translation progress vs token burn (read more).
mcwumbly responded to concerns that public edit history doesn’t reflect author/owner changes, flagging it as likely a bug or missing feature and moved it to UX for discussion (read more). They also confirmed a Discourse ID improvement: users can now change their username/name directly in settings after recent changes (read more).
Yesterday, Meta proved two things: bots can revive sleepy communities, and a 60-second edit window can keep the mustard-fueled hot takes delightfully accountable.
Revan_Manaflı reported a strange profile/UI behavior (“blue, nameless button”) affecting a single Discourse instance; Moin suggested confirming whether it reproduces elsewhere and using Safe Mode to rule out customizations in Kali Forums Bug. The reporter confirmed it disappeared in Safe Mode, pointing to a theme/component issue rather than core (safe mode reference).
ice.d asked whether Discourse requires users to be 13+ and whether hosted vs self-hosted changes that requirement; Lilly highlighted Meta’s ToS language and child-safety compliance considerations in Age requirement for Discourse. For policy context, the “volunteer moderators” section change was also noted recently in What Changed in the META ToS (July 18, 2024) (and prior comparison thread: read more).
Incoming email workflows regressed for private categories: hellekin described cases where email-to-category fails with Email::Receiver::InsufficientTrustLevelError, even when unknown-address email is allowed, in Incoming email stopped working for private categories.
Debugging AI translation behavior: RBoy enabled verbose translation logs and observed repeated retries that consumed daily token quotas, suggesting a potential loop or repeated job retries in What happens to translations when LLM changes? (ai).
Group visibility/admin UX edge cases: nathank noted that marking groups “automatic” removes the Membership tab entirely (making some admin edits awkward), and RGJ clarified the behavior is core—then flagged potential plugin maintenance follow-up—in Discourse Dynamic Groups.
Gallery navigation ergonomics: Canapin asked whether the gallery icon should open from the current/unread post rather than always from the start, especially on mobile, in Topic Gallery.
Visualization niceties: the long-running visualization thread got an update with a “snazzy” 3D view option shared by merefield in Community Network Visualisation.
Cookie inventories and compliance: miednr asked for a detailed cookie list attributable to the WP Discourse plugin; angus replied that the plugin doesn’t set its own cookies (noting WordPress auth cookies as standard behavior) in Cookie information request.
chapoi closed an off-scope support thread (site-specific theme/customization issue) after Moin helped narrow it down using Safe Mode, in Kali Forums Bug.
mcwumbly followed up on a mobile-title wrapping report, noting it appears fixed on current Meta themes and suggesting affected sites may need updates, in 标题过长，超出边界 (mobile).
Yesterday proved that Safe Mode is still the quickest way to turn “mystery blue buttons” into actionable theme fixes—right as everyone else was busy debating magic-link logins and chasing down cookie lists.
In the last 24 hours, Meta saw 94 new posts across 15 new topics (compiled from activity in the threads linked below, e.g. read more, read more, read more).
ice.d asked how age requirements / age verification interact with self-hosted vs CDCK-hosted sites, and supermathie pointed to hosting terms and “Special Data Regulations” constraints in the discussion on age requirement for Discourse.
(Also: awesomerobot clarified where “talk to your government” fits when regulations apply to hosting regions read more.)
A theme/component interaction after updating to 2026.4.0 caused category badge text color to change while scrolling; chapoi suggested safe mode and inspection steps, and Lilly shared a quick CSS fix in issue with font colour in category badges.
Follow-up: chapoi said the team would investigate root cause read more.
A new admin asked for a “send it back to the author to rewrite it” flow for incomplete/low-quality/AI-ish topics in how to force a topic to be edited by the user.
This one is likely to evolve into a moderation-workflow conversation (flags, staff messages, slow mode, approval queues, etc.) as the thread develops read more.
A GitHub → Discourse integration attempt hit a snag: issue creation posts fine, but issue comment webhooks don’t appear in Discourse in Discourse Code Review Questions.
Context-wise, the asker is comparing the Code Review plugin to the older GitHub integration plugin docs/threads read more.
Accessibility scanning surfaced that custom badge images may be missing alt text, prompting a question about whether this needs core changes or admin-side work in Custom Badges are not applying Alt Text.
This is a classic “is the HTML attribute missing in render, or can the badge UI supply it?” investigation read more.
Data Explorer users reported that query results appear capped to a tiny scrollable viewport (effectively “5 rows”) regardless of result size in Explorer reports limited to 5 rows….
After Lilly offered a CSS workaround and a pointer to the SCSS in the plugin read more, nat confirmed a fix was in progress read more and later posted that it was fixed and deployedread more.
A crawler-related error appeared post-upgrade: ArgumentError (Document tree depth limit exceeded) in middleware logs, likely triggered by bots requesting uploaded assets, in Middleware - document tree depth exceeded. Falco asked for a reproducible page/request to debug the culprit read more.
manuel published a repo of Claude Code “skills” for theme authoring and the Blocks API, including reference material and an example theme, in Skills for authoring themes and blocks.
In follow-up, manuel explained how Blocks shift theme customizations toward “layout frames” per outlet and showed where initializer-driven layouts live read more.
CI friction popped up again around dev tooling, with a report that a Minio installer breaks CI affecting workflows in Minio installer breaks CI.
This kind of thread is a bellwether for “dev environment parity” work read more.
Admin ergonomics for reporting got attention: ganncamp proposed a better way to share Data Explorer queries without forcing admins to manually hunt down group report URLs, in Sharing a Data Explorer Query. Lilly suggested a deterministic /g/.../reports/... pattern and hinted at a possible PR (plus a UX need to show which groups a query is shared with) read more.
Embedding/Comments users confirmed a fix landed, but continued discussing a lingering horizontal scroll on mobile in Tecnoblog’s Experience With Discourse Comments. Falco couldn’t reproduce on-device and shared screenshots while investigating read more.
A “paid build” request sparked healthy scope/budget reality checks: a community platform owner requested help for a v2 launch (theme QA + custom member portal/profile work) in [Paid] Discoure Community Platform - development for v2.
The thread quickly focused on clarifying milestones, fragility of nav injection, and realistic pricing expectations read more.
#Self-hosting
A self-hoster asked how to run Discourse behind an external reverse proxy and disable Let’s Encrypt in the docker setup in Fresh install without lets-encrypt on docker.
The canonical reference thread often cited for this area is “Allow SSL/HTTPS for your Discourse Docker setup” read more.
supermathie provided the key legal/terms pointer for hosted customers around “Special Data Regulations” (including COPPA) in Age requirement for Discourse, grounding the discussion in the actual contractual clause.
awesomerobot added an operational note on compliance realities for hosted services—where regulation applies, CDCK must comply, and feedback is best directed at lawmakers—in Age requirement for Discourse.
pmusaraj shipped and showcased a new official-ish theme entry with install + getting-started references in Verso Theme, expanding the “lightweight theme” ecosystem and giving admins another clean baseline option.
That’s a wrap—may your Data Explorer tables grow taller than five rows, your category badge text stay readable while scrolling, and your Blocks layouts snap neatly into place.
Proposed new defaults for TL3 requirements behind an upcoming change: read more
Interesting Topics
#Announcements
lindsey introduced four new Topic Voting badges (Daydreamer/Brainstormer/Innovator/Visionary) to celebrate ideas that attract votes, then flipped them on for Meta; follow-up clarified backfill + notification rules (only notify if earned in last 2 weeks, and only the highest badge if multiple thresholds are met). read more
Related context: earlier Topic Voting improvements: read more and long-running “Vote Notifications” discussion: read more
The April 2026 monthly release dropped, with david pointing admins to the full 2026.4 changelog for details on what shipped. read more
martin announced an upcoming change to make TL3 achievable on very active forums by reducing viewed/read caps and increasing minimum promotion duration (defaults only; manual overrides remain untouched). read more
#Feature
In an embedded-comments rollout, Thiago_Mobilon shared screenshots of horizontal scrolling on iOS that seemed to affect admin sessions; pmusaraj confirmed the “admin-only” angle and pointed to a core fix via PR. read more
A long-running gamification request got a quick victory lap: Falco noted per-leaderboard scoring values were merged, and Lilly highlighted the new granular scoring configuration options. read more
A moderation workflow pain point: requesting that a user must edit a topic before it can proceed. Suggestions ranged from approvals to converting to PMs, but the most practical path discussed was using custom flags, plus UI-limiting them to staff via CSS. read more
Supporting links: category-level approvals flexibility: read more and the “staff-only custom flag” CSS approach: read more
“Age requirement for Discourse” turned into a compliance reality-check: HAWK clarified UK Online Safety Act scope for U2U platforms (and noted DSA requirements in the EU), emphasizing that jurisdictional exposure matters even for self-hosters. read more
A Chinese-language support thread asked where to enable allow_user_api_key; the resolution was simply pointing to the User API Keys specification doc topic. read more
Reference: the spec itself: read more
Event notifications in French (“Notifier un évènement à un groupe”) surfaced confusion around bulk invitations/notifications where only the first user seemed to receive the invite, prompting a call to rethink group notification flows. read more
Discourse shared an Office Hours replay focused on Discourse AI for Enterprise, covering semantic/conversational search and automation patterns for moderation and ops work. read more
Related: the webinar/office-hours program context: read more
The calendar/events UX thread about “all day events” effectively got closed out by a now-shipped All day event checkbox in the create-event modal, removing the “00:00 confusion” problem. read more
Related feature request that’s now completed: read more
Another calendar UX improvement also landed: event exports now include event descriptions in the .ics file, improving the “save to calendar” experience. read more
A completed calendar request was formally closed, with an offer to split follow-ups into a new feature topic if needed (good housekeeping that keeps feature scopes clean). read more
Oneboxing edge case: MediaWiki-style image HTML pages sometimes break oneboxes (especially on certain MediaWiki hosts), and the suggestion was to detect Content-Type: text/html to avoid treating it as an image. read more
A “document tree depth exceeded” middleware issue got a couple fixes linked directly to PRs, with Falco flagging it for review/visibility. read more
#Theme component
The “Video Upload to YouTube and Vimeo” theme component thread progressed toward permission scoping: multiple folks emphasized restricting upload access by group to prevent abuse, and Arkshine discussed Vimeo OAuth work so uploads can go to a user’s Vimeo space. read more
#Plugin
The “Discourse to Markdown” plugin discussion explored a clean integration path with Discourse MCP: try Accept: text/markdown first, then fall back to JSON API with include_raw=true. read more
Related: Discourse MCP announcement thread: read more
#Community Building
A fresh, practical write-up shared a lightweight pattern for using Discourse as an LMS/course tracker built around categories/topics + Docs, with a small plugin + theme component to compensate for “notification decay” in lesson progress. read more
Dependency referenced: Doc Categories plugin: read more
lindsey shipped and enabled the new Topic Voting badges, then clarified how the badge backfill + notification throttling works to avoid retroactive notification spam. read more and notification behavior detail: read more
Also closed the loop on calendar UX improvements by pointing to shipped solutions for all-day events: read more and .icsevent descriptions: read more, and wrapped up a completed calendar-default-view request: read more
david published the pointer for the 2026.4 (April 2026) release notes. read more
He also added an important implementation note elsewhere: group sync is now available for OIDC, pointing admins to the plugin topic and changelog. read more (referencing the OIDC plugin’s “group sync” documentation: read more)
martin proposed an “upcoming change” to adjust TL3 default requirements, reducing caps for topics viewed/posts read while increasing minimum duration—aimed at very active communities where TL3 becomes unreachable. read more
HAWK provided jurisdiction-specific clarification on UK OSA applicability (and noted DSA considerations), emphasizing that sites “may have users from” regulated regions and should plan compliance accordingly. read more
pmusaraj helped narrow down an embedded-comments horizontal scroll issue to an admin-context repro and linked the upstream fix PR that should resolve it. read more
Danielle shared the AI for Enterprise Office Hours replay, outlining how AI search and automated moderation aim to remove repetitive work while keeping humans in the loop. read more
Falco flagged multiple “this is now fixed/shipped” updates across the day:
Noted per-leaderboard scoring values were merged. read more
Linked PRs for the middleware document tree depth exceeded fixes. read more
Suggested an LLM configuration troubleshooting step (“disable thinking”) in an AI translations thread. read more
fzngagan outlined a practical moderation workaround for “force user edits” using the flag system’s Hide Post flow (while noting limitations around custom messaging), and pointed back to approvals as the more proactive approach. read more
If yesterday’s Meta had a theme, it was “ship the badges, fix the scroll, and let calendars finally have all-day events without doing midnight math.”
Topic Gallery