From aef9ab55547ffaf666537ee4358502fa5b439158 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Cihat=20G=C3=BCnd=C3=BCz?= <jeehut@fline.dev>
Date: Tue, 28 Oct 2025 12:33:09 +0100
Subject: [PATCH] Remove outdated macOS user identifier documentation

---
 .gitignore                   |  1 +
 articles/telemetry-client.md | 10 ----------
 2 files changed, 1 insertion(+), 10 deletions(-)

diff --git a/.gitignore b/.gitignore
index aa089d0..1614a82 100644
--- a/.gitignore
+++ b/.gitignore
@@ -138,3 +138,4 @@ site/
 .claude/
 Context.md
 Context/
+CLAUDE.md
diff --git a/articles/telemetry-client.md b/articles/telemetry-client.md
index bb654a0..e46aaea 100644
--- a/articles/telemetry-client.md
+++ b/articles/telemetry-client.md
@@ -62,16 +62,6 @@ let email = MyConfiguration.User.Email
 TelemetryDeck.signal"userLoggedIn", customUserID: email)
 ```
 
-<div class="alert alert-secondary" role="alert">
-<h4 class="alert-heading">Note on User Identifiers on Mac</h4>
-<p><small>If you are writing a Mac App, TelemetryDeck can not create a unique user identifier, and will instead default to a concatenation of your OS Version and App Build number, which is not exactly unique, so user counting will be less accurate.</small></p>
-
-<p><small>We therefore strongly recommend to either use a unique identifier for your users, such as an email address, or to generate and store a `UUID().uuidString`, for example in `UserDefaults`, and always pass that to TelemetryDeck as User ID.</small></p>
-
-<p><small>The reason why TelemetryDeck can't do that itself is that it feels like crossing a line if this simple tool would generate IDs itself and write those to a directory on disk. We feel that this is not expected behaviour for a privacy-first analytics package.</small></p>
-
-</div>
-
 ## Payload Data
 
 You can also send additional parameters with each signal: