{ "id": "0cc5bdae2be242b7dc3938db9e41aca41ba57f3f9f8e2ed95e0641520795fed7", "pubkey": "efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19", "created_at": 1788205249, "kind": 1621, "tags": [ [ "a", "30617:45835c36f41d979bc8129830f2f5d92562f5343d6feddd6f30aa79480730f26e:remote-nip07", "wss://nostr.bitcoiner.social/" ], [ "p", "45835c36f41d979bc8129830f2f5d92562f5343d6feddd6f30aa79480730f26e", "wss://nostr.bitcoiner.social/" ], [ "subject", "Consider using more privacy-friendly relays by default" ], [ "alt", "Git issue: Consider using more privacy-friendly relays by default" ] ], "content": "Thanks for building this awesome project!\n\nI skimmed through the source code—I see that relays that require NIP-42 auth for NIP-46 events seem to be not currently supported. Specifically this should fail for `nak serve --eager-auth` and `nak serve --auth` should be failing right now. It would be awesome to support it.\n\nPlease consider removing abandoned wss://relay.damus.io (it still works but admin doesn't support it anymore) and wss://relay.nsec.app, and possibly adding auth-only relay wss://auth.nostr1.com\n\nAnd since there are very few relays currently require NIP-42 for NIP-46 events for now, we could by default use these less private relays designed for NIP-46 (they store events for shorter periods of time; the latter requires authors or a p-tag in REQ):\n\n```\nwss://bucket.coracle.social\nwss://nrs.primal.net\nwss://relay.nip46.com\n```", "sig": "45f0a7a948f5dd4b7a0b70178ed04c97d48b531f53b461228561304b2bcc9b684cd7eba6ba07a84587d7b7d072170f281254b0276e46b1c54831ece095b39dc8" }