franzap on Nostr: Gotcha, I was thinking along the same lines and we discussed this in one of our ...
Gotcha, I was thinking along the same lines and we discussed this in one of our design calls. I heard an argument against listing maintainers/contributors and that's leveraging natural abstractions: Fabricating a pencil involves a huge amount of people and they're not all listed in a single place, that's what the price system is for. You pay a certain amount for the pencil and the company internally distributes payments.
If a project requires this level of detail they probably should be using something like nostrocket. Thoughts on this gsovereignty (npub1myg…sn5p) ?
And again, I don't think kind 30063 releases should be immutable (file metadata definitely should). In all honesty, who do you think will be issuing trust attestations to an event pointing to binaries in 7 different architectures/platforms/OSs? Who would be vouching for all of those binaries at the same time?
If a project requires this level of detail they probably should be using something like nostrocket. Thoughts on this gsovereignty (npub1myg…sn5p) ?
And again, I don't think kind 30063 releases should be immutable (file metadata definitely should). In all honesty, who do you think will be issuing trust attestations to an event pointing to binaries in 7 different architectures/platforms/OSs? Who would be vouching for all of those binaries at the same time?