The difference is your example uses bool values, the code in question uses expressions that (should) evaluate to bool. && is short-circuited if a is false, such that b is not evaluated.
A network for Amazon devices is certainly one use case. Another is selling network access to other IoT devices.
I would expect most residential broadband TOS would explicitly prevent reselling their network bandwidth/access. That's what you are doing with networks like Helium, even if it is in the form of a token instead of dollars. Amazon has gotten around this by just not paying. You buy the Amazon device, you provide the network access, Amazon gets the revenue.
The author is conflating max allowed bandwidth from the bridge to Sidewalk server with per-end-node bandwidth. The 80Kbps includes the bundle of all of the LoRaWAN messages it has received for all end-node-devices within range. This is a marketing point to show the Amazon device owner that this won't consume large amounts of their bandwidth. The Things Network suggests a maximum expectation of 250 BITS/s. This is not going to replace cell networks.
https://www.thethingsnetwork.org/docs/lorawan/limitations.ht...