> On 11/7/09 10:07 AM, Hongfei Tian wrote: >> Hi, >> I wonder if there is any special reason that why we don't allow other >> languages in nickname, tag, and group name. >> I understand those could become part of URL path. >> >> If I allow other languages, would it cause bugs? > > Right now I think you'll need to bump around tweaking a lot of regexes; > not impossible but annoying. :) > > The main problem you're likely to have changing the allowed chars is > with remote subscriptions, as other StatusNet sites may reject the > usernames. > > If I've got time I'm going to be fixing up support for other chars and > case-preservation soon, not sure it'll make it into 0.9 though. > Now that I'm starting to get into external authentication providers, such as LDAP, I'm really starting to see a problem with the a-z0-9 restriction we have on usernames. LDAP usernames frequently are in the format of "first.last" or "first_last" which makes their use currently impossible in StatusNet.
For the commercial side of the business, you may want to increase the priority of expanding the allowed characters in nicknames (at the very least to include _ and .), so businesses can more easily use StatusNet, and you SNI guys can make more money. :-) ~Craig _______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
