This page will evolve during the iterations of the development of MindWeb.io
Features
When a MindWeb MindMap is created by a Creator of his MindMap
There will be status ‘Review’, ‘Rejected’, ‘Approved’
The creator of his MindMap will decide, this belongs to him (owner of his mindmap) :
– ‘approve’ the entire root node (mindMap) that each other creator (1 to many potentially) added to his MindMap
– ‘reject’ branches and/or sub-branches that each other creator (1 to many potentially) added to his MindMap
What is stored on-chain (not exhaustive list)?
– Keywords about the mindmaps and the owner (aka name) in order that MindWeb MindMaps can be found onto the platform (MindMaps are classified into topics)
– IPFS CID of the MindMap File
– Status of a MindMap (Review, Rejected, Approved)
The MindWeb Account is an email and password (needed in order that MindWeb.io can send an invite for the collaboration online)
– With an EOS Account tied and if this is an Eden on EOS Member Account, the Eden Member Account will be accessible from MindWeb.io to see the induction video.
When diving into a MindMap, if a branch is the root node (MindMap) of an Eden Member, this branch will be tagged with the AKA Name and link to Eden on EOS
The profiles on MindWeb are: Users, Creators, Admins, Owner
The level of functions: Everyone, Creators, System.
System is for example for the function for the MindMap’s rating (possible integration with eosrate.io)