Profile: 463a3e1b...

$40? Guess it's not that important to get the word out LOL

Why not spend less time begging and more time programming? More relays, and more intelligent filtering on the relays, would cut down the workload.

Now watch them pile on and try to smear me. They can't just ignore me because our discussion is already out there on - you guessed it - thousands of decentralized, non-cloudflare-censored relays. All they can do is try to dilute my message with spam (the spam they want to save you from).

#[6] and #[5] have been shilling me the idea of (((paid relays))) and degree of separation from (((trusted authorities)) for spam filtering.

This is an old scam, and there's nothing about nostr that makes it immune. Only the ability to use TOR is significant. Having everyone run their own hidden services would work just as well.

Replying to Avatar Cyph3rp9nk

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.

Add a paid relay, add a cloudflare proxy, and keep my relay list as short as possible? Brilliant! Almost as good as Twitter! 😂

This is what I mean about confusing ui. The qr code scanner and generator buttons should be grouped with the "copy npub" and "copy nsec" buttons.

You know you can post more than 256 chars on nostr, right?

You don't own nuthin goy