justinzeus/wolfskin
1
0
Fork 0
Code Issues 2 Pull requests 4 Releases 3 Packages Activity

Recover failed person switches without changing identity

Browse source
This commit is contained in:
justinzeus 2026-11-08 16:49:53 +01:00
parent c21d17dfdf
commit 9355288f79
11 changed files with 400 additions and 68 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docker/README.md
View file

@ -216,6 +216,18 @@ require-login profiles still go through the existing protected sign-in flow.
cannot replace a different selected person. Name revalidation updates only the
name column and reloads the saved user, preserving newer settings and PINs.
A failed person switch reopens the picker on the still-authenticated person and
shows “The household server didn’t answer.” Back from a reopened avatar picker
dismisses to that person's navigation; the next Back exits. Back from a launch or
setup picker exits instead of exposing a previous person's content. Settings,
login and error panels return to the picker first; Back can exit a busy setup
request. PIN and require-login selection rules are unchanged.
Failed or cancelled Jellyfin switches restore the previous API token as well as
retaining the signed-in identity. A person-switch cover has a ten-second deadline;
an unfinished switch/replacement falls back to the setup picker with a message,
without choosing a different authenticated person.
Jellyfin, Conductarr, artwork, playback and crash-report clients share one
`PersistentDns` instance through the application graph. It keeps system-ordered
IPv6/IPv4 answers in memory and `noBackupFilesDir/wolfskin-dns.json` (at most 32 hosts).