Yeah, of course, it is.
Discussion
He can't see what I write, so he always has to wait for someone else to pass it on.
We already do this, with nostr:nprofile1qqsq7pslujvn5pp3ggzje3qqfua45lyrnrfrsj68emztfe7qpzvwt6qprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz9nhwden5te0vaex2etwwdhh2mpwwdcxzcm99ukv33hp. If you attend the meetup and leave a good impression on us ladies, you get a badge.
And nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz8rhwden5te0w35x2cmfw3skgetv9ehx7um5wgcjucm0d5hsjmvd7t might start doing SW quality audits, with badges, since we have so many QAers on board. Maybe with different levels, like CMMi audits. Gold, Silver, Bronze, etc.
(But don't tell Karnage. It's a secret.)
That would be badges for repo events, not npubs, BTW. So, new use case.
But they would display on your repo and maybe we could get them added to zapstore, or something.
But, again, top-secret.
The super idea is that anyone with a npub can be a credential issuing authority. It’s one thing not to know who is the relevant credential issuing authority, it’s an entirely another thing to have to rely on a ‘certificate authority’ cartel to issue a certificate on your behalf and according to their rules. TBH, along with zaps, I find this to be one of the most exciting aspects of #nostr.
