Youâre đŻ about the hot data mess. No way around that, ever. We may as well come to grips.
Which means that as a consumer of the hot mess, youâll have to interpret data that comes packaged in multiple formats. Each external format needs to be interpreted into a *single common format of your choosing* so that you can synthesize them all together in a way that is of maximum utility to you.
Yes, but if the majority are interoperable, that raises the pressure on others to use the same event type for the same data type, unless they can prove that they have some novel use case that requires a different tactic. Which is possible.
Like, if Zapstore is using labels for ratings, I'll just use labels. I don't need to invent a new "rating kind", just to be a jerk about it. My incentive is to just go along, to retain interoperability and not preclude future use cases. That's part of the magic of Nostr.
Itâs true that if everyone else is using some specific format or nip for ratings, then itâs in my interest as a dev to adopt the same system. This is how we avoid a Tower of Babel type situation.
But it will never boil all the way down to a single global format that we are all forced to use. There will always be multiple formats. If we know how to synthesize multiple formats from multiple data sources together to answer a single question, like whatâs does my WoT put at the top of my rec list, thatâs a good thing.
Problem: how does my WoT rank widgets from top to bottom?
Data source 1: vendor follows, mutes, zaps
Data source 2: 5 star ratings of the widget from store A
Data source 3: emoji reactions on adverts of that product on a nostr classified ads client
And Iâm sure we can think of MANY more data sources than those 3.
Edit:
Data source 2: 5 star ratings of the widget from stores A, B, C, and D, plus 0-100 point ratings from store E written by some pain in the ass nonconformist weirdo dev who uses a different format for reasons you may or may not agree with or even understand
Answer: the grapevine method synthesizes all these data sources into a single score. If you want to buy a widget and your fav nostr store has listings of 1000 widgets from 1000 vendors, why not use ALL of the above data sources to rank those 1000 products from top to bottom?
That's a complicated set of math to do.
Yes but quite doable. Too much to do on the fly on the front end, but the heavy lifting can be done ahead of time on the back end.
I built a front end demo using only two data inputs (follows and mutes) which is how I realized itâs too much for the front end. nostr:npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tn streamlined the download process into a single click and you can try it out here:
It will output the top 1000 recommended pubkeys minus the ones you already follow as a NIP-51 list which you can upload to a few clients (Coracle, Amethyst, nostrudel maybe?) and browse the feed when you get tired of you follows feed. Great way to discover new high quality follows.
nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h and nostr:npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tn and I are working on replicating the above but calculating scores on the back end using a relay that already has follows and mutes data, so no need to dump all of that onto the browser, much better UX.
So I did that and have no clue how to view that list on amethyst. Not your problem, just, trying to see the output.
Start out going to listr.lol and see if you have a list with âGrapevineâ in the title
Yup. "Grapevine recommended"
Can any #Amethyst users help a beaver out? How to import a NIP-51 list and browse a feed and whatever else you can do with it?
#askNostr
Ah. I see. It's just a filter that you apply, basically. I can't see see the list itself, it is just applied as a filter. That's... Not exactly useful. I don't see anyone new on that feed at all.
No one new? It should omit the pubkeys youâre already following when it builds the list. Did it not do that?
Didn't seem to. Mostly just my own stuff comes up. đ
Yup. It's literally a feed of me. Kinda weird, TBH
I see your list â yeah, didnât populate it at all except for your pubkey. Check out my Grapevine list on listr to see what it is supposed to look like.
When you built the list were you signed in using an extension? Smartphone?
I can't figure out how to see lists via a different npub.
Yes. An extension (nos2x, IIRC) on an android phone with kiwibrowser.
We havenât tested list generation on android â maybe thatâs why?
On listr you can browse lists of other npubs. Search by username at the bar on the top. Or go to listr main page Activity Feed and right now I see one or two My Grapevine Recommended lists recently updated â the first two I click on seem to have worked (mostly) correctly (except only 878 items, should be 1000? đ¤)
I get an error 504 when I click on your grapevine list.
I dunno what else to try. đ
On listr?
See if this works:
That mostly works.
I can see the list, just not nyms or avatars, so I don't know who anyone on that list actually is.
Hereâs what I see (not logged in) 
Everything is populating on that list now. So that's cool.
But that's not the same as mine. It's just my npub and that's it.
I find listr useful to view the list itself. Itâs easy to scroll down and check who youâre following and who youâre not.
At first we just exported the top 1000 and youâd get a mix of current follows and suggested follows, but then we figured weâd omit current follows so youâd get a fresh feed from high quality pubkeys.
Soon youâll be able to generate multiple lists. With / without current follows; Grapevine page 1, page 2, etc
I still can't see the list on listr. It's just... A block?
Your âMy Grapevine Reccomended Followsâ list was published to Nostr from grapevine.my. You can confirm this using listr. I havenât personally tested on android (yet) but I believe you can make custom feeds in Amethyst, using Nostr user lists?
Yes. I just was thinking that I could view the list itself, not the filtered results of the list. Not as useful.
Yes it is complicated. But there are a âfiniteâ set of these data types (Nostr event kinds that interact with other events in ways that may be interesting for WoT) to calculate.
There doesnât need to be a standard of âwhich data typesâ should be used âin which mannerâ by clients. Some de facto standards may arise, while other algo inputs will only increase in complexity. Standards are not as important as adaptability.
For the foreseeable future, developers of WoT recommendation engines will have to keep their ears to the ground to adapt their algo inputs accordingly. But this complication does not need to be developed all at once or overnight.
Mind you, this is a new perspective for me. Itâs much easier to just say âletâs make a standardâ, to make development easier. But life IRL does not work this way. Life adapts. So we must learn to adapt as Nostr grows.
Today we do this. Tomorrow we do a bit more. Baby steps.
đ đŻ
