Avatar
DanConwayDev
a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d
freedom tech developer and creator of ngit, https://gitworkshop.dev and https://metadata.nostr.com

I have found its really hard to get feedback. Its probably a reputation thing. The small number of core devs are probably tagged in more messages than they have time to read given the growth of nostr.

Working on a bounty or two might be a good way to build relationships?

Nostr is permissionless. Perhaps just broadcast a bunch of different sized messages to lots of relays under a fresh pubkey and see which ones get rejected?

Yes, I working on it. Check out my long form nostr posts. I'll post a prototype CLI in Rust soon. Happy to discuss on a call if you like?

the standard commands must be supported. Clone, pull and push could all be abstracted through a wrapper that receives and sends only patches over Nostr.

I should probably expand on this in a long form note so that my three other long form buddies can agree with me.

I'm not sure a grey or purple checks for a NIP-05 address is the best approach. The association with twitter's blue check gives the wrong impression of what sort of verification is happening. #[3]