Closed ghost closed 11 months ago
What I've thought is, there is a public database to which only the application can write and all users can read it. There is a feed with every edit that a user has made. Other users vote on that feed. The application adds a feed entry to the public database when it has enough votes.
How do I make sure that only the application and not the user is allowed to write in the public database?
Peerbit may be a better choice for that scale of collaboration. However, the idea of "the application and not the user" doesn't really work in a p2p database since they are one in the same, no way to prevent a user from acting on behalf of "the application". So it sounds like you need a server for running "the application" part, or a smart contract. Alternatively, you can look into Holochain which is more than a p2p database and allows things such as not permitting writes unless they're signed with validity based on custom rules (such as "had enough votes") that are enforced by every peer.
I would recommend reaching out to the community to discuss your requirements in more detail.
I would like to do a collaborative, crowd-sourced distributed database for a file organizer with auto-tagging where each user has a copy and changes are voted between the users and applied to all databases when they are approved. Is OrbitDB a good option for this or is there anything simpler?