radion is an internet radio CLI client, written in Bash.

https://gitlab.com/christosangel/radion

Radion can be customized as far as the station selecting program is concerned. The user can choose between:

  • read

read

  • fzf

fzf

  • rofi

rofi

  • dmenu

dmenu

Update: Introduced new feature: customizing prompt text for fzf dmenu and rofi.

Update: MacOS support added now thanks to Andrea Schäfer

Also, I was forced by my daughter to add some anime radio stations…

Update: Recording functionality added, with the use of another (you guessed it) bash script

icy

Also options in read as Preferred selector are also case insensitive.

Any feedback is appreciated!

  • @folkrav
    39•9 months ago

    deleted by creator

    • Maeve
      12•9 months ago

      That’s why it’s impressive. It’s not easy.

      • @folkrav
        14•9 months ago

        deleted by creator

        • Maeve
          5•9 months ago

          Some people just have a natural affinity, I guess. If it made the programmer happy and it’s not full of maliciously exploitable bugs, why not?

          • @folkrav
            2•9 months ago

            deleted by creator

    • shinomoroll
      11•9 months ago

      Everything is not pure bash here, it’s a radio frontend for mpv. It is also using sed, awk… A standard bash use case actually.

    • Dran
      10•9 months ago

      My entire homelab env is written in “pure bash”. Bare metal deployments, creation, build, deployment, update, and backup, of docker containers (which are also just convenience wrappers around other pure bash projects of mine.). Etc…

      I do it because I got sick of losing data, work, workflow or convenience to black boxes I didn’t create myself. Hell, even with my third party projects like Plex I have a lot of bash automation around extracting playlists from the internal sqlite db, etc. It really shifts your perspective on what’s possible when you build things by hand yourself.

      • @folkrav
        5•9 months ago

        deleted by creator

        • Dran
          3•9 months ago

          It’s not like I don’t use open source solutions, I use docker for example rather than automating chroots/cgroups by hand in bash. I just use them as little as possible. While you’re correct, I don’t lose data in a well designed open source project, I do lose work, workflow, and convenience when those projects change or shut down. What’s really nice about the pure bash solutions is they’re entirely portable once you have them dialed in. If I wanted to switch from docker back to vms or forward to something like harvester/rancher/k3s I’d be able to port the projects very trivially. If I built everything around one of those projects in mind, all of my work would rely on it not changing. I acknowledge it’s sometimes a little more work but it’s work that I get to decide when to do, not when the project maintainers decide it for me.

    • DreamButtEnglish
      5•9 months ago

      Not to mention the tool isn’t meant to be anything more than glue between other programs