Replies (10)

No. I did that a few months back. Made a small scale proof of concept thing. A few days of work. Tried to get some feedback, but got nothing useful. Now, I made myself a client, to be at a resonable starting point. To generate keys and custom events easier if need be. I will not invest months into a this without a specified endpoint. I don't want to make a huge effort just to be ignored in the end, or to be simply told that's not what he had in mind, or that my approach is not up to industry standard. I'd like either a solid description of what he wants, or channel, a person of contact, that I can discuss my approach and progess with.
I pay a lot of attention at what's going on in nostr and didn't hear anything about your proof of concept, perhaps you didn't get anything useful because it was either too early to be usable in any way or you didn't promote your work enough? either way, I don't think you should "invest months into it" with no clear guidelines; the magic of nostr is that it allows for incredibly small, composable pieces, that are useful on their own. A single person/team doesn't need to replace all of github in one go, that's unreasonable/undesirable. Irreducible complexity is a byproduct of platform-thinking as opposed to composable, protocol thinking. Either way, I don't have any line of communications to jack and it sounds like that's what you're interested in so I won't waste your time, I just wanted to give you a different perspective in case it could be useful. PV
Carrying it further, if you don’t have an idea, find one of the projects that’s being built on #Nostr and contribute. Or fork. In both cases, you’re working on someone else’s idea or vision. If you don’t have an idea that sets your hair on fire to solve, best not to be the lead. THAT is how you waste your time. Best to be a contributor while you build intuition.
Oh yeah, I agree with whoever told you you’re recreating git, which is already decentralized-first, instead of GitHub. What needs replacing is the stuff GitHub offers on top of git
Many places, but storage != revision mgmt system 😅 If it were a matter of wanting to leverage nostr relays for storage and data distribution you would probably be better off just saving git blobs on relays and leveraging git enormous, decentralized-first, architecture. (To be clear, I don’t think that should be done)