Subnostr

Wrote a quick and dirty trending notes concept today powered by our aggregator relay. It tracks replies, reposts, reactions, zap count, and zap amount total on an hourly basis for all notes and allows queries over a time period with sums. It will also support overall counts.

Don’t have anything to show yet since it’s just a database but I’m thinking I’ll expose it via API and an ugly front end. Would this be useful for anyone?

Viktor Vsk 2y ago

There is a problem with any type of aggregation at current stage. Any relay (even taking the best attempts to collect all the data from all other relays) — will never have a complete picture of events. And thats rather good for the network.

However, aggregation in this case becomes the source of truth that is flawed by default. Of course, it may be used for some estimates but it locks you to the specific relay instance

On the other hand client aggregating all the events from different relay (say, regarding zaps to specific note) is very inefficient and slow but it is able to find “source of truth” on its own

Reply to this note

Please Login to reply.

Discussion

Mazin 2y ago

Yes, totally agree. This is the main trade off.

I am not (and don’t want to be) a client developer so a lot of the innovation I can experiment with on the relay side is inherently centralized.

The good news is the data is public so users don’t have to blindly trust our counts, they can verify themselves. I think we will continue to see an increase in the availability of caching/archival services so that at least there are many sources of truth.

Viktor Vsk 2y ago

Centralized part of nostr should definitely evolve, too, the main question is to how properly integrate it into decentralized design