491–500 of 716 posts
That aged well...
Earlier quoted context omitted.
Do you really want Backblaze to ignore all the side effects of scanning through the entire contents a badly-designed network filesystem?
What I actually want is not a backup. That is just an artefact of the process. What i want is restores. The ability to restore anything from ideally any point back in time. How that is achieved is not my concern. Obviously Backblaze does not achieve that, today.
You're dodging the question. Wanting to ignore the side effects does not mean they won't affect you.
I once had to restore around 2 TB of RAW photos. The app was a mess. It crashed every few hours. I ended up manually downloading single folders over a timespan of 2 weeks to restore my data. The support only apologized and could not help with my restore problem. After this I cancelled my subscription immediately and use local drives for my backups now, drives which I rotate (in use and locations). I never trust them…
Earlier quoted context omitted.
+1. It works perfectly if your mental model is: “Every file is only ever written to from a single client, and will be asynchronously made available to all other clients, and after some period of time has elapsed you can safely switch to always writing to the file from a different client”.
Bidirectional file sync is also in hot demand from people who don't know the words, "file", "client", "write", "async", "available", or "time" :P
Earlier quoted context omitted.
According to http://web.archive.org/web/20260317212538/https://support.mo... its F9 on Windows Ctrl + Alt + R on Linux Command + Option + R on macOS (It uses JS to only show the one for your platform but with view source you can see it mentions all three of these different OSes.) So I guess the first guy is a Windows user and you other two use Linux.
> (It uses JS to only show the one for your platform but with view source you can see it mentions all three of these different OSes.) There is a dropdown at the top-right to select the platform - no need to view source.
Earlier quoted context omitted.
YouTube is constantly reencoding videos to save space at the expense of older content looking like mud, so arguably even they're having their struggles.
We all know the "nobody has watched this video in ten years, login at least once or it'll be yeeted" email is coming, someday.
Earlier quoted context omitted.
Bidirectional auto file sync is a fundamentally broken pattern and I'm tired of pretending it's not. It's just complete chaos with wrong files constantly getting overridden on both ends. I have no clue why people still use it and I'd cut my losses if I were you, either backup to the cloud or pull from it, not both at the same time like an absolute tictac.
> I have no clue why people still use it This is an instance of someone familiar with complex file access patterns not understanding the normal use case for these services. The people using these bidirectional sync services want last writer wins behavior. The mild and moderately technical people I work with all get it and work with it. They know how to use the UI to look for old versions if someone accidentally overw…
Earlier quoted context omitted.
Why would it do that more than once unless you are modifying 4TB of data every day, in which case you are causing the problem.
I don't know how your client works, but reading metadata (e.g. requesting size) off any file causes some cloud clients to download it completely. Of course I'm not modifying 4TB on a cloud drive, every day.
Earlier quoted context omitted.
"Dear Claude, please create an eztensive testing suite for this app. Love, cobertos"
"Great idea wise customer, I will certainly mock one out just for you!"
In the last panel, Charlie Brown tells him, "You have to move your feet, too."