It says that the parental settings (when enabled!) are just letting children do whatever they want by default:
- buying overpriced objects
- chat without any restriction online
- play without interruption for long time
I think the first one is probably the most poignant: piping children into disguised gambling addiction by default seems like a major fault. Borderline illegal, if you ask me.
It looks a lot like a phony feature "let's add a parental control, it will make people feel like we're trustworthy and bring back more revenue. And please don't disable ingame purchases by default, this is our cash cow".
We shouldn't be saying "if an individual chooses to do so, we could achieve political harmony".
At what point does the government says: twitter/X has attained a critical mass and should adhere to strict political neutrality and enforce net-neutral policies, otherwise be dismantled ?
I know, your current US government benefits from this. But in general, a government should be working towards neutrality. Otherwise this is a power grab.
Apart from very specific people, that want to manipulate masses, having such a great power over opinion by manipulating what people see should be strictly controlled.
My wife’s work WiFi is handled by a gl.inet 150 (https://www.gl-inet.com/products/gl-ar150/) which is tucked behind her desk since at least 2019. Vanilla openwrt on it, provides WiFi from an Ethernet slot in the wall.
Uptime is in years, it’s invisible and chugs along without visible power draw. All her devices connect to it, including her Cisco voip phone. It autossh to my ovh server with remote port forward for remote admin. Cost me 15€ in 2016.
Cause the codebase wasn't in my scope originally and I had to review in emergency due to a regression in production. I took the time to understand the issue at hand and why the code had to change.
To be clear, the guy moved back a Docker image from being non-root (user 1000), to reusing a root user and `exec su` into the user after doing some root things in the entrypoint.
The only issue is that when looking at the previous commit, you could see that the K8S deployment using this image wrongly changed the userId to be 1000 instead of 1001.
But since the coding guy didn't take the time to take a cursory look at why working things started to not work, he asked the LLM "I need to change the owner of some files so that they are 1001" and the LLM happily obliged by using the most convoluted way (about 100 lines of code change).
For the second time of the week this morning, I spent 45 min reviewing a merge request where the guy has no idea what he did, didn’t test, and let the llm hallucinate a very bad solution to a simple problem.
He just had to read the previous commit, which introduced the bug, and think about it for 1min.
We are creating young people that have a very limited attention span, have no incentive to think about things, and have very pleasing metrics on the dora scale. When asked what their code is doing, they just don’t know. They can’t event explain the choices they made.
Honestly I think AI is just a very very sharp knife. We’re going to regret this just like regretting the mass offshoring in the 2000s.