One reason I can think of for including it is that it may make it easier for the consumer to check the status code if it's in the JSON. Depending on how many layers of abstraction you have, your app may not have access to the raw HTTP response.
Although, yeah you lose the single source of truth though.
Most men are hard working and want to support their families
... which is exactly why you should take paternity leave and support your family, instead of abandoning them for 8 hours a day at work. I'd feel like a total asshole if I just took off and said, "Good luck with the baby, honey. I'm gonna go hang out with my friends at work."
LOL! You caught that! I vaguely remember seeing that somewhere? Was it on the Simpsons trivia episode? 30 years later, I still remember that, but I couldn't tell you the equation to draw a line... 😅
There is some degree of independence. For example, if Mozilla releases some super evil patch tomorrow, I'm pretty sure everyone would just patch it out immediately. In fact, this is what most derivatives seem to do, patch out the ad/telemetry stuff.
But yeah, these are all modified Firefox browsers. Hopefully, nobody was thinking these were unique, new, browsers.
Librewolf and Waterfox seem pretty similar on paper. I went with Waterfox cuz idk. So far, Waterfox seems to be a drop-in replacement. I haven't noticed any problems with websites and haven't run into any bugs.
One note about Waterfox is that I would have liked if it was added to the official Arch Linux repos. I installed fine with the AUR, but still.
I briefly looked into passkeys a while ago, but I think I remember really disliking them because they just seemed like another excuse for companies to lock you in.
Has this changed? With Bitwarden + passwords, I can change to any platform, any device, at any time, and instantly get all my creds moved over securely.
I don't want to be in a situation where I'm locked into using Android, Chrome, iOS, or whatever because I can't move my creds.
I've seen the status code in a JSON response before: https://cloud.google.com/storage/docs/json_api/v1/status-codes#401-unauthorized
One reason I can think of for including it is that it may make it easier for the consumer to check the status code if it's in the JSON. Depending on how many layers of abstraction you have, your app may not have access to the raw HTTP response.
Although, yeah you lose the single source of truth though.