that is a small part of it, though I'm unsure how many use negentropy and how many are simply doing basic scrapers.. a lot of this is actually clients, when two or more people add a relay, and they see a message they like, they comment or etc, and it blasts out to all their relays.  this is all client side optimization for "event not found" stuff..  eventually it will be nice if they didn't have to do this and could simply use relay hints, outbox etc.  but for now, it does make nostr 'work better' for the twitter model.  then on top of that, the scrapers are looking at nostr.watch and if the relay is there, you can pretty much know it's part of a huge shadowy supercoder network shuttling messages around.  nostr1 does not do any of this pro-actively, it just happens once nostr.watch sees the relay via the relay lists.

```curl https://api.nostr.watch/v1/online |jq```

we all like seeing notes so much and growing nostr, test messages tend get a lot of engagement lol..