☰

Twitter Show Sensitive Content

No more extra click to show stupid tweets!

Nasıl kurarım

Bu betiği kurabilmeniz için Tampermonkey, Greasemonkey ya da Violentmonkey gibi bir kullanıcı betiği eklentisini kurmanız gerekmektedir.

You will need to install an extension such as Tampermonkey to install this script.

Bu betiği kurabilmeniz için Tampermonkey ya da Violentmonkey gibi bir kullanıcı betiği eklentisini kurmanız gerekmektedir.

Bu betiği kurabilmeniz için Tampermonkey ya da Userscripts gibi bir kullanıcı betiği eklentisini kurmanız gerekmektedir.

Bu betiği indirebilmeniz için ayrıca Tampermonkey gibi bir eklenti kurmanız gerekmektedir.

Bu komut dosyasını yüklemek için bir kullanıcı komut dosyası yöneticisi uzantısı yüklemeniz gerekecek.

(Zaten bir kullanıcı komut dosyası yöneticim var, kurmama izin verin!)

Nasıl kurarım

You will need to install an extension such as Stylus to install this style.

You will need to install an extension such as Stylus to install this style.

You will need to install an extension such as Stylus to install this style.

You will need to install a user style manager extension to install this style.

You will need to install a user style manager extension to install this style.

You will need to install a user style manager extension to install this style.

(Zateb bir user-style yöneticim var, yükleyeyim!)

Yazar
rigid_function
Günlük kurulumlar
0
Toplam kurulumlar
5.864
Değerlendirmeler
5 1 1
Versiyon
0.3.6
Oluşturulma
27.12.2021
Güncellenme
27.12.2022
Boyut
5,79 KB
Lisans
GPL
Geçerli

Not working with the new Account Required elements! (No API response without Account)

Is there a Workaround? Yes. You can use Nitter instances which server is outside of the affected restricted regions (eg. Netherlands) but, for the rest of the regions, it's in the same boat as the average non logged user :(

Normal "Click to see" elements with buttons are still working

Removes the annoying "The following media includes potentially sensitive content." warning on Twitter

(Also known as "Twitter Show Hidden Content")

Note: I tried to make it as reliable as possible. No guarantee this will always work

Firefox: Please, before saying "it doesn't work". (this doesn't apply to Chromium)

Verify if your user script manager is executing on the page. Twitter uses a CSP (Content Security Policy) in the header that tells your browser to prevent "insecure" inline code injections. This is bad for you because prevents extensions from working.

No Workarounds: Greasemonkey & Violentmonkey

Workarounds: Tampermonkey

Source (https://github.com/Tampermonkey/tampermonkey/issues/952#issuecomment-638373937):

  1. Switch to Tampermonkey beta branch
  2. Change security settings to allow Tampermonkey to modify CSP

Or try:

  • Disabling FastForward/Universsal Bypass(unmaintained) extension
  • Try in a new profile (about:profiles)
  • Restore Tampermonkey ?
  • (bad idea) Setting dom.caches.enabled to false
  • (dangerous) Setting security.csp.enable to false. **But that's a really bad idea!!!
  • Chromium base browser

More info:

Tampermonkey issues:

Bugzilla issue trackers: