Use the ws properties and User-Agent header provided during client initialization for RemoteAuth #378
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@connerdassen RemoteAuth used in |
|
Discord does care about these headers for my purpose, they are used to identify the client type shown in the devices list that is currently in beta |
|
Client.QRLogin() also still works fine with my edits |
|
I've made another commit for QRLogin to use the same user agent and ws properties as well, before it was still using a random UA and default ws properties. |
|
nice ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With these changes RemoteAuth will use the same User-Agent header and WS properties as were provided in the Client options during initialization instead of picking a random User-Agent and using default WS properties.