- related :

VRM
CustomerTech
design - IndyVRM

- tutorial :

- why : IndyWiki
IndyWiki is your Personal First protal to all your Knowledge Work

- demo steps :

go to http://localhost:8081/Fission/Webnative/IndieHub#wiki/VRM@trailmarker

- slogans : IndyWeb

Forging the IndyVerse as communities of Edge-Players/Edge Developers.
Connecting People as Edge Players to digital creators & their digital creations along with the tools they need
These WebNative Apps form their own born interoperable networks.
Everything: people, creators, creations and their tools in this network is FAIR:

Findable,
Accessible,
Interoperable,
Reusable,
repurposable and
remixable.

The participants act as their own Hub and set the terms for sharing creating a value flows
for the benefit of the participants,

These communities coalesce around Open, Commons based peer co-created
WebNative Apps provided by Edge Developers.
These Apps are Tinkerable, born interoperable, edge-player personalizable and extensible,

- demo : // qua slides

- comment :

since I am demonstrating IndyWiki and TrailHub1 pilot and it's core capability Indiehub
I forego the generation of slides, although I have a prototype too for that capability
let's call it IndySlides
instead show the sources for the slides as a section in the IndyWiki page for this demo

- comment :

this is in line with the primary purpose of IndyWiki which is
to provide a single place for all your

networked writing (writing to think)
annotated web research
sharing hypermapped networks of your thoughts as

wiki pages
deeply rearranged narrative trails as HyperBlog articles
your Mind's Graph to be explored showing

your work
as an entire scaffolding with which it has been erected

interpersonal deep collaboration

- what is : IndyWiki

- slogans :

Experience the Web as an Extension of your Mind

Is a single place for all your Personal Knowledge Work

It is in the form of a Wiki

it is doing the job of
extending & organizing the endless frontier of your Personal Knowledge
When you reach the edge of your knowledge the wiki invites you to

name what you think should be there
and just create a link to it
Think a Link

Conduct Annotated Web Research

two-way link annotation context to

trails of thoughts and
narrative trails you create

Capture the intertwingulairy of your Thoughts and Work

a Vehicle for inter personal deep conversations powered by IndieHub

that lets you invite others as IndyWiki customers

to join any of your circles and channels

these conversations are continuous, without being synchronous
act as portals to the work of the others in the emergent network

- what is : IndieHub

is an inter personal communications/collaboration
layer powered by Fission and OrbitDb
for sharing of personal knowledge work
along the means of managing, extending your knowledge
created as Full Edge WebNative fission and TrailHub powered Apps
It is designed to be able to turn

single-player,
local-first
Progressive Web Apps into
Multiplayer, extensible, tinkerable Apps

It provides minimal viable Vendor Relationship Management Capabilties

for Indepe WebNative Software Vendors
Full Edge Indy WebNative Developer

- what is : IndyVRM

It is an instance first prototype for Indy Vendor Relationship Management

developed as a WebNative Capability within IndieHub

It allows TrailMarks (us) as an Independent WebNative Software Vendor,
to establish two way communication channels with our Customers
- features:

- read only - conduits :

- gloss : conduits, connect end points in two way communication

customer 2 vendor
customer 2 community
- note :

as a premium feature IndieHub allows customers to create their own community
This is in contrast to creating channels dedicated to topics which
can be accessed by invitation only
Communities allow and process requests to join
or as in the case of VRM they are automatically joined into the
Customer Community for the Independent WebNative Software Vendor

Product information
Terms of sharing & collaboration

All communication channels can have their own terms
Customers must accept them before they are created
Certain functions become available only when customers accept the terms
Unless otherwise specified all channels maintain immutable records in OrbitDbs
of request/responses made and contain the Fission User Names of the participants
These records are encrypted with dynamically generated, changed keys in the database
but both participants can, if they so choose, keep these records as files in the
private part of their own Fission WebNative Drive

- comment :

no need for privacy terms, that usually about the extent to which user loosers are required to
allow services to violate their privacy

- vendor - notification - channels :

conduit
software update

the terms for these will evolve as the

- customer - notification - channels :

require action on behalf of the user

as the software is being develops

in
as IndyWiki Pages in a the TrailMarks IndyWiki

- target audience: Full Edge developers

it provides a minimal viable Vendor Relation Management Capabilities

Dominant social networks are centralized,
Upcoming federated social networks as the IndieWeb are server based
With all of them people flock to sites for capabilities they want
With dominant social networks you pay with privacy for the convenience
and u r the product being sold
People's connection to each other
require intermediaries,
their contribution to ongoing conversations
are scattered across networks, and silos.
We need people to be able to connect with each other
without intermediaries,
empowered to form their own(ed)
Personal First inter personal networks
share and collaborate in their own terms

- the solution :

Flip the prevailing paradigm

People are creators, not users,
in fact together with Full Edge developers
people can become co-creators of
Commons Based
Peer Produced
WebNative
Tinkerable Apps that come to them

Use the best of the emergent Web 3 technologies,

Fission's Webnative, IPFS, and OrbitDb
to flip the model

Reject the prevailing paradigm

In line with Fission's vision of no backend
Come up with an architecture
based on the idea that Data is

owned and
stored, replicated, backed up by their creators
on their own devices First

Ensure thorough

carefully evaluated technology choices

IPFS, Fission, OrbitDb

that creators
own their data, make it availbale offline
put them in control of the ways they share their creations
Ensure Lifelong permanence and availability
of their data encyrpted if desired.
Allow individuals and all the participants
in their owned networks
to remain in control of their data
ensure trustful data flows,
search and discover each others knowledge bases
mutually set and agree to terms of sharing and exchange
using WebNative, trusted but verifiable

dedicated communication channels

Back to the Future Conceptual Innovations

bring Universality and Simplicity
MindGraph
TrailMarks
Conceptipedia

Architect and develop software in new ways

Fission's WebNative Constellation Provider technology

radically reduces the complexity of
the development of applications
that share key components like authentication and storage
thereby achieving a shared and born interoperable data layer
to bring simplicity and enduring concepts and approaches
things like Elm and
AppRun inspired by Elm, think of it as Elm in TypeScript
to the world of web development
No backend, Full Edge development
gives you an edge

when contrasted and compared to
main stream approaches

and guarantees a common data layer

in the form of a WebNative file system

let individuals to be their own(ed) hubs
with strong privacy guarantees
connecting to other people that they can trust
set their own terns of mutual sharing
to form emergent interpersonal (interest/intent based)
indie social gossip networks.
TrailHub1 tries to solve.

Weaving

WebNative
Inter Planetary,
interpersonal,
indie social networking constellations
as IndieHubs that connect to form the IndieVerse.
The same hard issues that hyperknowledge federation
seek to address in the context of centralized,
or federated architectures
can be reformulated and
in fact much more easily tackled
at least in first approximations
in this architecture,
as it is based on trust,
and bad actors can be blocked from entering the "gossip" network
at the webnative entry points .
so that they can act as like the
"blood brain barrier" for the brain
(key idea I learned from Jack Park)
can treat federation servers and
other aggregators as "sanctuary organs"
such that these trust networks can provide
strong guarantees of acceptable conduct
towards federation points or inter personal peer to community

demo - Fission Demo Day 2021 March