Unless I'm mis-understanding it doesn't just wallop the owner of the site. It wallops all of that site's users as well. I know Google is less likely to be walloped but imagine a site similar to Google docs or gmail went down until the key expires. That's not just going to affect the site, it affects all of it's users.
Users can still get their data; the owners need to stand up another hostname. They're inconvenienced. But the attack is devastating to companies, who depend on user convenience to attract and retain users.
> Well, the real risk here is that it creates a new consequence for being hacked by a criminal, right.
No disagreement from me here, which was one reason we set out to talk about RansomPKP at BH/DC in the first place :) That said, I do think this can, and should, be reported to site owners. You're not going to see much innovation if people don't take time to futz around with technologies and see what they can do with them. HPKP has plenty of potential to hurt, but as you alluded to, it's generally just your own feet in harm's way.
> This particular risk though just wallops the owners of the site.
Yeah, that's what the (cough) team was going for.
On the other hand, it's an internalized risk, which is kind of a beautiful thing: so many of the risks we create through poor security are externalized to end-users --- so much so that you can run a secure messaging site, get owned up, cost thousands of people their privacy, and still keep chugging along as if nothing happened. This particular risk though just wallops the owners of the site.