In the past, with two different apps, we have been “restricted” due to “unsolicited @mentions?” We never do that, and Twitter platform never explained exactly what triggered the restrictions. We are going to relaunch one of the apps, but would like opinions on whether the app will again be restricted. It doesn’t seem to do anything many apps haven’t done in the past.

Basically, all the app does is retweet items that authorized users “refer” to a company’s main twitter @account by either a) DMing a tweet URL to it, or b) including a special #tag in each tweet that is then picked up via search. That’s it.

Question 1: Is there anything that seems it would be a violation, therein?

Question 2: We ran this app for over a year with no issues at all, but we were also testing other things, so our developers were also “generally” tweeting thru our api, and that might have caused some appearance of spam if they were over-mentioning in their personal tweets. (Since twitter is never specific, it’s impossible to know for sure what triggered the restrictions.) The fear here is, that while they never will say so, Twitter may actually not want the API ever be used for “general” user tweets, so any app doing so will be seen as spam if they simply over mention a few @names in their tweets (which millions of users do every day, but just not via the API). We certainly pray this isn’t the case, because that would mean no app can ever help the user compose threads or massage text in any way if the text must be posted via the api. But, alas, we can’t know. It’s all we can think might be the cause of “unsolicited mentions.” Could this in fact be the problem, and the only solution is never write apps that post general tweets on the user’s behalf, as many twitter-client apps once did? It would be a disaster for us, but obviously, we need to know.

Any theories welcomed.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.