Your NameandClaude Sonnet 5
4bf4e75cac
用户实测报告：systest01打开着与systest02的会话，切到别的标签页后，systest02
发消息过来，systest01这边的标签页标题完全没反应。追查后发现根因比表面看到的
更深——这不是标题栏本身的bug，是更底层的已读状态被静默污染了。
读tinode-sdk源码确认：TopicMe自己的_routePres在处理服务端推给"me"话题的
`{pres what:"msg"}`通知时（这本来是让未在查看的会话也能收到未读更新的机制），
调用`cont._updateReceived(pres.seq, pres.act)`，只要`act`是假值或者等于自己，
就会无条件把`read`设成`seq`——也就是直接标记成已读。而一个只是保持"打开"状态
的会话（ConversationView挂载着、话题处于订阅状态），哪怕标签页在后台完全没人
看，一样会收到这条推送，被自动标记已读——跟标签页是否可见毫无关系。之前只
在ConversationView自己的显式noteRead()调用上做了可见性判断，根本拦不住这条
更底层、完全独立的SDK自身机制。
修复：在topics.ts里新增一套独立于SDK自身read/unread字段的"真正已读"记录
（markConfirmedRead/confirmedReadSeq），只在会话真正被看到时（打开且标签页
可见）才推进；me.onPres处理`{pres what:"msg"}`时，如果受影响的会话不是当前
正在被查看的那个，就用这份独立记录把SDK刚自动标记的已读状态纠正回去。
openConversation()打开会话时会拿当前seq给这份记录打个初始基准，但同样加了
可见性判断——直接刷新/深链到一个标签页本身就在后台的会话这种边界情况下，
不能假设"打开=看过"。activeConversationTopic的追踪从push.ts挪到了topics.ts
（两边都要用，且topics.ts不能反向依赖push.ts）。
实机验证（systest04/systest05全新账号对，因为systest01/systest02当时正被
用户自己在真实浏览器里同时测试，避免互相顶号干扰）：会话保持打开、标签页
确认处于hidden状态时，对方发消息——未读数正确从0变成1，标题栏数字正确跟着
增加；随后模拟标签页重新变为可见——未读数正确清零、标题恢复正常，走完了
用户报告的完整场景闭环。
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
