Software Development and GDPR

Software Development and GDPR by OISIN HURLEY (OISIN)
Are you in control of the presence of data in your database? Yes. It’s up to you to delete it when requested. Are you in control of the data on your hard drive? Yes. It’s up to you to delete it when requested. Are you in control of the operating system implementation or database implementation of deletion? No. Could you get the data back if you wanted to? Yes – but that’s not part of your usual run of business, so why would you explicitly do that? What if some bad dude steals your hard drive and then rummages through it? Ok, we are getting a little far-fetched here for most businesses that are not keeping special category data, but if this does happen, then you have failed in your security controls.

NwAvGuy and the Objective 2 ODAC

NwAvGuy: The Audio Genius Who Vanished by David Schneider (IEEE Spectrum: Technology, Engineering, and Science News)

An anonymous engineer created some of the best DIY audio designs—and his fans want to know where he went

 

“I don’t want any revenue from the O2,” NwAvGuy wrote on his blog, “but I do humbly request everyone please respect the license, which includes proper attribution.” But the particular open-source license he applied—Creative Commons CC BY-ND—requires more than just proper attribution: It forbids derivative works. This is different from most open-source projects, which are released with the intent of letting others build on the original, perhaps improving things and, in any event, ensuring that useful designs will not languish if the creator goes bankrupt, loses interest, or otherwise moves on.

A few years ago I researched this and wanted to purchase from one of the two suppliers. I never did and forgot about it until recently. It’s back on my birthday wish list.