111–120 of 170 posts
Edit: I sound like a total fangirl :/
Cool to see in terms of Go style how they handle errors -- https://github.com/upspin/upspin/blob/master/errors/errors.g... It's a common pattern I've seen, but given that this comes from Rob Pike etc., glad to see that the pattern is considered a good one Edit: I sound like a total fangirl :/
It's worth noting /u/eneff's comment about the initial code though: https://twitter.com/enneff/status/834167073508978689
Cool to see in terms of Go style how they handle errors -- https://github.com/upspin/upspin/blob/master/errors/errors.g... It's a common pattern I've seen, but given that this comes from Rob Pike etc., glad to see that the pattern is considered a good one Edit: I sound like a total fangirl :/
I'm excited to see what kind of discussion comes up around this codebase. It's worth noting /u/eneff's comment about the initial code though: https://twitter.com/enneff/status/834167073508978689
Earlier quoted context omitted.
What problem does this solve for the end-user that isn't already or better solved by Google Drive, Dropbox, or sharing in chat apps like Hangouts or WhatApp? Or is it like, "Here is some cool technology!" without identifying a clear user need this solves, like Google Wave?
Dropbox uses one key for all content... Google drive means google can see all of your stuff... Sharing in hangouts is just like drive... WhatsApp isn't close to this robust... Wave was just really far ahead of its time but you see the modern incarnation in google docs and paper. This is like the infra to build spideroak on your own hardware. It's not the same as a service where you have to trust the operator.
I noted the disclaimer: "Upspin is not an official Google product". Yet it is announced on the Google Blog? Is it a separate "skunk works" team effort? Also, I note that they can set access levels based on email addresses, but I am unsure how that would work? Would those emails have to be linked to a Google account so that Upspin could check the currently logged in Google account to allow/disallow access to the files…
Upspin is one of Google's many Open Source projects. It's not really skunkworks, per se, just something that we wanted to work on and were lucky enough to be supported by Google in doing so. The email addresses are Upspin user names whose public keys are registered with a central server, key.upspin.io. To act as an Upspin client, you need to sign up: https://upspin.io/doc/signup.md Requests made by Upspin users are s…
Earlier quoted context omitted.
I don't think you fully read how it works. It said the storage providers etc can be self hosted.
I might have misinterpreted the overview, but the key server/service that provides authentication for users sounded like a central point in the system.
Earlier quoted context omitted.
Gotcha, thanks for the extra info. So you still have to sign up with the Upspin service to be able to consume shared files? I was under the impression from the post that it was an 'account free' type of service, in as much as you can publish a URL where people can grab files, but still provided a level of access control, and I was having a hard time reconciling that in my head.
You need to register your public key with key.upspin.io in order to speak to any Upspin servers, so in that sense it is not "account free". You need to prove to others that you are who you say you are. There is an "all" permission that shares with the world (see https://upspin.io/doc/access_control.md ) but in most cases we expect people will share with a specific set of named users.
Cool to see in terms of Go style how they handle errors -- https://github.com/upspin/upspin/blob/master/errors/errors.g... It's a common pattern I've seen, but given that this comes from Rob Pike etc., glad to see that the pattern is considered a good one Edit: I sound like a total fangirl :/