Collecting invoices is cash accounting, whereas revenue is realized only over the length of the contract and doesn’t care when the customer pays. (Of course sometimes you have a short-term contract including for professional services and such, but not to the point where a single day would likely be particularly inflated.)
Presumably they mean they could make user code trigger a write out of bounds to kernel memory, but they couldn’t figure out how to escalate privileges in a “useful” way.
“30% of viewing” I think clearly means either time played or items played. I’ve never worked with a data team that would possibly write that and mean users.
If it was a stat about users they’d say “of users”, “of members”, “of active watchers”, or similar. If they wanted to be ambiguous they’d say “has reached 30% adoption” or something.
The endpoint is not whatever the client asks for. It's marked specifically as exposed to the user with "use server". Of course the people who designed this recognize that this is designing an RPC system.
A similar bug could be introduced in the implementation of other RPC systems too. It's not entirely specific to this design.
ZDR is a risk thing for them. They want to make sure you're a legitimate company and have monitoring in place on your side to reduce the chance you're using them for illegal things.
“360 degree peer review” isn’t a thing, the whole idea is that a 360 includes feedback from both your manager and your peers, that’s what distinguishes it from a 180!
Website says "Up to 27 hours video playback", which is apparently 7–8 hours more than the iPhones 13–15 and 4–5 more than the 13–15 Pro. Also normally their battery estimates are conservative.