←back to thread

798 points bertman | 5 comments | | HN request time: 0s | source
Show context
djoldman ◴[] No.45899558[source]
From

https://github.com/yt-dlp/yt-dlp/wiki/EJS

it looks like deno is recommended for these reasons:

> Notes

> * Code is run with restricted permissions (e.g, no file system or network access)

> * Supports downloading EJS script dependencies from npm (--remote-components ejs:npm).

replies(2): >>45900422 #>>45900960 #
arbll ◴[] No.45900422[source]
It's fine for this project since google is probably not in the business of triggering exploits in yt-dlp users but please do not use deno sandboxing as a your main security measure to execute untrusted code. Runtime-level sandboxing is always very weak. Relying on OS-level sandboxing or VMs (firecracker & co) is the right way for this.
replies(3): >>45900665 #>>45903690 #>>45907042 #
1. baobabKoodaa ◴[] No.45903690[source]
> It's fine for this project since google is probably not in the business of triggering exploits in yt-dlp

yt-dlp supports a huge list of websites other than youtube

replies(2): >>45905509 #>>45907797 #
2. blackhaj7 ◴[] No.45905509[source]
Is there a full list? I struggled to find one
replies(2): >>45907205 #>>45907591 #
3. dcassett ◴[] No.45907205[source]
https://github.com/yt-dlp/yt-dlp/blob/2025.09.23/supportedsi...
4. NoahZuniga ◴[] No.45907591[source]
There's a supportedsites.md file in the base directory of the git repo.
5. arbll ◴[] No.45907797[source]
I assumed they only use this setup for youtube, that might be wrong