> there isn't actually a security issue The official blog from DigitalOcean is here: https://www.digitalocean.com/blog/transparency-regarding-data-security ht

> there isn't actually a security issue The official blog from DigitalOcean is here: https://www.digitalocean.com/blog/transparency-regarding-data-security https://www.digitalocean.com/blog/transparency-regarding-dat... While it does not call it a “security issue” directly, it details several changes to the service to prevent customer data leaking between accounts. That seems to contradict your position that there was no problem. > 10 years later and I still remember how pissed off I was that day, hah. I would have hoped that after 10 years you would be able to admit that letting customers read each other’s data was a mistake. The existence of a disk scrub API, the problem being improperly reported, and DO being advertised as “not for production use” are not valid excuses.