Auto-translate is saying ‘snap knife’, but I’d imagine it’s to do with it being deployable / spring loaded in some way.
Same, been kicking myself since I found out it was all gone a few weeks ago. Don’t know why I didn’t make a ‘just in case’ backup / export.
Still infuriating they can just go “oops all gone”. It came through the roll-out fine, I remember looking stuff up in February. As far as I can tell it was a later unrelated glitch.
Google also accidentally deleted a random amount of user’s timeline data if you didn’t immediately catch it and restore from back up last March before the affected backups were overwritten. If you didn’t keep a close enough watch on your timeline to know that that happened, everything before ~Feb 2025 is gone now.
Ask me how I know. Yes I kept up on permissions. Yes I had backups on. No I didn’t have a new device. I even have dozens of available gigabytes of paid storage on Google One.
I’m sure it will only get more stable due to maps and timeline being revenue generators that encourage investment.
Building from source is always going to come with complications. That’s why most people don’t do it. A docker compose file that ‘just’ downloads the stable release from a repo and starts running is dramatically more simple than cross-referencing all your services to make sure there are no dependency conflicts.
There’s an added layer of complexity under the hood to simplify the common use case.
For now anyway, it used to be $20+/gb. I’ll settle for flooding the market with refurbished 16+tb drives.