Announcing NDK 2.0:

๐Ÿก Automatic connection to main user's relays -- no longer a task your app needs to perform

๐Ÿคซ Automatic flagging of muted events / pubkeys

๐Ÿชฒ Many, many bugfixes and performance enhancements.

๐Ÿคž Better NIP-07 (e.g. getalby/nos2x) handling when NDK is called before they are ready to sign.

โš ๏ธ Deprecation of user.hexpubkey in favor of user.pubkey

And from earlier today, NDK Svelte components:

๐Ÿงต Threading component to make rendering threads as good as it is on Twitter and work as any sensible person would expect.

From now on, all NDK packages will follow the same version number.

Reply to this note

Please Login to reply.

Discussion

Lume is upgrading to NDK 2.0 ๐Ÿ”ฅ

Youre a beast ๐Ÿ‘๐Ÿ‘๐Ÿ‘

You are a machine. Well done!!

If ndk connects automatically to relays using the explicitRelayUrls, what is the best way to update the list of relay addresses? What I'm doing now is I run ndk.connect() every time the user makes changes to the explicitRelayUrls list.

There's a ndk. Pool. AddRelay for this

Yeah I had a feeling that wasn't the proper way to do it, thanks.