re:call

Источник: dev/fera/re-call/README.md (read-only; сгенерировано scripts/sync-docs.mjs)

re:call

The future pure-Rust reimplementation of Telegram’s calling stack — voice/video calls and streams, from scratch, no C++.

Reserved, not started. This repo exists to hold the name and the intent; work begins in a later major version of Fera, after the tgcalls-based calling line (rstgcalls) has proven the calling UX end to end.

Why “re:call”

The re: prefix is the project’s naming pattern for rewrites/redo — a from-scratch reimplementation of something that first shipped as bindings. The name was reserved in the design corpus (NAMING-UX §1) long before this repo existed, deliberately kept separate from rstgcalls (which honestly describes what it is: Rust bindings to tgcalls).

What will live here

• A pure-Rust WebRTC-compatible media/transport stack targeting Telegram’s calling protocol.
• Signaling over MTProto via grmrs — the same protocol layer the rest of Fera uses.
• The same nylon-ring module slot rstgcalls occupies today — a swap, not a new integration point (ADR-018’s deferred goal).

Why not now

The calling stack is not a documented, stable public protocol. Reimplementing it before the bindings-based line has real-world usage data means flying blind on undocumented protocol behavior — the exact risk ADR-018 was written to avoid.

Status

Reserved placeholder. No code, no timeline commitment — the Fera release line decides when this becomes active.

Team: recall — repo access is granted through the team.

License

TBD — decided before the first public release.