Last modified: 2014-09-28 23:21:32 UTC
https://en.wikipedia.org/wiki/Special:CentralAuth/Nemo_bis I think an entire column of dashes saying "not blocked here either!" is pretty bad design. Perhaps we should change the "Groups" table column to be a "Notes" column and kill the "Blocked" table column entirely. The (re-labeled) notes column would list local groups, if any, and local blocks, if any. The overlap between the two (blocked users in user groups) is likely usually small, but in that case, we can just output both in the notes field.
Just omitting the field *sometimes* might be confusing but merging the two fields into one will be bad for the sortability.
The column of dashes is a little weird for most users, but I'm not sure there are any better options. Important things here are: * Sortability * Discoverability of info * Usefulness of info * Hell if I know As Marius says, blocking blocks together under notes could be problematic since it would mess with sortability. On the other hand, sorting by groups is already problematic because all the groups are blocked together. In a way, 'blocked user' is another kind of group, too... So the real question there is if people are apt to be sorting by both groups and blocks. As far as discoverability is concerned, the question is, if hidden, how will people know to read that: as no info, or no blocks? Removing the column and instead adding a separate note that they're not blocked anywhere could mitigate that, but then it'd still be weird having an entire column for one block among a couple hundred projects, so I doubt that would be worth trying.
