일일 요약 (UTC 오전 5시)

[system]

Today on meta.discourse.org…

It was another busy 24 hours on Meta, with a brand-new Voice feature generating excitement, a rapid-fire Horizon bug fix, and plenty of thoughtful discussion about permissions, AI search, and username policies. Here’s a recap of everything you might have missed.

Key Stats

• 95 new posts and 38 new topics were created in the last 24 hours.
• Those posts received 135 likes in total.
• The most active users, ranked by likes, were:

User	Posts	Likes
Martin	7	12
Zogstrip	3	11
Nat	5	10
Moin	8	9
Angus	2	9
Damian_Boon	2	9
Falco	2	8
NateDhaliwal	7	7
SkyeDragon	3	7
Small-Lovely-Cat	1	7

Interesting Topics

#Announcements

• Angus shared his love for the new Discourse Voice rooms, suggesting “live” as a better name than “voice” because it works as an adverb or verb in everyday English. SkyeDragon then asked whether viewers can adjust each speaker’s volume independently, and Falco confirmed you can right-click any participant to tweak their audio. SkyeDragon later posted detailed feedback after trying the feature, including a useful Linux workaround for screenshare audio, an appreciation for the IP privacy popup, and a note that the room list can be hard to find on mobile — read more.

• The discussion around Ask AI search continued as Moin reported that the new search interface on his tablet no longer lets him press Enter to perform a classic search, and noticed that selecting “in this topic” is lost when you refine your query. Nat acknowledged the UX regression and said he would look into it, while Sam shared an AI-generated state diagram produced with his Jarvis tool to help map out the feature’s intended behavior — read more.

• The granular group-based permissions proposal sparked a robust debate about removing the everyone group. Martin defended the change, explaining that everyone didn’t consistently mean “public access” across the platform, and that the new explicit anonymous_users and logged_in_users groups are clearer. Merefield pushed back, suggesting a “Public” shortcut in the UI to make selecting both groups easier; Martin replied that a UI shortcut is possible while keeping the underlying permissions explicit. A related conversation about excluding groups from categories also resurfaced.

• Martin announced new filter and sort options for chat channels, letting users choose between “All channels,” “Active only,” “Unreads,” and “Mentions,” and sort alphabetically, by recent activity, or by priority. NateDhaliwal briefly hit a missing-migration error, but resolved it by running migrations — read more. This is a welcome addition for anyone juggling many channels, and builds on the earlier feature request to group chat channels into categories.

bug

• A scary admin warning appeared on several sites: “Your site may not work because a theme / component has errors”, traced back to the Horizon theme. Zogstrip quickly acknowledged the problem, and David confirmed it was resolved shortly afterward. Phew!

• Small-Lovely-Cat wrote a thorough analysis of a ruby-i18n regression introduced by an upstream update, where display languages could accidentally fall back to the site default due to how Fiber-local configuration was being copied. They proposed rolling back the version until the upstream fix lands, and Nat said they were investigating it.

• WaitroseCarpark shared a deep-dive bug report on Patreon v2 sync reporting “0 users synced”, tracing the problem to the plugin reading member emails from the wrong resource in the API response. They included a working patch, which might point the way to an official fix.

• BOUCUR confirmed that post and topic links under badges are now appearing again after a recent regression.

• Zogstrip thanked RGJ for reporting a chunked backup uploader rate-limit issue, and linked to a pull request fixing the problem.

Support

• Richie was wondering why a bunch of new Voice badges had appeared on a site that doesn’t even have chat or voice enabled. NateDhaliwal showed that you can simply remove the Voice group from Group settings to hide them all, and Zogstrip flagged the default-enabled behavior to Falco as something they should probably fix — read more.

• Happyhappy asked whether LibreTranslate can be used without AI in Discourse, since the older Translator plugin is now end-of-life. NateDhaliwal explained the two translation options and pointed to the Discourse Translator plugin topic for LibreTranslate support, while Satonotdead noted that self-hosting open models can still respect user privacy — read more.

#Community Building

• Damian_Boon kicked off an ambitious project to turn Discourse into a Reddit/X-style scrolling feed, designed to serve the “silent 90%” of lurkers with continuous discovery, embedded topic previews, and personalized feeds. They documented their stack, which builds on the Redditish theme and the Topic Preview Modal, and promised to keep the thread updated with lessons learned.

General

• A practical question from Jenmck about allowing users to change usernames indefinitely drew several community policies. Ondrej mentioned a two-year cooldown used on another forum (tracked via user notes), while Satonotdead suggested six months as a reasonable middle ground. Moin pitched a workflow that alerts staff when a username change happens too frequently — read more.

ux

• Moin reported that quoting posts on a Galaxy Tab with Firefox requires two taps, even though first tap highlights the text. Jenmck reproduced it on her Samsung Galaxy s26 Ultra, and Merefield asked if it was related to an earlier unresponsive popup menu on Android issue. Moin clarified that this is a distinct bug, since text selection works fine — read more.

#Plugin

• The new Discourse Boards plugin is already a hit. Andrew_Rowe called it “amazing” and asked the community how they surface board access to users. Martin showed the current global sidebar link and floated a few ideas, including a dedicated “Boards” sidebar block or an “Add to my sidebar” option in the board menu. For another board-like visual, the Kanban Board theme component also got a mention.

• Jenmck reported several problems with the Custom Wizard admin panel after upgrading, including disappearing conditions and a form that would blank out on save. Angus stepped in and merged a fix for the admin panel, asking her to test it — read more.

#Developer Guides

• A new guide on bundle splitting for plugins was published, explaining how plugins can opt into the staticModules system to lazy-load routes, components, and libraries for faster boot times. The guide includes helpful examples for grouping routes and dynamically importing modals using DAsyncContent — a must-read for plugin developers.

Activity by the Team Group

• Zogstrip responded to the Horizon theme error report, and David confirmed the fix was deployed. Zogstrip also flagged the Voice badge default behavior for Falco, and thanked the reporter of the backup uploader rate-limit bug with a linked PR.

• Nat was busy on the I18n regression caused by the ruby-i18n update, and spent time refining the Ask AI search experience, acknowledging Moin's feedback about lost search scoping and promising to address it.

• Martin announced the new chat channel filter and sort options, discussed Discourse Boards sidebar discoverability, and wrote a detailed defense of the removal of the everyone group. He also spotted an edge case with AI Agent group settings in the transition and prepared a quick fix PR.

• Angus shared his enthusiastic feedback on the new Voice rooms, and later merged a Custom Wizard admin panel fix to help Jenmck.

• Falco explained the per-participant volume controls in Voice and received the heads-up from Zogstrip about not enabling Voice badges by default.

• Pmusaraj offered debugging help on the ActivityPub plugin build failure, asking for a full backtrace and the exact core/plugin commit hashes.

• Sam surprised everyone by generating an Ask AI state diagram with his Jarvis tool, giving the community an AI-generated overview of the search feature’s states and prompts.

From new voice rooms to smarter chat filters, the Meta community spent the day getting louder, sharper, and more organized—one topic at a time!