Happy October 29, Cyrus the Great Day

Bitcoin Core Onboarding

Consensus specification

Bitcoin Core developer onboarding documentation

The requirements to be compliant with "the bitcoin spec" are to be bug-for-bug compatible with the Bitcoin Core implementation. --- We need a Bitcoin specification. So we can develop more core alternatives, more options to select and run.

Zapstore new relay is now using WoT. Onward. 🫡🚀 View quoted note →

WTFFFFFF🥶🥶🥶🥶🥶🥶🥶🥶

@fiatjaf I think njump relay need to both implement and respect NIP-70 and NIP-62. Since it collects data over the network, people need to opt out for it. For their whole pubkey or just one event. I know people who tried to delete their notes from njump, they even asked me and I sent direct nak requests for them but they still find their event on njump. This is really really important. I know all these stuff can be gamed by bad actors collecting everything and do nothing about it, but we need to respect this as much as possible specifically in clients like njump where people try to find something first.

در نوشتاری باستانی («چامه هرمزگان») نوشته شده است: «پرستش‌گاه‌ها ویران شدند…؛ تازیان [عرب‌های اسلام‌گرای] ستمکار، روستاهای پیرامون شهر را با خود شهر، یکسان [نابود] کردند؛ زنان و دختران را به اسیری گرفتند و آزادمردان در خون خود غلتیدند…».

Stay humble, stack ideas.

NIP-51 bookmarks need to support categories or collections somehow. If I'm bookmarking a post, I may want to put this post between some specific section like ideas, buy list, vacation or something like that. It can be done using a new addressable event for bookmarks, or just adding a new value at the end of `e` tags for bookmark events which will be counted as category or collection name.