mceachen

Please don't conflate a volunteer effort with no expected economic gain with a very well funded company (or fleet of companies).

With the CCP's highly successful track record with subsuming other markets, Occam's razor applies to why they're doing this.

All of those phrases I've heard actively used even a decade (or two) ago. (I actually had to read your comment twice because I thought you were saying always, not never!)

"Critical path" and "long pole in tent" didn't make it into the model training data, but those were certainly also in play incessantly.

But they're all reasonably useful descriptions for common things, so I'm not surprised.

I don't know if it's universal, but your non-dominant hand may form reflected letters delightfully easily if you air-write simultaneously with your dominant hand.

If you're really wanting to do perceptual hash based deduplication, use multiple, heterogeneous hash algorithms (phash, dct hash, mean hash, ...) as it is likely that a given hash algo will happily lossily match with very very different images--but if all hashes match, you're much less likely to have false positives.

I wrote up what I do here: https://photostructure.com/guide/what-do-you-mean-by-dedupli...

More than 3 channel displays have been attempted by several companies, but I suspect they fail due to:

1) trying to convince content makers to use new custom high-gamut hardware to capture the new spot colors

2) you'd need a full video content production pipeline that can render to that color space

3) finding enough people to care enough to pay the (substantial) premium for niche production numbers.

4) Most content just doesn't warrant high gamut unless it's narrated by David Attenborough.

So, you have both a chicken and egg problem, and not that big of a TAM to warrant the struggle.

Here's how to do it with more recent versions of Hugo:

https://photostructure.com/coding/hugo-markdown-output/

(It includes the grandparent's head link suggestion, but it's not just "change .html to .md" because I'm old skool and as a wee nerd was told that URLs ending in .html or .php or whatever we're frowned on, so the above link's markdown is available by appending /index.md )

It's worse: Google added and then dropped even experimental support of jxl in 2021-2022. Several years later they adopted the rust jxl library, but have kept it behind experimental flags.

"No nukes" was Sun Microsystems lawyers' liability reduction, not a political statement.

See https://www.lawinsider.com/clause/note-on-java-support/_2 for the specific verbiage and diffs over time.

If your engineer tells you that, you're going to have a bad time.

I think you're thinking this:

If you are not embarrassed by the first version of your product, you've launched too late. -Reid Hoffman

Nope, current flagship models are very happy to make huge missteps across the whole development stack of design, planning, implementation, and testing -- but playing different models against each other can help catch more egregious issues.

This is a very recent model behavior change: for me, Opus 4.6, Gemini 3.1 Pro, and ChatGPT 5.4(ish) -- prior models and harnesses suffered much more from sycophancy.

(I still prompt some questions and reviews with "our intern suggested..." to allow models to judge the quality of the content apart from the messenger)

I've found this surprisingly effective. Higher "thinking levels" may result in more than one approach being considered, but you can also tell your LLM to do brainstorming explicitly: https://photostructure.com/coding/claude-code-replan/

I applied it to PhotoStructure more than a year ago—I think it was when I first saw this on HN?

My point is that there *is* such a thing as software that tries to respect their users. I'm not the only one.

Random crowd anecdata is still anecdata.

Since when did corporations care? Most seem to just pay their insurance premium for cyber liability and call it a day.

Yup. No noxious fumes.

Roughly:

`ssh remote "cd $src/repo ; git diff" | git apply`

(You'll need to season to taste: what to do with staged changes, how to make sure both trees are in the same HEAD, etc)

12 year old me would have sold their skateboard AND their bike to have a magic Patiently Explain Anything And Everything To Me robot instead of the mostly-impenetrable-to-my-tween-brain software engineering books I had access to in my town.

He discusses this and his sixpence wager here: https://youtu.be/pJgKYn0lcno

(Source: TFA)

No mention of auto renewal is made as far as I (and Claude) could determine.

Their OSS offer is first-hit-is-free.

At the same time, at least to me, the text reads like a transcript from one of their YouTube tear downs.

Before anyone downvotes this guy, spend some time on the official Apple support forum.

I can't point at a bug that I've seen addressed in subsequent OS releases.

Seizure-inducing HDMI flickering from Night Shift. Finder Trash not supporting put-back _sometimes_. Printers becoming permanently "paused" sporadically, or worse, very consistently. Mouse lag/stuttering because you used "the wrong USB port." Apple photos libraries corrupting themselves with no recovery paths.

It would be strictly better to just not have the forum, then shouting sorrows into the void would feel more solitary.

Currently profitable? Many are old enough to have a generic, and are close to the cost of aspirin at this point.

I suspect an LLM would read the instructions more thoroughly than a human.

So if there are only brown M&Ms greeting you in your dressing room, most likely they were put there by a robot.

FWIW "You're absolutely right" broadly declares "a human is not piloting the keyboard"

I drove a Scitex RIP (raster image processor) as my part time job in college. The CMYK (and if you were rich, N more spot colors) rotation degrees were held in religious fervor. Me: "These degrees seem random." Boss: "You are not to ever digress from those, they are the Only True Values" (and if you play with them in TFA you'll see it indeed becomes a moire mess with tiny tweaks, which would cost a ton in reprinting and delays).

It was mildly humorous that stochastic dithering (even with dot-gain compensation) was an option back in 1990, and produced much higher grade color reproductions, but clients wouldn't have any part of it, because it wasn't "the look" that I think they expect their readers expected.

I maintain a fork of sqlite-vec (because there hasn't been activity on the main repo for more than a year): sqlite-vec is great for smaller dimensionality or smaller cardinality datasets, but know that it's brute-force, and query latency scales exactly linearly. You only avoid full table scans if you add filterable columns to your vec0 table and include them in your WHERE clause. There's no probabilistic lookup algorithm in sqlite-vec.

It’s the inconsistency that gets me. Very similar tasks, similar complexity, same code base, same prompting:

Session A knocks it out of the park. Chef’s kiss.

Session B just does some random vandalism.

I wrote some tips and tricks that I've found to help coax Google Takeouts into working: https://photostructure.com/faq/takeout/

Also: you should try out the latest build! https://photostructure.com/about/v2026.1/

FWIW all of these projects rely on ExifTool (which people should donate to!) and my open-source node.js wrapper (that adds concurrency, does a ton of extra parsing work, and makes things a bit more ergonomic to live with): https://github.com/photostructure/exiftool-vendored.js

Gobsmackingly poor deals made by city and town politicians are par for the course, and why https://www.strongtowns.org/ should be prerequisite reading for any council member, mayor, or board member approving deals that impact their community.

It's easy to look at a glossy project 2-pager and only see the immediate tax revenue.

It's much harder to glean a nuanced understanding of future financial burdens from a given project. No company will have any incentive to be forthright with that information.