Hacker Newsnew | past | comments | ask | show | jobs | submit | mceachen's commentslogin

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.


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.

You're absolutely right—sqlite-vec currently only supports brute-force search, and its latency does scale linearly with dataset size. We did some rough comparisons using its benchmark tools: on the SIFT dataset, latency was around 100ms; on GIST, it was closer to 1000ms. In contrast, with zvec's HNSW implementation, we get ~1ms latency on SIFT and ~3ms on GIST, while achieving recall@100 of 99.9% on SIFT and 97.7% on GIST.

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

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.


Thanks for that link. Great starting point for me.


YMMV but TFA page content body didn’t render for me until I disabled my local pihole.


Firefox reader mode also helps


The big value to me as a BART/Caltrain rider was the ability to avoid traffic and avoid parking hassles within SF. In SOMA, at least, street parking is mostly metered 4 hours max, and private parking is $30-60/day.


@dang please retitle with (2018)


Followed by “where is the back button.”

Answer: sometimes apps let you swipe right from the left margin, sometimes there may be a left arrow in the upper left, but it may not be visible unless you enable tinted Liquid Glass, but also look in the bottom left, there may be a less-than sign, and some times you have to force-quit the app and restart (like with Libby books borrowed via Kindle…)


You mean the “roulette-wheel do-something-vaguely-backish” button?


I can't remember the last time I've encountered an app that didn't let you swipe to go back. That's practically built into iOS at this point.


Does apply still sometimes put the back button in the top left?

That used to drive me nuts especially as they grew the phone to size 5+ inches


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: