14 years ago I ran my longest distance, 15 miles. Today, I just finished my first 18 mile run.

Combining `p` , `e` , `t` , and `word` mutes into a single list is so stupid. In order to properly support any of these features, you need an interface for two separate scenarios (private and public mutes). If you want to support all four, you need eight separate inputs. A perfect case study in why it's annoying to overload event kinds.

Let's say I run my own ecash mint. I issue myself a bunch of tokens, then I go and spend them. My mint allows the recipient to redeem them, but later on when someone (other than me) wants to melt the tokens, the mint just pretends to be offline or something. I'm then able to rug spent tokens because I own the infrastructure. It seems like the only way to defend against this attack would be for recipients to immediately melt all tokens issued by untrusted mints. Is this the standard pattern for receivers? Is mint trust model front and center in cashu implementations?

Community apps feel like the new nostr gold rush, everyone keeps building new ones that all work completely differently. I agree with their importance (obviously), but it seems like this has the potential to fragment things more than ever, just because communities are a rorschach test. Everyone also has their own libraries and preferred development stack. What if we just all agreed to start from scratch and work together to create something new? It probably wouldn't work because we're all so disagreeable, but one really good community app would be better than 10 incompatible ones.