Michael Dilger

String content and array order don't change based on different JSON serialization implementations, so signatures will match. JSON objects with keys may come out in a different order and screw...

> I get this! What I'm suggesting is to add a note in the corresponding NIPs to explain the reasoning. I support that.

> hosting git data directly on Nostr is a bad idea Agreed. Also the git protocol is a very efficient optimized for git, and git itself is already fully distributed.

> QQ: How do NIPs get numbered? What I've done is look through all the PRs, find the highest number, and go one higher.

Nostr provides redundancy if you utilize it. Dev B should post to more than one relay. Now the trick here is that people following the repo need to see Dev...

Either I don't quite understand several things you said, or I disagree, and I'm not sure which. I'm going to write this as if I disagree, but perhaps I don't...

Ok you are talking about replies to threads. I didn't get that. The 2-step I was talking about was learning about a person's relays which IMHO shouldn't be done over-and-over...

> I don't see any reason for a client to know what relays an author is generally reading from, as it's not displayed in the Iris UI. If I want...

I see the argument that you don't need to know someone's read relays nearly as often as you need to know their write relays. In fact NIP-65 started out without...

I like the idea. Is this done as a tag with URL + AES key? Is the AES key in the tag for everybody with the nostr note? I like...