I can sometimes get someone to create a Nostr event for their git repo, but because they leave the issues open on GitHub, they never go look at it.
I post issues and get no response. Or they ask me to repost on GitHub because that's better for their statistics.
Live-view of me, using NIP-34.
Maybe I should post GitHub issues that only include a link to the Nostr issue?
Or is that rude?
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.
I have no idea what any of this means but I feel you
We have a monumental software project, that everyone feels really excited about, but I'm the main person using/testing it and I can't figure out how to get anyone else to join me.
There's no incentive to use it, until it's really good, but it won't get really good, unless we all use it.
Catch 22.
Hmmm that’s quite a predicament. What is it about it that makes people excited?
Would it help to have a non-dev, but tech literate guy like me use/test it with you? If it is anything to do with Project Alexandria, I am 100% down.
Yes, it will! ☺️ We actually hope to have a first alpha release out for testing, within a few weeks. We had to go back to the drawing board and fiddle with the design, some more, after we changed the spec for the events we're using. I'll issue a call for testers in the note announcing the version.
But that doesn't really help with my core problem that only a few repos (including ours and those from nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr ) are getting responses from the repo users and maintainers.
Can't help with the GitHub woes, but will be standing by to test the alpha build once available.
I'm not worried. so long as we have enough usage to continue improving the tools, eventually there will be waves of adoption. The value proposition is there, the trends our on our side and we will grow as nostr grows.
I'm the trend, Dan, and I'm getting exhausted. 😅
Your contributions are and have been invaluable. Ideas, testing and feedback, publicising and creating a conversation, work with nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz...the list goes on.
Particularly during this early phase before there has been much interest. You have created momentum.
Hopefully #GitViaNostr is entering a new phase with workable tools and more interest.
I don't know how you manage to be always be online and always posting! Pace yourselves because it sounds like burnout is a big think in the bitcoin and nostr space.
maybe it is harder to look out for one another being in non-IRL communities.
I literally gave up my day job and my kids are on summer vacation. But both of those are about to change and we're moving house this month, so I won't be able to keep up this pace.
I gave it a good 6 months, to help get it going. Was worth it. Sometimes you just have to buckle down, for a bit.
But, yeah, this is my plea that more OtherDevs focus on actually using OtherStuff, rather than only building it.
Even if I ping them on Nostr, they respond elsewhere, instead of under the issue, so it looks like I'm talking to myself.
I've had a pretty good response rate to issues posted via nostr. Then again, I am not a prolific nostr tester and issue raiser like you are. Can you post some examples issues? the clearly 'mileage may vary'.
Even my own team. Been like pulling teeth. 😅
hrmm. thanks for shaing. I wonder whether they are not getting notifications in the clients they are using or whether, as its not in the main place they manage issues, it doesnt get seen.
The idea of a bridge so that you could look at nostr for all the issues has come up to address that second problem, but that has its own challenges.
It would probably help a lot, if they had a personal feed on GitWorkshop, actually. Like, my guys are responding to some repos, but not to others, because they're not actively working on those and forget to check on them.
I also have to click on like 10 repos, to see if someone responded. I sometimes miss notifications, even if they are sent, because I get drowned by notifications, sometimes.
there are a few usecases here: 1) discovery of new interesting content on git 2) notifications of content I have indicated I'm interested in; and 3) Inbox style - messages I definitely need to be looking at.
I'd like there to be experiences for all three on GitWorkshop.
I completely agree that notifications just for git related things is needed.
I haven't forgotten about this as a more PR focused inbox for ngit is also important
I'm reminded of the workflow of Greg Kroah-Hartman as discussed here https://www.youtube.com/watch?v=vyenmLqJQjs and how CLI tools (eg ngit) could aid in the workflow of maintainers.
Just a nitch client showing these NIP-34 related events (notifications) would be very helpful to have 👀
This can replace all the emails I have sorted out with labels from Github and Gitlab issues and Drupal.org issues (which is many)
Agree. Like, I can't go looking in 5 different repo issue lists twice per day.
I have important shitposts to write.
I totally hate the emails. I don't even open them, I just see the name of the repo and then go to it and read there.
Didn't nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s want to get emails turned into notes to a NIP-05, or something?
Could we use kind 1111 for that?
no I just wanted mail on nostr, not convert email to nostr. it's really just a UI/design thing
