5 ms·

They cite Twitter as using this pattern. That's hilarious, considering Twitter is currently one of the shittiest site around : half the time I click on a Twitte

by c-cube 6y ago

They cite Twitter as using this pattern. That's hilarious, considering Twitter is currently one of the shittiest site around : half the time I click on a Twitter link (I don't have an account) it leads to "you are not allowed to see this". After one or more reloads (actuary number seems to be rolled off a dice) I get to see the content, ie. 280 characters and maybe an image. I imagine they never tried to use their own website.

tobr 6y ago
I also get that infuriating message all the time recently. I seem to recall reading that it is some kind of heavy-handed security feature, but I can’t find any references for it... can anyone fill in?
- twittair_pr 6y ago
  This issue is not being fixed because it improves the downloads of the native Twitter app, which makes more money (no ad blockers, push notifications, more tracking).
sergeykish 6y ago
Twitter is not accessible without javascript. It serves 15kB page and does not include these 280 characters. Even its CSP header (2kB) is much bigger than actual message. Instead it wants (hard refresh, uBlock) 49 requests 795 kB transferred 3.6 MB resources Finish: 7.60 s DOMContentLoaded: 1.03 s
- colesantiago 6y ago
  > Twitter is not accessible without javascript. What did you expect, isn't the web now built this way, I doubt you can play a video from Netflix without javascript.
  - sergeykish 6y ago
    Glad to surprise you — most of the web works fine with first party CSS and images only, uMatrix: * * * block * * frame block * 1st-party css allow * 1st-party frame allow * 1st-party image allow Some use CDN, allow 3rd party CSS and images, that's almost uMatrix defaults: * * * block * * css allow * * frame block * * image allow * 1st-party frame allow Even facebook serves some visible content [1]. Yes, some sites require JS, youtube could have <video><source>, image lazy loading required JS, we've got <img loading=lazy> now. [1] https://www.facebook.com/lasytoy/ https://www.facebook.com/lasytoy/
kaoD 6y ago
I had that error for years, but it evolved. Nowadays Firefox (desktop and mobile) just refuses to load anything due to a "protocol violation error" unless I hard-refresh with CTRL-F5. I gave up trying to fix it.

by c-cube 6y ago

tobr 6y ago

I also get that infuriating message all the time recently. I seem to recall reading that it is some kind of heavy-handed security feature, but I can’t find any references for it... can anyone fill in?

twittair_pr 6y ago
This issue is not being fixed because it improves the downloads of the native Twitter app, which makes more money (no ad blockers, push notifications, more tracking).

sergeykish 6y ago

Twitter is not accessible without javascript. It serves 15kB page and does not include these 280 characters. Even its CSP header (2kB) is much bigger than actual message. Instead it wants (hard refresh, uBlock) 49 requests 795 kB transferred 3.6 MB resources Finish: 7.60 s DOMContentLoaded: 1.03 s

colesantiago 6y ago
> Twitter is not accessible without javascript. What did you expect, isn't the web now built this way, I doubt you can play a video from Netflix without javascript.
- sergeykish 6y ago
  Glad to surprise you — most of the web works fine with first party CSS and images only, uMatrix: * * * block * * frame block * 1st-party css allow * 1st-party frame allow * 1st-party image allow Some use CDN, allow 3rd party CSS and images, that's almost uMatrix defaults: * * * block * * css allow * * frame block * * image allow * 1st-party frame allow Even facebook serves some visible content [1]. Yes, some sites require JS, youtube could have <video><source>, image lazy loading required JS, we've got <img loading=lazy> now. [1] https://www.facebook.com/lasytoy/ https://www.facebook.com/lasytoy/

kaoD 6y ago

I had that error for years, but it evolved. Nowadays Firefox (desktop and mobile) just refuses to load anything due to a "protocol violation error" unless I hard-refresh with CTRL-F5. I gave up trying to fix it.