3 ms·

I'd tunnel it over a websocket, or there's no reason why you couldn't translate its verbs into a REST API. It's a super simple protocol with not a lot of compl

I'd tunnel it over a websocket, or there's no reason why you couldn't translate its verbs into a REST API. It's a super simple protocol with not a lot of complexity. It sounds like you're after a federated storage protocol though, i.e. something that two totally different apps can use to allow a user to transfer data between them. This is a much, much bigger leap in complexity and requires a very strong authentication and authorization story. IMHO look into the fediverse and whatever is going on with storage and files there.

mike_hearn 4y ago
Isn't translating filesystem operation verbs into an HTTP based protocol what WebDAV does?
- anderspitman 4y ago
  Yes, and it's almost what we need. I think it's just too ossified to adapt to the few remaining shortcomings. Here's a couple: * Doesn't specify a federated authentication/authorization mechanism to allow self-hosted instances to work with each other. This includes things like how to have an app delegate permissions to other apps, ie for things like launcher apps which can open external apps and give them access to only specific files. * Doesn't specify a way to implement image thumbnails/previews, which is necessary for any sort of remote file explorer or gallery app.