Should I now believe you are so in favor of not making incompatible changes? No, because providing a completely meaningless value is an incompatible change, so that’s not consistent. But elsewhere you argued strongly in favor of incompatible, breaking changes, even going so far as to claim they aren’t really changes or breaking. What am I supposed to believe? Not 0s from Twitch, apparently.
That example doesn’t even follow. If OBS were relying on that information for some reason, it would be when the information would presumably be correct.
It is pretty standard to either exclude a key or provide a semantically defined null or undefined value. Twitch already does this elsewhere. A program that in unable to handle unexpected data gracefully is already broken. But changing 0 to null or undefined isn’t always breaking. In Javascript, for example:
null + 0 === 0
Number.isNaN (undefined + 0) === true
In most dynamically typed languages, if there is any issue with this sort of implicit conversion, a warning will be raised instead of an error. In other languages, programmers need to be particularly careful about incoming data anyway.