Conversation

Notices

1. khm (khm@mastodon.sdf.org)'s status on Thursday, 09-Feb-2023 04:13:17 JST khm

   Google only has one real product, across all their offerings, and that product is spying on people. They're absolutely unable to help themselves.

   https://github.com/golang/go/discussions/58409

   • khm (khm@mastodon.sdf.org)'s status on Thursday, 09-Feb-2023 13:45:18 JST khm

     in reply to

     • Cassidy James :eos: :gg: :fh:

     @cassidy Who can see the usage data is not really relevant, especially because there's no way in hell we can ever know if the data we get has been molested by Google bureaucrats.

     The problem here is that a multibillion-dollar corporation is so shitty at community management that they want to unilaterally embed spyware in a development toolchain.

     Imagine someone suggesting this shit at the Austin Group, and the firestorm that would result. This is demonstrating an accountability issue in Go.

     Wrongthink likes this.
   • Cassidy James :eos: :gg: :fh: (cassidy@mastodon.blaede.family)'s status on Thursday, 09-Feb-2023 13:45:19 JST Cassidy James :eos: :gg: :fh:

     in reply to

     @khm honestly, the proposal sounds… fine for the most part? I love the idea of fully transparent telemetry, where the data is directly published in the open to validate what is collected and hold the project accountable; in fact, this is exactly what Plausible Analytics enables which I think is a great model.

     Opt in versus out is a good question and would require some thought. I do feel like an active choice (rather than a passive default) would be the best route, though.

   • khm (khm@mastodon.sdf.org)'s status on Thursday, 09-Feb-2023 13:45:28 JST khm

     in reply to

     • Cassidy James :eos: :gg: :fh:

     @cassidy Open source software already runs the world. Caving into spyware isn't going to put Debian machines on the shelves in Best Buy.

     If you allow this spyware to infect FOSS projects, you've taken a major step toward compromising the entire purpose of software freedom. This is not an example of how to do metrics correctly, it's an attack.

     The example of how to do metrics correctly is "don't." Build relationships with your users so they trust you with information.

     Wrongthink likes this.
   • Cassidy James :eos: :gg: :fh: (cassidy@mastodon.blaede.family)'s status on Thursday, 09-Feb-2023 13:45:30 JST Cassidy James :eos: :gg: :fh:

     in reply to

     @khm I have a problem with unilaterally calling open source, transparent metrics “spyware,” regardless of who maintains the project. That isn’t helpful when there are actually-invasive closed telemetry permeating everything we do, and fighting *that* is actually worthwhile. But mixing them up just means open source software will forever be at a massive disadvantage when instead we could lead the way with how to do metrics correctly, while actually preserving privacy and transparency.