RuiTalk TEST

RuiTalk

Подготавливаем рабочее пространство…

Вход в RuiTalk

Введите e-mail, чтобы продолжить.

https://test-talk.ruiru.ru

v2.0.480

E-mail

Вход в RuiTalk

Введите пароль для продолжения.

E-mail

—

Пароль

Регистрация временно недоступна

Мы сможем продолжить регистрацию после запуска подтверждения почты.

Код пока не отправляется.

RuiTalk TEST ENV

https://test-talk.ruiru.ru

Тестовая среда — безопасно проверяйте новые сборки. Preview-вход не использует реальный сервер.

Диалог

Выберете чат для общения...

Сообщение

Calls

Open the bounded calls destination from the shell row.

Open Calls from the shell destination row.

Contacts

Open Contacts from the shell destination row.

Open Contacts from the shell destination row.

Secondary surfaces

Search, profile, groups and settings share one bounded return stack.

Open a secondary surface from the launcher row.

Call session

Open a bounded call from a profile quick action or from Calls.

Open a bounded call from a profile quick action or from Calls.

Manage folders

Folder management stays inside Chats as a bounded secondary surface.

Open manage folders from the chat shell.

Bounded host-side Step 8 media flow

Kind File name Size (MB)

Caption Pause once after chunk 1 for bounded sender resume After chunk 1, lose upload-session access before bounded resume can continue For video only: fail worker processing on the same bound message once For video only: let bind succeed, then block worker processing on the same canonical message After one processing failure, let the bounded retry lose access on the same canonical message Fail finalize once after all chunks and require one bounded retry on the same uploaded bytes Fail bind once after finalize and require one bounded retry on the same accepted upload Fail bind once, then lose retry access before canonical message materialization After finalize, lose bind access and block canonical message materialization on the accepted upload Let bind succeed, then lose media access after one bounded ready/open window on the canonical message After one processing failure, let replace-on-same-message reach open once and then lose access