1/ so this morning I was ruminating on Cortez and how he burned his ships behind him to motivate his men... and I was thinking about the complexity of building a ship (even 16th century ships were super high tech, and in an "I, Pencil" sense, no one person knew how to make one).
-
-
4/ The Spanish had already colonized the Carribean and had been hanging out there for a QUARTER OF A CENTURY before the Cortez expedition. So this was not a 3,000 mile expedition. This was more like D-Day: hop off from England and cross a small pond >>>
Show this thread -
5/ with fellow country men, ships, and supplies just a few hundred miles away. HUH! I DID NOT KNOW THAT! So, the next thing I learned was that Cortez was NOT AUTHORIZED TO PULL THIS STUNT.
Show this thread -
6/ And, in fact, word of his shenanigans got back to Cuba, and the Spanish Governor of Cuba sent out a secondary expedition to go grab Cortez by the ear, and drag him back so that he could 'spain himself. Cortez, camped in what's now Mexico City, with the ruling family >
Show this thread -
7/ kept as sort of hostages / collaborators in a Vichy France kind of way. So Cortez learned that he was in trouble, and left the city in charge of his #2 while he headed out to intercept the backup expedition, to, I dunno, try to smooth stuff over? So what did #2 do ?
Show this thread -
8/ (This is some
@hradzka -explaining-hard-right-activists stuff here) What did Cortez's #2 do, while he was unsupervised for two weeks? YES, THAT'S RIGHT, s̶e̶t̶ ̶u̶p̶ ̶a̶ ̶g̶r̶o̶u̶p̶ ̶o̶n̶ ̶D̶i̶s̶c̶o̶r̶d̶ murdered the entire royal family while they were feasting. YOLO !Show this thread -
9/ This worked ... poorly. The entire city which had already been dubious about the kinda-conquerers and their kinda-negotiated settlement realized that they were, in fact, conquers, and rose up. There was bloodshed. A wee bit.
Show this thread -
10/ several good comments herehttps://twitter.com/moheroy/status/1286704623244455936 …
Show this thread - End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.