Nostr Web Client

Yes, for users, this is no different from a typical relay. It’s even slower and provides less data.

I think this model is worth trying. Unlike other relays, its data is provided by ordinary users, making nostr more decentralized. I also encourage more people to expose their local nostr-relay-tray through services like ngrok.

Freakoverse 1y ago

Ah ok, if that's the case, then I think this is a better UX (along with being more decentralized), all the while giving more control (in a sense) to users, in comparison to manual input of multiple relays or random auto relay setup, right?

Instead of me adding 10 relays, I can add 1 hub (or 2 just in case) that I like, and those hubs can do the work for me in terms of the relays they aggregate, and they can add however many relays they want for maximum decentralization.

This got me thinking, i'm assuming this is what you meant with "expose their local nostr-relay-tray", is that a hub doesn't have to manually add relays, but keep listening to relays that want to expose themselves hubs/aggregators and they'd be automatically added.

Reply to this note

Please Login to reply.

Discussion

Cody 1y ago

I’m glad to hear your thoughts, and it made me think more seriously.

If you want to replace 10 relays with an aggregated relay to save bandwidth, you should choose the bostr relay.

Currently, most relays use the same code and data, so I don’t think there is any difference between users selecting a few relays themselves and directly using a centralized platform like X.

The goal of nostr-relay-tray is to enable everyone to easily run their own relay and have the right to save and broadcast their own events.

You can run a hub with your friends to ensure you have your own events. The cost of running a hub is low (even free) because it only forwards data without storing it, and it is not used by many people. Additionally, hubs can set password, so you can restrict who can join your hub. For testing purposes, my hub has no restrictions set.