...when using noscl to test the relay
I'm able to terminate tls requests when I stand up a little python oneliner file server on the box, so I think I have the proxy well configured. I'm still seeing "error adding relay 'wss://
right on, thanks!
I'm using the docker-compose.yml in the relayer repo to build and launch the relayer server and postgres. the whole setup is running in an ubuntu 20.04 droplet in digitalocean. using nginx as a proxy, with letsencrypt certs.
I'm standing up a relay. please shamelessly self-promote an option. I'm currently going with https://github.com/fiatjaf/relayer
so heard and followed
thank you, followed
void where prohibited
๐
reply to this if you're listening, I'll follow back 
if you are still stuck on that, try #[4] 's rundown: https://gist.github.com/metasikander/609a538e6a03b2f67e5c8de625baed3e I was missing the CORS header on my nostr.json.
thank you, this worked for me. I've been monkeying around with this trying to get it to work, this got it done!
an amazing demonstration, thank you!
*bro* do you even
# markdown?
mentions are working brilliantly #[0]
@melvincarvalho.com I'm trying to set my NIP05 identifier "plantimals@plantimals.org" -> https://plantimals.org/.well-known/nostr.json but having trouble getting nostr.rocks to recognize it. how should I format the identifier to submit in the "NIP-05 Identifier" field?
thank you @cameri and @melvincarvalho.com - accessibility leaping forward