Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Suggestion] Redact formats in info json with an option #455

Closed
3 tasks done
Lesmiscore opened this issue Jun 29, 2021 · 1 comment
Closed
3 tasks done

[Suggestion] Redact formats in info json with an option #455

Lesmiscore opened this issue Jun 29, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@Lesmiscore
Copy link
Contributor

Lesmiscore commented Jun 29, 2021

Checklist

  • I'm reporting a feature request
  • I've verified that I'm running yt-dlp version 2021.06.23
  • I've searched the bugtracker for similar feature requests including closed ones

Description

For some websites like YouTube, they might include IP address or any kind of identification in the URL. This is one of the cases that AutoModerator modifies the post on r/youtubedl.

This is a serious problem on privacy, since info json may be uploaded along with the video for archiving purposes.

So I suggest to add an option to remove formats and url when the user wishes to remove them.

Thanks

@pukkandan
Copy link
Member

With 119e40e, fe74d5b, all metadata fields can now be removed using --parse-metadata "video::(?P<url>)" etc.

So an alias like:

--alias --minimal-info-json '--parse-metadata "video::(?P<formats>)" --parse-metadata "video::(?P<url>)" --parse-metadata "video::(?P<http_headers>)" --parse-metadata "video::(?P<automatic_captions>)" --parse-metadata "video::(?P<subtitles>)" --parse-metadata "video::(?P<thumbnails>)"'

could be used to write a very minimal info json. Is a single option to do this still desired?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants