Spotify wants you in prison for skipping lines of code
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- content
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.
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.
- Dominant language
- HTML
- Stars
- 136
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from spotify/spotify.github.io
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
spotify/spotify.github.io#30 · 5 comments · 25 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
spotify/spotify.github.io#29 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
spotify/spotify.github.io#21 · 9 comments · 1 reaction ·
All issues in spotify/spotify.github.io
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TheOdinProject/curriculum#31408 ·
-
archived coursework help wanted scope: curriculum
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
freeCodeCamp/freeCodeCamp#70260 · 1 comment ·
-
雪鸿集 Open待处理 申请收录
Difficulty 1/5 Under an hour Newbie friendliness 72/100
travellings-link/travellings#4000 · 1 comment ·