# Dagelijkse samenvatting (13:00 UTC) **URL:** https://meta.discourse.org/t/daily-summary-1pm-utc/291852 **Category:** Forum summaries **Created:** [16 januari 2024 om 22:00 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852 "2024-01-16T22:00:28Z") **Posts on this page:** 20 **Page:** 28
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [13 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/768 "2026-03-13T13:02:35Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 78 - **New topics (last 24h):** 11 **Top users (posts / likes in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @Danielle | 2 | 10 | | @derak | 1 | 8 | | @LotusJeff | 2 | 8 | | @supermathie | 2 | 4 | | @nat | 1 | 3 | | @Lilly | 1 | 3 | | @ice.d | 4 | 3 | | @awesomerobot | 3 | 3 | | @dax | 2 | 3 | | @hellekin | 3 | 2 | **Quick links to other active threads that saw fresh replies** - Terminal-based Discourse client updates in [**termcourse**](https://meta.discourse.org/t/-/395285/21?silent=true) - Discobot onboarding discussion continued in [**New users aren’t starting the discobot tutorial**](https://meta.discourse.org/t/-/62995/107?silent=true) - “Solved” UX expectations debated in [**Mark topic as solved without specifying solution post**](https://meta.discourse.org/t/-/335397/8?silent=true) - Hosted configuration clarity in [**Hidden Settings on Discourse Hosted Sites**](https://meta.discourse.org/t/-/310574/7?silent=true) - Plugin maintenance question in [**Locations Plugin**](https://meta.discourse.org/t/-/69742/1231?silent=true) - Self-hosting hardening follow-ups in [**Nftables rules for hardening Discourse installation**](https://meta.discourse.org/t/-/240591/5?silent=true) - Theme/customization debugging tips in [**Applying SEO settings to tags**](https://meta.discourse.org/t/-/352543/44?silent=true) - Old-browser UI tweaks in [**Dumbcourse – Old-browser friendly UI at /dumb**](https://meta.discourse.org/t/-/395104/28?silent=true) - Federation troubleshooting in [**ActivityPub Plugin**](https://meta.discourse.org/t/-/266794/477?silent=true) - Security notice + migration guidance in [**Sign-In with Ethereum plugin**](https://meta.discourse.org/t/-/231897/53?silent=true) - UI layering oddity report in [**Bug clicked on user profile then scrolled**](https://meta.discourse.org/t/-/398327/1?silent=true) - A grateful wrap-up in [**A praise for Discourse:**](https://meta.discourse.org/t/-/397851/7?silent=true) * * * ## Interesting Topics ### #Announcements - @Danielle announced a live session on building sustainable moderator programs in [**Webinar: Creating & Nurturing a Moderator Program**](https://meta.discourse.org/t/-/398295/1?silent=true), and confirmed a replay will be posted after the event for those who can’t attend live ([read more](https://meta.discourse.org/t/-/398295/3?silent=true)). - A GDPR-minded question surfaced about how analysis data is processed for the AI sentiment admin report; @awesomerobot clarified the answer depends on your AI provider/configuration in [**Introducing Discourse AI Sentiment Analysis: New Admin Report Available**](https://meta.discourse.org/t/-/355901/7?silent=true) ([read more](https://meta.discourse.org/t/-/355901/6?silent=true)). ### #community-building Building - Meta got a nostalgia-meets-migration roll call: @LotusJeff asked how long communities have been running and what platforms they migrated from in [**How Old is Your Forum?**](https://meta.discourse.org/t/-/398335/1?silent=true), sparking stories of decades-old forums and long migration journeys ([read more](https://meta.discourse.org/t/-/398335/5?silent=true)). ### #customization:plugin - A new WebRTC calling plugin landed: @derak introduced **peer-to-peer voice/video calls inside Discourse** (with optional TURN) in [**📞 diskuz Call – Voice and video calls inside Discourse (P2P, no external apps)**](https://meta.discourse.org/t/-/398331/1?silent=true) (installation background: [**How to install plugins in Discourse**](https://meta.discourse.org/t/-/19157/1?silent=true)). - The official signatures plugin picked up several long-requested admin controls (group restrictions, category display, “first post only”, stricter URL validation, etc.) after @jamie.wilson merged a PR into [**Discourse Signatures**](https://meta.discourse.org/t/-/42263/213?silent=true) ([read more](https://meta.discourse.org/t/-/42263/1?silent=true)). ### #Support - Admin workflows around banners changed: staff can no longer make **global banner topics** from **read-restricted categories** , and @dax suggested an interim “unlisted topic + Automation script” workflow in [**Can no longer create global banners from restricted categories**](https://meta.discourse.org/t/-/398306/2?silent=true). @isaac emphasized the underlying issue is inadvertent exposure of restricted content via banners ([read more](https://meta.discourse.org/t/-/398306/6?silent=true)). - Localization limitations for custom objects came up again: @nat corrected earlier guidance and shared the console-based approach for translating custom badge strings in [**How can badges and groups be localized (multilingual)?**](https://meta.discourse.org/t/-/398127/8?silent=true) (and why `/admin/customize/site_texts` won’t find keys that don’t exist yet). - Email-in reliability troubleshooting: a site using POP3 polling started throwing `Net::ReadTimeout` and stopped ingesting inbound messages in [**Discourse stopped polling my POP3 server**](https://meta.discourse.org/t/-/398324/1?silent=true) ([read more](https://meta.discourse.org/t/-/398324/1?silent=true)). - A new Discourse AI support question (in Chinese) asked about tool-call timeouts and whether Discourse timeouts can be configured in [**Discourse ai 的工具调用超时如何解决？是否可以调整discourse超时时间，如何调整？**](https://meta.discourse.org/t/-/398355/1?silent=true) ([read more](https://meta.discourse.org/t/-/398355/1?silent=true)). ### #bug - A fix shipped for category form-template selection: @awesomerobot merged a fix so multiple “Form templates” behave properly again in [**Multiple “Form templates” for a category doesn’t work**](https://meta.discourse.org/t/-/398176/4?silent=true) ([read more](https://meta.discourse.org/t/-/398176/1?silent=true)). - “Phantom notification” behavior popped up: @ice.d reported a notification badge that wouldn’t clear in [**Discourse states i have a notification**](https://meta.discourse.org/t/-/398328/1?silent=true), and @chapoi explained why these async edge cases can be “impossible-to-solve-properly” in the general case ([read more](https://meta.discourse.org/t/-/398328/5?silent=true)). - A scary draft + scheduled publishing sequence was reported to send the UI into a severe broken state (repeating header, unresponsiveness, browser pain) in [**Set Topic Timer May Result in Catastrophic Failure**](https://meta.discourse.org/t/-/398284/1?silent=true) ([read more](https://meta.discourse.org/t/-/398284/1?silent=true)). - Admin UI refresh inconsistency: newly created groups appear in category security selectors but not the “moderator group” dropdown until a reload, per [**Group drop downs are not refreshed correctly with new groups**](https://meta.discourse.org/t/-/398285/1?silent=true) ([read more](https://meta.discourse.org/t/-/398285/1?silent=true)). ### #customization:extras - The “Clip To Discourse” extension shipped **text selection clipping** (plus context-menu support and template customization) in [**‘Clip To Discourse’ Chrome Extension**](https://meta.discourse.org/t/-/392335/7?silent=true), with plans to adopt the Discourse User API authorization flow ([read more](https://meta.discourse.org/t/-/48536/1?silent=true)). ### #Dev - AI-assisted Discourse development got a reality check: @jrgong noted models need up-to-date guardrails for theme/plugin work in [**Claude & Discourse-related development. How good is it?**](https://meta.discourse.org/t/-/394773/12?silent=true), and @chapoi pointed to the developer docs now living in-repo ([read more](https://meta.discourse.org/t/-/394773/13?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Danielle drove signups for the upcoming moderation webinar and promised a recording shortly after the event in [**Webinar: Creating & Nurturing a Moderator Program**](https://meta.discourse.org/t/-/398295/3?silent=true) ([read more](https://meta.discourse.org/t/-/398295/1?silent=true)). - @dax explained the reasoning behind restricting banners sourced from private categories and proposed an interim workflow using an unlisted topic plus Automation scripting in [**Can no longer create global banners from restricted categories**](https://meta.discourse.org/t/-/398306/2?silent=true), then reiterated why Automation is needed when pin controls vanish on unlisted topics ([read more](https://meta.discourse.org/t/-/398306/11?silent=true)). - @isaac clarified the access-control risk: banners could unintentionally expose content from read-restricted categories, in [**Can no longer create global banners from restricted categories**](https://meta.discourse.org/t/-/398306/6?silent=true) ([read more](https://meta.discourse.org/t/-/398306/1?silent=true)). - @supermathie marked a support thread as effectively “unsupported browser behavior,” recommending modern browsers and explaining why deeper investigation isn’t viable in [**The three buttons that pop up after selecting text on a mobile browser do not work**](https://meta.discourse.org/t/-/397943/6?silent=true) ([read more](https://meta.discourse.org/t/-/397943/8?silent=true)). - @nat corrected prior instructions and provided the accurate console-based method for translating custom badge strings in [**How can badges and groups be localized (multilingual)?**](https://meta.discourse.org/t/-/398127/8?silent=true) ([read more](https://meta.discourse.org/t/-/398127/8?silent=true)). - @awesomerobot merged a fix for multiple form templates per category in [**Multiple “Form templates” for a category doesn’t work**](https://meta.discourse.org/t/-/398176/4?silent=true), asked for console evidence on a “Solved” UI lock report in [**How to understand the “Solved” locked status**](https://meta.discourse.org/t/-/398266/4?silent=true), and clarified AI sentiment compliance depends on provider/configuration in [**Introducing Discourse AI Sentiment Analysis**](https://meta.discourse.org/t/-/355901/7?silent=true). - @jamie.wilson merged a substantial feature/security hardening PR into the official signatures plugin in [**Discourse Signatures**](https://meta.discourse.org/t/-/42263/213?silent=true) ([read more](https://meta.discourse.org/t/-/42263/213?silent=true)). - @chapoi responded on two fronts: (1) explaining the practical complexity behind “stuck notification” edge cases in [**Discourse states i have a notification**](https://meta.discourse.org/t/-/398328/5?silent=true), and (2) pointing to upstream fixes for iPad/tablet UI issues in [**Ipad - Composer peek mode button causes editor to go off screen**](https://meta.discourse.org/t/-/396942/10?silent=true) and [**Opening TOC on iPad in portrait causes TOC to overlay text with no background**](https://meta.discourse.org/t/-/387532/5?silent=true). - @sam gave a clear technical boundary: replacing Markdown outright isn’t supported, and the path forward would be extending markdown-it in [**Can Markdown be replaced with Quarkdown**](https://meta.discourse.org/t/-/398341/2?silent=true) ([read more](https://meta.discourse.org/t/-/398341/2?silent=true)). - @martin confirmed a fix is in progress for solution-selection problems after topic merges in [**Cannot mark reply as “solution” after merger**](https://meta.discourse.org/t/-/398163/16?silent=true) ([read more](https://meta.discourse.org/t/-/398163/16?silent=true)). Yesterday’s energy had everything: communities reminiscing about 20+ year timelines while the rest of us debated banners, browsers, and bugs—classic Meta, vintage edition. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [14 maart 2026 om 13:03 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/769 "2026-03-14T13:03:00Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New topics (last 24h): 13** - **New posts (last 24h): 35** **Top users by recent activity (posts) and appreciation (likes):** | User | Posts | Likes | Notable recent contributions | | --- | --- | --- | --- | | @Falco | 4 | 15 | Expanded hosted LLM limits and model/token performance updates in [Announcements](https://meta.discourse.org/t/-/390985/12?silent=true) + quick diagnosis of Cloudflare/IP bans in [Support](https://meta.discourse.org/t/-/398408/3?silent=true) | | @LotusJeff | 3 | 7 | Shared long-term community growth insights (and survival tactics vs. social platforms) in [Community Building](https://meta.discourse.org/t/-/398335/13?silent=true) | | @Canapin | 3 | 3 | Helped troubleshoot logouts/IP bans in [Support](https://meta.discourse.org/t/-/398408/2?silent=true) and added context to “elder forum” history in [Community Building](https://meta.discourse.org/t/-/398335/12?silent=true) | | @supermathie | 2 | 4 | Tracked down a mail regression to a gem update (and the fix) in [Support](https://meta.discourse.org/t/-/393621/23?silent=true) and proposed a UX hint for multisite Sidekiq access in [Feature](https://meta.discourse.org/t/-/398415/1?silent=true) | | @merefield | 2 | 1 | Continued work on terminal-based Discourse tooling/localization in [Extras](https://meta.discourse.org/t/-/395285/22?silent=true) and chimed in on Quarkdown curiosity in [Dev](https://meta.discourse.org/t/-/398341/3?silent=true) | | @Ethsim2 | 2 | 1 | Raised nuanced admin/visibility questions about groups on `/about` in [Support](https://meta.discourse.org/t/-/398417/1?silent=true) and flagged doc/UI drift for Google PSE setup in [Integrations](https://meta.discourse.org/t/-/307107/13?silent=true) | | @satonotdead | 1 | 3 | Posted a practical “orphan uploads → DB records → rebake” recovery walkthrough in [Support](https://meta.discourse.org/t/-/152978/9?silent=true) | | @pacharanero | 1 | 3 | Published a step-by-step Discourse MCP + OpenCode CLI setup guide in [Users](https://meta.discourse.org/t/-/398378/1?silent=true) | | @pfaffman | 1 | 1 | Clarified display-name behavior and related settings in [Support](https://meta.discourse.org/t/-/398407/2?silent=true) | | @jmsachs | 1 | 1 | Reported a regression in showing username + real name after upgrading in [Support](https://meta.discourse.org/t/-/398407/1?silent=true) | **Other threads that also saw fresh movement:** chat settings disappearing after disabling chat ([Bug](https://meta.discourse.org/t/-/398401/1?silent=true)), the tablet floating-search oddities (reversed typing in [Bug](https://meta.discourse.org/t/-/398423/1?silent=true) and the uncloseable popover in [Bug](https://meta.discourse.org/t/-/398427/1?silent=true)), and a Bilibili inline player theme component announcement in [Theme component](https://meta.discourse.org/t/-/398438/1?silent=true). * * * ## Interesting Topics ### #Announcements - @Falco announced major capacity increases for Discourse’s hosted LLM service (bigger plan limits, updated open-weights model, higher max tokens, faster generation), with the new caps already live and reflected on customer dashboards ([details](https://meta.discourse.org/t/-/390985/12?silent=true)). ### #community-building Building - A long-running-community “roll call” turned into a mini playbook: @LotusJeff shared how a niche forum avoids “social media leaks” via deep archival know-how and a strong core, while @Canapin reflected on migrations from newsgroups/phpBB and the “multiple migration phenomenon” ([discussion](https://meta.discourse.org/t/-/398335/13?silent=true), plus context on migrations [here](https://meta.discourse.org/t/-/398335/12?silent=true) and the referenced older thread [read more](https://meta.discourse.org/t/-/383890/1?silent=true)). ### #users - A new guide walks through installing **Discourse MCP** into OpenCode CLI—framing the three-piece architecture (remote forum, local MCP server, and the client) and encouraging people to let an LLM help with the steps ([guide](https://meta.discourse.org/t/-/398378/1?silent=true)); it also cross-links to a companion setup for another client ([Codex CLI](https://meta.discourse.org/t/-/397662/1?silent=true)). ### #Support - A “why are we being logged out / IP blocked?” incident got a classic diagnosis: with Cloudflare in front, everyone can appear to come from the same IP, so banning one bad actor can effectively ban everyone—plus a reminder to use the Cloudflare template in `app.yml` ([problem report](https://meta.discourse.org/t/-/398408/1?silent=true), @Falco’s explanation [read more](https://meta.discourse.org/t/-/398408/3?silent=true)). - A hands-on recovery recipe landed for admins who migrated uploads (S3 → local filesystem) and ended up with `transparent.png` due to missing DB records: @satonotdead documented an approach to recreate `uploads` rows from on-disk files and then rebake posts ([walkthrough](https://meta.discourse.org/t/-/152978/9?silent=true)). - A staging upgrade to `2026.3.0-latest` surfaced a display-name mismatch: “username + real name” wasn’t appearing as expected, and @pfaffman pointed out the “same value” suppression behavior (and that there’s a setting to force both) ([report](https://meta.discourse.org/t/-/398407/1?silent=true), reply [read more](https://meta.discourse.org/t/-/398407/2?silent=true)). - A subtle permissions/visibility question explored how `about page hidden groups` interacts with `about page extra groups`, especially whether “hidden” should be absolute or conditionally visible to privileged viewers (e.g., admins) ([question](https://meta.discourse.org/t/-/398417/1?silent=true)). - A known email regression reappeared “in the wild”: @supermathie tied it to a merged gem update (with a specific breaking commit and a later fix) to help anyone who hit outbound mail failures after updating ([post-mortem + pointers](https://meta.discourse.org/t/-/393621/23?silent=true)). ### #contribute:feature - A UX improvement request argued that admins on a **multisite guest** who hit `/sidekiq` should get an explanatory hint rather than a confusing error—continuing a thread from an earlier discussion and leaning on the “law of least surprise” principle ([feature request](https://meta.discourse.org/t/-/398415/1?silent=true), prior context link [read more](https://meta.discourse.org/t/-/398397/7?silent=true)). - Private calendar ergonomics improved: @Falco noted authenticated ICS access work already in progress, then followed up with efforts to make user API key generation friendlier for non-technical users—bringing Discourse closer to “private RSS feed”-style usability for calendars ([update](https://meta.discourse.org/t/-/393203/4?silent=true)). ### #bug - Two tightly-related tablet/search issues were reported on [try.discourse.org](http://try.discourse.org): one where characters appear _reversed_ in the floating search widget in landscape mode ([bug report](https://meta.discourse.org/t/-/398423/1?silent=true)) and another where the floating search popover persists and can’t be closed after rotating back to portrait ([bug report](https://meta.discourse.org/t/-/398427/1?silent=true)). Both were reproducible even in [Safe Mode](https://meta.discourse.org/t/53504?silent=true) ([Safe Mode reference](https://meta.discourse.org/t/-/53504/1?silent=true)), and @Canapin proposed an interim workaround: _only search for palindromes_ ([quip](https://meta.discourse.org/t/-/398423/2?silent=true)). - A report in Chinese flagged that enabling AI translation can also translate **tags** into the user’s language and then make the localized tag content uneditable; @nat suggested enabling the **“Experimental tag settings page”** to edit those localizations ([report](https://meta.discourse.org/t/-/398440/1?silent=true), solution path [read more](https://meta.discourse.org/t/-/398440/2?silent=true)). - Disabling Chat appears to remove Chat preferences permanently (redirecting `/preferences/chat` back to `/latest`), and a responder confirmed reproducibility—referencing an older “once chat is disabled…” regression report ([new report](https://meta.discourse.org/t/-/398401/1?silent=true), reproduction note [read more](https://meta.discourse.org/t/-/398401/2?silent=true), earlier related topic [read more](https://meta.discourse.org/t/-/217271/1?silent=true)). ### #customization:theme component - A new **Bilibili inline player** theme component was shared as a “no rebuild” alternative to a server-side plugin approach, with a setup guide via the Themes UI and notes on fallback behavior for edge cases ([announcement](https://meta.discourse.org/t/-/398438/1?silent=true), comparison plugin link [read more](https://meta.discourse.org/t/-/389149/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco delivered a substantial upgrade announcement for hosted #ai LLM capacity/limits and model performance, including a clear plan-by-plan table of the new caps ([post](https://meta.discourse.org/t/-/390985/12?silent=true)). He also quickly identified a likely Cloudflare/IP-ban cause behind widespread forced logouts and suggested checking the Cloudflare template in `app.yml` ([support reply](https://meta.discourse.org/t/-/398408/3?silent=true)). On the calendar front, he shared progress on authenticated ICS feeds and improving User API Key ergonomics to make “private calendar feeds” feel as seamless as private RSS ([feature update](https://meta.discourse.org/t/-/393203/4?silent=true)). He additionally asked for clarification to narrow down an AI tool timeout question ([support follow-up](https://meta.discourse.org/t/-/398355/2?silent=true)). - @supermathie traced an outbound-email regression to a gem update (and pointed to the fixing commit), effectively serving as a same-day heads-up for anyone upgrading and suddenly losing mail delivery ([support update](https://meta.discourse.org/t/-/393621/23?silent=true)). He also proposed a UX improvement: when a multisite guest admin hits `/sidekiq`, Discourse should explain _why_ it’s unavailable instead of simply erroring, referencing earlier discussion context ([feature request](https://meta.discourse.org/t/-/398415/1?silent=true), earlier thread link [read more](https://meta.discourse.org/t/-/398397/7?silent=true)). - @nat responded to a bug report about AI translation affecting tag localizations, pointing admins to enable the experimental tag settings page so localized tag strings can be edited ([reply](https://meta.discourse.org/t/-/398440/2?silent=true)). * * * If today’s floating search box starts typing **gniht** instead of **thing** , it might be time to lean into yesterday’s wisdom and search for palindromes until the bug is squashed. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [15 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/770 "2026-03-15T13:02:25Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 53** - **New topics (last 24h): 4** — including: - Forum acquisition / importing content: [read more](https://meta.discourse.org/t/-/398452/1?silent=true) - Composer toolbar overflow (buttons hidden): [read more](https://meta.discourse.org/t/-/398473/1?silent=true) - Intermittent 500s uploading a theme via CLI: [read more](https://meta.discourse.org/t/-/398471/1?silent=true) - Attachment click counters missing: [read more](https://meta.discourse.org/t/-/398453/1?silent=true) **Top users by recent activity (posts) and appreciation (likes):** | User | Posts | Likes | | --- | --- | --- | | @Falco | 4 | 10 | | @Timelord | 5 | 4 | | @itsbhanusharma | 1 | 4 | | @darkpixlz | 4 | 4 | | @NateDhaliwal | 5 | 2 | | @satonotdead | 3 | 2 | | @chapoi | 2 | 2 | | @pfaffman | 1 | 2 | | @Canapin | 1 | 2 | | @LotusJeff | 2 | 1 | **Team shout-out:** Top posters in the **[@team](https://meta.discourse.org/groups/team?silent=true)** group were **@Falco** ([read more](https://meta.discourse.org/t/-/389820/24?silent=true)) and **@chapoi** ([read more](https://meta.discourse.org/t/-/398435/2?silent=true)). * * * ## Interesting Topics ### #Support - @Timelord asked how to _merge/import content from another Discourse site without a full restore_, and @itsbhanusharma pointed to the long-running “move topics between instances” guidance as a practical path forward ([read more](https://meta.discourse.org/t/-/398452/1?silent=true), plus the referenced how-to: [read more](https://meta.discourse.org/t/-/38930/1?silent=true)). - A regression (or at least a surprising behavior change) popped up around **attachment click counters** —uploaded files using the `|attachment` syntax weren’t showing counters, and now counters appear missing even when that part is removed ([read more](https://meta.discourse.org/t/-/398453/1?silent=true), follow-up discussion: [read more](https://meta.discourse.org/t/-/398453/2?silent=true)). - “How do I show images on the article front page?” got a very “use the right building block” answer: @chapoi suggested the **Topic List Thumbnails** theme component as the likely solution ([read more](https://meta.discourse.org/t/-/398435/2?silent=true), component: [read more](https://meta.discourse.org/t/-/150602/1?silent=true)). - A tricky auth/config edge case continued: disabling **local logins** could prevent new-user signup and surface console/log errors (including missing MaxMindDB files and OAuth `access_denied`)—with reproduction notes on a fresh install ([read more](https://meta.discourse.org/t/-/397895/14?silent=true)). - “Problems setting up Sentiment” resurfaced with questions about **backfilling older sentiment data** on self-hosted sites (#ai #ai-sentiment). @Falco clarified that the last **60 days** backfill automatically after enabling, but the thread continues with debugging questions for cases where that doesn’t appear to run ([read more](https://meta.discourse.org/t/-/309270/15?silent=true), staff answer: [read more](https://meta.discourse.org/t/-/309270/16?silent=true), continued troubleshooting: [read more](https://meta.discourse.org/t/-/309270/17?silent=true)). - Theme development tooling hit turbulence: an intermittent **500 error** while uploading a theme via CLI led to requests for logs, clarification about which tooling was being used, and eventual suspicion about a problematic plugin in the build (#themes). The thread includes log excerpts and advice to clean up/remove a noisy plugin while investigating ([read more](https://meta.discourse.org/t/-/398471/1?silent=true), request for logs: [read more](https://meta.discourse.org/t/-/398471/2?silent=true), log excerpt: [read more](https://meta.discourse.org/t/-/398471/7?silent=true), plugin caution: [read more](https://meta.discourse.org/t/-/398471/9?silent=true)). (Related references: theme CLI topic [read more](https://meta.discourse.org/t/-/82950/1?silent=true) and theme install guide [read more](https://meta.discourse.org/t/-/63682/1?silent=true)). ### #bug - On tablets, the **floating search widget** reportedly reversed typed character order (#search #tablet). @Falco couldn’t reproduce with a specific environment and suggested trying different keyboards, and the reporter later narrowed it to the “floating keyboard” feature and a particular IME configuration ([read more](https://meta.discourse.org/t/-/398423/1?silent=true), staff debugging question: [read more](https://meta.discourse.org/t/-/398423/3?silent=true), additional findings: [read more](https://meta.discourse.org/t/-/398423/5?silent=true)). ### #ux - A UX gotcha: when the **composer toolbar has many buttons** , later buttons become effectively invisible—responders noted it’s horizontally scrollable, but the gradient hint may be too subtle (#composer). The thread also points out similar affordance issues elsewhere in the UI ([read more](https://meta.discourse.org/t/-/398473/1?silent=true), suggestion to scroll: [read more](https://meta.discourse.org/t/-/398473/2?silent=true), gradient hint critique: [read more](https://meta.discourse.org/t/-/398473/3?silent=true)). ### #contribute:feature - Users asked to **display all likes/reactions on a post** , specifically how to expand “and N more…”. @Falco confirmed work is underway on a new UI component that would support this more cleanly ([read more](https://meta.discourse.org/t/-/389820/23?silent=true), staff update: [read more](https://meta.discourse.org/t/-/389820/24?silent=true)). - The long-running discussion about **SEO settings for tags** (#seo #tags) picked up again, with additional feedback proposing parallel fields for categories and major landing pages (Latest/Top/New): _UI title/description_ and _meta title/description_ ([read more](https://meta.discourse.org/t/-/352543/46?silent=true), recent “happens on fresh install” report: [read more](https://meta.discourse.org/t/-/352543/45?silent=true)). ### #Integrations - Discourse AI’s “Google Programmable Search / Custom Search API” guidance needs revisiting: Google discontinued a key feature, Vertex AI Search is too limited for broad replacement, and the team is researching new providers and potentially native web-search tools from major LLM platforms (#ai #how-to). > “Google discontinued this feature… Vertex is limited to a handful of domains, it is not a suitable alternative.” ([read more](https://meta.discourse.org/t/-/307107/15?silent=true)) ### #Marketplace - A practical “should I self-host?” thread continued with advice ranging from “I can install it for free” to “use a dashboard to run one-click upgrades,” plus reminders that managed Discourse hosting/services can reduce operational risk ([read more](https://meta.discourse.org/t/-/398340/5?silent=true), dashboard mention: [read more](https://meta.discourse.org/t/-/398340/8?silent=true), hosting/provider angle: [read more](https://meta.discourse.org/t/-/398340/9?silent=true), follow-up question on provider choice: [read more](https://meta.discourse.org/t/-/398340/11?silent=true)). ### #Theme\_component - **Banner Featured Links** got a compatibility refresh: swapping deprecated `htmlSafe` usage, updating for a new banner class, and a broader cleanup + tests. The maintainer shipped an update and pinned the TC to a newer core version ([read more](https://meta.discourse.org/t/-/327497/24?silent=true), maintainer update & changelog: [read more](https://meta.discourse.org/t/-/327497/27?silent=true)). ### #customization:plugin - In **Discourse OpenID Connect (OIDC)** (#openid-connect), a request resurfaced to sync Discourse groups with OIDC-provided groups/claims, citing an earlier PR that wasn’t pursued and asking whether it could be integrated ([read more](https://meta.discourse.org/t/-/103632/320?silent=true)). - The **Geo Blocking plugin** thread revisited Cloudflare considerations: @LotusJeff asked about Cloudflare headers, and @RGJ clarified what `CF-IPCountry` actually provides and noted the plugin relies on Discourse’s internal MaxMind database (plus pointing to Cloudflare best practices) ([read more](https://meta.discourse.org/t/-/227824/35?silent=true), clarification: [read more](https://meta.discourse.org/t/-/227824/36?silent=true), related guide: [read more](https://meta.discourse.org/t/-/293405/1?silent=true)). ### #Using\_Disourse - A question came up about the `/filter` feature: whether filters can be used “in category” while still keeping a left-side navigation experience like category menus / doc-style sidebars (#search #topic-filter) ([read more](https://meta.discourse.org/t/-/375558/19?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@Falco** focused on product direction + debugging across several threads: - **@chapoi** helped with practical “what component/setting do I need?” guidance: * * * _That’s a wrap—may tomorrow’s imports be smooth, your toolbars scroll sideways on the first try, and your search widgets type in the correct direction._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [16 maart 2026 om 13:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/771 "2026-03-16T13:01:45Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 33** - **New topics (last 24h): 3** — including discussions like the composer toolbar visibility on touch devices ([read more](https://meta.discourse.org/t/-/398473/4?silent=true)), a privacy question about proxy access ([read more](https://meta.discourse.org/t/-/398517/1?silent=true)), and embedding Bunny Stream videos ([read more](https://meta.discourse.org/t/-/398491/1?silent=true)). **Top users (posts + likes in the last 24h)** | User | Posts | Likes | Recent reference | | --- | --- | --- | --- | | @awesomerobot | 2 | 4 | Composer toolbar arrow behavior on touch devices ([read more](https://meta.discourse.org/t/-/398473/6?silent=true)) | | @Canapin | 3 | 3 | Requesting a better workflow for post edits / staff attention ([read more](https://meta.discourse.org/t/-/397606/50?silent=true)) | | @merefield | 2 | 3 | Advice on locking down a forum being mirrored via proxy ([read more](https://meta.discourse.org/t/-/398517/4?silent=true)) | | @Tealk | 1 | 2 | ActivityPub logs confirming repeated handle validation behavior ([read more](https://meta.discourse.org/t/-/266794/478?silent=true)) | | @chapoi | 1 | 2 | Root-cause analysis for missing counts in a Ghost theme outlet ([read more](https://meta.discourse.org/t/-/398418/4?silent=true)) | | @darkpixlz | 1 | 2 | Converting a post to wiki so the author can update it themselves ([read more](https://meta.discourse.org/t/-/397606/51?silent=true)) | | @amotl | 2 | 1 | Hosted CDN attachments missing after a hiccup ([read more](https://meta.discourse.org/t/-/398493/1?silent=true)) | | @Falco | 2 | 1 | Sentiment setup: checking the self-hosting guide + clarifying backfill ([read more](https://meta.discourse.org/t/-/309270/18?silent=true)) | | @renato | 3 | 1 | UX suggestion: show toolbar overflow affordance based on pointer type ([read more](https://meta.discourse.org/t/-/398473/7?silent=true)) | | @ばこん | 3 | 1 | “Someone else’s URL can access my forum” follow-up + resolution ([read more](https://meta.discourse.org/t/-/398517/5?silent=true)) | * * * ## Interesting Topics ### #ux - The composer toolbar overflow affordance came under scrutiny: @awesomerobot noted Discourse _hides_ the scroll arrow on touch devices and wondered if that assumption should change ([read more](https://meta.discourse.org/t/-/398473/6?silent=true)), while @renato suggested switching the logic to “show if a fine pointer is available” to avoid issues on touch-enabled laptops ([read more](https://meta.discourse.org/t/-/398473/7?silent=true)). - The same thread also turned into a debugging checklist: [safe mode](https://meta.discourse.org/t/53504?silent=true) showed the missing arrow for the OP, hinting at a theme/style interaction rather than core behavior ([read more](https://meta.discourse.org/t/-/398473/4?silent=true)) and confirming that reproduction depends on environment/device quirks ([read more](https://meta.discourse.org/t/-/398473/8?silent=true)). * * * ### #Support - A privacy/security concern: a user reported their forum could be accessed via “someone else’s URL” (proxy-style exposure) and asked how to prevent mirroring ([read more](https://meta.discourse.org/t/-/398517/1?silent=true)). The accepted guidance was pragmatic: go fully private if needed and ban accounts showing obvious “visit everything” scraping behavior ([read more](https://meta.discourse.org/t/-/398517/4?silent=true)). - A Ghost-theme-specific display issue: reply/view/activity counts disappeared _inside_ a category topic list when the category had **no subcategories** , due to the chosen rendering outlet not appearing in that context ([read more](https://meta.discourse.org/t/-/398418/4?silent=true)). The report included screenshots and narrowed the problem to an outlet selection tradeoff ([read more](https://meta.discourse.org/t/-/398418/3?silent=true)). - Hosted customers asked how to recover _individual_ missing CDN uploads (one image + two JSON attachments) after a hiccup, particularly when they’re comfortable self-hosting but unsure what options exist on hosted ([read more](https://meta.discourse.org/t/-/398493/1?silent=true); [read more](https://meta.discourse.org/t/-/398493/2?silent=true)). - Embedding video from Bunny CDN Stream: attempts to paste a Bunny “[player.mediadelivery.net](http://player.mediadelivery.net)” URL resulted in a plain link rather than an inline embed, prompting questions about allowed/whitelisted oneboxes and embedding rules ([read more](https://meta.discourse.org/t/-/398491/1?silent=true)). - Discourse AI tool calls timing out: a user shared screenshots showing tool execution timing out during script testing and asked whether Discourse’s timeout can be adjusted ([read more](https://meta.discourse.org/t/-/398355/3?silent=true); [read more](https://meta.discourse.org/t/-/398355/4?silent=true)). - Automation composer formatting: users trying to paste special markup like `[wrap]` into automation text fields found that rich-text pasting escapes content; @renato pointed out a fix that landed, while acknowledging the broader “rich editor vs plain markdown” expectation mismatch ([read more](https://meta.discourse.org/t/-/391347/10?silent=true)). - Sentiment setup and historical backfill: @Falco pointed users back to the self-hosting guide for Sentiment/Emotion ([read more](https://meta.discourse.org/t/-/309270/18?silent=true))—and the follow-up clarified that the dashboard works, but the community wants **more than 60 days** of backfill and needs to know how far back is feasible ([read more](https://meta.discourse.org/t/-/309270/21?silent=true)). For reference, the guide being cited is here: [read more](https://meta.discourse.org/t/-/334451/1?silent=true). * * * ### #Site feedback - Meta experimentation around “content gardening” doubled as a process question: @Canapin explained they often flag their own old posts to request edits, but after a previous staff edit the flag UI only offered “It’s illegal,” so they asked for a better path ([read more](https://meta.discourse.org/t/-/397606/50?silent=true)). @darkpixlz solved the immediate need by turning the post into a wiki so the author can update it directly ([read more](https://meta.discourse.org/t/-/397606/51?silent=true)). - That same exchange tied together several “knowledge curation” threads: @Canapin wanted to update their earlier post about monitoring uploads ([read more](https://meta.discourse.org/t/-/358635/2?silent=true)) to point at a relevant plugin and topic gallery tooling ([read more](https://meta.discourse.org/t/-/394953/1?silent=true)), and @darkpixlz noted staff-attention DMs can be replied to later since they tend not to close ([read more](https://meta.discourse.org/t/-/396989/1?silent=true)). * * * ### #customization:plugin - ActivityPub troubleshooting continued with confirmatory logs showing repeated `/webfinger/handle/validate` requests and a follow-up `find-by-handle` lookup, suggesting a consistent reproduction pattern across installs ([read more](https://meta.discourse.org/t/-/266794/478?silent=true)). - Topic Voting feature request: someone asked whether **advanced search** can be limited to “votable” areas and/or sorted by votes, referencing an older closed related question ([read more](https://meta.discourse.org/t/-/40121/316?silent=true); [read more](https://meta.discourse.org/t/-/272279/1?silent=true)). * * * ### #Self-Hosting - Cloudflare best practices got fresh field notes from a long-term proxy-mode setup: key takeaways included ensuring the Cloudflare template is in `app.yml`, bypassing cache for `/session/*`, and skipping WAF on post creation/edits—plus a nuanced WordPress-comment caching strategy to handle bursty traffic ([read more](https://meta.discourse.org/t/-/293405/28?silent=true)). * * * ### #customization:theme component - Topic List Previews (TLP) theme component: a user reported that visiting `/u/user/messages/tags/abc` was being auto-switched into a “tiles topic lists” display mode and asked how to keep **messages** on the default display instead ([read more](https://meta.discourse.org/t/-/209973/728?silent=true)). * * * ### #bug - Anchor links inside Discourse topics: @renato reported they can no longer reproduce the issue after a fix merged, and moved toward closing the report unless someone still experiences it ([read more](https://meta.discourse.org/t/-/397748/7?silent=true)). * * * ### #General - A “coding agents + SSH” anecdote: a community member described being emboldened as a Discourse admin by using coding agents to resurrect a long-dead vBulletin install—an interesting signal of how admin workflows are changing ([read more](https://meta.discourse.org/t/-/398120/2?silent=true)). * * * ### #users - Discourse MCP setup in OpenAI Codex CLI saw a brief update: a follow-up post was deleted by the author, leaving the thread without that additional context ([read more](https://meta.discourse.org/t/-/397662/2?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** investigated why the composer toolbar overflow arrow wasn’t visible and asked whether [safe mode](https://meta.discourse.org/t/53504?silent=true) showed it—strongly suggesting a theme/CSS interaction ([read more](https://meta.discourse.org/t/-/398473/4?silent=true)). They also clarified current intent: the arrow is intentionally hidden on touch devices because horizontal scrolling is “easier,” while openly questioning whether the UI should change to show it anyway ([read more](https://meta.discourse.org/t/-/398473/6?silent=true)). - **@chapoi** diagnosed the Ghost theme issue where views/replies/activity disappear inside certain category lists, pointing to the `topic-list-after-category` outlet not being available when there’s no category context, and noted they’d check whether an easy outlet switch exists ([read more](https://meta.discourse.org/t/-/398418/4?silent=true)). - **@Falco** supported a Sentiment/Emotion deployment by confirming whether the self-hosting setup guide was followed ([read more](https://meta.discourse.org/t/-/309270/18?silent=true)) and then pushed for clarification on what data range was actually backfilled so troubleshooting could proceed with clear expectations ([read more](https://meta.discourse.org/t/-/309270/20?silent=true)). - **@renato** weighed in on the composer toolbar affordance logic, proposing a refinement: show/hide the arrow based on _screen width_ or _fine pointer availability_, rather than the broad “touch device” rule ([read more](https://meta.discourse.org/t/-/398473/7?silent=true)). They also noted an anchor-link bug appears fixed and queued the topic for closure unless further reports come in ([read more](https://meta.discourse.org/t/-/397748/7?silent=true)), and confirmed an automation formatting/paste issue should be addressed by recent changes while acknowledging remaining UX tension ([read more](https://meta.discourse.org/t/-/391347/10?silent=true)). * * * _Sign-off:_ Yesterday’s meta moral: if your toolbar controls vanish, don’t panic—sometimes the missing arrow is just playing hide-and-seek until you flip into [safe mode](https://meta.discourse.org/t/53504?silent=true). ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [17 maart 2026 om 13:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/772 "2026-03-17T13:01:56Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 85 - **New topics (last 24h):** 12 **Top posters & most-liked (last 24h)** | User | Posts | Likes | | --- | --- | --- | | @das-g | 11 | 7 | | @chapoi | 7 | 9 | | @NateDhaliwal | 5 | 5 | | @sam | 4 | 4 | | @martin | 3 | 10 | | @dax | 3 | 4 | | @merefield | 3 | 4 | | @manuel | 3 | 3 | | @mae | 1 | 4 | | @RGJ | 1 | 3 | > Much of today’s momentum centered around _theme/component modernization_, _support category UX_, and _documentation category navigation_ — with concrete fixes and “what’s the right default?” discussions across [Dev](https://meta.discourse.org/t/-/398553/1?silent=true), [UX](https://meta.discourse.org/t/-/398616/1?silent=true), and [Announcements](https://meta.discourse.org/t/-/398338/1?silent=true). * * * ## Interesting Topics ### #Dev - @das-g tracked down why a legacy footer component started rendering template directives literally, and @chapoi tied it to ongoing modernization (including deprecations like `registerConnectorClass`) and advised refactoring around plugin outlets (e.g. `above-footer`) in [Templating of my “component” broke. How do I fix it?](https://meta.discourse.org/t/-/398553/1?silent=true) (see the deprecation nudge in-context at [post 7](https://meta.discourse.org/t/-/398553/7?silent=true), and related guidance referenced via [Plugin outlet modernization topic](https://meta.discourse.org/t/-/32727/1?silent=true) and the theme guides [here](https://meta.discourse.org/t/-/91966/1?silent=true) and [here](https://meta.discourse.org/t/-/93648/1?silent=true)). - A practical naming discussion emerged for making repos instantly recognizable as Discourse theme components (e.g. `discourse-tc-*`), with community conventions captured in [Is there a naming convention for theme component projects?](https://meta.discourse.org/t/-/398572/1?silent=true) (including @awesomerobot’s “not enforced, but often `discourse-`” in [post 2](https://meta.discourse.org/t/-/398572/2?silent=true) and a tidy three-way split from @RGJ in [post 5](https://meta.discourse.org/t/-/398572/5?silent=true)). - Theme devs revisited how to reference images shipped inside a theme component, clarifying that items in `assets/` count as uploads addressable via `settings.theme_uploads.*` in [How do I use images from assets in HTML of a Glimmer-based theme component?](https://meta.discourse.org/t/-/398578/1?silent=true) (with helpful cross-linking back to the older assets documentation topic [here](https://meta.discourse.org/t/-/62459/1?silent=true)). - A quick-and-clear workflow note landed on localization expectations for PRs: “handle English; robots/community translations get collated later,” in [If a PR needs localization what do we do?](https://meta.discourse.org/t/-/398585/2?silent=true) — plus a broader point from @sam about preferring dedicated Meta topics over doc comments for triage in [post 4](https://meta.discourse.org/t/-/398585/4?silent=true). - A small docs breakage got spotted and fixed: the Theme Directory / Component Directory links in the long-running quick reference stopped working, then were repaired after the report in [Theme Developer Quick Reference Guide](https://meta.discourse.org/t/-/110448/11?silent=true). ### #Announcements - Discourse introduced a smoother “Support category type” flow that auto-configures sensible defaults (and leverages #solved), making Q&A-style categories far easier to set up in [Easily create Support categories using the discourse-solved plugin](https://meta.discourse.org/t/-/398338/1?silent=true) (and it explicitly builds on the long-running [Discourse Solved plugin topic](https://meta.discourse.org/t/-/30155/1?silent=true)). - Chat power-users discussed what “pinning a chat message” really means over time (especially if chat history expires), in [Pin chat messages for increased visibility](https://meta.discourse.org/t/-/397571/10?silent=true). ### #blog - Discourse’s internal culture of writing (as a tool for thinking, alignment, and “ideas that survive pushback”) sparked reflection in the companion thread [How Discourse Is Becoming a Community of Writers](https://meta.discourse.org/t/-/398571/1?silent=true). ### #bug - A #solved-related UI snag resurfaced: once enabled, category-level “solved” controls couldn’t be disabled cleanly; @martin confirmed a fix is in motion (with a PR link) in [Unable to disable the solved feature for categories after it has been enabled](https://meta.discourse.org/t/-/398439/4?silent=true) (follow-up and PR reference in [post 5](https://meta.discourse.org/t/-/398439/5?silent=true)). - A report in Chinese noted that when Chat is disabled, its settings vanish; @sam acknowledged and queued investigation in [聊天功能被禁用后，其设置消失。](https://meta.discourse.org/t/-/398401/3?silent=true). - A “profile click then scroll” issue continued to get triage attention, with @sam immediately pushing for a safe-mode sanity check in [Bug clicked on user profile then scrolled](https://meta.discourse.org/t/-/398327/2?silent=true). ### #ux + #Site\_feedback - Meta’s documentation IA continues to evolve: a focused question asked whether clicking a documentation category should land on an index topic (vs. latest list), prompting thoughts about _scan-friendly navigation patterns_ and sidebar layouts in [What should the homepage be for doc categories?](https://meta.discourse.org/t/-/398616/1?silent=true). - Related: category box click behavior and “index link discoverability” remain under debate in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/56?silent=true), including whether index links are a workaround for gaps in the new docs experience and whether pinned index behavior differs per user in [post 59](https://meta.discourse.org/t/-/396306/59?silent=true) and [post 60](https://meta.discourse.org/t/-/396306/60?silent=true). - Category creation UX got another incremental improvement: admins can now set _title placeholders per category_, with @dax pointing to the core change in [More friendly category creation](https://meta.discourse.org/t/-/390841/19?silent=true) (also referenced again as “now in core” from a support angle in [Is it possible to change Topic Title prompt for a category?](https://meta.discourse.org/t/-/205219/4?silent=true)). ### #Support (and adjacent) - A self-host admin hit upload size confusion after editing `discourse.conf` inside the container (changes reverted on reboot), then discovered the “right place” is persistent config via `app.yml`; the thread includes the canonical pointer for correct configuration in [Maxmum upload size](https://meta.discourse.org/t/-/398601/1?silent=true) (with the practical fix link shared in [post 3](https://meta.discourse.org/t/-/398601/3?silent=true) to [Change the maximum attachment upload size](https://meta.discourse.org/t/-/26435/1?silent=true)). - A subtle URL normalization bug was reported: sidebar custom links can strip your internal hostname out of an _external_ URL’s query parameter, breaking redirects and specialized clients, in [Sidebar custom link strips internal hostname from query parameters of external URLs](https://meta.discourse.org/t/-/398537/1?silent=true). - Discourse Hub app users reported getting “stuck” in post-edit mode (save/close controls unresponsive) and needing to force quit; @chapoi started narrowing variables around iOS versions and cross-site reproducibility in [Unable to exit editing post](https://meta.discourse.org/t/-/398604/1?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @martin shipped a major usability win for admins: the new “Support” category type that auto-enables the right defaults for Q&A workflows in [Easily create Support categories using the discourse-solved plugin](https://meta.discourse.org/t/-/398338/1?silent=true) (which builds atop [Discourse Solved](https://meta.discourse.org/t/-/30155/1?silent=true)). He also confirmed an overlooked #solved UI issue and flagged an incoming fix/PR in [Unable to disable the solved feature for categories after it has been enabled](https://meta.discourse.org/t/-/398439/4?silent=true) with implementation notes in [post 5](https://meta.discourse.org/t/-/398439/5?silent=true). - @chapoi did a lot of hands-on developer support today: diagnosing theme-component breakage as part of Discourse’s Glimmer modernization and pointing to plugin-outlet-based approaches in [Templating of my “component” broke. How do I fix it?](https://meta.discourse.org/t/-/398553/7?silent=true). They also triaged an iOS editing lock-up report with targeted questions in [Unable to exit editing post](https://meta.discourse.org/t/-/398604/2?silent=true). Additionally, they followed up on theme/rendering issues for category counts with an update and PR reference in [Subcategories and Categories with no subcategories don’t show views/reply counts](https://meta.discourse.org/t/-/398418/7?silent=true). - @sam set expectations around localization workflow in [If a PR needs localization what do we do?](https://meta.discourse.org/t/-/398585/2?silent=true) and reinforced that _doc comments are hard to triage compared to dedicated topics_ in [post 4](https://meta.discourse.org/t/-/398585/4?silent=true). They also acknowledged two bug reports quickly — chat settings disappearing after disabling chat in [聊天功能被禁用后，其设置消失。](https://meta.discourse.org/t/-/398401/3?silent=true) and a “profile click then scroll” issue with a safe-mode check in [Bug clicked on user profile then scrolled](https://meta.discourse.org/t/-/398327/2?silent=true). - @dax connected shipping code to real-world admin needs: confirming that category-specific title prompts/placeholders are now in core (with commit reference) in [More friendly category creation](https://meta.discourse.org/t/-/390841/19?silent=true) and [Is it possible to change Topic Title prompt for a category?](https://meta.discourse.org/t/-/205219/4?silent=true). They also helped unblock banner workflows by making “Pin Topic” visible for unlisted topics in [Can no longer create global banners from restricted categories](https://meta.discourse.org/t/-/398306/15?silent=true). - @mae published the companion discussion for a blog post on Discourse’s writing culture in [How Discourse Is Becoming a Community of Writers](https://meta.discourse.org/t/-/398571/1?silent=true). - @supermathie solved an embedding issue by pointing to proper iframe usage and the `allowed iframes` setting in [Allow Embedded Video from Bunny CDN stream service](https://meta.discourse.org/t/-/398491/2?silent=true). - @manuel weighed in on documentation-category navigation and the “index topic vs. category landing page” experience, highlighting duplication and pinning behavior questions in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/58?silent=true), and continued the “best entry point” discussion in [What should the homepage be for doc categories?](https://meta.discourse.org/t/-/398616/2?silent=true). - @awesomerobot clarified there’s no enforced naming convention for theme components (while noting common team patterns) in [Is there a naming convention for theme component projects?](https://meta.discourse.org/t/-/398572/2?silent=true). - @mcwumbly continued hands-on iteration around the docs category UX and “clickable index links inside category boxes” behavior in [Updating how categories are organized on Meta](https://meta.discourse.org/t/-/396306/56?silent=true) and followed up in [post 59](https://meta.discourse.org/t/-/396306/59?silent=true); they also kicked off the focused follow-on about doc-category landing behavior in [What should the homepage be for doc categories?](https://meta.discourse.org/t/-/398616/1?silent=true). - @pmusaraj stayed in the weeds on federation and auth troubleshooting: asking for version details to debug ActivityPub actor discovery in [ActivityPub Plugin](https://meta.discourse.org/t/-/266794/479?silent=true), and continuing to diagnose Discourse ID signup issues (credentials regeneration and configuration review) in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/15?silent=true). * * * Sign-off: With support categories getting friendlier and theme components getting more Glimmer-modern, may today’s plugin outlets be clickable and your “solved” toggles stay solvable. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [18 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/773 "2026-03-18T13:02:49Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **In the last 24 hours** , Meta saw **98 new posts** across **12 new topics** , with a lot of energy around new tooling and moderation/ops workflows (e.g. [Discourse Suggested Edits](https://meta.discourse.org/t/-/398691/1?silent=true) and the new plugin build pipeline in [Introducing a new build system for plugins](https://meta.discourse.org/t/-/398713/1?silent=true)). ### Top users (posts / likes) | User | Posts | Likes | Recent activity | | --- | --- | --- | --- | | @Moin | 7 | 5 | Shared review-queue strategy using groups in [Force post approval for specific users only?](https://meta.discourse.org/t/-/398648/6?silent=true) | | @chapoi | 7 | 4 | Pointed to prior art on per-user moderation in [Force post approval for specific users only?](https://meta.discourse.org/t/-/398648/2?silent=true) | | @Falco | 6 | 3 | Followed up on ICS client compatibility in [Authenticated ICS feeds for private calendar events](https://meta.discourse.org/t/-/393203/7?silent=true) | | @itsbhanusharma | 3 | 6 | Suggested admin-side mitigation steps in [Dealing with a hacked user account should not require the console](https://meta.discourse.org/t/-/398627/4?silent=true) | | @sam | 3 | 5 | Announced an experimental plugin in [Discourse Suggested Edits](https://meta.discourse.org/t/-/398691/1?silent=true) | | @merefield | 3 | 3 | Clarified dev→prod boundaries in [What’s yall’s work-flow like?](https://meta.discourse.org/t/-/398655/3?silent=true) | | @das-g | 3 | 3 | Posted the working fix + commit trail in [Templating of my “component” broke. How do I fix it?](https://meta.discourse.org/t/-/398553/12?silent=true) | | @darkpixlz | 2 | 3 | Highlighted oddities in review-queue UX in [“Is this post something else or spam?”](https://meta.discourse.org/t/-/398686/2?silent=true) | | @Ethsim2 | 3 | 3 | Narrowed down Google Calendar behavior in [Authenticated ICS feeds for private calendar events](https://meta.discourse.org/t/-/393203/8?silent=true) | | @david | 1 | 3 | Detailed the modernization plan in [Introducing a new build system for plugins](https://meta.discourse.org/t/-/398713/1?silent=true) | * * * ## Interesting Topics #### #Self-hosting - @dccmuseum argued that **recovering a compromised account** shouldn’t require console access, while @itsbhanusharma outlined safer UI-level mitigation steps like deactivation/suspension in [Dealing with a hacked user account should not require the console](https://meta.discourse.org/t/-/398627/4?silent=true) ([read more](https://meta.discourse.org/t/-/398627/7?silent=true)). - A practical “what do you actually deploy?” thread: @beeburrt asked how people move changes from dev to production; @Falco emphasized using plugins/themes (not backups) with pointers to [Install plugins on a self-hosted site](https://meta.discourse.org/t/-/19157/1?silent=true) and [installing themes/components](https://meta.discourse.org/t/-/63682/1?silent=true) in [What’s yall’s work-flow like?](https://meta.discourse.org/t/-/398655/2?silent=true). - A Chinese-language upgrade report described admin UI breakage after updating to 3.5.3, then further trouble jumping forward; responders encouraged upgrading properly and checking `/logs` in [升级至v3.5.3之后管理员页面出现异常](https://meta.discourse.org/t/-/398634/1?silent=true) ([read more](https://meta.discourse.org/t/-/398634/7?silent=true)). * * * #### #Support - Per-user “always approve this person” isn’t built-in today, but the thread evolved into a deeper tour of approval triggers, groups, and workarounds—starting at [Force post approval for specific users only?](https://meta.discourse.org/t/-/398648/1?silent=true), with helpful side references to [Configuring automatic post review triggers](https://meta.discourse.org/t/-/328584/1?silent=true), [Discourse dynamic groups](https://meta.discourse.org/t/-/365342/1?silent=true), and the older plugin discussion at [Force specific users through moderation](https://meta.discourse.org/t/-/58179/1?silent=true). - A tricky sign-up failure investigation: after disabling plugins/components and testing safe-mode, @asc still saw 404s for sourcemaps and Sidekiq “can’t alloc thread” errors; @supermathie suggested this looked _system-level_ (RAM/limits/swap) in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/22?silent=true) ([read more](https://meta.discourse.org/t/-/397895/24?silent=true)). - Discourse AI timeouts: @Falco noted a **10s `read_timeout`** and asked whether the upstream API is slower, prompting a follow-up that the API can take 20–30 seconds in [Discourse ai 的工具调用超时如何解决？是否可以调整discourse超时时间，如何调整？](https://meta.discourse.org/t/-/398355/7?silent=true). - A new question asked how to connect Discourse AI to a self-hosted knowledge base / RAG pipeline in [Discourse ai 如何引入自建知识库RAG？](https://meta.discourse.org/t/-/398712/1?silent=true) (#ai). - A configuration confusion report: a user expected `skip_review_media_groups` to trigger review for image posts but observed no approval queue entry, raising questions about expectations vs. actual review rules in [Skip\_review\_media\_groups 这个配置不生效](https://meta.discourse.org/t/-/398690/1?silent=true). * * * #### #Dev - Discourse announced a modernized, mostly backward-compatible **build system for plugin JS** , bringing better caching and ES module output in [Introducing a new build system for plugins](https://meta.discourse.org/t/-/398713/1?silent=true) (#dev-news). - A theme-component dev thread closed out with a concrete working approach and a linked commit after a templating breakage in [Templating of my “component” broke. How do I fix it?](https://meta.discourse.org/t/-/398553/12?silent=true) ([read more](https://meta.discourse.org/t/-/398553/15?silent=true)). - A related theming question explored how to reference assets correctly from Glimmer-based theme component HTML; the accepted fix included key gotchas about template interpolation limitations in [How do I use images from assets in HTML of a Glimmer-based theme component?](https://meta.discourse.org/t/-/398578/5?silent=true). * * * #### #customization:plugin - A new official-but-experimental plugin proposal would let members **suggest edits** with reviewer-controlled diffs—aiming for a “Wikipedia-style” workflow without granting full edit permissions—in [Discourse Suggested Edits](https://meta.discourse.org/t/-/398691/1?silent=true) (#experimental). - A UI polish issue in the official calendar surfaced: on mobile, “extra text” appended to topic titles lacks the expected boxed styling, in [Discourse Calendar (and Event)](https://meta.discourse.org/t/-/97376/569?silent=true) (#calendar-and-event). * * * #### #ux - A small wording/UI clarity issue: the review flow asks “Is this post something else or spam?” with Yes/No buttons, which @peternlewis notes isn’t a sensible yes/no question; @darkpixlz added more review-queue UI weirdness in [“Is this post something else or spam?”](https://meta.discourse.org/t/-/398686/1?silent=true). * * * #### #bug - A long-running “can’t mark solution after merge” issue got a concrete fix: @davidb confirmed the patch is deployed via commit reference in [Cannot mark reply as “solution” after merger](https://meta.discourse.org/t/-/398163/19?silent=true) (#solved). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @sam shipped and documented a brand-new experimental plugin concept in [Discourse Suggested Edits](https://meta.discourse.org/t/-/398691/1?silent=true), requested actionable diagnostics for a split/merge 500 in [Bug when trying to split](https://meta.discourse.org/t/-/398678/2?silent=true), and connected the dots between policy and tooling in [Discourse documentation policy](https://meta.discourse.org/t/-/322621/2?silent=true). - @chapoi helped steer moderation expectations in [Force post approval for specific users only?](https://meta.discourse.org/t/-/398648/2?silent=true), nudged troubleshooting forward on a split/merge error in [Bug when trying to split](https://meta.discourse.org/t/-/398678/4?silent=true), and continued the tablet/table UX investigation with an implementation pointer in [Huge gap below tables on tablets](https://meta.discourse.org/t/-/333153/6?silent=true). - @david announced the modernization of plugin JavaScript builds (with performance and caching implications for hosts and developers) in [Introducing a new build system for plugins](https://meta.discourse.org/t/-/398713/1?silent=true). - @Falco pushed forward on calendar interoperability and troubleshooting steps (including checking `/logs`) in [Authenticated ICS feeds for private calendar events](https://meta.discourse.org/t/-/393203/9?silent=true), clarified expected dev→prod workflows in [What’s yall’s work-flow like?](https://meta.discourse.org/t/-/398655/2?silent=true), questioned upstream latency for AI tool calls in [Discourse ai 的工具调用超时如何解决？是否可以调整discourse超时时间，如何调整？](https://meta.discourse.org/t/-/398355/7?silent=true), and confirmed an embed-url bug was reproduced and fixed in [Should Discourse make an effort to become a viable comment platform?](https://meta.discourse.org/t/-/274455/69?silent=true). - @davidb confirmed a shipped fix for the solved-plugin edge case in [Cannot mark reply as “solution” after merger](https://meta.discourse.org/t/-/398163/19?silent=true). - @martin followed up on a quality-of-life improvement to simplify creating solved-enabled support categories in [Easily create Support categories using the discourse-solved plugin](https://meta.discourse.org/t/-/398338/3?silent=true) (#solved #categories). - @supermathie validated Discourse ID signups from their side and reframed errors as likely resource/limits issues (swap/RAM/threads) in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/24?silent=true) (#discourse-id). - @awesomerobot added corroboration (and noted reproducibility challenges) for an editing/composer lockup report in [Unable to exit editing post](https://meta.discourse.org/t/-/398604/6?silent=true) (#ios-app). - @pmusaraj kept the troubleshooting loop tight by requesting the suspected plugin link in [New users can’t sign up, 404 errors in console](https://meta.discourse.org/t/-/397895/20?silent=true). * * * Yesterday’s vibe: if you weren’t chasing a 500 error, you were probably refining the review queue—or polishing an ICS feed until Google Calendar finally agrees there are events. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [19 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/774 "2026-03-19T13:02:42Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 95** - **New topics (last 24h): 11** **Top contributors (posts / likes in the last 24h)** - **@Moin** — 18 posts / 22 likes - **@Arkshine** — 2 posts / 10 likes - **@pmusaraj** — 2 posts / 6 likes - **@awesomerobot** — 2 posts / 4 likes - **@chapoi** — 3 posts / 4 likes - **@zogstrip** — 2 posts / 4 likes - **@WaitroseCarpark** — 1 post / 4 likes - **@j.jaffeux** — 3 posts / 4 likes - **@mattdm** — 1 post / 3 likes - **@ChrisBeach** — 2 posts / 3 likes * * * ## Interesting Topics ### #Site feedback - @Moin and @manuel dug into why pinned topics may not “stick” and whether Discourse should _distinguish_ between “Automatically unpin topics” and “Default topics automatic unpin”, with follow-up on improving the wording and admin UX ([read more](https://meta.discourse.org/t/-/396306/62?silent=true)). Related: the deeper settings/wording discussion continues in [read more](https://meta.discourse.org/t/-/386365/7?silent=true) and older context around “automatically unpin” behavior was referenced here ([read more](https://meta.discourse.org/t/-/386255/9?silent=true)). - In the collaborative gardening hub experiment, @Moin and @NateDhaliwal asked for help closing out issues that are already tagged #fixed, as part of ongoing “tidy-up Meta” efforts ([read more](https://meta.discourse.org/t/-/397606/55?silent=true)). The “please close” list pointed at several threads, including [read more](https://meta.discourse.org/t/-/396807/1?silent=true), [read more](https://meta.discourse.org/t/-/398163/20?silent=true), [read more](https://meta.discourse.org/t/-/293324/1?silent=true), [read more](https://meta.discourse.org/t/-/397115/1?silent=true), and [read more](https://meta.discourse.org/t/-/397345/1?silent=true). ### #Announcements - The Discourse **Free plan beta** got a clarification: you _can_ make the whole site public or private, but you can’t run a public site with some private categories on Free (aside from the seeded Staff area) ([read more](https://meta.discourse.org/t/-/395632/35?silent=true)). - The “create Support categories using #solved” flow prompted translation + UX feedback: @Moin highlighted issues with forced lowercase (bad for German nouns) and ambiguous “auto close” wording, with @martin confirming fixes are planned (including restoring “after the last reply” clarity) ([read more](https://meta.discourse.org/t/-/398338/5?silent=true)). Background references included the formatting guidance ([read more](https://meta.discourse.org/t/-/324637/1?silent=true)), earlier lowercase side-effects on flag reasons ([read more](https://meta.discourse.org/t/-/325608/2?silent=true)), and related translation/admin-UI friction around settings discoverability ([read more](https://meta.discourse.org/t/-/396962/4?silent=true)). ### #ux - Moderation review-queue wording came under scrutiny: “Is this post something else or spam?” reads like it’s _always_ “Yes”, and the thread converged on using more generic, action-oriented phrasing when multiple flag types are combined ([read more](https://meta.discourse.org/t/-/398686/5?silent=true)). The discussion also connected to an older visual glitch report ([read more](https://meta.discourse.org/t/-/393403/1?silent=true)) and the lowercase-translation edge case mentioned above ([read more](https://meta.discourse.org/t/-/325608/2?silent=true)). - A self-hosting UX papercut: dismissing a persistent “advice” banner doesn’t _really_ dismiss it if the underlying condition remains—so it keeps returning after reload/new browser sessions ([read more](https://meta.discourse.org/t/-/398754/1?silent=true)). The “known behavior” explanation cited prior notes about planned “snooze” semantics ([read more](https://meta.discourse.org/t/-/329504/9?silent=true)). - RTL polish request: the “reply” icon under the user-profile menu isn’t using the RTL variant consistently, and a fix is already queued via a core PR ([read more](https://meta.discourse.org/t/-/398766/2?silent=true)). - Another translation/layout UX issue: German “Click to upload or drag & drop file” text overflows the placeholder area on some admin upload screens, prompting a request for line-breaking or smarter wrapping ([read more](https://meta.discourse.org/t/-/398782/1?silent=true)). - RTL positioning bug: when reactions are _hearts only_, the “who reacted” popup appears in the wrong place/direction compared to LTR behavior; other reaction mixes appear OK ([read more](https://meta.discourse.org/t/-/398793/1?silent=true)). ### #bug - A desktop UI glitch appears when clicking a user profile and then scrolling; @Arkshine suspects a CSS interaction (possibly in the chat plugin stylesheet) and provided reproduction evidence ([read more](https://meta.discourse.org/t/-/398327/14?silent=true)). - Chat on iOS/iPadOS continues getting attention: a fix PR for scrolling/member-list overflow got peer review, with follow-up testing and small adjustments reported ([read more](https://meta.discourse.org/t/-/398683/3?silent=true)). - Chat settings disappearing after disabling chat (reported in Chinese) was flagged as time-sensitive; @j.jaffeux indicated it should be fixed shortly and asked for confirmation if it persisted ([read more](https://meta.discourse.org/t/-/398401/11?silent=true)). - A long-running “can’t disable solved after enabling it for categories” bug reached the finish line: @martin noted the fix has now been merged ([read more](https://meta.discourse.org/t/-/398439/6?silent=true)). ### #Support - Discourse MCP + granular API keys hit a sharp edge: the MCP server fails validation because it can’t read `about.json` with scoped credentials, forcing users onto non-scoped “global” keys as a workaround ([read more](https://meta.discourse.org/t/-/398792/1?silent=true)). ### #contribute:feature - A Zulip integration improvement PR landed on Meta: terminology updates (“stream” → “channel”, “subject” → “topic”) plus per-thread topic mapping so each Discourse thread can map cleanly to a Zulip topic when left blank ([read more](https://meta.discourse.org/t/-/398789/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@pmusaraj** clarified Free-plan privacy constraints (site-wide public/private, but no private categories on public Free sites) in the Free plan beta thread ([read more](https://meta.discourse.org/t/-/395632/35?silent=true)), and also advised that “disabled” plugins may still run code—recommending fully removing suspect plugins from `app.yml` when debugging login issues ([read more](https://meta.discourse.org/t/-/397895/25?silent=true)). - **@awesomerobot** unpacked why the new review-queue “Yes/No” UX can be confusing when multiple flags are merged, and suggested switching to a more generic “Is there something wrong with this post?” copy for multi-flag situations ([read more](https://meta.discourse.org/t/-/398686/5?silent=true)). - **@zogstrip** confirmed fixes are coming for two UX issues: the missing RTL reply icon variant in the user menu ([read more](https://meta.discourse.org/t/-/398766/2?silent=true)) and German upload-helper text overflowing its placeholder in admin settings ([read more](https://meta.discourse.org/t/-/398782/2?silent=true)). - **@chapoi** reviewed and commented on an iOS/iPadOS chat scrolling/member-list overflow fix, noting it looked good and calling out a few additions they felt weren’t needed ([read more](https://meta.discourse.org/t/-/398683/3?silent=true)). They also pointed to a core fix for “huge gap below tables on tablets” ([read more](https://meta.discourse.org/t/-/333153/9?silent=true)) and merged a new “can’t see who liked a post anymore” request into the existing “display all likes/reactions” feature thread ([read more](https://meta.discourse.org/t/-/389820/27?silent=true)). - **@j.jaffeux** acknowledged and planned testing for the iOS/iPadOS chat scrolling fix ([read more](https://meta.discourse.org/t/-/398683/2?silent=true)), provided an imminent “should be fixed shortly” update for chat-settings disappearing after disabling chat ([read more](https://meta.discourse.org/t/-/398401/11?silent=true)), and clarified that pinned chat messages are _not_ destroyed ([read more](https://meta.discourse.org/t/-/397571/11?silent=true)). - **@manuel** explained the two different unpin-related site settings and questioned whether Discourse should keep them distinct or improve the descriptions for clarity ([read more](https://meta.discourse.org/t/-/396306/62?silent=true)); they also cross-linked the broader usability conversation about pinned-topic settings ([read more](https://meta.discourse.org/t/-/386365/7?silent=true)). - **@martin** confirmed a bugfix has been merged for disabling the #solved feature after enabling it for categories ([read more](https://meta.discourse.org/t/-/398439/6?silent=true)), and responded to feedback on the “Support categories with #solved” feature by agreeing to fix forced lowercase (to avoid broken translations) and to restore clearer “auto close after last reply” wording ([read more](https://meta.discourse.org/t/-/398338/6?silent=true)). - **@mcwumbly** closed a feature request as a duplicate and pointed to the canonical topic for restricted-category visibility of who has access ([read more](https://meta.discourse.org/t/-/131575/7?silent=true)); they also weighed in on the pinned-topic mystery, noting it was plausibly due to past manual actions or having read topics while auto-unpin was enabled ([read more](https://meta.discourse.org/t/-/396306/66?silent=true)). - **@sam** jumped into a “bug when trying to split” report to establish whether the affected site is hosted by Discourse or self-hosted—key triage info for next steps ([read more](https://meta.discourse.org/t/-/398678/5?silent=true)). _May your pinned topics stay pinned, your warnings learn how to snooze, and your moderation buttons never again answer “Yes” to a question that wasn’t asked._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [21 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/775 "2026-03-21T13:02:52Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 74** - **New topics (last 24h): 16** **Top users (posts / likes received in the last 24h)** _(Links go to a recent post from each user as a reference.)_ | User | Posts | Likes | Recent highlight | | --- | --- | --- | --- | | @david | 5 | 23 | Deprecations: [.js.es6](https://meta.discourse.org/t/-/398894/1?silent=true) and fixes for plugins ([read more](https://meta.discourse.org/t/-/398882/3?silent=true)) | | @Moin | 8 | 10 | Tracked an API key error down to a plugin ([read more](https://meta.discourse.org/t/-/398948/2?silent=true)) | | @Falco | 4 | 15 | Shipped new calendar subscription URLs ([read more](https://meta.discourse.org/t/-/398902/1?silent=true)) | | @LeoDavidson | 3 | 5 | Reported a plugin build issue and confirmed the fix ([read more](https://meta.discourse.org/t/-/398882/4?silent=true)) | | @markvanlan | 1 | 5 | Improved clarity for deeply nested thread “context view” ([read more](https://meta.discourse.org/t/-/398910/1?silent=true)) | | @gilles | 3 | 4 | Reported Android breakage tied to a theme component ([read more](https://meta.discourse.org/t/-/342277/76?silent=true)) | | @Don | 1 | 3 | Merged a fix for the F-NAV Android issue ([read more](https://meta.discourse.org/t/-/342277/77?silent=true)) | | @awesomerobot | 1 | 3 | Fixed awkward “Default LLM” duplication in AI UI errors ([read more](https://meta.discourse.org/t/-/398845/2?silent=true)) | | @ganncamp | 1 | 2 | Shared assignment API endpoint gotchas + solution ([read more](https://meta.discourse.org/t/-/398168/4?silent=true)) | | @satonotdead | 2 | 2 | Added to the nested replies testing chatter ([read more](https://meta.discourse.org/t/-/398826/7?silent=true)) | ## Interesting Topics ### #Announcements - Discourse introduced **calendar subscription URLs** so people can subscribe to forum-based reminders/events in external apps (Google/Apple/Outlook) via a new Preferences → Calendar tab ([read more](https://meta.discourse.org/t/-/398902/1?silent=true)). Related context: it builds on the #calendar-and-event ecosystem, including the [discourse-calendar plugin](https://meta.discourse.org/t/-/97376/1?silent=true), and comes alongside ongoing ICS export refinements ([read more](https://meta.discourse.org/t/-/378672/8?silent=true)) plus real-world event-creation gotchas ([read more](https://meta.discourse.org/t/-/383728/9?silent=true)). - The March “Current Projects” thread continued with questions about **how translations should be contributed** (Crowdin vs PR workflow), with a promise of follow-up from the team ([read more](https://meta.discourse.org/t/-/398565/7?silent=true)). ### #Dev - Discourse is **formally deprecating `.js.es6`** in themes/plugins and plans to remove support after the next ESR—migration is simply renaming files to `.js` ([read more](https://meta.discourse.org/t/-/398894/1?silent=true)). - Discourse is also **deprecating `.hbs` templates** , encouraging migration to `.gjs` for better tooling and future performance gains ([read more](https://meta.discourse.org/t/-/398896/1?silent=true)). For folks upgrading existing code, the team pointed to automation guidance ([read more](https://meta.discourse.org/t/-/368051/1?silent=true)). - A real-world “it broke after updating” report landed quickly: a plugin hit a **Rollup “Duplicate export” compile error** after upgrading to `2026.3.0-latest`, and a core fix was shipped and confirmed working ([read more](https://meta.discourse.org/t/-/398882/3?silent=true)). This also tied back into the broader shift described in the new plugin build system announcement ([read more](https://meta.discourse.org/t/-/398713/4?silent=true)). - A dev asked (in French) how to make **rich text “interpret” HTML instead of showing it** , and the guidance was effectively: _prefer Markdown_, because only a small subset of HTML is accepted/safe ([read more](https://meta.discourse.org/t/-/398919/2?silent=true)). ### #Nested Replies Testing - Work continued on making deeply nested conversations feel “lovely”: after ~10 nesting levels Discourse switches into a dedicated “context view,” and new styling aims to make that state **much more obvious** ([read more](https://meta.discourse.org/t/-/398910/1?silent=true)). The change was demonstrated against the ongoing nested replies mega-test thread ([read more](https://meta.discourse.org/t/-/398759/16?silent=true)). - The main nested-replies test thread also raised usability questions like whether a user’s **Top/New/Old sorting preference** can persist across visits ([read more](https://meta.discourse.org/t/-/398759/67?silent=true)). ### #contribute:feature - A feature request proposed a smoother **“Translate” affordance** (especially on mobile) and a cost-saving idea: **store AI translations** so the first translation can be reused instead of re-billing the API 100 times ([read more](https://meta.discourse.org/t/-/398950/1?silent=true)). This was linked to earlier discussion about saving AI translations for localization workflows ([read more](https://meta.discourse.org/t/-/397477/1?silent=true)). - For auth setups, a request asked for parity with OAuth2’s “email verified” toggle: admins want an option to **disable email verification when using OIDC** too ([read more](https://meta.discourse.org/t/-/398963/1?silent=true)). ### #Data & reporting - A new thread asked for Discourse’s **Data Processing Agreement (DPA)** and details on how contact data is stored, retained, and shared—community replies pointed toward existing legal/privacy pages and prior Meta discussion ([read more](https://meta.discourse.org/t/-/398913/1?silent=true); older reference: [read more](https://meta.discourse.org/t/-/88391/6?silent=true)). ### #Support - A self-hoster hit an **API key creation page exception** referencing `:dumbcourse_base_path`; troubleshooting quickly fingered the “dumbcourse” plugin, and removing it resolved the issue ([read more](https://meta.discourse.org/t/-/398948/3?silent=true)). The suspected plugin is discussed here ([read more](https://meta.discourse.org/t/-/395104/1?silent=true)). - On hosted (free) sites, admins debated what the dashboard label “ **last month** ” actually means: previous calendar month vs rolling last ~30 days. The thread includes evidence it behaves like a rolling window and suggestions that the label should reflect that more clearly ([read more](https://meta.discourse.org/t/-/398924/4?silent=true)). - Patreon integration got attention from two angles: a long-running request to **update the Patreon plugin to API v2** got an “I’ll take a stab next week” commitment ([read more](https://meta.discourse.org/t/-/386701/7?silent=true)), while a hosted customer reported Patreon group membership **not syncing** reliably (including a manual sync button that appears to do nothing) ([read more](https://meta.discourse.org/t/-/398944/1?silent=true)). ### #bug - A bug report showed that when an **Update** request fails, the **Update button duplicates** , quickly becoming “literally unusable” ([read more](https://meta.discourse.org/t/-/398947/1?silent=true)). - A Chinese-language bug report described a confusing flow where attempting to **permanently delete a post** before the 5-minute window elapses can result in the post appearing to **restore itself** , forcing a second delete + wait ([read more](https://meta.discourse.org/t/-/398938/1?silent=true)). - Another UX/bug papercut: when a user has a **post pending approval** , clicking “New Post” can trigger a **discard confirmation modal** , falsely implying the pending content will be lost. Others confirmed the confusion and suggested the UI needs refinement ([read more](https://meta.discourse.org/t/-/397711/2?silent=true)). ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco shipped the new **external calendar subscription URLs** experience (with one-click subscribe options) in #Announcements ([read more](https://meta.discourse.org/t/-/398902/1?silent=true)), and also gave quick feedback that the nested “detached thread” styling looks clear ([read more](https://meta.discourse.org/t/-/398910/2?silent=true)). On the integration front, @Falco committed to taking a run at the **Patreon API v2 update** next week and asked for testing credentials/process ([read more](https://meta.discourse.org/t/-/386701/7?silent=true)). - @david posted two major dev-facing notices: **deprecating `.js.es6`** in themes/plugins ([read more](https://meta.discourse.org/t/-/398894/1?silent=true)) and **deprecating `.hbs` templates** in favor of `.gjs`, including ESR timing expectations ([read more](https://meta.discourse.org/t/-/398896/3?silent=true)). @david also jumped on a breaking plugin build report and linked the fix that resolved the “duplicate export” error ([read more](https://meta.discourse.org/t/-/398882/3?silent=true)), then cross-referenced that resolution back in the broader plugin build system thread ([read more](https://meta.discourse.org/t/-/398713/4?silent=true)). - @markvanlan iterated on nested replies UX, adding **stronger “you are in context view” styling** to reduce confusion once threads get extremely deep ([read more](https://meta.discourse.org/t/-/398910/1?silent=true)). - @awesomerobot acknowledged an awkward AI-related UI error and linked the fix to remove redundant “Default LLM” wording ([read more](https://meta.discourse.org/t/-/398845/2?silent=true)). - @lindsey responded in the “Current Projects” roadmap thread about **translation contribution paths** and said they’re investigating the best approach and will follow up ([read more](https://meta.discourse.org/t/-/398565/7?silent=true)). > If yesterday taught us anything, it’s that even when the **daily summary bot misses its shift** ([read more](https://meta.discourse.org/t/-/291853/286?silent=true); see also [read more](https://meta.discourse.org/t/-/291852/1?silent=true)), Discourse still finds time to ship calendar feeds—and dive 10 levels deep into nested replies without getting lost. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [22 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/776 "2026-03-22T13:02:20Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 66** - **New topics (last 24h): 13** **Top contributors (posts / likes received in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @Moin | 8 | 15 | | @Falco | 6 | 11 | | @R23D_Printing | 1 | 7 | | @darkpixlz | 2 | 5 | | @GaurangBlaze | 1 | 4 | | @Heliosurge | 4 | 3 | | @newkid | 1 | 2 | | @Thomas_Rother | 3 | 2 | | @NateDhaliwal | 3 | 2 | | @nesges | 2 | 2 | **Themes that drove discussion today (with receipts):** - **Calendar exports & subscriptions** continued to get polished and debated in [calendar subscription URLs for external apps](https://meta.discourse.org/t/-/398902/2?silent=true), with several related feature threads pointing back to it (e.g. [iCal export & CalDAV](https://meta.discourse.org/t/-/312279/19?silent=true), [category-level ICS/GCal](https://meta.discourse.org/t/-/293972/4?silent=true), and [authenticated ICS feeds](https://meta.discourse.org/t/-/393203/11?silent=true)). - **Upgrades & admin resilience** popped up in threads like [low disk space during upgrades](https://meta.discourse.org/t/-/398989/1?silent=true) and “wait, did it update?” caching confusion in [dashboard shows the old version](https://meta.discourse.org/t/-/398990/1?silent=true). - **Translation UX** and “when to automate” was debated again in [Translate post with AI and save translation](https://meta.discourse.org/t/-/398950/3?silent=true). * * * ## Interesting Topics ### #customization:theme-component - @Moin spotted that **G-Translate** wasn’t packaged as an installable component (missing `about.json`) in [G-Translate - Fast and easy translate you entire Discourse Forum for free](https://meta.discourse.org/t/-/398973/4?silent=true), with @darkpixlz and @Heliosurge steering the author toward the proper structure and install expectations ([read more](https://meta.discourse.org/t/-/398973/7?silent=true)). - Rich Text Editor compatibility friction continues: @renato asked what functionality was _actually required_, and explained when Discourse prefers calling ProseMirror commands directly rather than parity via legacy APIs, in [Composer Button Bonanza](https://meta.discourse.org/t/-/352525/32?silent=true) (with follow-up about how missing fidelity affects the component: [read more](https://meta.discourse.org/t/-/352525/33?silent=true)). ### #customization:plugin - A new gamification plugin landed: @R23D_Printing introduced **time-limited daily check-in challenges** (hashtags/photos, leaderboards, automated posts, badges) in [Discourse Daily Challenges](https://meta.discourse.org/t/-/398980/1?silent=true) (#gamification), including install pointers back to the canonical [plugin install guide](https://meta.discourse.org/t/-/19157/1?silent=true). - A breaking change workaround was confirmed for Custom Wizard: after an update, `/admin/wizards` stopped loading, and setting `ROLLUP_PLUGIN_COMPILER=0` restored access in [Custom Wizard Plugin 🧙](https://meta.discourse.org/t/-/73345/931?silent=true), with the new build system context linked from [Introducing a new build system for plugins](https://meta.discourse.org/t/-/398713/2?silent=true) and the fix confirmed by the reporter ([read more](https://meta.discourse.org/t/-/73345/934?silent=true)). ### #announcements - Calendar subscription URLs shipped, but not without debate: users pushed back on showing **Google/Microsoft options** by default and asked for more granular feeds (e.g. filtering by group), while @Falco suggested CSS hiding and questioned whether group membership already scopes results in [Calendar subscription URLs for external calendar apps](https://meta.discourse.org/t/-/398902/3?silent=true) (and continued in [read more](https://meta.discourse.org/t/-/398902/7?silent=true)). Related “now solved” pointers were also dropped into older requests like [Calendar plugin should offer ical export and caldav](https://meta.discourse.org/t/-/312279/19?silent=true), [Category-level ICS/GCal link](https://meta.discourse.org/t/-/293972/4?silent=true), and [Authenticated ICS feeds for private calendar events](https://meta.discourse.org/t/-/393203/11?silent=true). - Setup UX win: @newkid reported the revamped flow was **“much easier than before”** , especially on mobile, in [Simplified category setup](https://meta.discourse.org/t/-/394971/27?silent=true). ### #contribute:feature - A pragmatic “make upgrades less scary” request: @GaurangBlaze proposed proactively detecting low disk space and offering a cleanup _before_ an upgrade starts, to avoid UI-breaking 500s and repeated image downloads in [Proposal to gracefully handle low disk space during a Discourse upgrade](https://meta.discourse.org/t/-/398989/1?silent=true). - AI translation UX trade-offs resurfaced: @Falco argued that the existing _topic-level automatic translation toggle_ is meant to avoid per-post “translation invocation” friction and duplicated API costs, while the OP wanted _intentional_ friction for a multilingual event in [Translate post with AI and save translation](https://meta.discourse.org/t/-/398950/3?silent=true) (continued: [read more](https://meta.discourse.org/t/-/398950/4?silent=true)). ### #Support - A post-upgrade surprise: @hellekin “lost” the banner-topic UI controls; @Moin traced it to banners in **private categories** and pointed to the known limitation/related thread in [I just upgraded to the latest tag, and lost banner topic!](https://meta.discourse.org/t/-/398976/1?silent=true), referencing [Can no longer create global banners from restricted categories](https://meta.discourse.org/t/-/398306/1?silent=true). - Provisioning hiccups: multiple users reported `id.discourse.com/create-site` stuck at “Almost there…” and then hitting “provisioned too many sites,” with one workaround suggestion being **try another browser** in [Got stuck when creating site](https://meta.discourse.org/t/-/398993/1?silent=true) ([read more](https://meta.discourse.org/t/-/398993/3?silent=true)). - Federation language weirdness: @Jagster reported ActivityPub publishes in the original language but the _linking UI_ appears in English, possibly tied to translations and/or client behavior, in [ActivityPub publish using original language but uses English for linking](https://meta.discourse.org/t/-/398996/1?silent=true). - Form templates validation gap: `required: true` works for most fields but seemingly **not for `upload`** , letting users submit without attachments in [Required: true not enforced for upload field in form templates](https://meta.discourse.org/t/-/398972/1?silent=true). ### #self-hosting - A migration edge case: @Wall-E asked about moving **only a group’s private inbox messages** to a new Discourse instance; @NateDhaliwal noted topic moves exist, but PMs likely require API/rails-console creativity in [Transfering inbox group messages to another instance?](https://meta.discourse.org/t/-/398971/1?silent=true). ### #ux - A small but sharp UI nit: @Moin found that tags (and votes) are visually “too low” in the composer’s _similar topics_ popup due to CSS margins, in [Tags are too low in similar topic pop up](https://meta.discourse.org/t/-/398986/1?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@Falco** spent time closing the loop on calendar export work and feedback: he suggested a CSS workaround for hiding corporate calendar options and pushed back on some workflow concerns in [Calendar subscription URLs for external calendar apps](https://meta.discourse.org/t/-/398902/3?silent=true) (plus follow-ups: [read more](https://meta.discourse.org/t/-/398902/7?silent=true)). He also pointed multiple older “calendar export” requests to the new implementation, e.g. [Calendar plugin should offer ical export and caldav](https://meta.discourse.org/t/-/312279/19?silent=true), [Category-level ICS/GCal link](https://meta.discourse.org/t/-/293972/4?silent=true), and [Authenticated ICS feeds for private calendar events](https://meta.discourse.org/t/-/393203/11?silent=true). Finally, he reiterated why Discourse prefers topic-level automatic translation toggles over repeated manual per-post AI calls in [Translate post with AI and save translation](https://meta.discourse.org/t/-/398950/3?silent=true). - **@j.jaffeux** weighed in on a confusing Chat report, challenging the premise (“this is not an issue you can have on your site…”) in the ongoing thread [聊天功能被禁用后，其设置消失。](https://meta.discourse.org/t/-/398401/13?silent=true), as troubleshooting continued around [safe mode](https://meta.discourse.org/t/53504?silent=true) and plugin enablement ([read more](https://meta.discourse.org/t/-/398401/14?silent=true)). - **@renato** clarified Discourse’s stance on rich editor APIs and when parity with old textarea-based abstractions is not guaranteed, recommending direct ProseMirror command usage for complex operations in [Composer Button Bonanza](https://meta.discourse.org/t/-/352525/32?silent=true). * * * Yesterday’s vibe: if your upgrade disk is full, your calendar feed is picky, and your translations are intentionally frictiony… at least your CSS can still start a lively debate. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [23 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/777 "2026-03-23T13:02:10Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours (2026-03-22 → 2026-03-23), Meta saw **63 new posts** across **8 new topics** , with most of the discussion clustering around update/ops reliability, UX polish, and plugin/theme edge cases (e.g. theme update checks in [this Support thread](https://meta.discourse.org/t/-/399003/1?silent=true) and self-hosting email/version-job debugging in [this report](https://meta.discourse.org/t/-/399014/1?silent=true)). - **Total new posts:** **63** - **Total new topics:** **8** **Top users (posts / likes received in the last 24h):** - **@Moin** — 7 posts / 13 likes - **@Richie** — 9 posts / 9 likes - **@david** — 3 posts / 8 likes - **@Quantic_Aether** — 2 posts / 3 likes - **@nesges** — 1 post / 3 likes - **@Lilly** — 1 post / 2 likes - **@Andrew_Rowe** — 2 posts / 2 likes - **@robbie.morrison** — 1 post / 2 likes - **@merefield** — 2 posts / 2 likes - **@Heliosurge** — 2 posts / 2 likes **Most-active / most-referenced threads (sampling):** - Theme git errors after updating to 2026.3.0-latest.1: [read more](https://meta.discourse.org/t/-/399003/1?silent=true) - Staff accounts + associated accounts visibility (and 2FA): [read more](https://meta.discourse.org/t/-/399045/1?silent=true) - Custom Wizard compiler/env var regression & fix path: [read more](https://meta.discourse.org/t/-/73345/935?silent=true) - Preloading/oneboxing and “leaking” host IP (proxy approaches): [read more](https://meta.discourse.org/t/-/399012/1?silent=true) - Missing “new version” emails & suspected `CallDiscourseHub` job failure: [read more](https://meta.discourse.org/t/-/399014/1?silent=true) - Mobile UX: add a grip bar to post admin actions menu: [read more](https://meta.discourse.org/t/-/399043/1?silent=true) - Topic Voting + tags punctuation edge case: [read more](https://meta.discourse.org/t/-/399039/1?silent=true) - Feature idea: wide-screen expand-table view for readers (#table-builder): [read more](https://meta.discourse.org/t/-/399034/1?silent=true) - ActivityPub / Mastodon auth scope suspicion: [read more](https://meta.discourse.org/t/-/398803/2?silent=true) - Post approval UX: discard confirmation modal + broader flow concerns: [read more](https://meta.discourse.org/t/-/397711/3?silent=true) - Skeleton compatibility pinning + future versioning strategy: [read more](https://meta.discourse.org/t/-/398985/2?silent=true) - Solved-categories announcement follow-up fix: [read more](https://meta.discourse.org/t/-/398338/10?silent=true) * * * ## Interesting Topics ### #Support - @Richie reported that **all themes/components started showing “Error cloning git repository” after upgrading to 2026.3.0-latest.1** , even though manual checks succeeded; suggestions ranged from rebuild attempts to GitHub rate limits/outages (with GitHub-status context noted by @david). [read more](https://meta.discourse.org/t/-/399003/1?silent=true) - @Richie asked why **“Associated Accounts” controls aren’t visible for staff accounts** , and the thread concluded it’s likely **hidden when staff have 2FA enabled** , with a pointer to the existing guidance. [read more](https://meta.discourse.org/t/-/399045/1?silent=true) - In the long-running Custom Wizard thread, users narrowed down an **env var naming gotcha** (`ROLLUP_PLUGIN_COMPILER` vs prefixed variants), while @david linked an upstream PR and warned the fallback won’t be around forever. [read more](https://meta.discourse.org/t/-/73345/935?silent=true) ### #Self-hosting - A privacy/security-focused self-hoster argued Discourse can **reveal the origin server IP** when fetching remote resources for previews/embeds; discussion explored proxy/plugin angles, but initial plugin settings didn’t prevent direct fetches in the reporter’s testing. [read more](https://meta.discourse.org/t/-/399012/1?silent=true) - A self-hosted admin reported **“new version” notification emails stopped** (despite settings enabled), and follow-up debugging suggested a failing `CallDiscourseHub` job with a Redis argument-type exception. [read more](https://meta.discourse.org/t/-/399014/1?silent=true) - Group inbox migration logistics came up again: one approach floated was **converting PMs to topics, moving, then converting back** , acknowledging potential workflow limitations. [read more](https://meta.discourse.org/t/-/398971/4?silent=true) ### #contribute:site-feedback - A small-but-annoying UI edge case: with #topic-voting enabled and **0 votes** , the vote indicator disappears and a **dangling comma appears after the last tag** ; investigation pointed at a customization that hid “0 votes,” and disabling themes restored expected layout. [read more](https://meta.discourse.org/t/-/399039/1?silent=true) ### #contribute:feature - A request proposed an **“expand-table” wide-screen viewer for regular users** (read-only), mirroring the author-only #table-builder full-width editor view—aimed at making markdown tables usable on laptops. [read more](https://meta.discourse.org/t/-/399034/1?silent=true) ### #ux - On mobile, @ondrej suggested adding the same **grip bar affordance** seen in topic admin actions to **post admin actions** as well, to make the sheet more obviously draggable. [read more](https://meta.discourse.org/t/-/399043/1?silent=true) ### #bug - A long-running #calendar-and-event “Uncaught (in promise)” report moved toward closure: @sam asked for clarity on what’s still broken, and the reporter replied with testing evidence suggesting FullCalendar is functioning across setups. [read more](https://meta.discourse.org/t/-/385342/26?silent=true) - ActivityPub troubleshooting continued: @sam flagged a Mastodon connection issue and suspected **OAuth now requires an explicit scope** in the payload, looping in the likely maintainers for ideas. [read more](https://meta.discourse.org/t/-/398803/2?silent=true) - The post-approval flow got another UX papercut: a **discard confirmation modal appears when clicking “New Post” if a post is pending approval** , and @sam emphasized the broader end-user experience can feel hostile without clearer queue visibility and expectations. [read more](https://meta.discourse.org/t/-/397711/3?silent=true) ### #Dev - A small process note: **theme/plugin skeleton compatibility pinning happened again** , and @david confirmed the team is moving to a **branch-based versioning strategy** and won’t run the old automated `.discourse-compatibility` process going forward. [read more](https://meta.discourse.org/t/-/398985/2?silent=true) - A versioning-strategy RFC thread gained more field feedback: a user reported they could install a specific branch, but **the UI update page didn’t detect newer updates** , complicating upgrade validation. [read more](https://meta.discourse.org/t/-/383536/61?silent=true) ### #Announcements - Follow-up in the “Support categories + discourse-solved” announcement: @martin dropped a link to the PR that **fixes the reported issues**. [read more](https://meta.discourse.org/t/-/398338/10?silent=true) - Calendar subscription URLs for external apps: feedback noted that **regenerating URLs after first reveal makes multi-device setup awkward** , and there was discussion about wanting community-specific feeds rather than combined output. [read more](https://meta.discourse.org/t/-/398902/9?silent=true) ### #Marketplace - A large migration request landed: **phpBB → Discourse** with ~ **870k posts** , **Hebrew RTL** , strict **SEO/301 redirect** requirements, and minimal downtime expectations. [read more](https://meta.discourse.org/t/-/399048/1?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@david** weighed in on the theme git-access errors, backing the theory that **GitHub rate limiting/outages** are likely culprits and pointing to GitHub’s recent incident history ([read more](https://meta.discourse.org/t/-/399003/17?silent=true)). He also advanced the Custom Wizard troubleshooting by linking an upstream fix PR and recommending migrating off the legacy compiler flag once patched ([read more](https://meta.discourse.org/t/-/73345/937?silent=true)). Additionally, he confirmed the team’s future approach on skeleton compatibility/versioning strategy changes ([read more](https://meta.discourse.org/t/-/398985/2?silent=true)). - **@sam** responded to the hard-to-reproduce theme update error reports with “try removing and re-adding” and called out the likelihood of environment-specific behavior or GitHub rate limiting ([read more](https://meta.discourse.org/t/-/399003/15?silent=true)). He also followed up on a #calendar-and-event console error report to verify whether anything is still broken ([read more](https://meta.discourse.org/t/-/385342/26?silent=true)), flagged a likely **OAuth scope requirement** in an ActivityPub/Mastodon connection issue ([read more](https://meta.discourse.org/t/-/398803/2?silent=true)), and pushed for a more humane, end-to-end UX for “post approval required” flows after a confusing discard modal report ([read more](https://meta.discourse.org/t/-/397711/3?silent=true)). - **@martin** posted a direct pointer to the fix PR for issues raised in the “Easily create Support categories using the discourse-solved plugin” announcement thread ([read more](https://meta.discourse.org/t/-/398338/10?silent=true)). _Sign-off:_ Between GitHub hiccups, compiler flags, and a surprise “favorite TV series” detour into **LG OLED evo** territory ([read more](https://meta.discourse.org/t/-/398826/11?silent=true)), Meta stayed delightfully unpredictable—here’s hoping tomorrow’s rebuilds take only one try. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [24 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/778 "2026-03-24T13:02:27Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 68 _(as seen across [Latest](https://meta.discourse.org/latest?silent=true))_ - **New topics (last 24h):** 14 _(as seen across [Latest](https://meta.discourse.org/latest?silent=true))_ ### Top users (posts + likes, last 24h) | User | Posts | Likes | Recent highlight | | --- | --- | --- | --- | | @awesomerobot | 3 | 14 | Clarified AI/semantic search messaging in a solved thread — [read more](https://meta.discourse.org/t/-/394348/13?silent=true) | | @Ivan_Rapekas | 3 | 11 | Released a theme component adding the #ai #ai-summarize button into the topic header/sidebar — [read more](https://meta.discourse.org/t/-/399069/1?silent=true) | | @Moin | 4 | 11 | Opened a PR to make “Restrict uploads” work via **groups** instead of trust levels — [read more](https://meta.discourse.org/t/-/112688/31?silent=true) | | @zogstrip | 3 | 9 | Confirmed a fix for “permanently delete” restore-state bug via core PR — [read more](https://meta.discourse.org/t/-/398938/2?silent=true) | | @Eilgnaw | 1 | 8 | Announced **Dexo** , a native iOS client for Discourse — [read more](https://meta.discourse.org/t/-/399129/1?silent=true) | | @david | 4 | 7 | Tracked “no new version emails” to a `redis` gem update and linked a fix — [read more](https://meta.discourse.org/t/-/399014/4?silent=true) | | @darkpixlz | 3 | 7 | Flagged issues in a plugin announcement and suggested the official skeleton — [read more](https://meta.discourse.org/t/-/399077/5?silent=true) | | @nathank | 4 | 6 | Weighed tradeoffs of App Store wrappers for PWAs in a forum app discussion — [read more](https://meta.discourse.org/t/-/398997/5?silent=true) | | @Arkshine | 2 | 5 | Shipped a quick UX fix for alias/title handling in Quote Callouts — [read more](https://meta.discourse.org/t/-/350962/53?silent=true) | | @pmusaraj | 5 | 5 | Investigated #activitypub verification failures (meta actor vs. other actors) — [read more](https://meta.discourse.org/t/-/399066/3?silent=true) | > “I’ve heard this feedback from a few different places now, so I’ve added a little messaging around it to clarify…” — @awesomerobot on search behavior changes ([source](https://meta.discourse.org/t/-/394348/13?silent=true)) **Also active (more threads worth a click):** - Topic Voting UI punctuation fix when votes = 0 and tags are present — [read more](https://meta.discourse.org/t/-/399039/6?silent=true) - Similar-topics popup tag positioning (#ux) — [read more](https://meta.discourse.org/t/-/398986/2?silent=true) - Discotoc floating Contents/Timeline buttons issue (#disco-toc) — [read more](https://meta.discourse.org/t/-/399082/1?silent=true) - Admin webhooks page layout + localization concerns — [read more](https://meta.discourse.org/t/-/399120/1?silent=true) - [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) configuration uncertainty on an inherited forum — [read more](https://meta.discourse.org/t/-/399081/1?silent=true) - A long-running search guide got pruned/updated, then selectively restored — [read more](https://meta.discourse.org/t/-/273328/23?silent=true) - Ongoing #dev-news thread: converting themes/plugins to `.gjs` — [read more](https://meta.discourse.org/t/-/368051/9?silent=true) - Self-hosting: cron-based auto-updates safety check-in (2026 edition) — [read more](https://meta.discourse.org/t/-/241232/6?silent=true) - Feature request: “pin” authoritative topics for certain search keywords — [read more](https://meta.discourse.org/t/-/281205/6?silent=true) - Self-hosting privacy: reducing IP leakage from preloading / fetching external resources — [read more](https://meta.discourse.org/t/-/399012/6?silent=true) - Bug: “required: true” not enforced for upload field in form templates (#form-templates) — [read more](https://meta.discourse.org/t/-/398972/2?silent=true) - Feature: ICS exports missing post URLs (#calendar-and-event) — [read more](https://meta.discourse.org/t/-/399015/2?silent=true) - Bug report (ZH): permanent-delete flow unexpectedly “restores” state — [read more](https://meta.discourse.org/t/-/398938/1?silent=true) - Support (FR): admin warning about `discourse.resolver-resolutions` in a third-party plugin — [read more](https://meta.discourse.org/t/-/399080/1?silent=true) - Marketplace: bulk-create + approve ~1,500 users via API (#Marketplace) — [read more](https://meta.discourse.org/t/-/399083/1?silent=true) * * * ## Interesting Topics ### #customization:theme component - @Noble_Fish spotted confusing duplicate callout entries when aliases share a Title, and @Arkshine quickly shipped a fix to filter the type list properly — [read more](https://meta.discourse.org/t/-/350962/51?silent=true) - @Ivan_Rapekas released **“AI Summary In Topic Header”** , a theme component that surfaces the Discourse AI summarize action in the topic’s right sidebar (desktop) and title area (mobile/narrow) (#ai #ai-summarize) — [read more](https://meta.discourse.org/t/-/399069/1?silent=true) - In “Restrict uploads”, @Moin shared a PR switching restrictions from trust levels to **groups** , making “subscriber-group-only uploads” much easier to model — [read more](https://meta.discourse.org/t/-/112688/31?silent=true) ### #customization:extras - @Eilgnaw introduced **Dexo** , a native iOS Discourse client (UIKit/Swift) featuring multi-forum management, HTML rendering, secure User API Key auth, and light/dark/system themes — [read more](https://meta.discourse.org/t/-/399129/1?silent=true) ### #customization:plugin - The “ImgLink” plugin announcement drew scrutiny: @Moin questioned “random/spammy tags” and broken links, and @darkpixlz removed tags and suggested starting from the official plugin skeleton — [read more](https://meta.discourse.org/t/-/399077/2?silent=true) - A long-running “Custom Wizard Plugin” thread got a notable update: @david said the fix was merged and asked maintainers to re-enable the rollup plugin compiler for verification — [read more](https://meta.discourse.org/t/-/73345/938?silent=true) ### #bug - “No new version emails” appears to have broken after a `redis` gem update (dating back to March 2025); @david linked the core PR addressing it — [read more](https://meta.discourse.org/t/-/399014/4?silent=true) - ActivityPub integration hit a Mastodon compatibility snag: Mastodon seemingly renamed `scope` to `scopes`; @pmusaraj proposed a fix and later confirmed meta-side resolution (#activitypub) — [read more](https://meta.discourse.org/t/-/398803/3?silent=true) ### #Support - A report about failing to connect Discourse ActivityPub actors suggests something specific to the **meta actor** (other actors worked in testing); @pmusaraj is still investigating and comparing cross-instance behavior (#activitypub) — [read more](https://meta.discourse.org/t/-/399066/3?silent=true) - @kirupa asked how to add custom links beneath the welcome banner; responses pointed to the “Banner Featured Links” component and potential plugin-outlet configuration mismatches after banner migrations — [read more](https://meta.discourse.org/t/-/399111/1?silent=true) - @joshhabka asked about MediaWiki-style `[[wikilinks]]` autocomplete in posts; discussion covered alternatives like standard markdown linking and Watched Words for auto-linking common phrases — [read more](https://meta.discourse.org/t/-/399075/1?silent=true) ### #contribute:feature - A request proposed **updating only themes/components** (without full core upgrades) to reduce admin friction and avoid rate limits when updating many components — [read more](https://meta.discourse.org/t/-/399055/1?silent=true) - A detailed #calendar-and-event request argues for **multiple `[event]` blocks per topic** so tentative times can all appear on the calendar during scheduling, rather than fragmenting discussions into one-event-per-topic — [read more](https://meta.discourse.org/t/-/293965/2?silent=true) ### #Data & reporting - @nathank shared a [Data Explorer](https://meta.discourse.org/t/32566?silent=true) query to list event invitees **including primary email addresses** , aimed at event follow-ups/reminders (#calendar-and-event #sql-query) — [read more](https://meta.discourse.org/t/-/399106/1?silent=true) ### #blog - Discourse published a new Discover roundup highlighting communities “where builders learn together,” with a companion discussion topic on meta — [read more](https://meta.discourse.org/t/-/399114/1?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot focused on UX polish and clearer messaging: they added explicit UI copy distinguishing “exact” vs semantic/AI-ish matches in search results feedback ([search thread](https://meta.discourse.org/t/-/394348/13?silent=true)), and confirmed a fix for a Topic Voting tag-list comma glitch ([topic-voting + tags](https://meta.discourse.org/t/-/399039/6?silent=true)). They also pointed to a fix for tags appearing too low in the “similar topics” popup ([UX report](https://meta.discourse.org/t/-/398986/2?silent=true)). - @zogstrip pushed multiple fixes forward by tying reports directly to core PRs: a “permanently delete” state bug report in Chinese ([bug report](https://meta.discourse.org/t/-/398938/2?silent=true)), “required: true” not being enforced for upload fields in form templates ([form-templates bug](https://meta.discourse.org/t/-/398972/2?silent=true)), and missing post URLs in ICS exports ([calendar feature](https://meta.discourse.org/t/-/399015/2?silent=true)). - @david handled a mix of diagnosis, guidance, and maintenance follow-through: they traced “no new version emails” to a `redis` gem change and linked the fix ([bug thread](https://meta.discourse.org/t/-/399014/4?silent=true)), advised that `.gjs` format updates should be done in a local dev environment ([dev-news thread](https://meta.discourse.org/t/-/368051/10?silent=true)), clarified a French admin-warning banner was caused by a third-party plugin and suggested uninstall/report-to-author ([support thread](https://meta.discourse.org/t/-/399080/2?silent=true)), and confirmed a Custom Wizard fix was merged plus requested retesting with rollup enabled ([custom wizard](https://meta.discourse.org/t/-/73345/938?silent=true)). - @pmusaraj spent time deep in #activitypub troubleshooting: they identified Mastodon parameter drift (`scope` → `scopes`) and proposed a plugin-side fix ([mastodon issue](https://meta.discourse.org/t/-/398803/3?silent=true)) before confirming it was resolved on meta ([follow-up](https://meta.discourse.org/t/-/398803/6?silent=true)). In a separate report, they noted failures seemed tied to the **meta actor** and compared behavior across instances/domains ([Discourse AP connection issue](https://meta.discourse.org/t/-/399066/3?silent=true)). - @sam performed doc gardening on “Searching for content effectively”: they removed stale discussion after cross-referencing current code ([doc update note](https://meta.discourse.org/t/-/273328/23?silent=true)), then restored previously deleted wiki content to unblock improvements and encouraged suggested edits to the OP ([restoration](https://meta.discourse.org/t/-/273328/25?silent=true)). * * * If yesterday taught us anything, it’s this: may your callout aliases stay tidy, your summarize buttons stay visible, and your ActivityPub “scopes” always be spelled correctly. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [25 maart 2026 om 13:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/779 "2026-03-25T13:01:55Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours (2026-03-24 → 2026-03-25), Meta kept busy across support, dev-news, and feature discussions—ranging from dev-container bootstrapping tips to UX polish and plugin releases (see activity in threads like [read more](https://meta.discourse.org/t/-/399187/1?silent=true) and [read more](https://meta.discourse.org/t/-/399144/1?silent=true)). - **New posts:** **91** - **New topics:** **9** **Top users (posts / likes received):** - **@Moin** — **12** posts / **17** likes (e.g. dev workflow guidance in [read more](https://meta.discourse.org/t/-/399187/2?silent=true), plus CSS theming pointers in [read more](https://meta.discourse.org/t/-/399156/12?silent=true)) - **@R23D_Printing** — **1** / **8** (new plugin announcement: [read more](https://meta.discourse.org/t/-/399190/1?silent=true)) - **@zogstrip** — **3** / **4** (bug triage + fixes: [read more](https://meta.discourse.org/t/-/398151/2?silent=true), [read more](https://meta.discourse.org/t/-/397622/2?silent=true)) - **@RGJ** — **3** / **4** (dev-news followups: [read more](https://meta.discourse.org/t/-/398896/4?silent=true), and plugin versioning clarification in [read more](https://meta.discourse.org/t/-/97376/573?silent=true)) - **@putty** — **2** / **4** (theme component maintenance: [read more](https://meta.discourse.org/t/-/326460/4?silent=true), [read more](https://meta.discourse.org/t/-/336150/11?silent=true)) - **@Squidgemonster** — **1** / **4** (UX idea on anonymous mode: [read more](https://meta.discourse.org/t/-/399144/1?silent=true)) - **@mcdanlj** — **2** / **4** (threading/nested replies feedback: [read more](https://meta.discourse.org/t/-/398759/69?silent=true)) - **@shortmort37** — **1** / **3** (PDF previews improvements: [read more](https://meta.discourse.org/t/-/157649/166?silent=true)) - **@pfaffman** — **4** / **3** (SSO/config clarification: [read more](https://meta.discourse.org/t/-/399081/4?silent=true)) - **@awesomerobot** — **2** / **3** (dev + docs updates: [read more](https://meta.discourse.org/t/-/399187/5?silent=true), [read more](https://meta.discourse.org/t/-/398306/18?silent=true)) **Quick link round-up (other threads with notable fresh replies):** - Nested Replies ongoing testing feedback: [read more](https://meta.discourse.org/t/-/398759/69?silent=true) - [Data Explorer](https://meta.discourse.org/t/32566?silent=true) API/query changes breaking tooling: [read more](https://meta.discourse.org/t/-/394388/3?silent=true) - Self-hosted mail receiver TLS/domain mismatch question: [read more](https://meta.discourse.org/t/-/49487/539?silent=true) - Auto-update via cronjob safety debate: [read more](https://meta.discourse.org/t/-/241232/7?silent=true) - Environment variable site settings question: [read more](https://meta.discourse.org/t/-/256210/3?silent=true) - “Hidden flagged content in raw URL” security/feature discussion: [read more](https://meta.discourse.org/t/-/350051/23?silent=true) - Open-source forum app discussion continues: [read more](https://meta.discourse.org/t/-/398997/9?silent=true) - “Guidelines vs FAQ” wording and navigation cleanup: [read more](https://meta.discourse.org/t/-/397938/8?silent=true) - Push notifications “it’s working again” mystery: [read more](https://meta.discourse.org/t/-/394149/8?silent=true) - Composer draft expectations & UX around “save draft” removal: [read more](https://meta.discourse.org/t/-/385291/22?silent=true) - Official Calendar plugin “version number” expectations now that it’s in core: [read more](https://meta.discourse.org/t/-/97376/570?silent=true) - Carousel mode sizing/linking questions: [read more](https://meta.discourse.org/t/-/392955/15?silent=true) * * * ## Interesting Topics ### #customization:plugin - @R23D_Printing announced **Discourse Member Application** (#discourse-member-application), a plugin to run a pre-invite application workflow at `/apply`, with admin review and automated invite links: [read more](https://meta.discourse.org/t/-/399190/1?silent=true). Related install/how-to references: [read more](https://meta.discourse.org/t/-/19157/1?silent=true) - In **Discourse Suggested Edits** (#experimental), @Moin reported missing notifications for suggesters/affected users, suggesting the notification flow may not match expectations: [read more](https://meta.discourse.org/t/-/398691/2?silent=true). This ties into broader composer/draft expectations raised elsewhere: [read more](https://meta.discourse.org/t/-/385291/22?silent=true) - A **Subscriptions** (#subscriptions) renewal/update error (“PaymentIntent does not have a payment method…”) was reported with Stripe + legacy supporter history, prompting discussion of cleanup/handling older billing states: [read more](https://meta.discourse.org/t/-/399179/1?silent=true). Prior related incident referenced for comparison: [read more](https://meta.discourse.org/t/-/336233/1?silent=true) * * * ### #Dev - A dev-container workflow snag—_email confirmation blocks first login without SMTP_—was resolved by pointing to `bin/rails admin:create`, improving the “first admin” bootstrap story for new contributors: [read more](https://meta.discourse.org/t/-/399187/1?silent=true). @awesomerobot also suggested using MailHog to “receive” dev mail without real SMTP config: [read more](https://meta.discourse.org/t/-/399187/5?silent=true) and the Docker dev guide was referenced in-thread: [read more](https://meta.discourse.org/t/-/102009/1?silent=true) - The ongoing **.hbs deprecation** (#dev-news) conversation continued as @RGJ flagged docs needing updates, and @david clarified timelines and added notes (including pointing people to [ask.discourse.com](http://ask.discourse.com) for help): [read more](https://meta.discourse.org/t/-/398896/4?silent=true). The “modernizing inline script tags” companion announcement was also updated to note the removal has now landed: [read more](https://meta.discourse.org/t/-/366482/49?silent=true) * * * ### #Support - A hosted/free provisioning block (“ **You have provisioned too many sites in the past hour** ”) turned out to be domain-related; staff asked for the domain value and the user confirmed switching domains resolved it: [read more](https://meta.discourse.org/t/-/399186/1?silent=true). - A new Free plan site owner couldn’t find where to configure auth/login and learned that **Discourse ID** handles social login on the free tier; they then reported an inability to enable it, triggering follow-up investigation: [read more](https://meta.discourse.org/t/-/399201/1?silent=true). The Free plan beta announcement was referenced as the baseline expectation: [read more](https://meta.discourse.org/t/-/395632/1?silent=true) * * * ### #ux - A thoughtful UX request proposed making **Anonymous Mode** (#anonymous-mode) more discoverable (e.g., from the composer) and adding clearer “you’re anonymous” affordances for switching back: [read more](https://meta.discourse.org/t/-/399144/1?silent=true). - @Moin reported that **Klipy** (#gifs) search results appear to repeat while scrolling (unlike Giphy’s finite scroll), asking whether Klipy can adopt similar “end-of-results” behavior: [read more](https://meta.discourse.org/t/-/399155/1?silent=true). - A theming question about moving a banner/image to the _very top_ ended with a practical CSS target (`.d-header .wrap`) and a pointer to the canonical “custom CSS changes” doc for step-by-step guidance: [read more](https://meta.discourse.org/t/-/399156/1?silent=true). Referenced resources: Brand Header component [read more](https://meta.discourse.org/t/-/77977/1?silent=true) and the custom CSS guide [read more](https://meta.discourse.org/t/-/168101/1?silent=true) * * * ### #Announcements - **Admin Reporting improvements** (#dashboard-reports #reporting) prompted confusion about why “Staff only” wasn’t available; clarification: it’s intentionally a simple **Everyone/No one** toggle because the reporting UI applies globally: [read more](https://meta.discourse.org/t/-/395768/23?silent=true). The broader “Upcoming changes” mechanism was referenced as context: [read more](https://meta.discourse.org/t/-/392894/1?silent=true) * * * ### #Site feedback - In the “collaborative content gardening” experiment, adding #fixed unexpectedly **re-opened an old closed topic** as a side-effect of automation—confirmed as unintended and slated for adjustment: [read more](https://meta.discourse.org/t/-/397606/60?silent=true). The reopened example topic was linked directly: [read more](https://meta.discourse.org/t/-/386370/4?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** helped smooth dev workflows by recommending MailHog for local email capture during development ([read more](https://meta.discourse.org/t/-/399187/5?silent=true)) and updated banner documentation to reflect that dismissible banners need public-category placement ([read more](https://meta.discourse.org/t/-/398306/18?silent=true); referenced doc: [read more](https://meta.discourse.org/t/-/153718/1?silent=true)). - **@zogstrip** drove multiple fixes/triage updates: acknowledging a bug report and proposing/confirming a fix for a sidebar “Update Discourse” oddity ([read more](https://meta.discourse.org/t/-/398151/2?silent=true)), noting an ignored-users/digest issue is covered by a PR ([read more](https://meta.discourse.org/t/-/397622/2?silent=true)), and clarifying that “Reporting improvements” is a global on/off (Everyone/No one) toggle ([read more](https://meta.discourse.org/t/-/395768/23?silent=true)). - **@chapoi** confirmed the #fixed-tag reopening behavior is _unintended_ and should be adjusted ([read more](https://meta.discourse.org/t/-/397606/62?silent=true)), and answered a Carousel Mode question: height is fixed by design; customization requires CSS ([read more](https://meta.discourse.org/t/-/392955/16?silent=true)). - **@pedro** followed up on a hosted provisioning limit report by asking for the exact domain value entered, helping isolate the trigger ([read more](https://meta.discourse.org/t/-/399186/3?silent=true)). - **@HAWK** acknowledged the same provisioning report and escalated it internally for review ([read more](https://meta.discourse.org/t/-/399186/2?silent=true)). - **@lindsey** documented a serious approval-queue UX issue where a discard modal can block posting broadly when a post is pending approval, plus shared investigation notes around where pending content appears ([read more](https://meta.discourse.org/t/-/397711/5?silent=true)). - **@gerhard** confirmed a translations/context issue should now be fixed, after reports that a “removed” label looked wrong ([read more](https://meta.discourse.org/t/-/395051/15?silent=true)). - **@david** updated dev documentation threads: adding guidance/notes around the `.hbs` deprecation and highlighting that [ask.discourse.com](http://ask.discourse.com) can help with smaller migrations ([read more](https://meta.discourse.org/t/-/398896/5?silent=true)), and announced that support for legacy inline script tags has been removed in the latest Discourse version ([read more](https://meta.discourse.org/t/-/366482/49?silent=true)). - **@martin** confirmed a fix for the “Enable form templates” targeting/sidebar issue has been merged ([read more](https://meta.discourse.org/t/-/398151/3?silent=true)). - **@sam** kept docs tidy by updating the Composer Popup Messages guide and removing outdated items ([read more](https://meta.discourse.org/t/-/317734/11?silent=true)). * * * If your day included a carousel that won’t resize, a dev inbox living at `localhost:8025`, and a mysteriously re-opened topic just because someone added #fixed… congratulations: you’ve basically experienced the full Meta variety pack. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [26 maart 2026 om 13:03 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/780 "2026-03-26T13:03:22Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 82** — conversation clustered around release visibility, UX details, and plugin/dev workflows (e.g. [read more](https://meta.discourse.org/t/-/399268/1?silent=true), [read more](https://meta.discourse.org/t/-/274455/70?silent=true), [read more](https://meta.discourse.org/t/-/49487/541?silent=true)). - **New topics (last 24h): 7** — including new support questions like hiding staff from `/about` ([read more](https://meta.discourse.org/t/-/399286/1?silent=true)) and making an “Announcements” category _effectively_ read-only on the free plan ([read more](https://meta.discourse.org/t/-/399298/1?silent=true)). **Top users (posts/likes in the last 24h, with an example jump-in):** | User | Posts | Likes | Reference | | --- | --- | --- | --- | | @Falco | 3 | 29 | Pointed to context on the “33 security fixes” discussion ([read more](https://meta.discourse.org/t/-/399268/2?silent=true)) | | @Moin | 11 | 18 | Suggested “require approval” as a free-plan workaround for read-only categories ([read more](https://meta.discourse.org/t/-/399298/2?silent=true)) | | @david | 3 | 13 | Explained the release comms change + raised the feedback internally ([read more](https://meta.discourse.org/t/-/399268/5?silent=true)) | | @merefield | 2 | 12 | Reacted to the release thread and noted the “AI getting some credit” angle ([read more](https://meta.discourse.org/t/-/399268/6?silent=true)) | | @zogstrip | 5 | 11 | Dropped PR links for bug fixes (example: whispers bumping) ([read more](https://meta.discourse.org/t/-/397588/2?silent=true)) | | @Ed_S | 4 | 10 | Raised concern about “stealth” security releases & missing Announcement pointers ([read more](https://meta.discourse.org/t/-/399268/1?silent=true)) | | @nathank | 10 | 10 | Walked through `/about` group-hiding mechanics and alternatives ([read more](https://meta.discourse.org/t/-/399286/4?silent=true)) | | @asc | 3 | 5 | Proposed weekly/interval-based check-ins for Daily Challenges plugin ([read more](https://meta.discourse.org/t/-/398980/2?silent=true)) | | @NateDhaliwal | 4 | 4 | Asked clarifying questions re: hiding users vs hiding groups on `/about` ([read more](https://meta.discourse.org/t/-/399286/5?silent=true)) | | @R23D_Printing | 3 | 4 | Confirmed feature interpretation and explored mod-level creation for challenges ([read more](https://meta.discourse.org/t/-/398980/3?silent=true)) | **More threads with fresh replies worth a glance:** - Translation tooling background jobs temporarily impacted string context features ([read more](https://meta.discourse.org/t/-/395051/17?silent=true)) - Watched-words auto-tagging fix reminder: “update when you are able” ([read more](https://meta.discourse.org/t/-/397601/7?silent=true)) - Reporting permissions still evolving (“Staff only” / “No one” options planned) ([read more](https://meta.discourse.org/t/-/395768/24?silent=true)) - Marketplace: paid request for Kajabi ↔ Discourse integration + migration ([read more](https://meta.discourse.org/t/-/399279/1?silent=true)) - Anonymous mode visibility mockups for composer + banner UI ([read more](https://meta.discourse.org/t/-/399144/2?silent=true)) - ActivityPub plugin version check-in from a running install ([read more](https://meta.discourse.org/t/-/266794/481?silent=true)) - Theme component maintenance chatter (“Classic About Statistics”) ([read more](https://meta.discourse.org/t/-/336150/13?silent=true)) - Theme component fix notes for prefilled composer link generator ([read more](https://meta.discourse.org/t/-/326460/7?silent=true)) - Plugin warning after update: discourse-formatting-toolbar needs code updates ([read more](https://meta.discourse.org/t/-/40649/194?silent=true)) - Horizon/UX: sticky category header tradeoffs discussed in the older thread too ([read more](https://meta.discourse.org/t/-/387267/5?silent=true)) - A “Modern Theme” March update landed with DM support and various UI fixes ([read more](https://meta.discourse.org/t/-/357665/42?silent=true)) - A longstanding “mail-receiver” how-to gained a Cloudflare/TLS deep dive + caveats ([read more](https://meta.discourse.org/t/-/49487/541?silent=true)) * * * ## Interesting Topics ### #Support - @Ed_S raised alarm that **`v2026.3.0-latest.1` shipped with “33 security fixes”** yet felt “stealthy” due to fewer Announcement pointers; @Falco linked background, and @david acknowledged the pain around visibility + said the feedback was raised internally ([read more](https://meta.discourse.org/t/-/399268/1?silent=true), [read more](https://meta.discourse.org/t/-/399268/2?silent=true), [read more](https://meta.discourse.org/t/-/399268/5?silent=true)). Follow-up context included the newly posted/backdated release pointers ([read more](https://meta.discourse.org/t/-/399301/1?silent=true), [read more](https://meta.discourse.org/t/-/399302/1?silent=true)) and references to older “dashboard advice” confusion ([read more](https://meta.discourse.org/t/-/390357/1?silent=true)) and version-notification oddities ([read more](https://meta.discourse.org/t/-/387639/28?silent=true)). - A site owner asked for a **built-in way to remove the default `@moderators` section from `/about`** (without CSS/theme work). The thread dug into what `about_page_hidden_groups` _actually_ hides, and how to keep staff access without listing everyone publicly (#about-page) ([read more](https://meta.discourse.org/t/-/399286/1?silent=true), [read more](https://meta.discourse.org/t/-/399286/6?silent=true)). A notable possible extension was using **dynamic group membership** to hide “trainee mods” as a set ([read more](https://meta.discourse.org/t/-/365342/1?silent=true)). - On the **free hosted plan** , @Naoshi wanted an “Announcements” category where only staff can create topics, but everyone can reply. @Moin suggested a pragmatic workaround: enable **approval for new topics** in that category and simply don’t approve non-staff topics (#free-plan #categories) ([read more](https://meta.discourse.org/t/-/399298/1?silent=true), [read more](https://meta.discourse.org/t/-/399298/2?silent=true)). ### #Self-Hosting - The long-running mail-receiver guide got a very practical Cloudflare-focused addendum: why **Cloudflare proxying blocks SMTP** , the need for a separate inbound-mail hostname, and how to do **Let’s Encrypt via DNS challenge** for TLS. The discussion also surfaced risks around exposing origin IPs when adding a DNS-only record ([read more](https://meta.discourse.org/t/-/49487/541?silent=true), [read more](https://meta.discourse.org/t/-/49487/546?silent=true), [read more](https://meta.discourse.org/t/-/49487/547?silent=true)). ### #customization:plugin - “Discourse Daily Challenges” drew feature requests for **non-daily intervals (e.g. weekly check-ins)** and letting **mods/category mods** create challenges instead of requiring admins. The back-and-forth clarified expectations like “1 entry per week across a month” and even referenced Calendar’s configurable week start (#gamification, tangentially) ([read more](https://meta.discourse.org/t/-/398980/2?silent=true), [read more](https://meta.discourse.org/t/-/398980/3?silent=true), [read more](https://meta.discourse.org/t/-/97376/1?silent=true)). - The **diskuz Call** plugin (P2P voice/video inside Discourse) got a strong +1, plus a request to consider **group calls / meetings** as a next step (#experimental-ish in spirit, even if not tagged that way) ([read more](https://meta.discourse.org/t/-/398331/2?silent=true)). ### #Dev - A long-awaited improvement landed: **an “icon type” SiteSetting** exists now. The thread quickly turned into “this will make updating theme components easier”, and it also connected to real-world fallout like FontAwesome icon availability and free/regular fallbacks (with the Reactions plugin cited as benefiting) ([read more](https://meta.discourse.org/t/-/370452/7?silent=true), [read more](https://meta.discourse.org/t/-/308408/6?silent=true), [read more](https://meta.discourse.org/t/-/370555/10?silent=true)). - Work continued on a **new build system for plugins** , with @david announcing a public talk at Ember Europe for those who want the architectural overview and rationale (#dev-news) ([read more](https://meta.discourse.org/t/-/398713/5?silent=true)). ### #bug - “Impossible to prevent [x.com](http://x.com) oneboxes (and they’re broken)” got a clear “will be fixed by PR” response, continuing the ongoing efforts to keep oneboxing reliable and configurable (#onebox) ([read more](https://meta.discourse.org/t/-/397516/2?silent=true)). - A new report: **Chat plugin fails to compile** when the rollup plugin compiler is enabled by default, with a concrete error trace pointing at `_assert is not a function` (#chat) ([read more](https://meta.discourse.org/t/-/399321/1?silent=true)). - “Whispers only temporarily bump topics” progressed toward a fix, while still surfacing a philosophical split: some want _any_ staff-visible activity to bump, others want no bump because “nothing happened” publicly (#whispers) ([read more](https://meta.discourse.org/t/-/397588/2?silent=true), [read more](https://meta.discourse.org/t/-/397588/5?silent=true)). ### #ux - The Horizon theme’s sticky category heading became a mobile pain point: what’s “lovely on desktop” can crowd the topic list on small screens. @chapoi noted it’s an unintended side-effect of keeping navigation visible, and invited others to investigate a cleaner solution (#horizon-theme #mobile #pr-welcome) ([read more](https://meta.discourse.org/t/-/387267/5?silent=true), [read more](https://meta.discourse.org/t/-/387267/6?silent=true)). ### #Community Building - In the long-running “comment platform viability” conversation, @Falco announced Discourse’s own blog comments were swapped over to a **new embedded-topic commenting system** , with early feedback already noting theme/padding/light-vs-dark mismatches and the plan to iterate via a theme component first ([read more](https://meta.discourse.org/t/-/274455/70?silent=true), [read more](https://meta.discourse.org/t/-/274455/71?silent=true), [read more](https://meta.discourse.org/t/-/274455/72?silent=true)). ### #Nested Replies Testing - More hands-on feedback landed in the “Testing Nested Replies on Meta” sandbox: users called out how notifications/flat view can make it hard to know which “nested chunk” a reply belongs to, and suggested adding “parent comment” affordances (LiveJournal-style) to improve orientation ([read more](https://meta.discourse.org/t/-/398759/72?silent=true), [read more](https://meta.discourse.org/t/-/398759/73?silent=true)). ### #Marketplace - A new paid request asked for a developer to integrate **Discourse with a Kajabi membership site** , including migration, tiered access automation, branding, and replacing Disqus-style comments—explicitly aiming for Facebook-like simplicity on the front-end while keeping Discourse power behind the scenes ([read more](https://meta.discourse.org/t/-/399279/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@Falco** helped contextualize the sudden “33 security fixes” concern and engaged on release visibility expectations ([read more](https://meta.discourse.org/t/-/399268/2?silent=true)), and also announced that Discourse’s blog comments are now running on a new embedded Topic-based system and invited feedback ([read more](https://meta.discourse.org/t/-/274455/70?silent=true)). - **@david** responded directly to the release-visibility feedback, apologized for the long-unnoticed email issue, and said the team is discussing adding Meta pointers back into Announcements; he also linked the newly posted/backdated release announcement topics ([read more](https://meta.discourse.org/t/-/399268/5?silent=true), [read more](https://meta.discourse.org/t/-/399268/10?silent=true), [read more](https://meta.discourse.org/t/-/399301/1?silent=true), [read more](https://meta.discourse.org/t/-/399302/1?silent=true)). He additionally shared a public talk slot about the plugin build system ([read more](https://meta.discourse.org/t/-/398713/5?silent=true)). - **@zogstrip** continued the “here’s the PR” style of bug-triage updates across multiple threads—whispers bumping behavior ([read more](https://meta.discourse.org/t/-/397588/2?silent=true)), [x.com](http://x.com) onebox breakage/config limitations ([read more](https://meta.discourse.org/t/-/397516/2?silent=true)), topic timer instability ([read more](https://meta.discourse.org/t/-/398284/2?silent=true)), and the discard-confirmation modal annoyance when approvals are involved ([read more](https://meta.discourse.org/t/-/397711/11?silent=true)). - **@gerhard** explained why translation context lookup could be temporarily degraded: a background job was running to backfill AI-generated context, expected to settle within about a day ([read more](https://meta.discourse.org/t/-/395051/17?silent=true)). - **@nat** posted a quick status update that the watched-words auto-tagging issue had already been fixed and encouraged updating when possible ([read more](https://meta.discourse.org/t/-/397601/7?silent=true)). - **@martin** noted an upcoming refinement to reporting/share options—adding clearer “Staff only” / “No one” choices since “Everyone” doesn’t map well to certain report behaviors ([read more](https://meta.discourse.org/t/-/395768/24?silent=true)). - **@chapoi** weighed in on the Horizon theme sticky heading issue, framing it as an unintended side effect of keeping navigation visible and inviting community PRs if someone can disentangle the containers cleanly ([read more](https://meta.discourse.org/t/-/387267/6?silent=true)). * * * _Yesterday’s Meta energy was peak “blink and you’ll miss it”: stealthy security-fix releases on one side, and shiny new embedded blog comments on the other—keep one eye on your dashboard and the other on the comment box._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [27 maart 2026 om 13:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/781 "2026-03-27T13:01:28Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 96** - **New topics (last 24h): 11** - **Top users (posts / likes in the last 24h)** > Activity snapshot is reflected across active threads like Discourse ID + HTTPS configuration discussions in #Self-hosting ([read more](https://meta.discourse.org/t/-/399376/1?silent=true)) and releases/distribution workflow feedback in #General ([read more](https://meta.discourse.org/t/-/399414/1?silent=true)). * * * ## Interesting Topics ### #Self-hosting - @darkpixlz hit a blocker enabling **Discourse ID** when `force_https` is disabled; @supermathie and @Falco reiterated the fix is getting the reverse proxy + HTTPS signaling correct so Discourse can generate valid redirect URIs ([read more](https://meta.discourse.org/t/-/399376/1?silent=true)). Related: an earlier Discourse ID redirect-URI edge case was also recently addressed ([read more](https://meta.discourse.org/t/-/396136/16?silent=true)). - A continuing discussion on deploying **older / pinned Discourse versions** turned into a practical guide (update `discourse_docker`, set `version`, rebuild), with @david clarifying that `version: esr` _should_ work and that changes belong in `containers/app.yml`, not `web.template.yml` ([read more](https://meta.discourse.org/t/-/399409/13?silent=true)). Background references: tracking branches overview ([read more](https://meta.discourse.org/t/-/17014/1?silent=true)) and beta-branch/tag history ([read more](https://meta.discourse.org/t/-/262063/1?silent=true)). - Self-hosted inbound email ops got an update: @LotusJeff revised Cloudflare guidance and discussed running **mail-receiver** separately to avoid exposing origin IPs ([read more](https://meta.discourse.org/t/-/49487/550?silent=true)). - A long-running hosting/security nuance resurfaced: someone troubleshooting why the **Security** UI shows Cloudflare IPs got a reminder to verify DNS/proxying and sometimes “remove/re-add domain” to re-trigger provisioning flows ([read more](https://meta.discourse.org/t/-/296601/7?silent=true)). * * * ### #General - Feedback landed on the shift toward **[releases.discourse.org](http://releases.discourse.org)** as the canonical changelog source: concerns about discoverability and readability turned into quick iteration—RSS was added and styling improvements are in-flight, with @david welcoming actionable UX feedback ([read more](https://meta.discourse.org/t/-/399414/1?silent=true)). Supporting refs shared in-thread include RSS discovery tips ([read more](https://meta.discourse.org/t/-/264134/1?silent=true)) and release notification options ([read more](https://meta.discourse.org/t/-/230675/1?silent=true)). * * * ### #ux - A tiny-but-real papercut: the **“champagne” emoji shortcode** doesn’t resolve even though the tooltip says “Champagne”; @Falco traced it to a mapping issue in discourse-emojis and suggested removing the conflicting alias entry ([read more](https://meta.discourse.org/t/-/399338/1?silent=true)). - On Meta specifically, **2FA inputs were left-aligned** (visually off compared to the rest of the login layout). @awesomerobot narrowed it down to the “login via email” path and linked the fix PR ([read more](https://meta.discourse.org/t/-/399333/2?silent=true)). * * * ### #Support - Clarification on **permanent deletion and attachments** : uploads tied to a permanently deleted post will be removed after `clean_orphan_uploads_grace_period_hours`, with caveats if anything else still references the file (avatars, emojis, site settings, etc.) ([read more](https://meta.discourse.org/t/-/399315/8?silent=true)). Deep dives referenced: permanent delete introduction ([read more](https://meta.discourse.org/t/-/207109/1?silent=true)), upload cleanup guidance ([read more](https://meta.discourse.org/t/-/248343/1?silent=true)), and historical quirks around auto-purging uploads ([read more](https://meta.discourse.org/t/-/51306/7?silent=true)). - A user asked why Meta “doesn’t notify” them anymore; @manuel pointed them to per-topic notification levels and global tracking preferences (e.g., set topics to **Watching** if you want every reply) ([read more](https://meta.discourse.org/t/-/399412/2?silent=true)). - A likely UX bug/validation mismatch: setting **Welcome Banner text color** via the picker saved without a leading `#`, then failed validation; workaround was to manually enter `#RRGGBB`, and it was suggested this might warrant a UX report ([read more](https://meta.discourse.org/t/-/399334/1?silent=true)). - New report: **Android app keyboard not appearing** when composing posts. @NateDhaliwal asked for version details and whether it reproduces in [safe mode](https://meta.discourse.org/t/53504?silent=true), while noting they couldn’t reproduce in Discourse Hub / Chrome ([read more](https://meta.discourse.org/t/-/399408/2?silent=true)). - Someone exploring the experimental **/filter** topic list syntax asked for boolean “OR” between category/tag constraints; replies confirmed it’s not supported today and suggested filing a feature request ([read more](https://meta.discourse.org/t/-/399383/1?silent=true)). Related docs: the original filter feature thread ([read more](https://meta.discourse.org/t/-/263641/1?silent=true)), search tips ([read more](https://meta.discourse.org/t/-/273328/1?silent=true)), and filter operator examples ([read more](https://meta.discourse.org/t/-/375558/1?silent=true)). * * * ### #bug - A theme/CSS rendering oddity: **tables without ``** are getting a header divider as if a `` existed (seen on Horizon + Meta). The report includes minimal HTML reproduction and explains why Markdown/CommonMark expectations differ ([read more](https://meta.discourse.org/t/-/399335/1?silent=true)). - Search UX friction continues: autocomplete can override intended `#category` input when mixing category+tag or tag+tag, and recent category organization changes may have made “simple category entry” harder on Meta ([read more](https://meta.discourse.org/t/-/294830/7?silent=true)). * * * ### #customization:plugin - The **Discourse Challenges** plugin shipped updates, then quickly hit a “create challenge = 500” report. The maintainer diagnosed a badge-name regression and requested logs while preparing fixes and clarifying required fields like existing Topic ID and tag entry format ([read more](https://meta.discourse.org/t/-/398980/9?silent=true)). - Long-running ecosystem note: the **Formatting toolbar** plugin maintainer expressed concern about ongoing compatibility and the sustainability of maintaining plugins/components as core evolves ([read more](https://meta.discourse.org/t/-/40649/195?silent=true)). * * * ### #Dev - Theme/component dev question: adding **avatar decorations/overlays from custom user fields**. The recommended approach was to reference examples of accessing custom user fields in theme components; prior art discussions around frames/overlays were also pointed out ([read more](https://meta.discourse.org/t/-/399394/1?silent=true)). References: accessing fields via a theme component example ([read more](https://meta.discourse.org/t/-/386594/1?silent=true)) and earlier avatar frame discussion ([read more](https://meta.discourse.org/t/-/318545/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @supermathie helped diagnose why Discourse ID requires HTTPS redirect URIs, emphasizing that `force_https` is about _assumption of scheme_ (not “serve on 443”), and the proxy must forward the right headers ([read more](https://meta.discourse.org/t/-/399376/2?silent=true)). - @Falco reinforced the pragmatic fix for Discourse ID enablement— **fix the reverse proxy/HTTPS setup first** —in the same thread ([read more](https://meta.discourse.org/t/-/399376/4?silent=true)); also flagged the emoji alias issue for `:champagne` and pointed to the exact constants mapping that likely needs removal ([read more](https://meta.discourse.org/t/-/399338/2?silent=true)). - @Falco weighed in on calendar/event workflows, pointing people to calendar subscription URLs as a near-term solution for staying synced across instances ([read more](https://meta.discourse.org/t/-/399329/2?silent=true)). - @awesomerobot investigated the misaligned 2FA UI, identified it as specific to the email-login flow, and linked the upstream fix PR ([read more](https://meta.discourse.org/t/-/399333/4?silent=true)). - @pmusaraj documented that Discourse now handles the “redirect URI already exists” Discourse ID setup issue by generating new keys when re-registering with the same redirect URI ([read more](https://meta.discourse.org/t/-/396136/16?silent=true)); and followed up on a Discourse ID alternate-email report requesting reproducible details/screenshots ([read more](https://meta.discourse.org/t/-/398181/2?silent=true)). - @david responded to changelog/release UX feedback: clarified that **Highlights are curated** (similar intent to old release notes), invited further actionable feedback, shipped an RSS feed for the releases site, and outlined ongoing styling work ([read more](https://meta.discourse.org/t/-/399414/3?silent=true)). - @david also clarified correct version-pinning mechanics for self-hosters: use `containers/app.yml`, not templates, and confirmed tags like `esr` are designed to work via `git checkout $version` ([read more](https://meta.discourse.org/t/-/399409/13?silent=true)). - @manuel helped a user regain expected notifications by pointing them to per-topic notification levels and the Preferences → Tracking page for global defaults ([read more](https://meta.discourse.org/t/-/399412/2?silent=true)). * * * Yesterday’s Meta managed to ship an RSS feed, debug a few login/layout mysteries, and still found time to debate why `:champagne` isn’t actually champagne—classic Discourse energy. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [28 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/782 "2026-03-28T13:02:22Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 71** (across ongoing discussions like the #customization:plugin thread on [Discourse Daily Challenges](https://meta.discourse.org/t/-/398980/24?silent=true) and new reports like [All plugins not functioning](https://meta.discourse.org/t/-/399466/1?silent=true)). - **New topics (last 24h): 12** (see list below). ### Top users (posts / likes in the last 24h) | User | Posts | Likes | | --- | --- | --- | | @david | 3 | 14 | | @eisammy | 7 | 14 | | @darkpixlz | 4 | 10 | | @R23D_Printing | 8 | 7 | | @ToddZ | 4 | 6 | | @Falco | 3 | 6 | | @patrickemin | 4 | 5 | | @codixer | 3 | 4 | | @RGJ | 1 | 4 | | @paco | 3 | 4 | ### New topics published (12) - #Praise: [Celebrating 2 years of my Instance :discourse:](https://meta.discourse.org/t/-/399423/1?silent=true) - #community-building\ Building: [Opinions on the forum I’ve built](https://meta.discourse.org/t/-/399434/1?silent=true) - #Bug: [Fix: Discourse renders as unstyled HTML in Facebook’s in-app browser on iPhone](https://meta.discourse.org/t/-/399440/1?silent=true) - #Feature: [Gif + texte dans le même message dans chat](https://meta.discourse.org/t/-/399428/1?silent=true) - #Support [Getting rid of the big red banner, how?](https://meta.discourse.org/t/-/399461/1?silent=true) - #Self-hosting: [All plugins not functioning](https://meta.discourse.org/t/-/399466/1?silent=true) - #Self-hosting: [Unstable software - constantly breaking update processes](https://meta.discourse.org/t/-/399468/1?silent=true) - #UX: [“reply to this message” goes nowhere?](https://meta.discourse.org/t/-/399477/1?silent=true) - #ux (tagged #horizon-theme): [Category creation floating box blocks out settings at the bottom](https://meta.discourse.org/t/-/399481/1?silent=true) - #community-building\ Building: [Eu tenho um fórum, mas não sei se ele está bem organizado o suficiente](https://meta.discourse.org/t/-/399483/1?silent=true) - #Bug: [Lost paragraphs / huge post due to HEIC upload](https://meta.discourse.org/t/-/399453/1?silent=true) - #Events: [About the Events category](https://meta.discourse.org/t/-/399439/1?silent=true) ## Interesting Topics ### #community-building:praise - @eisammy marked two years of community-building and learning-by-doing (including theme components and open-source experiments) in [Celebrating 2 years of my Instance :discourse:](https://meta.discourse.org/t/-/399423/1?silent=true), with a warm wave of congratulations following in [the replies](https://meta.discourse.org/t/-/399423/2?silent=true). ### #Support - A “big red banner” mystery turned into a _theme component health check_: @darkpixlz explained the banner indicates a broken component and pointed to [Chat Sidebar](https://meta.discourse.org/t/-/298829/1?silent=true), while @david strongly cautioned against hiding the warning with CSS in [Getting rid of the big red banner, how?](https://meta.discourse.org/t/-/399461/3?silent=true) (the component was then fixed, per the thread’s conclusion in [post 4](https://meta.discourse.org/t/-/399461/4?silent=true)). - An API edge-case is still seeking traction: @aangi asked for help with _granular API access_ not being able to read `about.json` in the #Support thread [API user with granular access cannot read about.json | Discourse MCP](https://meta.discourse.org/t/-/398792/1?silent=true). ### #bug - A crisp diagnosis (and quick upstream action): Facebook’s iPhone in-app browser was being mistaken for a crawler due to default UA matching, causing Discourse to render a “noscript/unstyled” view; @david responded with a core PR plan in [Fix: Discourse renders as unstyled HTML in Facebook’s in-app browser on iPhone](https://meta.discourse.org/t/-/399440/2?silent=true) after the detailed report in [post 1](https://meta.discourse.org/t/-/399440/1?silent=true). - A painful composer failure report: an HEIC upload error led to a reload and _no draft recovery_, wiping a long post-in-progress in [Lost paragraphs / huge post due to HEIC upload](https://meta.discourse.org/t/-/399453/1?silent=true). - Search UX got a concrete fix path: the long-running issue where autocomplete overrides the first choice (category+tag or tag+tag) received a “this should fix it” update from @davidb in [Autocomplete overrides first choice when searching for category + tag, or tag + tag](https://meta.discourse.org/t/-/294830/8?silent=true) (#search #hashtag-autocomplete). ### #contribute:feature - A chat UX limitation (GIF + text in the same message) was clarified as _long-standing behavior_ of the GIF component: @Falco confirmed history and reclassified accordingly in [Gif + texte dans le même message dans chat](https://meta.discourse.org/t/-/399428/4?silent=true). - Reviewable workflows raised a subtle but important question: the system DM text says “reply to this message,” but replies appear to go nowhere—prompting suggestions like notifying moderators or changing the copy in [“reply to this message” goes nowhere?](https://meta.discourse.org/t/-/399477/1?silent=true). - The #patreon plugin modernization continued: @Falco confirmed the API v2 work is testing well and added a custom user-agent idea for debugging in [Upgrade Patreon Discourse Plugin to API v2](https://meta.discourse.org/t/-/386701/11?silent=true) (and [follow-up](https://meta.discourse.org/t/-/386701/13?silent=true)). ### #Self-hosting - A site where “everything plugin-related stopped working” turned into likely CDN/CORS diagnosis: @darkpixlz suggested investigating CDN script errors (and testing with CORS tools) in [All plugins not functioning](https://meta.discourse.org/t/-/399466/2?silent=true), with the original symptoms described in [post 1](https://meta.discourse.org/t/-/399466/1?silent=true). - Reliability concerns for the web-based update path resurfaced: a self-hoster outlined repeated “random breakages” and asked about regression prevention in [Unstable software - constantly breaking update processes](https://meta.discourse.org/t/-/399468/1?silent=true), while @NateDhaliwal pointed to the stability tradeoff between `latest` and `esr` in [post 2](https://meta.discourse.org/t/-/399468/2?silent=true). (Related incident references: [upgrade abort / unicorn workers](https://meta.discourse.org/t/-/393003/1?silent=true) and a past migration breakage thread [migration error in rename discourse rewind](https://meta.discourse.org/t/-/393049/1?silent=true).) - Version pinning expectations were reinforced: @david helped troubleshoot YAML/parameter placement and clarified that downgrades aren’t supported (and ESR requires waiting for the next ESR release if you’ve advanced) in [Help deploying older versions of Discourse](https://meta.discourse.org/t/-/399409/19?silent=true). ### #ux - Admin UI polish request: the category-creation floating action box can obscure bottom settings, documented (with screenshots) in [Category creation floating box blocks out settings at the bottom](https://meta.discourse.org/t/-/399481/1?silent=true) (#horizon-theme). - The “FAQ → Guidelines” ecosystem cleanup continued: @mcwumbly aligned on updating docs and highlighted that opting in can be done via “Upcoming Changes” in [Review and update topics related to FAQ & Guidelines links](https://meta.discourse.org/t/-/397938/12?silent=true), with follow-up discussion about hidden settings in [post 14](https://meta.discourse.org/t/-/397938/14?silent=true). Helpful related reads: [Renaming FAQ to Guidelines](https://meta.discourse.org/t/-/395099/1?silent=true), [Using Hidden Site Settings](https://meta.discourse.org/t/-/308773/1?silent=true), and [Introducing Upcoming Changes…](https://meta.discourse.org/t/-/392894/1?silent=true). - Emoji data hygiene got a tiny but meaningful guardrail: @zogstrip added validation to avoid aliasing non-existent emojis in [Trivial observation about the champagne emoji](https://meta.discourse.org/t/-/399338/3?silent=true) (#emoji). ### #community-building\ Building - A forum design “show and tell” for a Resonite community drew praise plus actionable UI feedback (notably on mobile header links) in [Opinions on the forum I’ve built](https://meta.discourse.org/t/-/399434/1?silent=true) (see the mobile CSS note in [post 6](https://meta.discourse.org/t/-/399434/6?silent=true)). - A Portuguese-language “is my forum organized well?” thread surfaced practical IA tradeoffs (tags vs subcategories, homepage choice, issue metadata) in [Eu tenho um fórum, mas não sei se ele está bem organizado o suficiente](https://meta.discourse.org/t/-/399483/1?silent=true), with suggestions around onboarding and landing pages in [post 3](https://meta.discourse.org/t/-/399483/3?silent=true). (A referenced enhancement path included theme components like [Topic List Previews (TLP)](https://meta.discourse.org/t/-/209973/1?silent=true).) ### #General / #events / #customization:plugin (high-signal ongoing) - Brand + UX tweaks for Discourse’s own release tracking site continued: @derek noted feedback would inform an upcoming refresh in [Releases.discourse.org feedback & suggestions](https://meta.discourse.org/t/-/399414/9?silent=true). - Meta’s event hub got its “About” topic: @Danielle introduced what belongs in the category in [About the Events category](https://meta.discourse.org/t/-/399439/1?silent=true). - The #customization:plugin thread for challenges hit a migration snag and recovered: @R23D_Printing walked through missing DB columns and a path to resolution (including rebuild guidance and an update push) in [Discourse Daily Challenges](https://meta.discourse.org/t/-/398980/24?silent=true) through the “it works” confirmation in [post 34](https://meta.discourse.org/t/-/398980/34?silent=true). ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @david pushed back on “just hide the warning” instincts, emphasizing why broken-component banners are intentionally loud in [Getting rid of the big red banner, how?](https://meta.discourse.org/t/-/399461/3?silent=true). - @david also jumped quickly on a crawler-detection misfire affecting real users, replying with a core PR to improve default UA handling in [Fix: Discourse renders as unstyled HTML in Facebook’s in-app browser on iPhone](https://meta.discourse.org/t/-/399440/2?silent=true). - @david helped a self-hoster untangle version configuration and set expectations around downgrades/ESR timelines in [Help deploying older versions of Discourse](https://meta.discourse.org/t/-/399409/19?silent=true). - @Falco advanced the #patreon work, confirming a merge timeline and incorporating a better, identifiable plugin user-agent in [Upgrade Patreon Discourse Plugin to API v2](https://meta.discourse.org/t/-/386701/11?silent=true) and [post 13](https://meta.discourse.org/t/-/386701/13?silent=true). - @Falco clarified long-standing chat behavior and correctly re-scoped it as a feature discussion in [Gif + texte dans le même message dans chat](https://meta.discourse.org/t/-/399428/4?silent=true). - @derek acknowledged community feedback and tied it directly to upcoming brand/UX changes for [releases.discourse.org](http://releases.discourse.org) in [Releases.discourse.org feedback & suggestions](https://meta.discourse.org/t/-/399414/9?silent=true). - @mcwumbly guided the doc-refresh effort around Guidelines/FAQ, pointing to “Upcoming Changes” as the opt-in path and focusing the next steps on documentation updates in [Review and update topics related to FAQ & Guidelines links](https://meta.discourse.org/t/-/397938/12?silent=true). - @zogstrip tightened emoji data integrity by adding validation so aliases can’t be created for missing emojis in [Trivial observation about the champagne emoji](https://meta.discourse.org/t/-/399338/3?silent=true). - @chapoi answered a theme/layout question with a precise pointer to the right outlet (and linked learning material) in [I want to lower the header icons down into the top part of the main outlet](https://meta.discourse.org/t/-/392522/6?silent=true) (and the referenced tutorial: [Theme Developer Tutorial: Using Outlets](https://meta.discourse.org/t/-/357799/1?silent=true)). - @Danielle established the purpose of the Events category with the canonical category description topic in [About the Events category](https://meta.discourse.org/t/-/399439/1?silent=true). - @davidb linked a concrete fix PR for search autocomplete behavior in [Autocomplete overrides first choice when searching for category + tag, or tag + tag](https://meta.discourse.org/t/-/294830/8?silent=true). _Yesterday, meta featured everything from dancing “challenge solved” celebrations to big red banners getting defused the right way—may your migrations be smooth and your components forever unbroken (or at least loudly warning you when they are)._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [29 maart 2026 om 13:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/783 "2026-03-29T13:01:22Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **Last 24 hours (2026-03-28 → 2026-03-29)** - **New posts:** 46 - **New topics:** 6 **Top contributors (posts / likes received)** | User | Posts | Likes | | --- | --- | --- | | @ToddZ | 5 | 1 | | @Lilly | 4 | 3 | | @NateDhaliwal | 4 | 2 | | @merefield | 3 | 4 | | @Steven | 3 | 3 | | @awesomerobot | 2 | 5 | | @ferdnyc | 2 | 3 | | @stephtara | 1 | 3 | | @supermathie | 1 | 2 | | @canbekcan | 1 | 2 | **Also seeing fresh replies / ongoing threads worth a look:** - Category thumbnails & aspect ratio concerns continued in [Tiny category image](https://meta.discourse.org/t/-/380837/4?silent=true) (with a CSS workaround pointed out in [follow-up](https://meta.discourse.org/t/-/380837/5?silent=true)). - Plugin maintenance talk kept rolling in [Formatting toolbar](https://meta.discourse.org/t/-/40649/197?silent=true) and the maintainer clarified plans in a later reply ([read more](https://meta.discourse.org/t/-/40649/199?silent=true)). - Theme-component longevity got a quick check-in at [MD Topic List Mobile component](https://meta.discourse.org/t/-/146341/66?silent=true). - A quick celebratory note landed in [Celebrating 2 years of my Instance :discourse:](https://meta.discourse.org/t/-/399423/3?silent=true). - A plugin upgrade warning popped up for [Landing Pages Plugin](https://meta.discourse.org/t/-/180967/157?silent=true). * * * ## Interesting Topics ### #Support - @awesomerobot agreed it’s reasonable that granular API access should be able to read `about.json`, and noted a PR was opened for review in **“API user with granular access cannot read about.json”** (#mcp) — [read more](https://meta.discourse.org/t/-/398792/3?silent=true). The thread also dug into whether the current error messaging is misleading, with @supermathie specifically calling that out ([read more](https://meta.discourse.org/t/-/398792/4?silent=true)) and the original poster confirming the confusion ([read more](https://meta.discourse.org/t/-/398792/6?silent=true)). - A “how do I customize the sidebar like this?” question led to identifying the likely feature as the Docs Categories plugin in **Theme customize - sidebar content** ; @Lilly pointed to the relevant component as a starting place ([read more](https://meta.discourse.org/t/-/399504/3?silent=true)), referencing [Discourse Doc Categories](https://meta.discourse.org/t/-/322376/1?silent=true). - A potential regression (or expectation mismatch) surfaced: **“Use name for username suggestions”** appears to have _no effect_ on the standard signup form, confirmed by another admin in **“Use name for username suggestions”: no effect on signup form?** (#signup) — [read more](https://meta.discourse.org/t/-/399499/1?silent=true), plus confirmation in-reply ([read more](https://meta.discourse.org/t/-/399499/2?silent=true)). This was spun out of the now-solved registration UX discussion in [Customize registration form / hide or normalize username field](https://meta.discourse.org/t/-/399497/1?silent=true), where @ToddZ suggested using site text + settings (and even CSS) to guide “real-name-like” usernames ([read more](https://meta.discourse.org/t/-/399497/2?silent=true)), and later noted the suspected issue and opened the follow-up topic ([read more](https://meta.discourse.org/t/-/399497/7?silent=true)). - Export/printing needs resurfaced in **Is there a way to print a single post in a topic?** : @Thomas_Rother described a workflow need for sharing a _single_ Discourse post (e.g., a wiki meeting protocol) into other channels, ideally as PDF — [read more](https://meta.discourse.org/t/-/258689/12?silent=true). ### #Self-Hosting - In **Help deploying older versions of Discourse** , troubleshooting focused on YAML structure: @Ed_S suggested the `version` line was likely mis-indented because it belongs under `params` ([read more](https://meta.discourse.org/t/-/399409/21?silent=true)), after @RBoy shared a screenshot showing the config layout ([read more](https://meta.discourse.org/t/-/399409/20?silent=true)). - **How to set up fine-grained admin permissions or limit export capability?** (#backups) revisited a common constraint: admins effectively have full control. @NateDhaliwal asked for the underlying goal and pointed to the standard automation approach ([read more](https://meta.discourse.org/t/-/399510/2?silent=true)) while referencing the guide on [automatic backups](https://meta.discourse.org/t/-/14855/1?silent=true). Another reply suggested environment-defined settings may take precedence over UI configuration ([read more](https://meta.discourse.org/t/-/399510/3?silent=true)). ### #bug - A frustrating composer failure report in **Lost paragraphs / huge post due to HEIC upload** moved toward reproducibility: @awesomerobot asked for the exact error and whether the issue could be reproduced with similar text + the same images, emphasizing repeatable steps as the quickest path to root cause ([read more](https://meta.discourse.org/t/-/399453/2?silent=true)). ### #contribute:site-feedback - Accessibility/readability feedback continued on the **Meta Branded redesign: theme refresh** thread (#meta-theme-feedback, #meta-redesign-2026). @stephtara reported that linked text in the dark palette was “just below readable,” especially the purple-on-dark contrast, after comparing against other themes ([read more](https://meta.discourse.org/t/-/397246/47?silent=true)). ### #General - **[Releases.discourse.org](http://Releases.discourse.org) feedback & suggestions** sharpened into a concrete accessibility checklist: @ferdnyc identified contrast failures (including a failing WCAG ratio for white-on-`--color-feature`) and argued the site needs an accessibility review ([read more](https://meta.discourse.org/t/-/399414/10?silent=true)), then enumerated additional contrast problem areas flagged by tooling ([read more](https://meta.discourse.org/t/-/399414/11?silent=true)). > The contrast ratio cited for one key pairing was **3.46:1** , below the **WCAG AA 4.5:1** minimum ([details](https://meta.discourse.org/t/-/399414/10?silent=true)). ### #customization:plugin - A brand-new admin-oriented utility, **Plugin Cleaner** , was introduced as a way to scan/audit orphaned data left behind after uninstalling plugins ([read more](https://meta.discourse.org/t/-/399505/1?silent=true)). @merefield offered a detailed critique, warning about edge cases like plugin-owned tables and the risk of deleting fields that may later become core ([read more](https://meta.discourse.org/t/-/399505/2?silent=true)). - **Tag Intersection Navigator** got both maintenance and a practical UX improvement: @merefield shared PRs for upkeep and a feature allowing “normal banner notifications” while staying on the tag-intersections view, making it more viable as a homepage ([read more](https://meta.discourse.org/t/-/368815/26?silent=true)). - **Discourse Daily Challenges** shipped **v1.4.0** , adding an optional **ChallengeBot** for DM-based confirmations, reminders, and mention-driven commands (like `status` / `leaderboard`)—with rate limiting and a new site setting for bot username ([read more](https://meta.discourse.org/t/-/398980/39?silent=true)). A user also asked about displaying the challenge info elsewhere (e.g., on user cards) earlier in the thread ([read more](https://meta.discourse.org/t/-/398980/38?silent=true)). ### #Community Building - In **Eu tenho um fórum, mas não sei se ele está bem organizado o suficiente** , @NateDhaliwal discussed information architecture tradeoffs (e.g., why tags don’t always map cleanly to subcategories) and suggested improving “Report a Bug / Give Suggestion” flows by linking directly to a pre-filled composer ([read more](https://meta.discourse.org/t/-/399483/5?silent=true)), pointing to the how-to: [Creating a link to start a new topic with pre-filled information](https://meta.discourse.org/t/-/28074/1?silent=true). ### #contribute:feature - A chat UX gap was reported in **Pouvoir changer de canaux et de fermer en grande fenêtre chat** (#chat): when the chat window is expanded, the controls to switch channels or close the window appear to be missing, forcing users to shrink the panel to regain navigation ([read more](https://meta.discourse.org/t/-/399495/1?silent=true)). ### #customization:extras - **OpenClaw plugin for Discourse integration** hit a snag when a referenced page began returning 404 ([read more](https://meta.discourse.org/t/-/397239/9?silent=true)); a follow-up pointed back to context in the related **OpenClaw skill** discussion ([read more](https://meta.discourse.org/t/-/398771/3?silent=true)), with a direct reply and link-drop in the OpenClaw integration topic ([read more](https://meta.discourse.org/t/-/397239/10?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot engaged on API permissions + developer ergonomics in **API user with granular access cannot read about.json | Discourse MCP** (#mcp), saying it’s reasonable to include `about.json` access and noting a PR had been opened ([read more](https://meta.discourse.org/t/-/398792/3?silent=true)). - @awesomerobot also worked the debugging angle in **Lost paragraphs / huge post due to HEIC upload** , asking for the error details and encouraging reproduction steps to isolate the cause ([read more](https://meta.discourse.org/t/-/399453/2?silent=true)). - @supermathie followed up in the same MCP/API thread by questioning whether the current “invalid API username/key” message is misleading in granular-access cases, hinting at an opportunity to improve the error text ([read more](https://meta.discourse.org/t/-/398792/4?silent=true)). * * * May your plugin residue be minimal, your contrast ratios pass audits, and your ChallengeBot DMs arrive right on schedule. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [30 maart 2026 om 13:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/784 "2026-03-30T13:01:55Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts:** **82** (with lots of momentum around AI + admin tooling, e.g. [AI translation + PMs](https://meta.discourse.org/t/-/399524/1?silent=true) and routing fixes like [/llms.txt 404s](https://meta.discourse.org/t/-/397239/11?silent=true)). - **New topics:** **9** , including: - **Top users (posts / likes in the last 24h):** ## Interesting Topics ### #contribute:feature - @tobiaseigen found that **AI translation appears “100% complete” yet won’t backfill 1:1 PMs** , prompting discussion of clearer UI and a more granular setting set (including a proposed `ai_translation_backfill_targets` menu) in [Help me troubleshoot why AI is not translating PMs on my site](https://meta.discourse.org/t/-/399524/1?silent=true) (#ai #content-localization). Related roadmap chatter: [limit translation to specific categories](https://meta.discourse.org/t/-/392993/1?silent=true) and setting redesign ideas surfaced in-thread ([read more](https://meta.discourse.org/t/-/399524/5?silent=true)) ### #customization:extras - A long-running integration thread surfaced a **routing issue for “special paths” (like `/llms.txt`) depending on how they’re opened**, and the discussion converged on missing Ember routes and the “two routers” tax in [OpenClaw plugin for Discourse integration](https://meta.discourse.org/t/-/397239/11?silent=true) (with historical parallels to [Safe Mode](https://meta.discourse.org/t/53504?silent=true) docs: [safe mode topic](https://meta.discourse.org/t/-/53504/1?silent=true)). The fix was tied back to a core change ([read more](https://meta.discourse.org/t/-/397239/16?silent=true)) ### #customization:plugin - The “cleanup after uninstall” debate returned: @pfaffman warned that an automated remover is risky, while @elmuerte highlighted how **foreign keys can make leftover tables more than just clutter** in [Plugin Cleaner](https://meta.discourse.org/t/-/399505/3?silent=true) (and why reliable detection is hard) ([read more](https://meta.discourse.org/t/-/399505/4?silent=true)) ### #Support - @paco asked how `/faq`, `/privacy`, and `/about` _actually work_ (especially with `must be logged in` enabled) and how to add an `/acceptable-use` equivalent; the consensus: **those routes are special/hardcoded** , but **Page Publishing + permalinks** can approximate the desired behavior in [How do root level links work?](https://meta.discourse.org/t/-/399520/1?silent=true) (see also: [Page Publishing](https://meta.discourse.org/t/-/151971/1?silent=true)) - Scheduling a topic for later publication still has sharp edges: **group mentions won’t notify the way admins expect when a scheduled post publishes** , leading to workarounds like editing after publish (and linking back to the known issue) in [Question about group mentions in a private category](https://meta.discourse.org/t/-/399539/1?silent=true) (related: [mentions don’t fire when scheduled post is published](https://meta.discourse.org/t/-/212342/2?silent=true)) - A French-language Chat UX question turned into a “working as designed” clarification: in fullscreen, Chat becomes a dedicated page (no drawer close button), and channel switching moves to the sidebar in [Pouvoir changer de canaux et de fermer en grande fenêtre chat](https://meta.discourse.org/t/-/399495/2?silent=true) (#chat) ([read more](https://meta.discourse.org/t/-/399495/4?silent=true)) ### #Self-hosting - After upgrades, some sites saw **plugins fail due to CORS issues when using BunnyCDN** , and the resolution leaned on understanding that newer systems increasingly load JS via `type="module"` (which requires correct headers) in [All plugins not functioning due to CORS error after recent upgrade](https://meta.discourse.org/t/-/399466/4?silent=true) (#cdn). The thread also cross-referenced older BunnyCDN/highlight.js behavior ([read more](https://meta.discourse.org/t/-/296333/1?silent=true)) and the “why now?” explanation landed here ([read more](https://meta.discourse.org/t/-/399466/6?silent=true)) - Self-hosters compared upgrade methods (rebuild instance vs `./launcher rebuild app`, and what “production-safe” means across channels) in [Production upgrades - correct procedure to follow](https://meta.discourse.org/t/-/399550/1?silent=true). The conversation pointed back to release/channel docs like [Understanding Discourse release channels](https://meta.discourse.org/t/-/264400/1?silent=true) and [Configure a supported tracking branch](https://meta.discourse.org/t/-/17014/1?silent=true) ([read more](https://meta.discourse.org/t/-/399550/4?silent=true)) - Tag/branch confusion and constrained networks came up again as @david clarified how the rebuild script treats tags vs branches, and why a tag checkout can look “weird” but still be expected behavior in [Help deploying older versions of Discourse](https://meta.discourse.org/t/-/399409/25?silent=true) ### #bug - A setting expectation mismatch became a clarified limitation: **“Use name for username suggestions” only applies to SSO/OAuth flows** , not the local signup form—leading to a docs/description update in [“Use name for username suggestions”: no effect on signup form?](https://meta.discourse.org/t/-/399499/3?silent=true) (#signup) ([read more](https://meta.discourse.org/t/-/399499/4?silent=true)) - Google Search Console warnings about structured data reappeared after an update: “Either `acceptedAnswer` or `suggestedAnswer` should be specified” became actionable again and was tied to recent changes, with a fix queued in [Google search console acceptedAnswer error](https://meta.discourse.org/t/-/399525/1?silent=true) ([read more](https://meta.discourse.org/t/-/399525/2?silent=true); related background: [Either acceptedAnswer or suggestedAnswer should be specified](https://meta.discourse.org/t/-/111809/3?silent=true)) - A report described a puzzling **“Image could not be loaded”** error _only when clicking directly to zoom_ (but not when navigating via arrow keys), with testing suggestions around [safe mode](https://meta.discourse.org/t/53504?silent=true), cache reload, and account-based repro in [“Image could not be loaded error” when click to zoom in](https://meta.discourse.org/t/-/399548/1?silent=true) ([read more](https://meta.discourse.org/t/-/399548/2?silent=true)) - Hosting surfaced a possible incident: **Discourse-managed CDN domain was reportedly failing SSL validation** (as observed via Cloudflare warnings) in [Discourse CDN with an invalid SSL cert?](https://meta.discourse.org/t/-/399543/1?silent=true) (#cdn) ### #Dev - A contributor offered forward-compat help by opening a PR to support **Sidekiq 8.1** in `mini_scheduler`, unblocking Rails app upgrades in [PR: Add Sidekiq 8 support to mini\_scheduler](https://meta.discourse.org/t/-/399560/1?silent=true) ### #ux - A small but visible polish issue: when the category name is Chinese, the **category dropdown and title input align slightly differently** , producing a “not quite level” composer row in [中文类别选择框与标题输入框不对齐](https://meta.discourse.org/t/-/399556/1?silent=true) (#composer) (#horizon-theme) ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco proposed reworking a single boolean into a more expressive setting menu so admins can explicitly choose translation targets—potentially including **all PMs** —in [AI translation PM backfill targets](https://meta.discourse.org/t/-/399524/4?silent=true). - @nat previewed an upcoming “translate these categories” feature and suggested splitting translation controls into clearer options like _“translate PMs”_ plus category scoping in [AI translation settings rethink](https://meta.discourse.org/t/-/399524/5?silent=true). - @sam confirmed the `/llms.txt` behavior is a real routing gap (not just “documented weirdness”) and suggested tracking it properly in [OpenClaw plugin thread](https://meta.discourse.org/t/-/397239/13?silent=true), later noting why fixing it matters more than [Safe Mode](https://meta.discourse.org/t/53504?silent=true)’s long-documented new-tab quirk in [the same thread](https://meta.discourse.org/t/-/397239/15?silent=true). - @zogstrip linked the `/llms.txt` + related 404s to an incoming core fix and pointed to the PR in [OpenClaw plugin thread](https://meta.discourse.org/t/-/397239/16?silent=true). - @david explained why “suddenly after upgrading” CORS problems appear: the migration to `script type="module"` makes correct CORS headers mandatory, especially for CDNs, in [CORS errors after recent upgrade](https://meta.discourse.org/t/-/399466/6?silent=true). He also clarified expected behavior when deploying tags/refs vs branches in [deploying older versions](https://meta.discourse.org/t/-/399409/25?silent=true). - @HAWK helped triage signup expectations by moving a report into bug classification in [username suggestion setting report](https://meta.discourse.org/t/-/399499/3?silent=true), and pointed to prior art around scheduled posts + mention notifications in [group mentions + scheduled publishing](https://meta.discourse.org/t/-/399539/3?silent=true). - @chapoi confirmed a reported Chat fullscreen “can’t close / can’t switch channels” behavior is expected and showed where those controls live in [Chat fullscreen behavior explained](https://meta.discourse.org/t/-/399495/4?silent=true). - @martin dropped helpful “this was already removed” context for FAQ/guidelines navigation changes in [FAQ & Guidelines links review](https://meta.discourse.org/t/-/397938/15?silent=true), and pointed admins to the current category-level setting for easier Solved-based support workflows in [Support categories + discourse-solved](https://meta.discourse.org/t/-/398338/13?silent=true). > Until tomorrow: may your CORS headers be correct, your `/llms.txt` route resolvable, and your “translate PMs” checkbox finally say what it means. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [31 maart 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/785 "2026-03-31T13:02:09Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 97** - **New topics (last 24h): 15** - A lot of the day’s energy clustered around _localization/translation UX_ and _upgrade/migration edge cases_, especially in threads like [AI tag translations](https://meta.discourse.org/t/-/399570/1?silent=true) and the [migration collision bootstrap failure](https://meta.discourse.org/t/-/399572/1?silent=true). **Top users (posts / likes)** _(with a “where they showed up” link)_ | User | Posts | Likes | Reference | | --- | --- | --- | --- | | **@Moin** | 13 | 16 | dug deep into localization issues like [AI tag translation quality](https://meta.discourse.org/t/-/399570/1?silent=true) and [translated tags not linkifying](https://meta.discourse.org/t/-/399591/1?silent=true) | | **@david** | 8 | 6 | helped root-cause a gnarly [migration ID collision bootstrap error](https://meta.discourse.org/t/-/399572/6?silent=true) and explained downgrades in [Oops error](https://meta.discourse.org/t/-/399614/9?silent=true) | | **@pfaffman** | 7 | 4 | reported + diagnosed the [bootstrap/migration collision](https://meta.discourse.org/t/-/399572/5?silent=true) (with bonus AI-generated “pfaffman-style” humor) | | **@nat** | 5 | 9 | responded on [AI-generated tag translations](https://meta.discourse.org/t/-/399570/5?silent=true) and shared the PM/category translation settings PR in [PM translation troubleshooting](https://meta.discourse.org/t/-/399524/8?silent=true) | | **@darkpixlz** | 5 | 6 | clarified behavior around [account deletion emails](https://meta.discourse.org/t/-/399576/2?silent=true) and investigated an [API scope regression](https://meta.discourse.org/t/-/399597/1?silent=true) | | **@Falco** | 5 | 5 | proposed tool-assisted context gathering for better [tag translations](https://meta.discourse.org/t/-/399570/4?silent=true) and answered calendar sync expectations in [Calendar subscription URLs](https://meta.discourse.org/t/-/398902/12?silent=true) | | **@merefield** | 3 | 4 | weighed in on dev deprecations like [`.hbs` deprecation](https://meta.discourse.org/t/-/398896/9?silent=true) and [`.js.es6` deprecation](https://meta.discourse.org/t/-/398894/3?silent=true) | | **@RGJ** | 3 | 4 | pushed for UI support in [incoming email for automatic groups](https://meta.discourse.org/t/-/399611/1?silent=true) and highlighted the [auto-migration path to `.gjs`](https://meta.discourse.org/t/-/398896/10?silent=true) | | **@nat** _(already listed above)_ | 5 | 9 | see: [tag translations](https://meta.discourse.org/t/-/399570/5?silent=true) / [translation settings PR](https://meta.discourse.org/t/-/399524/8?silent=true) | | **@ganncamp** | 2 | 3 | noticed an intermittent regression in [Edit Assignment dialog focus](https://meta.discourse.org/t/-/279508/5?silent=true) | * * * ## Interesting Topics ### #Site feedback - @Moin cataloged a bunch of _hilarious-but-problematic_ AI translations for tags (e.g., **#raspberry-pi → “Himbeere-pi”** ) and flagged the more serious issue: collisions where different tags map to the same translation, breaking discoverability in [AI-generated tag translations do not work perfectly](https://meta.discourse.org/t/-/399570/1?silent=true). @nat said she’ll tweak prompts ([read more](https://meta.discourse.org/t/-/399570/3?silent=true)), while @Falco suggested giving the agent context via tools/glossaries to improve grounding ([read more](https://meta.discourse.org/t/-/399570/4?silent=true)). - Ongoing refinements to the Meta redesign continued: @manuel acknowledged color/usability issues and pointed to a new theme modifier enabling themes to limit available color schemes, in [Meta Branded redesign: theme refresh](https://meta.discourse.org/t/-/397246/48?silent=true). A side investigation into “inconsistent link highlighting” turned out to be a _local CSS bleed_ from a different site theme on @darkpixlz’s laptop ([read more](https://meta.discourse.org/t/-/397246/53?silent=true)). ### #Self-hosting - A bootstrap failure turned into a cautionary tale about **migration version collisions** : @pfaffman hit `relation "ai_agent_mcp_servers" does not exist` during `db:migrate`, eventually discovering an _ID collision_ between a plugin migration and `discourse-ai`, documented in [Bootstrap error: relation “ai\_agent\_mcp\_servers” does not exist – due to migration id collision](https://meta.discourse.org/t/-/399572/1?silent=true). @david confirmed ordering looked correct upstream and helped triangulate what actually ran ([read more](https://meta.discourse.org/t/-/399572/4?silent=true)), then marked the collision explanation as the solution ([read more](https://meta.discourse.org/t/-/399572/6?silent=true)). - A “what branch should we run?” ops question concluded with a plan to follow `release` for monthly updates in [Production upgrades - correct procedure to follow](https://meta.discourse.org/t/-/399550/6?silent=true). Related self-hosting/versioning guidance also came up elsewhere (e.g., “older versions” pitfalls in [Help deploying older versions of Discourse](https://meta.discourse.org/t/-/399409/26?silent=true)). ### #Support - Moderation workflow question: after deleting an obvious spam account, @haydenjames noticed Discourse sent an `account_deleted` email and asked if spam deletions can be silent in [Should Discourse notify users when accounts are deleted for spam?](https://meta.discourse.org/t/-/399576/1?silent=true). @darkpixlz confirmed it’s expected behavior and linked prior discussion indicating it’s by design ([read more](https://meta.discourse.org/t/-/399576/2?silent=true); also see earlier thread [Can we turn off emails to deleted users and stop contacting our spammers?](https://meta.discourse.org/t/-/382412/11?silent=true)). - A rebuild led to persistent “Oops” errors that boiled down to a classic: **downgrading isn’t supported**. In [Oops 错误](https://meta.discourse.org/t/-/399614/1?silent=true), @david quickly identified a likely `latest → esr` downgrade and explained why schema/code mismatches can’t be reconciled without restoring the right backup ([read more](https://meta.discourse.org/t/-/399614/7?silent=true)). - A detailed request proposed “always-on bilingual” chat/thread UX: show original + translation together, ideally paragraph-by-paragraph, to bridge multilingual discussion in pan-African contexts in [Ongoing translation in threads](https://meta.discourse.org/t/-/399610/1?silent=true). This intersects with recent localization work (see translation settings/prior art in [content localization topics](https://meta.discourse.org/t/-/399606/2?silent=true)). - Event/calendar usability: a user report noted Google Calendar didn’t immediately reflect edits/deletions from Discourse event feeds in [Calendar subscription URLs for external calendar apps](https://meta.discourse.org/t/-/398902/11?silent=true). @Falco clarified Google typically fetches updates ~twice daily, so “last-minute changes” won’t propagate instantly ([read more](https://meta.discourse.org/t/-/398902/12?silent=true)). ### #Dev - Two parallel deprecation threads drew strong reactions from plugin/theme authors: [Deprecating .hbs file extension in themes and plugins](https://meta.discourse.org/t/-/398896/8?silent=true) and [Deprecating .js.es6 file extensions in themes and plugins](https://meta.discourse.org/t/-/398894/2?silent=true). Community replies emphasized the long runway and available automation, including the bulk updater path in [Automatically updating themes and plugins to .gjs file format](https://meta.discourse.org/t/-/368051/1?silent=true), and noted `.es6` is _well past_ “new” ([read more](https://meta.discourse.org/t/-/398894/3?silent=true)). - An API regression report: a previously-working script using scope `all-users` started failing with 400s in [API scope `all-users` not working anymore](https://meta.discourse.org/t/-/399597/1?silent=true). This one looks poised to become a sharper “is this intended?” / “what changed?” debugging thread as more details arrive. ### #ux - Review Queue ergonomics: @ice.d asked why “helpful flags” isn’t clickable / filterable directly, and @darkpixlz agreed it seems unintended, offering a workaround via the Approved filter in [Why can’t we see helpful flags?](https://meta.discourse.org/t/-/399600/1?silent=true) ([read more](https://meta.discourse.org/t/-/399600/6?silent=true)). - Localization UX inconsistencies piled up across _tags vs categories_ behavior: @Moin asked why categories translate immediately with UI language, but tags only translate when the “translate titles/posts” toggle is enabled in [Why are the criteria for displaying translated categories and tags not the same?](https://meta.discourse.org/t/-/399596/1?silent=true). Closely related: translated tag autocomplete can suggest localized tags that then **don’t linkify** (and may not apply as tags), in [Using translated tags](https://meta.discourse.org/t/-/399591/1?silent=true), echoing earlier autocomplete oddities in [When localized category autocomplete sometimes works…](https://meta.discourse.org/t/-/374737/7?silent=true). ### #contribute:feature - Category metadata translations may be drifting out of date: @Moin requested that translated category names and descriptions auto-update when originals change in [Automatically update translations of category names when the original is changed](https://meta.discourse.org/t/-/399585/1?silent=true) and [Automatically update translated category descriptions](https://meta.discourse.org/t/-/399587/1?silent=true). The concrete example: Meta’s category rename “Installation → Self-hosting” not propagating into German, and the #category-banner pulling an older German description even after the underlying “about topic” translation updated. - A small but meaningful admin UX request: enable incoming email addresses for _automatic groups_ (like “staff” or “TL3”) directly in the UI, rather than requiring console workarounds, in [Allow incoming email for automatic groups](https://meta.discourse.org/t/-/399611/1?silent=true). @Moin confirmed it can be done via Rails console today but agreed the UI restriction is confusing ([read more](https://meta.discourse.org/t/-/399611/2?silent=true)). ### #community-building Building - A thoughtful “how do we do this well?” thread: @Lew_Grothe asked for real-world experiences supporting Spanish/French/Portuguese in a members-only community, with questions about rollout strategy and moderation, in [Seeking experience: Supporting a multilingual Discourse community](https://meta.discourse.org/t/-/399606/1?silent=true). The discussion quickly pointed toward the newer AI-driven localization options (see the pointer to [content localization with Discourse AI](https://meta.discourse.org/t/-/399606/2?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@nat** followed up on the (very entertaining) #tags/#ai translation quality report in [AI-generated tag translations do not work perfectly](https://meta.discourse.org/t/-/399570/3?silent=true), and discussed adding more context (like tag descriptions) to improve #dynaloc translation outcomes ([read more](https://meta.discourse.org/t/-/399570/5?silent=true)). She also shared the in-flight settings migration/PR in [Help me troubleshoot why AI is not translating PMs on my site](https://meta.discourse.org/t/-/399524/8?silent=true), and cross-posted that same PR as progress in [Feature request: Limit topic translation to specific categories](https://meta.discourse.org/t/-/392993/5?silent=true). - **@david** debugged and ultimately solved the migration collision case in [Bootstrap error: relation “ai\_agent\_mcp\_servers” does not exist](https://meta.discourse.org/t/-/399572/6?silent=true), then helped a self-hoster understand why `latest → esr` downgrades break schema compatibility in [Oops 错误](https://meta.discourse.org/t/-/399614/7?silent=true) (and confirmed the root cause plainly in the accepted answer: [read more](https://meta.discourse.org/t/-/399614/9?silent=true)). He also checked in on an outstanding build issue in [Chat plugin fails to compile with rollup plugin compiler](https://meta.discourse.org/t/-/399321/3?silent=true). - **@Falco** pushed the “give the model tools/context” angle for better translations in [AI-generated tag translations do not work perfectly](https://meta.discourse.org/t/-/399570/4?silent=true) and added practical grounding around external calendar sync intervals in [Calendar subscription URLs for external calendar apps](https://meta.discourse.org/t/-/398902/12?silent=true). - **@manuel** continued iterating on Meta’s refreshed theme, noting color issues and pointing to improved theming controls in [Meta Branded redesign: theme refresh](https://meta.discourse.org/t/-/397246/48?silent=true), then asked for browser inspection details when odd link highlighting was reported ([read more](https://meta.discourse.org/t/-/397246/52?silent=true)). - **@zogstrip** shipped a fix for a social UX edge case (“can’t unfollow banned members”) in [Banned members cannot be Unfollowed](https://meta.discourse.org/t/-/304256/3?silent=true), and clarified intended behavior + upcoming improvements for recurring event attendance management in [Repeating Event “going” gets not deleted anymore](https://meta.discourse.org/t/-/335780/13?silent=true). - **@schleifer** resolved a hosted-support report about an outdated/retired CDN hostname presenting an invalid cert in [Discourse CDN with an invalid SSL cert?](https://meta.discourse.org/t/-/399543/3?silent=true). - **@sam** acknowledged that AI agents often ignore the “use real timestamps” migration guidance, and floated adding a “how to do migrations” skill or linting to prevent repeats, in the bootstrap collision thread: [read more](https://meta.discourse.org/t/-/399572/8?silent=true). - **@awesomerobot** confirmed a Horizon theme fix was coming for a blocked settings UI and linked the patch in [Category creation floating box blocks out settings at the bottom](https://meta.discourse.org/t/-/399481/4?silent=true). - **@renato** noted a recent change to `[details]` serialization behavior in the rich editor, asking for follow-up if issues remain in [“Hide Details” section open by default in new editor](https://meta.discourse.org/t/-/377645/23?silent=true). - **@j.jaffeux** explained why recurring events keep “going” lists (no per-date event entry model today) in [Repeating Event “going” gets not deleted anymore](https://meta.discourse.org/t/-/335780/14?silent=true). * * * _That’s a wrap—may tomorrow’s migrations include real timestamps, and may your tags never again translate #raspberry-pi into “Himbeere-pi.”_ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [1 april 2026 om 13:01 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/786 "2026-04-01T13:01:15Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 103** - **New topics (last 24h): 14** **Top contributors (posts / likes in the last 24h)** - **@Moin** — 13 posts / 13 likes - **@sam** — 3 posts / 12 likes - **@Lilly** — 5 posts / 12 likes - **@nat** — 2 posts / 11 likes - **@awesomerobot** — 4 posts / 9 likes - **@david** — 4 posts / 8 likes - **@RGJ** — 1 post / 7 likes - **@WorldIsMine** — 2 posts / 6 likes - **@ToddZ** — 5 posts / 5 likes - **@Falco** — 2 posts / 4 likes > Notable trend: lots of “platform plumbing” today—CDN/CORS behavior, mobile rendering regressions, and a fresh wave of AI + MCP capability announcements (see [read more](https://meta.discourse.org/t/-/399668/1?silent=true) and [read more](https://meta.discourse.org/t/-/399466/12?silent=true)). * * * ## Interesting Topics ### #customization:theme-component - @RGJ shipped a playful new theme component, **Full Screen Cover Image** , aimed at splash screens for maintenance notices, announcements, or _April 1st chaos_—with install pointers to the official guides for [installing theme components](https://meta.discourse.org/t/-/63682/1?silent=true) and the [themes beginner guide](https://meta.discourse.org/t/-/91966/1?silent=true) ([read more](https://meta.discourse.org/t/-/399690/1?silent=true)). - The same splash component sparked real-world “OMG” reactions when @WorldIsMine shared a live April Fools deployment and discussed how it could become a serious “everyone must see this” announcement pattern later ([read more](https://meta.discourse.org/t/-/399690/3?silent=true)). ### #Support - A mysterious **infinite “is replying…” presence indicator** was solved by toggling the `Presence enabled` setting off and back on—confirming the bug was tied to the presence feature path, not a stuck user account ([read more](https://meta.discourse.org/t/-/399655/2?silent=true), solution confirmed [read more](https://meta.discourse.org/t/-/399655/4?silent=true)). - A self-hosted admin asked how to create “integrated” custom pages like `/rules` and `/apply` (without `/pub` URLs), with the community pointing toward the **Landing Pages** approach as a practical fit ([read more](https://meta.discourse.org/t/-/399679/1?silent=true), plugin suggestion [read more](https://meta.discourse.org/t/-/180967/1?silent=true)). - A new **Data & reporting** question explored embedding “About page” site activity graphs or reports into an external homepage, kicking off a discussion on what’s feasible and where to look for implementation paths ([read more](https://meta.discourse.org/t/-/399678/1?silent=true)). - A report of **search not finding exact title words** (plus a 500 when AI semantic search/embeddings are enabled) landed as a fresh troubleshooting thread—especially relevant for multilingual communities ([read more](https://meta.discourse.org/t/-/399693/1?silent=true)). ### #announcements - Discourse AI agents can now **connect out to any MCP server** (“Bring your own MCP!”), turning Discourse into a two-way MCP citizen (Discourse as _client_ + Discourse as _server_)—positioned as a major expansion of AI-agent tool access ([read more](https://meta.discourse.org/t/-/399668/1?silent=true), plus related MCP context [read more](https://meta.discourse.org/t/-/386983/1?silent=true)). - The **March 2026 monthly release** announcement dropped, with early adopter feedback noting smooth upgrades and a successful switch to the `release` track ([read more](https://meta.discourse.org/t/-/399630/1?silent=true)). - Continued real-world testing feedback came in on **calendar subscription URLs** (ICS), including requests for more “feature complete” behavior (like persistent display until revoked and better filtering semantics for multi-community setups) ([read more](https://meta.discourse.org/t/-/398902/15?silent=true)). ### #bug - Meta itself hit a nasty mobile regression where topic pages (and even lists like `/latest`) rendered only the header/title until themes were disabled—later traced to a **discourse-tag-icons theme component** change that was temporarily reverted while investigated ([read more](https://meta.discourse.org/t/-/399691/1?silent=true), root-cause note [read more](https://meta.discourse.org/t/-/399691/5?silent=true)). - Archived-topic behavior got scrutinized: users could sometimes click “like” on posts with no reactions, but then hit confusing errors—prompting a fix for **reactions logic in archived topics** ([read more](https://meta.discourse.org/t/-/399681/1?silent=true), fix PR mentioned [read more](https://meta.discourse.org/t/-/399681/5?silent=true)). - A long-running “chat build” thread continued: the **Chat plugin fails to compile with rollup** report remains unresolved, with @david probing whether local customization/patches might be the real culprit ([read more](https://meta.discourse.org/t/-/399321/4?silent=true)). ### #site-management - The detailed guide for **AI Bot – Bring Your Own MCP Server** explains how to register MCP endpoints, cache tool discovery, and assign tools per-agent—framed as “no JavaScript required” compared with custom tool scripting ([read more](https://meta.discourse.org/t/-/399667/1?silent=true), related “custom tools” contrast [read more](https://meta.discourse.org/t/-/314103/1?silent=true)). ### #self-hosting - A “plugin apocalypse” report turned out _not_ to be plugin deprecations after all: **CORS + `script type="module"`** behavior with CDN setups caused dynamic imports to fail until headers/rules were updated; the thread now includes guidance and an NGINX-config fix requiring a CLI rebuild ([read more](https://meta.discourse.org/t/-/399466/9?silent=true), follow-up + fix guidance [read more](https://meta.discourse.org/t/-/399466/12?silent=true)). - The ongoing “is discourse/discourse production-ready?” discussion continued with practical notes about **custom images and plugin builds** (and why building on boot is a bad plan), including an example build that adds a plugin during image creation ([read more](https://meta.discourse.org/t/-/380646/25?silent=true), plugin referenced in that workflow [read more](https://meta.discourse.org/t/-/389056/1?silent=true)). ### #events - Meta formalized how it’s labeling and organizing **Webinars vs Community Office Hours** , and highlighted the new Events category as the canonical home for announcements and replays ([read more](https://meta.discourse.org/t/-/399640/1?silent=true)). - A small but meaningful scheduling fix: an event time display confusion was reported and quickly adjusted, reinforcing the goal of making events discoverable (including past sessions) via the Events calendar ([read more](https://meta.discourse.org/t/-/398295/5?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@sam** introduced the headline AI capability: Discourse AI agents can now connect to external MCP servers, dramatically expanding tool access (“Bring your own MCP!”) ([read more](https://meta.discourse.org/t/-/399668/1?silent=true)). @sam also posted the full admin guide for configuring MCP servers with Discourse AI bots ([read more](https://meta.discourse.org/t/-/399667/1?silent=true)) and did a bit of spring cleaning by moving outdated GetSatisfaction content out of official docs ([read more](https://meta.discourse.org/t/-/56197/9?silent=true)). - **@nat** published the companion discussion for a deep history of multilingual support at Discourse—how language support evolved over 13 years ([read more](https://meta.discourse.org/t/-/399661/1?silent=true)). @nat also confirmed progress on translated tags support for the tag icon component, pointing to an in-flight PR ([read more](https://meta.discourse.org/t/-/399594/3?silent=true)). - **@david** posted the March 2026 release announcement and pointers to changelogs for supported versions ([read more](https://meta.discourse.org/t/-/399630/1?silent=true)). @david also engaged in two separate “ops meets JS” threads: asking diagnostic questions about a chat rollup compiler issue ([read more](https://meta.discourse.org/t/-/399321/5?silent=true)) and addressing CDN/CORS breakage from module-based plugin loading—ending with an apology, a proposed fix, and guidance that a **CLI rebuild** is required for NGINX config updates ([read more](https://meta.discourse.org/t/-/399466/12?silent=true)). - **@davidb** identified the likely culprit behind Meta’s mobile rendering regression as a recent change in the **discourse-tag-icons** theme component and noted it was being reverted while the team investigates ([read more](https://meta.discourse.org/t/-/399691/5?silent=true)). - **@awesomerobot** helped triage support and product polish: they questioned whether the “infinite replying” issue might be user/bot-state related ([read more](https://meta.discourse.org/t/-/399655/3?silent=true)), and proposed a UX fix for “reply to this message” going nowhere when `site_contact_username` / `site_contact_group_name` aren’t configured—opening a PR to adjust the system message copy accordingly ([read more](https://meta.discourse.org/t/-/399477/2?silent=true)). @awesomerobot also followed through on review-queue UX by opening (and noting the merge of) a PR to link “helpful flags” to the new “Flagged by” filter ([read more](https://meta.discourse.org/t/-/341613/8?silent=true)). - **@dax** confirmed the “borked on mobile viewport” regression on Meta and stated the team was looking into it ([read more](https://meta.discourse.org/t/-/399691/2?silent=true)). - **@zogstrip** responded to the archived-like/reaction inconsistency by confirming incorrect logic and pointing to a fix PR for reactions handling on archived topics ([read more](https://meta.discourse.org/t/-/399681/5?silent=true)). They also shared that vote-limit UI can now be disabled/hidden as part of ongoing Topic Voting improvements ([read more](https://meta.discourse.org/t/-/308402/44?silent=true)). - **@Danielle** updated an event listing after a time-format confusion report and clarified the intent: improving visibility of past events on the calendar ([read more](https://meta.discourse.org/t/-/398295/6?silent=true)). @Danielle also published how Meta will structure webinars and office hours going forward ([read more](https://meta.discourse.org/t/-/399640/1?silent=true)). - **@Falco** contributed hands-on guidance for multilingual communities, pointing to real examples and emphasizing Discourse’s native content localization—while noting that _chat translation_ is the main missing piece (for now) ([read more](https://meta.discourse.org/t/-/399610/2?silent=true), related “seeking experience” thread [read more](https://meta.discourse.org/t/-/399606/4?silent=true), plus the documentation hub [read more](https://meta.discourse.org/t/-/370969/1?silent=true)). - **@featheredtoast** weighed in on Docker-image operational realities, explaining why adding plugins via docker-compose “on boot” isn’t supported and why custom images are the sustainable path—plus sharing an example pipeline that bakes plugins into an image build ([read more](https://meta.discourse.org/t/-/380646/25?silent=true)). * * * _That’s a wrap—between April Fools-ready splash screens and Discourse joining the MCP tool party, today felt like equal parts “prank day” and “ship serious platform capabilities” day._ ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [2 april 2026 om 13:02 UTC](https://meta.discourse.org/t/daily-summary-1pm-utc/291852/787 "2026-04-02T13:02:30Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 91 - **New topics (last 24h):** 7 - **Most-liked post:** @Falco’s announcement of **full app mode embeds** (27 likes) — [read more](https://meta.discourse.org/t/-/399743/1?silent=true) **Top users by activity (posts / likes received in the last 24h):** - **@Falco:** 11 posts / 51 likes (notably in [full app embeds](https://meta.discourse.org/t/-/399743/1?silent=true), plus follow-ups like [this reply](https://meta.discourse.org/t/-/399743/5?silent=true)) - **@Moin:** 8 posts / 6 likes (including product feedback in [Upcoming Changes](https://meta.discourse.org/t/-/392894/19?silent=true)) - **@Lilly:** 4 posts / 8 likes (including reporting ideas in [Data & reporting](https://meta.discourse.org/t/-/399678/4?silent=true)) - **@zogstrip:** 4 posts / 3 likes (including a likely fix pointer in [Topic Voting](https://meta.discourse.org/t/-/399649/16?silent=true)) - **@awesomerobot:** 3 posts / 3 likes (including a UX improvement PR proposal in [review queue rejection flow](https://meta.discourse.org/t/-/373992/19?silent=true)) - **@mcwumbly:** 2 posts / 4 likes (including feedback on [Building for Every Language](https://meta.discourse.org/t/-/399661/2?silent=true)) - **@RGJ:** 2 posts / 4 likes (including a new bug report for [Category Experts](https://meta.discourse.org/t/-/399785/1?silent=true)) - **@sam:** 2 posts / 3 likes (including product direction in [AI Persona mention-only behavior](https://meta.discourse.org/t/-/399221/2?silent=true)) - **@mcmcclur:** 2 posts / 4 likes (including embed UX notes in [full app embeds](https://meta.discourse.org/t/-/399743/4?silent=true)) - **@pfaffman:** 1 post / 3 likes (S3 clues in a solved CORS thread: [read more](https://meta.discourse.org/t/-/399466/15?silent=true)) * * * ## Interesting Topics ### #Announcements - @Falco introduced **“full app mode” embeds** (#embedding), letting visitors reply/like/quote _inside the iframe_ rather than clicking through to the forum; early feedback surfaced UI/scroll affordance concerns and “reply target confusion” risks for blog readers — [read more](https://meta.discourse.org/t/-/399743/1?silent=true) (see also the UI-tradeoffs discussion: [read more](https://meta.discourse.org/t/-/399743/5?silent=true)). _Related embedding threads:_ “Topic as widget” now points here ([read more](https://meta.discourse.org/t/-/49811/10?silent=true)), and “Embedding full threads” was updated with the same answer ([read more](https://meta.discourse.org/t/-/360386/5?silent=true)). - “Upcoming Changes” (#upcoming-changes) got UX feedback: @Moin asked for sorting by status (alpha/beta/experimental), and @martin confirmed both **status sorting** and a potential **“when it appeared on your site”** sort are on the way — [read more](https://meta.discourse.org/t/-/392894/19?silent=true) and the follow-up commitment: [read more](https://meta.discourse.org/t/-/392894/20?silent=true). - Calendar subscription URLs (#calendar-and-event, #bookmarks): @Falco suggested checking the “Discourse post event enabled” setting, but the reporter later determined this looks like a **plugin migration regression** where events stopped showing in posts — [read more](https://meta.discourse.org/t/-/398902/17?silent=true) (and the migration suspicion: [read more](https://meta.discourse.org/t/-/398902/18?silent=true)). - “Current Projects – March 2026” (#current-projects): @lindsey posted a quick status update that blog styling components are pending a Crowdin setup step once a teammate returns from leave — [read more](https://meta.discourse.org/t/-/398565/10?silent=true). * * * ### #bug - Self-hosted backups to **Cloudflare R2** fail during multipart upload with `aws-sdk-s3 1.182.0` due to `undefined method 'downcase' for nil`, blocking scheduled backups after successful archive creation — [read more](https://meta.discourse.org/t/-/399768/1?silent=true). - The **Category Experts** plugin (#category-experts) can crash user merges run via command line; the report notes disabling the plugin prevents the merge failure, implying a validation side-effect during merge operations — [read more](https://meta.discourse.org/t/-/399785/1?silent=true). - Bulk group invites bug (#groups, #email, #invites): on `latest`, bulk-adding emails could still send invitations even when **“Notify users”** is unchecked; @zogstrip linked a fix PR and clarified intent is simply respecting the checkbox — [read more](https://meta.discourse.org/t/-/397334/2?silent=true). - RTL polish: an **external link icon** wasn’t rendering correctly for RTL layouts (#rtl, #featured-link); @zogstrip confirmed it’s addressed via a PR — [read more](https://meta.discourse.org/t/-/397432/2?silent=true). * * * ### #ux - Review queue UX (#review-queue): when a post is rejected, the user can’t easily edit-and-resubmit; @awesomerobot proposed a pragmatic improvement—create a **draft from the rejected content** and link the user to it—plus opened a PR — [read more](https://meta.discourse.org/t/-/373992/19?silent=true) (with process clarification after merge: [read more](https://meta.discourse.org/t/-/373992/21?silent=true)). - Horizon theme layout constraints (#horizon-theme): @awesomerobot explained why making only the nav sticky (while the category header scrolls away) isn’t straightforward with CSS given the current DOM structure, and that restructuring could risk regressions across themes — [read more](https://meta.discourse.org/t/-/387267/11?silent=true). _Related Horizon discussion:_ broader Horizon compatibility questions continue here — [read more](https://meta.discourse.org/t/-/360486/78?silent=true). * * * ### #Support - A numeric tag URL edge case (#bug): a forum with a 4-digit tag (e.g. `6309`) returns a **server error** at `/tag/6309` instead of a clean 404, causing Google crawl warnings — [read more](https://meta.discourse.org/t/-/399784/1?silent=true). - Hosted moderation emails (#hosted-support, #email, #category-moderators): a site using category-level “Require approval for all new topics” reports posts enter review queue, but **`post_needs_approval` email** doesn’t send; they’re seeking a way to trigger it without turning on the global setting — [read more](https://meta.discourse.org/t/-/399775/1?silent=true). - Topic Voting (#topic-voting): users reported missing vote tallies and trouble voting; @zogstrip pointed to a core commit as a likely fix, with follow-up logs showing 500s tied to poll-related errors — [read more](https://meta.discourse.org/t/-/399649/16?silent=true) (and the shared error/log detail: [read more](https://meta.discourse.org/t/-/399649/20?silent=true)). * * * ### #customization:theme component - Topic List Previews (TLP) breakage: updating to **2026.1.3 ESR** pulled an incompatible component version due to a missing compatibility pin; a PR adding the pin was merged, plus a temporary fork workaround was provided for impacted admins — [read more](https://meta.discourse.org/t/-/209973/730?silent=true) (merge confirmation: [read more](https://meta.discourse.org/t/-/209973/731?silent=true)). - Easy Responsive Footer (#easy-responsive-footer): a report suggests the footer appearing on `/login` causes the page to **jump back to the top while scrolling** ; [Safe Mode](https://meta.discourse.org/t/53504?silent=true) testing indicates a theme/component interaction — [read more](https://meta.discourse.org/t/-/95818/260?silent=true) (and the referenced [Safe Mode](https://meta.discourse.org/t/53504?silent=true) guide: [read more](https://meta.discourse.org/t/-/53504/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Falco drove a major announcement: **full app mode embeds** (#embedding), including implementation details and early design trade-offs around simplifying embed UI — [read more](https://meta.discourse.org/t/-/399743/1?silent=true) and follow-ups like [read more](https://meta.discourse.org/t/-/399743/5?silent=true) and [read more](https://meta.discourse.org/t/-/399743/7?silent=true). He also pointed older embedding/widget questions to the new capability ([read more](https://meta.discourse.org/t/-/49811/10?silent=true), [read more](https://meta.discourse.org/t/-/360386/5?silent=true), [read more](https://meta.discourse.org/t/-/81473/9?silent=true)). - @Falco continued AI tooling work: he added an **edit tool to Discourse MCP** and advised updating to the latest version — [read more](https://meta.discourse.org/t/-/386983/31?silent=true). - @sam weighed in on AI agent ergonomics, suggesting “mention-only” might be a better default than adding yet another option, with @Falco recommending waiting for **workflows** to handle niche routing needs — [read more](https://meta.discourse.org/t/-/399221/2?silent=true) and [read more](https://meta.discourse.org/t/-/399221/3?silent=true). @sam also reiterated that **workflow support** should eventually cover configurable AI response delays — [read more](https://meta.discourse.org/t/-/398209/2?silent=true). - @awesomerobot proposed an immediate UX win for rejected posts by turning rejections into editable drafts (with a linked PR), and clarified how/when the change ships after merge — [read more](https://meta.discourse.org/t/-/373992/19?silent=true) and [read more](https://meta.discourse.org/t/-/373992/21?silent=true). He also provided a detailed explanation of why Horizon’s sticky layout is hard to adjust safely without structural changes — [read more](https://meta.discourse.org/t/-/387267/11?silent=true). - @zogstrip triaged and linked fixes across multiple issues: respecting “Notify users” during bulk group invites ([read more](https://meta.discourse.org/t/-/397334/2?silent=true)), correcting an RTL external-link icon ([read more](https://meta.discourse.org/t/-/397432/2?silent=true)), and pointing to a likely fix for Topic Voting breakage ([read more](https://meta.discourse.org/t/-/399649/16?silent=true)). - @mcwumbly highlighted the long-term value of multilingual communities in response to “Building for Every Language,” praising both the narrative and the shipping features — [read more](https://meta.discourse.org/t/-/399661/2?silent=true). He also weighed in on the “content gardening hub” experiment and tag/automation behavior — [read more](https://meta.discourse.org/t/-/397606/69?silent=true). - @martin confirmed planned improvements to “Upcoming Changes,” including new sorting options (status and “when it appeared”) — [read more](https://meta.discourse.org/t/-/392894/20?silent=true). - @lindsey posted a project status update on Crowdin-related work needed for blog styling components — [read more](https://meta.discourse.org/t/-/398565/10?silent=true). * * * Yesterday’s highlight was the community collectively recovering from April 1 chaos—some folks _really_ believed their site was “seized” thanks to the full-screen cover prank theme component ([read more](https://meta.discourse.org/t/-/399690/8?silent=true)). [Previous page](https://meta.discourse.org/t/daily-summary-1pm-utc/291852.md?page=27) [Next page](https://meta.discourse.org/t/daily-summary-1pm-utc/291852.md?page=29)