rich1.0DanConwayDev (npub15q…cyejr)https://nostr.now/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejrnjumphttps://nostr.nowThe intent of `git repository announcement` kind `30617` events was to claim ownership of a repository and indicate that you are accepting Issues and PRs via nostr. nip34 reads: > \[git repositories\] existence can be announced using Nostr events, as well as their willingness to receive patches, bug reports and comments in general I expected that announcement would either reflect this or be intentional affinity scams by bad actors which could be weeded out as spam. I now think the intent is not very intuitive as most repositories on github are private forks for creating PRs or hosted a patch just for that user. Some users created an `announcement` event as they tried to figure out how to do a PR. Some users wanted to send Patches or Issues to a respository not using #GitViaNostr as a way to encourage them to use it and created an `announcement` event for this. Trying to enforce a non-intuitive original intention on a permissionless protocol like nostr is like pissing in the wind. Maybe we should add some flags to the announcement event to enable announcing someone else's repository? Github has the concept of pinned repositories which seems relivant here.