Post AlnOA6NW6qsCsGnU7U by sundew@beige.party
(DIR) More posts by sundew@beige.party
(DIR) Post #AlnMI0XZUxzTB28sSW by sundew@beige.party
2024-09-08T10:44:09Z
0 likes, 0 repeats
@MagicLike @askfedi As I understand it, there are some serious security caveats with Waterfox:https://www.reddit.com/r/waterfox/comments/933j6a/is_it_safe_to_use_waterfox/
(DIR) Post #AlnMI1I0iJ8ZV3rxqK by mima@makai.chaotic.ninja
2024-09-08T13:42:04.207Z
0 likes, 0 repeats
@sundew@beige.party 2018 was a time when Waterfox was still a hard-fork of Firefox 56 ESR (to preserve XUL and bootstrapped extensions as well as NPAPI plugins and XPCOM as long as possible). A lot of what's written in the comments of that thread no longer applies to this day as Waterfox now closely follows current ESR and abandoned compatibility with old extensions@MagicLike@soc.sekundenklebertransportverbot.de @askfedi@a.gup.pe
(DIR) Post #AlnOA6NW6qsCsGnU7U by sundew@beige.party
2024-09-08T13:54:33Z
0 likes, 0 repeats
@mima @MagicLike That's good to know.Are the concerns about "delayed application of security patches" and "one-person dev team" still applicable?
(DIR) Post #AlnOA7Egv9PLXBfx0C by mima@makai.chaotic.ninja
2024-09-08T14:03:05.151Z
0 likes, 0 repeats
@sundew@beige.party I remember Alex hiring a full-time dev before to work on Waterfox with him, though that was when the "Classic" version (where the 56 ESR fork ended up) was still being maintained. Looking at it now looks like Waterfox is back to being pretty much one-person again... However this is not too much of a problem imo because all you need to do with a soft-fork like Waterfox is to reapply all your own set of patches each release by the Mozilla upstream.This also means that "delayed application of security patches" is less true now because Waterfox doesn't have to worry about whether a particular security fix is applicable to (or even break) the codebase or not.@MagicLike@soc.sekundenklebertransportverbot.de