60s OTK TTL for meet windows, independent chat/email invites that don't block on backend

Fixkamo-internal
Ya
29 Machi 2026, 16:17 UTC
Mwandishi
kamo
Ahadi ya
bf7286d

ROOT CAUSE: The OTK had a 10-second TTL. By the time the kamo-meet page loaded all its assets and branding/overrides.js ran to validate the OTK, it had already expired in Redis → 401 → no session → no name → no JWT → 'Waiting for moderator'. Fixes: - Meet OTKs now get 60s TTL via ?purpose=meet parameter - Chat invites run independently (not after backend meeting creation) - Email invites run independently - Backend meeting record creation is fire-and-forget (doesn't block)

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei