No. This is not a limitation of Cromite but of all Chromium-based projects in general, as general public is not allowed to use Google's APIs for free unless when using Chromium.
Additionally, these features would not be privacy-friendly.
No.
Yes, but if you were to find connections to cloud-based services please report them via the issue tracker.
Cromite uses Internal firewall patch to disable unwanted connections and ungoogled-chromium: no special hosts/domains for the removal of all code that uses pointers to Google servers.
Please note that the patch is called ungoogled-chromium but has nothing to do with the project of the same name.
No, since it is unclear whether any externally retrieved DRM required licence is bound to the device and the correct way to delete it.
No, but there are plans to activate it.
It is not on the official F-Droid repository.
You can use F-Droid client to install and receive updates via the official Cromite F-Droid repository.
Using Cromite will favour the monopoly of the Chromium/Blink engine, why do you develop and maintain Cromite?
Many years of experience with chromium code leads me to think that it is indeed the best browser out there. Its flaws are Google's priority to its customers over its users, but I don't have that problem.
No. But there is an intention to explore this issue further.
The Chromium Blink engine uses GCM to deliver messages when websites use the Push API; this will not work in Cromite because cloud integrations are disabled (GCM in this case).
No. TWAs will not work because they are generated server-side on googleapis.com (which is not allowed in Cromite).
What is supported is home shortcuts that launch the browser without its interface.
Yes, the native Android autofill can be used.
No, this would require Play Store binary blobs.
No. Cromite does not make any choice related to default search engines, user will have to decide during the first launch. You are still free to enter any search engine you prefer via the settings ui.
Cromite uses public lists for adblock that you see in the settings. Please check if the issue is due to the rules (and if so, report the problem in its correct repo) before requesting a check.
Cromite comes with JavaScript JIT disabled by default. You are free if you prefer to reactivate it via settings.
ADB is developed in c++ while uBlock is an extension in javascript. Currently, support for extensions is not active in Android.
ADB in Cromite is enhanced with support for cname uncloaking and blocking even in workers (a unique feature of Cromite). Support for "acceptable ads" has been completely removed.
I haven't decided yet. Currently the motivation is that I have no time or desire to understand how donations work in my country and with my current job position. Fortunately, I don't need it for now.
JIT stands for Just-In-Time compilation and is a feature of chromium v8 which is the module responsible for executing javascript code. The purpose of JIT is to compile javascript to speed up its execution.
However, the use of JIT opens up possible security holes exploited over time to scale the chromium sandbox and allow access to privileged processes by javascript. Technically, the reason is that the memory used by JIT is read/write/execute and can therefore be exploited to insert code from, for example, a UAF (use-after-free) error within a javascript callback. In addition, the activation of JIT allows the exchange of shared memory between different frames, an amazing and at the same time risky feature.
For this reason, in cromite (and its predecessor cromite) it was chosen to disable JIT by default, penalising execution but offering a smaller attack surface.
If you trust the site or have performance needs or need to use WebAssembly, you can activate that feature specifically for that website via UI:
Show me how
Cromite blocks the ability to open apps from the web by default.
The reason for this is that, together with the app to be opened, information may be passed on and cannot be filtered out: for example, youtube links definitely send the url of the video, but not necessarily other data. The other information could link your web browsing with that within the app.
It is however possible to disable this behaviour and allow apps to be opened.
Show me how
