How it would be achieved is a pretty important bit! One which Dario is not proposing any concrete solution for other thanks hand waves at some gov safety committee.

Would this restrict downloads of an open model, or publishing?

Say we ban domestic hosting un-approved open models. How does Dario propose to ban downloads from abroad? You can’t tell what an encrypted payload contains, do we need to restrict encryption?

In any case, I’d summarize my position as “you cannot stop open source AI, and attempts at it will inevitably empower bad actors relative to good ones.”

I didn't give it much treatment because my frame of reference is about open vs closed AI, and I don't see a lot of daylight in safety concerns between the two.

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

Points: 310

# Comments: 215

Cash App was not an acquisition, it originated as a hackweek within (what was then called) Square.

Possibly you’re thinking of the Afterpay acquisition?

“I don’t really have a strong preference between the two” is another way of saying “the product isn’t sticky”, which is another way of saying “this provider has very little room to increase margins”

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

Points: 3

# Comments: 0

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

Points: 1753

# Comments: 503

In any case, drug dealers really don’t need to do any pushing, the drugs sell themselves. Have you ever taken an opioid? The idea that unfettered access would result in less addiction and death is a pretty remarkable POV

I think the first step of thinking about war objectively is to consider how each side sees it. The US POV is no less circular, from Iran’s perspective - they could list any number of provocations from the US to justify arming themselves, none more obvious than the war itself.

The debate around who started the hostility is ultimately pointless, the question is what to do about. Ideally the answer isn’t “arm for obliteration because the other side started it”

What you’re describing sounds more like code review guidelines, which can be explicitly brought into context at specific times during a change. A memory system is both too complex and less accurate for this

I think with automatic creation you need async consolidation (calling it dreaming is a little dramatic for my taste).

My implementation is at Elroy.bot, I recently wrote about different approaches to agent memory here: https://tombedor.dev/approaches-to-agent-memory/