Even if you want it make it "off by default" for new installs, and leave it off for mastodon.social, at least give the server operators a way to turn it back on if they want to. PLEASE consider restoring this functionality, and making it configurable by each server operator. I'm sure that after the acquisition, Zoom wanted the Keybase developers to work on the Zoom client code, so it makes sense to me that the "pace of commits" on the Keybase client repo dropped at the time. Remember that the whole reason Zoom acquired Keybase was to get access to their security expertise, after several security issues were found in the Zoom client. there have been new features added, including Keybase Sites, which I am currently using to host a few personal web sites. If it were being abandoned, they would have just shut it down entirely, rather than continuing to pay the S3 storage bill for everybody's encrypted data blocks (for which users are still not being charged). Zoom said it has fixed the flaw in the latest.
Flaws in zoom keybase kept images software. Your keybase data is stored on servers located in the united states. Most messengers will keep your messages until your account is deleted. The bug was fixed last month, so users are.
Keybase IS still being actively maintained - certainly not at the same rate it was originally, but it hasn't been abandoned by any means. Flaws in zoom's keybase app kept chat images from being deleted. I can understand if some people might not want to allow Keybase proofs, however I think this is a decision which should be left up to each server operator, rather than being forced on every server by fiat like this. chicksdaddy writes: The Security Ledger reports that a flaw in Zoom's Keybase secure chat application left copies of images contained in secure communications on Keybase users' computers after they were supposedly deleted, according to researchers from the security research group Sakura Samurai.
0 kommentar(er)
