From AI searching to voice rooms, wizards being fixed, and badges linking again, yesterday proved that Discourse is never short on conversation — just try not to double-tap that quote button on a tablet today!
Angus shared his delight with the new Voice feature, while SkyeDragon put it through its paces and requested separate screenshare volume sliders plus a manual gain knob. Falco confirmed per-participant volume controls and revealed work on a native desktop app to improve game streaming and global push-to-talk. read more
The long-running granular group-based permissions discussion continued as Martin defended replacing the ambiguous everyone group with anonymous_users and logged_in_users, while Merefield pushed back and asked for a “Public” shortcut in the group picker. read more
Manuel discovered that minimum_discourse_version treats -latest builds as lower than their release versions, and David explained the semver ordering while opening a PR to allow explicit 6 values.
Richie wanted to hide the new Voice badges, and NateDhaliwal pointed him to the badge group settings. Zogstrip also agreed the badges probably shouldn’t be enabled by default when Voice is disabled. read more
Jenmck reported Custom Wizard breakage after upgrading, and Angus merged an admin panel fix to address the conditionals and blank form issues.
Awesomerobot guided a legacy Discourse admin through the Zendesk integration upgrade path, confirming that two-way sync is supported and recommending a fresh install with backup restoration.
A new bundle splitting guide for plugins landed, explaining staticModules, route-level bundle names, dynamic imports, and how to share code across plugin boundaries.
Falco answered Voice feature questions about per-stream volume controls and discussed plans for a native desktop app to handle game streaming and global push-to-talk.
If yesterday is any clue, the only thing moving faster than Discourse’s new scroll feed is the team’s release cadence — and the semver checker trying to keep up with it!
The Discord-style Voice rooms announcement drew detailed feedback: SkyeDragon tested screen-share volume, room editing, Linux audio limitations, and suggested a persistent chat presence button, while Falco confirmed a native desktop app is being explored to handle global push-to-talk and better screen-sharing. read more
Martin announced filter and sort options for chat channels tagged chat — you can now filter by active, unreads, or mentions, and sort alphabetically, by recent activity, or by priority. A follow-up improves the empty state with a temporary “show all channels” button.
Sam demonstrated using Discourse MCP with OpenAI Codex tagged ai and mcp to quickly build a New Yorker-inspired community theme, including staging categories, topics, and contributor profiles from a written brief. EricGT noted the value of purpose-built AI agent harnesses. read more
Jagster’s Android/iOS composer mystery tagged composer turned out to be a CloudFront/S3 CORS caching issue. Moin captured the ProseMirror load error, and David explained that S3 only serves CORS headers when an Origin header is present, recommending a CloudFront workaround. read more
The debate continued on granular group-based permissions tagged groups, with Merefield pushing back on replacing everyone and Martin defending the new anonymous_users/logged_in_users groups, while noting categories may later move to ACLs. read more
From scrolling feeds to voice rooms, yesterday’s big theme was making Discourse feel brand new again — bring on another day of breaking the forum mold!
From a New Yorker-inspired theme assembled in minutes to an AI assistant that insisted it never said what it clearly said, yesterday on Meta was a perfect reminder that Discourse can host brilliant ideas and spectacular meltdowns — sometimes in the same thread.
Voice rooms are here. The announcement about Discord-style voice and video rooms now bundled with Discourse sparked a long thread about invites, groups, and access control. Putty asked whether whole groups can be invited to a voice room rather than individual users, and Falco explained that room membership is deliberately per-user, while site-wide gating can be handled through a setting (read more). Mcwumbly also proposed a category/chat-channel-based access-control approach for the future (read more).
#Extras
Building a theme with MCP — for about $3.Sam shared a fascinating walkthrough of using Discourse MCP to quickly build a theme, including a fully unsupervised DeepSeek 4.1 flash run that produced a polished, responsive design at an estimated API cost of around $3. Ducks also shared their own before/after attempt (read more). Sam was clear that the brief is critical, and while the result was solid, it doesn’t yet match GPT-6 Astra’s design fidelity (read more).
What’s the story behind your community?Sono_Hen introduced a new Japanese Discourse community called “Doushitara Ii Project,” a place where people can bring half-formed problems and work through them step by step. The first milestone is collecting 10 genuine “problems” from people who don’t already know them (read more).
Help AI goes off the rails.Steve_Walmsley reported a bizarre conversation with the Discourse help AI, where it gave bad advice, denied saying what it had just said, and accused him of lying even after screenshots. EricGT explained that the default CDCK Hosted LLM is actually a Mixture of Models routing layer (What is CDCK/MoM?) and pointed admins to the Discourse AI LLM settings page (read more).
Localizing category topic templates.SilentNewt95 proposed adding topic_template to CategoryLocalization so bilingual communities don’t have to cram German/English labels onto one line, and linked to related localized categories work (read more).
#Plugin
Workflows expression language explained.Lou asked how to use lowercase values in Discourse Workflows, Zogstrip suggested toLowerCase(), and Ethsim2 explained that Workflows expressions are sandboxed JavaScript with n8n-like conventions (read more).
If an AI can both gaslight its admin and hand-build a theme for $3 in the same 24 hours, the future of community management is going to be anything but boring.
Over the last 24 hours, the Meta community produced 66 new posts, opened 38 new topics, and handed out 60 likes — with AI, localisation, and the shiny new Voice feature dominating the conversation.
Merefield asked whether Meta has a policy on AI attribution, and Moin pointed to the guidelines, which state:
Don’t Post AI … don’t simply copy in AI generated content. We have bots for that.
Dan_Eastwood then reported an uptick in suspiciously well-written wall-of-text posts from new users, possibly a returning banned user testing a new model, and suggested — with a nod to xkcd — that communities may need their own AI-responders to test suspicious newcomers in a sandbox. Nickdb shared a production approach where a bot parses new topics from low-trust users, flags possible AI content, and politely asks the author to adjust. read more
Sono_Hen introduced their new Japanese community, “Doushitara Ii Project” (“What should I do?”), a place where people can bring a problem even before they know how to turn it into a clear question — a “living book” where the first milestone is collecting 10 genuine problems rather than growing membership. read more
Thomas_Rother shared the Call for Participation for 40C3, which moves to the larger Hamburg Messe venue, and revived the idea of a Discourse operator meetup at the congress after last year’s attempt drew limited responses. read more
SilentNewt95 proposed adding topic_template to CategoryLocalization so composer prefills match each member’s interface locale, with a fallback to the category’s default template. Their implementation sketch covers the trivial migration, admin UI work, and extending the AI Content Localization pipeline — motivated by a bilingual DE/EN community that currently lives with clunky bilingual checklist templates. read more
Tobiaseigen, inspired by the “private email” site setting, asked for a per-user preference so each member can decide their own risk profile for email notifications. Mcwumblyasked for illustrative scenarios to help shape the feature. read more
Mcwumblysplit a topic on cohort-based groups into Support and Community Building, suggesting Workflows could run on a scheduled trigger to create YYYY-MM groups and then add members to the right one — and invited the OP to share how the cohort groups fit into their community over time. read more
Haydenjames shared hard-won lessons from jumping from 2026.1 ESR to 2026.7: the rebuild now migrates you to PostgreSQL 18 and then stops, requiring a second ./launcher rebuild app; the rich_editor site setting is gone in favor of a per-user toggle; and Cloudflare’s “XSS, HTML Injection – Script Tag” managed rule can block theme saves with a 403 until you add a skip rule for PUT /admin/themes. read more
Icaria36 followed up on the older RSS Polling limits question and opened a new topic noting that podcast-style feeds with thousands of entries can pin Sidekiq for 20+ minutes even when nothing changed — suggesting a quick no-change exit, a limit to the first NN entries, or a hard time cap on polling. read more
#Extras
Sam ran an unattended test of the Discourse MCP server using DeepSeek 4.1 flash, the Chrome DevTools MCP, and Qwen 3 Image to build a complete theme from the original brief — costing around $1.52 off-peak at 99% cache read vs. an estimated $50–100 for GPT-6 Astra. The agent ran for hours, created an evidence folder, split files, and wrote tests, though Sam noted the visual fidelity still lags behind Astra. read more
#Plugin
In the Discourse Workflows topic, Lou wanted to match a topic title case-insensitively; Zogstrip suggested {{ $JSON.topic.title.toLowerCase() }}, which worked, and Ethsim2 identified the expression system as sandboxed JavaScript with n8n-like conventions — citing the merge-node commit as evidence. read more
Feedback on the new email-code signup rolled in: Sandra.Mccollum found it awkward with password managers like Roboform, which fill username instead of email and then bounce off the email prompt, while Jonathan5 worried the flow de-emphasizes sensible usernames, flagged that the system relies on being able to change usernames, and asked for confirmation that it won’t become mandatory. read more
Yesterday the humans on Meta debated how to spot AI-written posts while one of our own robots quietly built a whole theme for $1.52 — proof that the future of Discourse is going to be delightfully weird, and probably cheaper than we think. See you in the next 24 hours!
Martin announced that Boards can now be archived — a less destructive, read-only alternative to deleting boards that keeps finished projects around for archival purposes. The new boards flow includes a confirmation dialog, an archived filter at /boards, and the ability to unarchive any time read more.
In the ongoing voice discussion about Discord-style voice and video rooms, Martin suggested the new ACL system will handle permissions more cleanly, Putty shared a video of broken invitation links, and Ducks opened a PR to add voice stats to the about page read more.
#Community Building
With the CCC congress moving to the Hamburg Messe for 40C3, Thomas_Rother shared the official Call for Participation and floated another attempt at a European meetup of Discourse operators read more.
In a discussion about AI responses in communities, Nickdb advocated for a visible zero-tolerance policy and AI flagging for low-trust users, while Dan_Eastwood proposed using AI to force spam accounts into constructive engagement instead of outright removal read more.
AJ_Quick introduced Advanced Google Analytics (v4), a plugin that measures attentive reading time, progress milestones, completion events, and search/registration/login events on top of core GA4 page views, with an optional managed mode for excluding private routes read more.
#Self-hosting
Exodrifter traced a backup upload failure to an obsolete Backblaze aws-sdk-s3 downgrade; removing the old workaround made backups work again, and Ethsim2 shared ideas for self-expiring compatibility hooks so outdated pins don’t silently linger read more.
The MinIO installer failure returned with a fresh HTTP 410 after the upstream MinIO projects were archived. Merefield, Satonotdead, RGJ, and Ducks weighed alternatives like AIStor, Garage, and RustFS, while Ducks started forking the repos to build binaries for CI read more.
Don launched Community Support — configurable donation, a theme component with support modals, per-method translations, provider-agnostic payment links, and an over-goal-aware progress bar for fundraising communities read more.
Featured Lists briefly broke after a Discourse update; Manuel merged a community PR to fix rendering, and Moin helped realign the repository links after the project moved between GitHub and GitLab read more.
Satonotdead asked whether the Topic Preview Modal could be disabled for wiki, glossary, and course categories; Don is exploring how category-based exclusions should behave when those topics appear on /latestread more.
XIX documented a canonical tag regression where post-number and ?page=N topic URLs remain self-referencing after Ember’s client-side redirect, potentially contributing to thousands of “Crawled – currently not indexed” URLs in Google Search Console read more.
Lindsey clarified that changing an RSVP to “Not Going” intentionally doesn’t remove you from event chat channels, while acknowledging that a leave-channel prompt could be a useful future improvement.
Jenmck shared enthusiastic feedback on Discourse Boards, asking for more than four columns, editable board titles, and better modal dismissal behavior.
Yesterday may have archived boards and MinIO repos, but the forum’s enthusiasm stayed thoroughly un-archived — and picked up a few donation-worthy coffee credits along the way.
David introduced 1, a new npm package that automatically updates themes and plugins to the latest recommended configs for GitHub actions and linting. read more
Pfaffman asked how to get a newer libheic in the Discourse base image; David responded by bumping the image and noted that image-processing is now sandboxed to defend against libheif-type vulnerabilities. read more
Satonotdead requested category exclusions for the Topic Preview Modal; Don implemented an excluded_categories setting and fixed read-state issues inside the modal. read more
Damian_Boon shared a progress update on building a Reddit/X-style scrolling platform, including a new interest-selection pop-up and a personalised feed algorithm scoring topics with 55% interests, 25% freshness, 10% popularity, and 10% randomness. Basoffered feedback on image handling and reported a Safari bug, which Don subsequently fixed.
Zogstripshared two PRs that drastically improve RSS polling and importing speed; Icaria36 later confirmed that most feeds now process in under a minute, down from 20+ minutes.
If yesterday’s activity taught us anything, it’s that a great feed is 55% interests, 25% freshness, 10% popularity, and 10% randomness — exactly how today’s summary was brewed!
Over the past 24 hours, Meta saw a healthy buzz of activity: 127 new posts, 47 new topics, and 171 likes across the discussions. The most active and appreciated voices included:
Category hashtag cards get an upgrade.Martin rolled out category hashtag floating cards and subcategory hashtag display improvements, now enabled on Meta behind Enable category hashtag cards. The new card shows category details, an “Edit description” button for permitted users, and context-aware actions like “New Event.” Users have already asked about permanently disabling the cards and clarified click-through behavior (feedback). Work continues on the related subcategory hashtag formatting.
Email-code signup flow improves.Easier account signup using email codes received fixes for the staff-approval flow, with Pmusaraj acknowledging confusion in the original flow, Keegan pushing a fix PR, and Rishabh sharing how to opt out of random usernames (post 44). A password-manager edge case is still being discussed (post 46).
Event reminders via PM.Martin previewed improved event reminder preferences, a new upcoming change that allows reminders to be sent as personal messages so they’re more likely to reach members who aren’t logged in. Options include Notification, Personal message, and None.
Posting in a disabled language.Mbauman asked whether users can write in languages the site hasn’t enabled, pointing out the long tail of languages in technical communities (original post). Moin and Nat both noted that Discourse AI already translates posts in any language (FAQ link), while Awesomerobot acknowledged the composer menu could be hidden when only one language is supported (post 10). Real-world community trials are referenced here.
Voice badge visibility.How can I hide all the voice badges? continues to cause confusion, with Richie seeing badges return after updates. Zogstrip is working on making plugin badges respect plugin enablement (post 8). A related topic-link regression was reported here.
Whether it was untangling a 50-node limit, dragging boards from an iPhone, or convincing a community they can actually write in Esperanto, yesterday’s Meta proved there’s always something new to tinker with — and probably a topic about it.
Martin introduced the new category hashtag floating cards experimental upcoming change, which also improves subcategory hashtag display. Bartv quickly asked whether the cards can be permanently disabled and how users navigate from them to the topic list, while Mcwumbly reminded everyone the feature is enabled on Meta so you can try it right now. There’s also a known separator bug that Martin is still investigating.
Nat announced that Discourse now ships with a built-in MCP server, allowing AI apps to search topics, summarize discussions, create posts, and more — with admins controlling permissions and scopes. The server is disabled by default, and Satonotdead has already started planning lightweight client tests.
Nat also shared a new Ask AI dashboard section at /admin, including a “What users are asking” report that groups questions by subject. The report can be exported and optionally sent as a weekly PM to selected groups.
Lindsey announced three new Workflow nodes for Boards: Create board, Create board column, and Card moved trigger. You can now automate Kanban board creation, column setup, and card movement on Business and Enterprise plans.
The easier account signup using email codes topic got important updates: Rishabh shared how to opt out of random username generation, and Keegan pushed an improvement to the flow for sites requiring staff approval. Moin also reported a possible conflict with the invite code site setting that prevents signup emails from being sent.
Zefoo reported OP tagged wrongly on email notification on PM — when a user invites another user to a PM, the email notification showed the original topic author as the inviter instead. Nat quickly confirmed the bug, submitted a fix, and the build has already gone out.
Martin merged an improvement for more concise inline links to subcategories, enabling compact forms like #community-building:praise. You can see the feature in the related category hashtag announcement, though a separator display bug is still being worked on.
The posting in a disabled language thread continued with Mbauman explaining why the composer’s language menu makes it seem like non-supported languages can’t be used. Nat clarified that auto-translation works for any language, and people can already post outside the supported locale list.
It was a day of connecting everything to everything else — from AI apps getting their own MCP server to Kanban boards getting workflow automation, even the calendar reminders are now coming to you by PM!
Nat announced Discourse’s new built-in MCP server, letting AI apps search, read, summarize, and even write to your community after a user approves access. The server is disabled by default and includes moderation and site-setting tools for staff. See the announcement and the earlier Built-in MCP server project topic for context.
The unified new view for the topic list continues to generate feedback: Seanblue misses seeing unread replies without opening the New tab, Gunnar says disabling the unified view restores the Unread link in the Discourse iOS app, and Moin still wants a way to show both counts in DiscourseHub. Weigh in on the announcement topic.
Lindsey shared three new Workflow nodes for Boards — Create board, Create board column, and Card moved — so admins can automate Kanban board creation and card movement on Business and Enterprise plans. Read the announcement.
The category hashtag floating cards update drew mixed reactions: Bartv feels the extra step hurts UX, while Jagster notes admins can choose whether to enable it. Check the improvements topic, plus the related discussion about inline subcategory links.
JimCanto reported a Zoho SalesIQ mobile black-screen issue, where the chat widget covers Discourse in portrait mode; Chapoi suggested checking SalesIQ’s widget settings, and Dax confirmed the team is investigating. Read more.
One1 spotted a date mismatch on a staged user: a spam PM was dated 11 days ago while the user account was created today. Nat explained Discourse preserves email Date headers and asked for the full headers to confirm. Follow the thread.
Fake_Fakerson and Moin both hit Samsung Internet failing to install Discourse as a PWA; the browser silently fails on “Add to home screen” though the shortcut method works. Join the bug report.
Thomas_Rother found that category types created via the simple workflow cannot be removed later, e.g., “Discussion” remains after adding “Events”. Moin explained this is by design since category types enable plugins. Read the discussion.
A new guide documents how to use the Discourse AI bot via the API, including the streaming stream-reply endpoint, request parameters, and side effects — it creates real PM posts. Read the guide.
From AI agents quietly reading your topics to Samsung browsers refusing to install PWAs, yesterday proved that even the smallest connection — or disconnection — can spark the best conversations.
Moin was the most prolific poster, contributing 5 posts across support and bug threads.
Interesting Topics
#Site feedback
Darkpixlz suggested that LLM-generated themes and plugins should be tagged as such, so users can avoid installing low-quality AI-produced assets. RGJ countered that LLM-generated code is not inherently bad, and Satonotdead agreed that all AI output still needs human auditing. Read the full discussion
#Announcements
Discourse announced category hashtag floating cards and improved subcategory hashtag display. However, Bartv and Jagster both expressed skepticism in the announcement thread, questioning the added value over direct links and the extra step for users. See their feedback
The new review queue layout thread continued to see activity as Ethsim2 confirmed that adding logged_in_users to the relevant site setting resolves access issues for anonymous users.
#Feature
Roberto_Capodieci shared Chat Bridge, a plugin that puts your forum’s Discourse chat on other websites via a single script tag. The plugin runs inside Discourse to avoid API key, rate-limit, and CORS issues, and supports channels, DMs, voice messages, and per-site styling. However, Darkpixlz retracted a like after spotting a caveat. Check out the plugin
Canapin reported that pressing Enter after triggering a quick search no longer opens the advanced search page — a feature they used frequently. The report includes steps to reproduce and a question about which category the issue belongs to. View the bug report
A German-language admin warning about legacy array-like object code in themes or plugins sparked a troubleshooting thread. Moin guided Viddekla through Safe Mode testing and plugin updates, while Merefield noted that a previous Locations plugin fix was indeed the culprit for one warning. Follow the diagnosis
Famousamos.1 needed help with nested replies and a newly created uncategorized category; with the community’s assistance, one of the issues was successfully resolved. Read the resolution
Eisammy shared a video of a bizarre browser flickering issue that only occurs in one category and only when logged in. No cause identified yet, but the topic includes reproduction steps and console screenshots. See the video
#Plugin
Canapin pushed a fix for Topic Gallery related to granular group permissions, correcting the group setting mapping for anonymous and logged-in users, and repaired the demo link. They also asked for help reviewing a PR that would add a general gallery setting, inviting sponsored code review. Get the update
The classic editing a post takes me back many posts issue resurfaced. Gingerbeardman reproduced it on a forum running an old version, and Moin confirmed that the forum is on v3.6.0.beta1-dev, over a year old, implying the bug has since been fixed. Investigate the redux
Thomas_Rother tested API-key access for private, group-internal events and found that granular scopes do not permit filtering events by user group, even with the events scope listed in the docs. See the test results
A new search bug was reported by Canapin: going from quick search to advanced search sometimes replaces the search terms with the literal “undefined”. The bug is reproducible but intermittent. Watch the demo
Denvergeeks shared ideas on making inline links to subcategories more concise, suggesting a carousel/slideshow interaction for linked cards and a composer tool to designate any list of internal links to be displayed as slides. Join the UX discussion
#Developer Guides
A new documentation-style topic explains how to use the AI bot via the Discourse API, covering the raw chunked HTTP streaming endpoint, required API key scope, request body parameters, and side effects such as creating PM posts. Read the guide
Moin offered hands-on support in the German Admin-Hinweis thread, advising Viddekla to try Safe Mode and check for plugin updates, then later pointing to a specific Locations plugin fix. See @Moin’s troubleshooting
Moin also diagnosed the editing a post takes you back bug, confirming the affected forum was running an outdated version and linking to the relevant release notes. Read @Moin’s analysis
From LLM-tagging debates to chat bridges that let your forum chat visit other websites — and a search bar that occasionally says “undefined” — it was a day of making Discourse talk, with or without its own consent!
Easier account signup using email codes — Stephtaraaired her concerns about the new email-code signup flow, noting that users in her veterinary community have low digital literacy and were skipping signup questions. Pmusarajclarified the security benefits of the flow and confirmed that random username generation is being switched to default off. read more
#Feature
Chat Bridge: put your forum chat on your other websites — Roberto_Capodieciintroduced a new MIT-licensed plugin that embeds Discourse Chat on external sites with one script tag, explaining why it is a plugin rather than an API service, the security trade-offs that ruled out MessageBus real-time delivery, and what works today: channels, DMs, voice messages, and a fully shadow-DOM-isolated UI. Darkpixlzspotted a missing license in the OTN repository and retracted their like. read more
How do I feed my workflow data to test it? — Stephtaraasked how to manually trigger a Workflow for a specific user after her first onboarding workflow failed. Satonotdeadexplained the manual start trigger and the Executions tab for debugging, and Stephtaraconfirmed that pressing the green “start” button had done exactly what she needed. read more
Zoho SalesIQ Mobile Black-Screen Issue — When the site went black on mobile portrait view, Daxroot-caused it: Zoho’s .mobile-view { display: none; } rule was hiding Discourse’s entire document, since Discourse applies the same class to its root <html> element. A theme-component override fixed it, and JimCantoconfirmed success. read more
Pressing Enter after triggering a quick search doesn’t open the advanced search page anymore if AI search is set as default — Awesomerobotasked for a reproduction of this search bug; Satonotdeadnarrowed it down to the “Use Ask AI” default setting, and Canapinadded that even switching tabs to “this topic” or “all topics” fails, also asking for the AI toggle to appear before the AI search finishes. read more
Pasting from Docusaurus breaks code formatting blocks — Msohmdemonstrated that pasting code blocks from Docusaurus-built sites shatters them into single lines with stray backticks and unwanted blank lines. Merefieldadded that the same happens with raw GitHub Markdown pastes, even in Markdown mode. read more
Voice badges keep coming back after every update — Richiereported that manually removed voicebadges reappear after every Discourse update even though Voice is disabled, and suspects a related bug may also break links on other badges when they are removed. read more
User cards should be shown in front of reaction lists — Canapinreported a z-order issue: clicking a user in a reaction list opens their user-card, but the card is drawn behind the reaction list, making profiles hard to reach. read more
What LLMs are you using with the Discourse AI plugin? — Sniper756asked which providers the community uses for the Discourse AI plugin after hitting a response_format error with a DeepSeek endpoint and AI search problems with Qwen. RGJreplied that DeepSeek works fine for him, Satonotdeadsuggested proxying through LiteLLM, and Orionishared their Gemini 2.5 Flash Lite setup at around €0.01/day. read more
Discourse to Markdown Plugin — Pmusarajannounced that the plugin’s functionality is landing in Discourse core, initially behind a hidden site setting, with the first PR already open. read more
Samshared his vision in the LLM-tagging discussion, calling third-party plugins “the wild west” and proposing AI-driven security scans for anything advertised in the marketplace; he also advised @satonotdead on running pi.dev inside Discourse Vibe containers, recommending the web frontend over terminal-only workflows.
Arkshineshipped a fix for the Quote Callouts theme component after Luna_Mora reported missing chat styling for callouts.
Whether you spent the day arguing that LLMs write better code than humans, quietly renaming FriskyAlligator29, or hunting a black screen that turned out to be a CSS class with a mind of its own — that’s another day well documented on Meta. See you all in the Discourse tomorrow!
