I don’t know the Immich API, but I’ve seen several REST APIs that used the usual pattern of

GET /api/v1/user/<id> - read user
POST /api/v1/user/ - create user
...

but also allowed

GET /api/v1/user/<id> - read user
GET /api/v1/user/?action=create - create user
...

Surface are basically a tablet (=all hardware and weight in the monitor). You can get them with a cover that contains a keyboard but it is still top heavy (think of a normal cover for a tablet, but slightly more sturdy because of the keyboard).

There’s also a surface book that more or lees is like a laptop - from the looks of it. The bottom part with the keyboard is heavier, but only contains the keyboard, an USB hub and additional batteries. It’s till top heavy with it, as you can “detach the screen” and still have a fully functional “PC tablet”.

They now run Arch btw

In most jurisdictions this project wouldn’t have any problem, when it’s a “clean room” implementation - meaning they figured out by themselves how the server works.

Several jurisdictions even allow reverse engineering and such to ensure compatibility / supporting an product that hasn’t any official support anymore.

Others simply don’t care.

It’s all in the details, but they might not get sued that easily.