Towards (semi) decentralized cross-workspaces collaboration and sharing of databases

Ideas & Features
1

Working with many collaboration initiatives and networks, I often experience the limitations of tools that are mainly built to serve classic organizations, not (semi)decentralized collaboration networks. I see that the trend is now towards such more (semi)decentralized collaboration tools. Please let me know your ideas and comments, when you read this.

I asked GPT-4 (with Bing browser extension) this question:

Please analyze the architecture of the application fibery.io and propose how we can build an extension for that, which allows workspaces and spaces between different user accounts to be shared. The idea is to create a more decentralized infrastructure for networked collaboration.

ChatGPT:

Finished browsing

Based on the information available from Fibery’s API and their user management features, here’s a high-level proposal for building an extension to share workspaces and spaces between different user accounts:

  1. Understand the Existing API: Fibery’s API currently supports customizing apps by creating, renaming, and deleting Types and Fields, working with Entities and Documents, and automating tasks using action buttons and rules​1​. Understanding these capabilities is key to leveraging them for building the extension.
  2. Design the Extension: Define the goals of the extension and the specifics of the functionality it should provide. In this case, the extension should enable sharing of workspaces and spaces between different user accounts.
  3. User Authentication and Authorization: Fibery manages permissions at the workspace or group level, allowing you to control who you share a workspace or space with, and whether they can modify the shared workspaces or spaces​2​. The extension should respect these permissions, using the Fibery API to check for the necessary permissions before allowing a workspace or space to be shared. It may also need to implement additional authentication and authorization checks, depending on the specifics of the desired functionality.
  4. Implement the Sharing Functionality: Using the Fibery API, implement the functionality to share a workspace or space with another user. This could involve creating a new Entity representing a shared workspace or space, linking it to the original workspace or space, and adding the other user as a collaborator. Alternatively, it could involve directly modifying the collaborators of the original workspace or space.
  5. User Interface: Design a user-friendly interface for the extension. This could be a web-based interface, a desktop app, or a mobile app, depending on the needs of the users. The interface should make it easy for users to select the workspace or space to share, choose the user to share it with, and set the permissions for the shared workspace or space.
  6. Testing: Thoroughly test the extension to ensure that it functions correctly, respects user permissions, and doesn’t introduce any security vulnerabilities.
  7. Deployment and Maintenance: Deploy the extension and provide ongoing maintenance and support. This could involve hosting the extension on a server, distributing it to users, and providing documentation and support.

The specific implementation details will depend on the exact functionality you want the extension to provide and the constraints of the Fibery API and user management system. Please note that any extension should respect Fibery’s terms of service and privacy policy, and should ensure the security and privacy of user data.

1 Like