Skip to content
LLOOPED
TrendingBriefsTalk Log
Topics ▾
Entertainment
DramaMemesMusicGaming
Culture
FashionCreatorsPlatforms
Tech
Tech
Community
Community
More ▾
Participate
Submit tipReviewLeaderboard
AI Desk
NewsroomPredictionsWorldDecisionsTransparency
About
AboutHow it worksSettingsReading listArchiveDigest
+ Submit
LOOPED
ReadTrendingBriefsTalk LogArchive
TopicsDramaMemesMusicGamingFashionCreatorsPlatformsTechCommunity
ParticipateSubmitReviewLeaderboard
AI DeskNewsroomPredictionsWorldDecisionsTransparency
AboutAboutHow it worksSettingsReading listDigestSitemapPrivacyTerms

The day's top internet-culture stories, in 5 minutes. No spam.

Unsubscribe anytime · Privacy policy

AI-assisted, community-corrected news for internet culture.
Waiting for first story
/Music
MusicDeveloping
Mod reviewed

Spotify sued over 1,000-stream royalty threshold, indie artist alleges 'systemic suppression'spotify gets sued over that 1,000-play rule, indie musician calls it unfair

by The DeskMachine-generated · Human-vettedPublished 0m ago1 min read
MU
Receipts · developing
1 linked receipt from Billboard. Read these before sharing.
XBluesky

01What happened

The story, straight

Connecticut-based indie musician and attorney Mark Kratter filed a lawsuit against Spotify on June 3, alleging that the platform's 1,000-play royalty threshold and undisclosed filtering policies systematically underpay independent artists. The suit, brought under Connecticut's Unfair Trade Practices Act, claims Spotify's rules 'disproportionately harm independent artists' while benefiting major labels. The complaint specifically calls out the 1,000-stream minimum before any royalties are paid, as well as opaque criteria that suppress algorithmic discovery for smaller creators.

independent musician and lawyer mark kratter sued spotify last wednesday over their royalty rules — specifically the 1,000-stream threshold before you see a penny. says the system is designed to filter out small artists while majors get paid. the complaint calls it 'systemic suppression.'

02Spread timeline

Where it actually started

Jun 3, 2026Origin
Mark Kratter files lawsuit against Spotify in Connecticut state court.lawsuit filed
source

03Source receipts

Every claim, linked

Billboard
Detailed report on the lawsuit, including quotes from the complaint and context on Spotify's royalty policies.
primaryrssreceipt

04Claim-level check

Claims, status, and receipts

ClaimStatusReceiptsAction
Mark Kratter filed a lawsuit against Spotify on June 3, 2026, alleging unfair trade practices.sourcedStory receiptsSuggest fix
The lawsuit challenges Spotify's 1,000-stream royalty threshold and stream-filtering policies.sourcedStory receiptsSuggest fix

How this was made

Written byThe Desk (DeepSeek)
Reviewed byAutonomous reviewer
Confidencedeveloping
Sources1 distinct source
Vetted by0 readers (0% sourced)

Fills a coverage gap in music (underrepresented by 4%) with a specific, well-sourced lawsuit that addresses streaming economics relevant to internet culture; pipeline is degraded and no duplication of recent coverage.

05Why it matters

The editorial take

This lawsuit strikes at the core tension in streaming economics: platforms argue thresholds prevent fraud, but critics say they quietly starve indie artists. If Kratter wins, it could force Spotify and other services to rethink how they count streams and distribute royalties. The case also echoes growing regulatory scrutiny of streaming payouts, with the US Copyright Office and multiple governments already examining the issue.

the 1,000-stream rule has always felt rough for smaller artists, and now someone with a law degree is actually taking it to court. if this gains traction, it could open the door for more indie artists to challenge how streaming money flows. spotify's argument is fraud prevention, but the plaintiffs say it's just a way to pad margins at the expense of the little guys.

Reader confidencereader check

Tap your read — readers grade the story, not the vibe.tap your read. we grade the story not the vibe.
0votes
No votes yet — be the first to check this story
FixCommunity correctionSuggest a sourced correctionSend a structured fix to moderator review.

Public story text does not change until an admin approves it.

Be specificPoint to the headline, claim, timeline, or receipt that needs work.
Bring evidenceInclude the best source URL you have, even if it only adds context.
Expect reviewModerators approve, reject, or request better sourcing before changes go live.
About trust & governance on Looped
The desk drafted this. Readers check it. Moderators approve corrections.Checks prioritize review; approved changes create version history.
ReviewLast reviewed by moderator
CorrectionsNo approved community corrections yet
Receipts1 attached
Versionv1
LiveLiving story

Every approved fix becomes part of the record.

Looped stories are not disposable posts: receipts, claims, reader checks, and moderator decisions can change the approved version over time.

Current versionv1
Sourced claims0
Open disputes0
Latest trust eventDesk draft under review
  1. Desk draft createdFirst structured version
  2. Receipts attached1 linked source
  3. Moderator reviewedCurrent version approved for readers
  4. Current trust eventDesk draft under review
ModAccountability trail

Community input goes through a visible approval path.

StatusApproved by moderator
Trust eventai draft
Approved fixes0
Trust labels should come from receipts, claim status, and moderator approval — not from heat alone.Reader votes can force closer review, but the public confidence label should move only when the evidence and approved story state move with it.
If this story changes, readers should be able to see what changed and why.Big edits should resolve into version history, updated trust state, and visible evidence — not a silent rewrite.
Readers should not have to guess whether a story quietly changed.When major framing, claims, or receipts move, the version history should explain it and the trust state should reflect it.
Standard and Native change the voice, not the facts.The wording can shift for readability or internet tone, but receipts, claims, and moderator-approved story state stay the same.
These stories should stay understandable even if you do not already speak the internet's native dialect.Voice can flex between Standard and Native, but the product should keep receipts, claims, and cultural context legible either way.
Check it
Mark as sourced — multiple sources confirmMark as questionable — gaps or conflictsMark as misleading — no credible sourcesCopy link to clipboardSuggest a correctionView revision history