The central knowledge shared is that knowledge behaves like germs and can spread. Those that play on emotions spread better, and among the thought germs that spread based on emotions, the ones that play on anger spread the best.

Worst yet: There are anger based thought germs which live in symbiosis and harmony even if they cause conflict among the humans who hold that germs. You can see this take hold when communities exist entirely of folks who hold a singular belief and they spend all day constructing and destroying uncharitable straw men of opposing ideas.

I've noticed that Reddit _really_ likes this sort of content and fosters these sorts of communities. Communities at scale on reddit quickly become about fostering negatives: hatred of others, blame on the system, self-pity, snarky responses. Instead of the better and more effective: tactical empathy, acceptance and understanding what is within your personal sphere of influence, concrete actions, personal improvements, and forgiveness.

I'm definitely not saying one has to accept the world for how it is, or that it's fair, or anything like that. Humans should change this world! You should vote, you should volunteer, you should help your neighbor, you should understand and be kind to others with different beliefs, and perhaps under the extreme you should die for your beliefs to help enact them.

What you shouldn't do though is spend all day reading and posting memes about subjects you are already familiar with. If you've already made up your mind and are informed on a subject you don't need another meme to help radicalize yourself.

See the difference between mass shooters and hero's like Daryl Davis [2].

[1] https://www.youtube.com/watch?v=rE3j_RHkqJc [2] https://www.npr.org/2017/08/20/544861933/how-one-man-convinc...

As opposed to the bystanders who are suffering from every ICE vehicle sold? Make better EVs.

> You can use Amazon S3 Inventory to help manage your storage. For example, you can use it to audit and report on the replication and encryption status of your objects for business, compliance, and regulatory needs. You can also simplify and speed up business workflows and big data jobs by using Amazon S3 Inventory, which provides a scheduled alternative to the Amazon S3 synchronous List API operations. Amazon S3 Inventory does not use the List API operations to audit your objects and does not affect the request rate of your bucket.

>

> Amazon S3 Inventory provides comma-separated values (CSV), Apache optimized row columnar (ORC) or Apache Parquet output files that list your objects and their corresponding metadata on a daily or weekly basis for an S3 bucket or objects with a shared prefix (that is, objects that have names that begin with a common string). If you set up a weekly inventory, a report is generated every Sunday (UTC time zone) after the initial report. For information about Amazon S3 Inventory pricing, see Amazon S3 pricing.

https://docs.aws.amazon.com/AmazonS3/latest/userguide/storag...

Software is going to continue to play a bigger influence on everyones life. The majority of this software is going to be written by engineers of average intelligence. Having tools that are easier for everyone to use will make your life better down the line too.

Distributed databases are often conceptually modeled as a state machine. Writes are then mutations on the state machine.

With a starting state (empty database), if everyone agrees that on a fixed list of mutations which are executed in a rigidity defined ordering, you will get the same final state.

Which makes sense, right? If you run the following commands on an empty database, you would expect the same final state:

1. CREATE TABLE FOO (Columns = A, B) 1. INSERT INTO FOO (1, 2) 1. INSERT INTO FOO (3, 4)

Which would be:

``` FOO: |A|B| |-|-| |1|2| |3|4| ```

So where does "consensus" come into play? Consensus is needed to determine `mutation 4`. If the user can send a request to HOST 1 saying 'Mutation 4. should be `INSERT INTO FOO (5, 6)`' then HOST 1 will need to coordinate together with all of the other hosts and hopefully all of the hosts can agree that this is the 4th mutation and then enact that change on their local replica.

This ordering of mutations is called the transaction log.

So, why is this such a hard problem? Most of the reasons are in [Fallacies of distributed computing](https://en.wikipedia.org/wiki/Fallacies_of_distributed_compu...) but the tl;dr is that everything in distributed computing is hard because hardware is unreliable and anything that can go wrong will go wrong. Also, because multiple things can be happening at the same time in multiple places so it's hard to figure out who came first, etc.

RAFT is such an algorithm to let all of these hosts coordinate together in a fault tolerant way to figure out the 4th mutation.

Disclaimer: The above is just one use of RAFT. Another way RAFT is used in distributed databases is as a mechanism for the hosts to coordinate a hierarchy of communicate among themselves and when a host in the hierarchy is having problems RAFT can be used again to figure out another hierarchy. (Think consensus is reached on leader election to improve throughput)

This is because the MITM will not have a valid certificate to provide authenticity for the public key returned.

The reason why middle boxes in corp networks can MITM is because the the corp owns the device and has installed their own domain trust to the device. This means the MITM can return a cert and public key that your device will trust. This is because the cert returned will be signed by the installed domain trust.

Another way to think about why HTTPS is secure over radio: HTTPS is at the highest level of the OSI networking model. You could do HTTPS with pen and paper and the mail if you wanted. Think about starlink! The internet today is literally going over radio waves.

This is likely why there isn't progress on encrypting old fashion radios! There is no need to encrypt old fashioned radios -- you'll just use internet over radio instead if you wanted encryption.

You bring a good point through. Since it's radio, anyone can jam your transmissions, but, they won't be able to spoof your intended friend if you are using https via radio.

> Only thing complicated is scale. But meta has that in place.

This is silly. Scale is hard. Rolling out to massive scale on the first attempt is even harder. Within the first day they got 30 million active users without any hiccups. That's not easy. Look at AAA game launches for just how hard this is to get right.

One other thing here. They choose the right minimal set of features so that rolling out and scaling quickly would be successful. Again, that's impressive, because they didn't paint themselves into a corner supporting something that is difficult to scale successfully.

Since it was built with a lean team on a tight deadline, I can see why install size has taken a back seat. Only so many hours in a day and focusing on execution timelines and product market fit is 100x more important.

I want an app that solves a problem; not focus on a purity test.

Even beyond that, as an experienced engineer like yourself, you know sometimes you make compromises you don't necessarily agree with. Trashing others people work comes across as immature.

The job literally could not exist anywhere else because no one would pay it. But they aren't making any more land in Manhattan and they aren't building subway lines quick enough so landlords get to pass that expense off to tenants

Great example that highlights the balance of presumption of innocence with the asymmetrical bullshit principal. This person should be referred to criminal prosecution for fraud as a deterrent to others. 1,200 page reports to provide proof beyond a reasonable doubt is not scalable.