android VS client

Such apps exist. Essentially they require a license key before accesing. For example, Cryptomator (github) and Threema (github) .

Cryptomator (version 2772): Put a lock on your cloud: Take the security of your data into your own hands

You mean this? https://github.com/cryptomator/android

Yep, also want to point out the app is actually open source, the only reason it's paid on Google Play is so that you can support the devs: https://github.com/cryptomator/android

If you use Cryptomator, using Google Drive is fine.

Android: https://github.com/cryptomator/android/releases

Maybe it is related to https://github.com/cryptomator/android/issues/426 and the corresponding upstream issue https://github.com/pCloud/pcloud-sdk-java/issues/36 ... u/pCloudApp would be awesome if you could forward this into your company too as it is a quiet important one.

See: https://github.com/keybase/client/issues/24577

There have been 17 releases since Keybase was acquired

> development slowed down to a crawl

It's pretty wild that you can see exactly the moment when Zoom bought them on their github activity graph: https://github.com/keybase/client/graphs/code-frequency

Related: Open source the server components of Keybase (GitHub issue, 147 comments)

https://github.com/keybase/client/issues/24105

- We are still making regular updates to Keybase. These updates consist primarily of bugfixes, security fixes, performance improvements and patches to 3rd party libraries. We are not currently pursuing any major new features. The paper trail for Keybase updates is visible for all to see here: https://github.com/keybase/client/tags

Yeah looking at the commit graph for the keybase client shows a pretty obvious acquisition date..

https://github.com/keybase/client/graphs/contributors

Yes, this has always been the case. The root CA is embedded in the Keybase client: https://github.com/keybase/client/blob/master/go/libkb/ca.go

This provides a way to add some protection against a polluted trusted CA store.

> The source code for Keybase is, right now, fully open source on their Github

Really? My understanding was that the client and some libraries they use are open source, but the actual server code is closed source. Although if Zoom isn't going to continue maintaining keybase, then open sourcing the server code seems like "the right thing to do" (at least morally, and probably from a PR standpoint as well). Even if they did want to continue maintaining it, it would be a good thing in my opinion, but moreso if the project will die otherwise.

See https://github.com/keybase/client/issues/24105

This may be unrelated but week before last a new buggy version of the keybase client was released (v5.9.0). This is the first release since September. It has issues related to KBFS mounts that caused me to have to downgrade to the previous version. If you're seeing problems that only recently cropped up, this may relate to this new version.