Fedora considers “privacy-preserving” telemetry
The actual proposal:<p><a href="https:&#x2F;&#x2F;lwn.net&#x2F;ml&#x2F;fedora-devel&#x2F;CAJqbrbeOZrHvYjvMCc=qGZD_VXBs3-qReeirr+F8t01Eq1sYhw@mail.gmail.com&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;lwn.net&#x2F;ml&#x2F;fedora-devel&#x2F;CAJqbrbeOZrHvYjvMCc=qGZD_VXB...</a><p><pre><code>    === What data might we collect? ===

    We are not proposing to collect any [...] particular metrics
    just yet, because a process for Fedora community approval of
    metrics to be collected does not yet exist. That said, in the
    interests of maximum transparency, we wish to give you an idea
    of what sorts of metrics we might propose to collect in the
    future.

    One of the main goals of metrics collection is to analyze
    whether Red Hat is achieving its goal to make Fedora Workstation
    the premier developer platform for cloud software development.
    Accordingly, we want to know things like which IDEs are most
    popular among our users, and which runtimes are used to create
    containers using Toolbx.

    Metrics can also be used to inform user interface design
    decisions.  For example, we want to collect the clickthrough
    rate of the recommended software banners in GNOME Software to
    assess which banners are actually useful to users. We also want
    to know how frequently panels in gnome-control-center are
    visited to determine which panels could be consolidated or
    removed, because there are other settings we want to add, but
    our usability research indicates that the current high quantity
    of settings panels already makes it difficult for users
    to find commonly-used settings.

    Metrics can help us understand the hardware we should be
    optimizing Fedora for. For example, our boot performance on hard
    drives dropped drastically when systemd-readahead was removed.
    Ubuntu has maintained its own readahead implementation, but
    Fedora does not because we assume that not many users use Fedora
    on hard drives. It would be nice to collect a metric that
    indicates whether primary storage is a solid state drive or a
    hard disk, so we can see actual hard drive usage instead of
    guessing. We would also want to collect hardware information
    that would be useful for collaboration with hardware vendors
    (such as Lenovo), such as laptop model ID.

    Other Fedora teams may have other metrics they wish to collect.
    For example, Fedora localization wishes to count users of
    particular locales to evaluate which locales are in poorer shape
    relative to their usage.

    This is only a small sample of what we might want to know; no
    doubt other community members can think of many more interesting
    data points to collect.
</code></pre>
That last piece &quot;no doubt other community members can think of many more interesting data points
to collect&quot; sounds pretty bad for telemetry that&#x27;s enabled by default, with people having to opt out of it. :(