I created an API that returns top 5 of your "following-who-follow-x" sorted by PageRank.
For example this is how we both connect: https://zap.store/api/trust/npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m/npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9
(Give it a little time, it's slow right now)
Our connections with higher signal on our social graph are Gigi ⚡🧡 (npub1der…xzpc) PABLOF7z (npub1l2v…ajft) and others (you follow them and they follow me)
Why an API, when all other approaches do it client-side? IMO makes no sense to pull a ton of data and heavy calculation client-side, certainly with less awareness of weights in the social graph. With this API you get a small number of npubs you can then pull contact lists from client side and verify the API is not bullshitting you.
I am currently working on making it way faster (will use a more specialized DB). Let me know if this interests you
franzap
npub1wf4…dgh9
2024-05-16 18:17:03
in reply to nevent1q…yjtw
Author Public Key
npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9Published at
2024-05-16 18:17:03Event JSON
{
"id": "1114273c1eee9d58fad2a1df1a0c68d53592ee7fdb9aaa1240340411a5239f16",
"pubkey": "726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11",
"created_at": 1715876223,
"kind": 1,
"tags": [
[
"e",
"91709c397900b23ed2badf0fe78f85a31fb79d803bc9f945dd9b45f2e882d804",
"wss://nostr.fmt.wiz.biz/",
"root"
],
[
"e",
"91709c397900b23ed2badf0fe78f85a31fb79d803bc9f945dd9b45f2e882d804",
"wss://nostr.fmt.wiz.biz/",
"reply"
],
[
"p",
"6ad08392d1baa3f6ff7a9409e2ac5e5443587265d8b4a581c6067d88ea301584",
"wss://nostr.fmt.wiz.biz/",
"mention"
],
[
"p",
"726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11",
"wss://relay.damus.io/",
"mention"
],
[
"p",
"6e468422dfb74a5738702a8823b9b28168abab8655faacb6853cd0ee15deee93",
"",
"mention"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"",
"mention"
]
],
"content": "I created an API that returns top 5 of your \"following-who-follow-x\" sorted by PageRank. \n\nFor example this is how we both connect: https://zap.store/api/trust/npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m/npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9\n\n(Give it a little time, it's slow right now)\n\nOur connections with higher signal on our social graph are nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and others (you follow them and they follow me)\n\nWhy an API, when all other approaches do it client-side? IMO makes no sense to pull a ton of data and heavy calculation client-side, certainly with less awareness of weights in the social graph. With this API you get a small number of npubs you can then pull contact lists from client side and verify the API is not bullshitting you.\n\nI am currently working on making it way faster (will use a more specialized DB). Let me know if this interests you",
"sig": "7b0fbc76339cb6a3a289fe8800d827ae3de874257b7fecbef32447879c22bdc73cce49876f20329a3ef95bb0cc30aea914f2e44145e484acc66b4123eb9b74fb"
}