Goal: Segregate the Internet and break it up through forceful decentralization via age verification.

The idea is quite simple. Target FOSS repositories that are compatible with age verification and submit pull requests and issues that implement functionality for age verification. Implement AV in a way that purposefully, but not too obviously shows the freedom-restricting nature of AV. We will let the grifters scream about how this hurts Internet Freedom so we dont have to say it to the faces of the ignorant masses and make it obvious.

SystemD implemented a prototype for AV. Extend upon it and demonstrate a true proof of concept in a program. Claim credit. Associate with Cyberix and draw more attention to the Operation.

Expectation: A slew of fortified alternatives, made for decentralization will spring up. I expect a flavor of Linux to come out soon that declares freedom and proper self-defense from kernel sabotage. Programs that do what they are tasked to do and nothing more. Useless garbage goes away and change for the sake of change becomes prohibited.
Best scenario: The old UNIX hacker philosophy is revived once more and common sense in programming prevails
Alternative scenario: Lol lmao i don't even use it so it doesn't impact me

thoughts?

Honestly we can only hope with our fingers crossed that this is the scenario that happens. Honestly I cannot see many of the people who use unix for freedom adopting any of these age verification standards. I stopped using any single website that begs for it , I always had the idea though what if we used it to further fuck with the system. Find a way to use AI To upload fake face verification , " Oh what you're 100 Years old ?" , Just use their own tools against them.

Why don't you make the fortified alternatives and Linux flavours you talk about instead of implementing age verification? You want to piss on the floor to make others clean it up. Lack skills to do anything constructive? Expecting others will do it all for you? I believe in making the change you want to see, if more people had that attitude we would all have less problems.
There's existing software anyway. I don't think the BSD systems will take to this, and am aware some distros will be actively pushing back on this.
This age verification thing has got me thinking of switching from Debian to OpenBSD soon. Will be an effort because I have to move a software RAID config, and have to test that I can still use my JTAG tools on it.

>>12325
>Implement AV in a way that purposefully, but not too obviously shows the freedom-restricting nature of AV.
What does this look like?

The digital age assurance act doesn't demand ID verification. It's a dropdown.

The freedom-restricting aspect is buried in the fallout, when they add more demands. When you need to get your ID validated by one or more commercial services to even access a normie search engine. When every app that allows people to communicate demands access. When every one of the top N websites demands it. When websites can cross-validate when age thresholds were passed to determine exact ages.

>A slew of fortified alternatives, made for decentralization will spring up.

Spring up now, spring up later, or already sprang up years past? Not every project self-doxes and lives in USA. It's still an important issue. (I heart normie scum.)

I don't get what you mean by segregating the internet. Underage vs of age? Normies vs users of freedom software? The former is their ostensible goal, the latter may be their actual goal.

__________________

I think getting out ahead of it is the right idea, but accelerationism is often too clever by half. We can't know for certain that the calculus works out in our favor when we use this sort of "make it worse... so someone else will fix it for me!" step in a plan.

The process of validating an ID is either
A. making sure the ID looks right in a photograph, and the face looks like the person's face
B. cryptography
C. asking a server with access to a government database if it is a good ID

A is a computer vision task- something you can implement locally, without a third party service. Bloaty but about as self-sovereign as you can be while complying with soyciety.

B is something we aren't set up for in the USA, but may be an issue across the pond?

What can can we do in timeline C? Not much, only avert it.

So: implement A locally to prevent C.

Remember, their justification for this is that KIDS are going to be at risk. It doesn't need to be fundamentally secure against a "hacker" who literally owns the hardware. It only needs to be plausibly secure against a kid. No, not your hacker genius kid, the actual kid as perceived by worried parents who vote. So make insecure ID "verification" to set the powers that be back a step in their justifications.

________________________

What about the side effects of exposing age data, no matter how it was validated? Exposing DoB to any app with the right permissions is a bad idea. But what is substantially better?

I know there are people who are working on zero-knowledge proofs for this kind of thing, but as in differential privacy a query that gets an answer always leaks information. Even if there were clear legal standards for what age barriers to place, if you see a website or app asking every day "are you your_age + 1 yet" that isn't clearly bad behavior. On a microblogging site like tumblr your feed could be populated by content from people you follow and they're trying to hide the content for your_age + 1 and show the your_age, every single day.
You could try to popularize a standard where age is only updated quarterly. Which would mean you need to be 18 and an average of 1.5 months before you can view porn. The law and business obviously wouldn't like a standard where the computer lies about someone's age up or down for legal reasons- especially near the legally significant age boundaries like 18 and 21. You're always either losing business or open to liability. But it isn't a law, it is a standard that is more considerate of the privacy and safety of users and kids.