Resumo Diário (21h UTC)

Today on meta.discourse.org

Key Stats

Top contributors (posts / likes in the last 24h)

User Posts Likes Recent reference
Lilly 5 13 Helped explain profile titles in “regular” title thread and asked about disabling Upcoming Changes alerts without CSS in Upcoming Changes
Moin 2 9 Clarified that “regular” is a selectable title in this reply and pointed to UX discussion for anon reactions access in this reply
Noble_Fish 3 1 Raised moderation defaults gap in approval settings request and flagged potential duplicate badge issue in Badges thread
Arkshine 1 2 Investigated edge cases + shortcut ideas for Quote Callouts in this update
merefield 1 2 Posted a deployment + sponsor-feature split update in Locations plugin
Falco (team) 1 0 Advised on structured outputs model requirements in AI translations errors

Interesting Topics

Support

  • kairo162 noticed the label “regular” showing under usernames and across profiles; Lilly connected it to trust-level naming (post), and Moin clarified it’s a selectable Title (often from trust-level badges) that users can enable in preferences (solution). read more

  • In Chinese-language support, jack222 reported that anonymous visitors can’t view /activity/reactions and suggested either enabling read-only access or improving the error message (report); Moin pointed to an existing UX request discussing exactly that permission/UX gap (reply) and referenced the related feature request (Allow /activity/reactions to be visible by anon). read more

  • cshll hit a “Badges” page failure and suspected configuration issues (report); NateDhaliwal suggested checking the enable_badges site setting (reply), while Noble_Fish asked whether it duplicates an earlier thread (dup-check) and probed whether the install looked non-standard (follow-up). read more

  • cshll also posted an SEO/validation screenshot about “inspecting Live URL,” but without details yet—likely a “needs repro steps” thread unless more context lands (topic). read more

  • Noble_Fish requested global defaults for “New topic approval” and “New reply approval,” noting that current global settings only cover Everyone except selected groups and don’t match the workflow where a subset of users later gets moved into “must be reviewed” mode across all categories (feature request). read more

  • In a self-hosting migration discussion, Lilly shared a recent real-world migration (Ubuntu 24.04 → Ubuntu 24.04) and highlighted practical tips like shortening DNS TTL and planning for backup upload time (migration notes). read more

bug

  • janbolmeson reported that @discourse/mcp fails when connecting to Discourse installed in a subfolder (e.g. /forum) because tool calls drop the subpath—breaking validation and subsequent API calls (bug report). read more

  • In an ongoing structured-data issue, Richie noted Google tests still failing for three URLs due to missing mainEntity.suggestedAnswer.text, despite partial improvements (status update). read more

  • AI translation troubleshooting continued: RBoy encountered a 400 error tied to unsupported json_schema response formatting with a model change (error details), and Falco explained translations need a model that supports structured outputs (common in recent SOTA models) (guidance). read more

#Theme component

  • Quote Callouts got a UX + edge-case sweep: nathank observed rendering issues in excerpts/Oneboxes (note), scavin flagged the default shortcut as risky on macOS because users may hit ⌘+Q and quit the browser (macOS concern), and Arkshine weighed alternative key combos while tracking excerpt/Onebox behavior (response). read more

#Announcements

  • The “Upcoming Changes” notification system drew feedback on notification noise: Lilly asked if alerts can be disabled without CSS (preferring a setting-level solution) and shared a temporary CSS workaround (request + snippet); NateDhaliwal pointed out a likely remaining unread-count indicator even if notifications are hidden (reply). read more

#Plugin

  • The Locations plugin thread got a substantial update: merefield announced a fix now deployed (plus compatibility work) and described how Early Access differs from the public version—including a 3D globe users map and IP-based location lookup (release notes); gilles thanked them for the quick turnaround (thanks). read more

development

  • Theme authoring guidance discussions continued: BrianC asked how to approach forking a theme while ensuring the parent stays updated over time—raising the common long-term maintenance question for serious customizations (question). read more

General

  • A complex “facts from logs” question landed: Sukenik asked how a forensic expert might establish whether historical suspensions carried over during a 2023 migration from Discourse to a custom forum (scenario); Andrew_Rowe highlighted how hosting model and log retention matter, and that three years is a long time for server logs to survive (initial response). read more

Activity by the @team Group

  • Falco helped unblock AI translation troubleshooting by explaining that translation workflows require a model that supports structured outputs, and that most modern SOTA models now include this capability (AI translations guidance, context in error report).

If you made it through today’s feed without accidentally hitting ⌘+Q while trying to insert a callout, you’ve earned your Regular title the hard way.

Today on meta.discourse.org

Key Stats

  • New posts (last 24h): 97 (spread across threads like the iOS PWA push investigation in read more and the new bulk tag workflow announcement in read more)
  • New topics (last 24h): 13 (including new reports like the Edge mobile modal sizing issue in read more, plus new how-tos like standardizing sidebar categories in read more)

Top users (posts / likes in the last 24h)

User Posts Likes Recent activity sample
Lilly 15 21 Automation troubleshooting in read more and theme/login guidance in read more
Moin 10 12 Sidebar defaults discussion in read more and passkeys setting tip in read more
chapoi 9 7 Confirming old modal UI and next steps in read more
klappradla 2 7 Deep-dive + PR proposal for iOS PWA push in read more
RGJ 2 5 Klipy + infinite search limit bug analysis in read more
denvergeeks 7 3 Repro attempts for repeated image uploads in the RTE in read more
nat 1 3 Translation/quote attribute investigation in read more
lindsey 1 3 Announcing the new bulk tag management modal in read more
sniper756 1 3 Reporting the Edge mobile “permanent delete” modal width issue in read more
fzngagan 1 4 Publishing a sidebar-standardization how-to in read more

Interesting Topics

#Announcements

  • Staff introduced a cleaner bulk-tag workflow: a single Manage Tags modal replaces separate add/replace/remove actions, prompting follow-up feedback about revision history clarity and missing UI affordances in Better bulk tag management. Related: the missing tag info button discussion in read more and the older feature request this essentially fulfills in read more.

#Site Management

bug

ux

Support

#Self-hosting

  • A migration/restore failure involving Cloudflare R2 and checksum incompatibilities surfaced during a server move; troubleshooting and environment details are collected in 迁移Discourse恢复数据失败, including an R2-specific env-var suggestion in read more.

  • A “badges error launching” support thread turned into a broader self-hosting health-check: plugin overload, incorrect SMTP settings, and risky storage choices were called out in Badges Error launching, with concrete “remove unofficial plugins first” guidance in read more.


Activity by the @team Group

  • chapoi confirmed the Edge mobile delete-modal is legacy UI and praised the report in read more, continued triage on the repeated-upload-in-RTE report in read more, and helped narrow self-hosting/plugin troubleshooting steps (including safe mode) in read more. chapoi also pulled nat into localization/quote metadata concerns in read more, and confirmed a fix got merged for reaction long-press behavior in read more.

  • fzngagan posted a clear step-by-step guide for enforcing consistent sidebar categories for all users in read more, sparking follow-up testing/edge-case questions from others in read more.

  • lindsey announced the consolidated bulk tag management modal and invited feedback in read more, which immediately surfaced UX expectations around tag tooling and revisions in read more.

  • nat analyzed why translated quotes lose useful source info (with German being hit hardest) and noted more evaluation work is needed in read more.

  • sam linked a fix PR for a reported MCP subfolder-install issue in read more.

  • manuel clarified how the “skills” track and the Blocks API should remain maintainable over time (and what to expect if you fork examples) in read more.

  • awesomerobot acknowledged the “Permanent” filter confusion on Upcoming Changes and explained it as an optional workflow step that was skipped for some items in read more.

  • gerhard proposed a concrete Cloudflare R2 workaround using AWS checksum-related env vars (plus rebuild steps) for restore failures in read more.

  • HAWK responded to an SEO console “Live URL inspection” concern, suggesting the issue is likely due to new/empty sitemaps and minimal public content in read more.

  • supermathie requested environment details (object store specifics) to unblock troubleshooting for the restore/migration failure in read more.


Yesterday’s theme was “tiny modals, missing automations, and service workers refusing to take charge”—may today’s builds be smooth, your tags tidy, and your push subscriptions actually land where they should.

Today on meta.discourse.org

Key Stats

  • New posts (last 24h): 53
  • New topics (last 24h): 12

Top contributors (posts / likes received on their recent activity):

User Posts Likes
Falco 2 23
Lilly 5 8
chapoi 3 3
zogstrip 3 2
bayardo.rivas 2 2
putty 2 2
martin 1 2
awesomerobot 1 2
ferdnyc 2 1
RGJ 1 1

Interesting Topics

#Announcements

Support

bug

ux

General


Activity by the @team Group


Yesterday’s theme was making things smaller, smoother, and less surprising—may your GIFs shrink into WebPs, your automations land on the right day of the month, and your 404s politely find their way home.