Cooking self sliced bacon. Thick. #foodstr

How do I enable showings badges I've received in my profile? #asknostr #badges

GN.

One day I will hug @The Fishcake (nostr.build) physically. I just need a low time preference, laser eyes and dog bisquit.

1. Accept this challenge. 2. Stay for 10 blocks exclusive on nostr (only drinking water allowed besides this). 3. Count how many notes you signed and multicasted after those 10 blocks. 4. Reply this number here. 5. Get zapped #value4value by me for your work. My budget until block height 898'000 is 10'000 sats. 6. Enjoy the feeling you get out of your 10 blocks nostr streak. cc #v4v

Draining @shy kids and @Wavlake's battery by a full listen of A Gathering of Batteries. Now at 1k sats while looping heavenly clouds. I intend to claim the sats of this listen session. I'm worth it! My attention is worth this well self treatment. PV to all the people pleasers and philanthropists. We are the same but we are not. 🫂

What happend to #zapathon's? #asknostr

I'm thinking about finally publishing my book with the title "Worthy Wrench Attack Targets" as #v4v product. In currently 18 chapters called "class of 2008", "class of ...", "class of 2025" with facepages of ever class and as much info and bio about every entity I was able to aggregate. In part two of the book you can educate yourself about theoretical concepts and models in a spectrum of "bad ideas someone impelented in reality already but I'm not fully aware of or don't want to belive in" as well as "bring paranoia to the next level" and "KYCnotME". As hope and closing chapters in part three I feature the concepts of INZO - Angst and @Alan ₿ among others. Updated yearly. Are you willing to #value4value this? PV #wwatTHEbook 🫂

If core decides to merge the OP_RETURN data limit, I won't update to any new version of core with this default implemented. Just think about what use cases coule and which most probably will emerge. As an example you can broadcast data through the mempool without paying for the transmitted data by RBF'ing the tx before the tx hit's the first confirmation and replace it as long as it doesn't get that much sats/vb to be confirmed. This lowers the relative fee for any further RBF (with new data included and distributed) DRAMATICALLY and will create incentives for mempool only use cases which just consume node bandwith which isn't even paid for to the miners. Sounds like siphoning the avaiable bandwith of node runners for the distribution of data. I won't give my node ressources in support of creating and maintaining a relative RBF sats/vb market. h/t @OceanSlim