Are you actually still using this, or can this be removed? I assume many users would appreciate not being tracked by third-party sites while browsing your repository.
Actually, that analytics image is probably not working as desired at the moment anyway because GitHub is caching the image and serving it from https://camo.githubusercontent.com/... instead. There might be ways to clear the cached image, but that still does not seem suitable for analytics.
Additionally, GitHub itself offers to maintainers the option to see traffic for a repository, including information about clones, which files are browsed and from where the visitors arrived to the repository, see GitHub documentation. Potentially that is much more useful than what third-party analytics could provide.
Hello, it seems the README contains an image for analytics (originally added by 8fb322ac9baa2830565e0c94f31e45bbd62338f8): https://github.com/json-path/JsonPath/blob/2d4cc06cd24e3422e29e2de02f154b34d75f5de0/README.md?plain=1#L494
Are you actually still using this, or can this be removed? I assume many users would appreciate not being tracked by third-party sites while browsing your repository.
Actually, that analytics image is probably not working as desired at the moment anyway because GitHub is caching the image and serving it from
https://camo.githubusercontent.com/...instead. There might be ways to clear the cached image, but that still does not seem suitable for analytics.Additionally, GitHub itself offers to maintainers the option to see traffic for a repository, including information about clones, which files are browsed and from where the visitors arrived to the repository, see GitHub documentation. Potentially that is much more useful than what third-party analytics could provide.