Nishi FamilyCompare › Messaging & Comms Platform

Nishi vs the Field

Messaging & Comms Platform — mechanically measured, liar-killed, sovereign.

Nishi live comms (nishifamily.com/video + relay + sovereign codec + E2EE) vs Telegram and WhatsApp and Signal and Discord

How this is scored. Every Nishi cell is measured: the generator reads the real organ source on disk and requires the implementing symbol to exist (no self-grading). Competitor cells record documented capability presence. Best=leads this axis, Yes=present, Part=partial, No=absent. This is capability presence, not depth or scale: the majors lead on index size and neural ranking. Nishi's genuine exceeds are the sovereignty / neutrality / determinism axes.

Feature matrix

CapabilityNishiTelegramWhatsAppSignalDiscordNotes
Real-time group chatYesBestYesYesYesIn-room chat over the sovereign relay; Telegram chat UX is the reference
Group video callsYesYesYesYesBestOUR OWN codec end to end; Discord group calls are Best-in-class UX; others license/embed WebRTC
Voice (lossless LPC audio)YesYesYesYesYesSovereign lossless voice path; majors use Opus
E2EE for calls AND chatYesPartYesBestNoChaCha20 relay-blind on video+audio+chat; Signal is the E2EE reference; Telegram E2EE is opt-in secret chats; Discord has none
Video messages (circles)YesYesYesYesNoTelegram video messages equivalent, self-hosted
Screen shareYesYesYesYesBestDiscord screen share is the reference
Private keyed rooms (invite links)YesYesYesYesYessha256 token wall = private invite links
SFU + simulcast + last-NYesYesYesYesBestPer-receiver layer verdicts + seq rewrite + dynacast-class suspension -- Discord-class infra, ours sovereign
Relay cascade (multi-relay scale)YesBestBestYesBestOcto-class split-horizon inter-relay; majors run planetary fleets (Best)
Media FEC resilienceYesYesYesYesYesReed-Solomon 8-of-10 on frames
Message history / offline deliveryNoBestYesYesBestTHE core messenger gap: chat is in-call ephemeral today; no store-and-forward
Multi-device syncNoBestPartYesBestTelegram cloud sync is the reference; nothing on our side yet
Reactions / message interactionsYesBestYesYesBestSOVEREIGN protocol + emoji set in the core (wire 0x45); floating emoji live on every tile (800)
Bot / programmable platformNoBestPartNoBestTelegram Bot API + Discord bots are the references; our wire protocol is open but has no bot surface
Channels / broadcast at scaleNoBestPartNoPartTelegram channels are the reference
Ratcheting group E2EE (MLS-class PFS/PCS)NoNoYesBestNoThe 2025/26 group-crypto bar (RFC 9420); our room key is static per session
Post-quantum hybrid key exchangeNoNoPartBestNoSignal PQXDH / iMessage PQ3 class -- the 25/26 crypto frontier
Metadata privacy (sealed sender)NoNoNoBestNoSignal-only frontier capability
Sovereign full stack -- own codec, relay, crypto, language, no WebRTC/OpenSSL anywhereBestNoNoNoNoEvery major sits on WebRTC/licensed codecs/TLS libraries; ours is one auditable stack down to the compiler
Integer bit-exact media + recon-hash conformanceBestNoNoNoNoPer-frame decode-truth verification is impossible on float pipelines
Self-healing ops (drift badges, auto-fallback, self-upgrade)BestNoNoNoNoThe call diagnoses and heals itself; majors ship opaque failures
coverage 666/1000EXCEEDS 3PRESENT 11ABSENT 7
Honest verdict. Nishi has broad, sovereign search-engine presence — a real organ behind every core ranking and crawl axis, built bits-up in one language. It is not yet a scale or neural-ranking rival: the majors lead on index size (billions to trillions vs a Common-Crawl-seeded slice) and trained rerankers. Nishi's genuine exceeds are structural — owning the whole stack, neutrality by construction, and a zero-JS integer-deterministic result page. The climb is a bigger index and a trained reranker.

Generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/comms.matrix — every Nishi cell verified against real organ source on disk. Zero JS, zero trackers.