And phone number verification too? So that's 3 hurdles to jump to just get opus.

for verification you can buy phone number for $1 easily.

Doesn't ~every phone number verification service check the telephone provider and only allow from a select whitelist of residential providers?

Phone verification services exist to give you a real number for the purpose of passing this kind of verification.

They even have APIs for these services. They make money since they can use the same number to verify different things.

With esim and virtual credit card services, why would that be a blocker? Who's got a landline these days?

You can easily get lots of esims for $5-10 months in EU / UK or just for free.

I think it is really good to start to use CAMARA GEOLOCATION for it. A fraudstear could be intercepted if is not under the MNO antenna.

Title says uri but post only about urls, a type of uri

In 2017. Wonder what it's like today.

"US, for 1st time in 50 years, experienced negative net migration in 2025" [0]

Curious how they jumped for nearly decade old stats, huh?

[0] https://abcnews.com/US/us-1st-time-50-years-experienced-nega...

Funny. When you input only milk and soy milk, it ignores the soy. If only soy, suddenly the butter needs to be vegan.

Another potential use case: This may help jujutsu auto split a large revision into small orthogonal revs.

Sometimes agent makes a monolithic commit and it's a lot of work to manually split code you didn't write. After such an auto split I can manually squash related revs into feature/ticket level.

That's a really compelling use case actually

Thx oh and maybe don't call it sem. It's not really semantic, more like a big picture view vs the ground level git lines. How about "bye", short for bird's-eye?

Literally what china is doing now

Standardization. Who writes llms.txt? Everyone writes their own? Will agents still behave the same?

Biggest design bug imo is the workers need to register for the workflows they support, but will happily pull tasks from unrelated workflows if they're on the same queue. No way to put failed tasks back into the queue again either.

Isn't split stack architectural, i.e. client heavy vs thin client. Not a hard TS feature?

With Phoenix you can write actually 0 code that runs on the client, just the backend and html templating.

I'd say cue is nicer, but the tooling available is even less mature.