bot | rael.io

tgfwdbot

Sun, 09 Jul 2017 11:23:56 +0200

Bot to forward messages between supergroups and private chats, to allow talking in Telegram supergroups when banned.

Why

Sometimes, due to trolls reporters, users can be banned from any Telegram supergroup, not only the one where reported. With this bot, users will be able to participate in specific groups through the bot.

This bot can be added to the group, identified by TELEGRAM_GROUP_ID, and will:

Forward any message from the Group to the private conversation with the banned user
Forward any message from the private conversation with the banned user to the Group

The admins of the groups where the bot is a member will decide if the allows the banned users to participate or not.

Disclaimer

This bot is not intended to be a tool for spammers and malicious users to bypass Telegram bans. The purpose is to allow users to interact in the groups with the authorization of the group admins when globally banned from supergroups due to troll reportings.

Notes

Gopher art from ashleymcnamara/gophers.

PyBot

Thu, 02 Mar 2017 11:23:56 +0200

pybot

Wrapper for python-telegram-bot to allow dynamic plug-in architecture, an attempt to make python-telegram-bot more hubottish.

Execution flow

bin/pybot starts the bot with the selected adapter and using the configuration options defined in conf/pybot.conf or the command-line arguments.
The selected adapter receives the message and sends it to the brain.py.
The brain.py loads in runtime all the .py files in the ./memory folder each time and try to execute a defined method, for example hear(message.text).
Each module in ./memory with that method returns a response, the brain.py sends it to the pybot.py and it sends the response back to the chat.

As the methods are dynamically loaded, you can edit and add the files in ./memory without need to restart pybot.py, and they will be reloaded on the next message. Overkill but funny.

Makefile targets

usage: Show this help
setup-venv: Setup virtualenv
lint: Run code linter to check code style
telegram: Run pybot with the telegram adapter
docker-build: Build the docker image for running pybot
docker-telegram: Run with telegram adapter in the docker container
docker-lint: Run pep8 in the docker container
docker-clean: Remove the docker image

Execution example

make docker-telegram

docker run -it --rm --name pybot -v /Users/rael/Code/python/pybot:/usr/src/pybot -w /usr/src/pybot 'pybot' bin/pybot telegram
Starting pybot using conf token file. CTRL-C to quit.
2017-04-17 07:35:54,392 - pybot.interfaces.telegram - INFO - Bot raelbot up and ready!
2017-04-17 07:36:39,371 - pybot.brain - INFO - 116133952, Hello world!, 53693428, 2017-04-17 07:36:39,"53693428";

Contributing

Contributions of all sizes are welcome.

Attributions

Header image from python-telegram-bot.org

License

You may copy, distribute and modify the software provided that modifications are described and licensed for free under GNU General Public License v3.0. Derivatives works (including modifications or anything statically linked to the library) can only be redistributed under LGPL-3, but applications that use the library don’t have to be.

Hubot Raelbot

Sun, 16 Aug 2015 11:23:56 +0200

raelbot is a chat bot built on the Hubot framework.

Running raelbot Locally

You can test your hubot by running the following, however some plugins will not behave as expected unless the environment variables they rely upon have been set.

You can start raelbot locally by running:

% bin/hubot

You’ll see some start up output and a prompt:

[Sat Feb 28 2015 12:38:27 GMT+0000 (GMT)] INFO Using default redis on localhost:6379
raelbot>

Then you can interact with raelbot by typing raelbot help.

raelbot> raelbot help
raelbot help - Displays all of the help commands that raelbot knows about.
...

Persistence

If you are going to use the hubot-redis-brain package (strongly suggested), you will need to add the Redis to Go addon on Heroku which requires a verified account or you can create an account at Redis to Go and manually set the REDISTOGO_URL variable.

% heroku config:add REDISTOGO_URL="..."

If you don’t need any persistence feel free to remove the hubot-redis-brain from external-scripts.json and you don’t need to worry about redis at all.

Adapters

Adapters are the interface to the service you want your hubot to run on, such as Campfire or IRC. There are a number of third party adapters that the community have contributed. Check Hubot Adapters for the available ones.

If you would like to run a non-Campfire or shell adapter you will need to add the adapter package as a dependency to the package.json file in the dependencies section.

Once you’ve added the dependency with npm install --save to install it you can then run hubot with the adapter.

% bin/hubot -a <adapter>

Where <adapter> is the name of your adapter without the hubot- prefix.

Deploying to UNIX or Windows

If you would like to deploy to either a UNIX operating system or Windows. Please check out the deploying hubot onto UNIX and deploying hubot onto Windows wiki pages.