stylegan2-pytorch VS yt-dlp

export default function ChannelListBottomBar(): JSX.Element { const { client } = useChatContext(); const [micActive, setMicActive] = useState(false); const [audioActive, setAudioActive] = useState(false); return (

{client.user?.image && (

div> )}

{client.user?.name} span> {client.user?.online ? 'Online' : 'Offline'} span> p> button>

setMicActive((currentValue) => !currentValue)} > button> setAudioActive((currentValue) => !currentValue)} > button> button> div> ); }

...then they just use the app on generated images of not real people (potentially based on specific inputs to remind you of a real person).

At lest, a way to complete the AI-generated cycle that https://thispersondoesnotexist.com/ started.

Thispersondoesnotexist.com - It's what the title says. It's terrifying but whenever you refrest the page, it shows you a new "person" who doesn't exist.

This X Does Not Exist is a list of gens for People, Cities, Words, Lyrics and other items that have been created by GANs (generative adversarial networks).

thispersondoesnotexist.com for making profile pics when you want to be anonymous

Nvidia is the one who made GANs popular. All this buzzword that people say about Generative AI, it was popularised by Nvidia with their StyleGAN paper. You must have seen or hear about thispersondoesnotexist.com? That's Nvidia.

GANs on the other hand uses a generator and discriminator model, where the generator learns to generate images that are "good enough" to fool the discriminator. It may make it easier to make discriminators that are better at picking out visual artefacts that stand out for humans, (it was easy to pick out "fake humans" from the early versions of thispersondoesnotexist.com by looking at their eyes and teeth, they tend to be pointing in different directions, or their teeth are too irregular before the discriminator got better at picking those out) but they can suffer from mode collapse, and generate images with very little variety.

Generative networks like StyleGAN

You can put these options in a config file and they will become the default: https://github.com/yt-dlp/yt-dlp?tab=readme-ov-file#configur...

Yep. yt-dlp and youtube-dl

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

https://github.com/ytdl-org/youtube-dl

Will also start to feel the impact. My theory is that we will see a bunch of new video hosting sites as youtube itself attempts to lock down its ecosystem. They haven't paid attention in any adversarial way as far as I can tell.

When they do, it wont be great.

The points you make aren't unreasonable.

It is necessary to establish clear boundaries of what can and can be provided by the maintainers. If not done at an earlier stage of the project, the support burden becomes too much to bear at which point the maintainer transfers ownership, and the project suffers from catastrophic consequences such as the xz backdoor we're talking about here, or other cases where the project mostly stalls and serves as an ego-boosting platform for the new maintainer, as was the case with PhantomJS[6].

This can also happen in your life, where a "friend" sees that you possess a certain skill, and then gradually tries to push an inordinate amount of their personal work related to this field onto you.

Personally, I think it's best to use an approach with extremely clear communication as to what the maintainer can and cannot provide. This can be seen, for example, in yt-dlp[1], where the consumer is clearly informed upfront that not providing detailed information as requested will lead them to block said consumer; or sqlite where their position regarding contributed patches[2] and support[3] is similarly made clear.

Having a shouty BDFL like Torvalds can also help improve code quality[4] and questionable contributions[5], though it is better that the shouty BDFL makes statements that are professional and do not show as much aggression; so for example, "Mauro, shut the fuck up"[7] would become "Mauro, your response is completely unbecoming for a Linux kernel maintainer, and is not in line with the promise of not breaking userspace."

[1] https://github.com/yt-dlp/yt-dlp/issues/new?assignees=&label...

[2] https://www.sqlite.org/copyright.html

[3] https://www.sqlite.org/support.html

[4] https://www.theregister.com/2024/01/29/linux_6_8_rc2/

[5] https://cse.umn.edu/cs/linux-incident

[6] https://github.com/ariya/phantomjs/issues/14541

[7] https://lkml.org/lkml/2012/12/23/75

To download audio from YouTube videos, you'll utilize the widely used yt-dlp library, which can be installed using the pip command as follows:

Use: `yt-dlp with --write-comments --no-download --batch-file FILE`

- FILE is a text file with a list of YouTube id's/URL's

- https://superuser.com/a/1732443/4390

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

> Then youtube-dl wasn't a thing anymore (maybe it is again?)...

yt-dlp is definitely a thing: <https://github.com/yt-dlp/yt-dlp>

What differentiates this from YT-DLP? The latter gets regular updates, and supports more things than the original tool does:

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