-
Notifications
You must be signed in to change notification settings - Fork 40
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
The script just doesnt load somehow #12
Comments
You will need to 1 disable CSP - you can look for a CSP disabling extension on the chrome store. Also the document selectors have changed since the UI on CGPT has changed quite a bit.
|
Utilizing your script, I can only retrieve a response to the previous message, not the one currently being sent. |
I have made a few tweaks lately, mainly around queueing up multiple asynchronous calls and how it extracts Markdown. |
good job! Thank you for your assistance. However, have you conducted tests under GPT-4? I have consistently been unable to receive user responses. |
Yes - I use it almost daily. |
Is there an latest version can you share with me Thank you very much |
Hi @codisfy do you have a new script for the latest chatgpt.com interface by any chance? |
I have tried everything. changing the port, running as admin, disabling content security policy, using firefox edge chrome, etc.. but the script will not show any error in console, say anything in console or display any text. sometimes it randomly says error for a second or so but i cant find any pattern when that happens
edit: i found the error that sometimes pops up but only once then its gone for some time again doesnt matter what i do "Uncaught NS_ERROR_CONTENT_BLOCKED:"
edit2: the websocket works fine on other sites google etc just not on chatgpt
edit3: lol :) the problem seems to be that the script waits until the page is loaded but that never seems to happen according to the code to do that. i removed it and its kinda hacky and i dont get a response but the script loads in the first place
The text was updated successfully, but these errors were encountered: