It's much worse than it used to be. Before it was only really a problem with apps with a lot of menus, and you could access the items by switching to an app with fewer of them. Now, the notch takes up a lot of space, and you hit it really soon on a 14" display—I can only have maybe three third party menu applets on top of my collection of built-in ones before they disappear into the notch.
I think it's not just the notch, but that menu bar icons are more widely spaced than they used to be. I want to say it happened around Sonoma (10.14)? I was working on a Mac app at the time. Icon styles went from dense with a generally square clickable area to widely spaced, wide rectangular clickable area, and a highlight with rounded corners when clicked.
I have a 16 inch and even I moved to the “no notch” resolution last year because a ton of apps don’t let you choose whether to have a menu icon, and many of them are required corporate crapware. Apple should have bought Bartender and made it part of the OS 10 years ago, or at least before shipping this stupid notch. Apple’s “we know what you need better than you do” approach is so exhausting.
(Real examples, with "phish" replacing a string of 3-4 random letters)
In some ways, it's a more convincing fake URL, since even if you're used to reading the domain right-to-left, your brain wants to start from the hyphen since it's a different character following a familiar TLD. But that type of domain also seems a lot easier for spam detection rules to catch.
I think you have it the other way, the hyphen should be in a place where it can be confused with a period. E.g. foo-example.com, which at first glance mentally parses similarly to foo.example.com
This is how the scam page in OPs article is formatted, and I think it could easily fool a technical person who's tired. Precisely for the reason you touched on that when you're used to working with reverse DNS notation your eye is drawn to the last period. But hyphen and period are both used as "separators" in different contexts, so you have to be vigilant enough to override the natural instinct to chunk based on any separator.
Not too sure of the utility of this. It's not an easy sentence to remember, because while grammatical, it's nonsense—it would take some effort. So if I'm trying to memorize a static IP, setting up a DNS name is likely to be easier. And also if I'm going to be using this to memorize IPs I'd like the algorithm to be open source.
All that being said, I think it's a neat idea and a cool tool!
I didn't get that sense from the prose; it didn't have the usual LLM hallmarks to me, though I'm not enough of an expert in the space to pick up on inaccuracies/hallucinations.
The "TRAINING" visualization does seem synthetic though, the graph is a bit too "perfect" and it's odd that the generated names don't update for every step.
For me it was the prose that alarmed me. Short sentences, aggressive punctuation, desperately trying to keep you engaged. It is totally possible to ask the model to choose a different style - I think that's either the default or corresponds to tastes of the content creators
> it really makes me doubt that what is written there is actually true at all
Indeed, the whole "Ironically, switching from Apache 2.0 to AGPL irrevocably makes the project forkable" section seems misguided. Apache 2.0-licensed software is just as forkable.
The point being we can simply tell our agents to start at the rug pull point and implement the same features and bug fixes on the Apache fork referring to the AGPL implementation.
> I wanted to see if, with the assistance of modern AI, I could reproduce this work in a more concise way, from scratch, in a weekend.
I don't think it counts as recreating a project "from scratch" if the model that you're using was trained against it. Claude Opus 4.5 is aware of the stable-diffusion.cpp project and can answer some questions about it and its code-base (with mixed accuracy) with web search turned off.
The two projects have literally nothing in common. Not a line of code, not the approach, nor the design. Nothing. LLMs are not memorization machines that recall every project in the cut & paste terms you could think of.
I have had issues with resizing Quick Look windows with their rounded corners on macOS for the last several major versions, well before Tahoe. The resize cursor indicator there also doesn't seem to appear at the correct location for the actual resize handles.
Because I learned JS before ECMAScript 6 was widely supported by browsers and haven't written a ton of it targeting modern browsers. You're right that it's unnecessary.
