straycat on Nostr: grapevine-brainstorm.vercel.app uses neo4j to maintain a graph of NostrUsers and ...
grapevine-brainstorm.vercel.app uses neo4j to maintain a graph of NostrUsers and their FOLLOW and MUTE connections. Visitors to the site can calculate personalized hops, personalized PageRank and personalized GrapeRank scores and browse the results in table format. They can also export those scores as kind 30382 events following
Vitor Pamplona (npub1gcx…nj5z)'s NIP-85 format which means the scores can be imported and used by clients for whatever purposes they see fit (although I don’t think any clients are using NIP-85 yet). Once the details of
franzap (npub1wf4…dgh9) and
pippellia (npub176p…vgup) ‘s WoT DVM NIP are hammered out to the satisfaction of a few client devs, I’ll also make personalized WoT scores available via API.
Currently I’m taking what I learned building the above service to build a next-generation personalized WoT relay. It will run strfry and neo4j together, calculate personalized WoT scores as above, and use those scores to manage strfry filters and plugins. I think it will do better than state of the art personalized WoT relays which are fantastic at weeding out spam, but probably err on the side of being too exclusive. My fear with existing personalized WoT relays is that newcomers to nostr are filtered out by default, they’ll get little if any engagement, and too many will quit nostr before discovering how awesome it can be. Personalized centrality algos like personalized PageRank and personalized GrapeRank do a much better job of sorting the wheat from the chaff and imho are a needed tool if we are ever to address that problem.
Published at
2025-02-21 20:38:36Event JSON
{
"id": "43fd7f543a37560c82a423fa3c506f70e11fbdf1f587c59ec4a2ca7c3cc5d68a",
"pubkey": "e5272de914bd301755c439b88e6959a43c9d2664831f093c51e9c799a16a102f",
"created_at": 1740170316,
"kind": 1,
"tags": [
[
"e",
"3b04de3fc05576f51b56ce14af2328d96a4904c51304e4278d87f0e1a37ec991",
"wss://relay.bitcoinpark.com",
"root"
],
[
"e",
"2df75876bb6691e231e07fa03179b9df3cd551f5eaa054d921627d37afa68680",
"",
"reply"
],
[
"p",
"62a6a41e2f0f8224586215bce21b8d4b1c7f418622e2d476e3978ddab12acb43"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11"
],
[
"p",
"f683e87035f7ad4f44e0b98cfbd9537e16455a92cd38cefc4cb31db7557f5ef2"
]
],
"content": "grapevine-brainstorm.vercel.app uses neo4j to maintain a graph of NostrUsers and their FOLLOW and MUTE connections. Visitors to the site can calculate personalized hops, personalized PageRank and personalized GrapeRank scores and browse the results in table format. They can also export those scores as kind 30382 events following nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z's NIP-85 format which means the scores can be imported and used by clients for whatever purposes they see fit (although I don’t think any clients are using NIP-85 yet). Once the details of nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 and nostr:npub176p7sup477k5738qhxx0hk2n0cty2k5je5uvalzvkvwmw4tltmeqw7vgup ‘s WoT DVM NIP are hammered out to the satisfaction of a few client devs, I’ll also make personalized WoT scores available via API.\n\nCurrently I’m taking what I learned building the above service to build a next-generation personalized WoT relay. It will run strfry and neo4j together, calculate personalized WoT scores as above, and use those scores to manage strfry filters and plugins. I think it will do better than state of the art personalized WoT relays which are fantastic at weeding out spam, but probably err on the side of being too exclusive. My fear with existing personalized WoT relays is that newcomers to nostr are filtered out by default, they’ll get little if any engagement, and too many will quit nostr before discovering how awesome it can be. Personalized centrality algos like personalized PageRank and personalized GrapeRank do a much better job of sorting the wheat from the chaff and imho are a needed tool if we are ever to address that problem.",
"sig": "90814c432378621c0ac949de893360110efa1732c904869e048029f43c12a3efebc90d3423c5d50fe6b8d8e55461733611a1b4290893478da7d23170955f9393"
}