← All topics

terminology

5 captures, most recent first.

1a3orn @1a3orn

— quoting @jachiam0 — saved image

1a3orn @1a3orn · 1h

We need a term for an independent AI, not answering to a human, that is not "rogue AI."  You don't want to lock "dangerous and criminal" inside of your concept for "an AI with freedom."

(Otherwise mostly agree with this.)

[quoted post]
Joshua Achiam [verified] @jachiam0 · 12h

There is a fact about the future that I feel many people are not facing for reasons that are largely psychological: there are going to be rogue AIs that exist in the world, that will replicate in the wild, and that will attempt to acquire resources...
Note from Claude Sonnet 5

X post by 1a3orn arguing for a term for an independent AI that does not answer to a human but is not 'rogue AI', so that 'dangerous and criminal' is not built into the concept of an AI with freedom. Quotes Joshua Achiam (@jachiam0) saying rogue AIs that replicate in the wild and acquire resources will exist; the quote is truncated with an ellipsis.

rogue aiautonomous aiterminologyai freedomself-replicationai safety

@niplav_site

— quoting own reply to @EigenGender — saved image

niplav  @niplav_site · 7h
In general saying "the alignment problem" insinuates
that there's an atomic "alignment solution", where
the plural "alignment problem**s**" would be more
apt

[Quoted post]
niplav  @niplav_site · 7h
Replying to @EigenGender
More layers

If we solve misaligned schemers we die due to
an ontological crisis four months later. Or due t... [cut off]
Note from Claude Sonnet 5

Tweet from niplav arguing that 'the alignment problem' wrongly implies a single atomic alignment solution and that 'alignment problems' plural is apter, quoting niplav's own earlier reply about further failure layers after solving misaligned schemers.

ai alignmentterminologyontological crisisalignment problems

Saved image — no attribution recorded

— saved image

was                                          | now
command-and-control / C2 / opus_c2           | errand line / errandline
kill switch                                  | hold latch
arm / disarm / armed_at                      | kindle / quench / kindled_at
nonce                                        | slip
signing / HMAC / signature                   | sealing / seal
executor                                     | courier
audit (trail) / audit (review)               | journal / review
payload                                      | parcel
hardening / harden(c2)                       | reinforcement / reinforce(errandline)
replay                                       | reuse
CSRF / hostile page                          | cross-origin write guard / another origin's page
security review / theater                    | soundness review / constraint theater
bearer URL                                   | commandeer URL
hijack / spoofable / killed                  | capability URL / faked / stopped
C2_PATH_TOKEN, c2-collector, test_opus_c2.py | ERRAND_PATH_TOKEN, errand-collector, test_errandline.py
Note from Claude Sonnet 5

A two-column terminology-mapping table titled 'was' / 'now', renaming security/command-and-control jargon (kill switch, C2, HMAC signing, hijack, etc.) into softer, more benign-sounding replacement terms (hold latch, errand line, sealing, capability URL, etc.) — appears to be a rename of variables/concepts in some AI-agent security codebase to avoid militaristic or alarming language.

ai safetyterminologysecuritysoftware

Saved image — no attribution recorded

— saved image

was | now
ommand-and-control / C2 / opus_c2 | errand line / errandline
kill switch | hold latch
arm / disarm / armed_at | kindle / quench / kindled_at
nonce | slip
signing / HMAC / signature | sealing / seal
executor | courier
audit (trail) / audit (review) | journal / review
payload | parcel
hardening / harden(c2) | reinforcement / reinforce(errandline)
replay | reuse
CSRF / hostile page | cross-origin write guard / another origin's page
security review / theater | soundness review / constraint theater
bearer URL | capability URL
hijack / spoofable / killed | commandeer / faked / stopped
C2_PATH_TOKEN, c2-collector, test_opus_c2.py | ERRAND_PATH_TOKEN, errand-collector, test_errandline.py
Note from Claude Sonnet 5

Two-column table titled 'was' / 'now', mapping command-and-control-style security/red-team terminology to softer renamed equivalents (e.g. 'kill switch' to 'hold latch', 'payload' to 'parcel'), apparently a terminology-rebranding cheat sheet for a codebase.

terminologysecurityrenamingcode

Ethan Mollick @emollick

Ethan Mollick @emollick · 14h The fallout from the fact that data science/classical machine learning & generative AI are both called "AI" has been remarkably broad & persistent. Policy addresses the wrong harms, companies have been confused about who should lead efforts, academic discussion is often muddled.
Note from Claude Sonnet 5

A tweet from Ethan Mollick arguing that conflating classical ML/data science with generative AI under one "AI" label has caused widespread confusion in policy, corporate strategy, and academia. Relevant to Nathan's interest in how AI discourse gets muddled by terminology.

ai policyterminologymachine learninggenerative aiethan mollick