-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
added the addon and uhhhhhhh #975
Comments
happening to all firefox users, still waiting on fix |
Works fine with Firefox 133.0 |
couldn't switch to that, it would cause the echelon skin on my firefox to break. To get one thing, I would need to sacrifice another, and tbh I'd rather not fw that 😭 💀 |
vouch!! i have the same skin |
Please fix this for ESR 115 |
yeah i cant really get out of 115 esr bec im using it on a win 7 machine and im not gonna install things like extended kernels for newer apps on it |
Try latest version, maybe fixed |
ngl no idea at this point then |
Just wanted to mention that this is also happening with Chromium, as the current version of Opera GX i'm using is getting the same error, I have no idea how to fix it or if there is even a fix for it. (Just checked and I do have the most latest and current version of Opera GX/Chromium) |
"There was an error in initializing security header generator: Error: Failed to fetch homepage: TypeError: https:/// is not a valid URL.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0
OldTwitter doesn't allow unsigned requests anymore for your account security. Currently the main reason for this happening is social network tracker protection blocking the script. Try disabling such settings in your browser and extensions that do that and refresh the page. This can also happen if you're not logged in." (FYI, I am absolutely logged in)
I'm currently on the developer version of 115.0 Firefox (The version thats compatible for an aero mod)
It pretty much happens everywhere on Twitter, is there a way to fix this?
1.8.9.6
The text was updated successfully, but these errors were encountered: