Are you sure it's unusable with Github?

[josephernest]

I see you removed Github from the possible applications: 6acd862

Probably because README.md images are agressively "cached".

But they surely is a solution: many repos have "badge" images, that are frequently updated. So with the appropriate caching setting, couldn't it be possible to track with a pixel the page views? See @bkeepers 's comment github/markup#224 (comment):

We're pretty confident that the image caching works. If you're having issues with something like a CI badge, make sure the image has the Cache-Control: no-cache header, and either Expires, Last-Modified or Etag. See the Fastly documentation for more info. If you're still having issues, contact [email protected]

[Yrobot]

I think some part of ga-beacon is unusable now, such as UV.
This is the ga-beacon server logs whan i refresh my repo homepage, you can see cid is different, because the img is requested by the https://camo.githubusercontent.com/ server but client browser. cookie.cid is not working.

At least PV works fine.

[Yrobot]

I think some part of ga-beacon is unusable now, such as UV.
This is the ga-beacon server logs whan i refresh my repo homepage, you can see cid is different, because the img is requested by the https://camo.githubusercontent.com/ server but client browser. cookie.cid is not working.

At least PV works fine.

which means only Cache-Control, Expires, Last-Modified and Etag will work on github img

[sionsmith]

Has anyone managed to get this working recently? Or am I just completely wasting my time?!