luis

santa cruz, cali

twitter backup: https://www.luislopez.com/twitter/

Public Key

npub1nvktk6hxnm3qruh535x9q5nrtadpx7rfll9uw3pfry0cghde87ys3r797z

NIP-05 Address

luis@luislopez.com

Profile Code

nprofile1qqsfkt9mdtnfacsp7t6g6rzs2f347ksn0p5llj78gs53j8uytkunlzgpramhxue69uhkummnw3ezuampd3kx2ar0veekzar0wd5xjtnrdaksz8rhwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kqd2zp0t

Publishing to

nostr.walletofsatoshi.com

nostr.bitcoiner.social

Author Public Key

npub1nvktk6hxnm3qruh535x9q5nrtadpx7rfll9uw3pfry0cghde87ys3r797z

Show more details

Last Notes

2022-12-28 21:25:43

someone is going to need to rethink how the relays work once this thing starts to get the masses, and large file sizes. it doesn't seem it will scale cohesively. there's also the issue of transparent spam filtering. right now it's headed towards the same problems mastodon has.

2022-12-28 05:21:31

- reply

I don't think they are peering. right now, if you switch clients, you have to manually bring your relays with you or you lose access to data: followers etc..

2022-12-28 05:11:17

- reply

so there is dependence on certain relays staying up? in other words, I thought the relays could come and go and everything stays resilient.

2022-12-28 05:04:03

do the relays sync?

2022-12-27 19:17:51

- reply

🤙

2022-12-27 17:24:55

- reply

🤙

2022-12-27 17:12:59

- reply

tried all this. plus eliminated cloudflare. works on another server, but that kinda defeats the purpose of verifying against my own domain.

2022-12-27 16:10:43

what'sup with the nip-05 verification not working?
I have this file on my server: https://luislopez.com/.well-known/nostr.json
I have set the .htaccess for /.well-known for CORS: add_header 'Access-Control-Allow-Origin' '*';Control-Allow-Origin'
still not working.