Basically because they’re afraid that some transformer models can quickly rebuild the recommendation algo
developer.spotify.com/blog/2024-11-27-changes-to-the-web-api
developer.spotify.com/documentation/web-api/reference/get-recommendations
Explain in ktt2 terms
Spotify hiding s***, tryina give OvOAnon some fresh red meat
Explain in ktt2 terms
it’s like how KTT1 had PMs and KTT2 still doesn’t after 5 years
Can someone explain? We're all nerds here but there's levels...
They’re making it so apps need user permission to access any Spotify data, even public stuff like playlists or albums. They’re probably doing this for a few reasons: to give users more control over their data, improve privacy and security, crack down on misuse of Spotify (like scraping or unauthorized data collection), and maybe to stay in line with stricter privacy laws like Europe’s GDPR and stuff.
They’re making it so apps need user permission to access any Spotify data, even public stuff like playlists or albums. They’re probably doing this for a few reasons: to give users more control over their data, improve privacy and security, crack down on misuse of Spotify (like scraping or unauthorized data collection), and maybe to stay in line with stricter privacy laws like Europe’s GDPR and stuff.
Sounds good
it’s like how KTT1 had PMs and KTT2 still doesn’t after 5 years