Nostr Web Client

Is it just me, or does it seem like everyone is super reluctant to monetize services and relays on #Nostr?

If we can’t make these things sustainable then we will either lose them, or they will stay nothing more than a weird little corner of the internet with lots of hope but no chance of ever scaling.

I still haven’t seen the basic model of zap sharing tried by any major client or relay. But I DO see regularly comments about how expensive relays are. I mean it might not work, but can’t we TRY it?

I want to make the distinction here too that this doesn’t mean we are closing off the network, we are adding permissions to the protocol, this doesn’t suggest at all to used closed source code, we simply need the services necessary to keep this ecosystem robust, to be profitable and have the resources to thrive. If they aren’t, then NONE of this works. Economics is everything.

I know building features is more exciting. I know we all want to make everything that we can free, and I agree all of the *code* should be shared. However, I think there is a natural insecurity (and I say this because I have this problem personally) with charging a fair price, and fearing criticism or the ire of people who believe everything should be free (as in price) when we need things to be free (as in Liberty). They are not the same, and confusing the two could stifle, or drastically slow down, the insane potential of this place.

TL;DR We have GOT to divert some energy to thinking about how to make this ecosystem sustainable, or we will lose it.

(Disclaimer: this isn’t a judgement on whoever is thinking about this problem. It just *seems* like few are. If you are building in this way please share your ideas or what you are trying. I’m extremely interested)

Tetsu Tamasi 2y ago

Paid for a relay from soon after it was available and very happy with my purchase.

MOAR please

Reply to this note

Please Login to reply.

Discussion

Jeroen ✅ 2y ago

What value does this relay bring you that free relays don't atm? 🤔

Tetsu Tamasi 2y ago

//Cyph3rp9nk

Note from march 2023

Tips for Relays.

Forget about having a thousand and one relays.

The first option is to pay for nostr.wine, it allows you to use the filter.nostr.wine filter. The filter works both requesting events from other relays and sending events to other relays. In case you want to send events to other relays you have to add the relay with the following syntax:

wss://filter.nostr.wine/REPLACE_WITH_YOUR_NPUB?broadcast=true

Reading list:

wss://relay.damus.io

wss://nos.lol

wss://relay.current.fyi

wss://brb.io

wss://nostr.oxtr.dev

wss://relay.nostr.bg

wss://no.str.cr

wss://nostr.mom

wss://nostr.zebedee.cloud

wss://relay.plebstr.com

wss://offchain.pub

Writing list:

wss://relay.damus.io

wss://nos.lol

wss://relay.snort.social

wss://nostr.oxtr.dev

wss://relay.nostr.bg

wss://nostr.fmt.wiz.biz

wss://nostr.mom

wss://nostr.zebedee.cloud

wss://no.str.cr

wss://relay.plebstr.com

wss://offchain.pub

The next special relay is relay.nostr.band. This relay reads events from all relays and applies a spam filter, in the case of writing you only write to relay.nostr.band but it is a good complement to add content to relay filter.nostr.wine as it only requests events from your contacts and your contacts' contacts. It is not clear to me from which relay is requesting the events as the code is not available.

And finally the relay nostr.mutinywallet.com. This relay uses blastr which is a nostr cloudfare worker proxy that publishes to all known relays. Basically what it does is to read the list of online relays from nostr.watch and all events are queued to be executed in batches by another worker that rotates every 30s if there is an event queued, or once a certain amount of events are queued. In this case the relay is write-only.

In short, your relays could be reduced to 4:

wss://nostr.wine

wss://filter.nostr.wine/REPLACE_WITH_YOUR_NPUB?broadcast=true

wss://relay.nostr.band

wss://nostr.mutinywallet.com

With them you save bandwidth and battery, actually filter.nostr.wine in write mode and nostr.mutinywallet are redundant, but I put the two because nostr.mutinywallet.com has more amplitude because it publishes in all the online relays of nostr.watch and also because it has high availability in case of failure of any of the two relays mentioned above.

The same case is applicable in the case of reading for filter.nostr.wine and relay.nostr.band.