Thank you! Tryna zap you but getting an error fetching invoice?

Also, do I need to do something with these to ensure it pulls from my WoT rather than from UTXO’s web? Or is that automated already?

Yeah zap have been broken. Fixing it is just at the bottom of my to-do list.

Realistically and optimally, how many relays should we have/use?

So the thing about these style of relays is they pull from whoever's web of trust the user sets. So for instance my web of trust relay wot.sovbit.host uses me as an anchor and then pulls from my web of trust. As far as I'm aware, none of these relays are smart enough to use your input as the anchor for the web of trust. Maybe something's been changed on some of these implementations, but at least that's how my implementation works. And I think that's how all the other ones work as well. So you'll need to set up a relay of your own if you want to use your input as the anchor for web of trust.

Depends on whether or not your client has outbox support or not. If I remember correctly, I'm pretty sure you're an iPhone user (could be hallucinating things), which probably means you're on Damus. And I'm not sure if that has implemented outbox yet. (I'm really out of the loop on lots of client development.) Vitor wrote this for Amethyst And it's a good primer on relays. View article → If your client doesn't use the outbox model, I would describe it as vibe-relaying otherwise. 🤣 Just go what feels right. Maybe have a couple of public relays and then a couple of private relays. Just realize that if you overload your relay list, you're using a lot more data and it can sometimes cause client slowdowns.