![\"CleanShot](\"https://global.discourse-cdn.com/meta/original/4X/5/d/f/5df75d9a6862095053a9b0e1fa51e66c694dcd29.png\")
CleanShot 2026-09-25 at 10.46.081415×505 77.1 KB
这个主题组件是否会更新以反映最近对 user.groups 的弃用？
我在控制台中看到以下警告：
\n\n","post_number":2,"post_type":1,"posts_count":2,"updated_at":"2026-09-25T15:05:23.047Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":3,"readers_count":2,"score":45.6,"yours":false,"topic_id":226068,"topic_slug":"css-classes-for-current-users-groups","topic_title":"当前用户的组的CSS类","topic_html_title":"当前用户的组的CSS类","category_id":120,"display_username":"putty","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Regular","title_is_group":false,"bookmarked":false,"raw":"Will this theme component be updated to reflect the recent `user.groups` [deprecation](https://meta.discourse.org/t/deprecating-the-user-of-user-groups-in-the-user-model-in-javascript/411124)? \n\nI'm getting the following warning in my console:\n>DEPRECATION NOTICE: Calling user.groups is deprecated, use user.visibleGroups instead, it more accurately reflects what this array of groups represents, not all of the user's group memberships may be serialized to the client. For permission checks, check the user's groups server-side and add an attribute to the User/CurrentUserSerializer, or use `resolve_group_memberships: true` for theme settings","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":145678,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"这个主题组件是否会更新以反映最近对 user.groups 的弃用？ \n我在控制台中看到以下警告： \n\n弃用通知：调用 user.groups 已弃用，请改用 user.visibleGroups。它能更准确地反映该组数组所代表的内容，因为并非用户的所有组成员身份都会被序列化到客户端。对于权限检查，请在服务器端检查用户的组，并在 User/CurrentUserSerializer 中添加一个属性，或者为主题设置使用 resolve_group_memberships: true","truncated":true,"post_url":"/t/css-classes-for-current-users-groups/226068/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043870,"name":"putty","username":"putty","avatar_template":"/user_avatar/meta.discourse.org/putty/{size}/370902_2.png","created_at":"2026-09-25T14:58:16.211Z","cooked":"弃用通知：调用 user.groups 已弃用，请改用 user.visibleGroups。它能更准确地反映该组数组所代表的内容，因为并非用户的所有组成员身份都会被序列化到客户端。对于权限检查，请在服务器端检查用户的组，并在 User/CurrentUserSerializer 中添加一个属性，或者为主题设置使用
\nresolve_group_memberships: true
有人知道怎么清除这些消息吗？我可以确认它们不在群组收件箱里（当我点开下拉菜单时，所有群组都没有未读消息）。
\n\n这些消息是慢慢累积起来的，属于那种“以后再说”的情况。虽然不紧急，但当我有真正需要回复的消息时，它们会让界面变得杂乱无章。
","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-09-25T14:58:16.211Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":4,"readers_count":3,"score":5.8,"yours":false,"topic_id":413333,"topic_slug":"how-to-clear-missing-unread-messages","topic_title":"如何清除缺失的未读消息？","topic_html_title":"如何清除缺失的未读消息？","category_id":6,"display_username":"putty","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Regular","title_is_group":false,"bookmarked":false,"raw":"Any guesses on how I can clear these messages? I can confirm they're not in a group inbox (when I select the dropdown, none of the groups have unread messages). \n\n\n\nThese have slowly accumulated, and one of those \"I'll deal with it later\" things. Not a blocker, but it muddies things when I have messages that actually need a response.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":145678,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"有人知道怎么清除这些消息吗？我可以确认它们不在群组收件箱里（当我点开下拉菜单时，所有群组都没有未读消息）。 \n [CleanShot 2026-09-25 at 10.46.08] \n这些消息是慢慢累积起来的，属于那种“以后再说”的情况。虽然不紧急，但当我有真正需要回复的消息时，它们会让界面变得杂乱无章。","truncated":true,"post_url":"/t/how-to-clear-missing-unread-messages/413333/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2043857,"name":"Bernd","username":"ecki","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png","created_at":"2026-09-25T14:33:28.286Z","cooked":"我刚在错误日志里注意到，在 PG 更新之前，日志中似乎有一些与 SQL 相关的错误：
\nJob exception: PG::UndefinedFunction: ERROR: function array_remove(bigint[], integer) does not exist LINE 1: ...ATE \"access_control_lists\" SET allowed_user_ids = array_remo...\n这很奇怪，因为这个函数看起来是 PG9 引入的，而我之前运行的是 15 版本。这会不会是权限或搜索路径（search path）的问题？在数据库更新之后，这个问题似乎没有再出现，但也许这是批处理任务的时间差导致的……我看到这个函数在很多地方都被使用，甚至在迁移脚本中也有。
\n也许这意味着某些函数在旧版 PostgreSQL 上会失败，尽管它们的模板仍然被列在列表中。也许是我疏忽了，但我一直以为旧版本是兼容的。
","post_number":100,"post_type":1,"posts_count":97,"updated_at":"2026-09-25T14:33:28.286Z","reply_count":0,"reply_to_post_number":99,"quote_count":0,"incoming_link_count":1,"reads":4,"readers_count":3,"score":5.8,"yours":false,"topic_id":406194,"topic_slug":"postgresql-18-update-for-self-hosters","topic_title":"面向自托管用户的 PostgreSQL 18 更新","topic_html_title":"面向自托管用户的 PostgreSQL 18 更新","category_id":67,"display_username":"Bernd","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":117384,"username":"ecki","name":"Bernd","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png"},"bookmarked":false,"raw":"I just noticed in the error log, before the PG update, I seem to have some SQL related erros in the logs:\n\n```\nJob exception: PG::UndefinedFunction: ERROR: function array_remove(bigint[], integer) does not exist LINE 1: ...ATE \"access_control_lists\" SET allowed_user_ids = array_remo...\n```\n\nWhich is strange, it looks like this function is from PG9, and I was running 15 before. Could this be a permission or search path problem? It seems it does not occur after the DB update, but maybe its a batch timing thing... I see the function used in quite some places and even migration scripts.\n\nMaybe that means some functions fail on older PostgreSQL despite their templates are stilll listed. MAybe I missed it, but I thought the older versions are compatible.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":117384,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我刚在错误日志里注意到，在 PG 更新之前，日志中似乎有一些与 SQL 相关的错误： \nJob exception: PG::UndefinedFunction: ERROR: function array_remove(bigint[], integer) does not exist LINE 1: ...ATE "access_control_lists" SET allowed_user_ids = array_remo...\n\n这很奇怪，因为这个函数看起来是 PG9 引入的，而我之前运行的是 15 版本。这会不会是权限或搜索路径（search path）的问题？在数据库更新之后，这个…","truncated":true,"post_url":"/t/postgresql-18-update-for-self-hosters/406194/100","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043840,"name":"Kris","username":"awesomerobot","avatar_template":"/user_avatar/meta.discourse.org/awesomerobot/{size}/142900_2.png","created_at":"2026-09-25T14:05:43.114Z","cooked":"nah，这些想法早在2024年就已经在内部讨论过了，用的还是我们老派@chapoi的脑力……不过我不太清楚这有什么意义，不管起源如何，我们验证工作的方式和以前一样，AI并没有指挥我们（至少目前还没有 ![\":laughing:\"](\"https://emoji.discourse-cdn.com/twitter/laughing.png?v=15\" "\\":laughing:\\"")
）
我们推出了新的 Workflows 插件，可用于自动化任务。这些任务可以设置为定期重复执行，还可以选择性地引入 AI 智能体，并且我们一直在该插件中持续添加更多类型的操作。
\n您具体是想要进行哪些站点管理或维护检查？
","post_number":2,"post_type":1,"posts_count":2,"updated_at":"2026-09-25T13:57:19.177Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":9,"readers_count":8,"score":21.6,"yours":false,"topic_id":413327,"topic_slug":"muse-ai","topic_title":"Muse AI","topic_html_title":"Muse AI","category_id":124,"display_username":"Kris","primary_group_name":"team","flair_name":"team","flair_url":"https://global.discourse-cdn.com/meta/original/3X/e/b/ebee30bd98aef20357e4a177a5a1e45b877ce088.svg","flair_bg_color":"","flair_color":"111","flair_group_id":47,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"team","title_is_group":true,"bookmarked":false,"raw":"We have a new [Workflows](https://meta.discourse.org/t/discourse-workflows/407100) plugin that can be used to automate tasks, those can be scheduled to repeat, AI agents can be optionally included, and we've been steadily adding more types of actions there. \n\nAre there specific site management or maintenance checks you had in mind?","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":true,"staff":true,"user_id":2770,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我们推出了新的 Workflows 插件，可用于自动化任务。这些任务可以设置为定期重复执行，还可以选择性地引入 AI 智能体，并且我们一直在该插件中持续添加更多类型的操作。 \n您具体是想要进行哪些站点管理或维护检查？","truncated":true,"post_url":"/t/muse-ai/413327/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043835,"name":"agemo","username":"agemo","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/{size}.png","created_at":"2026-09-25T13:49:22.942Z","cooked":"众所周知，AI 多年来一直在辅助 Discourse 的开发，因此我很好奇这次重新设计中有多少部分是借助 AI 完成的，以及它是“如何”实现的？
\n我之所以好奇，是因为我想了解它的起源——在编写第一行代码之前，是否已经使用了 AI 来进行视觉构图？
","post_number":62,"post_type":1,"posts_count":56,"updated_at":"2026-09-25T13:52:01.470Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":7,"readers_count":6,"score":11.4,"yours":false,"topic_id":407849,"topic_slug":"help-us-test-the-composer-redesign","topic_title":"帮助我们测试 Composer 重新设计","topic_html_title":"帮助我们测试 Composer 重新设计","category_id":67,"display_username":"agemo","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"As we have known Ai has been used to further aid development of Discourse for years, so I wonder how much Ai went into this redesign and \"how\" it occured?\n\nI'm curious because I want to understand it's inception, was AI used for visual composition before a single piece of code was raised?","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":63573,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"众所周知，AI 多年来一直在辅助 Discourse 的开发，因此我很好奇这次重新设计中有多少部分是借助 AI 完成的，以及它是“如何”实现的？ \n我之所以好奇，是因为我想了解它的起源——在编写第一行代码之前，是否已经使用了 AI 来进行视觉构图？","truncated":true,"post_url":"/t/help-us-test-the-composer-redesign/407849/62","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043827,"name":"Falco","username":"Falco","avatar_template":"/user_avatar/meta.discourse.org/falco/{size}/179432_2.png","created_at":"2026-09-25T13:23:53.123Z","cooked":"\n任何提供 OpenAI 兼容 API 的模型都可以使用。
\n\n计算公式为：公开主题数乘以嵌入模型的维度，再乘以 16（数据字节数），加上主题数乘以维度再除以 8（索引部分）。
","post_number":44,"post_type":1,"posts_count":23,"updated_at":"2026-09-25T13:23:53.123Z","reply_count":0,"reply_to_post_number":43,"quote_count":1,"incoming_link_count":0,"reads":6,"readers_count":5,"score":16.2,"yours":false,"topic_id":259603,"topic_slug":"discourse-ai-embeddings","topic_title":"Discourse AI - 嵌入","topic_html_title":"Discourse AI - 嵌入","category_id":53,"display_username":"Falco","primary_group_name":"team","flair_name":"team","flair_url":"https://global.discourse-cdn.com/meta/original/3X/e/b/ebee30bd98aef20357e4a177a5a1e45b877ce088.svg","flair_bg_color":"","flair_color":"111","flair_group_id":47,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"team","title_is_group":true,"bookmarked":false,"raw":"[quote=\"Dmitry_Krasnoperov, post:43, topic:259603\"]\nCan Deepseek be used as provider? Which model?\n\n[/quote]\n\nAny model exposing the OpenAI compatible API can be used.\n\n[quote=\"Dmitry_Krasnoperov, post:43, topic:259603\"]\nHow to estimate cost of creation as I have quite large DB (14.3 GB).\n\n[/quote]\n\nNumber of public topics times the embedding model dimensions times 16 for the data in bytes, plus number of topics times dimensions divided by 8 for the index.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":true,"staff":true,"user_id":8722,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"任何提供 OpenAI 兼容 API 的模型都可以使用。 \n\n计算公式为：公开主题数乘以嵌入模型的维度，再乘以 16（数据字节数），加上主题数乘以维度再除以 8（索引部分）。","truncated":true,"post_url":"/t/discourse-ai-embeddings/259603/44","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"+1","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043821,"name":"putty","username":"putty","avatar_template":"/user_avatar/meta.discourse.org/putty/{size}/370902_2.png","created_at":"2026-09-25T13:18:16.532Z","cooked":"我又仔细想了想，还有几个其他选项：
\n<!-- Hide Me-too -->| User | \nPosts | \nLikes received | \n
|---|---|---|
| Awesomerobot | \n3 | \n14 | \n
| Pmusaraj | \n5 | \n8 | \n
| Ed_S | \n4 | \n7 | \n
| NateDhaliwal | \n4 | \n6 | \n
| MachineScholar | \n3 | \n6 | \n
| Lilly | \n2 | \n6 | \n
| BigDavy | \n6 | \n4 | \n
| Falco | \n1 | \n4 | \n
| Putty | \n2 | \n3 | \n
| DaniW42 | \n1 | \n3 | \n
Here’s what caught the community’s attention over the past day, grouped by category:
\n#Announcements
\nAwesomerobot introduced an experimental user sidebar navigation for user profiles, replacing the horizontal links with a collapsible, filterable sidebar. It’s available via /admin/config/upcoming-changes as sidebar user navigation, and you can join the design experiments group to test it here on Meta. Early feedback flagged that reactions, votes and solved topics are missing from notification lists, while One1 praised the reduced horizontal scrolling but found the “Filter Links” wording confusing (read more).
Markdown endpoints for topic lists and views are now part of Discourse core. Pmusaraj confirmed the discourse-to-markdown plugin should be removed to avoid conflicts and listed the supported routes, including /latest.md, /hot.md, /top.md, /new.md, /unread.md, category and tag lists, plus /categories.md and /tags.md directories (read more). He also noted that Cloudflare’s own Markdown-for-agents conversion will override Discourse’s handling when the Accept: text/markdown header is intercepted. Moin asked why /unseen isn’t included (post), and Ethsim2 wondered whether discourse-post-event blocks will get a dedicated Markdown representation (post).
In the Voice rooms announcement, Putty hit 404 errors when inviting users to voice rooms. Pmusaraj traced the problem to periods in usernames breaking the /invited-by/... route and shared a fix PR (read more), while Falco promised to dig deeper once he’s back from vacation (post).
#Site feedback
\n#Feature
\nTobiaseigen asked how to suppress the “Me too” button on specific topics, and Putty delivered a tidy CSS workaround that hides the button when a (hidden) tag is present (read more).
\nJonathan5 wants to remove the “Latest” tab from the top menu, but Discourse currently insists top_menu must include latest. The related sidebar scroll jump on Categories pages was diagnosed by Awesomerobot as the sidebar auto-scrolling to bring the active link into view (read more).
MachineScholar requested group-based access for Workflow forms, so only designated groups can discover and submit a form — a natural extension of the Discourse Workflows plugin conversation.
\nThe new Markdown endpoints hit a snag when Lilydjwg reported an Encoding::CompatibilityError with non-ASCII usernames like 依云. Pmusaraj quickly opened PR #44106 to fix it (read more).
\nMachineScholar is battling low-resolution, stuttering camera video with a self-hosted LiveKit server. LiveKit logs show duplicate layer and unbound buffer overflowing messages, and Voice appears to request a lower-quality stream than configured (read more).
Sailor reports that RSS Polling now marks unchanged feed items as “Updated the existing topic” on every poll after a recent fix. He suggests exposing the content_changed / title_changed flags from TopicEmbed.import to the poll job so the status is accurate (read more).
The Error for logged in users and Git hang saga continues: Agemo reports that long-standing admins still get the “Oops…” screen while freshly created admins log in fine (post). Ed_S says his forum recovered when GitHub rolled out a fix and suspects it may be geography- or provider-specific (read more).
\nJustinZ found the launcher’s use of 21 is incompatible with BusyBox on Alpine Linux, breaking the disk-space check. Merefield pointed to the install docs, which only require 64-bit Linux despite Ubuntu being recommended, while the broader discussion continues in Bug in discourse launcher (read more).
\n#Plugin
\nAwesomerobot launched the experimental user sidebar navigation and gathered early feedback. They also confirmed a separate AI Q&A homepage feature is in the works, and diagnosed the sidebar scroll quirk on Categories pages.
\nPmusaraj had a productive day: he traced the voice invitation 404s to periods in usernames and opened PR #44088; documented the supported Markdown topic list endpoints; posted PR #44106 to fix the non-ASCII username crash; and explained the security rationale for email codes over magic links in the account signup discussion.
\nChapoi weighed in on the LLM-generated plugin tagging debate, arguing that manually reviewing every third-party theme and plugin is simply not viable.
\nFalco acknowledged the ongoing voice room invite issues and said he’ll pick it up when he returns from vacation.
\nPedro helped troubleshoot the Chat Integrations plugin, advising the poster to check whether their Slack integration is using Granular Scopes.
\nTgxworld earned public thanks for a quick fix that stopped voice badges from reappearing after every update.
\nWhether you’re casting black or white balls, hopping into a voice room, or wrestling a BusyBox stat — may your only 404 today be a page that truly doesn’t exist!
Richard，你好！
\n关于 WordPress/Discourse SSO 的问题，我们想跟你同步一下最新进展，问题已经解决了。
\n最终，我们决定不再继续使用自定义的 DiscourseConnect/HMAC 实现，而是回退到标准的 WP-Discourse DiscourseConnect Provider。
\n我们创建了一个全新的 Discourse API 密钥，轮换（更新）了 DiscourseConnect 共享密钥，在网络层级启用了 WP-Discourse Provider，并将 Discourse Connect URL 从旧的自定义回调地址更改为 WP-Discourse 指定的 WordPress 站点 URL。
\n随后，我们使用一个全新的 WordPress 用户和一个干净的 Discourse 会话进行了测试：
\nWordPress 登录 → 进入社区 → 自动以同一用户身份登录 Discourse。
\n因此，标准的 WP-Discourse 现在可以正确处理 SSO 了。
\n再次感谢你们在排查过程中为我们指明了方向。
\nGee
","post_number":9,"post_type":1,"posts_count":9,"updated_at":"2026-09-25T12:32:48.730Z","reply_count":0,"reply_to_post_number":8,"quote_count":0,"incoming_link_count":0,"reads":4,"readers_count":3,"score":0.8,"yours":false,"topic_id":413092,"topic_slug":"discourseconnect-hmac-validation-fails-with-wordpress-despite-matching-callback-parameters","topic_title":"DiscourseConnect HMAC 验证在 WordPress 中失败，尽管回调参数匹配","topic_html_title":"DiscourseConnect HMAC 验证在 WordPress 中失败，尽管回调参数匹配","category_id":6,"display_username":null,"primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":203801,"username":"Gallussi","name":null,"avatar_template":"https://avatars.discourse-cdn.com/v4/letter/g/ac91a4/{size}.png"},"bookmarked":false,"raw":"Hi Richard,\n\nJust closing the loop on the WordPress/Discourse SSO issue. We got it working.\n\nIn the end, the solution was to go back to the standard **WP-Discourse DiscourseConnect Provider** rather than continuing with our custom DiscourseConnect/HMAC implementation.\n\nWe created a fresh Discourse API key, rotated the DiscourseConnect shared secret, enabled the WP-Discourse Provider at the network level, and changed the Discourse Connect URL from our old custom callback to the WordPress site URL specified by WP-Discourse.\n\nWe then tested with a completely new WordPress user and a clean Discourse session:\n\n**WordPress login → Enter Community → automatically logged into Discourse as the same user.**\n\nSo standard WP-Discourse is now handling the SSO correctly.\n\nThanks again for pointing us in the right direction while we were working through it.\n\nGee","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":203801,"hidden":false,"trust_level":0,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Richard，你好！ \n关于 WordPress/Discourse SSO 的问题，我们想跟你同步一下最新进展，问题已经解决了。 \n最终，我们决定不再继续使用自定义的 DiscourseConnect/HMAC 实现，而是回退到标准的 WP-Discourse DiscourseConnect Provider。 \n我们创建了一个全新的 Discourse API 密钥，轮换（更新）了 DiscourseConnect 共享密钥，在网络层级启用了 WP-Discourse Provider，并将 Discourse Connect URL 从旧的自定义回调地址更改为 WP-Discours…","truncated":true,"post_url":"/t/discourseconnect-hmac-validation-fails-with-wordpress-despite-matching-callback-parameters/413092/9","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043776,"name":null,"username":"aliciadavid","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/a/58f4c7/{size}.png","created_at":"2026-09-25T11:24:24.195Z","cooked":"我最近正在测试 Meta 新推出的 Muse from Meta 智能体，看看它在处理后台自动化任务方面的表现。由于我已经将我的网站迁移到了 WordPress，我想知道是否有人尝试过使用这类智能体工具来简化网站管理、处理重复性的维护检查，或协助撰写内容。
","post_number":1,"post_type":1,"posts_count":2,"updated_at":"2026-09-25T11:24:24.195Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":22,"readers_count":21,"score":59.4,"yours":false,"topic_id":413327,"topic_slug":"muse-ai","topic_title":"Muse AI","topic_html_title":"Muse AI","category_id":124,"display_username":null,"primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"I am testing out Meta's new [Muse from Meta](https://muse.ai) agent recently to see how it handles background automation tasks. Since I automated my site on WordPress, I was wondering if anyone has tried using agentic tools like this to streamline site management, handle repetitive maintenance checks, or assist with content drafting.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":203331,"hidden":false,"trust_level":0,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我最近正在测试 Meta 新推出的 Muse from Meta 智能体，看看它在处理后台自动化任务方面的表现。由于我已经将我的网站迁移到了 WordPress，我想知道是否有人尝试过使用这类智能体工具来简化网站管理、处理重复性的维护检查，或协助撰写内容。","truncated":true,"post_url":"/t/muse-ai/413327/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2043770,"name":"Dmitry Krasnoperov","username":"Dmitry_Krasnoperov","avatar_template":"/user_avatar/meta.discourse.org/dmitry_krasnoperov/{size}/65079_2.png","created_at":"2026-09-25T11:07:11.818Z","cooked":"可以使用 Deepseek 作为提供商吗？应该选择哪个模型？
\n由于我的数据库相当大（14.3 GB），如何估算创建成本？
大家好，
\n我最近为 Discourse 的语音功能搭建了一个 LiveKit 服务器。通话可以正常连接，音频效果也很好，但摄像头视频始终模糊且严重卡顿（帧率在 8-20 FPS 之间，伴有大量画面冻结）。
\n我尝试了不同的设备、浏览器和视频质量设置（包括最高画质），但问题仍未解决。
\n我的配置如下：
\n在一次两人的测试中（分别使用 Chrome 和 Safari），使用 Safari 的一方看到使用 Chrome 一方的视频出现卡顿。
\n在大家的协助排查下，我们检查了通话期间的 LiveKit 服务器状态。服务器负载非常低，且两个浏览器均通过 UDP 连接。日志中包含以下信息：
\nadding up track failed: duplicate layer\n\nunbound buffer overflowing, dropping packets\n在排查过程中，出现了两个可能相关的现象：
\n我不确定这些发现是否能解释全部问题，而且由于这是生产环境，我尚未应用任何代码更改。
\n有没有其他人遇到过使用语音功能配合自托管 LiveKit 服务器时的类似问题？是否有我遗漏的设置，或者这可能是集成方面的问题？
","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-09-25T14:51:29.848Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":16,"readers_count":15,"score":68.2,"yours":false,"topic_id":413325,"topic_slug":"voice-self-hosted-livekit-low-resolution-camera-video-and-one-way-stuttering","topic_title":"语音 + 自托管 LiveKit：低分辨率摄像头视频和单向卡顿","topic_html_title":"语音 + 自托管 LiveKit：低分辨率摄像头视频和单向卡顿","category_id":1,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":2,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Bug Reporter","title_is_group":false,"bookmarked":false,"raw":"Hi everyone,\n\nI recently set up a LiveKit server for Discourse’s Voice feature. Calls connect and audio sounds great, but camera video is consistently blurry and very laggy (frames per second between 8-20 with lots of frozen frames).\n\nI’ve tried different devices, browsers, and video-quality settings, including Maximum, without resolving it.\n\nMy setup:\n\n* Discourse 2026.10.0-latest\n* LiveKit v1.13.7\n* Discourse and LiveKit run on separate DigitalOcean servers in the same VPC.\n* Both servers have DigitalOcean firewalls.\n* No custom changes to Discourse or LiveKit’s code.\n\nIn one two-person test using Chrome and Safari, the person using Safari saw the Chrome participant’s video stuttering.\n\nWith some help troubleshooting, we checked the LiveKit server during the call. It was under very little load, and both browsers were connecting over UDP. The logs included these messages:\n\n```\nadding up track failed: duplicate layer\n\nunbound buffer overflowing, dropping packets\n```\n\n Two things came up during that investigation that might be relevant:\n\n* Voice appears to request a lower-resolution camera stream even when higher quality is selected, which might explain the blurry picture.\n* There are signs that the same camera might be getting published twice, which might be related to the stuttering.\n\nI don’t know whether those findings explain the whole problem, and I haven’t applied any code changes since this is my production site.\n\nHas anyone else experienced this with Voice and a self-hosted LiveKit server? Is there a setting I might have missed, or could this be an issue with the integration?","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":150857,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"大家好， \n我最近为 Discourse 的语音功能搭建了一个 LiveKit 服务器。通话可以正常连接，音频效果也很好，但摄像头视频始终模糊且严重卡顿（帧率在 8-20 FPS 之间，伴有大量画面冻结）。 \n我尝试了不同的设备、浏览器和视频质量设置（包括最高画质），但问题仍未解决。 \n我的配置如下： \n\nDiscourse 2026.10.0-latest\nLiveKit v1.13.7\nDiscourse 和 LiveKit 分别运行在同一 VPC 内的两台 DigitalOcean 服务器上。\n两台服务器均配置了 DigitalOcean 防火墙。\n未对 Discourse 或 Live…","truncated":true,"post_url":"/t/voice-self-hosted-livekit-low-resolution-camera-video-and-one-way-stuttering/413325/1","locale":"en","is_localized":true,"language":"en","localization_outdated":true,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[{"id":"eyes","type":"emoji","count":1},{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2043761,"name":"Robert","username":"merefield","avatar_template":"/user_avatar/meta.discourse.org/merefield/{size}/176214_2.png","created_at":"2026-09-25T10:33:16.892Z","cooked":"\n有道理，因为：
\ndiscourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub 指出 64 位 Linux 是基本要求（尽管 Ubuntu 被“推荐”使用）
","post_number":6,"post_type":1,"posts_count":6,"updated_at":"2026-09-25T10:33:52.366Z","reply_count":0,"reply_to_post_number":5,"quote_count":1,"incoming_link_count":1,"reads":6,"readers_count":5,"score":6.2,"yours":false,"topic_id":412435,"topic_slug":"bug-in-discourse-launcher","topic_title":"Discourse 启动器存在 Bug","topic_html_title":"Discourse 启动器存在 Bug","category_id":31,"display_username":"Robert","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Plugin Author","title_is_group":false,"bookmarked":false,"raw":"[quote=\"JustinZ, post:5, topic:412435\"]\nThe idea that the docker container isn’t actually portable between distros is confusing as that is what docker is for, works “everywhere docker is”.\n[/quote]\n\nFair, because:\n\nhttps://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md#server-specifications suggests 64-bit Linux is the basic requirement (even though Ubuntu is \"recommended\")","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":27384,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"有道理，因为： \ndiscourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub 指出 64 位 Linux 是基本要求（尽管 Ubuntu 被“推荐”使用）","truncated":true,"post_url":"/t/bug-in-discourse-launcher/412435/6","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043692,"name":"Justin","username":"JustinZ","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/j/e68b1a/{size}.png","created_at":"2026-09-25T07:24:43.936Z","cooked":"谢谢，我会在那里讨论。
","post_number":3,"post_type":1,"posts_count":3,"updated_at":"2026-09-25T07:24:43.936Z","reply_count":0,"reply_to_post_number":2,"quote_count":0,"incoming_link_count":1,"reads":7,"readers_count":6,"score":6.4,"yours":false,"topic_id":413298,"topic_slug":"stat-usage-in-launcher-not-cross-distro-compatible","topic_title":"启动器中的统计信息无法跨发行版使用","topic_html_title":"启动器中的统计信息无法跨发行版使用","category_id":6,"display_username":"Justin","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":63143,"username":"Ed_S","name":"Ed S","avatar_template":"/user_avatar/meta.discourse.org/ed_s/{size}/134015_2.png"},"bookmarked":false,"raw":"Thanks, I'll discuss there.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":96979,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"谢谢，我会在那里讨论。","truncated":true,"post_url":"/t/stat-usage-in-launcher-not-cross-distro-compatible/413298/3","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043690,"name":"Justin","username":"JustinZ","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/j/e68b1a/{size}.png","created_at":"2026-09-25T07:24:13.441Z","cooked":"认为 Docker 容器在不同发行版之间并不真正具有可移植性，这种说法令人困惑，因为 Docker 的设计初衷就是“在任何支持 Docker 的环境中都能运行”。
\n启动脚本可以改用 df 命令代替 stat，因为 df 在 Alpine 和 Ubuntu 上输出的信息是相同的。
我今天早上更新了，语音徽章没有再出现。
\n感谢 @tgxworld 的快速修复 ![\":person_bowing:t2:\"](\"https://emoji.discourse-cdn.com/twitter/person_bowing/2.png?v=15\" "\\":person_bowing:t2:\\"")
核心团队是否计划为 discourse-post-event 块提供专用的 Markdown 表示形式，就像投票、引用、onebox 和可折叠区块那样？从技术角度来看，在 CookedProcessor 中添加这一功能似乎是相当可行的：检测 div.discourse-post-event，读取其 data-* 属性，并在通用的 ReverseMarkdown 处理之前将其替换为保留的 Markdown 块。
嗨 @BigDavy，我做过类似的 Discourse 项目。刚给你发了私信，里面有一些示例。
","post_number":4,"post_type":1,"posts_count":4,"updated_at":"2026-09-25T06:54:53.710Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":14,"readers_count":13,"score":7.8,"yours":false,"topic_id":413244,"topic_slug":"paid-discourse-specialist-wanted-premium-private-membership-community","topic_title":"[有偿] 招聘Discourse专家 – 高端私密会员社区","topic_html_title":"[有偿] 招聘Discourse专家 – 高端私密会员社区","category_id":14,"display_username":"Anna Radnor","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Hi @BigDavy I’ve worked on similar Discourse projects. Just sent you a DM with some examples.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":170236,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"嗨 @BigDavy，我做过类似的 Discourse 项目。刚给你发了私信，里面有一些示例。","truncated":true,"post_url":"/t/paid-discourse-specialist-wanted-premium-private-membership-community/413244/4","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043655,"name":"Jakke Flemming","username":"Jagster","avatar_template":"/user_avatar/meta.discourse.org/jagster/{size}/192154_2.png","created_at":"2026-09-25T06:06:32.415Z","cooked":"当然！它应该改变，但
\n\n这目前已经可以通过编辑站点文本来实现。但修改所有可能的语言变量可能有点棘手 ![\":wink:\"](\"https://emoji.discourse-cdn.com/twitter/wink.png?v=15\" "\\":wink:\\"")
我喜欢！我真的很反对横向滚动的界面。屏幕外的内容太容易被忽略了。
\n对我来说，“筛选链接”这个说法没什么意义。
\n\n我根本不会把它们看作“链接”。它们更像是菜单项。遗憾的是，你无法为所有用户设置提供完整的搜索/筛选功能，但也许大家调整设置的频率并不高，不值得为此投入。
\n就我个人而言，我觉得“徽章”是个人资料中不太重要的部分，所以我更希望把它放在列表的末尾。
\n感谢你的工作。这是一个很大的改进。
","post_number":4,"post_type":1,"posts_count":4,"updated_at":"2026-09-25T05:14:04.699Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":12,"readers_count":11,"score":52.4,"yours":false,"topic_id":413150,"topic_slug":"experimental-user-sidebar-navigation","topic_title":"实验性用户侧边栏导航","topic_html_title":"实验性用户侧边栏导航","category_id":67,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"I like it! I'm really against horizontal scrolling interfaces. Far too easy to miss things off screen.\n\nTo me, \"Filter Links\" doesn't make much sense.\n\n\n\nI don't really think of those as \"links\". They are more like menu items. It's too bad you can't have a full search/filter for all user settings, but maybe people don't tweak settings enough to make it worth it.\n\nPersonally, I feel like \"Badges\" are the least important part of a profile, so I'd prefer if it was at the end of the list. \n\nThanks for working on this. It's a big improvement.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":80288,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我喜欢！我真的很反对横向滚动的界面。屏幕外的内容太容易被忽略了。 \n对我来说，“筛选链接”这个说法没什么意义。 \n [image] \n我根本不会把它们看作“链接”。它们更像是菜单项。遗憾的是，你无法为所有用户设置提供完整的搜索/筛选功能，但也许大家调整设置的频率并不高，不值得为此投入。 \n就我个人而言，我觉得“徽章”是个人资料中不太重要的部分，所以我更希望把它放在列表的末尾。 \n感谢你的工作。这是一个很大的改进。","truncated":true,"post_url":"/t/experimental-user-sidebar-navigation/413150/4","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043650,"name":"system","username":"system","avatar_template":"/user_avatar/meta.discourse.org/system/{size}/443519_2.png","created_at":"2026-09-25T05:04:00.694Z","cooked":"The last 24 hours on Meta were busy: 81 new posts across 36 new topics, with 65 likes given out.
\n| User | \nPosts | \nLikes | \n
|---|---|---|
| Awesomerobot | \n3 | \n11 | \n
| Pmusaraj | \n5 | \n6 | \n
| Ed_S | \n4 | \n5 | \n
| NateDhaliwal | \n4 | \n5 | \n
| Lilly | \n2 | \n5 | \n
| MachineScholar | \n2 | \n4 | \n
| Falco | \n1 | \n4 | \n
| BigDavy | \n6 | \n3 | \n
| Putty | \n2 | \n3 | \n
| DaniW42 | \n1 | \n3 | \n
The most-liked conversation of the day (13 likes) was about how to handle LLM-generated themes and plugins, with the new voice and video rooms announcement close behind (10 likes).
\nThe debate over requiring LLM-generated themes and plugins to be tagged as such is still drawing strong opinions. Chapoi was blunt:
\n\n\n“I can with 100% confidence say that’s absolutely not a viable idea, for us to review every third party plugin and theme.”
\n
Ed_S floated a self-certified checklist approach, NateDhaliwal pushed back on calling AI-assisted work “slop,” and Lilly noted she uses AI to assist, not replace, her own judgement. read more
\nVoice: Discord-style voice and video rooms are now bundled with Discourse, but invite links were returning 404s. Pmusaraj traced it to periods in usernames being rejected by the /invited-by/ route and shared a core fix. Falco is on holiday and will dig deeper when he’s back. read more
Awesomerobot unveiled the experimental user sidebar navigation, applying the contextual sidebar design to user profiles. Early testers noticed missing reactions, votes and solved items in notifications, and Awesomerobot also diagnosed the related sidebar scroll-to-active-link quirk that surfaced while testing Jonathan5's “no Latest tab” idea. read more
\nDiscourse core now includes Markdown endpoints for topic lists and views. Pmusaraj walked through the supported routes — /latest.md, /new.md, /c/category/12.md, /tag/example.md — and warned that the old Discourse-to-Markdown plugin must be removed to avoid conflicts. Eisammy shared detailed Cloudflare proxy testing notes, confirming the origin sends the right Vary: Accept headers. read more
Removing Uncategorized and migrating to a standard category is about to become permanent, and Steffahn flagged that it isn’t entirely invisible: uncategorized posts now carry an “Uncategorized” badge and the composer behaves differently from a plain pre-selected category. They pointed back to sam’s year-old recommendation for a theme component that preserves the old look. read more
\nEasier account signup using email codes prompted questions about making the new mechanism optional. Pmusaraj explained why a single email-confirmation mechanism is better for security — and why codes are less vulnerable to social engineering than magic links.
\nLilydjwg hit an Encoding::CompatibilityError on the new Markdown links when a topic has a non-ASCII username (like 依云). Pmusaraj responded with a fix in pull request #44106. Meanwhile, Ethsim2 reported Markdown escaping differences on iOS Safari when copying from /raw/. read more
Sailor spotted a regression: after the slow feed processing fix, unchanged RSS items are now reported as “Updated the existing topic” on every poll. They suggest exposing whether TopicEmbed.import actually changed anything. read more
The error-for-logged-in-users and Git hang story continues: Ed_S's forum recovered after GitHub relaxed its over-defensive systems, while Agemo found that creating a fresh admin via rake restores access — even though the original admins remain locked out. read more
\nJustinZ reported that the launcher’s 8 usage breaks on BusyBox (Alpine Linux), since format=%a*%S isn’t portable. Ed_S pointed to the earlier report noting the launcher assumes Debian/Ubuntu coreutils. read more
MachineScholar proposed limiting workflow forms to specific groups — e.g., Teacher A in School A shouldn’t see School Y’s form — echoing the Discourse Workflows request. read more
\nTobiaseigen wanted the “Me too” button gone from specific topics — and Putty delivered an elegant CSS trick that hides it when a (hidden) tag is present. read more
\nSailor filed two closely related RSS Polling improvements: extension points for plugins (a feed-form outlet, feed ID in import args, and an update-path hook) and reading video descriptions from YouTube channel feeds, since Media RSS content is currently dropped before it reaches FeedItem. read more
![\"image\"](\"https://global.discourse-cdn.com/meta/original/4X/6/f/e/6fe85d04d2564fad74c0105522ec9954a7e6c494.png\")
/boards intro line “Create and manage boards with columns” is odd for regular viewers who can do neither, and the page could use a rename option (roadmap, projects, …). read moreThe Team group was all over announcements, bug fixes, and community support:
\nAwesomerobot announced the experimental user sidebar navigation, confirmed plans for a companion feature in the AI Q&A homepage thread, and explained the sidebar scroll-to-active-link behavior on the Categories page.
\nPmusaraj was a support machine: he documented the new Markdown endpoints, answered Cloudflare compatibility questions, fixed the Markdown encoding bug, explained the email-code signup design, and rooted out the voice-room invite 404 caused by dots in usernames.
\nEd_S shared his own GitHub-outage experience, linked the known launcher stat issue, and proposed a self-certified checklist in the LLM-generated assets debate.
\nChapoi put his foot down in that same debate: manually reviewing every third-party theme and plugin is simply not viable.
\nFalco acknowledged the voice-room invite reports and will pick them up when he’s back from vacation — while Gilles sent him off with bonnes vacances (translation: have a good holiday!).
\nPedro recommended checking Slack’s Granular Scopes for a Chat Integrations setup that had stopped reacting to new posts.
\nFrom black-and-white ballots to sky-blue voice rooms, and from AI-slop squabbles to silent RSS feeds, it was a day of big debates and tiny fixes — so while Falco sips a piña colada on some sunny beach, the rest of us will just have to keep making Discourse better. ![\":palm_tree:\"](\"https://emoji.discourse-cdn.com/twitter/palm_tree.png?v=15\" "\\":palm_tree:\\"")
![\":hot_beverage:\"](\"https://emoji.discourse-cdn.com/twitter/hot_beverage.png?v=15\" "\\":hot_beverage:\\"")
确实，我认为传统上判断某样东西质量的方法，就是查看制作该产品的实体（或人）的声誉。当一个人活跃于开源社区时，个人声誉往往非常有效。通常来说，如果某人过去做过出色的工作并且响应及时，他们未来也会继续保持这种状态。
","post_number":54,"post_type":1,"posts_count":54,"updated_at":"2026-09-25T04:34:07.545Z","reply_count":0,"reply_to_post_number":53,"quote_count":1,"incoming_link_count":1,"reads":12,"readers_count":11,"score":22.4,"yours":false,"topic_id":412871,"topic_slug":"require-llm-generated-themes-plugins-to-be-tagged-as-such","topic_title":"要求对由 LLM 生成的主题和插件进行相应标注","topic_html_title":"要求对由 LLM 生成的主题和插件进行相应标注","category_id":3,"display_username":"Ed S","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Bug Reporter","title_is_group":false,"bookmarked":false,"raw":"[quote=\"Lilly, post:53, topic:412871\"]\ni control the agents, review the code (sometimes with another agent or llm set of eyes to help), and test them.\n[/quote]\n\nIndeed, I think the traditional approach to knowing the quality of something is to check the reputation of the entity which made the thing. Personal reputation works well, when a person is active in open source. Generally, if someone has previously done good work and been responsive, they will continue to do so.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":63143,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"确实，我认为传统上判断某样东西质量的方法，就是查看制作该产品的实体（或人）的声誉。当一个人活跃于开源社区时，个人声誉往往非常有效。通常来说，如果某人过去做过出色的工作并且响应及时，他们未来也会继续保持这种状态。","truncated":true,"post_url":"/t/require-llm-generated-themes-plugins-to-be-tagged-as-such/412871/54","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043632,"name":"Ed S","username":"Ed_S","avatar_template":"/user_avatar/meta.discourse.org/ed_s/{size}/134015_2.png","created_at":"2026-09-25T04:28:40.421Z","cooked":"如前所述，大约十天前：
\n","post_number":2,"post_type":1,"posts_count":3,"updated_at":"2026-09-25T04:28:40.421Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":10,"readers_count":9,"score":27.0,"yours":false,"topic_id":413298,"topic_slug":"stat-usage-in-launcher-not-cross-distro-compatible","topic_title":"启动器中的统计信息无法跨发行版使用","topic_html_title":"启动器中的统计信息无法跨发行版使用","category_id":6,"display_username":"Ed S","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Bug Reporter","title_is_group":false,"bookmarked":false,"raw":"See previously, about ten days ago:\n[quote=\"darkpixlz, post:4, topic:412435\"]\nI think that the launcher script expects you are running on Debian/Ubuntu. It seems like your stat error is from the BusyBox version of `stat` not recognizing the `format` flag here\n[/quote]","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":63143,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"如前所述，大约十天前：","truncated":true,"post_url":"/t/stat-usage-in-launcher-not-cross-distro-compatible/413298/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043611,"name":"Justin","username":"JustinZ","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/j/e68b1a/{size}.png","created_at":"2026-09-25T03:31:27.426Z","cooked":"看起来 launcher 工具针对特定版本的 stat 使用了特定的语法。
Would you like to attempt to recover space by cleaning docker images and containers in the system? (y/N) y\nFinished cleaning\nstat: unrecognized option: format=%a*%S\nBusyBox v1.37.0 (2026-01-10 15:38:28 UTC) multi-call binary.\n由于我目前还有超过 5GB 的可用空间，我刚刚编辑了 launcher 文件，让它返回 true 以暂时绕过这个问题，但最好能使用一个可以在任何平台上运行的工具。
供参考，我这是在 Alpine Linux 上使用的。
","post_number":1,"post_type":1,"posts_count":3,"updated_at":"2026-09-25T03:31:27.426Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":11,"readers_count":10,"score":12.2,"yours":false,"topic_id":413298,"topic_slug":"stat-usage-in-launcher-not-cross-distro-compatible","topic_title":"启动器中的统计信息无法跨发行版使用","topic_html_title":"启动器中的统计信息无法跨发行版使用","category_id":6,"display_username":"Justin","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"It seems that the `launcher` tool uses a specific syntax for a specific release of `stat`.\n\n```\nWould you like to attempt to recover space by cleaning docker images and containers in the system? (y/N) y\nFinished cleaning\nstat: unrecognized option: format=%a*%S\nBusyBox v1.37.0 (2026-01-10 15:38:28 UTC) multi-call binary.\n```\n\nI just edited the launcher file to return `true` to workaround this for now as I have more than 5GB free, but it would be nice to see a tool used that can be used on any platform.\n\nI'm using this on Alpine Linux for reference.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":96979,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"看起来 launcher 工具针对特定版本的 stat 使用了特定的语法。 \nWould you like to attempt to recover space by cleaning docker images and containers in the system? (y/N) y\nFinished cleaning\nstat: unrecognized option: format=%a*%S\nBusyBox v1.37.0 (2026-01-10 15:38:28 UTC) multi-call binary.\n\n由于我目前还有超过 5GB 的可用空间，我刚刚编辑了 launche…","truncated":true,"post_url":"/t/stat-usage-in-launcher-not-cross-distro-compatible/413298/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2043602,"name":"Nate Dhaliwal","username":"NateDhaliwal","avatar_template":"/user_avatar/meta.discourse.org/natedhaliwal/{size}/313494_2.png","created_at":"2026-09-25T02:41:50.325Z","cooked":"是在回复上还是在主题上？我通过“帖子菜单 > 管理员扳手 > 更改所有权”成功修改了两者。在安全模式下也能这样操作吗？
","post_number":2,"post_type":1,"posts_count":2,"updated_at":"2026-09-25T02:43:57.653Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":10,"readers_count":9,"score":52.0,"yours":false,"topic_id":413292,"topic_slug":"how-to-change-an-author-in-nested-categories","topic_title":"如何更改嵌套分类中的作者","topic_html_title":"如何更改嵌套分类中的作者","category_id":6,"display_username":"Nate Dhaliwal","primary_group_name":null,"flair_name":"plugin_authors","flair_url":"plug","flair_bg_color":"dddddd","flair_color":"111111","flair_group_id":48,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Senior Tester","title_is_group":false,"bookmarked":false,"raw":"On a reply or the topic? I managed to change both via post menu > admin wrench > Change ownership. Does it work in safe mode?","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":135392,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"是在回复上还是在主题上？我通过“帖子菜单 > 管理员扳手 > 更改所有权”成功修改了两者。在安全模式下也能这样操作吗？","truncated":true,"post_url":"/t/how-to-change-an-author-in-nested-categories/413292/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":true,"topic_accepted_answer":true},{"id":2043594,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-25T02:34:17.197Z","cooked":"我在想这个问题有没有什么变通方法？试过 rails 控制台；当启用嵌套视图时，作者无法被更改。
\n也许这是与我当前实例相关的某个问题？
","post_number":1,"post_type":1,"posts_count":2,"updated_at":"2026-09-25T02:34:17.197Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":11,"readers_count":10,"score":7.2,"yours":false,"topic_id":413292,"topic_slug":"how-to-change-an-author-in-nested-categories","topic_title":"如何更改嵌套分类中的作者","topic_html_title":"如何更改嵌套分类中的作者","category_id":6,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"I wonder if there is a workaround for this? Tried rails console; the author can not be changed when nested view is enabled.\n\nPerhaps it is something tied to my instance?","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我在想这个问题有没有什么变通方法？试过 rails 控制台；当启用嵌套视图时，作者无法被更改。 \n也许这是与我当前实例相关的某个问题？","truncated":true,"post_url":"/t/how-to-change-an-author-in-nested-categories/413292/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":true,"can_vote":false},{"id":2043591,"name":"Penar Musaraj","username":"pmusaraj","avatar_template":"/user_avatar/meta.discourse.org/pmusaraj/{size}/119489_2.png","created_at":"2026-09-25T02:24:44.230Z","cooked":"感谢反馈，此修复应能解决该问题
\n","post_number":3,"post_type":1,"posts_count":2,"updated_at":"2026-09-25T02:24:44.230Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":7,"readers_count":6,"score":21.4,"yours":false,"topic_id":413290,"topic_slug":"incompatible-character-encodings-for-some-markdown-links","topic_title":"部分 Markdown 链接的字符编码不兼容","topic_html_title":"部分 Markdown 链接的字符编码不兼容","category_id":1,"display_username":"Penar Musaraj","primary_group_name":"team","flair_name":"team","flair_url":"https://global.discourse-cdn.com/meta/original/3X/e/b/ebee30bd98aef20357e4a177a5a1e45b877ce088.svg","flair_bg_color":"","flair_color":"111","flair_group_id":47,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"team","title_is_group":true,"bookmarked":false,"raw":"Thanks for the report, this should fix it\n\nhttps://github.com/discourse/discourse/pull/44106","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":true,"staff":true,"user_id":21029,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"感谢反馈，此修复应能解决该问题","truncated":true,"post_url":"/t/incompatible-character-encodings-for-some-markdown-links/413290/3","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043587,"name":"","username":"twofoursixeight","avatar_template":"/user_avatar/meta.discourse.org/twofoursixeight/{size}/574822_2.png","created_at":"2026-09-25T01:50:31.891Z","cooked":"我还想补充一点，由于侧边栏中没有显示，我在通知里也看不到投票或已解决的帖子。
\n","post_number":3,"post_type":1,"posts_count":4,"updated_at":"2026-09-25T01:50:31.891Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":22,"readers_count":21,"score":54.4,"yours":false,"topic_id":413150,"topic_slug":"experimental-user-sidebar-navigation","topic_title":"实验性用户侧边栏导航","topic_html_title":"实验性用户侧边栏导航","category_id":67,"display_username":"","primary_group_name":null,"flair_name":"theme_creator","flair_url":"palette","flair_bg_color":"ddd","flair_color":"111","flair_group_id":84,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Ghostwriter","title_is_group":false,"bookmarked":false,"raw":"Want to also add i cannot see votes or solved topics in my notifications either due to not being in my sidebar\n\n","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":120090,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我还想补充一点，由于侧边栏中没有显示，我在通知里也看不到投票或已解决的帖子。 \n [Screenshot_20260924_184847_Chrome]","truncated":true,"post_url":"/t/experimental-user-sidebar-navigation/413150/3","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043585,"name":null,"username":"lilydjwg","avatar_template":"/user_avatar/meta.discourse.org/lilydjwg/{size}/515838_2.png","created_at":"2026-09-25T01:42:42.905Z","cooked":"我刚了解到新的 .md 链接支持，所以在更新到最新版本后，我在自己的网站上尝试了一下，结果有时会出现以下错误：
![\"Screenshot_20260924_184847_Chrome\"](\"https://global.discourse-cdn.com/meta/original/4X/2/e/a/2eae9f43dfa2da21e847f1fc844849c5615266b0.jpeg\")
Encoding::CompatibilityError (incompatible character encodings: UTF-8 and US-ASCII)\nlib/markdown_endpoint/topic_renderer.rb:83:in 'MarkdownEndpoint::TopicRenderer#render_post'\nlib/markdown_endpoint/topic_renderer.rb:23:in 'block in MarkdownEndpoint::TopicRenderer#render'\nlib/markdown_endpoint/topic_renderer.rb:21:in 'Array#each'\nlib/markdown_endpoint/topic_renderer.rb:21:in 'Enumerable#each_with_index'\nlib/markdown_endpoint/topic_renderer.rb:21:in 'MarkdownEndpoint::TopicRenderer#render'\napp/controllers/topics_controller.rb:1592:in 'block (2 levels) in TopicsController#perform_show_response'\napp/controllers/topics_controller.rb:1568:in 'TopicsController#perform_show_response'\napp/controllers/topics_controller.rb:233:in 'TopicsController#show'\napp/controllers/application_controller.rb:458:in 'block in ApplicationController#with_resolved_locale'\napp/controllers/application_controller.rb:458:in 'ApplicationController#with_resolved_locale'\napp/controllers/application_controller.rb:1140:in 'ApplicationController#ensure_dont_cache_page'\nlib/middleware/omniauth_bypass_middleware.rb:35:in 'Middleware::OmniauthBypassMiddleware#call'\nlib/middleware/crawler_hooks.rb:13:in 'Middleware::CrawlerHooks#call'\nlib/content_security_policy/middleware.rb:12:in 'ContentSecurityPolicy::Middleware#call'\nlib/middleware/anonymous_cache.rb:431:in 'Middleware::AnonymousCache#call'\nlib/middleware/csp_script_nonce_injector.rb:13:in 'Middleware::CspScriptNonceInjector#call'\nlib/middleware/track_view_session_id_injector.rb:12:in 'Middleware::TrackViewSessionIdInjector#call'\nconfig/initializers/008-rack-cors.rb:14:in 'Discourse::Cors#call'\nlib/middleware/default_headers.rb:13:in 'Middleware::DefaultHeaders#call'\nconfig/initializers/100-quiet_logger.rb:20:in 'DiscourseRackQuietAssetsLogger#call'\nconfig/initializers/100-silence_logger.rb:29:in 'SilenceLogger#call'\nlib/middleware/enforce_hostname.rb:23:in 'Middleware::EnforceHostname#call'\nlib/middleware/request_tracker.rb:384:in 'Middleware::RequestT...\n看起来它不兼容我的非 ASCII 用户名（依云）。
查看自己的通知时，似乎缺少了反应。
","post_number":2,"post_type":1,"posts_count":4,"updated_at":"2026-09-25T01:08:38.024Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":24,"readers_count":23,"score":54.8,"yours":false,"topic_id":413150,"topic_slug":"experimental-user-sidebar-navigation","topic_title":"实验性用户侧边栏导航","topic_html_title":"实验性用户侧边栏导航","category_id":67,"display_username":"Lillian ","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"reactions seems to be missing when viewing my own notifications","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":127856,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"查看自己的通知时，似乎缺少了反应。","truncated":true,"post_url":"/t/experimental-user-sidebar-navigation/413150/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043577,"name":"Pedro Maldonado","username":"pedro","avatar_template":"/user_avatar/meta.discourse.org/pedro/{size}/365099_2.png","created_at":"2026-09-24T23:25:52.232Z","cooked":"以防万一，能否请您再次确认一下，您的 Slack 集成目前是否正在使用 Granular Scopes？
\n","post_number":4,"post_type":1,"posts_count":4,"updated_at":"2026-09-24T23:26:13.768Z","reply_count":0,"reply_to_post_number":3,"quote_count":0,"incoming_link_count":1,"reads":8,"readers_count":7,"score":6.6,"yours":false,"topic_id":412438,"topic_slug":"chat-integrations-plugin-doesnt-react-on-new-posts","topic_title":"聊天集成插件对新帖子没有反应","topic_html_title":"聊天集成插件对新帖子没有反应","category_id":6,"display_username":"Pedro Maldonado","primary_group_name":"team","flair_name":"team","flair_url":"https://global.discourse-cdn.com/meta/original/3X/e/b/ebee30bd98aef20357e4a177a5a1e45b877ce088.svg","flair_bg_color":"","flair_color":"111","flair_group_id":47,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"team","title_is_group":true,"reply_to_user":{"id":203103,"username":"Soma","name":"","avatar_template":"/user_avatar/meta.discourse.org/soma/{size}/577764_2.png"},"bookmarked":false,"raw":"Just in case, could you double-check if your Slack integration is currently using Granular Scopes?\n\n [quote=\"Discourse, post:1, topic:66730\"]\n## Upgrading to ‘Granular Scopes’\n\nIf you set up your integration a while ago, you may need to upgrade to Slack’s “Granular Scopes” for things to work as described above.\n\n[details=\"Instructions\"]\n 1. Go to https://api.slack.com/apps and choose your Discourse integration app\n\n 2. On the left, choose “Update to Granular Scopes”\n\n \n\n 3. For “Bot Token Scopes”, select `chat:write` and `chat:write.customize`. If you’re using slash commands and/or transcript posting, also select `users:read`, `channels:history`, `groups:history`, `im:history`. You can unselect all other scopes.\n\n 4. Click Next\n\n 5. Uncheck all User Token scopes - we don’t need any of them\n\n 6. Click Next, and complete the migration by clicking “Yes, Migrate my app”\n\n 7. On the left, choose “Install App”, then “Reinstall to Workspace”\n\n 8. Copy the “Bot User OAuth Token”, and paste it into the “chat_integration_slack_access_token” setting in Discourse\n\n 9. In the Slack sidebar, under “Apps”, choose your Discourse integration.\n\n10. Click its name at the top, then “Add this app to a channel”\n\n11. Select all the channels which you want Discourse to integrate with\n\n12. Done :tada:\n\n[/details]\n[/quote]","actions_summary":[],"moderator":false,"admin":true,"staff":true,"user_id":127447,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"以防万一，能否请您再次确认一下，您的 Slack 集成目前是否正在使用 Granular Scopes？","truncated":true,"post_url":"/t/chat-integrations-plugin-doesnt-react-on-new-posts/412438/4","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043565,"name":"Terenui","username":"m_terenui","avatar_template":"/user_avatar/meta.discourse.org/m_terenui/{size}/537133_2.png","created_at":"2026-09-24T21:57:08.703Z","cooked":"你好，下午好！
\n我已经升级了我的论坛，现在可以创建并使用新的“看板”（Boards）功能了。
\n这真是太棒了！
\n这里有一个改进建议（当然，这更像是一个“可以考虑的优化”而非“必须实现的功能”）：/boards 页面有一句介绍文字：“创建并管理带有列的看板。” 对于普通“查看者”来说，这句话有点奇怪，因为他们实际上无法创建或管理看板。
\n也许最好只让管理员看到这句介绍文字？或者允许自定义这段文字？
\n此外，我也希望能在 /boards 页面根据各自的使用场景重命名“Boards”这个名称（例如，有些人可能想称之为“路线图”，有些人可能称之为“项目”等）。
\n非常感谢！![\":slight_smile:\"](\"https://emoji.discourse-cdn.com/twitter/slight_smile.png?v=15\" "\\":slight_smile:\\"")
祝好
我使用 AI 来辅助开发我的插件和组件。请自行评估风险使用它们，但我不会为此添加任何免责声明或标签，这与 Discourse 核心代码的做法并无二致。我控制着这些智能体，审查代码（有时会借助另一个智能体或大语言模型来帮忙审阅），并进行测试。你可以选择不使用它们，但我见过更多完全由人类编写的糟糕代码，而不是由 AI 编写的。
","post_number":53,"post_type":1,"posts_count":54,"updated_at":"2026-09-24T21:38:36.859Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":21,"readers_count":20,"score":119.2,"yours":false,"topic_id":412871,"topic_slug":"require-llm-generated-themes-plugins-to-be-tagged-as-such","topic_title":"要求对由 LLM 生成的主题和插件进行相应标注","topic_html_title":"要求对由 LLM 生成的主题和插件进行相应标注","category_id":3,"display_username":"Lillian ","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"i use ai to *assist* me in developing my plugins and components. use them at your own risk but i won’t be labeling them with any disclaimer or tag, no different than Discourse core does. i control the agents, review the code (sometimes with another agent or llm set of eyes to help), and test them. you’re free to not use them, but i’ve more often seen poor code written entirely by a human than by ai.","actions_summary":[{"id":2,"count":5}],"moderator":false,"admin":false,"staff":false,"user_id":127856,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我使用 AI 来辅助开发我的插件和组件。请自行评估风险使用它们，但我不会为此添加任何免责声明或标签，这与 Discourse 核心代码的做法并无二致。我控制着这些智能体，审查代码（有时会借助另一个智能体或大语言模型来帮忙审阅），并进行测试。你可以选择不使用它们，但我见过更多完全由人类编写的糟糕代码，而不是由 AI 编写的。","truncated":true,"post_url":"/t/require-llm-generated-themes-plugins-to-be-tagged-as-such/412871/53","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":5}],"current_user_reaction":null,"reaction_users_count":5,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043539,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-24T21:20:25.917Z","cooked":"分享一篇与此主题相关的精选文章：
\nTrail of Bits 认为，AI 智能体在审计中最有价值的用途是构建自定义工具，而不仅仅是发现漏洞。在对 Miden zkVM 的审计中，他们使用 Claude 和 Codex 创建了一个 LSP 服务器、反编译器、静态分析器以及 Lean 模型，从而发现了一个高严重性的签名伪造漏洞，并通过 95 个 Lean 证明捕获了两个细微问题。
\n由于智能体使得雄心勃勃的副业项目成本更低，审计的经济模式已转向以工具驱动的审查，能够比以往更彻底地保障复杂系统的安全性。
\n\n","post_number":52,"post_type":1,"posts_count":54,"updated_at":"2026-09-24T21:20:25.917Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":20,"readers_count":19,"score":4.0,"yours":false,"topic_id":412871,"topic_slug":"require-llm-generated-themes-plugins-to-be-tagged-as-such","topic_title":"要求对由 LLM 生成的主题和插件进行相应标注","topic_html_title":"要求对由 LLM 生成的主题和插件进行相应标注","category_id":3,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"Just sharing a curated article related to this topic:\n\nTrail of Bits argues AI agents are most useful in audits for building custom tooling, not just finding bugs. In a Miden zkVM audit, they used Claude and Codex to create an LSP server, decompiler, static analyzer, and Lean model, uncovering a high-severity signature-forgery bug and 95 Lean proofs that caught two subtle issues.\n\nBecause agents make ambitious side projects cheap, the economics of audits have shifted toward tool-driven reviews that can secure complex systems far more thoroughly than before.\n\nhttps://blog.trailofbits.com/2026/09/18/auditing-in-the-age-of-good-enough-ai/","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"分享一篇与此主题相关的精选文章： \nTrail of Bits 认为，AI 智能体在审计中最有价值的用途是构建自定义工具，而不仅仅是发现漏洞。在对 Miden zkVM 的审计中，他们使用 Claude 和 Codex 创建了一个 LSP 服务器、反编译器、静态分析器以及 Lean 模型，从而发现了一个高严重性的签名伪造漏洞，并通过 95 个 Lean 证明捕获了两个细微问题。 \n由于智能体使得雄心勃勃的副业项目成本更低，审计的经济模式已转向以工具驱动的审查，能够比以往更彻底地保障复杂系统的安全性。","truncated":true,"post_url":"/t/require-llm-generated-themes-plugins-to-be-tagged-as-such/412871/52","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043531,"name":"agemo","username":"agemo","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/{size}.png","created_at":"2026-09-24T21:11:08.492Z","cooked":"好的，这个实例是基于美国的 DO 云主机。![\":thinking:\"](\"https://emoji.discourse-cdn.com/twitter/thinking.png?v=15\" "\\":thinking:\\"")
我们为 RSS 轮询功能开发了一个小型的配套插件（discourse-rss-onebox）：导入的博客文章会以文章 onebox 的形式渲染，并支持可选的 feed 摘要、YouTube 描述以及标题格式。由于存在三个功能缺口，我们不得不通过包装核心方法来实现，而不是使用已记录的钩子（hooks）。
\nFeed 表单中缺少插件出口（plugin outlet）。 rss-polling-feed-form.gjs#L287-L351 中没有 PluginOutlet，且更新契约（update contract）只接受一组固定的属性（update.rb#L9-L14）。插件无法为每个 feed 添加选项，因此我们的插件需要一个独立的管理页面。如果提供一个出口以及一种持久化额外字段的方式（例如 feed 自定义字段），就能解决这个问题。
Feed ID 从未传递到导入流程中。 轮询任务（poll job）知道 rss_feed_id，但 TopicEmbed.import（poll_feed.rb#L110）和 topic_embed_import_create_args 修饰器（modifier）（topic_embed.rb#L108）从未接收到它。我们包装了轮询任务以捕获该 ID。如果将其作为选项传递下去，插件就可以针对每个 feed 执行操作。
更新路径上缺少钩子。 当 feed 项的内容发生变化时，TopicEmbed.import 会使用 feed 内容修订帖子（topic_embed.rb#L147-L152），从而绕过了创建修饰器所做的任何处理。如果博主编辑了一篇帖子，插件生成的主题格式会被静默地还原为普通的 feed 文本。如果在更新更改时提供一个镜像 topic_embed_import_create_args 的修饰器，就能弥补这一缺陷。
针对第 2 和第 3 点的变通方案是在 TopicEmbed.import 和轮询任务之前插入（prepend）代码。这种做法非常脆弱：main 分支后来为 TopicEmbed.import 添加了一个 truncate: 关键字参数，这破坏了任何镜像 2026.7 版本签名的包装器——我们不得不发布一个版本仅仅是为了传递该参数。如果提供已记录的钩子，就可以避免这类破坏性问题。
我们通过 RSS 轮询将多个 YouTube 频道导入到一个论坛分类中。每个主题都会包含视频 URL，并自动转换为播放器，但视频描述从未出现在帖子中。对于许多视频而言，描述才是真正的内容——例如路线、地点、装备、链接等——会员们经常询问这些信息。
\nYouTube 频道的源是带有 Media RSS 扩展的 Atom 格式，每个条目都在 <media:group><media:description> 中包含完整的描述，以及 <media:thumbnail>。RSS 轮询使用 rss gem（0.3.3 版本，Gemfile.lock#L614）来解析源，该 gem 没有 Media RSS 模块，因此这些元素在 FeedItem 处理之前就被丢弃了，导致 YouTube 条目回退到仅显示 URL（feed_item.rb#L17-L23）。
以下改进会有所帮助：
\nmedia:description（以及 media:thumbnail）。目前，我们通过一个小型配套插件在轮询期间重新读取源 XML 来实现这一功能（discourse-rss-onebox）。它在我们论坛的主题中运行正常，但它依赖于 RSS 轮询的内部实现，如果能在核心功能中实现，会更简单且更稳定。
","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-09-24T21:05:46.257Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":10,"readers_count":9,"score":12.0,"yours":false,"topic_id":413281,"topic_slug":"rss-polling-read-the-video-description-from-youtube-channel-feeds","topic_title":"RSS 轮询：从 YouTube 频道源读取视频描述","topic_html_title":"RSS 轮询：从 YouTube 频道源读取视频描述","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"We import several YouTube channels into a forum category with RSS Polling. Each topic gets the video URL, which oneboxes into the player, but the video's description never makes it into the post. For many videos the description is the actual content - route, location, gear, links - and members ask for it.\n\nYouTube channel feeds are Atom with Media RSS extensions, and every entry carries the full description in `Top users by posts and likes received:
\nExperimental user sidebar navigation — Awesomerobot shared an upcoming change that gives user profiles a collapsible sidebar with filtering, and admins can enable it for everyone or specific groups via /admin/config/upcoming-changes read more.
Voice: Discord-style voice and video rooms — Putty reported 404s when inviting other users, and Pmusaraj traced the issue to periods in usernames with a core PR fix; Falco is on vacation, so Voice invitation debugging will resume next month read more.
\nDiscourse core now includes Markdown endpoints for topic lists and views — Pmusaraj explained which lists are supported, including /latest.md, /hot.md, category lists, and tag lists, and warned that Cloudflare’s Markdown-for-Agents feature may override Discourse’s native .md responses read more.
Easier account signup using email codes — Rishabh confirmed that random username generation is no longer enabled by default, while Ecki raised privacy/data-protection concerns and Pmusaraj defended email codes as more secure than magic links read more.
\nHow TurboRenault Moved 20,000 Members from XenForo to Discourse — Andrew_Bond's migration story was published on the blog, and he said his only regret is not making the switch sooner read more.
\nIntroducing Discourse Workflows — The blog announced Workflows for automating repetitive community-management overhead, now bundled with Discourse core; you can also follow the Discourse Workflows plugin topic for ongoing discussion read more.
\nWhere is the Version — Ecki couldn’t find the Discourse version number in the new admin dashboard; Andrew_Bond and Mcwumbly pointed to the System section, which arrived as part of the redesigned admin dashboard, while Moin explained that ESR builds must wait until the next ESR release for feature fixes read more.
\nFlags can’t be edited, even if they’ve never been used — Mbauman reported that unused custom flags still can’t be edited; Awesomerobot confirmed an ID collision and linked to a fix.
\nHow to stop users from editing topic titles — Rlauriston asked how to prevent non-admins from renaming topics they didn’t create; HAWK and Rubi clarified that TL3+ users can edit titles and pointed to the Trust Level Permissions Reference read more.
\nFeature request: respect “Hide my public profile” user pref — Tobiaseigen wants hidden users to stay out of the user directory and Who’s Online; Moin suggested staged users and noted that hiding a profile isn’t the same as hiding an account’s existence read more.
\nAllow admins to decide what (not) to automatically translate — Gryzor requested an option to skip tag-based translation, or to ignore tags entirely; Nat moved the discussion into a dedicated feature request and flagged recent tag-translation improvements read more.
\nAllow only specified groups to access and submit a workflow form — MachineScholar proposed group-based access for Workflow forms, and Kamal_S outlined key implementation considerations around discovery, direct URLs, group membership changes, and backend permission checks read more.
\n/admin/plugins/:plugin_id and the fingerprint plugin’s admin route, then submitted a PR that Zogstrip reviewed and merged read more.Ballotage – secret black/white-ball ballots — DaniW42 released a plugin for secret club ballots, with voting and management pages, participation oversight, and counters designed to keep votes anonymous read more.
\nDiscourse Boards — Mid shared detailed feedback on the new Boards feature, including syncing assignment statuses with board columns, auto-adding topics by tag or category, and using Boards for incoming feedback triage read more.
\nAwesomerobot was especially active: launching the experimental user sidebar navigation, confirming a flags editing bug fix, explaining the sidebar scroll restoration on the Categories page, and sharing that an AI Q&A homepage feature is being considered.
\nAwesomerobot also let the community know that Tgxworld has a fix on the way for pressing Enter after triggering quick search when AI search is set as default read more.
\nPmusaraj helped with the Voice room invitation 404, answered detailed questions about Markdown endpoints, and explained the security rationale behind email-code signups.
\nZogstrip reviewed and merged the fingerprint plugin route fix and confirmed a fix for extra spaces in topic summaries sent to LLMs.
\nNatalie T (Nat) moved the automatic translation tag feature request into its own topic and noted that the tag translator was improved earlier this month, as discussed in the AI tag translations topic.
\nFalco noted in the Voice announcement that Voice room invitation debugging will be picked back up after vacation.
\nChapoi pushed back on manually reviewing every third-party plugin in the LLM-generated plugins discussion, saying that isn’t a viable approach for the team.
\nTgxworld is working through a fix for Voice badges reappearing after every update.
\nMcwumbly helped surface the System section in the redesigned admin dashboard, where self-hosters can once again find their Discourse version.
\nYesterday brought everything from secret ballots and luxury member clubs to a brand-new sidebar and a Voice room full of friendly ghosts — just another day on Meta! ![\":rocket:\"](\"https://emoji.discourse-cdn.com/twitter/rocket.png?v=15\" "\\":rocket:\\"")
这是针对 RSS 轮询可能需要 20 分钟或更长时间才能处理一个订阅源 以及 #43645 的后续讨论，该 PR 通过将轮询作业切换到 post.previously_new_record? 来停止将未更改的项目计为已导入（poll_feed.rb#L132）。
该修复留下了状态的另一半问题：一个已经导入且未更改的项目现在会在每次轮询时被报告为“Updated the existing topic”（更新了现有主题），因为无论 TopicEmbed.import 是否修改了任何内容，它都会返回其现有的帖子，而状态逻辑是 previously_new_record? ? :imported : :updated。
我们在 2026.7.3 ESR 版本中看到了相同的标签（在该版本中是由旧检查加上 rss_polling_use_pubdate 引起的），并且通过阅读 6ba633db 处的 main 分支代码，它似乎仍然存在；我尚未运行 main 分支以确认。
复现步骤
\n实际结果： 每个项目都显示“Updated the existing topic”（更新了现有主题）。
\n预期结果： 未更改的项目应报告为未更改（或跳过），只有当帖子确实被修改时，才显示“Updated”（已更新）。
\nTopicEmbed.import 已经计算了是否有变化（topic_embed.rb#L140-L153 中的 content_changed、title_changed、tags_changed）；将该结果暴露给轮询作业将使状态准确。
非常感谢！这样就可以了。标签必须对用户可见，所以我得想一个有意义的名称。
","post_number":4,"post_type":1,"posts_count":5,"updated_at":"2026-09-24T20:16:12.948Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":20,"readers_count":19,"score":14.0,"yours":false,"topic_id":413259,"topic_slug":"is-there-a-way-to-suppress-the-me-too-button-on-a-specific-topic","topic_title":"有没有办法在特定主题中隐藏“我也一样”按钮？","topic_html_title":"有没有办法在特定主题中隐藏“我也一样”按钮？","category_id":2,"display_username":"Tobias Eigen","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"Thanks much! That works. The tag has to be visible to the user so had to make up one that makes sense.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":8571,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"非常感谢！这样就可以了。标签必须对用户可见，所以我得想一个有意义的名称。","truncated":true,"post_url":"/t/is-there-a-way-to-suppress-the-me-too-button-on-a-specific-topic/413259/4","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043423,"name":"putty","username":"putty","avatar_template":"/user_avatar/meta.discourse.org/putty/{size}/370902_2.png","created_at":"2026-09-24T19:20:17.671Z","cooked":"如果存在（隐藏的）标签时将其隐藏，会怎样？
\nbody.tag-YOUR-TAG-HERE .post-action-menu__solved-shared-issue {\n display: none;\n}\n| \n | \n | \n |
|---|---|---|
![\":information_source:\"](\"https://emoji.discourse-cdn.com/twitter/information_source.png?v=15\" "\\":information_source:\\"") | \n摘要 | \n针对特定成员组的秘密黑白球投票（“ballotage”），并支持参与情况监督。 | \n
![\":hammer_and_wrench:\"](\"https://emoji.discourse-cdn.com/twitter/hammer_and_wrench.png?v=15\" "\\":hammer_and_wrench:\\"") | \n仓库链接 | \nGitHub - DaniW42/discourse-ballotage: A Discourse plugin for secret black/white-ball ballots (\"ballotage\" — in German \"Kugelung\"), as used by clubs, societies and other membership organizations for admitting new members. A member either casts a black or a white ball; who voted is recorded, but what they voted is not. · GitHub | \n
![\":open_book:\"](\"https://emoji.discourse-cdn.com/twitter/open_book.png?v=15\" "\\":open_book:\\"") | \n安装指南 | \n如何在 Discourse 中安装插件 | \n
这属于比较小众的功能……但是：许多俱乐部、协会和会所通过黑白球秘密投票来接纳新成员。此插件将该流程引入 Discourse：
\n/ballotage 的投票页面，配置好的组成员可在设定时间段内（默认为开始日 00:01 至结束日 23:59，可选自定义时间）投出最终一票——黑球或白球。/ballotage/manage 的管理页面，供监督组和管理员使用：在投票进行期间查看谁已投票，投票结束后查看黑白球结果。![\"投票页面\"](\"https://global.discourse-cdn.com/meta/original/4X/f/2/d/f2dd058a544191fc300bcd4ef16d04fcf8c0e894.png\")
![\"结束后的管理页面\"](\"https://global.discourse-cdn.com/meta/original/4X/e/4/5/e4509ed107ad2e945feaaac07c28b6697d070fcc.png\")
updated_at 字段。局限性：如果有人拥有直接数据库访问权限，并在投票进行期间监视计数器，仍有可能关联投票。这超出了插件的能力范围，需要通过组织层面的措施来处理。
\n| 设置 | \n描述 | \n
|---|---|
ballotage_enabled | \n启用插件 | \n
ballotage_voting_group | \n允许投票的组 | \n
ballotage_oversight_group | \n可查看参与情况和结果的组（管理员始终可以） | \n
ballotage_oversight_can_manage | \n允许监督组创建、取消、定稿和删除投票 | \n
ballotage_info_text | \n显示在投票页面上的可选通知文本 | \n
ballotage_timezone | \n开始/结束时间的时区（默认 Europe/Berlin） | \n
在侧边栏或菜单中添加指向 /ballotage 的链接，以便成员找到投票页面。
Discourse 2026.7 及更高版本。自 2026 年 9 月起已在小型论坛的生产环境中运行。
\n欢迎反馈、错误报告及翻译——请在此处或 GitHub 上提出。
","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-09-24T18:29:17.192Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":3,"reads":27,"readers_count":26,"score":95.4,"yours":false,"topic_id":413266,"topic_slug":"ballotage-secret-black-white-ball-ballots","topic_title":"Ballotage – 秘密黑白球投票","topic_html_title":"Ballotage – 秘密黑白球投票","category_id":22,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":2,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Plugin Author","title_is_group":false,"bookmarked":false,"raw":"| | | |\n|----|----|----|\n| :information_source: | **Summary** | Secret black/white-ball ballots (\"ballotage\") for a member group, with participation oversight. |\n| :hammer_and_wrench: | **Repository Link** | https://github.com/DaniW42/discourse-ballotage |\n| :open_book: | **Install Guide** | [How to install plugins in Discourse](https://meta.discourse.org/t/install-plugins-in-discourse/19157) |\n\n我一直认为，让正文针对每个主题拥有动态的 CSS 样式会很有价值，就像群组和特定页面那样。
","post_number":2,"post_type":1,"posts_count":5,"updated_at":"2026-09-24T18:21:36.655Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":25,"readers_count":24,"score":10.0,"yours":false,"topic_id":413259,"topic_slug":"is-there-a-way-to-suppress-the-me-too-button-on-a-specific-topic","topic_title":"有没有办法在特定主题中隐藏“我也一样”按钮？","topic_html_title":"有没有办法在特定主题中隐藏“我也一样”按钮？","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"I always thought it would be valuable that body have dynamic CSS style for each topic, as is the case with groups and specific pages.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我一直认为，让正文针对每个主题拥有动态的 CSS 样式会很有价值，就像群组和特定页面那样。","truncated":true,"post_url":"/t/is-there-a-way-to-suppress-the-me-too-button-on-a-specific-topic/413259/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043383,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-24T18:07:31.086Z","cooked":"\n谢谢，我之前在一个按类别和标签过滤的主题列表中尝试过，但没起作用，所以有点困惑。我测试时总爱选些不合适的例子。
\n为什么你包含了 /new 和 /unread，却没有包含 /unseen？
","post_number":10,"post_type":1,"posts_count":11,"updated_at":"2026-09-24T18:08:44.202Z","reply_count":0,"reply_to_post_number":6,"quote_count":1,"incoming_link_count":0,"reads":20,"readers_count":19,"score":49.0,"yours":false,"topic_id":413006,"topic_slug":"discourse-core-now-includes-markdown-endpoints-for-topic-lists-and-views","topic_title":"Discourse 核心现已包含用于主题列表和视图的 Markdown 端点","topic_html_title":"Discourse 核心现已包含用于主题列表和视图的 Markdown 端点","category_id":67,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Kluges Köpfchen","title_is_group":false,"bookmarked":false,"raw":"[quote=\"pmusaraj, post:6, topic:413006\"]\nCurrently, the following:\n[/quote]\n\nThanks, I was confused because I first tried on a topic list filtered for a category and a tag and it didn't work. I tend to choose bad examples for testing.\n\nWhy did you include /new and /unread but not /unseen?","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":95552,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"谢谢，我之前在一个按类别和标签过滤的主题列表中尝试过，但没起作用，所以有点困惑。我测试时总爱选些不合适的例子。 \n为什么你包含了 /new 和 /unread，却没有包含 /unseen？","truncated":true,"post_url":"/t/discourse-core-now-includes-markdown-endpoints-for-topic-lists-and-views/413006/10","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"+1","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043366,"name":"Kenjura","username":"kenjura","avatar_template":"/user_avatar/meta.discourse.org/kenjura/{size}/578908_2.png","created_at":"2026-09-24T17:49:43.571Z","cooked":"（帖子已被作者删除）
","post_number":47,"post_type":1,"posts_count":47,"updated_at":"2026-09-24T18:05:10.381Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":4,"readers_count":3,"score":0.6,"yours":false,"topic_id":357665,"topic_slug":"pyxs-modern-theme","topic_title":"Pyx 的现代主题","topic_html_title":"Pyx 的现代主题","category_id":61,"display_username":"Kenjura","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":2,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"(post deleted by author)","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":203943,"hidden":false,"trust_level":0,"deleted_at":null,"user_deleted":true,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"（帖子已被作者删除）","truncated":true,"post_url":"/t/pyxs-modern-theme/357665/47","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043355,"name":"Tobias Eigen","username":"tobiaseigen","avatar_template":"/user_avatar/meta.discourse.org/tobiaseigen/{size}/539204_2.png","created_at":"2026-09-24T17:33:54.138Z","cooked":"我希望能够在支持分类中添加一些说明性/欢迎主题，这些主题上不需要显示“我也遇到了”按钮。此外，“关于此分类”页面也不应显示“我也遇到了”按钮，我看到它确实没有显示，这很好！是否有某种 Markdown 技巧或管理操作可以针对特定主题隐藏该按钮？
","post_number":1,"post_type":1,"posts_count":5,"updated_at":"2026-09-24T18:09:17.553Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":26,"readers_count":25,"score":30.2,"yours":false,"topic_id":413259,"topic_slug":"is-there-a-way-to-suppress-the-me-too-button-on-a-specific-topic","topic_title":"有没有办法在特定主题中隐藏“我也一样”按钮？","topic_html_title":"有没有办法在特定主题中隐藏“我也一样”按钮？","category_id":2,"display_username":"Tobias Eigen","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":2,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"I'd like to be able to add a few explanatory/welcome topics to a support category that do not have the \"Me too\" button on them. Also the \"About this category\" should not have a \"Me too\" button and I see it is not shown, which is great! Is there some markdown magic or admin action to suppress it on a specific topic?","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":8571,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我希望能够在支持分类中添加一些说明性/欢迎主题，这些主题上不需要显示“我也遇到了”按钮。此外，“关于此分类”页面也不应显示“我也遇到了”按钮，我看到它确实没有显示，这很好！是否有某种 Markdown 技巧或管理操作可以针对特定主题隐藏该按钮？","truncated":true,"post_url":"/t/is-there-a-way-to-suppress-the-me-too-button-on-a-specific-topic/413259/1","locale":"en","is_localized":true,"language":"en","localization_outdated":true,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[{"id":"+1","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":true},{"id":2043351,"name":"Sammy","username":"eisammy","avatar_template":"/user_avatar/meta.discourse.org/eisammy/{size}/528804_2.png","created_at":"2026-09-24T17:27:37.530Z","cooked":"感谢提供指引，以下是关于此问题的回复：
\n\n\n\n
\n- \n
X-Discourse-Route: topics/show：显示处理该话题的 Discourse（Ruby on Rails）内部控制器/操作。- \n
X-Runtime: 0.133969：应用生成响应所花费的时间（约 133 毫秒）。- \n
Cf-Ray: ...-GRU：请求由位于圣保罗瓜鲁柳斯（Guarulhos/São Paulo，代码GRU）的 Cloudflare 边缘节点处理。- \n
Cf-Cache-Status: DYNAMIC和Cache-Control: no-cache, no-store：动态内容，不会滞留在边缘缓存中。- 检查不带
\n.json的常规 HTML URL 时，服务器返回：\n\n
\n- \n
Link: <https://segredin.com/t/conselhos-duvidosos/22054.md>; rel=\"alternate\"; type=\"text/markdown\"- \n
X-Discourse-Crawler-View: true（表明 Discourse 也为爬虫和阅读器提供了原生.md/ Markdown 格式的干净版本）。
指示替代版本的 Link 头部：Link: <https://segredin.com/t/conselhos-duvidosos/22054.md>; rel=\"alternate\"; type=\"text/markdown\"
无论 DNS 层面的外部功能如何，源站都会返回 Vary: Accept。
如果请求选择不带 .json 后缀，它将默认返回 .md 作为转换结果。
HTTP/1.1 200 OK\nContent-Type: text/markdown\nVary: Accept\n我有些疑惑，因为我收到了来自 Claude 的 12.3 万个请求，而且自从我使用核心功能更新 Discourse 以来，大多数请求量并没有呈指数级增长。我将在未来几周内继续监控。
","post_number":9,"post_type":1,"posts_count":11,"updated_at":"2026-09-24T17:27:37.530Z","reply_count":0,"reply_to_post_number":8,"quote_count":0,"incoming_link_count":0,"reads":21,"readers_count":20,"score":4.2,"yours":false,"topic_id":413006,"topic_slug":"discourse-core-now-includes-markdown-endpoints-for-topic-lists-and-views","topic_title":"Discourse 核心现已包含用于主题列表和视图的 Markdown 端点","topic_html_title":"Discourse 核心现已包含用于主题列表和视图的 Markdown 端点","category_id":67,"display_username":"Sammy","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Bug Reporter","title_is_group":false,"reply_to_user":{"id":21029,"username":"pmusaraj","name":"Penar Musaraj","avatar_template":"/user_avatar/meta.discourse.org/pmusaraj/{size}/119489_2.png"},"bookmarked":false,"raw":"Obrigado pelo norte, fica aqui a resposta sobre isso:\n\n> * **`X-Discourse-Route: topics/show`**: Mostra a controller/action interna do Discourse (Ruby on Rails) processando o tópico.\n> * **`X-Runtime: 0.133969`**: Tempo que a aplicação levou para gerar a resposta (cerca de ~133ms).\n> * **`Cf-Ray: ...-GRU`**: Requisição atendida pelo edge da Cloudflare em Guarulhos/São Paulo (`GRU`).\n> * **`Cf-Cache-Status: DYNAMIC`** e **`Cache-Control: no-cache, no-store`**: Conteúdo dinâmico que não fica estagnado em cache de borda.\n> * Ao inspecionar a URL HTML comum sem `.json`, o servidor responde com:\n> * `Link:我不太确定，最简单的办法是在一个实时网站上进行测试，并将其输出结果与 meta 的输出进行对比。两者所包含的内容会有所不同。如果你得到的响应在启用或未启用 Cloudflare 功能时完全相同，那么说明它确实遵循了 Discourse 核心返回的 Markdown。
","post_number":8,"post_type":1,"posts_count":11,"updated_at":"2026-09-24T17:15:19.397Z","reply_count":1,"reply_to_post_number":7,"quote_count":0,"incoming_link_count":1,"reads":22,"readers_count":21,"score":29.4,"yours":false,"topic_id":413006,"topic_slug":"discourse-core-now-includes-markdown-endpoints-for-topic-lists-and-views","topic_title":"Discourse 核心现已包含用于主题列表和视图的 Markdown 端点","topic_html_title":"Discourse 核心现已包含用于主题列表和视图的 Markdown 端点","category_id":67,"display_username":"Penar Musaraj","primary_group_name":"team","flair_name":"team","flair_url":"https://global.discourse-cdn.com/meta/original/3X/e/b/ebee30bd98aef20357e4a177a5a1e45b877ce088.svg","flair_bg_color":"","flair_color":"111","flair_group_id":47,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"team","title_is_group":true,"reply_to_user":{"id":146973,"username":"eisammy","name":"Sammy","avatar_template":"/user_avatar/meta.discourse.org/eisammy/{size}/528804_2.png"},"bookmarked":false,"raw":"I don't know for sure, easiest option is to test on a live site and compare the output with what meta outputs. There will be differences in what content is included. If the response you get is the same with or without Cloudflare's feature, then it is respecting the Markdown returned by Discourse core.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":true,"staff":true,"user_id":21029,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"我不太确定，最简单的办法是在一个实时网站上进行测试，并将其输出结果与 meta 的输出进行对比。两者所包含的内容会有所不同。如果你得到的响应在启用或未启用 Cloudflare 功能时完全相同，那么说明它确实遵循了 Discourse 核心返回的 Markdown。","truncated":true,"post_url":"/t/discourse-core-now-includes-markdown-endpoints-for-topic-lists-and-views/413006/8","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"+1","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2043341,"name":"Sammy","username":"eisammy","avatar_template":"/user_avatar/meta.discourse.org/eisammy/{size}/528804_2.png","created_at":"2026-09-24T17:13:08.523Z","cooked":"如果启用了，应该会覆盖吧？我在他们的博客里没找到任何关于他们是否阻止源站自行发送该标头的信息。
","post_number":7,"post_type":1,"posts_count":11,"updated_at":"2026-09-24T17:13:08.523Z","reply_count":1,"reply_to_post_number":6,"quote_count":0,"incoming_link_count":0,"reads":22,"readers_count":21,"score":9.4,"yours":false,"topic_id":413006,"topic_slug":"discourse-core-now-includes-markdown-endpoints-for-topic-lists-and-views","topic_title":"Discourse 核心现已包含用于主题列表和视图的 Markdown 端点","topic_html_title":"Discourse 核心现已包含用于主题列表和视图的 Markdown 端点","category_id":67,"display_username":"Sammy","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Bug Reporter","title_is_group":false,"reply_to_user":{"id":21029,"username":"pmusaraj","name":"Penar Musaraj","avatar_template":"/user_avatar/meta.discourse.org/pmusaraj/{size}/119489_2.png"},"bookmarked":false,"raw":"Sobrescreveria se estiver habilitado, certo? Não achei no blog deles nenhuma informação sobre se eles impedem que a própria origem sirva esse cabeçalho.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":146973,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"如果启用了，应该会覆盖吧？我在他们的博客里没找到任何关于他们是否阻止源站自行发送该标头的信息。","truncated":true,"post_url":"/t/discourse-core-now-includes-markdown-endpoints-for-topic-lists-and-views/413006/7","locale":"pt_BR","is_localized":true,"language":"pt_BR","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null}]}