每周总结

新闻和活动 论坛摘要
114

This week on meta.discourse.org…

Key Stats

Reporting window: 2026-03-08 → 2026-03-15, as reflected across active threads like the FAQ/Guidelines housekeeping discussion (read more) and late-week UX/browser reports (read more).

  • Total new posts: 426
  • Total new topics: 72

Top users (posts + likes in the last 7 days)

User Posts Likes Recent reference
Falco 24 50 Cloudflare IP bans explanation (read more)
ToddZ 23 37 Theme-component solution for /groups intro text (read more)
Canapin 16 30 “How old is your forum?” community thread (read more)
LotusJeff 9 29 “How old is your forum?” opener + history (read more)
nat 9 20 Badge i18n deep dive + console workaround (read more)
sam 7 19 OpenAI/Azure “service tiers” announcement (ai, #Announcements) (read more)
awesomerobot 12 17 Form templates multi-template bug + fix guidance (read more)
NateDhaliwal 19 16 “Quick start” self-host install guidance (read more)
merefield 9 15 Dashboard traffic-graph scaling feedback (read more)
Danielle 3 14 Webinar announcement: moderator programs (read more)

Interesting Topics

#Announcements

  • Discourse AI got OpenAI/Azure “service tier” selection, letting admins trade off cost vs latency vs reliability in provider settings (ai, #Announcements) — read more

  • A new webinar was announced: “Creating & Nurturing a Moderator Program” (with a promised replay for registrants) (webinar, #Announcements) — read more

  • Hosted AI capacity limits were increased significantly (plus model + throughput improvements), with updated quotas reflected on the pricing page (ai, #Announcements) — read more

blog

  • The Discourse team published a detailed write-up on the Upcoming Changes system and how it supports gradual rollouts across varied site configurations (blog) — read more

#Community Building

  • A fun and insightful thread asked: “How old is your forum?”—prompting migration histories from Yahoo Groups, phpBB, Ning, vBulletin, and more (#Community Building) — read more

  • Cross-platform community ops came up again in a “WhatsApp challenges” follow-up: one practical pattern was capturing key takeaways from chat groups into a shared Discourse category (#Community Building) — read more

  • Meta’s evergreen “Discourse is great” energy continued, with community members sharing milestones and encouragement (#Praise) — read more

Support

  • A tricky edge case: after merging topics, one post could no longer be marked as the Solved answer—eventually traced to an existing solved record in the original topic and manually repaired, with a fix planned (solved, Support) — read more

  • Multilingual admins asked how to localize custom badges and groups; the key takeaway: seeded badges are i18n’d, but custom badges need translation overrides (currently console-dependent) (translation, badges, Support) — read more

  • A “forum acquisition” question explored how to bring topics from one Discourse into another without full restore, pointing back to established migration workflows (Support) — read more

  • A clean, low-code customization request: adding explanatory text above /g (groups index) was solved with a tiny theme component using After Header + CSS gating (groups, Support) — read more

  • Moderator capability boundaries surfaced: moderators can delete users, so the recommended approach for tighter control was Category Moderators + per-category moderator groups (Support) — read more

  • A self-hosting anxiety post (“install on my VPS”) turned into a practical mini-guide: one-line installer, backup mindset, and hosted-vs-self-host tradeoffs (#Self-hosting, Support) — read more

  • A Onebox/OpenGraph failure that worked on Meta but not on the user’s site ended up being a certificate chain / server-side fetch trust issue, reinforcing that Onebox generation is server-side and sensitive to TLS setup (onebox, Support) — read more

  • Admins trying to “require TOS acceptance” used a clever workaround: a required custom user field checkbox to gate saving profile/preferences (Support) — read more

bug

  • A dashboard UX/data issue: the Site Traffic graph becomes unhelpful when crawlers dominate, prompting a request for smarter scaling or a “rescale” control (dashboard-reports, bug) — read more

  • A content-localization bug: localized tag names weren’t being cleaned/slugified, breaking body classes and tag display; a fix plus migration shipped (content-localization, bug) — read more

  • Form Templates: selecting multiple templates per category didn’t persist after refresh due to missing save behavior in a simplified category-creation flow; workaround + merged fix provided (form-templates, bug) — read more

  • Discourse v2026.3.0 upgrade pain: discourse-subscriptions failed boot due to a route constant load-order/deprecation edge case; a core PR removed the deprecation point (subscriptions, bug) — read more

  • A scary report: using topic timers + schedule publishing in a draft with a missing destination category could spiral into a heavy, “catastrophic” UI state (topic-timers, bug) — read more

ux

  • Mobile composer toolbar: when too many buttons exist (often from theme components), later buttons can look “missing”; discussion turned to whether scroll affordances (like arrows) should appear on touch devices (composer, ux) — read more

  • On some tablets/browsers, the floating search widget produced bizarre input behavior (reversed character order), eventually linked to a floating keyboard feature (search, Support) — read more

  • A login-page polish issue: top logo alignment shifts when language switcher or theme toggle is present (login, ux) — read more

#Plugin / #Theme component

  • A notable new plugin: diskuz Call brings peer-to-peer voice/video calls into Discourse using WebRTC (signaling on server, media P2P/TURN) (#Plugin) — read more

  • Another plugin showcase: a Discourse Points Mall prototype (check-in, shop, orders, ledger) with candid notes about current bugs and readiness (#Plugin) — read more

  • A theme-component tooling thread: Tag Style Tool shipped updates quickly after reports of disappearing UI and Font Awesome SVG subset quirks (tags, #Theme component) — read more

  • A no-rebuild alternative to server plugins: Bilibili inline player as a theme component, compared against an existing rebuild-required plugin approach (onebox, #Theme component) — read more

  • “Banner Featured Links” got an update to address htmlSafe deprecation and other cleanup, pinned to 2026.3.0-latest (#Theme component) — read more

  • The terminal-based Discourse client “termcourse” added MessageBus-powered realtime notifications and began aligning shortcut conventions (experimental, #Extras) — read more

Activity by the @team Group

  • Falco focused on practical admin fixes and roadmap notes: explained Cloudflare “everyone got banned” IP behavior and the need for the Cloudflare template (read more), confirmed work on a new UI to display full “and N more…” reactions lists (read more), clarified Data Explorer API behavior changes and limits/pagination guidance (read more), expanded hosted LLM capacity limits and model capabilities (read more), and outlined replacements for Google’s discontinued Custom Search integration plus future “native web search tools” support (read more).

  • nat delivered several “deep internals” clarifications and fixes: corrected the realities of i18n for custom badges and provided the console-based TranslationOverride approach (read more), investigated localized tag output and shipped a cleanup fix + migration (read more), responded to dashboard traffic-graph scaling feedback with “changes coming” context (read more), and pointed users to the experimental tag settings page for managing translated tags after AI translation (read more).

  • sam shipped and discussed multiple AI/automation developer-facing improvements: announced OpenAI/Azure provider service tiers and how to configure them in LLM settings (read more), advanced the “automation pipelines” idea (trigger → filters → actions, observability, extensibility) (read more), responded to upgrade issues around USERNAME_ROUTE_FORMAT with a core PR to remove the deprecation pressure point (read more), and continued triage on AI Search resource usage expectations vs unexpected CPU pressure (read more).

  • awesomerobot handled a broad spread of admin UX + bug triage: reproduced and confirmed the multi-form-template persistence bug, suggested a workaround, and followed with a merged fix (read more); investigated toolbar overflow behavior and the “hidden arrow on touch devices” tradeoff (read more); identified a third-party plugin causing “official” components to fail after update and offered safe-mode isolation steps (read more); and suggested structured approaches for gating access via guidelines acceptance using Policy + Automation patterns (read more).

  • Danielle coordinated community-facing updates: announced the moderator-program webinar and confirmed recordings will be shared after the session (read more), and helped steer a process for reviewing/updating older FAQ/Guidelines documentation references (read more).

  • supermathie provided crisp diagnostics and user-expectation improvements: tested problematic mobile browsers for text-selection UI issues and concluded the most viable path is recommending supported browsers (read more), documented a temporary email regression caused by a gem update (with break/fix commits) for anyone impacted that day (read more), and proposed a UX hint for multisite “guest” admins who can’t access /sidekiq to reduce confusion (read more).

  • chapoi engaged on UX polish and dashboard/report behavior: clarified the intent behind the site-traffic Y-axis behavior and agreed it should be smarter in crawler-heavy scenarios (read more), pointed developers to Discourse docs being included directly in the core repo (read more), and confirmed a tablet TOC overlay bug should be fixed by an upstream DiscoTOC PR (read more).

  • martin worked on both production troubleshooting and product communication: diagnosed why “mark as solution” can fail after merges (a prior solved record in the old topic) and applied a fix while investigating a preventative change (read more), and published the companion discussion topic for the “Upcoming Changes system” blog post (read more).

  • HAWK kicked off a cleanup thread about FAQ/Guidelines link confusion, which quickly evolved into a documentation and process review effort (read more).

  • pmusaraj supported Discourse ID troubleshooting: requested backtraces for “can’t alloc thread” signup failures and helped narrow suspicion toward memory constraints / reproducibility via fresh installs (read more), and offered direct cleanup of duplicate redirect-URI credentials as a temporary fix while workflow improvements are in progress (read more).

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

115

This week on meta.discourse.org…

A busy week on Meta (2026-03-15 → 2026-03-22), with lots of energy around experimental UX (nested replies), developer-facing changes (plugin build tooling + deprecations), and a steady stream of admin/support troubleshooting across hosting, auth, and calendars (see the mega test thread: read more).

Key Stats

  • New posts: 644
  • New topics: 82

Most active / most appreciated users (posts + likes received this week):

User Posts Likes
Moin 62 108
Falco 30 111
chapoi 21 33
NateDhaliwal 27 21
darkpixlz 16 29
Lilly 14 44
david 13 60
merefield 13 24
martin 6 27
Canapin 10 44

Conversation drivers worth noting (with sources):

Interesting Topics

#Announcements

Dev

ux

#Site feedback

Support (and #Self-hosting)

#Nested Replies Testing

  • Discourse shipped a very experimental nested/threaded topic view plugin for testing, explicitly framed as feedback-on-feel rather than bug reporting: Testing Nested Replies on Meta.

  • To reduce “where did the other posts go?” confusion once deep nesting triggers a detached “context view,” a UI clarity pass was proposed and demoed in UX improvements for deeply nested thread view.

#Plugins / #Theme component / #Extras

#Feature

bug

Activity by the @team Group

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

1 个赞
116

本周 meta.discourse.org 动态…

关键数据

在过去 7 天的讨论和修复中（例如 v2026.3.0-latest.1 安全修复讨论 和 发布站点反馈）：

  • 新增帖子总数： 502
  • 新增话题总数： 68

本周活跃用户（发帖数 / 获得点赞数）

  • Moin — 34 篇帖子 / 75 个赞 — 协助分类了诸如话题投票标签标点符号问题（阅读更多），并阐明了删除后的上传清理行为（阅读更多）。

  • david — 20 篇帖子 / 70 个赞 — 就发布可见性和 Meta 公告进行了回应（阅读更多），修复了停滞的“新版本邮件”问题（阅读更多），并迭代了发布站点（RSS + 样式反馈循环）（阅读更多）。

  • Falco — 12 篇帖子 / 55 个赞 — 解释了安全修复浪潮的背景（阅读更多），推动了 Patreon API v2 升级（阅读更多），并讨论了 Discourse AI 的私信翻译目标（阅读更多）。

  • zogstrip — 12 篇帖子 / 29 个赞 — 安排了一系列修复，包括表情符号别名验证（阅读更多）以及审核/队列用户体验改进（阅读更多）。

  • merefield — 12 篇帖子 / 28 个赞 — 对“数据库残留清理”插件提供了深思熟虑的风险分析（阅读更多），并推动了隐私/链接获取的可维护解决方案（阅读更多）。

  • R23D_Printing — 21 篇帖子 / 28 个赞 — 快速迭代了 Discourse Challenges，增加了周期间隔和版主访问权限，随后推出了基于私信的 ChallengeBot（阅读更多）。

  • awesomerobot — 9 篇帖子 / 27 个赞 — 修复了如话题投票标点符号等 UI 回归问题（阅读更多），并针对 about.json 提出了 API 权限改进方案（阅读更多）。

  • darkpixlz — 19 篇帖子 / 25 个赞 — 协助调试了 CDN/CORS 插件故障（阅读更多），并正确地反对隐藏“大红”主题故障横幅（阅读更多）。

  • RGJ — 8 篇帖子 / 20 个赞 — 清晰地解释了永久删除后上传文件何时被清除（阅读更多），并建议了更安全的链接获取/隐私代理方案（阅读更多）。

  • nathank — 16 篇帖子 / 20 个赞 — 提供了实用的管理员指导（例如关于页面的群组可见性）（阅读更多），并探索了围绕事件和呼叫的功能/工作流方案（阅读更多）。

有趣的话题

支持

  • Ed_S 对 “隐蔽”发布 表示担忧，并请求将发布帖子重新归类为公告；david 承认了这一痛点，并表示团队正在讨论如何在 Meta 上提供更好的指引（阅读更多）。

  • 关于 releases.discourse.org 可用性 的专题讨论中，发布消费方面的困惑持续存在，用户请求 RSS 和更好的可读性——结果 RSS 订阅源迅速上线（阅读更多）。

  • 托管免费计划注册流程遇到了“已配置站点过多”的错误；HAWK 和 pedro 立即介入调查并确认输入（阅读更多）。

  • 自托管用户在调试 Discourse ID 时学到了硬性要求：如果您的站点告诉 Discourse ID 重定向 URI 不是 HTTPS，则需要更正 force_https / 代理头——讨论中涉及了常见的反向代理误解（阅读更多）。

  • 一个实用的支持线程询问如何在 /about 页面移除版主而不移除群组；简单的“隐藏群组”方法（以及可选的动态群组）解决了问题（阅读更多）。

  • 关于“大红横幅”的问题变成了一个提醒：主题故障警报故意设计得很醒目，正确的做法是解决组件问题，而不是隐藏警告（阅读更多）。

  • 一位管理员询问如何将横幅/图像移动到 最 顶部——回答强调最好通过小型主题组件/CSS 调整来完成，而不是篡改标记（阅读更多）。

bug

  • 一个长期存在的烦恼——没有“新版本可用”邮件——被追溯到 redis gem 的变更，并已通过核心 PR 修复了该故障作业（阅读更多）。

  • iPhone 上 Facebook 应用内浏览器中出现的“看起来像纯 HTML”的尖锐问题，被归因于 爬虫检测错误分类 MetaIAB，已开启核心 PR 以调整默认设置（阅读更多）。

  • 多位管理员报告 插件在升级后静默失败，原因是 CDN 端的 CORS 行为；早期调试指向 BunnyCDN 标头和回归时间问题（阅读更多）。

  • 一个虽小但真实的 UI 小麻烦：启用话题投票且隐藏“0 票”时，最后一个标签后会出现逗号；Meta 的主题定制被牵涉其中，并已迅速调整（阅读更多）。

  • 一次痛苦的编辑器事件：上传 HEIC 图片 导致错误和重新加载，丢失了长篇草稿；调查集中在复现步骤和错误详情上（阅读更多）。

ux

  • Meta UX 报告指出，通过“邮箱登录”流程登录时，2FA 输入框左对齐；已开启修复 PR，Meta 的登录布局受到了重新审视（阅读更多）。

  • 表情符号的正确性得到了关注：:champagne: 并不存在，但别名使其看起来好像存在；后续措施增加了验证功能，以防止别名指向不存在的表情符号（阅读更多）。

  • 移动端交互请求：在帖子管理操作底部面板中添加 抓手条（与话题管理操作 UI 匹配），以提高可发现性和操作便利性（阅读更多）。

  • 功能 UX 请求提出了一种 宽屏“展开表格”查看器（只读），以便在不进入编辑模式的情况下阅读大型 Markdown 表格（阅读更多）。

  • Meta 上关于 嵌套回复 的持续实验引发了兴奋和导航困惑，特别是当从通知或平铺视图进入时（阅读更多）。

开发

  • 主题/插件作者再次收到推动：.hbs 文件已弃用（请迁移至 .gjs），该话题还提到了 Ask Discourse 作为小型转换的快速助手（阅读更多）。

  • 内联 <script type="text/discourse-plugin"> 支持现已移除；标准现代化线程已更新，包含 2026 年 3 月的移除里程碑（阅读更多）。

  • 团队更新：新的插件构建系统演讲已在外部（Ember Europe 聚会）分享，为开发者提供了学习新工作流的途径（阅读更多）。

#Plugin

  • Discourse Challenges 迅速演进：周期间隔、版主访问权限，随后 ChallengeBot（私信确认、提醒、如 status/leaderboard/streak 等命令）迅速上线（阅读更多）。

  • 一个新插件构想 Plugin Cleaner 旨在扫描并移除未安装插件遗留的“残留”；反馈强调了删除未知/未迁移插件结构的固有风险（阅读更多）。

  • Discourse Member Application 引入了结构化的 /apply 申请流程，用于邀请制/私密社区，用 Discourse 内部的审核 + 邀请流程取代了外部表单/电子表格（阅读更多）。

#Extras

  • Dexo 是一款使用 UIKit/Swift 构建的原生 iOS Discourse 客户端，展示了多论坛支持、HTML 渲染、认证流程和简洁的 UI 方法（阅读更多）。

#Community 建设

  • 一位新的社区所有者请求对游戏社区的新 Discourse 论坛提供反馈；回复涵盖了主题、UX 优化以及让 Discourse 开箱即用不那么“通用”（阅读更多）。

  • 一位葡萄牙语社区经理询问他们的游戏论坛组织是否得当；建议包括重新思考标签/子类别的权衡，并改进入职流程（例如直接链接到预填的编辑器）（阅读更多）。

市场

  • 一项大规模请求寻求 phpBB 到 Discourse 的迁移专家，处理约 87 万篇帖子，涉及希伯来语 RTL 和严格的 SEO/重定向要求，强调最小化停机时间和 URL 映射（阅读更多）。

@team 群组活动

  • david 重点关注 发布体验 和升级信号：他在安全修复线程中解决了关于缺失 Meta 公告和仪表板混乱的担忧（阅读更多），移动并组织了发布站点反馈，同时迅速交付了如 RSS 等改进（阅读更多），并回应了自托管版本锁定问题（并纠正了设置 version: 的位置）（阅读更多）。他还推动了核心修复/更新，涵盖“新版本”邮件投递（阅读更多）和 Facebook iPhone 应用内浏览器的 UA 检测（阅读更多），并记录了旧版内联脚本标签的移除（阅读更多）。

  • Falco 结合了产品反馈、集成和 AI：他解释了为何许多安全修复集中发布（阅读更多），更新了 Discourse 博客的嵌入式评论体验并指出了主题/内边距问题以进行迭代（阅读更多），并推进了 Patreon 插件 API v2 迁移——按请求添加了自定义用户代理（阅读更多）。他还澄清了聊天/GIF 行为预期（功能还是 bug）（阅读更多），将日历功能请求指向新的订阅 URL 工作（阅读更多），并提议改进 AI 翻译控制，以便管理员可以明确选择是否包含私信（阅读更多）。

  • zogstrip 处于修复 bug 的高潮期，始终将修复与 PR 关联：积极讨论了审核队列/编辑器流程修复（阅读更多），为私信置顶行为制定了实施计划（阅读更多），单盒问题（包括损坏的 x.com 行为）已排队修正（阅读更多），并承认了永久删除的边缘情况，已有修复即将上线（阅读更多）。他还改进了表情符号别名管道，防止别名指向不存在的表情符号（阅读更多），并继续完善“即将变更”切换的管理员/报告 UX 预期（阅读更多）。

  • awesomerobot 专注于 UI/UX 小麻烦和务实改进：话题投票/标签标点符号回归问题在 Meta 上迅速修复（阅读更多），邮箱登录 2FA 对齐问题已追踪到特定流程并排队修正（阅读更多），并明确了语义/AI 搜索结果与精确匹配的区别（阅读更多）。在 API 方面，他开启了 PR 以允许细粒度 API 用户读取 about.json（阅读更多），并要求在 HEIC/草稿丢失报告上提供更好的 bug 复现（阅读更多）。

  • supermathie 帮助解决了自托管身份/认证问题：他解释了为何 Discourse ID 坚持要求 HTTPS 重定向 URI（以及 force_https 的实际作用）（阅读更多），并跟进关于 about.json 访问和细粒度密钥的 API 范围/错误消息讨论（阅读更多）。

  • sam 就“难以复现”的托管问题和更广泛的 UX 发表了意见：他参与了一个棘手的主题 git-clone 失败线程（指出 GitHub 中断/速率限制可能是嫌疑人）（阅读更多），推动了对“帖子批准”给用户带来的整体感受进行重新思考（队列透明度、通知、编辑器行为）（阅读更多），并通过清理过时材料（如“有效搜索”指南）更新了核心文档（阅读更多）。他还更新了面向管理员的编辑器弹窗文档（阅读更多），并提请工程团队注意 Extras 集成链接出现 404 的问题（阅读更多）。

  • pmusaraj 调查了 ActivityPub 互操作性问题：识别出 Mastodon 的参数变更（scope → scopes）并提出了上游/插件内的修复方案（阅读更多），随后的 Discourse↔Discourse AP 验证问题被缩小到 Meta 参与者行为与其他参与者行为的差异（阅读更多）。他还确认了 Discourse ID 针对重定向 URI 冲突的改进（阅读更多），并跟进免费层级站点上的备用邮箱行为（阅读更多）。

  • manuel 针对有人报告“Meta 不再通知我”的情况，直接提供了关于通知设置（关注/追踪）的终端用户指导（阅读更多）。

  • HAWK 确认并升级了托管免费计划配置错误至团队，保持了支持循环的快速运转（阅读更多）。

  • pedro 介入同一托管配置问题，以收集诊断详情（输入的确切域名值）并帮助确认变通方案（阅读更多）。

感谢阅读，下周再见！ :slight_smile:

117

本周在 meta.discourse.org…

关键数据

在过去 7 天（2026-03-29 → 2026-04-05）中，Meta 论坛发布了596 篇新帖子，创建了77 个新话题。（如果您希望在自己的网站上生成类似的汇总报告，请参阅在 Data Explorer 和 API 方法中讨论的内容，详见 我如何发布实时报告链接或嵌入网站活动？ 和 使用 Discourse API 运行 Data Explorer 查询。）

本周活跃用户（帖子数 / 收到的点赞数）：

用户 帖子数 点赞数
Moin 60 93
Falco 25 93
RGJ 22 67
Lilly 20 52
Canapin 13 46
nat 12 46
awesomerobot 16 37
Ed_S 18 35
zogstrip 15 33
david 14 28

本周大部分精力集中在新的交互功能（新的 Boosts 实验：阅读更多）、将 Discourse 作为完整评论系统嵌入（阅读更多），以及持续迭代AI 和本地化工作流（例如：标签翻译质量反馈，阅读更多，以及后续修复，如支持翻译后的标签图标，阅读更多）。

热门话题

#announcements

  • Discourse 正在实验Boosts（带简短消息的反应功能），社区就其与点赞/反应的 UX 重叠、审核影响以及命名问题展开了讨论（“命名事物”甚至也短暂登场）。阅读更多

  • 嵌入功能迎来重大升级：“完整应用模式”现在可在 iframe 内加载完整的 Discourse 应用，访客无需离开宿主网站即可回复、点赞或引用。相关讨论涉及滚动条的可见性以及“回复话题”按钮的位置。阅读更多

  • Discourse AI 代理现在可以向外连接至任何 MCP 服务器（“自带 MCP”），通过外部工具扩展 AI 代理的自动化能力。阅读更多

  • 一项虽小但意义重大的支持改进：用户在跟踪/关注 solved 分类下的话题时，现在会在话题被标记为已解决时收到通知——此外还收集了关于通知偏好边缘情况的早期反馈。阅读更多

  • 2026 年 3 月月度发布帖子已上线，包含更新日志和补丁版本的链接，并引发了一次流畅的“切换到发布轨道”操作报告。阅读更多

blog

  • nat 发布了一篇关于 Discourse 过去 13 年多语言演进历程的“幕后”文章，团队随后给予了赞誉并补充了背景信息。阅读更多

events

  • 团队澄清了 Meta 将如何组织网络研讨会与社区办公时间，包括回放和未来会议的安排位置。阅读更多

#site-feedback

bug

  • 移动端回归导致部分 Meta 页面在 iOS 浏览器上仅渲染标题；调查追溯到主题组件的最近更改，随后进行了回滚。阅读更多

  • 标签横幅暂时丢失了标签显示（显示为空白横幅），迅速诊断为数据可用性问题，随后在主题组件中进行了修补。阅读更多

  • 数字标签边缘情况：旧的 /tag/#### URL 模式导致500 错误（对爬虫不友好）；团队确认已关注修复方案，同时保持 /tag/name 的兼容性。阅读更多

  • 分类专家插件因验证约束导致用户合并崩溃；已通过插件 PR 排队修复。阅读更多

  • 翻译回归导致AI 的“思考/评论”泄露到德语输出中；代理已更新，受影响的标题和帖子已清理。阅读更多

  • 使用较新版本的 aws-sdk-s3 时，备份到Cloudflare R2 在分块上传时失败；锁定版本恢复了受影响安装的功能。阅读更多

  • 已归档话题与反应的逻辑存在错误：在某些条件下仍可对某些帖子进行反应；核心修复已准备就绪。阅读更多

#feature

  • 标签图标组件增加了对翻译后的标签的支持（参考了 PR，并展示了翻译后的标签标签和正确图标的截图）。阅读更多

  • Mistral 嵌入集成遇到了与 OpenAI 兼容性的不匹配（dimensions 与 output_dimension），促使提出支持 Mistral 参数命名的请求。阅读更多

  • 一项实用的媒体请求：检测或拒绝 VP9-in-MP4 上传（这些上传在 iOS Safari 上会静默失败），并讨论了安全、可选的转码方案。阅读更多

  • 管理员请求允许自动群组接收邮件（以避免“重复群组 + 同步成员”的变通方法），并提到了现有的仅控制台变通方案。阅读更多

ux

  • 编辑器中的编辑流程中的“放弃”按钮仍然令人困惑：建议包括将 UI 文案改为“取消编辑”，并仅在存在实际更改时提示。阅读更多

  • 强制 MFA 可能将用户“锁定”在安全屏幕且缺乏足够指导；该线程探讨了更好的自定义模式（站点文本与主题组件插入在包装器出口上方）。阅读更多

  • 回归报告显示，在“简化分类创建”下，更改父/子分类关系时会重置分类权限，工作人员确认正在调查。阅读更多

  • 一个长期存在的流程小问题：用户无法取消关注被暂停/封禁的账户，除非先临时解除暂停；修复 PR 已链接。阅读更多

Community Building

  • 一篇坦诚的帖子探讨了在没有产品/服务“拉力”的情况下如何发展社区，重新审视了活动飞轮、99–9–1 模式以及可持续的“非创始人驱动”参与。阅读更多

General

  • “你的论坛有多精简？”引发了管理员对选择不启用的功能（分类、插件、聊天、反应、LLM）的具体盘点，并自然延伸到标签和信任级别的权衡。阅读更多

@team 组的活动

  • lindsey 发布了两项面向用户的公告：新的Boosts 实验（阅读更多）以及支持分类中已解决通知的改进（阅读更多）。她还跟进了一项与 Crowdin 样式组件相关的“当前项目”状态更新（阅读更多）。

  • Falco 推动了多个产品和平台相关话题：他宣布了嵌入功能的完整应用模式，并跟进 UI 简化和行为细节（阅读更多）；重申了 iOS 主屏幕推送通知的行为（并指出了其脆弱性的根本原因）（阅读更多）；确认 Meta 将很快在语言切换器中添加乌克兰语/俄语（阅读更多）；并讨论了 VP9 上传缓解策略，提及 Video Stream 作为选项（阅读更多）。他还继续迭代 MCP 和 AI 工作流（例如，权衡仅提及机器人的“工作流触发”方法，阅读更多，并强调 MCP 帖子编辑支持，阅读更多）。

  • nat 专注于本地化和 AI 翻译质量：她发布了长篇多语言历史文章“为每种语言构建”（阅读更多），迅速回应了

118

This week on meta.discourse.org…

Key Stats

Period covered: 2026-04-05 → 2026-04-12

  • New posts: 581
  • New topics: 78

Top users (posts / likes)

Notable launches & fixes that drove discussion

  • Bookmarks got a major discoverability improvement with “jump to bookmarked posts” from the topic footer action menu: read more

  • The Meta Branded theme rebuild shipped (new implementation + early look at the Blocks API), sparking a lot of UI/icon feedback: read more

  • A wave of quick UX and bugfix PRs landed (RSS exclude tags, calendar/iCal formatting, composer strings, localization edge cases), often with “fixed by PR” replies directly in-topic, e.g. RSS exclude_tag: read more

Interesting Topics

#Announcements

  • Boosts on Meta (#Announcements) — The ongoing “Boosts” experiment triggered a deep discussion about signal vs. noise, moderation implications, and UI density (especially on mobile), with proposals like folding/expanding boosts and concerns about “negative boosts”: read more

  • Easier access to bookmarks (bookmarks, #Announcements) — Discourse added quick access to all bookmarked posts in a topic via the bottom-of-topic bookmark control, making “where did I bookmark that?” much easier to solve: read more

ux

  • Mobile composer in 2026 (composer, mobile, ux) — Canapin kicked off a “mobile-first reality check” on the composer’s growing complexity; replies centered on what to remove, what must remain, and iOS-specific reliability issues: read more

  • How to close the tag selector on mobile (composer, mobile, tags, ux) — A small-but-daily papercut: the tag chooser doesn’t have an obvious “close” affordance on mobile, forcing users to learn a non-intuitive tap target: read more

  • Bookmarks UI edge cases on mobile (bookmarks, #Feature) — A nuanced UI/mental-model thread: how should the footer bookmark icon communicate “topic bookmarked” vs “post(s) bookmarked”, and how do you keep actions consistent without hiding “jump to bookmarks” discoverability? read more

  • Community-building discussions on Meta (#Site feedback) — mcwumbly asked how Meta should better encourage community building / management discussions after category reshuffles (and what behavior/structure changes would help): read more

  • Feature/bugfix announcement topics and version clarity (#Site feedback) — A practical meta-process request: include versions in announcement topics so admins who can’t realistically run tests-passed daily can still plan upgrades: read more

#Site feedback

  • Rebuilding the Meta Branded theme + Blocks API (meta-theme-feedback, meta-redesign-2026, #Site feedback) — The new Meta theme rebuild showcased Lucide icons, tighter theme/palette controls, a custom homepage direction, and an explanation of how Blocks differ from PluginOutlets for more stable layouts: read more

  • Inaccurate plugin availability notes (#Site feedback) — Several official plugin topics still claim “available on all hosting tiers” despite new plan tiers; the thread explored linking directly to pricing tables and reducing “two sources of truth” drift: read more

#Theme component

  • Discourse Lucide Icons (#Theme component) — A dedicated theme component topic for Lucide landed, quickly collecting icon mapping feedback (e.g., reply/share confusion, filled heart behavior, missing icons like calendar-heart): read more

  • Topic Hover Cards (#Theme component) — A new component proposes tooltip-style previews when hovering/tapping internal topic links; early feedback asked for clearer screenshots/preview before adoption: read more

  • Highlight to Search (search, #Theme component) — A small productivity boost: highlight any text and immediately search for it, packaged as a new theme component with a live preview: read more

  • Customizable Print to PDF Button (#Theme component) — A new “clean print” topic button component aimed at improving topic export/printing compared to the stock print flow: read more

  • Unhide composer fullscreen toggle for tablets (composer, tablet, #Theme component) — A focused component to restore the fullscreen composer toggle on touch devices with larger screens where it’s hidden by default: read more

Support

  • OIDC login error on the OpenAI hosted forum (openid-connect, hosted-support, Support) — Users reported OIDC authorization failures; escalation + confirmation of resolution followed shortly after: read more

  • Private Topics / Ticket System permission scare (resolved) (Support) — A “this might be a security incident” moment turned out to be a configuration misunderstanding in the Private Topics plugin; the fix was to remove a group from “always show topics started by…” so TL0 users wouldn’t see everything: read more

  • Windows support expectations (Support) — A clear statement emerged: Discourse doesn’t support Windows versions Microsoft doesn’t support, though browser forks may work in practice for legacy systems: read more

  • New site signup stuck on “Almost there…” (resolved) (free-plan, Support) — New customer onboarding briefly failed; staff confirmed an incident and then a fix: read more

bug

  • Structured data issue: missing fields in mainEntity.suggestedAnswer (bug) — A schema/microdata regression was investigated and partially fixed; follow-up indicated remaining validator complaints around missing text/datePublished fields: read more

  • Data Explorer won’t save queries containing semicolons in quoted HTML entities (data-explorer, bug) — A validation rule blocked harmless semicolons inside quoted strings; the request was to only reject actual query terminators outside quotes: read more

  • Data Explorer output double-escapes HTML (data-explorer, bug) — A confusing display bug: Fish & Chips renders as Fish &amp; Chips in query results, making it harder to work with plain text outputs: read more

  • Exclude_tag broken in category RSS feeds (rss-polling, bug) — Excluding tags from category RSS didn’t work, but a /latest.rss?category=...&exclude_tag=... workaround did; a core fix was proposed right in the thread: read more

  • Highlight.js bundles + S3/CDN CORS fallout after upgrade (fixed) (cdn, #Self-hosting) — A subtle “assets loaded from the wrong CDN” bug caused highlight-js failures on codeblocks; a PR corrected highlightjs bundle URL behavior for that S3-only configuration: read more

Activity by the @team Group

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

119

本周 meta.discourse.org 动态…

关键数据

  • 新活动（过去 7 天）： 551 篇新帖子，涵盖 73 个新主题（周汇总窗口 2026-04-12 → 2026-04-19）。

  • 最活跃用户（发帖数 / 获得点赞数）：

用户 发帖数 点赞数
Lilly 28 86
Falco 21 74
Moin 46 73
sam 4 43
awesomerobot 17 40
darkpixlz 14 38
NateDhaliwal 30 33
RGJ 12 31
pmusaraj 11 23
merefield 9 22

本周规模最大的“全员”讨论是关于 Discourse 在人工智能时代对开源的承诺：阅读更多

有趣的话题

blog

  • Discourse 重申了其开源立场（并解释了为何“通过隐匿实现安全”站不住脚），在“Discourse 不会转向闭源”一文中，及时回应了业界对 AI 驱动漏洞发现的担忧。阅读更多

#Announcements

  • 分类创建功能获得了重大用户体验提升：借助 Discourse 主题投票功能，现在可以更轻松地创建“想法分类”，包括更清晰的设置流程和默认值。阅读更多

  • 将 Discourse 嵌入为完整评论系统的功能持续成熟；公告帖收到了更多真实世界的反馈和后续跟进，包括改进之处，如浮动回复/时间线功能。阅读更多

  • 关于“自动为图片上传应用网格”的发布得到了澄清：“即将变更”中的“稳定”并不总是意味着该设置会消失；有时它只是默认值的调整。阅读更多

#Feature

  • 一场长期的用户体验辩论再次浮现：“回复旧主题”的警告已被移除，管理员希望有一个可配置的、以指导为导向的替代方案，而不是令人望而却步的阻断器。阅读更多

  • 审核队列的人机工程学：版主请求按用户分组待审核项（或提供更强的上下文），以避免在队列中举报和帖子分离时误执行“删除用户”操作。阅读更多

  • 聊天功能请求出现在两个密切相关的话题中：聊天频道内的投票和默认频道设置（例如预配置线程、权限等）。阅读更多 和 阅读更多

bug

  • 一个令人痛苦的升级边缘情况：当启用 enable_simplified_category_creation 时，插件无法保存分类设置；开发人员被指引参考 FormKit 迁移模式，并建议通过“即将变更”暂时退出。阅读更多

  • AI 翻译扩展性问题：当同时翻译成许多语言时，葡萄牙语（pt）被跳过，导致对后端故障、详细日志记录和重试行为的调查。阅读更多

  • 管理员帖子扳手菜单存在损坏或缺失的悬停提示；已提交核心 PR 以修复复制/粘贴错误并在需要时添加标题。阅读更多

  • 标签用户体验不一致：根据自动补全输入，编辑器有时声称允许使用标签，有时又不允许；修复需要在限制周围实施更“智能”的执行逻辑。阅读更多

  • 日历/事件 + 汇总回归：帖子事件小部件中缺失聊天链接的问题被追溯为构建系统变更，并通过 PR 迅速修复。阅读更多

  • 用户因路由错误（controllerFor 与 modelFor）无法查看邀请详情标签；已通过核心 PR 发布修复。阅读更多

  • 话题标签自动补全在安全模式下触发了控制台错误，其中一条路径与缺失的图标生成助手有关；在继续深入复现第二种错误模式的同时，相关修复已落地。阅读更多

  • RTL 编辑器优化：当“新主题标题”字段为空时，其方向仍为左到右（LTR）；已提出并合并了一个基于标记的修复方案，根据字段是否有内容来切换方向行为。阅读更多

ux

  • 移动端分享弹窗改进：复制按钮在小屏幕上的位置显得尴尬；一个 PR 重新组织了内容，同时保留了帖子日期。阅读更多

  • 审核队列透明度变更：由于造成困惑，举报评分详情被有意移除，引发了关于应保留哪些可见内容及其原因的讨论。阅读更多

  • 关于移动端创作限制的讨论持续深入（工具栏的可发现性、狭窄的编辑器高度，以及网页与应用程序期望之间的张力）。阅读更多

  • 免费计划信息混乱：用户报告误导性关闭/只读时间的沟通问题，促使工作人员调查时间线清晰度和自动化行为。阅读更多

Support

  • Redis 警示案例：清除 Redis“修复”了卡住的“更新中…

120

This week on meta.discourse.org…

Key Stats

Reporting window: 2026-04-19 → 2026-04-26 (last 7 days)

  • New posts: 615
  • New topics: 82

Top users (posts + likes received)

User Posts Likes
Lilly 41 110
Canapin 33 78
lindsey 7 75
Moin 37 68
Falco 22 66
nat 11 53
awesomerobot 11 40
Ed_S 17 40
merefield 15 40
chapoi 10 36

A few threads that drove a lot of discussion this week (sampling)

  • The Meta theme homepage got a Blocks-powered refresh, plus follow-up troubleshooting around “why don’t I see it when logged in?” (read more)

  • Reactions/likes UX changes kept evolving, including fixes and follow-ups for mobile/touch behavior (read more)

  • Nested Replies testing continued to surface real-world navigation + notification challenges (and feature debate) (read more)

  • Several admin-focused improvements landed in quick succession: Data Explorer charting (read more), category approval flexibility (read more), Topic Voting UX improvements (read more), and bulk pin/unpin actions (read more)

  • Internationalization and SEO got tangible wins: localized emoji search (read more) and a canonical/hreflang fix for ?tl= pages (read more)

Interesting Topics

#announcements

  • Current Projects (April 2026) landed with the latest “what we’re building now” roundup, framing recent deliverables like embedding improvements and ongoing focus areas for the platform (read more)

  • Data Explorer got more charting options: nat shared how the plugin now auto-selects better chart types based on result “shape”, making queries easier to interpret without exporting data elsewhere (data-explorer) (read more)

  • Category approvals became more flexible: new category moderation controls allow “everyone except certain groups” or “only certain groups” approval requirements, reducing mod workload while keeping guardrails (#announcements) (read more)

  • Topic Voting UX improvements shipped: voting access while scrolling, prompts to follow after voting, and improved “Hot” sorting made idea categories feel more responsive and intentional (topic-voting) (read more)

  • Bulk pin/unpin is here: admins can now pin or unpin multiple topics at once from topic list bulk actions—small change, big time saver for ongoing curation (#announcements) (read more)

  • Simpler email subject lines: lindsey outlined changes that remove redundant/technical formatting from email subjects to make communities feel less “developer-ish” in inboxes (email) (read more)

  • Emoji search now works in your language: emoji keyword matching expanded beyond English into 48 locales—a long-standing need for multilingual communities (localization) (read more)

#site-feedback

  • Meta’s homepage got a dashboard-style update: derek rolled out a Blocks-based homepage layout (events, hot topics, contributors), with discussion on why educational video content is surfaced and how personal homepage preferences interact with the new “Home” link (meta-redesign-2026) (read more)

  • Where should “show-and-tell” posts go? mcwumbly suggested a lightweight convention: post in General and tag show-and-tell—then let patterns emerge before adding structure (and the topic itself became a mini show-and-tell) (read more)

  • Category organization feedback continued: users highlighted friction around long inline category references (e.g. parent/subcategory paths), hashtag completion ergonomics, and discoverability tradeoffs after the Meta category refresh (meta-redesign-2026) (read more)

  • Restricted/private-ish tags leaking into UX: the “tag cleanup” thread resurfaced questions about whether restricted tags should be discoverable to unauthorized users at all—leading to investigation and a core fix (tags) (read more)

  • Possible slow rendering with disco-toc + many headings: Moin reported noticeable delays that disappeared in safe mode, raising suspicion that certain components (or ToC generation) may be too heavy on long/structured posts (disco-toc) (read more)

ux (and UX-adjacent buglets)

  • User deletion modal had an absurdly long button label on mobile: Canapin reported the truncation, and awesomerobot proposed a redesigned flow (choose delete type first, then confirm) with a PR already in motion (mobile) (read more)

  • Event date styling next to topic titles was confusing on mobile: the mobile rendering lacked the visual separation seen on desktop, prompting a quick “make it consistent (and simpler)” fix proposal (calendar-and-event) (read more)

  • Mobile review queue UI got a cleanup pass: misaligned header elements, spacing issues, and overly tall titles were raised—then awesomerobot followed up with a batch of improvements in core (review-queue) (read more)

bug / Support

  • SEO + localization bug: ?tl= pages canonicalized incorrectly: multilingual admins flagged that translated crawler pages couldn’t rank because the canonical pointed to the base language; nat agreed and shipped a fix via core PR (seo, content-localization) (read more)

  • Chat performance: Pitchfork timeouts and “silent threads”: a deep write-up suggested chat reply tracking could bloat over time and cause slow/unreliable loads; sam tested and reported a huge performance improvement via indexing/query changes (chat) (read more)

  • Mentions reachability check broke with uppercase usernames: thoka found case-sensitivity gaps that prevent “won’t notify” warnings in restricted categories; follow-up discussion led toward smaller, safer endpoint-level fixes (mentions) (read more)

#plugin / #theme-component

  • Communiteq Power Tools plugin: RGJ consolidated lots of “small but practical” admin enhancements into one maintained plugin—reducing the need for console access and bundling quality-of-life tweaks (#plugin) (read more)

  • Serve Discourse content as Markdown: benword released a plugin that outputs “cooked → markdown” via Accept: text/markdown or .md URLs, aimed at cheaper LLM ingestion and simpler downstream processing (markdown, ai) (read more)

  • Combined login/signup button component: Lilly shipped a header-space saving theme component that merges auth buttons into one dropdown/modal—especially helpful on mobile where signup can be hard to spot (login, signup) (read more)

  • Show hidden categories component: pfaffman shared a theme component approach to “preview” hidden categories (via a “fake category” linking to group join/request), and compared it to existing options (#theme-component) (read more)

General / #extras (show-and-tell energy)

  • Domniq: a Discourse-native Android+iOS app preview: nicolsdennis showcased an app build with push notifications, moderation actions, and a polished UI—plus discussion of theme inspiration and chat styling (show-and-tell) (read more)

  • “I populated my forum with bots” sparked a philosophical debate: the experiment reframed bots as a personal briefing engine rather than simulated community, and the thread explored authenticity, value, and design aesthetics (show-and-tell) (read more)

  • Discourse Shortlink Router proposed a new way to share “support URLs” cleanly: swap your domain for a router domain to generate clickable admin/settings links, alongside a trust/privacy discussion (#extras) (read more)

Activity by the @team Group

  • lindsey shipped multiple admin-facing improvements and updates this week: the April roadmap newsletter (Current Projects), more flexible category-level approvals (read more), bulk pin/unpin actions (read more), and Topic Voting enhancements (read more). She also continued the “make Discourse feel less technical in inboxes” push with simplified email subjects (read more) and documented new safeguards for permanent deletion settings becoming admin-visible (read more).

  • Falco advanced multilingual UX with localized emoji search (read more) and pointed translators back to the change when older support topics resurfaced (read more). He also kept driving embed-as-comments improvements and troubleshooting in the Tecnoblog embed thread (read more), helped isolate tracking/analytics issues via PR links (read more), and advised on Ghost integration behavior and expectations (read more). On AI translation operations, he clarified how switching LLMs affects translation progress (read more) and coached on improving AI triage examples/tool-call usage (read more).

  • nat focused on localization correctness and SEO: she confirmed that translated ?tl= pages should be self-canonical and shipped a fix quickly (read more), plus guided follow-up rollout questions (read more). She also clarified retry/backfill behavior and expectations in an AI translation reliability debate (read more), and closed the loop on multiple content-localization bugs with deployed fixes (read more; read more; read more). Separately, she announced richer Data Explorer charting to make community analytics more accessible (read more).

  • awesomerobot had a particularly UX-heavy week: he proposed a cleaner deletion flow to avoid giant mobile button labels (read more), addressed mobile event date styling inconsistency (read more), and pushed fixes for mobile review-queue alignment/spacing issues (read more). He also took on tricky mobile modal/viewport behavior with an “add user to list” modal fix attempt (read more) and explained why some “empty space” on topic lists is reserved for live presence UI (read more). On Meta’s redesign goals, he added important context about broadening Meta beyond developers in the homepage refresh thread (read more).

  • chapoi continued polishing the reactions/likes experience: he shared progress on making “display all reactions” better than the initial fix (read more) and clarified intended “new normal” behavior (reactions on the left) (read more). When users of likes-only sites objected to the new two-heart UI, he confirmed the team was working on restoring the single-like-button layout for reactions-disabled sites (read more). He also chimed in on Meta tag UX expectations around restricted tags (read more) and reacted to the AI-bot “show-and-tell” forum experiment with thoughtful framing (read more).

  • derek rolled out and supported the new Blocks-based Meta homepage, explaining design intent and tradeoffs (including surfacing educational content) (read more), and then quickly resolved a break caused by a core change interacting with the theme’s custom homepage model (read more).

  • zogstrip was active across multiple “small but sharp” bugfixes: he investigated restricted tags leaking into tag autocomplete and landed a core fix (read more), reviewed the “double-escaping underscores in image alt text” regression and opened a PR despite it being tricky (read more; read more), and handled draft deletion API inconsistencies with a fix proposal (read more). He also responded to mention-case-sensitivity issues by opting for safer incremental endpoint fixes (read more) and investigated a backups-page breadcrumb race condition (read more).

  • mcwumbly helped shape Meta’s culture/structure around “sharing builds” by proposing the show-and-tell convention (read more) and then encouraging spin-off topics for deeper feedback loops (read more). He also explored product-design space in a sensitive feature request about “post approval by future self / trusted friends,” including the idea of opt-in just-in-time AI feedback (read more), and apologized/clarified a Meta mishap where a topic became inaccessible due to category privacy changes (read more). Finally, he confirmed Discourse ID username changes are now available directly in user settings after recent work (read more).

  • supermathie tackled several technical/support edges: he highlighted how “private email” mode makes outgoing emails confusing when the topic link is removed (read more), participated in an older-but-active discussion about automating access to Discourse via external tools and clarified intent vs automation boundaries (read more), and dug into federated 2FA/MFA signaling limitations for Discourse ID (OAuth2 vs OIDC needs) (read more). He also confirmed an MCP permission fix for about.json access was merged (read more) and answered a self-hosting filesystem question with a pragmatic GeoIP symlink suggestion (read more).

  • pmusaraj stayed deep in Discourse AI and “diagnose + set expectations” support work: he explained token-cost implications and retry behavior in translation failures when upstream LLMs return errors (read more), and followed up with concrete improvements to category-targeting behavior and locale overrides in AI translation tooling (read more). He also encouraged contributions on Onebox behavior for Google Photos albums by tagging it pr-welcome (read more), and praised the “cooked-to-markdown” approach in the new Markdown export plugin thread (read more).

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

121

This week on meta.discourse.org…

Apr 26, 2026 → May 3, 2026

Key Stats

  • New posts: 480
  • New topics: 55

Top users (posts & likes received)

User Posts Likes
Lilly 47 120
RGJ 16 67
Falco 17 47
Moin 24 46
chapoi 8 43
lindsey 9 33
Canapin 10 30
Jonathan5 5 30
pfaffman 13 28
manuel 5 22

Interesting Topics

General

  • General Discourse’s “infinite scroll” sparked a nuanced debate about UI mechanics vs. algorithmic feeds, including accessibility/legal angles and whether “bottomlessness” is inherently addictive in a forum context. read more

  • General show-and-tell kirupa shared an update on resurrecting a quiet community with bots—now with full source code published for others to learn from. read more

#Announcements

  • #Announcements topic-voting badges New Topic Voting badges landed (Daydreamer → Visionary), plus thoughtful backfill/notification rules to avoid spamming users for ancient vote milestones. read more

  • #Announcements trust-levels Defaults for TL3 requirements are being adjusted via an upcoming change, aimed at making TL3 achievable on very active sites without admins needing to hand-tune caps. read more

  • #Announcements release-notes The April 2026 monthly release shipped, with the canonical changelog linked for the full list of improvements and fixes. read more

  • #Announcements calendar-and-event Calendar subscription UX got a real-world nudge: admins reported users grabbing the “wrong” subscription URL first, prompting discussion on re-ordering options to reduce confusion. read more

bug

  • bug data-explorer A Data Explorer UI regression limited report results to a cramped, scroll-boxed view—quickly confirmed and fixed for affected sites. read more

  • bug fixed Plugin/theme compilation logs got noisy and confusing due to missing ember-this-fallback helper modules; the underlying breakage was identified and patched (with a backport planned). read more

  • bug chat A “phantom ping spam” issue caused duplicate mention notifications from a single message; a fix was merged shortly after reports. read more

  • bug composer ai The new docked AI composer got early testing feedback: editing, quoting, sidebar interactions, and mobile scrolling issues were reported, triaged, and iterated on via follow-up fixes. read more

  • bug fixed After updating to 2026.4, some sites saw “Document tree depth limit exceeded” from crawler-related middleware paths; investigation led to targeted fixes. read more

ux

  • ux invites Invites UI oddities: users could create invites from other people’s profiles, which felt misleading because the invite still originates from the clicker—not the profile being viewed. read more

  • ux Relatedly, an Invite tab appearing on hidden profiles was flagged as a UI leak (even if it didn’t expose the hidden user’s data). read more

  • ux category-badge-styles Category badge text colors became unreadable for some themes due to foundation modernization CSS interactions; a component-level fix was proposed and PR’d. read more

  • ux Some users reported smaller mobile font sizes on certain hosted communities, with investigation pointing to the modernized Foundation theme being enabled on those instances. read more

  • ux tags mobile Long tags (or many tags) can get cut off at the screen edge without clear truncation affordances, raising questions about mobile readability and layout rules. read more

Support

  • Support The age requirement (13+) question turned into a practical guide on what differs between self-hosting and CDCK hosting, plus how compliance regimes (COPPA / UK OSA / EU DSA) shape obligations. read more

  • Support email A quick clarification on customizing digest/summary email subjects: admins can often do this via site texts like user_notifications.digest.subject_template. read more

  • Support Enabling Ruby YJIT via template led to a great debugging thread—ultimately boiling down to how environment variables were being checked (and how sudo can scrub env). read more

  • Support composer Admins asked how to hide category descriptions in the category chooser; a small CSS snippet solved it cleanly. read more

  • Support user-directory Partner-program “directories” came up again, with pointers to the built-in user directory and ways to present it as cards via theme components. read more

#Theme component / #Theme

  • #Theme component A “pagination-like” workaround arrived fast: Load More Button theme component intercepts auto-loading and requires manual input—useful for admins worried about “infinite scroll” semantics. read more

  • #Theme component Modern User Card work continues: restoring/modernizing the experimental usercard design surfaced deprecations and refactor needs as core evolves. read more

  • #Theme The new Verso theme dropped: lightweight, editorial-inspired styling with soft colors and both light/dark schemes. read more

development

  • development theme-guides blocks A new repo of Claude Code “skills” for Discourse theme + Blocks authoring was shared, including an example theme and patterns for layout frames/outlets. read more

  • development A candid “case study” write-up on learning plugin development while building a contact-form plugin—useful perspective for aspiring community builders who aren’t full-time engineers. read more

Marketplace

  • Marketplace A pre-launch community platform build request sparked candid scoping reality checks: “design-layer” tweaks, a custom member portal/profile, and auth-related flows likely exceed a tiny starter budget. read more

wordpress

blog

  • blog Discourse Discover: Hobbyist Edition highlighted communities built on deep, durable expertise—exactly the kind of “slow web” Discourse tends to enable. read more

Activity by the @team Group

  • Falco was everywhere this week: clarified hosting vs self-hosting responsibility in the age requirement thread (read more), fixed a duplicate-notification “ping spam” bug (read more), and untangled YJIT enablement confusion for self-hosters (read more). They also guided composer image resizing configuration—pointing out the difference between “threshold” and “target width” settings (read more), plus continued improvements around embedding Discourse as a full comment system (read more) and crawler middleware fixes (read more).

  • chapoi helped anchor two high-signal UX debates: the framing of “infinite scroll” vs algorithmic “infinite feeds” (read more) and the practical reality of footers/homepages in topic-list UIs (including a clear “not on the roadmap” answer on pagination) (read more). They also triaged a category badge contrast regression and committed to investigating root cause (read more).

  • lindsey shipped and enabled new Topic Voting badges, then explained how backfill notifications are intentionally throttled to avoid retroactive spam (read more). They also responded to calendar/event UX threads, including pointing to the newly added “All day event” checkbox (read more) and confirming .ics event descriptions now populate correctly (read more).

  • manuel published a practical, AI-assisted theming accelerator: theme + Blocks authoring skills and examples, plus follow-up notes on how Blocks shifts theme customization from “inject components” to “define layout frames.” (read more). They also reiterated that Meta’s branded theme isn’t intended for public reuse, while pointing builders to Blocks-based approaches to achieve similar outcomes (read more).

  • david posted the April 2026 release announcement pointing admins to the canonical changelog (read more) and jumped quickly on the ember-this-fallback deprecation crash report—shipping a fix and planning a backport (read more). They also clarified that OIDC group sync is now available and referenced the updated changelog/docs (read more).

  • pmusaraj released the Verso theme (editorial styling, light/dark, CSS-only) (read more) and diagnosed an iOS-only horizontal scrollbar issue affecting embedded comments/admin views—linking it to an in-flight fix (read more).

  • awesomerobot asked for sources and helped steer the “infinite scroll” thread toward evidence-based discussion (read more), and reinforced the practical constraints of hosting providers needing to follow regulations in jurisdictions they serve (read more).

  • martin announced upcoming default changes for TL3 promotion requirements, confirming how upcoming-change defaults interact with admin overrides and resets (read more).

  • HAWK provided an important compliance perspective: even self-hosted communities may have obligations (e.g., UK OSA) depending on where users can sign up from, and admins should plan accordingly (read more).

  • nat acknowledged and rapidly resolved the Data Explorer “5-row” layout regression, confirming when the fix landed for the reporter’s site (read more).

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

122

This week on meta.discourse.org…

Key Stats

Period covered: 2026-05-03 → 2026-05-10

  • New posts: 500
  • New topics: 62

Top users (posts + likes received)

User Posts Likes
Lilly 56 95
Moin 38 88
Falco 16 28
pmusaraj 13 25
david 12 23
NateDhaliwal 23 21
nat 4 21
awesomerobot 7 20
merefield 11 26
Ed_S 8 15

Team leaderboard (posts + likes received)

Team user Posts Likes
Falco 16 28
pmusaraj 13 25
david 12 23
nat 4 21
awesomerobot 7 20
chapoi 9 13
HAWK 3 10
gabriel 1 10
martin 2 7
derek 3 6

Fast-moving themes this week (with receipts)

  • Localization & translation UX kept surfacing in different corners of the product — from “what Discourse looks like in Japanese” (read more) to guidance on choosing one translation approach in the Translator plugin thread (read more) and schema / SEO edge cases tied to translated content (read more).

  • Embedding & comment experiences continued to get attention, including smoother embedded login flows (read more) and practical setup gotchas like cross-domain cookie behavior (read more) plus clarifications on auto-creating topics for embedded comment threads (read more).

  • AI operational reliability was a recurring thread: token / context sizing confusion (read more), translations getting stuck with “thinking” models (read more), and translation failures due to structured output / reasoning interactions (read more).

  • Admin UX & reporting: “Site traffic” visibility issues turned out to hinge on hidden settings (read more), and crawler counts differing between reports were clarified as rollout-date related (read more).

Interesting Topics

blog

  • “What It’s Actually Like to Use Discourse in Another Language” sparked practical discussion about what doesn’t translate (plugin UI, theme strings), and how quickly missing theme strings can be patched once spotted (read more).

  • “The Digg Lesson: Why Moderation Infrastructure Matters” revisited a classic cautionary tale and prompted thoughtful reflections on the tools and systems needed for moderation at scale (read more).

#Announcements

  • Discourse Discover got “Hot Topics”: a new cross-community surfacing mechanism was introduced (starting in DiscourseHub iOS), raising interesting implications for discovery and ranking across the network (read more).

  • Embedding Discourse as a full comment system got another round of practical Q&A, including confirmation that embedded threads can auto-create their backing topics on first visit (read more).

development

  • A plugin author’s “case study” on breakages, deprecations, and documentation turned into a broader conversation about pace, stability, and how docs should be maintained (GitHub PRs vs wikis, deprecation timelines, and expectations) (read more).

  • bin/lint regressions for non-bundled plugins were quickly reported, reproduced, and fixed, highlighting how linting workflows differ across plugin setups (read more).

#Feature

  • Chat as “first-class content”: a prototype “single activity view” concept proposed interleaving topics, subcategories, and chat channels by recency — raising big questions about information architecture and discoverability (read more).

  • Parent categories vs muted subcategories: a high-volume publishing/community hybrid use case asked for better ways to surface “hot” discussions without flooding Latest, while still enabling an aggregated view inside a parent category (read more).

  • Translated quotes losing context: a feature request argued that translation should preserve the helpful “quoted from topic/post” metadata and dropdown context currently present in non-translated quotes (read more).

ux

  • Impersonation auto-timeout UX: when experimental impersonation ends automatically, the UI can become misleading — prompting ideas like timers, MessageBus UI updates, and graceful “Stop impersonating” behavior (read more).

  • Blank /custom page after a theme switch on login: when a logged-out user’s theme has a custom homepage but the logged-in theme doesn’t, users can end up on an empty page — with suggestions to show an actionable “Take me home” fallback (read more).

  • The missing tag “info” button: a UX regression report noted that non-admin users can’t easily find tag descriptions anymore if the info affordance is gone (only admins see the wrench) (read more).

bug

  • Full name requirement vs Discourse ID: enabling full-name requirements didn’t behave as expected in a Discourse ID signup flow, and the issue was reproducible enough to be moved into bug for fixing (read more).

  • OpenID Connect group sync ejecting users from “unsynced” groups: a serious membership-change edge case was described where losing one OIDC group could remove users from unrelated groups, with a fix proposed quickly (read more).

  • Survey editing error after transferring topic ownership: editing someone else’s survey (after transfer) threw an error, and the plugin fix was shipped promptly (read more).

  • AI translation failures tied to “reasoning” models and structured outputs: debugging showed how reasoning tokens can consume completion budgets, and how model capability mismatches (e.g., json_schema support) can break translations (read more).

Support

  • Bootstrap mode removal (“legacy?”): the rationale, what got replaced (admin onboarding panel), and which old “bootstrap niceties” might deserve a comeback (directory refresh cadence, first-admin-as-mod, etc.) made for a very constructive postmortem (read more).

  • Discourse Splash (“blue dots”) can’t be disabled anymore: the removal of the disable setting was explained, including performance/SEO implications and a practical workaround via an animated SVG replacement (read more).

  • Excluding a category from Latest site-wide: admins compared “default muted categories” vs plugins and settings for suppressing noisy daily categories from the global feed (read more).

  • “Site traffic report” missing: the root cause was traced to the hidden use_legacy_pageviews setting — and how that hides the newer report UI entirely (read more).

#Self-hosting

  • “File too large” wasn’t actually a Discourse build issue: a Russian self-hosting thread ended up being a provider firewall / payload blocking problem (uploads + signups), with a detailed recovery and tuning checklist shared (read more).

  • Installing Discourse behind a non-routable public IP: the install “connection test” hurdle and HTTPS requirements came up again, with practical workarounds (skip test / dev install / tunnels / cert setup) (read more).

  • AWS Lightsail + Ubuntu upgrade planning: the thread compared in-place OS upgrades vs “spin up a new server, restore backup, swap DNS” migration playbooks (and TTL prep) (read more).

Marketplace

  • Safeguarding/reporting workflow needs: a charity asked for a specialized reporting button and emergency-protocol flows; replies clarified the boundary between theme vs plugin work and pointed to built-in flag tooling and components (read more).

#Community Building

  • Welcoming new users (especially via Chat): the community explored ways to notify regular users about new signups and how chat/email behavior affects “welcome” flows, especially under hosted constraints (read more).

Activity by the @team Group

  • nat focused on localization and translation expectations — showcasing multilingual UX in the companion blog topic (read more) and advising that communities should pick one translation experience (preferring newer automatic translations over the older Translator UX) (read more).

  • gabriel announced the new Discover feature “Hot Topics”, outlining how the crawler and subject clustering works and where it’s launching first (DiscourseHub iOS) (read more).

  • pmusaraj did a deep dive on “Bootstrap mode is legacy?”, explaining why it was removed, what replaced it (admin onboarding panel), and which parts might be worth reintroducing or rethinking (read more). They also clarified TestFlight availability and app UI scope in the Discover Hot Topics announcement thread (read more), engaged with “chat as first-class content” experiments (read more), reproduced and escalated the Discourse ID / full-name requirement issue into bug (read more), and posted a fix for OIDC group-sync membership removal edge cases (read more).

  • awesomerobot confirmed the removal of the splash-screen disable setting (and why it matters for Core Web Vitals), plus shared an animated SVG approach to replace the dots entirely (read more). They also clarified why crawler values can show as 0 in the newer Site Traffic report for older date ranges (read more), shipped accessibility polish for decorative badge images (empty alt tags) (read more), and continued tightening invites/profile UX by hiding confusing invite UI in unsupported contexts (read more; read more).

  • Falco was active across embedding, AI, and self-hosting guidance — including cross-domain embed login behavior via same_site_cookies settings (read more), confirming embedded-comment topic auto-creation behavior (read more), and steering AI translation debugging away from reasoning-model pitfalls (read more; read more). They also linked to fixes for ongoing crawler “document tree depth” errors (read more), and recommended a safe “new-server restore + DNS swap” path for Lightsail/Ubuntu migrations (read more).

  • david engaged on developer experience and maintenance tradeoffs — balancing stability/customization expectations in the plugin-author case study thread (read more) and clarifying deprecation timelines (read more). They also fixed and merged the bin/lint regression impacting non-bundled plugins (read more), explained Markdown link boundary behavior (and the angle-bracket escape hatch) (read more), requested plugin inventories in a self-hosting memory/precompile investigation (read more), and clarified that tests-passed remains a working alias for latest (read more).

  • derek shipped UI polish and theme-related fixes — quickly resolving a missing theme translation string spotted in multilingual browsing (read more), confirming a merge for category badge color/contrast issues (read more), and acknowledging investigation into the “blank custom homepage after theme switch” login edge case (read more).

  • chapoi provided context and guidance around constraints and implementation details — adding perspective on why documentation can lag during rapid platform evolution in the plugin-author case study (read more), pointing theme authors to the correct plugin outlet for inserting navigation headers (read more), and troubleshooting notification/trigger ambiguity in a UI-notification investigation thread (read more).

  • martin took ownership of improving the impersonation timeout experience, outlining a two-part approach (UI updates when time expires + graceful stop behavior), with an openness to PR collaboration (read more; read more).

  • HAWK drove community strategy discussion via a moderation-history lens in the Digg retrospective (read more) and shared community-building advice focused on intrinsic motivation and Communities of Practice dynamics (read more).

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

123

本周在 meta.discourse.org…

关键数据

过去 7 天（2026-05-10 → 2026-05-17）

  • 新帖子：457
  • 新话题：77

热门用户（帖子数 / 获得的点赞数）：

用户 帖子数 点赞数
Lilly 53 130
markvanlan 6 58
Falco 9 54
lindsey 4 41
Moin 22 38
HAWK 9 31
martin 7 30
RGJ 8 29
NateDhaliwal 16 23
awesomerobot 9 21

值得关注的重大发布：嵌套回复（阅读更多）、新的客户端图像优化（阅读更多），以及针对未解决支持话题的新“我也遇到”信号功能（阅读更多）。

有趣的话题

#Announcements

  • markvanlan 为需要完整线程化对话的社区引入了嵌套回复，并展示了单线程视图和管理员控制功能的早期预览（阅读更多）。

  • lindsey 宣布了“已解决”功能的改进：在支持类别的未解决话题中添加了“我也遇到”按钮，该功能还会订阅成员，以便在解决方案被接受时收到通知（阅读更多）。

  • Falco 推出了新的客户端图像优化，包括将 GIF 转换为动画 WebP，以减少上传大小并提升感知性能（阅读更多）。

  • 批量操作得到了清理，新增了更好的批量标签管理功能：添加/替换/删除标签现在统一在一个“管理标签”模态框中完成（阅读更多）。

  • martin 分享了一个简化的设置流程，用于使用“日历与事件”插件创建事件类别，这是“类别设置计划”的延续（阅读更多）。

  • Horizon 主题用户迎来了默认刷新：高上下文话题卡片现已默认启用，展示了“已解决/投票/分配”等信号以及更丰富的预览（阅读更多）。

  • martin 引入了细粒度的伪组，以实现更清晰的权限管理：将匿名用户与已登录用户分离，以减少在组列表站点设置中@everyone造成的混淆（阅读更多）。

bug

  • iOS PWA 推送通知：当服务工作者尚未控制应用时，订阅设置可能会静默失败，核心开发团队已提出并讨论了修复方案（阅读更多）。

  • Discourse 自动化中的一个边缘情况：每月 recurring 自动化未按预期触发，引发了对每月循环计算方式的深入探讨（阅读更多）。

  • 网格上传中的灯箱导航：图片显示顺序错误（例如 1, 3, 2, 4），相关修复已跟踪并链接（阅读更多）。

  • 群组页面回归问题：用户无法看到谁是群组所有者，尽管数据存在——这导致了一个用于重新渲染该信息的 PR（阅读更多）。

  • 嵌套回复早期的成长烦恼：帖子管理员扳手操作在嵌套视图中似乎无法使用，需要切换回平面模式作为临时解决方案（阅读更多）。

  • 主题创建者问题：在移动设备上导出主题会导致空白/白屏，而桌面端表现正常（阅读更多）。

  • 自托管更新小插曲：一次管理面板更新崩溃（插件 JS 编译超时）已通过执行 ./launcher rebuild app 重建应用得以恢复（阅读更多）。

ux

  • 书签模态框优化：关于编辑书签对话框中一个“多余”的切换按钮的讨论已达成，并通过 PR 将其移除（阅读更多）。

  • 类别编辑器的人体工程学：在简化的类别 UI 中，删除按钮比保存按钮更显眼，这被标记为存在风险/令人困惑（阅读更多）。

  • 个人资料微布局：用户简介中的斜体文本可能会略微被截断，这可能是由于溢出规则导致的（阅读更多）。

  • 移动端管理 UX：在手机视图中配置Discourse 自动化脚本显得拥挤且难以使用（阅读更多）。

  • 追踪行为问题：管理员注意到，进入话题后，话题在列表中失去“NEW”状态的速度似乎发生了变化（阅读更多）。

Support

  • 类别重组安全检查：讨论澄清了重命名类别名称/别名是安全的，因为 URL 通过 ID 解析，且旧的别名会进行重定向（阅读更多）。

  • 嵌入 Salesforce：iframe 和身份验证挑战导致了关于 Cookie 域名对齐和 same_site_cookies 调整的实际指导（阅读更多）。

  • 托管计费/升级困惑：一名免费计划的管理员无法看到Starter 升级选项，工作人员已介入调查并解决（阅读更多）。

  • 注重安全的自托管：关于 Nginx CVE-2026-42945 以及 Discourse 基础镜像/规则是否受影响的问题引发了团队的回应（阅读更多）。

#Theme_component

  • 一个新的主题组件旨在使回复按钮标签更清晰（且可翻译），这对于嵌套回复改变回复语义的情况尤为相关（阅读更多）。

  • 一个虽小但实用的主题组件，用于在话题投票 UI 中隐藏“剩余票数”（特别是在模拟“无限”票数时），并讨论了新的投票限制设置（阅读更多）。

@team 组的动态

  • markvanlan 领导了嵌套回复的发布和问答环节，解释了为什么线程化是管理员的选择（而非用户偏好），以及如何启用/禁用是可逆的（阅读更多，阅读更多）。

  • Falco 发布并解释了新的客户端图像优化管道（包括 GIF 转动画 WebP）（阅读更多），并通过请求服务工作者更新方法协调了 iOS PWA 推送修复（阅读更多）。他还就 Salesforce 部署中的 iframe/嵌入登录限制提供了建议（阅读更多），并回应了涉及插件构建超时的自托管更新失败问题（阅读更多）。

  • lindsey 宣布并澄清了针对未解决支持话题的新“我也遇到”体验，并讨论了计数器应如何表现（从 1 开始以包含原始发帖人）（阅读更多，阅读更多）。她还引入了用于工作人员工作流的综合批量标签管理模态框（阅读更多）。

  • HAWK 通过多个关于扩展性的线程推动了企业就绪度讨论的进展：社区增长时的瓶颈（阅读更多）、过早与过晚扩展的风险（阅读更多）、需要重新审视策略的早期阶段信号（阅读更多），以及用于反馈的企业就绪度检查表草案（阅读更多）。

  • martin 扩展了“类别类型设置”计划，使事件类别更易于配置（阅读更多），并在 Horizon 中默认启用高上下文话题卡片以丰富发现功能（阅读更多）。他还通过引入新的伪组来分离匿名用户与已登录用户，从而改进了更清晰的组语义（阅读更多），改进了管理员“即将变更”UI 中的报告功能选项（阅读更多），并澄清了“即将变更”条目中可选的“预览”和“反馈”链接的工作原理（阅读更多）。

  • awesomerobot 澄清了新“我也遇到”按钮与 Boost 的区别（以及为何它与解决方案通知绑定）（阅读更多），修复了移动端 UI 摩擦问题（自动化中的“上次运行”覆盖了操作按钮）（阅读更多），并通过 PR 解决了诸如“默认 LLM 标签未更新”等产品小瑕疵（阅读更多）。他还恢复了非工作人员用户查看群组所有者的权限（阅读更多），在隐藏“剩余票数”的背景下讨论了话题投票的投票限制设置（阅读更多），甚至在注意到可能的负面含义后清理了一个官方主题模式选择（阅读更多）。

  • zogstrip 提供了一系列稳定的修复：网格灯箱排序问题（阅读更多）、Edge 浏览器中过窄的移动删除对话框（阅读更多）、多个中文语言的编辑/导航流程复现与修复（阅读更多，阅读更多），以及针对与 silenced_till 序列化相关的 API 500 错误的支持排查（并指向相关修复）（阅读更多）。他还通过标记审查帮助引导了对 recurring 自动化“每月”错误的调查（阅读更多）。

  • chapoi 确认并解释了 UX 错误（包括移动端模态框问题和书签对话框的怪癖）（阅读更多，阅读更多），随后通过 PR 移除了不必要的书签切换按钮（阅读更多）。他还帮助排查了插件繁重的自托管问题（徽章/管理 UI），反复引导报告采用安全模式隔离（阅读更多），并指出了本地化/翻译引号问题以供进一步思考（阅读更多）。

  • nat 迅速回应了 AI/本地化问题：解决了挪威语区域检测不匹配的问题，并在计划核心提示词更新期间建议基于提示词的变通方案（阅读更多，阅读更多）。她还确认了翻译边缘情况，例如“标题已翻译但帖子未翻译”，指出了翻译长度阈值及后续调整（阅读更多），并讨论了翻译引号如何丢失重要元数据（特别是在德语中）（阅读更多）。

  • sam 处理了与安全相关和工程相关的事项：确认 Discourse 的默认重写规则不受影响，同时指出将发布基础镜像更新以应对 Nginx CVE 线程（阅读更多），合并/修复了 MCP 子文件夹安装问题（阅读更多），并跟进 AI 提供商配置的边缘情况（Gemini“思考预算”）（阅读更多）。

感谢您的阅读，我们下周再见！:slight_smile:

124

本周 meta.discourse.org 动态…

（本周涵盖时间：2026 年 5 月 17 日–24 日——从 自托管更新崩溃报告 等讨论，到本周晚些时候关于 邀请通知噪音 的支持问题。）

关键数据

  • 新帖子：447
  • 新主题：71

热门用户（过去 7 天发布的帖子数 / 收到的点赞数）：

  • Lilly — 46 篇帖子，68 个赞
  • awesomerobot — 9 篇帖子，36 个赞
  • Falco — 15 篇帖子，35 个赞
  • Moin — 26 篇帖子，27 个赞
  • NateDhaliwal — 15 篇帖子，22 个赞
  • darkpixlz — 12 篇帖子，19 个赞
  • sam — 3 篇帖子，17 个赞
  • Thomas_Rother — 6 篇帖子，15 个赞
  • david — 3 篇帖子，15 个赞
  • keegan — 1 篇帖子，14 个赞

本周推动关注度/点赞数的几个主题（示例）：

  • Discourse AI 用户体验改进备受瞩目，包括 星标 AI 聊天（阅读更多）以及用于机器人对话的 停靠式编辑器（阅读更多）。
  • 博客讨论引发了关于“开放网络”和
125

本周 meta.discourse.org 动态…

关键数据

统计周期：2026-05-24 → 2026-05-31

  • 新帖子：440
  • 新主题：60

热门用户（发帖数 + 获赞数）

用户 发帖数 获赞数
Lilly 53 72
david 4 41
Moin 23 34
sam 8 33
merefield 15 27
chapoi 13 25
awesomerobot 4 24
NateDhaliwal 14 23
darkpixlz 15 21
martin 3 19

本周的讨论热点主要集中在核心用户体验（UX）更新、嵌套回复的稳定性以及管理员/自托管故障排查上，其中多个讨论线程直接关联到新的或正在进行的平台变更，例如默认表情反应（阅读更多）和“小型操作”通知噪音问题（阅读更多）。

有趣的话题

#announcements

  • Discourse 核心正在引入全新的 JavaScript 构建系统，从 ember-cli/webpack 迁移至rolldown（基于 Rust，与 Vite 对齐），承诺在保持生产环境安装不受影响（得益于预编译资源）的同时，实现约 80% 的构建速度提升（阅读更多）。相关背景：自托管用户的预编译资源（阅读更多）。

  • 通过“即将变更”的发布流程，表情反应功能将默认启用于所有新站点和现有站点。martin 解释了默认设置变更的原因以及退出机制的处理方式（阅读更多）。功能背景：Discourse 表情反应插件讨论帖（阅读更多）。

  • “小型操作”帖子（如自动关闭通知、分配通知等）将从“关注/追踪”列表中排除，以减少管理员的通知垃圾信息。受实施限制影响，此功能不可选择（阅读更多）。

  • 日历和事件插件获得了更流畅的事件创建流程，直接在编辑器（富文本交互式编辑器和 Markdown 预览）中完成，降低了举办活动的社区的摩擦成本（阅读更多）。官方插件主题：日历和事件（阅读更多）。

  • 2026 年 5 月月度发布版已上线（v2026.05），为追踪自托管和托管安装升级的用户提供了完整的变更日志链接（阅读更多）。

  • Discourse 发布了“当前项目 – 2026 年 5 月”，其中包括捆绑插件和各项倡议的进展说明（ notably：主题投票改进和日历/事件设置的用户体验优化）（阅读更多）。

bug

  • 一个经典的“幽灵未读”问题浮出水面：用户看到 Unread (14)，但 /unread 页面却是空的。团队已确认该 bug 并正在修复中，同时分享了一个实用的 Rails/SQL 变通方案以清除全站未读状态（但重要提示是：该方案也会清除合法的未读内容）（阅读更多）。

  • 嵌套回复不断暴露边缘情况：建议主题链接指向嵌套路由时出现 404 错误（并可能导致头部状态异常）。核心修复已上线，随后展开了关于嵌套主题中重定向和未读指示器的讨论（阅读更多）。

  • 表单模板用户遇到了一个细微问题：当标签名大小写混合时，标签选择器字段失效。zogstrip 迅速复现并提交了修复 PR，将这一令人困惑的用户体验问题转化为一条实用经验法则：规范标签命名（阅读更多）。

  • 一个用户体验的小瑕疵演变为后端验证的改进：创建没有所有者的仅请求加入群组时，会显示无用的“FAILED”错误。调查指出了分步表单的复杂性和遗留的 Ember 模式；一个 PR 恢复了描述性的错误信息（阅读更多）。

  • 一个棘手的升级问题：db:seed_fu 因创建新系统组时与 anonymous 发生名称冲突而失败。该讨论突出了导入时的边缘情况（用户名为 anonymous 的用户或组），并引发了关于自动群组命名和兼容性的担忧（阅读更多）。

  • 法语实例暴露了一个排版陷阱：由于引号设置，某些撇号/引号替换将 ' 变成了 >。禁用 enable_markdown_typographer 解决了该问题，团队也标记了若干“快速改进”以提升体验（阅读更多）。

#announcements nested-replies

  • 嵌套回复的测试继续引发争议：一名运营者报告了生产环境的破坏（路由变更、通知链接失效、主题不兼容以及移动端布局问题），建议在启用前发出更强烈的警告，而其他人则探讨了测试策略和期望管理（阅读更多）。

  • 另一条关于嵌套回复兼容性的讨论解决了帖子投票与嵌套回复的冲突；短期方向倾向于在嵌套上下文中明确禁用帖子投票行为，并考虑未来在嵌套回复本身中引入“投票”功能（阅读更多）。

#feature

  • 移动端新手引导的摩擦问题受到了关注：Discourse 在移动端显著显示“登录”，但将“注册”隐藏在流程之后，导致用户困惑。该讨论探讨了 UI 权衡、替代组件以及改进可发现性的 PR 工作，同时避免使头部拥挤（阅读更多）。相关组件构想：组合认证按钮（阅读更多）。

  • 关于安全性与可操作性的讨论：当“注册后编辑邮箱”被禁用时，管理员也无法通过 UI 编辑邮箱。提议实施更细粒度的控制（仅限管理员 vs 仅限用户），可能伴随类似密码/双因素认证的“超级用户模式”摩擦以及强审计日志（阅读更多）。

  • Discourse AI 反馈：有人提出增加 AI 工件更新的 Webhook/事件支持（或禁用沙箱），团队指出将在“工作流”（一种新的自动化方法）上线后重新审视此问题（阅读更多）。

Support

  • 自托管用户比较了 VPS 供应商和 SMTP 现实情况：一条“Vultr vs DO”的讨论迅速提醒人们，邮件送达率通常取决于供应商端口策略和正确配置，而非市场镜像——且官方安装路径通常比调试不受支持的市场设置更快（阅读更多）。相关的 SMTP 故障排查和 YAML 陷阱（如弯引号！）也出现在“如果本地登录被禁用”（阅读更多）以及官方邮件故障排查指南（阅读更多）中。

  • 一个实际的存储问题：由于磁盘压力和大容器层导致升级失败。该讨论包含具体的清理指南（./launcher cleanup），以及关于基础镜像是什么、旧层为何积累以及如何安全释放空间的讨论（阅读更多）。

  • “无法自动注册 Discourse ID”在跳过邮箱时阻止了安装，根本原因被确定为HTTPS 重定向 URI 要求；变通方案是通过 CLI 创建管理员并启用 force_https，然后完成设置（阅读更多）。

  • 管理员发现了一个冒充防护机制：存在一个隐藏设置 experimental_impersonation_time_limit_minutes（默认 15 分钟），可通过 Rails 控制台修改（或通过配置文件修改后重建，但这比较笨拙）（阅读更多）。

  • 关于“需要通过 API 创建聊天频道”的问题得到了回答，提供了相关端点（POST /chat/api/channels）及可用的参数示例——这对通过程序化方式部署数百个社区的平台非常有用（阅读更多）。

  • 站点反馈指出，一份长期的“创建错误报告”指南在分类重构后包含死链接；建议的修复方法是使用带 ID 的分类 URL，以便未来的移动不会破坏引用（阅读更多）。参考指南：“在 Meta 上为 Discourse 创建错误报告”（阅读更多）。

#theme-component / #praise

  • 一个新的主题组件旨在通过自动关闭用户菜单中的某些通知类型来减少管理员的认知负担——对于拥有大量邀请或系统通知的站点特别有用（阅读更多）。

  • 一篇深思熟虑的表扬帖指出，捆绑热门插件（默认禁用但预安装）实际上是一个巨大的胜利：管理员可以在不中断在线操作的情况下启用功能（阅读更多）。

@team 团队活动

  • david 启动了一项重大开发新闻，介绍了 Discourse 核心的全新 JavaScript 构建系统（rolldown + 原生 ES 模块），在保持生产环境稳定的同时大幅提升了开发模式性能（阅读更多）。他还建议通过检查浏览器控制台中的功能检测失败来调试与 Discourse 不兼容的浏览器（阅读更多），并更新了关于新的 d-compat/* 策略的文档，用于插件/主题兼容性锁定（阅读更多）。

  • sam 发布/宣布了一项用户通知体验改进：小型操作不再计入追踪/关注活动，减少了批量关闭和计时器期间的“行政琐事打扰”（阅读更多）。他还将幽灵未读报告与小型操作变更的发布路径联系起来（阅读更多），并指引自托管故障排查者关注特定的提交集以修复中间件防护问题（阅读更多）。

  • chapoi 在用户体验和支持线程中保持活跃：确认幽灵未读bug 并证实团队正在处理（阅读更多）；提出反对按用户设置嵌套/线性视图偏好的详细心理模型论证（阅读更多）；指出结构化布局的实用选项（并澄清建议何时适用于主题列表或帖子正文）（阅读更多）；并帮助集成商找到聊天频道创建 API 端点（阅读更多）。

  • awesomerobot 宣布了日历和事件插件中改进的事件创建用户体验，将交互式事件编辑器直接嵌入编辑器中（阅读更多）。他们还协助解决了 JAWS + Discourse 键盘快捷键的无障碍问题（解释了屏幕阅读器如何拦截按键）（阅读更多），并就移动端注册可发现性讨论发表了意见，引用了热门网站中更广泛的用户体验模式（阅读更多）。

  • martin 宣布了即将推出的默认启用 Discourse 表情反应的发布，解释了产品理由以及“即将变更”机制如何使低风险发布比过去更可行（阅读更多）。

  • rishabh 发布了 5 月“当前项目”更新，总结了插件和持续倡议的工作（阅读更多），并分享了一个重要的可用性胜利：GitHub 信息框现在内联显示 PR 状态（阅读更多）。

  • Falco 在多个技术方面做出了贡献：标记嵌套路由错误以供调查并路由给正确的负责人（阅读更多）；讨论 Discourse AI 工件的未来事件/Webhook 选项（并将其与即将推出的工作流联系起来）（阅读更多）；澄清客户端图像优化行为以及增加更多管理员控制选项的权衡（阅读更多）；并就作为更广泛集成方案一部分嵌入 Discourse 评论提供建议（阅读更多）。

  • markvanlan 继续迭代嵌套回复：发布修复以解决损坏的嵌套链接和重定向行为预期问题（阅读更多），并概述了解决不兼容性问题（如帖子投票）的方向，即在嵌套上下文中明确禁用它（并长期考虑在嵌套回复中集成投票功能）（阅读更多）。

  • zogstrip 交付了多个快速修复：解决了表单模板标签组选择器的大小写混合 bug（阅读更多），发布了修复“谁投票”可见性的补丁（针对已关闭主题投票上下文）（阅读更多），并迭代改进了审批/通知正确性的边缘情况（阅读更多）。

  • loic 发布了2026 年 5 月月度发布版的官方指引，指引管理员查看完整的变更日志（阅读更多）。

感谢阅读，下周再见！:slight_smile: