tudo VS yt-dlp

Now, you have installed yt-dlp & ffmpeg (required with yt-dlp). Next, you have to install tudo; better for using scripts directly rather than cluttering ~/.termux/tasker with different scripts, read more here.

I already tried using tudo but i have no idea how to define the working directory. I tried this code as the argument

tudo is a wrapper script that allows you to send commands to Termux from Tasker (using the Termux plugin). Without it to use the Termux plugin you would need to write a script of what you want to do, copy it to Termux's files and program Tasker to tell Termux to run that script.

Check Termux:Tasker plugin for Termux for mostly everything you need. There are template tasks and scripts available as well. Or you can use tudo to directly run the commands with its script command type, no need for physical script files, much easier in many ways, template tasks available too. Download Termux and optionally Termux:Tasker from F-Droid and not from playstore, check here for why.

However, the slash will still remain whoever receives the intent as you mentioned. (reddit is not showing the slashes, use markdown code blocks). It's better to use the tudo way to replace commas with something else before sending intent and replace them back when the intent is received. Check Passing Arguments Using RUN_COMMAND Intent for details.

I see, that makes sense. Although, there are plans to add support to for a button that would show description in mobile browser before accepting to import from taskernet. That should solve some of your issues. The description is pretty readable if opened in browser in desktop mode after being formatted properly, which of course isn't done natively currently either.

You can also start sshd at some random time with tasker including boot or if ssh connection fails with tudo script with Termux:Tasker plugin or RUN_COMMAND intent. Check its example under bash examples. I also have a tudo script task in tasker that automatically detects if sshd is running and only keeps a new terminal session open if its not, but it isn't "export" ready.

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

Or just "yt-dlp "

yt-dlp ( https://github.com/yt-dlp/yt-dlp ) still works pretty well at the current state of Twitter.

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>