By default the public key of a node’s VPN daemon is not added to announced respondd data; this prevents malicious ISPs from correlating VPN sessions with specific mesh nodes via public respondd data. If this is of no concern in your threat model, this behaviour can be disabled (and thus announcing the public key be enabled) by setting pubkey_privacy to false. At the moment, this option only affects fastd.
As for supernodes the pubkey is quite often already visible for everyone on the internet,
I'd like to have this implemented for easier debugging.
Currently the path fastd.public_key is not implemented, yet.
https://gluon.readthedocs.io/en/latest/user/site.html
As for supernodes the pubkey is quite often already visible for everyone on the internet, I'd like to have this implemented for easier debugging.