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. @elsat 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?

There are the two people I see pressing into these ideas the most

I also think @Alex Gleason might invent fire

Its not Shakespeare or Ditto or Nostr Station or NostrOS. But its users expressing there creativity with other. creating their own experiences. UI and UX totally curated by the user.

Heresy! Are you just trying to stir up controversy because nostr is devoid of it this week? In terms of theatre, its second only to the syphon https://www.youtube.com/watch?v=mvmRtPGR4C4

More issues / PRs are showing up in the counts now. That's a cool design decision to show issue / PRs from other sources. Are you using https://nips.nostr.com/34#status for issue / PR status? The statuses aren't showing on any PRs/Issues on that gitworkshop repo.
I'm also getting inconsistent grasp / relay lists for the same repo.


the repo announcement event uses (3 of which are grasp servers):
```
[
"relays",
"wss://gitnostr.com",
"wss://relay.ngit.dev",
"wss://ngit.danconwaydev.com",
"wss://relay.damus.io"
],
```
are you showing the relays / grasp servers you are actually fetching from?
Thanks for fixing the announcement event shape to match nip34 and cleaning out alot of the clone urls that wouldn't work. This is much better. You are still listing 5 grasp servers as relays only. Most of these won't accept your event because you dont list them in the clone or push a valid state event and git data within 20mins. ```
[
"clone",
"https://git.gittr.space/npub1ruxskh0xm6gags4mpc5x50gnag4m9zkyysmprm9f9y63p0rz2t5q0ffu7z/tmptestgittr.git",
"[email protected]:@npub1ruxsk.../tmptestgittr.git"
],
[
"relays",
"wss://git.shakespeare.diy",
"wss://ngit-relay.nostrver.se",
"wss://git-01.uid.ovh",
"wss://git-02.uid.ovh",
"wss://gitnostr.com",
"wss://relay.ngit.dev",
"wss://ngit.danconwaydev.com",
"wss://relay.damus.io"
],
```
When creating an repo from scratch you try and sign a state event but ommit a commit id under `refs/head/main` which is in an invalid state.
```
"tags": [
[
"d",
"tmptestgittr"
],
[
"refs/heads/main",
""
],
[
"HEAD",
"ref: refs/heads/main"
]
],
```

this is how the gitworkshop repo looks on gittr:

and on gitworshop client:

See how the Issue and PR counts are wrong and its showing git data (tip of main) 8 months out of date?
Gittr lists 16 repository relays 7 grasp servers whereas the nip34 announcement event only lists 4 relays, 3 grasp servers and 2 additional git servers:

vs

when i click on issues it shows 76 open and 0 closed:

compared to 12 open, 78 resolved and 24 closed on the gitworkshop client:

Gittr still mades malformed nip34 repo announcement events. ie.multiple `clone` / `relays` tags rather than 1 tag with multiple values. it also includes 16 clone urls including non existing ones such as `[email protected]:<npub>/<id>.git`

I can understand how it could feel this way. I think the lack of compatibility with the NIP-34 ecosystem is is holding back users of other git nostr tools from using gittr.