Serve just metadata?

[pycaw]

Is it possible now, or if not, have you considered to serve just metadata? I would be interested in youtube video metadata as produced by yt-dlp -J .... But, youtube.js I suppose can produce it similarly.

[ihatespawn]

why would you want that

[pycaw]

why would you want that

Extract things like description or chapters to supplement cross-platform YT -> Obsidian video bookmarking workflow.

[ihatespawn]

why would you want that

Extract things like description or chapters to supplement cross-platform YT -> Obsidian video bookmarking workflow.

https://developers.google.com/youtube/v3/docs

link for descriptions etc: https://developers.google.com/youtube/v3/docs/videos/list

[pycaw]

why would you want that

Extract things like description or chapters to supplement cross-platform YT -> Obsidian video bookmarking workflow.

https://developers.google.com/youtube/v3/docs

link for descriptions etc: https://developers.google.com/youtube/v3/docs/videos/list

Note the part about Terms of Service: https://github.com/mattwright324/youtube-metadata/discussions/150#discussioncomment-6094304

I have vague insight but one must circumvent the API and find other means for most of use cases. Don't want to deal with API tokens either.

[ihatespawn]

why would you want that

Extract things like description or chapters to supplement cross-platform YT -> Obsidian video bookmarking workflow.

https://developers.google.com/youtube/v3/docs link for descriptions etc: https://developers.google.com/youtube/v3/docs/videos/list

Note the part about Terms of Service: mattwright324/youtube-metadata#150 (comment)

I have vague insight but one must circumvent the API and find other means for most of use cases. Don't want to deal with API tokens either.

Let me break this down

Note the part about Terms of Service: mattwright324/youtube-metadata#150 (comment)

YouTube probably did something wrong because it's not even matching what's written there. Did you click the link in that comment and actually read it?

Audiovisual Content

You and your API Clients must not, and must not encourage, enable, or require others to:

1. download, import, backup, cache, or store copies of YouTube audiovisual content without YouTube's prior written approval,
2. make content available for offline playback, or
3. use any aspect of the YouTube API Services to facilitate or promote copyright infringement or the exploitation of copyright-infringing materials.

I don’t think extracting descriptions or chapters would violate these rules.

Don't want to deal with API tokens either.

Maybe you sometimes need to? I don't have any problems with doing that so why would you? Give me some reasons why not.

[pycaw]

"Youtube did something wrong..." - that's your breakdown? Like it or not they canceled this metadata extraction service's main feature: simple export. And then, many tools do well without using the API.

[wukko]

this feature is out of cobalt's scope and has no purpose within the main project