android: the handoff — the pending rounds, the pipeline, and what is unverified
Everything written this session that has not been through the device: rounds 43 to 48 (each patch adversarially verified, 43's transient-notice expectation fixed), a partial round 49, the pipeline scripts, the Android Auto design and the icon comparison mock. Also the two harness changes that were never A/B'd — adaptive waits, which may only shorten a declared wait and never lengthen it, and a ship that runs the mock walk and the deploy at the same time. The A/B and its 255-step baseline are in handoff/tools; main stays at what the phone has actually walked.
This commit is contained in:
1 parent
867fd42972
commit
9f0601027c
400 files changed
+26401
-3
No files matched your search
@@ -0,0 +1,12 @@
|
||||
Every name in Community can wear one you gave it. The peer's sheet ends in
|
||||
**Name and notes** (`src/mobile/contacts.svelte.js`, `contacts_meta_list` /
|
||||
`contact_meta_set`): a petname, a group, a private note and the two marks,
|
||||
Favorite and Trusted. All of it sits in the app's own config on this phone
|
||||
and is published nowhere — Soulseek never learns it, and neither does the
|
||||
person it describes. The petname stands in for the username on the buddy
|
||||
list, in the chat list, on a thread's bar, in the peer sheet, in a room's
|
||||
roster and on a room line, and the real username stays with it — on the
|
||||
line beneath, or beside the name in a room — so a stranger is never quietly
|
||||
turned into someone you know. Favourites sit at the top of the buddy list,
|
||||
a star and a shield mark the two, and clearing a person's details drops the
|
||||
entry rather than storing an empty one — the backend's own rule.
|
||||
Reference in new issue
Block a user