HN user

tucnak

585 karma

github:tucnak mailto:ilya@hrest.org

Posts14
Comments785
View on HN

I think people are afraid to read the documentation for postgres.

Postgres may introduce a single-file embedded filesystem because what the hell, but the irony is all these guys won't even notice it. The same people that say Postgres backups are too hard.

Yeah, I abandoned Breaking Bad around mid-season 2 because of how boring, slow, and repetitive it had become. Better Call Saul, on the other hand, was constantly clicking for me, from one episode to another. The writing is magnificent. There were a few slow-rollers, of course, but they were nothing compared to drip-feeding in Breaking Bad.

There are semi- and fully submersible variants on the way, that can stay underwater for prolonged periods of time! Sea Baby is growing into quite a few different things over the months.

Yeah, Adobe should be afraid because... checks notes... had the government not intervened, the "creative software industry" would willingly have sold out to Adobe completely years ago, and so there would be no "war" on them. Rally the troops.

We are an open-source project ourselves, recently crossing 24k stars, and our framework processes over 15 billion LLM tokens daily to find software vulnerabilities.

I'm sorry, but talking Github stars comes off as borderline pathetic.

The point of contention is whether Mythos is the product of its intelligence or its harness; the results like this, and other similar testimonies, call into question too-dangerous-to-release marketing, and for good reason, too. Because it is powerful marketing. Aisle merely says the intelligence is there in the small models. I say, it's already clear that competent defenders could viably mimic, or perhaps even eclipse what Mythos does, by (a) making better harness, (b) simply spending more on batch jobs, bootstrapping, cache better, etc. You may not be doing this yourself, but your probably should.

FWIW, Apple Virtualization framework is fantastic, and Rosetta 2 is unmatched on other Arm desktops where QEMU is required. For example, you can get Vivado working on Debian guest, macOS host trivially like that.

You're right on ergonomics.

CodeAct is one way to abstract away some things, and bring others to the forefront. Especially when it comes to anything requiring a sidecar for mTLS, or something agents must be aware of, like error handling for whenever some call fails deep inside the stack. Troubleshooting access issues is key, during tool development and when using said tool in production, too. For many, many things, CodeAct is simply superior to naive calling conventions that you see around MCP clients, think OpenAPI.

The .com purist advice is sound but you're not getting four-letter domain names that way, and in some ccTLD zones you can still.

I was price-gouged out of owning a single, rare .icu domain when renewal fee for it went from 20 usd to 220 usd overnight, just for this one domain... I'm pretty sure it's not Gandi, but the TLD opetator, because other .icu domains I've had were fine. I decided to eventually abandon them all anyway. Moved away from Gandi later when they started doing gouging of their own, too.

What is HN's opinion on Dynadot?

What you're talking about exists, and it's called Relationship-based Access Control, or ReBAC. There are a few implementations, Zanzibar paper, etc. The issue is not capability system, it's governance. The operator needs to write policies, of course! They don't want to read, write policies, audit other people's policies.