To be clear I did read the links i provided in my above post.
Do you not consider this instructions on “disablong features”
How to completely disable / remove features in Brave
The instructions above show how to “hide” features from the browser UI. However, in some cases, you can take the added step of completely disabling the code that runs these features, and/or that keeps these features updated. This is equivalent to removing network calls or the downloading of any new code related to updates for that feature.
Which provides more information about actually disabling some features. Note that if you want “Origin-level functionality” in that you don’t want these features complied into the browser that is not possible here, but that is only available on standalone versions of Origin (vs an “upgrade”) regardless.
I do see that you link to this page and quote yourself. Is your issue here that these group policies are not available on iOS/Android?
Ping is not just a UI bug.
I am aware, however what I mean here is that from my testing the ping is not actually being sent, there is just a meissleading UI toggle appearance on first boot, which disappears after first boot.
There was an issue with this ping being enabled and sent by default in Origin, however as I previously stated in my testing and discussion it appears to me the ping is no longer sent by default, though the confusing UI situation still exists.
If Brave really does intend to leave this ping disabled in Origin it would make sense to me to completely remove the “daily usage ping” toggle UI from the browser, instead of leaving it in potentially causing confusion.
Android/iOS - Group policies are not available. Features cannot be disabled, only hidden.
macOS - requires downloading MDM software or SSH access
Windows - Pro edition is required and you need to download and apply policy templates, on Home edition you need to make changes to the registry. Doesn’t look very user-friendly. Administrator privileges are also required to apply group policies.
A more or less normal way to disable settings for a regular user exists only in Linux, where you can simply create a JSON file.
By the way, Brave itself doesn’t even recommend all these manipulations.
Note that this action applies at the level of your device’s operating system, and could have unintended consequences. You should only attempt to disable features via Group Policy if you have a high level of technical knowledge.
Anonymous 479 on the other post about brave origin has confirmed that Brave Origin actually does send daily usage ping on Linux when those settings are enabled by WireShark. Have you also inspected the packets yourself?
When I tested on Brave Nightly, the report_enabled entry didn’t even exist in the config file. I had to manually add the line and set its value to false. Did this change on full release?
Yes, in my testing both nightly and full release versions of Brave Origin had the reporting_enabled variable present in the Local State configuration file and set to “false” before user intervention or browser restart. Even though the UI toggle “send daily usage ping” was present and “enabled” on first boot.
Regarding:
I did not leave Brave Origin open for a prolonged Wireshark network capture, however on my latest testing I did briefly view the packets being sent by Brave Origin and did not see the daily usage ping being sent in the full release or latest version of nightly for Brave Origin.
@JohnDose I would be interested to know when you did the testing you mention here? All testing I mention has been done in the last ~4 days, with the latest testing happening within the last 2 days.