spectrums_coherence

For people who are not aware, “Yao-Shun-Yu” are the first three (half-mythical) kings of China. They are famous for their altruism and kindness.

At this point, I am not even sure naming robots after human rulers is dystopian or not.

Login keyring should automatically unlock upon first user login after boot, maybe you want to see if it is there, and troubleshoot that.

Possible reason that the login keyring is locked is: automatic login by bypassing password, or fingerprint login (only the first login, after that, unlock suspended machine should be fine) both will not unlock your login keyring.

If you need to keep these login, which I honestly don’t recommend (for a general purpose computer), then you can either

1. delete the login keyring password (by setting it to empty in gnome password and keys or keyrack)
2. set the electron password store to basic.

Both of these will store your password and sensitive information in plain text, meaning all program with access to your user space will have unrestricted access to these informations.

But on the third hand,

I know an AI comment when I see one /jk

Seems like this one still exists https://github.com/flatpak/xdg-desktop-portal/pull/1922

The good side: I feel it might enables me to better setup parental control in the future. If software read from the age field, then the blocking can be more robust than a simple DNS sink hole by pihole, which is really easy to get around, with mobile data or directly visiting IP address.

I do find this field is fundamentally different from verification using government issued ID (yet). I will definitely fight the next one, but I am kind of okay with this one.

Cons: it is additional fingerprint parameter, I hope the xdg-desktop protocol can be implemented to give out as little information as possible for the age field, instead of just handing the birthday field to every app that ask for it. And I hope all adult who don’t have any age-based content filtering needs will opt to leave the field empty.

I think the law in Brazil have already come into effect at the time of the merge. So it is not really compliance in advance.

• https://reclaimthenet.org/brazil-digital-eca-age-verification-law
• https://github.com/systemd/systemd/pull/40954#pullrequestreview-3971009945

It is optional field and can be unset and set to arbitrary value by the administrator. If you can build your own OS, isn’t it easier to just unset this value?