No! At the risk of duplicating the conversation on the NIP PR nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 just opened:
In nostr:nevent1qvzqqqqqqypzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqqs9ydqwez3x2k3e5rk8tmjkumg5zgf6xf8054zudfru0m9cc0p6slsf4n332 I proposed we should add a Git repository 'set' with a default d=starred that acts as a follow list.
but maybe a 'standard' NIP-51 git repository follow list like that PR suggests is better. Would / should clients label this list as starred repositories? I think may git clients will want to inherit the 'starred' concept from github but I there is an overlap with reactions, zaps and a repository follow list.
We should definately add git repositories as a set.
BudaBit is using lists for git repositories so we should also build on their work nostr:npub1ehhfg09mr8z34wz85ek46a6rww4f7c7jsujxhdvmpqnl5hnrwsqq2szjqv nostr:npub16p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gq7kfhdw.
Login to reply
Replies (1)
To me sets with canonical names are an antipattern (see discussion in https://github.com/nostr-protocol/nips/pull/880 and the trouble we all had to prune the spec from these).
I think the concept of "starred" is just publishing a reaction to a repository (with a "k" tag of "30617"). Those can easily be queried later.
Following should be a simple list, either if you want to follow a repository to see everything that happens in it or someone to see their repositories and the patches they send elsewhere.
That should be the base and the simplest thing to implement. Sets are much more complex.
Organizing people and repositories in sets can be done (like for all the other lists we also have sets) but honestly that's more like a power user feature and we should postpone that to 2027 because there aren't even enough repositories today to fill a short simple list.