Great. Another grift.

I imagine sabots would do pretty well against graphics cards.

I… doubt it?

I took the liberty of looking in the developer tools as it failed, and there was a 500 response. The connection to Hulu’s servers was all over HTTPS and I didn’t get any certificate warning, so unless my ISP managed to get Hulu’s private key or got with a corrupt registrar willing to issue a valid replacement certificate, no ISP should be able to change response codes on a man-in-the-middle basis or a redirecting-traffic-to-a-hostile-server basis.

And given how many people have reported issues, I doubt it’s specific to any particular ISPs.

Net neutrality being dead is a huge bummer, but I don’t think this can be blamed on that.