4 ms·

[Update] I've missed the upspin.io link, which wasn't in article. Now I see (unless I'm misunderstanding it) it's something similar to to Keybase Filesystem, ex

[Update] I've missed the upspin.io link, which wasn't in article. Now I see (unless I'm misunderstanding it) it's something similar to to Keybase Filesystem, except distributed. That's a good thing, then. My apologies for not getting this before writing the original comment. ---- So... they had reinvented HTTP, and had thrown in some email-based authentication module, and formalized aeons-old /~username/ spec into /user@email.address.tld/? Anyone with the HTTP server can host files. Traditionally, .htpasswd or similar measures were used for access controls. This seems to be different only in a sense that it uses emails (found no docs and too lazy to read the code). I've glanced over the repo and I don't get what all that code is for. A re-implementation of webdavfs that maps first-level directories (emails) to hosts? Or... what? Can anyone link to some docs?

enneff 10y ago
You're definitely missing a lot. Please take a look at the overview doc, it should be mostly explained here: https://upspin.io/doc/overview.md https://upspin.io/doc/overview.md One of the key elements of Upspin is that all content is signed and encrypted by the client. Sharing is totally in control of the content owners, and the servers need not be trusted at all.
- drdaeman 10y ago
  Ah, thanks. Article didn't have a link to upspin.io, so I've missed this link. Yes, with client-side signing it makes more sense. So it's something similar to Keybase Filesystem, except distributed? That's a good thing, then.
  - enneff 10y ago
    Yeah it was a mistake not to include that link in the blog post. It is definitely similar to Keybase Filesystem, and a few other things too. There are many axes for making trade offs in this space, and I think Upspin set of trade offs is unique. We'll see if it works well for people.
sfeng 10y ago
There is a reason people use Dropbox not Apache to share files. Unless you can explain why that is, I'm not sure what criticizing their open source work achieves.
- drdaeman 10y ago
  I get the reason, but don't think it's similar. (And, AFAIK, Dropbox uses nginx to share files.) Yet, article clearly said this is not a product, but a set of protocols. So I was wondering what's the point, if the protocols (HTTP, WebDAV) are already there for a long time, and even have native support and can be easily mounted as local drives in most modern OSes. I've missed the encryption and signing bits. Sorry about that.

enneff 10y ago

You're definitely missing a lot. Please take a look at the overview doc, it should be mostly explained here: https://upspin.io/doc/overview.md https://upspin.io/doc/overview.md One of the key elements of Upspin is that all content is signed and encrypted by the client. Sharing is totally in control of the content owners, and the servers need not be trusted at all.

drdaeman 10y ago
Ah, thanks. Article didn't have a link to upspin.io, so I've missed this link. Yes, with client-side signing it makes more sense. So it's something similar to Keybase Filesystem, except distributed? That's a good thing, then.
- enneff 10y ago
  Yeah it was a mistake not to include that link in the blog post. It is definitely similar to Keybase Filesystem, and a few other things too. There are many axes for making trade offs in this space, and I think Upspin set of trade offs is unique. We'll see if it works well for people.

sfeng 10y ago

There is a reason people use Dropbox not Apache to share files. Unless you can explain why that is, I'm not sure what criticizing their open source work achieves.

drdaeman 10y ago
I get the reason, but don't think it's similar. (And, AFAIK, Dropbox uses nginx to share files.) Yet, article clearly said this is not a product, but a set of protocols. So I was wondering what's the point, if the protocols (HTTP, WebDAV) are already there for a long time, and even have native support and can be easily mounted as local drives in most modern OSes. I've missed the encryption and signing bits. Sorry about that.