NIP-05 handle related question πŸ™‹β€β™‚οΈ

#[0] registered a handle [at]nostrich.love which looks like this:

AshToHashes 24.0.1 πŸͺ’β›βš‘οΈ#FreeRoss

I can see the check mark on snort but not on Damus. Wonder if others can see it on the clients they’re using? πŸ€”

Should it be even possible to support this kind of characters?

Reply to this note

Please Login to reply.

Discussion

I see it on Damus.

Thanks for the info πŸ€™ For some reason I don’t, even though I cleared the cache

I don’t see it! What relays? Did they save their profile after updates to relays? 🐢🐾🫑

Thanks for checking πŸ€™

Too many relays!!! 70?is not good. Reduce down to under 20 or somewhere in that area. 🐢🐾🫑

18-20 seems like magic number. Relays seem more stable now too.

" NIP-05 assumes the part will be restricted to the characters a-z0-9-_., case insensitive."

local-part is everything before the @, so the username

https://github.com/nostr-protocol/nips/blob/master/05.md

I see… Thanks for sharing! πŸ€™πŸ’œ Gonna add these constraints to the api

Thanks for zapping πŸ’œπŸŒž

Exactly

It is because they have not sanitized the username, I think thant you have broken their nostr.json!!

Seems to be working though πŸ€™πŸ˜…

https://nostrich.love/.well-known/nostr.json

πŸ˜€πŸ˜€πŸ˜€

Try to remove the dots and emoji, at nostrcheck I sanitize first for security. In the other hand, is the best username that I’ve seen ever 🀣🀣

πŸ˜†

Is not broken, but this usename (I think, will not be valid)

Shows on snort though (I can see the check mark)

Anyways, gonna have to add proper constraints to the service, as I’m the one developing this πŸ€™

If you want we can talk by DM and I can send you my sanitization function πŸ˜€