Does Brave have proprietary components? If so, do you know which parts?
Iām not sure, I just know itās impossible or close to impossible to build if from source code (and have if as fully featured as the official build).
In the words of one of the developers:
Only Brave Software produces the official builds for Brave browser
It looks like it is fully open source.
There is an AUR package for it:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=brave
Isnāt that true for any software? That seems like a rather meaningless statement.
With
--official_buildenabled, there are going to be a lot of config values needed (Google keys for safe browsing, etc) which only the Brave Software owned official build servers have configured. You can stub those config values out (putting fake or empty values)- but the services that Brave consumes at runtime (Safe browsing, fetching extensions, fetching adblock rules, Brave Rewards, Brave News, etc) will fail and folks checking the binary against the signing keys will realize itās not an official build
I am not sure these things failing is actually a bad thingā¦
Going through the git repo everything is public so it doesnāt seem like they are hiding a thing. Not too sure what @Kresimir is refering to with it
What isnāt true for any software is that the user gets a different set of features from the officially distributed binary, and the binary one builds by oneself, unofficially. This difference practically ensures that Brave cannot be compiled from source by distro maintainers for the repos, at least without taking a binary from Brave.
My concern, of course, is that with binary distribution of a browser, one cannot be sure if the published source code is the one that was used to actually build the binary. So I would like my browser to be compiled by the people I trust, the distro maintainers.
According to the above, the features are the same. You just donāt get the Brave keys. This makes some things not work unless you replace them with valid keys yourself.
The whole code and repo are very open, binary vs the git will always be different and I canāt spare the resources to try see if there are any differences.
Of course. But thatās missing the point. The point is: who is building the binary? Brave? Or Arch TUs?
If you use the binary from Brave, thatās completely equivalent to it being closed source, because you cannot know whether the binary was built using the published source code.
(itās a hypothetical question, since Brave is not in the repos)
Yer I donāt use and with browsers I would never use them from the AUR, I get that sort of point sorry if I missed it. I would much prefer if I was going to go that route to build it myself, sorry for the misunderstanding
Sounds like a good thing actually ![]()
SaFE BrOWsINg is used to censor some legit websites in times of political turmoil, for instanceā¦not only scam and baddies.
Yes I can think of a recent one here (george last name rhymes with bell) was blocked by all ISPs and Media wasnāt allowed to say anything about it at first except mention the outlining facts. Many people jumped online using VPNs etc at the time to expose the story. Anyone else it would have been instantly public information.
No itās the other thing that you canāt āsolveā with VPN, itās basically a system that flags websites untrustworthy and shows huge red page saying that itās DANGEROUS!!!1111111 ![]()
Itās list curated by Google which can be abused in a short-term byā¦just mass-reporting.
So basically you can scare most normies away during short period of time from any website by simply abusing this crapā¦Thatās exactly why i always turn it off in my Firefox / Librewolf.
I have a virtual machine set up for links like this and the majority of these flagged sites are safe except for maybe learning the other side of the story, I get what you mean
I want this!
Iām confused by this story. Whatās wrong with people only changing minimal stuff if they publish the source code of those changes? It means if there are ever any meaningful improvements he can use that to improve his own code.
I like the license he chose, if I understand it correctly, it should make it hard for people to make money from his work. I think this means that they have to publish the source code for the modifications.
3.1. Distribution of Source Form
All distribution of Covered Software in Source Code Form, including any Modifications that You create or to which You contribute, must be under the terms of this License. You must inform recipients that the Source Code Form of the Covered Software is governed by the terms of this License, and how they can obtain a copy of this License. You may not attempt to alter or restrict the recipientsā rights in the Source Code Form.
3.2. Distribution of Executable Form
If You distribute Covered Software in Executable Form then:
- such Covered Software must also be made available in Source Code Form, as described in Section 3.1, and You must inform recipients of the Executable Form how they can obtain a copy of such Source Code Form by reasonable means in a timely manner, at a charge no more than the cost of distribution to the recipient; and
- You may distribute such Executable Form under the terms of this License, or sublicense it under different terms, provided that the license for the Executable Form does not attempt to limit or alter the recipientsā rights in the Source Code Form under this License.
If I understand the issue correctly, there were people changing only the logo/name on the browser and monetizing it. Basically, they were profiting solely off his work and not disclosing that it was based on floorp.
His new license requires both attribution and non-commercial use.
There was also the thing with those āclonesā not upstreaming some of their commits in accordance with the license, other than monetizing.
Where is the new license mentioned? On github I only found MPL2.0. After a bit more reading itās a weak file based copyleft license.
Isnāt CC BY-NC-SA made for art and ācreativeā works? Why not use AGPL? Iām planning to release something, but itās so confusing.
It looks like he changed the license again by creating his own. It is here:
It more or less has the same core provisions.
The AGPL would be a strange choice for a web browser. It wouldnāt be much different than the GPL for that use case, right?
Iām in the process of learning about licenses and itās confusing, Iāve read some questions and answers, but they just made me more confused. So yeah, not sure when to think AGPL or GPL.
I still donāt understand, how can someone sell a version of Floorp if they only change the name and logo? Who would be stupid enough to pay for that? Was this even a real issue or the developer was overthinking?
If someone makes some useful modifications to the browser, and they want to monetize it with those, wouldnāt they be required to release the source code for those modifications under GPL?
Letās say they donāt comply, he could DMCA them?