given that nostr acts as glue, we don't need one or two githubs using relays as backends; we need disparate tools that accomplish one task really well for some people and interoperability
rebuilding github in nostr has been misunderstood as building github with a nostr backend, which misses the point, like creating a car and put a horse in front of it to pull on it
so nostr is just a protocol for creating infinite payload standards, aka nips? and clients can follow those nips and use the payloads to create useful, interoperable apps. but creating an app that misuses existing nips is bad form. good way to read this?
oversimplifying, i know other things are defined in nips.
Sooo… about that workout app… whatchu doing next weekend Pablo?? 😂
Traveling to japan 😅😅😅
Separating GitHub into a bunch of different microapps is not what Jack asked for. That’s not very user-friendly! 😅
We should maintain backwards compatibility with both git and #nostr
I think we need a self-hostable nostr version of github. Not just one or two sites with relays as the backend. But how would nostr github work as a dozen of microapps? How would you separate them? How would you use them?
