Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bing Chat's Edge browser requirement can be (for now) worked around by setting Edge's UserAgent #2

Open
replikvlt opened this issue Jun 2, 2023 · 3 comments

Comments

@replikvlt
Copy link

therefore it should be possible to use other browsers after setting UserAgent to Edge.

It can be set using Playwright's emulation

@replikvlt
Copy link
Author

Example userAgent that can be used is: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36 Edg/113.0.1774.42'

@ryanhlewis
Copy link
Owner

ryanhlewis commented Jun 2, 2023

Hey @replikvlt

Thanks for your pull request and your issue. I'll look into both as soon as I can.

I'm not enjoying the fixed 7 second wait you set on your pull request, and I want to try to make a fix for that before merging up, but your other changes in regard to handling "new chat" is wonderful.

As for this issue, do you think we should switch to a Chrome approach? Are there benefits to Selenium versus Playwright?
I've seen benchmarks that indicate the opposite.

Edge is built-in (and practically uninstallable) on all Windows machines, so I feel that although it seems a little strange to use Edge for some people, it's something that everyone has, regardless of whether you wanted it or not.

@replikvlt
Copy link
Author

I didn't say anything about Selenium and I'm not familiar with it. Playwright is good enough I think, and it also supports not just Edge browser but other browsers.

The 7 second wait is bad solution, but I already explained it in the PR commit description, was just a quick hack to test other changes.

I think support for other browser is not mandatory for this project, however I think its possible that this project may be hosted on other OS'es such as Linux, and not all of them support Edge browser and diversity in this regard may be nice. As long as the check for Edge browser is simple UserAgent check, it seems easy to be 'fooled'. It may become hard or outright impossible in future if they will implement other check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants