NIP-42 (Client Authentication) enables an unlimited amount of client/relay user level configurability. Simple use cases include but are not limited to private/paid to read relays, restricting access to DM metadata for unauthorized pubkeys, personal private clearnet relays (without needing to restrict access by IP), and paid subscription relays (patreon).

More advanced possibilities include remote relay management for administrators, bandwidth/usage metering by pubkey, remote privatekey management, and many more.

If you are interested in contributing, check out our feature requests and bounties here:

Damus: https://github.com/damus-io/damus/issues/940

Amethyst: https://github.com/vitorpamplona/amethyst/issues/354

☑️ Snort: https://github.com/v0l/snort/issues/520 (assigned)

Iris: https://github.com/irislib/iris-messenger/issues/364

Thank you to the awesome developers providing their NIP-42 ideas. I’ll keep retweeting other ones I see!

Reply to this note

Please Login to reply.

Discussion

Omg I said retweet someone kill me

Time to start over with a new account on the welcome relay

Literally. I don’t think there exists any path to recover from this…

Might as well start up twitter.nostr.wine now 😁

Do you see “the tweet” here in the room with you now sir?

Old habits die hard. 🤣 Retweet is the one that trips me up the hardest too.

Nostr typos are forever 😂

https://layernet.pages.dev GET WHITELISTED ( CLAIM REWARDS ).

Seamlessly

Connected

Blockchains

SAY HELLO TO LAYERZERO, AN OMNICHAIN INTEROPERABILITY PROTOCOL. LAYERZERO ENABLES THE REALIZATION OF CROSS-CHAIN APPLICATIONS WITH A LOW LEVEL COMMUNICATION PRIMITIVE.