By the same token, now you have to implement pie.toast() and cake.toast() and lots of other useless and irrelevant methods, even though you're never ever going to use them, simply because they extend the isBakeable() interface.
Unnecessary, since the IsBakeable interface provides a default implementation of the toast() method that throws an exception if you attempt to toast something that is not toastable.
The real issue is why the IsBakeable interface has a toast() method in the first place...
Unfortunately a great number of embedded control devices generate a new self-signed cert. every time they boot
I think your angst should be directed towards these lazy and inconsiderate hardware developers for violating the intended purpose of HTTPS, rather then at Firefox for doing what is essentially the right thing.
Oh, but wait, it makes your life just a little bit more difficult. I guess it must be bad.
Many people write memos to tell you they have nothing to say.