▲ | Immich mobile app sync V2(immich.app) | ||||||||||||||||||||||||||||||||||||||||
65 points by bo0tzz 8 hours ago | 12 comments | |||||||||||||||||||||||||||||||||||||||||
▲ | pentagrama 43 minutes ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||
I really appreciate the work behind Immich and how solid the product already is. Personally, I don’t want cloud sync/storage, but I understand it’s a need for many users. What I hope is that a fully local mode can be considered in the future. For me, the goal is simply to have a great photo management app. Google Photos, for example, limits functionality if you don’t use their cloud and pushes you toward paid storage. That’s where Immich has a opportunity to shine. | |||||||||||||||||||||||||||||||||||||||||
▲ | dpcx 8 hours ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||
This will be great. I only noticed two issues with the mobile app, and one of them had to do with performance - it would get "stuck" uploading an image to the server, and no amount of waiting would let it complete. So I'd have to restart the app, and it would always start over and check every image that was in the library before uploading would begin again. The second issue is still related to timestamps from iCloud photos. The date that's on the photo in iCloud is not respected when uploading to Immich, meaning photos tagged from 40-90 years ago show up as being taken today. | |||||||||||||||||||||||||||||||||||||||||
▲ | mijoharas 7 hours ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||
I was just looking into Immich the other day. Would people recommend it? | |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||
▲ | wakawaka28 2 hours ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||
The app needs a search bug fix. If you search by "Description" in the app, it always shows no results. "Context" kind of handles some of the descriptive search features but this should be an easy fix. | |||||||||||||||||||||||||||||||||||||||||
▲ | skeptrune 7 hours ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||
Huge win! Excited for better perf | |||||||||||||||||||||||||||||||||||||||||
▲ | jauntywundrkind 6 hours ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||
Nice: > Having just migrated to Kysely from TypeORM, we were already seeing massive improvements with regard to speed and memory usage in other parts of the application as we migrated queries to use the streaming interface (see #16600, #16666, #16700, #16706, etc.). I would generally suggest folks look at something like ElectricSQL Postgres Sync Engine. There's a pretty good ShapeStream HTTP API for shipping shape logs across to the client. It can do so much of the heavy lifting for shipping updates for you, & will be reliable! https://electric-sql.com/docs/api/clients/typescript#shapest... ElectricSQL are also authors of pglite, a wasm postgres, for running a sync-ed to mini postgres on the client (via wasm). https://news.ycombinator.com/item?id=37584049 https://news.ycombinator.com/item?id=41224689 |