ETL to QE, Update 44, Revising some constraints
Date: 2024-10-20
So what was our scoped mission statement?
I want to be able to publish what I this the content of my Obsidian Vault, with version control, as Nostr Events and Multiformats IPFS CID Hashes as references to content such as images, videos, and files.
So what happened to make you revise those constraints?
Discovering NIP19 Nostr bech32-encoded entities
NIP19 is used to reference other nostr events, accounts, and profiles inside the content of nostr events and is also used by clients to identify, route to, and show events.
If nostr events could be shared as Markdown links with the nostr bech32 code rather than a URL I would be able to easily publish this blog to traditional nostr clients.
Discovering NIP54 wiki events with implementations nostrudel, wikistr, and wikifreedia
Perspective matters most when developing in an open space
I was trying to encode NIP19 URL's manually rather than looking inside nostrudel, nostr-tools and wikistr's source code.