Since cutting out the most spamming relays, the NostrGram database load dropped so much that I was able to double the number of relays that it's indexing without affecting performance at all. That guarantees even better relay coverage when you use Nostrgram. #[1]

You mean post as "notes" or all kind of events? I push more than 100 events a day, even more, am I offender? I dont understand your point to censorship a entire relay before checking with its administrator if is something going wrong. So abusive .

i'm not liking the idea of discussing creating a digital ghetto announced in public because the spammers might notice and simply swap relays, rendering the whole effort not only useless but also permanently tarnishing the reputation of the affected relays; on the other hand transparency is always appreciated

👀🤯 THE MOST SPAMMING NOSTR RELAYS LIST

I put together a list of the most spamming relays to see if any particular relay(s) are the biggest source of the spam issues. As it turns out, there are 4 that are by far the worst offenders.

What I did was take the number of posts over the last 24 hours to the relay (as indexed in NostrGram) and divided that by the number of users for that relay. I keep stats on how many users each relay has, and rebuild those stats a couple of times a day.

As it turns out, the worst offenders BY FAR are:

**relay, post count (24 hrs), user count, posts/user (24 hours)**

wss://relay.nostr.bg, 74892, 6544, 11.4

wss://nostr-relay.digitalmob.ro, 65063, 194, 335.4

wss://nostr.drss.io, 56028, 467, 120

wss://nostr.einundzwanzig.space, 36742, 453, 81.1

Since paid relays are the most likely to reflect how often real people post on average, I checked the average of all the paid relays in terms of posts per user per day. They average 1.2 posts per user per day (the Damus relay also averages about 1.1 per day).

**The top 4 worst offenders average 140 posts per user per day.** 🤯

I am removing those 4 relays from NostrGram indexing effectively immediately, and I recommend you remove them from your read/write list as well to prevent performance issues on whatever client you use.

s/o to #[0] for suggesting I put together some metrics

I see, thanks, but still a possible future problem.

I see, thanks, but still a possible future problem.

Would be fun if there was a zap war that was set up like capture the flag. 🤔

Your mom, no offense, is likely at the end of the adoption curve. We’re very far from that.

First, we’ll get people who NEED nostr - both for speech and commerce. Then the more tech savvy will join. Then the Twitter crowd. And lastly, the moms.

My mom is not going to join nostr for its wallets. Also my brother is not going to join nostr for its only bitcoin payment mode. He is afraid of digital currencies because his lack of knowledge on security. First of all keep it simple.

What nostr has revealed:

1. We need more super simple UX lightning wallets. WoS is great but we need options.

2. Lightning infra is weak and needs work to scale. Props to those leading the way but much more work ahead.

3. Even with improved UX, newbs still perceive nostr client as difficult to use - we have to do better.

4. Plebs are the real bitcoiners who find signal in noise. To stay ahead, follow the plebs.

True, though Jyn is a she. 😉

Yes, do this. Most paid relays are read-only, so you can still add them and they’ll popular your global.

Ultimately, though, they’re cheap. I’ve earned far more in tips than I’ve spent on paid relays.

Yes, but not until Apple allows the next update. You’ll be able to filter global by only paid relays.

Coding time.

The NIP57 message is broadcast upon payment of the Lightning Invoice, by that entity, is what I understand

If you are able to see is going to depend if they have a NIP57 compatible Lightning Address set in their profile