v4 is less efficient but more private.

The math is simply not in there favor, by a number so large we cannot conceive of it in our tiny brains.

UUIDs have other useful properties. For example, they don't expose counts (e.g. how many customers you have.) They make URL / resource guessing impossible.

ids in the form of `[prefix]_[uuid stripped of dashes]` is ideal for most use cases. It should be the default the way Postgres is the default. Any deviation have good reason.

No commands run.

No persistent access.

Lawyers are amazing.

Edit: Yes, based on the comment by dherls, this is how they're getting around it. Streaming replication is not commands run by the attackers (it's your own system doing the exfiltration!)

No one reasonable is saying, “hook up this model to do anything it wants with no other system available.”

Will people fuck it up? Absolutely! But, “the model has to be perfect or it will bankrupt a company” is more cynical than reality.

Looks like they've built (or are building) their own index and return cached results. What you do with that information is up to you. If you want to visit the live page, you'd need to find a way around bot detection.

One reason (not the only one!) people use Anubis is to prevent the endless flood of requests from AI companies. If Deepseek scrapes once every few hours, that helps the website owner with the traffic problem while allowing access.

If they don't want to allow access, my guess is that deepseek's search crawler respects robots.txt but I don't know.

They’ll likely embed text models more deeply in the future, but the history of “Apple Intelligence” doesn’t give a lot of hope that they’ll nail it.

So they’re not selling shovels (a precursor to making the thing) but products and services to use it.

I will say that I asked Siri some questions recently that I was pretty sure it would fumble and it answered directly.

“Does brown go with charcoal in clothing?”, for example, didn’t fall back to “I’ve found some web results. I can send them to your iPhone”. It actually answered.

It still has random nonsense regularly, but the “ask a question, get an actual answer” is new to me.

They leave the room and when they come back immediately know which is which. Specifically because of the over-alternation that yours mentioned. A string of HHHHHH is exactly as likely as HTHTHT, but people don't intuit that.

If yours happened to contain consecutive digits or common ones (ending in zero, significant numbers like 911 or 42 or 69), that would imply less randomness even if it's actually the result of "real" RNG.

What's also crazy is that they can detect fire alarms, will alert your iPhone, and then can pipe both sound and voice to the HomePod. It announces that it's going to do so, so it's not a privacy nightmare.

Pretty cool. I didn't know it existed until it happened. (Thankfully nothing bad.)

(Not exactly the same power feed but you know what I mean)

Jev has been around for a couple weeks. Cost and performance matter more than anything. Staying with an existing provider (the # of people choosing Jev without already having a frontier API key is probably zero?) is way easier than this.

What the hell are we even talking about.

What you could achieve with $10k a year ago vs today is quite different.