Cute! 🤙🤙
Welcome! 👋🤙
Yes, post the YouTube URL and it should embed.
Welcome! 👋🤙
Your posts and responses are published to relays. Others connected to the relays can see it.
Followed you! #plebchain
Hey! Welcome 👋🤙
Hello! 🤙👋
Hey! 👋🤙
Hey! 👋🤙 welcome.
Perfect! 🤙🤙
Good night! 🌙🌃
Hey all, I was going to run a Nest / *Space* over at https://spaces.nostrplebs.com/general to talk about #[0] joining Nostr today, but honestly I am exhausted. It was a long day and I just did 2 hours of Spaces on the blue bird app. I may go to bed early tonight. My wife will appreciate that as well 😉 Feel free to get one going without me. Otherwise we'll do a recap tomorrow? Until then, keep building. 🤙
Good night! 🤙🌙🌃
Welcome! 🤙
Hey! A reply is here.
🤙🤙 It indeed was. Getting more activity by the day. I guess Snowden being here brought in many users too.
Btw in your relay list you may want to remove the ‘/‘ forward slash towards the end of my relay Nostr.orangepill.dev . Some clients may or may not accept it.
I agree that’s what I though. Since they would otherwise be out in the open for relays or others to query the content tags for location shared.
Right also while using ws://torrelay.onion with most clients won’t work. I think astral supports it but astral almost never loads on TOR or is painfully slow. To get wss we need a paid SSL because let’s encrypt won’t work with .onion. Have to buy one using HARICA or similar providers that support .onion.
Or clients needs to allow ws:// for .onion relays.
Yes, but with a GitHub setup it worked across clients because GitHub handles CORS automatically.
Currently https://terrenly.com/.well-known/nostr.json points to a DigitalOcean IP address and not GitHub.
I’m assuming you’re running on a cloud server which would require CORS setup for certain web clients. Refer to my guide above for that.
Yes, but with a GitHub setup it worked across clients because GitHub handles CORS automatically.
Currently https://terrenly.com/.well-known/nostr.json points to a DigitalOcean IP address and not GitHub.