Embedded systems run into this a lot, especially on low level communication busses. It’s pretty common to have a comm bus architecture where there is just one device that is supposed to be in control of both the communication happening on the bus and what the other devices are actually doing. SPI and I2C are both examples of this, but both of those busses have architectures where there isn’t one single controller or that the devices have some other way to arbitrate who is talking on the bus. It’s functionally useful to have a term to differentiate between the two.

I’ve seen Master/Servant used before which in my experience just trips people up and doesn’t really address the cultural reason for not using the terms.

Personally I’m a fan of MIL-STD-1553 terminology, Bus Controller and Remote Terminal, but the letters M and S are heavily baked into so much literature and designs at this point (eg MISO and MOSI) that entirely swapping them out will be costly and so few people will do it, so it sticks around

I’m not really feeling it

I have the B2 which as far as I can tell has the same backing OS.

Out of morbid curiosity I connected mine to the Internet at first and watched all of the traffic it was trying to send. It’s definitely a lot but using a pi-hole to sink it’s DNS requests is surprisingly effective.

I’ve also done experiments where I told it to turn off wifi and watched to see if it ever tried to reconnect which it wouldn’t over the span of two weeks.