this post was submitted on 02 Nov 2025
310 points (94.0% liked)

Privacy

4139 readers
72 users here now

Welcome! This is a community for all those who are interested in protecting their privacy.

Rules

PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!

  1. Be civil and no prejudice
  2. Don't promote big-tech software
  3. No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
  4. No reposting of news that was already posted
  5. No crypto, blockchain, NFTs
  6. No Xitter links (if absolutely necessary, use xcancel)

Related communities:

Some of these are only vaguely related, but great communities.

founded 1 year ago
MODERATORS
 

AB-1043 "Age verification signals: software applications and online services."

Text https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260AB1043

Other info https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB1043

California AB 1043 signed. Mandatory os-level, device-level, app store, and even developer-required age verification for all computing devices.

Edit: altered title from "ID check" to "Age Verification check"

you are viewing a single comment's thread
view the rest of the comments
[–] 0x0@lemmy.zip 7 points 4 days ago (1 children)

It'll be systemd-agecheck, good luck.

[–] veniasilente@lemmy.dbzer0.com 3 points 3 days ago (1 children)

Just use the normal procedure for switching to sysvinit (or openrc) + elogind. Easy to perform if you still have your install media.

[–] 0x0@lemmy.zip 2 points 3 days ago (1 children)

Just use the normal procedure for switching to sysvinit

On Debian?? That's news to me.

[–] veniasilente@lemmy.dbzer0.com 3 points 3 days ago (1 children)

It's actually well-documented in their wiki (yeah, I know, it's 2025 people don't read that because it's not Discord and that shit). Tho i recommend adding Antix's nosystemd repo if you do that on systems that are not Sid, because the packaging of some important high-level tools is stupidly tied to systemd for some weird reason (NetworkManager being a good example) and the upstreams refuse to unfuck it (which is as simple as restoring the init script those upstreams already used to have).

[–] 0x0@lemmy.zip 1 points 3 days ago (1 children)

is stupidly tied to systemd for some weird reason

Intentional hard-linking.

I went gentoo once debian forced systemd on its users, i wasn't aware they sorta backtracked, nice to know.
Slackware and Devuan fill my other needs so i have no plans to go back to Debian.

[–] notabot@piefed.social 1 points 3 days ago (1 children)

Debian never actually forced the use of systemd, they just didn't make it obvious you could switch at install time fairly easily, or later with a bit more work. I'm running multiple sysvinit debian systems, ans they're ticking along quite happily.

[–] veniasilente@lemmy.dbzer0.com 1 points 12 hours ago (1 children)

I'm not sure "tying the use of user-facing structures most useful for the community" (such as cgroupsv2 or NetworkManager) doesn't count as "forcing", since IIRC wicd (alternative to NetworkManager which doesn't require systemd) has not been available in packages since Bookworm.

[–] notabot@piefed.social 1 points 12 hours ago

NetworkManager seems to operate correctly without systemd, although maybe there is some aspect of it that I'm not using that does require it. It's working find on both desktop machines and laptops though, correctly managing ethernet, wifi, and vpn connections.

Likewise, I've not encountered any issues with cgroupsv2.

Support for different init systems was improved in Bullseye, although sysvinit had pretty good support even before then. I followed the instructions here and everything seemed to work out of the box.