Our great sponsors
-
user.js
Firefox privacy, security and anti-tracking: a comprehensive user.js template for configuration and hardening
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
firefox-privacy-restorer
A script to modify your Firefox preferences to disable telemetry, built-in advertisements, and data collection anti-features
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
serverless-dns
The RethinkDNS resolver that deploys to Cloudflare Workers, Deno Deploy, Fastly, and Fly.io
-
rethink-app
DNS over HTTPS / DNS over Tor / DNSCrypt client, WireGuard proxifier, firewall, and connection tracker for Android.
-
>Telemetry isn't surveillance.
(honest question) Why is this necessary then: https://github.com/arkenfox/user.js
What I'd like to see is a Firefox (and Chromium) fork with
- automatically builds and uploads via GitHub CI (or similar) from a well-commented build script
- all the knobs for reproducible builds set up, so anyone can fork the repo, run the CI themselves, and see that it's bit-for-bit the same thing
- an automatic merge or rebase of the latest stable release tag, and the result of that merge being plugged into automatic updates
- an automatic merge or rebase of the latest beta tag (or even nightly), and some form of alerting if the build fails
- perhaps some Selenium + Wireshark automation to see what requests happen and make sure there are no unexpected ones
And, actually, it seems like LibreWolf is on the way there. https://gitlab.com/librewolf-community/browser/common has a decently-well-commented build script that grabs the latest tarball from Mozilla and builds on top of it, and their documentation (https://librewolf-community.gitlab.io/docs/) mentions that as well. But I don't see where it is run / who runs it, and what they do if the build fails.
(Honestly it seems like setting up the release automation and alerting is a substantial project in itself.)
Maybe I’m missing something but it looks like there aren’t actually code changes, rather a repackage with a strict policy file:
https://gitlab.com/librewolf-community/settings/-/blob/maste...
I was wondering how they could instantly patch nightly builds and this seems to be the approach. Good idea and nice to have a build pipeline that allows tweaking Firefox to this degree.
It started with this, but applies to other extensions also:
[1] https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
I'm part of the team maintaining the "boot 2 gecko" aka b2g fork (we push it to https://github.com/kaiostech/gecko-b2g) so I have some experience building a non-firefox product on top of gecko, and maintaining a non-upstream platform (the "android without java" stack called Gonk).
At some point we compared gecko with a blink port on Gonk, maintaining both while we were doing performance comparison on low end mobile devices. We were looking both at memory usage and page loading speed.
(Disclaimer: I work on the Firefox Application Update system)
> But let me opt out
It seems to me that you can opt out. You can use the "Check for updates but let you choose to install them" setting in `about:preferences`. Or you can use the exact policy currently under discussion: `DisableAppUpdate`. Or there is another policy called `ManualAppUpdateOnly` [0].
> (Mozilla, are you listening?)
Why yes, we are listening. We have heard many people request the ability to disable automatic updates, which is why we have the options that I mentioned above. If you feel that these options don't meet your needs, we would really appreciate you filing a bug [1]. We will get to it fastest if you put it in the correct component (which for this issue is `Toolkit::Application Update`).
> for the love of god please don't override my preferences back to automatic updates when you decide to change the UI of preferences.
I'm guessing that you are referring to when we removed the "Never install updates" setting [2]? This wasn't fundamentally a UI change. We had several good reasons to remove the underlying pref. Naturally, that meant that the UI for that pref went away as well. I won't spend a lot of time getting into our reasoning here, but we would be happy to discuss it with you if you want to chat with us about it. You can find us in the `#install-update:mozilla.org` channel on https://chat.mozilla.org
[0] https://github.com/mozilla/policy-templates/#manualappupdate...
NextDNS is the gold-standard and many capable alternatives have cropped up in its wake in the recent times like windscribe's controld.com but RethinkDNS is not it.
Our primary objective is anti-censorship, and so, we make it simple for folks to deploy their own DoH (which means all our code is open source). Today, the serverless DoH stub resolver deploys to cloudflare workers but we plan to support deno.com/deploy and fly.io soon (already have it working in our development branches but the incompatibility between node and deno is causing a bit of pain to merge with mainline). RethinkDNS is a reference serverless DoH deployment, if you will.
We build content-blocking too but believe the right avenue to block content is either in-app where possible (like uBlockOrigin in Firefox) or at the IP-layer (not DNS), and hence we also build a Firewall (due to our limited eng resources, our open source firewall is Android-only, for the time being [1]).
That said, we do plan to achieve parity with NextDNS, but that's going to happen over a period of time since our team of 3 is stretched thin between building the firewall (too much complexity!) and the dns (too much work!).
[0] https://github.com/serverless-dns/serverless-dns
[1] https://github.com/celzero/rethink-app
NextDNS is the gold-standard and many capable alternatives have cropped up in its wake in the recent times like windscribe's controld.com but RethinkDNS is not it.
Our primary objective is anti-censorship, and so, we make it simple for folks to deploy their own DoH (which means all our code is open source). Today, the serverless DoH stub resolver deploys to cloudflare workers but we plan to support deno.com/deploy and fly.io soon (already have it working in our development branches but the incompatibility between node and deno is causing a bit of pain to merge with mainline). RethinkDNS is a reference serverless DoH deployment, if you will.
We build content-blocking too but believe the right avenue to block content is either in-app where possible (like uBlockOrigin in Firefox) or at the IP-layer (not DNS), and hence we also build a Firewall (due to our limited eng resources, our open source firewall is Android-only, for the time being [1]).
That said, we do plan to achieve parity with NextDNS, but that's going to happen over a period of time since our team of 3 is stretched thin between building the firewall (too much complexity!) and the dns (too much work!).
[0] https://github.com/serverless-dns/serverless-dns
[1] https://github.com/celzero/rethink-app
From the latest Audacity release notes:
>A journaling feature has been added for QA purposes.
What exactly does that mean?
https://github.com/audacity/audacity/releases