If your hearing someone trustworthy, it's fine repeat and support the message spread.
- This application is a twitter application that basically recognize:
- one or more Twitter user operating as "master".
- one or more Twitter user operating as "supporter".
In order to be a supporter, the Twitter app need to be properly registered via dev.twitter.com
When one of the master account favorite a tweet, all the support retweet them. stop.
Is not a violation of Twitter policies, is not a violation of User Term of Service and Agreement and what you can have in mind. just, that.
It's a working prototype, not a stable industrial software. but this is the sequence:
Login with your twitter account, and register an app, the account used here MAY have not relationship in the master/supporter. Read the Twitter rules about automation because we want avoid make spam.
Assign to your app the permission (permission who is gonna to ask to the user) in "Read/Write", like here, (my app is called mic-check, your need to have a differet name because these name are unique):
Go in keys, click in "Your Access Token" button to create your own access token. you'll need to make tests at least.
Now, you've to copy this keys in the script files.
The script takes this options:
$ ./adminutils.py init | generate | complete <initiative_NAME>
init: initialize an application name
generate: generate a registration link
complete: +need the PIN as argument + Token from the URL
We've to initialize our app environment with adminutils of mic-CHECK:
$ ./adminutils.py init initiative_name
This will asks for the keys present in the twitter page. the "Developer token" is used to identify the master account right now.
Now your app/initiative is ready, the next two operation need to be made for each supported
$ ./adminutils.py generate mic-check
https://api.twitter.com/oauth/authorize?oauth_token=PepFuJsbtKq6MwnEzlnk0YcJT4mMrijM
1414
every time is called 'adminutils generate app_name' it return two lines:
- the first contain the URL the supporter has to authenticated (and get the PIN)
- the second, is a random identifier internally associated with the URL
$ ./adminutils.py complete mic-check 5150781 1414
sniffjoke
Calling the adminutils with the PIN receiver by the user (5150781) and the associated random ID, cause the app to successful complete the registration (and print out the username)