The project doesn't involve any scraping. All of the site's data (i.e. a complete list of videos) is embedded in the HTML that they serve as a JSON blob[1].
[1] https://lol-content-dumps.s3.amazonaws.com/courses_v2/lol/co...
[1] https://lol-content-dumps.s3.amazonaws.com/courses_v2/lol/co...
You're pretty clearly being a bad actor here.
Links to videos on their site that you need to log in to view? Totally no problem and they'd be unreasonable to complain.
Deriving direct links to private content to make it accessible to the general public? Doesn't matter if their content has the security of a wet cardboard box, you should not be doing this.
I think they should probably be fixing deep linking to the content working for unregistered users instead of threatening you with legal action, but that doesn't make what you're doing OK.
I don't think you have a guilt-free position, the fact your website is public puts you at risk of litigation (not a lawyer.)
If it’s before, the website have a serious conception problem. But if it’s after then it’s not « public ».
In any case (but IANAL) it’s not because you can hack it that it’s ok to do it.
Can a non-registered user read all these?