Keys.pub – Manage cryptographic keys and user identities
1–10 of 92 posts
Re: Keys.pub – Manage cryptographic keys and user identities
#2This seems like a cool project. Keybase has kinda lost it's way and has no idea what it is anymore. Where this seems pretty focused on doing one thing and one thing well.
Re: Keys.pub – Manage cryptographic keys and user identities
#3One of the killer features for Keybase is the combination of teams + KeybaseFS. Unfortunately this doesn't look like it has either of those features.
Re: Keys.pub – Manage cryptographic keys and user identities
#4I was a very early user of Keybase and I've been super disappointed in the direction they've gone. They've had some neat ideas along the way but packing them onto the key service and the cryptocurrency missteps have caused me to shy away from them.
This looks like a good start for a real competitor. Obviously it's early but I'm seeing the right things.
Re: Keys.pub – Manage cryptographic keys and user identities
#5One of the killer features for Keybase is the combination of teams + KeybaseFS. Unfortunately this doesn't look like it has either of those features.
That's the cruft. If they separated those out into separate apps, I'd be happy. It's an E2E-encrypted Slack-clone, public key management system, encrypted file storage, and a crypto wallet.
Re: Keys.pub – Manage cryptographic keys and user identities
#6One of the killer features for Keybase is the combination of teams + KeybaseFS. Unfortunately this doesn't look like it has either of those features.
Sounds interesting, how is this feature useful?
Re: Keys.pub – Manage cryptographic keys and user identities
#7One of the killer features for Keybase is the combination of teams + KeybaseFS. Unfortunately this doesn't look like it has either of those features.
That's the cruft. If they separated those out into separate apps, I'd be happy. It's an E2E-encrypted Slack-clone, public key management system, encrypted file storage, and a crypto wallet.
I guess one man's cruft is another man's crucial feature.
Re: Keys.pub – Manage cryptographic keys and user identities
#8I get that this is new and in development, but I'd really like to see a more in-depth comparison to keybase than:
> This project borrows many ideas from Keybase, including sigchains and user (proofs), and uses Saltpack and keybase/go-keychain and other packages. However, this project only links a single key to a user.
I say this while noting I've seen that "Better documentation" is an item in the todo list. However, it just isn't clear - to me - where they plan to move or draw a finish line for features.
If you have a better comparison please post it, and I guess a PR for the project too ;)
Re: Keys.pub – Manage cryptographic keys and user identities
#9> This project is in development and has not been audited.
I love seeing notes like this. Everyone needs to start somewhere, and for security projects there is a danger of overselling initially, which undermines credibility. This sounds like someone who understands that theres a lot of complex challenges to get this to production level security.
Re: Keys.pub – Manage cryptographic keys and user identities
#10I was a very early user of Keybase and I've been super disappointed in the direction they've gone. They've had some neat ideas along the way but packing them onto the key service and the cryptocurrency missteps have caused me to shy away from them. This looks like a good start for a real competitor. Obviously it's early but I'm seeing the right things.
I see this from a lot of people and I'm puzzled, can you not just avoid using the features you don't like? I don't see anyone going "I used to use VS Code but they added a database viewer so I stopped".