Then later, Barb: keybase team add-member treehouse -user=carter -role=writer Keybase team add-member treehouse -user=barb -role=admin How they would've done this, command-line edition Carter can write files and chats, but he cannot edit the signature chain, since he's not an admin. In the above, we see a chain of length 3, where treehouse now has 2 admins (barb and alice) and 1 "writer" (carter). And technically, people themselves are chains, so you're signing their chains onto the team chain. Your first link declares that only you can append to the chain. When you create a team, you begin a chain of signatures. This isn't some malleable, trusted SQL database with team roles in it. (Spoiler: truly private repos.) Anyway, teams have signature chains This is only the beginning the GUI is evolving fast and we'll have another announcement in ~2 weeks about encrypted git for teams. FilesĪ team's encrypted files can be found in /keybase/team/: Teams with multiple chat channels are grouped under "Big teams."Īlso, there is no upsell on message history. If a team is small, it'll blend into your inbox. Teams can be casual and small: bezosfamily. What if your team's history got stolen from Slack and leaked or published? The legal and emotional nightmare.Īlso, Keybase accounts are simpler you don't have to switch at the top level of the app. Alternatively, you can lie awake at night.fearing a breach of your company's messaging history. But Keybase teamwork is end-to-end encrypted, which means you don't have to worry about server hacks.
0 Comments
Leave a Reply. |