When comparing Flock vs Keybase, the Slant community recommends Flock for most people. In the question“What is the best team chat software?” Flock is ranked 17th while Keybase is ranked 25th. The most important reason people chose Flock is:
They have apps for Windows, Mac, Chrome, iOS, Android and web interface. And all the chat sessions are always on sync.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Cross-platform
They have apps for Windows, Mac, Chrome, iOS, Android and web interface. And all the chat sessions are always on sync.
Pro Clean and clutter free interface
Pro Cheaper than Slack
It is half the price of Slack and full of nice features like polls, assign to do's, etc.
Pro Very powerful integration APIs
Unlike its rivals, it not only allows you to receive events, but also allows you to push content to it and receive various user action events.
Pro No IT team required for setup
Moving a team or organization to flock does not require any setup from the company's IT team. At max, what might be required would be to whitelist their domain in case the organization's IT team has gotten external domains blocked. You can simply download Flock and invite others in your organization by using their email ids in order to start collaborating. That's all there is in the name of setup.
Pro Free if you don't need the most advanced features
Most of its features are free, even video conferences. But also they have a Pro version with unlimited chat history, Active Directory integration among other things.
Pro Unlimited groups and teams
There is no limit on the number of groups or of group members. Similarly, within a team you can have unlimited members. There is no limit of number of teams too.
Pro Faster than Slack
Flock is offering an app that is faster than Slack.
Pro Highly configurable permissions
For every team, the permissions and restrictions can easily be set over the participating members and the conversations they are having.
Pro Better than slack
Pro Stickers
Posting messages is more fun with them in addition to emojis.
Pro Customisable UI, integrations surface just like native features
There are multiple options like slash commands, message buttons, chat buttons, attachment picker etc., where the integrations can surface inside the native app. This greatly eases the discoverability of a integration, making it really easy for the team members to find and use the integrations.
Pro E2E encrypted
Completely end-to-end encrypted.
Pro Identity verification
Users can publish proofs of identity (PGP public key, Twitter, Facebook, etc).
Pro FOSS
Free (as in beer) and Open Source Software.
Pro Encrypted file sharing
Securely share files.
Pro Public encrypted filesystem
For sharing files publicly.
Pro 250GB of free team file storage
250GB of free storage for encrypted files in a team.
Pro Public teams
Teams can be public with open access or admin-approved access. Opt-in to list public teams.
Pro Private teams
Teams can be completely private (access granted via admin-approval only, not publicly listed).
Pro Encrypted Git
Encrypted private or team Git repositories with automatic commit signatures.
Pro Blockchain technology
Based on blockchain technology.
Pro Sigchain verification
View/verify the cryptographic signature history of any user.
Pro PGP/GPG support
Encrypt/decrypt any PGP message or file with minimal effort.
Pro Public key encryption
Supports public key encryption.
Pro Private encrypted filesystem
Securely store personal files that only you can access.
Pro Shared private encrypted filesystem
Share files securely and privately with other users, a group of users, or a team.
Pro 250GB of free private file storage
250GB of free storage for privately-encrypted files.
Pro Free static site hosting
Host a public static website for free. Sites are automatically viewable via keybase.pub if an index.html or index.md exist in your public files.
Pro Emoji reactions to limit excessive posts and notifications
Pro E2E encrypted team chat
Teams are E2E encrypted, unlike Slack and other services.
Cons
Con No thread feature
Reply command only quotes snippets. There's no implementation to show thread(s) of an initial message.