I think we agree on most of this stuff. Most of this note is just restating what I said in my blog post.

Maybe my idea of the ideal network topology is wrong, but it's the entire reason I started on this project over two years ago, so I'm going to keep pursuing it. Blastr is annoying because it makes that harder, but if the vision can't be accomplished without chaotic actors it doesn't work anyway.

Lots of client devs run relays. I run a few for my coracle.tools pilot customers. But that's not needed to have insight into why many relays have shut down — they're just not needed, and that's not (entirely) blastr's fault. People wanted to be a part of nostr, so they "ran a node". But running a node doesn't matter if you don't use it properly.

> Also Blastr does NOT actively crawl the network and scrap then blast notes.

Ok, I'm curious if you have visibility into how notes get spread across the network then? I know lots of clients re-broadcast, but my sense is that a whole lot gets propagated pretty quickly. I thought I had read somewhere that blastr was doing more than just relaying notes.