And maybe accept npubs in filters too, why not? What else, Markdown on notes, HTML, editable notes? HTTP relays? Keep it coming. Let's make Nostr "flexible".
Discussion
Exactly! It’s not hard to identify npub as npub, so are the other things! 🐶🐾🫡
The issue is that no one knows what hex is these days. We all moved on to npub's and left this spec behind.
I feel like users don't. But the service runners do, straight. They can convert their npubs on the fly, and still chill the protocol way #timechain
I agree with that, but the amount of people who will be setting their own nip05 manually and do not know the difference between hex and npub is likely very small. It's not worth bloating the protocol because of that.
The people you're seeing are using self-hosted nip05s? Where are they? Maybe these services that host nip05s for others should start validating their input and converting npubs to hex before serving.
Some self hosting, some services. Too hard to debug and fix for users since no client offers hexes anymore. :(
What services? We can talk to them and ask them to fix their servers.
https://void.cat/d/Js1GLuw1z5V2cBakzVqo4a.webp
https://void.cat/d/8TJFW3ZnbNWHhAZBPurKDD.webp
There are many services out there which are confusing users with wrong information. Is not about not knowing it needs to be in hex.
I found one that says "Some clients may not recognise your public key as used above and you may have to use your npub key instead".
Unfortunatelly apps are not converting to hex anymore (IMO it could appear in the profile) and https://damus.io/key/ is a rare exception. Other sites that said they would convert (in some documentation) doesn't do that anymore.
https://nak.nostr.com/ does the conversion.
What is that first site? It's so completely wrong.
The second one is nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc's https://nostr.how/.
The first one is this: https://thebitcoinmanual.com/articles/nostr-account-nip-05-verified/
Dont forget pinnes 📌 notes🥰