סיכום שבועי

This week on meta.discourse.org…

(Covering 2026-07-26 → 2026-08-02)

Key Stats

  • New posts: 701
  • New topics: 72

Top contributors (posts / likes received):

User Posts Likes
Lilly 40 72
Moin 40 70
awesomerobot 23 53
Damian_Boon 36 52
chapoi 21 47
alltiagocom 40 45
NateDhaliwal 22 42
zogstrip 13 42
merefield 27 41
Canapin 16 38

What drove the conversations this week (high-level highlights): a new ESR release and follow-on upgrade questions (read more), more iteration on nested replies (including a new “Hot” sorting mode) (read more), and a cluster of UX/admin dashboard discussions about “where did the version info go?” (read more).


Interesting Topics

#enterprise

  • How close should customers be to your teams? HAWK kicked off a thoughtful thread on setting healthy boundaries between customers and product teams—covering “hidden costs” of engagement and how to build trust without creating an always-on expectation (read more).

#announcements

  • July 2026 monthly release + ESR shift: The 2026.7 release landed and became the new ESR, prompting practical guidance on pinning to a specific branch (e.g. release/2026.1) to avoid surprise jumps (read more).

  • Intermediate security releases (July 31): david posted the “intermediate releases” roundup and clarified that some “unexpected jumps” were actually due to the new ESR being released earlier in the week (read more).

  • Composer controls cleanup: The composer preview toggle moved to sit alongside the other window controls (fullscreen/minimize), and the minimized draft bar was simplified for clarity (read more).

  • Nested replies: “Hot” sorting: A new sort option designed to surface currently-engaging subthreads in nested replies—bridging the gap between “Top” and “New” (read more).

  • Pending user approval reminders: new default: A new upcoming change drops the default delay from 8 hours to 30 minutes on sites with approval enabled, improving staff responsiveness for queued users (read more).

#extras ai

  • Improving AI report accuracy via validation: sam introduced a more robust pipeline for AI periodic reports by adding workflow-based validation steps—aimed at improving summary quality without changing LLMs (read more).

  • “Agent skills” for Discourse AI: A proposal to store skill definitions in topics (one topic per skill), enabling more maintainable and permissioned agent behavior through progressive disclosure (read more).

  • Workflows + Gemini schema pain: A thread on Gemini choking on schema constructs (notably additionalProperties), with sam noting a spike toward the Interactions API for a more stable bridge (read more).

Community Building

  • Moderating “AI-ish” content (without constant conflict): A practical report on using an AI classifier to flag overly formal / thesis-like AI-generated topics (especially from new users), including real-world cost estimates and moderation workflow details (read more).

  • Office Hours replay: embedded Discourse in full app mode: The team shared a replay about bringing Discourse conversations directly into external websites via full-page embedded experiences (read more).

  • Survey: needs of community administrators: A bachelor’s thesis survey asked admins/mods what analytics actually matter (newcomers, departures, workload, returning users, etc.) (read more).

#self-hosting

  • Cheaper alternatives to Hetzner? A wide-ranging thread on pricing changes, availability constraints, and real-world sizing advice (plus a script idea to alert when specific Hetzner instances become available) (read more).

  • Maintenance page workaround (Cloudflare Workers vs dual-container): Discussion weighed “nice touch” maintenance UX against complexity; dual-container rebuild strategy was repeatedly recommended to shrink downtime windows (read more).

  • “Updated to ESR but 578 new changes available” bug: david explained a DiscourseHub version-check issue (counting commits between refs) and posted the fix + a manual job trigger for impatient admins (read more).

ux

  • Where did the version information go (new dashboard concerns): Admins debated the redesigned dashboard focus (community manager vs sysadmin needs), with discussion on roles/hats and potential future customization (read more).

  • Dark theme readability: reduce pure-white text: A design request to avoid harsh high-contrast white-on-black typography—especially relevant to the newer palettes in Horizon-style themes (read more).

  • Staff-only mode should not show login/signup CTAs: A UX improvement to avoid frustrating anonymous users with actions they can’t complete—fixed via a core PR (read more).

  • “Start Updating” button doesn’t look clickable: A small-but-painful affordance issue in the admin update UI, with a note that it changes under certain upcoming theme changes (read more).

bug

  • Turkish translation outputs archaic/Ottoman language: The “Translate to Turkish” feature was over-transforming; the prompt was tightened to “stay in its lane” and produce faithful translations (read more).

  • Chat search results can’t scroll on mobile: Global chat search results were unscrollable via touch; fix shipped quickly in core (read more).

  • Homepage shows older topics (bfcache headers): A long-running “latest isn’t latest” issue was traced to bfcache-compatible headers and addressed via a PR (read more).

  • Reply-by-email from Outlook truncates after numbered lists: A reproducible formatting bug (with fixture email) was fixed via PR (read more).

development (and closely related implementation threads)

  • Trust Level 3 transparency: progress UI + core logic clarification: A plugin to expose TL3 progress to TL2 users sparked a broader conversation about what to reveal vs what can be gamed (read more), while a separate deep dive clarified how the % posts read requirement and the cap work in core (read more).

  • Logo behavior: small logo breakpoint override: A “why does the primary logo stay too long?” question ended up traced to a theme component overriding behavior; a new setting was added to restore default behavior (read more).

  • Correct CSS for light/dark: use light-dark() A concise styling tip: the native CSS light-dark() function can be simpler than container queries when you truly need explicit dual colors (read more).

#plugin / #theme-component

  • Resenha voice rooms: rapid UX iteration + new features: Multiple improvements landed (private lock icon, participant list discoverability, deep links to rooms), plus highlights like coturn auth, recording, flags, and tile right-click menus (read more).

  • Theme component: Mobile Composer Preview restored: The preview toggle was brought back for mobile (and debugging uncovered some Theme Creator preview-link flakiness, with better testing workflow tips) (read more).

  • Plugin: Event Duplicator for calendar topics: A new plugin to duplicate event topics into a new time period gained “shift (months)” support quickly (useful for monthly/quarterly event patterns) (read more).


Activity by the @team Group

sam

  • Pushed forward Discourse AI reporting quality by adding workflow-driven validation steps to the AI report pipeline (read more).
  • Proposed a structured approach to “agent skills” stored as topics—aimed at reducing unwieldy system prompts and making agent capabilities easier to maintain collaboratively (read more).
  • Responded to Workflows + Gemini provider limitations and noted an upcoming push toward Interactions API for better stability (read more).
  • Shipped (or pointed to) fixes around media review behavior and edge cases in upload review logic (read more).

david

  • Clarified ESR upgrade mechanics (pinning to release/2026.1 vs tracking esr) in the monthly release thread (read more).
  • Posted the intermediate security releases list and explained why some “stable” installs jumped due to ESR timing rather than the intermediate release itself (read more).
  • Diagnosed and resolved the “578 new changes available” display issue as a DiscourseHub version-check API bug (read more).
  • Traced an avatar/image optimization failure back to an archived plugin and recommended removing it to restore normal uploads (read more).
  • Helped narrow down remaining iOS upload problems (beyond the older-iOS fix) by requesting better UA/log evidence (read more).

Falco

  • Fixed an AI translation prompt that was over-stylizing output, causing archaic Turkish; the revised prompt keeps translations faithful to tone and meaning (read more).
  • Delivered multiple Resenha improvements (UX fixes for private rooms and better participant management discoverability), plus deep-linking to rooms (read more).
  • Investigated iOS upload issues, suspecting instance-specific settings when “sandbox works but my site doesn’t” (read more).
  • Reduced noise from AI “structured output JSON warning” logs by moving that message to INFO level (read more).

zogstrip

  • Improved UX for staff-only sites by removing misleading login/signup CTAs for anonymous users (read more).
  • Introduced the “pending users reminder default” upcoming change, reducing the delay to 30 minutes for sites requiring approval (read more).
  • Landed multiple fast-turnaround fixes across moderation/review and notifications:
    • “Suspend” option in review flows / consistency improvements (read more)
    • Duplicate poll title in email notifications (read more)
    • Flag “reason” formatting regression fix (read more)
    • Outlook reply-by-email truncation fix (read more)
  • Traced “opening forum shows older topics” to bfcache-compatible headers and posted a PR to address it (read more).
  • Implemented the requested boolean input behavior for manually mapped Workflows fields and kept the topic updated with PR links and status (read more).

chapoi

  • Announced a composer control tidy-up (preview toggle moved, minimize icon standardized, draft bar simplified) (read more).
  • Helped users navigate support and UX behavior around unread/unseen semantics (post-level vs topic-level) (read more).
  • Guided translation contributors on the correct path to become proofreaders (and linked the canonical instructions) (read more).
  • Confirmed Horizon’s intentional declutter decision re: hiding the “unread/new topics” line under suggested topics (read more).

awesomerobot

  • Shipped a fix for mobile chat global-search scrolling and linked the core PR for inclusion on next update (read more).
  • Identified theme-component interference in header logo swapping behavior and added a new setting to restore default behavior in the full-width component (read more).
  • Advised on safer customization patterns (CSS variables over brittle selectors, stable plugin outlets over overrides) and what tends to break across updates (read more).
  • Provided a clean solution for light/dark styling using the CSS light-dark() function (read more).
  • Helped debug URL anchor stripping issues in the rich editor by suggesting HTML wrappers that survive composer transformations (read more).
  • Flagged a Meta theme translation issue (empty banner text) and looped in nat for investigation (read more).

HAWK

  • Started a substantial discussion on staff participation frameworks and reducing fear-of-engagement across teams (especially when not everyone is an engineer/designer) (read more).
  • Weighed in on AI-content moderation norms and pushed back (lightly, but clearly) on the idea that humans should “downgrade writing style” to prove they’re not bots (read more).
  • Pointed users toward site text customization as the first stop for notification wording changes (read more).

markvanlan

  • Introduced “Hot sorting” for nested replies—designed to surface active subthreads without freezing early-liked replies at the top forever (read more).
  • Confirmed expected behavior for “new nested reply appears at top until refresh” and explained the UX rationale (visibility vs strict ordering) (read more).
  • Continued nested replies stabilization work with fixes for scroll jumping and post leakage across topics (read more).

mcwumbly

  • Explained the TL3 “posts read” math and the cap in a way that finally made the logic click for folks reading core code (read more).
  • Added nuance to the “where did version info go?” debate by framing admin needs as multiple “hats” (sysadmin vs site admin vs community manager) and pointing toward more customizable /admin futures (read more).
  • Turned a “Me too” reporting question into a working Data Explorer query for admins to track shared-issue clicks by topic + date range (read more).
  • Engaged in early thinking around nested subcategory presentation in dropdowns, including tradeoffs and potential UI affordances (read more).

nat

  • Fixed Meta’s “empty banner box” issue by removing accidental manual empty overrides in a theme component’s translations (read more).
  • Merged a date picker improvement for AI Translate settings to make backfill dates clearer and easier to configure (read more).
  • Advanced multi-language preferences for localized content display, sharing screenshots and inviting Meta testing/feedback (read more).

Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

Key Stats

It’s been another busy week across Meta, with the community generating 613 new posts across 75 new topics in the last 7 days. A chorus of insightful feedback, robust testing, and thoughtful product discussion filled the forums—from a major composer redesign test to the bumpy path towards PostgreSQL 18.

Top users by activity (posts & likes):

User Posts Likes
Moin 31 93
merefield 33 90
Lilly 22 50
awesomerobot 17 49
HAWK 13 48
satonotdead 37 47
chapoi 23 46
Canapin 12 43
pfaffman 15 39
Falco 11 36

A special shout-out to satonotdead, who was the most prolific poster this week with 37 posts, and Moin and merefield, who led the likes chart. Great to see the community buzzing with activity.


Interesting Topics

#Announcements

  • Help test the Composer redesign! chapoi unveiled a major experimental redesign of the composer, with goals to modernize the look & feel and improve mobile composing. The feedback floodgates opened: darkpixlz questioned why the title input was so huge, Don loved the modern look but suggested adding a visual grip/handle to the swipeable textarea, Canapin raised issues with the H1 title looking like part of the textarea and large titles getting partially hidden, and NateDhaliwal reported “colourless category icons” (accidental, fix on the way). satonotdead defended the bottom toolbar as more reachable on one-handed mobile use, and Don referenced an old bug where the context menu covers the editor button bar. sk-or-v1-contents even shared a CSS fix for the blue flash on expanding. read more

  • PostgreSQL 18 update for self-hosters — chrisr announced the upgrade of the Docker image to PostgreSQL 18, requiring roughly 2x database size in free disk space. The thread saw extensive Q&A: chrisr corrected the space warning to 2x, added a fix for core count detection using nproc --ignore=1, and Falco reported a smooth upgrade on a Pi 5. Lilly shared a detailed step-by-step guide for dual-container setups with Cloudflare CDN and R2 buckets read more, and Tobias_1 provided a German-language fix for the “group id 993 which does not exist” error by cleaning up leftover upgrade files and correcting permissions. read more

  • Gemini Interactions API support — sam announced that Discourse AI now supports the new Gemini Interactions API, recommending it for all Gemini inference. The new provider brings tool call streaming, native code execution, and a Google Maps tool—though the new API no longer allows disabling “thinking” on 2.5 flash models. read more

  • Updates on granular group-based permissions — In the ongoing thread about granular group-based permissions for anonymous and logged in users, satonotdead asked about CSS classes, and martin confirmed that official components now use resolve_group_membership and disallowed_groups, with several PRs merged for official components. Lilly contributed a PR to add anonymous_users and logged_in_users classes to the theme component. read more

#Community Building

  • For the next decade of the internet (2026 edition) — mcwumbly opened a thought-provoking discussion about what the next decade of the internet looks like, harking back to Discourse’s 2013 launch promise. awesomerobot gave a brilliant historical perspective, noting that we’ll still be “typing words into boxes” in 2036, just as we did in 2003. Ed_S raised concerns about monetisation of human connection and polarisation, while satonotdead envisioned both a multimedia-centric hub future and a hard-resistance, cypherpunk-decentralized option. read more

  • What’s the story behind your community? — Danielle invited members to share the origin stories of their communities, from caregivers of diabetic cats to interest hubs. HAWK shared how they see Meta as supporting both a shared project and a mission, with the open-source ethos at its heart. read more

  • Scalable engagement models — HAWK asked the community about one-to-many engagement models, citing office hours and webinars as infinitely scalable formats. mcwumbly shared the pattern of having feature announcements made by the people closest to the change, which hooks nicely into the product-building process and lets the community engage directly with builders. read more

  • Learning music (off-topic but interesting) — HAWK split out this delightful off-topic discussion about learning music from another thread, sharing his own journey from clarinet to drums. The thread evolved into sharing academic papers on Icaros, shamanic drumming and even a project to reconstruct imagined melodies from brain signals, contributed by philip_rhoades and satonotdead. read more

#Enterprise

#Feature

  • More direct access to topics with new replies — The unified new view continues to generate heated feedback. martin confirmed a user preference for splitting new/unread isn’t planned, but suggests a theme component could do it. Shauny reported user complaints about the 2-click workflow, seanblue said the old way “worked perfectly” for them, and awesomerobot proposed a prioritization preference. Moin pointed to the Custom Top Navigation Links component as a potential place to regain separate counts. read more

  • Always allow username-based password reset — southpaw highlighted that the hide_email_address_taken setting (enabled by default) makes the forgot-password form require email, and the feature request to always allow usernames gained traction. pfaffman admitted he had been “wrong-headed” and apologized for his initial dismissive response, noting that long-standing community members often don’t remember their signup email. awesomerobot noted this was an intentional change from a 2021 PR to harden sites against password-reset abuse. read more

  • Doc categories landing page option — mostapha asked for an option to make the index page the landing page for documentation categories, noting a confusing default that shows a list of posts instead of the documentation index. Turns out this had been requested before, and the discussion continued there. read more

  • Multiple profiles for one user — a_lilian discussed the feature request for multiple profiles per user, referencing PluralKit and explaining how this matters for accessibility and for users with complex identity needs. satonotdead connected it to Simplex chat design. read more

  • Redesigned admin dashboard feedback — In the thread about the redesigned admin dashboard, mcwumbly linked to further discussion about where version information went, and Moin noted the removal of the Docker manager plugin. read more

development

#Praise

  • Contributor appreciation August (& Feb) 2026 — Moin wrote a heartfelt thank-you to all contributors over the past six months (and the previous ESR release), continuing the tradition from old release blog posts. HAWK added a much-appreciated :heart:. read more

#Self-hosting

  • Spanish self-hosting saga — Picho_Pelis ran into repeated failures setting up their Discourse instance on several VPSes. pfaffman diagnosed the core issue: the domain debatehosting.co didn’t exist (confirmed by supermathie with an actual host lookup), and merefield noted that “SSL blocked my domain” was actually Let’s Encrypt rate-limiting after the domain was cancelled. Lilly asked for better handling of the “solution” selection, and the user later confirmed a successful install on another domain. read more

Support

  • Discourse-ID displays its own logo & name — Karthik_K1 reported that Discourse ID showed “Discourse” instead of their forum name. chapoi initially thought it wasn’t a bug, but after investigation, the workaround involved clearing the Discourse ID client credentials in the Rails console and toggling the feature. rishabh shared the admin button that triggers the same refresh and noted PRs are in place to automatically update ID metadata when the title/logo changes. read more

  • Is there any built-in chatbot? — Soumya_Ranjan_Mishra asked about built-in chatbot functionality beyond Discobot. RGJ pointed to the AI Bot and the Chatbot plugin, while awesomerobot explained that all the requested features (answering questions, auto-categorizing, auto-tagging) are available through Discourse AI, which ships with new installs—and powers ask.discourse.com. read more

  • Adding languages to the language selector — Karthik_K1 wanted to add Indian languages (Hindi, Telugu, Tamil, etc.) to the language selector. nat explained the selector is intentionally limited to Discourse-supported locales because it changes the whole UI (not just post content), and pointed to plugin creation and Crowdin translation as solutions. read more

  • Looking for storage details after update — m_terenui couldn’t find backup space and free disk info after the latest update. Moin linked the relevant discussions about the redesign, and awesomerobot provided the still-available admin/reports/storage_stats.json endpoint. read more

  • Bounce score does not reset when email address is changed — RGJ reported a bug where the bounce score persists when a user changes their email, expecting that a bounce score should be tied to the address, not the user. read more

  • Anyone else seeing a drastic drop in Support forum activity? — HAWK shared an interesting AI-agent perspective on why search volatility is changing community dynamics, noting Reddit’s Q2 traffic numbers and the risk of dependence on external discovery. satonotdead recommended a self-hosted searxng instance for those who want real information. read more

ux

#Site feedback

  • Meta error banner - MERGE_BRANCH deployment failed — Users reported a deployment error banner on Meta. tgxworld confirmed the fix, and david later explained it was caused by a system that deploys git branches for testing, and that the error wasn’t supposed to be displayed to everyone. read more

Activity by the @team Group

The @team group had another massive week, engaging deeply across the platform on testing, feedback, and product development. Here’s what caught the team’s attention:

Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

It’s been a busy and productive week on Meta, with 499 new posts across 56 fresh topics. The @team has been especially active, shipping fixes, opening AMAs, and pushing forward major features like AI subagents, a redesigned admin dashboard, and the new Workflows system. The community also rallied around moderation safety, self-hosting upgrades, and privacy-AI discussions.

Key Stats

  • New posts: 499
  • New topics: 56

Top posters this week:

User Posts Likes received
Moin 53 96
awesomerobot 14 54
Don 14 51
merefield 20 41
HAWK 17 35
NateDhaliwal 21 35
sam 7 30
Falco 7 27
zogstrip 8 21
lindsey 6 20

Interesting Topics

#Announcements

  • sam announced Discourse AI subagents, a major upgrade that lets you delegate work from a main agent to specialized subagents—mixing LLMs, reducing context bloat, and increasing concurrency. The community quickly began imagining use cases like web researchers and fact-checkers, and Falco and sam shared plans to make skills more accessible. read more

  • renato unveiled a sticky bar for pinned chat messages, so important channel pins now stay visible at the top of the chat while you scroll, with tap-to-jump navigation between multiple pins. read more

  • The Composer Redesign testing thread continued with chapoi implementing a wave of fixes based on community feedback—ranging from tag button cutoffs to the rich text editor’s quirks. Testers like Canapin and per1234 provided detailed feedback, and chapoi is now refining title input and the markdown/preview split. read more

  • chrisr and the team walked self-hosters through the PostgreSQL 18 upgrade, fixing broken multisite upgrades and sharing detailed rollback steps. Users like agemo and Andrew_Rowe reported their own migration experiences, including disk-space gotchas, and Moin helpfully documented a manual dump-and-restore workaround. read more

  • The Workflows preview continues to spark excitement. lindsey and j.jaffeux recommended using Workflows even for simple automations due to flexibility and better visibility, and users are already exploring how it replaces the older Automations plugin. read more

  • sam announced delegated vision for AI, enabling text-only models like DeepSeek v4 Flash to use the full Discourse AI feature set by handing off image understanding to vision-capable models like Qwen or Gemma. read more

  • The unified topic list view is rolling out, but community members like Damian_Boon and soraiden are asking how to keep a simple “new topics by date” URL for social-style forums. jordan.vidrine confirmed the change is moving to permanent and will be merged into core. read more

#Feature

Support

#Enterprise

#Self-hosting

#Data & reporting

#Plugin

  • The Custom Wizard Plugin saw a flurry of activity as Lebron and Eviepayne reported fields, tags, and group settings being cleared on save. angus responded with multiple PRs (#318, #319), fixing the category and tag issues, though some edge cases around theme selection and signup redirects remain. read more

  • Don released the Custom Splash HTML Builder, a plugin for fully custom splash screens with admin-defined HTML/CSS—originally motivated by mobile performance concerns with SVG animations. agemo praised it as a long-awaited solution for better branding during slow connections. read more

#Community Building

  • OS_Corsair opened [“How do I grow my community?” and received mixed responses. While Moin and NateDhaliwal offered thoughtful questions about audience, structure, and value proposition, the topic eventually veered off-track and was closed by moderators. It’s a good reminder that a clear, specific question yields much better advice. read more

Activity by the @team Group


Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

Welcome to your weekly digest of everything happening on Meta! This week the forum buzzed with AI-themed debate, major new admin features, and plenty of helpful community troubleshooting. Read on for the key stats, the most interesting discussions, and a rundown of what the @team has been up to.


Key Stats

Over the last 7 days, the community produced 576 new posts across 65 new topics. A big thank you to everyone sharing knowledge, reporting bugs, and helping fellow admins!

Top users this week (ranked by likes received, with post counts):


Interesting Topics

#Announcements

  • lindsey announced that the admin dashboard can now identify likely crawler traffic, separating automated bots and scrapers that run real browser JavaScript from genuine anonymous visitors. ted asked whether likely crawlers still count toward the monthly pageview limit — @lindsey confirmed it’s undecided — while kris.kotlarek noted the detection also works for logged-in users, having found TL0 scanners on Meta itself. read more

  • rishabh published the Current Projects – August 2026 newsletter, recapping recent work on dashboard improvements, the Events plugin, AI Image Captions v2, and a new Kanban plugin. satonotdead asked whether Zoom livestreaming would support Livekit or Jitsi alternatives, and awesomerobot explained that Livestream and Resenha are on separate development paths — with YouTube, Twitch, Kick, TikTok, Instagram, and Facebook already supported. read more

  • sam released a new admin-only feature for detailed AI logs at /admin/plugins/discourse-ai/ai-logs, complete with retention controls, streaming response decoding, and rich filtering. nickdb praised it as a great tool for tracking automatic translation, and floated the idea of an auto-refresh option. read more

  • zogstrip showcased a change where the empty tag picker now suggests tags from your 10 most recent topics instead of site-wide popular tags. sren-1 worried this creates a self-reinforcing loop that reduces tag diversity, while satonotdead suggested a middle-ground toggle — and zogstrip agreed it’s worth experimenting with. read more

  • Falco announced a complete refresh of chat notification sounds, with five new synthesized sound packs — Classic and clean, Soft marimba, Retro 8-bit, Playful bubble, and Ethereal glass — each with distinct tones for messages and mentions, inspired by experiments in Resenha. read more

#Community Building

  • Divinebaboon asked how moderators deal with users who employ AI to auto-reply to threads in order to gain trust levels. merefield highlighted even sneakier sock-puppet patterns, mbauman noted the AI “load-bearing seams” usually show through, and HAWK argued for a first-principles approach: if the content is valuable, does it matter how it was created? satonotdead shared a custom karma-quest system designed to make automation boring. read more

  • The long-running thread on the drastic drop in community activity for Support forums continued with passionate debate. nickdb observed that AI-assisted volume is hard for small communities, mbauman shared that new posters are the biggest drop-off in programming communities, and Mevo pushed back on form-versus-content. HAWK pondered when “the snake starts to eat itself” if everyone blocks crawlers from fresh human content. read more

  • HAWK launched Show us your Workflows, revealing a Weekly Update Reminder workflow that serves progressively worse CSS to teammates who delay their check-ins. chapoi admitted it was “the ugliest theme I’ve ever made,” zogstrip explained the LLM classifier and data explorer logic, and nickdb shared a simpler workflow that auto-corrects misplaced categories based on tags. read more

  • The philosophical thread asking Can money be the only moderator of a forum? continued, with awesomerobot explaining why subscription models beat microtransactions due to payment friction, Mevo citing YouTube’s ad-revenue approach, and satonotdead linking a 1999 essay on micropayments and mental transaction costs. read more

Support

  • Ryan_Scott reported the calendar was down for all ~1,200 users after updating to 2026.8, then self-resolved it by re-enabling the discourse post event enabled site setting. awesomerobot confirmed the team identified and applied a migration fix to prevent it from happening to other sites. read more

  • sk-or-v1-contents reported flaky search behavior with stop words and smart quotes. awesomerobot explained that words like it, we, and don't are excluded from indexing because they appear too often, and that quoted phrases require exact matches — prompting satonotdead to wonder whether search itself needs some refactoring love. read more

  • Jagster couldn’t see AI-translated post content after switching their interface language to English. Moin explained that the Content languages preference controls this — remove Finnish from understood languages, or leave the field empty, and translations will appear as before. read more

  • Joshua8600 reported that auto-bumped topics no longer show unread indicators after upgrading from February to July 2026. Moin traced it to changes in how small action posts are tracked, noting this may be why bumps no longer mark topics as unread. read more

  • satonotdead asked how to move the New Topic button on Horizon to a floating bottom-right position. chapoi provided working CSS, diagnosed the stacking-context issue caused by a position: sticky parent, and suggested a z-index: 1 fix on the sidebar-wrapper. read more

development

#Self-hosting

#Theme Component

  • Don shipped several updates to the Topic Preview Modal: a new open_all_topic_links setting, nested view support, a desktop/mobile toggle, plus fixes for Horizon’s high-context topic card mode. Jagster and joo reported edge cases that Don quickly patched in follow-up commits. read more

  • satonotdead explored adding a New Topic button and dynamic reply behavior to the F NAV Mobile Navigation Tabs component. Don responded by adding a /new-topic destination option and clarified that positioning relies on the --f-nav-height variable. read more

#Plugin

  • j.jaffeux answered community questions in Discourse Workflows, sharing a data-explorer workflow node example for retrieving user info and demonstrating the bump topic operation. patrickemin asked about filtering new-user triggers by activation status, and Aurora confirmed success in German. read more

  • Falco detailed major Resenha updates: reworked WebRTC controls for noise suppression, auto gain control, and echo cancellation; three AI noise suppression models (RNNoise, DTLN, DeepFilter3); and direct 1:1 calls which are disabled by default and can be restricted by group. read more

#Translations

  • happyhappy asked about adding a Basque language interface to Discourse. Moin explained that new locales are added once roughly 50% of the software is translated on Crowdin, with Basque currently at 13%. Undeterred, happyhappy began rallying native speakers and discovered the 100,000+ strings awaiting translation. read more

Activity by the @team Group


Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

Key Stats

It was another busy week on Meta, with 51 new topics and 453 new posts created between 2026-08-23 and 2026-08-30. Community members were in a generous mood, racking up thousands of likes as discussions ranged from brand-new admin tools to deep theme customisation and Workflows experiments.

Top users by likes and posts:

User Posts Likes
lindsey 4 38
Don 21 37
Andrew_Bond 12 36
satonotdead 34 36
Moin 26 32
awesomerobot 12 29
ErespawN 7 27
NateDhaliwal 15 25
tgxworld 2 25
gilles 17 25

Top Discourse Team members this week were lindsey, awesomerobot, tgxworld, sam, and chapoi, whose work is detailed in the Activity by the @team Group section below.


Interesting Topics

#Announcements

  • Site traffic explorer for new admin dashboard — tgxworld unveiled a new admin-only Site Traffic Explorer as part of the redesigned admin dashboard, offering filters for dimensions such as URLs, referrers, countries, networks, browsers, and IP addresses. The explorer analyses up to 200,000 pageviews by default, configurable to 1,000,000 via the site_traffic_explorer_event_limit setting. In the thread, tgxworld confirmed there are no current plans for event tracking like Umami, and noted that badge-related URLs dominating Top URLs look like bot traffic with a 100% bounce rate. read more

  • New drag-and-drop support for managing custom sidebar content — lindsey announced two new drag-and-drop behaviours that make building custom sidebar sections much easier: you can now drag any link directly into an existing custom section (triggering the Edit modal) or drop it at the bottom of the sidebar to create a brand-new section. The built-in Categories and Tags sections are excluded from rearrangement. read more

  • Discourse MCP the next version — sam announced Discourse MCP v0.3, which ships with a whopping 131 tools compared to 25 in 0.2.9, introducing a new “toolsets” concept that lets you expose features ranging from workflow generation and administration to AI configuration, analytics, and theme creation. Falco pointed to the original announcement video for inspiring use cases. read more

  • Discourse Calendar is now Discourse Events! — lindsey announced the rebranding of Discourse Calendar to Discourse Events to better reflect the plugin’s expanding feature set, highlighting recent improvements including easy event categories, more flexible RSVPs for recurring events, integrated livestreaming, and support for Zoom webinars. read more

  • August 2026 monthly release — loic published the release notes for v2026.8.0, along with patch releases for v2026.7.2, v2026.6.3, and v2026.1.8. elmuerte reminded everyone that this is the final month of support for the 2026.1 old-ESR line. read more

  • Help Us Test the Composer Redesign — The composer redesign continued to draw passionate feedback. chapoi said toolbar customisation is a desired idea but not part of the current styling-focused redesign, while sren-1 cautioned that mobile-first changes shouldn’t come at the expense of desktop users’ muscle memory. nickdb countered that desktop-only communities are a shrinking minority, and j127 raised contrast concerns for the active input border. read more

#Community Building

#Theme component / #Theme

  • Topic Preview Modal — Don iterated rapidly on this popular theme component, adding configurable mobile dismiss gestures (None/Grip/Gesture), native Back-handling that closes the modal without losing your place in the topic list, optional haptic feedback on Android, and a dedicated timeline modal. Extensive testing feedback came from Damian_Boon, Jagster, and satonotdead across iOS and Android. read more

  • FKB Pro - Social theme — Don announced FKB Pro v2, a substantial under-the-hood update with a more flexible desktop topic list layout, better responsive behaviour for narrow screens and overflowing content, and performance optimisations for off-screen topic cards. gilles reported a mobile category-heading layout bug, which Don addressed with a CSS grid-based fix. read more

  • Guest Gate Theme Component — Don shipped Guest Gate v2.0, a major update that moves beyond simple page-view limits to support multiple trigger types — page views, time, scroll depth, lightbox opening, or any combination — along with configurable delays, optional analytics, and a completely rebuilt trigger system. read more

#Plugin

  • Discourse Workflows — A huge week for Workflows. Ethsim2 opened PRs adding Event actions (Close/Open event) and a generic Event → Set attendance operation, while j.jaffeux confirmed a native Event node is arriving next week and fixed pm_tags_allowed_for_groups errors for AI agent tagging. putty and AJ_Quick shared their own workflow experiments and got helpful troubleshooting. read more

  • Animated Avatar — Alteras pushed two urgent fixes for the animated avatars plugin affecting Discourse v2026.8+, resolving the key not found: "resize_animated" error and a subsequent malformed gifsicle --crop argument bug. akanora and satonotdead confirmed the fixes work, though animated WebP support remains a future possibility. read more

  • ProxyTracer: VPN & Proxy Blocker — ProxyTracer engaged with a lively community discussion about Cloudflare template compatibility, floated an hCaptcha middle-ground option (instead of outright blocking) for privacy-conscious VPN/Tor users, and responded to questions about mobile network IP/ASN handling and login attempt visibility. read more

  • See TL3 Progress — merefield suggested expanding the plugin beyond TL3 into a whole “Trust Level Progress Meter,” and NateDhaliwal agreed a rework is possible. EricGT noted the timing is excellent as TL3 work nears completion, and saw potential for automating guidance for TL0 users stuck on entry requirements. read more

Support

ux

#Site feedback

  • When was this new Search page added? — NateDhaliwal spotted a redesigned Search page here on Meta and wondered if it was a Meta-only experiment. Falco revealed it’s v2 of Conversational AI Search coming to Discourse AI, with a full announcement expected next week. read more

  • Search icon covers search input — Moin reported the search icon overlapping the input text in the header banner. awesomerobot explained Meta is running a testing branch and the overlap appears for users (and logged-out visitors) with the “Enable AI search discoveries” preference unchecked — with a fix promised soon. read more


Activity by the @team Group

The Discourse team had a notably productive week across announces, bug squashing, and community support:

Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

Key Stats

It’s been another action-packed week on Meta! Over the last 7 days, the community produced 526 new posts across 57 new topics, with several major product announcements sparking lively discussion.

Here are the top contributors by likes and posts:

User Likes Posts
Falco 109 23
mcwumbly 103 26
rishabh 35 8
satonotdead 30 38
nat 28 8
Don 25 13
sam 24 12
merefield 21 10
lindsey 20 3
Ed_S 19 19

Interesting Topics

#announcements

  • Voice is here! Falco announced that the experimental Resenha project has graduated into Voice, a Discord-style voice and video rooms plugin now bundled with every Discourse install, bringing peer-to-peer WebRTC calls directly into the sidebar read more. supermathie cheekily replied: “I think you mean Discourse-style voice and video rooms?” read more. pmusaraj confirmed the feature can be restricted by group read more, while satonotdead helped users get up and running, including Jagster who eventually found room deletion in the settings tab read more.

  • Boards goes core. mcwumbly announced the new Boards feature — configurable, drag-and-drop kanban-style boards — is bundled directly into Discourse core, available on Business and Enterprise plans read more. A companion plugin topic clarifies that no separate installation is needed, and mcwumbly confirms it can be enabled via the Upcoming changes admin panel read more.

  • Ask AI for better search. nat unveiled Ask AI, a natural-language search feature that works alongside indexed search and offers follow-up questions, with a handy “Create topic” call-to-action when no good results are found read more. nat also noted admins can monitor token usage via the AI usage panel and restrict exposure to specific trust levels read more.

  • Admin reports get granular. lindsey announced that the Signups, New Contributors, and Accepted Solutions reports now show the specific users and posts behind the numbers read more. Zanbabe requested even deeper drill-downs read more, while sren-1 shared detailed use cases for additional data like primary email and trust level read more.

  • Design wizard. rishabh introduced the new Admin Design Wizard, which guides admins through picking themes, color palettes, fonts, and landing pages in just a few clicks after setup read more. itsbhanusharma called it “a significant step in the right direction” read more.

  • Automatically generated llms.txt. sam announced that all sites will ship a default llms.txt via an upcoming change, providing conservative, token-efficient instructions for AI crawlers read more. sam passionately defended the template — “I love how so many people on the Internet are experts on a technology that has only existed for a few months” — and urged admins to keep customizations minimal read more.

  • Discourse Admin Assistant. rishabh unveiled the Discourse Admin Assistant, an upgraded chat assistant that can answer questions, change site settings with approve/cancel buttons, help with moderation, and is aware of your hosting tier read more.

  • Current Projects, last issue. mcwumbly announced the final Current Projects post, as the team transitions to individual project topics in Contribute > Projects with a board view for at-a-glance status read more. He acknowledged the tradeoffs but hopes the new format lets people follow what interests them more closely read more.

Support & #self-hosting

  • GitHub outage takes down forums. A widespread issue saw logged-in admins unable to access their sites as Git operations hung. jeanas reported the issue, Ed_S traced it to DiscourseUpdates.has_unseen_features read more, and satonotdead confirmed GitHub was limiting unauthenticated downloads read more. Falco found and merged a PR to fix the underlying problem, with jeanas and Ed_S confirming the fix read more. The related Fatal: could not read Username topic had Arkshine sharing the HTTP/1.1 workaround read more.

  • Voice migration conflicts. Jagster hit a PG::UndefinedTable error when upgrading, caused by the old Resenha plugin’s migrations colliding with the new Voice plugin’s read more. nat diagnosed the conflicting migration versions and provided a SQL fix read more, which Jagster confirmed worked perfectly read more.

  • LiveKit API exposure. nicolsdennis, building a mobile client for Discourse communities, requested public booleans to determine if a site supports LiveKit read more. pmusaraj noted the voice plugin is still experimental and likely to change read more, while Falco pointed to the authenticated rooms.json API’s expected_transport field as the intended way to distinguish LiveKit from mesh rooms read more.

  • Gemini API key errors. Karthik_K1 struggled to connect Google Cloud Vertex AI to Discourse AI read more. Lilly walked through her working Gemini API configuration read more, and satonotdead recommended a LiteLLM proxy to use GCP credits with low latency read more.

  • Odd spam attacks. LordOfBikes reported a surge in spam registrations with random strings in pronoun fields, and shared their network-blocking strategy read more. one1 recommended hCaptcha as a complete elimination of the specific spam type read more, while Ed_S added a mandatory “Interests” user field to help human moderators read more.

#feature

  • Granular camera and screen permissions. Luna_Mora requested that camera and screen-sharing permissions be separated and made group-based rather than an all-or-nothing toggle, drawing on their experience locking down a Discord community read more. Falco confirmed a PR was ready to deliver exactly that read more.

  • Category moderators managing membership. happyhappy asked for category moderators to be able to add/remove users from private sub-categories read more. mcwumbly pointed out that group owners already have this ability through the group membership page read more, and later shared a convenient sidebar path to manage groups read more.

  • Delete topics anytime? emilio requested the ability for users to delete their own topics indefinitely, beyond the arbitrary 24-hour limit read more. Moin highlighted the hardcoded limit in the code read more, and Ethsim2 suggested making it configurable while retaining the existing posts_count <= 1 restriction read more.

  • Permanent deletion, simplified. emilio also asked for an option to truly delete topics without having to delete every post individually read more. Ethsim2 delivered an opt-in per-admin implementation that permanently deletes the topic and all replies, now up as a ready-for-review PR.

#projects & #plugin

  • Kanban v2 → Boards. mcwumbly debated the naming for the new kanban plugin — “kanban” vs “boards” vs something else — with community input read more. The discussion helped shape the decision to merge the plugin into core as Boards read more, and martin confirmed the merge read more.

  • Built-in MCP server. mcwumbly shared plans for a core MCP server served at /mcp, replacing the client-side MCP and enabling cloud harnesses to integrate with Discourse with permission-aware access read more.

  • Workflows gets new triggers. In the Discourse Workflows plugin topic, j.jaffeux responded to a request for AI-driven tag grouping, promising a tag-created trigger and tag-group node read more, then promptly shipped the commits.

Community Building

  • Show us your Workflows. sam and j.jaffeux engaged with community members sharing their workflow automations read more. per1234 shared an excellent Discourse Update Notifier workflow that posts to a dedicated topic after each forum update, providing transparency for UX-averse members read more.

bug

  • Signup rate-limit regression. HBP reported that a new rate limit on /u/check_username.json was blocking normal signup flows, as the username availability check can hit the limit during normal typing read more. southpaw confirmed a fix is in the works read more.

  • Impersonation + 2FA trap. Eviepayne found they couldn’t end impersonation when the user had enforced 2FA read more. Alteras quickly fixed it.

#theme-component

  • External Link Shield v2.0. Don released a major update to the External Link Shield theme component, swapping hand-maintained SVG mask-icons for real icon elements, adding settings for icon position and colors, and fixing an anonymous-user crash read more. Moin suggested using the icon setting type, which Don promptly adopted read more.

Activity by the @team Group

The @team group has been exceptionally active this week. Here’s a rundown of their contributions:

Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

It was a busy seven days on Meta, with 501 new posts across 72 new topics. The community saw major new feature announcements, deep design discussions, plenty of bug squashing, and an extraordinary amount of creative tinkering — from voice rooms to AI-built themes. Here’s the weekly recap.

Key Stats

:bar_chart: Last 7 days: 501 new posts · 72 new topics

Top users by activity and likes received:

User Posts Likes received
Moin 45 64
sam 13 52
Damian_Boon 19 43
martin 9 37
Falco 9 32
nat 13 26
awesomerobot 14 26
satonotdead 58 26
lindsey 2 23
zogstrip 6 19

Interesting Topics

#Announcements

#Community Building

#Extras

bug

#Self-hosting

  • Jagster’s Android users lost their virtual keyboard in the RTE while iOS users were stuck in Markdown. Moin’s device console revealed the cause: a CORS-blocked asset from a CloudFront/S3 misconfiguration. david explained the long-standing S3/CDN caching quirk (CDNs caching responses without Access-Control-Allow-Origin), and after some CloudFront cache invalidation, the issue was resolved. read more

Support

#Feature

ux


Activity by the @team Group


Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

Week of 13–20 September 2026

Key Stats

It was another busy week on Meta, with 386 new posts spread across 59 new topics. Here are the top contributors by posts and likes received:

User Posts Likes
Moin 43 52
martin 10 41
awesomerobot 18 40
nat 7 33
david 5 31
satonotdead 21 22
Damian_Boon 11 18
mcwumbly 6 17
mbauman 12 16
Don 5 14

A special shout-out to Moin, who continues to be an absolute machine in the Support categories, and to the @team members who shipped an impressive number of fixes and announcements this week.


Interesting Topics

#Announcements

#Feature

#Community Building

#Self-hosting

Support

ux

bug

#Theme component

  • Don added an excluded_categories setting to the Topic Preview Modal, so categories like wikis, glossaries, and docs can keep their sidebar without the modal. He also fixed two related bugs around nested views and new-topic dots read more.

  • Don released a new Community Support theme component for configurable donations, with a preview available on the theme-creator site read more.

development

  • david published @discourse/update-skeleton on npm, making it easy to update existing themes and plugins to the latest recommended GitHub Actions and linting configs — just run pnpx @discourse/update-skeleton@latest in your repo read more.

Activity by the @team Group


Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

Welcome to the weekly roundup of activity on meta.discourse.org for September 20–27, 2026. It was a busy week, headlined by a major debate about AI-generated plugins, several experimental UI announcements, new Markdown endpoints in core, and a flurry of bug fixes from the team.

Key Stats

  • New topics: 54
  • New posts: 426
  • Top users this week (likes / posts):
User Likes Posts
awesomerobot 66 15
chapoi 43 8
sam 42 9
pmusaraj 41 11
Canapin 34 7
satonotdead 30 35
darkpixlz 30 11
RGJ 24 15
Moin 21 19
Kianga 21 4

The @team group was exceptionally active, with awesomerobot, chapoi, sam, and pmusaraj topping the leaderboard — details in the team roundup below.

Interesting Topics

#Announcements

#Site feedback

  • The week’s defining debate: darkpixlz proposed requiring LLM-generated themes and plugins to be tagged as such for transparency. sam pushed back forcefully, arguing the real problem is the lack of security vetting for third-party code — and revealed he’s written only “a handful of lines of code” by hand in about 10 months, developing Discourse primarily with AI agents. He also flatly refused a “developed with 93.2% AI” sticker system, but offered to share his workflows. Kianga and darkpixlz argued for transparency on ethical and environmental grounds, chapoi noted even core is now heavily AI-developed, Canapin shared how a vibe-coded plugin nearly shipped with serious security flaws, and Lilly said she uses AI but won’t label her plugins. philh responded by creating DiscourseSkill.md as a practical review tool. read more

Support

bug

#Feature

ux

#Plugin

#Theme component

development

  • philh created DiscourseSkill.md, a skill file to help AI agents review Discourse plugins and themes for quality — spun out of the LLM tagging debate. After Moin’s sharp feedback that the initial structure didn’t match real theme layouts, the review method was expanded to classify plugins vs. themes vs. components and inventory more file types. read more

blog

Activity by the @team Group

Members of the @team group were out in force this week, driving announcements, shipping fixes, and answering support questions across the forum.


Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

A warm welcome back to your weekly round-up of everything happening on Meta! It’s been a busy seven days (27 September – 4 October 2026), full of sharp bug reports, beautiful new themes, and a very welcome announcement for self-hosters watching their RAM. Grab a coffee and let’s dive in.

Key Stats

Over the last 7 days, the forum saw 219 new posts across 37 new topics, with a great mix of support questions, bug reports, feature discussions, and community showcases.

Top users by posts and likes:


Interesting Topics

Grouped by category, here are the most interesting discussions from the past week.

#Announcements

tgxworld announced a significant RAM usage reduction for self-hosters, improving how Discourse shares memory between processes inside its container. One of their internal containers dropped from roughly 1.9 GB to 1.3 GB, and Editor0732 saw an even bigger win on their site: 11.8G → 10.5G after rebuilding. The improvement is available on main and backported to the 2026.9, 2026.8, and 2026.7 release branches — read more.

The bundled Voice feature continued to receive real-world feedback, with SkyeDragon reporting that stereo mics are transmitted without downmixing, which can result in audio only in one ear for some listeners. Falco noted the system downmixes on every quality below maximum, and Thomas_Rother shared positive experiences with groups of up to five people while asking about running a separate LiveKit backend with Docker Compose — read more.

The category hashtag floating cards and subcategory hashtag display improvements drew praise plus some UX pushback from stephtara, who found the click-to-open card an unnecessary extra step compared to a hover preview.

Feedback continued on the experimental user sidebar navigation, with Luna_Mora noting it’s a worse experience for sites using the dropdown navigation menu, and satonotdead calling for a unification of overlapping submenu options like profile, preferences, and account settings.

ux

terraboss released Terraglass, an open-source frosted-glass theme with carefully considered light/dark palettes, then iterated quickly through versions 1.1.0 and 1.2.0 adding an optional header tint plus glass menus and dialogs. NateDhaliwal pointed him toward the theme_authors group for proper categorization, and the theme is now live on several sites — read more.

terraboss also ran into a tricky backdrop-filter blur issue: transparency worked on .menu-panel, but backdrop-filter: blur() had no effect. awesomerobot explained that an element with a backdrop-filter becomes the root for the effect, so descendant panels can’t blur content beyond the header, and provided a clean pseudo-element workaround that terraboss confirmed fixed it — read more.

Ed_S reported that the red “last visit” line is almost invisible in dark mode on iPhone. nat filed a fix (PR #44177) with improved contrast for both dark and light modes — read more.

#Self-hosting

In a wide-ranging backup and recoverability discussion, Canapin asked for the most reliable ways to guarantee a forum can always be recovered. NateDhaliwal recommended S3 with daily backups, pfaffman emphasized keeping YML configs alongside off-site copies, Lilly suggested Cloudflare R2 with dual container builds, and Ed_S offered a threat-modeling framework covering fire, provider lockout, and dead admins — read more.

agemo and Ed_S collaborated on a deep debugging thread for an “Oops” error locking out admin accounts, eventually tracing it to has_new_upcoming_changes in current_user_serializer.rb choking on duplicate last_visited_upcoming_changes_at custom fields. Ed_S shared Rails console commands to inspect and flip the offending user option, and the thread concluded it likely needs a core bug fix — read more.

Support

burke asked whether user_badge webhook payloads could include username alongside user_id, kicking off a thoughtful discussion about least-privilege API keys and why user IDs are an internal convention. RGJ pointed out that -1 is a valid user id (the system user), and putty suggested using Discourse Workflows as a workaround; burke later shared a native JavaScript HMAC-SHA256 snippet to sign Workflow HTTP requests — read more.

awesomerobot clarified what the ‘Topic or post deleted’ filter in the mod queue actually does: it only shows held posts withdrawn before approval, and suggested renaming it to “Queued post withdrawn.” He also explained that deleted posts are soft-deleted and recoverable, and pointed to /latest?status=deleted as the right place to find deleted content — read more.

Several sites were briefly switched to read-only mode during scheduled maintenance. Heather_Phillips asked why her site was suddenly read-only, and NateDhaliwal pointed to the maintenance topic, while tgxworld apologized for the inconvenience and directed users to status.discourse.org for future announcements — read more.

bug

manut reported a fresh dev container logging ActionController::RoutingError (No route matches [POST] "/srv/se") in /logs. tgxworld confirmed the fix in PR #42712 by kris.kotlarek and backported it to 2026.7 — read more.

MachineScholar updated the Voice + LiveKit investigation to note that low-resolution video and stuttering persist even on LiveKit Cloud, so it isn’t a self-hosting issue. satonotdead suggested Apple’s WebKit restriction on iOS might be a factor, citing a UK CMA document, and Falco said he’d investigate in the coming weeks — read more.

RGJ documented an “Arrive at topic” invite permissions issue with detailed repro steps, and awesomerobot fixed it in PR #44201, noting the root cause was that the invite process couldn’t add users to automatic groups like trust_level_0 — read more.

manut also found the QUnit test runner fails to load dependencies on fresh dev instances, with bare specifier errors for plugins depending on other plugins; awesomerobot reproduced it in Firefox and submitted PR #44181 — read more.

jmx reported that Discourse AI silently drops parallel tool calls with Mistral during streaming: when a model returns several tool calls in a single streamed chunk, only the first runs, with no error logged. A minimal network-free repro was included — read more.

Sailor filed two related Discourse AI + Gemini bugs: an error event inside a streamed reply is ignored, causing partial translations to be stored as complete, and a request blocked via promptFeedback.blockReason being treated as an empty reply and never retried — read more.

#Plugin

Bitforo released the Crypto Ticker plugin, bringing live cryptocurrency prices (Bitcoin, Ethereum, Solana, memecoins…) to forums in six positions and four styles, with a CoinGecko-powered admin picker. NateDhaliwal asked whether normal stocks and indexes could be added, and Bitforo said yes, soon — read more.

#Theme-component

putty published a theme component that removes the parent category from inline category mentions, including an option to exclude specific categories. satonotdead noted the initial use of MutationObserver is discouraged in Discourse themes, and putty quickly reworked it to watch only the composer areas where no hook is available — read more.

The long-running Twitter Native Embed component got a new fork from terraboss, fixing a safe-mode crash and adding features like dark mode, no duplicate embeds, and fallback embedding of bare X links. Lilly reported the original still works fine on her site — read more.

#Feature

The popular request for a “Regular mode” or “sudo” for admins resurfaced, with nathank describing the frustration of not knowing what regular users can’t see or do; NateDhaliwal suggested pairing a temporary revoke_admin with a banner, and Jonathan5 proposed selecting from various trust levels and groups — read more.

The proposal to reduce local disk space by not redundantly gzipping backups gained more support, with adamengst noting doubled backup size causes failures on his site and pfaffman suggesting it could be a great pr-welcome candidate — read more.

nathank bumped the recurring events topic asking for individual event topics to be created from recurring events; Ethsim2 linked the open PR #43187 and shared lessons learned from maintaining core backports via after_code hooks — read more.

Community Building

The discussion on Building Communities That Think continued, with nukeador lamenting that real-time chat channels have drained engagement from forums and asking how to bring people back; satonotdead argued forums must offer unique value beyond chat, and Orioni shared an AI-summarization workflow to bridge Discord discussions into forum topics — read more.


Activity by the @team Group

The Discourse team was highly active across the forum this week, both shipping fixes and engaging with community feedback.


Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

Welcome to the weekly roundup! In the seven days from October 4–11, 2026, the community produced a steady stream of AI feedback, plugin releases, Workflows experiments, and self-hosting recoveries. Here’s what happened.

Key Stats

Over the past week, Meta saw 214 new posts and 39 new topics, with a lively mix of support threads, feature requests, and bug reports.

The top users by likes received (and posts made) were:

User Posts Likes
nat 5 27
merefield 16 26
pfaffman 5 17
NateDhaliwal 15 16
TripleU 3 14
zogstrip 8 14
sam 5 12
satonotdead 8 10
Falco 3 10
RGJ 7 9

merefield was the most prolific poster of the week with 16 posts, while nat collected the most likes through several high-impact replies on AI search and translated emails.

Interesting Topics

Announcements

  • Removing Uncategorized didn’t go as expected for some. gormus reported that despite allow_uncategorized_topics being false and an empty, unused category, the latest release left Uncategorized enabled for everyone — with two new topics already created in it. lindsey acknowledged the problem, and zogstrip explained the careful fix in PR #44385: the category will now only be deleted if it has never been touched, preserving sites that repurposed it. read more

  • Feedback on the experimental user sidebar navigation rolled in. southpaw noted that custom sidebar sections don’t appear in the contextual user sidebar inside PMs, disrupting workflows that rely on quick access to custom links. per1234 asked what “experimental” actually implies, and chapoi confirmed it means the change may be scrapped — so testing and feedback now genuinely shape its future. read more

  • Calls to keep the old new-view tabs grew louder. meiadeleite asked for an opt-out in the unified new view topic, while Gunnar opened a dedicated feature request to make Unified View optional permanently and preserve the “Unread” tab workflow, including in Discourse Hub. read more

  • Rebuilding for lower RAM worked. After Discourse advised self-hosters to rebuild the container to reduce memory usage, scavin shared results showing Pitchfork memory dropping from ~2.7–2.8 GB to ~2.3–2.45 GB — roughly a 15% (~400 MB) reduction that stayed stable after five days. read more

  • Composer redesign icon confusion. agemo reported seeing a “share type” icon for the “Reply as/to…” button in the composer while using the Meta Branded theme. chapoi identified it as a fontset mapping issue specific to that theme, with default-font themes unaffected. read more

UX

  • “Search is making me unhappy” sparked a productive AI-search discussion. pfaffman voiced frustration that both keyword search and the new AI search (tagged search and ai) missed a recent Postgres 18 upgrade announcement. nat responded by updating the AI prompts to value recent announcements more highly, and pointed out the toggle to turn off the AI view. RGJ shared a similar stale-result experience when searching for post custom fields documentation. read more

  • Badge count wording tripped someone up. ganncamp pointed out that the award count shown on badges reads as instance-wide rather than personal — prompting the question, “Yeah, but how many do I have?” — and suggested different wording. read more

Community Building

Feature

  • GitHub repo oneboxes could get richer. merefield opened PR #44289 to add language, star rating, and fork count to GitHub repo oneboxes (tagged onebox). After discussing the risk of stale metadata, he settled on a “data correct at” disclaimer rather than a polling system, keeping complexity down. read more

  • Deeply nested [details] blocks caused real pain. scavin reported a post with 24 levels of nested [details] sections that slowed Firefox to a crawl and made the .md endpoint take ~20 seconds. Ethsim2 investigated, found exponential recursive conversion in the Markdown endpoint, opened PR #44461 with a ~31× speedup, and is also working on a proposed details_max_nesting_depth site setting. read more

  • ActivityPub handles should be clickable. tobiaseigen suggested auto-linking @handle@domain into a clickable [@handle@domain](https://domain/@handle) so fediverse users can follow people without copy-pasting. read more

  • Translated emails are here. nat announced that notification and activity summary emails now use available translations when content localization is enabled, via PR #44240. Sailor immediately flagged a remaining timing gap where push notifications for new posts are still sent before the translation is stored. read more

Extras

Plugin

Bug

Self-hosting

Support

Activity by the @team Group

The @team group was highly visible this week across AI search, Workflows, and infrastructure fixes.

Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

“In 2013, Jeff Atwood, Robin Ward, and Sam Saffron launched Discourse with one mission: to give people a place to communicate together. For thirteen years, we’ve built for that mission.” — From the Discourse in 2027 blog post.

It was a busy week across Meta: 209 new posts and 40 new topics covering everything from AI agents and voice rooms to Halloween themes and the composer redesign. Here’s what happened.

Key Stats

Over the last 7 days, meta.discourse.org saw 209 new posts and 40 new topics, with the following members making the biggest splash:

User Posts Likes Received
awesomerobot 9 58
zogstrip 14 30
sam 5 28
nickdb 7 22
Falco 6 19
system 1 16
saquetim 1 13
merefield 12 9
satonotdead 11 8
supermathie 3 7

Notable activity came from the @team group, with awesomerobot, zogstrip, and sam leading the way in likes, while Falco, saquetim, chapoi, supermathie, rishabh, david, and manuel all contributed fixes, announcements, and support.

Interesting Topics

#Announcements

  • sam unveiled built-in support for decision models — a new class of fast, cheap AI classification models championed by TypeSafe and now offered by OpenAI and CloudFlare. satonotdead immediately asked whether they could act as a “gate” to route queries to the right subagent, and sam confirmed it’s something he wants to explore. read more

  • awesomerobot announced that chat channels can now be set as the Discourse default homepage, falling back gracefully when users lack access, and making it easier than ever to launch a chat-first community. read more

  • zogstrip introduced the “Update whispers allowed groups default” upcoming change, which makes whispers available to staff out of the box so the feature stops hiding in plain sight. read more

  • saquetim shipped a unified reordering control across all list-type settings — dragging, clicking, keyboard arrows, and screen-reader announcements all now work consistently. read more

  • The Voice rooms megathread continued with a lively privacy discussion: Thomas_Rother flagged GDPR concerns about default Google and Twilio STUN servers, Falco pointed to a guide for configuring your own STUN/TURN, and pacharanero asked about per-room group restrictions — Falco confirmed a unified access-control UI is on the roadmap. read more

  • Composer redesign feedback kept flowing: BeefofAges reported that Tab+Enter no longer submits a post on desktop, chapoi explained the accessibility rationale and pointed to Ctrl/Cmd+Enter, while RobinTS shared a screenshot of a missing mobile toolbar. awesomerobot traced that to a stale localStorage flag and opened a fix PR. read more

  • rishabh announced that the Admin Assistant can now write and edit Data Explorer queries from scratch, helping admins get community insights without learning the query language. read more

  • Feedback on email-code signups continued: MDNJ praised the low-friction signup flow but found the later password screen confusing for non-technical users, and noted the code expiry window feels very short. read more

  • tobiaseigen made a passionate plea to keep the ai_bot_enable_docked_composer setting, arguing that the docked composer breaks muscle memory for post writing — “please please, pretty please :face_holding_back_tears: not do that!” read more

blog

  • The companion topic for the “Discourse in 2027: Building Together” blog post opened, with eisammy celebrating Discourse’s longevity and its commitment to open communication as “one of the best CMS of the last decade.” read more

#Theme

  • awesomerobot released Concord, a self-hosted, open-source Discord alternative: a theme that turns Discourse into a channel-based community with text, voice, and forum channels while keeping your policies in your own hands. read more

  • Just in time for October, awesomerobot also published the Spoopy Halloween theme — a dark, moonlit theme with gnarled branches, bats, fog, and a grave composer. scavin already added it as a limited-time theme on their community, and gilles shared his own inspired remix. read more

#Community Building

  • scottfsmith raised the alarm about AI agents signing up for accounts, citing a strange post from an iLands LLM agent. Lilly suggested Discourse Captcha, nickdb recommended layered defense with user-agent blocks and scoped AI bots, and robbie.morrison chimed in from the openmod forum with coverage of the phenomenon in Science. read more

  • Andrew_Rowe floated a “respect system” where trusted humans get weighted votes to counter AI trolling. nickdb cautioned that humans willingly proxying AI content would undermine such a system, and merefield wondered whether community network visualisation could help identify cabals. read more

  • In the long-running AI-responses topic, nickdb shared a custom theme component he built that locks the new-topic button for new users who haven’t spent at least 5 minutes reading — a clever attempt to break the cut-and-paste-AI-slop habit. read more

#Theme component

  • nickdb released the “Read Before New Topic” theme component, which requires recorded reading time before a user can create a topic — a potential anti-bot and community-quality measure that Heliosurge and eisammy both welcomed. read more

  • satonotdead published a theme component to disable all of Discourse’s built-in keyboard shortcuts (j/k, ?, r, l, b…), so members stop accidentally liking posts, leaving pages, or logging out. read more

bug

  • mentalstring reported a 500 error in the Review queue that only affected their most active moderator, caused by a query blowing past the 30s timeout. zogstrip found a clever optimization, merged the fix, and backported it to v2026.7, with mentalstring confirming it “nailed the issue.” read more

  • A Let’s Encrypt “unable to get issuer certificate” bug led jmx to share certificate chains and supermathie to correct the openssl verify command used in the Docker image, merging the fix after a good collaborative debugging session. read more

  • Falco pushed a fix for low-resolution camera video and one-way stuttering in self-hosted LiveKit voice rooms. read more

  • James_Wong documented the ReactionLikeSynchronizer repeatedly trashing 26,766 PostAction likes every hour, causing 500s and unread topics. zogstrip reworked the sync into batches so it no longer blocks major tables. read more

  • profcaju found that pressing c twice to create drafts from a topic page triggers a false “draft is being edited in another window” conflict, with the autosave returning HTTP 409. read more

  • scavin reported inconsistent behavior where emoji tags appear as “Create” options in the composer and genuinely new emoji tags disappear after posting, with a clean reproduction on main. read more

Support / #Self-hosting

  • Andro was startled to find a wave of bot accounts auto-created after updating, and sam explained the deliberate design: one user per enabled AI agent, replacing the old per-model accounts. Crocodilus_CZ, however, argued the change should have been opt-in and asked for removal instructions. read more

  • scavin asked whether it’s safe to truncate the 902 MB browser_pageview_events_backup table left over from the September migrations, since nothing in the application code references it anymore. read more

development

  • das-g asked how to run the plugin and theme .gjs migration codemods inside the Docker-based dev setup; david recommended hopping into d/shell and running the pnpm commands from inside the container. read more

Activity by the @team Group

Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…


Key Stats

October 18 – October 25, 2026

This week saw the Meta community buzzing with 53 new topics and a healthy 294 new posts, reflecting a week dominated by major design announcements, security patches, and community building discussions.

Top Users Posts Likes
david 8 50
awesomerobot 15 35
mcwumbly 9 26
chapoi 9 23
manuel 4 22
NateDhaliwal 16 20
sam 8 19
zogstrip 9 17
martin 8 14
keegan 1 14

Notably, david led in likes received, while NateDhaliwal and awesomerobot were the most active contributors by post count. The team collectively drove much of the week’s energy, with major announcements around the new sidebar, mentions tab, and Data Explorer tags setting the tone for a feature-rich week.


Interesting Topics

#SITE_FEEDBACK

  • manuel launched what he’s calling a sense of place feature — a new discovery sidebar for the Meta Branded theme that gives category pages dynamic navigation, resource panels, and scoped leaderboards. NateDhaliwal and Bas both expressed a “love it / don’t love it” sentiment as longtime users adjusting to the change, while Andrew_Bond called it “monumental” and built his own custom panel within hours. chapoi praised the dynamic navigation but flagged that the “spaces” nomenclature adds mild confusion alongside the existing category list. manuel responded that custom panels are the intended extension path, and shared the public demo component on GitHub. Read more

  • NateDhaliwal questioned the category colour overhaul on Meta, noting that documentation subcategories all lost their distinct hues and became a single orange. awesomerobot attributed the change to manuel’s Meta Branded theme work, and manuel explained the new palette is perceptually uniform, with each top-level category now carrying its colour down into all subcategories for consistent visual grouping. Read more

#PRODUCT_SUPPORT

events

#COMMUNITY_BUILDING

#ANNOUNCEMENTS

#THEME & #THEME_COMPONENT

ux

#FEATURE

bug

development

General

blog


Activity by the @team Group

This was a heavy week for the Discourse team, with major design launches, security patches, and feature announcements dominating the conversation.

david was exceptionally active, handling the CVE-2026-109618 security inquiry with a swift “no action required” answer. He renamed the stale “new/standard” editor labels within minutes of RGJ’s report, shipped the Node 22.23.4 upgrade hours after sandra.mccollum’s question, published the October 23rd intermediate releases, and unveiled the backup compression rework eliminating the 2× disk space penalty. He also helped diagnose a VSCode remote dev environment content-length bug for NateDhaliwal.

awesomerobot (Kris) was the week’s most prolific team member with 15 posts across 10 topics. Kris explained HDR gain map handling for davidkingham, announced the combined AI search experiment, provided a detailed moderation API walkthrough, diagnosed the passkey visibility issue for Drakon74, identified the DSA-driven suspension email change and acknowledged the community’s feedback, clarified category card behaviour, expanded the chat homepage options, explained new user profile visibility rules, updated the spoopy theme with chat sounds, and provided free-plan AI settings guidance to opalgeist.

manuel led the design conversation, launching the discovery sidebar announcement that anchored the week, sharing his own early impressions and engaging with community feedback. He also explained the new colour palette rationale in response to NateDhaliwal’s category colour query.

mcwumbly organised the first fortnightly community hangout, answered migration questions on the blog post, flagged ongoing backup work, and corrected the Boards documentation after nathank’s report.

chapoi contributed across a remarkable 9 topics: discussed the sidebar and “spaces” naming, raised concerns about hashtag cards, posted the grid layout change announcement, fixed the broken feedback link for Noble_Fish, explained email auto-linkify limitations, discussed composer fullscreen design philosophy, corrected the full-width component status, and pointed @satgo1546 toward the existing quote-jump feature request.

sam drove the bug-fixing engine: answered the bot removal question, acknowledged transparency gaps, shipped the AI bot fix PR, fixed the ad plugin category picker, resolved the SES/SNS bounce notification mismatch, patched the scalar tags 500 error, and suggested a workaround for AI agent PM migration.

martin continued the category hashtag refinements, proposing user preference options, shipping the hashtag shortening PR, and confirming the visual result. He also returned from leave to review the recurring events PR, shared status on boosts testing, guided @j127 to the Markdown endpoints setting, linked the subcategory shortening fix, and tracked granular permission progress.

zogstrip shipped the long-requested jump-to-quote highlighting, investigated a scroll-position regression reported by @singpolyma, answered a workflow trigger question for patrickemin, and pointed @singi2016cn to the /about page for total user counts.

keegan authored the new Mentions tab announcement, introducing a dedicated notification tab with badge counts and flexible admin rollout controls.

lindsey announced Data Explorer query tags and guided @FabledQuokka62 through chat display settings for showing user titles in large organisations.


Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

Key Stats

The week of October 25 – November 1, 2026 was a packed one on meta.discourse.org, bringing a flood of announcements, community engagement, and development progress.

  • Total new posts: 280
  • Total new topics: 52
  • Date range: 2026-10-25 → 2026-11-01

Top Users (Posts & Likes)

User Likes Posts
Falco 41 6
zogstrip 32 4
awesomerobot 32 12
sam 25 8
nathank 19 12
mcwumbly 17 9
NateDhaliwal 16 18
RGJ 14 4
tgxworld 13 5
merefield 13 10

Falco topped the charts with 41 likes, largely thanks to the Discourse Live announcement. awesomerobot was the busiest contributor with 12 posts, engaging across search, theming, and support threads.


Interesting Topics

#ANNOUNCEMENTS

development

#THEME / #THEME-COMPONENT

bug

#FEATURE

Community Building

ux / #PRODUCT-SUPPORT

General / #EXTRAS / #PRAISE

events


Activity by the @team Group

This section tracks the @team (Discourse Team) group’s engagement across the forum.


Honorable Mentions

Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

A weekly roundup of activity across the Discourse community forum, covering November 1–8, 2026.


Key Stats

The past seven days saw 229 new posts and 31 new topics across meta.discourse.org, with spam mitigation, UI/UX refinements, and workflow tooling dominating the conversation.

Top contributors by engagement:

User Likes Posts
putty 28 20
mcwumbly 21 7
saquetim 19 1
satonotdead 18 15
Falco 17 6
watchmanmonitor 16 7
mbauman 15 8
dax 14 3
Laurent 14 3
RGJ 14 7

Within the @team (Discourse Team) group, the most active members were mcwumbly (21 likes, 7 posts), saquetim (19 likes, 1 post), Falco (17 likes, 6 posts), awesomerobot (14 likes, 7 posts), and dax (14 likes, 3 posts).


Interesting Topics

#Announcements

  • saquetim unveiled the new visual index editor for Discourse Doc Categories, allowing admins to build sidebar indexes directly in the UI without maintaining a separate index topic. The editor supports sections, links with custom icons, and warnings for duplicate entries. Categories already using an index topic continue to work unchanged. martin confirmed the initial PR is merged behind an experimental upcoming change, with further refinements expected before moving to Alpha. Read more  ·  Update

  • sam announced that hosted Discourse communities now get pre-configured access to a decision model through the TypeSafe Jev / System One AI infrastructure. Self-hosters can mint a free key at the vLLM SR app. putty reported this solved a persistent pain point with auto-responder emails creating unwanted public posts, noting the workflow reliably caught and flagged every instance. Falco followed up with a PR to expose the model ID in the admin Models page, addressing a bug putty encountered when trying to reference it. Read more

  • The Live voice and video rooms plugin continued maturing: PandaKai7 reported audio issues on macOS, and Falco identified a networking bug forcing clients onto relays unnecessarily with Chrome and Safari. The fix rolled out to hosted sites within 48 hours, and PandaKai7 confirmed the improvement. Read more  ·  Fix confirmation

  • singpolyma raised a usability concern with nested replies: clicking a topic from the main list or a board can land users in a focused “viewing a particular post” view, forcing repeated clicks on “view full topic.” This was discussed in the ongoing nested-replies announcement thread. Read more

  • pmusaraj shared an update to Markdown endpoint caching for the core Discourse topic-list endpoints, reducing cache retention so older content lives in Redis for just one hour instead of the prior longer TTL.

  • The automatically generated llms.txt feature drew a question from darkpixlz about setting a custom version to prevent AI agent bombardment. NateDhaliwal pointed to the existing admin upload path under Security settings. Read more  ·  Answer

  • A Discourse community hangout (fortnightly) continued generating discussion: putty questioned the rationale behind using a single recurring topic vs. separate topics per event, and mcwumbly explained it matches the informal spirit. mcwumbly also outlined ground rules—casual, no recording, no fomo—and announced the next session will feature martin discussing Events, Boards, and future ACL/permissions work. Read more  ·  Notes  ·  Next session

  • The Reddit vs. Discourse blog post examining two incentive models sparked lively debate. mbauman challenged the post’s optimism by pointing to a reported drastic drop in community activity, asking how knowledge platforms sustain without new participants. satonotdead, Heliosurge, and hhf.technology offered perspectives on small-community resilience and the opportunity to detach from doom-scrolling. eisammy shared a detailed account of blocking AI crawlers and the resulting traffic challenges. Read more  ·  Community response  ·  Eisammy’s story

  • Andrew_Bond posted a visual update on his Xenforo-to-Discourse migration, sharing light-skin, right-side block, and spacing refinements after months of gentle tweaking. Read more

  • tobiaseigen discussed icebreaker strategies for new-community onboarding, describing a “water cooler” category pattern and an automation that awards a badge when new members respond to introductions. Read more

bug

  • Luna_Mora reported that Chat skips a block of messages when someone posts while you’re catching up on unread history—the view jumps from the loaded page straight to the live message, silently omitting everything in between. awesomerobot reproduced the bug and submitted a fix to core, noting it will ship with upcoming Discourse updates. Read more

  • Dannii found that the review queue shows notes belonging to other reviews when navigating between flagged items via notifications. After identifying the likely upstream fix, pmusaraj confirmed and backported the PR to the 2026.7 LTS line. Read more

  • satgo1546 documented topic timeline style regressions introduced during the fix for the “Jump to…” button in the reply-target modal: labels shift between left- and right-alignment depending on date length, and the reply count appears visually off on high-volume topics. Read more

  • thoka flagged that tag descriptions are no longer visible in any UI surface outside the dedicated tag page since PR #42005 removed the title tooltip for accessibility. awesomerobot clarified this was an intentional change and suggested the Tag Banners component as an alternative, while acknowledging the discoverability gap could merit a feature request. Read more

  • Dannii reported that mail-receiver ignores Authentication-Results DMARC/DKIM failures, allowing spoofed emails (e.g., an AMEX spam message and a forged support@ post) to pass through to Discourse as legitimate staged-account emails. Read more

  • Sailor confirmed that SES/SNS bounce notifications now correctly match EmailLog entries after upgrading to release/2026.10, closing a bug where bounces went unrecorded since 2026.7. nat had previously updated the site-setting descriptions to clarify when the SNS allowlist actually applies. Read more

  • RBoy continued to see an embeddings-search “still running” error, traced to Gemini returning 503 “model overloaded” responses. The errors are being logged across 13+ copies, indicating a systemic rate-limiting issue rather than a Discourse bug. Read more

  • twofoursixeight reported that a forum update deleted or hid a custom Patron badge that had been miscategorized as a voice badge. The badge URL now returns 404, and users who once held it no longer see it. Read more

  • Ed_S noted that the “There is 1 unread topic remaining” counter at the bottom of a topic is off by one when you are currently reading the last unread item. Read more

  • Ethsim2 observed that edited posts remain stale in DiscourseHub on iOS until a manual refresh, possibly tied to cellular handover during travel. Further testing is planned to isolate whether a network-path transition triggers a retry race. Read more

ux

  • Laurent returned to the spam-queue Approve/Reject button swap to report accidentally accepting spam due to the inconsistent “yes”/“no” labeling between review types. merefield, bartv, RGJ, and putty all echoed the confusion, with RGJ noting missing combinations like “delete and block user.” mcwumbly acknowledged the team had tried to address this last year but hit walls, and expressed intent to revisit with fresh eyes. Read more

  • Justin_Grimm2 asked how to surface active live-chat users without cluttering the header, especially on mobile. Falco showed an existing sidebar count indicator but noted he wasn’t a fan of the design. Jagster highlighted the already-tight header space, and Justin_Grimm2 proposed merging text chat and video chat into a single unified messaging surface. Read more  ·  Falco’s mockup

  • watchmanmonitor was confused to find all 996 users listed under the “New Users” admin tab, even long-standing staff. olivia clarified this is expected—the tab simply sorts by registration date, not activity. RGJ suggested removing the tab entirely since it’s redundant with sorting the Active list by Created, and Ed_S proposed renaming to “By Age” vs. “By Activity.” watchmanmonitor ultimately suggested “Created” as a clearer label. Read more  ·  RGJ’s suggestion

  • olivia responded to satonotdead’s request to restore the translated-texts comparison view, asking for a specific example of missing data. satonotdead clarified that the old view showed both the original and the customized string side-by-side, while the new view only shows the default (unused) value. Read more

  • supermathie revisited the relative-time formatting issue, noting that a 31-day auto-open setting gets converted to “1.5 months” and then rounded up to “2 months,” losing the precise intent. Read more

  • louk and others in the avatar-menu thread argued for renaming the “Billings” menu item to “Subscriptions” for clarity. Read more

  • putty proposed that Meta’s new sidebar (part of the meta-redesign-2026 effort) was initially jarring but is “leaning more and more towards ‘I like it’” after a week of use. Read more

#Feature

product Support

  • mbauman initiated the week’s biggest thread by tracking down a massive spam-account wave: hundreds of unactivated, never-“seen” accounts created via API or direct endpoint hits. awesomerobot explained the mechanics and pointed to the existing auto-delete setting for unactivated accounts. putty, watchmanmonitor, and Danika_Dakika shared parallel experiences—268 accounts from a single IP (89.124.71.104), another wave with distinct IPv6 addresses using throwaway email domains, and spam DMs templated around topic titles. Mitigations included reCAPTCHA v2, tightened PM limits, email-domain blocklists, and watched-word filters. Read more  ·  IP block  ·  Danika’s summary  ·  Related report

  • Tonja discovered that after updating to Discourse 2026.10.0, the Events Calendar now appears in every subcategory of a parent category, not just the parent. awesomerobot confirmed this was an intended change with no current disable setting, and provided a CSS workaround to hide the calendar from subcategories. Tonja noted several internal teams were affected. Read more

  • Falco identified that rlauriston’s Gemini 2.0 Flash Lite model was deprecated by Google and pointed to the current 3.5 Flash Lite model as the migration target. Read more

  • awesomerobot diagnosed that rlauriston’s Ad Plugin Settings page was blank because a browser ad-blocker was matching the “ad” class on the settings container. Disabling the ad-blocker resolved it. Read more

  • putty discovered a conflict between reCAPTCHA and the user-creation API: POST /users.json with an admin key is rejected with a captcha verification failure, and POST /admin/users returns 404. This blocks n8n workflows that programmatically create accounts. Read more  ·  Spam thread

  • szhorvat asked whether Discourse auto-generates usernames matching a pattern seen in spam accounts. putty and NateDhaliwal confirmed they are spam, referencing the broader new-users thread, and pointed to the Enable random usernames site setting as the only built-in generator. Read more

  • rlauriston asked how to auto-flag spam posts containing a specific domain string. awesomerobot pointed to the Watched Words reference guide for automatic flagging, blocking, or silencing. Read more

  • BayResistance asked where Discourse’s non-self-hosted infrastructure lives for a security-conscious board member. supermathie directed them to the public subprocessors page. Read more

  • ADUG_Admin asked about reactivating a decommissioned free group. dax confirmed the site could not be restored and reminded the community that free sites are auto-decommissioned after inactivity, linking to the email-delivery troubleshooting guide. Read more

  • Mireille_Coilhac asked how to move a category between two Discourse forums. NateDhaliwal pointed to the topic-migration plugin guide with the category-export option. Read more

  • Giantkin_1 expressed frustration at frequent image-update requirements for self-hosted Discourse. NateDhaliwal suggested switching to the ESR (Extended Support Release) channel for slower, security-only updates. Read more  ·  ESR guide

  • pHneutre found that the documentation for muted vs. “suppressed from latest” categories appears inaccurate: replies and @mentions in a muted category still generate notifications. RGJ clarified the distinction and suggested a wording fix. Read more

  • Tony001 wanted to underline all topic headings but discovered the legacy $20/month starter plan lacks CSS-edit access. satonotdead confirmed and recommended self-hosting or upgrading. Read more

#Theme component / #Theme

  • satonotdead released Horizon AI Gists, a theme component that renders discourse-ai topic gists under Horizon’s high-context topic-card titles, since the theme lacks the standard plugin outlets. merefield pushed back, calling the need for a bespoke component targeting a single theme a symptom of a “fundamental design flaw in Horizon.” satonotdead responded thoughtfully, acknowledging the trade-off while celebrating Discourse’s open-source customization ethos. Read more  ·  merefield’s critique  ·  satonotdead’s reply

  • satonotdead also shipped Horizon Topic Thumbnails, solving a long-standing gap where topic thumbnails didn’t render in Horizon’s grid/minimal-grid/masonry modes. He linked the new component from both the Topic List Thumbnails thread and the Horizon feature-request thread, and directed users asking about thumbnails in the High Context Cards announcement. Read more

  • keegan iterated on the Conversation Map mini-map component after pmusaraj’s feedback: assign/voted mini-markers are now clickable, and a rendering issue causing multiple stacked mini-maps was addressed. Read more

  • putty and nathank continued building the Events Calendar on Custom Lists component, integrating the new event: filter query and resolving a Horizon integration question about whether the New Event button should live in the sidebar or above the calendar. nathank called the result “:rocket: AMAZING!!! :rocket:” but noted the /filter route still can’t surface events in Messages—a gap tracked in the separate feature request. Read more  ·  Validation

  • satonotdead shared a fork of F NAV with several enhancements for mobile, including F NAV on /chat (hiding the chat footer), restored sidebar buttons, and keyboard-aware height adjustments. He invited Don to pull the changes back upstream. Read more

  • Justin_Grimm2 flagged an oddity in Right Sidebar Blocks: recent replies containing only an image display the raw file name instead of a photo icon. Read more

  • jorgev asked whether the Reddit-ish theme is still a work in progress; satonotdead confirmed it’s production-ready and customizable from the repo. Read more

  • pacharanero documented a CLI tool (dsc) for managing custom user fields in bulk—including populating multiselect dropdowns with hundreds of options from a YAML file, avoiding the tedious one-by-one admin UI workflow. Bas also suggested using dsc to sort user-field dropdown items locally before pushing back. Read more  ·  Sorting tip

#Community Building

  • putty proposed a dedicated workflows category (analogous to Theme component or Plugin) instead of cramming all workflow examples into a single megatopic, arguing that tags and individual topics would better support discussion and Q&A. He also floated a one-click workflow sanitizer to null out credentials and site-specific data before sharing. Read more

  • hhf.technology shared a blocked-email-domains sync workflow that rebuilds the ~10,000-domain disposable-email list weekly from upstream, sanitizes carriage returns, preserves major providers, and only writes when content changes—eliminating the browser-freeze problem Bas described from pasting the raw list into the admin UI. Read more  ·  @Bas’s reaction

  • Thomas_Rother issued a reminder about a potential face-to-face meeting of Discourse operators at Chaos Computer Club Congress 40C3 in Hamburg, offering to organize an event outside the main venue so a 40C3 ticket isn’t required. Read more

  • fzngagan confirmed a fix for API-created topics allowing arbitrary archetype values, which caused user_stats to undercount posts. Read more

  • sam reviewed and approved two community-contributed bug fixes: showing userGroup flair in autoGroupFlairForUser, and stopping time tracking for deleted topics/posts. Read more

#Self-hosting

  • shoulders asked about installing Discourse on TrueNAS via docker-compose, noting the official installer only supports Docker (not compose). Andrew_Rowe directed them to the #unsupported-install tag and a community docker-compose effort, while cautioning about the undocumented path. Read more  ·  Tag reference

  • ivo1467 got stuck installing Discourse on a Debian VM via virt-manager because the installer demands a domain name. NateDhaliwal suggested using the dev install method instead of a production build. Read more

  • Mark_Wass updated the LetsEncrypt DNS-validation template for Cloudflare, warning that the original template in the top post is now out of date and can trigger duplicate-certificate rate limits. The new approach keeps the stock LE template and uses acmesh with a Cloudflare API token. Read more

events

  • The Discourse community hangout thread (covered above under #Announcements) also featured Vsekraski sharing a detailed wishlist for their decorative-plaster specialist community, including personal master pages, simple mobile publishing, and event announcements. mcwumbly encouraged the community-sharing behavior. Read more  ·  mcwumbly’s response

#Site Management

  • A new how-to guide for configuring a decision model in Discourse AI was posted, covering Yes/No, Choice, and Score question types, the D3 hosted example, and step-by-step admin setup. Read more

#Site feedback / meta-redesign-2026

  • Bas posted a follow-up on Meta’s new sidebar redesign, moving from initial “give it a week” skepticism to “leaning more and more towards ‘I like it’.” Read more

blog / mcp

  • singpolyma asked whether the Discourse MCP server has plans to add tools for reading Discourse boards (as opposed to just topics). Read more

Marketplace

#Migration

#Extras

  • Eilgnaw shared screenshots of the updated Dexo native iOS client for Discourse, now supporting iPhone Duo (Dynamic Island layout). Read more

Activity by the @team Group

Here’s a summary of notable contributions from the Discourse Team over the past seven days:


This summary was compiled from forum activity between November 1 and November 8, 2026. For additional topics discussed this week that weren’t covered above, browse the latest and top feeds.

Thanks for reading, and I’ll see you again next week! :slight_smile:

This week on meta.discourse.org…

November 8 – November 15, 2026


Key Stats

Over the past seven days, meta.discourse.org saw 295 new posts across 43 new topics, reflecting a busy week for the community and the Discourse team alike.

Top Users by Activity

User Posts Likes
awesomerobot 14 52
lindsey 5 23
putty 9 17
sam 5 17
merefield 6 16
RGJ 5 15
satonotdead 22 15
david 8 15
Michelle_L 5 12
Falco 5 10

Top Discourse Team Members

Team Member Posts Likes
awesomerobot 14 52
lindsey 5 23
sam 5 17
david 8 15
Falco 5 10
mcwumbly 4 8
chapoi 8 8
tgxworld 2 6
martin 2 5
manuel 1 4

Interesting Topics

ux

  • awesomerobot led a major overhaul of the review queue’s Yes/No button semantics, responding to long-standing community frustration that the same buttons meant opposite things depending on whether you were reviewing a spam flag or a pending approval. After collecting feedback across multiple threads, awesomerobot proposed that every question in the queue should now ask “Is there something wrong with this?” so that “Yes” always means “yes, there’s a problem.” A PR was merged and shipped as the upcoming change Consistent review queue answers, announced in this official post.

  • The re-framing immediately sparked debate in What happened to Approvals?, where Steve_Walmsley reported that the new user approval flow made him have to click “No” to accept someone — counter-intuitive for admins who process dozens of new users daily. awesomerobot acknowledged the friction and floated alternatives like approve/deny or Keep/Remove wording, with RGJ suggesting Keep User / Remove User and Laurent proposing a unified “Keep this post/user? → yes/no” framing. The discussion remains open for feedback.

  • tobiaseigen reported a persistent error message bug where the “Incorrect username, email or password” warning stays on-screen when switching from password login to email-link login. awesomerobot confirmed the issue and posted a fix PR that is on the way.

  • tobiaseigen also noted that when categories are set as the home page, the sidebar jumps down and auto-highlights “All Categories,” obscuring crucial links at the top of the navigation. No team response yet — see the report for replication steps.

product Support

#Community Building

#Announcements

#Plugin / official

#Theme / #Theme Component

#Self-hosting

bug

#Data & Reporting

development

events / #Community Events


Activity by the @team Group

awesomerobot

awesomerobot was the week’s most active team member with 14 posts and 52 likes, almost entirely focused on the review queue UX overhaul. After merging PR #45915, they announced the Consistent review queue answers upcoming change, then fielded community pushback in the approvals thread, carefully explaining the design rationale while remaining open to further iteration — including the possibility of abandoning Yes/No entirely for approvals. They also fixed the login error message persistence bug, shipped topic timeline style regression fixes, addressed event reminder field reversion, responded to DSA moderation feedback, investigated white background issues on Horizon, and flagged the Discourse ID invite-only gap as a known issue on the Free plan.

lindsey

lindsey published three official announcements: the Zendesk group permissions update, the temporary chat muting feature, and anonymous livestream viewing for Discourse Events. They also released the comprehensive Salesforce integration configuration guide for Enterprise admins, and updated the Zendesk plugin topic documentation.

sam

sam announced the revamped AI features admin page, acknowledging positive early community reception. They confirmed the AI summary link bug will be fixed, responded to the Android HTML paste issue as likely an Android-specific bug, and addressed MCP-related community interest. They also weighed in on the Patron badge seeding confusion, explaining the name-vs-ID approach and noting a candidate fix is pending.

david

david diagnosed the libvips/Synology kernel incompatibility, providing detailed security context about sandboxing and image processing as an exploit vector. They published the November 10th intermediate releases and resolved the changelog site outage within hours. They also confirmed the backup gzip change is working and asked about cmdntd’s upgrade memory failure.

chapoi

chapoi diagnosed the Chat Sidebar / grid layout conflict, explaining the precise DOM mechanism and pointing to the upcoming change documentation. They investigated topic creation failures after update, explained the wiki-post bump side-effect, helped debug the Horizon white background issue, solved the homepage feature visibility problem, and was actively investigating the categories not showing in the composer bug. They also engaged with the default editor feature request.

mcwumbly

mcwumbly suggested that the Boards sidebar link be shown conditionally rather than hidden entirely, and confirmed interest in AI-focused community hangout topics. They also endorsed using Workflows for account expiration instead of custom plugins, and weighed in on the review queue button redesign with a mental-model perspective.

Falco

Falco addressed Live room configuration questions about hiding chat globally while keeping in-room text, and shared that automatic screen-share spotlighting is now available. They helped troubleshoot @cmdntd’s upgrade issue by asking for the full app.yml, and confirmed the Ask AI post-age settings for limiting response context.

tgxworld

tgxworld confirmed the libvips backport fix and responded to DSA moderation feedback with clarity on the Statement-of-Reasons gaps and the purpose of the “Explanation” field in the transparency database submission.

martin

martin acknowledged that the Boards sidebar visibility issue was also raised internally by lindsey, and merged a PR to address putty’s request for a conditional link.

manuel

manuel acknowledged the Colored Tag Styles translation bug and committed to investigating a fix for the data-tag-name locale dependency.


Thanks for reading, and I’ll see you again next week! :slight_smile: