Once I heard the following from two Russian colleagues at works:

- Пить есть, есть нету?
- Есть есть, пить нету.

For more than a decade, I’ve been learning the language, for the art and jobs mainly, but that was quite hard to realize at the times…

Thank you! For some reason, your awesome work reminded me of Gnaar, a monster of Mental!
Particularly the one from Serious Sam 3: Before First Encounter (preview), or a female from Serious Sam 4 or Siberian Mayhem (preview) ✨

…than that prompt to get the same results…

I am sorry, but I am not sure about the same results. At all.
In case of scripts, yet - your program will always work the same it is supposed to.
In LLMs? You never know. The main idea behind it is “feedback”, and each next iteration may not match the previous.

…
- Human - But I see lxc-204 was backed-up on 2026-05-19 in the logs.
- LLM - You have a sharp eye! This was my mistake, I am sorry. There’s indeed a record that it was backed-up. Now, take another look!

You have no idea what you’re talking about, since you haven’t even read my case.
Not only that, but you don’t even share the actual source - useless.
Oh! And fudge you, too, moron. Sorry, get blocked.

Related: https://steamcommunity.com/sharedfiles/filedetails/?id=2349470260 (Portal to a New World… - Wallpaper Engine | Steam Workshop…)

Just to clarify, is it the Google Gemini logo in the bottom right?

Source (Our Motion Through Space Isn’t A Vortex, But Something Far More Interesting…)

Wonderful day!

I’ve never used the wonderful client yet, but was curious too, and checked the source code.
Evidently, it should be “person’s score”:

// ...
val personScore = personTracker.getPersonScore(targetPersonId = personId)
if (personScore != 0) {
  append(" [")
  val s = length
  append(personScore.toString())
  val e = length
  append("]")
// ...

Source: LemmyHeaderHelper.kt

We now ban every reporter Instantly who submits reports we deem AI slop. A threshold has been reached. We are effectively being DDoSed. If we could, we would charge them for this waste of our time.

We still have not seen a single valid security report done with AI help.

~ Daniel Stenberg
Source [2025]

-–

For those of you who don’t want to click into linked in, https://hackerone.com/reports/3125832 is the latest example of a invalid curl report

Source: https://news.ycombinator.com/item?id=43907751 [2025-05-06]

I am sorry, and though I appreciate Google for many miracles in my life, it seems more like:

- Google is encouraging its database developers to lean “heavily” on AI coding tools...  
+ Google is encouraging its database developers to lean “heavily” on their on-site AI coding
+ tools so that the developers got dependent on it and could not think nor operate without
+ their honored access to the LLM models Google provides for an additional fee alongside
+ the food tickets...

This is how I felt, and hence I believe the work what it should do - make you feel alive more, and make you love be alive!
Thank you for the feel… and for actually genius idea for the hole for the 3 arrows!
How it sparkles… reflecting on the warm Sun near the so blue magnificent Sea, and the wind is… in peace…

The crystal hue of paradise…
A light bluе dream…

~ Below Freezing - Bandana Cheyenna

Ineffably awesomely done! You are a miracle!

Of course, but the possibly LLM-generated article at 8ksec has no actual preview of even undisclosed proof-of-concept (PoC).
And the article is used as the main source at the Tom’s Hardware article, too.
Therefore, the question is, what is the main point of both the articles, if?:

1. No PoC preview is stated at all;
2. No LLM use is stated in the initial source (at 8ksec);
3. An explicit LLM use at 8ksec is mentioned in the Tom’s Hardware - Mythos by Anthropic;

In other words, it feels more like an ad for Mythos and Apple but based on absolutely no evidence at this point of time, and Mythos is mentioned at Tom’s Hardware article only.

I am sorry, but I didn’t see any actual exploit evidence, but just the ad “groundbreaking” Apple’s MIE and previous CVEs mentioned.

Nor there is any use of LLM/“AI” explicitly stated, too, except the article itself it refers to, which looks like LLM-written: 8ksec.io/mie-deep-dive-enabling-apps [web-archived]

Update (2026-05-17_13-09_0):
- In other words, it feels more like an ad for Mythos and Apple but based on absolutely no evidence at this point of time, and Mythos is mentioned at Tom’s Hardware article only.

The pass was audited more than the still freaking awesome KeePassXC mentioned (e.g. discussion#9921).
Also, no GUI is required, unless you meant keepassxc-cli.

More software supports pass out-of-the-box, including Git, Rclone, Docker etc., which you usually can change/proxy to a KeePass database handler like keepassxc-cli, but still.

Therefore, the KeePass specification is a marvel, too, especially for generally more convenient personal use, but Pass and GPG are just the enterprise/professional standard trusted by marvelous vendors (e.g. DigiCert).

keepassx2pass.py: imports KeepassX XML data
keepass2csv2pass.py: imports Keepass2 CSV data
keepass2pass.py: imports Keepass2 XML data

Source: https://www.passwordstore.org/

Just to clarify, how is it better than pass?: https://www.passwordstore.org/

Roger that! Thank you for being a developer and improving the ineffably magnificent world! ✨

In this case, we do relatively the same, and usually in database seeding and model factories, I believe, but personally I am more into the Laravel and Symfony, where the mentioned above PHP library is used there under the hood.

Please to stay safe!

Related: https://laravel.com/docs/13.x/eloquent-factories

A whole library, or a yet another ad for Python, sorry? Why not marvelous Perl, or any lovely PHP’s or a JavaScript faker?
Why a library in the first place?

In case of PHP (checked in v8.1)

echo date('Y-m-d', rand(strtotime('-90 years'), strtotime('-18 years')));
// 2007-07-30

And, I had a snippet for JavaScript (tested in the current Chrome’s EcmaScript).
We get the years in milliseconds, and substract from the current time.

console.log(new Date(Date.now() - 365*24*60*60*1000 * (18 + Math.random()*72)).toISOString().slice(0, 10));
// 1984-07-20

In shell even! Let’s use the common suit GNU coreutils (e.g. v9.4).
We have 90y - 18y = 72 years, that is 26,280 days or ~26,297 days (source)

$ date -d "-18 years -$(( RANDOM % 26297 )) days" -- '+%F';
# 1976-04-06

“You shouldn’t have to choose between open and secure.” The implementation backs that up. The friction is one-time for power users, but it’s a genuine obstacle for scammers and it makes opportunistic spyware installation meaningfully harder.

Source

-–

His argument: power users absorb a one-time inconvenience while vulnerable people (scam victims, children) get protected…
The pattern HN picked up immediately…

That’s the true believer pattern. The argument is ideological, so persuasion is off the table. He read the laws, decided compliance was the correct response, and went to work. Every objection the community raised went nowhere: that this enables surveillance infrastructure, that lying is trivially easy, that the laws themselves are unconstitutional overreach. He’d already accepted the law as legitimate and moved to implementation…

He hit three separate projects in one week…
He agreed entirely, writing that the approach would be “completely ineffective at preventing anyone from lying about their age.” He called it “hilariously pointless.” Then he said Arch Linux should implement it anyway because the law requires it…

The open source community has always relied on the assumption that contributors act in good faith toward user freedom. Taylor probably believes he does. The laws say collect birth dates, so he collected birth dates, and in his framing that was being helpful.

The reason to name him is the pattern. The surveillance state runs on volunteers: people who do the implementation work for free, out of genuine conviction, with no paper trail connecting them to the money that wrote the laws…

Taylor already has the resume line and knows the codebase well enough to try again. The deadline pressure only grows, the laws are real, and someone will be next. The community needs to recognize the pattern before the PR opens, not after.

Source