I installed #neonmodem by simply grabbing the tarball, which expands files directly into the $CWD instead of nesting them in a folder named after the app. Not a big deal but it gave a slight hint that this project might have quality issues.
This command executes just fine:
$ torsocks neonmodem connect --type lemmy --url https://sopuli.xyz
It’s irritating that it does not inform the user where the data is being stored and it’s also undocumented. You have to guess how to use it and it’s misleading (I think the connect command does not actually result in a connection being made, it apparently just stores the login creds).
Simply running it crashes instantly:
$ torsocks neonmodem
panic: Error(s) loading system(s)
goroutine 1 [running]:
github.com/mrusme/neonmodem/cmd.glob..func1(0x1771140?, {0xe973eb?, 0x0?, 0x0?})
/home/runner/work/neonmodem/neonmodem/cmd/root.go:128 +0x268
github.com/spf13/cobra.(*Command).execute(0x1771140, {0xc00008c1f0, 0x0, 0x0})
/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:944 +0x847
github.com/spf13/cobra.(*Command).ExecuteC(0x1771140)
/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:1068 +0x3bd
github.com/spf13/cobra.(*Command).Execute(...)
/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:992
github.com/mrusme/neonmodem/cmd.Execute(0xc0000061a0?)
/home/runner/work/neonmodem/neonmodem/cmd/root.go:141 +0x3e
main.main()
/home/runner/work/neonmodem/neonmodem/neonmodem.go:13 +0x25