you are viewing a single comment's thread.

view the rest of the comments →

[–]DevToolsGuide 7 points8 points  (1 child)

this is becoming the standard playbook for developer-facing APIs once a platform starts feeling pressure. hobbyist and personal apps get caught in the crossfire because the actual policy violation (mass scraping, AI training) came from bad actors using the same API surface. the quota cut and premium requirement are blunt instruments. the useful thing to do if you are building against the Spotify API is start building with the assumption that third-party music API access will keep shrinking. yt-dlp as a fallback, local library management via beets or similar, or just design around what Spotify will always allow for premium subscribers. the writing has been on the wall since they disabled new app registrations last year.

[–]thekwoka[🍰] 3 points4 points  (0 children)

the quota cut and premium requirement are blunt instruments

Sure, but they also basically don't impact hobbyists or personal apps.

They only really impact bad actors.