Phloto for My Photo Flow

cceckman.com

43 points·evakhoury··7 comments

I also wrote some houseplant programming for my photo flow, which incidentally also includes Darktable [0].

As part of this, I vibe coded a script using AI to suggest captions and categories for photo uploads to Wikimedia Commons [1].

I also have my own image viewer [2].

[0] https://github.com/dllu/pupphoto

[1] https://daniel.lawrence.lu/blog/2026-03-25-uploading-to-wiki...

[2] https://daniel.lawrence.lu/blog/2025-10-22-sriv-simple-rust-...

Absolutely love your line-scanned trains. Hope that is still going swell.

Photo Mechanic is often what photographers graduate to in terms of ingestion and culling speed.

Fast ingest. Fast selection.Edit metadata as needed in bulk. The. You import for editing in Lightroom or editor of your choice.

It’s a lot less horsepower to bring in your 7 selected photographs in for editing than an entire take.

Photo Mechanic fell by the wayside for me - it's gotten a lot slower on startup and even quitting. I loved it, but I moved on to FastRawViewer.

On a side note, what is your take on AVIF vs WebP? I recently moved my site to 11ty and looking to re-encode several hundreds of images. I do want to keep the quality of the photos as much as I can, while reducing the network load.

WebP is pretty much equal to JPEGs via jpegli (for lossy compression). AVIF is better than WebP and jpegli JPEGs for lossy compression and supported pretty much everywhere now. AVIF is worse than WebP for lossless compression.

jpegli JPEGs will convert to lossy JPEG XL without generation loss when JPEG XL is more well supported.

This really reminds me of Damselfly: https://github.com/Webreaper/Damselfly

Reply on news.ycombinator.com