There are reasons to use beta products even if you don’t have any interest in sharing data. I have to use a beta version of Firefox for Android, for example, because Mozilla decided stable releases aren’t allowed to access about:config or install addons they didn’t vet. I’ve also uses beta drivers for a while when stable release drivers crashed my computer.
If companies didn’t push their betas as timely bug fixes as often (and just made the data collection opt-in like they should do anyway) we’d probably see less outcry about this.
The point of betas/alphas is for testing. They aren’t really to help you out. If they don’t get testing data, there’s no sense in them letting users use it, then complaining about it breaking something and not getting the data to fix it with.
Firefox for Android does not let you access about:config and comes with an addon whitelist. Your options are to use the beras/nightlies or to use forks that don’t support things like EME.
I reported my findings on the bets drivers on the forum that linked them to me, but I doubt anyone ever looked into those. This was years ago, but I’ve never seen a manufacturer respond to forum topics with anything useful.
If companies would add feedback buttons to their software instead of telemetry, I’d be willing to provide it. I’ve only seen Microsoft take feedback through their software, though, and that feedback seems to disappear into a black hole that nobody reads or cares about.
I can promise you, the feedback is being read. They won’t respond, but it’s being seen. They also may not choose to change it in the way you want, because of how much effort it’d take or it going against their goals, but it’s being viewed by someone.
Yeah because it’s harder to bitch and moan about data collection when you’re opting in to a program that is literally for data collection.
But my privacy! I want all the latest and most unstable shit without giving anything back!
There are reasons to use beta products even if you don’t have any interest in sharing data. I have to use a beta version of Firefox for Android, for example, because Mozilla decided stable releases aren’t allowed to access about:config or install addons they didn’t vet. I’ve also uses beta drivers for a while when stable release drivers crashed my computer.
If companies didn’t push their betas as timely bug fixes as often (and just made the data collection opt-in like they should do anyway) we’d probably see less outcry about this.
The point of betas/alphas is for testing. They aren’t really to help you out. If they don’t get testing data, there’s no sense in them letting users use it, then complaining about it breaking something and not getting the data to fix it with.
huh? Of course you can access about:config on stable releases and install addons from outside their website?
And you installed beta drivers to see if they run better than the latest version. Would have you reported your findings back or just keep it to you?
Firefox for Android does not let you access about:config and comes with an addon whitelist. Your options are to use the beras/nightlies or to use forks that don’t support things like EME.
I reported my findings on the bets drivers on the forum that linked them to me, but I doubt anyone ever looked into those. This was years ago, but I’ve never seen a manufacturer respond to forum topics with anything useful.
If companies would add feedback buttons to their software instead of telemetry, I’d be willing to provide it. I’ve only seen Microsoft take feedback through their software, though, and that feedback seems to disappear into a black hole that nobody reads or cares about.
could have said that you were talking about firefox for android from the get go :)
Oops, I thought I did! I edited my comment, apologies for the confusion!
I can promise you, the feedback is being read. They won’t respond, but it’s being seen. They also may not choose to change it in the way you want, because of how much effort it’d take or it going against their goals, but it’s being viewed by someone.
deleted by creator