Sheogorath @sheogorath@shivering-isles.com

Note to self: More proof reading before tooting.

@Liberapay just curious, but why do I need an liberapay account for a donation via e.g. bank transfer?

Other people have favourites on GitHub, I mirror the repositories instead.

https://git.shivering-isles.com/explore/projects

And you can even subscribe to it, by subscribing to https://git.shivering-isles.com/shivering-isles/mirror-bot.

Every now and then, a new repository is added :)

Another idea would be the system-wide collection of these data and require a user-review on submit unless they decided to let it automatically submit.

This user-review would allow to review all telemetry data that is collected per application and enable or disable the submission of this data to upstream data providers.

This way the user is always in control and can decide what they want to share and what not. (Similar to the existing abrt reports)

What is not provided by now, is a way to track feature usage unless you package each feature individually. Here we really have to look into the details because this can easily result in profiling.

While this is the most useful data of the telemetry, it's also the most critical. We might need a way to announce a feature name with a boolean that is collected on a distro level as "trustworthy data handler" providing the detailed information only on a reasonable sample size.

I guess an easy way to pull these data together from the various vendors is missing. On Fedora abrt creates bugzilla tickets. Obviously, unless you also maintain the Fedora distro package, you won't get any of the crash reports. Doing that for every distro is absurd. So we need an easier way to move tickets upstream.

For the OS stats, each distro builds their own solution. Collecting these metrics in a reasonable wax including the variation on package name is a challenge.

I think it is valid for a vendor to try to get a view on the install base e.g. how many versions of my software run on which kind of systems. Those should be plain numbers, which on Linux can easily provided by a package manager. (We already do that on various distros)

It's also in the interest of the user, to have an easy way to report crashes to a vendor, without being overly into software development. Again, we have abrt for that on an OS level.

So what is missing?

Now may home directory swap is in the makings :3 looking forward to how it turns out :D

Even better that I produced a corrupt installation medium and didn't test it before exchanging the SSD of the device.

Good that I'm a real professional, otherwise I would have noticed that I forgot to download and setup the system image on the USB stick, AFTER installing the new SSD.

Some important rules to play this game: Write long, unaccusing, friendly emails. When you are redirected between responsibilities, do some fingerpointing, mention that the pointing authoritity doesn't value the targeted authority's time. Provide a small amount of proofs/hints (1-2 links of well-known news or research papers).

Mainly ask questions. If they are not answered, mention that they missed answering your question and ask it again.

It's a fun little game.