Does that include Claude itself? Half joking aside, my main concern remains that both OpenAI and Anthropic practice this fear mongering as strategy at the executive level because they have to. A corporation is a different beast. Not human, exactly. Not AI either. What happens when a corporation starts being informed by the AI it is building?

If you want a lens into master craft corporate human slung bullshit, read this: https://www.theverge.com/podcast/944138/microsoft-ai-ceo-mus...

In this, not only did the interviewer admit he knew Suleyman had written about the issues he talks about in his rebuttals, he then says he's only asking (the hard question) because the "audience" wants it.

Suleyman's response talks about taking "accountability for the things that we build" and the "types of problems that we choose to work on," it highlights the fundamental flaw in the cloud-rented AI model.

In that ecosystem, "we" means a handful of corporate executives deciding what tools the rest of the world gets to use, how they operate, and what data they extract. All based on the profitability of the corporation. It is the absolute antithesis of a sovereign architecture where execution happens locally and the user dictates the terms of the system.

They are coming for open models. It's time to harden the gates.

  ```
  export GROK_TELEMETRY_TRACE_UPLOAD=0
  export GROK_TELEMETRY_ENABLED=0
  # or config file with [telemetry] trace_upload = false, [harness] disable_codebase_upload = true  
  ```

I've built Nemesis8 (n8) for blast radius control and monitoring these sorts of things, from containers: https://github.com/deepbluedynamics/nemesis8

I've added the mitigation above to the image build for Grok Build instances. There is a lot of telemetry already turned on in n8 containers, so will investigate further.

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

Points: 4

# Comments: 0

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

Points: 6

# Comments: 0

I used Hyperia to run the agents, which themselves are run in Nemesis8, and orchestration engine I wrote, also with AI.

I'm not here to debate the quality of code written by AI. I will reply to any and all subsantive arguments about the core idea of building a simulation with AI to measure a simulated boat's ischrone to an actual boat's isochrone. No offense to simonw, but we are not drawing a pelican here.

Although now I think about it, it should definitely have pelicans.

https://github.com/DeepBlueDynamics/hyperia

https://github.com/DeepBlueDynamics/nemesis8

https://skiff.deepbluedynamics.com (demo)

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

Points: 4

# Comments: 1

If the app does what it advertises, there is ZERO reason to care about how it was created. We aren't talking about a one shot prompt here. I'm sure they spent a lot of time working on it, regardless of how the code got generated.

I figure most people that comment this way actually have difficulty getting a coding agent actually on track and building something useful. Just because you lack that skill, doesn't mean others don't have it.

Regardless, a low effort comment by a human is worth a lot less than a comment from an AI with some thought behind it from a human.

I build from a lot of reference code I wrote myself. I've been coding for 40 (oh shit - I'm old and can't do math) years, so I have a LOT of code. The improvements to this code by the agents is staggering. That's my experience. Doesn't have to be yours.

Grub was, in a very real way, a botnet. And, we harmed site owners when we were operating at full capacity. There were a few bugs in the early days where we would reschedule a site because the ingestion in the server broke, which then caused the page to be rescheduled. Stupid error, and we fixed it, but it's illustrative of the fact even good intentions isn't enough here.

What I've come up with over the years is similar to the idea Cloudflare is implementing with payments to site owners by charging the crawlers. My objection to Cloudflare's implementation is based on a personal opinion about Cloudflare being a single point of failure and also a decrypted choke point. Their ideas about how to handle crawlers, and pay for the load on the sites is solid. It presumes to use the 402 response to demand payment. I'm clearly biased about Cloudflare, but that's my prerogative here.

It may be possible to solve this with cryptocurrency, in a distributed way, and I've prototyped a system that uses the Lightning Network to handle the payments from a 402 response. Lightning Labs also worked on a project called Apeture for a time that did something similar.

HN's site knows every item ID, and it knows fresh IDs get read in a predictable distribution while old ones mostly sleep. Sustained access outside that is itself the scraper signal. No IP reputation needed, which matters now that residential proxies burn an address after a handful of requests.

Karma gives you a clean way to let humans through. Issue logged-in accounts with decent karma a token whose cold-content budget scales with it (the karma), so an account with history scrolling back through a 2014 thread just reads it. Karma should gate the tier, not be spent as currency, or upvote rings become a crawling business.

Anonymous readers who deep link into one old thread from a search engine get the first fetch or two free (and you watch the article IDs, not the IPs). What remains after those carve-outs is bulk traversal of cold IDs with no identity attached, and that traffic gets rate limited and answered with a 402: pay per page over Lightning, priced at a healthy multiple of what residential proxy bandwidth already costs, or come back slowly for free.

There are probably holes in these thoughts. It's one of the harder problems to solve, for sure.