Go to file
2017-12-10 20:20:30 +01:00
appkeys implement basic auto-reblogging 2017-06-17 18:15:13 +02:00
blacklists extended sleep time 2017-06-25 21:51:19 +02:00
campaign patc designed a more readable sticker :D 2017-11-01 23:10:40 +01:00
goodlists change goodlist to regex patterns 2017-06-25 21:12:26 +02:00
guides invented a campaign 2017-10-11 22:22:53 +02:00
local@c8e9d7fd7a small fixes, 280 limit, wait 60 seconds 2017-11-24 18:11:35 +01:00
logs added empty logs folder 2017-07-20 22:37:34 +02:00
.gitignore gitignore problem 2017-11-24 18:13:18 +01:00
LICENSE add license 2017-10-17 00:14:57 +02:00
README.md added todo 2017-12-10 20:20:30 +01:00
retootbot.py small fixes, 280 limit, wait 60 seconds 2017-11-24 18:11:35 +01:00
retweetbot.py small fixes, 280 limit, wait 60 seconds 2017-11-24 18:11:35 +01:00
ticketfrei.cfg.example minor correction to ticketfrei.cfg.example 2017-10-14 19:54:57 +00:00
ticketfrei.py small fixes, 280 limit, wait 60 seconds 2017-11-24 18:11:35 +01:00
trigger.py retweetbot worx again! 2017-06-25 23:50:58 +02:00

Ticketfrei micro messaging bot

The functionality is simple: it retweets every tweet where it is mentioned.

This leads to a community which evolves around it; if you see ticket controllers, you tweet their location and mention the bot. The bot then retweets your tweet and others can read the info and think twice if they want to buy a ticket. If enough people, a critical mass, participate for the bot to become reliable, you have positive self-reinforcing dynamics.

There is one security hole: people could start mentioning the bot with useless information, turning it into a spammer. That's why it has to be maintained; if someone spams the bot, mute them and undo the retweet. So it won't retweet their future tweets and the useless retweet is deleted if someone tries to check if something was retweeted in the last hour or something.

Website: https://wiki.links-it.de/IT/Ticketfrei

Install

Install python and virtualenv with your favourite package manager. Create and activate virtualenv

$ virtualenv -p python2 .
$ . bin/activate

Install dependencies

$ pip install python-twitter pytoml requests Mastodon.py

Configure

$ cp ticketfrei.cfg.example ticketfrei.cfg
$ vim ticketfrei.cfg

Edit the account credentials, so your bot can use your accounts.

blacklisting

Also add the words to the goodlist, which you want to require. A tweet is only retweeted, if it contains at least one of them. If you want to RT everything, just add your account name.

There is also a blacklist, which you can use to automatically sort out malicious tweets. Be careful though, our filter can't read the intention with which a word was used. Maybe you wanted it there.

Note that atm the good- & blacklist are still outside of ticketfrei.cfg, in separate files. we will repare this soon.

screen

To keep the bots running when you are logged out of the shell, you can use screen:

sudo apt-get install screen 
echo "if [ -z "$STY" ]; then screen -RR; fi" >> ~/.bash_login
screen
python ticketfrei.py

To log out of the screen session, press "ctrl+a", and then "d".

ideas

  • You can only use the twitter API if you have confirmed a phone number and sacrificed a penguin in a blood ritual. So we should build it in a way that it uses the twitter web GUI. It's difficult, but maybe it works. We had another twitter bot that worked similarly, years ago: https://github.com/b3yond/twitter-bot
  • Build a tool that deletes wrong toots/tweets on both platforms, would work nicely with a web UI.
  • write the muted people to the db, to easily undo the mutes if necessary.

to do

Desktop/pycharm-community-2017.1.4/bin/pycharm.sh

  • Twitter: Crawl mentions
  • Mastodon: Crawl mentions
  • Write toots/tweets to database/log
  • Twitter: retweet people
  • Mastodon: boost people
  • Twitter: access the API
  • Web UI that lets you easily delete toots/tweets per db id and/or mute the tweet author
  • Write Bots as Classes to be easier implemented
  • Create extra Class for the filter
  • Put as much as possible into ticketfrei.cfg
  • Make both bots run on their own and next to each other
    • implement trigger class in retootbot
    • read config in retweetbot
  • put shutdown contact in ticketfrei.cfg
  • document what you have to configure if you setup the bot in another city
  • write a script to setup the bot easily. ask the admin for the necessary information
  • write a web interface, so we can host the bot for other cities - ppl don't have to know the command line
  • send shutdown notifications via mail