[HN Gopher] Turning Down Upspin Infrastructure
___________________________________________________________________
Turning Down Upspin Infrastructure
Author : 4ad
Score : 7 points
Date : 2025-02-11 21:39 UTC (4 days ago)
(HTM) web link (groups.google.com)
(TXT) w3m dump (groups.google.com)
| pbohun wrote:
| This saddens me because I think the concept behind Upspin is
| powerful. Is it really that much of a resource drain to drop the
| key server? I imagine it could run on a $10/mo VPS.
|
| This is the talk that introduced Upspin:
| https://www.youtube.com/watch?v=ENLWEfi0Tkg
| mdaniel wrote:
| This is the first time I've heard of this but "All the users
| are connected through a central key server at key.upspin.io,
| which holds the public key and directory server address for
| each user"[1] sounds like they reinvented PGP's key server. To
| the best of my knowledge one can have arbitrary metadata in a
| published key[2], with the benefit that it's subject to
| revocation just like any other part of the key. I believe
| that's the _whole idea_ that keybase.io was trying to build
| upon, although them orphaning their infra when Zoom bought them
| isn 't lost on me
|
| 1: https://upspin.io/doc/arch.md
|
| 2: https://openpgp.dev/book/certificates.html#user-
| attributes-i...
| jagged-chisel wrote:
| I don't understand why this is (was?) dead. Can someone
| address mdaniel's comment and explain what is so egregious?
| olowe wrote:
| Sad. As a fan of Plan 9 myself it's somewhat expected. The ideas
| are strong but there's something about it all not quite catching
| on.
|
| I regularly referred others to Upspin's source tree [1] if they
| wondered about larger systems written in Go but weren't _too_ big
| and gross like Kubernetes.
|
| [1]: https://github.com/upspin/upspin
___________________________________________________________________
(page generated 2025-02-15 23:01 UTC)