npub is not supported here yet. Have to convert to hex. and get rid of these <>.
Discussion
This is the second time I've seen this angle bracket thing, is this in the spec or something and it's confusing people?
so jb... what is difference between blue and yellow checks (I think I know but asking to be sure)
I got this one:
Blue = verified people you follow
Yellow = verified people you don’t
so if we build a nostr platform our goal should be making things like verification, profile pics, etc easy and familiar for the public. I do think this is the framework that can drive the "everything app".. common e-commerce profile, email, social, search, etc.
yes - I left one in my noster.json and couldn’t figure it forever.
Should we support npub for nip-05?
I helped someone trouble shoot their self hosted nip 05 earlier today and this was the issue, so maybe yeah.
I was about to implement it in damus but I realized that would make verification incompatible between clients. I think it might make sense because its more of a human thing?
Definitely
Would it be easier to just make the public key hex on Damus? That way we can copy it directly from Damus and not worry about converting?
We should not use hex for client facing stuff anymore
#[6] and #[5]
Okay that makes sense. I refer people to Damus.io/key but this just seems to be the biggest issue. Not a huge deal, because we’re all here to help.
I wouldn't want to encourage that. There is https://damus.io/key if you need a hex key for some reason. I would rather update more tools to accept npubs directly
I’d rather see the protocol simple. Options tend to stack up and then you have a combinatorial explosion on your hands!
Perhaps a tool where you paste your npub string and your name and get the JSON back could make it easier for people?
We are deprecating hex
Is there a private offline way for me to convert my hex private key to an nsec key?
