Re: [twitter-dev] Re: Multiple Account creation
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
Re: [twitter-dev] Re: Multiple Account creation
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
Re: [twitter-dev] Re: Multiple Account creation
On 4/23/2010 3:08 PM, Taylor Singletary wrote: 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 Even putting a state hashtag at the start #CO, #CA, etc would work. Whatever suggestion you use you probably are going to have to apply for whitelisting. Geolocation tags may have an added bonus of being able to guide job applicants to where they should submit their applications. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Multiple Account creation
Sorry to bump this topic, but is there any here that can enlighten me? Thanks in advance! On Apr 18, 2:18 pm, Dinho nkerkvl...@hotmail.com wrote: Hi there, I'm a little confused about the number of accounts that is allowed. Searching through this group, the web and reading the Twitter EULA it seems just a few are allowed. However in these threadshttp://groups.google.com/group/twitter-development-talk/browse_thread... andhttp://groups.google.com/group/twitter-development-talk/browse_thread... it's stated that multiple accounts are allowed and that even 600 accounts could be allowed. But after reading the StatTweets and Sportytweets stories, and their suspended accounts I'm a little confused. Since on the other hand, TweetmyJobs.com has stated they manage over 8000 different Twitteraccounts. And that sounds like a huge multi-account violation to me. We're currently setting up a localised version of Tweetmyjobs, which will require a lot less accounts, but we would still need around 250 accounts (lto localise the jobs in different areas to different channels). So my question is; would this be acceptable and what would be the best way to set this up, without violating Twitters TOS. Or would it just be a waste of my time?
