News for hackers. Stuff that matters.

A comment on Standardizing lessons learned from AMP. Parent comment

Re:Standardizing lessons learned from AMP by reaperducer on Thursday March 08, 2018 @01:13PM (#16546298)
> And OCSP with the signature when Chrome themselves have disabled its use?

It's not the first (or probably last) time that Big G's said "Do as we say, not as we do."

Heck, the blog post is hosted on WordPress instead of Google's own Blogger.

[ Parent | on HN ]
Re:Standardizing lessons learned from AMP by Ajedi32 on Thursday March 08, 2018 @02:49PM (#16547078)
Chrome hasn't disabled OCSP. It just only enforces it when you're doing OCSP stapling with must-staple. Firefox did the same: https://bugzilla.mozilla.org/show_bug.cgi?id=1366100
[ Parent | on HN ]
Re:Standardizing lessons learned from AMP by username223 on Thursday March 08, 2018 @03:21PM (#16547317)
> Heck, the blog post is hosted on WordPress instead of Google's own Blogger.

That made me chuckle, and gave me a sense of how much they value this PR chum. Please, guys; at least make a semi-convincing attempt to pretend you think we're not morons. Hosting a blog post on your own domain would cost you almost nothing. You could even load it up with your own ads to recoup the cost.

[ Parent | on HN ]