Discourse Meta forum

satonotdead: I want to display some categories for everyone (anonymous) users but not specific automated groups. That would not make sense from a functional point of view, a user that belongs to that group could simply log out and see the category anyway. From a technical point of view it is impossible, if a category is accessible to everyone , Discourse sets the read_restricted flag to false and all access mechanisms are bypassed. From this plugins perspective, the closest you can get is NOT excluded_group (which is the same as trust_level_0 AND NOT excluded_group ). But an anonymous user cannot be in a group, so no.

Today on meta.discourse.org … Key Stats Over the past 24 hours, the community produced 43 new posts across 25 new topics , with 40 likes given. Here are the top contributors, ranked by likes received: User Likes Posts Falco 5 3 Sam 5 1 Zogstrip 4 2 Sono_Hen 4 1 Mcwumbly 3 5 NateDhaliwal 3 3 Merefield 3 2 Dan_Eastwood 3 1 Satonotdead 2 10 Ethsim2 2 1 AI was the day’s dominant theme, from building a complete theme with DeepSeek via the Discourse MCP for around $3 to a lively debate about handling AI-generated posts . On the infrastructure side, MinIO broke CI again with an HTTP 410 , and a first-hand 2026.1 ESR → 2026.7 upgrade report revealed a surprise two-stage PostgreSQL 18 rebuild. Elsewhere, Satonotdead noted that asking for a username after email validation and hiding the username on registration are now bundled into core, shared a custom theme component for A-Z sorting in the docs view , asked about custom 0 tag formats , scoping dynamic groups to anonymous users , and updated the Spanish trust level names thread . Meanwhile, tags localization issues got a follow-up, the Related vs Suggested Topics debate gained a comment from AJ_Quick , and Chaitanyji asked whether one post per month is enough to keep a free site active. Interesting Topics #Announcements Sandra.Mccollum reported that password managers are fumbling the new email-code signup flow ( login signup ): Roboform auto-fills stored credentials, then gets bounced to the one-time-code screen, where it inserts th

Thanks. I found I did not set primary lanuage of tags which should be compulsory not optional.

Well, that is the point. I want to hide specific categories to only one group.

Anonymous users as in logged out users? If they don’t have accounts, how can you add them? TL0 targets all users, if that’s what you’re looking for.

Thanks for building and sharing this. I wonder how to scope anonymous users? Tried anonymous , anon , and everyone , but no one reaches them. I want to display some categories for everyone (anonymous) users but not specific automated groups. The Category Lockdown plugin is the closest to it that I had found.

just acking this one and I’m looking. seems like the upstream builds have disappeared.

I want to paste: PS /> coredumpctl debug PID: 19088 (org_kde_powerde) UID: 1000 (RokeJulianLockhart) GID: 1000 (RokeJulianLockhart) Signal: 11 (SEGV) Timestamp: Sat 2026-09-12 23:23:40 BST (9min ago) Command Line: /usr/libexec/org_kde_powerdevil Executable: /usr/libexec/org_kde_powerdevil Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-powerdevil.service Unit: user@1000.service User Unit: plasma-powerdevil.service Slice: user-1000.slice Owner UID: 1000 (RokeJulianLockhart) Boot ID: 6c3ba3ed07c444fb9aed3e98e9c6523c Machine ID: 427143abd98046a4b2c750e2ca0036ea Hostname: beedell.rokeJulianLockhart.skqy07 Storage: /var/lib/systemd/coredump/core.org_kde_powerde.1000.6c3ba3ed07c444fb9aed3e98e9c6523c.19088.1789251820000000.zst (present) Size on Disk: 9.5K Message: Process 19088 (org_kde_powerde) of user 1000 dumped core. GNU gdb (Fedora Linux) 17.2-2.fc44 Copyright (C) 2025 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/li

Not sure if this is the right place to post about this, but it’s the closest topic I could find. Recently we are seeing an uptick in AI generated posts; new users with complicated wall-of-text posts, a bit too well written. The smoking gun is similar posts appearing on a different Discourse forum. My suspicion is a user previously banned for using AI in obnoxious ways, returning to test their latest model. These new posts are of much better quality than previous efforts. The next generation of AI generated posts is going to so hard to distinguish from human writing, we may never be know the difference. The question is, what can be done about it, if anything? So here is a suggestion, possibly a BAD suggestion, but here it goes anyway … We need our own AI-Responders to respond to suspicious new users, answering obvious questions and testing for human generated responses. It might need to happen in a sort of sandbox so it would not be obvious to the new user they are being tested. Original credit for the idea to Randall Munroe. explain xkcd 810: Constructive

Today on meta.discourse.org … Key Stats In the last 24 hours, meta.discourse.org saw 109 new posts across 49 new topics , with 108 likes shared across the returned posts. Top users by posts and likes received: User Posts Likes Moin 10 14 Falco 4 8 Awesomerobot 4 7 Sam 3 7 EricGT 6 6 Steve_Walmsley 5 6 Mcwumbly 6 5 NateDhaliwal 3 5 Satonotdead 13 4 Stephtara 3 4 Interesting Topics #Announcements 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 ). #Community Building Building a feed-style Discourse experience. In a topic about turning Discourse into a Blog,

this is happening again and breaking standard system test CI Minio installer breaks CI Development The minio_runner ’s install script is broken, because of a redirect that’s not being followed. That breaks the shared GitHub action workflows from the .github repository. For our plugins, this means, we cannot run Rails system tests on CI at the moment. They start, but as the setup cannot be completed, they stay red even before the first test runs . Run bundle exec ruby script/install_minio_binaries.rb /__w/zlb-community/zlb-community/vendor/bundle/ruby/3.4.0/gems/minio_runner-1.0.0… The standard Discourse plugin system-test CI failed during its shared MinIO environment setup. The MinIO client download returned HTTP 410 before any plugin system tests ran.

AdamWargon: As far as I know, @codinghorror deliberately avoided the thumbs-down option when first designing Discourse, in order to facilitate dialogue. In order to promote positive human connection, rather than technically accurate Q&A. Cool. And I am agree with him, this is about monitoring AI replies.