[twitter-dev] Mass Unfollow
Want to pare back on the number of people we follow. How many friends can one account unfollow at any one time and not get banned/suspend? (I understand the spam team implemented a policy last August by which accounts that unfollowed too many friends at a time got suspended. Lost an account at the time by dong so before the policy was announced.) Thank you.
[twitter-dev] Re: OAuth newbie question
Thank you so much Taylor. Can you believe that nowhere in the Twitter
API documentation can I find this crucial, yet very simple
instruction. There are ample pointers to explanations of how to get
OAuth token, but absolutely no instructions I can find for what to do
once you obtain the token key and secret.
I tried very permutation of posting them along with the twitter REST
calls, but the one you suggested of posting the secrets as parameters
without values. This single line instruction needs to be added to the
Twitter API documentation.
BTW: The php equivalent of url_escaped ()is urlencode().
Thanks much.
On Mar 7, 6:53 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
A lot of people have found my presentation on OAuth useful when trying
to learn the ins and outs of the entire request cycle with an OAuth-
protected API:http://bit.ly/oauth-zero-to-hero
When accessing a protected resource with OAuth, the oauth_token and
oauth_token_secret you receive become your access token. You include
oauth_token as an OAuth parameter in your signature base string and
authorization header, and then sign your entire OAuth request with a
composite signing secret:
{url_escaped(consumer_secret)}{url_escaped(oauth_token_secret)}
Taylor
On Mar 6, 2:55 pm, IDOLpeeps i...@idolpeeps.com wrote:
I've overcome the nuances of generating the oauth signature. It
shocks me that the API documentation provides no clear indication of
how to send the tokens along with an API call. It's not even a PHP-
specific question. Simply put: Where do the oauth_token and
oauth_token_secret get embedded in API call: As posted parameters?
If so, with what parameter names? Can anybody provide guidance? I
have seen many people ask this question, yet see no answer.
As far as why one would want to use their own library vs. somebody
else's, that's a question for the ages. One specific answer is that
many of us have created our own application-specific libraries that
accommodate traditional http authentication and we'd like to keep our
libraries when we add Oauth. To do so, it's best to have an answer to
this question.
Thank you.
[twitter-dev] OAuth newbie question
What do you do once you get the oauth_token and oauth_token_secret? Do the token and secret get passed along with the rest of the API call as posted parameters? Can someone please provide an example of how to form a CURL request in php using the token and secret? I can not find documentation anywhere that explicitly explains what to do once the token and secret are obtained. All the documentation I can find provides for use for somebody else's php wrapper. I don't want to use a third party wrapper. Thank you.
[twitter-dev] Re: OAuth newbie question
I've overcome the nuances of generating the oauth signature. It shocks me that the API documentation provides no clear indication of how to send the tokens along with an API call. It's not even a PHP- specific question. Simply put: Where do the oauth_token and oauth_token_secret get embedded in API call: As posted parameters? If so, with what parameter names? Can anybody provide guidance? I have seen many people ask this question, yet see no answer. As far as why one would want to use their own library vs. somebody else's, that's a question for the ages. One specific answer is that many of us have created our own application-specific libraries that accommodate traditional http authentication and we'd like to keep our libraries when we add Oauth. To do so, it's best to have an answer to this question. Thank you.
[twitter-dev] Re: Following Churn: Specific guidance needed
I agree my comparison to dictatorships is a stretch, but I was in a poetic mood and trying to emphasize the point that clarity is better than ambiguity. Twitter is obviously doing a tremendous job dealing with their explosive growth and dynamic nature of this new medium they've created. That said, capricious rules are also clearly as much an obstacle to growth as the problems (ie, spam) they are intended to prevent. When considerable investments in accounts are nullified in the blink of an eye by suspensions for which no notice, reason, or remediation is offered, entrepreneurs, marketers, investors, and individuals that could be great assets to the community lose faith and trust in continuing to be part of it. The issue is a quick follow and then unfollowing if not reciprocated. Would be very helpful to know the definition of quick as relates to following churn suspensions. As far as how general bulk unfollow relates to the type of patterned unfollowing that constitutes following churn: If a user is inspired by Scoble's post to wipe their friends list clean the same week they have added hundreds of followers, it is unclear if they risk suspension? Seems such a sequence lead to suspension of a friend's account (though of course one does not receive any feedback on the exact reason for suspension and she may not be interpreting the situation correctly.)
[twitter-dev] Re: Following Churn: Specific guidance needed
I agree my comparison to dictatorships is a stretch, but I was in a poetic mood and trying to emphasize the point that clarity is better than ambiguity. Twitter is obviously doing a tremendous job dealing with their explosive growth and dynamic nature of this new medium they've created. That said, capricious rules are also clearly as much an obstacle to growth as the problems (ie, spam) they are intended to prevent. When considerable investments in accounts are nullified in the blink of an eye by suspensions for which no notice, reason, or remediation is offered, entrepreneurs, marketers, investors, and individuals that could be great assets to the community lose faith and trust in continuing to be part of it. The issue is a quick follow and then unfollowing if not reciprocated. Would be very helpful to know the definition of quick as relates to following churn suspensions. As far as how general bulk unfollow relates to the type of patterned unfollowing that constitutes following churn: If a user is inspired by Scoble's post to wipe their friends list clean the same week they have added hundreds of followers, it is unclear if they risk suspension? Seems such a sequence lead to suspension of a friend's account (though of course one does not receive any feedback on the exact reason for suspension and she may not be interpreting the situation correctly.)
[twitter-dev] Re: Following Churn: Specific guidance needed
As soon as you do that, the naughties will set up their software to do just that, -1, to keep them just under the limit. That would be fine since anything under the limit is, by definition, not naughty. A fundamental principal of well ordered societies is having transparent rules. Imagine the US Code (law) was not published and citizens didn't know what specifically was legal and illegal. What kind of society would we be living in? Communist USSR? Iran? North Korea? Lots of community members and developers are leaving Twitter because of what appears to them to be arbitrary suspension of accounts they've invested considerable time and good citizenship developing only to have them removed without notice and oppty to remedy.
[twitter-dev] Re: Rate Limit on Unfollows?
Doug, Can you specify what constitutes a PATTERN of following and unfollowing (in terms of the number of follows/unfollows per day, the nature of the accounts unfollowed such as whether they follow back or not, etc.)? I am aware of accounts that were suspended for restarting by removing all their friends the day after following a bunch of people, but which behavior was hardly a pattern. Thanks
