vision - IndieHub

trans© trailmarker
Complementing Fission's Mission and Vision

- why? : many accounts
  • The many accounts are there because 
  • I am interested in providing a Kernel for building WebNative capabilities that are
    • FAIR
      • Findable
      • Accessible
      • Interoperable
      • Reusable
    • Personal First
    • Tinkereable
    • Personalizable
    • Extensible and
    • Composable 
  • There are two levels of capabilities
    • Meta level, enabling framework components/capabilities 
      • These are built using authentication, storage provided by Fission
      • Taken together needed to get this new holonic architecture / paradigm off the ground
      • and
    • point solutions addressing specific needs
  • IndieHub refers to a Minimun Viable Composition of capabilities  needed to support 
    • the development and commons based peer production of 
      • WebNative Software as a Conversation 
      • by Independent Full Edge Developers.
    • IndiHub's primary focus is to provide the means of
      • Inter Planetary,
      • Inter Personal, 
      • Inter Community, 
      • peer to peer, 
      • peer to community, 
      • community to peers,
      • eventually consistent,
      • near real time, 
      • communication and
      • sharing capabilities across apps
      • turn local first single player web apps into multiplayer conversations
        • with small modifications needed
        • or as a side car
      • IndieHub  is based on a People Central Architecture
        • It makes three radical simplifying assumptions
          • follows/adopts Fission WebNative stance
            • It gets of the ground thanks to Fissions
              • User Controlled Authentication Network
              • WebNative File System
            • It combines Fission with OrbitDb
            • Within the People Central Architectural 
            • IndieHub can deliver Progressive Accounts and Private File Sharing now
            • Both of these are on the Road map for Fission
            • to be deployed with wider range of architectures
          • keeps the number of active communication channels under 40
            • that the  communication networks to be realized
            • involves people acting as their own(ed) hubs
          • Built on Trust for Trust
            • Trust but verify
    • Inspired by IndieWeb, IndieHub re-imagines Indie Web on Web 3, in a
      • decentralized,
      • hostless, Webnative stetting
      • to  provides the means for people to connect with each other directly
      • act as their own hubs in their own(ed) networks of collaboration and sharing, and 
      • two-way linking anything, anywhere, 
      • That anything includes not only content but capabilities.
    • Aims to co-create and co-evolve interoperability across decentralized eco systems.
      • Starting with IPFS, Fission and OrbitDb as an instance first exemplar

  • Core capabilites integrated within IndieHub are
    • MindGraph
      • Universal Meta Data Model for describing any other app specific data 
      • (plays the role of RDF in SoLiD)
      • that use TrailMarks as its fundamental building block
      • MindDrive
        • WebNative Storage layer built on top of Fission 
        • that provide 
          • permanent 
          • personal first 
          • content addressable 
          • hierarchical,
          • de-duplicated,
          • file storage
        • with a round trip between it and MindGraph
        • TrailMarks 
          • is a Rich Text Editor or Networked Thought Processor
          • A Personal First tool for creating/writing high resolution intent addressable structured content 
          • that maps to MindGraph and 
          • can be used to bootstrap MindGraph to create intentional semantic models for 
          • all content the user creates/intar acts with 
          • along with the very capabilities needed to manage them across/over the web
        • SlipStream
          • guiding and assisting users to switch context and focus and 
          • maintain a comprehensible view across changing bursts of attention
          • helping the user to bring to mind what they had in mind
          • surface information they need in context in any context 
        • point solutions that address specific needs
          • While I have half a dozen or so early app prototypes that address specific needs, 
            • they were all designed and built to be Personal First based on  MindGraph
            • I will en devour  to bring all these into the WebNative setting forging the IndyVerse
          • my current focus is to ship IndyWiki as a HubLet that makes use of IndieHub
          • Build an Improvement Community around IndyWiki to share and exchange ideas 
          • Form an Open Collective around it, ship it early ship it often.
        • IndyWiki is
          • Re-imagining the Wiki on Web 3, going WebNative.
          • Build it as a Hublet powered by IndieHub