Skip to content

TRI-NET chat and calling: signed nicknames, CallKit, LiveKit, and Fullmoon UI - #90

Open
dmitrii-f-t27 wants to merge 32 commits into
mainfrom
feat/regen-final
Open

TRI-NET chat and calling: signed nicknames, CallKit, LiveKit, and Fullmoon UI#90
dmitrii-f-t27 wants to merge 32 commits into
mainfrom
feat/regen-final

Conversation

@dmitrii-f-t27

@dmitrii-f-t27 dmitrii-f-t27 commented Jul 22, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Refs #82

Follow-up to #89.

Summary

  • add signed per-device identity, exact nickname claim/lookup, multi-device linking, and encrypted direct/group chat
  • implement CallKit/PushKit call lifecycle, audible incoming-call presentation, separate audio/video intent, and terminal cleanup
  • route automatically over signed local mesh when available, with LiveKit/WebRTC fallback and macOS client parity
  • add the Fullmoon-inspired chat-first UI, presence, fingerprints, and server-authoritative unread state
  • integrate current main and preserve the previously published PR TRI-NET chat and calling: signed nicknames, CallKit, LiveKit, and Fullmoon UI #90 history without force-pushing
  • complete the macOS calling target and keep T27-generated Rust byte-identical while excluding it from hand-written formatting/lint rewrites

Validation

  • cargo fmt --all --check: passed
  • cargo clippy --all-targets -- -D warnings: passed
  • cargo build --verbose: passed
  • cargo test --verbose: passed
  • cargo test --manifest-path services/call-api/Cargo.toml: 24 passed
  • internet_call.t27: parse and typecheck passed with 0 errors / 0 warnings; 29 tests, 27 invariants, 1 benchmark; generated Rust matches byte-for-byte
  • iOS physical-device build-for-testing: passed
  • iPhone 17 physical unit run: 44/44 passed
  • macOS app build: passed

Current verification boundary

  • iPhone 13 was unavailable during the final run, so the final merged commit was not rerun on that device
  • the checked-in runtime endpoints are local (http://SSDs-MacBook-Pro.local:8080 and ws://SSDs-MacBook-Pro.local:7880)
  • public Internet/background calling is not verified or deployed: no confirmed public HTTPS/WSS/TURN route and no APNs provider credentials were available for this validation

SSD DDD and others added 6 commits July 22, 2026 17:02
SSD DDD SSD DDD
feat(phone): add signed nickname calling and group chat
3f8851a 
Add per-device P-256 identity, unique nickname discovery, account linking, presence-aware LiveKit call fan-out, and signed mesh invitations. Persist account-level group chats with membership checks and idempotent messages, expose the same UI on iOS and macOS, and add service and client tests.
SSD DDD SSD DDD
fix(phone): stabilize internet media connection
c5444f3 
Clear stale CallKit transactions before new calls, use LiveKit state for the call UI, and recover remote video subscriptions that arrive before the delegate callback. Add focused connection diagnostics. Verified on ssd26 and t27_dev with bidirectional audio/video for 53 seconds and zero RTP packet loss.
SSD DDD SSD DDD
chore(mesh): add three-node lab configs
dddaec8
SSD DDD SSD DDD
merge: integrate remote regen updates
cd7ade8
SSD DDD SSD DDD
Merge remote-tracking branch 'origin/feat/regen-final' into feat/rege…
0e2d413 
…n-final
SSD DDD @claude SSD DDD
fix(security): INVITE anti-replay via freshness timestamp
90869fc 
WAVE #15 authenticated the INVITE but left it replayable: a valid HMAC only
proves the sender knew the PSK once, so a sniffed INVITE could be replayed to
force a ring/auto-join later. Add a TS_MS field to the (HMAC-covered) payload and
reject any INVITE whose timestamp is missing or outside a +/-15s window. Verified
live: a replayed INVITE (valid MAC, 60s-old TS) -> 0 auto-joins; a fresh one ->
auto-joins. Both platforms; smoke updated and still PASSes. Residual: a 15s window
allows an immediate replay (a seen-MAC cache would close it fully) - left as an option.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@dmitrii-f-t27
dmitrii-f-t27 marked this pull request as ready for review July 22, 2026 17:05
SSD DDD and others added 21 commits July 24, 2026 13:50
SSD DDD @claude SSD DDD
docs(hw): radio mesh + internet-over-air results (refs #9)
d10fd7b 
trios_radiod on 3 boards, no Ethernet: ETX convergence, DATA delivery,
and M4 internet-over-radio (Ethernet-less node 13 fetched public IP
182.232.227.12 via gateway node 11, entirely over 2.4 GHz). Six radiod
bring-up defects documented (one-shot writer, O(n) prebuffer, AGC blind,
own-TX DC leak, fused bursts, fixed jitter).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
SSD DDD SSD DDD
docs(hw): wire-free re-test — internet-over-radio confirmed; board 12…
16b2790 
… RX-cal bug diagnosed+fixed (refs #9)
SSD DDD SSD DDD
docs(hw): board 12 into mesh (RX-cal fix + TX-gain), 3-node no-CSMA c…
28805eb 
…ollapse characterized
SSD DDD @claude SSD DDD
docs(hw): multi-frequency sweep + stable wire-free operation (refs #9)
f2da128 
Boards 2+3 fully off Ethernet. Frequency sweep 915/1575/2400/2450/5800
MHz: links strongly frequency-dependent, 2450 MHz best (backbone solid +
board 12 joins). Stable reliable config = default 2.4 GHz, no retune:
board 13 (wire-free) fetched internet over radio (182.232.227.12),
gateway confirmed reply. Board 12 marginal (needs CSMA). Operating
recipe + reboot-restore documented.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
SSD DDD @claude SSD DDD
docs(hw): CSMA mesh — full 3-node + board 12 internet over radio (refs …
8e73e5d 
…#9)

At 2425 MHz with CSMA/CA + hop-by-hop relay session fix, all three links
converge and board 12 (the previously-marginal node) fetched public IP
182.232.227.12 over the radio mesh. Documents the 4 changes (CSMA,
TRIOS_FREQ+channel scan, fetch retry, relay crypto fix), the 2.4 GHz
interferer hopping, and per-node tuning.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
SSD DDD @claude SSD DDD
docs(hw): wire-free confirmation — board 12 (no Ethernet) internet ov…
7788383 
…er radio @2455 (refs #9)

Boards 2+3 physically off Ethernet; live channel scan picked 2455 MHz
(2425 had since jammed). Gateway fetched 182.232.227.12 and board 12
logged INTERNET-VIA-RADIO-MESH over the air, no cable but power+console.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
SSD DDD SSD DDD
fix(video): restore LAN calls and render LiveKit media (refs #82)
5d978d2
SSD DDD SSD DDD
merge: integrate latest main call stack (refs #82)
bb4fc6d
TRI-NET dev
feat(ios): redesigned incoming-call screen + HANDOFF.md for continuation
602ccee 
- IncomingCallOverlay: gradient backdrop + breathing glow, 3 rippling rings,
  gradient avatar disc, ENCRYPTED . FORWARD-SECRET badge, glowing Accept button
  (ring/haptics/accept-decline wiring preserved). answerButton gains a glow param.
- HANDOFF.md: full continuation guide (running servers, folders, build/run,
  4-feature status + file:line, APNs .p8 requirement, next steps).
tri-net
feat(chat): group-chat chime + unread badge (iOS + macOS)
dc16487 
Feature C: the server already returns unread_count per chat and
total_unread_count; the client now consumes them.

- InternetCall.swift: GroupChatSummary decodes unread_count (optional for old
  servers); GroupChatsResponse decodes total_unread_count; groupChats() returns
  both. GroupChatController tracks unreadByChat + totalUnread, fires
  onNewMessage for messages from others, clears a chat's badge when opened, and
  reconciles local counts with the server's on each 3s refresh.
- iOS ViewModel + macOS CallManager: groupChat.onNewMessage plays the existing
  ChatChime (same blip as in-call 1:1 chat).
- iOS Views + macOS VideoCallTab: numeric unread badge on the group-chats icon
  and on each chat-list row, with accessibility labels.
- macOS BUILD SUCCEEDED; iOS Simulator BUILD SUCCEEDED.
tri-net
feat(ui): nickname-first call flow — no IP entry, one-tap call
8b3fe5c 
The call screen looked like a network-engineer tool: raw IP entry, IP/port in
the self line, an IP quick-dial list, and a Route picker as the first thing you
see. Calls were hard to start for a normal user.

Now the flow is: search by @Nickname -> tap a result to call them. Route (Auto
by default) is collapsed behind a disclosure. IPs are gone from the UI.

- Search field placeholder is now 'Search by @Nickname' (was 'nickname or IP').
- Results show each contact as a card with an avatar, nickname, and a Call
  button (macOS) / tap-to-call (iOS) — select + start the call in one action.
- Self line shows 'You are @nick' instead of '@nick | IP:port | fingerprint'.
- Removed the raw-IP quick-dial chips on both platforms (mesh-era affordance).
- Route picker moved under a 'Connection' disclosure (Auto is right for nearly
  everyone; LAN peers still appear by name via the roster).
- macOS + iOS both BUILD SUCCEEDED.

Server call-signaling is verified end-to-end by examples/live_call_check.
TRI-NET dev
Revert "feat(ui): nickname-first call flow — no IP entry, one-tap call"
887f0cb 
This reverts commit 8b3fe5c.
tri-net
feat(calls): nickname contacts + internet-call ringtone + clearer UI
9499992 
User-driven fixes after the previous UI pass was confusing.

Call flow — 'enter a nick, add it, tap to call' (iOS + macOS):
- Saved contacts list (@published, persisted). Add a contact by typing a
  nickname; tap the phone button to call them on the selected route.
- callNickname(_:) helper sets callee/searchQuery and starts the call.
- Directory search (online users) now adds + calls in one tap too.

Ringtone on incoming INTERNET calls (was mesh-only):
- internet.onIncomingCall now sets vm.incomingCall with an internetCallID, so
  the IncomingCallOverlay + RingSynth tri-tone fires for LiveKit calls too,
  not just mesh UDP. Previously internet calls were silent in-app (CallKit only).
- acceptIncoming branches: internetCallID -> answerInternetCall; else mesh.
- Shared beginIncomingTimeout() for the 40s auto-miss on both routes.

UI clarity — settings/icon tap targets:
- Top-bar buttons (group chats, settings) enlarged to 48pt with contentShape +
  solid backgrounds + accessibility labels, so icons are not crowded and the
  whole circle is tappable.
- 'Connection' disclosure shows the route (Internet default, Local Mesh) instead
  of a bare segmented picker as the first thing on screen.
- Removed raw-IP quick-dial chips on both platforms (nickname is the path).

Chat chime on incoming messages: already wired (groupChat.onNewMessage ->
chatChime.play()).

macOS + iOS both BUILD SUCCEEDED; server call-signaling verified end-to-end by
examples/live_call_check (create -> incoming -> join, all green).
tri-net
chore: stop tracking SPM checkouts + build dirs
8f66561
@dmitrii-f-t27
feat(calls): harden signed chat and two-device media (refs #82)
a9b9637
@dmitrii-f-t27
feat(calls): add nickname routing and resilient call lifecycle
defaab3 
Implements exact nickname directory lookup, Internet and signed local call lifecycle, CallKit/PushKit handling, E2EE direct messages, Dala-style UI, and production deployment contracts.

Refs #82
@dmitrii-f-t27
fix(call-api): tolerate measured iPhone clock skew
f920024
@dmitrii-f-t27
merge: preserve published PR 90 history (refs #82)
03ac9a1 
# Conflicts:
#	phone/TriNetVideo/ViewModel.swift
#	phone/TriNetVideo/Views.swift
#	phone/desktop/VideoCallTab.swift
#	phone/shared/InternetCall.swift
@dmitrii-f-t27
merge: integrate current main into PR 90 (refs #82)
5928e83 
# Conflicts:
#	src/bin/tri_rti.rs
#	src/lib.rs
@dmitrii-f-t27
fix(macOS): include calling transport sources (refs #82)
264f503
@dmitrii-f-t27
ci: keep generated Rust out of hand-written lint gates (refs #82)
24c9bea
@dmitrii-f-t27 dmitrii-f-t27 changed the title Follow-up: signed nickname calling, group chat, and mesh lab configs TRI-NET chat and calling: signed nicknames, CallKit, LiveKit, and Fullmoon UI Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@dmitrii-f-t27