The result looks to me like Facebook will ban access from non-approved OSes like Linux. Android will still be allowed, GrapheneOS probably not.
The result looks to me like Facebook will ban access from non-approved OSes like Linux. Android will still be allowed, GrapheneOS probably not.
Kids don't buy phones and computers, parents do. When setting up the account for the first time, the parents could set the account to be an "underage one", all the apps, browsers, etc., would get the USER_IS_UNDERAGE flag and filter content according to that. No need for every site to ask and verify the age, just set the date of birth at the time of purchase, set a parental password (for possible future changes, reselling, etc.) and prohibit formats/wipes/factory resets without a parental password being entered. The clerks in telco stores could even help with the first setup of that.
Same could be easily implemented in linux, via some user flag set by the su/sudo user during the first eg. ubuntu install.
This preserves privacy better by keeping more information about the user local, and gives people better tools to decide what metadata categories they want to filter- for their kids and for themselves.
As one example, the Internet Content Rating Association (ICRA) (and to a lesser extent the prior Recreational Software Advisory Council (RSACi)) had a rating scheme that allowed sites to provide a default rating label that was then overridden for individual pages and resources using <meta> tags and RDF-based labels. For example, Tumblr could set a family-friendly default rating and append a different rating on specific user pages, images, or ads.
An even more granular scheme could be applied via HTML attributes which would allow an individual section, image, link, or text snippet to be marked e.g. as "sexual", "violent", "substance use", "spoiler", or even "unknown" for unreviewed user-provided content. Then leave it up to web browsers to choose whether and how to render elements with these attributes. (Hidden entirely? With censor bars? Pixelated?)
There would be substantial logistical and regulatory challenges to get websites to comply, but it doesn't seem substantially harder than the current age verification schemes.
The solution is obvious: you show it on the front page if the user is 18+. However, your proposal deliberately forbids this and says the front page must be the same for everyone. Which leaves the other two bad options.
Without any requirement for verification, it'll be completely up to the parents to decide what their child will see, while the services will only get the minimum information needed. It'll basically make parental control easy, but still in the parent's control.
I don't understand why you think this is true when I specifically described a label that is applied to "an individual section" of the page.
To be more explicit: Today, each post on the Reddit front page appears in its own container element. If an 18+ post's container element could have some kind of "adult-content" attribute set then some web browsers could render the whole front page normally with the exception of that individual element. Perhaps they could black it out, collapse it, display it with a pixelated overlay and a "Request Access" button, whatever the browser supports and the device administrator prefers.
> The solution is obvious: you show it on the front page if the user is 18+. However, your proposal deliberately forbids this and says the front page must be the same for everyone.
Why do you think that my proposal requires that the front page must be the same for everyone? Providing different views to different users is the entire point of every child safety law and rating scheme I've ever seen. I'm merely saying that my preferred approach would be to mandate that potentially objectionable content is semantically annotated in the HTML somehow, so that each user's browser can apply whatever view restrictions (if any) the device's owner wishes. I think this is better than mandating that web browsers send personal information to every web site they visit and also mandating that sites pre-filter the content they send back.
First, leaking a device's content filtering settings is not the same as leaking a user's age bracket. For example, if the server identifies a web browser that isn't loading tags annotated with "sexual-content" that might indicate that the user is a child but could equally well indicate that they're a corporate office worker, religious, or anyone else who prefers not to see such content at the moment.
Second, if the standard defined multiple semantic tags or levels (e.g. violence, extreme violence, substance use, unknown, etc) then this gives more granular control to device administrators who may care more about some types of content than others.
Third, web browsers wouldn't even have to leak the content filtering settings. For example, perhaps an administrator could configure the web browser to render content overlaid with a semi-opaque blur, in which case the server would not know.
Fourth, and this is more philosophical, asking websites to provide more information to the device so that an admin can do their own filtering leaves the choices to them. Whereas if the only way a device admin can filter content is to submit the age of the device's user to a third party so the third party can decide how to pre-filter the content it sends back, that gives an uncomfortable amount of control to platforms and regulators.
A parent can change the setting in the OS and have every website and app comply with the OS setting is such a better situation than having to deal with a patchwork of content blockers, social media account settings, and parental controls that leak like a sieve.
Realistically, parents often don’t really have a good way to know what websites and apps you sign up for if you don’t have a crazily locked down device. Parental controls are complicated for non-technical parents and they usually know less than their kids do about the Internet.
A global OS age gate solves a lot of those problems, especially since OS-level controls are way easier to enforce and lock down compared to other methods.
But the objective of these regulations aren't what it says on the tin.
Also, the browser flag that indicates no consent already exists: https://globalprivacycontrol.org/faq
Glad it is now in place.
My family and school failed to stop me getting my hands on booze, fags, drugs, and porn. Teenagers are fundamentally not controllable. The Amish and the Mormons are having some success, but that's likely not what libertarians want to hear.
What you describe is the status quo. Parents and schools are already, variously, giving The Talk, confiscating devices, enabling internet filters. Society deems these measures ineffective. In tiny part, that's a skill issue, but mostly it's just trying to cut down a tree with a herring. Again: teenagers.
You may, of course, sulk about age restrictions on alcohol. Prohibitionists would like that. Keep your out of the contested zone, make them look reasonable.
If you want to stand on your principles, try seasteading. But I'd appreciate coherent contributions to the debate, to offset the excesses of the pearl-clutchers and the spies.
https://matduggan.com/you-know-gdpr-is-good-based-on-who-hat...
I hold values which lead to conflicting views and opinions, which i therefore hold lightly and attempt to balance. No action or inaction is a perfect solution to a wicked problem.
- yes, people should be free to do whatever they want with their computers - yes, people should have the freedom to exercise their independent choices - unfortunately, there is no such thing as independent choice (unless, maybe, you were already living as a hermit) - it is ostrichism to pretend that zuckerberg (to use him as shorthand) has not unilaterally and unaccountably engineered society to his own ends - society has shown considerable appetite to rein him (etc) in, for legitimate reasons - i do not, generally, support banning harmful things when stakeholders exist who favour those things - i also do not think that the existence of stakeholders who benefit should excuse all harm - therefore, this ugly compromise is approximately no worse than the least bad course of action or inaction
Things are shit. We are in shit. For all of history, we have always been in some or other grade of shit. We can sometimes choose between different piles of shit, but "not being in shit" is not an option. I find horseshit less objectionable than catshit, and so do many others; so here we are, actively jumping into horseshit.
Which OS is better for gaming? Windows or Linux?
A: Linux, because you can't play League of Legends
Or to things that we need, like medical care, government interactions, and financial services.
People shouldn't have to choose between safety features like those in Graphene OS and participation in society.
I wonder how feasible is it to use a separate phone and access it remotely from the main phone.
Think of the children!
• 2012: <https://memex.craphound.com/2012/01/10/lockdown-the-coming-w...>
• 2003: <https://www.fourmilab.ch/documents/digital-imprimatur/>
• 1997: <https://www.gnu.org/philosophy/right-to-read.html.en>
Then we decided we should punish ourselves rather than expect/require big business make safe products.
Oh no! Anyways…
excellent! won't have to worry about my kids wanting a FB account -- it just won't be accessible