Warning
Twitter announced that free API usage will be stopped since 2023/02/09.
While this project could instead rely on libraries that don't use the official API, I don't really think such...ehh... "illegal" libraries can be used consistently. If the platform itself does not encourage the development of API ecology, we can only respect its choice.
It just so happens that I hit a development problem and the solution I could learn and managed was inelegant and difficult to implement.
So... that's it. This project ceased development.
____ _ ____
,___|____\____________|_|____/____|____________________
|___|_|_)_|_|_|_|_'__\|___|_|_|___|_|_|_|_'__\__[____] ""-,___..--=====
| __/| |_| | | | | |_ | |_| | |_| | | | | \\_____/ "" |
|_| \__,_|_| |_|\__| \____|\__,_|_| |_| [ ))"---------..__|
You can use this tool to do some boring Twitter account management (such as automatically select and block users from a source like a tweet's likes, your follower...), then you can free up your time for other things.
This tool was originally conceived as a configurable automatic Twitter account blocker. What could be a better name for it than the Punt Gun, a special hunting weapon used to kill a large number of waterfowl in one shot. But that type of gun is a huge threat to the natural environment, and fortunately this tool only inherits the meaning of its origin, even to the benefit of the platform environment (or at least to its users).
This tool needs to be installed with the Python application management tool, no separate executable file is distributed, sorry for the inconvenience. The most convenient way to install (and update in the future) this tool is with the help of pipx, which is a handy Python application management tool. Install it first, then run:
pipx install puntgun
Or your can install this tool via pip which is installed with Python. This tool requires Python version 3.10 or above. Install Python if you haven't installed or your Python version not meet the required, then run:
python -m pip install -U puntgun
For users unfamiliar with the command line interface, this tool is a cross-platform command line tool, which means you need to use it in your Windows Command-line shell or Apple Mac Terminal or any other terminal.
First you need a "Twitter Dev OAuth App API" to enable the tool, with this we can request the developer APIs provided by Twitter. Run the command below to let the tool interactively guide you register one on Twitter platform for free. For more information, read documentation about available commands.
puntgun gen secrets
Then you need a Plan Configuration file to instruct what the tool will do for you, run the command below to generate an example file. For more information about plan configuration, read the documentation.
puntgun gen example
Now you can start the tool with your plan file with:
puntgun fire
If the tool doesn't exit quickly due to configuration errors (with red error logs printed pointing out what's wrong), you can leave the terminal (window) open and move on to other things. The tool will generate a report file (and log file) during runtime, which you can view later to see what happened.
For more information on usage, see the documentation website.
Essentially we make the tool a third-party application that can access the Twitter platform by registering a credential (a pair of secret token) with your Twitter account and then using your Twitter account to authorize this tool (the credential you registered from Twitter, in fact) to operate your account (for blocking users, etc.).
First, this tool's performance is depending on the complexity of plan configuration you set which you can control. And what you can't control is that your total API query volume is limited by Twitter, meanwhile the API have different rate limits with different permissions on different endpoints. These limits can sometimes be very impactful on execution speed, such as only fifty block API query is allowed for every fifteen minutes.
What's more, you can only search for last 7 days tweets (using "search/recent" API) with Essential Twitter API access, and query string length is limited up to 512.
Currently, we use the RSA4096 with the cryptographic library Cryptography for processing secrets to prevent them being saved into configuration file in plaintext format. For implementation details, check this source code file. For Cryptography's security limitation, check this documentation.
When the tool is running, the secrets will stay inside a client object of the Twitter API client library Tweepy, and it seems that they are stored as plaintext string. As it can't be garbage collected while we're invoking this client instance all the time when running, I guess we can't prevent secrets from a memory dump attack or something similar.
This project is open sourced under MIT license.