

CC is “creative cloud” its the Adobe cloud-ified software offering. All the software you used to love, with fewer features and a monthly rate!


CC is “creative cloud” its the Adobe cloud-ified software offering. All the software you used to love, with fewer features and a monthly rate!


I think that’s possible


Immich is not like Lightroom at all.
Immich is more akin to Google Photos or Apple Photos. It’s a library ONLY. Lightroom is for developing raws, publishing, and storing.


what zener_diode said.
when i was setting up this version of my homelab (this is v2), i had to contend with how to run docker. The general concensus is that the “best” way to run it is Proxmox>VM>Docker. Proxmox>LXC>Docker is supposed to be viable too. Proxmox>Docker is possible but is not recommend.
I have 20 active docker services with about 30 containers running all sorts of services and they’re extremely reliable under this setup. The only time I’ve had problems is when I ran out of disk space (128gb) because stale docker images weren’t pruned.


I haven’t documented this yet but I did do Google Takeout. It is just as bad and they rotate credentials every few minutes so they make it really hard to download the 80 files they output my pictures into
Immich has built-in tooling to handle Takeout, bless them
I don’t care one bit about all of the supposed performance optimizations in CachyOS.
It is SO DANG EASY. It just works.
Hardware: I have a custom setup with a bunch of amd graphics cards. I will do a writeup about that sometime this year.
I use opencode exclusively. It’s probably not the best harness but it’s the one that gives users the most control and I like that.
The actual models I used for this work are Qwen3.8 27b - FP8 and Qwen3.8 - Flash - Next UD_Q6_K.
I wrote my own agents with duty separation. Flash is the orchestrator and long-horizon guide. While 27b is the faster, more expandable worker. This combination feels about as smart as an opus 4.8 with maybe not as great token efficiency. For simple tasks, i use the worker directly. I have a ton of repo documentation and my agents have access to read and write to Forgejo, both for git and api (issues and PRs respectively)
Maybe I need to write an article about this…