cohost should have a blue checkmark, but it should be assigned to users at absolute random without communicating that fact to anyone
My approach to cohost feature design is less “would it be useful” and more “would it be funny”
| perfectionist who's trying to |
| stop being such a perfectionist |
| finally gave 🍬self a face |
| (send asks!) |
cohost should have a blue checkmark, but it should be assigned to users at absolute random without communicating that fact to anyone
My approach to cohost feature design is less “would it be useful” and more “would it be funny”
blue checkmarks but they rotate to new random users if someone clicks on them
everyone gets a blue checkmark but if you ever click on the "what's this?" explanation you lose it and can never ever get it back
theres a set amount and they get to given to a new set of people every day at random. if its ur day to have a blue checkmark congrats
everyone gets a different colored check mark, and the "verified color of the day" is randomized.
"site broken in ways that are funny" has been on the overall Design Goals doc since the beginning.
also capsule avatars rule and i'm still thrilled you got one commissioned specifically to look good in it
Honestly capsule avatars still just really delight me and it felt natural to get an avatar for it.
"checkmark but assigned at random without any communication" sounds kinda like what tumblr tried out a while back. It did not end well. (When does anything on tumblr, tho?)
(ISTR they applied it to gaud, without any explanation or even telling the pink squishy thing they were having a new shiny target painted on 'em; it was grim. Different user dynamic here, tho.)
blue checkmark battle royale: each day 99 chosters can fight to the death for control over the checkmark.