cannonpalms

Awesome, I will take a look! We need something for our end-to-end tests at work that we can use and trivially spin up buckets for millions of tests in parallel.

All of this was public knowledge, and there is nothing damning about knowing someone who worked on something.

Is there any "local"/minio-esque object store properly implements the full conditional GET/PUT/DELETE spec, ETag, etc.? I have struggled to find this in the past.

The incentives to create fake engagement to satisfy their actual users who want discussion are quite clear. Doing this also gives reddit an advantage when monetizing their data. Scrape posts & comments for free, and you won't know which are LLM-generated and which at least have a human in the loop (but the human still may use an LLM, so this is where fingerprinting comes in). Perfect for incentivising the ai labs / other consumers of reddit data to pay up for an official feed.

It seems to me that this is the way the market is heading. Strange bleeding edge perf or sprawling complexity feels like the last niche of front end engineers. The rest will move further down the stack or be replaced.

Having to build a distributed system to sync storage between two devices or build your own custom hardware isn't exactly trivial

This explanation doesn't make sense to me, because it is well known that groups of agents can coordinate already. There are much lower latency options available.

Supply and demand has to be considered. The more parties aware of the vulnerability, the more attractive sellers (reporters) have to make their ask to the buyer (defender).

I have had success in rooting these out by using the correct linguistic terminology for each. Negative parallelisms, tricolons/polycolons, etc. I haven't come up with the proper terminology for all of them.

This was in India, where he describes the medical knowledge of providers as subpar at best.

Search licensing would be one of the big ones

You are painting with extremely broad strokes here.

Claude, for example, already does write a git commit trailer with a session ID.

If you read the linked post, he covers this

It is "artificial" in the sense that the price is set well below the natural clearing price based on available supply and demand.

I guess, in theory, the prior distribution of language would allow for improved performance in some cases, especially where input quality is low.

Is this the kind of thing that retractions are typically issued for, or would it simply be your responsibility to submit a new paper correcting the record? I don't know how these things work. Thanks.

Just a quick shortcut

The canonical solution in this space so far is https://github.com/Dicklesworthstone/agentic_coding_flywheel..., and I would bet that this tool is just a paid version of the same, or worse, just a paid wrapper

Just don't open a comment with

> You're absolutely right!

And you're good

I believe this was the original thread.

Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API) | https://news.ycombinator.com/item?id=46661308

I doubt the equities analysts would appreciate this as much as a tech nerd would. It'd be seen as a step backwards and evidence of having no clue which way the world is heading.

So long as (fast/optimal) real-time access to new data is not a concern, you can introduce compaction to solve both problems.

You left behind a script clearly written by your LLM tool that patched some problems in your code. It's undeniable.

I'm all for using the tools available, but I don't understand lying about it.

https://github.com/whispem/minikv/blob/main/fix_ci_complete....

You're absolutely right(em dash)

Hilarious

Those whiteboarding sessions and discussions used to serve as useful opportunities for context building. Where will that context be built within the cycle now? During a production incident?

This is just a layer of emotion on top of raw capitalism. And it will always prove to be a lie when push comes to shove.

Time-to-market favors chromium. It's also by far the most commonly used engine for headless browsing, creating lots of useful prior art.

Google's AI overview regularly hallucinates or gets the answer wrong. Obviously if you're going to run inference on every search from billions of users, it has to be a very cheap model.

You can already do what you're looking for by reading the browser cache as new data is cached. This would allow you to see the site as it was loaded originally, instead of simply fetching an updated view from a URL. The data layout for the cache in Firefox and Chrome is available online.