

Doesnt always work like that.
Usually a lurker.
Maybe I should’ve just shut up and thought for a bit longer before writing that comment…
If you want to talk to me elsewhere, you know how to reach me.
Doesnt always work like that.
What bothers me is all these testers assume you are a USB hardware wizard and know which pin combo supports which USB standard.
The CaberQ can do exactly that.
Juat as a reality check:
What you and me consider fun isnt fun for most outside of the lemmy techie bubble.
At least not as persistent as RAM-DIMMs and PCIe
To solve the issue of identifying the capabilities of the cable: CaberQ.
Though a bit expensive for what it is.
It’s a Sci-fi space opera.
Literally. No point in it being hyper realistic
Sry morning brain fart. Read it’s ubuntu based
Isnt Raspberry PIOS debian based?
Even better
Yep, all you need are docker-compose.yml
, hwaccel.ml.yml
, hwaccel.transcoding.yml
and the .env
file.
And moat of that is copy pasting the template and adjusting (sticking the version number, choosing GPU/ML accelerator, etc.) ig
Looks like much but it’s basically copy pasting the base compose and adjusting for your current infrastructure.
The actual work comes with ingesting the data.
This is a JRPG an A-JRPG
Yeah in that use case syncthing fits more than immich.
In theory you probably could use immich.
During a phone replacement you pause immich sync, use syncthing to transfer the pictures and then enable immich sync again.
I believe immich should be able to detect those “new” pictures as duplicates and not upload it again.
In theory you can do that.
It just doesnt redownload to (usually) DCIM.
But say you upload your DCIM folder to immich, they are both on-device and on your server.
Until you delete them on the phone.
Neat!
I am already using a selective sync for my emulator save data between my NAS, PC and steamdeck in a triangle sync and on top another sync for the data I generate on my phone.
Doesnt work during an RMA.
After that: Yeah, sure.
And how much does Apple like that?
They explicitly mention in the deployment steps to pin the release number.
After that it’s just a case of reading the patch notes and looking out for breaking changes.
And obviously keeping backups :)
Maybe the point is to find your own meaning of life.
Like my reason to continue may be different than yours (once found)