The main issue is that IF nostr succeeds, 2GB will turn into 2TB just for contact lists. So, we can keep computing locally while we can, but at somepoint it will just be impossible to manage locally.
It's also true if you want WoT scores for every event (me talking about Nostr should have a higher score than me talking about soccer) instead of just per key.
Rotation will only go so far.
Login to reply
Replies (5)
Premature optimization.
Let's do the thing that we can do while we can do it, not worry about a hypothetical world that has a couple billion nostr users.
Can a user subscribe to some service that would host, calculate, and deliver the WoT scores embedded with the posts served (or a relay that computes them in the way you prefer for a fee)? Services could provide customizability or a few options. A service could host one on behalf of one user that then markets their list to others.
Just needs to be distributed with each user storing stuff for themselves and their friends
Yes and it already exists. See the providers that profilestr is using (Vertex, Relatr, etc). ContextVM makes all that easy.
Profilestr - Discover Nostr User Profiles
Explore and discover Nostr user profiles on Profilestr. Find influential creators, developers, and community members in the decentralized social ne...
Yep. Our git is already showing scores from trusted providers.