enfuse

Attempts to contact external telemetry servers under default configuration is the issue. That not all of the needlessly locally aggregated data would actually be transmitted is separate.

Telemetry is perfectly acceptable as long as it is opt-in and does not contain personal data, and both apply to Go's telemetry, so there's no need for a fork.

This changed somewhat recently. Telemetry is enabled by default (I think as of Golang 1.23?)

I am only aware since I relatively recently ran into something similar to this on a fresh VM without internet egress: https://github.com/golang/go/issues/68976

https://github.com/golang/go/issues/68946

If golang doesn't fully address this I guess Debian really should at least change the default (of they haven't already).

or if you want to say you use Arch then try Manjaro

EndeavourOS preferred over Manjaro.