Seconding this. Legitimately better than Google photos in a lot of ways, even if you don’t care about the data ownership aspect. If you’ve ever been annoyed at how Google Photos handles face detection / grouping, you’ll love Immich.
Seconding this. Legitimately better than Google photos in a lot of ways, even if you don’t care about the data ownership aspect. If you’ve ever been annoyed at how Google Photos handles face detection / grouping, you’ll love Immich.
I’d love to know what font was used for the big “Saturday” there!
Now please explain to me how C works.
That’s not what they’re asking. It’s not about how C works, it’s about how specific APIs written in C work, which is hard to figure out on your own for anyone who is not familiar with that specific code. You’ll have to explain that to any developer coming new into the project expected to work with those APIs, no matter their experience with C.
Not really. Timezones, at their core (so without DST or any other special rules), are just a constant offset that you can very easily translate back and forth between, that’s trivial as long as you remember to do it. Having lots of them doesn’t really make anything harder, as long as you can look them up somewhere. DST, leap seconds, etc., make shit complicated, because they bend, break, or overlap a single timeline to the point where suddenly you have points in time that happen twice, or that never happen, or where time runs faster or slower for a bit. That is incredibly hard to deal with consistently, much more so that just switching a simple offset you’re operating within.
So, basically cloud saves with extra steps, except you only get a single save and can’t replay the game? Sounds even worse than current solutions, honestly
Oh awesome, thank you so much!