I wonder if clients should enforce that, for now, once the user has a nip-05, the username must be the same as the nip05.
Handles in centralized platforms like twitter makes sense because they are unique. Since usernames aren't unique, I tend to think they should not be used. What is the benefit from UX standpoint where @someone may be 100s of different people?
fluizsp / Fábio Luiz
npub1d5…ajnx4
2023-02-27 15:06:05
in reply to nevent1q…wwxt
Author Public Key
npub1d5s32lzg6a0c49u42tvmz9s0v6ldv6mkm4rcsmwmj9qprsk6rpqs0ajnx4Published at
2023-02-27 15:06:05Event JSON
{
"id": "0a53579102f474dc146898864439a1635473018b6baa63cc90f327a4802fef27",
"pubkey": "6d21157c48d75f8a979552d9b1160f66bed66b76dd47886ddb914011c2da1841",
"created_at": 1677510365,
"kind": 1,
"tags": [
[
"e",
"87887d3ae908fecd0b53341a6787631e60605f1ebabbd4ffcbb589316347b1b7"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
]
],
"content": "I wonder if clients should enforce that, for now, once the user has a nip-05, the username must be the same as the nip05.\n\nHandles in centralized platforms like twitter makes sense because they are unique. Since usernames aren't unique, I tend to think they should not be used. What is the benefit from UX standpoint where @someone may be 100s of different people? ",
"sig": "1b45c39b8abd50bee14742f2e4f33f0d1be37aa62422ec1428518a19b6c60df11c9d4a805c1e93aef0ed74c7db5dd7bb1d4bdb96a479bb04aa444b307561a81d"
}