https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/55H3DT5CCL73HLMQJ6DK63KCAHZWO7SX/

However, we also want to ensure that the data we collect is meaningful, so gnome-initial-setup will default to displaying the toggle as enabled,even though the underlying setting will initially be disabled. (The underlying setting will not actually be enabled until the user finishes the privacy page, to ensure users have the opportunity to disable the setting before any data is uploaded.) This is to ensure the system is opt-out, not opt-in. This is essential because we know that opt-in metrics are not very useful. Few users would opt in, and these users would not be representative of Fedora users as a whole. We are not interested in opt-in metrics.

Essentially they’re playing with words to say it’s opt in but if you just click Next like most users will do, it’ll be enabled. The developer openly admits few users would opt in and complains that it wouldn’t be useful.

  • Secret300@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    On Endless OS, applications use a D-Bus API (via a small C library, eos-metrics) to record metrics events locally on the device. This API is implemented by a system-wide service, named eos-metrics-event-recorder or eos-event-recorder-daemon (no, I don’t know why it has two different names either), which buffers those events in memory, and periodically submits them anonymously to a server, Azafea, which ingests them into a PostgreSQL database (after a short layover in a Redis queue). If the computer is offline – often the case for Endless OS systems! – events are persisted to a size-limited ring buffer on disk, and submitted when the computer is online.

    From https://blogs.gnome.org/wjjt/2023/07/05/endless-oss-privacy-preserving-metrics-system/

    Fedora says they intend to deploy endlessOS’s metric system