3 ms·

Yeah....I'm not gonna trust a Firefox fork maintained by 1 dude, and if Firefox would ever disappear I don't expect any of these forks to pick up the slack. I'

Yeah....I'm not gonna trust a Firefox fork maintained by 1 dude, and if Firefox would ever disappear I don't expect any of these forks to pick up the slack. I'm not a fan of everything Mozilla does with the project but it's still better than the alternatives.

ryanisnan 4y ago
You are the only person to have brought this exact point up. And I think it's a huge one. I think it's pointless to go on about the features or the add-ons you'd need to add to Firefox to achieve this level of privacy in your browser, while ignoring the glaring problem that this has a really small maintainer pool and I assume folks have done no due-diligence on who those folks are. I'll admit, I haven't done due-diligence on any of the folks at Mozilla, but I think it'd be a lot easier to socially engineer a project like LibreWolf than Firefox. Edit: I'll add I mean no disrespect to the folks at LibreWolf, in fact it's awesome what they're doing. I just find it hard to take most things at face value these days, especially a browser.
- emsixteen 4y ago
  Mentioned the one you replied to, but it syncs as normal to Mozilla's profile sync - what are you losing out on if the maintainer stops maintaining it? "It can die some day" - everything does.
  - ryanisnan 4y ago
    That is far from the only concern. For me, the biggest consideration is trust. With such a small maintainer base, you are placing a large amount of trust in their team. There would be huge motivation in creating a privacy-focused browser that secretly slurps data and/or monitors users somehow[1]. Using a project like this would require me trusting a small-handful of people I don't know at all, and aren't represented by an entity I somewhat inherently trust (Mozilla). I can't say my logic is without holes, for example I don't do much to verify my trust in Mozilla, but you have to make generalizations in this field or you would never get anything done. [1] If you need a real-world example, see Anom.
emsixteen 4y ago
Normal syncing of profiles works with it so you have no need to worry if the fork ever does die.

ryanisnan 4y ago

You are the only person to have brought this exact point up. And I think it's a huge one. I think it's pointless to go on about the features or the add-ons you'd need to add to Firefox to achieve this level of privacy in your browser, while ignoring the glaring problem that this has a really small maintainer pool and I assume folks have done no due-diligence on who those folks are. I'll admit, I haven't done due-diligence on any of the folks at Mozilla, but I think it'd be a lot easier to socially engineer a project like LibreWolf than Firefox. Edit: I'll add I mean no disrespect to the folks at LibreWolf, in fact it's awesome what they're doing. I just find it hard to take most things at face value these days, especially a browser.

emsixteen 4y ago
Mentioned the one you replied to, but it syncs as normal to Mozilla's profile sync - what are you losing out on if the maintainer stops maintaining it? "It can die some day" - everything does.
- ryanisnan 4y ago
  That is far from the only concern. For me, the biggest consideration is trust. With such a small maintainer base, you are placing a large amount of trust in their team. There would be huge motivation in creating a privacy-focused browser that secretly slurps data and/or monitors users somehow[1]. Using a project like this would require me trusting a small-handful of people I don't know at all, and aren't represented by an entity I somewhat inherently trust (Mozilla). I can't say my logic is without holes, for example I don't do much to verify my trust in Mozilla, but you have to make generalizations in this field or you would never get anything done. [1] If you need a real-world example, see Anom.

emsixteen 4y ago

Normal syncing of profiles works with it so you have no need to worry if the fork ever does die.