this post was submitted on 05 Dec 2024
68 points (100.0% liked)

Technology

37800 readers
91 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Bougie_Birdie@lemmy.blahaj.zone 49 points 2 weeks ago (1 children)

Spotify has vaguely attributed the need for the API changes to improving security:

  • In its blog post, Spotify says that it rolled out the changes with “the aim of creating a more secure platform.”
  • In a community forum post, a Spotify employee says that “we want to reiterate the main message from the blog that we’re committed to providing a safe and secure environment for all Spotify stakeholders.” The post has many pages of replies from frustrated developers.
  • In a statement to The Verge, Spotify spokesperson Brittney Le Roy says that “as part of our ongoing work to address the security challenges that many companies navigate today, we’re making changes to our public APIs.”

This is fairly disingenuous. The affected endpoints are all GET requests, which are read-only requests that provide some data about the track/artist/playlist/etc. There isn't really very much potential to do anything insecure here.

The only thing they're securing is their hegemony.

[–] Delzur@vegantheoryclub.org 18 points 2 weeks ago

"To improve financial security"

Fixed it