- report an error
- ignore
- materialize
Regardless, if you make it back up software that doesn’t give this level of control to users, and you make a change about which files you’re going to back up, you should probably be a lot more vocal with your users about the change. Vanishingly few people read release notes.
If it's not open-source, but the protocol is documented, see above.
If it's not open-source, and the protocol isn't documented, well... that makes the decision easy, doesn't it?
I've used enough Claude coded applications that I wouldn't trust that with a backup, unless it had extensive tests along with it.
In the last panel, Charlie Brown tells him, "You have to move your feet, too."
https://featureassets.gocomics.com/assets/5ee4a050f894013014...
I can audit and verify Claude's output. Code running at BackBlaze, not so much. Take some responsibility for your data. Rest assured, nobody else will.
What time I do have, I've been using to try and figure out photo libraries. Nothing is working the way I need it to. The providers are a mess of security restrictions and buggy software.
You're forgetting the third option:
You can remain blissfully unaware of it.
And you can read many accounts of the outcome of that strategy in this very thread.