EOS SupportπŸ“šByWireNewsπŸ“°EOS LondonπŸ‡¬πŸ‡§EOS BeesπŸΖ’ractallyπŸŒ€MindStore🧠

MindWeb.io πŸ”„ Your Visual Knowledge Base On EOS

Presentation

This page will evolve during the iterations of the development of MindWeb.io

Interview by Jimmy D – Genereos.io Season 2
MindWeb – Your Visual Knowledgebase On EOS | Showcasing video
https://youtu.be/93eyNy35-Nw
Interview by Chris Barnes – Season 1
Interview by Jimmy D – Genereos.io Season 1
High overview – Whyology by NovaCrypto
High overview – Knowledge Builder by NovaCrypto
Integration with other Ecosystems on EOS – Not exhaustive

Features

  • Creators of MindWeb MindMaps
    • Anyone that create an account on MindWeb.io
  • Consumers examples
    • Support multi-lingual (first english)
    • Eosbees multi-lingual hive (first english)
    • Workshops
    • Edu platform
    • Publishing platform
  • Recognition of eos users and Eden Member users
    • Anchor/Unicove
  • Data sources connector and mindmap automation
    • Discord
    • Telegram
  • Integration with other platforms/website
    • iFrame, Rest API service
  • Decentralized storage
    • Meta-data about mindmaps are stored on eos mainnet – Mindmap on IPFS
  • Proof-of-mind
    • Mindweb mindmaps are minted as NFT on EOS Atomic Hub
  • Market Place mindmaster.io with new category eos/eosio
    • Mindweb mindmaps can be published for a potential of 4 million users in 180 countries
  • Functions
    • Everyone : editor online with collaboration features by one to many users on a mindweb mindmap)
    • Everyone : sharing
    • Creators : Authoring (read, read/write)
    • Everyone : Upload
    • Everyone : Thesaurus search
    • System : Rating of mindmaps based on subjective metrics (possible integration with eosrate.io)

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)