spotify / spotify/spotify.github.io

Spotify wants you in prison for skipping lines of code

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
136
Forks
49
PR merge metrics
No merged PRs in 30d

Description

"Spotify's takedown notice is procedurally deficient under 17 USC section 512 in GitHub's own DMCA guidance. Identifies only a PR URL, not specific file paths, and offers no factual explanation of the alleged circumvention. The notice doesn't identify any Spotify code, binaries, or decryption keys within our repository because none exist. Our repositories contain only independently authored patch logic. Patches do not decrypt, extract, or distribute Spotify works. They operate only in lawfully obtained copies that users provide themselves. The asserted technological protection measures are at most business model restrictions, such as timers, skip counters, and the user interface. Courts have repeatedly held that these rules do not constitute effective access controls. Under section 121, C Chamberlain versus Skylink, C Lex Mark versus Static Control in 2004. " - Louis Rossmann
https://www.youtube.com/watch?v=kgFCC9haqB4

I see this as a huge issue, and while the lawyers want to chat (kill open source), I figured I would drop this here to inform you and the general public that this is happening. Apparently, this information is getting taken down quickly (censorship, really, Spotify?), so I'd urge you to inform others without directly disclosing this issue link. The video link above is sufficient.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository file, test, or entry point, and does not specify a concrete change. Start by reviewing the takedown context and repository purpose; a contributor would need an explicit documentation or content scope before completion could be assessed.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.