Also huge shout out to the devs and relays keeping this all flowing as is.

I've got a couple paid relays under the belt. I'm aiming to get more...

Another question, some paid relays show as relays on Amethyst, does this mean I am connected to them through Amethyst on their end and if I pay I get to use them on different clients.

And aside from supporting the relays (which I would like to do) is there a benefit to paying if your client connects to them?

Reply to this note

Please Login to reply.

Discussion

Paid relays are almost always pay to publish, but you can still connect to them without that privilege.

Clients don't care what relays you use, and for the most part will carry over to other clients if you publish them (this can be done on Iris.to manually, or apps like Damus do it automatically.)

I am still highly skeptical of the paid relay concept. I certainly understand why it exists, but I think it has a long ways to go. Not to mention, relays and managing relays is not an easy thing to understand. Even with quite a bit of study, I am still not 100% certain how to guide someone on how to best use or select their relays.

šŸ¤” so much to consider šŸ˜µā€šŸ’«

Thank you for the thoughtful response šŸ«‚

My pleasure.

Feel free to add the relays that I am operating if you wish, I will whitelist you on the private relay. That one (running strfry) I have streaming to/from a few larger relays, so you can reduce the number of relays your client connects to. That in turn should provide a faster experience on all clients.

Private (Invite Only) - wss://strfry.nostr-x.com

Public - wss://rs.nostr-x.com