Send anonymous usage data with no identifier, on by default with a clear notice and a one-click off

Aperta
#724 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
macos, swift
Ambito
desktop

Direzione di ricerca

Start with Sources/StableBar/BugReport.swift for the existing Mac facts and configuration summary, then read the Settings → General implementation, setup flow, docs/, and DECISIONS.md. The issue leaves the report destination, legal review, and whether to publish totals open, so those decisions need resolution before implementation. Done means consent notices and controls, identifier-free daily reports, updated privacy text and decision record, and release notes are in place.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Problem

We decide what to build, test and keep without knowing how StableBar is used: which macOS versions people run (macOS 27 broke clicks on the bar, #366, and Menu bar items, #372), how many use AeroSpace, yabai, OmniWM or macOS Spaces, how many keep the bar below the menu bar instead of replacing it, how many displays and notched screens they have, and which built-in widgets and themes they keep. Trimming the bundled themes to seven (#370) was a guess. Today the only signals are issues from the few who report, stars, and GitHub's download count per release.

A switch people have to turn on would leave those numbers thin and skewed toward the most engaged people, so this proposes a report that's on by default and can't identify anyone, with a clear notice and a one-click off.

StableBar sends nothing about its use today. The privacy policy (https://stablebar.app/privacy.html) says "no account and no analytics", and the Product Hunt page says the same, so both change before the release that turns this on.

Proposal

Anonymous usage data, on by default, with no identifier.

Notice and off switch

  • Setup shows what's sent, with the Share usage data switch on the same page, so turning it off takes one click.
  • People who update from a release without this see a one-time notice with the same switch.
  • No report goes out before the person has seen the notice, in setup or after updating.
  • The release notes of the release that turns it on say so.
  • Settings → General gets a Usage data group next to Updates, with the switch and Show what's sent, which shows the exact report the way Copy bug report does.
  • It's an app preference like the update checks, not a configuration property, so a shared configuration, a theme or a package can't change it.
  • Turning it off stops sending at once.

What's sent, at most once a day per Mac while the bar runs, as one small JSON report over HTTPS:

  • StableBar version and update channel (stable or beta).
  • macOS version, Mac family (MacBook Air, MacBook Pro, iMac, Mac mini, Mac Studio, Mac Pro), how many displays and whether one has a notch.
  • Whether the bar replaces the menu bar or sits below it, and the workspace tool (AeroSpace, yabai, OmniWM, macOS Spaces or none).
  • The theme's ID when it's bundled or from the Store, which built-in widget kinds are on the bar and how many of each, how many script widgets, profiles and screen setups, and the IDs of installed Store packages.

There's no install ID: nothing ties one report to the next, and the Mac remembers only the day it last sent one. The totals count daily active installs, not people, and the receiving end doesn't keep IP addresses. Homebrew's analytics work the same way: on by default, with no per-install ID or IP address kept (https://docs.brew.sh/Analytics).

Never sent: any identifier for the Mac, the person or the install, configuration values, scripts and commands, file paths, the names of custom widgets, themes or packages from other sources, calendar, window or app data, and crash reports. Copy bug report (#93) already gathers most of these facts in Sources/StableBar/BugReport.swift (MacFacts, ConfigurationSummary), so the report can reuse them.

Docs: the privacy policy and the Product Hunt text, before the release that turns it on, the Settings page in docs/, and an entry in DECISIONS.md for what may be collected and that it carries no identifier.

Open questions for the maintainers

  • Where reports go: a hosted, privacy-focused service (TelemetryDeck, for instance) or a small endpoint we run. An SDK would be a new dependency, so a plain HTTPS request is better either way.
  • Whether a report with no identifier, on by default, is enough under EU rules on reading facts from a device. Someone who knows the law should check before it ships.
  • Whether to publish the totals, on the website or in the repository, so people see what their data is used for.

Possible today

No. GitHub counts DMG downloads per release, but not active installs, the versions in use, setups or widgets. Update checks read the appcast on GitHub, which gives no counts. Bug reports carry the environment only for the people who file one.

Related

  • #333 / #338: crashes stay on the Mac and leave it only in a GitHub issue the person submits. This doesn't change that; sending crash reports automatically would be an issue of its own.
  • #93 / #341: Copy bug report gathers the same facts about the Mac and the configuration.
  • #378: the privacy policy, which has to change with this.
  • #22: update checks, which can be turned off in Settings → General → Updates.

Triaged by Claude Code (Claude Opus 5.5).

Lingua principale
Swift
Stelle
184
Fork
12
Merge medio
3h 50m
PR unite (30g)
387

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Seb-GRAF/StableBar

Tutte le issue di Seb-GRAF/StableBar

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.