>>> telegram.Bot()

15 July 2026 22:41

Thanks! I'll definitely check out ptbcontrib once I modularize this a bit more.

>>> telegram.Bot()

15 July 2026 19:28

Hi! I had this exact issue, so I built a mini-framework for my own PTB projects. It has Postgres/Redis adapters, repository pattern, and a throttling middleware. It's fully modular, so you can easily add your own middlewares or repos to it.

I keep it in a private repo. If you want access to it, hit me up in DMs.

>>> telegram.Bot()

14 July 2026 20:57

I can't be friends with you, why?

>>> telegram.Bot()

14 July 2026 20:00

I couldn't find any official announcements for this. Is it sth new?

>>> telegram.Bot()

14 July 2026 15:31

Sometimes telegram is slow at replying so the pool connection get saturated, and it raises the error that the connection pool is full.

How are you dealing with that?

>>> telegram.Bot()

14 July 2026 15:29

Oh, does not vanish at view, but after a bit of time?

>>> telegram.Bot()

14 July 2026 15:26

No. PTB only provides an interface to build your own rate limiter and a minimal effort implementation of it, and you have to explicitly include it in your Application for it to take effect. Said minimal effort implementation does have a kwarg that allows you to specify the number of retries after getting a RetryAfter error, but even that defaults to 0 (no retries)

>>> telegram.Bot()

14 July 2026 15:23

"In this case, the message may be delivered across multiple active client applications of the user, but is regardless not guaranteed to be delivered to any of them."

>>> telegram.Bot()

14 July 2026 15:22

I wonder what this means: "It is not guaranteed that the ephemeral message will be received, especially if the user is offline."

>>> telegram.Bot()

14 July 2026 15:18

No in groups where they are admins, they can just send them

>>> telegram.Bot()

14 July 2026 15:14

They literally implemented them

>>> telegram.Bot()

14 July 2026 15:07

Telegram don't want this type of messages

>>> telegram.Bot()

14 July 2026 15:00

Can you please help me?

>>> telegram.Bot()

14 July 2026 14:32

Wiki of python-telegram-bot - Category Notable Features
Bot API Forward Compatiblity

>>> telegram.Bot()

14 July 2026 14:24

When will ptb support Ephemeral Messages ?

>>> telegram.Bot()

15 July 2026 20:06

We have a ptbcontrib repo if you want to contribuite to the community

>>> telegram.Bot()

15 July 2026 10:03

Ohk, so we have to do that. understood

>>> telegram.Bot()

14 July 2026 20:06

apparently it was only sent to winners of a few contests, it's not public yet

>>> telegram.Bot()

14 July 2026 15:45

scale up or throttle down

>>> telegram.Bot()

14 July 2026 15:29

Thats my understanding

>>> telegram.Bot()

14 July 2026 15:28

Well instead of the recative one, where a user likely is still looking at that specific client, the other one needs to be send to any in the hope it reaches a user and they actually look at it before it vanishes

>>> telegram.Bot()

14 July 2026 15:23

This i bonkers, what does it meeeean

>>> telegram.Bot()

14 July 2026 15:22

That they might get it, might not. Percentages aren't clear

>>> telegram.Bot()

14 July 2026 15:20

I think if bot hit the rate limits, then PTB retry sending it ? Isn't that written in docs ? Or something else they mean here - https://github.com/python-telegram-bot/python-telegram-bot/wiki/Avoiding-flood-limits#ptbs-rate-limiting-mechanism

>>> telegram.Bot()

14 July 2026 15:15

But only when user interact with bot

>>> telegram.Bot()

14 July 2026 15:14

They say disappearing message can be risky for safety reasons

>>> telegram.Bot()

14 July 2026 15:01

In the future for sure

>>> telegram.Bot()

14 July 2026 14:36

It is already supported for interactions message but not 1st hand due to privacy and safety concern 😕

>>> telegram.Bot()

14 July 2026 14:32

We don't give out ETAs but you can use our forward API

>>> telegram.Bot()

14 July 2026 13:04

Do we have to develop our own counter ?