I just wanted to jump into the thread and make sure to clarify a few things being discussed.
1) Re MyPostButler specifically - Brian and the Policy team did the right thing in responding to Dean and notifying him that his app is currently in violation of a number of policies that are listed in the Twitter Rules ( http://help.twitter.com/forums/26257/entries/18311) including: - Auto-follow by Keyword - Bulk unfollowing - Promoting serial account creation for the purpose of auto-following Brian and the team then offered to work with him to fix his app to be within the guidelines before switching over to OAuth to ensure his app wouldn't be suspended. We have to work together to protect the integrity of the ecosystem and all of the rules are in place for everyone's benefit. While "bulk unfollow" is a somewhat ambiguous rule, the real signal is if users of your application end up getting suspended frequently. We will work with applications to address the functionality until it no longer happens. If the app is unable or unwilling to make changes, the application will be suspended. It's also important to note that if your app incentivizes spammy behavior, like allowing them to switch app tokens for the sake of creating vanity URLs or hiding the source of the application ( http://blog.collins.net.pr/2010/04/oh-snap-mypostbutler-20-is-back.html), those users will be suspended and eventually banned. We would all much rather be spending our time helping improve the ecosystem instead of policing bad behavior. 2) @mypostbutler was suspended due to a clear violation of the Twitter Rules that prevents any user from selling their Twitter username. 3) Suspension emails don't currently include the exact reasons that an app is being suspended. We do call out the Twitter Rules and the ability to contact a...@twitter.com to get a definitive answer as to why it was suspended. Brian and the team will always provide explicit answers as to why a particular app was suspended. This is something we want to fix in the tools we use and I will make sure we do so in order to provide more clarity up front. In the end, we do not tolerate spammy behavior from users or from apps that enable it. Most everyone in the ecosystem builds app that add great net value and we would much rather be spending our time helping them then having to police bad behavior. I am happy to answer any policy questions or provide more context around how we make the decisions we make. We are also always looking to improve the process around how we interact and communicate with developers (like suspension notices including exact reasons for suspension) so please let us know any constructive ways that we can improve that and provide more clarity and certainty to you. Ryan On Mon, Apr 26, 2010 at 1:57 PM, John Meyer <john.l.me...@gmail.com> wrote: > On 4/26/2010 1:37 PM, Dean Collins wrote: > >> John, >> >> Nope, Dossy is pretty much on the money, I don't care about the money >> and I'd prefer to see people using it rather than let it die. >> >> >> Basically I'm a little over twitter and their amateur approaches to >> certain things. I'd be the first person lining up to pay my $20 a month >> or whatever for real commercial accounts with real support one on one >> support contacts 9eg something goes wrong you call the person you dealt >> with alst time so as not to explain everything again).. >> >> > you'll get no arguments that the support needs to be improved just a > little. The fact that I'm shocked that you even got an explanation shows me > just how much work needs to be done. > But let's look at the site promoting your program, which I think you're > promoting through http://www.mypostbutler.com/ . According to what you > posted, one of the reasons your app got denied because of bulk unfollowing. > Well, on your site you use the words "Bulk unfollow users". You may have > explained it in your message, but you did not add an explanation to the fact > that you have to manually check their names in order to "undelete". > > And then there's your first paragraph: > Do You understand the difference between a web based Twitter tool that can > make 150 API calls an hour for a single Twitter account and a dedicated > Twitter .Net application running directly on your computer that can make > 20,000 API calls an hour across multiple accounts? > > Ignoring the fact that this paragraphs hits people over the head with the > difference between 150 and 20000 (aka a beigelist and a whitelist), it > dosen't make sense. Why woulddn't a web site built upon twitter not > whitelist their own ip address particularly if they have multiple twitter > accounts? And you also mentioned MLM schemes closeby, if only in the > negative. Who exactly is buying your product that you need to mention that? > > Maybe this will do nothing, but I'd frame that into a legal (according to > twitter's rules) use. For instance, you might mention families who have > multiple twitterers but only one IP address. Kinda frustrating to get on a > computer after a sibling is hogging it only to realize that they have to > wait an hour to tweet. > > > > > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
