Your NameandClaude Sonnet 5
4a30cfa6b3
再次派7个agent覆盖全部11章，验证第三轮修复+找新问题。本次委托agent专门交叉核对 上一轮每一项修复是否真的生效，多数确认有效，但抓出2处"看似修好、实则有旁路"的情况 和若干新问题。 **编辑消息+拖放文件仍可静默覆盖被编辑消息（上一轮修复的完整旁路，Ch3-4 agent发现）** 上一轮给`onAttachFile`/`onAttachImage`/`onAttachAudio`三个prop加了editingMessage门禁， 但`isDragEnabled()`（messages-view.jsx）没有检查这个状态——拖放文件到聊天窗口走的是 `handleFileDrop`直接调用`handleAttachImageOrVideo`/`handleAttachFile`类方法本身，完全 绕开了被置null的props。编辑态下不点"+"号、直接把文件拖进聊天窗口，依然会静默替换掉 被编辑消息的原文。已给`isDragEnabled()`补上同款判断，这是`handleDrop`和渲染层拖放提示 两处调用的唯一门禁函数，一次性堵住。 同一个agent还发现编辑态下点击"回复"另一条消息会静默放弃当前编辑（`handlePickReply` 覆盖`this.state.reply`但不清`contentToEdit`，发送时值走了`reply`分支而不是`editing` 分支，编辑框里的原文被当成对另一条消息的新回复发出去，原消息未被修改）——已在 `handleShowMessageContextMenu`里比照`menu_item_edit`的年龄过滤模式，编辑态下直接不 提供"回复"这个菜单项。 **实名认证驳回提醒的dismissKey修复上一轮实际没生效（Ch1-2 agent发现，已重新修复）** 上一轮把dismissKey从纯status改成"submission_id或status"，但live验证发现 `bootstrap.security.realname`这个数据源根本不包含submission_id字段（后端serveIMBootstrap 的实现只有status/required/allow_skip/remind_after四个硬编码字段）——所以这个修复在 真实环境下永远退化回status，等于没有变化，两次独立驳回依然会互相误压制提醒。这次改为 额外调用专用的`GET /security/realname`接口（该接口的实现确实会返回submission_id）， 用它的数据驱动dismissKey和提醒触发条件，bootstrap的字段只保留用于remind_after/ allow_skip这些它独有的字段。已用真实账号验证dismissKey现在正确从这个新数据源生成。 **呼叫面板未卸载防护补全到call-panel.jsx（Ch8 agent发现，同类问题上一轮只修了 audio-recorder.jsx）** `start()`/`unmuteVideo()`/`handleSwitchCameraClick()`三处的getUserMedia/ enumerateDevices异步链，结尾都会touch `this.localRef.current`/`this.state.localStream`， 但都没检查组件是否已经卸载——权限弹窗未决出结果时通话结束（呼出超时/收到挂断/对方 主动挂断)，这些promise resolve后会在死实例上抛TypeError，被各自的catch吞掉后又会展示 一句过期的原始英文报错。三处都补了`this._unmounted`检查，拿到的媒体流/轨道直接停止 而不是继续使用。 **其余修复**：`call-message.jsx`补上和`call-status.jsx`一致的"进行中"状态文案（原来 通话进行中且消息还没有最终时长时显示"0:00"而不是"进行中"，已用真实渲染验证过两个 组件行为不一致）；`tinode-web.jsx`的`handleCallClose`补上重置`callSeq`（避免跨通话 残留旧值）+ 更新`armCallRingTimeout`注释准确描述它是后端30秒建立超时的二级兜底而非 主要防线（后端`call_establishment_timeout`默认30秒，已有独立机制处理"直接不接"的 常见场景）；`REASON_MESSAGES`补充`API_KEY_REQUIRED`/`METHOD_NOT_ALLOWED`（此前记录过 一次真实的部署期API Key配置漂移事故，属于这两个reason的真实触发场景）； `message-center-view.jsx`的`NOTIFICATION_TEXT`补充风险确认"取消"结果的文案（发消息 前风险提示点"取消发送"会产生这个系统通知，此前只收录了"继续"）；会话列表"置顶"从 只变背景色改为真正排到列表最前（原来只有CSS着色，没有任何排序逻辑，已用真实群聊 置顶验证过排序生效且系统消息/文件助手两个固定入口仍保持在最前）；好友聊天设置页 置顶/免打扰开关在初始GET未完成前禁用（避免`version:null`打到后端400）； `content-library-view.jsx`的`DownloadPage`修复带外附件下载使用未做域名归一化的裸 相对路径（生产环境webapp和文件域名跨域时会必现下载失败，已拆出`resolveFileUrl` 辅助函数只做URL拼装不做预先fetch，跟`getFileUrl`的实际下载区分开）； `security-support-view.jsx`的意见反馈分类配置改用`useCachedData`获得重试能力（原来 独立实现的边车缓存逻辑没享受到本轮`use-cached-data.js`的重试修复）。 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Tinode Web
Briefing
Single-page web chat application for Tinode. The app is built on React. The Tinode javascript SDK has no external dependencies. Overall, it's a lot like open source WhatsApp or Telegram web apps.
Although the app is generally usable, keep in mind that this is work in progress. Some bugs probably exist, some features are missing. The app was tested in the latest Chrome & Firefox only. NPM package is available.
Try possibly newer or older version live at https://sandbox.tinode.co/.
For demo access and other instructions see here.
Installing and running
This is NOT a standalone app, this is just a frontend, a client. It requires a backend. See installation instructions. See instructions for enabling push notifications.
Getting support
- Read client-side and server-side API documentation.
- For support, general questions, discussions post to https://groups.google.com/d/forum/tinode.
- For bugs and feature requests open an issue.
- Use https://tinode.co/contact for commercial inquiries.
Helping out
- If you appreciate our work, please help spread the word! Sharing on Reddit, HN, and other communities helps more than you think.
- Consider buying paid support: https://tinode.co/support.html
- If you are a software developer, send us your pull requests with bug fixes and new features.
- If you use the app and discover bugs or missing features, let us know by filing bug reports and feature requests. Vote for existing feature requests you find most valuable.
- If you speak a language other than English, translate the apps into your language. You may also review and improve existing translations.
- If you are a UI/UX expert, help us polish the app UI.
- Use it: install it for your colleagues or friends at work or at home.
Internationalization
The app is fully internationalized using React-Intl. The UI language is selected automatically from the language specified by the browser. A specific language can be forced by adding #?hl=XX parameter to the URL when starting the app, e.g. https://web.tinode.co/#?hl=fr.
The app is currently available in the following languages:
- English - default
- Arabic
- Chinese simplified
- Chinese traditional
- French
- German
- Italian
- Korean
- Romanian
- Russian
- Spanish
- Thai
- Ukrainian
- Vietnamese
More translations are welcome. See instructions.
Not done yet
- End-to-End encryption.
- Emoji support is weak.
- Mentions, hashtags.
- Previews not generated for links and docs.
- Location and contact sharing.
- Recording video messages.
Other
- Demo avatars and some other graphics are from https://www.pexels.com/ under CC0 license.
- Background patterns from http://subtlepatterns.com/, commercial and non-commercial use allowed with attribution.
- Fonts and icons from Google under license which permits commercial and non-commercial use.
- Push notifications built with https://firebase.google.com/.
Responsive design
Desktop screenshot
Mobile screenshots
