PipePipe is so nice with the fast auto-updates. If I ever even catch it breaking, I just have to use Firefox for a few hours and then F-Droid ships the fix and PipePipe works again.

All this is true for many other products, specifically cars. Ford makes the Bronco Sport anyway, and they make money on it.

I get it, Apple has much better margins than Ford. And maybe a iPhone 18 Mini would reduce total margin for them. But if they move a couple of million units, it absolutely would make money.

It will suffocate you on account of all that blood pulp in your lungs. And eyes, and nasal mucosa...

Having a high pressure ammonia leak indoors is a death sentence for anybody in the same room. Same building, if it's large enough...

Depends on setup, of course. If there's a central AC blowing hot/cold air through ducts, you're stuck using a grey water loop. But it is the least attractive setup...

Inflation is multiplicative, so: 1.277 * 1.26 = 1.61 giving us the 61% subscriptions went up.

And yes, VW is fighting for survival. The things they are killing are the low volume models specific to the Chinese market (because absolutely nobody in China is buying any VWs) and a lot of the variants and overlaps they've accumulated over the years. They'll continue making less than 100k iD.7s, and will be happy to do so (it's modestly profitable).

For comparison, that's roughly like Ford killing the Bronco Sport, or VW killing the ID.7.

That's the entire point of why knowledge cutoff is so important (if you use them offline).

I find it entirely believable that the Navier-Stokes conversation was auto-flagged as high value training data, and burned-in the models knowlegdge base.

The equivalent would be taking a (fully offline) LLM and asking it about the ending of one specific Goosebumps book, and it revealing the twist. And although that specific book was (probably) only once in the training data, a high parameter LLM can usually "remember" the twist.

No...? Of course not?

Because revenue is only one side of the equation. Did you ever look at total cumulative OPEX and CAPEX, and how long it will take them to even just break even at current growth?

I think the problem with that idea is that the rhizobacteria needs energy to break the nitrogen tripple bond. A lot of energy. It gets that energy by getting carbohydrates from the host plant - which in turn are not available to the plant to grow.

I'm sure there's plants where not fertilizing with nitrogen at all would make the trade-off worth it, but the vast majority of our optimized crops can't spare double-digit percentage points of their total yield to feed bacteria. You're much better of just using natural gas (or green hydrogen) to fix the nitrogen.

This, of course, requires 6G base stations to be spaced pretty tightly (hundreds of meters apart) and to feature sophisticated phased array antennas. But both can be assumed in cities (they're planning to completely replace WIFI with 6G, so every current WIFI access point will become a 6G micro cell). Walking humans can be detected much easier, but radar SNR is funny, that only gives you 4x-6x the detection range.

Software (signals processing) for all that will be... a lot of difficult work. Object separation/tracking, multipath reflections, clutter suppression, ect.

I can't think of many things, but there are a few: I want an LLM teaching 1 on 1 language lessons. Good ones, with tailored vocab, tailored reading, tailored listening, grammar lessons, and (most importantly): conversation training including it correcting my pronunciation and grammar.

Current LLMs can do most of that when prompted correctly (and supplied with textbooks and podcasts), just the last part is missing.

But what else is there?

Comments URL: https://news.ycombinator.com/item?id=49098406

Points: 9

# Comments: 5

That's useless if the backup account and the main account use different keys for the home partition.

VeraCrypt (used to?) have this. It was called a hidden volume. One volume, but two keys, two passwords, and two different containers full of data. Technically, the second volume is written into the partition "from the back" using key 2, while the first volume is written "from the front" using key 1.

Fun fact, there's no protection against writing over data in the other volume if volume 1 + volume 2 exceed the size of the partition - and there can't be, otherwise the volume wouldn't be hidden.