- Ya
- 10 Agosti 2026, 21:04 UTC
- Mwandishi
- kamo
- Ahadi ya
- 527e0bf
The per-tab sessionStorage flag was not a record of anything. Signing in on a second device replayed every conversation the first had already popped, and clearing storage lost the fact entirely — while a conversation deliberately left unread re-opened on every single load, because "unread" alone never stops being true. The component now asks the platform which conversations to raise and acknowledges each one it opens, against **************** A conversation is raised once, and again only when something newer than that arrives in it. Only what is actually opened is acknowledged, so anything beyond the burst cap is offered again next time rather than silently dropped, and a failed read writes nothing at all — the next sign-in simply tries again instead of the feature going quiet for the rest of the session.