Recommendations: store the issues in the git repo itself. New issues are “pull requests” to the main repo but ux should abstract that away … (Pull requests are really just metadata about a branch’s link to other branches.)
Use nostr for discovery, profiles, reputation, and other types of metadata.
I’d recommend not hosting files on nostr, but merely point to a git repo hosted at a public IP/domain or attempt some kind of NAT hole punching.
O wait that website is nostr? I haven't had a chance to figure out what nostr is but I didn't think it would be so user-friendly. I guess it depends on the client host, also I sent 50 sats to jack for fun does that mean lightning is built into nostr or is that just something the client implemented?
That's an interesting bounty because it challenges one of the weak points of Nostr, long-term storage & data availability. A git repo means nothing without 100% of the history present. So how do you incentivize relays to store all the commits? Let's see 👀!
Recommendations: store the issues in the git repo itself. New issues are “pull requests” to the main repo but ux should abstract that away … (Pull requests are really just metadata about a branch’s link to other branches.)
Use nostr for discovery, profiles, reputation, and other types of metadata.
I’d recommend not hosting files on nostr, but merely point to a git repo hosted at a public IP/domain or attempt some kind of NAT hole punching.
Haven't looked more into this, but there is project about doing bug / issue tracking in pure git itself - https://github.com/MichaelMure/git-bug.
Also, meta issue about decentralized / federated GitHub alternative - https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/1302.
I remember coming across git-bug when I was building https://gitern.com ... It's how I was planning to do issues.
deleted by author
deleted by author
Why not though? A relay might advertise that it's willing to host git files.
That's fair actually! I was mostly saying don't store git repos as nostr messages.
deleted by author
deleted by author
deleted by author
Holy moly. I'm jumping in that one!
What programming language are you going to write it in?
Dunno. Buy a lot of typescript for sure
deleted by author
deleted by author
I know right! Need to look up a quick tutorial now LOL
deleted by author
deleted by author
what is snort?
A nostr client
O wait that website is nostr? I haven't had a chance to figure out what nostr is but I didn't think it would be so user-friendly. I guess it depends on the client host, also I sent 50 sats to jack for fun does that mean lightning is built into nostr or is that just something the client implemented?
Either the client, or the user includes it in the profile bio.
Nostr is a decentralized protocol for social networks.
but wow exploring Nostr now its pretty amazing. it makes you wonder why Elon would say lightning wouldn't work for twitter.
deleted by author
ps what do you prefer stacker or nostr?
They are two very different animals.
SN is not (yet?) decentralized and the its goal is not to be a twitter, and that's a good thing.
Fair point its more of a reddit I guess.
deleted by author
deleted by author
deleted by author
deleted by author
deleted by author
deleted by author
deleted by author
That's an interesting bounty because it challenges one of the weak points of Nostr, long-term storage & data availability. A git repo means nothing without 100% of the history present. So how do you incentivize relays to store all the commits? Let's see 👀!
deleted by author
Use this, but swap out the code to access Github with code to access Nostr relays. And replace the Bitcoin-related code with some sort of Nostr code.
deleted by author
Did this ever get accomplished?
deleted by author