Follow-up to #57786.
The behavior described there is working as designed, but the UI is confusing enough that several people have hit it. Filing the design follow-up.
Looking for designer input. Not implementing yet.
The problem
Two independent visibility controls per field. Scope (lock icon) governs the address book, federation, and lookup server. Profile-page visibility (separate section) governs /u/<uid>. They sit far apart, use different vocabulary, and have different per-field defaults, so identical scope settings produce visibly inconsistent results.
Goal: one control change should produce a predictable outcome. Underlying privacy model and per-field granularity stay.
Concepts
Five rough directions. Copy/icons illustrative; nothing final.
A. Relabel and co-locate.
Two controls stay, sit next to each other, clearer labels.
B. Primary + advanced.
Profile-page is the per-field control; scope moves to a per-field Advanced disclosure.
C. Unified audience selector.
Collapse both into one dropdown with five public-ness levels; server maps to (scope, visibility) pairs.
D. Effective-visibility preview.
Keep both controls, add a plain-English pill showing the computed result. Composes with A.
E. Global discoverability switch.
One top-of-page switch sets scope defaults; per-field controls drop to profile-page only.
Asks
- Which concepts survive a gut check?
- Better word than "Discoverability"?
- Incremental for NC34, or hold for one bigger redesign?
Follow-up to #57786.
The behavior described there is working as designed, but the UI is confusing enough that several people have hit it. Filing the design follow-up.
Looking for designer input. Not implementing yet.
The problem
Two independent visibility controls per field. Scope (lock icon) governs the address book, federation, and lookup server. Profile-page visibility (separate section) governs
/u/<uid>. They sit far apart, use different vocabulary, and have different per-field defaults, so identical scope settings produce visibly inconsistent results.Goal: one control change should produce a predictable outcome. Underlying privacy model and per-field granularity stay.
Concepts
Five rough directions. Copy/icons illustrative; nothing final.
A. Relabel and co-locate.
Two controls stay, sit next to each other, clearer labels.
B. Primary + advanced.
Profile-page is the per-field control; scope moves to a per-field Advanced disclosure.
C. Unified audience selector.
Collapse both into one dropdown with five public-ness levels; server maps to (scope, visibility) pairs.
D. Effective-visibility preview.
Keep both controls, add a plain-English pill showing the computed result. Composes with A.
E. Global discoverability switch.
One top-of-page switch sets scope defaults; per-field controls drop to profile-page only.
Asks