madjo

That sounds like a great solution to my current frustration that the autobackup feature of Immich on iOS is so opaque. It only works when the app is open and even then oftentimes you’re just staring at the backup screen while seemingly nothing is happening, despite Immich’s backlog of thousands of photos still needing to be uploaded.

Half Life 3 takes place on open sea.

Valve just casually changing the entire PC gaming landscape on a Wednesday…

Yeah, they’re mostly centrist, somewhat left of center, but they’re far from socialist, let alone communist.

+1 for ProxMox.

I have that running and it’s pretty easy to work with

It’s a bit strange that when you create a note, you don’t automatically go to the editor.

I don’t mind those people, I just wish they wouldn’t go off on tangentially related subjects.

I tried to open it up, but one of the screws refuses to be removed, I’m looking for the least destructive method to remove it :)

It’s the only thing I could think of. One day it was working fine, I hooked it up to a charger (grabbed the wrong wire, not the official one, but a 5v one), and the next day, the screen didn’t turn on anymore, but the Deck itself still works, when I attach it to a screen.

That’s an amazing deal!

My steam deck’s screen has sadly stopped working, I think it’s because I used a wrong charger. The deck itself works fine, but only with an external screen.

the app version is also 2.0.0 on iOS, upgraded from the previous version.

So this isn’t a database issue on the server? But one in the app?

Apparently I have a database issue. It tries two photos and both fail with a foreign key error and then the process stops. I had deleted both photos it initially complained about, but then it complained about the next two. I fear I’m going to have to reinstall.

Went into the app’s logs (tap your icon in the upper right corner and choose Logs)

And in my case it’s a database issue:

SqliteException(787): while executing statement, FOREIGN KEY constraint failed, constraint failed (code 787) Causing statement: INSERT INTO “remote_exif_entity” (“asset_id”, “city”, “state”, “country”, “date_time_original”, “description”, “height”, “width”, “exposure_time”, “f_number”, “file_size”, “focal_length”, “latitude”, “longitude”, “iso”, “make”, “model”, “lens”, “orientation”, “time_zone”, “rating”, “projection_type”) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ON CONFLICT(“asset_id”) DO UPDATE SET “city” = ?, “state” = ?, “country” = ?, “date_time_original” = ?, “description” = ?, “height” = ?, “width” = ?, “exposure_time” = ?, “f_number” = ?, “file_size” = ?, “focal_length” = ?, “latitude” = ?, “longitude” = ?, “iso” = ?, “make” = ?, “model” = ?, “lens” = ?, “orientation” = ?, “time_zone” = ?, “rating” = ?, “projection_type” = ?, parameters: ffc547f5-78ad-42b9-856b-fdd9df8f6586, placename, state, country, 2025-05-24T14:43:35.000Z, , 1440, 1920, null, null, 3850688, null, 00.0000, 00.0000, null, Apple, iPhone 16 Pro, null, 1, Europe/Brussels, null, null, placename, state, country, 2025-05-24T14:43:35.000Z, , 1440, 1920, null, null, 3850688, null, 00.0000, 00.0000, null, Apple, iPhone 16 Pro, null, 1, Europe/Brussels, null, null.

(redacted lat/long positions a bit)

I think I’m going to reinstall. This issue is over my paygrade.

Ever since the upgrade to 2.0 I’ve been unable to sync the photos on my phone. “Sync failed, cannot process backup” and I don’t know why.

Upvote for the verbification of Kagi :)

Payment processors should be following the most free speech laws there are, because they have de facto monopolies. If they do have a choice though, if they don’t want to support porn, then they could choose not to be a payment processor.

Ideally they should be nationalised, or perhaps internationalised.

Payment providers are run by fuckin’ puritans…

That’s still a lot more people than I expected. I would’ve guessed 1 in 300

What is the use case for it?

Sure, but I’m not touching anything Sony with a 10 foot pole.