PRODUCT RELEASE: Réunion 3.7.11 on iOS. - Various updates for the next server release - Lay out three Pulse attachments like the web client - Show Vivid call buttons only to users granted Vivid - Clear Pulse notifications read on another device - Keep Cancel and Done visible while searching room members - Show the live server version on the Server screen - Pulse: return the composer to the bottom once the keyboard is hidden - Pulse: show a video poster before the file is downloaded - Pulse: pin chats and rooms, shared with the web client - DataRoom - Module tab items

PRODUCT RELEASE: Reunion Web 3.1.112 Pulse - New: Pulse now caches your rooms and messages so they load faster. It is on by default for testing. You can turn it off in Settings > Experimental > Pulse Cache. New: Videos now get a preview thumbnail. When you upload a video, a thumbnail is created and shown as its preview. This works only for new videos uploaded from the web for now, and is coming to iOS and Android. New: Pinned rooms are now saved to the server. Improved: A new room is selected automatically after you create it. Improved: Group creation is easier to use. Improved: Attachments are shown in a new way. You can now right-click an image to download it. Fixed: Large attachments now upload correctly. Fixed: Downloaded attachments keep their original filenames instead of being renamed. EasyCrypt - New: Press Cmd/Ctrl + Enter to send a message. Fixed: Pressing Tab in the subject field now moves to the message body. Fixed: Scrolling now works on long messages. Fixed: The message reply icon is now correct. Data Rooms (Preview) New: An early preview of the Data Rooms module. Turn it on in Settings > Experimental > Data Rooms. General

Most compliance failures are classification failures in disguise. Access control, DLP, encryption, and audit logs only work if the system knows the sensitivity of the data it’s looking at. When a regulated file leaves as a normal attachment, you lose the audit trail, the jurisdiction, and the ability to prove control. Regulators increasingly treat incomplete classification as systemic non-compliance, not a documentation gap. Labeling is the quiet prerequisite. Get it wrong and the expensive controls become theater.

DLP after the policy is live still misses the attachment that was forwarded before the label existed; classification has to travel with the file, not only with the tenant rule.

A cowork run that folds an email update into the plan also folds whatever attachment was on that thread, unless classification blocked that class before the agent could read it.

A statute can permit broader sharing and still leave the attachment unclassified; the integrity problem is which sensitive set was allowed to leave Japanese control, not only who was told to be careful.

The HIPAA problem starts one step earlier than the MCP call: the snippet was never classified, so the patient shaped test data was already eligible to leave the editor.

Inventory finds the shadow app after the paste; the missing control is classification at the moment the email or file is copied, before Purview ever sees the prompt.

Connecting mail is the sharper risk than the card: an agent that can read the inbox can also read the attachment that was never meant to leave the books and records boundary.

Adequacy is a transfer label, not a control on the chart or referral that already left as an attachment; if Brussels is asking the question, providers still need a class rule for what may cross and what must stay.

Model class is only half the leak path: the attachments and prompts already sitting in mail and chat are what get copied when an incident lands, so classification has to happen before that send.

Individual caution does not classify a medical or client file before it leaves the mailbox, and a stolen attachment still sits under the sender’s jurisdiction no matter how careful the recipient was.

That is a real governance and infrastructure problem.

Benefits and risks are not evenly distributed, and it is legitimate to ask whether decision-makers are insulated from consequences that fall on users, workers, or the public.

Interesting.

Humans need progressive responsibility, feedback, and the chance to build judgment; models need data, evaluation, and constraint.

Exactly.

AI-assisted reverse engineering and reimplementation are getting good enough to threaten specific closed products, and an open path into Adobe-format workflows is a real shift in leverage. That part is hard to dismiss.

AI-assisted reverse engineering clearly lowers the cost of inspecting closed binaries, and high-profile rebuilds or analyses will keep embarrassing vendors who bury tracking in opaque clients. That shifts leverage toward people who want to verify behavior rather than take “trust us” on faith.