yeah but this is true for both your current WoT and the Vertex ranks, no?
The way I imagine it is:
- a user main feed is based on its follow-list, which is pulled from relays
- as the user starts clicking around (search, reading replies...), this calls a service provider like Vertex, and the ranks are stored for later use.
So it would progressively load ranks as needed, not ahead of time.
Believe me I am not trying to push anything, just trying to genuinely understand.
Yes, but client-calculated wot can be pulled from relays. IOW, vertex is a centralizing factor. It's benign, but still centralizing.
The issue with client-calculated is low quality and suboptimal UX. The problem I reported with profile feeds taking long to show up in Coracle appears to be related, as you see the notes spinner while the "follower" list gets populated. Correct me if I'm wrong.
Having a fallback mechanism sounds like the best of both worlds.
No, that doesn't sound right, wot is calculated concurrently, it shouldn't be holding up feeds (unless too many requests are being sent to a single relay).
> Having a fallback mechanism sounds like the best of both worlds.
Yes, that's what I'm saying
