AI policies that don't suck
Hi folks,I don’t have a blog, but I have some thoughts about our current AI moment. I’m hearing a lot of good and bad ideas about how to organize around safety and paced development, but I haven’t heard these ideas yet and wanted to share them here in hopes that some discussion might take place or someone with reach steals them.1. Much of the xrisk discussion hinges on embodied AI.
- ▪Hi folks,I don’t have a blog, but I have some thoughts about our current AI moment.
- ▪I’m hearing a lot of good and bad ideas about how to organize around safety and paced development, but I haven’t heard these ideas yet and wanted to share them here in hopes that some discussion might take place or someone with reach steals
- ▪Much of the xrisk discussion hinges on embodied AI.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,963 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=49112835 |
| Publication time | Thu, 30 Jul 2026 17:13:21 +0000 |
| Retrieval time | 2026-07-30T18:57:29.406Z |
| Last seen | 2026-07-30T18:57:31.195Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 9VGQBPk4n4vr · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
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
Hi folks,I don’t have a blog, but I have some thoughts about our current AI moment. I’m hearing a lot of good and bad ideas about how to organize around safety and paced development, but I haven’t heard these ideas yet and wanted to share them here in hopes that some discussion might take place or someone with reach steals them.1. Much of the xrisk discussion hinges on embodied AI. Robots with arms and legs are robots that can kill, displace jobs, etc. All manufacturing of such robotics should come along with a mandatory registration, annual inspections, and functional kill switch that anyone can operate like a fire alarm.2. Rapid model advancement, especially recursive self-improvement, sounds like the center of risk but it really isn’t.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.