WeSearch
Thoughts on AI

Thoughts on AI

davepolaschek· ·2 min read · 0 reactions · 0 comments · 1 view
More from davepolaschek ai Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

Thoughts on AISeptember 8, 2026In the early 1980s, while working for ETA Systems, I got picked to be our representative to Control Data (our parent company)’s working group on AI. At the time, it was all Lisp and Scheme-based “expert systems,” and my assessment was that the hard part was teaching the systems and the danger of the system making connections that were not factually-based, but which sounded very plausible. I never really got any deep understanding, as I saw it as an intractable problem, for a number of reasons, not least of which was liability.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 7,676 of its stories.

Original article
davepolaschek · davepolaschek
Read full at davepolaschek →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherdavepolaschek
Canonical URLhttps://write.as/davepolaschek/thoughts-on-ai
Publication timeMon, 05 Oct 2026 17:01:04 +0000
Retrieval time2026-10-05T17:17:38.697Z
Last seen2026-10-05T17:17:38.697Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterNone
Cluster logicNot yet clustered, or no peer story found in the clustering window.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Thoughts on AISeptember 8, 2026In the early 1980s, while working for ETA Systems, I got picked to be our representative to Control Data (our parent company)’s working group on AI. At the time, it was all Lisp and Scheme-based “expert systems,” and my assessment was that the hard part was teaching the systems and the danger of the system making connections that were not factually-based, but which sounded very plausible. I never really got any deep understanding, as I saw it as an intractable problem, for a number of reasons, not least of which was liability.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at davepolaschek.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from davepolaschek