๐๐
We can't allow #[0] to easily run away with new features...

๐๐
We can't allow #[0] to easily run away with new features...

Nice. This will make it so much easier to follow in person!
Hey Vitor, I tried using your client but I couldnโt find peopleโs pubkeys anywhere. Is it hidden on purpose?
๐๐ค
#[0]
true. we must chase.

Should I be putting the "nostr:" part? I honestly don't know if other apps are parsing those URLs. If they are, great, I'll add it.
What about sharing nprofiles instead of npubs?
That way the relay information could be used to check if some relay must be added to follow the user properly.
If you look closely at the picture I posted, you can see that I do including the QR code for it (which is quite large).
I did see at the bottom the text "N-Profile", but didn't see any QR, sorry.
Nice to hear you also generate nprofile QR!! ๐
perhaps there should be a timestamp component to the nprofile QR code, in case clients accidentally scan old QR codes with outdated relay info
I like the idea, but a timestamp doesn't really indicate something has expired unless there is a policy to make a new one every N days. And 'nprofile' is defined in a NIP without having a timestamp, so you'd have to debate some people to have that changed. If you wanted the QR to contain things other than nprofile, then other clients wouldn't understand. So I think this isn't going to work.
The way.
Ngl, you literally created a master