UPDATE

Now introducing a new feature: the video description as well as the comments written by YT viewers will be shown in the terminal window, while the video is reproduced.

Thus, the user can be satisfied reading other viewers having a swing at the politicians/celebrities/stars they love to hate, or, watch closely to their heart's content, as cyber nuclear attacks are launched between self-righteous, valiant and livid keyboard fighters.

Comment loading is asynchronous to video loading, so it is possible that there will be some delay in the appearence of the comments. That depends on the number of comments, network speed etc.

top 9 comments

sorted by: hot top controversial new old

[-] danielquinn@lemmy.ca 6 points 2 months ago* (last edited 2 months ago)

That looks really impressive, but at nearly 1000 lines of Bash, I'm afraid I'm not comfortable running it on my machine. My Bash-foo isn't strong enough to be sure that there isn't a typo in there that could nuke my home folder.

[-] christos@lemmy.world 6 points 2 months ago

Fair enough, you do you.

For the record, no rm -r in the script.

The only rm command, line 394: rm "${UEBERZUG_FIFO_MAGIC_TAPE}"

[-] danielquinn@lemmy.ca 5 points 2 months ago

To be clear, I'm not throwing shade. That's an impressive piece of software. It's just, given the number of stories I've heard (and experienced) about Bash's tricky syntax leading to Bad Things, I'm less comfortable with running this than I would be with something in a language with fewer pitfalls.

But if others take the chance and it sticks around a bit, I'll come around ;-)

Thanks for the contribution! It's a great idea, and with Google fucking about with blocking things like NewPipe, a project like this is a great answer to that.

[-] christos@lemmy.world 2 points 2 months ago

But if others take the chance and it sticks around a bit, I’ll come around ;-)

Hey, like many bash scripts, this one is just a glorifief one-liner. But I use it everyday, I am biased, of course, but it is rather convenient, and prevents me from getting lost in rabbit holes.

[-] christos@lemmy.world 2 points 2 months ago

given the number of stories I’ve heard (and experienced) about Bash’s tricky syntax leading to Bad Things,

Been there, done that!

[-] Telorand@reddthat.com 3 points 2 months ago

Neat. I'll take a closer look later, but this sounds like an interesting project

[-] christos@lemmy.world 2 points 2 months ago

Thanks, any feedback is appreciated.

[-] Badabinski@kbin.earth 8 points 2 months ago

The screenshots look really nice. I've personally always struggled with designing nice TUIs, so I really appreciate the way this looks.

I'd recommend trying out shellcheck and potentially building it into your repo as a CI check. I've written a ton of Bash over the years, and I've found shellcheck to be absolutely essential for any script over ~100 lines. It's not perfect, but it does do a great job of helping you avoid many of the foot guns present in Bash. I also dearly love this site. It's a fantastic reference, and I look at it almost every day.

I may take some time later today and provide a bit of specific feedback.