I have to assume that at least someone in the room was well aware that all oil is not created equal and that US refineries were designed from the beginning for Venezuelan and similar oil rather than US oil.

If the US holds 100 tons of gold on behalf of another country and possesses that full amount, it isn't paper gold.

Derivatives are where paper assets come into play. You buy the right to own 100 tons, for example, and whoever owes you that either owns only a fraction of their total liability or plans to buy it when delivery is requested. That's an over simplification of a much more complex market, but the key is that "paper gold" owed doesn't exist in the full amount.

With a static site you know the output can be cached indefinitely and only invalidated by a new deploy.

With a server rendered site you can only recreate that by tracking ever piece of data a page is dependent on, tracking data changes, and invalidating any page a data change breaks.

No one does that though, so you may go for SWR or a short-ish cache window so changes take some set of minutes to roll out, looking like the delay in waiting for a static site to rebuild.

I'd never pick between static and server rendered based on caching. Factors like the size of the site, frequency of content updates, and technical skill of content authors (I've never found a git-based CMS I'd ask someone totally nontechnical to use).

I would be interested to see how this compares to industry standard though, 77% doesn't seem outrageous to me given all the trackers and advertising code I've seen over the years. It wouldn't surprise me if this is inline with many apps people install and don't think twice about.

I don't know of ant precedent where the code was literally generated on someone else's system. Its an open question whether that implies any legal right to the work and I could pretty easily see a court accepting the case.

It becomes legally challenging with regards to ownership if I ever use work equipment for a personal project. If it later takes off they could very well try to claim ownership in its entirety simply because I ran a test once (yes, there's a while silicon valley season for it).

I don't know if they'd win, but Anthropic absolutely would be able to claim the creation of that code was done on their hardware. Obviously we aren't employees of theirs, though we are customers that very likely never read what we agreed to in a signup flow.

I don't meant this as a drive by bazinga either, the practice of copying code or thinking you understand it when you don't is nothing new

There is a difference for sure between hosting your own email server and using it for official government communications and having your own personal email address used for personal communications.

The issue that seemed to completely disappear related to the use of Signal messenger for official white house communications seems more aligned to the email server issue. It was reported heavily at the time what the reporting requirements were and that they would have to submit the full chat histories within 30 days or something like that to stay within the law. I never heard whether that actually happened or not, the story just died.