Route scoring
Routes are ranked by reliability, latency, bandwidth, cost, metering, battery impact and hop count, with hard policy constraints such as "never use metered links".
JawaChat separates who you are and what you send from how it travels, so messages can use whichever compatible route is available.
Routes are ranked by reliability, latency, bandwidth, cost, metering, battery impact and hop count, with hard policy constraints such as "never use metered links".
Bounded queues, deduplication and TTL/hop limits support delay-tolerant delivery instead of assuming everyone is always online.
Gateway IDs encode country, subdivision and locality, so the same node software can represent a deployment in any ISO region.
The web app shows which relays are online, publishes to all of them and queues anything that fails in an encrypted outbox.
The routing core can step calls down from video to audio to text as network quality drops.
The JawaChat relay authenticates clients with signed challenges and enforces frame sizes, rate limits and origin allow-lists.
Gateways follow a predictable jawa-country-subdivision-locality-NN format, from Toronto to Ludhiana to São Paulo.
jawa-ca-ontario-toronto-01
jawa-in-punjab-ludhiana-01
jawa-gb-england-london-01
jawa-au-victoria-melbourne-01
jawa-jp-tokyo-01
jawa-br-sao-paulo-01
The registry can represent a gateway in every ISO region. It does not mean JawaChat operates physical infrastructure in all of them. Radio, carrier and satellite routes need compatible hardware, services and authorization.
Routing is separate from platform-specific transports, so new networks can be added one at a time.