Having a quick pint at the Old Windmill House.
People saying van Gaal needs to be sacked are being incredibly short-sighted. #mufc
Given Apple are releasing a battery pack, I’m hopeful future iPhones will have bigger batteries by default.
Giving WALL·E a watch
Wow I do love how easy @letsencrypt is
Oh dear, Chelsea just keep on losing! #football
I think my internet issues are now sorted and I can watch the game at last.
How are Man City playing so poorly? #football
OpenSSL and PHP updated, and now there’s a new GnuPG with TOFU!
Rebecca Murphey on HTTP/2’s encryption requirement:
HTTP/2 is a new protocol, and as such, it is greatly confusing to a large segment of the existing internet: proxies, antivirus software, and the like. During the development of HTTP/2 and SPDY before it, engineers observed that traffic that was transported on an insecure connection would frequently fail. The reason? The proxies, the antivirus software, and all the rest had certain expectations of HTTP traffic; HTTP/2 violated those expectations, and so HTTP/2 traffic was considered unsafe. The software that thwarted insecure HTTP/2 traffic didn't have the ability to inspect secure traffic, and so HTTP/2 traffic over a secure connection passed through just fine. Thus was born the requirement — which is a browser implementation detail, and not part of the HTTP/2 spec — that HTTP/2 web communication be conducted using TLS.