On Wed, Mar 29, 2017 at 12:29 PM, Kurt Roeckx <k...@roeckx.be> wrote: > The FAQ seems to suggest that telemetry is only enabled in the pre-release > versions > and not in the release versions. I assume there is a bias that is caused by > this.
There are two types of telemetry: "Firefox Health Report" (enabled by default) and "Telemetry" (enabled by default in Nightly, Aurora and Beta but not in release builds). Arguably, system configuration info belongs under FHR, so it would not be optimal if the Pulse check wasn't there but was in opt-in Telemetry instead. Where was it? It's a problem if distros disable FHR by default or if distros disable the first-run on-boarding UI for opt-in Telemetry. In any case, running without telemetry means not having a say in data-driven decisions about what configurations Mozilla should support. It's OK to disable telemetry (that's why it's user-controllable), but both users and distros that make decisions on users' behalf should to take into account that if don't let Firefox send info about your system config to Mozilla, your system config is invisible to Mozilla's decision making about what to support. > Pulseaudio is really a layer between the application and alsa. If pulseaudio > can do something it should be possible to do the same with alsa. It's not that "ALSA can't do this or that" it's "cubeb on top of ALSA without Pulse in between can't do this or that without additional work that's already done by Pulse or by cubeb on top of Pulse". > But maybe pulseaudio makes certain things easier, I don't know. That PulseAudio makes things easier has been a key point that has been made. -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
