Good to know. I may try it out in a VM and check out the before/after status. If I can come up with a good uninstall routine, I might make it a part of mydesktop build.
Great idea, Try it where it can’t do any damage to your main machine. It came on slowly, First brave would not even install and work. So I uninstalled it. Then after a couple updates using the updater I started getting warnings telling me that the updater would no longer work. I tried it anyways and was able to update a few times then it started refusing to update at all. Then I started to question why “Amazonaws.com” is involved with Brave at all...
Here are the errors I saved from the event.
Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/brave-sylvia.list:1 and /etc/apt/sources.list.d/brave-sylvia.list:2Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/brave-sylvia.list:1 and /etc/apt/sources.list.d/brave-sylvia.list:2Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list.d/brave-sylvia.list:1 and /etc/apt/sources.list.d/brave-sylvia.list:2Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/brave-sylvia.list:1 and /etc/apt/sources.list.d/brave-sylvia.list:2 The repository ‘https://s3-us-west-2.amazonaws.com/brave-apt sylvia Release’ does not have a Release file.Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.See apt-secure(8) manpage for repository creation and user configuration details.Failed to fetch https://s3-us-west-2.amazonaws.com/brave-apt/dists/sylvia/main/binary-amd64/Packages 403 ForbiddenSome index files failed to download. They have been ignored, or old ones used instead.