> Most coordinated disclosures follow a familiar pattern:

> 1. A vulnerability is reported.

> 2. A dialogue begins.

> 3. Severity is discussed.

> 4. Engineering teams investigate.

> 5. Fixes are developed.

> 6. Users are protected.

> 7. Public disclosure follows.

8. The author prompts an LLM to write a blog post.

9. HN users are wasting time, unsure which parts of the post come from the actual prompt, and which are hallucinated world knowledge slop.

Maybe the bug report got ignored because they posted another 1000 slop reports, who knows.

	▲	dakolli 3 hours ago \| parent \| next [-]
		The disclosure seems pretty straight-forward, definitely some LLM assisted writing here, but not nearly as bad as most of the other stuff on this site.
	▲	skeledrew 3 hours ago \| parent \| prev [-]
		Wonder who's fault it is when a critical security issue goes unresolved because "slop" report (sure ain't the reporters').