they could open source the tool now that it's essentially worthless behind their wall.
A Note about Spotify Transfers
61–70 of 180 posts
Re: A Note about Spotify Transfers
#62Earlier quoted context omitted.
I apologize. I edited the comment accordingly.
[flagged]
I'm pretty sure it has helped a lot already.
The key part is the "the don't keep data around forever just because you can" part.
Sure, the GDPR got a bit bloated, but I honestly believe most europeans lives got a little bit better because of it.
Edit: I think you're thinking about that horrible cookie warning law. That one needs to burned to the ground.
Re: A Note about Spotify Transfers
#63Earlier quoted context omitted.
According to Spotify’s own site [0], their users have > ...the right to request a copy of your personal data in electronic format and the right to transmit that personal data for use in another party’s service... [0] https://www.spotify.com/us/legal/privacy-policy/#s3 Why can’t a transfer service just use that file? Perhaps, it doesn’t include playlists or liked artists/albums/songs?
I've just requested my data. When I get it I'll take a look and see if it contains playlist information and either edit this comment or post a reply to myself if the edit window has closed with the results. They say it can take up to 30 days to process.
> They say it can take up to 30 days to process.
What the heck...
My current day-job is a multi-tenant SaaS system - every single entity in any of our heterogenous databases is tagged with a tenant identifier (it's also used in composite PKs/FKs in RDBMS databases to prevent incorrect inter-tenant references). Every database system we use (MSSQL, MySQL, Cassandra, etc) has some way to query itself (INFORMATION_SCHEMA, system_schema, etc) which allows for query-generation to generate queries that will reliably dump all data we have associated with any tenant (and by extension, any user) within seconds, even if there's been some ad-hoc or unplanned database design changes (this is the only time I use "SELECT *" in production code!) - this is from a weekend project where I wrote a simple web-application that generates and runs those queries and dumps data to CSV files for tables and JSON for document-stores, shoves them into a zip and uploads them to Azure Blob storage. I didn't build it for GDPR compliance but actually to allow me to undo any unintentional data-deletion without needing to do a full database restore.
My operation's scale is nothing compared to Spotify - but if a tool I built in a couple of days can reliably dump all data about a subject across multiple independent cloud databases within seconds - what's Spotify's excuse?
Re: A Note about Spotify Transfers
#64Earlier quoted context omitted.
This is exactly what I use SongShift for :D Apple's "New Music Mix" is absolute shit compared to Spotify's "Discover Weekly". Most of the stuff Spotify suggests to me are either complete bangers or listen-worthy at worst. Apple's stuff though... It's like they don't have ANY intelligence in the system at all. I listen to 80's gangsta-rap once, then I get modern mumblerap shit for months and months. BUT I do love how…
Btw, I wish Spotify would expand further on Discover Weekly/Release Radar: - a builtin weekly personal archive of DW/RR - a "get me more more interesting music in this style based on other peoples recommendations" button etc.
I’ve used IFTT successfully to run a weekly sync from the current Discover Weekly into a special DW Archive playlist so I don’t lose each weeks suggestions. It’s gotten the job done well.
Re: A Note about Spotify Transfers
#65Earlier quoted context omitted.
This is exactly what I use SongShift for :D Apple's "New Music Mix" is absolute shit compared to Spotify's "Discover Weekly". Most of the stuff Spotify suggests to me are either complete bangers or listen-worthy at worst. Apple's stuff though... It's like they don't have ANY intelligence in the system at all. I listen to 80's gangsta-rap once, then I get modern mumblerap shit for months and months. BUT I do love how…
Btw, I wish Spotify would expand further on Discover Weekly/Release Radar: - a builtin weekly personal archive of DW/RR - a "get me more more interesting music in this style based on other peoples recommendations" button etc.
Tidal auto makes a “most listened” playlist for your all time, for each month, and for the year. It’s a neat feature.
Re: A Note about Spotify Transfers
#66Earlier quoted context omitted.
Btw, I wish Spotify would expand further on Discover Weekly/Release Radar: - a builtin weekly personal archive of DW/RR - a "get me more more interesting music in this style based on other peoples recommendations" button etc.
I’ve used IFTT successfully to run a weekly sync from the current Discover Weekly into a special DW Archive playlist so I don’t lose each weeks suggestions. It’s gotten the job done well.
Yeah, Spotify has even contributed offical IFTTT triggers:
I think this functionality belongs in the core experience.
Re: A Note about Spotify Transfers
#67Earlier quoted context omitted.
I've just requested my data. When I get it I'll take a look and see if it contains playlist information and either edit this comment or post a reply to myself if the edit window has closed with the results. They say it can take up to 30 days to process.
> They say it can take up to 30 days to process. What the heck... My current day-job is a multi-tenant SaaS system - every single entity in any of our heterogenous databases is tagged with a tenant identifier (it's also used in composite PKs/FKs in RDBMS databases to prevent incorrect inter-tenant references). Every database system we use (MSSQL, MySQL, Cassandra, etc) has some way to query itself (INFORMATION_SCHEMA…
The 30 day figure is likely derived from the legal limit under GDPR for a Subject Access Request (one calendar month).
Why commit to a tighter SLA than you legally have to?
Re: A Note about Spotify Transfers
#68Earlier quoted context omitted.
I've just requested my data. When I get it I'll take a look and see if it contains playlist information and either edit this comment or post a reply to myself if the edit window has closed with the results. They say it can take up to 30 days to process.
> They say it can take up to 30 days to process. What the heck... My current day-job is a multi-tenant SaaS system - every single entity in any of our heterogenous databases is tagged with a tenant identifier (it's also used in composite PKs/FKs in RDBMS databases to prevent incorrect inter-tenant references). Every database system we use (MSSQL, MySQL, Cassandra, etc) has some way to query itself (INFORMATION_SCHEMA…
As someone else mentioned, there's a legal maximum, and I think a company is also held to their quoted timeframe (and they may be required to quote a timeframe as well).
Additionally, having a delay can be useful to make it harder for someone to take over your account, and grab all your data; especially if there's sensitive data that might not be otherwise accessible or enumeratable through the UI or API.
Re: A Note about Spotify Transfers
#69Earlier quoted context omitted.
I've just requested my data. When I get it I'll take a look and see if it contains playlist information and either edit this comment or post a reply to myself if the edit window has closed with the results. They say it can take up to 30 days to process.
> They say it can take up to 30 days to process. What the heck... My current day-job is a multi-tenant SaaS system - every single entity in any of our heterogenous databases is tagged with a tenant identifier (it's also used in composite PKs/FKs in RDBMS databases to prevent incorrect inter-tenant references). Every database system we use (MSSQL, MySQL, Cassandra, etc) has some way to query itself (INFORMATION_SCHEMA…
It's obviously not a technical problem. The 30 days comes from the GDPR legislation. Spotify is just behaving like an obnoxious child that needs a good smackdown from the EU. Howevever the GDPR also stipulates that this needs to happen without "undue delay".
I'm not a lawyer specializing in EU law, but I think this wording was put there for the precise reason of being able to punish companies that behave like that.
They'll get to them eventually.
Re: A Note about Spotify Transfers
#70I think this will push me to finally just jump to Apple Music (even though it’s worse and will now be harder to do, plus I’ll miss discover weekly). Spotify’s attack on podcasts with exclusivity and trying to destroy the open standard really bothers me: https://stratechery.com/2020/dithering-and-the-open-web/ Now with this I just don’t have much respect for them. When paired with their complaining about Apple’s polic…
Does Apple actually offer any of the services Spotify is banning via ToS? This feels like both companies are clearly in the wrong for engaging in the same sort of bad behavior.