Clarification on pm_active when using drop_pending_updates

[atcoun]

Hi!

I’m reviewing the template and noticed that pm_active is updated exclusively via
my_chat_member handlers, while at startup the bot calls
delete_webhook(drop_pending_updates=True).

As far as I understand, this can permanently drop my_chat_member updates that were
sent while the bot was offline, which may leave pm_active in a stale state.

Is this an intentional trade-off in the template design, or is pm_active not meant
to be treated as a reliable signal for direct messaging logic?

I just want to make sure I’m using the template as intended.

[andrew000]

pm_active is not intended to be used as a reliable signal for direct messaging logic in this template, but you can make it reliable.

Instead of dropping updates - u can filter+process old my_chat_member updates before starting bot (I didn't found proper way to do that, but I think it's possible) and update pm_active for users.