music-explorer VS wireguard-tools

The article might describe a common scenario, but there are plenty of outliers. I hardly listen to music I liked in my teens and early twenties. I love discovering new music.

Many comments here are very insightful and discuss phenomena like high music diversity, music proliferation and easy of producing music, and automated recommendations.

One thing that has been occupying me is that curation is still harder than I'd like when using streaming tools like Spotify, YouTube Music, Apple Music, Tidal. Pandora had good roots with its music genome project, and have built on that. (I can't use it without a VPN since they discontinued supporting the country I mostly live in). It's probably a function of how I consume my music today - no longer desk-bound at work, but on the go, so iPhone (and Apple Watch) are primary tools. Being able to select/skip/preview/tune what I'm listening to is nowhere near as powerful as I'd like. I've written library curation tools in the past, these always expected me to spend significant dedicated time in front of a screen (e.g. a similar tool like the cool looking https://github.com/kristopolous/music-explorer, I think).

This has strong parallels to how older people consumed music - either totally passive curation (radio), or very deliberate (find music in record stores, at a friend's place, and/or select records/CDs in your own shelves). Today's ephemeral digital libraries are much lower effort, are huge and curation/selection tools are not easy enough to use, so I tend to fall back onto old favourites or recommendation engines that usually don't satisfy me.

A solution would be a much more configurable curation assistant that is also super easy to use (and, in my case) very accessible on a mobile device with 0-1 clicks (because I'm busy doing other things).

Might as well drop what I use for my music discovery, my fairly poorly documented hacker-friendly set of tools:

https://github.com/kristopolous/music-explorer/

I'm a big fan of not posix bit instead modern bash and to all the complainers about dash and ash, I say "tough cookies".

Sometimes I'll even use zsh

Here's some example of a modern tool I have written for a subject I call "music discovery"

https://github.com/kristopolous/music-explorer/tree/master/t...

You'll see many languages in there.

If you don't like my practice then I guess don't use it. I've been using/developing these particular tools nearly every day for over 3 years and it works well for me.

I'm not going to say bash is awesome but it's pretty great for programming.

I use zsh as my interactive though

Sure. Related. It's an art.

Here's some code I wrote earlier, probably a good example

https://github.com/kristopolous/music-explorer/blob/master/w...

It's self contained, not very big, not trying to be fancy, as direct as possible

Oh, this is cool. I'm a huge proponent of CLI tools supporting sensible JSON output, and things like https://github.com/WireGuard/wireguard-tools/blob/master/con... and PowerShell's |ConvertTo-Json are a huge part of my management/monitoring automation efforts.

But, unfortunately, sensible is doing some heavy lifting here and reality is... well, reality. While the output of things like the LSI/Broadcom StorCLI 'suffix the command with J' approach and some of PowerShell's COM-hiding wrappers (which are depressingly common) is technically JSON, the end result is so mindbogglingly complex-slash-useless, that you're quickly forced to revert to 'OK, just run some regexes on the plain-text output' kludges anyway.

Having said that, I'll definitely check this out. If the first example given, parsing dig output, is indeed representative of what this can reliably do, it should be interesting...

> Possible? Maybe. Easy? No. Especially the “testable” part.

a testable shell script? Never seen one.

Thinking about scirpts I've read in the past, I remember seeing Jason Donenfeld's bash script for wireguard-wg and thinking how productive and readable it was,

https://github.com/WireGuard/wireguard-tools/blob/master/src...

I see this when my equipment roams back into my private network and the wireguard server is inside that LAN. It can be solved by NAT'ing packets arriving on your edge router's inside interface, destinated to your outside IP, back to the inside wireguard server IP.

Alternatively if your client is Linux, there is:

https://github.com/WireGuard/wireguard-tools/tree/master/con...

you have a copy here that you can edit: https://github.com/WireGuard/wireguard-tools/blob/master/contrib/reresolve-dns/reresolve-dns.sh

You could adapt this script for it. What this one does is re-resolve the domain of the endpoint for when it's a dynamic dns. You run it on a timer from cron, and when your dynamic dns changes it will update the endpoint IP with wg set. You could adapt this script to update your AllowedIPs instead of the endpoint.

I found the GitHub Repository to wireguard-tools however, I cannot read the exact commands required to connect to a certain VPN! I've created a .conf file and was wondering how you could use that with WireGuard-tools to establish a VPN tunnel to my network?