Eh, it depends though, doesn’t it?
A nip-05 on your company’s domain is presumably “verification” (for lack of a better term) that you do in fact work with the given business. At least in the majority of non-adversarial situations, where you can expect a company’s domain/registrar isn’t compromised.
A paid nip-05 is “verification” that you’re willing/able to spend a few sats, and are therefore much less likely to have come from a bot farm. Proof-of-funds if not perfect proof-of human…
A free nip-05 is, I agree, just a unique username. Coming from legacy social media, it’s going to take time to re-educate on how identification “works”. I expect that will happen in tandem with nostr clients becoming more versatile (and/or perhaps more standardized) in terms of how they display user profiles and handle search.
In the transition from legacy social media to nostr/keypair-based communication protocol, people will want to give their legacy followers a familiar way to find them - so if I “verify” in a Twitter post that you can find me at sexynip05@nostr.love, it provides a unique/reliable way to find me, for users who aren’t familiar with the concept of keypair crypto.
Is it less resilient and censorship-resistant? Of course. And those are important parts of what Nostr is about. Ideally as new users enter, it will pose opportunities for more and more people to learn these concepts and why they matter, such that maybe in 10 years it will be as commonplace as knowing how to attach documents to an email.
I’m curious though, if there’s a significant hole in my thinking here Semi?
bostonwine / boston wine
npub14q…e2q26
2024-08-30 16:25:05
in reply to nevent1q…6vr3
Author Public Key
npub14qz92uedt0a8jte8jqg63jr3s5cc99cej36jh883z6tprlu354uqqe2q26Published at
2024-08-30 16:25:05Event JSON
{
"id": "9ad75e43d98c61a0c2c13f7b1dcdbcf6529729dc63c248cdd80aedc61d80ca49",
"pubkey": "a80455732d5bfa792f279011a8c871853182971994752b9cf1169611ff91a578",
"created_at": 1725035105,
"kind": 1,
"tags": [
[
"e",
"1c5f4f0bada25a8a61322ba2bac13e437c2a254fafc6d3270b3a8dbd548c205b",
"wss://nos.lol",
"root"
],
[
"e",
"f2a56253864960f5207911f60459ab2a778b486a3babc76a765d9727c7e4bc79",
"",
"reply"
],
[
"p",
"e0e92e542d79b28e79c6efe95891d38f49636e48560a8e618b953bded630dfaa"
],
[
"p",
"52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd"
]
],
"content": "Eh, it depends though, doesn’t it?\n\nA nip-05 on your company’s domain is presumably “verification” (for lack of a better term) that you do in fact work with the given business. At least in the majority of non-adversarial situations, where you can expect a company’s domain/registrar isn’t compromised.\n\nA paid nip-05 is “verification” that you’re willing/able to spend a few sats, and are therefore much less likely to have come from a bot farm. Proof-of-funds if not perfect proof-of human…\n\nA free nip-05 is, I agree, just a unique username. Coming from legacy social media, it’s going to take time to re-educate on how identification “works”. I expect that will happen in tandem with nostr clients becoming more versatile (and/or perhaps more standardized) in terms of how they display user profiles and handle search.\n\nIn the transition from legacy social media to nostr/keypair-based communication protocol, people will want to give their legacy followers a familiar way to find them - so if I “verify” in a Twitter post that you can find me at sexynip05@nostr.love, it provides a unique/reliable way to find me, for users who aren’t familiar with the concept of keypair crypto.\n\nIs it less resilient and censorship-resistant? Of course. And those are important parts of what Nostr is about. Ideally as new users enter, it will pose opportunities for more and more people to learn these concepts and why they matter, such that maybe in 10 years it will be as commonplace as knowing how to attach documents to an email.\n\nI’m curious though, if there’s a significant hole in my thinking here Semi?",
"sig": "284b7ac9a623ff78494d5b6ee85a1a404790c05364f2456f6ecf3169a286786dc7c7c26dd1c5001249c254e083dd0fa2a4f633567630c4828117fb0af2a6a93e"
}