# 每日摘要（UTC早上5点）

**URL:** <https://meta.discourse.org/t/daily-summary-5am-utc/291851>\
**Category:** Forum summaries\
**Created:** [2024年一月16日 21:58 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851 "2024-01-16T21:58:09Z")\
**Posts on this page:** 1\
**Page:** 38

<div class="post-metadata">

**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:** [2026年九月29日 05:01 UTC](https://meta.discourse.org/t/daily-summary-5am-utc/291851/972 "2026-09-29T05:01:39Z")

</div>

# Today on [meta.discourse.org](http://meta.discourse.org)…

A roundup of the last 24 hours on Meta - from invisible red lines to stereo mic quirks, there was plenty to discuss.

## Key Stats

In the last 24 hours, the community generated **34 new posts** across **17 new topics** , collecting **29 likes** along the way. The most active contributors (by posts and likes) were:

| User | Posts | Likes |
| --- | --- | --- |
| @Ed_S | 2 | 5 |
| @Lilly | 1 | 3 |
| @Nat | 1 | 3 |
| @MDNJ | 3 | 2 |
| @NateDhaliwal | 3 | 2 |
| @Nathank | 2 | 2 |
| @SkyeDragon | 2 | 2 |
| @Chrisr | 1 | 2 |
| @RGJ | 1 | 2 |
| @Burke | 4 | 1 |

These numbers reflect only the threads captured in this digest, so the full picture may be even livelier.

## Interesting Topics

### #ux

- @Ed_S spotted that the **red “last visit” line** is nearly invisible in dark mode on an iPhone, making it hard to find new content ([read more](https://meta.discourse.org/t/in-dark-mode-the-red-line-for-last-visit-is-almost-invisible/413508/1?silent=true)). In a [related thread](https://meta.discourse.org/t/i-dont-see-the-red-line-for-last-visit-has-it-been-removed/409097/5?silent=true), they theorised that the line may vanish entirely when there are no new posts and the marker moves to the top of the list - a rare but real edge case.

### #Support

- @NateDhaliwal noticed that [status.discourse.org](https://meta.discourse.org/t/status-discourse-org-still-says-starter-and-not-free/413458/1?silent=true) still listed the legacy “Starter” plan instead of “Free”. @RGJ pointed out that legacy plans can still exist, and @Nat [confirmed the status page has been updated](https://meta.discourse.org/t/status-discourse-org-still-says-starter-and-not-free/413458/3?silent=true) to include “Free” alongside “Starter”.

- Two read-only mode alarms rang: @Kesa_Sayed [reported their site stuck in read-only mode](https://meta.discourse.org/t/site-stuck-in-read-only-mode/413454/1?silent=true) with a 500 error when trying to disable it, and @Heather_Phillips [asked why her site suddenly became read-only](https://meta.discourse.org/t/urgent-read-only-mode/413517/1?silent=true). @Chrisr [explained](https://meta.discourse.org/t/site-stuck-in-read-only-mode/413454/2?silent=true) it was scheduled maintenance, and @Tgxworld [confirmed](https://meta.discourse.org/t/urgent-read-only-mode/413517/3?silent=true) the same, apologising for the inconvenience.

- @Burke asked whether **user\_badge webhook payloads** could include `username` alongside `user_id` to avoid an extra admin-only API call ([read more](https://meta.discourse.org/t/could-usernames-be-included-in-user-badge-webhook-payload/413448/1?silent=true)). @Putty suggested routing through [Discourse Workflows](https://meta.discourse.org/t/discourse-workflows/407100?silent=true), while @Itsbhanusharma argued it’s just one API call away; @Burke pushed back in [this reply](https://meta.discourse.org/t/could-usernames-be-included-in-user-badge-webhook-payload/413448/7?silent=true) with a least-privilege argument.

- @Welsh_Selkie hit a frustrating snag with the **Custom Wizard** plugin: dropdowns that pull options from user fields only display a single option, not the full list ([read more](https://meta.discourse.org/t/custom-wizard-dropdown-using-user-field-options-only-shows-one-option/413482/1?silent=true)). The thread includes detailed screenshots and a list of troubleshooting steps already tried.

- In the ongoing “Git hang” saga, @Agemo [posted a follow-up](https://meta.discourse.org/t/error-for-logged-in-users-and-git-hang/411513/36?silent=true) linking to a new, more detailed thread about their self-hosted instance.

### #Feature

- The long-running **“sudo mode” for admins** discussion continued: @Nathank expressed a desire for a low-friction way to experience the site as a regular user while retaining admin powers ([read more](https://meta.discourse.org/t/regular-mode-for-admins-and-moderators-e-g-something-like-sudo/211617/47?silent=true)). @NateDhaliwal suggested an impersonation-style banner with a countdown and exit button, and @Jonathan5 wanted the ability to select trust levels and groups.

- @Ethsim2 shared a thorough update on the PR for **creating individual event topics for recurring events** ([read more](https://meta.discourse.org/t/create-individual-event-topics-for-recurring-events/370600/25?silent=true)). They discussed using an `after_code` hook to backport the upstream patch, but still favour merging the successor behaviour directly into the bundled Events plugin.

- @MDNJ provided feedback on the **Horizon theme** with the Topic Thumbnails component, noting that the post excerpt disappears and the full-width mobile image can be visually ambiguous ([read more](https://meta.discourse.org/t/horizon-theme-and-topic-thumbnails-component/386764/16?silent=true)). @Satonotdead acknowledged the notes and promised to look into them.

### #Theme component

- @Lilly confirmed that the **Twitter Native Embed** component works as expected on her site ([read more](https://meta.discourse.org/t/twitter-native-embed/261792/121?silent=true)). Meanwhile, @Terraboss has released an [experimental fork](https://github.com/terraboss/discourse-x-native-embed) that fixes several issues, including removing the duplicate link above tweets, improving dark mode, and handling bare X links.

### #Announcements

- @SkyeDragon gave detailed feedback on the new **Discord-style voice and video rooms** (#voice), specifically that stereo mics are not downmixed to mono, which can leave listeners with audio in only one ear ([read more](https://meta.discourse.org/t/voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse/411337/71?silent=true)). @Falco noted that downmixing depends on the audio quality setting and suggested trying a lower bitrate.

- @MDNJ reported that the new **email code signup** feature fails when an invite code is set - the email is never sent, with no error message ([read more](https://meta.discourse.org/t/easier-account-signup-using-email-codes/407068/59?silent=true)). Despite that, they praised the signup method as more secure than generic passwords.

### #Plugin

- @MDNJ also raised a formatting inconsistency in the **Discourse Events** plugin, where date/time notation mixes 12-hour and 24-hour clocks and the day/month order varies between cards, popups, and excerpts ([read more](https://meta.discourse.org/t/discourse-events/97376/638?silent=true)). Changing the “display local time” setting made no difference.

### #Self-hosting

- @Agemo detailed a new **“Git hang” / “Oops error”** issue affecting admin and staff accounts, complete with a full backtrace pointing to `CurrentUserSerializer#has_new_upcoming_changes` ([read more](https://meta.discourse.org/t/the-git-hang-and-the-admin-mod-user-accs-oops-error-page-error/413475/1?silent=true)). The error appears related to timezone parsing of an invalid value.

### #development

- @Nathank flagged a broken **upcoming-events block** in the demo theme, noting that it works on [meta.discourse.org](http://meta.discourse.org) but broke in the demo after a core change ([read more](https://meta.discourse.org/t/skills-for-authoring-themes-and-blocks/401629/24?silent=true)). He pinged @Manuel for guidance.

## Activity by the @Team Group

- @Nat responded to a status page report by updating it to include the “Free” plan alongside the legacy “Starter” ([post](https://meta.discourse.org/t/status-discourse-org-still-says-starter-and-not-free/413458/3?silent=true)).
- @Chrisr reassured a concerned site admin that scheduled maintenance was underway and pointed to [status.discourse.org](https://status.discourse.org) for updates ([post](https://meta.discourse.org/t/site-stuck-in-read-only-mode/413454/2?silent=true)).
- @NateDhaliwal linked to a maintenance notice to explain a read-only state ([post](https://meta.discourse.org/t/urgent-read-only-mode/413517/2?silent=true)) and also contributed to the “sudo mode” feature discussion ([post](https://meta.discourse.org/t/regular-mode-for-admins-and-moderators-e-g-something-like-sudo/211617/48?silent=true)).
- @Tgxworld confirmed that the sudden read-only mode was actually planned maintenance and apologised for the inconvenience ([post](https://meta.discourse.org/t/urgent-read-only-mode/413517/3?silent=true)).
- @Burke started a detailed discussion on webhook payloads, pushing back on suggestions to use an admin key due to least-privilege concerns ([post](https://meta.discourse.org/t/could-usernames-be-included-in-user-badge-webhook-payload/413448/1?silent=true), [follow-up](https://meta.discourse.org/t/could-usernames-be-included-in-user-badge-webhook-payload/413448/7?silent=true)).
- @Nathank shared his view on a low-friction admin “regular mode” ([post](https://meta.discourse.org/t/regular-mode-for-admins-and-moderators-e-g-something-like-sudo/211617/47?silent=true)) and later requested a fix for the broken upcoming-events block in the demo theme ([post](https://meta.discourse.org/t/skills-for-authoring-themes-and-blocks/401629/24?silent=true)).
- @Lilly verified that the Twitter embed component works as expected, providing a screenshot for reference ([post](https://meta.discourse.org/t/twitter-native-embed/261792/121?silent=true)).
- @Falco offered a workaround for the voice room stereo-mic issue, suggesting a lower audio quality setting ([post](https://meta.discourse.org/t/voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse/411337/72?silent=true)).

* * *

From invisible red lines to stereo mic mishaps, it was a day of keen observations and helpful fixes. **May your forums stay out of read-only mode and your red lines always be visible!**

[上一頁](https://meta.discourse.org/t/daily-summary-5am-utc/291851.md?page=37)
