master_crab

That’s not good either. It’s the same with poultry, many types of fruit, etc. This just makes the case further.

They don't have a monopoly on any meaningful product category.

By that reasoning I could have a monopoly on peanuts and it’s alright because consumers can choose from hundreds of other foods.

I wonder what happens to that gas price once the SPR can no longer be drawn from?

https://www.eia.gov/dnav/pet/hist/LeafHandler.ashx?n=PET&s=W...

Apologies. Not trying to come across as a prick.

But at least we both agree private dns =/= split brain. :)

Bless your sweet heart if you think private DNS servers are split horizon. :)

Because I was responding to this comment you had made:

So what's your solution when you have a wholly private service that will never have a public v4 address, nor a publicly routable v6? How do clients get the address for a nice domain name without the addresses in public DNS?

Which, if you claim you use private DNS, you know you can indeed solve by only having the private records sit on your private DNS service that can only be hit by clients on the internal network. Without the architectural bad practice of implementing split horizon.

The M-series are ARM chips based on the A series from the iPhones. Therefore Apple had ten years of chip design (plus the prior decades of ARM history) to rely on. The GPUs and modems were a much more recent effort.

(My take. happy to be corrected by someone with chip design experience who can comment.)

100%. Orchestrating multiple sub agents is a key requirement for many workflows. If only because it minimizes context sprawl (amongst multiple other reasons).

There is probably a middle ground though. Something like a main thread agent (say a local model for Hermes) orchestrating cloud based sub agents.

You don’t. You avoid split horizon because of the silent (usually failure) mechanics it introduces.

A lot of these are visual-heavy tests that often require first person sight to confirm results. Considering GLM isn’t multimodal, that might explain why it did better on the calculator question and not much else.

Wait…what? You have a fully internal service and you dont have an internal DNS server? I guess those exist in theory, but not in practice. :)

If you have a heavy enough tech stack to run fully internal services, than you can also run an internal DNS service (even pihole is enough) and load internal only entries there.

Or add everything to your hosts file if you have a central config service.

Split brain =/= done right.

This introduces all sorts of aberrant behavior. Most notably that clients will get different responses depending on their query and route that you now have to test for. It also is a “silent” deviation for audiences that may not be aware of.

I’m not sure what problem that is trying to be solved here? That the OP wanted internal users seeing a different site than external users? Or using a different route in? In both those cases the correct user behavior is to use a different DNS record.

He’s a lightning rod only because some people get unnecessarily triggered by facts that don’t fit their world view.

So short meta?

Containers is often the reason. You start a container and you are immediately pulling in a quarter to half a gig or more (often the latter).

Does the IIHS have a an Indiana Jones style warehouse where they keep 30 year old forgettable vehicles like the Blazer in storage for just this special occasion?

“Doctor killer” for a reason.

It can be monotonous and degrading, but commercial air is the safe way to travel.

There needs to be a distinction - because people are making an honest conflation - between distributed computing and cloud computing. The list in the article applies to both, but the limits and performance variability can apply quicker - and with more effect - in the cloud.

But it’s relevant whether we like it or not. This will affect the price of goods, salaries of workers, everything.

What, do people not remember Katrina? That was the sign to move, and it was 20 years ago.

Yeah it’s a sad state. But it’s also not worth putting oneself in harm’s way. Report it to the state authorities (not all of them are crooked). Or try another jurisdiction, like the local police.

This was incredibly dangerous of the victim. In another version of events, the officer could have shot him and plausibly (unfortunately) claimed the victim had a vendetta against the cop for arresting him.

IAM isn’t even really the most painful dependency. Route53 is. The control plane only runs out of use1.

Better make sure the only DNS operations you run during an outage are data plane queries and health check failovers.

Are you saying F/G AND any line serving less affluent areas? Because if not, the G (save for maybe 2-3 stops in Bed-Stuy) is all affluent neighborhoods.

Why is this getting downvoted? How is this any less ridiculous sounding than the multitude of other, ever-shifting reasons Trump gave for starting the war.

IPs are notoriously unreliable for identity pinning, particularly in this age of CGNAT.

If they can’t or don’t want cc numbers (makes sense considering how painful PCI guidelines are anyway) does that mean they need to rely on more tools from the processors or user accounts maintained by the merchant themselves?

I always wondered about this. Do companies tie the credit card to an identity to block or do they just block the cc number?

If the latter, seems like a small friction point for a consumer. Given how often cc numbers change and how many an (American) consumer has, this won’t block anything unless you are charging back more than once every few months.

Declaring someone an enemy does not automatically lead to war. America considered the USSR an enemy of democracy for 50 years. They never went directly to blows.

For production Postgres, i would assume it’s close to almost no effect?

If someone is running postgres in a serious backend environment, i doubt they are using Ubuntu or even touching 7.x for months (or years). It’ll be some flavor of Debian or Red Hat still on 6.x (maybe even 5?). Those same users won’t touch 7.x until there has been months of testing by distros.

Yes, sorry. I meant it more as a descriptor of how many tokens it consumes. You are still stuck burning money.