There was a section of IBM's quantum computing challenge that had you encrypt/decrypt logical qbits by transforming their phase state to a known degree. If the state was altered in-transit, than the inverse transform will not cancel out correctly.
the challenge also mentioned that for it to work in practice, the qbits themselves would have to be transported somehow.
> Austin was just a bunch of housed and employed people quietly dying because our government is anti-humanist.
Good lord.
It was a once in a century weather event. Austin and Texas in general celebrates a limited government. So you should take responsibility and prepare accordingly.
If you seriously feel like the city government is anti-humanist and out to get you, then maybe you should pack up and leave town immediately.
> I haven't yet heard a rational explanation for just how badly ECDSA mangles the Schnorr protocol in exactly the way that means a lot of implementations end up with horrible security holes.
I thought schnorr was under patent for a bit, so an open alternative was needed? Also ECDSA does allow for recovery of the public key from the signature, which can be useful.
Gas fees are also a solution to the halting problem that comes with Ethereum's EVM (and its Turing completeness). So you are paying for space and computation.
1) miners profit from energy surplus. They do not create new power plants. Nobody is firing up a new coal plant to mine bitcoin. That is absurd.
2) miners have incentives to find and use wasted energy. For ex, flare gas recycling. Which actually helps the environment.
3) miners can turn on/off at will, and produce energy loads on demand. Which means they balance out the energy grid. Especially from erratic energy sources like wind and solar. This is already being deployed in some states.
Yes this is the crux of any social media application. I don't know if there will ever be a perfect solution.
I like that nostr abstracts this problem away from the relays. Relays only focus on storing data and handling subscriptions. They can choose to censor and/or curate content if need be, but it's not their concern.
It's up to the client to come up with a solution, and that client can be a platform or a protocol of its own.
edit it also feels really great to work on that problem from the application layer. I can come up with a solution that isn't confined to the parent protocol.
Great question! Relays aren't involved in curation or discovery, so it fall on the client.
You can request very broad subscriptions from relays! For example, here is a site that subscribes to everything, showing you a gods-eye view of events streaming into a relay:
There are several implementations of core across various languages, not including custom forks of core.