hodlbod on Nostr: The short answer is that it couples group ID to pubkey, making it very difficult (if ...

The short answer is that it couples group ID to pubkey, making it very difficult (if not impossible if the pubkey is used for other things) to hand off administration to someone else. NIP 29 is in most ways overcomplicated and only useful for enforcing permissions on nested groups. I disagree with how it's generally used. My approach with flotilla is very similar to your NIP, but it reverses the pubkey/relay relationship. The relay url should be the primary identity because that can change without getting into the key rotation problem. But relays also have a`self` field in NIP 11, which it can use to authoritatively publish events. This doesn't get in the way of moving to a new group or running backup relays, and it avoids all the nasty problems associated with NIP 72.