ETL to QE, Update 45, Perspective is difficult
Date: 2024-11-04
Let's put some things in perspective,
- I spent hundreds of hours working on the Discord Binding developing various ETL pipelines and even a frontend
- Like two and a half years ago I started work on Question Engine developing various Question Engine POCs with the Oldest One being the most developed
- A while back I worked on the Nostr NIP05 Server but my idealist constraints overwhelmed me and we pivoted to CGFS
- In recent time we have spent dozens of hours working on CGFS going down various rabbit holes and technology rabbit holes Such as LevelDB
- Recently we worked on the Nostr CMS which is sorta functional but I would not trust anyone else to run the code, it is supposed to eventually replace dentropys-obsidian-publisher
- Recently we also worked on the AI Taskmaster project
Let's ask the important question,
Have we developed anything here that I could recommend other people to use?
I don't know anyone else that has a Markdown notes so no one can use my Obsidian Publisher
I have deployed the Discord Binding a couple times but it never had Authentication so it was either wide open on the clear net or behind a basic HTTP Proxy. I have demoed it personally many times and gotten enough feedback to know those graphs and statistics are relatively useless without additional context. Plus we are missing the most important feature, a chat interface to see what messages we generated graphs from.
Over the last couple days I have been freaking out a bit about weather or not I want to develop my own NIP or integrate a bunch of existing NIP's such as
- Nostr Event Kinds
- Nostr Event Tags
- NIP0 - Nostr Profiles
- NIP01 - Notes
- NIP02 - Follow Lists
- NIP03 - Timestamp Proof of Events
- NIP04/NIP17 - Encrypted Events
- NIP05 - DNS Identities
- NIP14 - The Subject Tag
- NIP19/NIP21 - Reposts and bech32 encoded entities such as Events, Addresses, Profiles, or Relays
- NIP22 - Comments, that can be done on media such as podcasts, movies etc. etc.
- NIP23 - Markdown Notes
- NIP24 - Metadata Tags such as Web URL's
- NIP25 Reactions
- NIP27 - Tagging Users and other Events, uses NIP19
- NIP28 - Public Chat
- NIP32 - Labeling (Tags), just like what I use in Hypothes.is and Raindrop.io
- NIP39 - External Identity Profiles, like Github and Mastodon, like Keybase account proofs
- NIP40 - Expiration for Events
- NIP46 - Remote Signer
- NIP42 - Client Relay Auth
- NIP48 - Reindex Media such as ActivityPub, RSS, and Websites
- Check out Mostr to port your profile over to Nostr
- NIP51 - Lists, think Raindrop or Wiki Directory Hierarchy
- NIP52 - Calendar Events
- NIP54 - Wiki Pages
- NIP56 - User Reporting
- NIP57 - Bitcoin Lightning Network Zaps
- NIP59 - Gift Wrap - Encrypted event delivery
- NIP65 - Relay List Metadata, DM's won't work without it
- NIP68 - Images
- NIP72 - Reddit Style Moderation
- NIP73 - External Content ID's such as ISBN, and Movie ISAN's
- NIP84 - Highlights
- NIP99 - Classifieds (Quests)
- nkbip
- nkbip-01
- nkbip-02 - AI Embeddings
- NIP96 / Blossom - Nostr flavored File Storage
Nostr Client or try and integrate with something like nostrudel which seems like a beautiful produce and code base.
There is a Nostr Knowledge Base Project already under construction
- GitWorkshop: Alexandria
- Alexandria - wikistr
- NKBIP-01
- Use Relays, wss://theforest.nostr1.com and wss://thecitadel.nostr1.com
- NKBIP-02
None of this touches the real world or interfaces with my life
Why should people care about Nostr when they got their tailored infotainment feed manipulating their limbic system? All the attention is being socked up by Big Social Media.... Yet I need to spend half an hour trying to look for a meme that is on the tip of my tongue.
Selling is as important to software as developing it. The seeds need to be spread but how does one go about marketing?