I think DVM feeds are lame and relay feeds are 100x better.
Discussion
It seems like DVM hype is entirely on the side of devs.
Which devs? I think dvms are spam
nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszynhwden5te0wp6hyurvv4cxzeewv4esdp32r9 and nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspz3mhxue69uhhyetvv9ujucn0w3jhvtnnwcq3yamnwvaz7tmsw4e8qmr9wpskwtn9wvqs6amnwvaz7tmwdaejumr0dsx2l4qj
Some devs
Power to the relays.
#asknostr
All I see is a wall of periods. Am I missing something?
Maybe Is the diversification cost of relays higher than the diversification cost of data?
People donโt care where feeds come from. Just make it fast and interesting
โ๏ธ
DVM is just outsourcing compute you would otherwise do client-side. It has nothing to do with relays or relay feeds. You could build a client that does all sorts of magical things with/on top of your beloved relay feeds, but the moment you are on your phone you dont want to do those things client side anymore, so you outsource it to a DVM.
maybe he doesn't like python, maybe he wants utxo to do more relay feed, so as to add it to his framework
Yes, because I earn 1 microsat every time a new relay is made using khatru.
I see 400 corrections, I gather you like to play with things. Or is this a spam attack?
he does not like edits on kind1, so he tries to make a point by breaking your user experience. Going through all the edits is actually a far better experience all together i must say, its a work of art.
I'm talking about outsourcing custom feed generation to specific relays instead of to non-relay machines that publish events with lists of event ids or something (I don't know how they work).
isn't DVM an advanced search feature with customization and automation ? i 'd reckon they would complement each other
My impression is that DVMs make some sense if you're doing tasks like translating notes that produce events that can be reused by thousands of clients, but they don't make sense if you're calling them like an API and generating a ton of garbage events in the process, sometimes even encrypted.
They both process data differently thatโs for sure - relay is your rawest and simplest decentralized form. Dvms are like Shopify - aggregators of sorts and have centralized access points - clients might find it easier to extract data and modify than to custom build, but might create a centralized bottleneck and other centralized risks if not careful. I donโt know enough about redundant events but sounds more like a design issue than a system issue? Maybe better implementations might help (filtering etc)
i guess the simplest way to imagine the differentiation between dvms and nostr is that relay on nostr functions like the internet itself, while dvm is an app that sits on top of it.
The risk is when all clients rely on dvm as primary access point, which can lead to centralisation.
Can you explain the difference and give an example of a relay feed? I'm just learning DVM feeds....
It seems to make more sense to build a feed on a relay, but the mechanics confuse me.