Repository navigation
Remove Plausible analytics from the mobile app - #121
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #120. Part of lockdown-systems/collective-tracking#51 — remove app telemetry entirely rather than re-implement it. Usage insight continues to come from cyd-server's own authenticated data.
Ripped out fully: no no-op transport, no
PlausibleEventsvocabulary left behind.Summary
The TODO about delete-job events dies with the map — that's the point of the epic's decision.
Evidence
grep -ri plausiblehitsservices/analytics.ts,types/analytics.ts, and their three consumers; every job-runner dispatch starts with atrackEventcall.After:
tsc --noEmitpasses,expo lintpasses,npx jest— 79 suites / 902 tests passed (6 pre-existing skips) — andgrep -ri plausibleover app code returns zero hits.What stays (not Plausible)
/user/activity(on mount),/bluesky-progress(including the unauthenticated fallback), push notifications, IAP — all stay.Merge Danger
Door: two-way — pure deletion; git revert restores everything.
Blast Radius: app startup, Bluesky sign-in, and the Bluesky job runner dispatch (one telemetry call each, nothing replaces them). No UI, settings, or store-listing changes. Ships with the next release whenever that is; released versions swallow the failed POST silently, so nothing breaks before then.
(This was written by an LLM.)