Redistributing Git with Nostr
12 points by fiatjaf
12 points by fiatjaf
Since the "Issues" GitHub feature is just a bunch of text comments it should be very obvious that Nostr is a perfect fit for it.
nostr.com says "[relays] can decide what to store and for how long". How would I go about storing issues in Nostr with the guarantee that relays won't simply forget them?
It's the same as storing issues on GitHub, nothing guarantees they won't be lost there.
But in the case of Nostr you may have 3 relays, say, github.com, gitlab.com and bitbucket.com, and your issues can live on all 3 at the same time. Now the likelihood of they all vanishing with your data is much lower, right?
Finally, there is always the option of self-hosting or combining self-hosting with corporate hosting or community-hosting and so on.
My understanding is the data typically gets replicated to other relays. Hosting a relay is easy (I did it briefly), so at the very least you can guarantee your data doesn't disappear. Otherwise, it seems like there's an ecosystem of paid relays that are reasonably unlikely to forget your data, though I've never used or looked into their services.
SourceHut has reminded GitHub users that Git has always had this (for most) arcane git send-email command that is the original way to send patches, using an once-open protocol. Turns out Nostr acts as a quite powerful email replacement and can be used to send text content just like email, therefore patches are a very good fit for Nostr event contents.
Try Discord