LinkedIn is crowdsourcing its fight against AI slop
LinkedIn has a serious AI slop problem, and it’s now turning to its own users to help fix it. The platform is rolling out a new button that lets users flag posts they suspect were generated by AI. It plans to use that feedback to fine-tune the system that decides how much reach a post gets outside a user’s own network, based on how AI-generated it appears.
- ▪LinkedIn has a serious AI slop problem, and it’s now turning to its own users to help fix it.
- ▪The platform is rolling out a new button that lets users flag posts they suspect were generated by AI.
- ▪It plans to use that feedback to fine-tune the system that decides how much reach a post gets outside a user’s own network, based on how AI-generated it appears.
Digital Trends files mainly under tech. We currently carry 582 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 | Digital Trends |
| Canonical URL | https://www.digitaltrends.com/social-media/linkedin-is-crowdsourcing-its-fight-against-ai-slop/ |
| Publication time | Fri, 31 Jul 2026 10:06:25 +0000 |
| Retrieval time | 2026-07-31T10:12:38.629Z |
| Last seen | 2026-07-31T10:12:38.629Z |
| 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 | kTHhvcT-35Ca · 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
LinkedIn has a serious AI slop problem, and it’s now turning to its own users to help fix it. The platform is rolling out a new button that lets users flag posts they suspect were generated by AI. It plans to use that feedback to fine-tune the system that decides how much reach a post gets outside a user’s own network, based on how AI-generated it appears. The announcement comes shortly after an analysis by Pangram found that more than forty percent of long-form LinkedIn posts are fully AI-generated, and it suggests that the reach-trimming measures the company rolled out earlier this year haven’t been enough on their own.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Digital Trends.
Discussion
0 commentsMore from Digital Trends
