@ hodlbod Any idea why I need to nuke all of my local coracle "data" sometimes? For instance I had half written a bug report about the search bar when I thought I'd try this real quick, and it fixed it, and this isn't the first time. I assume my browser is caching part of coracle when it shouldn't?

@Yuki Kishimoto I only took a quick look, but am I reading nostr-database correctly that it does its own in-memory indexing of all known events in memory, regardless of backend? If yes, was that intentional, or just a first pass implementation? (Seems weird to not utilize DB-native indexes where available, unless they turned out to be too slow)

Sure seems like a lot of smart devs have run off into a land of completely reckless protocol development meanwhile a sizeable contingent of plebs don't even realize CTV is safe. The ossifiers seem to have sandbagged the very conservative and safe CTV and the result may be a completely reckless activation of OP_CAT or worse.

As far as I can tell the "script restoration project" is literally blowing the doors open on all of the open ended, bad behavior with unknown incentives we've been worrying about for the past 6 years (or since Satoshi disabled the opcodes in the first place if you'd like). WTAF?

So we activating CTV or what? CoinPools are a good privacy enhancement, and we get all sorts of other goodies, too

@waxwing are you ready for a bunch of new joinmarket users? 😂

Tiffany really appreciates technical Bitcoin discussion!