What I'm proposing is that each relay store all of the reactions in a single event rather than a bunch of separate events so a client can make a single call and iterate through all of the reactions to tally them up. That's not different than what is done now except that it's not in a bunch of separate events that require the relay to scan its db for all of the reactions and the client to wait on receiving all of those separate reaction events rather than a single event with a single indexed key that's extremely efficient to lookup and send to the client.

I'm not talking about all relays sharing data. I mean each relay that receives the update adds it to its own list of reactions. I love the fact that there is no centralized "truth teller" with Nostr. People pick and choose which relays they trust and go with the data it presents them. That's great. I'd just like a less cost-intensive way to aggregate the reactions.

*loses head*

Fair point. A single event that contains all of the reaction tags for a given event id would work. Rather than create a new event each time a reaction comes in, just update the existing one and return that one event when the clients request the reactions.

As a dev that's worked in the marketing sector for 20+ years, I know that for every one person that replies there are 50+ people that liked what you had to say but didn't reply. The Like concept makes it easy to know if your audience is vibing with what you have to say (or not), esp for smaller creators. I'm not talking about algos or curation, but for the benefit of the content creators to know what their audience is looking for. Market forces. Supply and demand.

Working fine for me.

Initial debugging looking good :) Whole #stackchain on screen. I'll have to figure out some partial loading when it gets huuuge but shouldn't be a problem by the looks of it.

What does persistent storage have to do with CORS headers on pfps? Honest question

I believe (?) that CORS headers are no longer required for profile images on astral now? I might be wrong?

#[1] can u confirm

I'm seeing

```

Error fetching invoice from LNURL. TypeError: Cannot read properties of undefined (reading 'tag')

```

also:

TypeError: Cannot read properties of null (reading 'appendChild')

at Proxy.openInWallet (app.69f6b4d1.js:1:101542)