I know that Evan vetoed the idea of mixed case nicknames, but I'm having a problem that I bet a lot of people may be encountering.
Sites like BrainBird support mixed case nicknames - it's up to them, after all. However, when another StatusNet instance interacts with such a mixed case instance, Bad Things Happen. First, our nickname detection doesn't work. As shown in this notice http://identi.ca/notice/14779770 "@DeepSpawn" is not linked. Second, you cannot remote subscribe to someone with a mixed case nickname. If you try to do so (I tried to subscribe to DeepSpawn), you get this message: "Nickname must have only letters and numbers and no spaces." The error message is either incorrect, and should say "only *lower case* letters..." or we should allow such a subscription. Third, the OMB specification says: "nickname An alphanumeric short name for a person, 1-64 characters." It does not indicate a case requirement. It appears that StatusNet does not obey the StatusNet specification. I started looking through the code for how to fix this, and it appears that we need to split the NICKNAME_FMT constant into 2 constants, one for nicknames for local StatusNet users, and one for nicknames detection in notice text and remote subscriptions. How exactly should we fix this problem? Thanks, ~Craig _______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
