“At the end of the day, does it really matter much if the start of the next ice age is 50, 100, or 200 thousand years into the future?” Ridgwell said in a press statement. “We need to focus now on limiting ongoing warming. That the Earth will naturally cool back down is not going to happen fast enough to help us out.”
The work and context may be interesting, but this is the only paragraph you need to recognize from this article.
This worked pretty well for me, although constructing the cli command took a little elbow grease. This video proved to be very helpful.
Here’s the commands I ended up using:
Before performing the actual upload, test the process with this command:
immich-go.exe -server http://[server.ip:port} -key [put your apikey here w/o brackets} upload -dry-run -google-photos takout-*.zip
Once testing is successful, perform the full upload:
immich-go.exe -server http://[server.ip:port} -key [put your apikey here w/o brackets} upload -google-photos takout-*.zip
If you’ve previously uploaded photos before syncing your phone, remove duplicates with:
immich-go.exe -server http://[server.ip:port} -key [apikey} duplicate -yes
Lower overhead
Sorry, it’s a bit early in my day, but I’m interested.
Could you elaborate on how tailscale acts as an access gate?
How is the balance between security and convenience when using tailscale?
(Full disclosure, I’m an idiot, but willing to learn)
I’m in no way an authority on the subject, but RejectConvenience does a great job of examining this topic succinctly in this video.