Telemetry #90

Closed
opened 2025-09-12 14:25:22 +00:00 by vaibhav · 0 comments
Owner

For better understanding the demography, but not usage patterns, yet, we will call the home-server and send these data:

  1. Vault Public ID: This value uniquely identifies a vault. Since Vault Public ID is a sha256 hash of vault ID (which itself is unique for all practical purposes), the value will never tell what the vault ID was for the sent data, while also maintaining both the uniqueness as well as the privacy.
  2. The OS on which Chamber is running (macOS, Windows, Linux)
  3. The architecture on which Chamber is running (arm64, amd64)?
  4. The version of chamber that is running.

This data will be sent every few minutes - to know if a user is actually using Chamber actively or not. The value of few is to be defined later.

For this to function we have to first create a backend (for the home-server) which can accept the values sent by Chamber.

For better understanding the demography, but not usage patterns, yet, we will call the home-server and send these data: 1. Vault Public ID: This value uniquely identifies a vault. Since Vault Public ID is a sha256 hash of vault ID (which itself is unique for all practical purposes), the value will never tell what the vault ID was for the sent data, while also maintaining both the uniqueness as well as the privacy. 2. The OS on which Chamber is running (macOS, Windows, Linux) 3. The architecture on which Chamber is running (arm64, amd64)? 4. The version of chamber that is running. This data will be sent every few minutes - to know if a user is actually using Chamber actively or not. The value of `few` is to be defined later. For this to function we have to first create a backend (for the home-server) which can accept the values sent by Chamber.
vaibhav self-assigned this 2025-09-12 14:25:22 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
techrail/chamber#90
No description provided.