mk12

It's a bit more subtle than things like "it's not X, it's Y". And even that isn't "wrong", it's just the way AI talks, and therefore an indicator that the author offloaded their thinking to an agent. I've read so much Claude output that it's easy for me to recognize its voice, the same way I could recognize a friend's voice in writing. The examples I quoted are a weird kind of circuitous sentence structure with a certain shape and rhythm that scream Claude to me. Here is how I might rewrite them in human speak:

> Most of the path is automated; a person's attention goes where the risk is

--> We automate as much as possible, focusing human attention on risky parts

> The eval grows with every incident, and every change to the reviewer is scored against all of it.

--> We run reviewer evals against every incident

But that's just my interpretation and my voice. I can't know for sure what the authors would have said if they took the time to write it themselves.

I saw someone say the other day (in response to another blog post being well written) that Anthropic employees have a rule against using AI for writing/external comms? That seems clearly not the case here, normal people don't write like this:

> Most of the path is automated; a person's attention goes where the risk is

> The eval grows with every incident, and every change to the reviewer is scored against all of it.

Just another data point, I got a Beelink S13 Pro N150 running similar things as OP and haven't had any issues. I made changes in BIOS (set "Chipset > PCH-IO > State After G3" to S0 so it boots up again after regaining power) and they are sticking for me.

> Backblaze, Inc. (Nasdaq: BLZE), the cloud storage platform for the AI era, today announced an agreement with CoreWeave, Inc. (Nasdaq: CRWV), The Essential Cloud for AI™.

This will be great for storing my AI data in the AI era of AI.

If this prompt injection doesn’t work then what’s the big deal? If it does work, then what on earth is the whole industry doing feeding untrusted documents to LLMs?

HN title mangling strikes again. “How embryos shape their limbs” and “Embryos shape their limbs” are completely different titles for a discovery.

And there are basic things that shouldn’t be subjective at all but that the IRS refuses to give a clear answer to, like if/how the SALT cap affects deduction for NIIT. There are at least 3 possible interpretations and no consensus.

The Mercurial project has been incrementally rewriting core operations in Rust for several years now. As Pierre-Yves says in the talk, you can do an hg status on a million-file repo in 100ms. I rewrote hg annotate (aka blame) in Rust last year.

> A Practical Challenge: Paper Is Still the IRS’s Kryptonite

Please just give us the prompt.

Programming languages take a long time to build. Zig is a more ambitious project than most. I see lots of progress in these release notes and I'm happy to "give a pass" for the fact that it's not finished.

No one's been giving passes bewildering or otherwise for sweeping issues under the rug, because that didn't happen. The 0.16 release notes are linking to plenty of GitHub issues. If you have additional information to post on an issue then you can copy it to Codeberg: https://codeberg.org/ziglang/zig/issues/30027

Glad I switched from their personal computer backup to using restic + B2 a while ago. Every night my laptop and homelab both back up to each other and to B2. It takes less than a minute and I have complete control over the exclusions and retention. And I can easily switch off B2 to something else if I want.

I recently tried disabling notification in LinkedIn. The designers and engineers working there who created the notifications settings are truly evil. You have to go through 14 categories. Some of them let you toggle the whole category at once, some don't. Some categories are split into 8 more subcategories.

Slop article about a slop redesign.

No, that’s a different thing. “noreturn” is like Rust’s “never” type (spelled as an exclamation mark, !). Also known as an “uninhabited type” in programming language theory.

I took the current events as an opportunity to try switching to Claude and I actually like it much better so far.

I use Syncthing (with Synctrain client on iOS) and it works great.

I’ve seen Starbucks employees in the US do this often.

It does not, at all. Forming that judgment because of “Enter X” is ridiculous. I recognize my friend Claude in disguise all the time on HN and this is not one of those cases.

Notice the “quiet” at the end. LLMS love to shoehorn “quiet” or “quietly” into their writing. I learned this from Sam Kriss’s NYT piece and I keep noticing it now.

This is one of the best posts on I’ve read on this topic in the years since ChatGPT launched. Was hoping it would have gotten more discussion here!

How do we know if newcomers are real? I thing bigDinosaur is reacting to the fact that OP’s entire post and replies appear LLM generated.

The "knowledge base" at the bottom is 100% slop. Why? Why inflict this on people?

This has been happening a lot recently, where an article immediately sets off all my AI alarm bells but most people seem to be happily engaging with it. I’m worried we’re headed for a dystopian future where all communication is outsourced to the slop machine. I hope instead there is a societal shift to better recognize it and stigmatize it.

I hope someone will create a Debian package for Immich. I’m running a bunch of services and they are all nicely organized with user foo, /var/lib/foo, journalctl -u foo, systemctl start foo, except for Immich which is the odd one out needing docker compose. The nix package shows it can be done but it would probably be a fair amount of work to translate to a Debian package.

I have a few different types of content on my website and wanted to offer both individual feeds and a combined feed, so I was disappointed that nothing seems to support the category tag. I settled for prefixing the titles in the combined feed, e.g. "[Blog]" for blog posts.

I think the new async IO is great in simple examples like the one shown in the article. But I’m much less sure how well it will work for more complex I/O like you need in servers. I filed an issue about it here: https://github.com/ziglang/zig/issues/26056

It’s not the same situation because with async/await you end up with two versions of every function or library (see Rust’s std and crates like async_std, Node’s readFile and readFileSync). In Zig you always pass the “io” parameter to do I/O and you don’t have to duplicate everything.

Colors for 2 ways of doing IO vs colors for doing IO or not are so different that it’s confusing to call both of them “function coloring problem”. Only the former leads to having to duplicate everything (sync version and async version). If only the latter was a thing, no one would have coined the term and written the blog post.

If everyone did that, lots of people would still die of preventable causes in poor countries. I think GiveWell does a good job of identifying areas of greatest need in public health around the world. I would stop trusting them if they turned out to be corrupt or started misdirecting funds to pet projects. I don’t think everyone has to donate this way as it’s very personal decision, nor does it automatically make someone a good person or justify immoral ways of earning money, but I think it’s a good thing to help the less fortunate who are far away and speak a different language.

Update: I just tried upgrading again (from 10.11.1 to 10.11.2) and it seems to have fixed things!