Scenario 1: Open Src clients. Backend API paid access.

Users pay to use over a certain amount. Android app / mobile apps followed by web app.

Scenario 2: Open Src clients. Local storage. Users can sync

• Could use git or file sharing stuff (dropbox etc) for sync.
• Client app could be electon instead of browser
  • Electron seems to be a bad path see
  • Browser will be able to access file system stuff soon it seems
    https://wicg.github.io/file-system-access/

The below fundamental types of node are potentials:

1. Nodes that represent some information
2. Nodes that point at some external resource (book / site / film etc)
3. Nodes relating to primarily educational resources
4. Nodes that allow for categorising data

OR alternatively, the above should all be tags or otherwise on a node...

Partly depends on the power of the query language, and what logic we want to use to grab display sets

Interesting to think about what makes this different from a WIKI.

• What properties are shared between the two?
  • What learning can we take from established sites for both of those domains?
• What makes Lore unique and what value does this bring to the knowledge representation and transfer domain?

Web app could be free, mobile app could be a small subscription. App allows for data traversal and entry via shared links etc. Maybe can use for free for 3 creations a day?

Free for local use, paid monthly fee to store certain amounts. Do cheap i.e. 99p a month for up to x nodes etc

We should not allow storing of rich media unless on some higher plan. We can pull down images and vectorise and black and white them for low storage requirements.

If storing images we should just get them replicated on a CDN and cache locally

Mission:

To facilitate the journey from Data -> Knowledge -> Understanding -> Wisdom

Purpose:

To make informed decisions about how we live our lives and how we can contribute in the best possible way to society and the environment we need to be able to form an accurate understanding of the true nature of things. When bombarded with data every moment of our waking lives is is hard to allow ourselves to form deeper connections and understanding, and fundamentally to retain what is mentally valuable to us. Our purpose is to provide tools which help in both the retaining of information and widening the understanding of the connections between that information.

(credit: Dee Hock)

Principles:

• Open Source
  • WHY?
• Users should own their own data
  • Valuable, they don't want to lose it
• Simple clean tools
• Clean maintainable code

https://stackshare.io/

Initial Ideas

graph DB

• Neo4j
  • GraphineDB
  • https://github.com/neo4j/neo4j-browser
  • GPLv3, if run server side seems harmless (link)
• Amazon Neptune
  • How to guide to access in a serverless way https://acloud.guru/learn/aws-go-serverless-graph-database
• Amazon Appsync https://aws.amazon.com/appsync/
  • GraphQL proxy
• Cayley*
  • Truely open src
• Azure CosmosDB
  • NoSQL but supports gremlin
  • can be deployed serverless https://azure.microsoft.com/en-us/solutions/serverless/#solutions

non graph

• Firebase RealtimeDB or Cloud Firestore
  • not graph but can roll out serverless solution here
  • JSON or Document respectively
• IBM cloudant https://www.ibm.com/cloud/cloudant
  • serverless with auth
  • https://cloud.ibm.com/catalog/services/compose-for-janusgraph
    • beta

Host (PaaS)

For simplicity need a PaaS, dont have to worry about any real admin

• Digital Ocean
• Linode
  • better than digital ocean
• Heroku*
  • Seems best rated and good support
• Google App Engine
• Amazon Elastic Beanstalk

Host (Serverless)

• Amazon
  • https://aws.amazon.com/cloudformation/
  • https://aws.amazon.com/serverless/?nc2=h_ql_sol_use_servc
• IBM
• Azure
  • https://azure.microsoft.com/en-us/solutions/serverless/#solutions

Host (no host!)

Use file syncing like dropbox and or google drive. Web apps would be awkward, electron app for desktop? Would mean no costs at all for me.

• Google Drive https://developers.google.com/drive/api/v3/about-sdk

server side framework

• Springboot
• Kotlin (Ktor)*
  • simple, and its kotlin!

front end (options)

• Vue
• Service workers (if heavy weight web app)
• Snowpack (front-end build tool)
• React.js (or Preact + HTM)
• HTML5 Canvas / http://graphalchemist.github.io/Alchemy/

OR

Multiplatform

• Flutter!
• KMP with Kotlin/JS
• Electron (no mobile?)

Auth

• Firebase Auth
• Amazon Cognito

• UserVoice
• Holocracy
• Open Src proj man book

It may make sense to support both, private graphs for individuals and public graphs for sharing knowledge, with optional collaboration.

Would be interesting if the user auth and the data submission and acceptance modules were pluggable.

I guess it would be simpler for user auth to always support multiple accounts, and a graph would either have a flag saying private only, admin can invite, or world open.

For data submission and acceptance, it would be only admins submit, anyone can submit without validation, or anyone can submit with validation from a) 1 admin or b) x public users. Guess that stuff can all be pluggable, and toggleable by the user.

• https://www.thebrain.com
  • Really expensive, looks good but not for mass use due to price, maybe server side use only allows use of site?
  • Has mobile apps (low ratings, poor UI)
  • site has good anims for multilinked mindmaps
• https://roamresearch.com/
  • Notebook style, looks like html from a glance
• org-roam https://github.com/org-roam/org-roam
  • 3rd party FOSS version of the above
• graph commons
  • Pricy (I think)
• bear https://bear.app/
  • apple only
  • markdown
  • paid syncing
• Obsidian https://obsidian.md/
  • closed src
  • desktop only
  • syncing done by user via google / dropbox etc
  • markdown file based so users own their own stuff
  • interesting thread of views about Obsidian and all its competitors! https://news.ycombinator.com/item?id=23324598
• Joplin https://joplinapp.org/
  • FOSS
  • no graph
  • mobile apps
  • markdown
• Quiver https://github.com/HappenApps/Quiver/wiki
  • apple only it seems
  • markdown and latex support
  • renders latex flowcharts and sequence diagrams inline https://github.com/HappenApps/Quiver/wiki/Getting-Started (JS it seems)
• Trilium
  • Screenshots https://github.com/zadam/trilium/wiki/Screenshot-tour
• vnote https://tamlok.github.io/vnote/en_us/
• https://github.com/brettkromkamp/contextualise
  • build on top of topic maps https://docs.microsoft.com/en-us/previous-versions/aa480048(v=msdn.10)?redirectedfrom=MSDN
• https://tiddlywiki.com/
• Memex https://getmemex.com/
  • mostly fancy bookmarks
• https://orgpad.com/
  • Seems closest to a graph mindmeister

• Some products seem to be able to share and publish stuff online
  Add stuff from https://pragmaticlead.com/posts/unlock-your-productivity-by-taling-better-notes-zettlekasten

INTRO

INTERCONNECTED MICRO KNOWLEDGE GRAPH LEANING MAP TLDR-WIKI ... (type in, typo out)

(animate in musee style)
/-0
o-LORE-o
o-/

Sales pitch

Twitter of knowledge, micro knowledge map (limit chars etc)
Data -> Knowledge -> Understanding -> Wisdom

Core representation

• Medium? Obsidian homepage style title text
• Sketch.com
• Feedly.com

Core interaction

• adding new stuff
• querying whats there (LoreQL)
• refining whats there
• visualising and exlporing whats there

Tools

https://vectr.com

We should create a personal use prototype for mobile app and site, using Firebase. Perf does not matter, we can invite people to use with an alpha release.

Prototype a personal knowledge graph and then go from there. May want to expand to be able to collaborate and or publish graphs or parts of a graph.

Libraries

• https://github.com/antvis/g6/
  • https://g6.antv.vision/en/examples/gallery