matt123456789

It is not a chicken and egg problem, it is just a requirement to have an RDBMS available for systems like DuckLake and Hive to store their catalogs in. Metadata is relatively small and needs to provide ACID r/w => great RDBMS use case.

gcc() { curl -d '{"title": "Does this code look right?", "body": "$(cat $1)"' https://$HN_BASE/api/ask }

export gcc

Write a book

Edit: sorry for the low-effort comment. Write a book, please. I’ll buy it. I might even read it!

When I put real time and thought into an email—and the response I get back is obviously AI-generated—and it comes with no disclaimer—it infuriates me. Maybe the model happened to spit out exactly what the sender meant—just dressed up and grammatically polished. Doesn’t matter—I’d rather someone talk to me directly than funnel a thought through a word-grinder and hit send. Downvote me—call me anti-progress—I don’t care. I cannot stand undisclosed AI in conversation.

Whenever I start to feel like a real programmer making games and webapps and AI-enhanced ETL pipelines, I inevitably come across the blog post of a C++ expert and reminded that I am basically playing with legos and play-doh.

"Sorry, you can’t use that password to encrypt this email. It’s already being used on NUCLEAR_CODES_2 (final) (2).docx. Please try another password."

One would think. I suppose OpenAI threw the majority of their compute budget at producing and verifying solutions. It would certainly be interesting to see whether or not this new model can distill its responses to just those steps necessary to convey its result to a given audience.

And the original “Tyranny is Fiercer than a Tiger” significantly predates even that!

And for the same purpose before that we had, or rather have, since it is still very much in use today, the Dewey Decimal System. Peering further onward still into the annals of library science, one can find even more creative and revealing methods of indexing human knowledge. In doing so, one might even be inclined to believe that the state of the science has come so far as to be considered solved. Alas.

Interesting philosophical question, but entirely beside the point that I am making, because you and I didn't have to do either one before having this discussion.

You can't fathom reading?

Please tell me you're actually an AI so that I can record this as the pwn of the century.

What's different is nearly everything that goes on inside. Human brains aren't a big pile of linear algebra with some softmaxes sprinkled in trained to parrot the Internet. LLMs are.

I'm sure that the business case for it hasn't gone away, but unless they can side-channel some information out of the TPM, this proposal doesn't appear to give the server the ability to uniquely identify a visitor except through the obvious and intended method. So: maybe, but this appears to be separate.

Actually, it's the name of the paper. And while the team also developed and released a system to elicit the behavior by doing what you described, it's entirely possible that the researchers thought the title to be the most important finding in their work.

The benchmarking tool being used in this post accounts for that using multiple runs for each invocation, together with a warmup run that is not included in the result metric.

First of all - very cool, played with this for a few minutes before discovering the following bug:

In Safari (iOS 18.3.1) if you set the Mass slider to 0 and increase Tension, not only does the app crash, but a repeated clicking noise starts, and persists, even after the tab is closed - even after Safari itself is closed! Seems to be a Safari bug. I have reproduced it 3x.

If you reproduce this and want the noise to go away you have to start another app that tries to play sound.

I can write that query for you:

> select * from subscribers

What is the context for submitting this on HN? Assume I’ve been living under a rock.

Wait til you guys hear about DNA transcription error rates!

An excellent choice.

Oh I am definitely stealing that.

6PPD -> 6PPD-quinone

That’s actually great news - neuroplasticity turns out to increase as we age.

Yes. They put "experiment.py" which contains the timeout condition right into the directory of files that they were allowing their agent to access and modify. Don’t act surprised when it accesses it and tries to modify it. This is totally in-scope behavior and 110% expected by anyone who's played around with building an agent for more than 20 seconds.

From the article: "This information, combined with the starting point of that object, allows its future positions to be calculated."

It doesn’t go into the details of recalibration, I’ll give you that.

Don’t forget - the Chrome DevTools console can be styled and even renders ANSI escapes, so the text read by the LLM might be completely different than what you see on-screen.

https://developer.chrome.com/docs/devtools/console/format-st...

Yes, that is another thing that Commerce is doing. And your assumption of the motivation for this proposal is probably accurate. But the two things are not the same. Here, the wording of the proposed rule doesn’t appear to limit it in scope to H100s and GroqRacks. That makes this a separate issue. It also imposes entirely separate restrictions and reporting requirements on an entirely different class of provider. I’m not sure why you’re insisting that we treat them as the same issue.

Reporting known instances of transactions which could result in the training of a large AI model with potential capabilities that could be used in malicious cyber-enabled activity.

Which is to say: every language model and image generator with >100M params. In other words, IaaS providers must report nearly every transaction, since you can train a LoRA module for a small model on a few hundred ARM cores, or on nearly any datacenter GPU.

To be clear though, the rule doesn’t include prison time for you, the GPU user. The prison time and/or fines are for the noncompliant IaaS provider, which means that cloud GPUs (and possibly every other resource) will be much more expensive and harder to access.

Are you talking about the payment Mozilla receives for keeping Google the default search engine on Firefox? Just change it.