@unlambda@hachyderm.io
@unlambda@hachyderm.io avatar

unlambda

@unlambda@hachyderm.io

Working on eVTOLs at Beta Technologies. Python, C, Rust.

Too many hobbies, but right now spending the most of my time learning to fly.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

whitequark, to random
@whitequark@mastodon.social avatar

the problem with telemetry in open-source applications is that the majority of people who use them don't tell anybody about their workflow, so whenever you change something, you have to be prepared for a sudden and unexpected inflow of angry complaints about you breaking something

you could do polls, but that selects for people who would complete a poll, again excluding many who would be touchy about their workflow

unlambda,
@unlambda@hachyderm.io avatar

@whitequark I mean, a lot of tools have some kind of "report bug" feature that gathers some info about the system to report more complete information. Just gathering all of the info that you would want to collect in there, and giving the user an opportunity to review it, seems like a pretty reasonable approach.

unlambda,
@unlambda@hachyderm.io avatar

@whitequark oh, I realize that, but I don't think it's quite as cursed an idea as you think because the diagnostic info can also contain useful telemetry info, and as long as it's being manually submitted and reviewable, I don't think it would be all that objectionable

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • JUstTest
  • GTA5RPClips
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • everett
  • InstantRegret
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • modclub
  • kavyap
  • Leos
  • normalnudes
  • cubers
  • osvaldo12
  • tacticalgear
  • Durango
  • khanakhh
  • ngwrru68w68
  • provamag3
  • anitta
  • tester
  • cisconetworking
  • ethstaker
  • megavids
  • lostlight
  • All magazines
    •