NIP-05 is a group signaling mechanism, being able to block anyone with a nostr address from some domain should be an option anyway. I've been asking for this ever since the storm from nostrich.house

Reply to this note

Please Login to reply.

Discussion

So, is this a feature you’d like to see built on Mutable? I’ll consider it, but it might take some time for me to get to it.

yes please! Of course, no rush though. I do think it should be a standard, however.

What would we call this feature?

NIPless?

NIP-b-Gone?

NIP-eraser?

Do you want the feature to let you both mute and unfollow all users in your follow list with a specific NIP URL?

Something that makes it not sound like it's trying to go against the Nipponese lol - um.... NIPEraser or something sounds good.

That feature would be awesome, if having to mute every person you unfollow, that might be a nightmare depending on the length of the nip05 JSON file.

I hadn’t even thought about that. Glad I didn’t go with the word “nuke” in the title!

How about something simpler, like Domain Purge, since that’s what it would functionally do. Enter a NIP-05 domain name and it will search for anyone you follow with that domain in their profile data, so you can mass-mute and unfollow them.

This should be pretty straightforward.

That sounds awesome! Thank you heaps sir... nostr thanks you. And I do too!

Might do some airport vibecoding if I have time this morning.

Flight delayed…you might be in luck, guys.

đź‘€

True.. is very much group signaling but I guess depends on the amount of legit users on the NIP-05

If someone's allying with a domain that spams my periphery with noise, i really don't care about them and wouldn't bother validating their signal as a user in the first place.

Being able to have a nostr address point to so many free domains, and they choose the spammy one? No thanks, i'd rather block the domain by default. If they want to be seen by me, they're welcome to do the "work" and change out their address.

Its a bidirectional relationship as well. Maybe I only want to communicate/see users from @mynostrcommunity.com or want to block anyone that does/nt have a NIP-05. Its about enabling optionality and multiple types of barriers. What ultimately makes nostr robust as a whole ecosystem is that there's no single criteria to game.

You'll break nostr eventually if there's a singular best & unchangingWoT metric that all relays and clients use. Good luck doing that when every user, relay and client have even 10's of WoT algorithms to choose from.

Yup totally with you, being able to choose the notes you can and can't see through their domain affiliation is awesome.

Whitelist + blacklist for clients maybe, filter by nip05, not just WoT or relay choice but implicit rules like a firewall... small communities would love this so they can exist in their own pocket of the internet without spam or intervention from unknowns.

Surely this could be a model for more usage of nostr without nostr even being known to be the underlying tech?

On my freemium offering at NostrAddress.com it puts the free requests into an hourly batch before their address is live. It has mostly helped stop bots and bad actors as they don’t get the address immediately and have to wait.

On the relay side of things, after the reply guy spam, I introduced nip05 validation on Nosflare. This let you block any event who’s author didn’t have a valid nip05 and you could also block specific nip05 domains. I knew in the future there would be spam bots who would have nip05s.

It’s all a cat and mouse, whack-a-mole lol

Awesome! I'll have a look and spread the word <3 thanks dude