gsadmin/certctl
1
0
Fork 0
mirror of https://github.com/shankar0123/certctl.git synced 2026-06-07 21:51:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore(README): remove duplicative Scarf pixel — moved to certctl.io

Browse Source 
The README had two Scarf pixels (89db181e and b9379aff). For README
visit tracking, GitHub's built-in Insights → Traffic dashboard
already provides views, uniques, clones, AND referring sites with
click counts (Reddit, HN, Twitter, search, etc.) at higher
granularity than a Scarf pixel can extract — Scarf can only see
'github.com' as the referrer because that's where the README HTML
is served from, while GitHub Insights knows the actual external
referrer that landed the visitor on the README.

Removing pixel b9379aff-9e5c-4d01-8f2d-9e4ffa09d126 from the README
and reusing it on the certctl.io landing page (sibling commit on
certctl-io/certctl.io), where Scarf is the only analytics source
and the referrer header actually carries useful attribution.

Pixel 89db181e-76e0-45cc-b9c0-790c3dfdfc73 stays in the README as
a backup signal alongside GitHub Insights — keeps continuity for
the longer-running Scarf project counter.

No data loss: GitHub Insights covers what 89db181e was double-
counting, and b9379aff now serves a distinct surface (certctl.io)
where it actually adds new attribution data.
This commit is contained in:
shankar0123
2026-05-01 06:02:23 +00:00
parent 98cf6afcf0
commit ef7da23018
1 changed files with 0 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
-1
View File
@@ -3,7 +3,6 @@
</p>
<img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=89db181e-76e0-45cc-b9c0-790c3dfdfc73" />
<img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=b9379aff-9e5c-4d01-8f2d-9e4ffa09d126" />
# certctl — Self-Hosted Certificate Lifecycle Platform