Oddbean new post about | logout
 nostr:nprofile1qqsd5x8fscqypualfyu8dlqkkx539tj6dah634g4ns779wpr8gxes5gpz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3uamnwvaz7tmwdaehgu3dwp6kytnhv4kxcmmjv3jhytnwv46z7r379p8 
 The dream for DVMs is to be able to fall back to competitors when one doesn’t work, automatically. If a DVM doesn’t respond, you go with another one that solves the task. I’m hopeful we can build this but afaik it’s not a thing yet. For example, using information from dvmdash.live you could find the second most popular algo feed DVm for the feed you want and use that instead. (I plan to expose this capability eventually in a DVM like an API would).

algo feeds will be like 0.1% of DVMs, although they are the most popular right now (see https://dvmdash.live/kind/)

I totally understand the benefit of doing it locally, but you also miss out on the network effects. When @miljan puts out a new one, users of an app can benefit without the client devs touching a thing. 

Tradeoffs.