Command to display FAQ entry links (and possibly content itself) from the main library's FAQ wiki page.

This can be displayed either as separate messages or as an integrated inline message, using inline keyboards for navigation.

Also, it would be helpful to allow a simple search functionality:
/faq mysql, /faq commands, etc.

FAQ entries would be fetched and parsed either via cron or GitHub webhook and then saved in the DB to cache results, preventing unnecessary requests to GitHub and speeding up the process.

Note: It will be important to keep the FAQ page 100% parsable at all times, as this command would fail otherwise.

It seems like htmlentities is breaking for some people's names, maybe filter_var($new_user->getFirstName(), FILTER_SANITIZE_SPECIAL_CHARS) would be better? Anyone with experience in this?

Unban me group in telegram @PHP_Telegram_Bot_Support

Seems like the welcome message deletion isn't working properly.

Probably makes sense to keep an array of welcome message IDs, in case a deletion doesn't work for whatever reason. Then every new member joining would trigger the deletion of all IDs in the array.

The /link command allows admins to easily save and post important links that contain great information, allowing it to be shared easily.
e.g. Direct link to the README file, a great article online explaining bots, etc.

Administration is done through the command itself:
e.g.

• /link add readme https://link.to/readme.md
• /link update readme https://new.link.to/readme.md
• /link delete readme

Just sending /link could open a list of all available links for easy access.
e.g.

$ /list
readme: https://link.to/readme.md
bots-explained: https://online.article/about/bots

Basically start implementing the GitHub webhook handler and send a message to the support group letting everyone know that a new version of the core library is available 🎉

The deletion of old welcome messages doesn't always work and invalid IDs stay stuck in the DB. Must figure out why this is happening and improve the cleanup procedure.

This is due to GitHub sending 2 different release events when a new release is made:

• "action": "created"
• "action": "published"

We should only send a message on published

Instead of just sending a welcome message each time a user joins, best only send one if the previous message wasn't already a welcome message.
Or, maybe just a much shorter one?

Also, we could delete the "User joined the group" status message.

What do you guys think?

@php-telegram-bot/developers @Hitmare @chuv1

When a User, who already had permission to send Messages, leaves the group and joins it again, they get their permissions removed.
The Bot does not give them the Button to accept the Rules anymore when issuing the Rules command, hence they dont get the permissions to send a Message again

hi can share new example dot env file ?

i cant use env example on this repository because cannot read variable on .env file

PHP file

require_once __DIR__ . '/vendor/autoload.php';
Dotenv::createUnsafeImmutable(__DIR__)->load();

$logging_paths['LOG_DIR'] = getenv('TG_LOGS_DIR');

print_r($logging_paths);

Response
array(1) { ["LOG_DIR"]=> string(19) "${TG_BASE_DIR}/logs" }

Because it's always nice to be able to react to a new release 🎉

We shouldn't allow other bots in support-channel, therefore wer should auto-kick every joining user with bot in username. Before kick we could send a message in channel that bots are not allowed, if someone really has bot in name but isn't a bot, we could send some username to the user like "if you aren't a bot, write @UserXY to get unbanned.

so we need a command to add the user to whitelist =)

Add the ability to create self-destructing messages, which can be used in different scenarios:

• Let new users know that they must agree to the rules within X minutes.
• Let users know about private-only commands when they try to execute them in the group (like /rules, /id or /donate)

Add a command (and possibly inline keyboard button for new version releases) to take advantage of Telegram Payments and allow users to donate directly.

This is a general issue to discuss the core commands of the support bot. For more specific details and discussion is necessary, a separate issue should be created for each command.

As this is totally a work-in-progress, new suggestions and ideas are more than welcome! 😇

Here a list of suggested commands so far:

• /ask: "Don't ask to ask, just ask"
• /wiki: Link to Wiki
• /latest: Latest Version with Link?
• /issue: "Please open an Issue for this: $link"
• /allsupporters (admin): Tags all Supporters in Group and request help/info
• /link "name": Add custom shortcut link (e.g. to a wiki page, a web article, etc.)
• /faq: Command to navigate the FAQ

And some passive bot chores:

• Allow linking to GitHub issues / PRs for the core library.
  gh#123 -> https://github.com/akalongman/php-telegram-bot/(issues|pulls)/123
• Send automatic notification on new release (with changelog even?) via GitHub webhook.

I'll start this issue to collect and discuss ideas for a Approval Survey for new Users , so we can sort out some of the non bot library questions