77 karma · joined September 4, 2021
And in any case, have you tried applying at Facebook? If you have the answer to their problems and are capable, then why not?
And I know I've said this already but taking those "way too many steps" is exactly what you'd be asking them to do, so it's unclear why it's not worth it for you but it would be for them.
Do you have some numbers to back this up? I would suggest getting that before making any major product decisions. Also if you read the privacy policy, the telemetry is spelled out in detail, or at least it should be, so the people who are voting should be well aware of what is going on. If nobody reads it, then the solution there would then be to make it obvious and easy to read, not to throw it out completely.
>I fully agree, that is the other reason zero telemetry is a way to go and should be default. You can not beat that.
I don't understand. That isn't a meaningful comparison because you're comparing it with nothing, you would need to present an alternate data source. This to me is kind of like saying "not having a stomach beats having a stomach because you won't need to worry about eating anymore" or something like that.
>Imagine in an election, the votes of those who didn't explicitly vote get automatically extracted and cast based on a biased algorithm produced by the government.
I'm sorry but this is exactly what various governments already do in a lot of cases. Not for general elections but for services or programs that they run or for appointed positions. They will do a study with passive data gathering and determine who is actually using what services, and if the results are good they will increase funding to the service, otherwise they will cut funding, fire people, etc. This is generally how any organization functions at scale, so I really don't understand what you're getting at here or what alternative you're proposing. If you want to apply this to product development, it would simply be infeasible for users to vote on every single ticket that a developer handles, so you need to find some other data-driven way to make decisions. That's what telemetry is put in place to do. I think there is a misunderstanding here of how this works, but it's not your fault.
I wish you luck with your company, but I suspect you will have difficulty getting funding on the level of Firefox or Chrome, especially if you have no hard data from some kind of telemetry or similar source. The privacy-conscious user is known to be a fickle market. I also would advise against making misleading and/or unsourced statements about other browsers if you intend to develop a competing product, this makes your company look bad.
From the developer point of view, this is incorrect, the developers are using it to decide which features to prioritize. If you are aware that it's happening and you leave it on, then I don't see what the problem is. Resource and bandwidth usage should be very minimal, if it's not then I would urge you to actually measure it and report bugs. It should be possible to compress it so that it doesn't eat up your bandwidth. Remember that it also takes bandwidth and CPU to post on Hacker News, so you will have to compare it to that to have any kind of meaningful data.
My point is, it if lacks the data from those users, it would make sense to start sending them that data. It doesn't make sense to me to complain about them having incorrect data on you when you intentionally don't send them the right data and then threaten to jump ship because of what seems to be your own actions. I personally also disable telemetry but I know full well that I'm opting out of an important system for them so I don't expect to get attention in return for doing that. If you wanted to help, I think they would very much welcome attempts to fix the telemetry and make it more bandwidth-respecting and privacy-respecting, rather than finding ways to just throw it out.
>You can of course make a zero telemetry browser, relying 100% on your own research and what the users volunteer to tell you directly. And those most passionate about it with tell you the most, a wonderful positive feedback loop.
In my experience, this is an unreliable way to make products, the type of user who is passionate and volunteers this information is not the average user. You will end up with a very niche product that way, and the cost would be very high since you would be expecting the same quality of features but for a smaller number of users. If you're interested to do this I would suggest you to fork Firefox and attempt to get funding, and try that out just to see how much work it actually is compared to how little those users are actually willing to pay. Take a look at Waterfox if you want to see an example of how this would be done.
I think the huge number of about:config options is actually a major problem for Firefox, there is no possible way to test all those options and ensure they stay working forever and have zero regressions. You won't like this, but a lot of them probably need to be removed.
You would need to change the branding but I think some of the other Firefox modifications have systems in place to deal with that. If you ever need to do it, maybe it would be worth asking them.
I'll also mention that only one person needs to create the build, once you do that then anyone else can run that build. That's usually how development works, and in fact this is already the gist of how Mozilla tests their unstable builds.
>the customisability is decreasing, more features are being removed than added
I can't agree with this, maybe the amount of visible settings in the preferences has been reduced, but currently there are a few thousand about:config options, and the number seems to keep growing.
>But they are also bleeding users, so something is clearly not working for them. And maybe, as the OP suggests it is because of changes that anger a minority of their users.
For many years I asked people why they were switching to Chrome and I got various answers, very few of them were because of something negative about another browser, and most of them were about what they liked about Chrome. That's just my personal anecdote. It also just seems to me that Mozilla is in a bad place where people say they drop Firefox because they like Chrome, so Mozilla switches gears to make it more like Chrome, and then people complain it's not unique enough anymore and it's missing some old non-Chrome feature. How could they possibly win here?
Turning off telemetry by default is also not an option, because then they would have no data, and would just be making decisions at random -- I really doubt that would please you either.
It's true the build process is slow, but that's different from being difficult. I don't know what you mean by difficult. Maybe it was difficult in the past but it's entirely automated at this point. You can just start the build and come back some hours later, and that's only if you're starting from a clean repo and modifying the C++/Rust. For the CSS and Javascript, that doesn't need a rebuild at all.
Now after this you may want to refer back to the article. I have seen various pieces and rants like this article that complain about this but none of them offer any more reliable sources of information. The article makes an unverifiable claim of "Almost everyone hated the changes" and unfortunately those type of claims seem to be extremely common instead of presenting some data. That's not enough to change anyone's course.
But in the end, I don't know what you mean by "systematically removed" in that way, frequent addition and removal of various features is completely normal for a large project. And technically only the setting was removed -- you can still customize all that but you'll have to modify the browser itself. No they probably won't add back in the setting but as I explained above, those have a cost, and when the cost-benefit analysis doesn't play out the right way, it doesn't make sense to blame an organization for cutting it.
Yes an update could break your CSS fix, but if you follow the beta releases then this isn't a problem. You usually have at least a few weeks to update your patches before the release goes out.
And violence against trans people has also increased this year: https://www.theguardian.com/world/2021/jun/14/us-trans-trans...
Two years ago, many trans people were banned from serving in the US military. The ban was reversed earlier this year, but that's kind of the point: there are ongoing attacks against trans rights that are still happening right now and need attention. So that is why it gets the focus.