Even years later, Twitter doesn’t delete direct messages

Re:Even years later, Twitter doesn’t delete direct messages by NullPrefix on Friday February 15, 2019 @04:38PM (#19174970)

GDPR affects backup tapes too

[ Parent | on HN ]

Re:Even years later, Twitter doesn’t delete direct messages by kradroy on Friday February 15, 2019 @04:45PM (#19175012)

It does, but not like you'd think. If the backup is dormant, the right-to-be-forgotten portions can remain there. Once it comes out of cold storage, those RTBF requests have to be processed over the restored data. Although, in most cases, the dormant backups will expire and be deleted as per a data retention plan.

[ Parent | on HN ]

Re:Even years later, Twitter doesn’t delete direct messages by fh973 on Saturday February 16, 2019 @07:54AM (#19178371)

This is usually solved by encrypting and throwing away the key or seed to effectively delete.

Tape is no excuse to violating data retention policies.

[ Parent | on HN ]

Re:Even years later, Twitter doesn’t delete direct messages by msh on Saturday February 16, 2019 @07:10AM (#19178258)

That does not seem to be entirely correct: https://blog.quantum.com/backup-administrators-the-1-advice-...

[ Parent | on HN ]

Re:Even years later, Twitter doesn’t delete direct messages by guitarbill on Saturday February 16, 2019 @12:22PM (#19179643)

Which part isn't correct? What op described sounds like a good and easy way to do it (as long as you have sane retention periods) and doesn't seem to conflict with the article you linked in any way (in fact, they agree).

[ Parent | on HN ]

Re:Even years later, Twitter doesn’t delete direct messages by msh on Sunday February 17, 2019 @08:01AM (#19184258)

In addition you have to tell the customer how long you retain your backups (and only retain them for a reasonable time) and only restore for purely technical reasons.

[ Parent | on HN ]