Discord proxy

[selfhoster1312]

This is the continuation of #109 and #48.

Apparently i couldn't push to @Wohlstand's branch on #109 so i had to open this PR here.

[selfhoster1312]

Ready for review/testing @poVoq @Wohlstand

[selfhoster1312]

This should be processed in the background instead of blocking the main thread. This is wrong and we should merge #114 first and not edit file download at all here.

[Wohlstand]

On my end I already merged that: Wohlstand@3043425

[Wohlstand]

I rebased this to the latest branch locally and tested on my end, it works for me. Additionally I applied the similar tweak to Telegram (just re-use of existing parameter and configuring bot instance with a custom client and proxied transomrt), otherwise the bridge was broken on my side, and I fixed it by adding the proxy here too. But, this tweak directly depends on this one.

[selfhoster1312]

I just rebased myself. Let me know if this branch works for you @Wohlstand and we can merge it.

Sorry in the rebase i lost your authorship information in the comment. If that's important to you, i can put it back somehow. Or you can open a new PR with your authorship :)

[Wohlstand]

@selfhoster1312, it's just matching the state at my production build, and it works. 👍

[selfhoster1312]

@selfhoster1312, it's just matching the state at my production build, and it works. 👍

Great, could you maybe confirm if you shut down the proxy the success message is still printed? We should move it right after b.c.Open right?

[Wohlstand]

Great, could you maybe confirm if you shut down the proxy the success message is still printed? We should move it right after b.c.Open right?

Of course it gets printed, because it's just a dumb print command, and it's supposed to print the success connection report after the connection function return or at the callback that confirms the connection was successfull.