Twitter - Stop following user |
Declaration
<AMTWITTER ACTIVITY="stop_following_user" USER="text" SCREENNAME="text" ACCESSTOKEN="text" SECRETTOKEN="text" PROXYSERVER="text" PROXYPORT="text" PROXYUSERNAME="text" PROXYPASSWORD="text (encrypted)" /> |
Description
Enables the authenticating user to no longer follow a user specified by his/her screen name.
IMPORTANT: Automate's Twitter activities are performed using the Twitter REST API, therefore, launching and managing Twitter through Automate requires a valid Twitter account. |
Practical Usage
Used to un-follow (stop following) a particular user.
Parameters
General Properties
Property |
Type |
Required |
Default |
Markup |
Description |
User (Screen Name) |
Text |
Yes |
(Empty) |
USER="tweetybird |
The screen name of the user you wish to stop following. |
Authentication Properties
Proxy Properties
NOTE: Only HTTP proxy os supported.
Property |
Type |
Required |
Default |
Markup |
Description |
Proxy Host |
Text |
No |
(Empty) |
PROXYSERVER="host.domain.com" |
The host name (i.e. server.domain.com) or IP address (i.e. xxx.xxx.xxx.xxx) of the proxy server. |
Proxy Port |
Number |
No |
(Empty) |
PROXYPORT="300" |
The port that should be used to connect. |
Proxy Username |
Text |
No |
(Empty) |
PROXYUSERNAME="user" |
The user name that should be used to authenticate when connecting through the proxy server. |
Proxy Password |
Text |
No |
(Empty) |
PROXYPASSWORD="encrypted" |
The password that should be used to authenticate when connecting through the proxy server. |
Notes
OAuth Consumer Key/Secret Authentication
To use the Twitter API, the first thing you have to do is register a client application. Each client application you register will be provisioned a consumer key and secret. This key and secret scheme is similar to the public and private keys used in protocols such as ssh for those who are familiar. This key and secret will be used, in conjunction with an OAuth library in your programming language of choice, to sign every request you make to the API. It is through this signing process that Twitter trusts that the traffic that identifies itself is in fact you.
OAuth authentication is the process in which Users grant access to their Protected Resources without sharing their credentials with the Consumer. OAuth uses Tokens generated by the Service Provider instead of the User’s credentials in Protected Resources requests. The process uses two Token types:
Request Token:
Used by the Consumer to ask the User to authorize access to the Protected Resources. The User-authorized Request Token is exchanged for an Access Token, MUST only be used once, and MUST NOT be used for any other purpose. It is RECOMMENDED that Request Tokens have a limited lifetime.
Access Token:
Used by the Consumer to access the Protected Resources on behalf of the User. Access Tokens MAY limit access to certain Protected Resources, and MAY have a limited lifetime. Service Providers SHOULD allow Users to revoke Access Tokens. Only the Access Token SHALL be used to access the Protect Resources.
OAuth Authentication is done in three steps:
-
The Consumer obtains an unauthorized Request Token.
-
The User authorizes the Request Token.
-
The Consumer exchanges the Request Token for an Access Token.
Variables and Expressions
All text fields allow the use of expressions, which can be entered by surrounding the expression in percentage signs (Example: %myVariable% or %Left('Text',2)%). To help construct these expressions, you can open Expression Builder from these fields by clicking theInsert expression/variablebutton or pressingF2.
More on variables
More on expressions
More on the Expression Builder
Example
- The sample AML code below can be copied and pasted directly into the Steps Panel of the Task Builder.
- Parameters containing user credentials, files, file paths, and/or other information specific to the task must be customized before the sample code can run successfully.
Description:
Stop following user with the screen name Superman.
<AMTWITTER ACTIVITY="stop_following_user" USER="Superman" SCREENNAME="Batman" ACCESSTOKEN="138893066-pcQPBQlFnI8exepSZPaQcnljQJNg4tB6mUfGAywz" SECRETTOKEN="pL1IdTedxHU6JFd6HHRlkncy98R5PQLwKyrESGGM" /> |