Discourse Chat通知的快速回复

Falco · 2022 年11 月 12 日 17:44

从今天开始，Discourse Chat 通知允许用户在通知本身中进行内联回复

此 UI 在每个操作系统上都不同，因为它会集成到原生通知系统中。

Smartwatch Android Wear OS

Android

Windows

一切顺利的话，此功能接下来的可能步骤包括：

添加对内联回复的支持
将内联回复作为“回复”发送到它们所回复的消息
添加对主题/帖子的内联回复支持
处理发送内联回复时出现的错误，无论是网络错误还是业务逻辑错误。
回复按钮和占位符的国际化（i18n）

jordan-violet · 2022 年11 月 12 日 17:44

这是一个很棒的补充。当我想到“哇，一个动态示例图片显示了我的用户名”时，我感到非常困惑，然后才意识到这只是我用户名的截图。

我喜欢这个聊天功能增长的速度——我迫不及待地想在合适的时候将其添加到我们的社区。尽管我喜欢 Discord，但从我们的业务用例来看，我真的不希望再有一个平台来管理和分散我的用户。

一个不错的功能是能够选择一条或多条聊天消息，并将它们拆分成一个主题。

darkpixlz · 2022 年11 月 12 日 22:45

iOS 支持何时会推出？我仍然需要第三方应用程序才能获得带有内容的即时推送通知。

Falco · 2022 年11 月 12 日 23:02

不知道，那是苹果公司的事。我们是根据开放的 Web 标准实现的，它适用于实现该规范的每个操作系统，例如 Windows、Android、Chrome OS 等。人们可以希望苹果在 2023 年实现 WebPush 时能正确实现，但我们无能为力，只能希望。

Falco · 2026 年5 月 11 日 20:12

这个问题之前存在了一段时间，我现在以更稳健的方式重新添加了对它的支持。

github.com/discourse/discourse

FEATURE: Restore web push quick reply for chat messages (#39614)

main ← chat-push-quick-reply

merged 03:36PM - 29 Apr 26 UTC

xfalcox

+401 -98

**Previously**, the "Reply" action on chat web push notifications was silently b…roken — the service worker's chat URL regex stopped matching when chat routes moved to `/chat/c/:slug/:id`, and the chat-specific code lived in core with no thread support, URL encoding, or error handling. **In this update**, generalize the core service worker into a plugin-extensible action registry, move chat reply handling into the chat plugin with proper thread/encoding/fallback support, and convert single-emoji replies into reactions on the source message (falling back to a regular message post on any failure). ## Architecture Core (`app/views/static/service-worker.js.erb`) now exposes: ```js self.registerNotificationActionHandler(action, handler); ``` Push payloads can carry `actions` (Web Notifications API format) and `action_data` (an arbitrary object surfaced to the handler at `event.notification.data.actionData`). The click handler dispatches by `event.action` name and falls back to the existing focus-or-open behavior when no handler matches or a handler throws. `PushNotificationPusher` forwards `actions` / `action_data` when present. The chat plugin owns its own service worker (`plugins/chat/assets/javascripts/service-worker.js`), registered via `register_service_worker`. It registers a `chat-reply` handler that: 1. Fetches a CSRF token. 2. If the reply is a single emoji grapheme (detected via `Intl.Segmenter`, with a `\p{Extended_Pictographic}` regex fallback), `PUT`s to `/chat/:channel_id/react/:message_id`. 3. Otherwise — or if the reaction request fails — `POST`s to `/chat/:channel_id` with proper `URLSearchParams` encoding and the source `thread_id` if present. 4. If everything fails, opens the channel so the user can retype. `Chat::Notifier.push_notification_reply_action(chat_message, user)` builds the payload in the user's locale with `channel_id`, `message_id`, and optional `thread_id`. `Chat::MessageReactor#react!` resolves raw Unicode via `Emoji.unicode_replacements[emoji] || emoji` before validation, so smartwatch quick-reply chips (which send raw Unicode like `👍🏽` or ZWJ sequences) just work. Existing shortcode callers are unaffected. ## Why this matters Smartwatch notification UIs expose a single "reply" affordance with canned chips that include short text and emoji. The user can't choose between "send as message" and "react"; they tap a chip and a string comes through. Treating a single-grapheme pictographic reply as a reaction matches user intent on the watch UX without any new product surface. ## Test plan - [ ] On a chat-enabled site, subscribe to web push notifications. - [ ] Have another user post a message that mentions you, or a watched channel message. - [ ] On the resulting OS notification, confirm a "Reply" action button appears. - [ ] Type a text reply and submit — verify it posts as a message in the right channel/thread. - [ ] Submit a single emoji (e.g. 👍 or 👍🏽 with skin tone) — verify it lands as a reaction on the source message instead of posting a message. - [ ] Submit a ZWJ sequence (e.g. 👨‍👩‍👧) — verify it lands as a reaction (or falls back to message post if not in the emoji DB). - [ ] Sign out / let session expire and submit a reply — verify the channel opens as a fallback rather than silently failing. - [ ] Watch via Wear OS / watchOS quick-reply chips and confirm the same behavior end-to-end.

现在，我们还会将仅包含单个表情符号的回复作为反应进行捕获，并支持聊天线程！。

NateDhaliwal · 2026 年5 月 11 日 22:10

哇！这太酷了！有计划为话题也做同样的事情吗？

话题		回复	浏览量
Rich Notifications support for DiscourseHub Feature discourse-hub	10	1447	2023 年2 月 18 日
Bug with chat notifications not showing up Bug chat , notifications	26	864	2025 年11 月 25 日
Discourse Mobile: chat improvements, notifications, widget Feature mobile , chat	15	1366	2023 年11 月 20 日
Speccing out a full page chat plugin Development	29	8031	2022 年8 月 21 日
Embed Discourse in a native app? Development	36	5376	2024 年4 月 3 日

Discourse Chat通知的快速回复

Smartwatch Android Wear OS

Android

Windows

相关话题