For nearly five years, Arturo Fuente has been fighting with dabX over the company's logo. Fuente says it's an X, dabX says it's a stick figure with a circle on top.

The post Fuente Loses dabX Trademark Appeal appeared first on halfwheel.

“thenickdude”, on Reddit:

They’re using this to detect if you have Creative Cloud already installed when you visit on their website.

When you visit https://www.adobe.com/home, they load this image using JavaScript:

https://detect-ccd.creativecloud.adobe.com/cc.png

If the DNS entry in your hosts file is present, your browser will therefore connect to their server, so they know you have Creative Cloud installed, otherwise the load fails, which they detect.

They used to just hit http://localhost:<various ports>/cc.png which connected to your Creative Cloud app directly, but then Chrome started blocking Local Network Access, so they had to do this hosts file hack instead.

(Via Thom Holwerda at OSNews.)

They didn’t have to do this, of course. In fact, quite obviously, they definitely should not be doing this. Adobe is just a third-party developer, no better, no more trusted, no more important than any other. Imagine if every piece of software on your computer added entries to your /etc/hosts file. Madness. Adobe should be ashamed of themselves. Adobe used to be a bastion of best practices for developers to follow. Now their installer/updater is indistinguishable from malware.

See also: Marc Edwards on Mastodon, and Michael Tsai.

Link: old.reddit.com/r/webdev/comments/1sb6hzk/adobe_wrote_to_my…

Jason Snell, writing at Six Colors:

Software developer Photon, whose product requires running a bunch of Macs to connect to iMessage, discovered a pretty major bug:

Every Mac has a hidden expiration date. After exactly 49 days, 17 hours, 2 minutes, and 47 seconds of continuous uptime, a 32-bit unsigned integer overflow in Apple’s XNU kernel freezes the internal TCP timestamp clock… ICMP (ping) keeps working. Everything else dies. The only fix most people know is a reboot.

The whole story is wild (albeit technical). Photon says they’re working on a fix, but really, this is something Apple should be working on.

If you keep track of time using milliseconds, and store that in an unsigned 32-bit integer, it overflows after 49 days, 17 hours, 2 minutes, and 47 seconds. That’s the bug.

I think this bug is new to Tahoe. If you look at Apple’s open-source XNU kernel code — e.g. lines 3,732 to 3,745 in tcp_subr.c — you can see that the lines assigning the time in milliseconds to a uint32_t variable were checked in just six months ago, whereas most of the file is five years old. Also, I personally ran my MacBook Pro — at the time, running MacOS 15.7.2 Sequoia — up to 91 days of uptime in January. I even mentioned that remarkable uptime in my annual report card, in praise of Apple’s software reliability. Apple’s pre-Tahoe reliability, that is.

I was hesitant to link to this at all because the original (unbylined) report from Photon is so hard to follow. It’s downright manic — over 3,500 words with 33 section headings (<h2> and <h3> tags), with no cohesive narrative. The bug, seemingly, is not that complicated. The whole write-up from Photon just screams “AI-generated slop” to me, and I thus hesitate even to link to Snell’s piece linking to it. But I think the bug is real, and my sympathy for everyone afflicted with MacOS 26 Tahoe is sincere. (And if I’m wrong about the post being AI slop and a human at Photon actually wrote this, I would suggest taking it easy with the cocaine.)

Link: sixcolors.com/link/2026/04/macs-crash-after-49-days-of…

Pam Bondi removed from DoJ, and now DoJ gets on to serious business, right?

Wow. Just, look.

The First Photos From Artemis II’s Journey Around the Moon

On Monday, four people saw something no human ever had: the far side of the moon, with their own eyes.

NASA astronauts Reid Wiseman, Victor Glover, Christina Koch, and Canadian astronaut Jeremy Hansen spent seven hours circling the moon aboard the Orion spacecraft, photographing its ancient craters and dark plains from an altitude no person had reached since Apollo.

The far side, which is permanently hidden from Earth by tidal locking, has existed until now only in robotic photographs and imagination.

The first image released is an “Earthset”: Earth itself disappearing behind the moon’s edge, photographed from the far side.

It’s the quiet inverse of the famous “Earthrise” shot from Apollo 8 in 1968. Same moment, other direction. Our entire world, going dark.

A second photograph might be even more striking. As the crew completed their flyby Monday evening, the sun passed behind the moon, and they witnessed a solar eclipse from space.

Their image shows the moon’s silhouette ringed by the sun’s corona. They are the first people to ever see that.

During the flyby, Glover described the terminator: the line between light and shadow on the lunar surface, as producing “islands of light” among deep valleys. Koch noted that young impact craters glowed unexpectedly bright against older terrain, “like pinholes in a lampshade.”

One of their targets was the Orientale basin: a 600-mile-wide crater formed 3.8 billion years ago, straddling both sides of the moon.

At their farthest point, the crew was 252,756 miles from Earth — a new record for human distance from home, surpassing Apollo 13’s unintended mark from 1970 by more than 4,100 miles.

Now on their way home, they’re scheduled to splash down in the Pacific off San Diego on Friday. The full image collection follows after that.

Images via NASA.

The post Incredible New Images From Artemis 2 Show Earth From The Dark Side of the Moon 🌘 appeared first on Moss and Fog.