[taskset]

I no longer use GitHub for original projects. Source for fftool isn't public yet but I understand the concern — running an unaudited binary is a real ask. My site leans toward educational, so that people might consider building the tool from the instructions in the article. I'll probably post the source on the site as a zip or tarball at some point so people can more easily build it. The asciinema suggestion is a good one — I'll look into it.

[lionkor]

Weird, I swear the binary debug info says "github.com/bensantora-tech/fftool/main.go", so its just not public? Why?

[taskset]

Right, I missed that — the Go module path in go.mod references GitHub by convention even though the repo isn't there (it's embedded in the binary's debug info). I'll change the module path to something on my own domain. Thanks for spotting that.

[lionkor]

Yeah, I thought about it and remembered that Go assumes GitHub by default for some dumb reason!

[mr_mitm]

I never said you should publish to github. You can put it up on your own site, at least as a tarball. Even better: cgit or stagit

[taskset]

Source is now on the site: [bensantora.com/downloads/fftool-source.tar.gz] and .zip. Build instructions are in the article.

[overflowy]

Awesome, appreciate it :)