vldc-hq / vldc-bot Goto Github PK

remove all related ci cmd

For ppl who don't know what smile mode is

/uwu

• Detect new users in the chat
• Send the message with a mention for each new user and ask for a replay
• Wait for the answer
• Ban user if bot will not get a reply
• Post some funny stuff
• Post a message with a ban confirming

Plus:

• move all globals into config
• refactoring
• move filters to external file
• update readme (put more vldc stuff)
• rename repo to vldc_bot
• replace smile_bot by vldc_bot in the VLDC chat

The main problem right meaw than once kicked user can't retry to join the chat.

since-mode is counting and showing numbers of days since last mentation of our favorite themes.

It may be two option probably: catch themes buzz words in the messages, or use /since_ command.

For example:

user: ну вообще, ООП решает эту проблему
vldc_bot: This is are 0 days since ООП discussion

or

user: современный php – не такой плохой язык, им вполне можно пользоваться
user2: /since_php
vldc_bot: This is are 2 days since Современный ПеХеПе discussion

For these two options, we need the preselected list of our favorite themes.
Alternativly, we may allow users creating they owns since-words, like:

user: да макось вообще не позволяет ничего кастомизировать, толи дело арч
user2: /since бест ОС евер
vldc_bot: This is are 0 days since бест ОС евер discussion

В таком случае можно добавить вывод всех since за все время:

user: /since_all
vldc_bot:
ООП: 0 days
Современный ПеХеПе: 20 days
бест ОС евер: 2 days

Obviously, we need some persistent storage for this kind of stuff. Let's say it will be mongo

• add skill
• add adapter for persistent storage
  • add compose to run bot + storage
  • add .env file for configuration compose (token, chat name, mongo stuff)
  • add mongo into compose (everything become better with mongo)
  • add mongo driver to requirements
  • some way to backups? neh
• update docs | readme | cmd info in the come skill
• since cmd
• since_all cmd

Need to update /still command: replace 2k19 to 2k20

X-Mas is so near! The current leaderboard created by @C-Pro link: https://adventofcode.com/2019/leaderboard/private/view/458538

I believe bot should post it for /tree command

• a few buttons?
• replace button by reply back?

Just reply pong for ping command, and remove both messages after a few seconds.

To be sure bot is up

u1: да там надо шоткат из 12 кнопок добавить и все будет работать
u2: /still вим настраивать
bot: Вот бы сейчас вим настраивать в 2k19 LULW

python-telegram-bot/python-telegram-bot#855

Remove original /still smth message after bot posted answer

See #34

• collect all logs
• map it with users
• find the bots
• find the flooders 🍭

Add the list of strong \ abusive words to immediately removing msg with them. For example:

user: доброго времени суток, коллеги
vldc_bot: коллеги? no way!
# remove the msg

• add skill
• update docs and core skill description
• appruve black-list

Why choose Python for literally anything in 2k19? It's slow, unsafe, have poor ergonomics and just not good enough for modern development.

Have you heard about Rust? Rust is a statically typed language with strong safety guarantees, native performance and zero-overhead abstractions. It's super-duper cool, makes your code bugs-free and super fast. For free! And it's super popular and will bring you tens and hundreds of new contributors!

For some reason, the built-in message is not shown in the VLDC chat

Every mode should have modeName_on and modeName_off handlers, to change the state of mode by admins, without restart container.

It should be decorator for add_MODENAME_handlers.

Need to duplicate all bots messages in two languages. For some reasons, someone from the chat believes it will be a good option for a chat in Russian, idk. And, maybe new users will read bots messages more carefully.

@C-Pro I believe you know much more about this.

• main points
  • ru
  • en
• md
• raw txt for posting CoC by bot on demand (or I may just post the link to GitHub page with CoC)

I believe barrel should be loaded randomly every turn

To make more attention for bots message.

I believe it should be a custom Tg keyboard with all subjects as buttons.
User may use /since cmd, and then only this user will see the keyboard, and make a choice, wich one subject must be updated.

Only admins can add subjects. Let's say by /since_add cmd.

And we need some anti-flood protection I guess.

@C-Pro wtf???

458538-e2a0698b

See: https://core.telegram.org/bots/api#answercallbackquery

We need to add /soon, /events and /add_event commands.

For admins: /add_event will add event date, links and short description of the event.

For all:

• /soon – show info about the soonest event
• /events – show list of the last N events

As usual:

• add skill with new skill-group number
• add description of new command into core skill
• mongo as storage for events

Temporarily disable any non-essential features, like /uwu, /still etc., sometimes there's too much junk.

Suggested behaviours:

• ON/OFF. Like /smile or /since.
• Countdown. All minor features will be disabled for reasonable amount of time (like 10m or so).

@C-Pro could you add some automation for deployment each new version?

After each push into master Docker Hub will build the new latest version on the container. And, looks like we may just pull new container, but sometimes we are updating the docker-compose (for adding new services for example), and at this case, we need more smartest deploy.

We may user GitHub Actions for this purpose, I guess. So, I believe it may look like:

• push to master -> check (stylelints, tests, mypy, etc)
• DokcerHub build new Image (wait for it)
• if checks are the green and new image is ready: deploy a new version:

@lamak now it is your horse 🐴

• get GROUP_CHAT_ID from ENV
• add global VLDC_ONLY filter for all handlers

Add roll /roll support. This is command for regular users only (not for admins).

u1: /roll
bot: miss!
u2: /roll
bot: miss!
u1: /roll
bot: Boom! Mute for u1 for 24 hours

Note: chance to being shoot is 1/6

Let's use come GitHub actions magic!
What we should add to our quality gate?

build:

• tests
• mypy
• flake8

upd: for now, I'll restart container manually (meh)

/version should print version\build code and probably hostname

Something like /mute @C-Pro 90 for muting (removing all messages) by user @C-Pro during 90 minutes

Add "cleanup" decorator for modes and commands.

This decorator should take a number of seconds as a parameter, and provide the removing affected messages (user cmd, bot answers) after a while.

For example:

@cleanup(600)
def add_roll(upd: Updater, handlers_group: int):
    logger.info("registering roll handlers")
    dp = upd.dispatcher
    dp.add_handler(CommandHandler("roll", roll), handlers_group)

should looks in the chat like:

u1: /roll
bot: 💥 boom! u 😵 [8h mute]
u2: лол
u3: кек
u3: чебурек

after 10 minutes messages u1: /roll and bot: 💥 boom! u 😵 [8h mute] should be removed

If the user presses the button, we don't need to show a greeting message anymore

• remove greeting message if a new user is answered
• remove greeting message after 60 minutes if a new user is a bot