zeroone2numeral2 / bbr-staff-bot Goto Github PK

[events]

• chat_id

[webcal]

• api_key
• legal_subcal_name
• free_subcal_name
• other_subcal_name

Event model:

• chat_id PK
• message_id PK
• event_id (int)
• title
• start_date
• end_date
• region
• event_type (legal/free/other)
• canceled
• message_text
• message_date
• message_edit_date
• media_group_id
• media_file_id
• media_file_unique_id
• created_on
• updated_on
• message_json

related to #21

Manual commands that can be used in reply to any user message to accept/refuse the user

we need to keep track of the message id containing the invite link

also, revoke the invite link if we generated it per-user (see User model properties)

When you start typing something, the bot keyboard is hidden and users might have difficulties to access it again

An alternative solution would be sending a message with a ReplyKeyboardMarkup every time the user sends something, so the keyboard is displayed again

We should create a module where filters that handle messages in specific chats (staff chat, users chat) are initialized and updated when needed. In this way, messages that do not belong to these gtroups will no be handled by their special handlers because they will not pass filters

Allows to add a "reason"/"note" that will be logged to the staff message & log message

Assicurarsi che solo utenti autorizzati possano usare il comando

New fields:

• application_status: default to None, True if application was sent and accepted, False if it was rejected
• application_received_on
• application_evaluated_on
• application_evaluated_by
• is_member: None
• is_member_chat_id: the chat id we checked to decide whether the user is a chat member or not
• is_member_updated_on: when we last updated the is_member field (on user join/leave)

Shortcut methods:
.approved() -> application_status or is_member are true

only if they are not a super admin

Also save whether the user blocked the bot or not (new User model property)

Todos:

• command to get the message with an inline button prompting the user to select another users with switch_inline_query_chosen_chat (also allow group chats?)
• inline mode should be supported. prompt the user to send their invitation link
• command to ban invitations from an user (if their link is used, warn the user that the invite link they used is not valid)
• /ban should also ban invitations from that user
• the log chat message should show a special field with the inviter

Will add a line to the staff message & post a message to the log chat

Requires two taps

Quando vengono rimossi da admin, modifica anche il loro scope

if so, what to do with this info?

We should keep a stack of invite links (new InviteLink db model) that should be used to let people join the users chat: every n hours, the bot revokes the previously generated invite link (selecting all the links in the db and try to revoke those who have revoked == false(), and generates a new one.
This newly generated invite link might be set to expire directly at api request-level. In this case we don't need to revoke it (maybe try to test what happens when we try to revoke an expired link).

When an user is accepted, send them a message with an inline button that says "tap here to get the invite link". When tapped, the reply markup is edited with the url button containing the most recent link. This "tap to get the link" behavior allows to avoid an user tapping on an expired link, because they saw the message many hours later after we sent it.

We might decide to select an url from the invite links stash just when generating a one-time url fails

We would need to save also every message sent in the admins chat

Mark the user as "did not apply yet", and treat every message from the user as a new user message

Just log or also send to the user?

also warn them when they still have two messages left to send at max