dckc
commented
7 years ago good formats for persistent objects, along with their protocols, and how their protocols relate to capTP (and waterken / HTTPS):
- CSV (spreadsheet UIs: excel on win/mac, openoffice on linux, google sheets, ethercalc (in sandstorm))
- several together: .zip
- JSON
- jupyter notebooks
- iphoto web thingy
- rfc822 / MIME email: IMAP, SMTP (and maybe even POP)
- .ical (SMTP? caldav?)
- git repo (https, ssh; there's a git network protocol too, right? what's the common API?)
- hg repo (very nice http protocol)
- HTML, sort of (google drive doesn't animate it)
- PDF (http)
- JPEG (http)
- mp4? (http; what's the video format on all our cell phones?)
microformats fits in here somewhere...
ski
I don't want backups. I never did. I want highly available persistent objects.
GETis__uncalle.g. the shortstory I wrote in macwrite or whatever in the early '90s - openoffice re-hydrated it as HTML just fine... it's like a GET on that original file with accept: application/html and openoffice can convert macwrite to html on the server side. Now I have little use for the macwrite format copy except for audit purposes. (though I didn't make any cryptographic commitments at the time, so there's not much value there.)
backup of large media files has bothered me for ages... but any number of providers will now turn those into highly available object capabilities: google drive, dropbox, probably amazon drive... sandstorm?
A name I control would be nice... IPFS has nice naming, but only for public stuff. I guess filecoin is the next step there? These decentralized storage marketplaces don't seem to be there