Practical suggestions for resolving the Brazilian problem

Aha, with my beard it will be ok. But who trimmed him was a Morrocon Muslim.
About child sex, never your are death, but at certain age horny, did not mention number. I cannot go into politics or religions.
Very important, now mus cheach food.
 
This is very interesting. So if the user is an adult (defined as over 18) the company is allowed to use surveillance methods, but if the user is under 18 the company must disable it?

Why not simply say "no company shall use electronic surveillance methods against their user regardless of age"?

Because it would be political suicide.

I agree the surveillance should be disable for all people, but I don't know what planet a politician could get such law approved; it would put a target on their back for big tech PR.
 
  • Like
Reactions: mer
I think the idea behind it is good. But as always lawyers/politicians want to make it difficult for everyone. They should focus on the problem. And target solution which fixes specific problem. But then most layers now nothing about informatics or software in general. They tend do write large documents. And that is their business.

If this is an accurate statement about the reason (I think it is):
The purpose of the law is not to monitor users, but block companies from track, collect, profile and sell personal data from children, also block advertising targeted to children, block dark patterns and other tricks used in e-commerce and games platforms and other stuff that can be considered harmful to children. It is not government surveillance.

Then the real problem is companies tracking/collecting/profiling/selling personal data. Ignore the "age" related aspect, if the companies should not do it for minors, why should they be allowed to do it for adults? About the only thing one could argue is "age related target advertising" as in don't present Lagavulin ads to a 12 year old but present to a 33 yr old. But also do the reverse: don't present ads targeting 12 yr olds to a 33 yrs old.

So ban/restrict all these things regardless of age.
 
To respond directly to the thread title I have a simple answer. "Ignore it!" In a practical sense it is kind of meaningless to a cloud based FOSS project. If the code is hosted in-country then they might demand that it be removed. If it is hosted elsewhere then what can they do other than try to keep their own citizens from downloading and using it? and we know how well that works. LOL
 
The Virginia version seemingly got blocked because it included certain categories but not others (addictive games): https://cbsaustin.com/resources/pdf/70c794d9-f8d7-489d-b4d0-9409fd2d36fb-189114911210.pdf

Blocking everything "nefarious" would likely include gambling, and sports companies aren't going for that :p
I don't disagree, but how does a website validate the user input? You tell Facebook you were born 1/1/1901. They accept it, but how do they verify it? You'd need to enter more and more personal identification "upload a picture of your birth certificate or gov issued photo id" for them to be "sure". Which every moderately secure person says "No".

A minor lies, gets adult access, parents sue company because "you exposed my baby to bad stuff"
Adult lies, gets limited to minor access, gets tossed in jail because "impersonating minor".

So as a theory, age restricted content is an overall public good, but implementation has more holes than a colander. Adding the force of government behind "you got it wrong" makes it even worse to me.
Almost as if every website will need to verify a user fingerprint or retinal scan against a gov database which means the gov has more and more identifying data on the individual.
Or does every individual get microchipped at birth (like is done with dogs and cats), then website verification is "hold this scanner against your chip and upload the results for verification".

To me I have no problem with the intent of the law, but work through the implementation and it fails.
 
Are you a lawyer? Are you the FreeBSD foundation's lawyer? How are you qualified to give advice? Hint: I'm not qualified to give advice, because I am not a lawyer, in particular not the foundation's lawyer, and in particular not familiar with Brasilian or international law (in spite of the fact that my passport says "Republica Federative do Brasil" on the front cover).

... how the FreeBSD developers could resolve this problem within the next 11 days.
The FreeBSD source code exists, and is openly visible from pretty much anywhere on the internet, including Brasil. Most source files have a copyright, with the holder of the copyright being the person who wrote the code. Most source files have a license, which in most cases is the BSD license. Only the copyright holder can modify the license. There must be thousands of people who have copyrights on the code; the idea that they can all modify the licenses to add "not to be distributed in Brasil" is ridiculous.



1. Geo-block Brazil from image downloads and from pkg repositories.
The foundation operates the main download site, and that content then feeds to a variety of mirrors. The foundation could do this for their own distribution. It's not clear to me that doing so would violate the license. But this is pointless. The old adage "the intern treats censorship as a traffic disruption and routes around it" would apply: A variety of other download sites would spring up.

Given the licenses, the foundation has no power to restricts others from distributing FreeBSD.

Pkg will also have to state on every execution that the FreeBSD package repo is for 18+ users only and it is the responsibility of the system administrator not to permit use of the system by minors.
I strongly suspect that nobody has the power to modify existing licenses by adding an age clause, other than the holders of the copyright. If someone (such as the foundation) did this, they would become a target of lawsuits.

I would suggest that we leave it to the people who are potential affected by this (the holders of the copyrights, and the foundation) to get some legal advice and deal with it (which includes the option of doing nothing). The solution to this will be legal, political and contractual, not technical. Talking about "tokens" and such makes no sense at this point.
 
  • Like
Reactions: mer
a certain Peter T
HumanCertificate.jpg
 
Wow, he's human? Another piece of human garbage, ruined a company because they printed something bad about him. If curious look up Hulk Hogan and Peter Thiel.

Unfortunately, in this world, if you have money, you can do that and avoid all consequences.
 
Wow, he's human? Another piece of human garbage, ruined a company because they printed something bad about him. If curious look up Hulk Hogan and Peter Thiel.

Unfortunately, in this world, if you have money, you can do that and avoid all consequences.
Actually, entity 345,273,742-H is not him, it's some other person. All certificates feature his picture because he considers himself more important than the certified individual 😲

I know about the Hulk Hogan story. I wonder where I heard about it. I can't remember right know. Possibly on a YouTube video.
 
Good point, but considering that for Thiel it was just payback, I was rooting for the other side--who, to be honest I don't remember their name without web searching, just remembered they were a scandal type site.
 
As I see it, this is an attack on free software made by people outside of "official institutions".

It's easy to understand: the more oppressive "official software" becomes, the bigger the demand for decent software, and so free software becomes a bigger problem for those trying to impose their abusive software.

What we are seeing now are just the first steps trying to wipe off free software as we have known it so far; the Google attempt to lock down Android is just a step in the same direction.

The excuse of age verification doesn't hold, Brazil has 32 million children living in poverty (63%) with much bigger problems than accessing or not an operative system.

So my proposal about the "Brazilian problem" is facing it and call it by its real name: a few unelected people controlling big tech already have too much power over Western countries, and are trying to wipe off free software so they have still more power.
 
Looking at the 2025 FreeBSD Community Survey, 94% of users in the survey were older than 25. One can expect the number of users who are younger than 18 to be a strict subset of the 6% of users who are younger than 25. From that, it's clear that the vast majority of users are adults.

I'm not clear on whether "likely to be accessed by" means "children are prohibited from using" or "a low proportion of use by children is allowable".
However, if I look at the 3 elements of "likely to be accessed" enumerated in the pdf shared prior in this thread:
i) "whether the ITPS is attractive to minors" - Very doubtful, given the survey results.
ii) "whether it is easy to use and accessible" - Not if you take these forums at their word.
iii) "whether it poses a significant degree of risk to the privacy, security, or biopsychosocial development of minors" - To hazard a guess, a minor using FreeBSD would develop better knowledge of how to safeguard their privacy and security online, but would be best served seeking their romantic partners elsewhere.

If the below is true:
The purpose of the law is not to monitor users, but block companies from track, collect, profile and sell personal data from children, also block advertising targeted to children, block dark patterns and other tricks used in e-commerce and games platforms and other stuff that can be considered harmful to children. It is not government surveillance.
Then as far as I am aware, FreeBSD does not monitor users, track, collect, profile, or sell personal data from children, target advertisements to children, or use dark patterns, tricks, or other techniques within e-commerce or a games platform to sell to children. From which my non-lawyer mind infers that FreeBSD is already compliant with the spirit of the law.

Additionally, the BDS license states the following:
IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES ...
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
Say we assume a child was using FreeBSD, and a tech giant failed to recognize that the child was a child, resulting in that tech giant targeting advertisements to that child, or collecting that child's data. Does the license not protect the contributors? Why should harm resulting from either the tech giant's actions or the child/parent's use be assigned to contributors, when such an assignment of liability directly contradicts the licensing terms?

Further, assuming code would be implemented, how is the age-data determined or verified by a party relying on it, or on an assertion of age?
Section 4.3 of the pdf, Age Verification Measures, prohibits "age verification through self-declaration", and requires "proportionate, auditable, LGDP-compliant, and technically secure age verification measures". Yet what does that mean, precisely? What is the format? Is this text, or numeric? What format is expected by those requesting it? Who is requesting it? Do they intend for the data to be anonymized, or public? Does it apply to locally-running applications, websites a browser connects to, or local applications that may download data from various servers? What is considered "content" w.r.t. an OS? Are they asking for every file in memory, or saved to the filesystem, to be scanned and automatically assigned an age-rating or assessed for "legality", according to Brazilian law? Is the law sufficiently precise that it can be reasonably implemented?
 
TL;DR
I do not think FreeBSD should necessarily do anything at this moment in time besides some form of malicious compliance if/where feasible. FreeBSD is not aimed toward kids/teens, and the Brazilian law text is too broad and too poorly written in order to even gauge if its usage by kids/teens is "probable enough"; furthermore, the text seems to foresee further regulation and the possibility of different requirements for distinct platforms, so things could change.



I do not know if/when this will get posted (though I am not new to FreeBSD, I am new to the forums). Also, I'd like to apologize to the reviser of this wall of text beforehand. I'm sorry :p



Context
Just to contextualize a little: in 2025, a major Brazilian influencer by the name of Felca randomly decided to upload an explosive video exploring (in the sense of "reporting the dangers of") the concept of "adultization" of minors. The video depicted very strong (and thus censored) footage that included Brazilian minors (specially teenager girls), half or even fully naked, lying in bed with adults or doing sensual dances and poses for videos and pictures to be uploaded to social networks or sold otherwise. The video also showed how adults had been profiting out of child/teen sexualization and exposition, and even accused some of the most blatant wrongdoers, presenting names and faces of such exploiters to the public. Safe to say it left the whole country horrified, and so a state of moral panic ensued along an outcry for "blood". Some high-profile personalities got arrested for exploitation of minors, and politicians scrambled to make an emergency law in order to "protect our children and teenagers". Thus was born Law 15.221/25, a.k.a. "The Digital ECA", a.k.a. "The Felca Law", approved on September/2025 and set to take effect starting on March 17, 2026 (Art. 41-A). The law was clearly created in a haphazard way (just out of curiosity, even the name of the Brazilian president is written wrongly at the end of the law's official text, missing a starting 'L'), and also clearly written by people unfamiliar with digital systems and platforms, as politicians and lawmakers tend to be.


How much probable/likely is "probable/likely enough"?
Among its many problems, one is the generality of the text: it refers to safeguards that need to be implemented by systems/platforms that are aimed at children and teenagers, but then adds the very generic "or which are probable/likely to be accessed" by them. But how probable, and how to measure such probability? That is up to interpretation. Considering the internet and its nature, I conceive every single system/platform has a non-zero probability of being accessed by children/teenagers. Is that probable enough for the law to apply? Also up to interpretation.


Age signals and some current implementations/responses
Among its many devices, one that is of particular concern is located under Chapter IV, more precisely Art. 12-III, where it is established that systems/platforms will need to provide an API which will be responsible for managing (i.e. generating, saving, providing accessors such as getters and setters for) what is called an "age signal". The idea is that this signal will need to be used for the purposes of identifying an age bracket for the user of a digital system/platform in order to determine whether said user can access that particular system/platform or not. This is where the law mainly expects most systems to take action in order to provide such API (though there are many more requirements that might demand action under Articles 24 through 33). In Android, we are already having to do age signaling via Google's Play Age Signal API. M$ is expected to start rolling something out soon, possibly making its chaotic usage of the TPM, which will then store user IDs alongside age signals. Others, like Apple and Steam, are trying to bypass this hellscape by using the (possibly already provided) credit card information of a user: the idea is that, if you have a credit card in your name, then you are a legal adult and that's it. And, since it seems to be a possibility nowadays, if a child/teen has a credit card in his/her name, then there needs be a legal guardian (e.g. a parent) associated with that card, and apparently a backend can be used for such verification without the need for any additional information. Some Linux distros, such as Omarchy, have already issued "no-comply" statements, not specifically to the Brazilian law, but to the "retarded California law" (their words). I do not expect their response to be different regarding the Brazilian one. And, as for huge Linux distros like Ubuntu, the latest information seems to be that they are analyzing, along with legal counsel, the texts that are popping all over the U.S and the world in order to decide what course of action to take.


What about FreeBSD?
As for FreeBSD, in what concerns the Brazilian law, I personally think that it should not need to do anything at the moment, or at least not anything concrete, at most some sort of malicious compliance if/when/where feasible. My opinion is that the text in its current form is just too broad and poorly written in order to even gauge if and where FreeBSD should take any action in the first place. FreeBSD is certainly not something that would be improper for minors, so it does not fit under Art. 9º (which is the only article that explicitly vets autodeclaration in the official text). It also certainly is not children/teenagers oriented, though there does exist a non-zero probability that it could be used by minors. But, as already discussed, would it be "probable enough" to warrant action? Plus, Art. 34 already states that complementary norms may be issued to regulate the devices presented by the text, which strikes me as some sort of self-awareness that the text is very poorly written (or maybe a backdoor to make it even worse in the future). And Art. 34, § 2º foresees the possibility of regulatory authorities adopting distinct requirements that are proportional to each service's nature, risk and business model. Meaning, things can change, though if to alleviate or even radicalize some of the devices presented therein is unknown.

Just my two cents (or lots of cents). Sorry for the text wall.
 
I think it would make sense for the Brazilian FreeBSD user group to send a polite letter to the Brazilian National Congress explaining the reasons why FreeBSD (and similar projects) should be exempt from that law and asking for an amendment to the law exempting them from complying with it.

This could be important because:
  • It makes clear that they don't agree with the law, otherwise, saying/doing nothing could be interpreted as being perfectly happy with it.
  • Maybe somebody in the Congress will realize the awkward situation and a proper amendment will be made, and this would be an important precedent for similar laws anywhere else (i.e. if Brazil made an exception for FreeBSD in its law why shouldn't California do the same in theirs?).
  • If Congress doesn't reply the letter it could be understood as "siléncio administrativo" which means they agree with the letter, and so that letter could be used to justify not complying with the law (this works in some countries, I don't know in Brazil).
Of course the letter should be sent by a legally binding method, in Argentina this is called "Carta Documento" and "Burofax" in Spain, in Brazil there must be something similar.

I believe doing nothing is a bad idea: an abuse that is tolerated just leads to suffer bigger abuses.
 
Back
Top