A basic pledge (that is actually followed) to not delete everyone’s data, finetunes, etc.
Such a commitment would not be credible. Even if you’re confident Meta won’t do the classic Google thing of sunsetting the service, or go broke, or change CEOs, they’d still be subject to things like DMCA takedowns that running locally safeguards you from.
This is a stronger argument than I first thought it was. You’re right, and I think I have underestimated the utility of genuine ownership of tools like fine-tunes in general.
I would imagine it goes api < cloud hosting < local hosting in terms of this stuff, and with regular local backups (what’s a few TB here or there) then it would be feasible to protect your cloud hosted 405B system from most takedowns as long as you can find a new cloud provider. I’m under the impression that the vast majority of 405B users will be using cloud providers, is that correct?
Such a commitment would not be credible. Even if you’re confident Meta won’t do the classic Google thing of sunsetting the service, or go broke, or change CEOs, they’d still be subject to things like DMCA takedowns that running locally safeguards you from.
This is a stronger argument than I first thought it was. You’re right, and I think I have underestimated the utility of genuine ownership of tools like fine-tunes in general. I would imagine it goes api < cloud hosting < local hosting in terms of this stuff, and with regular local backups (what’s a few TB here or there) then it would be feasible to protect your cloud hosted 405B system from most takedowns as long as you can find a new cloud provider. I’m under the impression that the vast majority of 405B users will be using cloud providers, is that correct?