Skip to content

DDaemon Master Plan

Inspiration Encapsulation

We can use Biscuit + DAG-JSON CID's + JSONSchema + ethersjs + NFT+ IndexedDB + Nostr + Polars to produce the core Question Engine application.

The nature of Question Engine is peer to peer. I answer your question by spending one of your tokens. A individuals questions do not need to be stored on a Nostr server but can be CID's that are stored client side in IndexedDB.

A user can encrypt and send their entire IndexedDB database to themselves.

A user can sync another device over Nostr though some websocket connection would likely work better. Imagine something like Tox where people connect to each other randomly in order to produce an space for Anon's.

The authority of a Question Engine anon can regulate threads so we can create 4chan.

People can broadcast the commons they want to manage on the blockchain, for example I can broadcast ddaemon.org because I will take in people's annotations and comments on there.

People can have a permissioned link tree where they know when people go and request their data from there.

People can focus on asking the most interesting questions.

DDaemon Directory

Key User Journeys

  1. Community Meme Context Generation User Journey
  2. Publishing PKMS on Question Engine User Journey
  3. Question Engine - QE
  4. Questioning Tulpa's User Journey
  5. Community (DAO) Interrogation User Journey
  6. Web Browsing with Competitive Context User Journey
  7. Annotate the Munk Debate User Journey

Reminders

  • OrbitDB
  • We need a way for people to comment on all my user stories and journeys
  • I need a way to map files, such as memes ebooks and documents etc, to an ontology
  • Produce memelets that have value to others

DDaemon Design Prompts

  • We need a way to annotate all digital data.
  • Imagine multi threaded twitter being produced from my logs, for example I can stream my browsing history when I am researching a specific topic.
  • We need a way to collaboratively life log.
  • We need a way to communicate our quests.
  • If a competent dev can produce a twitter clone by themselves in under a week by themselves whatever replaces twitter should also be able to be done in a week but use a fundamentally different design.
  • We need a embedding hub, sure we use CID's to look stuff up but we also need to do embeddings for images and text.
  • Where is blockchain twitter, where is blockchain reddit, why haven't people started using these things

DDaemon Design

Design Doc

DDaemon Components

  • Context Graph File System
    • Annotate Anything
    • Life Log File System
    • Key Value Store on top of IPLD using CID's inspired by Perkeep
  • Question Engine - QE
    • Have productive conversations with contextualized data
  • Something to do with Data Caching or AI Execution on Private Data

DDaemon Apps