I actually started off writing a Python CLI, but my interaction with you was so productive, that I was like,
Why do this twice? 😂
And, as you can see, we need to match at the CLI level, or the events will eventually lose interoperability.
I actually started off writing a Python CLI, but my interaction with you was so productive, that I was like,
Why do this twice? 😂
And, as you can see, we need to match at the CLI level, or the events will eventually lose interoperability.
There is so much design space in #GitViaNostr, so few of us working on it and hardly any usage, that it makes less sense to duplicate functionality right now.
It is somewhat inevitable and eventually healthy when things are more mature as projects die, new projects do things better or on different stacks, etc.
Yes, I think this realm isn't mature enough to handle competition on that level, yet. We're still working through the kinks in our own NIP-01, basically.
If we diverge too much, now, it's gonna be a shitshow and turn people off of the concept.
We should probably compete more on sw features, than on core event kinds.
Yes, at a protocol level (event kinds and format), it is almost never a good idea to diverge.
Product/ project manager experience taking
Yeah, sorry. Used to managing complex sw projects and it occasionally leaks out.
Ngit silos just sounds like a train wreck. 😂