Hi all,
I am posting to inform you of changes the IPFS Ignite (IPFS GUI & Tools) team is doing regarding metrics collection across our projects.
You can read more at Define basic metrics and patterns for consent & collection. · Issue #125 · ipfs/ipfs-gui · GitHub, but the summary is that we will start collecting some basic metrics by default for our projects, which will be opt-out.
NOTE: These metrics will not track IPFS usage, CIDs, or other non-app-specific usage metrics.
- Collect
necessarymetrics by default.These will be enabled when using our projects moving forward. i.e. you cannot opt-out of these metrics. However,We are doing our best to ensure that these necessary metrics are the minimum required for us to prioritize work on our projects.- necessary metrics will be ‘sessions’ and ‘views’ as categorized by countly (i.e.
const necessaryFeatures = ['sessions', 'views']). See Provide example snippet of data sent to our `countly.ipfs.io` endpoint for necessary features · Issue #130 · ipfs/ipfs-gui · GitHub for more information- sessions - tracks when, how often, and how long users use your website
- views - allows for the views/pages accessed by a user to be tracked
- Note that these view metrics are “App views” and not page URL (i.e. public/private gateway access views that include CID)
- We will allow the disabling of
necessaryfeatures once we switch to opt-out metrics. See feat: switch to opt-out metrics · Issue #2 · ipfs-shipyard/ignite-metrics · GitHub
- necessary metrics will be ‘sessions’ and ‘views’ as categorized by countly (i.e.
- Do not collect any other metrics by default. In each app, prompt users, upon metrics change, to accept to decline the additional metrics.
- Provide a way for users to opt-in or opt-out of
non-necessarymetrics at any time (via settings pages or other)- We will allow the disabling of
necessaryfeatures once we switch to opt-out metrics. See feat: switch to opt-out metrics · Issue #2 · ipfs-shipyard/ignite-metrics · GitHub
- We will allow the disabling of
- Ensure any existing apps have a very obvious banner for existing users to be informed of the following:
- Change of metrics collection policies
- Consent banner to accept/decline
non-necessarymetrics - Note that we may not be able to discern new users from existing users, so we may need a single consent banner that accomplishes both of the above bullet items.
Please post any comments, questions, or concerns on Define basic metrics and patterns for consent & collection. · Issue #125 · ipfs/ipfs-gui · GitHub or in response to this post.
I am not as responsive on discuss.ipfs.tech as I am on github, but will do my best to respond promptly to any comments posted on this thread.