hoppe

Looks like #amethyst changed a bit in a weird way. I was wondering why it seemed off even though I hadn’t updated it — turns out I was looking at the Conversation tab instead of the New Threads tab.

I'm not sure which is more profitable — running a JoinMarket maker bot or operating a Lightning node. Both usually earn fees proportional to the volume they process, and the more liquidity you provide, the higher your chances of being chosen, so naturally, more funds mean better profitability. Assuming you run both with, say, 10 BTC — not that I actually have 10 BTC, just saying — I wonder which one would be more profitable. Anyone out there know?

I’ve built a service that backs up nostr events. More precisely, it synchronizes between relays. There have probably been similar tools before, but what sets this apart is that it strictly synchronizes based on the outbox model. Well, maybe something like this already exists too, but who cares? The world is full of similar programs anyway. https://tajava2006.github.io/sync-nostr-relay/ The usage is simple: just enter your npub and press the sync button below. From that moment, it starts going back in time until there are no more events to fetch, syncing the relays as it goes. It queries notes in chronological order and republishes them only to the relays where they’re missing. It syncs the posts I’ve written only to my write relays, and the posts I need to read only to my read relays. This whole idea was inspired by this post I deeply resonated with: nostr:naddr1qq2nskt2w9vx6dznfdvj64rpw4mk5nmxf3v9xqg4waehxw309aex2mrp0yhxgctdw4eju6t09upzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqvzqqqr4guvtytln Because of that, the sync feature is not provided to users who have registered too many relays. This should be helpful when you’ve changed your relay configuration and want to back up your past notes to newly added relays.

Thank you for the interesting article. It was very helpful in understanding the nostr ecosystem. I have one question to confirm if my understanding is correct. Assuming all clients adhere to the Outbox Model (NIP-65), and all relays store and serve requested notes completely, users should theoretically be able to find 100% of the posts authored by people they follow and the reactions to those specific posts without guessing or manually adding relays (ignoring the bootstrapping problem of how to initially find the NIP-65 event for someone I follow, let's assume that's solvable through reasonable guessing or indexers). However, my understanding is that finding an original post (let's call it Post A) when someone I follow replies to or quotes it cannot be achieved 100% solely through the Outbox Model of the person I follow. It seems dependent on NIP-10 hints (p and e tags). Specifically, is this process correct? When my follow replies/quotes, their event must include hints (like a p-tag for the original author, let's call them Author B, and an e-tag for Post A). My client finds the reply/quote on my follow's write relays (as per NIP-65). My client extracts Author B's pubkey (from the p-tag) and Post A's event ID (from the e-tag). My client then needs to find Author B's NIP-65 event (facing the bootstrapping issue again). Then, my client must query Author B's write relays to fetch Post A itself (using its event ID). And additionally, query Author B's read relays to find other reactions (likes, zaps, other replies) to Post A (since Author B is tagged in those reactions). Is this multi-step process, relying on hints and the original author's NIP-65 relays, the correct way this interaction works within the Outbox Model's scope?

https://nostr.download/e50752fb1a7e81850b10956a9fba4e2554b5d444f98e9f116bea9a8a558118f3.mp4 My first #lightning payment at an offline store. March 29, 2025, South Korea.

Every time I eat pork, I can't help but wonder if it might actually be tastier than beef. Of course, that thought lasts only until the next time I have beef. https://nostr.download/d01710814f246477c6562c504585839a4e0d5f0a7ad4d0ccf77a4c4c9ad8365e.mp4

https://video.nostr.build/2baec0f1bfd5f9a68c1b31357bcd83bed2133efb233d22c35b95a8f34517e27a.mp4 #amethyst is great, but there's one annoying thing—when I scroll up, images that were expanded while scrolling down collapse and then expand again, which pushes the content in a way I didn't intend. Am I the only one bothered by this?

Can someone recommend a combination of Bitcoin/Lightning Network node implementations that work well with a pruned Bitcoin node? I'm using Bitcoin Core and LND, and I've found that LND fails to sync properly when Bitcoin Core is pruned. #asknostr #lightning

The government's excessive power stems from its monopoly on currency issuance. At a deeper level, its authority is upheld only by the public’s belief that government is necessary. Since Bitcoin is inherently anarchic in nature, the U.S. government will inevitably turn against it again. If people truly realize that Bitcoin is real money and that the dollar is fake, why would they continue to use dollars and go through the hassle of exchanging them? Workers would demand to be paid in Bitcoin from the start, and merchants would insist on accepting Bitcoin for payments. Of course, this won’t happen overnight, but in a world where fiat currency continues to lose value, it is an eventuality. When that time comes, people will also realize that transacting in Bitcoin could allow them to avoid paying taxes. That’s when the government will step in and take action.