Hopefully in the future, you can choose certain letters in your Nostr pubkey when you generate it, so you don't have to wait hours for an automated program to generate millions of them until it eventually lands on the right one.
Discussion
If this happens you won't even need NIP 05 anymore.
I don't think so, NIP-05 just makes it easy for a human to find you and make sure it's actually you. Someone could generate another Nostr npub that has the same 5 characters as your original one, without NIP-05 you'd have to compare the rest of the npub just like you do today.
Also the only way to generate the stupid things is by brute force, but there's nothing stopping a client dev from adding that ability into the client sign-up. It would delay the process by however long it takes to strike one and it doesn't really solve anything, but it looks cool.
Choosing the first few characters of your pubkey accomplishes the same thing. It doesn't matter if other people can generate the same thing, that also applies for NIP 05.
It's similar, but NIP-05 also has the provider verify it's indeed you by having a file that links your npub to the you@theirdomain.tld.
If I change my NIP-05 to aspartame@nip05.social, clients won't show me with a verified tick, because when they check with nip05.social, aspartame@nip05.social is linked to a different npub than mine.
But each key is also unique, so I don't see the difference, aside from the check mark.
It's just easier for people to see a tick and recognize the bla@bla than it is for them to remember this: npub17e6l6tp789hwwnugm3l6zmgfffh369lv08yfuwj452hflhc530xq36epc7.
Once wider adoption happens, it will also help organizations verify that it is indeed them by having NIP-05 off their own domain (e.g. Google could be google@google.com)
Anyone could generate something that looks like npub17google789hwwnugm3l6zmgfffh369lv08yfuwj452hflhc530xq36epc7
True, NIP 05 is better for an actual important person, but that's not how anyone is using it rn.
What are you talking about? It's seamless