Concerns about badge recommendation #158
Description
Related to #157
Hello,
I would like to suggest reconsidering the use of badges as currently recommended by your specs.
My main points are use of resources and privacy.
About Resource use:
- Every visit triggers a HTTP request to an external server.
- Requests consume resources like energy, contributing to CO2 emissions.
About Privacy:
- Such requests exposing IP address, referrer, and other browser information to the extern server.
- In case of shields.io it seems to be hosted in areas accessible by US Goverment.
- Visitors can be tracked, even though that the badge itself contains no personal data.
My suggestion would be, that badges should be "hosted" locally in the repo. I am aware that dynamic badges then are hard to realize.
IMHO the benefits of badges do not justify the costs.