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

Twitter won't load any tweets or profiles when script is running #41

Open
Jars1415 opened this issue Aug 5, 2024 · 7 comments
Open
Labels
question Further information is requested

Comments

@Jars1415
Copy link

Jars1415 commented Aug 5, 2024

I have the script installed in tampermonkey. When visiting twitter, I see an error that says "Something went wrong. Try reloading." where tweets/profiles should be (reloading did not fix this). After disabling the script in tampermonkey and reloading twitter, everything appears normal. Re-enabling the script and reloading twitter again causes the error to re-appear.

@DB9-max
Copy link

DB9-max commented Aug 14, 2024

Get violentmonkey
Check script match https://x.com/*

@XiaJiuge
Copy link

In tampermonkey settings, change "Config mode" to advance, then go to the "Security" and change "Modify existing content security policy (CSP) headers" to Yes ,then go to bottom of page, in "Experimental" , change "Add Tampermonkey to the HTML's CSP" to Yes

@pandacat42
Copy link

Having same issue, neither of above fixes seem to work on firefox

@DB9-max
Copy link

DB9-max commented Aug 16, 2024

Get Violentmonkey - it's open source and lightweight compared to Tampermonkey

@prinsss
Copy link
Owner

prinsss commented Aug 19, 2024

Hi all,

This could be a problem about Content-Security-Policy (CSP) and was discussed before in #19.

For Chrome users, it should just work.

For Firefox users with Tampermonkey installed, try setting:

  • Modify existing content security policy (CSP) headers: yes
  • Add Tampermonkey to the HTML's CSP: yes

image

For Firefox users with Violentmonkey installed, the upstream issue is tracked here:

violentmonkey/violentmonkey#1001

@prinsss prinsss added the question Further information is requested label Aug 19, 2024
@Jars1415
Copy link
Author

Thanks. I tried this and unfortunately it didn't work. I then tried changing "Modify existing content security policy (CSP) headers" from "Yes" to "Remove entirely (possibly unsecure" just to see if it would make a difference, and that worked. I then changed it back because I don't know enough to judge if "possibly unsecure" is a problem for me, but this seems to be a possible solution.

@kqvanity
Copy link

@Jars1415 Thanks. That did the trick!

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

No branches or pull requests

6 participants