Good news for Anthropic.

It’s a PR issue not a legal one.

This draft spec was eventually published as RFC 9562. Compared to the previous spec it adds versions 6, 7, and 8, plus best practices guidance.

Basically, there are a bunch of UUID alternatives that arose to fix the problem that UUIDs are bad for use as database keys in large tables (here’s the perspective of MySQL experts Percona). A bunch of these alternatives are actually linked from the RFC, which I haven’t seen done before. Version 7, in particular, is meant to address this use case.

Successful malls have an Apple Store, Tesla, and Louis Vuitton, which tells us something about who can still afford to shop there.

Apparently there’s a recipe on that page. Here’s the same page without the crud: https://www.justtherecipe.com/?url=https://houseofnasheats.com/brazilian-lemonade-limeade/

So that’s why they haven’t been able to launch yet. It all makes sense now.

There also needs to be some way to indicate that a JSON construct is a Set, Map, plain object, or array. You’d want a date/time type as well.

Without breaking existing JSON parsers, the way to do that is to add metadata like a _type field to an object, or to add a “sidecar” object like superjson does. Which works but is ugly IMO.

Then there’s BSON, YAML, JSON Schema, and the one we don’t mention ₓₘₗ. To my knowledge all of those could be extended in a way to support new types, but require the producer and consumer to both understand and follow whatever convention you use. They lack the universal interchangeability of JSON.

Set and Map would be more useful if they were compatible with JSON. I see a lot of people using an object as a dictionary or an array as a set because of that.

Sometimes it’s the only option or the preferred option.

I haven’t. Maybe someday I’ll be willing to, but not today. It’s a hassle and extremely intrusive to provide my bank statement and photo ID to a company whose security I don’t trust.

That’s usually how I pay if someone requests money. Venmo is owned by PayPal but my account there works just fine.

I thought about that, but they ask for enough info that they’d be able to identify me. And then they’d probably ban me. At least right now I have the option of restoring my account, even though I have no intention of doing so.

You live in a city, but most of the store chain’s customers live in the suburbs where gas is a major expense and fuel perks are a big incentive to shop at a particular store.

The store isn’t trying to promote fossil fuels. They only care about customer loyalty. Besides (they might rationalize), their customers have to buy gas somewhere so why not from us?

Good. Apple’s malicious compliance — following the rules but making it extremely unappealing — is coming back to bite them in the ass. I don’t know why they thought they could win this game of chicken. Let us use the product we paid for, how we choose to do so.

This looks like an interesting replacement for the Chevy Bolt class of cars that currently is missing. A lot of these are being announced but not on the market yet.

I don’t think there’s any plan to bring this to the US. If they did, GM would manufacture it in the US a NAFTA country (see reply below).

They can’t realistically start charging for the emergency SOS satellite feature (“sorry your family member died but they didn’t have a paid subscription”).

I think this will be a way to charge for non-emergency texts to subsidize the free usage. Plus it’s a cool feature of course.

The one that’s not shown: Standalone Passwords app

I see Valles Marineris on a partially-terraformed Mars with, perhaps, Phobos in the foreground.

Their implementation won’t be gimped. Apple’s lock-in does not depend on RCS sucking. Instead, it depends on Apple adding new features to iMessage -- real features like group messaging, or gimmicks like “Genmoji”. RCS is a moribund carrier-controlled standard and has no hope of keeping up feature parity with iMessage. It will always be outdated, no matter how good or complete the implementation is (or isn’t).