It’s remarkable that the software and service are still going, despite strong recommendations to prefer https://en.wikipedia.org/wiki/Spanner_(database) for most use-cases.
Open implementations are HBase and Cassandra. The pattern of log-structured merge trees is well worth a closer look if you’re not familiar: https://en.wikipedia.org/wiki/Log-structured_merge-tree
i'm a tiny bit worried on the backup side of self-hosting. like, it's probably fine when stuff is on the phone locally + on the vps, but older files will be just on the vps, single point of failure. I don't rly have a NAS or something else set up (yet?)
It's a bit of an orthogonal question to photos specifically, but it influences my choice
photos from my android phone are automatically uploaded to google photos (i imagine a common setup). for me it's useful as a means of backup, and the ability to view/sort through them on my desktop afterwards. i like that i don't have to think about it.
however, lately i do have to think about it bc my free 17 GB ran out. i would honestly even pay, but google literally doesn't let me with my russian account.
does anyone know good low effort alternatives? i could even self host on a vps i guess
@dalias @ilumium There's two reasons for why that can happen:
1. The actual house numbers aren't in OpenStreetMap/the underlying data yet.
2. Our search for addresses can indeed be a bit flaky when it comes to full US addresses unfortunately, e.g. https://codeberg.org/comaps/comaps/issues/4383 and https://codeberg.org/comaps/comaps/issues/854
@m0bi Prawdopodobnie zadziałałoby, ale tylko na płaskich, niezadrzewionych przestrzeniach, gdzie wiatry przy ziemi odpowiednio się rozpędzają. Nawet zakrzewiony teren będzie dość mocno hamował wiatr i nic z tego nie wyjdzie
