8 ms·
Graph of Keybase commits pre and post Zoom acquisition
- sydthrowaway 5y agoWhat was so special about keybase that a bunch of nerds needed to add their public key everywhere?
- ceejayoz 5y agoIt was a wonderfully user-friendly front end to GPG. I used it extensively with some non-technical clients to exchange credentials when they originally wanted to send them via email.
- Hizonner 5y agoWhat's so special about Zoom? If Zoom fell off the face of the Earth, by the next day everybody would have switched to any of half a dozen nearly identical services, many of them older than Zoom. Within another couple of days, everybody would have stopped noticing the difference.
- brabel 5y agoWe've used Skype, GoToMeeting, Slack... and finally Zoom, and Zoom was the best quality video conferencing by far. No echo, no sound+video synch issues, rarely any "breaking up"... they must've implemented some very nice tricks to make all these work even when we have meetings with people sitting in from several different countries. Despite their security issues, it's not surprising they came to dominate the market: it was the only product that really worked.
- ahnick 5y agoWhat's special is the ability to publish cryptographic proofs on public social media profiles to link back to a central identity. You could say this person on Twitter, Facebook (discontinued), Github, HN, etc. is 100% the same person. Key provisioning and recovery becomes easy then when you setup multiple devices and your messages are available across mobile, laptop, desktop and across various operating systems. And it was all end-to-end encrypted.
- SamPatt 5y agoWith good UX for chat and excellent file sharing. Very sad it didn't get more traction. I still use it.
- ahnick 5y agoI still use it regularly as well. There is definitely a thriving ecosystem of users on it, which tells me that it is providing real value to some people. Either someone is going to breathe new life into Keybase or someone is going to come along and build something similar to Keybase with better execution and be wildly successful.
- toastal 5y agoThe browser extension also gave you a way help verify as well as giving you the ability to send an encrypted DM which is more secure than most of these social platforms. (But had it caught on, it would not have been fun to deal with spam and moderation)
- 1MachineElf 5y agoIt looks as if it's been in maintenance mode since the acquisition. Why is that?
- randtrain34 5y agoFrom https://keybase.io/blog/keybase-joins-zoom https://keybase.io/blog/keybase-joins-zoom > Initially, our single top priority is helping to make Zoom even more secure. Although the git graph looks like it's their only priority at the moment...
- throwaway984393 5y agoThis PR release says the point was "Developing the Most Broadly Used Enterprise End-to-End Encryption Offering" (https://investors.zoom.us/news-releases/news-release-details/zoom-acquires-keybase-and-announces-goal-developing-most-broadly https://investors.zoom.us/news-releases/news-release-details...) Five months later, they announce their initial technical preview of E2E encryption (https://blog.zoom.us/zoom-rolling-out-end-to-end-encryption-offering/ https://blog.zoom.us/zoom-rolling-out-end-to-end-encryption-...) What usually happens after M&A is if the acquired product isn't a profit-maker, they "integrate" it into other products and it goes into maintenance mode, eventually to be sunset. If the product did make money, they'd re-brand it and keep development going... unless they have plans to integrate the product's core feature into a larger corporate product (Zoom) that a separate branded product would compete against internally. It seems like keybase has been eaten and absorbed into the Zoom app, and the rest will be flushed.
- melony 5y agoThey were acquired to appease investors/public relations during the explosive pandemic growth phase when a multitude of security issues were uncovered.
- modeless 5y agoBecause Zoom only wanted the employees and the appearance of caring about encryption and didn't care about the product.
- solarkraft 5y agoOh boy. Is it too early to say RIP?
- smitty1e 5y agoThe github repo looks ripe for a fork.
- deleted 5y ago[deleted]
- ryukafalz 5y agoThe servers are not FOSS and would need reimplementing.
- whateveracct 5y agoand that's numberwang
- derefr 5y agoLikely easy enough for a client based on E2E encryption principles; the backend is in many ways a (fancy) dumb pipe. (It could still require complex infrastructure, but at least there'd be relative little "feature" code on the backend to be rewritten.)
- westurner 5y agoFWIU, Cyph does Open Source E2E chat, files, and unlimited length social posts to circles or to public; but doesn't yet do encrypted git repos that can be solved with something like git-crypt. https://github.com/cyph/cyph https://github.com/cyph/cyph It would be wasteful to throw away the Web of Trust (people with handles to keys) that everyone entered into Keybase. Hopefully, Zoom will consider opening up the remaining pieces of Keybase if not just spinning the product back out to a separate entity? From https://news.ycombinator.com/item?id=19185998 https://news.ycombinator.com/item?id=19185998 https://westurner.github.io/hnlog/#comment-19185998 https://westurner.github.io/hnlog/#comment-19185998 : > There's also "Web Key Directory"; which hosts GPG keys over HTTPS from a .well-known URL for a given user@domain identifier: https://wiki.gnupg.org/WKD https://wiki.gnupg.org/WKD > GPG presumes secure key distribution > Compared to existing PGP/GPG keyservers [HKP], WKD does rely upon HTTPS. Blockcerts can be signed when granted to a particular identity entity: > Here are the open sources of blockchain-certificates/cert-issuer and blockchain-certificates/cert-verifier-js: https://github.com/blockchain-certificates https://github.com/blockchain-certificates CT Certificate Transparency logs for key grants and revocations may depend upon a centralized or a decentralized Merkleized datastore: https://en.wikipedia.org/wiki/Certificate_Transparency https://en.wikipedia.org/wiki/Certificate_Transparency How do I specify the correct attributes of my schema.org/Person record (maybe on my JAMstack site) in order to approximate the list of identities that e.g. Keybase lets one register and refer to a cryptographic proof of? Do I generate a W3C DID and claim my identities by listing them in a JSON-LD document signed with W3C ld-proofs (ld-signatures)? Which of the key directory and Web of Trust features of Keybase are covered by existing W3C spec Use Cases? From https://news.ycombinator.com/item?id=28701355 https://news.ycombinator.com/item?id=28701355: > "Use Cases and Requirements for Decentralized Identifiers" https://www.w3.org/TR/did-use-cases/ https://www.w3.org/TR/did-use-cases/ >> 2. Use Cases: Online shopper, Vehicle assemblies, Confidential Customer Engagement, Accessing Master Data of Entities, Transferable Skills Credentials, Cross-platform User-driven Sharing, Pseudonymous Work, Pseudonymity within a supply chain, Digital Permanent Resident Card, Importing retro toys, Public authority identity credentials (eIDAS), Correlation-controlled Services > And then, IIUC W3C Verifiable Credentials / ld-proofs can be signed with W3C DID keys - that can also be generated or registered centrally, like hosted wallets or custody services. There are many Use Cases for Verifiable Credentials: https://www.w3.org/TR/vc-use-cases/ https://www.w3.org/TR/vc-use-cases/ : >> 3. User Needs: Education, Retail, Finance, Healthcare, Professional Credentials, Legal Identity, Devices >> 4. User Tasks: Issue Claim, Assert Claim, Verify Claim, Store / Move Claim, Retrieve Claim, Revoke Claim >> 5. Focal Use Cases: Citizenship by Parentage, Expert Dive Instructor, International Travel with Minor and Upgrade >> 6. User Sequences: How a Verifiable Credential Might Be Created, How a Verifiable Credential Might Be Used Is there an ACME-like thing to verify online identity control like Keybase still does? Hopefully, Zoom will consider opening up the remaining pieces of Keybase if not just spinning the product back out to a separate entity?
- kmfrk 5y agoCan anyone get the "abandon proof" button to work in the profile in-browser if you want to remove something from your profile? I can't get it to work in Firefox and Edge for some reason. Don't want to reset or delete the entire account for now, but I'd like to remove some stuff.
- peterldowns 5y agoMy friend who joined Zoom via the acquisition said it’s abandoned, all future work is on Zoom, no plans to do anything other than bare minimum maintenance on the keybase systems. No surprise here. Bit of a shame though. Edit: following up on this since i think it was slightly misleading -- this has always been Zoom's public opinion since they announced the acquisition. Their goal was always to integrate the Keybase technology into Zoom. See their blogpost for more https://blog.zoom.us/zoom-acquires-keybase-and-announces-goal-of-developing-the-most-broadly-used-enterprise-end-to-end-encryption-offering/ https://blog.zoom.us/zoom-acquires-keybase-and-announces-goa...
- deleted 5y ago[deleted]
- swiley 5y agoKeybase had one of the few centralized chat apps I didn't hate. It's all such a shame but I guess that's why I stay away from centralized chat services.
- ahnick 5y agoIt is being maintained and still actively used. The largest user, afaik, is Chia Network (https://www.chia.net https://www.chia.net) and they rely on that for the bulk of their internal and external community comms. If Zoom decides not to host the servers anymore I predict they will likely try to acquire it from Zoom or re-implement the server portion. There is probably a profitable business to be built to implement an opensource version of the Keybase server that is backwards compatible with the client and then start charging enterprises a reasonable price for data storage and communications to host it in the cloud. Zoom is sitting on a potential gold mine and they are just letting it languish.
- SergeAx 5y agoYes, Zoom is sitting on a gold mine and it is online video conferencing. Keybase is a silver mine at best. Guess which mine you would prioritize?
- parhamn 5y agoA good reminder to take the verification off my HN profile now.
- atatatat 5y agoI've been surprised at how long it's taken the community to react in this way.
- wincent 5y agoIt always bugged me that the proof went on the profile itself and not on a mere comment like it does for other identities (Twitter → tweet, Reddit → a post in /r/KeybaseProofs etc).
- detaro 5y agono real place to make such a comment where it's not out-of-place, profile IMHO makes sense then.
- judge2020 5y agoThe problem with doing this on HN is that you can’t delete or edit comments after a few hours, so there would be no way to remove the proof besides a reply to your own comment (which also doesn’t work once the thread is old enough to not allow comments)
- neximo64 5y agoAcquisition canary
- reilly3000 5y agoI don’t know if I believe in such a thing. Salesforce has done many acquisitions over the years, and they have ranged from acqui-hire to complete independence. Zoom has no such history, and I’m bummed about Keybase, but the next one could be 100% different.
- deleted 5y ago[deleted]
- ianopolous 5y agohttps://peergos.org/posts/keybase-left-building https://peergos.org/posts/keybase-left-building
- simonw 5y agoZoom must have had the craziest period of hyper-growth over the past 18 months. Not at all surprising that the Keybase engineering team would be focused on Zoom problems.
- xrd 5y agoI would be really fascinated to read about acquisitions that led to actual explosion of the original product inside an organization and those that didn't, apparently like Keybase. Seems like there must be a financial metric where the purchase price should reflect that, or the size of the team divided by the purchase price would indicate something.
- 0des 5y agoWasn't Tesla one of these that was purchased and then blew up?
- grepfru_it 5y agoCompare to rundeck after they were acquired by Pagerduty https://github.com/rundeck/rundeck/graphs/contributors https://github.com/rundeck/rundeck/graphs/contributors
- mwest 5y agoIt's quite heart breaking. I particularly loved the idea of the Keybase Filesystem, sad to see this fall into an abandoned state. The closest Keybase alternative I've found so far is https://keys.pub/ https://keys.pub/ (on HN: https://news.ycombinator.com/item?id=22995792 https://news.ycombinator.com/item?id=22995792) Welcome any suggestions for KBFS alternatives!
- SamPatt 5y agoAgreed, file sharing via Keybase is a dream. It automatically creates an encrypted folder on my filesystem that is shared with the other party. Super convenient, I tried to evangelize it solely for this reason.
- jd3 5y agoignoring its UX, https://upspin.io/ https://upspin.io/ is the closest alternative that i'm aware of
- owerflov 5y agoI use keyoxide (https://keyoxide.org https://keyoxide.org) for showing proofs such dns and github.
- ashton314 5y agoKBFS was pure magic. I wish they had kept their focus on that. Alas, all good things…
- ianopolous 5y agoYou might like Peergos (disclaimer: co-founder here), an encrypted global filesystem built on ipfs - https://peergos.org https://peergos.org More detail in our book - https://book.peergos.org https://book.peergos.org We can also do signed identity proofs with better privacy than keybase's. Here's a public example https://beta.peergos.net/public/ianopolous/.profile/ids/ianopolous.Twitter.id.cbor?open=true https://beta.peergos.net/public/ianopolous/.profile/ids/iano...
- 5y ago
- computerfriend 5y agoOne of the top three worst things to happen in 2020.
- ornornor 5y agoWell they didn’t lie then when they said “nothing will change after the acquisition”.