puddingbot / pudding-bot Goto Github PK

Come up with a consistent scheme that also denotes Alpha, Beta and RC versions.

Move code out of main.py into separate modules, and move modules into subfolders (bot, user, group, fun).

Bot token was accidentally exposed in main.py.

Resolution:

• Revoke token and generate a new one.
• Remove comment line with old, now non-functional token.
• Implement a mechanism to prevent accidentally sharing credentials in the future.
• Replace file_id in about.py.
  • Use pudding-bot-assets instead.

Implement a /sticker command to display a sticker's ID and the set it belongs to.

Implement a /nosticker command to disable stickers or sticker sets.

/sticker

• Add and register command handler.
  • Command list scope: All
• Add sticker ID.
• Add stickerset the sticker belongs to.

/nosticker

• Add and register command handler.
  • Command list scope: Admins & Owner
• Args: Solo to disable one sticker instead of entire set.

Ship /sticker command mentioned in #2 early, as part of 0.0.6.

Implement a beautiful, comprehensive and informative in-bot help.

• Add and register command handler.

  • Should be on top of commands list for regular users/DM and further down for admins/owner — the latter are pointed towards it through /start anyways and seeing the /help on top might get in the way of performing their regular admin duties).

• Add short intro text.

• Add Buttons.

• Add links to code repository and online documentation.

• Add links to support/update channels.

• Add donation link.

Group configuration, filters, stickers, Welcome/Goodbye messages and other persistent data need to be stored in a database.

Viable options are PickleDB and MongoDB, with a preference for the latter.

See #12

https://docs.github.com/en/code-security/security-advisories/about-github-security-advisories

Provide commands for DM, user, admin and owner scopes.

• Refresh Commands and AdminCommands
• Add DmCommands and OwnerCommands
• Expose OwnerCommands by querying for group owner during new_chat_members event when member.username matches "PuddingBot"
  • Don't hardcode the bot username. Put it in config.py.
    • Could probably query for bot's username, too. But let's save that API call.

Add exception handling code for network errors.
Restore connection gracefully on timeout/disconnect.

Create a style guide.

• Add linter.
• Decide whether or not to use newline EOF.
• Prepend license header to top of every source file.
• Author style guide intro for developer documentation.

Present new or returning user with an introductory onboarding message
and a straight-forward way to add the bot to their group (via inline button).

Should be scoped to DM-only.

Code like this would cut back on complexity/custom implementations and improve the overall clarity of the source code @app.on_message(filters.chat(TARGET) & filters.new_chat_members)

Reason PTB doesn't have filter decorators:

python-telegram-bot/python-telegram-bot#899

As an alternative to Pyrogram, consider contributing to PTB-Contrib

A third option might be to create a library specifically for @PuddingBot's needs. A PuddingLib.