<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>izacus</author><text>&amp;gt; Just as an example, if I wanted to get a list of every song I liked on Spotify and import it into Apple Music, how would that even work? The songId of Spotify is undoubtedly different than the one Apple uses. Are Apple and Spotify supposed to agree on a common file format?&lt;p&gt;Why wouldn&amp;#x27;t it work? Desktop apps had m3u playlist formats which could be read by multiple players - from Winamp on desktop, iTunes on a Mac or even car headunits. It&amp;#x27;s now kinda wierd to say that rockstar engineers of Apple&amp;#x2F;Spotify can&amp;#x27;t find a way to export playlists and liked songs (a global singletons essentially) they got from the SAME publishers and probably ingest from the SAME content owner data sources.</text><parent_chain><item><author>somethingAlex</author><text>What are consumers intuitively expecting compliance with this law to look like?&lt;p&gt;Data from one service may be in an entirely different schema than the service you want to import it too - let alone format. Service A may summarize your data and throw away the granular stuff, but service B runs on the granular data.&lt;p&gt;Are consumers going to implement ETL pipelines to achieve portability? Are they expecting to hook up streaming mechanisms for enormous swathes of data?&lt;p&gt;Just as an example, if I wanted to get a list of every song I liked on Spotify and import it into Apple Music, how would that even work? The songId of Spotify is undoubtedly different than the one Apple uses. Are Apple and Spotify supposed to agree on a common file format?&lt;p&gt;I agree with the intent of the law but I&amp;#x27;m not surprised most services do not offer an automated way to take out data. It&amp;#x27;s a rare case, often a heavy workload, and there&amp;#x27;s really no way to guarantee the data you receive is actually portable.</text></item></parent_chain></comment><story><title>Data portability, the forgotten right of GDPR</title><url>https://www.alias.dev/report</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dsr_</author><text>There are incentives for, say, Mastodon to be able to ingest your tweeting history, or for Linked-In to eat your Facebook social graph.&lt;p&gt;There&amp;#x27;s no incentive other than the law for Twitter or Facebook to make that data exportable.</text><parent_chain><item><author>somethingAlex</author><text>What are consumers intuitively expecting compliance with this law to look like?&lt;p&gt;Data from one service may be in an entirely different schema than the service you want to import it too - let alone format. Service A may summarize your data and throw away the granular stuff, but service B runs on the granular data.&lt;p&gt;Are consumers going to implement ETL pipelines to achieve portability? Are they expecting to hook up streaming mechanisms for enormous swathes of data?&lt;p&gt;Just as an example, if I wanted to get a list of every song I liked on Spotify and import it into Apple Music, how would that even work? The songId of Spotify is undoubtedly different than the one Apple uses. Are Apple and Spotify supposed to agree on a common file format?&lt;p&gt;I agree with the intent of the law but I&amp;#x27;m not surprised most services do not offer an automated way to take out data. It&amp;#x27;s a rare case, often a heavy workload, and there&amp;#x27;s really no way to guarantee the data you receive is actually portable.</text></item></parent_chain></comment><story><title>Data portability, the forgotten right of GDPR</title><url>https://www.alias.dev/report</url></story>