dmesg submission service -- please submit today

Matt S staroscik at
Mon Oct 8 17:25:09 UTC 2018

I don't see how "dark pattern" applies because this doesn't trick you into
an ongoing subversive data-sharing arrangement. In this idea, install asks
you if you want to share stats once--you are not opted in to a system.
Then, when processing upgrades, the Handbook would remind you that the
report ability exists and this is a good time to do it if you've made any
changes. Nothing happens without your explicit agreement during install,
and nothing happens afterwards unless you type in a command, every time.

If the current data is adequate for the project's needs, nothing needs to

If the project needs to know more about hardware stats, the request to get
hardware info needs to be somewhat visible. Making it an optional part of
installing/updating seems reasonable to me.

I'm assuming we trust the project, but if the idea of easier stat-sharing
is offensive, then I guess there's nothing to talk about.

On Mon, Oct 8, 2018 at 10:09 AM blubee blubeeme <gurenchan at> wrote:

> On Tue, Oct 9, 2018 at 12:48 AM Matt S <staroscik at> wrote:
>> It really seems like the project would benefit from having better hardware
>> stats. If you make it a package, people have to be educated to get it and
>> use it--not that it doesn't have value, it just isn't well exposed and you
>> will only get stats from the most clueful users.
>> I would suggest making anonymized stat upload part of the install and
>> upgrade process, to get wider coverage.
>> - When installing, there's a new step or checkbox with an opt-in for
>> hardware data sharing, defaulting to off
>> - If you opt in, your info is uploaded as part of the install process
>> - Expose the same functionality in a new system-level command like
>> 'freebsd-uploadstats' and make it an optional but suggested part of the
>> upgrade process, which is something most users will see repeatedly if they
>> continue to be users.
>> Perhaps the local machine can generate a hash of the report, check that
>> with the server before the upload goes through. Hardware doesn't change
>> that often.
>> I do not want the project to turn in to Google or Microsoft, but knowing
>> the hardware in use is a pretty worthy goal.
>> MS
>> _______________________________________________
>> freebsd-stable at mailing list
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at"

More information about the freebsd-stable mailing list