I suspect they're talking about circumvention of technical DRM measures.

https://www.law.cornell.edu/uscode/text/17/1201

They could also be talking about the Apple email leak caused by incrementing an UUID.

There's probably other notable cases with the same failure mode.

One of the things you learn working in computer security: history doesn't repeat itself, but it does rhyme.

> history doesn't repeat itself, but it does rhyme.

I do like Mark Twain

Ah, yeah, that's where I heard it from first. Thanks!

weev and AT&T as well.

Nah history in information security repeats daily. How many unsecured mongodb databases exposed to the internet and unsecured S3 buckets did we see? Credentials have been committed to github so often that Github chose to build an automated alert system on their own dime that you don't even have to sign up for. How many times have lastpass and Experian been breached? How often do we STILL see sql injection attacks, a problem that has been actually solved for decades?

Perhaps in reference to the judyrecords fiasco:

https://www.judyrecords.com/what-happened-with-tyler-technol...

No one was actually sent to jail, but the proprietor of the site was dragged through the media as a dangerous hacker and felon.

you should do it with Typescript