From ef7da23018899ad7bc3c29a4618eaec1ae0eb311 Mon Sep 17 00:00:00 2001 From: shankar0123 Date: Fri, 1 May 2026 06:02:23 +0000 Subject: [PATCH] =?UTF-8?q?chore(README):=20remove=20duplicative=20Scarf?= =?UTF-8?q?=20pixel=20=E2=80=94=20moved=20to=20certctl.io?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 7baadfd..d49f0ee 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,6 @@

- # certctl — Self-Hosted Certificate Lifecycle Platform