3 ms·
Piggybacking off of the original question, I too have a question in this scope: With all the products you're offering, is there any indication which products w
by notheguyouthink 9y ago
Piggybacking off of the original question, I too have a question in this scope:
With all the products you're offering, is there any indication which products will be staples of Keybase? Eg, I'm always hesitant of the "Google Product", where something gets added only to be abandoned ~1yr later after it doesn't gain the traction the company expected.
For example, I'd love to get my wife and I switched to Keybase Chat from Telegram. With that said, I love the features of Telegram, they're killing it for me honestly, but I can't expect Keybase to compete with Telegram unless they're really invested in it.
So which products from Keybase are one-off experiments, and which are long-roadmapped products - expected to have continued development and support for years to come? I'm having trouble understanding what to trust.
Note, none of this is critical to Keybase. I'm wary of startups in general, despite loving you guys, so I'm just seeking understanding. I appreciate whatever information you can give me, even if small :)
- woolvalley 9y agoWhy not use signal?
- unlmtd1 9y agoNeither keybase chat nor signal are the future of communication; matrix is.
- iivarih 9y agoSignal only provides chat functionality... And doesn't support multiple devices... Also the history is lost on device change (or upgrade/reset etc)... And you cannot chat with people who you don't trust with your phone number
- zamber 9y agoMy best guess as an uninformed lurker and a Keybase user is that it's too early to know. You would have to know what's the impact of "sunsetting" features and for that you probably need more than 180k early adopters. In case of chat you can always fallback to Telegram (I've done that after trying to move people to Wire). In case of git you can always move the repo. With the setup that's there now I can see how it could be used as the main origin along with a push to GitHub hook. Pull requests would be even mergable (blessed be Torvalds), though I'm not 100% sure if GitHub would pick up on that and autoclose the PR.