Maybe I should post GitHub issues that only include a link to the Nostr issue?
Or is that rude?
Discussion
Like, I get the statistics, thing, because most devs use GitHub, and potential employers lurk there, so having more activity there raises your repo "page rank" and allows your GitHub follows to see that you've got active power users. If we move the issue activity off of GitHub, you lose that cred.
GitHub is a social network that is simply much much bigger than Nostr. Especially since most Nostriches are also on GitHub.
But this is not a problem only for current devs. It's the hurdle we face, getting anyone to move, so we should maybe fix it.
nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr Have you thought about this?
Yes. I'm hoping that use of #GitViaNostr actually becomes a positive singal to employers of a understand of open source and open protocols.
There is plenty of spam and low quality PRs and code on github. employers know this and will see through it.
I think contributors looking to work in freedom tech and open source focused communities and business would be better of using #GitViaNostr where possible.
Interesting point. Accurate, I think. Putting your code where your mouth is, so to say.
If they are already on nostr in don't think it is rude.
I might do that, then. Maybe they aren't looking at GitWorkshop because no one was posting in their repo, there, and they lost interest.
This is an example of progress. We just need a few more nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz9mhxue69uhkummnw3ezuamfdejj7qg6waehxw309ahx7um5wgh8g6r9wdsk6etrv96zu6t09uqsuamnwvaz7tmwdaejumr0dshs9h69jx's out there nudging people towards creating issues on nostr and adoption will increase and then hopefully snowball. Thanks nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz9mhxue69uhkummnw3ezuamfdejj7qg6waehxw309ahx7um5wgh8g6r9wdsk6etrv96zu6t09uqsuamnwvaz7tmwdaejumr0dshs9h69jx
I am trying to slowly move over to gitworkshop, since its going to be so much better than github mostly because users don't have to create an account to open or share an issue
however I wont respond to any of the issues there until it implements NIP-22. Its ideological but I don't like kind 1 being used as the reply kind :)
Is that the generic reply kind? Why clients support notifications for that?
*which. I realise that typo changes the meaning of the question.
none yet. but I'm planning on adding support for it in noStrudel for replying to articles and wiki pages, so that will be at least one client
This is the challenge. Clients aren't incentivesd to support it because most clients don't publish with it. Clients don't publish with it because most clients don't support it. Catch 22.
A catch 22 is still better than using kind 1 for everything :)
If nothing else then I will try to break the catch 22 with noStrudel
Should we all just use the NIP-22 generic comment thing?
I would love to see a future where we reply to kind 1 notes with NIP-22 replies, then pulling the "default" social feed of kind 1 notes would be so much cleaner
but transitioning to that will take some time and coordination on the part of clients
We need NIP-22 for our books and gitstuff. Don't want everyone replaying with kind 01s, but that's all there is, now.