I've been dabbling with Nostr packages lately and decided to experiment by creating a real-time mirror of the Bitcoin Mailing List on Nostr, going back to 2011๐Ÿ‘ด

nostr:npub15g7m7mrveqlpfnpa7njke3ccghmpryyqsn87vg8g8eqvqmxd60gqmx08lk

To help catch up on discussions, threads from 2011 and 2023 with multiple responses include AI generated summaries ๐Ÿค–. If this sparks interest, I might expand this feature.

Each sender has an archive account for easy access to all their messages and stats ๐Ÿ“ฌ. The best part is that there's no moderation here - I believe in client-side filtering.

Considering making it two-way: zapped notes could bounce back to the mailing list based on popularity. ๐Ÿ”„ What's your take?

Please note, due to rate limits, it's not on all popular relays. However, for those of you who run a fancy relay and would like to store a backup, I can provide the full npubs whitelist๐Ÿ”’

Lightning mailing list is coming next!โšก๏ธ

Using nostr:npub1ndk0nwqwjajykt5fnlyjhdlp33dffurcmx5vfp2hljp2y7ew62fsq7qfy4 for this was straightforward, shoutout to nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and the team! Feedback is welcome, let me know your thoughts!

nostr:npub1qgwhaaa2lsp54rl0hfx7qa3z678ax6wlre0em475rhpvl7n54cpqgg7y7n

https://void.cat/d/UZpkYKpLJZ9rSHVMF61eZa.webp

Reply to this note

Please Login to reply.

Discussion

neat!

Thanks!

We can now tag here you archive profile nostr:npub1d7e068ud72v0au6xf53qvek44eccfhlgnhzuclf6za6hnxrvx89sc93exj ๐Ÿ˜„

Holly shit, this is fantastic!

nostr:npub1ww82xmhhfv4vszlm8zrmgp3hclwd7a82dmkh83cckuvnxyaep7dsnyxmjl replies don't tag the event that it was replied to? That would be amazing.

So you can navigate directly to the thread event from any message? noted for future threads.

Yeah, so you can navigate the entire thread Iโ€™m a more natural way and it preserves the natural hierarchy

#[5]โ€‹ this is ๐Ÿ”ฅ

What can team #ndk do from dev, and/or design perspective to make your experience using #ndk even better?

What did you find most valuable in using #ndk?

cc #[9]โ€‹ #[3]โ€‹ #[10]

I looked into a few options and NDK stood out as the simplest and best built. It is really tough to spot any issues.

I had to go through some nips and work out the exact tag symbols to use, which I think could be avoided. Also, I couldn't catch and handle the rate-limit exception from outside the library code.

Weโ€™re you using fetchEvent or subscribe when you were hitting limits or was it publishing events?

I was connecting to multiple relays and publishing all threads from 2011. Ideally, I would want the rate limit to be abstracted out so that publishing blocks until it has actually been published to 'k' out of 'n' relays.

Did you publish the code somewhere?

Wrt the first part; Iโ€™m about to launch an ndk-kinds library that makes dealing with NIPs transparent.

Iโ€™ve been writing it and makes dealing with NIP peculiarities very nice and intuitive

Sick! Needed this one.

Doing via Twitter API would have been cool too but looks like they made it paid which sucks.

Yea, and they probably don't allow the creation of hundreds of new archive profiles ๐Ÿ˜„

The harsh reality for developers is that once you begin exploring the world of uncensorable, programmable money and social network, turning back becomes almost unthinkable.

This looks awesome #[0]

cool!