Feed

Page 3 of 27

Erik Craddock@eriklink

Import AI 462: Superpersuasion; self-sustaining AI; paths to ASI

“Our findings establish frontier AI as a more capable conversational persuader than the most prepared, incentivized, and expert humans we could recruit. Training humans does not appear to close that gap,” they write. “As access to these systems continues to grow, the question is no longer whether AI can out-persuade humans but how, where, and on whose behalf this capability will be exercised.”

Import AI 462: Superpersuasion; self-sustaining AI; paths to ASI

Import AI

Import AI 462: Superpersuasion; self-sustaining AI; paths to ASI

Welcome to Import AI, a newsletter about AI research. Import AI runs on arXiv, cappuccinos, and feedback from readers. If you’d like to support this, please subscribe. Subscribe now AI can decisive…

linkby Erik Craddock (@erik)
Erik Craddock@eriklink

SaaS is dead; long live SaaS!

That era of building a viable SaaS business in a few months is gone. I mean, it technically still exists today but only in the arbitrage sense that the rest of the world hasn’t yet caught on to how quickly and easily software can be built. It’ll be gone soon, I promise.

Jamie’s blog

SaaS is dead; long live SaaS!

How AI has changed the SaaS equation: what’s no longer valuable, and what remains

linkby Erik Craddock (@erik)
Erik Craddock@eriklink

There Are No Instances in atproto — overreacted

In atproto, every app is a projection of the whole Atmosphere, just like Feedly and Google Reader are projections of the entire Blogosphere. You mostly “decentralize” by swapping your hosting, and/or by making and trying new apps. Running many full copies of the Bluesky database server is possible, but it’s not any more useful than running many copies of Google Reader.

There Are No Instances in atproto — overreacted

overreacted.io

There Are No Instances in atproto — overreacted

Like RSS and Google Reader.

linkby Erik Craddock (@erik)
Erik Craddock@eriklink

The future of the con is already here, it's just not evenly distributed

Here’s a partial list of scam-relevant capabilities that LLMs have that would previously require significant skilled human effort per target:

Researching a mark to find out the best way to go after them. Personally tailoring all communication with a mark in mind, dynamically adjusting based on how they respond to various approaches. Cloning the voice of a person the mark trusts, like a relative. Plausible, real-time deepfaking of a video call. Building a plausible-looking corroborating fake web presence 6. Realtime monitoring of compromised resources, and dynamically building up the scam based on this monitoring. Better triage and discovery of marks. Avoiding signature-detection based spam filters (shown by Heiding et al). Scanning for and chaining known exploits in unpatched deployed software. Mass scanning isn’t new, but cheaply building tooling that can keep tabs on the latest CVEs and learn new tricks is7.

These are capabilities that exist today, and they’ll only improve from here. We should look at these skills as a floor, not a ceiling.

The future of the con is already here, it's just not evenly distributed

manishearth.github.io

The future of the con is already here, it's just not evenly distributed

The Set-Up Johnny Hooker: Sometime after 2:00, a guy’s gonna call on that phone there and give you the name of a horse. Imagine yourself, perhaps a typically-well-paid, tech-savvy professional, on …

linkby Erik Craddock (@erik)Credit: Manish Goregaokar
Erik Craddock@eriklink

CLI Authentication, the Right Way

The user opens the URL on whatever device they want, not necessarily the box running the CLI. They log in, see the requested scopes and the client name, confirm the short code matches what the CLI printed, and approve.

CLI Authentication, the Right Way

ABGEO's Personal website

CLI Authentication, the Right Way

Most CLI auth flows spin up a localhost server and pray your browser cooperates. That model breaks the moment you're SSH'd into a server. RFC 8628 fixed this in 2019 and a lot of tools still haven't caught up.

linkby Erik Craddock (@erik)
Erik Craddock@eriklink

Building Pi With Pi

The most frustrating failure mode right now is that people submit issues that are not in their own voice. They contain an observed problem somewhere, but it has been thrown into a clanker and the clanker reworded it and made a huge mess of it. Typically, it was prompted so badly that the conclusions produced are more often than not inaccurate but always full of confidence. The result is complete guesswork on root causes, fake-minimal repros, suggested implementation strategies, analogies to adjacent but often the wrong code, and long lists of error classes that might or might not matter.

That is worse than no diagnosis.

Building Pi With Pi

Armin Ronacher

Building Pi With Pi

Learnings from post-AI Open Source and how we’re approaching this so far.

linkby Erik Craddock (@erik)Credit: Armin Ronacher
Erik Craddock@eriklink

Import AI 458: Reckoning with the future; and a singularity story

This change maps to a brewing theory among economists: that one consequence of automation via AI is that humans move to figuring out how to validate the outputs and price the operational risks of AI systems. That increasingly seems to me to be what we’re doing inside the company. The more we add AI automation, the more humans move to some “verification layer” that sits atop it. The verification layer sits atop of a much larger “virtual organization” which consists of increasingly large quantities of AI systems working on behalf of humans.

Import AI 458: Reckoning with the future; and a singularity story

Import AI

Import AI 458: Reckoning with the future; and a singularity story

Welcome to Import AI, a newsletter about AI research. Import AI runs on arXiv, cappuccinos, and feedback from readers. If you’d like to support this, please subscribe. This issue consists of a leng…

linkby Erik Craddock (@erik)
Erik Craddock@eriklink

Clanker: A Word For The Machine

A compiler does not feel humiliated when I swear at it, a car does not suffer when I call it a shitbox and a power drill is not oppressed by being handled roughly. An LLM is more complicated than those things, and the interactions you can have with them can be truly uncanny, but a moral status does not appear just because the machine can emit text in the first person.

Clanker: A Word For The Machine

Armin Ronacher

Clanker: A Word For The Machine

Why I like the word clanker and why machines are not people.

linkby Erik Craddock (@erik)Credit: Armin Ronacher
Erik Craddock@eriklink

Prompts are technical debt too

In this sense, prompts are a worse form of technical debt than code. When technical debt blows up, it usually causes errors or a tangible slowdown as you try to understand the code. Prompts will decay silently. Also, even janky code tends to be relatively stable when untouched, but every single model upgrade could turn a functional prompt into a non-functional one.

Prompts are technical debt too

seangoedecke.com

Prompts are technical debt too

linkby Erik Craddock (@erik)
Erik Craddock@eriklink

There Is No ‘Hard Problem Of Consciousness’ | NOEMA

Earth is not metaphysically different from the heavens, living beings are not metaphysically different from inanimate matter, humans are not metaphysically different from other animals. The soul is not metaphysically different from the body. We are all parts of nature, like anything else in this sweet world.

There Is No ‘Hard Problem Of Consciousness’ | NOEMA

NOEMA

There Is No ‘Hard Problem Of Consciousness’ | NOEMA

Consciousness is not separate from the physical world — our “soul” is of the same nature as our body and any other phenomenon of the world.

linkby Erik Craddock (@erik)Credit: Carlo Rovelli