edflsafoiewq

That's the whole internet now. That or Anubis.

*distant sound of the sorcerer's apprentice is heard*

Mutable releases are used for continuous/nightly builds.

You recoup the saving of home automation immediately as additional leisure time. But for most people, work automation neither reduces your working time nor increases your wage.

You're unlikely to get any radio signal that isn't specifically meant for you.

I use an MVNO and I never needed any ID.

Typically you'd also be in debt to the BNPL provider, not the merchant.

How?

> CAISI chose GPT-5-mini as a comparator for V3.1 because it is in a similar performance class, allowing for a more meaningful comparison of end-to-end expenses.

The NIST report doesn't engage with training costs, or even token costs. It's concerned with the cost the end user pays to complete a task. Actually their discussion of cost is interesting enough I'll quote it in full.

> Users care both about model performance and the expense of using models. There are multiple different types of costs and prices involved in model creation and usage:

> • Training cost: the amount spent by an AI company on compute, labor, and other inputs to create a new model.

> • Inference serving cost: the amount spent by an AI company on datacenters and compute to make a model available to end users.

> • Token price: the amount paid by end users on a per-token basis.

> • End-to-end expense for end users: the amount paid by end users to use a model to complete a task.

> End users are ultimately most affected by the last of these: end-to-end expenses. End-to-end expenses are more relevant than token prices because the number of tokens required to complete a task varies by model. For example, model A might charge half as much per token as model B does but use four times the number of tokens to complete an important piece of work, thus ending up twice as expensive end-to-end.

They compare with gpt-oss.

> What decision-making process led to the idea of injecting human urine into a frog in the first place?

Hormones are basically messages sent through an animal's body to signal some change should take place. It was discovered that there was a hormone called hCG produced by the human placenta that triggers "you're pregnant" changes in the body. hCG is also present in the urine.

So if you want to detect a hormone, the idea is you inject it into an animal and see if it triggers the relevant changes (since the changes are usually internal, you generally need to kill the animal to check). So you would look for an animal that responds somehow to the hCG hormone, inject urine into it, and check for the response. Mice and rabbits were first used, but it was eventually discovered that certain species of frog that are highly sensitive to hormonal changes made for much simpler and faster testing.

My takeaway from this story has always been that both MS and Plan 9 simply passively implemented Unicode as received. It was only IBM that had the vision to see that the encoding was wrong and they should make a new one.

Running what are functionally massive orphanages seems like it'd be harder than the purely technical problem of automated gestation.

An example is translation. I MTLed some text recently where the name of a (fictional) city was translated about a dozen different ways. Sometimes you'd get a calque, sometimes you'd get a transliteration (including several wrong ones). Ironically "dumb" MTLs are often much more consistent about this than LLMs.

I love how completely prosaic phrases are now "ChatGPT signals".

I think this is the same as the brush stabilizer in Krita.

That's how I do "prompt engineering" haha. Ask for a specific format and have a script that will trip if the output looks wrong. Whenever it trips add "do NOT do <whatever it just did>" to the prompt and resume. By the end I always have a chunk of increasingly desperate "do nots" in my prompt.

Ideally people who have .DS_Store, .vscode, etc. would put them into their own $GIT_DIR/info/exclude files and not pollute the shared .gitignore with stuff from their personal setup.

How? If CC companies refuse to process any itch payments unless the content they object to is removed from the site, then crypto would have to become itch's sole payment option. That would probably kill the site.

Yes, imagine the sunburns.

In the strict sense, sure, but the point is they depend not only on the seed but on seemingly minor variations in the prompt.

Immediate mode only describes the interface.

Isn't that basically what VDOM is?

There are subpopulations with high birth rates. They are very small currently, but if you really think the general population will die off for want of reproduction, eventually they will comprise a sufficiently large fraction of the population to raise the overall birth rate.

Certainly this is a factor; is there a reason to think it is a significant one?

They'll do that to large PNGs too.

I guess you're thinking of jpegli? Do you know how big a difference this actually makes?

Probably they mean uploading WebPs where an image is expected often doesn't work.

I have one of those too. The connection dropping out is the real crux of the matter I think. If it's merely slow you can just wait longer, but an intermittent connection requires qualitatively different design.

Many people have already said designing for iffy internet helps everyone: this is true for slimming your payload, but not necessarily designing around dropped connections. On a plane or train, you might alternate between no internet and good internet, so you can just retry anything that failed when the connection is back, but a rural connection can be always spotty. And I think the calculus for devs isn't clearly positive when you have to design qualitatively new error handling pathways that many people will never use.

For example, cloning a git repo is non-resumable. Cloning a larger repo can be almost impossible since the probability the connection doesn't drop in the middle falls to zero. The sparse checkout feature has helped a lot here. Cargo also used to be very hard to use on rural internet until sparse registries.