ETL to QE, Update 35, Epic User Journeys
Date: 2024-05-07
It seems that I have lost the forest for the trees. All this talk of Proof of Concepts and CGFS has distracted me from the original goal of this project and its predecessors. Let's do a quick overview of where we came from, where we are, and where we are trying to go.
Before Question Engine
Back in 2020, I wrote this document whose goal was to replace centralized platform with self hosted alternatives that were already on the market while building bridges between all of them.
I later realized that these self hosted apps are a pretty bespoke making it difficult to share data between them. This is when I came up with the, DDaemon - Two Root Problems concepts which I have repeated below,
I am interested in two problems.
- How does one put all data they have personally generated into an single accessible API with RBAC(Rule Based Access Control).
- Once all one's data is all easily queryable what do you do with it?
- Ask yourself, what is Data For?
Conceptualizing Question Engine's First Epic User Journey
As someone that thinks about coding more than they actually code I have come to discover a shit test to test myself and others. If you can't develop your own basic social media app like twitter or bug tracker github issues by yourself you are probably not as smart as you think you are.
As I started applying the, can you develop a DIY sociel media app by yourself huristic, to myself I realized there was no good crypto social media protocols at the time. Today there is Nostr, Farcaster, DeSo among others some of which were around at the time but I was not aware. I was walking through the steps to actually develop the application and realized there was room for innovation within the original formula setup by twitter, facebook, Instagram, reddit and the like.
This was when I wrote the Original Question Engine User Journey whose underlying concepts of self issued tokens to gate access to social media content were first founded.
This token gated conversational data structure with digital signing as well as hash based Provenance was the first epic user journey, and I expect to have finished by 2024-05-12 frontend and all.
Other Epic User Journeys
You can check out the Epic User Journeys document to see how this conversation is evolving.
I have not found the perfect app for organizing my data, so below I have listed some expectations for software I have in the future that each count as a Epic User Journey in my books,
I want my photo management, bookmarking, and web annotation applications to hook up seamlessly with my Personal Knowledge Management System.
I want this blog to not only be published using Question Engine and CGFS but editable, forkable, and linkable.
I want a AWS Mechanical Turk that operates in a crypto native environment.
I want crypto provenance of media on the internet so we can know what was written by humans, what was not, be able to have intense debates about these questions, and avoid AI model collapse. Note: AI model collapse is when AI's get trained on too much data generated by AI's.
I want a decentralized knowledge graph or maybe more accurately a meme graph to track the provenance and evolution of meme. Oh and everyone should have their own personal meme graph that integrates with public meme graphs managed by DAO(Decentralized Autonomous Organizations)'s.
I want to be able to subtly interrogate any form of media by linking it's provenance to a meme graph, relating the content to other media, and hooking the memes to Decentralized Knowledge Graphs.
But the long term vision here is that I want QE and CGFS to be the roots of our digital future. When it comes to "Society" people are their data and CGFS should be the most decentralized, secure, and privacy enabled provenance way to store individuals data and how it get's transformed by others and AI systems.
Brainstorming
- What is the goal of this piece?
- Mapping out the documentation
- So what is the problem with the documentation?
- Oh yea composable context manifesto
- Who is the intended audience of this piece?
- Bryan Peters should read this
- What are we trying to communicate with this piece?
- I have a vision that I am trying to OODA towards
- Each of these ideas is a separate project that has similar underlying data structures
- What question does this piece implicitly ask?
- What is the Vision of QE, DDaemon, CGFS?
- What products can QE, DDaemon, and CGFS be used for
- What problem is this piece trying to solve?
- Let's create some milestone goal posts that we can use to orient and judge ourselves(Specifically myself) in the future