Open amijafi opened 2 months ago
I haven't seen this problem myself, and I haven't heard anyone else complain. I'll keep the issue open so others can find it.
The invizible app developer (which uses tor) mentioned the same issue for his app and telegram but said that the problem was from telegram and the way it utilizes socks5 but he made some changes in his app to make telegram full compatible , i've no more technical details
The invizible app developer (which uses tor) mentioned the same issue for his app and telegram but said that the problem was from telegram and the way it utilizes socks5 but he made some changes in his app to make telegram full compatible , i've no more technical details
Do you have a link to where this is mentioned? I'd like to read it myself, perhaps I can figure out the problem.
Check the post comments , the app developer mentioned sth about battery power saving
https://github.com/bepass-org/warp-plus/assets/125953876/da645e0f-7619-4da0-b06c-0a608683a118
When using the proxy 127.0.0.1:8086 directly in telegram, telegram constantly switches between connecting and connected to proxy status like for 20 times before reaching stability for a few seconds
But when using an intermediate proxy app like nekobox to redirect to another port like 2080, it works perfect
Changing the default bind address in warp-plus does not fix the problem , using intermediate proxy app seems necessary for me