#firefox128 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #firefox128, aggregated by home.social.
-
#Mozilla warns #Firefox users to update browsers to the latest version to avoid facing disruption and security risks caused by the upcoming expiration of one of the company's #rootcertificates.
Mozilla certificate expires this Friday, March 14, 2025, and was used to sign content, including add-ons for various Mozilla projects and Firefox itself.
Users need to update to #Firefox128 (released in July 2024) or later and ESR 115.13 or later for 'Extended Support Release'.
https://www.bleepingcomputer.com/news/software/mozilla-warns-users-to-update-firefox-before-certificate-expires/ -
CW: Der Entwickler vom Firefox Fork Mull wird den Browser wohl nicht mehr weiterentwickeln
#Firefox128 is out today with 20 security fixes. I encourage you all to switch to another #browser if you use #Mull, such as #Brave as configured per https://divestos.org/pages/browsers#tuningBrave
I say this because I am not going to work on #Mull128 as it stands. #Mozilla has repeatedly for years now constantly made compiling #Firefox for #Android from source increasingly difficult. And now there is a second circular dependency which I do not care to handle.
And if this means your choices for a browser all contain proprietary code, then you might as well use one with the most protections available at leastNot Mozilla's user-hostile approach which is Firefox for Android.
extensions? no. about:config? no. actual security features? no.
@mozilla does not care.
Does Brave just want your money and cryptoshit scams? Yes, but at least they have strong privacy features and they inherit the security features of Chromium.
Ultimately Mozilla doesn't care if #FirefoxforAndroid can be compiled from source
If someone still wants something like #Fennec F-Droid or Mull they need to put the work inI've been doing it 7 years now and @relan has done it even longer
I don't see anyone else trying
every single other firefox fork on android contains proprietary blobs, including tor browser of all projects you'd expect not tothey don't care either somehow
compilation of 127 is: #fenix < android components < #gecko < application services < android components (older) < glean < glean (older) < wasi126 moved android components into gecko but still depended on an older version that was not in gecko and could be compiled standalone
but not 128 needs a newer but still older version that is now in gecko which means gecko needs to be compiledso likely solution to compile 128 is: fenix < android components < gecko < application services < android components (older) < gecko (older) < application services (even older) < android components (even older) < glean (even older) < etc.
do you see the loop there?
they expect you to just use their prebuilt older versions
you effectively would always have to bootstrap from that 126 version
you can't do this
it is fucked
Quelle: @divested