This is a Telegram bot which uses Markov chains to learn how to speak from the messages of other users. It can answer with text messages, but also stickers, animations and audio messages. These are the available commands:
fioriktos - Talk
sticker - Send a sticker
gif - Send a gif
audio - Send an audio
torrent - Automatic replies
enablelearning - Enable learning
disablelearning - Disable learning
thanos - Halve the memory of this chat
bof - Best of Fioriktos
gdpr - Privacy stuff
There are a number of extra commands that can be issued through /gdpr, namely:
/gdpr download: Download all the data for the current chat in a text file, so that a user can inspect them./gdpr delete: Erase the entire content of the current chat in one shot. Be careful when using this function: the deletion of your data will happen without asking confirmation and is not reversible, so do it wisely./gdpr flag: Remove a specific sticker or gif from Fioriktos' memory. Let's say some troll publishes a porn gif in your group. Instead of deleting it, reply to it with/gdpr flag, this way the gif will be removed from the bot's memory and Fioriktos won't publish it again later. If the bot has administrator rights, it will also care about deleting the message from group history. The operation can be undone with/gdpr unflag./gdpr tx: If you want to transfer the data stored by Fioriktos from one chat to another, first send this command in the source chat. The bot will answer with a code that must be sent in the target chat to complete the transfer. The code will be available for up to ten minutes (five minutes on average) and it is something like/gdpr rx DEADBEEF.
Since this bot has access to private messages of Telegram group users, it has been designed with a high focus on openness and transparency to guarantee that private data are not used in an improper way. The simple act of making the source code public is already a great step towards this goal, a step which has not been made by other bots similar to Fioriktos.
Fioriktos is storing a set of data for each chat it is added in. These data consist of:
- Chat ID
- Sent words
- Sent stickers
- Sent gifs
It does not store any information about users, such as user ID, username, profile picture et cetera. Keep in mind that Fioriktos is not storing the whole messages sent by users (that would be extremely unpleasant), but only the single words composing them. This is obviously needed to implement Markov chains and generate new messages.
The bot is deployed on Heroku and the learnt models are stored on an Amazon S3 bucket.
No. When Fioriktos is removed from a group, the relative data will be automatically deleted after 90 days of inactivity, unless the bot is added to the group again.
As I said, Fioriktos is not storing the whole messages, but only the words composing them, so it is not technically possible to recover the original messages. Anyway, I would like to remark that, whenever you use a Telegram bot which has access to all messages you send, you are accepting the risk that the bot owner will use your data unfairly. If you use a bot which is closed source and you do not know where it is deployed, how it works, what data it stores and even who are the people managing it, nothing can guarantee that the unknown developers are not storing all your conversations in some hidden server on the Pacific Islands or worse they are collecting your pictures and videos to feed some deepfake algorithm. Every bot which both implements Markov chains and is closed source could potentially do this without our knowledge nor permission (I am thinking about a very famous one). With Fioriktos, you know exactly how it works (see the code ;) ), where it is deployed, what it stores and who is developing it (hello there!). In this scenario, I feel much more secure.
Of course you can, and I even encourage people to do so. If you want to create a copy of Fioriktos, the easiest way is to replicate its exact working environment. To do this, you need:
- A Telegram account
- A GitHub account
- A Heroku account
- An Amazon Web Services account
Then you have to follow these steps:
- In Telegram, create your new bot through @BotFather. You can freely choose its name and profile picture, while as a list of commands, copy-paste the one at the top of this page.
- In GitHub, create a new repository by forking this project.
- In Amazon Web Services, go to Simple Storage Service (S3) and create a new bucket. NOTE: this is easier said than done. Creating and configuring an account on AWS is not straightforward. If you need more details on how to do it, look for a video tutorial on YouTube by some smart Indian guy. They are better than official documentation. At the end of this process, you will have many pieces of information: the AWS Access Key, the AWS Secret Access Key, the region where you created the bucket and the bucket name. You need all these data in the next step.
- In Heroku, create a new project and go to the Settings tab. Here you can manage Config Vars, which are nothing else than a list of key-value pairs. For the correct working of your bot, you need to set these config vars:
BOT_TOKEN= the token of your Telegram bot (you can get it from @BotFather)
ADMIN= your Telegram user ID (you can get it from @userinfobot)
HEROKU_APP_NAME= the name of your Heroku project
AWS_ACCESS_KEY_ID= your AWS Access Key
AWS_SECRET_ACCESS_KEY= your AWS Secret Key
REGION_NAME= the AWS region where you created your bucket
S3_BUCKET_NAME= the name of the bucket
Then, under the Deploy tab, you can connect the GitHub repository of your bot to Heroku and deploy it, making it effectively operational on the web. By clicking on More > View logs, you can watch the logs generated by your application and check if everything is alright or if there are some errors.
Note that Fioriktos can be configured in two modes: FullRam and ThreeLevelCache. The first one stores all data in a single giant file which is entirely loaded in RAM when the bot starts up and it is regularly updated. The second one stores data in a separate file for each chat and only the current active ones are kept in RAM. The former version is recommended for a low-traffic bot, since it also requires fewer requests to S3 and is cheaper as a consequence. The latter is adviced when dealing with a higher traffic, when keeping the whole database in RAM is not sustainable. You can decide which version to adopt by editing the call to create_memory_manager inside the main function.
At this point, you have created a working copy of Fioriktos. Now you can make all changes you desire to your GitHub fork and deploy those changes to Heroku at any time. Have fun!
If you'd like to support the project, please contribute. This will be helpful to keep the bot up and running while being used in hundreds of groups.
Thanks for your support!