I 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".
Keys.pub – Manage cryptographic keys and user identities
11–20 of 92 posts
Re: Keys.pub – Manage cryptographic keys and user identities
#12Earlier quoted context omitted.
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
#13I'm not sure if I misread the documentation, but it seems that with keys.pub each "service" offers a disconnected world. If somebody manages to publish a proof in my github account, it can trick people using keys.pub to think that's still me.
OTOH, with keys.pub I don't need to trust any server.
Am I misunderstanding something?
Re: Keys.pub – Manage cryptographic keys and user identities
#14I 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".
Not that I'm saying they should support just me, everyone has their own set of a magical does-just-enough feature set.
Re: Keys.pub – Manage cryptographic keys and user identities
#15I 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".
Re: Keys.pub – Manage cryptographic keys and user identities
#16Jokes aside, gpg does exactly key management, signing, encryption and so on.
Plus, it's nice to acknowledge and support the work of the author.
A tiny wrapper that provides a friendly CLI/TUI would be welcome.
Re: Keys.pub – Manage cryptographic keys and user identities
#17One 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?
https://github.com/plyint/encpass.sh/blob/master/extensions/...
Re: Keys.pub – Manage cryptographic keys and user identities
#18I 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".
Re: Keys.pub – Manage cryptographic keys and user identities
#19I 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".
No: people cat take a moral stance against things that look sleazy like asking for uploading private keys or trying to sell cryptocurrencies.
> can you not just avoid
"can you just" is a bit patronizing, would you mind not using that tone?
Re: Keys.pub – Manage cryptographic keys and user identities
#20I 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".
Nothing is free. Adding features takes up resources, adds complexity and errors and increases attack surface. Sometimes that's an OK tradeoff - I like being able to see images in my email client. Sometimes the tradeoff is not worth it - my text centric IDE has no business touching database files.