the git repo announcement event (30617) is a small and infrequently updated event designed for discoverability. It should live on relays that store pubkeys relay lists and metadata.
Its less overhead for relays and clients than if we designed such that each repo had its own pubkey.
What happens if the the top 5 big relays censor anyone publishing events with Bitcoin code in it?
There will be some types of relays that just archive everything
more relays
How do you discover these relays automatically?
There has been tall about putting "accepted kinds" into NIP-11, which would be the first step to making these relays discoverable if I understand the problem correctly.
Updated answer: NIP-22 via NIP-66
See `k` tag in `30166` event.
What do you mean by in it? These events just have metadata about where to find the code and are used as the root event to reply to with issues and patches.
Are you suggesting these will be censored? If they were, wouldn't the maintainers npubs also be sensored along with their NIP-51 git relay lists that you were suggesting?
Clients could follow the huluristics about where they might find events from those users and look for the announcement events there.
