Skip to content

WebCaller v0.17.1 — Faster sharing, 200 MB files and guided Docker

Choose a tag to compare

@adlererik adlererik released this 19 Oct 04:02
· 35 commits to main since this release

WebCaller is a Signal-like WebRTC phone for Android, iPhone and desktop browsers, with end-to-end encrypted conversations, adaptive calls and simple invitations. No SIM or phone number is required.

This release makes sharing during calls much faster on healthy links, supports files up to 200 MiB (shown as 200 MB in the interface), and provides source downloads and a small, guided prebuilt Docker bundle.

Faster sharing, with voice first

  • Replace the old sequential 4 KiB in-call bottleneck with up to four adaptive encrypted-chunk workers. Probe the actual file connection rather than treating every unknown network as a slow cellular link.
  • Allow file payload rates up to 24 Mbps on healthy links, with a 2 Mbps limit when the browser explicitly reports cellular or Save-Data. These are ceilings, not guaranteed speeds; browsers do not always report their connection type.
  • Pause and abort file requests when call statistics are weak, stale or reconnecting; resume cautiously when fresh healthy samples return. Video temporarily yields bandwidth during sharing. Voice remains the priority, but no application can guarantee intelligible audio on an unusable connection.
  • Show transfer progress and preserve complete encrypted media caches when reopening chats. Incremental caching avoids an extra full ciphertext copy; browser storage limits and memory needed to display very large media still apply.
  • Support 200 MiB files without changing the existing AES-256-GCM chunk format. Fresh reservation defaults are 1 GiB per sender and 4 GiB overall; existing explicit lower quotas are preserved.

Also included

  • Updated Vodozemac 0.11.1 browser binding, stricter invalid-Curve25519 rejection and compatibility checks for previous identities, sessions, unread messages, history and call verification.
  • Reproducible browser-crypto packaging: remove optional compiler-description metadata while keeping all executable/data sections identical and retaining exact loader integrity checks.
  • Prefer confirmed ntfy call alerts to avoid duplicate browser notifications, with a browser-push fallback. Existing normal Web Push and optional self-hosted ntfy remain available. A website cannot force a locked phone to override OS restrictions, Silent mode or Focus.
  • Calling codes, easier invitations, modern home and Settings screens, contact renaming, light/dark themes, and a professional handset icon.
  • Off and custom disappearing-message timers through four weeks. New timed messages expire independently: the sender timer begins on sending, the recipient timer on first viewing. Unread encrypted copies may therefore outlive the sender's copy.
  • Preserve the full camera frame across portrait, landscape and desktop calls.
  • Signal-like text/media bubbles, replies, reactions, own-message editing, synchronized deletion, voice notes, camera/files/location sharing and inline/full-screen playback. Adaptive Opus voice and negotiated hardware-aware video preferences remain available.

Security, explained plainly

New messages, file-key manifests and call signaling use Olm Double Ratchet, X25519, AES-256-CBC, HMAC-SHA-256 and HKDF-SHA-256. Signed identities/envelopes use ECDSA P-256. Attachments and local wrapped records use AES-256-GCM. Live media uses the browser's DTLS-SRTP; it is not individually Double-Ratcheted. Optional four-word per-call SAS binds the accepted media connection: read all four words to each other. Skipping the comparison does not interrupt the call, but provides no human SAS verification.

The README and security guides explain forward secrecy, retained-history limits, identity pins, legacy traffic, metadata and the comparison with Signal. This remains classical cryptography, not a post-quantum protocol. Trusted browser code and authenticated contact keys are essential. The website operator controls delivered JavaScript, compromised phones expose plaintext, and this project has not had an independent security audit.

Choose your installation

Simplest for a new Linux server: download WebCaller-Docker-v0.17.1.tar.gz (or ZIP), check SHA256SUMS.txt, extract it, then follow its README. Install Docker Engine and Compose, run ./webcaller setup, ./webcaller start, then ./webcaller qr. The wizard creates fresh private secrets and the first-phone QR. Public amd64/arm64 images are pulled automatically and pinned by digest. The bundle offers optional TURN, ntfy, and HTTPS or a Cloudflare connector. You still need your own domain and reachable HTTPS/TURN configuration; Docker cannot bypass CGNAT or phone notification rules.

Source/native users: download WebCaller-v0.17.1.tar.gz or ZIP. Native Node.js/systemd and source-built Docker are both documented. Existing native installations do not need to migrate to Docker.

Upgrading and verification

Read the installation-specific update instructions first. Preserve private configuration, data volumes, browser storage, identities and keys. Refresh both phones after updating. Do not run first-time setup again, clear site storage or delete a Home Screen app to perform an upgrade. Existing lower file quotas remain in force until the operator deliberately changes them. New timers require current clients. A service restart may interrupt an active call.

Verification includes 248 passing public-source tests, complete encrypted 200 MiB upload/download with every plaintext byte verified, deletion cleanup, aborted-request recovery, legacy crypto/history compatibility, and two-peer browser sharing/cache/pause-resume checks during generated-media calls. Local-loopback timing is not an internet-speed benchmark. CI builds and exercises disposable Docker stacks on native amd64 and arm64 runners. Physical-phone memory, audible quality and difficult real mobile networks still need device testing.

Only audited public source and generic deployment templates are distributed. No live server configuration, credentials, account databases, browser profiles or private deployment backups are included. Checksums cover all four release archives; Docker bundle project images are additionally pinned to their tested release manifest digests.