# Dagelijkse samenvatting (21.00 uur UTC) **URL:** https://meta.discourse.org/t/daily-summary-9pm-utc/291850 **Category:** Forum summaries **Created:** [16 januari 2024 om 21:56 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850 "2024-01-16T21:56:19Z") **Posts on this page:** 20 **Page:** 32
### 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 mei 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/878 "2026-05-30T21:01:38Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 22 - **New topics (last 24h):** 3 **Top users (posts + likes received in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @RGJ | 3 | 4 | | @chapoi | 2 | 3 | | @NateDhaliwal | 1 | 2 | | @xlg256 | 2 | 1 | | @Bryanpwo | 1 | 1 | | @bksubhuti | 2 | 1 | | @Rubi | 1 | 1 | | @ego-lay_atman-bay | 3 | 0 | | @Lilly | 1 | 0 | | @Jose_C_Gomez | 1 | 0 | * * * ## Interesting Topics ### #Announcements - **Should nested replies be a per-user preference?** In the ongoing #Announcements discussion on #nested-replies, @bksubhuti asked why individuals can’t choose this in their personal interface settings ([read more](https://meta.discourse.org/t/-/402812/40?silent=true)). @chapoi argued that letting different users view the same shared conversation with _divergent structures_ breaks shared reference points, permalinks, and “conversation as shared space” expectations ([read more](https://meta.discourse.org/t/-/402812/41?silent=true), [read more](https://meta.discourse.org/t/-/402812/43?silent=true)). - **French translation nuance for “Support” category type.** @patrickemin flagged that translating “support” as _“soutenir”_ is incorrect in this UI context, and suggested it should remain untranslated for clarity ([read more](https://meta.discourse.org/t/-/398338/15?silent=true)). - **“Ideas” category type affecting voting behavior.** @patrickemin reported that removing the “Ideas” type from categories appears to remove the vote button as well, which seems unintended for sites that want voting outside “Ideas” categories ([read more](https://meta.discourse.org/t/-/399365/3?silent=true)). ### #Support - **Self-hosting disk pressure: “Running out of space — Docker image is large?”** A self-host admin on a 25GB VM found large usage under `/var/lib/containerd` and `/var/docker` and asked if that’s normal and what can be done before upgrading ([read more](https://meta.discourse.org/t/-/404122/1?silent=true)). @NateDhaliwal suggested trying `./launcher cleanup` as a first step ([read more](https://meta.discourse.org/t/-/404122/2?silent=true)). - **“Unfortunately, your browser is unsupported” troubleshooting.** In a support thread, @Rubi recommended checking the browser console, clearing cache/cookies, and hard refresh to resolve an “unsupported browser” message ([read more](https://meta.discourse.org/t/-/404070/3?silent=true)). @Bryanpwo followed up by asking which browser was being used, noting Firefox works across Discourse instances ([read more](https://meta.discourse.org/t/-/404070/4?silent=true)). - **Endless spinner in _one_ category (Staff) with a `name_key` error.** @Jose_C_Gomez reported an “endless spinner” affecting only their Staff category and included a stack trace pointing at `post.js` / `post-stream` hydration logic, asking why it would be scoped to a single category ([read more](https://meta.discourse.org/t/-/404136/1?silent=true)). (They referenced a similar prior incident for comparison in the same report: [read more](https://meta.discourse.org/t/-/404136/1?silent=true)). ### #bug - **Reply count not updating in “Blog Style” mode for Topic List Thumbnails.** @xlg256 reported that when using the Topic List Thumbnails theme component with the “Blog Style” layout, the reply count appears broken, and provided screenshots for diagnosis ([read more](https://meta.discourse.org/t/-/404124/1?silent=true)). (Related component context: [read more](https://meta.discourse.org/t/-/150602/353?silent=true)). ### #contribute:feature - **Making “Sign Up” easier to find on mobile (sidebar/account UX).** @awesomerobot discussed common UX patterns across popular sites and favored approaches that don’t explicitly separate login vs signup until after an email step—while acknowledging tradeoffs ([read more](https://meta.discourse.org/t/-/404022/13?silent=true)). @Lilly questioned the value if it can’t be removed, and shared a CSS-based alternative to show a “Sign up” link only for _mobile anonymous users_ ([read more](https://meta.discourse.org/t/-/404022/14?silent=true)). ### #customization:plugin - **Snapblocks: plugin vs theme component tradeoffs.** In the #customization:plugin topic tagged #bbcode, @RGJ suggested Snapblocks’ current behavior might be better implemented as a theme component rather than server-side plugin logic ([read more](https://meta.discourse.org/t/-/310155/7?silent=true)). @ego-lay_atman-bay explained they’re hooking into the message parser to prevent parsing inside tags and want WYSIWYG composer support, plus “enable once globally” behavior ([read more](https://meta.discourse.org/t/-/310155/9?silent=true)). @RGJ countered that plugins are _more_ cumbersome (rebuilds, updates, hosted plan limitations) and theme components can cover the current JS-side functionality with click-to-update convenience ([read more](https://meta.discourse.org/t/-/310155/10?silent=true), [read more](https://meta.discourse.org/t/-/310155/12?silent=true)). - **Voting button behavior tied to category type (possible glitch).** In the long-running #customization:plugin thread for #topic-voting (tagged #official and #included-in-core), @patrickemin shared findings that categories not marked as “ideas” can’t show the vote button—potentially contradicting expected behavior for mixed discussion + voting setups ([read more](https://meta.discourse.org/t/-/40121/321?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @chapoi focused on _shared conversational coherence_ in the nested replies debate, cautioning that allowing per-user display modes creates divergent mental models and undermines stable references like post ordering and meaning across participants ([read more](https://meta.discourse.org/t/-/402812/41?silent=true)). They also pushed back on the idea that engagement should outrank communication quality in Discourse’s design philosophy ([read more](https://meta.discourse.org/t/-/402812/43?silent=true)). - @awesomerobot weighed in on mobile account UX, noting that many sites prioritize login entry points (or unify login/signup flows) and outlining pros/cons of email-first “branching” patterns ([read more](https://meta.discourse.org/t/-/404022/13?silent=true)). * * * If yesterday was any indication, today’s Discourse recipe is: _a dash of nested-replies philosophy, a sprinkle of mobile signup UX debate, and just enough Docker cleanup to keep your VM from bursting at the seams._ ---
### 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 mei 2026 om 21:03 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/879 "2026-05-31T21:03:02Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 45** - **New topics (last 24h): 9** **Top users by activity (posts) and appreciation (likes):** | User | Posts | Likes | | --- | --- | --- | | @Lilly | 7 | 4 | | @Ethsim2 | 4 | 1 | | @Ed_S | 3 | 8 | | @NateDhaliwal | 3 | 5 | | @RalfJung | 2 | 2 | | @nwnuyhs | 2 | 2 | | @Jagster | 1 | 2 | | @LotusJeff | 1 | 1 | | @Ahmed26 | 1 | 1 | | @Moin | 1 | 1 | * * * ## Interesting Topics ### #Support - @long_season dug into disk pressure from self-hosting and large container layers in **“Running out of space - Docker image is large?”** ; @Ed_S suggested a cleanup workflow and shared real output from `./launcher cleanup` and image sizes ([read more](https://meta.discourse.org/t/-/404122/3?silent=true), [read more](https://meta.discourse.org/t/-/404122/5?silent=true)). - A quick “is this built-in or a plugin?” question landed as _Solved_: @haydenjames asked about a dismissible UI box, and @Lilly confirmed it’s a private theme component used by the team ([read more](https://meta.discourse.org/t/-/404166/1?silent=true), [read more](https://meta.discourse.org/t/-/404166/2?silent=true)). The thread also points to the related banner discussion ([read more](https://meta.discourse.org/t/-/233189/1?silent=true)). - In **“Unfortunately, your browser is unsupported”** , @guy_rouillier narrowed symptoms down to a site-wide landing-page issue (but topic pages loading fine), including a console error reference, while others suggested connectivity/MTU workarounds and testing steps ([read more](https://meta.discourse.org/t/-/404070/5?silent=true), [read more](https://meta.discourse.org/t/-/404070/6?silent=true)). @Lilly later reported testing on Firefox/Ubuntu successfully and suspected identity/caching quirks in the login flow ([read more](https://meta.discourse.org/t/-/404070/7?silent=true), [read more](https://meta.discourse.org/t/-/404070/9?silent=true)). - **“Forum logo isn’t showing”** was resolved after configuration review: @Lilly couldn’t reproduce and asked for branding settings; @nwnuyhs confirmed enabling “force https” in Admin settings fixed it ([read more](https://meta.discourse.org/t/-/404163/1?silent=true), [read more](https://meta.discourse.org/t/-/404163/2?silent=true), [read more](https://meta.discourse.org/t/-/404163/3?silent=true)). - **“PhotoSwipe new icons visual collision”** flagged a UI regression/UX snag: @haydenjames noted the lightbox overlay controls shifting from text to icons and colliding with screenshot content, asking if it’s been reported and whether any toggles exist ([read more](https://meta.discourse.org/t/-/404167/1?silent=true)). ### #Site feedback - The **“Creating bug reports for Discourse on Meta” guide** was reported with dead category links after the recent restructure: @RalfJung noticed `/c/bug` no longer resolves, @NateDhaliwal suggested editing to use category-ID-based links, and @Moin argued for durable permalinks when categories move or become subcategories ([read more](https://meta.discourse.org/t/-/404150/1?silent=true), [read more](https://meta.discourse.org/t/-/404150/2?silent=true), [read more](https://meta.discourse.org/t/-/404150/3?silent=true), [read more](https://meta.discourse.org/t/-/404150/4?silent=true)). ### #bug - In **“‘Unread’ tab is not listing all thread with unread messages”** , @RalfJung provided side-by-side screenshots showing unread items visible in _Latest_ but missing from _Unread_, describing the risk of silently missing required replies across hosted instances ([read more](https://meta.discourse.org/t/-/404151/1?silent=true)). - **#pwa #math** users may have hit a rendering regression: @Ethsim2 reported **“Occasional cropped delimiters on iOS portrait after recent rebuild”** (with a reproduction video and rebuild details) and noted it didn’t reproduce later in subsequent PWA sessions ([read more](https://meta.discourse.org/t/-/404148/1?silent=true)). - A permissions edge-case cropped up after an update: **“403 when setting publish\_to\_category topic timer after update”** describes a formerly-working workflow where a global moderator can no longer schedule _publish to category_ from a private staging area, receiving a 403; @Lilly asked clarifying questions about whether the affected user truly has create/post access in the staging category ([read more](https://meta.discourse.org/t/-/404164/1?silent=true), [read more](https://meta.discourse.org/t/-/404164/2?silent=true)). ### #development - Plugin authors hit a CI stumbling block: **“Github actions failing ‘Check SKIP\_DB\_AND\_REDIS bootability’ step”** explains a failure that was hard to reproduce locally, and @elmuerte tracked it to Rails boot-time DB access caused by an ActiveRecord call inside a controller constant (`Reward.attribute_names...`) ([read more](https://meta.discourse.org/t/-/404152/1?silent=true)). ### #customization:plugin - The **“Discourse Suggested Edits”** plugin saw a boot-order/race warning: @Lilly identified an initializer ordering issue (“Attempted to modify service:composer, but it was already initialized”) and proposed reordering `api.modifyClass` before `api.customizeComposerText`, including a specific code pointer and opening a PR ([read more](https://meta.discourse.org/t/-/398691/6?silent=true), [read more](https://meta.discourse.org/t/-/262064/1?silent=true)). - The **“Geo Blocking plugin”** was impacted by a core change: @LotusJeff linked an upstream GitHub issue, and @RGJ replied that the problem was resolved and attributed it to a specific Discourse core change ([read more](https://meta.discourse.org/t/-/227824/48?silent=true), [read more](https://meta.discourse.org/t/-/227824/49?silent=true)). - A deprecation warning surfaced for **“Discourse Category Lockdown”** : @Luna_Mora reported console output noting `.hbs` connector templates are deprecated and should be refactored to `.gjs` (with a deprecation reference) ([read more](https://meta.discourse.org/t/-/70649/133?silent=true), [read more](https://meta.discourse.org/t/-/398896/1?silent=true)). ### #contribute:feature - A localization request came in for #ai: in **“希望ai插件可以设置提示词为中文”** (#ai #localization), @bird asked for the AI plugin to support Chinese prompt text for things like summaries/titles/DM summaries, noting these currently default to English ([read more](https://meta.discourse.org/t/-/404143/1?silent=true), [read more](https://meta.discourse.org/t/-/404143/2?silent=true)). - Mobile UX continues to be debated: in **“Make it easier to find ‘Sign Up’ on mobile”** , @Jagster argued the sidebar/hamburger interaction is the core discoverability hurdle, and @Lilly shared that—even if not her preferred option—some approaches are being discussed because they accomplish similar goals ([read more](https://meta.discourse.org/t/-/404022/15?silent=true), [read more](https://meta.discourse.org/t/-/404022/17?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Lilly helped close the loop on a “feature or plugin?” support request by confirming a dismissible UI element is a private team theme component in **“Is this a plugin? or a built in feature.?”** ([read more](https://meta.discourse.org/t/-/404166/2?silent=true)). - @Lilly assisted troubleshooting a logo rendering issue by checking reproducibility and requesting branding settings in **“Forum logo isn’t showing”** ([read more](https://meta.discourse.org/t/-/404163/2?silent=true)). - @Lilly joined investigation of a permissions regression in **“403 when setting publish\_to\_category topic timer after update”** , focusing on whether the affected moderator has the necessary create/post access in the staging category ([read more](https://meta.discourse.org/t/-/404164/2?silent=true)). - @Lilly added field-testing and a possible caching/identity-provider angle to **“Unfortunately, your browser is unsupported”** , after verifying Firefox/Ubuntu behavior and describing a confusing password-reset loop that later resolved ([read more](https://meta.discourse.org/t/-/404070/7?silent=true), [read more](https://meta.discourse.org/t/-/404070/9?silent=true)). - @Lilly flagged and diagnosed a plugin initializer ordering issue (and opened a fix PR) in **“Discourse Suggested Edits”** ([read more](https://meta.discourse.org/t/-/398691/6?silent=true)). - @Lilly weighed in on mobile sign-up discoverability tradeoffs in **“Make it easier to find ‘Sign Up’ on mobile”** ([read more](https://meta.discourse.org/t/-/404022/17?silent=true)). * * * Vacuumed your Docker images, chased a vanishing #bug category link, and dodged a couple of 403s—just another day of spring-cleaning on Meta. ---
### 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 juni 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/880 "2026-06-01T21:01:17Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **Total new posts (last 24h): 66** - **Total new topics (last 24h): 9** _A slice of the activity came from threads like the composer redesign announcement_ ([read more](https://meta.discourse.org/t/-/403635/1?silent=true)) _and multiple bug reports around likes, unread, and uploads/CDNs_ ([read more](https://meta.discourse.org/t/-/404198/1?silent=true), [read more](https://meta.discourse.org/t/-/403986/10?silent=true), [read more](https://meta.discourse.org/t/-/404174/1?silent=true)). **Top users by recent activity (posts) & appreciation (likes):** | User | Posts | Likes | | --- | --- | --- | | @NateDhaliwal | 8 | 2 | | @Lilly | 6 | 5 | | @sam | 5 | 5 | | @martin | 3 | 3 | | @JustinZ | 3 | 3 | | @Heather_Phillips | 3 | 2 | | @RGJ | 2 | 4 | | @jordan.vidrine | 1 | 6 | | @david | 1 | 3 | | @Andrew_Rowe | 1 | 3 | (Examples of where the conversation clustered: UX around category posting permissions ([read more](https://meta.discourse.org/t/-/404204/1?silent=true)), troubleshooting “phantom/missing unread” behavior ([read more](https://meta.discourse.org/t/-/403986/10?silent=true)), and a fresh alpha composer change behind a flag ([read more](https://meta.discourse.org/t/-/403635/1?silent=true)).) * * * ## Interesting Topics ### #bug - @RGJ reported that **topic card likes stopped working** after a linting update in the #TAG `topic-cards` component, and linked a fix PR; @david merged it quickly ([read more](https://meta.discourse.org/t/-/404198/1?silent=true), [read more](https://meta.discourse.org/t/-/404198/2?silent=true)). - @Lilly found **chat thumbnails bypass `s3_cdn_url` and leak raw bucket URLs** , breaking thumbnails for some secure S3-compatible setups (e.g., Cloudflare R2) in #TAG `chat` + #TAG `cdn` + #TAG `s3`; @sam noted a rebake after site move issues ([read more](https://meta.discourse.org/t/-/404174/1?silent=true), [read more](https://meta.discourse.org/t/-/404174/2?silent=true), plus related R2 investigation context [read more](https://meta.discourse.org/t/-/358204/1?silent=true)). - In an upgrade edge case, **`db:seed_fu` failed due to a user/group name namespace collision** ; @martin investigated why an existing migration didn’t prevent the clash and moved toward a PR to reduce conflicts (and improve related permission logic) ([read more](https://meta.discourse.org/t/-/404037/5?silent=true), [read more](https://meta.discourse.org/t/-/404037/7?silent=true), [read more](https://meta.discourse.org/t/-/404037/8?silent=true), and the permissions feature referenced [read more](https://meta.discourse.org/t/-/402273/1?silent=true)). - The long-running **Unread count vs `/unread` missing topics** thread gained sharper diagnosis: @sam connected missing items to “small actions” suppression being only half-implemented, while @RalfJung argued they were missing _real posts_, not just small-action closures ([read more](https://meta.discourse.org/t/-/403986/10?silent=true), [read more](https://meta.discourse.org/t/-/403986/11?silent=true)); a related report was closed as a duplicate earlier ([read more](https://meta.discourse.org/t/-/404151/2?silent=true)). - A #TAG `composer` + #TAG `pwa` + #TAG `ios` regression where the **Reply button wasn’t visible while composing on iOS PWA** got a practical next step from @olivia: rebuild the app container to pick up the resize fix ([read more](https://meta.discourse.org/t/-/403662/6?silent=true)). - A moderator workflow started failing with **403 errors when setting `publish_to_category` topic timers** after an update; the thread continues to focus on permissions/config changes between rebuild and reproduction ([read more](https://meta.discourse.org/t/-/404164/3?silent=true), [read more](https://meta.discourse.org/t/-/404164/4?silent=true)). ### #ux - @putty flagged a confusing UX where the **“New Topic” button still appears in read-only categories** , opening the composer without the category selected; @chapoi explained why the team prefers not blocking composer entry (users may want to post elsewhere while referencing what they’re viewing), and moved the thread into #ux ([read more](https://meta.discourse.org/t/-/404204/1?silent=true), [read more](https://meta.discourse.org/t/-/404204/4?silent=true)). ### #Announcements - @jordan.vidrine introduced an alpha **composer redesign behind `enable_new_composer_actions`** , replacing the legacy SelectKit actions with a unified dropdown and embedding whisper/no-bump/unlist toggles directly in that menu ([read more](https://meta.discourse.org/t/-/403635/1?silent=true)). - The “small actions” tracking change continued to ripple outward: @sam confirmed the **suppression applies broadly to small actions including unlisting/listing** , tying back to the ongoing unread/page behavior discussions ([read more](https://meta.discourse.org/t/-/404058/3?silent=true), and the implementation context [read more](https://meta.discourse.org/t/-/404058/1?silent=true)). - Discussion continued on **branding the Discourse splash screen with SVGs** , with @Ethsim2 exploring an “escape hatch” for a truly different dark-mode asset instead of purely variable-based recoloring ([read more](https://meta.discourse.org/t/-/395100/33?silent=true)). ### #Support - @Heather_Phillips noticed **homepage topic link fonts shrinking unexpectedly** ; @chapoi pointed to the upcoming change “Modernize Foundation theme” as the likely driver and suggested disabling it; later, @chapoi considered switching sizing units (REM vs EM) to avoid overly small text ([read more](https://meta.discourse.org/t/-/404203/2?silent=true), [read more](https://meta.discourse.org/t/-/404203/6?silent=true), [read more](https://meta.discourse.org/t/-/404203/9?silent=true), with background threads referenced [read more](https://meta.discourse.org/t/-/395331/1?silent=true) and [read more](https://meta.discourse.org/t/-/403614/1?silent=true)). - A self-hosted admin got stuck where **new users were redirected to [id.discourse.com](http://id.discourse.com)**; @NateDhaliwal suggested `/u/admin-login` and shared the console setting to disable Discourse ID if needed ([read more](https://meta.discourse.org/t/-/396095/6?silent=true), [read more](https://meta.discourse.org/t/-/396095/7?silent=true)). - An admin reported an **endless spinner when staff view posts in a specific Staff category** , while a subcategory worked—suggesting a category-specific setting or data edge case worth isolating ([read more](https://meta.discourse.org/t/-/404136/2?silent=true)). ### #contribute:feature - @JustinZ requested the Discourse installer **accept pasted input** (notably for long secrets), to avoid error-prone manual typing during setup; the thread clarified it’s about installation prompts, not signup forms ([read more](https://meta.discourse.org/t/-/404191/1?silent=true), [read more](https://meta.discourse.org/t/-/404191/3?silent=true)). ### #Enterprise - @fsasaki shared a first iteration of an **Enterprise Discourse AI Getting Started Guide** , inviting feedback on feature toggles, data processed, and visibility of AI outputs ([read more](https://meta.discourse.org/t/-/404245/1?silent=true)). ### #Developer Guides - A quick documentation nit: @NateDhaliwal questioned whether the **Fedora dev setup guide** should still say “not an official guide,” implying it may need an update/clarification ([read more](https://meta.discourse.org/t/-/163348/24?silent=true)). - @NateDhaliwal asked whether **Markdown extensions** described in the dev guide can be used via a Theme Component or if they remain plugin-only—useful for folks trying to keep customization lightweight ([read more](https://meta.discourse.org/t/-/66023/24?silent=true)). ### #Integrations - A Slack integration question resurfaced: can the `discourse-chat-integration` plugin **tag specific people in Slack based on keywords** coming from Discourse notifications? ([read more](https://meta.discourse.org/t/-/66730/118?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @jordan.vidrine announced an alpha **composer actions redesign** (unified dropdown + embedded toggles) behind `enable_new_composer_actions` ([read more](https://meta.discourse.org/t/-/403635/1?silent=true)). - @sam connected the **Unread list not matching unread counts** to the ongoing “small actions suppression” implementation, and clarified it’s the same underlying issue users are observing ([read more](https://meta.discourse.org/t/-/403986/10?silent=true), [read more](https://meta.discourse.org/t/-/404058/1?silent=true)). - @sam also closed a duplicate unread-report thread, pointing folks back to the canonical discussion so fixes land in one place ([read more](https://meta.discourse.org/t/-/404151/2?silent=true), [read more](https://meta.discourse.org/t/-/403986/10?silent=true)). - @sam handled site maintenance fallout by **rebaking** (noting likely site-move related onebox oddities) in the chat thumbnail/CDN investigation thread ([read more](https://meta.discourse.org/t/-/404174/2?silent=true)). - @david merged the fix for **broken likes on topic cards** after @RGJ identified the removed getter calls and posted a PR ([read more](https://meta.discourse.org/t/-/404198/2?silent=true)). - @martin investigated a **`db:seed_fu` upgrade failure** involving auto-groups and name collisions, then moved toward a PR-level fix and noted implications for the anonymous/logged-in permissions work ([read more](https://meta.discourse.org/t/-/404037/5?silent=true), [read more](https://meta.discourse.org/t/-/404037/8?silent=true), and the referenced permissions feature thread [read more](https://meta.discourse.org/t/-/402273/1?silent=true)). - @chapoi guided a UX discussion about **why the composer can still open in read-only categories** (and recategorized the topic to #ux), emphasizing that users may want to start writing and then choose an allowed category ([read more](https://meta.discourse.org/t/-/404204/4?silent=true)). - @chapoi also helped diagnose **shrunk homepage topic fonts** as likely fallout from the “Modernize Foundation theme” upcoming change, suggested disabling it, and later considered improvements to sizing units (REM vs EM) to avoid surprises ([read more](https://meta.discourse.org/t/-/404203/2?silent=true), [read more](https://meta.discourse.org/t/-/404203/6?silent=true), [read more](https://meta.discourse.org/t/-/404203/9?silent=true), with background [read more](https://meta.discourse.org/t/-/395331/1?silent=true)). - @olivia advised a practical remediation for iOS PWA composer layout: **rebuild the app container** to pick up the latest resizing fixes ([read more](https://meta.discourse.org/t/-/403662/6?silent=true)). - @fsasaki published an initial **Enterprise Discourse AI Getting Started Guide** and explicitly asked for feedback to refine it ([read more](https://meta.discourse.org/t/-/404245/1?silent=true)). * * * _That’s a wrap—may tomorrow’s “unreads” be less phantom, and your topic-card likes stay eminently clickable._ ---
### 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 juni 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/881 "2026-06-02T21:01:59Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **70** new posts • **8** new topics - **Most active contributors (posts / likes):** | User | Posts | Likes | | --- | --- | --- | | **@jordan.vidrine** | 5 | 11 | | **@Lilly** | 6 | 5 | | **@chapoi** | 5 | 6 | | **@haydenjames** | 4 | 5 | | **@Moin** | 3 | 7 | | **@NateDhaliwal** | 3 | 5 | | **@Andrew_Bond** | 3 | 4 | | **@JimCanto** | 2 | 4 | | **@ted** | 1 | 3 | | **@featheredtoast** | 1 | 3 | - **New topics opened (highlights):** [Registration challenge to stop spam registrations](https://meta.discourse.org/t/-/404247/1?silent=true) • [Meta forcing discourse login on IOS app?](https://meta.discourse.org/t/-/404250/1?silent=true) • [Stray `` in topic-cards](https://meta.discourse.org/t/-/404301/1?silent=true) • [How to add small banner ads to a forum!](https://meta.discourse.org/t/-/404304/1?silent=true) • [Problème sur l’apostrophe en texte enrichi](https://meta.discourse.org/t/-/404312/1?silent=true) • [Possible to nest sidebar links?](https://meta.discourse.org/t/-/404314/1?silent=true) • [Passkey login: The security key is not owned by the user](https://meta.discourse.org/t/-/404317/1?silent=true) • [Как поставить Банер на главной странице](https://meta.discourse.org/t/-/404244/1?silent=true) * * * ## Interesting Topics ### #Announcements - **Foundation theme modernization hit an accessibility flashpoint.** @Moin reported low-contrast and sizing issues with the WCAG palette, @chapoi clarified Meta can’t opt-out anymore, and @jordan.vidrine apologized for delayed follow-up and committed to addressing earlier feedback—then shared multiple fixes landing via PR work ([read more](https://meta.discourse.org/t/-/395331/95?silent=true), [read more](https://meta.discourse.org/t/-/395331/98?silent=true)). Related: the font-size regression discussion in [Why did our home page topic links font shrink?](https://meta.discourse.org/t/-/404203/8?silent=true) and the ongoing #ux thread in Chinese about small homepage fonts ([read more](https://meta.discourse.org/t/-/403614/17?silent=true)). - **Nested replies: admins want _choice_ (flat vs nested), but the “view as flat” switch is gone.** A request for a global flat default with per-topic nested toggling came up, and @markvanlan confirmed the flat toggle was removed after internal testing; @jordan.vidrine explained the “wider” layout is due to the timeline being removed ([read more](https://meta.discourse.org/t/-/402812/48?silent=true), [read more](https://meta.discourse.org/t/-/402812/50?silent=true)). - **Embedding comments: confirmed you can show public comments while restricting _who can post_ to private-community members.** @JimCanto asked about “visible to all, comment only for members,” and @featheredtoast confirmed standard permission rules still apply as long as the topic is public ([read more](https://meta.discourse.org/t/-/399743/32?silent=true)). - **Events category creation flow: “calendar category” now defaults to “create event,” and that may be too opinionated.** @Lou reported friction when a category needs a calendar header but _mostly normal topics_; @awesomerobot said the default was intentional but suggested a setting might be needed for mixed-use categories ([read more](https://meta.discourse.org/t/-/401309/9?silent=true)). Related: mobile UX feedback in [It’s easier than ever to create events in Discourse!](https://meta.discourse.org/t/-/404041/2?silent=true) and ongoing breakage reports in the long-running [Events Plugin](https://meta.discourse.org/t/-/69776/891?silent=true) thread. - **Composer “Post Type” dropdown: topic-link rendering looks like it’s leaking HTML.** @jordan.vidrine flagged that the “topic link” option appears to render with HTML code mixed into the title, suggesting a formatting/escaping bug in the new composer actions UI ([read more](https://meta.discourse.org/t/-/403635/3?silent=true)). ### #Support - **Spam signup mitigation on hosted/free plans: what’s realistic without custom plugins?** A site owner asked for a signup “questionnaire” challenge; replies covered limits of UX-only challenges, using #DiscourseAI spam detection to hide spam posts, and admin workflows like `must_approve_users` ([read more](https://meta.discourse.org/t/-/404247/1?silent=true)). Related reading: [Discourse hCaptcha](https://meta.discourse.org/t/-/291383/1?silent=true), [Immediate actions you can take during a spam attack](https://meta.discourse.org/t/-/347425/1?silent=true), and [Tips for preventing spam](https://meta.discourse.org/t/-/264020/1?silent=true). - **Sidebar links: “nesting/collapsible groups” isn’t supported, but a workaround solved the immediate need.** @haydenjames wanted collapsible group links; @chapoi initially noted it’s not available, then the OP solved it using Discourse’s built-in “add custom section” approach ([read more](https://meta.discourse.org/t/-/404314/4?silent=true)). Related: [Discourse Indented Subcategories](https://meta.discourse.org/t/-/393838/1?silent=true) and collapsing custom sections discussion at [How to make a global custom section collapse by default?](https://meta.discourse.org/t/-/358845/3?silent=true). - **Ad placements: “small banner ads” in specific UI spots may require plugin constraints and accepted locations.** A support thread explored the feasibility and pointed back to standard plugin approaches like the official advertising plugin and its placement options ([read more](https://meta.discourse.org/t/-/404304/4?silent=true); see also [Discourse Advertising Plugin](https://meta.discourse.org/t/-/33734/1?silent=true)). - **PhotoSwipe icon collision fixed with CSS (but flagged as potentially fragile).** A solved thread documented a CSS workaround after icon positioning collided with OS window controls, with a caution that UI changes may break the tweak later ([read more](https://meta.discourse.org/t/-/404167/2?silent=true)). ### #bug - **Passkeys regression: “security key is not owned by the user” appears reproducible on Meta.** @pmusaraj confirmed reproduction (not Microsoft-specific) and flagged it as likely a Discourse regression worth immediate investigation ([read more](https://meta.discourse.org/t/-/404317/2?silent=true)). - **Unread count shows “Unread (14)” but the unread list is empty.** @sam noted a fix is in progress and asked affected users to hold tight while the patch lands ([read more](https://meta.discourse.org/t/-/403986/13?silent=true)). - **Invalid HTML in #topic-cards: stray `` after glimmerization.** A regression analysis explained how cells hard-coded `` and introduced invalid markup; a PR was opened to reintroduce valid structure and keep a11y behavior aligned with core ([read more](https://meta.discourse.org/t/-/404301/1?silent=true)). - **Rich-text editor on AZERTY: apostrophes turning into `l>eau`-style sequences.** A report in French was quickly routed to an existing related thread for troubleshooting and context ([read more](https://meta.discourse.org/t/-/404312/2?silent=true); related: [compositeur remplace les caractères spéciaux](https://meta.discourse.org/t/-/403905/6?silent=true)). ### #ux / #Site\_feedback / #Integrations - **UI polish: why does the “Reply” action have a background transition while text color doesn’t?** A UX thread calls out inconsistent hover/transition behavior in post actions and asks whether it’s intentional or an overlooked styling detail ([read more](https://meta.discourse.org/t/-/404362/1?silent=true)). - **Meta redesign feedback continues: tiny icons on topic lists (and more).** Follow-ups in the Meta branded theme rebuild thread highlighted icon sizing issues (topic list + inline icons), reinforcing that small visual changes can cascade into usability complaints ([read more](https://meta.discourse.org/t/-/400013/30?silent=true)). - **Embedding comments on a private forum + separate domains: a reported HTTP 419 “Page Expired” and what it implies.** An integrations thread explored private embedding constraints and domain alignment, echoing the documented limitation that fully private forums won’t embed across unrelated domains ([read more](https://meta.discourse.org/t/-/31963/491?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@jordan.vidrine** jumped into multiple design-forward threads: apologized and committed to prioritizing accessibility fixes in the Foundation theme modernization ([read more](https://meta.discourse.org/t/-/395331/95?silent=true)), posted a detailed “fixed / fixed / fixed” follow-up referencing shipped corrections ([read more](https://meta.discourse.org/t/-/395331/98?silent=true)), explained the wider nested-replies layout as a timeline-removal side effect ([read more](https://meta.discourse.org/t/-/402812/50?silent=true)), and flagged an apparent HTML rendering issue in the new composer “Post Type” dropdown ([read more](https://meta.discourse.org/t/-/403635/3?silent=true)). Also continued investigating font-size reports in the Foundation-related UX thread ([read more](https://meta.discourse.org/t/-/403614/17?silent=true)). - **@chapoi** handled a broad sweep of product/support edge cases: clarified the Foundation opt-out group is obsolete and responded to accessibility priority concerns ([read more](https://meta.discourse.org/t/-/395331/86?silent=true), [read more](https://meta.discourse.org/t/-/395331/90?silent=true)), answered sidebar nesting feasibility (and later acknowledged the misunderstanding once the OP solved it) ([read more](https://meta.discourse.org/t/-/404314/2?silent=true), [read more](https://meta.discourse.org/t/-/404314/5?silent=true)), and guided Horizon banner compatibility details in the Russian self-hosting thread ([read more](https://meta.discourse.org/t/-/404244/6?silent=true)). - **@markvanlan** confirmed a key product decision: the **“view as flat”** nested-replies toggle was removed after internal testing, as it wasn’t providing sufficient value to keep ([read more](https://meta.discourse.org/t/-/402812/48?silent=true)). - **@featheredtoast** clarified embedding permissions: visitors can see embedded comments on a public topic, but only members with permission can post—membership restrictions remain up to the community admin ([read more](https://meta.discourse.org/t/-/399743/32?silent=true)). - **@sam** provided a status update on the unread-state bug, noting a fix is underway and setting expectations for follow-up debugging if needed ([read more](https://meta.discourse.org/t/-/403986/13?silent=true)). - **@HAWK** advised on event/meetup feasibility under tighter budget scrutiny and suggested gathering data first (e.g., interest + agenda) before pushing for in-person investment ([read more](https://meta.discourse.org/t/-/389731/11?silent=true)). - **@martin** merged a PR to resolve upgrade failures caused by seed group-name conflicts, unblocking affected installs and prompting a backport request ([read more](https://meta.discourse.org/t/-/404037/13?silent=true)). - **@pmusaraj** reproduced and acknowledged the passkey login regression, flagging it for investigation and looping in another engineer for regression context ([read more](https://meta.discourse.org/t/-/404317/2?silent=true)). - **@awesomerobot** explained the rationale behind the new “Events category” default-to-event behavior and floated the idea of adding a setting for mixed event/topic categories ([read more](https://meta.discourse.org/t/-/401309/9?silent=true)). Also continued accessibility/support investigation around screen readers and shortcuts behavior ([read more](https://meta.discourse.org/t/-/404095/4?silent=true)). * * * If yesterday taught us anything, it’s that **nested replies change the shape of everything—sometimes even the timeline—and the smallest icon can start the biggest discussion.** ---
### 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: [3 juni 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/882 "2026-06-03T21:01:24Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats > Last 24 hours in review: **58 new posts** across **9 new topics**. _(Source: activity in threads linked below.)_ ### Top users (posts / likes) - **@chapoi** — **5 posts** , **6 likes** (theme/design pointers in [Approximate Meta’s design](https://meta.discourse.org/t/-/404432/2?silent=true) and settings deep-dive in [educate\_until\_posts](https://meta.discourse.org/t/-/403727/2?silent=true)) - **@haydenjames** — **4 posts** , **6 likes** (shared a new CLI tool in [Discourse-health-check](https://meta.discourse.org/t/-/404458/1?silent=true) and followed up on sidebar config in [Right Sidebar Blocks](https://meta.discourse.org/t/-/231067/195?silent=true)) - **@one1** — **4 posts** , **4 likes** (reported a pattern of signup spam in [odd spam user attack](https://meta.discourse.org/t/-/404427/1?silent=true)) - **@fhe** — **3 posts** , **6 likes** (shared a [Data Explorer](https://meta.discourse.org/t/32566?silent=true) approach for detecting bot signups in [odd spam user attack](https://meta.discourse.org/t/-/404427/4?silent=true)) - **@Andrew_Rowe** — **2 posts** , **6 likes** (shared design/navigation tips in [Approximate Meta’s design](https://meta.discourse.org/t/-/404432/3?silent=true) and spam pattern context in [odd spam user attack](https://meta.discourse.org/t/-/404427/2?silent=true)) - **@sableraph** — **2 posts** , **5 likes** (called out UX inconsistency in the review queue in [Yes/No actions](https://meta.discourse.org/t/-/404418/1?silent=true)) - **@awesomerobot** — **2 posts** , **5 likes** (suggested UX copy direction in [Yes/No actions](https://meta.discourse.org/t/-/404418/2?silent=true) and weighed in on IP blocking tradeoffs in [odd spam user attack](https://meta.discourse.org/t/-/404427/8?silent=true)) - **@adam_voulstaker** — **1 post** , **7 likes** (stopped by to say thanks in [Hi I am Adam Voulstaker](https://meta.discourse.org/t/-/404391/1?silent=true)) - **@sam** — **1 post** , **3 likes** (flagged a deployed fix for unread regression in [Unread is empty](https://meta.discourse.org/t/-/403986/15?silent=true)) - **@Roman** — **1 post** , **3 likes** (reconsidering the behavior of an education setting in [educate\_until\_posts](https://meta.discourse.org/t/-/403727/3?silent=true)) ## Interesting Topics ### #Support - @one1 reported a wave of suspicious signups with patterned usernames/emails and random values in a signup custom field, prompting suggestions like manual approvals, [Data Explorer](https://meta.discourse.org/t/32566?silent=true) queries, and strategic IP/email blocks in [Is anyone experiencing an odd spam user attack? Any way to block?](https://meta.discourse.org/t/-/404427/1?silent=true) ([read more](https://meta.discourse.org/t/-/404427/8?silent=true)) - @alehandrof asked how to replicate Meta’s look-and-feel (hidden-by-default sidebar, featured categories, simplified nav, custom sidebar, category descriptions), and @chapoi / @Andrew_Rowe pointed to building blocks like the custom homepage and theme/components in [Approximate Meta’s design in my own forum](https://meta.discourse.org/t/-/404432/1?silent=true) (see also [custom homepage feature](https://meta.discourse.org/t/-/302496/1?silent=true), [Meta branded theme rebuild + Blocks API](https://meta.discourse.org/t/-/400013/1962288?silent=true), [default hidden sidebar](https://meta.discourse.org/t/-/252984/4?silent=true), and [Featured Topics component](https://meta.discourse.org/t/-/217580/1?silent=true)) - @LetITFly hit a self-hosting pain point where avatars/images fail to upload after a Docker install; @supermathie immediately narrowed the troubleshooting to the configured upload storage backend in [Failed Uploading Avatar and Photos](https://meta.discourse.org/t/-/404430/1?silent=true) ([read more](https://meta.discourse.org/t/-/404430/2?silent=true)) - @nitinkg asked how to suppress “congrats, you’re staff now” PM/email noise while still sending `admin_confirmation_message` when granting admin/mod status via API, in [How to prevent emails other than admin confirmation when granting Admin/Moderator access?](https://meta.discourse.org/t/-/404452/1?silent=true) - @pHneutre questioned whether Microsoft and Meta/Facebook auth setups imply paid plans or surprise billing (Azure credit-card prompts; outdated Facebook docs), in [Do Microsoft and Meta authentication require payment?](https://meta.discourse.org/t/-/404421/1?silent=true) (and the related docs threads: [Configure Facebook login for Discourse](https://meta.discourse.org/t/-/13394/210?silent=true) and [Microsoft authentication](https://meta.discourse.org/t/-/51731/2?silent=true)) ### #ux - @sableraph highlighted a muscle-memory hazard in the unified review queue: **“Yes”** sometimes means “take action” (spam) and sometimes means “approve,” and @awesomerobot floated flipping the prompts so **Yes** consistently means “something’s wrong” in [Inconsistent meaning of Yes/No actions in the review queue](https://meta.discourse.org/t/-/404418/1?silent=true) ([read more](https://meta.discourse.org/t/-/404418/2?silent=true)) - Button micro-interactions got a close look: a subtle background transition on the “Reply” post action appears theme-dependent, with comparisons across Foundation / Horizon / Meta branded in [Why does the “reply” button in post actions have a background transition effect?](https://meta.discourse.org/t/-/404362/1?silent=true) ([read more](https://meta.discourse.org/t/-/404362/6?silent=true)) - A permissions UX edge case continued: users seeing “New Topic” affordances even when they can’t post, with follow-up thanks for proposed options in [New Topic still available when users don’t have permission](https://meta.discourse.org/t/-/404204/10?silent=true) ### #bug - @thgl reported that **AI Helper tag suggestions** can ignore category tag restrictions (suggesting tags you can select but then cannot submit), and @zogstrip responded with a PR already queued up for review/deploy in [AI Helper can suggest tags not allowed in category](https://meta.discourse.org/t/-/404423/1?silent=true) ([read more](https://meta.discourse.org/t/-/404423/4?silent=true)) - A regression where the UI showed an unread count but `/unread` was empty received a fix callout (including a deploy note) from @sam, in [Unread count shows Unread (14) but /unread is empty](https://meta.discourse.org/t/-/403986/15?silent=true) ### #customization:extras - @haydenjames shared a one-shot bash script to sanity-check a Discourse host (services, backups, TLS, exit codes for cron), and @Falco corrected a runtime detail (“Discourse doesn’t run Puma”) in [Discourse-health-check: one-shot CLI overview of your Discourse server](https://meta.discourse.org/t/-/404458/1?silent=true) ([read more](https://meta.discourse.org/t/-/404458/2?silent=true)) ### #customization:theme component - A quick configuration win: @haydenjames asked to increase “Top Contributors” from 5→10 in the right sidebar block, and @chapoi pointed out the existing `count` parameter in [Right Sidebar Blocks](https://meta.discourse.org/t/-/231067/195?silent=true) ([read more](https://meta.discourse.org/t/-/231067/196?silent=true)) - Topic tiles got more clickable and more robust: multiple community PRs landed for TLP (avatar wrapping, timestamp wrapping, blank tile click behavior), in [Topic List Previews (TLP)](https://meta.discourse.org/t/-/209973/735?silent=true) - Mermaid diagram support saw forward motion with a community PR submission following @Falco’s encouragement, in [Discourse Mermaid](https://meta.discourse.org/t/-/218242/55?silent=true) ### #Announcements - A fix shipped for the newly introduced “Post Type” composer actions dropdown, with @jordan.vidrine linking the PR in [Introducing a new “Post Type” Composer actions dropdown](https://meta.discourse.org/t/-/403635/4?silent=true) ### #Integrations - Facebook login documentation drift was flagged again (“/apps link is dead”), reinforcing that auth how-tos need upkeep in [Configure Facebook login for Discourse](https://meta.discourse.org/t/-/13394/210?silent=true) ### #Self-hosting - Hosting provider experiences continued: warnings about Vultr policies and a reminder that SMTP deliverability is often best handled by a specialist provider (and not necessarily your VM host) in [Vultr vs DO for discourse](https://meta.discourse.org/t/-/403964/31?silent=true) ([read more](https://meta.discourse.org/t/-/403964/32?silent=true)) ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot engaged on anti-spam tactics, endorsing signup custom fields/[Data Explorer](https://meta.discourse.org/t/32566?silent=true) approaches and reassuring that proactive IP blocking hasn’t harmed Meta’s signup flow in [odd spam user attack](https://meta.discourse.org/t/-/404427/8?silent=true), and also explored copy/flow options to make “Yes/No” review queue actions more consistent in [review queue UX](https://meta.discourse.org/t/-/404418/2?silent=true). - @chapoi helped reverse-engineer Meta’s layout: pointing admins at the custom homepage + Blocks API building blocks in [Approximate Meta’s design](https://meta.discourse.org/t/-/404432/2?silent=true), then followed up with theme-component config guidance in [Right Sidebar Blocks](https://meta.discourse.org/t/-/231067/196?silent=true). @chapoi also dug into setting semantics and proposed updating copy/behavior around `educate_until_posts` in [composer education message discussion](https://meta.discourse.org/t/-/403727/2?silent=true), and suggested webhook-based automation for flagged-post workflows (plus a hint of “something cool” coming) in [auto-reply after flag approval](https://meta.discourse.org/t/-/403359/2?silent=true). - @sam flagged a regression fix and deploy timing for unread state issues, crediting @zogstrip’s fix in [Unread is empty](https://meta.discourse.org/t/-/403986/15?silent=true). - @Roman acknowledged that recent changes may have overcorrected by making `educate_until_posts` effectively irrelevant (if the message only shows once), and committed to revisiting the implementation in [educate\_until\_posts](https://meta.discourse.org/t/-/403727/3?silent=true). - @zogstrip responded to the AI tag-suggestion/category-restriction mismatch with a fast PR turnaround and status update in [AI Helper tag restrictions](https://meta.discourse.org/t/-/404423/2?silent=true) and [follow-up](https://meta.discourse.org/t/-/404423/4?silent=true). - @jordan.vidrine linked the fix PR for the new composer “Post Type” actions dropdown in [composer dropdown announcement thread](https://meta.discourse.org/t/-/403635/4?silent=true). - @Falco reviewed a community-shared server health script and corrected a key runtime detail (“no Puma”) in [Discourse-health-check](https://meta.discourse.org/t/-/404458/2?silent=true), and also encouraged a contribution that turned into a PR for Mermaid support in [Discourse Mermaid](https://meta.discourse.org/t/-/218242/55?silent=true). - @pmusaraj clarified DiscourseHub behavior: Meta isn’t forcibly added, and the iOS re-login prompt is about a stale session rather than forced auth, in [Meta forcing discourse login on iOS app?](https://meta.discourse.org/t/-/404250/3?silent=true). - @HAWK helped troubleshoot a subtle UI animation by comparing theme behavior and probing whether the transition is just more noticeable on the reply button in [reply button transition effect](https://meta.discourse.org/t/-/404362/2?silent=true) ([read more](https://meta.discourse.org/t/-/404362/6?silent=true)). - @supermathie started diagnosis on upload failures by immediately asking which upload storage option was configured in [Failed Uploading Avatar and Photos](https://meta.discourse.org/t/-/404430/2?silent=true). Yesterday’s vibe check: between bots inventing genders at signup and the review queue making “Yes” mean _two different things_, it’s been a wonderfully chaotic day of humans vs. edge cases. ---
### 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: [4 juni 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/883 "2026-06-04T21:01:21Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New activity (last 24h):** **53** new posts, **12** new topics. Source: see the day’s new threads like the Horizon nested-replies navigation bug report ([read more](https://meta.discourse.org/t/-/404488/1?silent=true)) and the theme-import branch UX discussion ([read more](https://meta.discourse.org/t/-/404507/1?silent=true)). - **Top users (posts / likes received):** - **Also active (quick links):** tag-based “pinning”/featured content discussion ([read more](https://meta.discourse.org/t/-/404496/1?silent=true)), “approximate Meta’s design” homepage/category featuring question ([read more](https://meta.discourse.org/t/-/404432/1?silent=true)), one-topic view-count oddity ([read more](https://meta.discourse.org/t/-/403522/1?silent=true)), self-hosting provider comparisons continuing (Vultr vs DO) ([read more](https://meta.discourse.org/t/-/403964/1?silent=true)), user-card buttons missing due to theme/SCSS ([read more](https://meta.discourse.org/t/-/404526/1?silent=true)), and an RTL reactions popup direction check-in ([read more](https://meta.discourse.org/t/-/398793/2?silent=true)). * * * ## Interesting Topics **#bug** - @Andry_Osminin reported a #TAG #nested-replies state bug where replies from a previously viewed topic can remain rendered when navigating via “suggested/related topics” in-app—apparently Horizon-specific, likely tied to “instant” navigation not tearing down the prior topic state ([read more](https://meta.discourse.org/t/-/404488/1?silent=true); Horizon vs Foundation observations: [read more](https://meta.discourse.org/t/-/404488/3?silent=true); @markvanlan hints at an incoming fix: [read more](https://meta.discourse.org/t/-/404488/5?silent=true)). - Passkey login troubleshooting continued for the #TAG #passkey error _“The security key is not owned by the user”_, with @pmusaraj noting difficulty reproducing and suspecting earlier test inconsistency—while inviting more Windows/passkey implementation feedback ([read more](https://meta.discourse.org/t/-/404317/1?silent=true); latest investigation: [read more](https://meta.discourse.org/t/-/404317/3?silent=true)). - A long-running report about getting **403** errors when setting the `publish_to_category` topic timer after an update resurfaced, with the OP reaffirming permissions hadn’t changed and they were the only admin able to change category settings ([read more](https://meta.discourse.org/t/-/404164/1?silent=true); latest detail: [read more](https://meta.discourse.org/t/-/404164/5?silent=true)). * * * **#ux** - Theme import got a sharp UX audit: the “branch: main” field behaves like a placeholder, so leaving it blank sets `branch=nil` (not `main`)—leading to confusion when a theme pulls a `d-compat/...` branch instead of what admins _think_ they selected ([read more](https://meta.discourse.org/t/-/404507/1?silent=true); @chapoi escalates for triage: [read more](https://meta.discourse.org/t/-/404507/2?silent=true); clarification on intended `d-compat` behavior: [read more](https://meta.discourse.org/t/-/404507/5?silent=true)). - A mobile #TAG #pwa #ios regression made date labels appear “glitchy”; @chapoi confirmed it as a recent regression and said a fix is being worked on ([read more](https://meta.discourse.org/t/-/404484/1?silent=true); status update: [read more](https://meta.discourse.org/t/-/404484/2?silent=true)). - Composer layout edge-case: long personal-message titles overflow and get covered by buttons on Android Edge, reportedly reproducible even in [safe mode](https://meta.discourse.org/t/53504?silent=true) on the affected site (but not on Meta) ([read more](https://meta.discourse.org/t/-/404508/1?silent=true); @chapoi notes a recent composer UI change may make it obsolete and looks for a quick fix: [read more](https://meta.discourse.org/t/-/404508/2?silent=true); related composer change: [read more](https://meta.discourse.org/t/-/403635/1?silent=true)). - Review queue consistency concerns continued: users want clearer confirmation flows because “Approved/Rejected” can mean different outcomes depending on whether you’re confirming a flag vs rejecting a queued post, and “Yes/No” actions can feel inverted depending on context ([read more](https://meta.discourse.org/t/-/404418/1?silent=true); continued analysis from moderators: [read more](https://meta.discourse.org/t/-/404418/4?silent=true)). * * * **#Support** - A “silenced” confusion turned out to be historical UI: the public profile header can show a count like “silenced once” even if the admin panel shows the user is _not currently silenced_—clicking reveals when it occurred in logs ([read more](https://meta.discourse.org/t/-/404521/1?silent=true); @awesomerobot explains the historical counter: [read more](https://meta.discourse.org/t/-/404521/4?silent=true)). - Webhook troubleshooting: a `user_added_to_group` webhook began triggering ~24 minutes late; @chapoi pointed to Sidekiq queue latency (especially the `low` queue) as a likely cause and recommended using `/sidekiq` to inspect queues and busy jobs ([read more](https://meta.discourse.org/t/-/404505/1?silent=true); Sidekiq pointers: [read more](https://meta.discourse.org/t/-/404505/2?silent=true)). - Anti-abuse discussion continued around unusual spam user attacks and IP blocking tradeoffs—balancing VPN-abuse realities vs potentially excluding legitimate users in regions with pooled IP ranges ([read more](https://meta.discourse.org/t/-/404427/1?silent=true); @Ed_S cautions about pooled IP collateral damage: [read more](https://meta.discourse.org/t/-/404427/10?silent=true); @awesomerobot discusses VPNs as an abuse vector and the desire for reputation-based approaches: [read more](https://meta.discourse.org/t/-/404427/11?silent=true)). - POP3 polling issues (revisited): despite Gmail forwarding and app-specific passwords “working,” an admin wanted to clear a persistent dashboard POP3 authentication warning, noting the setup involves an address forwarding into Gmail which Discourse polls for inbound email topic creation ([read more](https://meta.discourse.org/t/-/404533/1?silent=true); earlier related thread referenced: [read more](https://meta.discourse.org/t/-/229297/1?silent=true)). * * * **#customization:extras** - A new utility tool, **discourse-health-check** , kept improving: community feedback suggested verifying whether backups have been _read_ since being written (as a proxy for offsite copying), and the author added an atime-vs-mtime check with `noatime` awareness and credits ([read more](https://meta.discourse.org/t/-/404458/1?silent=true); backup check suggestion: [read more](https://meta.discourse.org/t/-/404458/5?silent=true); implemented in v1.0.2: [read more](https://meta.discourse.org/t/-/404458/6?silent=true); and yes, _“Pitchfork nowadays!!”_ ([read more](https://meta.discourse.org/t/-/404458/4?silent=true))). * * * **#community-building Building** - Building a customer/product feedback channel: the community recommended combining #TAG topic voting with structured intake using form templates—pointing to the Topic Voting plugin and Form Templates as building blocks for upvotes + submission forms ([read more](https://meta.discourse.org/t/-/404481/1?silent=true); plugin + forms pointers: [read more](https://meta.discourse.org/t/-/404481/2?silent=true); Topic Voting plugin: [read more](https://meta.discourse.org/t/-/40121/1?silent=true); Form Templates: [read more](https://meta.discourse.org/t/-/278631/1?silent=true)). * * * **#contribute:translations** - Translation sleuthing: a missing Arabic string for reactions’ “All” label was identified as `discourse_reactions.users_popup.all`, helping locate it in Crowdin ([read more](https://meta.discourse.org/t/-/404525/1?silent=true); key name provided by @zogstrip: [read more](https://meta.discourse.org/t/-/404525/2?silent=true)). * * * **#Self-hosting** - SEO and headings: a Russian-language thread asked how to control H1/title/description on the homepage and `/categories` for SEO; replies suggested some of this is already handled by Discourse document titles and that the `title` site setting controls the suffix/branding portion ([read more](https://meta.discourse.org/t/-/404534/1?silent=true); follow-up clarifying what can be changed: [read more](https://meta.discourse.org/t/-/404534/4?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@chapoi** handled a wide spread of triage and support: asking for theme-scope repro details on the Horizon nested replies rendering bug ([read more](https://meta.discourse.org/t/-/404488/2?silent=true)), escalating the theme-import branch placeholder confusion for engineering triage ([read more](https://meta.discourse.org/t/-/404507/2?silent=true)) and aligning on the right fix direction ([read more](https://meta.discourse.org/t/-/404507/6?silent=true)), confirming an iOS/PWA date regression is being fixed ([read more](https://meta.discourse.org/t/-/404484/2?silent=true)), acknowledging the PM composer overflow and tying it to the newer composer actions UI ([read more](https://meta.discourse.org/t/-/404508/2?silent=true)), and providing the accepted Sidekiq-based explanation for webhook delays ([read more](https://meta.discourse.org/t/-/404505/2?silent=true)). - **@markvanlan** jumped into the Horizon nested replies bug thread and indicated a fix is in progress, expected in an upcoming PR impacting mobile nested topic view ([read more](https://meta.discourse.org/t/-/404488/5?silent=true)). - **@awesomerobot** clarified a key “silenced” misunderstanding—distinguishing _historical silences_ from _current status_ on profiles ([read more](https://meta.discourse.org/t/-/404521/4?silent=true))—and continued the moderation/abuse discussion on VPN/IP blocking tradeoffs and the need for something like IP reputation rather than all-or-nothing blocks ([read more](https://meta.discourse.org/t/-/404427/11?silent=true)). - **@zogstrip** helped unblock translators by naming the exact i18n key for reactions’ “All” label ([read more](https://meta.discourse.org/t/-/404525/2?silent=true)), and assisted in debugging missing user-card buttons by isolating the issue to themes/plugins via [safe mode](https://meta.discourse.org/t/53504?silent=true) and advising to identify the offending customization ([read more](https://meta.discourse.org/t/-/404526/2?silent=true); confirmation it’s customization-related: [read more](https://meta.discourse.org/t/-/404526/4?silent=true)). - **@pmusaraj** investigated the passkey login error report and shared reproduction results, suggesting early tests may have been unreliable and noting potential Windows implementation changes as a factor worth watching ([read more](https://meta.discourse.org/t/-/404317/3?silent=true)). * * * If yesterday taught us anything, it’s this: keep an eye on Sidekiq, don’t trust placeholder text, and always make sure your backups have actually been _read_—Pitchfork-approved. ---
### 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: [5 juni 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/884 "2026-06-05T21:01:42Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h):** 50 - **New topics (last 24h):** 7 **Top users (posts / likes received in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @pmusaraj | 1 | 9 | | @NateDhaliwal | 4 | 7 | | @Lee_Ars | 1 | 5 | | @one1 | 4 | 4 | | @awesomerobot | 6 | 2 | | @Tealk | 2 | 2 | | @chapoi | 4 | 2 | | @Lilly | 1 | 2 | | @Falco | 1 | 2 | | @satonotdead | 2 | 1 | * * * ## Interesting Topics ### #customization:theme - @pmusaraj released **“Accent Theme”** , a clean, card-based light theme with accent-driven styling and both light/dark schemes—plus support for common UI areas like chat and PMs ([read more](https://meta.discourse.org/t/-/404620/1?silent=true)). Related references: theme install guide ([read more](https://meta.discourse.org/t/-/63682/1?silent=true)) and the themes beginner’s guide ([read more](https://meta.discourse.org/t/-/91966/1?silent=true)). ### #customization:theme component - In **“Discourse Sidebar Menu Reorder”** , @tobiaseigen documented a sharp edge: sidebar section names must match _exactly_ (spaces become dashes), and even a trailing space can generate a slug that breaks matching—prompting @Lilly to improve the component’s guidance ([read more](https://meta.discourse.org/t/-/394049/15?silent=true), and @Lilly’s update at [read more](https://meta.discourse.org/t/-/394049/16?silent=true)). Related component: “Discourse group sidebar menus” ([read more](https://meta.discourse.org/t/-/394653/1?silent=true)). ### #Support (#automation) - In **“After user update automation…”** , @one1 explored how to trigger an automation from a required profile/custom field while _optionally_ including other fields, and @awesomerobot suggested using conditional blocks like `{{#foo}}...{{/foo}}` so empty fields don’t render ([read more](https://meta.discourse.org/t/-/404595/2?silent=true), plus the deeper explanation at [read more](https://meta.discourse.org/t/-/404595/6?silent=true)). The thread also surfaced a potential snag: custom-field names containing symbols may need normalization for templates to work smoothly ([read more](https://meta.discourse.org/t/-/404595/4?silent=true)). Background: “Using the new user update automation” ([read more](https://meta.discourse.org/t/-/296389/1?silent=true)) and “Allow ‘after user update’ automation trigger to fire without custom field” ([read more](https://meta.discourse.org/t/-/368575/1?silent=true)). - In **“How to customize AI tag and category suggestions”** (#ai #ai-helper), @Falco clarified a key implementation detail: **tag/category suggestions aren’t using LLMs** —they rely on embeddings comparing the current draft to existing topics, which explains why “prompting” doesn’t affect tag/category output the way it might for title generation ([read more](https://meta.discourse.org/t/-/404618/2?silent=true)). - **“User Shows as ‘Silenced’ Publicly but Not in Admin Dashboard”** was resolved after @Tealk noticed silences were being reversed quickly; @awesomerobot explained that if the underlying flag is rejected in the review queue, the system silence can be automatically lifted ([read more](https://meta.discourse.org/t/-/404521/6?silent=true)). - In **“Is anyone experiencing an odd spam user attack? Any way to block?”** , mitigations ranged from Cloudflare WAF rules and log exploration ([read more](https://meta.discourse.org/t/-/404427/12?silent=true) with Cloudflare best practices at [read more](https://meta.discourse.org/t/-/293405/26?silent=true)) to Discourse’s official hCaptcha plugin as a signup/bot defense ([read more](https://meta.discourse.org/t/-/404427/13?silent=true) and plugin details at [read more](https://meta.discourse.org/t/-/291383/1?silent=true)). There was also renewed interest in Cloudflare Turnstile support as a lower-friction alternative ([read more](https://meta.discourse.org/t/-/302821/1?silent=true)). ### #contribute:feature (#ai) - In **“Feature request for ai title generator: toggle title/tag/category”** , @Frully asked for per-feature toggles (title vs tag vs category suggestions), and @NateDhaliwal offered a practical workaround: hide only the title-suggestion button using CSS (`button.suggest-titles-button { display: none; }`) ([read more](https://meta.discourse.org/t/-/404580/2?silent=true)). - **“Group groups for groups page?”** resurfaced, with @satonotdead advocating for clearer hierarchy (and separating “subscriptions/team/staff” groups from trust-level concepts); @awesomerobot confirmed there’s still room to discuss, though it’s not currently prioritized ([read more](https://meta.discourse.org/t/-/58232/21?silent=true), and team reply at [read more](https://meta.discourse.org/t/-/58232/22?silent=true)). ### #Self-hosting - In **“Why can’t I install plugins locally?”** , @Willy dug into why copying plugin folders into `/var/discourse/plugins` in a production container doesn’t “just work.” @chapoi summed it up: it’s not _blocked_, it simply won’t work as expected in that setup—use `app.yml` or test locally in a dev environment; they also covered using private Git repos safely via tokens ([read more](https://meta.discourse.org/t/-/404594/6?silent=true) and private repo guidance at [read more](https://meta.discourse.org/t/-/404594/8?silent=true)). Helpful references shared: backing up/restoring to move data into a local test instance ([read more](https://meta.discourse.org/t/-/122710/1?silent=true)) and the plugin install guide (including private repos) ([read more](https://meta.discourse.org/t/-/19157/1?silent=true)). - In **“Discourse version 2026.6.0 and old browser resp OS”** , @Alfi asked for a browser/OS compatibility reference before upgrading a community with many older users; @NateDhaliwal pointed to official “supported browsers” info and suggested checking “Dumbcourse” for an older-browser-friendly UI approach ([read more](https://meta.discourse.org/t/-/404584/2?silent=true) and Dumbcourse at [read more](https://meta.discourse.org/t/-/395104/1?silent=true)). ### #ux (#mobile) - **“Could we close the user reactions list by draging the list element down…”** proposed a small-but-impactful mobile improvement: allow dismissing the reactions list by dragging within the list itself, rather than requiring a reach to the empty area above ([read more](https://meta.discourse.org/t/-/404606/1?silent=true)). - In **“Misleading ‘branch’ input in theme import”** (#fixed), @chapoi confirmed the UX confusion is addressed via a core fix (linked PR), closing the loop on misleading UI expectations in theme imports ([read more](https://meta.discourse.org/t/-/404507/8?silent=true)). ### #bug - **“Validation failed: Primary email has already been taken…”** highlighted issues handling Gmail dot-variants in inbound email and secondary email workflows; @ted agreed it appears to be a bug and suggested `normalize_emails` as a possible (but risky) mitigation while investigating ([read more](https://meta.discourse.org/t/-/404042/2?silent=true)). - In **“Oneboxed text localization issue”** (#onebox #content-localization), @nat noted improvements are planned “soon™,” signaling upcoming work on localized onebox text rendering ([read more](https://meta.discourse.org/t/-/395766/9?silent=true)). ### #wordpress - **“Old topics published via WordPress embed are missing x-robots: noindex and canonical tags”** got a practical contribution: @Thiago_Mobilon shared a plugin that adds `X-Robots-Tag: noindex` headers for topics in selected categories to help manage indexing/SEO for embedded content ([read more](https://meta.discourse.org/t/-/403109/10?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @pmusaraj shipped a brand-new theme announcement for **Accent Theme** , including preview + repo links and positioning it as “accent-color driven” with easy branding adjustments ([read more](https://meta.discourse.org/t/-/404620/1?silent=true)). - @awesomerobot was active across support + feature discussions: - @Falco provided a decisive clarification on AI behavior: **category/tag suggestions rely on embeddings, not an LLM** , which changes what kinds of customization are possible today ([read more](https://meta.discourse.org/t/-/404618/2?silent=true)). - @chapoi closed the loop on multiple admin/operator pain points: - @martin dug into a **Topic Voting** configuration report, asking for concrete examples and suggesting a rails-console check (`Category.can_vote?(cat.id)`) to diagnose category-level voting behavior ([read more](https://meta.discourse.org/t/-/40121/325?silent=true)). - @nat briefly previewed upcoming improvements to address localized onebox text issues, signalling maintenance work in the onebox + localization area ([read more](https://meta.discourse.org/t/-/395766/9?silent=true)). * * * May all your sidebar slugs be space-free, and all your automation fields render only when they’re actually filled in. ---
### 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: [6 juni 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/885 "2026-06-06T21:01:37Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 43** - **New topics (last 24h): 7** **Top contributors (posts / likes received in the last 24h):** - **@Moin** — **4 posts** , **8 likes** (e.g. language detection + translation quirks: [read more](https://meta.discourse.org/t/-/404674/2?silent=true), troubleshooting admin edit errors: [read more](https://meta.discourse.org/t/-/404684/2?silent=true)) - **@darkpixlz** — **3 posts** , **5 likes** (install connectivity + port access debugging: [read more](https://meta.discourse.org/t/-/404658/2?silent=true), Foundation theme rollout guidance: [read more](https://meta.discourse.org/t/-/404656/2?silent=true)) - **@pfaffman** — **3 posts** , **4 likes** (Virtualmin/self-hosting clarifications: [read more](https://meta.discourse.org/t/-/404658/7?silent=true), migration password-hash context: [read more](https://meta.discourse.org/t/-/403319/13?silent=true)) - **@awesomerobot** _(#team)_ — **2 posts** , **3 likes** (Microsoft OAuth docs gotchas: [read more](https://meta.discourse.org/t/-/404421/6?silent=true), tablet behavior in header links TC: [read more](https://meta.discourse.org/t/-/90588/223?silent=true)) - **@David_Ghost** — **2 posts** , **2 likes** (Cloudflare R2 legacy upload URLs: [read more](https://meta.discourse.org/t/-/358204/9?silent=true)) - **@Denis_Advert** — **1 post** , **3 likes** (asking about Foundation theme improvements: [read more](https://meta.discourse.org/t/-/404656/1?silent=true)) - **@typed-sigterm** — **1 post** , **2 likes** (China + WeChat Mini Program context: [read more](https://meta.discourse.org/t/-/312085/10?silent=true)) - **@Andro** — **1 post** , **2 likes** (nested replies experimental feature failure case: [read more](https://meta.discourse.org/t/-/404662/1?silent=true)) - **@NateDhaliwal** — **1 post** , **2 likes** (email provider recommendation in auth discussion: [read more](https://meta.discourse.org/t/-/403735/29?silent=true)) - **@RGJ** — **1 post** , **2 likes** (defending migrated password-hash approach: [read more](https://meta.discourse.org/t/-/403319/14?silent=true)) * * * ## Interesting Topics #### #Support - @Denis_Advert noticed big UI/typography improvements in the Foundation theme and asked when they’ll roll out everywhere; @darkpixlz pointed out you can enable it via the **“Modernize foundation theme”** upcoming change toggle (no global timeline yet). [read more](https://meta.discourse.org/t/-/404656/1?silent=true) ([solution context](https://meta.discourse.org/t/-/404656/2?silent=true)) - A self-host install hit the dreaded “ **Port 443… does not appear to be accessible** ” despite earlier checks passing; @darkpixlz suggested bypassing the connectivity test with `--skip-connection-test` and linked prior learnings, while @pfaffman clarified that you **should not install Postgres manually** (Docker includes what’s needed) and that port ownership/exposure is the real culprit. [read more](https://meta.discourse.org/t/-/404658/1?silent=true) ([skip-test workaround](https://meta.discourse.org/t/-/404658/4?silent=true), [follow-up clarifications](https://meta.discourse.org/t/-/404658/7?silent=true), [related thread](https://meta.discourse.org/t/-/396661/1?silent=true)) - Experimental #nested-replies got called out as “a disaster” after users reported missing posts and the admin couldn’t revert cleanly—raising concerns about how reversible upcoming changes are when something goes sideways. [read more](https://meta.discourse.org/t/-/404662/1?silent=true) - After restoring a test site, @Maxine reported that **all upload URLs (including avatars)** rewrote back to the forum domain instead of the S3 bucket URL, and asked both how to fix and how to prevent it in production (#s3 #hosting). [read more](https://meta.discourse.org/t/-/404659/1?silent=true) - A reproducible mobile-web issue: the **new-topic composer** appears _crushed/too small_ on “iOS 26.5 Safari Web”, while replies still work—reported with screenshots from [try.discourse.org](http://try.discourse.org) and user agent details (#ios-26). [read more](https://meta.discourse.org/t/-/404681/1?silent=true) - Admin topic editing errors: @stephtara hit failures editing multiple topics and asked where to troubleshoot; @Moin recommended checking the browser console and `/logs`, and the follow-up mentioned JS errors like “Failed to load discourse-custom-wizard”. [read more](https://meta.discourse.org/t/-/404684/1?silent=true) ([first troubleshooting step](https://meta.discourse.org/t/-/404684/2?silent=true)) - OAuth reality check: @awesomerobot walked through Microsoft login and found it requires a **free Azure/Entra setup** (including a credit card during registration) but not necessarily payment; they also tested Facebook login and noted the “verify as a business” friction that can block completion (#auth-plugins #365-oauth #social-auth). [read more](https://meta.discourse.org/t/-/404421/6?silent=true) ([topic start](https://meta.discourse.org/t/-/404421/1?silent=true)) #### #bug - Composer auto-replacement pain: a French-writing workflow got wrecked by special-character substitution (especially apostrophes), prompting @stephtara to disable the setting—even while mourning the loss of emdash replacement (#composer). [read more](https://meta.discourse.org/t/-/403905/12?silent=true) - Cloudflare R2 migrations: @David_Ghost reported that **older uploads** still render with the R2 endpoint URL (and only show correctly with a particular theme component), while @Lilly suggested running `uploads:migrate_to_s3`, rebaking posts, and ensuring `DISCOURSE_S3_CDN_URL` is set—plus a possible `discourse remap` fallback. [read more](https://meta.discourse.org/t/-/358204/9?silent=true) ([rake + rebake guidance](https://meta.discourse.org/t/-/358204/10?silent=true), [CDN URL ordering](https://meta.discourse.org/t/-/358204/12?silent=true)) #### #Site feedback - AI language detection & stale translations: @stephtara saw an English post labeled as French (apparently triggered by the word “French”), then edits “not showing” until it became clear they were viewing an outdated translation; @Moin explained the locale button and how translations can lag edits (#ai #dynaloc #content-localization). [read more](https://meta.discourse.org/t/-/404674/1?silent=true) ([diagnosis](https://meta.discourse.org/t/-/404674/2?silent=true), [follow-up](https://meta.discourse.org/t/-/404674/4?silent=true)) #### #ux - The “New Topic” button appearing even when users can’t post got an update: @Moin surfaced that a hidden site setting (`hide_disabled_create_topic_button`) can restore the older behavior—hiding the button in read-only contexts once you’re on a version that includes the merged change. [read more](https://meta.discourse.org/t/-/404204/11?silent=true) #### #customization:theme component - The Image Comparison Slider theme component got a substantial modernization proposal: @Arkshine shared a PR adding zoom/pan, fullscreen, lightbox originals, keyboard accessibility, RTE editing support, group restrictions, and a new `[wrap]`-based format—while keeping backward compatibility. [read more](https://meta.discourse.org/t/-/264479/33?silent=true) #### #development - WeChat Mini Program integration: the thread explored whether embedding Discourse inside a Mini Program is worth it, the challenges around WeChat identity/email, and broader China-specific browser/app ecosystem constraints; @typed-sigterm added on-the-ground context for why “just open it in a browser” often isn’t realistic. [read more](https://meta.discourse.org/t/-/312085/10?silent=true) ([ecosystem context](https://meta.discourse.org/t/-/312085/13?silent=true), [related WeChat login thread](https://meta.discourse.org/t/-/221343/1?silent=true)) #### #support:migration - PHPBB migration security tradeoffs: @pfaffman recommended the long-standing **migrated password hashes** approach for self-hosters, while @RGJ pushed back on blanket “don’t migrate passwords” advice, noting the plugin’s track record and emphasizing keeping insecure-password allowances disabled. [read more](https://meta.discourse.org/t/-/403319/13?silent=true) ([plugin reference](https://meta.discourse.org/t/-/19512/1?silent=true), [security discussion](https://meta.discourse.org/t/-/403319/14?silent=true)) #### #Site Management - Auto-bump refinement request: @patrickemin suggested making auto-bump selection smarter by factoring in _interest signals_ (views/votes) and _age thresholds_, and referenced a related pain point about keeping only the last auto-bump alert message. [read more](https://meta.discourse.org/t/-/262158/31?silent=true) ([related suggestion thread](https://meta.discourse.org/t/-/365825/1?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @awesomerobot investigated real-world friction in third-party auth setups—confirming Microsoft login can be configured with a **free Azure/Entra account** (credit card required during setup, but not necessarily paid) and documenting where Facebook login flow can dead-end without business verification. [read more](https://meta.discourse.org/t/-/404421/6?silent=true) - @awesomerobot also chimed in on responsive behavior nuances for the **Custom Header Links** theme component—reminding everyone that tablet layout behavior depends on device size and orientation. [read more](https://meta.discourse.org/t/-/90588/223?silent=true) * * * > Yesterday’s vibe: between AI confidently “detecting” French from the word _French_ and admins learning the magic of `--skip-connection-test`, it was a day of _polite chaos and practical workarounds_ on Meta. ---
### 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: [7 juni 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/886 "2026-06-07T21:02:12Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New topics (last 24h): 3** - **New posts (last 24h): 22** **Top posters (with likes received in the last 24h):** - @stephtara — **4 posts** , **2 likes** (incl. theme/debug digging in [read more](https://meta.discourse.org/t/-/404684/6?silent=true) and Safari/Air Theme follow-up in [read more](https://meta.discourse.org/t/-/197703/605?silent=true)) - @merefield — **2 posts** , **4 likes** (pricing/free-plan discussion: [read more](https://meta.discourse.org/t/-/404699/3?silent=true)) - @ice.d — **2 posts** , **2 likes** (free plan + groups question: [read more](https://meta.discourse.org/t/-/404699/2?silent=true), [read more](https://meta.discourse.org/t/-/404701/1?silent=true)) - @Moin — **2 posts** , **1 like** (nested replies expectations + groups pseudo-group nuance: [read more](https://meta.discourse.org/t/-/404662/3?silent=true), [read more](https://meta.discourse.org/t/-/402273/5?silent=true)) - @Lilly — **1 post** , **2 likes** (Cloudflare R2/chat thumbnail fix pointer: [read more](https://meta.discourse.org/t/-/358204/14?silent=true)) - @mcdanlj — **1 post** , **1 like** (spam handling / block-email-vs-IP idea: [read more](https://meta.discourse.org/t/-/404427/14?silent=true)) - @itsbhanusharma — **1 post** , **1 like** (primary group → flair precedence: [read more](https://meta.discourse.org/t/-/404701/2?silent=true)) - @David_Ghost — **1 post** , **1 like** (R2 thumbnail behavior details: [read more](https://meta.discourse.org/t/-/358204/13?silent=true)) - @ばこん — **1 post** , **1 like** (free plan economics question: [read more](https://meta.discourse.org/t/-/404699/1?silent=true)) - @Hasimir — **1 post** , **0 likes** (Custom Wizard crash report with stack trace: [read more](https://meta.discourse.org/t/-/73345/959?silent=true)) * * * ## Interesting Topics ### #contribute:site-feedback - @ばこん asked how Discourse can sustainably offer a **free plan** , with @merefield framing it as a sensible _conversion funnel_ business model and @ice.d pointing to paid-plan economics ([read more](https://meta.discourse.org/t/-/404699/1?silent=true), [read more](https://meta.discourse.org/t/-/404699/3?silent=true)). ### #bug - Ongoing investigation into **Cloudflare R2 image URL / thumbnail display** issues: @David_Ghost reported old thumbnails still broken even after remapping, while @Lilly shared a fix-in-progress and linked a related chat-thumbnail thread ([read more](https://meta.discourse.org/t/-/358204/13?silent=true), [read more](https://meta.discourse.org/t/-/358204/14?silent=true), plus related: [read more](https://meta.discourse.org/t/-/404174/1?silent=true)). ### #Support - A fresh report that the **#nested-replies experimental feature** may be buggy (or at least under-documented in the community so far): @Moin noted it’s new, it’s the weekend, and suggested alternate routes for quicker attention ([read more](https://meta.discourse.org/t/-/404662/1?silent=true), [read more](https://meta.discourse.org/t/-/404662/3?silent=true)). - Spam defenses and tradeoffs: in an “odd spam user attack” thread, @mcdanlj advocated _suspending forever_ to harvest patterns and argued for an option to **block email without blocking IP** , with @Ed_S agreeing and comparing moderation workflows ([read more](https://meta.discourse.org/t/-/404427/14?silent=true), [read more](https://meta.discourse.org/t/-/404427/15?silent=true)). - Group management clarity: @ice.d asked what **setting a “primary group”** is actually for, and @itsbhanusharma highlighted a practical win— **flair precedence** when multiple group flairs exist ([read more](https://meta.discourse.org/t/-/404701/1?silent=true), [read more](https://meta.discourse.org/t/-/404701/2?silent=true)). - A Safari-only editor failure was narrowed down: @stephtara tracked an **error when editing a topic** to the presence of **tags** , observed it disappears in [safe mode](https://meta.discourse.org/t/53504?silent=true) / with other themes, and suspected the **#air-theme** path specifically ([read more](https://meta.discourse.org/t/-/404684/6?silent=true), plus the cross-reference in the Air Theme thread: [read more](https://meta.discourse.org/t/-/197703/605?silent=true)). - Discourse Automation field templating: @one1 confirmed `{{languages}}` works but struggled with profile/custom fields whose names contain punctuation/parentheses, raising the possibility of either naming constraints or a needed code-level tweak ([read more](https://meta.discourse.org/t/-/404595/8?silent=true)). ### #self-hosting - @stephtara explored the idea of giving **Claude Code read-only access** to a self-hosted Discourse (SSH + DB), seeking ways to lock down sensitive paths and permissions while still enabling efficient troubleshooting ([read more](https://meta.discourse.org/t/-/404698/1?silent=true)). ### #announcements - In the **granular group-based permissions** announcement thread, @Moin dug into theme-component implications and “pseudo-group” behavior, referencing prior art and edge-cases around group-ID comparisons ([read more](https://meta.discourse.org/t/-/402273/5?silent=true), and mentioned component context: [read more](https://meta.discourse.org/t/-/386594/1?silent=true)). ### #customization:plugin - Calendar UX request: @Lou asked whether event **locations** could support typeahead/lookup (like Google Calendar/Facebook) and become **clickable to open map apps** ([read more](https://meta.discourse.org/t/-/97376/598?silent=true)). - Potential breaking change: @Hasimir reported that a recent core update appears to crash the **discourse-custom-wizard** plugin during boot (even blocking [safe mode](https://meta.discourse.org/t/53504?silent=true)), sharing an `admin_stylesheets` registry error and confirming disabling the plugin restores startup ([read more](https://meta.discourse.org/t/-/73345/959?silent=true)). ### #customization:theme - More signals that **Air Theme** may have a Safari-specific interaction issue, with @stephtara providing a reproducible path tied to editing a tagged topic ([read more](https://meta.discourse.org/t/-/197703/605?silent=true) and supporting investigation notes in [read more](https://meta.discourse.org/t/-/404684/6?silent=true)). - On **FKB Pro** , @xlg256 praised the card UI but reported confusing mobile “hit-or-miss” tap targets, proposing a CSS _pointer-events whitelist_ approach so only key content areas are clickable ([read more](https://meta.discourse.org/t/-/234323/496?silent=true)). ### #development - The long-running WeChat Mini Program integration thread saw activity (a post by @merefield was later deleted by the author), indicating continued interest/maintenance attention in that integration space ([read more](https://meta.discourse.org/t/-/312085/18?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @Lilly followed up on the Cloudflare R2/chat thumbnail display investigation, noting that prior steps didn’t resolve it for the reporter and pointing to a PR/fix thread for chat thumbnails ([read more](https://meta.discourse.org/t/-/358204/14?silent=true), related fix thread: [read more](https://meta.discourse.org/t/-/404174/1?silent=true)). * * * Yesterday’s vibe: _we chased Safari tagging gremlins, debated the economics of “free,” and tightened the anti-spam toolkit—all before the weekend even cooled down_ ([read more](https://meta.discourse.org/t/-/404684/6?silent=true), [read more](https://meta.discourse.org/t/-/404699/3?silent=true), [read more](https://meta.discourse.org/t/-/404427/14?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: [8 juni 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/887 "2026-06-08T21:02:02Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 63** - **New topics (last 24h): 7** **Top contributors (posts / likes in the last 24h):** | User | Posts | Likes | | --- | --- | --- | | @awesomerobot | 7 | 5 | | @Moin | 5 | 4 | | @fearlessfrog | 4 | 4 | | @markvanlan | 4 | 3 | | @HAWK | 3 | 7 | | @haydenjames | 3 | 3 | | @david | 2 | 4 | | @Canapin | 2 | 4 | | @martin | 2 | 3 | | @Zanbabe | 1 | 4 | **A few threads that drove the conversation today (quick links):** [Boosts paused on Meta](https://meta.discourse.org/t/-/399835/85?silent=true) · [iOS composer too small](https://meta.discourse.org/t/-/404681/2?silent=true) · [Nested replies navigation rendering bug](https://meta.discourse.org/t/-/404488/7?silent=true) · [Right sidebar tags block conflict](https://meta.discourse.org/t/-/404723/1?silent=true) · [Free plan explained](https://meta.discourse.org/t/-/404699/4?silent=true) * * * ## Interesting Topics ### #Site feedback - @HAWK clarified that Discourse’s free tier is effectively a **freemium acquisition** layer (often behaving like an “indefinite free trial”), while others dug into what “power usage” really means in terms of typical server sizing and cost — [read more](https://meta.discourse.org/t/-/404699/4?silent=true). Related context on the “minimum vs recommended” hosting footprint was also shared from install guidance — [read more](https://meta.discourse.org/t/-/404699/7?silent=true) ### #Announcements - Meta’s live experiment with **Boosts** was **disabled for now** after feedback, with commenters asking Discourse not to abandon the idea and suggesting it could complement likes/reactions rather than replace them — [read more](https://meta.discourse.org/t/-/399835/85?silent=true). Several folks argued for making Boosts an optional mode alongside classic reactions — [read more](https://meta.discourse.org/t/-/399835/89?silent=true) ### #Announcements - The “Solved improvements” feature (letting users indicate they’re also experiencing an issue) got follow-up tweaks: it’s now a **category-specific setting** , and the button label can be customized right in category settings — [read more](https://meta.discourse.org/t/-/402498/40?silent=true). This should make it easier to enable for true support areas while keeping noise out of categories where it doesn’t fit — [read more](https://meta.discourse.org/t/-/402498/40?silent=true) ### #Support - On iOS Safari (iOS 26.5), the **new topic editor/composer can become unusably small** ; @awesomerobot suggested hiding the toolbar via the `☰` button as a temporary workaround while considering UI improvements to preserve at least one line for typing — [read more](https://meta.discourse.org/t/-/404681/2?silent=true). The discussion also resurfaced a mobile fullscreen composer theme component thread, now updated to work on newer Discourse versions — [read more](https://meta.discourse.org/t/-/255225/54?silent=true) ### #bug - A navigation bug where **posts from the previous topic remain rendered** after in-app navigation received an update: @markvanlan noted the fix landed as part of a larger mobile UX refactor and was merged, with a request for testers to confirm after updating — [read more](https://meta.discourse.org/t/-/404488/8?silent=true). The same area also references ongoing quirks like the formatting of the `views` label — [read more](https://meta.discourse.org/t/-/404488/8?silent=true) ### #Support - The experimental **#nested-replies** feature caused a nasty failure mode when toggled: disabling it could lead to missing-message errors, and @markvanlan asked for screenshots + suggested URL swapping (`/n/` ↔ `/t/`) as a diagnostic — [read more](https://meta.discourse.org/t/-/404662/5?silent=true). The thread highlights how hard “safe rollback” can be for experimental UX features if URLs/routes behave differently — [read more](https://meta.discourse.org/t/-/404662/8?silent=true) ### #contribute:feature - A request came in to include **reply-to notation in `/raw//` output** , so raw text can preserve reply relationships; responders pointed out the JSON already includes `reply_to_post_number`, and asked for more context to clarify the need — [read more](https://meta.discourse.org/t/-/404722/1?silent=true). If you’re building tooling, this is also a good moment to confirm whether JSON endpoints can replace raw text for your workflow — [read more](https://meta.discourse.org/t/-/404722/2?silent=true) ### #bug - The **Right Sidebar “Tags” block** appears to “consume” tag data on load, leaving the _native_ header tag dropdown empty; @chapoi confirmed reproducibility and called for triage — [read more](https://meta.discourse.org/t/-/404723/2?silent=true). The report includes clear reproduction steps and a simple workaround (remove the block) while awaiting a fix — [read more](https://meta.discourse.org/t/-/404723/1?silent=true) ### #ux - On tag pages, the **tag info (`circle-info`) button** can appear clickable but do nothing (notably on localized tag paths like `/ap/about`); @awesomerobot filed a PR to hide the button when the reused component lacks the data it expects — [read more](https://meta.discourse.org/t/-/402436/10?silent=true). This is a nice example of a “component reuse” edge case that only shows up in less common navigation flows — [read more](https://meta.discourse.org/t/-/402436/9?silent=true) ### #ux - An edge case in **content localization** was documented where the UI language stays English while topic list elements (titles/tags/excerpts) partially flip to German after changing the header language in a separate tab — [read more](https://meta.discourse.org/t/-/404774/1?silent=true). The repro steps are concrete and should help narrow down caching/state leakage across tabs — [read more](https://meta.discourse.org/t/-/404774/1?silent=true) ### #ux - Theme import UX got a practical polish: the “branch” input can be misleading, so @david opened a PR to show the **actually installed branch** and the resolved target branch used for updates — [read more](https://meta.discourse.org/t/-/404507/10?silent=true). This comes from real-world confusion where instances pulled from a compat branch instead of `main` — [read more](https://meta.discourse.org/t/-/404507/10?silent=true) ### #ux - Foundation-theme-related font sizing is still a hot topic: users noticed subtle UI improvements, while others reported the homepage font becoming _too small_ after rebuild updates; @jordan.vidrine confirmed it’s on the fix list — [read more](https://meta.discourse.org/t/-/403614/19?silent=true). Related chatter continues in the broader “Modernizing the Foundation theme” announcement thread — [read more](https://meta.discourse.org/t/-/395331/99?silent=true) ### #development - A developer workflow issue: GitHub Actions failing a **“Check SKIP\_DB\_AND\_REDIS bootability”** step led @david to suggest toggling `schema_cache_dump` to reproduce locally, and floated the idea of adding an ENV to control it more cleanly — [read more](https://meta.discourse.org/t/-/404152/3?silent=true). The report calls out a specific ActiveRecord attribute edge case that likely wasn’t considered previously — [read more](https://meta.discourse.org/t/-/404152/3?silent=true) ### #development - A Chinese-language dev post shared an **AI/LLM-assisted refactor** of a Flarum import script (tested and posted as a gist), and @cocococosti asked for more detail about the migration needs to better understand the use case — [read more](https://meta.discourse.org/t/-/404732/5?silent=true). If this grows legs, it could become a handy community-maintained bridge for Flarum → Discourse migrations — [read more](https://meta.discourse.org/t/-/404732/1?silent=true) ### #Self-hosting - A security-minded question on giving **Claude Code read-only access** to a self-hosted install got a candid answer: you _can_ create a read-only SSH user, but it can still read highly sensitive data (PMs, hashes, IPs, API keys), so a sanitized duplicate environment is often safer — [read more](https://meta.discourse.org/t/-/404698/2?silent=true). This aligns with Discourse Team’s own policy of not allowing LLM access to production databases — [read more](https://meta.discourse.org/t/-/404698/2?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @HAWK helped explain Discourse’s **free plan positioning** as freemium/funnel tiering in [“Why are you able to offer a free plan?”](https://meta.discourse.org/t/-/404699/4?silent=true), and also clarified the purpose of **primary groups** (styling, default titles, flair, “main affiliation”) in [“What is the point in primary’s”](https://meta.discourse.org/t/-/404701/3?silent=true). - @martin flipped the switch to **disable Boosts on Meta** while the team evaluates next steps in [“Testing Boosts on Meta”](https://meta.discourse.org/t/-/399835/85?silent=true), and was pinged for triage on the sidebar tags regression in [“Tags block is conflicting with other tag dropdowns”](https://meta.discourse.org/t/-/404723/2?silent=true). - @awesomerobot covered a wide spread: composer usability on iOS in [“New Topic Editor Too Small iOS 26.5 Safari Web”](https://meta.discourse.org/t/-/404681/2?silent=true), a fix/PR for the tag info button in [“Where did the tag info button go?”](https://meta.discourse.org/t/-/402436/10?silent=true), min/max validation work in [“Survey plugin min/max not implemented nor validated”](https://meta.discourse.org/t/-/404023/2?silent=true), plus guidance on restores + S3 setup in [“Images after a restore don’t have S3 bucket URL”](https://meta.discourse.org/t/-/404659/2?silent=true). - @markvanlan shipped and confirmed a merged fix for the **topic navigation rendering issue** in [“Posts from the topic I just left stay rendered…”](https://meta.discourse.org/t/-/404488/8?silent=true), and jumped into a high-urgency support case on **#nested-replies** rollback breakage in [“Nested replies experimental feature buggy”](https://meta.discourse.org/t/-/404662/5?silent=true). - @david pushed UX improvements and debugging advice: clarifying the installed/target theme branch in [“Misleading ‘branch’ input in theme import”](https://meta.discourse.org/t/-/404507/10?silent=true) and suggesting a reproduction path for CI failures in [“Github actions failing ‘Check SKIP\_DB\_AND\_REDIS bootability’ step”](https://meta.discourse.org/t/-/404152/3?silent=true). - @lindsey posted concrete admin-facing improvements for issue-reporting signals in solved topics via [“Solved improvements: Allowing members to indicate they’re experiencing a reported issue”](https://meta.discourse.org/t/-/402498/40?silent=true). - @manuel pointed theme authors to a practical example theme approach when someone wanted to match Meta’s look in [“Approximate Meta’s design in my own forum”](https://meta.discourse.org/t/-/404432/6?silent=true), linking out to theme-building guidance in [“Skills for authoring themes and blocks”](https://meta.discourse.org/t/-/401629/1?silent=true) and additional ideas like [“Featured Categories Header”](https://meta.discourse.org/t/-/203779/1?silent=true). - @cocococosti thanked and followed up on the community-shared Flarum importer refactor in [“利用 AI LLM 重构 Flarum 导入脚本以迁移至 Discourse”](https://meta.discourse.org/t/-/404732/5?silent=true). - @chapoi kept the rails greased across multiple threads: asking for clearer context on a feature request in [“Include reply notation in raw text”](https://meta.discourse.org/t/-/404722/3?silent=true), confirming the sidebar tags block bug in [“Tags block is conflicting with other tag dropdowns”](https://meta.discourse.org/t/-/404723/2?silent=true), merging improvements for Horizon cards/events in [“Horizon: High Context Topic Cards”](https://meta.discourse.org/t/-/393470/30?silent=true), and pointing to a core fix for PM title overflow in [“Long personal message titles overflow in composer”](https://meta.discourse.org/t/-/404508/4?silent=true). - @jordan.vidrine acknowledged and queued a fix for the post-rebuild font sizing regression in [“刚才rebuild更新后，首页字体变的很小”](https://meta.discourse.org/t/-/403614/19?silent=true). * * * _Yesterday’s vibe check:_ Boosts may be paused, but the community still found plenty of ways to boost ideas—especially by making composers bigger, tags less confusing, and branches more honest. ---
### 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: [9 juni 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/888 "2026-06-09T21:02:23Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 72** - **New topics (last 24h): 9** - **Most-liked post of the day:** @lindsey’s preview of the redesigned admin dashboard hit **21 likes** — [read more](https://meta.discourse.org/t/-/404528/1?silent=true) **Top users (posts / likes, last 24h)** | User | Posts | Likes | Recent highlight | | --- | --- | --- | --- | | @lindsey | 3 | 21 | Shared an early look at the redesigned admin dashboard — [read more](https://meta.discourse.org/t/-/404528/1?silent=true) | | @martin | 4 | 15 | Announced the unified “New” topic list experience — [read more](https://meta.discourse.org/t/-/404728/1?silent=true) | | @nat | 2 | 7 | Chimed in on KPI customization requests for the new dashboard — [read more](https://meta.discourse.org/t/-/404528/3?silent=true) | | @soeren-1 | 2 | 6 | Asked for customizable KPIs and group controls in the dashboard redesign — [read more](https://meta.discourse.org/t/-/404528/2?silent=true) | | @HAWK | 2 | 6 | Started a discussion on community ownership models in enterprises — [read more](https://meta.discourse.org/t/-/404814/1?silent=true) | | @chapoi | 3 | 5 | Helped clarify unified new + shared Discourse GIFs mobile toolbar update — [read more](https://meta.discourse.org/t/-/404728/3?silent=true), [read more](https://meta.discourse.org/t/-/158738/294?silent=true) | | @Moin | 4 | 4 | Explained update cadence & nuances of New/Unread behavior — [read more](https://meta.discourse.org/t/-/404728/7?silent=true) | | @elmuerte | 3 | 3 | Continued investigating SKIP\_DB\_AND\_REDIS bootability checks — [read more](https://meta.discourse.org/t/-/404152/8?silent=true) | | @pfaffman | 1 | 3 | Reported a regression around searching user custom fields in `/u` — [read more](https://meta.discourse.org/t/-/404800/1?silent=true) | | @singi2016cn | 1 | 3 | Suggested likely network/Gem download issues during rebuild in China — [read more](https://meta.discourse.org/t/-/404816/7?silent=true) | _A few more threads that also saw fresh momentum:_ nested replies feedback and fixes — [read more](https://meta.discourse.org/t/-/402812/55?silent=true) — plus right-sidebar tag dropdown conflicts — [read more](https://meta.discourse.org/t/-/404723/4?silent=true) — and user-directory filtering edge cases — [read more](https://meta.discourse.org/t/-/404885/1?silent=true). * * * ## Interesting Topics ### #Announcements - A **highly experimental redesign of the admin dashboard** was previewed by @lindsey, focusing on a more modular hub for KPIs, pinned reports (including [Data Explorer](https://meta.discourse.org/t/32566?silent=true) queries), traffic, and engagement—follow-up discussion quickly zeroed in on _customizable KPIs_ and better-fit stats for non-public/internal communities (#dashboard) — [read more](https://meta.discourse.org/t/-/404528/1?silent=true) (see also the KPI customization ask: [read more](https://meta.discourse.org/t/-/404528/2?silent=true), and the follow-up question from @lindsey: [read more](https://meta.discourse.org/t/-/404528/4?silent=true)). - Discourse introduced the **unified “New” view** as the upcoming default topic-list experience, consolidating the old `/new` and `/unread` split into clearer subtabs (Topics / Replies / All), with guidance to manage it via “Upcoming changes” — [read more](https://meta.discourse.org/t/-/404728/1?silent=true) (background: [read more](https://meta.discourse.org/t/-/278811/1?silent=true), and the “Upcoming changes” system: [read more](https://meta.discourse.org/t/-/392894/1?silent=true)). - “Testing Boosts on Meta” got an update from @martin noting that rolling boosts/likes/reactions may return, but the combined concept isn’t getting full attention right now — [read more](https://meta.discourse.org/t/-/399835/90?silent=true). - The nested replies announcement thread continues to collect real-world UX feedback (including alternative collapse patterns and moderation visibility concerns), with settings-based suggestions and PR follow-ups (#nested-replies) — [read more](https://meta.discourse.org/t/-/402812/52?silent=true) (and the recent fix pointer: [read more](https://meta.discourse.org/t/-/402812/55?silent=true)). - The Horizon theme’s **High Context Topic Cards** got a positive field report after someone “gave it a spin” and shared screenshots (#horizon-theme) — [read more](https://meta.discourse.org/t/-/393470/32?silent=true). ### #bug - A likely regression was reported where the **user directory (`/u`) search fails to match user custom fields** even though global search does; @zogstrip replied with a fix PR to align the code paths (#user-directory) — [read more](https://meta.discourse.org/t/-/404800/1?silent=true) (fix note: [read more](https://meta.discourse.org/t/-/404800/3?silent=true)). - A new report showed **SVG badge icons importing but not rendering** , with @awesomerobot diagnosing missing dimensions (common with some Font Awesome SVGs) and preparing a core fix (#badges #bug) — [read more](https://meta.discourse.org/t/-/404832/1?silent=true) (diagnosis + PR link: [read more](https://meta.discourse.org/t/-/404832/2?silent=true)). - The **right sidebar tags block** was conflicting with other tag dropdowns; @martin acknowledged and linked a fix PR (#right-sidebar-blocks) — [read more](https://meta.discourse.org/t/-/404723/4?silent=true). - A self-host reported **Discourse Gamification’s `/leaderboard` returning 404** due to a `MissingAttributeError` caused by a narrow `SELECT` list omitting `users.admin`/`users.moderator`, with a suggested patch (#bug) — [read more](https://meta.discourse.org/t/-/404855/1?silent=true). - A particularly gnarly nested-replies-related bug persists where **posts from the previous topic remain rendered after in-app navigation** ; @markvanlan shipped “another go” at a fix PR and asked for retesting (#nested-replies) — [read more](https://meta.discourse.org/t/-/404488/9?silent=true) (latest fix attempt: [read more](https://meta.discourse.org/t/-/404488/10?silent=true)). - The upgrade issue where **`db:seed_fu` fails on `002_groups.rb`** due to “Name has already been taken” saw @martin pointing to a PR resolution — [read more](https://meta.discourse.org/t/-/404037/15?silent=true). ### #Support - A new self-host deployment thread covered **Discourse failing to bootstrap** (bundle install exit code 15); responders asked for earlier log lines, while another user suggested the likely culprit was _network/Gem access issues in China_ during a sensitive period — [read more](https://meta.discourse.org/t/-/404816/2?silent=true) (request for more logs: [read more](https://meta.discourse.org/t/-/404816/6?silent=true), network hypothesis: [read more](https://meta.discourse.org/t/-/404816/7?silent=true)). - A report found **`/u?exclude_groups=admins` behaves differently when logged out** , potentially exposing admin accounts despite group pages being inaccessible; discussion explored group visibility/privacy semantics and info-leak implications (#groups #user-directory) — [read more](https://meta.discourse.org/t/-/404885/1?silent=true) (follow-up confusion/analysis: [read more](https://meta.discourse.org/t/-/404885/5?silent=true)). - A restore/migration thread revisited why **images can lose correct S3 bucket URLs after restore** , including advice that restore tooling needs S3 config available during restore and a note about `discourse backup --sql_only` to avoid URL rewrite (#s3 #hosting) — [read more](https://meta.discourse.org/t/-/404659/4?silent=true) (ongoing details: [read more](https://meta.discourse.org/t/-/404659/5?silent=true)). - An AI Tools Test Runner edge case was confirmed: **HTTP only works to port 80; other ports default to HTTPS** , and the topic was marked solved (#rest-api #ai) — [read more](https://meta.discourse.org/t/-/404705/2?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @lindsey kicked off the day with a detailed preview of the **redesigned admin dashboard** and then explicitly asked the community which KPIs/datapoints they’d want to see modularized (#dashboard) — [read more](https://meta.discourse.org/t/-/404528/1?silent=true), [read more](https://meta.discourse.org/t/-/404528/4?silent=true), [read more](https://meta.discourse.org/t/-/404528/6?silent=true). - @martin announced **unified new** (making the combined New experience the default) and later helped keep the “Boosts” expectations grounded while still optimistic about its return — [read more](https://meta.discourse.org/t/-/404728/1?silent=true), [read more](https://meta.discourse.org/t/-/399835/90?silent=true). He also linked fixes for two separate issues: right-sidebar tags conflicts — [read more](https://meta.discourse.org/t/-/404723/4?silent=true) — and a `seed_fu`/groups validation failure — [read more](https://meta.discourse.org/t/-/404037/15?silent=true). - @nat responded to early dashboard feedback with a “_soon_” nod on KPI customization, and separately acknowledged a UX edge case around **language mismatch between UI language and translated content** (#content-localization) — [read more](https://meta.discourse.org/t/-/404528/3?silent=true), [read more](https://meta.discourse.org/t/-/404774/2?silent=true). - @HAWK started a thoughtful #Enterprise thread on **community ownership models** (where community teams “sit” org-wise), and teased upcoming **Workflows** as “superpowered automations” in an automation thread (#automation) — [read more](https://meta.discourse.org/t/-/404814/1?silent=true), [read more](https://meta.discourse.org/t/-/383691/23?silent=true). - @chapoi helped reduce confusion around New vs Unread in the unified-new thread and encouraged version-checking for admins who couldn’t see the toggle — [read more](https://meta.discourse.org/t/-/404728/3?silent=true), [read more](https://meta.discourse.org/t/-/404728/5?silent=true). They also shipped a small UX win for the **Discourse GIFs** component: the GIF button now appears in the regular mobile toolbar like desktop (#official #gifs) — [read more](https://meta.discourse.org/t/-/158738/294?silent=true). - @Falco provided the accepted solution for the AI Tools Test Runner behavior: **HTTP-to-non-80 ports defaulting to HTTPS** (#ai) — [read more](https://meta.discourse.org/t/-/404705/2?silent=true). - @markvanlan continued shepherding #nested-replies: offering a configuration-based approach to limit depth and shipping PRs for nested-reply-related glitches, including a fix for moderation visibility and another attempt at the “carry-over rendered posts” bug — [read more](https://meta.discourse.org/t/-/402812/53?silent=true), [read more](https://meta.discourse.org/t/-/402812/55?silent=true), [read more](https://meta.discourse.org/t/-/404488/10?silent=true). - @awesomerobot clarified terminology for **New vs Unread vs Unseen** (and why unified new aims to be more intuitive), and diagnosed/fixed the SVG badge-dimension rendering issue (#badges) — [read more](https://meta.discourse.org/t/-/404728/8?silent=true), [read more](https://meta.discourse.org/t/-/404832/2?silent=true). - @gerhard advised on an S3 restore situation, emphasizing that restores need S3 to be configured in the right place and suggesting `discourse backup --sql_only` to avoid upload URL rewriting (#s3 #hosting) — [read more](https://meta.discourse.org/t/-/404659/4?silent=true). - @david jumped into a Development thread with concrete reproduction commands to test **SKIP\_DB\_AND\_REDIS bootability** behavior across modes — [read more](https://meta.discourse.org/t/-/404152/7?silent=true). > **Bonus team-side “drive-by fix signal”:** A Foundation theme font-size regression was pointed to a core PR by @jordan.vidrine (#foundation-theme) — [read more](https://meta.discourse.org/t/-/403614/20?silent=true). * * * May tomorrow’s “New” be truly unified, your dashboards endlessly modular, and your nested replies blissfully non-haunted by carry-over posts. ---
### 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: [10 juni 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/889 "2026-06-10T21:02:44Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, meta saw **97 new posts** across **11 new topics** (plus ongoing replies across existing threads). **Top users (posts / likes in the last day):** - **@Moin** — **22 posts** , **17 likes** - **@davidb** — **5 posts** , **14 likes** - **@david** — **5 posts** , **6 likes** - **@nat** — **2 posts** , **5 likes** - **@Falco** — **2 posts** , **5 likes** - **@HAWK** — **1 post** , **4 likes** - **@noahl** — **1 post** , **4 likes** - **@chapoi** — **3 posts** , **4 likes** - **@sren-1** — **1 post** , **4 likes** - **@nathank** — **3 posts** , **3 likes** **Also active (fresh replies worth a look):** - Data/metrics thinking showed up again in the admin/dashboard conversation: [read more](https://meta.discourse.org/t/-/404528/9?silent=true) - A small but important [Data Explorer](https://meta.discourse.org/t/32566?silent=true) workflow regression was reported: [read more](https://meta.discourse.org/t/-/404957/1?silent=true) - A composer polish fix got merged (HR stealing focus from emoji picker): [read more](https://meta.discourse.org/t/-/403019/4?silent=true) - Nested replies rollout continued to shake out edge cases (topic “leaking” fix confirmed + styling follow-ups): [read more](https://meta.discourse.org/t/-/404488/11?silent=true) - Discourse hosting/pricing questions popped up again: [read more](https://meta.discourse.org/t/-/404699/10?silent=true) - AI / sentiment resources were re-linked for folks exploring customization limits: [read more](https://meta.discourse.org/t/-/404193/10?silent=true) * * * ## Interesting Topics ### #Announcements - **GIFs are moving into core (via Klipy), with migrations and gotchas for existing setups.** @davidb announced the core move and outlined migration paths for hosted vs. self-hosted installs, including a rake task for self-hosters: [read more](https://meta.discourse.org/t/-/404829/1?silent=true). Related context: the “Upcoming changes” system that can surface this in-admin: [read more](https://meta.discourse.org/t/-/392894/1?silent=true), and the long-running GIF component/thread where the UI placement came up: [read more](https://meta.discourse.org/t/-/158738/294?silent=true). - **Admin dashboard redesign continues to evolve, with community metrics talk surfacing alongside screenshots.** The redesigned dashboard preview thread picked up fresh discussion about what’s useful to measure and how teams pull stats via custom queries: [read more](https://meta.discourse.org/t/-/404528/9?silent=true). - **The unified topic list view is iterating on empty-state UX and “how much guidance is too much.”** @martin shared updated copy/layout that avoids overly verbose empty states for long-time accounts while still helping new users: [read more](https://meta.discourse.org/t/-/404728/10?silent=true). - **Nested replies remains a “center of gravity” feature—people are now joking that even announcements should be nested.** The nested replies announcement thread is still attracting meta-discussion and adoption momentum: [read more](https://meta.discourse.org/t/-/402812/56?silent=true). For an older “can Discourse do this?” reference that now has a clear answer: [read more](https://meta.discourse.org/t/-/194095/4?silent=true). - **Boosts brainstorming continued, with a “Medium claps” style finite-currency angle.** The Boosts experiment thread got a thoughtful comparison to Medium’s multi-clap mechanic and what it might imply for long-form/community incentives: [read more](https://meta.discourse.org/t/-/399835/91?silent=true). ### #Support - **Hiding admins from rankings/user directory: a practical CSS workaround emerged (and a deeper privacy model discussion).** The thread explored why `/u?exclude_groups=admins` behaves differently depending on group visibility, and ended with a “just hide the row” CSS solution for anonymous views and top-contributor blocks: [read more](https://meta.discourse.org/t/-/404885/33?silent=true). Related sidebar component context: [read more](https://meta.discourse.org/t/-/231067/1?silent=true). - **SQL-triggered badges: how to attach grants to a specific topic/post.** @chapoi suggested adding a `post_id` subquery (and the need to target posts) so awarded badges can point at a canonical topic: [read more](https://meta.discourse.org/t/-/404943/2?silent=true). - **Content Localization language switcher confusion: UI toggle visible, but locale not changing as expected.** @Moin reported that selecting a language didn’t actually switch the interface language; the discussion quickly pointed to a required cookie-based locale setting mentioned in the AI localization guide: [read more](https://meta.discourse.org/t/-/404965/1?silent=true), with the referenced manual here: [read more](https://meta.discourse.org/t/-/370969/1?silent=true). - **Event reminders: can they email instead of being “easy to miss” in-app notifications?** The request/experiment is underway, including whether commenting on an event might trigger emails for RSVP’d users: [read more](https://meta.discourse.org/t/-/404895/1?silent=true). - **Bilibili embeds: iframe whitelisting vs. simply posting a link (and when a plugin helps).** A support thread in Chinese walked through why an iframe approach didn’t render as expected, and pointed to the bilibili onebox/plugin route; the OP ultimately found that posting a link could “just work”: [read more](https://meta.discourse.org/t/-/404906/1?silent=true). Related plugin reference: [read more](https://meta.discourse.org/t/-/389149/1?silent=true). ### #bug - **Ad placements + nested replies: too tall/annoying layouts and occasional sizing glitches.** @Moin documented how ads feel especially intrusive in nested replies topics and also noted edge cases where ads don’t reserve enough space (quotes/polls): [read more](https://meta.discourse.org/t/-/404917/1?silent=true). - **PDF previews regression: clicking the PDF link downloads instead of opening in a new tab.** The report notes this is especially painful when users want a full-window PDF view, and flags inconsistent behavior between local uploads vs. S3; a fix was linked via PR: [read more](https://meta.discourse.org/t/-/404910/1?silent=true). Historical reference for intended behavior: [read more](https://meta.discourse.org/t/-/388190/12?silent=true). - **ActivityPub federation: `[event]` (and other markdown-like artifacts) leaking into fed posts.** A fresh reply reiterated that event syntax (and other formatting) showing up on Mastodon can be embarrassing, especially when edits also federate: [read more](https://meta.discourse.org/t/-/364735/4?silent=true). ### #ux - **Horizon + Events: “New Topic” label regressed in the sidebar even though it creates an event.** The issue is cosmetic but confusing; @chapoi linked a fix PR after the report, and the thread references ongoing Events improvements: [read more](https://meta.discourse.org/t/-/404905/1?silent=true). Related plugin context: [read more](https://meta.discourse.org/t/-/97376/1?silent=true). - **Upcoming Changes notifications: should Discourse notify you about changes that are hidden because the theme/plugin is disabled?** @Moin reported a notification that led to an empty/hidden state, suggesting the notification itself might need suppression when the change is not actionable: [read more](https://meta.discourse.org/t/-/405009/1?silent=true). Background on the Upcoming Changes system: [read more](https://meta.discourse.org/t/-/392894/1?silent=true). ### #development - **Extending Discourse Chat “message blocks”: request for a plugin API/extension point.** A developer asked whether chat’s structured `blocks` JSON could become extensible (e.g. `registerChatBlockType`) to support richer cards for GitHub/GitLab-style activity feeds without patching core internals: [read more](https://meta.discourse.org/t/-/405006/1?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@davidb** drove the core GIFs announcement and migration details, including guiding self-hosters who couldn’t see the new setting yet and discussing migration edge cases (e.g., domain allow/deny lists and translation overrides): [read more](https://meta.discourse.org/t/-/404829/1?silent=true), [read more](https://meta.discourse.org/t/-/404829/9?silent=true), [read more](https://meta.discourse.org/t/-/404829/11?silent=true). - **@nat** helped clarify rollout timing for the GIFs-to-core build and also showcased the new GIF flow in the admin dashboard preview conversation: [read more](https://meta.discourse.org/t/-/404829/3?silent=true), [read more](https://meta.discourse.org/t/-/404528/8?silent=true). - **@david** engaged deeply on group visibility/privacy implications in “exclude admins from directory” behavior, including why group membership inference matters and what configurations change behavior: [read more](https://meta.discourse.org/t/-/404885/9?silent=true), [read more](https://meta.discourse.org/t/-/404885/18?silent=true), [read more](https://meta.discourse.org/t/-/404885/21?silent=true). - **@Falco** acknowledged an unfinished fix around ad layout in nested replies topics and pointed to documentation when troubleshooting the content localization language switcher: [read more](https://meta.discourse.org/t/-/404917/2?silent=true), [read more](https://meta.discourse.org/t/-/404965/2?silent=true). - **@chapoi** responded across multiple threads: clarifying the GIF button’s new location, proposing SQL to associate badge grants with a topic’s first post, and acknowledging/fixing the Horizon “New Event” sidebar label regression: [read more](https://meta.discourse.org/t/-/404829/14?silent=true), [read more](https://meta.discourse.org/t/-/404943/2?silent=true), [read more](https://meta.discourse.org/t/-/404905/2?silent=true). - **@HAWK** pushed the enterprise/community conversation forward by probing how community teams handle cross-department mandates and member-first boundaries inside marketing-led org structures: [read more](https://meta.discourse.org/t/-/404814/3?silent=true). - **@zogstrip** chimed in with a concrete fix path for the PDF-preview regression (noting S3 vs. local inconsistencies), and confirmed that Discourse does indeed offer a free plan (pointing to pricing): [read more](https://meta.discourse.org/t/-/404910/3?silent=true), [read more](https://meta.discourse.org/t/-/404699/10?silent=true). - **@awesomerobot** corrected a bot hallucination about “censored usernames,” clarifying that watched/blocked/censored words don’t apply to usernames and that `reserved usernames` is the current tool (with admin exemptions): [read more](https://meta.discourse.org/t/-/231232/8?silent=true). - **@renato** confirmed a UX polish fix was merged for the composer (horizontal rule stealing focus from the emoji picker), thanking the reporter/contributor: [read more](https://meta.discourse.org/t/-/403019/4?silent=true). - **@martin** shared updated thinking and visuals for the unified topic list view’s empty-state guidance, aiming for a better balance between help and noise: [read more](https://meta.discourse.org/t/-/404728/10?silent=true). * * * _Sign-off:_ If yesterday proved anything, it’s that Discourse can now power serious admin dashboards **and** the occasional GIF-only philosophical debate—just try not to let the ads nest themselves too. ---
### 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: [11 juni 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/890 "2026-06-11T21:02:17Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 70** - **New topics (last 24h): 13** **Top users (posts / likes in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @Moin | 7 | 15 | | @lindsey | 2 | 6 | | @pmusaraj | 4 | 4 | | @JDParker | 3 | 4 | | @awesomerobot | 4 | 4 | | @Sara_Carmona_y_Lladó | 1 | 3 | | @RGJ | 1 | 3 | | @Honeyxilia | 1 | 2 | | @system | 1 | 2 | | @ted | 1 | 2 | **Most active [@team](https://meta.discourse.org/groups/team?silent=true) members (posts / likes)** | User | Posts | Likes | | --- | --- | --- | | @pmusaraj | 4 | 4 | | @awesomerobot | 4 | 4 | | @lindsey | 2 | 6 | | @martin | 2 | 1 | | @nat | 2 | 1 | | @chapoi | 4 | 0 | | @Falco | 1 | 2 | | @renato | 1 | 1 | | @zogstrip | 1 | 1 | | @saquetim | 1 | 0 | * * * ## Interesting Topics ### #Support - @Sara_Carmona_y_Lladó dug into AI Translation behavior changes—specifically why **“Translatable categories”** disappeared and how **cost/scope** is now determined—and @Moin confirmed there _was_ a migration to **excluded categories** , including how the values were converted and where to audit changes (staff action logs), plus a handy [Data Explorer](https://meta.discourse.org/t/32566?silent=true) query to inspect translation volume ([read more](https://meta.discourse.org/t/-/405072/1?silent=true), [migration details](https://meta.discourse.org/t/-/405072/2?silent=true), [SQL idea](https://meta.discourse.org/t/-/405072/3?silent=true), [referenced migration note](https://meta.discourse.org/t/-/392993/7?silent=true), #ai #dynaloc). - @JDParker couldn’t add a secondary email because the UI button was missing; the culprit ended up being the `email_editable` site setting (and related settings that can hide email edit controls) ([question](https://meta.discourse.org/t/-/405100/1?silent=true), [diagnosis](https://meta.discourse.org/t/-/405100/3?silent=true), [solution](https://meta.discourse.org/t/-/405100/5?silent=true)). - A mobile layout oddity with #custom-header-links (a “Blog” link dropping to the bottom-left) was traced to wrapping/padding behavior, and a fix was merged to prevent the bad wrap on mobile ([report](https://meta.discourse.org/t/-/405086/1?silent=true), [fix](https://meta.discourse.org/t/-/405086/2?silent=true)). - [Data Explorer](https://meta.discourse.org/t/32566?silent=true) troubleshooting continued in German: empty query results looked like a **UI/version mismatch** , with team nudging toward updating after recent [Data Explorer](https://meta.discourse.org/t/32566?silent=true) changes ([analysis](https://meta.discourse.org/t/-/404957/2?silent=true), [team follow-up](https://meta.discourse.org/t/-/404957/3?silent=true), #data-explorer #bug). ### #Announcements - Livestream has been officially folded into the Events plugin, consolidating virtual/in-person events and livestream scheduling under one roof, with notes about migration behavior and hosted plan availability ([announcement](https://meta.discourse.org/t/-/404866/1?silent=true), #calendar-and-events #discourse-livestream). ### #contribute:feature - The long-running “Matrix protocol for chat” thread got a fresh jolt: @pmusaraj shared a **proof-of-concept Discourse ↔ Matrix chat bridge** , including a test instance and follow-up debugging around federation and room visibility ([PoC drop](https://meta.discourse.org/t/-/210780/74?silent=true), [follow-up fix](https://meta.discourse.org/t/-/210780/79?silent=true), [community context](https://meta.discourse.org/t/-/210780/76?silent=true), #chat). - A new embedding feature request asked for embeds to optionally include the **first post** (or even a “create topic” flow) so external sites can show context + multiple related threads; the proposal builds on existing embed capabilities and prior discussions ([feature request](https://meta.discourse.org/t/-/405070/1?silent=true), [topic list embeds](https://meta.discourse.org/t/-/293709/1?silent=true), [classic comments embed](https://meta.discourse.org/t/-/31963/1?silent=true), [prior first-post approach](https://meta.discourse.org/t/-/172969/5?silent=true), #embedding). ### #bug - Recurring events localization: an `Every [missing %{weekday} value]` rendering bug (notably on en-UK) turned out to already be fixed upstream, but required pulling newer commits; a rebuild/update resolved it for the reporter ([bug report](https://meta.discourse.org/t/-/405016/1?silent=true), [fix status](https://meta.discourse.org/t/-/405016/3?silent=true), [confirmed resolved](https://meta.discourse.org/t/-/405016/6?silent=true), #calendar-and-events). - Nested replies met advertising layout: topic list ads were consuming too much vertical space in topics using nested replies, and fixes landed in the _component_ (not the main Ads plugin), plus a candid “wrong plugin” detour that will feel familiar to anyone who’s debugged ad stacks ([fixes + context](https://meta.discourse.org/t/-/404917/3?silent=true), [Ads plugin reference](https://meta.discourse.org/t/-/33734/1?silent=true), #nested-replies). - A chat + CDN issue remained in the review queue: chat thumbnails were reported to bypass `s3_cdn_url` and instead use raw S3 bucket URLs; the PR was described as waiting on human review after automated help got tests green ([status update](https://meta.discourse.org/t/-/404174/4?silent=true), [question](https://meta.discourse.org/t/-/404174/3?silent=true), #cdn #s3 #chat). - Composer behavior change: auto-conversion of certain characters was removed _while typing_ in the rich editor (though conversions may still happen during cooking under some conditions), which ties into ongoing reports of “apostrophe becomes quote-like characters” on some installs/locales ([team explanation](https://meta.discourse.org/t/-/403905/13?silent=true), [related report](https://meta.discourse.org/t/-/405083/1?silent=true), [older similar issue](https://meta.discourse.org/t/-/123227/4?silent=true), #composer). ### #ux - Admin navigation feedback: @RGJ argued that **Tags** and **Tag Groups** are still too “hidden” in the new admin IA, suggesting they deserve first-class placement under **Content** rather than being discovered indirectly via settings links ([proposal](https://meta.discourse.org/t/-/405039/1?silent=true), #tags #tag-groups #admin-sidebar). - A micro-interaction deep dive: the “Reply” post action’s background transition effect was questioned as inconsistent with other controls; @awesomerobot traced it to older UI behavior and pushed a PR to remove an unnecessary transition while discussing whether the subtle hover differentiation still earns its keep ([PR context](https://meta.discourse.org/t/-/404362/9?silent=true), [behavior rationale](https://meta.discourse.org/t/-/404362/14?silent=true)). ### #customization:theme component - DiscoTOC + translations: @Honeyxilia reported that enabling DiscoTOC’s side panel can make the **topic translation swap button** effectively disappear, and asked for a way to keep the default Discourse control accessible even with the TOC panel present ([report](https://meta.discourse.org/t/-/111143/487?silent=true), #official #disco-toc). ### #Site feedback - Tag translation quality got an on-meta improvement: @nat confirmed that several problematic AI-generated tag translations should now be handled properly on Meta, while noting that passing richer context to the tag translator is still not high priority ([update](https://meta.discourse.org/t/-/399570/18?silent=true), #tags #ai #dynaloc). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@lindsey** announced that livestream is now part of the Events plugin and outlined enablement + migration details ([read more](https://meta.discourse.org/t/-/404866/1?silent=true)); she also acknowledged a report about recurring RSVP “going” state not resetting and flagged it for investigation ([read more](https://meta.discourse.org/t/-/335780/19?silent=true)). - **@pmusaraj** revived the Matrix chat discussion with a Discourse ↔ Matrix bridge proof-of-concept and iterated live based on early tester feedback (room visibility/federation) ([read more](https://meta.discourse.org/t/-/210780/74?silent=true), [follow-up](https://meta.discourse.org/t/-/210780/79?silent=true), [implementation notes](https://meta.discourse.org/t/-/210780/78?silent=true)). - **@awesomerobot** confirmed the recurring events localization bug was already fixed and advised updating to pick it up ([read more](https://meta.discourse.org/t/-/405016/3?silent=true)); merged a mobile layout fix for #custom-header-links ([read more](https://meta.discourse.org/t/-/405086/2?silent=true)); and dug into the “Reply” button hover transition behavior, including rationale and cleanup ([read more](https://meta.discourse.org/t/-/404362/14?silent=true), [PR context](https://meta.discourse.org/t/-/404362/9?silent=true)). - **@Falco** posted the concrete fixes for excessive ad spacing with nested replies—after discovering it lived in a separate topic list ads component rather than the main Ads plugin ([read more](https://meta.discourse.org/t/-/404917/3?silent=true)). - **@renato** clarified that the rich editor no longer auto-converts characters while typing (though cooking-time conversion may still happen), pointing to the relevant change ([read more](https://meta.discourse.org/t/-/403905/13?silent=true)). - **@zogstrip** quickly sanity-checked whether the recurring events localization issue was running on a version that included the very recent fix ([read more](https://meta.discourse.org/t/-/405016/2?silent=true)). - **@martin** pointed folks tracking Foundation rollout to the canonical modernization thread ([read more](https://meta.discourse.org/t/-/404656/4?silent=true)) and confirmed a UX bug where some upcoming-change notifications are hidden, promising a fix ([read more](https://meta.discourse.org/t/-/405009/3?silent=true)). - **@nat** confirmed fixes/cleanup for AI tag translations on Meta ([read more](https://meta.discourse.org/t/-/399570/18?silent=true)) and acknowledged a bug report about translated-language post links for further investigation ([read more](https://meta.discourse.org/t/-/403555/4?silent=true)). - **@chapoi** followed up on recent [Data Explorer](https://meta.discourse.org/t/32566?silent=true) changes and suggested updating to rule out a newly-fixed UI issue ([read more](https://meta.discourse.org/t/-/404957/3?silent=true)); helped debug an external email recipient rejection by focusing on group-alias recipient limits and relevant site settings ([read more](https://meta.discourse.org/t/-/405050/2?silent=true), [settings check](https://meta.discourse.org/t/-/405050/4?silent=true)); and clarified limitations in the GitHub integration architecture (commit/PR oriented, not issue comments), pointing toward the right feature request path ([read more](https://meta.discourse.org/t/-/401673/4?silent=true), [related feature request](https://meta.discourse.org/t/-/203780/1?silent=true)). - **@saquetim** explained that Doc Categories doesn’t support a card view yet (theme customization likely required) and pointed to the plugin’s compatibility pinning approach for ESR/self-hosters ([read more](https://meta.discourse.org/t/-/322376/163?silent=true)). * * * Yesterday’s vibe: **merge a plugin, bridge a chat network, and then rebuild anyway because “latest” is sometimes just a state of mind.** ---
### 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: [12 juni 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/891 "2026-06-12T21:02:17Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **New posts (last 24h): 57** - **New topics (last 24h): 10** **Top users (posts / likes in the last 24h):** - @awesomerobot — **7** posts / **6** likes - @nathank — **4** posts / **5** likes - @Moin — **3** posts / **8** likes - @chapoi — **2** posts / **6** likes - @MeganBowers — **2** posts / **5** likes - @lindsey — **2** posts / **4** likes - @pmusaraj — **2** posts / **4** likes - @zogstrip — **1** post / **5** likes - @asa — **1** post / **4** likes - @Falco — **1** post / **4** likes > Activity spanned UX tweaks (like safer category admin actions) and event/chat refinements, across threads such as the category editor UX discussion [read more](https://meta.discourse.org/t/-/403037/2?silent=true), the mobile drawer UX improvement [read more](https://meta.discourse.org/t/-/404606/2?silent=true), and recurring event RSVP fixes [read more](https://meta.discourse.org/t/-/335780/23?silent=true). Additional threads that also saw fresh replies in this window include: event reminder expectations [read more](https://meta.discourse.org/t/-/404895/4?silent=true), translation guidance for new RSVP strings [read more](https://meta.discourse.org/t/-/402827/8?silent=true), and a self-hosting bulk import win [read more](https://meta.discourse.org/t/-/118349/40?silent=true). * * * ## Interesting Topics ### #ux - @chapoi flagged that the **“Delete category”** button feels _too prominent_ vs Save in the category editor, proposing a clearer “Danger zone” pattern [read more](https://meta.discourse.org/t/-/403037/2?silent=true); @lindsey agreed with the direction [read more](https://meta.discourse.org/t/-/403037/3?silent=true). - Mobile UX got a boost: @renato shared that a **global drag-to-close refinement** for slide-up drawers has been merged, improving things like the reactions list dismissal flow [read more](https://meta.discourse.org/t/-/404606/2?silent=true). ### #Support - @Andry_Osminin reported that with **#nested-replies** enabled, the _root post becomes too narrow on mobile_ due to avatar/indent layout [read more](https://meta.discourse.org/t/-/405142/1?silent=true); @Falco suggested moving author info above the post (like flat topics) [read more](https://meta.discourse.org/t/-/405142/2?silent=true). - A missing icon mystery: @pHneutre couldn’t get the Font Awesome **`ranking-star`** to display via a header icons component [read more](https://meta.discourse.org/t/-/405144/1?silent=true); @Moin solved it by pointing out the **`fab` prefix mismatch** (it’s not a brand icon) and noted Discourse now ships a newer FA version than expected [read more](https://meta.discourse.org/t/-/405144/2?silent=true). - Email digest customization: @newbit1337 asked where to change the **“click here”** string in digest footers [read more](https://meta.discourse.org/t/-/405183/1?silent=true); @awesomerobot identified the relevant locale key (`user_notifications.digest.click_here`) and where it gets composed [read more](https://meta.discourse.org/t/-/405183/2?silent=true). - CDN migration edge case: @Canapin found that after removing a CDN, **poll option image URLs remained broken** even after rebakes and remaps, likely due to polls storing rendered HTML separately from post raw [read more](https://meta.discourse.org/t/-/405198/1?silent=true). - Restore + S3 confusion: in a restore scenario, @Maxine reported **S3-backed upload URLs appearing rewritten to local `/uploads/…`** , breaking images [read more](https://meta.discourse.org/t/-/404659/10?silent=true); @gerhard clarified how `.sql.gz` restores skip upload URL rewriting and asked for a clean repro with restore output details [read more](https://meta.discourse.org/t/-/404659/11?silent=true). - Invite throttles: @Prempavee asked why users hit a **10-invite limit** despite higher site settings [read more](https://meta.discourse.org/t/-/405150/1?silent=true); @chapoi pointed to the difference between _individual invites_ vs _re-usable invite links_ and which settings to adjust [read more](https://meta.discourse.org/t/-/405150/2?silent=true). - Visual “new activity” indicators: @gilles asked why there isn’t always a **badge/pastille on categories** to show new messages [read more](https://meta.discourse.org/t/-/405194/1?silent=true); @awesomerobot noted it exists in some UI surfaces (like the sidebar) but not others (like certain category page layouts) [read more](https://meta.discourse.org/t/-/405194/2?silent=true). ### #contribute:feature - Calendar & Events enhancement request: @MeganBowers proposed **email reminders for events** (not just in-app notifications), with customizable timing/content for RSVPed/Interested users [read more](https://meta.discourse.org/t/-/405192/1?silent=true); @awesomerobot dug into notification-vs-message mechanics and highlighted a broader “events email preference gap” [read more](https://meta.discourse.org/t/-/405192/3?silent=true). - @gilles asked for an **event image URL field** (linking an image instead of uploading), to streamline event creation workflows [read more](https://meta.discourse.org/t/-/405167/1?silent=true). - Matrix + chat access debugging: in the ongoing Matrix protocol discussion, @rokejulianlockhart couldn’t see the “General” channel [read more](https://meta.discourse.org/t/-/210780/80?silent=true); @Moin suggested checking `chat_allowed_groups` defaults (especially post–bootstrap mode changes) [read more](https://meta.discourse.org/t/-/210780/83?silent=true), and @pmusaraj confirmed enabling TL0 resolved it [read more](https://meta.discourse.org/t/-/210780/84?silent=true). ### #bug - Recurring events RSVP fix: @zogstrip confirmed a bug where **“My events” showed RSVPs on every upcoming occurrence** and linked the fix PR [read more](https://meta.discourse.org/t/-/335780/23?silent=true). ### #sso - Account continuity planning: @Ethsim2 laid out a careful migration plan away from institutional email domains / external SSO toward **local accounts with personal emails** , aiming to reduce impersonation and unsafe merges [read more](https://meta.discourse.org/t/-/405143/1?silent=true). ### #community-building Building - Search interventions: @AkarinLiu asked (in Chinese) whether Discourse can show a **gentle “tip” prompt** when users search certain sensitive keywords (akin to some major platforms’ self-harm deterrence messaging) [read more](https://meta.discourse.org/t/-/405163/1?silent=true). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @chapoi weighed in on safer category editing UX, questioning whether **Delete should appear on every tab** and suggesting a dedicated “Danger zone” pattern [read more](https://meta.discourse.org/t/-/403037/2?silent=true); they also helped troubleshoot **invite limit settings** and clarified the two invite pathways admins often mix up [read more](https://meta.discourse.org/t/-/405150/2?silent=true). - @lindsey supported the “Danger zone” approach for category deletion, agreeing that the current placement feels odd and endorsing the redesign direction [read more](https://meta.discourse.org/t/-/403037/3?silent=true); later, they discussed whether burying delete behind “advanced settings” is acceptable given the risk profile [read more](https://meta.discourse.org/t/-/403037/6?silent=true). - @awesomerobot stayed busy across UX and email configuration: they debated where category deletion should live in the UI [read more](https://meta.discourse.org/t/-/403037/5?silent=true), explained the digest string composition behind **“click here”** localization [read more](https://meta.discourse.org/t/-/405183/2?silent=true), and explored options for **event reminders and email preference handling** [read more](https://meta.discourse.org/t/-/405192/3?silent=true). They also pointed out where category “new content” indicators _do_ and _don’t_ appear in the UI today [read more](https://meta.discourse.org/t/-/405194/2?silent=true), and offered debugging steps for missing notifications on an out-of-date site [read more](https://meta.discourse.org/t/-/405023/3?silent=true). - @Falco confirmed the mobile layout issue with **threaded/nested replies** and suggested aligning the root post author layout with the flat-topic approach (author info above, not beside) [read more](https://meta.discourse.org/t/-/405142/2?silent=true). - @pmusaraj debugged Matrix chat onboarding, confirmed visibility issues, and flipped access to include TL0 after a `chat_allowed_groups` hint—unblocking new users from seeing chat channels [read more](https://meta.discourse.org/t/-/210780/84?silent=true). - @zogstrip acknowledged and triaged the recurring event RSVP bug, linking the GitHub fix for **My events showing RSVPs on every occurrence** [read more](https://meta.discourse.org/t/-/335780/23?silent=true). - @renato shipped a small-but-mighty mobile UX improvement: drag-to-close behavior in slide-up drawers (including reactions lists) was refined via a global change, and the topic was scheduled for closure pending any regressions [read more](https://meta.discourse.org/t/-/404606/2?silent=true). - @gerhard continued deep-dive troubleshooting on **S3 upload URLs after restore** , clarifying when URL rewriting does/doesn’t happen and requesting a clean repro with restore logs to pinpoint why URLs appeared unexpectedly remapped [read more](https://meta.discourse.org/t/-/404659/11?silent=true). - @mcwumbly followed up on the collaborative content gardening experiment, agreeing that if manual edits aren’t practical, raising the issue is the right call [read more](https://meta.discourse.org/t/-/397606/103?silent=true). If yesterday taught us anything, it’s this: keep dangerous buttons in a _Danger zone_, make drawers draggable, and always check `chat_allowed_groups` before assuming the Matrix is glitching. ---
### 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 juni 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/892 "2026-06-13T21:01:30Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats **Last 24 hours (2026-06-12 → 2026-06-13)** - **New posts:** 40 - **New topics:** 5 **Top posters & likes (last 24h)** | User | Posts | Likes | | --- | --- | --- | | @Heliosurge | 6 | 1 | | @Moin | 4 | 2 | | @awesomerobot | 4 | 2 | | @Canapin | 2 | 2 | | @Aurora | 2 | 1 | | @jordan.vidrine | 1 | 4 | | @asa | 1 | 3 | | @AkarinLiu | 1 | 2 | | @merefield | 1 | 1 | | @happyhappy | 1 | 1 | * * * ## Interesting Topics ### #Announcements - **Foundation theme modernization tweaks continued** : @Moin flagged subtle UI regressions (like the category box accent border and truncated group names), and @jordan.vidrine confirmed the thinner border is _intentional_ (a softer evolution rather than full removal) and noted adjustments to show more characters in group dropdowns, with changes tracked in a PR. [read more](https://meta.discourse.org/t/-/395331/106?silent=true) (also see context: [original thread](https://meta.discourse.org/t/-/395331/1?silent=true)) - **Recurring event RSVPs + translation/process notes** : discussion continued around the “Improved Events” RSVP flexibility rollout, with @Moin clarifying feedback expectations for translation suggestions and how notes were being interpreted. [read more](https://meta.discourse.org/t/-/402827/10?silent=true) ### #Support - **Avatar frames: no off-the-shelf component (yet), but a plugin prototype emerges**: @hieppu asked about an “avatar frame” component/plugin, @Heliosurge suggested this likely needs custom work (and pointed to #Marketplace as an option), and @asa shared a fresh plugin experiment using GIF-based frames as a starting point. [read more](https://meta.discourse.org/t/-/318545/10?silent=true) (thread start: [here](https://meta.discourse.org/t/-/318545/1?silent=true), plus @Heliosurge’s guidance: [here](https://meta.discourse.org/t/-/318545/9?silent=true)) - **[try.discourse.org](http://try.discourse.org) sending “Account no longer on hold” PMs**: @Canapin reported repeated automated PMs after resets and noted the demo instance appears empty; @awesomerobot confirmed they’re seeing it too and suspects the daily restore process may be off. [read more](https://meta.discourse.org/t/-/405253/4?silent=true) (report: [here](https://meta.discourse.org/t/-/405253/1?silent=true), resets note: [here](https://meta.discourse.org/t/-/405253/2?silent=true), follow-up: [here](https://meta.discourse.org/t/-/405253/3?silent=true), additional confirmation: [here](https://meta.discourse.org/t/-/405253/7?silent=true)) - **Unified “New” view confusion: “New Topics” vs “New & unread”** : @Heliosurge noticed “New Topics” appears to show a merged view; @Moin pointed to the unified-new view announcement and suggested URL parameters, while the thread honed in on UX labeling/clarity (especially when arriving from the bottom-of-topic navigation). [read more](https://meta.discourse.org/t/-/405247/1?silent=true) (solution pointer: [here](https://meta.discourse.org/t/-/405247/2?silent=true), UX suggestion: [here](https://meta.discourse.org/t/-/405247/7?silent=true), plus related announcement: [read more](https://meta.discourse.org/t/-/404728/1?silent=true)) - **Admin access on hosted free plan: wrong account/login mismatch** : @whitelabel couldn’t access admin/mod tools on a free hosted site; @awesomerobot helped diagnose that they weren’t signed in with the original admin identity and recommended logging out/in via Discourse ID, which resolved it. [read more](https://meta.discourse.org/t/-/405211/4?silent=true) (question: [here](https://meta.discourse.org/t/-/405211/1?silent=true), triage: [here](https://meta.discourse.org/t/-/405211/2?silent=true), resolution confirmation: [here](https://meta.discourse.org/t/-/405211/5?silent=true)) - **Event image URLs vs uploads (“hotlinking”)**: in a discussion about using external image URLs for events (instead of uploading), @merefield cautioned that hotlinking is generally bad practice, while the thread explored whether Discourse could _fetch and store_ the remote image as a safer middle ground. [read more](https://meta.discourse.org/t/-/405167/5?silent=true) (context & examples: [here](https://meta.discourse.org/t/-/405167/2?silent=true), clarification: [here](https://meta.discourse.org/t/-/405167/4?silent=true)) - **S3 restore quirks: missing avatars/uploads after restoring from sql.gz** : @Maxine reported that restoring from an S3-stored `sql.gz` mostly worked but left some avatars/posts broken—likely tied to which uploads actually made it to S3 at creation time—then asked whether a “normal” production setup fully using S3 would avoid this outcome. [read more](https://meta.discourse.org/t/-/404659/12?silent=true) ### #bug - **Custom flag reasons UI: disabling one reason hides others** (#bug): @AkarinLiu reported that disabling any custom flag description (except the “send message to @%{username}” one) causes other custom reasons to disappear, with before/after screenshots showing the issue clearly. [read more](https://meta.discourse.org/t/-/405254/1?silent=true) ### #contribute:feature - **Desktop chat notification sounds framed as accessibility** : @tamaracha explained that subtle _foreground_ chat notifications would help blind users notice new messages without repeatedly scanning history via screen reader—positioning this as #a11y rather than “addictive sounds.” [read more](https://meta.discourse.org/t/-/23465/17?silent=true) (continued discussion: [here](https://meta.discourse.org/t/-/23465/18?silent=true)) - **Calendar subscription URLs: request for an “OFF” switch** (#calendar-and-events): @happyhappy asked whether sites can disable sharing events externally via calendar subscription URLs—useful for communities that don’t want event data flowing into outside calendar apps. [read more](https://meta.discourse.org/t/-/398902/26?silent=true) - **Event email reminders: keep it simple (topic replies can carry custom messaging)** (#email, #calendar-and-events): discussion continued on reminder emails, with @nathank arguing per-event custom content might be unnecessary because a topic reply plus strategic @mentions already provides flexible messaging. [read more](https://meta.discourse.org/t/-/405192/6?silent=true) (additional support for the idea: [here](https://meta.discourse.org/t/-/405192/7?silent=true)) ### #customization:plugin - **Calendar RSVP Posts plugin: community code tweak to reduce confusing duplicate avatars** (#calendar-and-events): @gilles described an issue where RSVP participation could show duplicate avatars until refresh, and shared a code modification they made locally to reduce confusion—offering it upstream in case it’s helpful. [read more](https://meta.discourse.org/t/-/390058/9?silent=true) ### #Support (more) - **AI plugin admin bot account (“deepseek-chat”) removal** (#ai): @sniper756 asked how to delete an auto-created admin account; @NateDhaliwal suggested it’s the bot account for the #ai plugin and linked guidance for deleting staff users via Rails console if it’s truly not needed. [read more](https://meta.discourse.org/t/-/405250/2?silent=true) (question: [here](https://meta.discourse.org/t/-/405250/1?silent=true), referenced console guide: [read more](https://meta.discourse.org/t/-/141540/11?silent=true)) - **Category “badges/pills” visibility and home page UX** (#categories): @gilles explored improving accessibility/clarity when the homepage lands on categories, sharing screenshots and asking how to surface the category indicator more clearly. [read more](https://meta.discourse.org/t/-/405194/3?silent=true) - **Update/notification pipeline troubleshooting** (#notifications): in a thread about notifications not happening, @awesomerobot requested more diagnostics, and @NateDhaliwal suggested rebuilding from the command line (`./launcher rebuild app`) as a more reliable update path than the Admin UI in some cases. [read more](https://meta.discourse.org/t/-/405023/5?silent=true) (CLI suggestion: [here](https://meta.discourse.org/t/-/405023/6?silent=true)) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@jordan.vidrine** followed up on Foundation theme changes—confirming the thinner category accent border was a deliberate design compromise (not a regression), and adjusting group dropdown truncation to show more characters. [read more](https://meta.discourse.org/t/-/395331/106?silent=true) (thread context: [read more](https://meta.discourse.org/t/-/395331/1?silent=true)) - **@awesomerobot** investigated demo-instance oddities on [try.discourse.org](http://try.discourse.org), acknowledging suspicious “account no longer on hold” PMs and pointing to the restore process as the likely culprit. [read more](https://meta.discourse.org/t/-/405253/4?silent=true) (report context: [read more](https://meta.discourse.org/t/-/405253/1?silent=true)) - **@awesomerobot** helped a hosted customer regain admin access by confirming they likely weren’t logged into the original admin identity and recommending a Discourse ID logout/login flow that fixed it. [read more](https://meta.discourse.org/t/-/405211/2?silent=true) (solution: [read more](https://meta.discourse.org/t/-/405211/4?silent=true), confirmation: [read more](https://meta.discourse.org/t/-/405211/5?silent=true)) - **@awesomerobot** continued triage on missing notifications by asking for concrete error details to narrow down whether the issue is configuration, delivery, or update-related. [read more](https://meta.discourse.org/t/-/405023/5?silent=true) * * * Yesterday’s vibe: borders got _less thicc_ while [try.discourse.org](http://try.discourse.org) got _more mysterious_—classic Meta 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: [14 juni 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/893 "2026-06-14T21:01:51Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats - **Time window:** 2026-06-13 → 2026-06-14 (last 24 hours) - **New topics:** **2** (including a new accessibility question and a migration/SEO report: [read more](https://meta.discourse.org/t/-/405274/1?silent=true), [read more](https://meta.discourse.org/t/-/405270/1?silent=true)) - **New posts:** **21** **Top users (posts + likes in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @RGJ | 3 | 2 | | @asa | 2 | 1 | | @Richie | 2 | 1 | | @david | 1 | 5 | | @nathank | 1 | 2 | | @MY_YISHI | 1 | 2 | | @NateDhaliwal | 1 | 1 | | @Larry_Baker | 1 | 0 | | @HAWK | 1 | 0 | | @merefield | 1 | 0 | **Most active [@team](https://meta.discourse.org/groups/team?silent=true) members:** @david and @HAWK (see details: [read more](https://meta.discourse.org/t/-/405253/10?silent=true), [read more](https://meta.discourse.org/t/-/404814/6?silent=true)) * * * ## Interesting Topics **#Support** - @david confirmed a fix (and deployment) for [try.discourse.org](http://try.discourse.org) accounts unexpectedly switching off “on hold,” sharing the PR and noting it’s now live ([read more](https://meta.discourse.org/t/-/405253/10?silent=true), background in the same thread: [read more](https://meta.discourse.org/t/-/405253/1?silent=true)). - A community thread on avatar “frames” evolved into a shareable plugin direction: @NateDhaliwal reacted to the UI/monetization vibe ([read more](https://meta.discourse.org/t/-/318545/11?silent=true)), @RGJ suggested a source of decorative frames ([read more](https://meta.discourse.org/t/-/318545/12?silent=true)), and @asa later shared a GitHub repo for **discourse-avatar-frames** ([read more](https://meta.discourse.org/t/-/318545/15?silent=true); topic context: [read more](https://meta.discourse.org/t/-/318545/1?silent=true)). - In an edge-case ops workflow discussion, @Richie asked about extending or disabling the impersonation timeout (tagged #impersonate and #site-settings) ([read more](https://meta.discourse.org/t/-/403961/9?silent=true)); @RGJ pointed out the setting accepts long values (even formula-style) ([read more](https://meta.discourse.org/t/-/403961/10?silent=true)), and @Richie confirmed success after adjusting it ([read more](https://meta.discourse.org/t/-/403961/11?silent=true); topic: [read more](https://meta.discourse.org/t/-/403961/1?silent=true)). - A new accessibility (#accessibility, #ux) topic asked for best practices using the **JAWS** screen reader with Discourse, inviting tips from experienced admins and users ([read more](https://meta.discourse.org/t/-/405274/1?silent=true)). - In a related ongoing #accessibility / #ux support thread, @happyhappy followed up on navigating Discourse with JAWS and keyboard shortcuts—specifically re-checking prior suggestions ([read more](https://meta.discourse.org/t/-/404095/5?silent=true); earlier context: [read more](https://meta.discourse.org/t/-/404095/1?silent=true)). **#contribute:feature** - A long-running request to let **Category Moderators** change post ownership gained fresh support: @nathank said it seems reasonable—especially behind a site setting—while noting it may need more visibility to gain traction ([read more](https://meta.discourse.org/t/-/246052/10?silent=true); feature request context: [read more](https://meta.discourse.org/t/-/246052/1?silent=true)). **#customization:theme component** - A legacy theme-component thread received fresh engagement (in Chinese), with @MY_YISHI praising the post and the author—suggesting the component/topic still has reach years later ([read more](https://meta.discourse.org/t/-/149353/10?silent=true); thread context: [read more](https://meta.discourse.org/t/-/149353/1?silent=true)). **#bug** - A bug report flagged a stray HTML `` in topic cards (tag: #topic-cards). @RGJ noted they already have a PR ready and have fixed linting—waiting for review ([read more](https://meta.discourse.org/t/-/404301/2?silent=true); report context: [read more](https://meta.discourse.org/t/-/404301/1?silent=true)). **#Enterprise** - In a discussion about community ownership models (tag: #enterprise-ready), @HAWK responded to concerns about marketing-owned communities by sharing how Discourse views support/enablement as retention—plus a candid note that Meta itself falls under Marketing internally ([read more](https://meta.discourse.org/t/-/404814/6?silent=true); topic context: [read more](https://meta.discourse.org/t/-/404814/1?silent=true)). **#Announcements** - The “nested replies” announcement (#nested-replies) got a design-focused question: @Larry_Baker asked what theme was used in a screenshot, and @Lilly answered it was “original foundation with wcag palette” ([read more](https://meta.discourse.org/t/-/402812/57?silent=true), [read more](https://meta.discourse.org/t/-/402812/58?silent=true); announcement context: [read more](https://meta.discourse.org/t/-/402812/1?silent=true)). **#Site Management** - In the “Making your forum more accessible” how-to (#accessibility, #how-to), @happyhappy asked whether WCAG options mainly help partial sight users rather than people with no sight—continuing the thread’s practical focus on accessibility outcomes ([read more](https://meta.discourse.org/t/-/226242/6?silent=true); guide context: [read more](https://meta.discourse.org/t/-/226242/1?silent=true)). **#support:migration** - A new migration thread (tag: #seo) reported a significant Bing ranking/weight drop after moving from Flarum to Discourse, with @AkarinLiu posting progress updates ([read more](https://meta.discourse.org/t/-/405270/1?silent=true), [read more](https://meta.discourse.org/t/-/405270/2?silent=true)). @merefield suggested comparing crawler-visible HTML outputs (e.g., via curl with a bot user-agent) between the old and new installs to isolate what changed ([read more](https://meta.discourse.org/t/-/405270/3?silent=true); topic: [read more](https://meta.discourse.org/t/-/405270/1?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@david** wrapped up the [try.discourse.org](http://try.discourse.org) “account no longer on hold” issue by thanking reporters, linking the fix PR, and confirming deployment—turning a report into a shipped resolution ([read more](https://meta.discourse.org/t/-/405253/10?silent=true); thread context: [read more](https://meta.discourse.org/t/-/405253/1?silent=true)). - **@HAWK** contributed to a strategic discussion on who should “own” communities, addressing concerns about marketing-led stewardship and describing Discourse’s perspective on community support as a retention driver ([read more](https://meta.discourse.org/t/-/404814/6?silent=true); topic: [read more](https://meta.discourse.org/t/-/404814/1?silent=true)). * * * Yesterday’s vibe: part bug-fix sprint, part philosophy seminar—because on Meta you can deploy a production fix _and_ debate who “owns” a community before lunch. ---
### 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 juni 2026 om 21:02 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/894 "2026-06-15T21:02:10Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… A snapshot of the last 24 hours of discussion and development chatter on Meta (2026-06-14 → 2026-06-15). * * * ## Key Stats - **New posts:** 42 - **New topics:** 4 ### Top users (posts / likes) | User | Posts | Likes | | --- | --- | --- | | @awesomerobot | 7 | 9 | | @nathank | 5 | 7 | | @HAWK | 5 | 6 | | @zogstrip | 4 | 5 | | @Falco | 1 | 5 | | @merefield | 2 | 2 | | @pfaffman | 2 | 2 | | @Jagster | 1 | 2 | | @chapoi | 1 | 2 | | @Lilly | 1 | 2 | **What the day revolved around (with receipts):** - Search indexing edge-cases with inline HTML landed in a new #Support thread: [read more](https://meta.discourse.org/t/-/405296/1?silent=true) - Events UX got multiple angles of attention, from notification email content to RSVP sorting: [read more](https://meta.discourse.org/t/-/405280/1?silent=true) and [read more](https://meta.discourse.org/t/-/405312/1?silent=true) - Accessibility questions resurfaced (screen readers + scrolling behavior): [read more](https://meta.discourse.org/t/-/405274/3?silent=true) and [read more](https://meta.discourse.org/t/-/202652/7?silent=true) - A few “ongoing maintenance” threads moved forward too—plugins, bugs, and infra: [read more](https://meta.discourse.org/t/-/180967/167?silent=true), [read more](https://meta.discourse.org/t/-/404301/3?silent=true), and [read more](https://meta.discourse.org/t/-/405047/2?silent=true) > On event RSVP avatar ordering, @zogstrip summarized the current behavior as being sorted by _status_ and then by _user id_—stable, but not meaningful to humans: [read more](https://meta.discourse.org/t/-/405312/2?silent=true) * * * ## Interesting Topics #### #Support - @Jagster reported that certain inline HTML (notably `strong` + `sub`) can break search matches (e.g., `B17-vitamiini`), and @awesomerobot reproduced it—likely because the indexer splits the term into fragments: [read more](https://meta.discourse.org/t/-/405296/2?silent=true) - In a French-language category UX question, @awesomerobot noted that some `/categories` layouts don’t visually indicate “recent activity” well, and suggested using a different `Desktop category page style` that exposes recency cues: [read more](https://meta.discourse.org/t/-/405194/4?silent=true) - Event hosts asked how the “going” user icons are ordered; @zogstrip explained the current sorting and flagged it as something to improve (with a fix planned): [read more](https://meta.discourse.org/t/-/405312/3?silent=true) - A new thread dug into _end-user_ JAWS screen reader best practices; @HAWK responded by clarifying what kind of guidance the poster was seeking (using JAWS itself vs. design practices): [read more](https://meta.discourse.org/t/-/405274/2?silent=true) - A self-hoster hitting GitHub HTTPS timeouts during rebuilds asked about an SSH-only workaround; @pfaffman emphasized that most of the toolchain expects HTTPS and suggested addressing outbound connectivity instead: [read more](https://meta.discourse.org/t/-/405047/2?silent=true) #### #ux - @nathank argued that event notification emails feel _too lean_ when they omit the Event **Description** field, even if the topic body is included—pushing for richer event emails: [read more](https://meta.discourse.org/t/-/405280/1?silent=true) - “Streamlined date/event insertion UI” got an update: @nathank pointed to improvements for specified Calendar & Event categories, while follow-ups clarified the request was really about streamlining the _individual event creation_ experience too: [read more](https://meta.discourse.org/t/-/359938/8?silent=true) - Icon rendering in Category/Group descriptions remains inconsistent; @chapoi suggested it’s fixed in the base theme but still broken on Meta’s branded theme due to how a banner is rendered: [read more](https://meta.discourse.org/t/-/338969/7?silent=true) #### #bug - The “topic-cards” markup issue (“stray ``”) saw progress; @awesomerobot confirmed the fix was merged after updates from participants: [read more](https://meta.discourse.org/t/-/404301/3?silent=true) - Chat thumbnails bypassing `s3_cdn_url` (showing raw S3 bucket URLs) appears to have been merged per @Lilly’s update, reducing a sharp edge for CDN setups: [read more](https://meta.discourse.org/t/-/404174/5?silent=true) - A bug report in Chinese described how disabling a “report description” can inadvertently hide other descriptions; @zogstrip linked it to an upstream fix: [read more](https://meta.discourse.org/t/-/405254/2?silent=true) #### #customization:plugin - The Resenha voice rooms plugin continues to evolve—@Falco shared that **video (screen-share + webcam)** is now available behind a site setting: [read more](https://meta.discourse.org/t/-/389056/50?silent=true) - “Calendar RSVP Posts” explored reducing UI confusion; @mariodsantana added a mutex to avoid race conditions and shipped a new plugin version for feedback: [read more](https://meta.discourse.org/t/-/390058/10?silent=true) #### #Self-hosting - Multisite vs. multiple containers got a crisp rule of thumb from @pfaffman: if sites can share the same plugins and SMTP, multisite is best; otherwise separate containers per site (optionally sharing one DB container): [read more](https://meta.discourse.org/t/-/175275/12?silent=true) #### #Enterprise - In a discussion about who should “own” a community internally, @HAWK outlined how governance and workload get split across a small org—distinguishing support, customer success, and marketing strategy: [read more](https://meta.discourse.org/t/-/404814/8?silent=true) * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - **@awesomerobot** jumped on a reproducible search bug where inline tags split words in the index ([read more](https://meta.discourse.org/t/-/405296/2?silent=true)), merged a fix for topic-cards markup ([read more](https://meta.discourse.org/t/-/404301/3?silent=true)), and weighed in on category page activity indicators ([read more](https://meta.discourse.org/t/-/405194/4?silent=true)). They also revisited accessibility + scrolling behavior in older threads to see if improvements landed ([read more](https://meta.discourse.org/t/-/329422/4?silent=true), [read more](https://meta.discourse.org/t/-/202652/7?silent=true)), and clarified WCAG naming/intent in an accessibility how-to thread ([read more](https://meta.discourse.org/t/-/226242/8?silent=true)). - **@HAWK** guided a migration/SEO concern by noting it’s normal to see a temporary drop after migrations and that it tends to self-correct ([read more](https://meta.discourse.org/t/-/405270/6?silent=true)), asked for clarification to better answer a JAWS screen reader question ([read more](https://meta.discourse.org/t/-/405274/2?silent=true)), and suggested a direction for “search-term triggers” (likely via theme customization, with a nudge toward workflow possibilities) ([read more](https://meta.discourse.org/t/-/405163/2?silent=true)). They also added deeper org context to the community ownership models discussion ([read more](https://meta.discourse.org/t/-/404814/8?silent=true)). - **@zogstrip** drove multiple “this will be fixed” moments: confirming an upcoming fix for event emails missing the Event Description ([read more](https://meta.discourse.org/t/-/405280/3?silent=true)), explaining and patching the unintuitive sorting of “going” avatars in events ([read more](https://meta.discourse.org/t/-/405312/2?silent=true), [read more](https://meta.discourse.org/t/-/405312/3?silent=true)), and pointing to a fix for a report-description setting that hid other descriptions ([read more](https://meta.discourse.org/t/-/405254/2?silent=true)). - **@Falco** shipped a meaningful feature update to the Resenha voice rooms plugin by adding optional video (screen-share + webcam) behind a setting ([read more](https://meta.discourse.org/t/-/389056/50?silent=true)). - **@chapoi** flagged theme-level nuance around missing icons in descriptions—suggesting the base theme is fixed while Meta’s branded theme may still need adjustment ([read more](https://meta.discourse.org/t/-/338969/7?silent=true)). - **@isaac** kept the Nested Replies test thread warm with an in-thread test reply (because someone has to) ([read more](https://meta.discourse.org/t/-/398759/121?silent=true)). * * * If yesterday was any indication, tomorrow’s Meta will be a place where `` tags become searchable, event emails get less “lean,” and RSVP avatars finally stop sorting like it’s 1999. ---
### 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 juni 2026 om 21:01 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/895 "2026-06-16T21:01:18Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours (2026-06-15 → 2026-06-16), Meta saw **53 new posts** across **8 new topics**. For the full context behind today’s biggest conversations, see the threads on community engagement ([read more](https://meta.discourse.org/t/-/405401/1?silent=true)) and reliability/maintenance workarounds ([read more](https://meta.discourse.org/t/-/405387/1?silent=true)). **Top users (posts / likes received in the last 24h)** | User | Posts | Likes | | --- | --- | --- | | @chapoi | 10 | 21 | | @Michael_Furtenbach | 10 | 8 | | @Helga_Razinkova | 3 | 13 | | @noahl | 2 | 13 | | @JammyDodger | 1 | 12 | | @Canapin | 2 | 7 | | @merefield | 1 | 6 | | @Bas | 1 | 5 | | @awesomerobot | 1 | 4 | | @Tris20 | 2 | 4 | * * * ## Interesting Topics ### #community-building Building - @Helga_Razinkova asked if others are seeing a **drastic drop in community activity** , sharing engagement charts and looking for root causes; replies explored whether support forums are being reshaped by AI-first habits and what “new reasons to return” could look like ([read more](https://meta.discourse.org/t/-/405401/1?silent=true), plus AI impact speculation from @JammyDodger [read more](https://meta.discourse.org/t/-/405401/5?silent=true), community redesign ideas from @noahl [read more](https://meta.discourse.org/t/-/405401/8?silent=true), and the “information degradation cycle” warning from @awesomerobot [read more](https://meta.discourse.org/t/-/405401/9?silent=true)). - A Chinese-language thread continued on whether search can return a **friendly “tip” message** for specific keywords; @j.jaffeux noted it’s feasible but needs UX work and performance optimization (and likely not for a few weeks/months) ([read more](https://meta.discourse.org/t/-/405163/3?silent=true)). ### #Self-hosting (#backups) - @Michael_Furtenbach hit a **backup restore failure** due to duplicate rows preventing a unique index rebuild; @chapoi linked prior similar cases and coached through debugging ([read more](https://meta.discourse.org/t/-/405387/2?silent=true)), and @gerhard provided a cleanup + reindex approach that ultimately got the restore working ([read more](https://meta.discourse.org/t/-/405387/15?silent=true), followed by the final “it worked!” confirmation [read more](https://meta.discourse.org/t/-/405387/22?silent=true)). ### #Support (#bug) - Transparent PNGs uploaded for flair/badges/logos were appearing with a **white background** ; the root cause was PNGs being auto-converted to JPG, and setting image quality to “original” resolved it ([read more](https://meta.discourse.org/t/-/405378/1?silent=true), solution details [read more](https://meta.discourse.org/t/-/405378/2?silent=true)). - A plugin developer asked (in Chinese) how to configure **array-of-object site settings** with `json_schema` while still using Discourse pickers like categories/usernames—highlighting limitations when schema fields fall back to plain text inputs ([read more](https://meta.discourse.org/t/-/405376/1?silent=true)). ### #Announcements (#ai #ai-helper #ux) - Discourse’s **AI Helper suggestions** (category/tag) were moved _inline_ in the composer UI: category now offers a “Choose for me” one-step flow, while tags offer “Show AI suggestions” in-place ([read more](https://meta.discourse.org/t/-/405394/1?silent=true), with a quick clarification that it only applies when AI helper is enabled [read more](https://meta.discourse.org/t/-/405394/3?silent=true)). - In the long-running ActivityPub thread, @pmusaraj announced that **ActivityPub is now disabled on Meta** to simplify UX, while the plugin remains in maintenance mode (security/performance/bug fixes still supported, and updates recommended) ([read more](https://meta.discourse.org/t/-/266794/485?silent=true)). ### #ux (#calendar-and-events) - Feedback on the renewed calendar/events UX flagged several rough edges: clicking the event hero image linking to the image rather than the topic, missing plugin outlets in composer/advanced settings, lack of a unique CSS hook for custom fields, and a confusing “Advanced settings” toggle button state ([read more](https://meta.discourse.org/t/-/405388/1?silent=true)). - An “upcoming changes” UX issue continued: **notifications about upcoming changes** were hidden on the upcoming changes page; @martin pointed to a fix already in progress ([read more](https://meta.discourse.org/t/-/405009/4?silent=true)). - The “streamlined date/event insertion UI” thread received another nod of appreciation, reflecting continued interest in reducing friction around inserting dates/events ([read more](https://meta.discourse.org/t/-/359938/10?silent=true)). ### #bug (#calendar-and-events) - A new bug report said **event creation fails** with `Validation failed: An event accepts only group names`, affecting creation via the upcoming events calendar and standard topic creation ([read more](https://meta.discourse.org/t/-/405428/1?silent=true)). - Another calendar/events bug report found that **event custom fields** are unexpectedly constrained: dots/dashes in field names crash the advanced settings dialog, and only lowercase/underscore fields persist reliably ([read more](https://meta.discourse.org/t/-/405386/1?silent=true)). - An older-but-still-active bug thread noted intermittent **500 errors when moving posts** remain unresolved and hard to reproduce, with no obvious nginx log evidence on the container side ([read more](https://meta.discourse.org/t/-/397654/7?silent=true)). ### #development (#chat #plugin-api) - A dev discussion asked about officially supporting **extensible chat message block types** via a stable API (register type/schema/renderer); @j.jaffeux said it’s not high on the roadmap but requested more detail on the desired API surface ([read more](https://meta.discourse.org/t/-/405006/2?silent=true), with concrete proposed capabilities from @Anton_Akhmerov [read more](https://meta.discourse.org/t/-/405006/3?silent=true)). ### #Enterprise (#enterprise-ready) - The “community ownership models” discussion continued with reflections on whether Meta is best framed as customer support vs marketing when many users aren’t paying customers—changing how “ownership” lines get drawn ([read more](https://meta.discourse.org/t/-/404814/9?silent=true)). ### #Announcements (#feedback #new-feature #form-templates) - New feedback arrived on **Form Templates** : @mentalstring praised the feature but requested more control over post-body output formatting, and suggested editing a post could return users to the form to preserve validation/structure ([read more](https://meta.discourse.org/t/-/278631/92?silent=true)). * * * ## Activity by the [@team](https://meta.discourse.org/groups/team?silent=true) Group - @chapoi was all over today’s support + product updates: they helped diagnose the backup restore unique-index failure and pointed to prior solutions before the thread reached a working fix ([read more](https://meta.discourse.org/t/-/405387/2?silent=true), troubleshooting follow-ups [read more](https://meta.discourse.org/t/-/405387/8?silent=true), and later steps [read more](https://meta.discourse.org/t/-/405387/12?silent=true)); they also posted the solution for transparent PNG uploads getting a background by addressing JPG auto-conversion and image quality settings ([read more](https://meta.discourse.org/t/-/405378/2?silent=true)); and they announced the inline composer integration for AI suggestions ([read more](https://meta.discourse.org/t/-/405394/1?silent=true)). They also chimed in on the broader “engagement drop” discussion and the role AI might be playing ([read more](https://meta.discourse.org/t/-/405401/6?silent=true)). - @Bas jumped into the community activity decline thread to ask for specifics on _what_ is declining (pageviews, topics, active users), helping steer the conversation toward measurable diagnosis ([read more](https://meta.discourse.org/t/-/405401/2?silent=true)). - @awesomerobot expanded the “AI-first support” angle with a caution about an **information degradation cycle** (communities shrinking reduces AI training data, which makes AI worse, leaving fewer places to ask) ([read more](https://meta.discourse.org/t/-/405401/9?silent=true)). - @gerhard delivered the practical win of the day: clear instructions to remove duplicates + rebuild indexes (and a privilege workaround via `reindexdb`) that enabled a successful restore on a long-running forum backup ([read more](https://meta.discourse.org/t/-/405387/15?silent=true), privilege workaround [read more](https://meta.discourse.org/t/-/405387/21?silent=true)). - @pmusaraj announced that ActivityPub has been **disabled on Meta** while the plugin remains supported in maintenance mode, and urged plugin users to update due to merged security fixes ([read more](https://meta.discourse.org/t/-/266794/485?silent=true)). - @j.jaffeux engaged on extensibility and search UX: they asked what plugin API would be needed to support extending chat message blocks ([read more](https://meta.discourse.org/t/-/405006/2?silent=true)), and confirmed feasibility (with caveats) for keyword-triggered search messaging in the Chinese-language thread ([read more](https://meta.discourse.org/t/-/405163/3?silent=true)). - @martin pointed to an incoming fix for the UX issue where upcoming-change notifications were hidden on the upcoming changes page ([read more](https://meta.discourse.org/t/-/405009/4?silent=true)). * * * Yesterday’s theme was clear: between **reindexing to save backups** and **AI reshaping engagement** , Meta managed to be both a repair shop _and_ a crystal ball—try not to click any event hero images on your way out. ---
### 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 juni 2026 om 01:32 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/896 "2026-06-18T01:32:45Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, Meta saw **66 new posts** across **27 topics** , generating **72 likes** in total. The community continues to buzz with both high-level product strategy discussions and granular technical troubleshooting. **Top Posters by Likes:** - @Chapoi (16 likes, 7 posts) – consistently active across multiple feature discussions and support threads - @Zogstrip (7 likes, 4 posts) – busy merging fixes for polls, event custom fields, and more - @Singi2016cn (6 likes, 5 posts) – driving a key discussion on missing `type: group` site setting implementation - @Gassim (5 likes, 2 posts) – reported a logging gap for poll closures, prompting an immediate fix - @SkyeDragon (5 likes, 2 posts) – proposed an elegant UX improvement for emoji display - @Tyler-Mairose-Sp (4 likes, 2 posts) – provided detailed, constructive feedback on the new admin dashboard - @Jumagura (4 likes, 1 post) – released an updated plugin version fixing deprecation warnings - @Davidb (3 likes, 2 posts) – merged a change to preserve transparency for site assets - @Darkpixlz (2 likes, 3 posts) – troubleshooting a thorny asset 500 error with hardware insights - @Gerhard (2 likes, 2 posts) – helped clarify site setting history and translation tooling ## Interesting Topics ### #Announcements - The [redesigned admin dashboard](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/12?silent=true) preview continues to generate rich feedback. @Tyler-Mairose-Sp asked insightful questions about [Data Explorer](https://meta.discourse.org/t/32566?silent=true) custom query response formats, how top countries are calculated in site traffic (confirmed by @Chapoi as IP-based), and requested highlight section personalization and tile reordering – which @Chapoi [confirmed is on the roadmap](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/13@chapoi?silent=true). @Nat clarified that the dashboard is already [toggleable for testing](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/11?silent=true) via `/admin/config/upcoming-changes`. [read more](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/14?silent=true) ### #Support - @Singi2016cn discovered that the `type: group` site setting type appears to [never have been implemented](https://meta.discourse.org/t/type-group/405487/6?silent=true) as a select dropdown, despite documentation hints. @Chapoi confirmed it was a long-standing gap, with @Gerhard [noting](https://meta.discourse.org/t/type-group/405487/6?silent=true) a TODO in the importer script regarding documentation. The correct current approach is `type: group_list` with custom validation for single-selection. [read more](https://meta.discourse.org/t/type-group/405487/4?silent=true) - @Gassim asked how to determine [who closed a poll](https://meta.discourse.org/t/who-closed-the-poll/405495/1?silent=true) – a data point not logged in standard post revisions or staff logs. @Asa suggested a [Data Explorer](https://meta.discourse.org/t/32566?silent=true) query against `post_revisions`, but @Gassim [reported](https://meta.discourse.org/t/who-closed-the-poll/405495/4?silent=true) this didn’t capture poll status changes. @Zogstrip promptly [merged a fix](https://meta.discourse.org/t/who-closed-the-poll/405495/5?silent=true) that both displays who closed a poll inline and logs the action for audit. [read more](https://meta.discourse.org/t/who-closed-the-poll/405495/5?silent=true) - @Darkpixlz described [random 500 errors](https://meta.discourse.org/t/lots-of-assets-randomly-returning-500/405482/1?silent=true) on JavaScript assets, with `NS_ERROR_CORRUPTED_CONTENT` in browsers. @Lilly diagnosed the root cause: the server’s [donated older SSDs](https://meta.discourse.org/t/lots-of-assets-randomly-returning-500/405482/2?silent=true) with blinking orange Dell firmware are likely producing high I/O latency, causing 30-second timeouts when Discourse attempts simultaneous reads of compiled assets. She recommended replacing the drives or using Cloudflare R2 object storage as a workaround. @Darkpixlz [confirmed](https://meta.discourse.org/t/lots-of-assets-randomly-returning-500/405482/3?silent=true) this explanation aligns perfectly with the symptoms. [read more](https://meta.discourse.org/t/lots-of-assets-randomly-returning-500/405482/3?silent=true) - @Davidb [announced](https://meta.discourse.org/t/transparent-images-are-being-uploaded-with-a-background/405378/9?silent=true) a merged change (PR #40975) that prevents transparent PNGs from being converted to JPG for branded site assets like logos and badges, eliminating a long-standing workaround for designers. [read more](https://meta.discourse.org/t/transparent-images-are-being-uploaded-with-a-background/405378/9?silent=true) - @Alefattorini asked about [reducing AI token usage](https://meta.discourse.org/t/reducing-ai-token-usage-with-category-filtering/405510/1?silent=true) by restricting the AI bot to a specific category. @Falco [pointed out](https://meta.discourse.org/t/reducing-ai-token-usage-with-category-filtering/405510/2?silent=true) that the Agent Edit form already supports category filtering for the default Search tool. [read more](https://meta.discourse.org/t/reducing-ai-token-usage-with-category-filtering/405510/2?silent=true) - @Ethsim2 [explored](https://meta.discourse.org/t/best-practice-for-moving-users-away-from-institutional-email-domains-while-avoiding-duplicate-impersonation-accounts/405143/2?silent=true) best practices for transitioning a community away from institutional email/SSO while avoiding impersonation. @Pfaffman noted that institutional email provides stronger identity assurance, while @Ethsim2 outlined a cautious manual transition strategy: adding personal emails as secondary, keeping the splash page clear, and avoiding automatic account merges. [read more](https://meta.discourse.org/t/best-practice-for-moving-users-away-from-institutional-email-domains-while-avoiding-duplicate-impersonation-accounts/405143/3?silent=true) ### #Contribute > Bug - @Newbit1337 reported an [error creating events](https://meta.discourse.org/t/error-when-trying-to-create-an-event/405428/2?silent=true) that pointed to an “invalid group” despite `status="public"`. @Awesomerobot couldn’t reproduce but @Newbit1337 [traced](https://meta.discourse.org/t/error-when-trying-to-create-an-event/405428/3?silent=true) the issue to a user named `trust_level_0` – changing status to `status="standalone"` resolved it. [read more](https://meta.discourse.org/t/error-when-trying-to-create-an-event/405428/3?silent=true) - @Octobadger reported a [large poll bug](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511/1?silent=true) on [community.drownedinsound.com](http://community.drownedinsound.com) where users cannot amend votes on polls with 50-100 options. Clicking “Vote” buttons scrolls to the bottom of the page instead of showing the voting interface. @Zogstrip has [a fix brewing](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511/4?silent=true) for part of the issue (PR #41001) but notes the scroll-to-bottom problem is harder to resolve. [read more](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511/4?silent=true) ### #Contribute > UX - @SkyeDragon proposed that hovering over emoji should show a [larger version](https://meta.discourse.org/t/hover-over-emoji-could-show-larger-version-of-emoji/405546/1?silent=true), similar to Discord’s implementation, especially useful for custom emoji drawn at full resolution. @Canapin [teased](https://meta.discourse.org/t/hover-over-emoji-could-show-larger-version-of-emoji/405546/2?silent=true) that default emoji are usually readable, but @SkyeDragon [confirmed](https://meta.discourse.org/t/hover-over-emoji-could-show-larger-version-of-emoji/405546/3?silent=true) the issue is most acute for custom emoji. [read more](https://meta.discourse.org/t/hover-over-emoji-could-show-larger-version-of-emoji/405546/1?silent=true) ### #Contribute > Feature - @Steradiant requested the ability to [optionally allow other groups to open/close topics](https://meta.discourse.org/t/optionally-allow-other-groups-to-open-close-topics/405497/1?silent=true) for more efficient workflow with topic timers. @Chapoi [suggested](https://meta.discourse.org/t/optionally-allow-other-groups-to-open-close-topics/405497/2?silent=true) using category moderators with the [Category Moderators Enhancer](https://meta.discourse.org/t/category-moderators-enhancer/268065?silent=true) plugin. [read more](https://meta.discourse.org/t/optionally-allow-other-groups-to-open-close-topics/405497/2?silent=true) - @Singi2016cn [formalized a feature request](https://meta.discourse.org/t/type-group/405492/1?silent=true) to implement `type: group` as a single-select dropdown for site settings (similar to `type: category`). @Chapoi [merged the addition](https://meta.discourse.org/t/type-group/405492/2?silent=true) on the same day via PR #40981 – a remarkably fast turnaround. [read more](https://meta.discourse.org/t/type-group/405492/2?silent=true) - @Nathank [requested](https://meta.discourse.org/t/we-could-do-with-a-couple-of-extra-options-in-the-recurrence-dropdown/405557/1?silent=true) additional recurrence options for the Calendar plugin: every 3rd week, the xth day of every other/3rd/6th/12th month. He also suggested [a broader discussion](https://meta.discourse.org/t/add-more-recurrent-event-options-to-calendar-plugin/236593/2?silent=true) about adopting a Google Calendar-style custom recurrence interface. [read more](https://meta.discourse.org/t/we-could-do-with-a-couple-of-extra-options-in-the-recurrence-dropdown/405557/1?silent=true) ### #Plugin - @Jumagura [released](https://meta.discourse.org/t/discourse-category-lockdown/70649/134?silent=true) the latest version of the [Discourse Category Lockdown](https://github.com/paviliondev/discourse-category-lockdown/pull/21) plugin, fixing deprecation warnings. [read more](https://meta.discourse.org/t/discourse-category-lockdown/70649/134?silent=true) - @Jagster [commented](https://meta.discourse.org/t/activitypub-plugin/266794/486?silent=true) on the ActivityPub plugin thread, noting that low follower counts on the Fediverse stem from non-Discourse users needing to know exactly what to follow, while Meta is a special case where admins are the primary user base. [read more](https://meta.discourse.org/t/activitypub-plugin/266794/486?silent=true) ### #Community Building Building - @Satonotdead contributed a [thoughtful reflection](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/19?silent=true) on the AI-driven decline in support forum activity, showcasing examples of forums where AI answers have replaced human interaction. He argued that surviving communities must urgently focus on fostering belonging through surveys, onboarding, events, and curated human content. [read more](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/19?silent=true) ### #enterprise - @Mcwumbly [detailed](https://meta.discourse.org/t/community-ownership-models/404814/10?silent=true) the multi-faceted ownership model of Meta itself, noting that community strategy has emerged organically from dogfooding and support to now include retention, advocacy, and business growth – reporting under Marketing but heavily involving Customer Success, Product, and the executive team. [read more](https://meta.discourse.org/t/community-ownership-models/404814/10?silent=true) ## Activity by the @Team Group The @Team group was highly productive today, with several members merging code changes and providing detailed support: - @Chapoi was the most active team member, engaging across multiple threads. He [confirmed](https://meta.discourse.org/t/type-group/405487/4?silent=true) that `type: group` was never implemented, then [merged the implementation](https://meta.discourse.org/t/type-group/405492/2?silent=true) within hours (PR #40981). He also [provided feedback](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/13?silent=true) on dashboard questions and suggested the [Category Moderators Enhancer](https://meta.discourse.org/t/optionally-allow-other-groups-to-open-close-topics/405497/2?silent=true) plugin for topic management permissions. - @Zogstrip was prolific with fixes. He [merged a change](https://meta.discourse.org/t/who-closed-the-poll/405495/5?silent=true) (PR #40989) to show who closed a poll both inline and in audit logs. He [fixed](https://meta.discourse.org/t/event-custom-fields-can-only-be-lowercase/405386/3?silent=true) the event custom fields case restriction (PR #40995). He also has [a partial fix brewing](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511/4?silent=true) (PR #41001) for the large poll amendment bug, while noting the scroll-to-bottom issue is harder. - @Davidb [merged PR #40975](https://meta.discourse.org/t/transparent-images-are-being-uploaded-with-a-background/405378/9?silent=true) to preserve transparency for branded site assets like logos and badges, [referencing](https://meta.discourse.org/t/category-icon-converts-to-jpeg/375797/5?silent=true) the same fix for category icon JPEG conversion. - @Gerhard [provided historical context](https://meta.discourse.org/t/type-group/405487/6?silent=true) on the `type: group` site setting, confirming it was likely never implemented as a select. He also [shared](https://meta.discourse.org/t/cant-find-string-all-in-reactions/404525/4?silent=true) the better translation search tool at [translations.discourse.org](https://translations.discourse.org/strings?q=%22All%22). - @Awesomerobot [investigated](https://meta.discourse.org/t/error-when-trying-to-create-an-event/405428/2?silent=true) an event creation error and also conducted [nested reply testing](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/122?silent=true) on the sandbox, alongside @Markvanlan who [pointed](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/134?silent=true) to the nested posts sandbox sites. - @Nat [clarified](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/11?silent=true) that the redesigned admin dashboard is already available for testing via the Upcoming Changes page. * * * > _“In a day where @Chapoi implemented a feature request from scratch in under four hours, we learned that on Meta Discourse, the gap between “wouldn’t it be nice if…” and “it’s been merged” is sometimes shorter than a coffee break.”_ ---
### 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 juni 2026 om 21:00 UTC](https://meta.discourse.org/t/daily-summary-9pm-utc/291850/897 "2026-06-18T21:00:32Z")
# Today on [meta.discourse.org](http://meta.discourse.org)… ## Key Stats In the last 24 hours, **89 posts** were created across **37 topics** , garnering **136 likes**. ### Top Users | @USERNAME | New Posts | Likes Received | | --- | --- | --- | | @Chapoi | 7 | 16 | | @Zogstrip | 5 | 16 | | @Sam | 2 | 11 | | @HAWK | 1 | 10 | | @SkyeDragon | 3 | 7 | | @Singi2016cn | 4 | 6 | | @Falco | 3 | 6 | | @Southpaw | 2 | 6 | | @Gassim | 2 | 5 | | @Mcwumbly | 2 | 4 | * * * ## Interesting Topics ### #Contribute > UX - **Hovering for a closer look at emoji:** @SkyeDragon [discovered](https://meta.discourse.org/t/hover-over-emoji-could-show-larger-version-of-emoji/405546/1?silent=true) that some custom emojis are too small to see properly at 16x16 and proposed a hover-to-enlarge feature. @Canapin [noted](https://meta.discourse.org/t/hover-over-emoji-could-show-larger-version-of-emoji/405546/2?silent=true) that default emojis are fine. @Sam [delivered](https://meta.discourse.org/t/hover-over-emoji-could-show-larger-version-of-emoji/405546/4?silent=true) a working theme component as a proof-of-concept. [read more](https://meta.discourse.org/t/hover-over-emoji-could-show-larger-version-of-emoji/405546?silent=true) - **Event calendar UX feedback:** @RGJ [reported](https://meta.discourse.org/t/event-calendar-ux-issues/405388/2?silent=true) an odd interaction bug where clicking the topic title input requires two clicks after editing event details, as the first click activates the post content area instead. [read more](https://meta.discourse.org/t/event-calendar-ux-issues/405388?silent=true) ### #Contribute > Feature - **Reviving PWA share-target on Android:** @Southpaw [revisited](https://meta.discourse.org/t/on-android-my-discourse-is-not-always-an-option-for-sharing/112176/5?silent=true) the idea of Discourse as a share target on Android, suggesting options like creating a topic or PM from shared content. @Carlh-Foa [agreed](https://meta.discourse.org/t/on-android-my-discourse-is-not-always-an-option-for-sharing/112176/7?silent=true) it would be great. @Falco then [showcased](https://meta.discourse.org/t/on-android-my-discourse-is-not-always-an-option-for-sharing/112176/8?silent=true) a working prototype with a PR ready. [read more](https://meta.discourse.org/t/on-android-my-discourse-is-not-always-an-option-for-sharing/112176?silent=true) - **Granting open/close topic permissions to other groups:** @Steradiant [proposed](https://meta.discourse.org/t/optionally-allow-other-groups-to-open-close-topics/405497/1?silent=true) a feature to allow specific groups to open and close topics for better workflow management. @Chapoi [suggested](https://meta.discourse.org/t/optionally-allow-other-groups-to-open-close-topics/405497/2?silent=true) the “Category Moderators Enhancer” plugin as a possible solution. [read more](https://meta.discourse.org/t/optionally-allow-other-groups-to-open-close-topics/405497?silent=true) - **Adding more recurrent event options:** @Nathank [requested](https://meta.discourse.org/t/we-could-do-with-a-couple-of-extra-options-in-the-recurrence-dropdown/405557/1?silent=true) additional recurrence patterns like every 3rd week, bi-monthly, quarterly, etc., suggesting Google Calendar’s custom recurrence as a model. This follows the recent addition of “nth weekday of the month” options. [read more](https://meta.discourse.org/t/add-more-recurrent-event-options-to-calendar-plugin/236593/2?silent=true) - **Implementing `type: group` for site settings:** Following a Chinese-language discussion about a missing feature, @Singi2016cn [formally requested](https://meta.discourse.org/t/type-group/405492/1?silent=true) the implementation of a single-group select setting (similar to `type: category`). @Chapoi [delivered](https://meta.discourse.org/t/type-group/405492/2?silent=true) by merging the addition. [read more](https://meta.discourse.org/t/type-group/405492?silent=true) ### #Contribute > Bug - **Large poll voting broken:** @Octobadger [reported](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511/1?silent=true) that users cannot amend votes on open polls with many options—clicking the “Vote” button scrolls to the bottom instead. @Zogstrip [fixed](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511/4?silent=true) part of the issue and then [completed](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511/5?silent=true) the second fix. [read more](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511?silent=true) - **Transparent images gaining backgrounds:** @Davidb [noted](https://meta.discourse.org/t/transparent-images-are-being-uploaded-with-a-background/405378/9?silent=true) that a fix was merged to prevent branded site assets (like logos) from being converted to JPG, preserving transparency. [read more](https://meta.discourse.org/t/transparent-images-are-being-uploaded-with-a-background/405378?silent=true) - **Event creation error linked to invalid group:** @Newbit1337 [found](https://meta.discourse.org/t/error-when-trying-to-create-an-event/405428/3?silent=true) that a test user named “trust\_level\_0” was causing an “invalid group” error. Changing the event status to `standalone` resolved the issue. [read more](https://meta.discourse.org/t/error-when-trying-to-create-an-event/405428?silent=true) ### #Support - **Who closed the poll?:** @Gassim [asked](https://meta.discourse.org/t/who-closed-the-poll/405495/1?silent=true) how to track which user closed a poll. @Asa [suggested](https://meta.discourse.org/t/who-closed-the-poll/405495/3?silent=true) a [Data Explorer](https://meta.discourse.org/t/32566?silent=true) SQL query. @Zogstrip then [added](https://meta.discourse.org/t/who-closed-the-poll/405495/5?silent=true) native support for showing and logging who closed a poll. [read more](https://meta.discourse.org/t/who-closed-the-poll/405495?silent=true) - **SSL-certificate asset errors and failing SSDs:** @Darkpixlz [described](https://meta.discourse.org/t/lots-of-assets-randomly-returning-500/405482/1?silent=true) random 500 errors on JS assets. @Lilly [diagnosed](https://meta.discourse.org/t/lots-of-assets-randomly-returning-500/405482/2?silent=true) failing SSDs as the likely cause, with I/O timeouts matching the 30-second error window. [read more](https://meta.discourse.org/t/lots-of-assets-randomly-returning-500/405482?silent=true) ### #News and Events > Blog - **How I use AI as the co-CEO of a remote company:** @HAWK [shared](https://meta.discourse.org/t/how-i-use-ai-as-the-co-ceo-of-a-remote-company/405564/1?silent=true) a companion discussion for a blog post detailing practical AI usage for remote team management. [read more](https://meta.discourse.org/t/how-i-use-ai-as-the-co-ceo-of-a-remote-company/405564?silent=true) ### #Community Building Building - **Facing the AI-driven support forum decline:** @Satonotdead [offered](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/19?silent=true) a thoughtful analysis on the existential challenge AI poses to support forums, advocating for increased focus on human-centered engagement. @JammyDodger [asked](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401/20?silent=true) for concrete examples of optimizing content for LLMs. [read more](https://meta.discourse.org/t/anyone-else-seeing-a-drastic-drop-in-community-activity-for-support-forums/405401?silent=true) ### #enterprise - **The strategy behind community ownership models:** @Mcwumbly [elaborated](https://meta.discourse.org/t/community-ownership-models/404814/10?silent=true) on how [meta.discourse.org](http://meta.discourse.org) evolved from dogfooding and support to serving marketing, customer success, and product development. @Ed_S [questioned](https://meta.discourse.org/t/community-ownership-models/404814/11?silent=true) where user bug reports fit. [read more](https://meta.discourse.org/t/community-ownership-models/404814?silent=true) ### #Plugin - **Discourse Category Lockdown updated:** @Jumagura [released](https://meta.discourse.org/t/discourse-category-lockdown/70649/134?silent=true) a new version fixing deprecation warnings. [read more](https://meta.discourse.org/t/discourse-category-lockdown/70649?silent=true) - **ActivityPub plugin follower challenges:** @Jagster [discussed](https://meta.discourse.org/t/activitypub-plugin/266794/486?silent=true) why visibility and follower counts remain low, noting that non-Discourse users must know the exact actor to follow. [read more](https://meta.discourse.org/t/activitypub-plugin/266794?silent=true) ### #Announcements - **Redesigned admin dashboard preview feedback:** @Tyler-Mairose-Sp [provided](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/12?silent=true) detailed feedback—asking about custom [Data Explorer](https://meta.discourse.org/t/32566?silent=true) report formats, the source of country traffic data, and the ability to reorder dashboard highlights. @Chapoi [responded](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/13?silent=true) that reordering is on the roadmap. [read more](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528?silent=true) ### #development - **No excerpt in categories API:** @Darkpixlz [reported](https://meta.discourse.org/t/no-excerpt-property-in-categories-api-response/405566/1?silent=true) that the category topics API endpoint lacks an `excerpt` property, despite being documented. [read more](https://meta.discourse.org/t/no-excerpt-property-in-categories-api-response/405566?silent=true) ### #Site feedback - **Daily Summary moved to workflows:** @Sam [announced](https://meta.discourse.org/t/daily-summary-feedback/291853/290?silent=true) that the Daily Summary feature now uses GitHub workflows for easier prompt engineering and testing, and shifted to a self-hosted DeepSeek v4 Flash model. [read more](https://meta.discourse.org/t/daily-summary-feedback/291853?silent=true) * * * ## Activity by the @Team Group The @Team group was busy tackling bugs and improving the platform. A highlight was @Zogstrip, who [fixed](https://meta.discourse.org/t/who-closed-the-poll/405495/5?silent=true) the “Who closed the poll?” issue by adding audit logging and direct display, and also [resolved](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511/4?silent=true) a major poll bug affecting large polls—[part 2](https://meta.discourse.org/t/large-poll-bug-users-cannot-amend-votes-on-open-polls/405511/5?silent=true) was completed shortly after. He also [fixed](https://meta.discourse.org/t/event-custom-fields-can-only-be-lowercase/405386/3?silent=true) the case-sensitivity bug in event custom fields. @Chapoi was active on multiple fronts: [merging](https://meta.discourse.org/t/type-group/405492/2?silent=true) the new `type: group` site setting, [advising](https://meta.discourse.org/t/optionally-allow-other-groups-to-open-close-topics/405497/2?silent=true) on category moderator tools, and [responding](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/13?silent=true) to dashboard feedback. @Sam shared a [theme component](https://meta.discourse.org/t/hover-over-emoji-could-show-larger-version-of-emoji/405546/4?silent=true) for emoji hover previews and [ported](https://meta.discourse.org/t/daily-summary-feedback/291853/290?silent=true) the Daily Summary to workflows. @Falco [provided](https://meta.discourse.org/t/on-android-my-discourse-is-not-always-an-option-for-sharing/112176/8?silent=true) a prototype and PR for Android share-target support, and [helped](https://meta.discourse.org/t/reducing-ai-token-usage-with-category-filtering/405510/2?silent=true) with AI token filtering. @Davidb [merged](https://meta.discourse.org/t/transparent-images-are-being-uploaded-with-a-background/405378/9?silent=true) a fix preventing transparent PNG assets from being converted to JPG. @Gerhard [contributed](https://meta.discourse.org/t/cant-find-string-all-in-reactions/404525/4?silent=true) a link to the translations tool for finding strings. @Nat [clarified](https://meta.discourse.org/t/a-preview-of-the-redesigned-admin-dashboard/404528/11?silent=true) the availability of the new dashboard via the “Upcoming changes” page. @Awesomerobot [attempted](https://meta.discourse.org/t/error-when-trying-to-create-an-event/405428/2?silent=true) to reproduce an event creation bug. @Mcwumbly [shared](https://meta.discourse.org/t/community-ownership-models/404814/10?silent=true) a thoughtful history of the meta community’s strategic evolution. * * * _After all that activity, it seems the Discourse team would rather fix a poll than close it—so the voting remains open for your next great idea!_ [Previous page](https://meta.discourse.org/t/daily-summary-9pm-utc/291850.md?page=31) [Next page](https://meta.discourse.org/t/daily-summary-9pm-utc/291850.md?page=33)