#[3] did something happen to our blue checkmarks? On the branle.netflify.app client yours gone too, so it is probably not isolated to just me I presume?
#[1] This is an interesting idea. Is there somewhere I can read about how you define "nostr difficulty?"
fantastic! I have a blue checkmark now like all the cool kids. Thanks #[5]
right on! what's the exact name you want listed? it must only contain the following characters: a-z0-9-_. as explained here: https://github.com/fiatjaf/nostr/blob/master/nips/05.md
Sorry for my delay in reply. I will DM you to set my blue checkmark up too!
I think this is a pretty solid prediction. Great work getting i PoW relay setup!
#[1] how can I get one of these blue checkmarks on branle without owning a domain name? Is there a relay which offers (expiring) NIP-05 codes in exchange for lightning payment?
how can I get one of these blue checkmarks on branle without owning a domain name? Is there a relay which offers (expiring) NIP-05 codes in exchange for lightning payment?
Not that I know of. In general a video/audio conferencing solution that (client-side) blurs faces and disguises voices to allow for pseudonymous yet real-time collaboration is interesting. I wonder if such things exist?
For the address reuse problem, it seems to me like the main solution would be for participants in nostr who want to do payments to adopt (by convention) something like paynym or similar. Alternatively, if nostr has a simple way to switch out a pubkey for a new one...
Sorry if you are getting multiple replies @0xtr Branle seems to be lagging for me. But yes, Bolt12 and paynyms is interesting. Hopefully custodial-relay wallets are not really necessary.
for implementing payments, two questions:
1. for lightning, are you mostly thinking trusted/custodial (offered by the user's relay?) or something else?
2. since each nostr key can be used to create a valid bitcoin address, what do we do to prevent/discourage address re-use?