The parental controls on Nintendo Switch are a joke. Barely any options to be useful.
For example, try blocking a specific app, like YouTube.
I think that's one a the biggest problems, when a company adds parental controls. It's usually minimal effort. Just enough so they can say "see, we give parents control". It's a PR move.
More than doing the bare minimum as a PR move I think it just has to do with such options being of limited practicality. No amount of that kind of tinker knob beats the effectiveness and manageability of requiring approval to download anything, which the Switch does support.
Two game controller companies. Garvis (1998) & Mad Catz (2004)
My Gravis Xterminator's cable was coming out of the controller body. They shipped me a new one, and the box came with a return label. All free of charge.
My Mad Catz PS2 controller's tumbsticks had some stick-drift. They wouldn't replace the whole unit (out of warranty?) but did send me replacement parts for free. The rep. said they'd sent almost any replacement part for free.
I've always found it oxymoronic that "adult words" or "mature humor" are established when we are in our [pre]teens. These things typically don't have origins after coming-of-age.
I'd like to see some general best practices/architecture. Something that would fit a large range of web applications, not just the one I'm making.
For context, below are some details of what I plan to make.
This web application will have:
- user provided content
- login/sign-up
- email notifications (sign-up, user comments, etc)
- limited number of users at the beginning (less than 100 per day). But I want it architected in a way that allows me to scale up when the time comes.
- Standard web application security patterns
- Standard web application performance patterns (load balancers, containers, CDNs, etc)
- Secrets will be stored in Vault (or similar)
My planned full-stack is:
- Vue
- Vuetify
- PWA
- SSR
- Apollo GraphQL + Hasura + PostgreSQL
- Node or Python
