I'm not sure but it can be changed to anything the user wants:
> all of the components of the server (discussed below) are open source, and we will provide instructions for how to run a simple server yourself and view its metrics database. You can redirect metrics from Fedora’s server to your own by changing a URL in a configuration file.
I'm fine with these changes as long as they are transparent.
So, to me, as long as they use a specific and dedicated (and known) fqdn, I may just block the whole telemetry adding that entry in /etc/hosts file), can't I?
And you need to remember to do that every time, on every host that runs Fedora. In practice, after a while you'll stop doing that. That's the beauty of opt-out, eventually nobody opts out any more.
Whether it is useful or not skates pretty close to a utilitarian argument which has little to do with privacy, it is quite possible to violate privacy and get some use out of it but it shouldn't happen anyway.
The privacy respecting part here seems to be handled carefully, I'm not sure if it is opt-in or not (in my opinion it should be) and the payloads appear to be benign, but, that could still go off the rails if there is a bug in ABRT.
In principle I want my machines (desktops, servers) only to initiate network calls and to respond to network calls that I allow. Outbound firewall rules are there for a reason.
> all of the components of the server (discussed below) are open source, and we will provide instructions for how to run a simple server yourself and view its metrics database. You can redirect metrics from Fedora’s server to your own by changing a URL in a configuration file.
I'm fine with these changes as long as they are transparent.