what do you think nostr:npub16r0tl8a39hhcrapa03559xahsjqj4s0y6t2n5gpdk64v06jtgekqdkz5pl nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl nostr:npub1896p07z8xngpct5ma00mdrad4gqfnwfwdqcl706wrm25ajynahhs27x5ge?
I'm cooking something for nostr:nprofile1qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6vuxagm
Hey git loversdev, does this make any sense to you?
#nostrdesign #dev
Discussion
Ah, I noticed the nifty little flowchart at the top, when I logged in today. Like!
In nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk's previous iteration the order was 1) nostr, 2) ngit, 3) any git server, 4) gitworkshop.dev.
I liked that (and implemented). 1) nostr - the communication protocol, 2) ngit - git tool to interact with nostr, 3) any git sever, as thats still required but just to access the authoritative code, 4) gitworkshop.dev
> as thats still required but just to access the authoritative code
This make sense! Actually it is an optional part.
I will revert the design to the first iteration.