mikebrandon/here-telemetry-rnd
1
0
Fork 0
Code Issues Pull requests Projects Releases 10 Packages Wiki Activity Actions
10 releases 10 tags
  • v0.1.0 34c5d3e0ed

    v0.1.0 — the Windows client, and macOS Pre-release

    mikebrandon released this 2026-09-04 08:16:15 +00:00 | 67 commits to main since this release

    Work-session telemetry that captures on a contributor's own machine, gates every byte locally,
    and shows the person what it took.

    This is the first release, and it carries two clients: the Windows one, which is the reference,
    and a macOS port of all seven signals.

    What is in the box

    Nothing server-side. That belongs to the platform team and docs/PLATFORM-INTEGRATION.md is
    their handoff.
    here-capture-macos-arm64.zip here capture.app — Apple Silicon, twelve binaries in one bundle
    Windows to follow, from a Windows machine

    macOS

    Unzip it, put it in /Applications, open it. It is not signed, so Gatekeeper will refuse
    it after a download — right-click and choose Open, or:

    xattr -d com.apple.quarantine "/Applications/here capture.app"

    It will ask for nothing until you switch a signal on, and three signals need a permission
    that only you can grant     — Screen Recording, Accessibility and Input Monitoring, in System
    Settings › Privacy & Security. Until they are granted the Capture screen lists exactly which
    signals are refused and which setting each one needs, rather than switching them on to produce
    nothing.

    Apple Silicon only. An Intel or universal build is a one-line change to
    scripts/bundle-macos.sh if anybody needs one.

    What each platform enforces, and where they differ

    Two claims are weaker on macOS than on Windows, and the client says so on its own first screen
    rather than leaving it in a document:

    • Network denial is not enforced. On Windows every collector is blocked by a firewall rule
      before it starts, and one that could not be blocked is not started at all. macOS has no
      per-process rule, so "a collector cannot leak" rests on a reviewed binary with no network
      code. Weaker, and stated as weaker.
    • The store's key is a file only its owner can read, rather than wrapped by DPAPI. The
      Keychain is the right API and cannot be used until the client is signed: an item's access list
      is per-binary, this client is four processes, and a second unsigned binary reading an item the
      first created blocks on a modal dialog.

    Not built, and named so it is not mistaken for done

    • No code signing on either platform. SmartScreen and Gatekeeper will both object, and
      modules.signature_ok records false rather than pretending.
    • No installer.
    • The browser extension is unpacked; it loads through Developer mode and registers with
      scripts/install-extension.sh or .ps1.
    • The macOS pill is read-only — it says what is being captured and offers no way to act on it.
    • Linux has the transport and the paths and nothing else.

    HANDOFF.md is where to pick any of that up.

    Downloads