D
F
Replying to
@danabra
hmm is that useful if (part of) the goal is to broadly change social incentives though
4,850 views
D
Replying to
@futur
even if the default changes, a change so significant should be gradual imo. i’m just saying opt-in makes it immediately mergeable
4,850 views
F
Replying to
@danabra
yeah fair, how do you make something like that gradual though? at some point the default ux has to go from a to b aesthetically the idea having display name/handle on different lines hurts but from a practical pov it would make it easier to bite the bullet
4,850 views
D
Replying to
@futur
one route is that you’d first introduce as opt-in, then at some point either (1) flip default for new users while prompting existing users to make a choice, or (2) do a hard cutover
4,850 views
D
D
Replying to
@danabra
i like two things about it - really puts identity first and makes domains central - immediately makes screenshots feel different from twitter, it’s a vibe
4,850 views
F
Replying to
@danabra
definitely agree, almost feels more techy than the rest of the app ui tries to be but I think that's good to have a bit of in such an important spot
4,850 views
M
Replying to
@futur
One cultural downside is joke/seasonal display names are a big thing for some folks. Maybe there’s a way of putting the domain first, and the name after is optional, though not sure if that really works
4,850 views
D
Replies
F
Replying to
@danabra
if the actual problem is display names obscuring handles, why would we not move handles to the line below just like we do in the detail view? lowest effort solution
4,850 views