Just to clarify, blockchain data is openly distributed anyway, and it's supposed to be.
Privacy problems arise when we start scanning the actual traffic that goes in and out of the full node peers.
That's when you would see IPs (of not just full nodes, but also of SPV wallets, etc...)...
The decentralized explorer service will do nothing like this, since it merely reads data from the coins data folders,
which consists of the blockchain dat files.
What I was thinking about is maybe let the UBA even read out the peers.dat file of a coin, so that people who have connectivity issues with a coin,
could ask the decentralized explorer to return some full node ips that host their coin, so that they can then add them in their conf file (addnode).
You know, basically what a dns-seeder does: return a set of healthy full node IPs.
Maybe that's something the decentralized explorer could do too.
Full Node IPs are supposed to be known and shared anyway.