I suppose that this is the marketing cardinal sin, that nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 was writing about, yesterday. Nostr products are too often aimed *people on Nostr*, but that is actually a miniscule subset of the global userbase, and it's one generally uninterested in anything other than zapping and tweeting. That's why products that do things other than zapping and tweeting tend to get little publicity, on here.
We should be designing products that appeal to larger swathes of the potential userbase, including almost all humans on the planet, who have never heard of Nostr and don't care about it. They just want to do XYZ and are looking for a tool, for that purpose. They are not looking for a Nostr tool. And most Nostriches aren't looking for a tool, for that purpose. So, we need to market to the XYZ people, directly, with some Nostriches also falling into that category. This is a distinction with a difference.
No, you're conflating git with GitHub. Git repos are awesome and inherently decentralized.
GitHub is "free" storage and gitserver for git repos, from Microsoft, where people can go to search for particular repos and find repos to particular topics, to submit changes to the repos, or to chat about repos and write bug reports and stuff. It's the Nostr-y part that wraps around git repos.
We were thinking that we could come up with a Nostr-y git repo storage place and gitserver, that people could pay for with zaps, and make it so that you can login with a signer and sign commits with NIP-05s and stuff, and get notices over your npub instead of email and etc. Issues and discussions and patches are already available on Nostr, and we'd just tie into that.
But it doesn't make business sense, for us to do it for anyone outside of our team, if hardly anyone else is interested, as we'd be stuck with the costs and the work of a larger, more complex system, for no reason.
We have to know if there's interest BEFORE we start building. This is an *infrastructure* project, not merely code. That's why it doesn't exist, yet. Only a larger team, like we are, can build this effectively. We thought of it as a public service sort of thing.
Showing page 1 of
1 pages