ts-matterbridge (Integrate teamspeak chat with matterbridge).ServUO-matterbridge (A matterbridge connector for ServUO servers).MatterAMXX (Counter-Strike, half-life and more via AMXX mod).fbridge-asyncio (Facebook messenger support).MatterBukkit (Matterbridge link for Minecraft Bukkit/Spigot server chat).MatterCraft (Matterbridge link for Minecraft Forge server chat).MatterLink (Matterbridge link for Minecraft Forge server chat, archived).Feel free to make a PR to add your project to this list. Whatsapp multidevice beta is natively supported but you need to build yourself, see here.Not supported anymore, see here for more info.Support multiple gateways(bridges) for your protocols.Bridge slack (#general) - discord (general).Bridge mattermost (off-topic) - irc (#testing).Building with whatsapp (beta) multidevice support.Root teams (e.g., nike) don't have implicit adminsĪ subteam (e.g., nike.Note: Matter most isn't required to run matter bridge. The above properties are summarized in the following access matrix: role Their KBFS or Chat, but it has that ability anyways by just corrupting all of Setup gives the server the ability to break the user's attempt to decrypt Server-stored key-half that is only distributed if the ACLs permit it. (1) the shared key that is encrypted for all user's Per-User Keys and (2) a Team needs (for Chat or KBFS or Saltpack), the ultimate key used is an XOR of: The cryptographic mechanism here is that for any shared secret team key the An owner is an admin for root team who additionally has the power to delete the team.But Keybase can still enforce, for instance, that a sysadmin for Campbell Soup Corp.Thus, a subteam can avoid dangerous situations in which all of its members have lost their access to data.Server-gated keys for that team, and therefore does not get access to KBFS and chat data. An implicit admin of a subteam who hasn't been explicitly added to the subteam does not get access to.Keys, which in turn allow access to KBFS and chat data. All explicit admins have read/write access to their teams, and get full access to server-gated.An implicit admin is one who is an admin of a parent subteam, but not this subteam.An admin can additionally deactivate a team as long as it's not a root team. An admin can add or remove admins, readers, and writers to the team, and establish a subteam for the team.A writer has all of the permissions of a reader, but can also write to the team's KBFS resources.A reader can read the KBFS folders for a team, and he can both read and write a team's chat.A team is a group of keybase users, consisting of: admins, owners, implicit admins,.Since so doing would reveal nike's membership to adidas, and vice versa. Right now, Keybase does not support shares across teams, like /keybase/team/nike,adidas, Will be able to read and write the team, while those with only read permissions will lack With multiple channels, and every member of the team, regardless of their role,įor KBFS, team shares will be available under paths such as /keybse/team/nikeĪnd /keybase/team/nike.hr.interns.volleyball. Mutable and uniquely identified by name, without fear of a malicious serverįor chat, every team like nike.hr.interns.volleyball, will have private chats, That we initially support with Keybase teams. Team members can be certain that the Keybase servers aren't equivocating about ![]() ![]() ![]() Pseudonyms, pointed to by their parent teams. The team lets_fire_bob.just_kidding_fire_bruce, then Bruce would have no way ofĪs we will see, every team and subteam has its own signature chain that's insertedĭirectly into the Keybase global tree. The very existence of subteamsĪre hidden from all who aren't members of the subteam. Nike.hr.interns.volleyball are all valid subteams. ![]() The team lets_fire_bob, the whole world will see it, they just won't be able to getĪny details about who the members are unless they are themselves team members. These names are visible to the whole world, so if you create So valid root teams include nike, google, Teams and SubteamsĪ root team is a top-level identifier in the Keybase namespace, which obeys the This document provides a high-level description of Keybase teams, specifying applications,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |