The problem of “do i want my work/git issue comments to be visible in kind1 social media clients” is an interesting one. I’m leaning toward no. nostr:note1tc7gpwraduq48c3qad50q3qn5y4wr2ss2l94ph4ejph5l50fvkusw9vkml
Discussion
i still think your subkey idea would have solved all this.
Although i only found this issue because of a kind1 comment… but i dont feel like thats right. It would make more sense if these replies were only visible in my git nostr client.
I think of it like: put the data in its own kind and then, if you really really want, publish a kind 1 that references the commit and includes an excerpt. This goes for pretty much any other stuff. This way it's a conscious choice each time to post git commits into the social timeline.
Representing other stuff data in kind 1s makes it almost impossible to create a client that exclusively shows the other stuff and not social stuff.
agree
pretty sure I would annoy a lot of my followers here if every github comment appeared in their timeline. I post a lot of github issue comments that most people won't care about.
people in a git nostr client might though.
Even if i was careful to send to just my git relay I'm sure someone would just rebroadcast it to be annoying.
I also don't want to create a new identity just to comment on git issues.
Exactly. People can (and have) made bots to do this automatically on a dedicated pubkey for those who really want social feed updates like this.
But they are totally annoying anyways lol I've followed and unfollowed a at least one
I don't like how the comments and interactions then get split across the original event and the kind 1 in this design pattern. Wouldn't it be better to use the infamous kind 6 repost instead of a kind 1?
The main mistake with kind 1 was giving it the number 1. No one would be debating any of these if short form public text notes were kind 26 or any other number. 1 probably shoulda been something more basic and common, maybe like display name.