Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
enneff
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
50 ms
·
631.
▲
by
enneff
10y ago
It'd be interesting to talk about how this might work.
632.
▲
by
enneff
10y ago
> How many files per directory has this been tested on? Not a massive number. The current DirServer implementation will likely run into problems once the corpus reaches a certain size. But there can be more than one DirServer implementat
633.
▲
by
enneff
10y ago
The signup process sends a verification message to your email address to confirm that you own it.
634.
▲
by
enneff
10y ago
I didn't write the "unofficial" part, but I can answer the questions: > Does it mean that people don't work on it full-time and it's a 20% project? That there are a few of us paid full-time to work on this, plus
635.
▲
by
enneff
10y ago
We haven't written the docs. That's what the issue I linked in the parent post is about.
636.
▲
by
enneff
10y ago
A better godoc link: https://godoc.org/upspin.io
637.
▲
by
enneff
10y ago
In Upspin you typically store your files in a remote server somewhere on the net (our default implementation uses Google Cloud Storage as its storage backend), which is something you need to pay for. The solution to the problem you describe
638.
▲
by
enneff
10y ago
Upspin users maintain their own storage servers, or use storage servers maintained by someone else. The Upspin project itself doesn't have any authority or control over the type of content stored or shared with the system. > google
639.
▲
by
enneff
10y ago
That's the plan! :-)
640.
▲
by
enneff
10y ago
This is pretty much correct. Upspin is way more filesystem-like than Camlistore, but I would emphasize Upspin's single global name space, rather than the filesystem-ness. I think both Camlistore and Upspin have promising models.
641.
▲
by
enneff
10y ago
In case it's not clear, this project is in its very early stage of development. There's a ton of work to do to get it into the hands of non-technical users. From the readme: "Upspin has rough edges, and is not yet suitable fo
642.
▲
by
enneff
10y ago
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"
643.
▲
by
enneff
10y ago
I feel like it's still early days, but that's a good suggestion! I filed an issue: https://github.com/upspin/upspin/issues/209
644.
▲
by
enneff
10y ago
We are aware of kbfs, ipfs, and several other systems. There are many trade-offs one can make in this space, and I think Upspin's set of tradeoffs is somewhat unique. One reason we started this project instead of contributing to others
645.
▲
by
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 un
646.
▲
by
enneff
10y ago
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 nam
647.
▲
by
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 One of the key elements of Upspin is that all content is signed and en
648.
▲
by
enneff
10y ago
My interpretation was that the "citation needed" was in reference to "we have seen similar claims before that have turned out to be false or exaggerated greatly".
649.
▲
by
enneff
10y ago
Aren't decrypt and decipher synonyms? What is their distinction, if any?
650.
▲
by
enneff
10y ago
Microsoft puts more effort into keeping things working than Apple does. Go works on XP as a result of the work Microsoft has done, not the Go project. Apple change subtle things in each OS X release making it onerous to support the older on
651.
▲
by
enneff
10y ago
Those features were the impetus for the tool, and as far as I'm aware they were Not Invented Anywhere at the time. :-)
652.
▲
by
enneff
10y ago
I don't remember the details of our testing platform, it's been a while since I've been involved in ARM6 builders. I do remember that we used to test against emulators but they diverged significantly enough from the real hard
653.
▲
by
enneff
10y ago
Reveal wasn't a thing when I wrote present. I probably would have used it as a front end, had it existed. Tools like Keynote and Google Slides were exactly the kind of thing we were trying to improve upon. They're great for making
654.
▲
by
enneff
10y ago
Can you suggest another presentation tool that makes it as easy to author and maintain slides? Nothing like this existed when Rob and I wrote present.
655.
▲
by
enneff
10y ago
Well Apple stopped supporting 10.8, so why should Go continue to support it? ARM6 support is a lot of work, actually, as IIUC a lot of stuff that the chip doesn't support needs to be done in software, and we don't have a reliable
656.
▲
by
enneff
10y ago
For a car of that vintage and condition no advertising is necessary. Any interested parties will find out about it one way or another.
657.
▲
by
enneff
10y ago
I look at #3 and ask "What are x, y, and z? How did they get into this scope?"
658.
▲
by
enneff
10y ago
Russ Cox, the guy who wrote this post, is the technical lead for the Go project. He authored more of Go's code base than anyone else (by a huge margin). His opinion about these issues holds more weight than pretty much anyone. I wouldn
659.
▲
by
enneff
10y ago
> I think you overestimate how willing someone is to sit in a small car with 3 other strangers during their morning and evening commutes. The self-driving vehicle needn't be a small car.
660.
▲
by
enneff
10y ago
And also the original MacOS font, Chicago!
More ›