Release
Velta 1.4.79 brings Velta Beam to groups
· 3 min read
Velta Beam works in group chats now, the Accounts menu hosts Profile management, and a person’s profile no longer lists everyone’s files.
Version 1.4.79 ships on a new core (2.65.0) and pays most of its attention to how files and profiles behave.
Velta Beam reaches groups
The attach menu’s Velta Beam used to be a two-device affair. In a group chat it now works the way a share should: everyone who opens Beam can receive the file, and everyone who already has it helps pass it on. Someone who opens Beam after the sender left still downloads the file from any holder — as long as one holder keeps Beam open, the file keeps flowing, device to device.
The item is simply called Velta Beam now (it was “Send directly”), and the receiver count has moved onto the file card, right next to its list, where the receivers actually are.
Accounts, with Profile management inside
The drawer’s “Switch account” button is now Accounts and is always there — even when this device has a single profile, because the popover now holds Profile management… right under the profile list. Add a profile, set up a second device, export a backup, delete a profile: one tap from the top of the drawer. The Profile management row in the settings list stays, so the same modal opens from two doors.
A person’s profile shows their files, not everyone’s
Opening a member’s profile from a group used to list Apps, Photos, Videos, Audio and Files from all chats on your account. Those sections now show only the media you two share in your 1:1 chat — and stay out of the way when no such chat exists yet.
Also in this release
- Android: uncaptioned photos and videos now notify in the background too, not only text.
- Android: a flaky network can no longer pause the message connection at the wrong moment.
- Links in the in-app browser hand off properly: mailto: opens your mail app, tel: dials, store links open the store.
Under the hood: the vendored core moved to chatmail 2.65.0 with all 25 local patches carrying over unchanged — no database migration, nothing to do on your side. A retired local service fallback is gone, and shell commands for picked files are now gated on the Rust side (security audit V-07).