From 355da058edfbac9c0f3345cbada203cefbcde3ce Mon Sep 17 00:00:00 2001 From: shankar0123 Date: Fri, 1 May 2026 20:59:22 +0000 Subject: [PATCH] =?UTF-8?q?chore(README):=20remove=20the=20second=20Scarf?= =?UTF-8?q?=20pixel=20=E2=80=94=20analytics=20consolidated=20to=20certctl.?= =?UTF-8?q?io?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The README has carried two Scarf pixels for some time: - 89db181e-76e0-45cc-b9c0-790c3dfdfc73 (kept earlier as 'GitHub traffic complement to GitHub Insights') - b9379aff-9e5c-4d01-8f2d-9e4ffa09d126 (moved to the certctl.io landing page in commit ef7da23) Re-evaluating: GitHub Insights → Traffic already provides repo views, uniques, clones, and referring sites with click counts at higher granularity than a Scarf pixel can extract from the README (Scarf can only see 'github.com' as the referrer; GitHub Insights knows the actual external referrer that landed the visitor on the README). The 89db181e pixel was duplicative-and-worse. Removing it. All certctl analytics now consolidate to: - GitHub Insights → Traffic (built-in, more granular than Scarf on the README surface) - certctl.io's b9379aff pixel (referrer-attribution for landing- page traffic, where Scarf actually adds value) - Scarf Docker Gateway via shankar0123.docker.scarf.sh/* (when the Helm chart + docker-compose.yml are routed through it — follow-up work) The Docker-pull example block at line 246 stays (it documents how operators install certctl via the Scarf gateway). Only the in-README tracking is removed. --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index d49f0ee..cba7ef4 100644 --- a/README.md +++ b/README.md @@ -2,8 +2,6 @@ certctl logo

- - # certctl — Self-Hosted Certificate Lifecycle Platform [![License](https://img.shields.io/badge/license-BSL%201.1-blue.svg)](LICENSE)