Avatar
PABLOF7z 2y ago

Finally catching up with nostr:npub1nstrcu63lzpjkz94djajuz2evrgu2psd66cwgc0gz0c0qazezx0q9urg5l talks

watching nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn 's

very good talk so far; very clear thinking -- thank you, hodlbod 💜

https://www.youtube.com/watch?v=R-5DHymkfzw

Reply to this note

Please Login to reply.

Discussion

Avatar
hodlbod 2y ago

You're welcome

89
nobody 2y ago

Hey NDKUsers has follows > right. Do I have to fetchProfile() one at a time asynchronously…. Or should there be `user.follows().fetchProfiles() or user.fetchFollows() to fetch in single shot or is that simply potentially too large and relays won’t let that happen? (How many author keys can you put in filter before relay rejects?) just wondering stuffs

89
nobody 2y ago

Also in this block when I was goofing around, when my NDK instance is configured with MORE relays… it will not return me full profile and images.

But as I remove the explicitRelayUrls…..then I see more images coming in (as if NDK is getting lost somehow in case of multiple relays? dunno just observed this but super green at this moment)

```

{#await user.follows() then ndkUsers}

{#each ndkUsers as ndkUser}

{#await ndkUser.fetchProfile() then follower}

pfp

{ndkUser.npub}

{/await}

{/each}

{/await}

```

89
nobody 2y ago

What I meant is, this for with await had lots of blank images....whereas if I just keep 1 or 2 relays the page fills up entirely without images missing 😩🫢😆