Switching to - showing y'all this wonderful volunteer #buttercrunch#lettuce plant that decided to grow out of rocks in our front yard! What a lovely #edible surprise 😊
By the time #Biden arrived in Tel Aviv on Wednesday — amid Israeli airstrikes that had already killed >3k #Palestinians inside #Gaza, an ongoing #siege that left millions of #civilians w/o food & water & preparations for a full-scale Israeli #ground assault of the enclave — the need to buy time for Israel “to think this through,” in the words of one #US ofcl, had become a core objective of the trip.
What if there is more #Hamas resistance to a #ground attack than you anticipate, & your forces get bogged down? What about #HumanitarianAid? How will you protect #civilians? What about the hundreds of Israelis & foreigners being held #hostage? What if the #WestBank becomes a #war zone? If #Hezbollah attacks from the north? If #Iran gets directly involved?
On #Biden’s visit, Blinken said, “He is coming here at a critical moment for Israel, for the region & for the world.” The president’s plan means it is unlikely that Israel will start its #ground#offensive against #Hamas in Gaza before Wed.
Hamas’s ruthless & spectacular attack on Israel last Sat was many things: an atrocity, a display of militant ingenuity, & a demo of the weakness of #Israeli intelligence & defenses.
Hamas’s ldrs & their Iranian backers have a conscious strategy. Like almost all other acts of spectacularly bloodthirsty #terrorism, Hamas’s assault on s. #Israel was designed to provoke an emotional & equally or even more outrageous response by the targeted society. #Hamas & #Iran are attempting to goad the Israelis into #Gaza for a prolonged confrontation—which is to say that the intended effect is precisely the #ground assault Israel is now preparing in order to root out & destroy Hamas….
#Hamas surely would not have meticulously planned its audacious assault w/o also extensively planning a response to the hoped-for Israeli #counterattack on the #ground. The Israeli military will likely encounter a determined #insurgency in #Gaza. After all, #Israel has had control of the land from the outside, but not on the inside. Israeli dominion over Gaza’s coastal waters, airspace, electromagnetic spectrum, & all but one of its crossings, including the only one capable of handling goods…
US ofcls expect #Israel to launch a #ground incursion into densely populated #Gaza early this week. Israel maintains a complete air & sea #blockade of the Gaza Strip & allows only a small flow of goods & people through 2 land crossings, which have been cut off amid the fighting. Israel had also provided the enclave w/electricity.
I often like to do thought experiments while #cycling and sometimes I can’t think all the way through to the end of the answer. Here’s a recent one for #physicists who specialize in #relativity. A #bike's #wheel rotates such that the bit in contact with the #road is instantaneously at rest with respect to the #ground (no skidding), at least in #NewtonianMechanics. On the other hand, the bit diametrically opposite to it is moving at precisely twice the speed of the #bicycle...
I've got a busted consumer product here that has 2 #Holtek#microcontrollers in it. Either one would be sufficient to run this product (a brushless-motor tower fan), but #MCUs are cheap, so why not throw a second one in if it saves a few centimeters of wire?
I'm trying to determine if there's a #standard#serial#physical#layer in use here to communicate from one #MCU to the other. It's one-way communication.
The connection from one MCU to the other is a single #signal#wire, plus shared #power and #ground. It's a point-to-point link; there's no addressing involved. It's simplex, so no collision detection or anything complicated.
In fact, it's dirt-simple, and extremely low-bandwidth. The secondary MCU transmits a single #byte of data to the primary MCU approximately every 120ms. So ~70 bits per second, max.
The other MCU pulls the signal wire to #ground to xmit.
The MCUs - Holtek BS82C16A-3 and BS84B08A-3 - natively support #SPI and #I2C, but this isn't either of those.
Each #frame with one byte of data starts with a long (~10ms) low pulse (for #sync, presumably), followed by the #data line returning high for ~5ms, then the data bits are transmitted as low #pulses of different durations for 0 and 1 - 0.6ms and 2.8ms.
The eight data bits are followed by a stop/end bit, always short.
A question on Static vs Poison Point
What is the balance reason for some abilities to ignore type effectiveness while others don't....