The good nostr won't want me to zap anyone to make it work, it will work by being p2p.

I paid for Primal Legends because I knew they would struggle to honor their end of the deal and my money would only hurt them. With Damus, my money could hurt them, or it could help them hurt nostr, or it could help them make nostr better, but I can support that effort in better ways.

3 important things re: years of dev sats. (I don't know why I'm back weeks later, sorry)

1.

At least adding Monero and doggie coin tipping (with external wallets) shouldn't cost years of dev sats. How can we make that happen? Sure would be simpler to implement for the devs, and easier to use for users, compared to zaps. Way easier to troubleshoot and maintain, of course.

2.

If nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 / nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s is really working on P2P functionality, how many years of dev sats would it take to have a NIP spec for P2P nostr functionality that includes provisions for Tor Onion services and non-internet network protocol like ham radio meshnets and stuff?

3.

If we can make a P2P nostr spec that natively supports Onion services and ham radio meshnets and stuff without strange workarounds, how many years of dev sets would it take to ensure this P2P spec also supports a JavaScript-free, geographically neutral (as opposed to English-centric) binary "compressed nevent" format so devs in Iran can 𝕙𝕪𝕡𝕠𝕥𝕙𝕖𝕥𝕚𝕔𝕒𝕝𝕝𝕪 program a nostr client without a single English word in any line of code and still have it send compatible notes to Damus users? This is a simple spell, but quite unbreakable. Before deciding how many years of dev sats this would be, consider how the deep state will forever target anyone involved. It's a bigger deal than it might seem like.