I'm nostr:npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw now! 🤓 haha
This is the recording of the Nostr Workshop we've done at nostr:npub13e6qu4kdjsyysrfl5an558rawvqg0rx2xuat9ca706spcdqjzhuqq6md43: https://youtu.be/Eu0rNhmENXQ
Discussion
We discovered that the coordinator was down when you did the presentation, damn 😅
We need more non-Brazilian coordinators 🥸
Maybe we can support redundant coordinators, nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6?
In addition, my.nstart.me also permits to set a custom coordinator in the interface.
I think redundant coordinators will work, you just have to have more than one in your bunker URI. Also I don't want to run this coordinator forever, this was just a prototype until someone made one in Rust.
But for now I think the signers are the biggest problem. There may be something wrong with nostrlib that causes it to not reconnect to the relay after a connectivity glitch, so they stop reacting to messages. Or at least that is something that seems to be happening with `nak bunker` too and it uses the same approach, but I can't figure out what the exact cause is. If someone can help find the bug that will be much appreciated. Or rewrite it in Rust.
