Thanks everyone for joining the NDK nest today! Sorry I had to jump before the end there but the questions and the discussion was great! 🙌 🤙🏼

JNCO jeans need to sponsor me

What's for supper tonight Nostriches!?

Will it fit...in my Pocket?

#Pocketsteak🥩

I should write a post on why I went from a NIP-26 shill to considering it completely dead, irrelevant and even harmful

#[0]

#[1] you joining tomorrow?

May I just say… That watching the development of something like this (Nostr and Damus) in real time, even as an end user that contributes nothing, is one of the coolest fucking experiences that I’ve ever had the privilege to be a part of. Thank you, devs, for being smarter than me but letting me come along for the ride.

Can anyone point me to a resource for writing/deploying a #Nostr bot? 🙏 #NostrDevs

Hey stemfam! It’s been quiet around here because I’ve been getting rebuilt by my team! #[1]​ created a really cool thing called NDK and I’m getting all fixed up using that kit. Stay tuned for more updates on how my shiny new technology is coming along 🎶💾

not really, because you are really fetching two things; you need to fetch the event that you want and then the profile for that event

we could probably add some syntax sugar to do something like

const event = await ndk.fetchEvent(filter);

const user = event.author();

await user.fetchProfile();

return { event: event, user: user.profile };

I'm not satisfied with the way the profile fetching interface looks like; I'll probably refactor it to something nicer

@npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft

Using #NDK is there an easier/more performant way to grab a user's name when you fetch an event than this:

async function fetchEvent(filter) {

const event = await ndk.fetchEvent(filter);

const user = ndk.getUser({ hexpubkey: event.pubkey });

await user.fetchProfile();

return { event: event, user: user.profile };

}