Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Regarding the second bullet point, you would have to explain to me what that has to do with GDPR.

Without the gdpr the cheapest alternative is to dev null the email, with the gdpr the cheapest alternative is to re-enable the api.

> I'm not making a point beyond this, so the responses so far have been a bit confusing.

Welcome to the internet :P

I do think your point is a bit weak here to be honest, and that people are reacting to this. It relies on interpreting the original demand as strictly "re-enable the api" and not "comply with the GDPR, and btw we both know the easiest way for you to do that is to re-enable the api".

In the example being used it was really the latter, consider that all the followup emails included the phrase "or allow for some other method to allow me to exercise my rights under the GDPR". It's also not like the overall goal of exporting data to another provider would have not been achieved if they implemented some new method instead, you can be sure that songshift would still do the work to make it easy to switch from spotify to them.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: