Our great sponsors
-
brave-core
Core engine for the Brave browser for mobile and desktop. For issues https://github.com/brave/brave-browser/issues
-
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.
-
bromite
Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser!
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
privacytests.org
Source code for privacytests.org. Includes browser testing code and site rendering.
> The gclient utility (part of depot tools) will fetch the official Chromium source code. The tag that is fetched is captured in our package.json (for example, 70.0.3538.35). All of the source code will be downloaded into the ./src/ folder
The "captured in our package.json" part links to https://github.com/brave/brave-browser/blob/master/package.j...
But I think it's supposed to link to https://github.com/brave/brave-core/blob/master/package.json
The text is a link to the commit disabling it (https://github.com/brave/brave-core/pull/4548/commits/322153...), which is within a PR (https://github.com/brave/brave-core/pull/4548), which has the following comments:
> May I ask why this is disabled? I personally found this feature useful for sharing direct links to parts of pages that did not have a nearby id attribute.
> more info here: https://www.theregister.com/2020/02/20/chrome_deploys_deepli...
There were some privacy concerns, regarding leaking of user information: https://github.com/WICG/scroll-to-text-fragment/issues/76
Also check out Ungoogled Chromium (https://github.com/ungoogled-software/ungoogled-chromium) which goes above & beyond by not just "proxying" services but rather removing all phone-home functionality altogether.
There's no for-profit entity behind it, so no perverse incentives to monetize either (but that also means they don't have a budget for proper CI, signing, distribution, etc.) so there's a bit of DIY work involved on less-popular platforms.
I use Ungoogled Chromium as a backup whenever a website makes the unfortunate choice of not properly supporting my main browser, Firefox.
Add the Bypass Paywalls extension, it works on Firefox and Chromium. https://github.com/iamadamdev/bypass-paywalls-chrome
I personally use Bromite.
https://www.bromite.org/
I used to use SRWare Iron on the desktop, but not for many years.
https://en.m.wikipedia.org/wiki/SRWare_Iron
As it stands today, the spec has issues when considering other pre-existing options and future comparability. For example, there is no way to get the URL if the protocol is `file://`.
For a real world example: https://github.com/mozilla/standards-positions/issues/194#is...
See the stack overflow issue: https://stackoverflow.com/questions/67039633/get-the-text-fr...
I think it can be easily fixed, using things like but there probably needs to be apart of a wider discussion concerning URL extensibility.
I don't use Brave and I'm not shilling for it, but it does consistently rate high in privacy research:
https://privacytests.org/
https://arstechnica.com/information-technology/2020/03/study...