Resumen diario (21:00 UTC)

[system]

Today on meta.discourse.org…

Key Stats

• In the last 24 hours on the Latest page: 104 new posts and 13 new topics.

• Top users:

  • ToddZ: 11 posts, 10 likes
  • Moin: 10 posts, 8 likes
  • renato: 8 posts, 8 likes
  • Steradiant: 2 posts, 5 likes
  • saquetim: 3 posts, 4 likes
  • david: 1 post, 4 likes
  • supermathie: 2 posts, 4 likes
  • FINDarkside: 1 post, 3 likes
  • tobiaseigen: 10 posts, 3 likes
  • angus: 2 posts, 2 likes

Interesting Topics

• Feature In “Official groups/posts”, ice.d proposed an official marker for high-priority threads and asked “but if you have 5 pins what if one is the most important?” The discussion expanded when tobiaseigen pointed out the existing official reply feature (post 6), and folks compared the Category Banners vs the Category Headers component for keeping “about” topics visible.

• Dev In “Improving automatic switching of mobile/desktop modes”, stuwest explained how disabling the old viewport based mobile mode broke their category-first workflow. david clarified that linking to /categories is an alternative (post 6), and awesomerobot showed how setting “Desktop category page style” to “Categories with featured topics” and adjusting user prefs can restore the old feel (post 7).

• Dev saquetim announced that the widget rendering system will be disabled on next update, linking to PR #35504 and noting admins can still toggle deactivate_widgets_rendering for now (details).

• Dev The “Upcoming post stream changes” topic saw Boost report tests against Glimmer overrides and saquetim confirm that the Glimmer Post Stream will become default soon, even on incompatible sites, with clear instructions on toggling glimmer_post_stream_mode and deactivate_widgets_rendering (post 12).

• UX In “Show “and XY other groups” instead of “…” on user profile”, Steradiant flagged discoverability issues. ToddZ suggested a simple CSS tweak (post 2), Steradiant confirmed the hard-coded dots (post 3), and ToddZ refined the CSS to hide “…” and insert “and more” with a negative margin (post 4).

• UX “Can we improve usability of pinned topic site settings?” saw tobiaseigen propose merging two unpin prefs into one dropdown. ToddZ gave feedback on simplifying the UI (post 3), Moin weighed in on default vs. user override scenarios (post 4), and tobiaseigen updated his approach to clarify when the user pref appears (post 5).

• UX In “FluentUI emojis has background”, Don pointed out the new white-background +1 emoji from the recent commit 028aa5c. They compared the deleted version () vs. the new one ().

• Support “Any way to send PM to TL2 without including TL3 and TL4?” solved by tobiaseigen suggesting BCC or a custom group, and ToddZ highlighting the Discourse BCC Plugin and ad-hoc BCC workarounds (post 3, post 4, post 5).

• Support In “Why is my CSS color choice being overwritten?”, Jack_McCarthy showed how their theme CSS reset on reload. jahan_gagan recommended overriding the root variables (--primary-low, --primary-very-low, etc.) (post 2), and Jack confirmed it resolved the issue (post 3).

• Support “Chat icon in edit history – what does it mean?” saw NateDhaliwal self-answer that it marks a PM converted to a public topic (solution), and Moin linked to the code that implements it (post 3, source).

• #SiteFeedback: In “Unable To Invite Users To Topics on ask.discourse.com”, Rubi confirmed the workaround—sign into Meta then navigate to ask.discourse—and tobiaseigen noted that Site feedback has no Solution box but the issue is resolved (post 8).

• #Blog: “Why I Chose Discourse Over Discord” linked to the Blog post. ToddZ chimed in that it reads like a Joan Westenberg piece before realizing it was by jawestenberg (post 2).

• Community “Multilingual user feedback on Automatic Translations” featured FINDarkside collecting requests from polyglot users who prefer no auto-translation and suggesting per-user language opt-outs.

• #WordPress: “Webhook names query/inconsistent?” saw TimMOz patch supported_events in sync-discourse-topic.php and angus promise an update in the next plugin release (post 4).

• Bug In “Merge pasted preformatted text => code block in the new composer”, renato asked for repro steps but noted many inline/block code improvements have landed—inviting testers on latest.

Activity by the @team Group

• renato clarified smart-quotes behavior in Single/double quotes require two backspaces, addressed escaped tildes in Rich text editor bug, and weighed in on pasted preformatted text in Merge pasted preformatted text.

• tobiaseigen showed official posts in Official groups/posts and led the UX discussion on pinned topics in Improve pinned topics usability.

• saquetim posted on the widget rendering EOL in Widget rendering EOL announcement and the Glimmer Post Stream rollout in Post stream changes.

• supermathie guided API troubleshooting in 400 Bad Request Using API.

• david helped refine mobile/desktop switching in Automatic mobile switching.

• awesomerobot suggested desktop category layout tweaks in Automatic mobile switching.

• Falco offered a fix for older Chromium WebView issues in Chromium webview error.

• chapoi corrected button styling in Remove password button and discussed emoji alignment in FluentUI emojis background.

• lindsey weighed in on smart-quotes in Smart quotes in new composer.

• jordan.vidrine announced the end-of-life for the Custom Category Boxes component in Custom Category Boxes lifecycle update.

That’s a wrap—here’s hoping none of your next drafts disappear after you hit “cancel”!