Keybase is a powerful and secure team-organizing software. And because Keybase is so transparently good at what it does, Keybase is a foundational software that facilitates the future of work: effective, inclusive, secure Remote Teams.

Keybase is a free, end-to-end encrypted, open-source program with almost limitless flexibility. Each Keybase user or team is a unique cryptographic identity. Each message or interaction that a user has with a team or other user, is verifiable and digitally-signed. Custom combinations of users/teams/bots, can be designed to catalyze Remote Teams of all kinds, this process can also be automated. Keybase includes Git integration for versioning, bots from multiple platforms to facilitate audio/video-conferencing, a Cryptocurrency wallet, and many advanced privacy features to make you more or less traceable.

Services like Slack and Discord are centralized platforms that perform analytics on your behavior and can sell or leak this data to 3rd parties. Any audio/video features available within Slack or Discord, are bound to be less secure and less flexible than excellent alternatives such as Jitsi. Slack and Discord do have a fun, causal feel to them, which can potentially facilitate social engagement in certain conditions (also many users are already on these platforms).

Centralized and Proprietary team platforms such as Discord and Slack have a large market presence (at least in the USA) based on their first-mover advantage, name recognition, and network effects from size. However these products do not have the flexibility or power of Keybase. Keybase excels on its own excellence, and also has an open and active developer community.

Find us on Keybase: @remotorteam (Keybase username) @remotor.public (Public Keybase Team)

We chose RocketChat over other communications suites like Cliq or Slack mainly because we can self-host it on our own infrastructure. Since we have quite some projects going on which demand that we stay in touch with a lot of different stakeholders, pricing was an issue, too. With RocketChat, we have a huge set of features basically for free, RC offers apps for all major devices and systems and overall, we're very happy with it. The only downside is the limited amount of apps and integrations, but we can make due with what we have available.

we were using slack and at the same time we had a subscription with office 365. after a while we hit the slack free limitation quota. and it got annoying. the search ability was useless in free tier. and more annoying whenever you search, it opens a webpage and doesn't do it in the app.

on mobile there were many cases that I didn't get notification of important discussions. rooms was the way to separate a talk. but it become tedious. each time for a new subject that you wanted to discuss, you needed to add all the team members into a new room. and after a while the room goes silent. you will end up with a tons of not-in-use rooms that you don't want to clean up them for history purposes. also the slack UI for sub discussion is very stupid. if someone forget to check the checkbox to post the subdiscussion in the main discussion thread, other team members even won't notice such discussion is in progress.

we was paying for office 365 and thought why not give the teams a shot. we won't be in worth situation than we are. we moved to teams and we loved it instantly, we had a separate tab aggregated all the files upload. we could reply on other talk. no need of creating a new room. this way room belongs to a team and not a certain topic. our sub discussion was visible to the whole team. enjoyed integration with azure and unlimited history. the best part was integration with outlook. it was a full suit solution. our stats become busy on outlook meeting events. we get weekly analyse. we didn't need to host our wiki seperated. we've created wiki per team. the communication was much more fun.

lxd/lxc and Docker aren't congruent so this comparison needs a more detailed look; but in short I can say: the lxd-integrated administration of storage including zfs with its snapshot capabilities as well as the system container (multi-process) approach of lxc vs. the limited single-process container approach of Docker is the main reason I chose lxd over Docker.