... not sure what to add since I dont want to publish IP addresses or peer informations
Bitcoin users know that their IP addresses are public if they participate in the peer-to-peer network without specifically choosing their peers. The most offending demonstration:
https://blockchain.info/ip-logIf you don't want to show the IPs of connections, you can dump your port 8333 connection IPs through a salted hash to make an identifier; bash example:
ipaddr="127.0.0.1"
salt="mysecret"
hash=$(echo $ipaddr$salt | sha256sum)
id=${hash:0:8}
echo $id
gives an identifier "b10ea208", nearly as unique as IP addresses.
Privacy is not a concern in that regard. I dont think IP addresses are personal information anyway. Behind most IP's are several users, sometimes companies with 1000's of employees and if someone wanted to hide his/her IP address there are services like tor. But IP addresses connected to is nothing I can make a picture of with rrdtool and I dont want to add php/mysql. Im perfectly fine with a number of connections in that regard. Frankly I think a list of IP addresses isnt that interesting to look at. A full dump of getpeerinfo (see other sites linked above) is a different matter, but I will restrict the information shown to number of bits/connections etc.
# of connections by version might be something to consider, but that would require a very sophisticated script. Get different versions, check if data base for version exists if so update with current count, if not make a new one and add a cronjob to update the resulting picture as well as the html page. Depending on the name of the version used that could probably result in problems along the way.
