You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Telegram for Android, when users attempt to connect to a new proxy from proxy channels, a pop-up displays the proxy’s information. One piece of information is the proxy’s Status and Ping, which indicates whether the proxy is still active. If it’s not, users should simply avoid trying to add or connect to the proxy.
Telegram Desktop does not have this feature, and it would be beneficial to add it.
Additional context
No response
The text was updated successfully, but these errors were encountered:
I'll agree. I think it means the output of information directly to the popup, so that you can easily find out the ping, without adding a proxy and opening the proxy settings. This is a user friendly feature.
@ilya-fedin, yes, I’m aware of that. However, what I’m suggesting is to display the ping in the pop-up even before adding the proxy to the user’s proxy list, exactly as @kr-ilya mentioned.
In the desktop version, we only have the ‘Server’ and ‘Port’ information in the pop-up. For me, having the ‘Ping’ information is more important than knowing the proxy’s ‘Server’ and ‘Port’ address when choosing a proxy to connect. It helps me avoid adding inactive proxies and keeps my proxy list organized.
Is your feature request related to a problem?
no
Describe the solution you'd like
Describe alternatives you've considered
In Telegram for Android, when users attempt to connect to a new proxy from proxy channels, a pop-up displays the proxy’s information. One piece of information is the proxy’s Status and Ping, which indicates whether the proxy is still active. If it’s not, users should simply avoid trying to add or connect to the proxy.
Telegram Desktop does not have this feature, and it would be beneficial to add it.
Additional context
No response
The text was updated successfully, but these errors were encountered: