🛡️ Android: Classified conversations

[nickvergessen]

• Overview issue in 🛡️ Overview: Classified conversations spreed#18679

Classified conversations

Backend support for "classified" conversations is implemented server-side. The web frontend and mobile clients need to hide/adapt settings and options. A conversation is classified when TalkRoom.attributes & 4 (the CLASSIFIED bit) is set. Gate all of this behind the classified-conversations capability.

Detection

• Detect classified conversations via TalkRoom.attributes & 4 (CLASSIFIED bit); only apply this behavior when the classified-conversations capability is present.

Hide / disable settings & actions in classified conversations

• Hide "Message forwarding" action (forward-to-conversation / forward-to-note-to-self) on all messages. (frontend-only, no backend block)
• Hide "Reply privately" action on messages. (backend returns 403, but hide the action)
• Render image/file messages as blurhash placeholder only; do not auto-load the inline preview — clicking still opens the preview/viewer. (frontend-only)
• Hide/lock the "Sensitive conversation" toggle and show it as permanently on (backend rejects un-marking with 400). (forced sensitive for everyone)
• Hide SIP dial-in/out settings (backend rejects enabling with 400).
• Hide "Allow guests" / make-conversation-public / share-link options (backend blocks public type).
• Hide federation and email options
• Hide breakout rooms feature
• Hide "Open conversation" (listable/joinable) settings (backend rejects with 400).
• Hide the call-recording start button / recording-consent option (backend rejects with 400).
• Hide the "Start live transcription" action (backend rejects with 400 classified).
• Hide the live-translation / target-language picker (backend rejects with 400 classified).
• Hide the "Download participants list" action (backend returns 403).
• Hide the "Summarize chat" / unread-summary action (backend rejects with 400 classified).
• Hide Bots and Matterbridge settings (backend rejects with 400 classified).
• Add a "🛡️ Classified conversation" (Shield icon + text) red button in the top bar similar to the "Meeting 16. July" meeting hint. *In the planning meeting it was said it's okay if this button is also blink-fading similar to the recording icon to create awareness.

Auto-delete-after-call ("keep" action)

• Add OBJECT_TYPE_CLASSIFIED ('classified') to the hasRetentionPeriod() check so the "Keep conversation" shortcut shows on the call_ended system message in classified conversations.
• Wire that shortcut to the existing DELETE /room/{token}/object (unbind) call — it flips the room to classified_persist and stops auto-deletion permanently.
• Treat objectType === 'classified' as "pending auto-deletion" and 'classified_persist' as "kept" for any retention/expiry UI hints (optional: surface the config.conversations.retention-classified seconds value).

[thirumani-vihaan]

hi @nickvergessen.

reading through the spec, it looks like it requires wiring up a central check for the CLASSIFIED bitmask (TalkRoom.attributes & 4) alongside the classified-conversations capability, and then propagating that state down to hide or disable the various menu actions and settings toggles (sip, bots, recording, federation, etc) across the ui.

i can also handle adding the blinking red shield indicator to the top bar and wiring up the classified_persist unbind call for the auto-delete system message.

if no one else is currently working on this, could i take it on? i would really appreciate the opportunity to tackle it.

[nickvergessen]

@rapterjet2004 @mahibi fine for you?

[rapterjet2004]

Hey thirumani, that sounds great! Just checking in on the status of this. I'm here, if you have any questions

[rapterjet2004]

Hey @thirumani-vihaan what's the status of your fix?