We need client apps to support content warnings, and better support of reporting content and being able to set content warnings for content you don’t post that you can choose to have your client use. This all needs to be opt-in by relays and clients, but we need this if Nostr will grow beyond bitcoiners. nostr:note1x3nqfuy7neezhpqpuge0duemuzrmr8vkkprjcwkphkrzm2ljk2mq4stcce

And your next problem kind of becomes buying voters. Find people who value a money over voting and will sell you their vote.

Australian politicians who speak languages other than English literally target community voters who cannot speak English and give them pre-signed ballots to sign. (To clarify, this is branch stacking and less so normal elections). Illegal - but no one caught has had anything happen.

Democracy is largely an illusion today. It’s not fair. It’s not the voice of people. It’s a game that people exploit - the same people who have power, to give themselves new laws, and to keep the game going.

Slight tangent… however voting is very hard to solve fairly and reliably.

Yep. If you provably burn the sats instead of transfer them them.

It doesn’t solve the double vote issue however.

I think we talked about NIP-94/95, so I am not sure how your comment is relevant. Sorry if I misunderstood! 🐶🐾🫡

🐶🐾🫡 logical move! DDoS attack opportunities are enormous with that NIP! 🐶🐾🫡

Zap validation is also expensive (network requests and computation) and multi-step and also stateful.

If I change my lud, all previous ZAPs now technically should fail validation, unless you change it back. You either need a profile/lud snapshot at the zap time, or to validate zaps instantly (read: race condition and impossible in a decentralised network) and record that outside of Nostr, to the query later.

Zaps are awesome. But they aren’t trustworthy or polished in many ways. Hopefully we can iterate.

Sats are real. PoW is real.

And you never get bad handshake issues ever?

I think these Golang websocket libraries are all broken.

Alternatively, the websocket protocol is another victim of Google stepping in and "embracing" it but adding pseudo-optional features to it such as compression and weird parameters that not all libraries support in the same way but some will assume others do support.

I just swatted my screen

every ad is a psyop,

every celebrity a shill,

every culture artificial,

a copy of a copy of a copy,

every politician a puppet,

every government a cryptocracy

be not afraid they tell us

"we have your best interests in mind"

Oh my bad 🙈 Till now I always had hashes/sec in mind. Silly me 🤦

Michael responded to my pull request and said the following

"*A pow of 7 gives you 7 leading zeros. In binary. I will rename it to "leading zero bits*"