You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ℹ️ 已知:Android 版是測試版(debug 簽章,能接 USB 偵錯的人可讀取記憶體,請勿用它處理你真正在意的對話);桌面版未經程式碼簽章,安裝時 Windows SmartScreen 會跳警告。和還沒更新的舊版之間,舊版那一側仍可能出現信令錯誤。
What's new (English)
🔧 Fix: two people on different relay anchors couldn't receive each other's messages. Sign-up picks an anchor automatically, so you and a friend may land on different ones; previously messages always went to your own anchor and never reached them. Messages now go to the anchor in the other person's share string; with only an npub, a copy goes to each anchor until they reply. Online status is fixed the same way. The sender needs this version for it to take effect.
🔧 Fix: after a reload or app start, others took minutes to see you online. Presence beacons, direct-connection signaling and typing indicators sent before the relay connection finished authenticating were rejected and lost; they are now resent once authentication completes.
🔧 Fix: "⚠️ Signaling failed" in the chat and no direct connection when both people open the conversation at the same time (or one after the other). One side now yields, and a stuck negotiation restarts on a fresh connection. A failed direct connection already falls back to the relay, so these errors are no longer shown in the chat.
🔧 Messages explicitly rejected by the recipient's relay are marked failed right away (red retry) instead of being treated as sent after 30 seconds; when a relay reports it is full, the message is sent to another relay.
🔒 Cryptography libraries upgraded (@noble/@Scure 2.4.0): signing is now guaranteed constant-time. Message formats are unchanged and old and new versions interoperate; passcode locks and chat history created with older versions still unlock as before.
ℹ️ Known: the Android build is a test build (debug-signed; anyone with USB debugging can read its memory — don't use it for conversations you really care about); the desktop build is not code-signed, so Windows SmartScreen will warn on install. With older versions that haven't updated, the older side may still show signaling errors.