Replies (52)

Ok, will look into it insh'Allah, shouldn't be too hard. But I need free NIP-17 inbox relays more urgently tbh. So I can implement secure messaging. Would be nice if I could preconfigure Noornode for that.
I checked it out. Bro, it's soft-corn. And it's really in early alpha stage. So if there's no other real use case and no NIP or spec, then honestly, I'm not going to implement it yet. I mean, I couldn't even if I tried.
We can give NIP5s away to whomever for all it matters. That's not the point. It's how they get used in a trust relationship. It is simply easier for a relay operator to whitelist a nip5 domain at scale than it is to manage each individual npub.
Can't speak for other clients use case (although it seems related to trust scoring and access control leveling) but the aim I have with these is that @PodSystems is making children's content so we will want a kidstr relay + client which requires access level amnagment beyond what most clients are pursuing. @Constant has outlined some of the ideas behind getting there in their articles. Multisig (parent/child) npubs + nip5 id access leveling for different permissions types is a good way to manage this. A few examples could be: 1, #NoorNode uses nip5s to whitelist special otherwise paywalled bonus content from #PodSystems 2, #NoorNode hosts a group chat for SAIF that is nip5 whitelisted 3, #PodSystems uses nip5s for moderator access leveling. 4, we use nip5s for a sisters only relay 5, #NoorNode uses a nip5 to limit access to certain kind/post types on the relay (like only livestreams or articles). I will stop there but point is there are many use cases for this and it seems silly not to pursue the possibilities.
Animestr, all of the stuff at GitCitadel (or they will, as it's on the list to do), and... Dangit. I know that there are another couple but I can't remember at the moment. No "big" clients yet, but I don't care about those aside from being annoyed at their devs for not getting the utility and SIMPLICITY of implementing it.
So basically, all you need is a client that can handle multiple NIP-05 addresses and display them in the profile, right? Any other technical requirements?
It's pretty straightforward, you can check it out in my profile JSON or @ابو مريم's. It looks something like this: image Structure: content = JSON string with all the fields (including just the first NIP-05 for compatibility) tags = Array with all the NIP-05s as separate ["nip05", "..."] entries Other clients only parse content.nip05, so they see one. The ones that support it read the tags, so they see both.
Yeah the aspect of managing such information (extra nip05s, extra lightning addresses) is tricky in terms of functionality. We will see how to implement it.