Blemgo

That is true. However, 2 things have to be considered here:

1. LLMs are easily manipulatable. So if the LLM says some advice, the person can easily spin it in a way where the LLM believes that its own advice doesn't apply even when it does. And admitting problems in oneself exist is harder in some people.
2. LLMs can talk like a person, but will miss out on details about the other, making their advice rather boilerplate, which can be very hit or miss.

In contrast, people can overcome both hindrances. They can either try to make the other realize the issues they are denying are going on, or coerce the other to still try the advice. Generally, our gift of reading little aspects of how the other talks/behaves helps us communicate with the other a lot more than we think.

Overall, not really, since with a competent talking partner you also would get ways to improve your situation, and help with pressing matters. It might be good in the short term, but there needs to be more to be good in the long run.

My guess would be the same phenomenon that existed with ELIZA. People want to be heard, especially lonely people, and LLMs are pretty good at that, asking questions and acting supportive, by design.

This whole situation reminds me of that fact that some people hire escorts to just have someone to talk to.

Apart from the vibe-coded stuff (though I guess that was due to it being a test run rather than something solid) this is pretty neat! I don't think anyone will really use it for competitive games (since you can't edit the levels), but I see how that would make it much easier to do virtual walkthroughs. It's cheap, relatively easy and uses a lot less resources, I imagine, than using classic rendering techniques. The environment itself reminds me a bit of the levels in SteamVR, where Valve digitised some locations for you to visit on your own.

I think another big problem that hampers the computer age in many places is bureaucracy and clinging to old structures.

For many companies there are checks that are enforced, simply because there is no trust in a new system, or the processes to be automated requires a major reorganisation that spans departments, and those departments might oppose such a restructuring, may it be for fear of their jobs, simply clinging to old processes or not having the capacity to carry out bigger projects.

And if that doesn't work, there's this method that even got awarded the 2006 Ig Nobel Price in Medicine.

That's sad to see. Granted, I haven't played Rec Room in ages, but when I still played VR it really felt like a great and safe playground for all ages. But yeah, I really often asked myself "how do they even make money?", as basically there was nothing really serious that cost money. A fear I had is that they sold my info or telemetry, but never too much.

It's nice that they chose to shutter things down rather than to enforce sustainability through scummy tactics.

I know of at least one that pretty much uses scummy tactics to keep things afloat, so it's heartwarming, although also a bit heartbreaking, to see that they would not let things go to shit and instead take the high road. Kudos to them and I wish the best for the team.

I mean, antitheists, a subgroup of atheism, are exactly that: people who are very vocal about their disdain regarding religion. And sadly often the vocal minority is seen as the majority.

I don't think that systemd is really bending the knee too hard on this one. Actually, I think this move is actually a great way to render any sort of age verification, when using systemd, inert. Because, let's think about it: it's an optional field, in a JSON file that NEEDS to be editable at all times. If a distro decides to implement any serious age verification, it will have to store the data, namely the date of birth, somewhere. The /home folder would be wrong, as the user could edit that at all times. The userdb on the other hand can be restricted, meaning that the user can only edit it with user privileges. So if a government questions the seriousness of this verification method, distros can just claim that it is the administrative duty of the parent to prevent their children accessing things they shouldn't, and that the Linux kernel itself provides the proper tool to do it without constant supervision. Yet systemd cannot enforce any stricter rules because service users, especially root, are not real people and thus cannot have any age verification. The only solution would be to tie these accounts to a person. This would cause an outrage at companies, considering that this role would most likely be the CEO or CIO, and if that device is stolen their identity could be linked to a crime, and I doubt any police station would bother trying to retrieve that laptop.

So this change will most likely be the maximum systemd can do without breaking distros for corporations, while at the same time allow classic Linux users, who most likely give themselves admin rights, a way to render any verification null and void by editing this optional field on their own.

EDIT: Also, being mad at an organisation trying to meet the laws in order to be usable will solve nothing. As you said yourself: a strong stance is needed. So complaining about systemd and trying to make them revert it will do nothing, because there will always be someone who bends the knee. If you want to do something, organize or join a protest and go to the streets, show that the law is for the people, not to be used as an oppression tool.

I mean, the introduction of the date of birth field is obviously done to make it easy for distros to comply with age verification by simply saving the birth date and nothing else.

As for the other fields: what use would it have to have such info at OS level? What application would use these fields and how? I mean, some fields, like the 'location' one, already are pretty useless, as, for example, the 'location' field doesn't seem to bhave any firm consensus on how it should be formatted. Even the documentation lists both "Berlin, Germany" as well as "Basement, Room 3a" as valid values.

So I doubt not introducing such fields has any sort of political agenda to it, but just raises the question on why such fields would be useful to begin with.

That is a valid point. Of course it still would be rather anonymised, but it could always be a 'frog in the pot' type situation, where most drastic changes are introduced very slowly. My main concern at the end of the day is how much info will be required to be given to services and how much data will be actually stored. If it's anonymised, then I don't see much of a threat. If a service requires me to fully identify for an age check, that's an entirely different thing, especially considering the last of Discord's data leaks.

I find that move extremely funny, since it's purely made for sensationalism and nothing else. I mean, if you hate how systems implemented age verification, then why don't you remove its identity verification too, i.e. also optional fields for stuff like your address an e-mail that most users don't even fill out.

There is no mechanism verifying what birth date you type in - you can type whatever date you want and systems doesn't care.

I'd say no matter where you stand with age verification, this is the best solution to handle the situation. After all, any and all age checks we have nowadays are a black box anyways. There is no real knowing how other systems are checking ages, and there is AFAIK no real government mandated rules on how it is verified. They could make you scan your ID's front, back, nuclear composition and dietary preferences and give you a result that is almost, but not quite, entirely unlike a proper age verification procedure.

If the government wants to introduce age verification, they have to do it themselves - build an API that handles the age verification, similar to how the digital ID in Germany works, as an example. If they want proper age verification, they also have to take the blame themselves if things go wrong.