5 ms·

I block AMP and its related domains in my aggressive blocking hosts list[1]. I've found many AMP related sites are purely for marketing, or 'news' articles that

I block AMP and its related domains in my aggressive blocking hosts list[1]. I've found many AMP related sites are purely for marketing, or 'news' articles that are thinly veiled ads. I haven't missed it at all. I also don't use Google, so perhaps that it part of it, but I applaud your decision to remove AMP. The web isn't meant to be centralized in this way. [1] https://github.com/lightswitch05/hosts/blob/master/tracking-aggressive-extended.txt https://github.com/lightswitch05/hosts/blob/master/tracking-...

bhhaskin 8y ago
Not sure why you are being down voted. You aren't wrong.
- dang 8y ago
  Please read the site guidelines, which ask you not to post comments about voting on comments. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
JoshMnem 8y ago
I block AMP pages too. Unfortunately, Google artificially slows down AMP pages so that they literally take 8 seconds to load if you block the AMP JavaScript. (Check the inline CSS.)
- SquareWheel 8y ago
  Are you sure that isn't just a timeout function in case AMP fails to load? edit: Dug up the code. <style> body {animation:-amp-start 8s steps(1,end) 0s 1 normal both} @keyframes -amp-start{from{visibility:hidden} to{visibility:visible}} </style> <noscript> <style> body {animation:none} </style> </noscript> The timeout function is turned off if JS isn't available, so JS being disabled shouldn't be a problem. I'm guessing this is actually to delay page paint so it doesn't display when half-loaded.
  - anoncoward111 8y ago
    If they don't allow you to fix this fallback, it's a punishment
    - bastawhiz 8y ago
      In fairness, blocking the external half of the code while not blocking the inline part of the code is on you. You could just as easily block/disable the <style> tag that adds this in addition to the AMP JS.
      - JoshMnem 8y ago
        Blocking inline CSS is more difficult than blocking external resources.
    - deleted 8y ago
      [deleted]
  - detaro 8y ago
    parent said > block the AMP JavaScript not, > JS being disabled
    - SquareWheel 8y ago
      Then the noscript tag wouldn't fire here. But that's just shooting yourself in the foot. A page won't function with half its code running.
      - tedunangst 8y ago
        The JavaScript should create the fade style, then it will only happen if js is running.
        SquareWheel 8y ago
        I'm pretty sure the JS actually stops the fade. The inline CSS will be executed very early on in the page, before any assets are loaded. Though it seems to me if the page is fast enough anyway (as amp pages claim to be), then this trick shouldn't be necessary anyway.

bhhaskin 8y ago

Not sure why you are being down voted. You aren't wrong.

dang 8y ago
Please read the site guidelines, which ask you not to post comments about voting on comments. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html

JoshMnem 8y ago

I block AMP pages too. Unfortunately, Google artificially slows down AMP pages so that they literally take 8 seconds to load if you block the AMP JavaScript. (Check the inline CSS.)

SquareWheel 8y ago
Are you sure that isn't just a timeout function in case AMP fails to load? edit: Dug up the code. <style> body {animation:-amp-start 8s steps(1,end) 0s 1 normal both} @keyframes -amp-start{from{visibility:hidden} to{visibility:visible}} </style> <noscript> <style> body {animation:none} </style> </noscript> The timeout function is turned off if JS isn't available, so JS being disabled shouldn't be a problem. I'm guessing this is actually to delay page paint so it doesn't display when half-loaded.
- anoncoward111 8y ago
  If they don't allow you to fix this fallback, it's a punishment
  - bastawhiz 8y ago
    In fairness, blocking the external half of the code while not blocking the inline part of the code is on you. You could just as easily block/disable the <style> tag that adds this in addition to the AMP JS.
    - JoshMnem 8y ago
      Blocking inline CSS is more difficult than blocking external resources.
  - deleted 8y ago
    [deleted]
- detaro 8y ago
  parent said > block the AMP JavaScript not, > JS being disabled
  - SquareWheel 8y ago
    Then the noscript tag wouldn't fire here. But that's just shooting yourself in the foot. A page won't function with half its code running.
    - tedunangst 8y ago
      The JavaScript should create the fade style, then it will only happen if js is running.
      - SquareWheel 8y ago
        I'm pretty sure the JS actually stops the fade. The inline CSS will be executed very early on in the page, before any assets are loaded. Though it seems to me if the page is fast enough anyway (as amp pages claim to be), then this trick shouldn't be necessary anyway.