Here is my question to you: if the node that wins the election (and the ones that accept its mined block, of course) is not the one voting on which transactions get to go into the chain, rather than be stuck in the mempool somewhere, who is? Do you genuinely think there is no decision being made there?
There is no "voting" and no "leader" except in the most abstract sense and I'm not sure why you're so determined to use those terms.
I agree that sanctimonious public health and politicians have created a lot of distrust. Their messaging is condescending, manipulative, and generates the direct opposite of what they are trying to achieve.
Public health messages need to be kept simple.
Natural immunity should be better because you are exposed to all the same proteins in the vaccine plus more and also possibly for a longer period of time and at a higher quantity.
Now that you had delta, you should be immune to delta and partially immune to whatever delta mutates into.
By simple you mean, dishonest?
People aren't as dumb as our betters believe. They pick up on obvious lies ("stop buying masks" => "everyone must wear a mask"), dishonesty ("ivermectin is for animals") and inconsistencies that fly in the face of intuition ("even if you had covid you still need the vaccination").
If the powers that be would stop trying to "shape human behavior" through lying we wouldn't see nearly the same level of vaccine hesitance and alternative medicine we do right now.
Is only conceptually true outside of "EC2 Classic", because (to the best of my knowledge) every other EC2 launches into a VPC, even if it's the default one for the account per region, and even then into the default security group (and one must specify the IDs). That may sound like "yeah, yeah" but is a level of moving parts that Lambda doesn't require a consumer to dive into unless they want to control its networking settings
I would think removing the time limit on Lambda would be like printing money since I bet per second for Lambda is greater than EC2
I doubt this is a difference marker for most medium to large sized customers though. Making a wrapper for invoking uploaded code is trivial and if done on EC2 doesn't come with the baggage of Lambda (cold starts, costlier expense, more challenging logging and debugging, lack of operational visibility, etc)
From the architecture, it's not really clear to me why Lambdas have the 15 min limitation. It seems to me AWS could use the same infrastructure to make a product that competes with Google Cloud Run. Maybe it's a businesses thing?
A lot of the novelty of Lambda is its identity as a function: small units of execution run on-demand. A Lambda that can run perpetually is made redundant by EC2, and the opinionated time limit informs a lot of design.
Right of innocent passage
Subject to this Convention, ships of all States, whether coastal or land-locked, enjoy the right of innocent passage through the territorial sea.
>Waters extending to 12 nautical miles from the shore of a coastal state. The territorial sea is under the sovereignty of the state, although foreign ships (civilian) are allowed innocent passage.
Is an 8500 ton destroyer a "civilian" ship?
I think acting offended by 'bitcoin bros' is hypocritical.
Note that this can cause issues: say you have a time sensitive application that receives a batch of "bad" messages which cause failed lambda invocations. The poller will slow down and the throughput will drop drastically, even though your intention might be for the lambda to continue processing at the same rate and power through the bad messages.
This behavior can be disabled with a support request.