Say who the tray is signed in as, and against which endpoint #3

Merged
geusebio merged 2 commits from feature/signed-in-as into main 2026-08-14 19:07:03 +00:00
Owner

Part of #578. Needs scclient #3 and the platform's #628.

The menu could show a whole tree of applications without ever saying whose they were — a real gap in something set up once and glanced at for months, whose token comes from a file or an environment variable, and where a tray on staging looks exactly like one on production.

The identity row

The row names the person, the token when the platform named one, and the endpoint. Asked once at startup, not on the poll: an identity does not change under a running tray, and re-asking every ten seconds would be six requests a minute to re-learn the same name. An unreachable platform falls back to the endpoint alone — the sync right after is where "the platform is down" gets said properly.

Per the capture policy, the stub scene answers /cli/me too, so the row is in the screenshots rather than only in a test. The stub now serves on someones.localhost rather than a loopback address, because this row prints the endpoint and http://127.0.0.1:8099 in a manual reads like a mistake.

go build, go vet, go test ./... clean; captures regenerated for all three themes.

Part of [#578](https://git.grey.ooo/Grey.ooo/Someones.Computer/issues/578). Needs [scclient #3](https://git.grey.ooo/Grey.ooo/someones.computer_scclient/pulls/3) and the platform's [#628](https://git.grey.ooo/Grey.ooo/Someones.Computer/pulls/628). The menu could show a whole tree of applications without ever saying whose they were — a real gap in something set up once and glanced at for months, whose token comes from a file or an environment variable, and where a tray on staging looks exactly like one on production. ![The identity row](https://git.grey.ooo/Grey.ooo/someones.computer_tray/raw/commit/abe70873c328e214ebfd83d0180737d2baeabe33/docs/images/macos/tray-menu.png) The row names the person, the token when the platform named one, and the endpoint. Asked **once at startup**, not on the poll: an identity does not change under a running tray, and re-asking every ten seconds would be six requests a minute to re-learn the same name. An unreachable platform falls back to the endpoint alone — the sync right after is where "the platform is down" gets said properly. Per [the capture policy](README.md), the stub scene answers `/cli/me` too, so the row is in the screenshots rather than only in a test. The stub now serves on `someones.localhost` rather than a loopback address, because this row prints the endpoint and `http://127.0.0.1:8099` in a manual reads like a mistake. `go build`, `go vet`, `go test ./...` clean; captures regenerated for all three themes.
Say who the tray is signed in as, and against which endpoint
Some checks failed
CI / build (pull_request) Has been cancelled
abe70873c3
The menu could show a whole tree of applications without ever saying whose
they were. That is a footnote in a terminal and a real gap in something set up
once and glanced at for months: the token comes from a file or an environment
variable, and one tray against staging looks exactly like one against
production.

The row names the person, the token when the platform named one, and the
endpoint — asked once at startup rather than on the poll, since an identity
does not change under a running tray. An unreachable platform falls back to
the endpoint alone; the sync that follows is where "the platform is down" gets
said properly.

The capture scene answers /cli/me too, so the row is in the screenshots rather
than only in a test, and the stub now answers on someones.localhost — the row
prints the endpoint, and a loopback address in a manual reads like a mistake.
Pin scclient to the merged identity read
All checks were successful
CI / build (pull_request) Successful in 7m25s
9cf3fc11c9
geusebio changed title from WIP: Say who the tray is signed in as, and against which endpoint to Say who the tray is signed in as, and against which endpoint 2026-08-14 19:06:43 +00:00
Sign in to join this conversation.
No reviewers
No labels
in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grey.ooo/someones.computer_tray!3
No description provided.