On top of the NIP-34 issue spec, ngit and gitworkshop currently support these three extra features: 1) post issue creation labels/tags, 2) editable issue subjects and 3) CoverNotes - editable pinned note with version history designed similar to an editable issue description. Here is the spec I am using: https://gitworkshop.dev/danconwaydev.com/gitnostr.com/gitworkshop/tree/main/NIP.md#shared-issue-patch-pr-metadata

Can you expand on 'any form of free communication may require compute power in the future'?

I like this approach. Significant effort goes into curating NIPs, I'd like to be able to delegate my 'view' of the NIPs to a committee and publish variations for specific NIPs. This way my overall view doesnt go stale. I'd also like to inspect other people's view, particilar their explicit variations.

How did you lose it?

They were empty. Isn't it a nicer user flow to use a default set (that amethyst automatically updates based on the relay landscape) when the user hasn't signed the corresponding events? I don't really want to sign an event to just enshrine defaults.

I also get this to the extent that I've learnt to recognise about 10 users by their .

Thanks for the ngit shoutout on . Is this the nicest thing you have ever said about a nostr client name?

i *think* nostrhub.io only uses the first listed server so it makes sense that it doesn't work for your repo when git.shakespeare.diy is down.

hrm🤔 I've been getting CORS and 502 errors git.shakespeare.diy but I've had no problems with relay.ngit.dev and gitnostr.com (the two that i run). Your screenshot showed relay.ngit.dev reachable but maybe just slow? I wonder if its geolocation related? I need some better montoring. and I have discussed this. I'm thinking about using a NIP-66 variant that probes grasp functionality too.

No. What sort or issues? What sort of timeframe?