@onelikeandidie@mastodon.social @icing@chaos.social Is that a serious question? .expect() is just equivalent to C's abort if things don't go your way. Pretty decent for fatal errors, bad if misused, like here.
Replying to
Remote
javalsai
@javalsai@mastodon.social
mastodon 4.8.0-nightly.2026-10-060 Followers
0 Following
7 Posts
Joined November 21, 2024
Website:
GitHub:
Replying to
@lbky@chaos.social @nixCraft@mastodon.social @kobold@orthographieanarchist.de
The fact that is optional doesn't make this any better and I'm sick of this argument, it would be filled with false data anyways. I'll play devil's advocate and imagine if they added a "sex"/"gender" field so some random sexist region in the world could legislate computer use for women. Would making such field optional improve the situation the slightest? Or would it still be complying with authoritarian measures that nobody wants to give room for?
Replying to
@lbky@chaos.social @nixCraft@mastodon.social @kobold@orthographieanarchist.de
I don't care if it's optional, it still aims for age verification and I don't want that to even be possible in an OS. All this does is make further surveillance even easier because if most distros become able to support age detection nothing is stopping apps and governments to enforce the use of such field.
Replying to
@lbky@chaos.social @nixCraft@mastodon.social @kobold@orthographieanarchist.de I don't want a technical solution to the social problem but this PR is clearly a step towards justifying the social problem, and that's what I dislike. Nothing is stopping enforcement yet I don't wish to make such enforcement easier.
The same "but a program can already indirectly read this information" is already true for a lot of stuff, like reading passwords or your national ID from browser cache but it's not a reason to design a default API for it.
Replying to
@lbky@chaos.social @nixCraft@mastodon.social @kobold@orthographieanarchist.de I basically agree with the argument given there, but I draw the line before age information.
For certain other PII there's no legitimate use.
I think it's just a matter of coming up with a reason and washing complaints off under it being optional.
But adding that information as first-class PII is only going to lead to misuse, the OS shouldn't be responsible of patental controls or any other reason. That should be tracked by the program that uses it.
Replying to
@nixCraft@mastodon.social I have gigabytes of logs of my personal website and it was growing insanely fast at around march (?) of this year. I remember seeing like 3 lines appear per second with some random AI bot user agent.
Soon after using the no-ai robots.txt I started getting less AI user-agents and more "browser-like" ones, but the total traffic didn't seem to change much.
That said, I haven't been getting notable traffic for around 2 months judging by logs size. One day I'll graph all of this out.
Replying to
@nixCraft@mastodon.social Technically relying on cloudflare's and google's dns. I personally like the simplicity of curl myip.wtf/text, even if 3rd party.
Nevermind, my eyes skipped the second part.