I am loving my new avatar. Thanks @BITwise 🐳 >>= RIGHTish !

Got an early day tomorrow and may not be able to hang. I did watch a few Alby videos and struggling with my new hub. Going to drop an invoice in the comments to tinker tomorrow. GN frens. 🤙 The moon is slacking tonight.

The #moon is still below my horizon and I am patiently waiting.

Chris Cornel tribute. Chris sang and delivered it *much* better

Just a quick update on the National Flood Insurance Program / #NFIP... * The Louisiana Department of Insurance continues reminding that existing policies remain in force until expiration, but no renewals or new policies are being issued during the lapse. (side note: Wright Flood Insurance - a write-your-own - sent all renewals through end of year ... they were smart!) * Pinellas County (FL) reaffirmed publicly that NFIP is “on hold”—no new or renewal flood policies allowable until reauthorization. (see side note above.) * Vermont sources note that, with no new guidance, the WYO Bulletin W-23012 (from 2023) remains de facto reference guidance in many states until replacement direction is issued. * News analysis suggests that Congress might bring a reauthorization bill to the floor soon, including possibilities for narrow or standalone measures. That said, the gov't remains shutdown. If your flood policy is to renew between now and year end, and you get a renewal bill, renew it. If the NFIP is not reauthorized and your policy lapses (after the grace period), you will not be able to renew until the program is reauthorized. You will then be subject to a 30-day waiting period as well as a new higher premium. During the shutdown period, renewals cannot be endorsed (coverage, deductibles, etc.).

GN frens. 💤

Tonight's #moon ... Waning Crescent, 40%.

@Zach⚡️ inspired me 🤙

The Core vs. Knots debate, from what I've gathered, is an illustration of Nostr's maturation in that it is no longer a single project ecosystem. It has become a vibrant, multi-client network with competing visions, all contributing to its growth in many different ways. Due to the passion of both sides, the debate has emotional heat. I understand that Core has been the client created by fiatjaf and prioritized to Nostr's protocol. Isn't Damus running great on an older and forked version of Core? Knots is just that, forked of Core thing and gives users new features before implementing into Core. While Core follows the NIP-57 standard, Knots may not and users may experience fragments of frustration. It's ok. Its part of growth. While there's a split of devs in taking sides, I'd like to encourage healthy debate as well as staying true to to your core moral values as developers. We all want innovation, but please don't sacrifice the basic principles that once set you apart. I feel that both sides can and should learn from while challenging each other. Let's make Nostr better. NanuNanu 🖖