Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It looks as if it's been in maintenance mode since the acquisition. Why is that?


From 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...


This 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...)

Five months later, they announce their initial technical preview of E2E encryption (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.


Because Zoom only wanted the employees and the appearance of caring about encryption and didn't care about the product.


It's entirely possible they genuinely cared about encryption for their own product, and didn't give two hoots about the Keybase product.


If they genuinely cared, they would have started a lot sooner.


Are they not allowed to shift priorities as they grow? I'm sure there are many things you genuinely care for these days which wouldn't have been true a few years ago. It would be dismissive for me to assert you don't truly care about those things, would it not?


That's not fair. A lot of companies start off not caring about security because they just need to ship and grow. They add security later after they get owned or when they need to take on the type of customer that also genuinely care about security. Maybe they didn't care before and they care now. That's allowed.


I disagree. At this point, there's no real reason to just not care about security from day one.

There's a wealth of tools and docs, and users are becoming more and more conscious (which is fantastic, for the record!). There's the obvious ethics of keeping the data your users entrust you with safe to the best of your abilities, too.


There's a real reason to not care about security from day one... the competitor who doesn't care will beat you to market, and then you don't get a day 2.

Sorry, but the vast majority of people just don't care. Customers want a working product.


Or they suddenly had a lot of reason to start caring more, and the best way to get competent people onto improving security was an acquihire?


Zoom wanted the hashes, not the employees.


Yours is the only comment on this thread so far that mentions hashes. Care to explain what you mean by hashes in this context, and what benefit you think zoom would get from acquiring them?


chinese law is such that any company holding password hashes turns them over to the government

none of those hashes stand up to government level resources

every keybase customer is now available to china, which has a long pattern of logging in as you


Ah I see, that seems to be a reasonable concern.


They were acquired to appease investors/public relations during the explosive pandemic growth phase when a multitude of security issues were uncovered.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: