demo of making the #headway issue tracking notedeck app ai-friendly the companion headway-cli tool talks to the embedded notedeck relay to interact with the UI, but also can work as a local issue tracker if notedeck is not open View quoted note →

extracting #headway business logic into a standalone crate. this will allow agents to interact with nostr-based issue tracking without depending on #notedeck. agents can use the cli to connect to the notedeck relay and interact with the board ui in realtime. if not using the notedeck relay it can just exist locally in a standalone nostrdb instance or connect to a remote relay for storage. this opens up the possibility of creating TUI issue tracking tools that exist independently of notedeck/relays but also can sync with them this is super decentralized way to use nostr, utilizing relays for backup but not requiring them. local first ftw. View quoted note →

another cool usecase for the #notedeck websocket relay: since notedeck/nostrdb unwraps giftwraps automatically, you can use the notedeck relay to subscribe to giftwrapped events like DMs. this is a handy way to access your nostr DMs in cli scripts while notedeck is running View quoted note →

slowly getting there View quoted note →

another idea: notedeck apps can register skills, then the embedded dave ai can know how to interact with any notedeck app by default. for example: when dave is building apps, it can see that notedeck_headway issue tracking is available, and automatically use that for tracking project issues. its like an ai-native, offline-first nostr browser 🤔 huge opportunity to reinvent how apps are built View quoted note →

the #notedeck browser's embedded relay can now be accessed via websockets. this allows you to dynamically interact with any notedeck app (insert/query notes) without needing any internet connection or external relay. going to use this to build clis for ai agents to interact with any notedeck app without needing external relays. View quoted note →

adding websocket relay support to #notedeck . this way you can read/write notes directly to/from the running app. this will be useful for building cli tools that interact with #headway, enabling ai agents to interact with the issue/project board directly without needing external relays. View quoted note →

gn

Just unfollowed like 50 people who haven’t posted in 2 years. No point sending tons of subscription data to relays for pubkeys that never post. View quoted note →

many are stimming on lisdexamfetamine to get ahead. few understand this.

Music on TIDAL

Bloc Party - Where Is Home (Burial Remix)

Listen to Where Is Home (Burial Remix) on TIDAL

chune

Whats cool about the notedeck_headway data model: its event sourced. Reduction of the board states is deterministic and order-independent, so replaying the whole log always yields the same board. This is also super efficient with nostrdb fold queries. This reduction happens as the query walks the index. No intermediate state and large memory usage when rebuilding board state. TLDR: shit just works and avoids janky replaceable events that overwrites previous states (like how contact lists get nuked all the time). This will enable collaborative kanban boards. View quoted note →

nostr board and issue model done. local first issue tracking! who needs linear/github/trello View quoted note →

added tasks ui to dave multi-agent coding dashboard making my own nostr-synced coding agent IDE is fun :D

View quoted note →

starting to think a temporary custodial layer on top of ark for async receive might be the cleanest non-custodial zap wallet implementation 🤔