nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 got Legendary!
nostr:note1pplamt0rkfrmq2ygfe3kfrnwsun6pqx2fc4zx4kcw02pwwgz6u6q6n80kl
nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 got Legendary!
nostr:note1pplamt0rkfrmq2ygfe3kfrnwsun6pqx2fc4zx4kcw02pwwgz6u6q6n80kl
New idea/more homework for you.
Score should be adjusted somehow by "reach". I suspect Derek or Corn get muted for different reasons than what one might assume
expatiate please
Derek probably gets muted because he contributes to a feed too much for some, or he's "too popular" and it annoys some people that even when they choose not to follow a person they may feel neutral about, they get "forced" to see his stuff via secondary interactions which are pronounced for popular npubs
LOL, that sounds like it would be very hard to accomplish.
Percentage of followers would be a good start, but yeah, getting a somewhat accurate count of followers isn't exactly easy.
In any case: neat tool, I like it!
Like, you're muted by rando new npubs vs well established ones?
Yeah, you could do all sorts of refinements. An obv simple first pass would be to weigh by follower count. Better still by "real" followers (graperank type logic), etc.
like Derek has a lot of mutes. Some likely just a volume of exposure thing. Some too from people who may feel neutral about him, but he makes it into their feed anyway with secondary engagement, leads to resentment and a mute. I dunno
It'll be interesting to see. These kinds of analyses will be possible with what I'm planning. Nostr stalker paradise.
Get busy deving
I'm on vacation and in a food coma. I'll get right on it.
Jay about to cook. Let him π€£

The Brainstorm prototype calculates muter count, total and GrapeRank-filtered. Same for followers and reporters. Graph databases make it easy to craft queries like this and to play around with more complex ones.
Looks like the Mute-O-Scope casts a wider net in terms of raw data, based on the total muter counts. One of the first decisions of a Brainstorm instance owner/operator will be which relays to draw data from.
You should do some mobile responsive optimizations to add a hamburger menu and eliminate content overflow.

Well, it seems like you can finish the minor details from here without me. YW
