Huh. I wonder if they can still sign in... You can also see one of them on the web here http://twitter.com/account/redirect_by_id?id=92595586
Other then an account here and there, from what was probably a bug in the validation code, there should be no accounts being created with such characters. <crosses fingers> Abraham On Wed, Feb 3, 2010 at 17:03, PJB <pjbmancun...@gmail.com> wrote: > > Hm, wait... this account was created in Nov 2009 and has spaces and a > \n in his screen_name?? > > http://twitter.com/users/show.xml?user_id=92595586 > > On Feb 3, 4:59 pm, PJB <pjbmancun...@gmail.com> wrote: > > Just FYI, Twitter screen names are not (or, apparently, didn't use to > > be) restricted to 0-9A-Z-_ > > > > <id>6295462</id> > > <screen_name>Magic carpet1</screen_name> > > > > <id>3939231</id> > > <screen_name>Walking the dog2</screen_name> > > > > <id>92595586</id> > > <screen_name>Its mine\nM2</screen_name> > > > > We're also seeing non-ASCII in some other screen names. (Though we > > don't currently know what they are... we just know they exist! ;) > > > > We're assuming this is a vestige of long ago coding? > > > > It does screw up our desire to use ascii char(15) in db... > > > > Maybe Twitter can fix? > -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
