701–710 of 768 posts
I will start making a list for linux then. rm - ok for all ages. grep - 18+, you can obviously use this to search for porn. find - 18+, see grep. reboot - ok for all ages. echo - ok for all ages. cat - 18+, prints the porn you found directly to your terminal. sudo - 18+, obviously. kill - ok for all ages. This is the US, right. ps - 18+, no peeping at other processes.
Earlier quoted context omitted.
What I'm reading of this law is that it requires OS developers to require users select their age (really their age bracket) when making a user account, and an interface for applications/websites to read that user-provided field. I.e. not age verification, but just a standard way to identify if a user is on a child account. If that understanding is correct, how is this bad at all ? It's a way to put to rest people's c…
It's not enough to just accept the age signal: > (3) (A) Except as provided in subparagraph (B), a developer shall treat a signal received pursuant to this title as the primary indicator of a user’s age range for purposes of determining the user’s age. > (B) If a developer has internal clear and convincing information that a user’s age is different than the age indicated by a signal received pursuant to this title, t…
Earlier quoted context omitted.
Term limits are anti-democratic, and it's just a way for voters to not take responsibility for their voting. A much more real issue is actually age limits. If someone starts in the Senate at 40 and serves for 24 years, term limits hardly seem to be the big issue. They are retiring at a normal time, and they should still be functioning at a high level. Conversely, someone who gets elected at 70 and then gets term-limi…
I don't really see why age limits would be exempt for "voters need to take responsibility for their voting". IMO, the real issue is that voters are coerced to accept candidates put up by the parties due to FPTP. The threat of the wrong side winning gets people to accept someone they don't want. The primary process does not need to be democratic, and the results are pressured by the future threat of losing to the othe…
US is running on beta version democracy; it was wonderful for a trial run and we learned a lot from it, but unfortunately the country has been stuck without upgrades for a while. It'd be like trying to connect a Xerox PARC desktop to the modern internet.
Obviously it's absurdly nontrivial to shift it at this point but I do agree that age and term limits both seem to be stopgap solutions due to the challenge of implementing more effective strategies.
Consider Australia: of 226 parliamentarians, there's one aged 75+: Bob Katter.
I'd say there's three features of the au system that keep us relatively free of the absurd incumbency advantages in USA:
1. Compulsory voting makes it harder to solicit votes from a subset of the populace.
2. The Australian Electoral Commission is highly trusted as a neutral body, so Gerrymandering is rare.
3. None of our voting systems use First Past The Post; it's all ranked choice, babes!
Does not require verification, no biggie, this is essentially a parental control system.
As others have pointed out, this is just a foot in the door. There's also a part of the law this article doesn't cover that requires EVERY application to query this information on every launch, regardless of whether or not the application has any age related limitations.
Earlier quoted context omitted.
I'm trying to understand how this is even a bad thing. Where is the privacy invading verification? Surely a given OS can implement the API response however it wants? If you're root, tell me your age. If you're not, (a child account), the admin (their parent) sets the age. Seems fine?
Even ignoring everything else, at a minimum it is backwards. There is no reason to tell the application, and by extension their developers, how old the user is. The application should tell the user what bracket it is appropriate for and then the operating system could filter appropriately without any of the user’s identifying information leaving their system. This is also technically superior because it moves the log…
How does this work with applications that have a wide array of content of varying appropriateness, for example web browsers? The obvious thing to do is for sites to self-report for 18+ content and have the browser query the OS using this newly mandated API and refuse to download/show the associated content. You really need both sides here for this to work well.
There's an obvious theme with lawmakers in California—they pass laws to regulate things they have zero clue about, add them to their achievement page, cheer for themselves, and declare, "There! I've made the world a better place." There are just too many examples. For instance: - Microstamping requirements for guns—printing a unique barcode on every bullet casing (Glock gen3 cannot be retired, thus, the auto-mode swi…
I will start making a list for linux then. rm - ok for all ages. grep - 18+, you can obviously use this to search for porn. find - 18+, see grep. reboot - ok for all ages. echo - ok for all ages. cat - 18+, prints the porn you found directly to your terminal. sudo - 18+, obviously. kill - ok for all ages. This is the US, right. ps - 18+, no peeping at other processes.
fsck - 18+ obviously can't just fsck around filesystems
Earlier quoted context omitted.
This law doesn't do anything that prevents non-anonymous access. Here's how you would access things anonymously if you bought a new computer that implemented this. 1. When you set up your account and it asks for your birthdate, make up any date you want that is at least far enough in the past to indicate an age older that what any site you might use that checks age requires. 2. Access things the way you've always don…
As with all age verification bills, the fact that developers are opened up to liability if children access content they're not "supposed to" means that facial scans and ID checks will be implemented as they currently are everywhere. From the bill: > (3) (A) Except as provided in subparagraph (B), a developer shall treat a signal received pursuant to this title as the primary indicator of a user’s age range for purpos…
If websites accept this as age verification it could provide a very easy way to bypass it.
In fact, looking at it again, point B specifically says if the "developer" has information rather than the "system" has information. So really sounds like if the developer isn't collecting logs that they can access themselves this wouldn't apply to them.
What a ridiculous law, smells of some sort of frog boiling scheme to me. step1: "lets see if we can get away with imposing a small easy requirement, you know 'think of the children'" step2: "now that we have a foot in the door, lets see if we can get some real tracking in place, for the children of course" Anyhow: as far as I can tell compliance on linux would be as simple as echo $YEAR_BORN > ~/.config/ca_ab_1043 It…
Waiting for BSD community maintainers reactions
But anyway I'm not in California nor the US so this doesn't apply to me in any way.