Jim Nielsen’s Blog

I recommended against using an AI browser unless you wanted to participate in a global experiment in security. My recommendation did come with a caveat:

But probably don’t listen to me. I’m not a security expert

Well, now the experts (that you pay for) have weighed in.

Gartner, the global research and advisory firm, has come to the conclusion that agentic browsers are too risky for most organizations.

Ground breaking research.

But honestly, credit where it’s due: they’re not jumping on the hype train. In fact, they’re advising against it.

I don’t have access to the original paper (because I’d have to pay Gartner for it), but the reporting on Gartner’s research says this:

research VP Dennis Xu, senior director analyst Evgeny Mirolyubov, and VP analyst John Watts observe “Default AI browser settings prioritize user experience over security.”

C’mon, let’s call a spade a spade: they prioritize their maker’s business model over security.

Continuing:

Gartner’s fears about the agentic capabilities of AI browser relate to their susceptibility to “indirect prompt-injection-induced rogue agent actions, inaccurate reasoning-driven erroneous agent actions, and further loss and abuse of credentials if the AI browser is deceived into autonomously navigating to a phishing website.”

And that’s just the beginning! It gets worse for large organizations.

The real horror of these AI browsers is that they can help employees to autonomously complete their mandatory trainings:

The authors also suggest that employees “might be tempted to use AI browsers and automate certain tasks that are mandatory, repetitive, and less interesting” and imagine some instructing an AI browser to complete their mandatory cybersecurity training sessions.

The horror!

In this specific case, maybe AI browsers aren’t the problem? Maybe they’re a symptom of the agonizing online instructional courses that feign training in the name of compliance?

But I digress. Ultimately, the takeaway here is:

the trio of analysts think AI browsers are just too dangerous to use

Imagine that: you take a tool that literally comes with a warning of being untrustworthy, you embed it as foundational in another tool, and now you have two tools that are untrustworthy. Who would’ve thought?

Reply via: Email · Mastodon · Bluesky

If you subscribe to this blog, you must like it — right? I mean, you are subscribed to it.

And if you like this blog, you might also like my notes blog.

It’s where I take short notes of what I read, watch, listen to, or otherwise consume, add my two cents, and fire it off into the void of the internet.

It’s sort of like a “link blog” but I’m not necessarily recommending everything I link to. It’s more of “This excerpt stood out to me in some way, here’s my thoughts on why.”

It’s nice to have a place where I can jot down a few notes, fire off my reaction, and nobody can respond to it lol. At least, not in any easy, friction-less way. You’d have to go out of your way to read my commentary, find my contact info, and fire off a message (critiquing or praising). That’s how I like it. Cuts through the noise.

Anyway, this is all a long way of saying: if you didn’t already know about my notes blog, you might like it. Check it out or subscribe.

Today, for example, I posted lots of grumpy commentary.

• https://notes.jim-nielsen.com/#2025-12-18T1130
• https://notes.jim-nielsen.com/#2025-12-18T1128
• https://notes.jim-nielsen.com/#2025-12-18T1136

Reply via: Email · Mastodon · Bluesky

My last article was blogging off Jeremey’s article which blogged off Chris’ article and, after publishing, a reader tipped me off to the Gell-Mann amnesia effect which sounds an awful lot like Chris’ “Jeopardy Phenomenon”. Here’s Wikipedia:

The Gell-Mann amnesia effect is a cognitive bias describing the tendency of individuals to critically assess media reports in a domain they are knowledgeable about, yet continue to trust reporting in other areas despite recognizing similar potential inaccuracies.

According to Wikipedia, the concept was named by Michael Crichton because of conversation he once had with physicist Murray Gell-Mann (humorously, he said by associating a famous name to the concept he could imply greater importance to it — and himself — than otherwise possible).

Here’s Crichton:

you read with exasperation or amusement the multiple errors in a story—and then turn the page to national or international affairs, and read with renewed interest as if the rest of the newspaper was somehow more accurate about far-off Palestine than it was about the story you just read. You turn the page, and forget what you know.

He argues that this effect doesn’t seem to translate to other aspects of our lives. The courts, for example, have a related concept of “false in one thing, false in everything”.

Even in ordinary life, Crichton says, “if somebody consistently exaggerates or lies to you, you soon discount everything they say”.

In other words: if your credibility takes a hit in one area, it’s gonna take a hit across the board.

At least, that’s his line of reasoning.

It’s kind of fascinating to think about this in our current moment of AI. Allow me to re-phrase Crichton.

You read with exasperation the multiple errors in AI’s “answer”, then start a new chat and read with renewed interest and faith as if the next “answer” is somehow more accurate than the last. You start a new prompt and forget what you know.

If a friend, acquaintance, or family member were to consistently exaggerate or lie to you, you’d quickly adopt a posture of discounting everything they say. But with AI — which even comes with a surgeon general’s warning, e.g. “AI can make mistakes. Check important info.” — we forgive and forget.

Forget. Maybe that’s the keyword for our behavior. It is for Crichton:

The only possible explanation for our behavior is amnesia.

Reply via: Email · Mastodon · Bluesky

Chris Coyier:

There’s the thing where if you’re reading an article in the newspaper, and it’s about stuff you don’t know a ton about, it all seems well and good. Then you read another article in the same paper and it’s about something you know intimately (your job, your neighborhood, your hobby, etc) there is a good chance you’ll be like hey! that’s not quite right!

Chris extends this idea to AI-generated code, i.e. if you don’t know or understand the generated code you probably think, “Looks good to me!” But if you do know it you probably think, “Wait a second, that’s not quite right.”

Here’s Jeremy Keith riffing on Chris’ thoughts:

I’m astounded by the cognitive dissonance displayed by people who say “I asked an LLM about {topic I’m familiar with}, and here’s all the things it got wrong” who then proceed to say “It was really useful when I asked an LLM for advice on {topic I’m not familiar with, hence why I’m asking an LLM for advice}.”

Kind of feels like this boils down to: How do we know what we know?

To be fair, that’s a question I’ve wrestled with my whole life.

And the older I get, the more and more I realize how often we barely know anything.

There’s a veneer of surety everywhere in the world.

There are industries of people and services who will take your money in exchange for a sense of surety — influencers, consultants, grifters, AI, they all exist because we are more than willing to pay with our time, attention, and money to feel like we “know” something.

“You’re absolutely right!”

But I, for one, often feel increasingly unsure of everything I thought I knew.

For example: I can’t count the number of times I thought I understood a piece of history, only to later find out that the commonly-accepted belief comes to use from a single source, written decades later in a diary or on a piece of parchment or on a stone, by someone with blind spots, questionable incentives, or a flair for the dramatic, all of which leaves me seriously questioning the veracity and objectivity of something I thought I knew.

Which leads me to the next, uncomfortable question: How many other things are there that I thought I knew but are full of uncertainty just like this?

All surety vanishes.

And that’s an uncomfortable place to be. Who wants to admit “I don’t know”?

It’s so easy to take what’s convenient over what corresponds to reality.

And that’s what scares me about AI.

Update 2025-12-16

After publishing, I was tipped off to the Gell-Mann amnesia effect which is right up the subject alley of this post.

Reply via: Email · Mastodon · Bluesky

Related posts linking here: (2025) The “A” in “AI” Stands For Amnesia

I complained about this on the socials, but I didn’t get it all out of my system. So now I write a blog post.

I’ve never liked the philosophy of “put an icon in every menu item by default”.

Google Sheets, for example, does this. Go to “File” or “Edit” or “View” and you’ll see a menu with a list of options, every single one having an icon (same thing with the right-click context menu).

It’s extra noise to me. It’s not that I think menu items should never have icons. I think they can be incredibly useful (more on that below). It’s more that I don’t like the idea of “give each menu item an icon” being the default approach.

This posture lends itself to a practice where designers have an attitude of “I need an icon to fill up this space” instead of an attitude of “Does the addition of a icon here, and the cognitive load of parsing and understanding it, help or hurt how someone would use this menu system?”

The former doesn’t require thinking. It’s just templating — they all have icons, so we need to put something there. The latter requires care and thoughtfulness for each use case and its context.

To defend my point, one of the examples I always pointed to was macOS. For the longest time, Apple’s OS-level menus seemed to avoid this default approach of sticking icons in every menu item.

That is, until macOS Tahoe shipped.

Menus in macOS Tahoe

Tahoe now has icons in menus everywhere. For example, here’s the Apple menu:

Let’s look at others. As I’m writing this I have Safari open. Let’s look at the “Safari” menu:

Hmm. Interesting. Ok so we’ve got an icon for like half the menu items. I wonder why some get icons and others don’t?

For example, the “Settings” menu item (third from the top) has an icon. But the other item in its grouping “Privacy Report” does not. I wonder why? Especially when Safari has an icon for Privacy report, like if you go to customize the toolbar you’ll see it:

Hmm. Who knows? Let’s keep going.

Let’s look at the "File" menu in Safari:

Some groupings have icons and get inset, while other groupings don’t have icons and don’t get inset. Interesting…again I wonder what the rationale is here? How do you choose? It’s not clear to me.

Let’s keep going. Let’s go to the "View" menu:

Oh boy, now we’re really in it. Some of these menu items have the notion of a toggle (indicated by the checkmark) so now you’ve got all kinds of alignment things to deal with. The visual symbols are doubling-up when there’s a toggle and an icon.

The “View” menu in Mail is a similar mix of:

• Text
• Text + toggles
• Text + icons
• Text + icons + toggles

You know what would be a fun game? Get a bunch of people in a room, show them menus where the textual labels are gone, and see who can get the most right.

But I digress.

In so many of these cases, I honestly can’t intuit why some menus have icons and others do not. What are so many of these icons affording me at the cost of extra visual and cognitive parsing? I don’t know.

To be fair, there are some menus where these visual symbols are incredibly useful. Take this menu from Finder:

The visual depiction of how those are going to align is actually incredibly useful because it’s way easier for my brain to parse the symbol and understand where the window is going to go than it is to read the text and imagine in my head what “Top Left” or “Bottom & Top” or “Quarters” will mean. But a visual symbol? I instantly get it!

Those are good icons in menus. I like those.

Apple Abandons Its Own Guidance

What I find really interesting about this change on Apple’s part is how it seemingly goes against their own previous human interface guidelines (as pointed out to me by Peter Gassner).

They have an entire section in their 2005 guidelines (and 1992 and 2020) titled “Using Symbols in Menus”:

See what it says?

There are a few standard symbols you can use to indicate additional information in menus…Don’t use other, arbitrary symbols in menus, because they add visual clutter and may confuse people.

Confused people. That’s me.

They even have an example of what not to do and guess what it looks like? A menu in macOS Tahoe.

Conclusion

It’s pretty obvious how I feel. I’m tired of all this visual noise in my menus.

And now that Apple has seemingly thrown in with the “stick an icon in every menu by default” crowd, it’s harder than ever for me to convince people otherwise. To persuade, “Hey, unless you can articulate a really good reason to add this, maybe our default posture should be no icons in menus?”

So I guess this is the world I live in now. Icons in menus. Icons in menus everywhere.

Send help.

Reply via: Email · Mastodon · Bluesky

As ever, Mandy Brown casually drops a blog post that makes you examine the everyday meaning of words:

One of the imperatives in contemporary, professional work culture is to “grow.” There is often a sense of height or largeness with that imperative, as if growth must be measured in your distance up the ladder, your territory across the way. In The Soul’s Code, James Hillman implores us to think rather of growing down, of growth not of branch but root, of becoming more grounded, sturdier, less able to be pushed around by the whims of others.

I love this idea of “growing down”, becoming more rooted and sturdy.

It got me thinking about the word “growth”.

Contemporary usage of the word in business often communicates human intervention and imposition against an otherwise natural outworking.

“Growth” in a forest is different than “growth” in business.

In business, we talk about “growth hacking” as if the natural cadence of growth isn’t sufficient. It requires modification because we deem it insufficiently slow.

We “engineer” growth instead of tending it.

Personally, when I say I want to grow, I mean like a tree. Not like a cancer.

Tree growth responds to its environment and integrates with its ecosystem. Growth is sustainable, balancing expansion and repair. It scales in harmony with its context.

Cancer growth is selfish, consuming resources at the expense of its host. Growth is uncontrolled until the system that supports it collapses. It scales through extraction until failure.

When we talk about the growth of technology in the 21st century, which kind of growth do you think best describes it?

“Hey, {social media | AI} grew so big, we all sat together under its canopy and enjoyed the shade.”

Said no one.

More likely: “Hey, {social media | AI} grew so big, it metastasized beyond what society could bear and now look at the mess we’re in.”

Reply via: Email · Mastodon · Bluesky

I wrote about the 404s I serve for robots.txt. Now it’s time to look at some of the other common 404s I serve across my static sites (as reported by Netlify’s analytics):

• /wp-login.php
• /wp-admin
• /news/wp-includes/wlwmanifest.xml
• /login/
• /wp-includes/wlwmanifest.xml
• /news/wp-includes/wlwmanifest.xml
• /website/wp-includes/wlwmanifest.xml
• /info.php

I don’t run WordPress, but as you can see I still get a lot of requests for wp-* resources.

All of my websites are basically just static files on disk, meaning only GET requests are handled (no POST, PUT, PATCH, etc.). And there’s no authentication anywhere.

So when I see these requests, I think: “Sure is nice to have a static site where I don’t have to worry about server maintenance and security patches for all those resources.”

Of course, that doesn’t mean running a static site protects me from being exploited by malicious, vulnerability-seeking traffic.

Here are a few more common requests I’m serving a 404 to:

• /.env
• /.env.production
• /.env.local
• /.env.dev
• /.git/config
• /data.sql
• /database.sql.gz
• /mysql.sql
• /db.sql.gz
• /backup.sql.gz
• /database.sql

With all the magic building and bundling we do as an industry, I can see how easy it would be to have some sensitive data in your source repo (like the ones above) end up in your build output. No wonder there are bots scanning the web for these common files!

So be careful out there. Just because you’ve got a static site doesn’t mean you’ve got no security concerns. Fewer, perhaps, but not none.

Reply via: Email · Mastodon · Bluesky

Patrick Collison, CEO of Stripe, interviewed Jony Ive at Stripe Sessions. Below are my notes from watching the interview. I thought about packaging these up into a more coherent narrative, but I just don’t have the interest. However, I do want to keep these notes for possible reference later, so here’s my brain dump in a more raw form.

On moving fast and breaking things:

breaking stuff and moving on quickly leaves us surrounded by carnage.

There’s an intriguing part in the interview where Ive reflects on how he obsessed over a particular detail about a cable’s packaging. He laughs at the story, almost seemingly embarrassed, because it seems so trivial to care about such a detail when he says it out loud.

But Collison pushes him on it, saying there’s probably a utilitarian argument about how if you spend more time making the packaging right, some people mights save seconds of time and when you multiply that across millions of people, that's a lot of savings. But Collison presumes Ive isn’t interested in that argument — the numbers, the calculation, etc. — so there must be something almost spiritual about investing in something so trivial. Ive’s response:

I believe that when somebody unwrapped that box and took out that cable, they thought “Somebody gave a shit about me.”

I think that’s a nice sentiment. I do.

But I also think there’s a counter argument here of: “They cared when they didn’t have to, but they were getting paid to spend their time that way. And now those who can pay for the result of that time spent get to have the feeling of being cared for.”

Maybe that’s too cynical. Maybe what I’m getting at is: if you want to experience something beautiful, spend time giving a shit about people when you don’t stand to profit from it.

To be fair, I think Ive hints at this with his use of “privilege” here:

I think it’s a privilege if we get to practice and express our concern and care for one another [by making things for one another at work]

People say products are a reflection of an organization’s communication structure.

Ive argues that products are a function of the interpersonal relationships of those who make them:

To be joyful and optimistic and hopeful in our practice, and to be that way in how we relate to each other and our colleagues, [is] how the products will end up.

Ive talking about how his team practiced taking their design studio to someone’s house and doing their work there for a day:

[Who] would actually want to spend time in a conference room? I can’t think of a more soulless and depressing place…if you’re designing for people and you’re in someone’s living room, sitting on their sofa or floor and your sketchbook is on their coffee table, of course you think differently. Of course your preoccupation, where your mind wanders, is so different than if you’re sitting in a typical corporate conference room.

Everybody return to the office!

Ive conveying an idea he holds that he can’t back up:

I do believe, and I wish that I had empirical evidence

What is the place for belief in making software?

Ive speaks about how cabinet makers who care will finish the inside parts of the cabinet even if nobody sees them:

A mark of how evolved we are as people is what we do when no one sees. It’s a powerful marker of who we truly are.

If you only care about what's on the surface, then you are, by definition, superficial.

Reply via: Email · Mastodon · Bluesky

The data is in.

The number one requested resource on my blog which doesn’t exist is:

/robots.txt

According to Netlify’s analytics, that resources was requested 15,553 times over the last thirty days.

Same story for other personal projects I manage:

• iOS Icon Gallery: 18,531 requests.
• macOS Icon Gallery 10,565 requests.

“That many requests and it serves a 404? Damn Jim, you better fix that quick!”

Nah, I’m good.

Why fix it? I have very little faith that the people who I want most to respect what’s in that file are not going to do so.

So for now, I’m good serving a 404 for robots.txt.

Change my mind.

Reply via: Email · Mastodon · Bluesky

Related posts linking here: (2025) Malicious Traffic and Static Sites

I enjoyed listening to Feross Aboukhadijeh, founder and CEO of the security firm Socket, on the Changelog podcast “npm under siege”. The cat-and-mouse nature of security is a kind of infinite source of novel content, like a series of heist movies that never produces the same plot so you can never quite guess what happens next.

I like how succintly Feross points out the paradox of trying to keep your software safe by upgrading packages on npm:

The faster you upgrade your packages, the safer you are from software vulnerabilities. But then the faster you upgrade the more vulnerable you are to supply chain attacks

He points out (and I learned) that pnpm has a feature called minimumReleaseAge that lets you avoid installing anything super new. So you can, for example, specify: “Don’t install anything published in the last 24 hours.”

In other words: let’s slow down a bit. Maybe we don’t need immediacy in everything, including software updates. Maybe a little friction is good.

And if security vulnerabilities are what it took to drive us to this realization, perhaps it’s a blessing in disguise.

(Until the long running cat-and-mouse game of security brings us a bad actor who decides to exercise a little patience and creates some kind of vulnerability whose only recourse requires immediate upgrades and disabling the minimumRelaseAge flag, lol.)

Later in the podcast Feross is asked whether, if he was the benevolent dictator of npm, he would do things the same. He says “yes”. Why? Because the trade-offs of “trust most people to do the right thing and make it easy for them” feels like the better decision over “lock it down and make it harder for everyone”. He’s a self proclaimed optimist:

There’s so much good created when you just trust people and you hope for the best.

Obviously Feross has an entire business based on the vulnerabilities of npm, so his incentives are such that if he did change things, he might not exist ha. So read that how you will.

But I like his optimistic perspective: try not to let a few bad actors ruin the experience for everyone. Maybe we can keep the levers where they are and try to clean up what remains.

Reply via: Email · Mastodon · Bluesky