A great suggestion, yes. In a world where every Twitter client were geo-aware and provided features that would allow for easy segmentation by area (and the API features to match), I would very much recommend that approach. Much of the discoverability features based on locale are present today.
Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Apr 23, 2010 at 2:00 PM, John Meyer <john.l.me...@gmail.com> wrote: > On 4/23/2010 2:58 PM, Taylor Singletary wrote: > >> Hi Dinho, >> >> This is a slippery area. You're correct to use the guidance of past >> discussions on this topic and the policies in place to determine if >> you're doing the right thing. >> >> The best thing I can tell you is: >> - make sure each account is useful and contributing valuable content >> to the ecosystem. valuable content is of course interpretable >> - don't surprise or annoy users with spam, auto-follows, >> au...@mentions, auto-dms, etc. >> - don't use any kind of mechanization to create your users. do it >> iteratively, by hand. it will take you awhile. >> >> Taylor Singletary >> Developer Advocate, Twitter >> http://twitter.com/episod >> >> > > Couldn't another way to localize without having to create multiple accounts > be to add geolocation information to the tweet? > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >