Am I blind or is there no link to the source? I get that running code from any old repo on github has become normalized, but running random binaries is pushing it. Also, I think when advertising a TUI, you should include an asciinema video (or comparable).

▲

taskset 2 hours ago | parent | next [-]

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 2 hours ago | parent [-]

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

▲

taskset 2 hours ago | parent [-]

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 2 hours ago \| parent [-]
		Yeah, I thought about it and remembered that Go assumes GitHub by default for some dumb reason!

▲

an hour ago | parent | prev | next [-]

[deleted]

▲

lionkor 2 hours ago | parent | prev | next [-]

To be fair, it ships with debug info.

▲

garymoon 2 hours ago | parent | prev [-]

Same