By "same mechanism", I was referring to DVMs (Data Vending Machines) as a method to deliver custom nostr feeds.
We have also been working on WoT standards and custom feeds for many months. While our team is still small and scrappy, we’d be interested to work more closely with you and others to see cross client interoperability for end users. nostr:note1frlz5anaph8cheudt3sn295smmeqyfyvk74f2knmvz075t8mxpmqc2zjw7 Maybe we can get on a topical #devcall with you, @hodlbod and other devs in this space to better our alignment?
Have you considered coracle's custom feeds? It allows for incorporating dvms without relying entirely on them. Feeds can also be saved, shared, and bookmarked, creating a marketplace of feeds. https://wikifreedia.xyz/cip-01/hodlbod@coracle.social
I looked for this previously on Wikifreedia as you suggested, but couldn't find it. 😅 It does look interesting. It would be great if we could come up with a standard feed spec. DVMs are more general and could be useful for feeds. Let's talk more. You going to Riga?
I’m def hoping to learn more about DVMs and their applications at Riga (I’ll be there). In the meantime, to keep things simple, we’re streamlining the export of NIP-51 kind 30000 lists. Right now, we’re generating two types of lists: 1. the Grapevine WoT List 2. New Follow Recommendations List 1 will be the top N pubkeys as determined by the Grapevine WoT Score. This is fully personalized. A user in a community centered in China or Japan will get a different list than someone embedded in the mainstream nostr community. List 2 will be the same as list 1 but minus pubkeys you already follow. So any client that supports NIP-51 lists will be able to benefit from Grapevine-generated lists. Once sufficiently validated, next step will be contextual recommendations, eg: top 10 experts on homesteading (or whatever) as per my Grapevine.