discreeetly is perfect for when you don't want to create a burner Twitter account to detach yourself from a high-profile government leak, or for when you just want to complain abour your boss. It allows users to write tweets that will be posted to a Twitter account, without the need for them to register for anything or give over any identifying information. Sometimes you just can't be the first person to tweet something out, so let discreeetly take the heat! This code was running at https://www.discreeetly.com until Twitter shut it down due to it violating their TOS. I have left the source code here for reference.
The submitter's IP is immediately hashed and the hash is saved with each submission so that the app can limit the amount of submissions that an IP can have queued up at any one time. The maximum amount of submissions you choose to allow an IP to queue is a setting in the config.php. The user's real IP is never stored in the database.
All of the submissions are moderated before they're actually tweeted out by the associated Twitter account. A human gets an opportunity to not let the app tweet out anything that could get the account shut down for violating Twitter's terms of service (although, I imagine this entire thing is a violation of Twitter's terms of service). It's up to the human on what they'll let through. The human will receive a Twitter DM for each of the submissions and the app will wait for the moderator to reply with a yes/no response, and then handle accordingly.
Run that composer install in the /html folder. A popular Twitter API wrapper package is required.
Create a new app with your Twitter account at apps.twitter.com, and when creating an access tokens make sure to include the option of allowing it to read/write direct messages. Copy the two app consumers keys and the two access token and paste them in to the config.php
Also, go set the rest of values in here.
Run the schema.sql file in your MySQL/MariaDB environment. In order to support emojis, you need to make sure your database supports utf8mb4 character encoding. If yours doesn't, the schema.sql will generate errors when you run it.
There are two files in the /cron directory that need to be scheduled to execute as often as possible. These scripts are what look for approved submissions that are waiting in the queue to be tweeted, and they look for new DMs from the moderator to act on.
If you are running this with an SSL certificate (and you should), make sure you set the following php.ini directives as follows:
session.cookie_http=1session.use_only_cookies=1session.cookie_secure=1
- Simple API for allowing programatic submissions
- Adjusting moderation to be for one tweet at a time.
- Allow users to create anonymous user names/password to keep track of the tweets they've sent out in the past, keep track of faves and replies of the tweets they've submitted, and allow them to send out reply tweets threaded to the original.
- Allowing the submission to be a reply tweet, to an existing tweet.
Send me a tweet @varwwwhtml, or email me: tom AT itsmetomsmith DOT com